Object Oriented System Analysis and Design

Use Case Name: Maintain Class Records

ID:

Importance Level:

Primary Actor: School Staff

Use Case Type: Detail, Essential

Stakeholders and Interests:

School Staff – maintain (create, edit, modify, and delete) class records for a given course

Brief Description:

This CRUD (Create, Read, Update, and Delete) use case maintains the school records of the classes it offers (in a course by course fashion). It provides the School Staff actor with complete control over the creation, deletion, modification and the reading of class records for a given course.

Trigger: A School Staff wanting to maintain the class records for a given course

Type: External

Relationships:

Association: School Staff

Include: Login

Normal Flow of Events:

1. Staff executes the login into SRS use case.

2. Staff enters the course whose class is to be maintained or added.

3. A list of all classes (either online or face-to-face) for the entered course is displayed.

4. If a class is to be maintained, then staff selects one of the classes and chooses Delete or Modify.

5. If a class is to be added, then add Class Begin Date, and Class End Date. a. If a class is online, add Class URL, Class Browser b. If a class is face-to-face, add Class Building, Class Room

SubFlows:

Alternate/Exceptional Flows:

2a: When the course entered does not exist in the system

Use Case Name: Register Student for Classes

ID:

Importance Level:

Primary Actor: School Staff, Student

Use Case Type: Detail, Essential

Stakeholders and Interests:

Student – self-register for classes

School Staff – register on behalf of students

Brief Description:

This use case enables the actor to select a class (either online or fact-to-face) and then registers a student for the selected class provided that the student meets the registration requirements for the class

Trigger: an actor (Student, School Staff) who wants to register a student for a class

Type: External

Relationships:

Association: Student, School staff

Include: Login

Normal Flow of Events:

1. Staff or student executes the login into SRS use case.

2. The student is identified implicitly from the login (if the actor is a Student) or by explicitly entering the student ID (if the actor is a School Staff) and verifying it

3. A list of available courses is displayed.

4. The actor enters the course to register for.

5. A list of classes (online and face-to-face) offered for the selected course is displayed.

6. The actor then selects a class from the list of classes.

7. Perform S-1_Validate_Registration_Rules.

8. If registration rules are verified, then the student is registered for the class and the registration is confirmed. If not, then an error message is printed to the actor with the reason why registration cannot be completed at this time

SubFlows:

S-1_Validate_Registration_Rules

a. Class is open for registration.

b. No duplicate registration for class.

c. If online class, then student acknowledged they have required hardware and software.

d. If GPA is < 3.5, then no more than 3 class registrations for semester.

Alternate/Exceptional Flows:

2a: When the entered student ID is not found in the system, an error message is displayed.

Student can drop the class which is recorded in registration record. If the student completes the class, a grade is added to registration record