Hospital Mis
NOTE: This template is shareware downloaded from www.processimpact.com. All shareware payments are donated to the Norm Kerth Benefit Fund to help a consultant who is disabled with a brain injury. Please visit http://www.processimpact.com/norm_kerth.html to make a shareware payment ($10 suggested). Thank you!
Software Requirements Specification for HOSPITAL MIS
Version 1.0 approved
Prepared by , Agha farooq,
INTERNATIONAL MARKET FOR PREPARING SRS (IMSRS).
TABLE OF CONTENTS: 1. Introduction 1.1. Purpose 1.2. Scope 1.3. Definitions, Acronyms, and Abbreviations 1.4. References 1.5. Overview
2. General Description 2.1. Product Perspective 2.2. Product Features 2.3. User Characteristics 2.4. General Constraints 2.5. Assumptions and Dependencies
3. System Features 3.1. Systemfeature 1 3.2. Systemfeature 2(& so on)
4.External Interface Requirements 4.1. Hardware Interfaces 4.2. Software Interfaces 4.3. Communication Interfaces
5. Other Non-Functional Requirements 5.1. Security 5.2. Performance Requirements 5.3. Maintainability 5.4. Reliability
6.Other Requirements Appendix A:Glossary Appendix B:Analysis Model
1. Introduction
1.1. Purpose The purpose of this document is to describe the requirements for the Hospital Patient Info Management System (HPIMS). The intended audience includes all stakeholders in the potential system. These include, but are not necessarily limited to, the following: Administrative Staff, patients and developers.
Developers should consult this document and its revisions as the only source of requirements for the project. They should not consider any requirements statements, written or verbal as valid until they appear in this document or its revision.
1.2. Document Conventions:
Hospitals main features are especially highlited with RED and BLUE combination.
Software Requirements Specification for HOSPITAL MIS
Version 1.0 approved
Prepared by , Agha farooq,
INTERNATIONAL MARKET FOR PREPARING SRS (IMSRS).
TABLE OF CONTENTS: 1. Introduction 1.1. Purpose 1.2. Scope 1.3. Definitions, Acronyms, and Abbreviations 1.4. References 1.5. Overview
2. General Description 2.1. Product Perspective 2.2. Product Features 2.3. User Characteristics 2.4. General Constraints 2.5. Assumptions and Dependencies
3. System Features 3.1. Systemfeature 1 3.2. Systemfeature 2(& so on)
4.External Interface Requirements 4.1. Hardware Interfaces 4.2. Software Interfaces 4.3. Communication Interfaces
5. Other Non-Functional Requirements 5.1. Security 5.2. Performance Requirements 5.3. Maintainability 5.4. Reliability
6.Other Requirements Appendix A:Glossary Appendix B:Analysis Model
1. Introduction
1.1. Purpose The purpose of this document is to describe the requirements for the Hospital Patient Info Management System (HPIMS). The intended audience includes all stakeholders in the potential system. These include, but are not necessarily limited to, the following: Administrative Staff, patients and developers.
Developers should consult this document and its revisions as the only source of requirements for the project. They should not consider any requirements statements, written or verbal as valid until they appear in this document or its revision.
1.2. Document Conventions:
Hospitals main features are especially highlited with RED and BLUE combination.