User Stories

BSA/385 v7

User Stories
BSA/385 v7
Page 2 of 3

User Stories

In Agile software development, user stories capture description of features from end users’ perspective. user stories are often referred to as epics, themes or features. Typically, user stories are just well-expressed requirements. User stories must provide type of user, what they want, and why they want. These are starting points to a conversation that will define the product requirements.
There is one major difference between user stories and requirements. The user story focuses on the experience—what the person using the product wants to be able to do. A requirement focuses on functionality—what the product should do.

Requirements

There are two categories of requirements: Functional and non-functional.
Functional Requirements (FR) express what is required. Example: Secure a conference site.
Non-Functional Requirements (NFR) describe solution attributes such as security, reliability, performance, availability, etc. Example: Response time less than 2 seconds.

Examples of User Stories

The director of software engineering and the product manager for the company visited the client and collected the user stories below:
· From the chief financial officer: In to meet HIPAA requirements, I need to provide detailed records of all bills. Your program needs to be very accurate; there should be ways you can prove to me the bills you produce are correct.
· From the data entry clerk: I have red-green color blindness. Your program needs to have an interface that is easy for me to interpret. If you use a warning/alert sign in a program, it cannot come up in red; I will not be able to read it.
· From the discharge clerk: Patients often do not understand their hospital bill. It would be so helpful if the bill also described the medications they are given. The bill is sometimes bad news for the patient, so I would like the printed bill to use soft, calming colors and include a happy face.
· From the pharmacist: Accuracy is very important to me. If the bill states the medication inaccurately, I can be sued.
· From the compliance manager: HIPAA gives me headaches every day. Your program needs to meet all of the requirements to protect PII. My security team manager said that our PHI Policy prohibits the use, storage, and discloser of personal health information (PHI) and electronic personal heal information (EPHI), except as specifically permitted or required by HIPAA regulation.
· From the data entry supervisor: All of my clerks are very young. They would like the user interface to look like an iPhone or Facebook page for easy navigation or they will not be able to use it. The user interface and the bill should have our logo on it.
· From the surgery supervisor: I feel very strongly that program usage should be restricted to those who “need to know.” Some of the software around here is not locked down; even the janitor knows the username and password sometimes.

Copyright 2020 by University of Phoenix. All rights reserved.
Copyright 2020 by University of Phoenix. All rights reserved.