Software Requirement Specification Essay - 1748 Words

A patient information system called Mental Health Care-Patient Management System (MHC-PMS) is needed to provide medical information about patients with mental health issues and the treatments that are receiving. The MHC-PMS will be a database in which all clinics can interact with to get patient medical information. A Software Requirement Specification (SRS) will be needed which will include four user requirements and four system requirements. A detail description of four nonfunctional and four functional requirements will be found in the SRS. The last part of the SRS will include a detail requirement specification. According to Sommerville (2011), the SRS is an official statement which system developers use to know what needs to be†¦show more content†¦Another requirement would be to make it easy to input the patient information into the database. For an example using the tab key to move from field to field instead of having to move the mouse and click in the next field. By having keyboard short cuts built into the program will allow staff to input information more quickly into the database saving time. A fourth user requirement will be to allow the staff to input information into the system from other hospitals or clinics from out of town if they have an electron record such as text file or spreadsheet information. There are some system requirements the system will need to meet along with the user requirements. Medical information is protected under the Health Insurance Portability and Accountability Act (HIPAA). According to Kim Solomon (2012), HIPAA applies to protected health information which includes mental and physical health data, (p. 442). The MHC-PMS database will contain protected health information and in order to meet the requirements of HIPAA, security elements will need to be added as a system requirement. One example of security added into the system is using login and password information to help prevent unauthorized access to the da ta. User accounts will be setup only to access files the staff needs to get to. For an example doctor will see medical information such as test results and be able to add information where a receptionist will not have access toShow MoreRelatedSoftware Requirement Specifications1475 Words   |  6 PagesSoftware Requirements Specification 1. Introduction 1.1 Purpose This document is a definition of software requirements to develop an automated night class enrolment system and flexible query database required by St.Johns Central College. This document will present the functional, non-functional, and design constraint requirements for the system to be developed. Use case models and descriptions are included along with class diagrams to help model and specify the functional requirements and specificationsRead MoreSoftware Requirements Specifications For Emergency Calling1309 Words   |  6 Pages Software Requirements Specifications Emergency Calling Version Primary authors Description of Version 1.0 Lavanya Yellapragada(w930339), Venkata Kodali(w927197) Software requirement specification document 1.Introduction 1.1 Purpose of the document The purpose of this software requirements specification document is to provide a detailed description of the functionalities of the Emergency Calling application. This document will cover each of the applications intended features, as well asRead MoreSoftware Requirements Specification ( Srs ) Essay1283 Words   |  6 Pages Software Requirements Specification The introduction of the Software Requirements Specification (SRS) provides an overview of the entire SRS Purpose, Scope, Definitions, Acronyms, Abbreviations, References and Overview of SRS. A requirements specification for a software system is a complete description of the behavior of a system to be developed. It includes a set of Use cases that describe all the interactions the users will have with the software. Use cases are also known as FunctionalRead MoreUse Of Software Requirements Specification ( Srs )2204 Words   |  9 PagesMost project teams generally use software requirements specification (SRS) to document their requirements in natural language. However, a document based approach has some limitations: a document is difficult to keep current especially if it is a long one, it is hard to communicate changes to the team members who are affected by that change, it is difficult to associate supplementary information with each requirement and it is hard to define links betwe en requirements and its decompositions or correspondingRead MoreUsing Quality Function Deployment in Software Requirements Specification5390 Words   |  22 PagesUSING QUALITY FUNCTION DEPLOYMENT IN SOFTWARE REQUIREMENTS SPECIFICATION Abstract. We present in this paper an approach to requirements specification based on quality function deployment (QFD). We discuss how techniques like QFD with accompanying tool-support can contribute to the development of high quality requirements models that are the basis for information systems that are perceived as valuable by the stakeholders of the systems. Based on the practical application of this technique on aRead MoreSoftware Requirements Specification : Automated Employee Management System Essay844 Words   |  4 Pages Software Requirements Specification AUTOMATED EMPLOYEE MANAGEMENT SYSTEM BY BALAKRISHNA PASAM 023220257 Table of contents Table of contents†¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦........ Revision History†¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦ 1. Introduction†¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦. 1.1 Purpose†¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦... 1.2 Intend Audience and reading suggestions†¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦.. 1.3 Project Scope†¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦ 1.4 References†¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦ 2Read MoreSoftware Requirements Specification : Project Details1986 Words   |  8 Pages Software Requirements Specification Project Details Project No. Project Name SRS Name Document Signed Off By Name First name Surname Title Signature Date (Project Sponsor) (Local Business) (Business Analyst) (Delivery Manager) Please add new row if more signoff parties are required SRS Version Control Version Number n.n Issued On Date YYYY/MM/DD Author(s) First name Surname Title Reviewer(s) First name Surname Title Change DescriptionRead MoreWhat And How The Software Requirement Specification ( Srs ) Should Be Made Between Customers And Contractors? Essay1754 Words   |  8 PagesThe debate about what and how the software requirement specification (SRS) should be made between customers and contractors or suppliers continues. Also most computer science engineers and researchers agree that, software requirements specification permits a rigorous assessment of requirements before design can begin and reduces later redesign. It should also provide a realistic basis for estimating product costs, risks, and schedules [1], in other words, the SRS is the step that one would use toRead MoreThis chapter will describe about the software requirements and specifications of the HBScan600 Words   |  3 PagesThis chapter will describe about the software requirements and specifications of the HBScan application. This will cover about the purpose, scope, references, overall descript ion, functional and non-functional requirements, user classes and characteristics, and operating environment. Those topics will be discuss further in next section. 4.2 PURPOSE The purport of this document is to present a detailed description of the HBScan. It will explicate the purport and features of the application, whatRead MoreEssay on Captiva Conglomerate Case Study Analysis632 Words   |  3 PagesMajor Facts: ï  ¶ System specifications not clearly defined ï  ¶ Contract wording is partial to S. O. Software ï  ¶ Spares management module is a disaster ï  ¶ Spares management module currently complicated and un-useable/outdated ï  ¶ Spares management module behind schedule ï  ¶ Regional and centralized inventory management system behind schedule ï  ¶ S.O. Software depleted allotted financing ï  ¶ The system software specifications were not drafted by S.O. Software personnel Major Problems: ï  ¶ The contract