Use case tutorial examples

Example 1 Question2: Online registration system King AbdulAziz University established a new online registration system for external students . At the beginning of each semester students may request a course catalogue containing a list of course offerings for the semester. Information about each course, such as professor, department, and prerequisites will be included to help students make informed decisions. The new on-line registration system will allow students to select four course offerings for the coming semester. In addition, each student will indicate two alternative choices in case a course offering becomes filled or canceled. No course offering will have more than ten students. No course offering will have fewer than three students. A course offering with fewer than three students will be canceled. Once the registration process is completed for a student, the registration system sends information to the billing system, so the student can be billed for the semester. Professors must be able to access the on-line system to indicate which courses they will be teaching. They will also need to see which students signed up for their course offering. For each semester, there is a period of time that students can change their schedules. Students must be able to access the on-line system during this time to add or drop courses. The billing system will credit all students for courses dropped during this period of time.

Example 1(cont..) You are required to Maintain Use-case Diagram. Write the use-case description using the expanded format (with typical course of events and alternatives sections) for manage schedule use-case, create schedule, add course, delete course.

Use case diagram View Students Manage schedule View Course professor student <<extend>> <<extend>> <<extend>> biling system <<Include>> < <Include>> Use case diagram View Students Manage schedule View Course Receive information Create course Add course Delete course View catalogue

Manage schedule Use case Name: manage schedule. Actor: student, billing system. Description: The use case begins when the student wants to create schedule for the next semester or update his current schedule. Type: primary, essential. Cross reference: add, delete and create. Precondition: the student has an account in the system.  

Expanded use case (cont..) Typical course of event Actor Action System response 1. This use case begins when the student enters the student id number. 2.The system verifies that the student id number is valid 3. Prompts the student to select the semester #.  4. The student enters the desired semester. 5. display choices 6. The student selects to the desired operation 7. The student indicates that the activity is complete… 8. The system will print the student schedule and notify the student that registration is complete. 9. The system sends billing information for the student to the billing system for processing.

Expanded use case (cont..) Alternatives Alternative at 2: If an invalid id number is entered, the system will not allow access to the registration system. Alternative at 5: If the student select current semester, system will display (update schedule). If student select next semester, system will display (create). Alternative at 6 Extension point: If student select create, go to create use-case. Extension point: If student select add, go to add use-case Extension point :If student select drop, go to drop use-case

Create Use case Actor Action System response 1. the student view available course using view catalog use-case 2. The student enters 4 primary course offering numbers and 2 alternate course offering numbers. 3. The student then submits the request for courses 4. Checks those prerequisites are satisfied for the requested course. 5. Adds the student to the course offering if the course offering is open. Alternative at 5: If a primary course offering is not available, the system will substitute an alternate course offering.

Add course Use case Actor Action System response 1. the student view available course using view catalog use-case 2. The student indicates which course offerings to add. 3. The system checks that the final date for changes has not been exceeded. 4. The system then: Verifies that the maximum course load for the student has not been exceeded. Checks that prerequisites are satisfied for the requested course. Adds the student to the course offering if the course offering is open Alternative at 4: if the system can't add the course for any reasons, then it will display a message to indicate that.

Delete course Actor Action System response 1. The student indicates which course offerings to delete. 2. The system checks that the final date for changes has not been exceeded. 3. The system deletes the student from the course offering. 4.The system notifies the student that the request has been processed Alternative at 3: if minimum course load for the student was exceeded due to the delete, then drop operation will stop.

Use case-example The Indian railways wish to develop a ticketing and reservation system. This must support advance booking of tickets and change of class of a ticket. All this is handled by the reservation clerk. The system will also have a web interface where the users can register themselves and purchase tickets online. They can pay either by using their online banking account or by credit cards or by VPP. Reservations made over the internet can be canceled across the counter. The users can also print the tickets. The seats are updated when ever the reservation is made or canceled . In case of payment failure a notification is generated by the system The system will also have querying facility that allows users to check train timetables, fares and availability of tickets.

Use cases Cancel reservation Make Reservation Register as member Modify Class Print ticket Check fare Query timetable Make Payment

HW You are required to Maintain Use-case Diagram. Write the use-case description using the expanded format (with typical course of events and alternatives sections) for make reservation;