Problem Statement

LCO wants to computerize its registration system

5. The Registrar sets up the curriculum for a semester
6. Students select 3 ~ 5 courses
7. Once a student registers for a semester, the billing system is notified so the student may be billed for the semester
8. Once a student registers for a semester, the registrar is notified as well for records
9. Students may use the system to add/drop courses for a period of time after registration
10. A class cannot exceed 20 students
    • Otherwise, the class is closed
11. Professors use the system to set their preferred course offerings and receive their course offering rosters after students register
    • The teaching load at LCO is that a professor teaches 2 ~ 4 courses a semester
    • One course may have several offerings, i.e., a course may be offered in several sessions.

Q1: Please draw a use case diagram to illustrate the functionality of the system. Please identify actors, use cases, and associations between actors and use cases. (10 pts)

Q2: Assume that there is a use case of Create a course by registrar. Normally, a course form is used when creating a course. The course form includes the course information, e.g., course name, course id (e.g., SE4433), prerequisites, and credit hours. Please draw a sequence diagram for this use case ONLY. (10 pts)

Q3: Please draw a class diagram for the above problem statement. (80 pts)

• For a class, you need to include attributes and operations if such information is needed by other classes
  • If you have included attributes and operations, please define their visibility
• Identify the relationship between classes
  • For associations, please also identify multiplicity
• Please pay attention to the relationship between a sequence diagram and a class diagram, i.e., the information should be consistent between the sequence diagram and the class diagram.

Attention: Please use a UML tool to draw these diagrams. A good choice is StarUML.