1. Object Oriented Software Modeling and Design CE 350 Abdel-Karim Al-Tamimi, Ph.D. [email_address] http://faculty.yu.edu.jo/altamimi Al-Tamimi 2011 ©

9. Door Master: Initial Use-Case Diagram Al-Tamimi 2011 ©

11. Door Master: Refined Use-Case Diagram Al-Tamimi 2011 ©

13. Door Master: Refined Use-Case Diagram Al-Tamimi 2011 ©

20. CRS: Initial Use-Case Diagram Al-Tamimi 2011 ©

25. Documenting Use-Cases Formal Style Al-Tamimi 2011 © Use case name Register Courses Use case ID UC-100 Super use case - Actor(s) Primary Actor(s): Student Secondary Actor(s): Billing System Brief description The student initiates the use case to create, read, update or delete a course for the coming semester Preconditions Registrations for the Semester are open to Students. Post-conditions A Schedule has been created/updated for a Student.

27. Documenting Use-Cases Formal Style Al-Tamimi 2011 © Alternative flows and exceptions 1a: Invalid Student Details Entered 1. The System denies access and displays an error message 2. The use case resumes at step 1 (of Primary flow)  Continued on next slide Priority High Non-behavioral requirements The system should be able to handle at least 10,000 students concurrently Assumptions Issues Refer to UI Specification xxx for the user interface associated with this use case Source User Interview Memo 21, 8/9/01

28. Documenting Use-Cases Formal Style Al-Tamimi 2011 © Alternative flows and exceptions 2 : Student Selects to Create a Schedule 1. The System checks that the Student does not already have a Schedule for the upcoming semester. 2. The Student selects 4 primary course offerings, 2 alternative course offerings and submits their selections. 3. The System checks that the prerequisites are satisfied and adds the Student to the course offerings. 4. The System generates charges associated with the selections made. 5. The use case resumes at step 4 (of Primary flow). 3 : Student has an existing Schedule IRM Training - White Paper 1. The System displays an error stating the Student already has an existing Schedule and cannot create a new one. 2. The use case resumes at step 2 (of Primary flow).