Universities nowadays have their own online registration system to facilitate the course registration process where each student can use it to register for his/her courses before the semester begins. The system also enables the staff of each academic department to examine the course offered by their department, add and remove courses, and change the information about them (e.g., the maximum number of students permitted, course description, unique course number, course name, section number, time, etc.). It should permit students to examine currently available courses, add and drop courses to and from their schedules, and examine the courses for which they are enrolled. The system will allow the student to register for a single course only once and will allow them to print their schedule for the semester. Department staff should be able to print a variety of reports about the courses and the students they are enrolled in them. The system should ensure that any student will take no less than three courses and no more that five courses for each semester. Students who have any unpaid fees are not permitted to register (assume that a fees data store is maintained by the university’s financial office, which the registration system accesses but does not change). On the other hand, the system will allow the instructors to print reports about the courses they teach and the list of students enrolled in each course. Each user will maintain a user name and password that will allow him/her to access the system.
1. Create a Class diagram for the OUR system. Identify the classes and use the appropriate relationships along with the required multiplicities.
2. An object diagram shows a snapshot of the detailed state of a system at a point in time. Choose two use-cases (scenarios) fromOURsystem (Refer to your use case diagram), and draw twoObject diagramsshowing instances of a classes that play a part in your use-case scenarios.Note that, all the used objects in your diagram should be instantiated from the classes identified in your class digram (Make sure to identify the Use Case your are referring to).
3. Create a set of CRC cards listing all the attributes and the collaborations for all the potential classes of the OUR system.
