Location via proxy:   [ UP ]  
[Report a bug]   [Manage cookies]                

User Story Template With Some Example

Download as pdf or txt
Download as pdf or txt
You are on page 1of 10

User Stories

User Story 1: User registration

Size: 13
Priority: High
Component: User registration
Release: Release 1
Status: Upcoming
Attachment:
Acceptance criteria:

 User need to provide a username (e-mail), first and last name with no more than
256 symbols
 User need to provide a phone number with the format as +XX XXX XX XX XXX
 User need to input his date of birth
 Password can not be smaller than 8 symbols and maximum of 25 symbols with the
following requirements:
o Using a minimum of one Capital letter
o Using a minimum of one small letter
o Using minimum one Number
o Using at least one Special symbols
 User has to agree to the Terms and Conditions by checkbox before being able to
submit the input, if not he is not able to submit the data
 User is only able to submit and to open the page via secure encrypted URL by
default
 After submit the user received an email with a unique confirmation link
 Password and Repeat password has to be while the user provides input with *
 User must provide input to the following:
o Username/email
o First and Last name
o Date of birth
o Password and
o Repeat password
User Story 2: Activate Two-Factor Authentication (2FA)

Size: 8
Priority: High
Component: Security
Release: Release 2
Status: Upcoming
Acceptance criteria:

 To activate two-factor authentication user must provide a phone number


 If the user provided a phone number during registration there should be only a
button to activate 2FA from user settings.
 If there is no user phone number provided during the registration process (as it is
not a requirement) then the user will be asked to provide first phone number in
format +XX XXX XX XX XXX.
 After the user provided the phone number SMS is going to be sent with unique
verification six numbers, validated only for 10 minutes, after the 10 minutes the
number is not valid.
 After activating the 2FA, every time when the user is logged-in with a username
and password will receive a unique 6 digit number on his phone.

User Story 3: User registration – confirmation (functional format)


 The platform has to be able to validate user profile, via email or SMS.
 The platform is able to send SMS with 6 digit code to verify his identity via phone.
 Generated code has to be unique and not be able to use it after 10 minutes time
frame.
 After successful verification of an SMS code (2FA) it has to be kept in the
database for audit purposes, with username, phone number, timestamp, and IP
address.
 Users should be able to receive SMS after 1 minute after clicking the activate 2FA
function.
 If the user provided their phone number during the registration process, then he
should be able from the user setting to activate 2FA without provided his phone
number, if not then he has to be able to provide an input of his phone number.

User Story 4: Create a user login


Create a user login

Content: As a user, I need a user login to prevent other people from using the
machine
Type:UserStory
Component: Users
Acceptance criteria:

 The program must allow data entry for a maximum of 2 users


 The user must send an SMS with the invoice number as a request to receive a
customer number
 Two users cannot receive the same generated customer number in an SMS
 The generated code cannot be longer than 16 characters.
 After receiving a client number, the program must be able to set a password
 The password must contain at least 8 characters – uppercase and lowercase letters
and numbers
User Story - Registration Screen - Username and Password
creation

User Story:
As a customer, I want to create login credentials So that I can securely access my
self-service online account

Acceptance Criteria:

1. Input data fields to enter - 1) Username 2) Password 3) Re-enter Password 4)


Security question 5) Security answer
2. Username data field specifications - TBD for specifications
3. Password data field specifications - At least 7 characters, 1 number, 1
uppercase letter, 1 lowercase letter, one special character
4. Security questions drop-down - TBD for content
5. Security Answer data field specifications - at least 4 characters
6. All fields are required data fields - error alert should be shown if user clicks
on Submit with any of the fields left blank " cannot be empty"
7. User should be prompted if username entered already exists in the system -
error message
"Username taken - please enter another username"
8. Password criteria should be displayed to the user when user clicks inside the
password data field.
9. Green check mark next to 'Password' data field should be displayed that
indicates to the user after typing password that the entry meets criteria
10.Red cross mark next to 'Password' data field should be displayed that
indicates to the user after typing password that the entry does not meet
criteria
11.Validate that inputs in 'Password' and 'Re-enter Password' data fields match-
Green check mark next to 'Re-enter' password data field should be displayed
that indicates to the user after typing if passwords match
12.'Password' and 'Re-enter Password' entries should be masked
13.Password entries will show the keystroke typed, and then after two seconds
the entered character is masked.
14.If 'Password' entry does not match criteria specified and user hits Submit,
show error alert "Password entry does not meet criteria"
15.If entries in 'Password' and 'Re-enter Password' do not match and user hits
Submit, show error alert 'Password entries do not match'
16.After successful validation of all entered fields and on clicking Submit,
show message indicating successful online account creation

Route user to Splash screen (Login screen)

You might also like