Michael Banet Database Systems

Joseph Casabona February 12, 2007

Dr. Yaodong Bi

Text Swap
Use Case Specification: Create Account
Name Create Account
Brief Description The Create Account use case allows the User to create a login and
become a Registered User.
Actor(s) Guest
Flow of Events
Basic Flow
This use case starts when the User accesses the system feature that enables him/her to create an
account by entering information that is maintained in the User’s account.
1. The User enters the required User Account information values and requests that the system
saves the entered values.
2. The system validates the entered User Account information.
3. The values for the User Account information are stored in the User’s account. The system
notifies the User that the account has been created.
4. The use case ends
Alternate Flows
Title Description
User Cancels Request At any time, the User may choose to cancel the account creation. At
which point, the processing is discontinued, the user account remains
unchanged, and the user is notified that the account management
request has been cancelled.
User Enters Invalid User If during Create Account, the system determines that the User entered
Account Information invalid User Account information, the following occurs:
1. The system describes which entered data was invalid and
presents the User with suggestions for entering valid data.
2. The system prompts the User to re-enter the invalid information.
3. The User re-enters the information and the system re-validates
it.
4. If valid information is entered, the User Account Information is
stored.
5. If invalid information is entered, the Entered Information is
Invalid alternative flow is executed again. This continues until
the User enters valid information, or chooses Cancel (see the
User Cancels Account Management Request alternative flow).
Invalid User Account information:
- Missing information items

Page 1
 - Username already exists in the system
- User Account information entered does not comply to its
definition in the glossary
- Not well formed e-mail address
- Offending words in any part of the User Account information
Pre-Conditions
Title Description
None
Post-Conditions
Title Description
Success The User entered data is stored in the user account. Confimation is sent
to the appropriate email address.
The user account was not The User entered invalid data or chose to cancel the account creation
created request. In either case, no account will be created.
Extension Points
None

Name Sign in
Brief Description
Actor(s) User, Administrator
Flow of Events
Basic Flow
This use case starts when the User accesses the sign in feature of the system.
1. The system prompts the User for his/her username and password.
2. The User enters his/her username and password.
3. The system validates the entered information, making sure that the entered username and
password are valid for one user account in the system, and that the required password is
entered for the entered username.
4. The User is signed in. The system displays a message indicating that the user is signed in.
5. The use case ends.
Alternate Flows
Title Description
New User If the User does not have an account, the System will give the User the
opportunity to create an account. See the Create Account use case.
Once the account is created, the User is considered signed in.
User Forgot User If the User forgot his/her user name or password, the System will
Name/Password prompt the user to answer his/her security question provided in the

Page 2
 Create Account stage. Provided that it is answered correctly, the user
name and password are emailed to the email address provided when
the account was created.
User Fails Authentication If the User entered an invalid username and/or password, the following
occurs:
1. The system describes the reasons why the User failed
authentication.
2. The system presents the User with suggestions for changes
necessary to allow the User to pass authentication.
3. The system prompts the User to re-enter the valid information.
4. The Basic Flow continues where the User enters new
information (see step 2 of the Basic Flow).
Pre-Conditions
Title Description
None
Post-Conditions
Title Description
Success The User is authenticated and the system displays all features available
for the role the user is associated with as defined in his/her user
account.
User not signed in This can occur because the User repeatedly entered invalid sign in
information. The User has been notified of the reason why he/she was
not signed in. The User is not authenticated and remains in the
Anonymous User role.

Page 3
Name Manage Account
Brief Description The Manage Account use case allows the User to update the User
Account Information maintained in the User's account.
Actor(s) Registered User
Flow of Events
Basic Flow
This use case starts when the User accesses the system feature that enables him/her to update the
information that is maintained in the User's account.
1. The system displays the User Account information currently stored for the User.
2. The User enters the desired User Account information values and requests that the system
saves the entered values.
3. The system validates the entered User Account information.
4. The values for the User Account information are stored in the User’s account. The system
notifies the User that the account has been updated.
5. The use case ends
Alternate Flows
Title Description
User Cancels Request At any time, the User may choose to cancel the account
update/deactivation. At which point, the processing is discontinued, the
user account remains unchanged, and the user is notified that the
account management request has been cancelled.
User Enters Invalid User If during Modify Account, the system determines that the User entered
Account Information invalid User Account information, the following occurs:
6. The system describes which entered data was invalid and
presents the User with suggestions for entering valid data.
7. The system prompts the User to re-enter the invalid information.
8. The User re-enters the information and the system re-validates
it.
9. If valid information is entered, the User Account Information is
stored.
10. If invalid information is entered, the Entered Information is
Invalid alternative flow is executed again. This continues until
the User enters valid information, or chooses Cancel (see the
User Cancels Account Management Request alternative flow).
Invalid User Account information:
- Missing information items
- Username already exists in the system
- User Account information entered does not comply to its
definition in the glossary
- Not well formed e-mail address

Page 4
 - Offending words in any part of the User Account information
Pre-Conditions
Title Description
User is signed in The User must be signed in before the User can edit or deactivate
his/her account. See the Sign In use case
Post-Conditions
Title Description
Success The User entered data is stored in the user account.
The user account was not The User entered invalid data or chose to cancel the account
updated management request. In either case, there is no change to the user
account.
Extension Points
None

Name View Items

Brief Description The View Items use case allows the User to view current selection of
Textbooks available
Actor(s) Guest, Registered User, Administrator
Flow of Events
Basic Flow
This use case starts when the User accesses one of the following system features:
1. Display all textbooks available.
2. Use of drop down menus to filter the results based on the criteria selected.
3. Direct search by distinct criteria.
Alternate Flows
Title Description
None
Pre-Conditions
Title Description
None
Post-Conditions
Title Description
Success Textbooks would be displayed on the current page.
No entries No textbooks available from the given criterion.
Extension Points
None

Page 5
Name List Book
Brief Description The users will be able to list books they want to trade
Actor(s) Registered User, Administrator
Flow of Events
Basic Flow
This use case starts when the User accesses one of the following system features:
1. Account Manager
Alternate Flows
Title Description
None
Pre-Conditions
Title Description
None
Post-Conditions
Title Description
Success A new textbook is added to the database
No entries
Extension Points
None

Page 6