Revision History

Sr. No. Revision Number Revision Date Author

1 0.1 1/1/2021 Girish Godbole
2 0.2 1/2/2021 Girish Godbole
3 0.3 1/3/2021 Girish Godbole
4 0.4 1/4/2021 Girish Godbole
5 1 1/4/2021 Girish Godbole
vision History
Summary
Intitial Draft
Incorporated review commnets given by peer
Incorporated review commnets given by Lead
Signoff Version by customer
Baselined Version
Use Case Id
Use Case Name
Brief Description
Actor(s)
Basic Flow
This use case starts when the User accesses the system feature that enables him/her to create an account by entering informa
1. The User enters the required User Account information values and requests that the system saves the entered va
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 t
4. The use case ends
Alternate Flows

User Cancels Request

User Enters Invalid User Account Information

Pre-Conditions
None
Post-Conditions
Success
The user account was not created
Extension Points
None

Use Case Id
Use Case name
Brief Description
Actor(s)
Basic Flow
This use case starts when the User accesses the system feature that enables him/her to update the information that is mainta
 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 val
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 t
5. The use case ends
Alternate Flows
Title

User Cancels Request

User Enters Invalid User Account Information

Pre-Conditions
User is signed in
Post-Conditions
Success
The user account was not updated
Extension Points
None
 UC002
Create Account
The Create Account use case allows the User to create a login and become a Registered User.
Guest

s the system feature that enables him/her to create an account by entering information that is maintained in the User’s account.
User Account information values and requests that the system saves the entered values.
red User Account information.
nt information are stored in the User’s account. The system notifies the User that the account has been created.

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.

If during Create Account, the system determines that the User entered 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
- 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

The User entered data is stored in the user account. Confimation is sent to the appropriate email address.
The User entered invalid data or chose to cancel the account creation request. In either case, no account will be
created.

Manage Account
Manage Account
The Manage Account use case allows the User to update the User Account Information maintained in the User's
account.
Registered User

s the system feature that enables him/her to update the information that is maintained in the User's account.
Account information currently stored for the User.
ser Account information values and requests that the system saves the entered values.
red User Account information.
nt information are stored in the User’s account. The system notifies the User that the account has been updated.

Description
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.
If during Modify Account, the system determines that the User entered 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
- 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

The User must be signed in before the User can edit or deactivate his/her account. See the Sign In use case

The User entered data is stored in the user account.

The User entered invalid data or chose to cancel the account management request. In either case, there is no change
to the user account.
Use Case Diagram example