Scenario: Sweetbriar College is redesigning their course registration system [CRS]. They plan for this system to be web-based, but first you need to model the main system behind the web interface. Here is a description of the interactions with the proposed CRS.
Faculty enter courses into the system, assign section numbers, instructors, dates, times, and classrooms for individual instances of a course. Students can browse available course-sections. Students or faculty advisors can register students for course-sections. Faculty can view a class list and enter grades for a course-section they are teaching. Students can view their course schedule and their grades for individual courses. The Registrar's office can view a student's history of courses and grades.
Using our Sweetbriar College scenario, evolve your Object Class Diagram for the CRS into design packages. Include packages for the Human Computer Interface [HCI] layer, the application layer, and the data management [DM] layer.
Expand the application layer package for the CRS. Include packages for Faculty and Staff, Students, and Courses.
Expand the HCI layer package for the CRS. Include packages for Faculty and Staff interface, and Student interface.
Expand the Sequence Diagram you developed for 'Student Registers for Course-Section' so that it includes the objects from the HCI layer and the DM layer.
Expand the Sequence Diagram you developed for 'Faculty Creates New Course-Section' so that it includes the objects from the HCI layer and the DM layer.