Code Blue
Business Requirements Document (BRD)
Version 2
Version and Approvals
UTORS
Version History
Version #
Date
Revised By
Reason for change
01
11/04/2017
Group
02
11/16/2017
Group
Required documents update
This document has been approved as the official Business Requirements Document for Code Blue, and accurately reflects the current understanding of business requirements. Following approval of this document, requirement changes will be governed by the project’s change management process, including impact analysis, appropriate reviews and approvals.
Document Approvals
Approver Name
Project Role
Signature/Electronic Approval
Date
Table of Contents
Project Details. 1
Overview.. 1
Document Resources. 1
Glossary of Terms. 1
Project Overview.. 1
4.1 Project Overview and Background. 1
4.2 Project Dependencies. 2
4.3 Stakeholders. 2
Key Assumptions and Constraints. 2
5.1 Key Assumptions and Constraints. 2
Use Cases. 2
Use Case Diagram.. 2
Use Case Narrative. 3
Business Requirements. 5
Appendixes. 7
Appendix A – Business Process Flows. 7
Appendix B – Business Rules Catalog. 10
Appendix C- Models. 10
Traceability Matrix. 10
Use Case Narrative Instructions. 10
Project Details
Project Name
Code Blue Mobile Application
Project Type
New Initiative for hospital
Project Start Date
11-2-2017
Project End Date
12-9-2017
Project Sponsor
Xponsor
Primary Driver
Increase profits by providing access for hospitals and users
Secondary Driver
Increase additional platform
Division
Departments: Development | Testing | PMO | IT
Project Manager/Dept
Muriel Campomizzi
Overview
This document defines the high level requirements [code blue]. It will be used as the basis for the following activities:
–Developing test plans, test scripts, and test cases to add on location for each of the hospital; add on opening hours for both hospital and doctors; doctor’s information in details . In addition, see how it works for the user. To see whether it gives good and accurate advice for patients.
–Determining project completion- finish the development of adding hospital information and doctor’s information and schedule, develop a rating system, develop a tutorial video, and develop a location system to find out the nearest hospital and doctor.
–Assessing project success– both hospital/doctors and patients are satisfied with the app, information is accurate and up to time.
Document Resources
Name
Role
Hospital list
The hospitals in NYC
Doctor‘s information
All the doctors under those hospitals
Hospital location
To find the nearest location
Doctor’s specialities
To match the patient’s needs
Project Overview 5
4.1 Project Overview and Background
Current situation and problem:
· People do not have enough time to go to the hospital.
· Patients are not sure if it is necessary for them to go to the hospital.
· People do not know all available hospital in some areas.
· Some patients prefer certain doctors or hospital so that they need to know doctor’s schedule.
· Hospitals would like to have more efficient access for patients to make reservations.
· One local hospital cannot serve too many patients at certain time while another hospital can do
· Difficult to get an appointment due to the busy schedule of both doctors and patients.
· Difficult to find a specialist doctor with good recommendations.
· There are too many doctors to choose, rating for a doctor can help patient to choose a professional doctor.
Objectives: Deliver a mobile application on Android and iOS platforms that allow users to search hospitals and doctors’ offices, make and cancel appointment with doctors, check doctor’s schedule and rate doctors as well. Through this application, users can also see photo, hospital, schedule, position, specialty and ratings of each doctor. At last, it will help integration of medical resources in NYC.
4.2 Project Dependencies
· Sign contract with local hospitals to get permission to post information of local hospitals and doctors.
· Collect information of hospitals and doctors.
· Promote the mobile application.
4.3 Stakeholders
The following comprises the internal and external stakeholders whose requirements are represented by this document:
Stakeholders
1
Hospitals
2
Patients
3
Doctors
4
Customers
Key Assumptions and Constraints
5.1 Key Assumptions and Constraints
#
Assumptions
1
Work, material, and costs resources will be available to support the project through the whole processes.
2
Hospital, medical institutions, and doctors will provide necessary information.
3
More than 90% of users are on iOS or Android.
4
The app always delivers precise and correct information to users.
5
More than 90% of users will know how to operate the application within 2 minutes for the first time.
6
The application will be accepted by the apple store within 5 days of submission.
7
The platforms will extend a code freeze for the 6 months prior to going live to ensure no app changes will be required.
8
Approval of project will be received prior to start of design/build of app.
#
Constraints
1
The develop resources won’t be available from project initiation to support project
2
Development team will be staffed at 30% during december due to holiday.
3
Cloud hardware guarantees uptime of only 90%.
4
Budget allows for only offshore development resources.
Use Cases
Use Case ID:
001
Use Case Name:
Emergency – Find the nearest doctor of orthopedics
Created By:
Zili Wang
Last Updated By:
Date Created:
11-12-2017
Date Last Updated:
Actors:
Application user
Description:
A patient, who broke his right leg at Times Square, wants to find the nearest doctor of orthopedics to check on his right leg. The user used his iPhone to download Code Blue app and searched for orthopedics category.
Preconditions:
App is downloaded and opened; location is detected.
Postconditions:
He searches for orthopedists at hospitals nearby and check the reviews.
Normal Course:
Download app | Open app | Select orthopedics | Detect location | Give result for the nearest orthopedics doctors | Select a doctor and make an appointment
Alternative Courses:
None
Exceptions:
No result found for orthopedics category available nearby.
Frequency of Use:
Depends, only used when ill or body check.
Special Requirements:
24/7 access
Use Case ID:
002
Use Case Name:
Regular Appointment
Created By:
Muriel Campomizzi
Last Updated By:
Date Created:
11/02/2017
Date Last Updated:
Actors:
Application user
Description:
A patient needs to schedule a regular consultation with a gynecologist, but the one she usually goes to is not available for the date she wants.
Preconditions:
She is already a Blue Code user.
Postconditions:
She searched for gynecologists nearby.
Normal Course:
She will check the reviews about those gynecologists that fit her time and location and make an appointment.
Exceptions:
She could not find an available gynecologist nearby and might need to expand the location ratio.
Frequency of Use:
Once a month
Business Requirements
The following sections document the various business requirements of this project.
Requirement Type
ID – Prefix
ID – Number
Function – Feature
Requirement
Use Case Reference
Required
??
??
Comments
Business User Requirements
f
0001
Customer will be able to login with Facebook account
f
0002
Customer will have access to doctor’s profile divided by specialties
f
0003
Customer will have access to doctor’s profile divided by location
f
0004
Customer will have access to hospitals profile divided by location
F
0005
Interactive map
Shows doctors, hospitals, and customers location
F
0007
Contact information
Shows information regarding hospitals and doctors contacts
f
0007
User Profile
Customer can update their personal information and anamneses
f
0008
My activities page
Recent activities and schedule
f
0009
Customer will be able to make or cancel an appointment
Reporting Requirements
f
0001
Offeror can pull a monthly report on the list of successful appointment
f
0002
Offeror can pull a monthly report on the customer’s reviews.
f
0003
Offeror can pull a monthly app status report
User Access/Security Requirements
f
0001
Password must contain numbers, lower and upper case letters, and special characters.
At least 15 characters.
f
0002
Each user has a unique authorization id and access control id to check their profile
Service Level/Performance Requirements
f
0001
f
0002
f
0003
f
0004
F
0005
F
0007
f
0007
f
0008
Scalability Requirements
f
0001
f
0002
f
0003
f
0004
Support and Maintenance Requirements
f
0001
f
0002
f
0003
f
0004
F
0005
F
0007
f
0007
f
0008
Appendixes
Appendix A – Business Process Flows
As Is Diagrams
To Be Diagrams
Appendix B – Business Rules Catalog
Business Rule Name:
Identifier
Description
Example
<(Optional) An example of the rule>
Source
Related Rules
Appendix C- Models
Traceability Matrix
Use Case Narrative Instructions
Use Case Field Name
Definition
Use Case ID
Give each use case a unique numeric identifier, in hierarchical form: X.Y. Related use cases can be grouped in the hierarchy. Functional requirements can be traced back to a labeled Use Case.
Use Case Name
State a concise, results-oriented name for the use case. These reflect the tasks the user needs to be able to accomplish using the system. Include an action verb and a noun. Some examples:
· View part number information.
· Manually mark hypertext source and establish link to target.
· Place an order for a CD with the updated software version
Created By
Include the name of the person who initially documented this Use Case.
Date Created
Enter the date on which the use case was initially documented
Date Last Updated
Enter the date on which the use case was most recently updated
Last Updated By
Include the name of the person who performed the most recent update to the use case description.
Actor
Enter the person or other entity external to the software system being specified who interacts with the system and performs use cases to accomplish tasks. Different actors often correspond to different user classes, or roles, identified from the customer community that will use the product. Name the actor(s) that will be performing this Use Case.
Description
Provide a brief description of the reason for and outcome of this use case, or a high-level description of the sequence of actions and the outcome of executing the Use Case.
Preconditions
List any activities that must take place, or any conditions that must be true, before the Use Case can be started. Number each precondition. Examples:
· User’s identity has been authenticated.
· User’s computer has sufficient free memory available to launch task
Post conditions
Describe the state of the system at the conclusion of the use case execution. Number each post condition. Examples:
· Document contains only valid SGML tags.
· Price of item in database has been updated with new value
Normal Course
Provide a detailed description of the user actions and system responses that will take place during execution of the use case under normal, expected conditions. This dialog sequence will ultimately lead to accomplishing the goal stated in the use case name and description. This description may be written as an answer to the hypothetical question, “How do I
Alternative Courses
Document other, legitimate usage scenarios that can take place within this use case separately in this section. State the alternative course, and describe any differences in the sequence of steps that take place. Number each alternative course using the Use Case ID as a prefix, followed by “AC” to indicate “Alternative Course”. Example: X.Y.AC.1
Exceptions
Describe any anticipated error conditions that could occur during execution of the use case, and define how the system is to respond to those conditions. Also, describe how the system is to respond if the use case execution fails for some unanticipated reason. Number each exception using the Use Case ID as a prefix, followed by “EX” to indicate “Exception”. Example: X.Y.EX.1
Includes
List any other use cases that are included (“called”) by this use case. Common functionality that appears in multiple use cases can be split out into a separate use case that is included by the ones that need that common functionality.
Priority
Indicate the relative priority of implementing the functionality required to allow this use case to be executed. The priority scheme used must be the same as that used in the software requirements specification.
Frequency of Use
Estimate the number of times this Use Case will be performed by the actors per some appropriate unit of time.
Business Rules
List any business rules that influence this Use Case.
Special Requirements
Identify any additional requirements, such as nonfunctional requirements, for the use case that may need to be addressed during design or implementation. These may include performance requirements or other quality attributes.
Assumptions
List any assumptions that were made in the analysis that led to accepting this use case into the product description and writing the use case description.
Notes and Issues
List any additional comments about this use case or any remaining open issues or TBDs (To Be Determined) that must be resolved. Identify who will resolve each issue, the due date, and what the resolution ultimately is.