Sample Use Case - Create User
Sample Use Case - Create User
Basic Flow
norwalkaberdeen.com Page 1 of 5
© 2022 NorwalkAberdeen
NorwalkAberdeen
Step ID Actor Action Notes and References
BF-6 System System verifies User Name is available BR-1 (User Names
and in proper format. Unique)
BR-2 (User Name
Format)
AF-A (User Name not
Available)
AF-B (User Name in
Invalid Format)
BF-7 System System verifies Password is in valid BR-3 (Password
format. Format)
AF-C (Password in
Invalid Format)
BF-8 System System verifies E-Mail address is in valid BR-4 (E-Mail 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 message: Extension: UC-9 (Send
“This user has been set up in the Credentials to New
system: User)
[Preferred User Name]
[Initial Password]
[E-Mail Address]”
Alternate Flows
norwalkaberdeen.com Page 2 of 5
© 2022 NorwalkAberdeen
NorwalkAberdeen
AF-B: User Name in Invalid Format
norwalkaberdeen.com Page 3 of 5
© 2022 NorwalkAberdeen
NorwalkAberdeen
Exception Flows
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.
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
norwalkaberdeen.com Page 4 of 5
© 2022 NorwalkAberdeen
NorwalkAberdeen