3/1/12

Sample - Software Requirements Specification for Hospital Info Management System

Real time chat

Keep participating in the monthly competition and win CASH prizes !!!

Home

Freshers

Career Advice

Articles

Interviews

Videos

Forums

Codes

Blogs

Jobs

Training

Community

MVPs | ASP.NET, WPF, SSIS etc. tutorials | C atalog | C oding Horror | Downloads | Quick Links | Top Posts | Top Authors | .NET News | Bookmarks |

Online : 14657 | Welcome, Guest!

Register Login

Home > Articles > Pattern and Practices > Sample - Software Requirements Specification for Hospital Info Management System

Sample - Software Requirements Specification for Hospital Info Management System

presents FREE videos on ASP.NET Tutorials HTML5 Tutorials CSS3 Tutorials GridView Tips Tutorials and more ...
Sha e

Article posted by Chvrsri on 10/26/2010 | Views: 17262 | Category: Pattern and Practices | Level: Beginn

Submit Article |

Search Articles |

Articles Home

Winners

This is a SRS document for Hospital Patient Information Management System. Where the hospital department people will store the info of the patient who has admitted and would retrieve his info when ever required. TABLE OF CONTENTS 1. INTRODUCTION 1.1. Purpose 1.2 Scope 1.3. Definitions, Acron ms, and Abbreviations 1.4. References 1.5 Overview 2. GENERAL DESCRIPTION 2.1 Product Perspective 2.2 Product Functions 2.3 User Characteristics 2.4 General Constraints 2.5 Assumptions and Dependencies 3. SPECIFIC REQUIREMENTS 3.1 Functional Requirements 3.2 Design Constraints 3.3 Non-Functional Requirements 3.3.1 Securit 3.3.2 Performance Requirements 3.3.3 Maintainabilit 3.3.4 Reliabilit

Gow.net Announcements Like us on Facebook

Top Articles Authors

Thu, 01-Mar-2012 Authors All Time Authors

4.CONCLUSION

1. I
1.1

d c i
Purpose

30050

12250

10000

Latest members | More ...

(Statis tic s delayed by 5 minutes )

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 dotnetfunda.com/ /article1052-sample-software-requirements-specification-for-hospital-info-manage
Ads

1/6

3/1/12

Sample - Software Requirements Specification for Hospital Info Management System statements, written or verbal as valid until they appear in this document or its revision.

1.2

Scope

The proposed software product is the Hospital Patient Info Management System (HPIMS). The system wil the information from the patients and then storing that data for future usage. The current system in use i system. It is too slow and cannot provide updated lists of patients within a reasonable timeframe.The in system are to reduce over-time pay and increase the number of patients that can be treated accuratel statements in this document are both functional and non-functional.

1.3 - Definitions, Acron ms, and Abbreviations HPIMS - Hospital Patient Info Management System PHN - Personal Health Number on health card Report - an account of patients Front-desk staff - administrative staff that work at reception desk Logon ID - a user identification number to enter the system Password - a word that enables one to gain admission into the system Web-based application - an application that runs on the Internet M SQL - a query language to interrogate the system GUI - Graphical User Interface SRS - Software Requirements Speficification 1.4 References No formal documents have been referenced in this document 1.5 Overview

Articles Categories

This Software Requirements Specification (SRS) is the requirements work product that formally specifies Info Management System (HPIMS). It includes the results of both business analysis and systems analysis techniques were used to elicit the requirements and we have identified your needs, analyzed and ref objective of this document therefore is to formally describe the systems high level requirements incl requirements, non-functional requirements and business rules and constraints. The detail structure of t organized as follows:

.NET Framework Articles ADO.NET Articles ASP.NET Articles ASP.NET AJAX Articles ASP.NET MVC Articles Azure Articles Best Practices Articles BizTalk Server Articles C# Articles CMS Articles CSS Articles Error and Resolution Articles F# Articles Advertisements HTML 5 Articles IIS Articles JavaScript Articles jQuery Articles LightSwitch Articles LINQ Articles Management Articles OOPS Articles Others Articles Pattern and Practices

Section 2 of this document provides an overview of the business domain that the proposed Hospi Management System (HPIMS) will support. These include a general description of the product, user charact constraints, and any assumptions for this system. This model demonstrates the development team's unde business domain and serves to maximize the team's ability to build a system that truly does support the bus Section 3 presents the detail requirements, which comprise the domain model.

2. Ge e a De c i
2.1 Product Perspective

This Hospital Patient Info Management System is a self-contained system that manages activities of the ho Info. Various stakeholders are involved in the hospital patient info system. 2.2 Product Functions The system functions can be described as follows:

Registration: When a patient is admitted, the front-desk staff checks to see if the patient is already reg hospital. If he is, his/her Personal Health Number (PHN) is entered into the computer. Otherwise a new Number is given to this patient. The patients information such as date of birth, address and telephone entered into computer system.

Patient check out. If a patient checks out, the administrative staff shall delete his PHN from the syste evacuated bed is included in available-beds list.

Report Generation: The system generates reports on the following information: List of detailed informatio patient who ha admitted in the hospital 2.3 User Characteristics
2/6

dotnetfunda.com/

/article1052-sample-software-requirements-specification-for-hospital-info-manage

3/1/12

Sample - Software Requirements Specification for Hospital Info Management System

The system will be used in the hospital. The administrators,front-desk staff will be the main users. Given th not all the users are computer-literate. Some users may have to be trained on using the system. The designed to be user-friendly. It uses a Graphical User Interface (GUI). Front-desk staff: They all have general reception and secretarial duties. Every staff has some basic for patients check-in or notification of appropriate people .

computer training. They

Administrators: They all have post-secondary education relating to general business administration practices. Every adminis computer training. They are responsible for all of the scheduling and updating day/night employee shifts. . 2.4 General Constraints The The this The

system must be delivered by January 1st 2011. existing Telecommunication infrastructure is based on IEEE100802.3 standards and the system m standard using category 5 cables for networking system must be user-friendly

2.5 Assumptions and Dependencies

It is assumed that one hundred IBM compatible computers will be available before the system is insta It is assumed that the Hospital will have enough trained staff to take care of the system

FlowChart Component

Use GoDiagram to add FlowCharts and Work Flows to your .NET application
www.nwoods.com

3. S ecific Re

i e

3.1 Functional Requirements Registration SRS001 Add patients The HPIMS shall allow front-desk staff to add new patients to the system. SRS002 Assign ID The HPIMS shall allow front-desk staff to give each patient a ID and add it to the patients record. This ID the patient throughout his/her stay in hospital. Check Out

Earn Degrees Online

Earn an Accredited Online Degree within 24 hours.Call 24x7.Apply Now

O nline De gre e Program sPr

hospital bed

used, hospital beds, medical equipm big assortment of used beds

www.hospitalbe d.nl

SRS003 Delete Patient ID The administrative staff in the ward shall be allowed to delete the ID of the patient from the system w checks out. SRS004 Add to beds-available list The administrative staff in the ward shall be allowed to put the beds just evacuated in beds-available list. Report Generation

University Degree Program

Earn an University Degree based on your Work or Life Experience.

www.Unive rsalDe gre e .com

SRS005 Patient information The HPIMS shall generate reports on patients about the following information: patients PHN, patients na bed number and the doctors name which was assigned. SRS006 Bed Aavailabilit The HPIMS shall generate reports on bed availability about the following information: ward name occupied/unoccupied. Database

Property Software

Software for landlords and property managers. 60 day free trial.

www.R e ntManage m e ntSof

SRS007 Patient Mandator Information Each patient shall have the following mandatory information: first name, last name, phone number, persona address, postal code, city, country, patient identification number. SRS008 Update Patient Information The HPIMS shall allow the user to update any of the patients information as described in SRS007. 3.2 Design Constraints

SRS009 Database The system shall use the MySQL Database, which is open source and free. SRS010 Operating S stem The Development environment shall be Windows 2000. SRS011 Web-Based dotnetfunda.com/ /article1052-sample-software-requirements-specification-for-hospital-info-manage

3/6

3/1/12

Sample - Software Requirements Specification for Hospital Info Management System SRS011 Web-Based The system shall be a Web-based application.

3.3 Non-Functional Requirements 3.3.1 Securit

SRS012 Patient Identification The system requires the patient to identify himself /herself using PHN SRS013 Logon ID Any user who uses the system shall have a Logon ID and Password. SRS014 Modification Any modification (insert, delete, update) for the Database shall be synchronized and done only by the adm ward. SRS015 Front Desk staff Rights Front Desk staff shall be able to view all information in HPIMS, add new patients to HPIMS but shall not b any information in it. SRS016 Administrators' Rights Administrators shall be able to view and modify all information in HPIMS. 3.3.2 Performance Requirements SRS017 SRS018 SRS019 SRS020 Response Time The system shall give responses in 1 second after checking the patients information. Capacit The System must support 1000 people at a time. User-interface The user-interface screen shall respond within 5 seconds. Conformit The systems must conform to the Microsoft Accessibility guidelines

3.3.3 Maintainabilit SRS021 SRS022 3.3.4 Reliabilit SRS023 Availabilit The system shall be available all the time Back Up The system shall provide the capability to back-up the Data Errors The system shall keep a log of all the errors.

4.CONCLUSION

This SRS document is used to give details regarding Hospital Patient Info Management System. In this a and non-functional requirements are specified inorder to get a clear cut idea to develop a project.

Requirements Software
Easy as Word, get Traceability on a Fingertip. Download Free Trial Now!
www.Polarion.com /Fre e -Trial

If you like this article, subscribe to our and Forums section.

RSS Feed. You can also subscribe via email to our Interview Q

Found interesting? Add this to:

Sha e

More | Bookmark It

Please Sign In to vote for this post. Latest Articles from Chvrsri How Different is C#.NET from VB.NET Creating a Windows Service Using C#

dotnetfunda.com/

/article1052-sample-software-requirements-specification-for-hospital-info-manage

4/6

3/1/12

Sample - Software Requirements Specification for Hospital Info Management System

Accessing a Method of aspx page into a User Control Restricting User To Login Multiple Times Using Same Credentials Multiple Row Deletion From GRIDVIEW

About Radha Srikanth

Experience: Home page: Member since: Level: Status: Biography: 0 year(s) https://www.mcpvirtualbusinesscard.com/VBCServer/RadhaSrikanth/card Friday, October 22, 2010 Silver [Member] [Moderator] [MVP] Myself , I am a MCTS on ADO.NET Application Development 3.5 . Working in an MNC @HYD

>> Write Response - Re pond o hi po

and ge poin Latest Articles Default child controls in any web page in the asp.net Creating Sql Server Report (RDLC) using Dataset Create SSRS Client Side Report

SQL Server integration with CLR aka SQL CLR (Part VI Creati user defined type in SQL CLR) WPF Data Binding Tutorial 3

How to play audio in the HTML5 and how to control the audio p HTML element ? What's new in HTML5 Forms WPF Data Binding Tutorial 2 HTML5 TAG ELEMENTS More ...

Related Posts
Design Pattern Interview Questions - Part 1 Design Pattern Interview questions, Factory, Abstract factory, prototype pattern ViewState Patterns in ASP.NET

Viewstate is one of the commonly use store to maintain state in page. For page level data or control data. But we some scenarios before using view state. This pattern helps to better manage ViewState in asp.net. How and where Microsoft has implemented [Decorator] GOF design patterns in .Net Framework Part-II

In Last articles, http://www.dotnetfunda.com/articles/article1514-how-and-where-microsoft-has-implemented-gof patterns-in-net-framewo-.aspx we saw that how Microsoft has used abstract Factory (GOF design pattern) patter framework library. In this article, we will see how Decorator Pattern has used in .Net Framework Library.

The Power of Documentation and Commenting the code

I have spent most of my career as a programmer. Most of the time i have been a stand alone programmer. I have organizations where documentation is always needed before a code can be written. where before you change a s program, you need to submit a change request document. By that time it looked like a waste of time, because mo are not fond of writting documentation, infect we rarely use Microsoft word. In this article i will share my experienc danger of not documenting your work. UML Interview Questions - Part 1

This Section will cover use case diagrams, primary and secondary actors, primary and secondary actors, Extend an class diagrams, protected in class diagrams, class diagram mean, composition in class diagrams, association in cla service class, entity and service class, generalization and specialization, abstract class and interface , object diagr diagrams.

File APIs for Programmers, by Aspose DOC, XLS, PPT, PDF, MSG and more Create, Edit, Convert and Print. Powerful and intuitive; used by more than 55 100 companies. Download your free trial version now. About Us | Contact Us | The Team | Advertise | Software Development | Write for us | Testimonials | Privacy Policy | Terms of Use | Link Exchange | Members | Go Top General Notice: If you found plagiarised (copied) contents on this page, please let us know the original source along with your

dotnetfunda.com/

/article1052-sample-software-requirements-specification-for-hospital-info-manage

5/6

3/1/12

Sample - Software Requirements Specification for Hospital Info Management System

correct email id (to communicate) for further action.

C opyright DotNetFunda.C om. All Rights Reserved. C opying or mimicking the site design and layout is prohibited. Logos, company names used here if any are only for reference purposes and they may be respective owner's right or trademarks. | 3/1/2012 10:44:42 AM

dotnetfunda.com/

/article1052-sample-software-requirements-specification-for-hospital-info-manage

6/6