07-04-2012, 01:02 PM
Software Requirements Specification
Software Requirements Specification.pdf (Size: 332.78 KB / Downloads: 67)
1. Introduction
1.1 Purpose
This SRS describes the software functional and nonfunctional requirements for release 1.0 of the Bethel Health Building System. This document is intended to be used by the members of the project team that will implement and verify the correct functioning of the system. The calculator is the highest priority and is set for release 1.0, but the database will not be constructed until release 2.0, as it has lower priority.
1.2 Intended Audience and Reading Suggestions
This document is intended for the use of the software developers and for our project partners, Rick and Anita Gutierrez. The software developers will use this document to identify which requirements are of highest priority, and our partners will read the document to confirm our understanding of their software needs.
1.3 Project Scope
The Bethel Health Building System will permit Rick and Anita Guiterrez, and their health building team, to input medical data regarding the carotid intima-media thickness, and make calculations that determine the vascular age of the patients and what actions should be taken by the patient to lower that vascular age. In addition to this, the patient information will then be stored in a patient database, which will allow for the team to follow up with patients in the future.
1.4 References
1. McClure, Todd and Stewart, Patrick. Bethel Health Building System Vision and Scope Document, users.marshall.edu/~mcclure53/Vision%20and%20Scope.pdf
2. Overall Description
2.1 Product Perspective
The Bethel Health Building System is a new system that replaces the current hand calculations and file system that they currently use. The context diagram in Figure 1 illustrates the external entities and system interfaces for the final release of the project. The first release of the system is expected to be able to perform the necessary calculations and then the second release will contain the database, which will store patient information.
Software Requirements Specification for Project TP Page 2
2.2 User Classes and Characteristics
Figure 1
Context diagram for the Bethel Health Building System.
User The user will be the one operating the Bethel Health Building System. They will perform the cIMT testing and input the data into the correct forms on the system. After the system processes this data, they will receive an output with the calculated data, given in printable forms to give to the patients.
Calculator The calculator will receive the data from the system that is inputted by the user. It will then take the data and find the mean, standard deviation, coefficient variation, and vascular age. It will then send the calculated data back to the system to update the forms.
Database The database will receive all of the information from the system, including the updated calculations, and store it in a database. This database will contain not only current information on the patient, but also information showing the medical history. The information will be sent to the system to update the form one last time before being sent to the user to be printed off.
Software Requirements Specification for Project TP Page 3
2.3 Operating Environment
The Bethel Health Building System will be designed to work on any operating system, provided that it can run a Java application.
2.4 Design and Implementation Constraints
CO-1: The database part of the system shall use the SQL database engine.
CO-2: All calculations shall be written in Java
2.5 User Documentation
The current system will not contain any user documentation. The final product should be close enough to the current system that it will be able to be used without instruction.
2.6 Assumptions and Dependencies
AS-1: The health building team will be able to understand the GUI and know where to input calculated data.
AS-2: The trained Zulu and Indian people will have some working knowledge or be able to be trained in using a computer.
DE-1: The operation of the system depends on our partners, Rick and Anita Gutierrez, training others how to use the system.
3. System Features
3.1 Data Collection and Display
3.1.1 Description and Priority
A user will be communicating with the system by inputting the measured cIMT data and receiving the final documents as an output for print. Priority = High.
3.1.2 Stimulus/Response Sequences
Stimulus: User inputs patient name
Response: System queries patient name to see if patient already exists
Stimulus: User inputs patient data
Response: System makes necessary calculations and updates the information to give back to the user for print.
3.1.3 Functional Requirements
Input.name: The system will check the database to see if patient already exists.
Input.data: The system will take the data and send it to the calculator to be updated.
Receive.data: The system will send the updated data back to the user in a printable form.
Software Requirements Specification for Project TP Page 4
3.2 Data Calculation
3.1.1 Description and Priority
A calculator will take the data from the system and use it to find the mean, standard deviation, coefficient of variation, and ultimately the composite vascular age. Then the data will be sent back to the system. Priority = High.
3.1.2 Stimulus/Response Sequences
Stimulus: System sends data to the calculator
Response: Calculator makes calculations and sends data back to the system
3.1.3 Functional Requirements
Data.retrieve: The calculator will retrieve the data from the system.
Data.calculate: The calculator will calculate the necessary data and find the composite vascular age.
Send.data: The calculator will send the data back to the system to update it.
3.3 Data Storage and Updates
3.1.1 Description and Priority
A database will take the patient information and store it in a centralized location that can be accessed by the medical team at any time. Priority = High.
3.1.2 Stimulus/Response Sequences
Stimulus: Updated information is sent to the database.
Response: Database adds entry and sends medical history back to system.
3.1.3 Functional Requirements
Patient.add: If the patient does not exist, then the database will add the patient to the database.
Patient.update: The database will take the information from the system and update the patient information.
Patient.send: The database will send the updated information, along with previous entries, to the system to update the final form.
4. External Interface Requirements
4.1 User Interfaces
UI-1: The Bethel Health Building System screen displays shall conform to the current forms that the medical team is currently using.
4.2 Hardware Interfaces
No hardware interfaces have been identified.
Software Requirements Specification for Project TP Page 5
4.3 Software Interfaces
SI-1: cIMT Database
SI-1.1: There is a connecting relationship between the Java GUI and the MYSQL Workbench database.
4.4 Communications Interfaces
No communication interfaces have been identified.
5. Other Nonfunctional Requirements
5.1 Performance Requirements
PE-1: The data from multiple laptops running the database should be able to be merged.
5.2 Safety Requirements
No safety requirements have been identified.
5.3 Security Requirements
Patient privacy is a security requirement, but this will be met by the fact that the medical team will be the only ones who have access to the portable database.
5.4 Software Quality Attributes
Adaptability-1: The database calculations will be made to be adaptable between people of different races and genders.
Portability-1: The database will be able to run on a portable laptop.