-
Notifications
You must be signed in to change notification settings - Fork 5
Detailed Use Case Descriptions
Title: Verify a new tutor
Actors: Company Manager
Intention: The intention of the company manager is to verify a new tutor by approving or rejecting them
Precondition: User is in the application and is already logged in
Main Scenario:
- System displays a list of new tutors applications.
- User selects the tutor of his choice.
- System acknowledges User’s request.
- System displays the full name of the tutor alongside their email address, phone number, educational background, work experience and the subjects, courses, universities that they can teach.
- User indicates their decision.
- System verifies the request, sends a confirmation notification to the User.
Alternatives/Exceptions:
- 1-4a: User decided not to continue the process:
- 1-4a1: Use case ends in failure
- 1a: There are no new tutors applications:
- 1a.1: System informs User that there are no new applications; use case ends in failure.
- 5a: User approves tutor:
- 5a.1: System validates the User’s choice; use case continues to step 6.
- 5a: User rejects tutor:
- 5a.1: System validates the User’s choice; use case continues to step 6.
- 6a: System could not confirm the User’s request:
- 6a.1: System informs the user that an error occurred; use case ends in failure
Postcondition: User verified a new tutor
Title: Add a new university
Actors: Company manager
Intention: The intention of the company manager is to add new universities to the system
Precondition: User is in the application and is already logged in.
Main Scenario:
- System displays a list of current universities in the system
- User selects to add a new university to the system
- User enters the university name into the system
- User selects to save the new university
- System verifies the request of the user, and creates the new university.
Alternatives/Exceptions:
- 1.a: There are no universities in the system
- 1.a1: There is no list to show, Use case ends in failure
- 1.a: The user decided not to continue with the process
- 1.a1: Use case ends in failure
- 5.a: The university already exists in the system
- 5.a1: System warns the user, use case continues to step 3
Postcondition: User has created a new university
Title: Remove student
Actors: Company Manager
Intention: The intention of the company manager is to remove students from the system
Precondition: Students are already verified by the system
Main Scenario:
- System displays the list of students
- User selects the student of their choice
- System acknowledges User’s request.
- System displays the full name and email address of the selected user
- User indicates the removal of the user to the system
- System verifies the removal request
- System displays removal confirmation
Alternatives/Exceptions:
- 1-4a: User decided not to continue the process:
- 1-4a1: Use case ends in failure
- 1a: There are no students currently registered in the system:
- 1a.1: System informs User that there are no students currently registered in the system; use case ends in failure.
- 5a: User removes student:
- 5a.1: System validates the User’s choice; use case continues to step 7.
- 6a: System could not confirm the User’s request:
- 6a.1: System informs the user that an error occurred; use case ends in failure
Postcondition: User has removed a student from the system
Title: Add a new course
Actors: Company Manager
Intention: The intention of the company manager is to add a new course for tutors to teach and students to take in the application
Precondition: User is in the application and is already logged in.
Main Scenario:
- System displays a list of current subjects in the system
- User selects a subject from the list
- System acknowledges User’s request, displays a list of current courses of the subject in the system
- User selects to add a new course to the subject
- User enters the course code, name, and university into the system
- User selects to save the new course
- System verifies the request of the user, and creates the new course.
Alternatives/Exceptions:
- 1a: There are no subjects in the system
- 1a.1: There is no list to show, Use case ends in failure
- 1a: The user decided not to continue with the process
- 1a.1: Use case ends in failure
- 3a: There are no courses for a subject
- 3a.1: There is no list to show, but the user can still add a course
- 7a: The course already exists, or doesn’t match regex
- 7a.1: System warns the user, use case continues to step 5
Postcondition: User verified a new tutor
Title: Add a new subject
Actors: Company manager
Intention: The intention of the company manager is to add new subject to the system
Precondition 1: User is in the application and is already logged in.
Main Scenario:
- System displays a list of current universities in the system.
- User selects a university
- System displays a list of current subjects in the university.
- User selects to add a new subject to the system
- User enters the subject name into the system
- User selects to save the new subject
- System verifies the request of the user, and creates the new subject.
Alternatives/Exceptions:
- 1.a: There are no universities in the system.
- 1.a1: There is no list to show, Use case ends in failure.
- 3.a: There are no subjects in the system
- 3.a1: There is no list to show, Use case ends in failure
- 1.a: The user decided not to continue with the process
- 1.a1: Use case ends in failure
- 5.a: The subject already exists in the system
- 5.a1: System warns the user, use case continues to step 3
Postcondition: User has created a new subject