Scribd
Upload
14 views3 pages

User Story Template

Uploaded by

tukaram
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
14 views3 pages

User Story Template

Uploaded by

tukaram
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
You are on page 1/ 3

User Story: Enter Ages for All Members

User Role: Existing Health Insurance Policyholder


User Goal: To successfully complete the porting process by providing
accurate member ages.

As an existing Health Insurance Policyholder I would like to complete the


porting process on TrueFin platform by providing accurate member ages
so that all the required members are considered in porting.

Acceptance Criteria:
A. Positive Scenarios
a. Valid Age Entry
When a user enters a valid age (within the specified range) for each
member, the "Next" button is enabled.
Upon clicking "Next," the user is navigated to the subsequent step in the
porting process.
b. Age Range Validation:
The system validates the entered ages to ensure they are within the
predefined age ranges for different plan categories (e.g., adult, child,
senior citizen).
If an age falls outside the acceptable range for a specific plan category, an
appropriate error message is displayed, and the "Next" button remains
disabled.

B. Negative Scenarios:
a.Empty Age Fields
If any age field is left empty, the "Next" button remains disabled, and a
prominent error message is displayed prompting the user to fill in all
required fields.
b.Invalid Age Input:
If a user enters a non-numeric value, a decimal value, or a negative
value, an error message is displayed, and the "Next" button remains
disabled.
If the entered age exceeds the maximum age limit for a particular plan
category, an appropriate error message is displayed.

C.Business Rules:
a.Age Validation:
Ages must be positive integers.
Ages must fall within the predefined age ranges for different plan
categories (if applicable)

D. Data Rules:
a. Data Type: Age should be stored as an integer.
b. Data Validation:** Age values should be validated to ensure they are
within the specified range.
c. Data Security: Age information should be securely stored and
transmitted, using encryption and other security measures.

E. UX and FE Considerations:
a. Clear and Concise Labels: Use clear and concise labels for age fields,
such as "Age of Member 1," "Age of Member 2," etc.
b. Error Messages: Provide specific and actionable error messages, such
as "Please enter a valid age between 0 and 100.
Provide all scenarios here.
c. Visual Feedback: Use visual cues like color-coding, tooltips, or inline
validation to provide immediate feedback to the user.
d. User-Friendly Input: Consider using number input fields with
appropriate keyboard input types to facilitate easy age entry.
e. Accessibility: Ensure the age input fields are accessible to users with
disabilities, adhering to accessibility standards (e.g., WCAG). < can be
deferred>
f. Provide responsive design for both mobile and desktop ( if in scope for
user story)

F. BE Considerations:
API related logic, whats input expected on user interaction and whats
output expected out of API

G. Current vs expected flow:

H. Non-Functional Requirements:
a. Performance: The system should respond quickly to user input and
avoid delays in processing age information, especially for large numbers
of members.
b. Security: Sensitive user data, including age information, should be
securely stored and transmitted, using encryption and other security
measures.
c. Scalability: The system should be able to handle a large number of
users ( Provide guesstimate from peak business volume projected) and
scale as the number of users and data increases.

I. Event Tracking:
a. Page Views: Track the number of times the age entry page is viewed.
b. Form Submissions: Track the number of times the form is submitted
with valid and invalid data.
c. Error Rates: Track form submissions with errors.
d. Time on Page: report events for the average time users spend on the
age entry page for that session
e. Conversion Rate for the page: Track the event for the users who
successfully complete the age entry process and proceed to the next step.
J. Ops Requirement & Risk handling

Not applicable for this release: but in case of business panel Operational
Requirements may kick in.

While this is just giving sense of how elaborate it can be, we can reduce to
fit for purpose.
Also api related requirements will kick in for relevant stories

You might also like