COURSE REGISTRATION SYSTEM ANALYSIS 1
Programming Assignment Unit 5
Software Engineer 2 (CS 4403)
University of the People
Course Registration System: An Object-Oriented Analysis 2
Introduction:
I have opted for the “Course Registration System” outlined in the appendix as prescribed
by the course in Conger’s The New Software Engineering. This analysis employs an object-
oriented approach to delve into the intricacies of the system. Due to the absence of a customer
interview, a comprehensive summary paragraph is crafted to highlight the essential high-level
processes.
The Course Registration System operates through a series of steps, starting with the
student’s initiation of a registration request, whether through mail or online, after selecting a
course. The received request is then automatically entered into the system or processed by the
Administration clerk. Subsequently, the system interfaces with ARS (Accounts Receivable
subsystem) to check for unpaid fees. If outstanding fees exist, the student receives a bill for
settlement. Conversely, if there is no outstanding balance, the system navigates through the
transcript database to verify prerequisites.
Upon confirming the satisfaction of prerequisites, the system proceeds to assess seat
availability in the selected course. If prerequisites are unmet or the course is closed, the system
Course Registration System: An Object-Oriented Analysis 3
promptly rejects the registration request and notifies the student. However, if all prerequisites are
met and there is an available seat, the system successfully registers the student, notifying them of
the successful registration. Additionally, the student’s registration details are seamlessly
integrated into the enrollment report for the Instructor. When all seats are filled, the enrollment
report is promptly dispatched to the instructor.
Noun Space Object
Student P Student
Courses S Course
Registration Request P RegRequest
Transcript S Transcript
Enrollment Report S EnrollReport
Analysis of the Course:
Given the absence of inheritance in this application, there is no necessity for a
generalization-specialization classes diagram. Nonetheless, the classes cardinality diagram holds
significance for this project. A student has the ability to enroll in one or more courses, while each
course may encompass zero or multiple successfully registered students. The transcript can
accommodate zero or more course records per student. Finally, a singular course can generate
multiple enrollment reports over a specified period.
Conclusion:
In conclusion, this object-oriented analysis provides a detailed exploration of the Course
Registration System. It emphasizes the critical processes involved in student course registration
Course Registration System: An Object-Oriented Analysis 4
and the interactions with relevant subsystems. The refined Object List delineates entities
essential to both problem and solution spaces, streamlining the understanding of the system’s
intricacies.
References:
Conger, S. (2008). The New Software Engineering.
[Link]
