0% found this document useful (0 votes)
3 views5 pages

Sample+Use+Case+ +Create+User

This document outlines the use case for creating a new user in the NorwalkAberdeen system by a Customer Service Representative (CSR). It details the preconditions, postconditions, basic flow, alternate flows for error handling, and business rules regarding user name, password, and email format. The process ensures that the user is successfully set up in the system while adhering to specified validation rules.
Copyright
© All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
3 views5 pages

Sample+Use+Case+ +Create+User

This document outlines the use case for creating a new user in the NorwalkAberdeen system by a Customer Service Representative (CSR). It details the preconditions, postconditions, basic flow, alternate flows for error handling, and business rules regarding user name, password, and email format. The process ensures that the user is successfully set up in the system while adhering to specified validation rules.
Copyright
© All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd

NorwalkAberdeen

UC-1: Create User


Description This use case describes the process by which a CSR sets
up a new user in the system.

Actors Customer Service Representative (CSR)


System

Preconditions CSR is credentialed for the system.


CSR is entitled to create users.
CSR has the preferred user name, initial password, and e-
mail address of the user.

Postconditions The user has been set up in the system.

Trigger CSR elects to create a new user.

Basic Flow

Step Actor Action Notes and


ID References
BF-1 Client Client Service Rep logs into the UC-7: Logon
Service Rep system.
BF-2 System System displays Main Menu.
BF-3 Client CSR elects to set up a new user.
Service Rep
BF-4 System System displays the New User Set-
Up view.
BF-5 Client CSR enters the following info:
Service Rep  Preferred User Name
 Initial Password
 E-Mail Address
BF-6 System System verifies User Name is BR-1 (User Names
available and in proper format. Unique)
BR-2 (User Name
Format)
AF-A (User Name
not Available)
AF-B (User Name in
Invalid Format)

[Link] Page 1 of 5 © 2026 NorwalkAberdeen


NorwalkAberdeen
Step Actor Action Notes and
ID References
BF-7 System System verifies Password is in BR-3 (Password
valid format. Format)
AF-C (Password in
Invalid Format)
BF-8 System System verifies E-Mail address is in BR-4 (E-Mail
valid format. Format)
AF-D (E-Mail
Address in Invalid
Format)
BF-9 System System creates user in database. EF-A (Problem with
Updating Database)
BF-10 System System displays confirmation Extension: UC-9
message: “This user has been set (Send Credentials to
up in the system: New User)
 [Preferred User Name]
 [Initial Password]
 [E-Mail Address]”

Alternate Flows
AF-A: User Name not Available

Step ID Actor Action Notes and


References
AF-A-1 System If the User Name is unavailable, the
system displays the following error
message to the user: “This user
name is not available. Please
choose another.”
AF-A-2 [Return to BF-5]

AF-B: User Name in Invalid Format

Step ID Actor Action Notes and


References
AF-B-1 System If the User Name is in an invalid BR-2 (User Name
format, the system displays the Format)
following error message to the
user: “This user name is invalid.
User names must be 6-20
alphanumeric characters.”
AF-B-2 [Return to BF-5]

[Link] Page 2 of 5 © 2026 NorwalkAberdeen


NorwalkAberdeen
AF-C: Password in Invalid Format

Step ID Actor Action Notes and


References
AF-C-1 System If the Password is in an invalid BR-3 (Password
format, the system displays the Format)
following error message to the
user: “This password is invalid.
Passwords must be 6-20
alphanumeric characters.”
AF-C-2 [Return to BF-5]

AF-D: E-Mail Address in Invalid Format

Step ID Actor Action Notes and


References
AF-D-1 System IF the E-Mail Address is in an BR-4 (E-Mail
invalid format, the system displays Format)
the following error message to the
user: “This e-mail address is in an
invalid format.”
AF-D-2 [Return to BF-5]

Exception Flows
EF-1: Problem with Updating Database

Step ID Actor Action Notes and


References
EF-A-1 System If the system encounters an
unexpected issue while attempting
to create a user account in the
database, the system will display
the following message to the user:
“The system was unable to process
your request due to an error in the
system. Please contact the
Technology Help Desk.”
EF-A-2 [End of Use Case]

[Link] Page 3 of 5 © 2026 NorwalkAberdeen


NorwalkAberdeen
Business Rules
NOTE: We recommend keeping business rules in a separate repository. Only include them in a use case
document if there is an organizational policy to that effect or if there is a very good reason to.

Rule ID Name Description


BR-1 User Names Any preferred user name may not be added to
Unique the database if it matches any existing user
name.
BR-2 User Name Format User names must adhere to the following rules:
 Must be 6-20 characters long
 Must be alphanumeric characters only
BR-3 Password Format Passwords must adhere to the following rules:
 Must be 6-20 characters long
 Must be alphanumeric characters only
BR-4 E-Mail Format E-mails must be of format: [x]@[y].[z], where:
 x is an alphanumeric string
 y is an alphanumeric string
 z is three or fewer characters and
 z is alphabetical characters only

[Link] Page 4 of 5 © 2026 NorwalkAberdeen


NorwalkAberdeen

[Link] Page 5 of 5 © 2026 NorwalkAberdeen

You might also like