Evaluation #67906
Details
903937351
asalunke8@gatech.edu
Accepted Applicant
pglenn8
4901 Evergreen Rd, Dearborn, MI 48128-1491
United States
[ 122861 ]
Computer Science II
Winter 2025
(Semester Basis)
4 credit hours
0.25
( Basis)
credit hours
CS 1XXX, 1 credit hours
Not Policy
CS 1XXX, 1 credit hours
Not Policy
dept-to-r1
Options
Notes
2025-07-21 16:01:06 - Pauline Marilyn Glenn <pglenn8>
Note for Reg: One time CS 1331 credit for this student here. Note for student: Faculty reviewer suggests you review the following resource to prep for CS 1332: https://www.edx.org/certificates/professional-certificate/gtx-introduction-to-object-oriented-programming-with-java
2025-07-21 15:20:21 - Adi Ashish Salunke <asalunke8>
Hello, I’d like to clarify that CIS 200 was specifically designed to deepen our understanding of object-oriented programming (OOP) concepts using C++. The course intentionally built on the foundational material from CIS 150, which introduced us to the basics of C++ programming. CIS 200 expanded upon that foundation by introducing more advanced OOP structures, including classes, inheritance, recursion, exception handling, and complex data structures such as trees and hash tables — all through C++. Java was not part of the CIS 200 curriculum, as our academic track planned for Java to be taught in a separate dedicated course, which was scheduled for the following semester. The goal was to ensure that we developed a strong, language-specific grasp of OOP principles in C++ first, before moving into Java. This approach was intended to give us a deeper and clearer understanding of the underlying concepts rather than merging multiple languages at once. As such, while CIS 200 did not include Java, it thoroughly fulfilled the role of an advance-level OOP course, with rigorous implementation in C++. I hope this explanation helps in evaluating its transferability. Please let me know if any additional information would be helpful. Best regards, Adi Salunke
2025-07-21 15:20:06 - Adi Ashish Salunke <asalunke8>
Hello, I’d like to clarify that CIS 200 was specifically designed to deepen our understanding of object-oriented programming (OOP) concepts using C++. The course intentionally built on the foundational material from CIS 150, which introduced us to the basics of C++ programming. CIS 200 expanded upon that foundation by introducing more advanced OOP structures, including classes, inheritance, recursion, exception handling, and complex data structures such as trees and hash tables — all through C++. Java was not part of the CIS 200 curriculum, as our academic track planned for Java to be taught in a separate dedicated course, which was scheduled for the following semester. The goal was to ensure that we developed a strong, language-specific grasp of OOP principles in C++ first, before moving into Java. This approach was intended to give us a deeper and clearer understanding of the underlying concepts rather than merging multiple languages at once. As such, while CIS 200 did not include Java, it thoroughly fulfilled the role of an advance-level OOP course, with rigorous implementation in C++. I hope this explanation helps in evaluating its transferability. Please let me know if any additional information would be helpful. Best regards, Adi Salunke
2025-07-21 07:24:38 - Jake D Vaughn <jvaughn67>
Please upload/resubmit and return to Registrar (R1) a response to this inquiry from the department - "Note for student: Do you have documentation of coverage of java in any class? "
2025-07-17 15:48:45 - Pauline Marilyn Glenn <pglenn8>
Note for student: Do you have documentation of coverage of java in any class?
2025-07-15 15:48:46 - Adi Ashish Salunke <asalunke8>
Hello, I’d like to provide further clarification regarding the CIS 200 course I completed and its coverage of event-driven programming. During the course, we had a dedicated discussion and focus on the event-driven programming paradigm, particularly in the context of interactive user-based applications. Event-driven programming is a model where the program’s flow is determined by user actions or system events — such as button clicks, text input, or menu selections. It often requires the program to wait for input and then react accordingly, rather than executing sequentially from start to finish. To reinforce our understanding, we were assigned Lab 09, which required us to build an interactive address book application in C++ using a Binary Search Tree (BST). The key component of this lab was implementing a menu-driven interface where users could: - Add a new contact - Remove an existing contact - Display all contacts in alphabetical order The program dynamically responded to the user’s input choices, and each operation was triggered as a result of runtime input — aligning with the event-driven paradigm. Through this lab, I gained hands-on experience with structuring programs to respond to user-initiated events, managing input validation, and designing logic that reacts to external actions. To support this explanation, I’ve attached: - The official Lab 09 prompt that outlines the lab objectives and event-driven requirements - My official submitted lab report, which includes both the code implementation and a reflection of the challenges and concepts addressed I hope this documentation confirms that I’ve not only been introduced to but have also successfully applied event-driven programming principles in an academic setting. Please let me know if any additional information is needed. Best regards, Adi Salunke
2025-07-15 15:47:17 - Adi Ashish Salunke <asalunke8>
Hello, I’d like to provide further clarification regarding the CIS 200 course I completed and its coverage of event-driven programming. During the course, we had a dedicated discussion and focus on the event-driven programming paradigm, particularly in the context of interactive user-based applications. Event-driven programming is a model where the program’s flow is determined by user actions or system events — such as button clicks, text input, or menu selections. It often requires the program to wait for input and then react accordingly, rather than executing sequentially from start to finish. To reinforce our understanding, we were assigned Lab 09, which required us to build an interactive address book application in C++ using a Binary Search Tree (BST). The key component of this lab was implementing a menu-driven interface where users could: - Add a new contact - Remove an existing contact - Display all contacts in alphabetical order The program dynamically responded to the user’s input choices, and each operation was triggered as a result of runtime input — aligning with the event-driven paradigm. Through this lab, I gained hands-on experience with structuring programs to respond to user-initiated events, managing input validation, and designing logic that reacts to external actions. To support this explanation, I’ve attached: - The official Lab 09 prompt that outlines the lab objectives and event-driven requirements - My official submitted lab report, which includes both the code implementation and a reflection of the challenges and concepts addressed I hope this documentation confirms that I’ve not only been introduced to but have also successfully applied event-driven programming principles in an academic setting. Please let me know if any additional information is needed. Best regards, Adi Salunke
2025-07-15 13:52:58 - Jake D Vaughn <jvaughn67>
Please upload/resubmit and return to Registrar (R1) a response to this inquiry from the department - "Note for student: Do you have any documentation of coverage of event driven programming? Please provide if you do."
2025-07-15 11:06:06 - Pauline Marilyn Glenn <pglenn8>
Note for student: Do you have any documentation of coverage of event driven programming? Please provide if you do.
2025-06-20 10:17:59 - Adi Ashish Salunke <asalunke8>
CIS 200 – Computer Science II was a continuation of CIS 150 and expanded on core programming principles using the C and C++ languages. The course emphasized object-oriented programming (OOP) concepts, including classes, inheritance, encapsulation, polymorphism, and dynamic memory management. It combined lecture-based instruction with hands-on, practical application of these topics through structured lab sessions. The lab component had its own dedicated meeting time separate from the lecture sessions and was a required part of the course. These labs involved weekly coding exercises, debugging practice, and project-based assignments aligned with the course material. However, despite the separate schedule, the lab was not offered as a standalone course and did not carry its own course registration or credit hours. All lab work was fully integrated into the grading structure of CIS 200, and the final grade for the course reflects performance in both the lecture and lab components combined. There is no separate lab grade or credit recorded on the transcript. When submitting this course for evaluation, I attempted to indicate that the lab carried “0 credit hours,” as accurately reflected in the course structure. However, the portal did not allow submission with a 0-credit entry, so I entered “0.25 credit hours” as a placeholder. I want to emphasize that the lab component was not assigned separate credit and is fully embedded within the overall CIS 200 grade. Additional Note: The syllabus provided for this course displays “Fall 2024” as the term. This is because the instructor typically reuses and updates the same base syllabus document across terms without changing the term label. However, I can confirm that this was the actual syllabus we followed during the course and that all material, assignments, and policies were consistent with what was stated in it.
Trail Log
2025-07-22 11:55:14
Final equivalencies entered by Alyssa Russo (arusso39) Final equiv: CS 1331 (3 hrs) AND CS 1XXX (1 hrs). Not policy. Phase set to Complete.
2025-07-21 16:01:06
Draft equivalencies entered by Pauline Marilyn Glenn (pglenn8) Draft equiv: CS 1331 (3 hrs) AND CS 1XXX (1 hrs). Not policy. Phase set to Registrar 2.
2025-07-21 15:25:31
Assigned to Pauline Marilyn Glenn (pglenn8) by Jake D Vaughn (jvaughn67). Phase set to Department.
2025-07-21 15:20:21
Resubmitted to Registrar 1 by Adi Ashish Salunke (903937351). Phase set to Registrar 1.
2025-07-21 07:24:38
Sent back to Student by Jake D Vaughn (jvaughn67). Phase set to Student. Must be resubmitted.
2025-07-17 15:48:45
Pass by Pauline Marilyn Glenn (pglenn8). Returned to Registrar's Office without evaluating. Phase set to Registrar 1.
2025-07-15 16:34:31
Assigned to Pauline Marilyn Glenn (pglenn8) by Shannon Davis (sdavis376). Phase set to Department.
2025-07-15 15:48:46
Resubmitted to Registrar 1 by Adi Ashish Salunke (903937351). Phase set to Registrar 1.
2025-07-15 15:48:19
Supplemental file attached to evaluation by Adi Ashish Salunke (903937351).
2025-07-15 15:48:02
Supplemental file attached to evaluation by Adi Ashish Salunke (903937351).
2025-07-15 13:52:58
Sent back to Student by Jake D Vaughn (jvaughn67). Phase set to Student. Must be resubmitted.
2025-07-15 11:06:06
Pass by Pauline Marilyn Glenn (pglenn8). Returned to Registrar's Office without evaluating. Phase set to Registrar 1.
2025-06-25 10:41:26
Assigned to Pauline Marilyn Glenn (pglenn8) by Shannon Davis (sdavis376). Phase set to Department.
2025-06-20 10:17:59
Evaluation initiated by Adi Ashish Salunke (903937351). Phase set to Registrar 1.