TASK 7
Requirement Engineering
Stratford University Falls Church
Musa Mohammed
Sarki Barkuma Amada
000-26-7727
02/14/2019
Questions:
1. User story title: Student Opening the software
As a new student, I want an ability to open registration software.
Acceptance criteria:

When student clicks on the software, it should open
2. User story title: Student Register
As a student, I want an ability to register using my email and create a new password.
Acceptance criteria:

When a student provides a valid email, he/she can register instantly.

If the student enters incorrect email, provide an error
3. User story title: Ability to login in to Student Register account
As a registered student, I want to login with my login credentials so that I can access my
account.
Acceptance criteria:

When a student provides a valid email and password, he/she can login in to the
account.

If customer enters an incorrect password or Id, provide an error

If customer enters nothing and hits sign in button then provide an error
4. User story title: Ability to register classes
As a user, I want an ability to register for classes.
Acceptance criteria:

When student adds a class to his/her cart, he should be able to register it
5. User story title: Ability to reset password
As a registered student, I want an ability to reset my password in case if I forget my
password.
Acceptance criteria:

When student enters incorrect password, results in error message

If user clicks on ‘forgot password’, is asked for email address to send the reset link.
6. User story title: Ability to find classes
As a site visitor, I want an ability to find classes by searching for it in the registration
software
Acceptance criteria:

When a student type-in a class, the software should show result of classes matching
the search query

Should show “No classes found” if no matching is found.
7. User story title: Student want to add class to cart
As a student, I want to be able to add classes to cart, so that I will register it later.
Acceptance criteria:

Class should be added successfully when student clicks on add to cart.
8. User story title: Ability to pay for classes online
As a student, I want to be able to pay for my registered classes online after registration.
Acceptance Criteria

Depending on the number of classes, student would pay the total amount of the
registered classes.
9. User story title: Ability to logout
As a student, I want the ability to logout of the software.
Acceptance criteria:

Logout student after he/she clicks on logout
10. User story title: Ability to remove classes from cart
As a student, I want the ability to remove classes from my cart, that I don’t want to register.
Acceptance criteria:

When student clicks to remove class from the cart, the particular class should be
removed from the cart.
Use Case:
Use Case Name: Register Student
Actors:



Registered Student (Has an existing account, possibly with billing information)
Non-registered student (Does not have an existing account)
Billing System (bills student for class that have been registered)
Triggers:

The student indicates that she/he wants to register a class that she/he has selected.
Preconditions:

Student has selected the class to be registered.
Post-conditions:

The order will be placed in the system.
Normal Flow:
1. The student will sign-in
2. The student will search for class available
3. The student will indicate that she/he wants to register the class that have already been
selected.
4. The system will add the class to the cart
5. The system will present the billing information that the user previously stored.
6. The student will confirm that the existing billing information should be used for
registration.
7. The system will present the amount that the order will cost, including applicable taxes.
8. The student will confirm that the order information is accurate.
9. The system will request that the billing system should charge the student for registration.
10. The billing system will confirm that the charge has been placed for the registration.
11. The system will indicate to the user that the student has been charged for registration.
12. The system will indicate to the user that the registration is successful.
13. The user will exit the system.
Alternate Flows:
3A1: The student enters billing and shipping information for the registration. The student
desires to use billing information that differs from the information stored in his/her
account. This alternate flow also applies if the student does not maintain billing
information in their account, or if the user does not have an account.
1.
2.
3.
4.
The student will indicate that this order should use alternate billing information.
The student will enter billing information for this registration.
The system will validate the billing information.
The use case continues
5A1: The student will discover an error in the billing information associated with their
account and will change it.
1.
2.
3.
4.
The student will indicate that the billing information is incorrect.
The student will edit the billing information associated with their account.
The system will validate the billing information.
The use case returns to step 2 and continues.
5A2: The student will discover an error in the billing information that is uniquely being
used for this order and will change it.
1. The student will indicate that the billing information is incorrect.
2. The student will edit the billing information for this registration.
3. The student case returns to step 3A1 step 3.
1. The use case ends.
Diagram
Create
Account
Create
Account
Login
Verify
Login
Search
classes
Show
found
classes
System
Add class
to cart
Register
class
Pay for
class
Add class
to cart
Register
class
Verify
payment
logout
logout