Software Requirements 2 About Health Care

Copyright 2014 by H4T Group.
System/Software
Requirements Specification
For
<HEALTH CARE PROJECT>

Version 1.0 approved
Prepared by
Copyright 2014 by H4T Group.
<H4T Group
NGUYEN SON HAI
PHAM DUC THINH
TA THIEN HUONG
PHAM GIA HUU
TRAN QUOC HUNG>
<SE10801>
<08/06/2014>
Software Requirements Specification for <Health Care Project> Page iii

Table of Contents
Table of Contents ........................................................................................................................ iiii
Revision History ........................................................................................................................... iv
1. Introduction ..............................................................................................................................1
1.1 Purpose ........................................................................................................................................ 1
1.2 System Purpose ........................................................................................................................... 1
1.3 Definitions, Acronyms and Abbreviations .................................................................................. 1
1.4 Document Conventions ............................................................................................................... 2
1.5 Intended Audience and Reading Suggestions.............................................................................. 2
1.6 Health Care Project Scope ........................................................................................................... 2
1.7 References ................................................................................................................................... 2
2. Overall Description ..................................................................................................................3
2.1 Product/System Perspective ........................................................................................................ 3
2.2 System/Product Features ............................................................................................................. 3
2.3 User requirements ........................................................................................................................ 4
2.4 User Classes and Characteristics ................................................................................................. 4
2.5 Operating Environment ............................................................................................................... 4
2.6 Design and Implementation Constraints ...................................................................................... 5
2.7 User Documentation .................................................................................................................... 5
2.8 Assumptions and Dependencies .................................................................................................. 5
2.9 Apportioning of Requirements .................................................................................................... 6
3. Specific Requirements .............................................................................................................6
3.1 Functional Requirements Specification ....................................................................................... 6
3.1.1 Function Diagram .................................................................................................................... 6
3.1.2 Use Case Diagram .................................................................................................................... 7
3.1.3 Function Home Page ............................................................................................................... 8
3.1.4 SEARCH 10
3.1.5 Disease Search 11
3.1.6 Disease List 13
3.1.7 Information about disease. 16
3.1.8 Medicine Advice 18
3.1.9Ways of avoiding 20
3.1.10 First aid methods 22
3.1.11 FQA 24
3.1.12 List Medical... 27
3.1.13 Administration and dosage 29
3.2 Non-Functional Requirements Specification ............................................................................. 32
3.2.1 External Interface Requirements ........................................................................................... 32
3.2.2 Other Nonfunctional Requirements ...................................................................................... 32
4. Other Requirements ..............................................................................................................33
Appendix A: Glossary..................................................................................................................33
Appendix B: Analysis Models .....................................................................................................33
Appendix C: Issues List ...............................................................................................................33

Software Requirements Specification for <Health Care Project> Page iv

Revision History
Name Date Reason For Changes Version
Create New 08/06/2014 Create 1.0
More Info Update 20/07/2014 Add more information about Usecase 1.1

Software Requirements Specification for <Health Care Project> Page 1

Introduction
1.1 Purpose
- This document provides for Developers, Testers and Quality Assurances a complete and comprehensive
description of the functional requirements of Medical system.
1.2 System Purpose

This document includes software requirements for heath, release number 1.00. This product is intended for those
students,and staff selling drugs, the object can use smart phones.. Describe the system objectives: This software
application on smart phones, that purpose is to help patients object it can aid rapid without the services of medical
institutions, In addition, this software also supports users know the signs of the disease they encountered,, The software
will show the extent of the disease according to the choice of software question, identified after disease, extent of
disease, the software will provide the names of drugs should drink and how to drink The salesman, then this software
is also able to provide information about the status of human healing, This particular software is only used for common
diseases scope of the product that is covered by this SRS, particularly if this SRS describes only part of the system or a
single subsystem.

1.3 Definitions, Acronyms and Abbreviations
Abbreviations Description Note
N/A None
SR SEARCH
DS Disease Search
LD List disease
IAD Information about disease
FAM First aid methods
FQA Frequently questionsasked

1.4 Document Convention
This document is for the convention between Health Care and the interaction with stack holder:

-When writing this document it was inherited that all requirements have the same priority.

-First there is presented an overall view about HealthCare and then all features and functions are analyzed in detail.

1.5 Intended Audience and Reading Suggestions
This requirement document contains general information about health care main classes and use cases, functions,
features and special technologies. It describes in detail all that health care needs to work properly and with safety. This
document is intended for:
-Developers: in order to be sure they are developing the right Health Care Project that fulfills requirements provided in
this document.
-Testers: in order to have an exact list of the features and functions that has to respond according to requirements and
provided diagrams.
-Users: in order to get familiar with the idea of the Health Care Project and suggest other features that would make it
even more functional. -Documentation writers: to know what features and in what way they have to explain. What
security technologies are required, how the system will response in each users action etc.
-Advanced end users, end users/desktop and system administrators: in order to know exactly what they have to expect
from the system, right inputs and outputs and response in error situations. This software application intended for
different audiences: to sell the drug when personnel enter the information, the patient's condition, the software will
display the drugs for sale..
1.6 Health Care Project Scope
-This software application intended for different audiences: employees sold drugs to achieve it in drugstores, the
software will display the drugs for sale -For users, it is used in smart phones
1.7 References

- http://www.ykhoanet.com
- http://www.cimsi.org.vn
- http://www.thuoc-suckhoe.com
- http://www.ykhoavn.com
- http://www.vietduchospital.edu.vn
- http://www.suckhoe360.com
- http://www.suckhoedoisong.vn
-http://www.amazon.com/b/ref=sr_aj?node=173514&ajr=0

+Pocket Medicine: The Massachusetts General Hospital Handbook of Internal Medicine Series: Pocket
NotebookLoose Leaf: 280 pagesPublisher: LWW; Fifth, North American Edition edition (October 7,
2013)Language: English

+CPT 2014 Professional Edition (Current Procedural Terminology, Professional Ed. (Spiral)) (Cpt / Current
Procedural Terminology (Professional Edition)Series: Cpt / Current Procedural Terminology (Professional
Edition)Spiral-bound: 912 pagesPublisher: American Medical Association; 2014 edition (September 23,
2013)Language: English

+Admission Assessment Exam Review, 3eSeries: Admission Assessment Exam Review (Book
3)Paperback: 184 pagesPublisher: Elsevier; 3 edition (March 20, 2012)Language: English


+Davis's Comprehensive Handbook of Laboratory and Diagnostic Tests With Nursing Implications
(Davis's Comprehensive Handbook of Laboratory & Diagnostic Tests With Nursing
Implications)Series: Davis's Comprehensive Handbook of Laboratory & Diagnostic Tests With Nursing
ImplicationsPaperback: 1536 pagesPublisher: F.A. Davis Company; 5 edition (January 25, 2013)Language: English

+Tietz Fundamentals of Clinical Chemistry and Molecular Diagnostics, 7e (Fundamentals of
Clinical Chemistry (Tietz))Series: Fundamentals of Clinical Chemistry (Tietz)Hardcover: 1104
pagesPublisher: Saunders; 7 edition (May 8, 2014)Language: English
Overall Description
1.8 Product/System Perspective
HealthCare should be a reuse the older version Health Care Project. It will be capable of integrating existing
control systems, in particular supervisory management software also other control systems. Ideally, it should
work with a variety of configuration management systems and not require any external software, although
the Java .Net will be required to operate it.This product is designed for managers, sellers,
student,dortor,teacher,but if user no have smaphone,they cant use this software

1.9 System/Product Features

P
r
o
c
e
s
s

n
a
m
e

Use Case Name Use Case Description

SEARCH Search all the information related to the disease, and
drugs
Disease Search Look up the common diseases
List disease List of common diseases
Information about disease Description of common diseases, symptoms, pathogens,
viruses cause disease, ...
First aid methods .

ways of avoiding the way to prevent disease
FQA Frequently asked questions about the disease
Medication Advice drugs recommended

List Medical List of drugs
Administration and
dosage
How to use the medication and tips
1.10 User requirements
This software must be satisfied the medium level of the education of the user, do not required the high level of
education or the expert knowledge about the technical.
Administrator: Admin is the one who operate the system. He is the top privilege level to control it. He must
have the advance knowledge about database and technology
Sellers: (including sellers, warehouse keepers and accountants) dont need to have the expert knowledge about
smart phone. They just have to know the most basic thing about smart phone
Customers they just have to know the most basic thing about smart phone..

2.4 User Classes and Characteristics
+ Sellers: is used to sell drugs, when customers buy medication sellers will search the diseases and drug loading of
software instructions + Customers: Customers will use software to aid when there is an emergency situation, in addition
customers will use the software to see how specific instructions for each type of patient medication
1.5 Operating Environment
HealthCare will be implemented in Java. It should therefore run on any platform to java.We will avoid the
use of platform-specific designs or code in doing so.HealthCare should run on Operating Systems:Android

- All new releases contain:
Filename Architecture Type
HealthCare -Setup.exe r112 .exe (android)
HealthCare-Setup.zip r112 .zip
Or Filename Architecture Type
HealthCare -Setup. r112 .exe (android)
HealthCare Setup.zip r112 .zip


And release notes witch describe what has changed and what has been added.
Nothing more than these is required for a fully functional HealthCare.
HealthCare. should run perfectly on older releases without any features limitations or data loss.
1.6 Design and Implementation Constraints
As mentioned, the implementation language will by Java, based off the .Net framework 2.0 free downloadable. The
issues will use Sky Driver as a data format.
These constraints are in place because HealthCare will be submitted as an entry in the Software Carpentry design
competition, which mandates the use of Java; the use of Android and Sky Driver is mandated to prompt an exploration
of Sky Driver as a technology (in addition to allowing the use of Sky Driver and existing libraries in development). It
should not rely on any particular command line implementation, etc.
1.7 User Documentation
By downloading HealthCare, the user also gets:
A compiled HTML Help file with a tutorial and full help on all features provided.
A HealthCare shortcut which take the user in the systems official website where are available downloads
update, plug-ins and extensions
1.8 Assumptions and Dependencies
Assumption
HealthCare is expected to be used by most of the Smart phone. It is assumed that with the API provided by
HealthCare it will be any control system by the managers It is assumed that HealthCare will be able to
handle any exception such as electricity cut off, experiment control systems, or accelerator control systems.It
is assumed that the operating systems on which HealthCare will run tasking.The number of users to be
handled with the HealthCare system will be very high

Dependencies
This HealthCare systems are inherited almost function of the older version and most provide all the function
of the current systems.
1.9 Apportioning of Requirements
-The HealthCare requirements described in sections 1 and 2 of this document are referred to as preliminary
specifications; those in section 3 are referred to as requirements (or functional) specifications. The two levels
of requirements are intended to be consistent. Inconsistencies are to be logged as defects. In the event that a
requirement is stated within both preliminary and functional specifications, the application will be built from
functional specification since it is more detailed.
'Essential requirements' are to be implemented for this version of 1.xx. 'Desirable requirements' are to be
implemented in this release if possible, but are not committed to by the developers. It is anticipated that they
will be part of future release. 'Optional requirements' will be implemented at the discretion of developers.

Specific Requirements
1.1 Functional Requirements Specification
1.1.1 Function Diagram


1.1.2 Use Case Diagram


3.1.3 Function Home page

Home page screen
Home page Definition

# Field Name Type Mandatory Max
Length
Description
1 Search Text Text Y 50
The textbox to enter
search keywords
Default Value: Search
Default value will be
cleared when Search
Text gets focus. When it
loses focus, if the text
value is still blank, the
default value will display
again.
2 Search Button Button Y -
The button to trigger
Search function

Enabled: True
3 Disease Search Button Y This image button
links to Disease
Search page

4 Medical List Button Y - This image button
links to Medical List
page

Use Case Specification

Home Page Use Case Diagram

Use Case ID UC01
Use Name Home Page
Actor User
Description Display the homepage and main application menu
Precondition N/A
Trigger Tap on Application Health System in the mobile phone
Post-Condition N/A
Main flows
Step Actor Action
1 User Tap on the hybrid application icon on mobile screen
2 System Display Loading screen with a progress bar
3 System After the progress bar finished loading, display the homepage of mobile
software

Alternative flows

N/A

3.1.4 SEARCH

Use Case

Use Case Search Diagram

Use Case ID UC02
Use Name Search
Actor User
Description Search a keyword in software application
Precondition MobiePhone have to turn on
Trigger Tap on Search button
Post-Condition Start Health Care application
Main flows
Step Actor Action
1 User Tap on search textbox in the page header
2 User Enter the search keyword
3 System A smart function will display a list of suggested keywords based on what user
is tapping
4 User Choose a suggested keyword or continue to type the keyword

5 User Tap the Search button in the virtual keyboard, or tap on the Search button
next to the search textbox
6

System
Display first 10 results in the search result page.
Display button NEXT in the end of search resultpage
7 User
Tap on NEXT button in the SEARCH RESULT page
8 System
Display a SEARCH RESULT with 10 other results
9 User
Tap on a result
10
Display a page that talk about the result
11 User
Tap on Back To Home button to go to Home page
Alternative flows

No. Actor Action
Exception Flow 1
1 User If User write nothing in the SEARCH TEXT and Tap on SEARCH
BUTTON
2 System Display SEARCH RESULT page with no result
No. Actor Action
Exception Flow 2
1 User If it has no result with key word in the search button
2 System Display SEARCH RESULT page with no result

3.1.5 Disease Search

Tap on
Disease Search

Disease Search Screen

Disease Search Definition

Length
Description
1 Search Text Text Y 50
The textbox to enter search
keywords
cleared when Search Text
gets focus. When it loses
focus, if the text value is
still blank, the default value
will display again.
2 Search Button Button Y -
Search function

Enabled: True
3 Disease List Button Y - List of disease .
Tap on the a disease in
the list to link to
Disease List screen
4 Name of Disease Button Y - List diseases , sort by
Anphabet

Tap on to link to
disease page
5 . Button N - ..is a buttom
Tap on to see more

Use Case


Use Case Disease Search Diagram

Use Case ID UC03
Use Name Disease Search
Actor User
Description Search Disease List
Precondition Mobie have to turn on
Trigger Tap on button Disease
Post-Condition Health Care Application are started
Main flows
Step Actor Action
1 User Tap on button Disease Search on the software
3 System After the progress bar finished loading, display a list common disease : 10
diseases
4 System A disease is a button
5 System The diseases sort by Anphabet
6 User Tap on . To see 10 other Diseases( = enable)
7 System Display 10 other Diseases
8 User Tap on a disease
9 System Display Disease Choice List
Alternative flows
No. Actor Action
Exception Flow 1
1 System In Step 7 at Main flows :
= disable if otherDisease = 0
2 System In Step 7 at Main flows : if it hasnt enough 10 other Diseases,
Display 1 or 2 or 3.or 9 flow the Database List Disease


3.1.6 Disease Choice List

Disease Choice List Screen

Length
Description
1 Search Text Text N 50
keywords
will display again
2 Search Button Button - -
Search function

Enabled: True
3 Information about disease Button - - This image button
links to Information
about disease page

4 Medicine Advance Button - - This image button
links to Medicine
Advance page
5 Ways to avoiding Button - - This image button
links to Ways to
avoiding page
6 First aid methods Button - - This image button
links to First aid
methods page
7 FQA Button - - This image button
links to FQA page

Use Case

Use Case Disease List Diagram

Use Case ID UC04
Use Name Disease List
Actor User
Description Display a list to Choose disease and see information about that

Precondition N/A
Trigger Tap on a Disease in the List Disease to display Disease Choice List
Post-Condition N/A
Main flows
Step Actor Action
1 User Tap on a Disease in the list
3 System After the progress bar finished loading, display Disease Choice List :
Information about disease button
Medicine Advance button
Ways to avoiding button
First aid methods button
FQA button
4 User Tap on Information about disease button
5 System Display Information about disease page
Alternative flows

No. Actor Action
Exception Flow 1
1 User Tap on Medicine Advance button
2 System Display Medicine Advance page
No. Actor Action
Exception Flow 2
1 User Tap on Ways to avoiding button
2 System Display Ways to avoiding page
No. Actor Action
Exception Flow 3
1 User Tap on First aid methods button
2 System Display First aid methods page
No. Actor Action
Exception Flow 4
1 User Tap on FQA button
2 System Display FQA page


3.1.7 Information about disease

Length
Description
keywords
will display again
Search function

Enabled: True
3 Information about disease Label - - Description of
common diseases,
symptoms, pathogens,
viruses cause disease,
...


UseCase Diagram

Use Case ID UC05
Use Name Information about disease
Actor User
Description Description of common diseases, symptoms, pathogens, viruses cause disease,
...
Precondition Start the Health Care application
Trigger Tap on a disease in the List Disease
Post-Condition Tap on Disease Search/a Disease/ Information about disease
Main flows
Step Actor Action
1 User Tap on button Information about disease in the list
3 System After the progress bar finished loading, display information about disease .

4 User Read information that user to know
5 User Touch and drag up the screen to see more information

6 System Information from the bottom of screen go up
Alternative flows

Exception Flow 1
Sub
step
Actor Action
2 System If no more information , the screen cant go up

3.1.8 Medicine Advice

Length
Description
keywords

will display again
Search function

Enabled: True
3 Medicine Advice

Labels The drugs
recommended to Take

Use Case Diagram

Use Case ID UC06
Use Name Medicine Advice

Actor User
Description Display drugs recommended , The drugs that user should to take
Post-Condition Tap on Disease Search/a Disease/ Medicine Advice
Main flows
Step Actor Action
1 User
Tap on button Medicine Advice
in the list

3 System After the progress bar finished loading, display a list of drugs user should to
take

4 User See a list drugs
Alternative flows

Exception Flow 1
Sub
step
Actor Action

3.1.9 Ways of avoiding

Length
Description
keywords

will display again
Search function

Enabled: True
3 Ways of avoiding

Labels - - Ways to avoiding
disease

Use Case Diagram

Use Case ID UC07
Use Name Ways to avoiding

Actor User
Description Display Some way to avoiding the disease
Post-Condition Tap on Disease Search/a Disease/ Ways to avoiding

Main flows

Step Actor Action
1 User
Tap on buttonWays to avoiding
in the list
3 System After the progress bar finished loading, display some ways to way to avoiding
the disease

4 User See information
Alternative flows

Exception Flow 1
Sub
step
Actor Action

3.1.10 First aid methods


Length
Description
keywords
will display again
2 Search Button
Button
- -
Search function

Enabled: True
3
First aid methods

Labels
- -
Ways to Fisrt aid
methods

Use Case ID UC08
Use Name
First aid methods

Actor User
Description Display First aid methods when see people is diseased
Post-Condition
Tap on Disease Search/a Disease/ First aid methods
Main flows
Step Actor Action
1 User
Tap on buttonFirst aid methods
in the list
3 System After the progress bar finished loading, display some ways to First aid methods
4 User See information

Alternative flows

Exception Flow 1
Sub
step
Actor Action


3.1.11 FQA

Length
Description
keywords
will display again
2 Search Button
Button
- -
Search function

Enabled: True
3
FQA

Labels
- -
Display some common
question about disease


Use Case Diagram

Use Case ID UC09
Use Name
FQA

Actor User
Description Display Some common question that user usually ask
Precondition
Start the Health Care application

Post-Condition
Tap on Disease Search/a Disease/ First aid methods
Main flows

Step Actor Action
1 User
Tap on buttonFQA
in the list
3 System After the progress bar finished loading, display some common question about
disease
Alternative flows

N/A
Sub
step
Actor Action
N/A

3.1.12 List Medical

Length
Description
keywords

will display again
2 Search Button
Button
- -
Search function

Enabled: True
3
List Medical

Button
- -
Display list of
medicine.
Tap on a medicine to
link to
Administration and
dosagepages

Use Case ID UC10
Use Name
List Medical

Actor User
Description Display list medicine
Precondition N/A
Trigger N/A
Post-Condition N/A
Main flows
Step Actor Action
1 User
Tap on buttonList Medical
in the Home screen

3 System After the progress bar finished loading, display The List All Medicine
Alternative flows

N/A
Sub
step
Actor Action
N/A

3.1.13 Administration and dosage

Length
Description
keywords

will display again
2 Search Button
Button
- -
Search function

Enabled: True
3
Administration and dosage

Labels
- -
Display
Administration and
dosage about medicine

Use Case ID UC11
Use Name
Administration and dosage

Actor User
Description Display information aboutAdministration and dosage of medicine

Precondition N/A
Trigger N/A
Post-Condition N/A
Main flows
Step Actor Action
1 User
Tap on buttonAdministration and dosage

in the List Medical screen
3 System After the progress bar finished loading, display Administration and dosage of
medicine
Alternative flows

N/A
Sub
step
Actor Action
N/A

1.2 Non-Functional Requirements Specification
1.2.1 External Interface Requirements
1.2.1.1 User I nterfaces
User interface is designed to be simple and easy to see. The main interface consists of functions:
search,list medical , list disease. With 2 main function is to display the diseases and shown the drug
to be used for each type of disease.

1.2.1.2 Hardware I nterfaces
These hardware requirements are based on hardware requirements of Microsoft SQL Server 2008
Database. The hardware requirements should be changed according to the actual through put of the
system. The detailed information of hardware configuration will be described in Infrastructure
Design.

1.2.1.3 Software I nterfaces
N/A


1.2.2 Other Nonfunctional Requirements
1.2.2.1 Performance Requirements
Data on medication and disease must complete and absolute accuracy. The ability of the server
to be large enough to support multiple users.
1.2.2.2 Design constraints
The system will be implemented to support for English only.
The interface must be designed so that everyone can become familiar.
The icons have been designed so that users can realize its function. The color of the interface as
well as the icons are not too many colors. Items "Search" should display search results can have
while typing each character. Interface compact, easy to use
1.2.2.3 Safety Requirements
N/A
1.2.2.4 Security Requirements
N/A
1.2.2.5 Software Quality Attributes

Ability to sort the data according to different themes to classify information according to
user.
Accuracy: Validate carefully the data before insert to database. Timesheet information has
to consistency in all system.
Code is written as a module and has comment for easy upgrade later.
Provide full documentation of the program code. Each function must have at least one
comment.
Once a month, the system will be tested carefully again based on the results of its
operation at time before.
Check logs must be kept to support the maintain process.

Other Requirements

Appendix A: Glossary
<Define all the terms necessary to properly interpret the SRS, including acronyms and
abbreviations. You may wish to build a separate glossary that spans multiple Health Care Projects
or the entire organization, and just include terms specific to a single Health Care Project in each
SRS.>

Appendix B: Analysis Models
<Optionally, include any pertinent analysis models, such as data flow diagrams, class diagrams,
state-transition diagrams, or entity-relationship diagrams.>
Appendix C: Issues List
< This is a dynamic list of the open requirements issues that remain to be resolved, including
TBDs, pending decisions, information that is needed, conflicts awaiting resolution, and the like.>

Software Requirements 2 About Health Care

Încărcat de

Informații document

Drepturi de autor

Formate disponibile

Partajați acest document

Partajați sau inserați document

Opțiuni de partajare

Vi se pare util acest document?

Este necorespunzător acest conținut?

Drepturi de autor:

Formate disponibile

Software Requirements 2 About Health Care

Încărcat de

Drepturi de autor:

Formate disponibile

Copyright 2014 by H4T Group.

S-ar putea să vă placă și