ASU Course Registration System Usecase Model 310414 REQUIREMENTS

ASU Course Registration System Use-case Model 310414 REQUIREMENTS CAPTURE 1

ASU — USE CASES At the beginning of each semester, students may request a course catalog containing a list of course offerings needed for the semester. Information about each course, such as instructor, department, and prerequisites are included to help students make informed decisions. functional requirement: allow someone to prepare the course catalog The new 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 is canceled. No course offering will have more than ten students or fewer than three students. A course offering with fewer than three students will be canceled. functional requirement: allow students to register for courses 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. functional requirement: provide information to the billing system 310414 REQUIREMENTS CAPTURE 2

ASU — USE CASES Professors must be able to access the online system to indicate which courses they will be teaching, and to see which students signed up for their course offerings. functional requirement: allow professors to select course to teach allow professors to request course enrollment list For each semester, there is a period of time that students can change their schedule. Students must be able to access the system during this time to add or drop courses. functional requirement: part of the course registration process for students 310414 REQUIREMENTS CAPTURE 3

ASU — ACTORS AND FUNCTIONAL REQUIREMENTS Registrar Student Billing System Professor 310414 A person who is responsible for maintaining the curriculum information inclusive of students, professors and courses. The Registrar uses the Registration System to prepare the course catalogue for the coming semester. A person who is registered to take classes at the university. A student uses the Registration System to register for courses in the current or a future semester. An external system responsible for billing students. Once a student successfully registers for a semester, the billing system is notified with billing information from the Registration System. A person who is part of the teaching staff of the university. A professor uses the Registration System to make choices on the courses to teach and to request course enrolment lists. REQUIREMENTS CAPTURE 4

ASU — USE CASES Maintain student information Maintain professor information Registrar Maintain course information Prepare course catalogue Student Register for courses Select courses to teach Professor Time Prepare billing information Billing System 310414 Request enrollment list «communication» association (implicit) REQUIREMENTS CAPTURE 5

ASU — USE-CASE SPECIFICATION Register for courses This use case describes the process of how a student registers for a course offering. It provides the capability to create and modify a student’s study schedule for the coming semester. Initial Flow of Events 1. The Student studies the course offerings for a semester to determine which courses to select. 2. The Student indicates her primary choice of courses, up to a maximum of four. 3. The Student indicates her alternate choice of courses, up to a maximum of two. 4. end The student can add or drop courses from their schedule until the of the add/drop period. 310414 REQUIREMENTS CAPTURE 6

ASU — USE-CASE SPECIFICATION Select courses to teach This use case describes how a professor can select courses to teach for a desired semester that has not started yet. Initial Flow of Events 1. The Professor selects a course offering for a semester. 2. the The Professor either adds or deletes himself as the instructor for course offering. 310414 REQUIREMENTS CAPTURE 7

ASU Course Registration System Use-case Detail Flow of Events Specification 310414 REQUIREMENTS CAPTURE 8

ASU — USE-CASE DETAIL Select courses to teach This use case describes how a professor can select courses to teach for a desired semester that has not yet started. Actors Invoked by: Professor Preconditions 1. The course offerings available for the professor to select must not have been open to students yet. Basic Path 1. The use case starts when the professor selects the option Select courses to teach. 2. The system prompts the professor to enter the semester in which he would like to teach courses. (A 1) 3. The professor is prompted to select one of the following options: CREATE, REVIEW, or MODIFY. 4. The professor makes a selection. 310414 REQUIREMENTS CAPTURE 9

ASU — USE-CASE DETAIL (cont’d) 5. If the option CREATE is chosen 5. 1. The S 1: Create a schedule subflow is performed. (A 2) 6. If the option REVIEW is chosen 6. 1. The S 2: Review a schedule subflow is performed. 7. If the option MODIFY is chosen 7. 1. The S 3: Modify a schedule subflow is performed. (A 3) 8. The user is prompted to re-select one of the available options again until he indicates that he does not want to carry out any further activities for the given semester. 9. The use case ends. Subflows S 1: Create a schedule 1. The system prompts the professor to enter the course codes that he would like to teach in the given semester. 2. The professor enters the information. (A 4) 3. The system validates the information entered. (A 5) 4. The system updates the information in the database. 5. The system notifies the professor that the request has been processed. 310414 REQUIREMENTS CAPTURE 10

ASU — USE-CASE DETAIL (cont’d) S 2: Review a schedule 1. The professor requests information of his teaching schedule for a given semester. 2. The system retrieves the corresponding information and displays all courses that the professor has selected to teach including course name, course code, course offering number, days of the week, time, and location. S 3: Modify a schedule 1. The system checks that the final date for changes has not passed. (A 6) 2. The system retrieves and displays the professor’s teaching schedule. 3. The system prompts the professor to make a change on his schedule that includes adding and deleting courses. 4. If the professor wants to add a course 4. 1. The S 3. 1 Add courses subflow is performed. 5. If the professor wants to delete a course 5. 1. The S 3. 2 Delete courses subflow is performed. 310414 REQUIREMENTS CAPTURE 11

ASU — USE-CASE DETAIL (cont’d) S 3. 1: Add courses 1. The professor indicates which further course(s) to teach. (A 4) (A 5) 2. The system validates the information. 3. The system adds the course(s) to the professor’s teaching schedule for the given semester. 4. The system notifies the professor that the request has been processed. S 3. 1: Delete courses 1. The professor indicates which course(s) not to teach. (A 4) 2. The system removes the course(s) from the professor’s teaching schedule for the given semester. 3. The system notifies the professor that the request has been processed. 310414 REQUIREMENTS CAPTURE 12

ASU — USE-CASE DETAIL (cont’d) Alternate Paths A 1. If the semester that the professor enters is invalid, no desired activity will be performed. Also, the system will prompt the professor to re-enter a valid semester or terminate the use case. A 2. If an attempt is made to create a teaching schedule for a semester where a schedule already exists, the system will prompt for another choice to be made. A 3. If the professor has not selected any courses to teach in the given semester, the system will notify him that this function is not available to him currently and prompt him to re-enter a valid semester or terminate the use case. A 4. The professor cancel the process at any time before the confirmation. A 5. If any code entered is invalid, the system will prompt the professor to re-enter another one or terminate the use case. A 6. If the final date for changes has passed, the system will reject the request and the use case ends. Postconditions 1. The course offerings available for the professor to select must still not be open to students yet. 310414 REQUIREMENTS CAPTURE 13

ASU Course Registration System Use-case Detail Include Relationship 310414 REQUIREMENTS CAPTURE 14

ASU — USE-CASE DETAIL: INCLUDE Add a new student subflow of Maintain student information Basic Path 1. The system loads a blank student information form onto the screen. 2. The user fills in the student information inclusive of student ID. 3. The user confirms the entered information. 4. Include(Validate The system checks person the correctness information). of the entered information. 5. The system checks … the correctness of the entered student-specific information. 6. The system. . . Validate person information Basic Path 1. The use case starts when the flow of control is passed from the Maintain professor information or Maintain student information use cases. 2. The surname of the person is validated to be non-null and to contain ASCII characters only. . 310414 REQUIREMENTS CAPTURE 15

ASU Course Registration System Use-case Detail Extend Relationship 310414 REQUIREMENTS CAPTURE 16

ASU — USE-CASE DETAIL: EXTEND Select courses to teach Basic Path 1. The use case starts when the professor selects the option Select courses to teach. 2. The system prompts the professor to enter the semester in which he would like to teach courses. (A 1) 3. <semester The systeminvalid>. . . 3. The system. . . Invalid semester Basic Path 1. This use case is initiated when an invalid semester is entered. 2. The system will prompt the professor to re-enter a valid semester or terminate the use case. è an extension requires a condition to be evaluated to determine whether to execute it 310414 REQUIREMENTS CAPTURE 17