310414 requirements capture 1 asu course registration system use-case model

310414310414 REQUIREMENTS CAPTUREREQUIREMENTS CAPTURE1

ASU Course Registration SystemASU Course Registration System

Use-case ModelUse-case Model


ASU — USE CASESASU — 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



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


ASU — ACTORS AND FUNCTIONAL REQUIREMENTSASU — ACTORS AND FUNCTIONAL REQUIREMENTS

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 theuniversity. 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 theuniversity. A professor uses the Registration System to make choices on the courses to teach and to request course enrolment lists.

Registrar

Billing System

Student

Professor



Register for coursesStudent

Billing System

Professor

Request enrollment list

Select courses to teach

Registrar

Maintain course information Prepare course catalogue

Maintain student information Maintain professor information

Prepare billing information

Time

«communication» association (implicit)


ASU — USE-CASE SPECIFICATIONASU — 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 determinewhich courses to select.

2. The Student indicates her primary choice of courses, up to amaximum of four.

3. The Student indicates her alternate choice of courses, up to amaximum of two.

4. The student can add or drop courses from their schedule until the end of the add/drop period.


ASU — USE-CASE SPECIFICATIONASU — USE-CASE SPECIFICATION


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 Professor either adds or deletes himself as the instructor for the course offering.



Use-case DetailUse-case Detail

Flow of Events SpecificationFlow of Events Specification


ASU — USE-CASE DETAILASU — USE-CASE DETAIL


This use case describes how a professor can select courses to teach for a desiredsemester that has not yet started.

ActorsInvoked by: Professor

Preconditions1. The course offerings available for the professor to select must not have been

open to students yet.

Basic Path1. 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. (A1)3. The professor is prompted to select one of the following options: CREATE,

REVIEW, or MODIFY.4. The professor makes a selection.


ASU — USE-CASE DETAIL (cont’d)ASU — USE-CASE DETAIL (cont’d)

5. If the option CREATE is chosen5.1. The S1: Create a schedule subflow is performed. (A2)

6. If the option REVIEW is chosen6.1. The S2: Review a schedule subflow is performed.

7. If the option MODIFY is chosen7.1. The S3: Modify a schedule subflow is performed. (A3)

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

S1: Create a schedule1. 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. (A4)3. The system validates the information entered. (A5)4. The system updates the information in the database.5. The system notifies the professor that the request has been processed.



S2: Review a schedule1. 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.

S3: Modify a schedule1. The system checks that the final date for changes has not passed. (A6)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 S3.1 Add courses subflow is performed.5. If the professor wants to delete a course

5.1. The S3.2 Delete courses subflow is performed.



S3.1: Add courses1. The professor indicates which further course(s) to teach. (A4) (A5)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.

S3.1: Delete courses1. The professor indicates which course(s) not to teach. (A4)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.



Alternate PathsA1. 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.

A2. 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.

A3. 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.

A4. The professor can cancel the process at any time before the confirmation.A5. If any code entered is invalid, the system will prompt the professor to re-enter

another one or terminate the use case.A6. If the final date for changes has passed, the system will reject the request and

the use case ends.

Postconditions1. The course offerings available for the professor to select must still not be open

to students yet.




Include RelationshipInclude Relationship


Validate person information

Basic Path1. 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....

4. The system checks the correctness of the entered information.5. The system …

ASU — USE-CASE DETAIL: INCLUDEASU — USE-CASE DETAIL: INCLUDE

Add a new student subflow of Maintain student information

Basic Path1. 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 person information).5. The system checks the correctness of the entered student-specific information.6. The system . . .




Extend RelationshipExtend Relationship




teach.2. The system prompts the professor to enter the semester in which he would like

to teach courses. (A1)3. The system ...

ASU — USE-CASE DETAIL: EXTENDASU — USE-CASE DETAIL: EXTEND

Invalid semester

Basic Path1. 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 evaluatedto determine whether to execute it



teach.2. The system prompts the professor to enter the semester in which he would like

to teach courses.<semester invalid>

3. The system ...

310414 requirements capture 1 asu course registration system use-case model

Documents