Page 1

< Gas agency management system > Software Requirements Specification <team name> Version < 6.0> <date>

< team Name >

Hospital Management System
Software Requirements Specification

Version < 6.0>

Team Guide: Mrs. G.G.Bilaye Members: 1 Tushar Jadhav. 2.Sunaina Darvesh

College Name: Smt. Kashibai Navale College Of Engineering. Pune. Department: Information Technology State: Maharashtra

Hospital Management system Software Requirements Specification <team name>

H <date>

Revision History
Date <date> <date> Version 1.0 2.0 Description Synopsis Synopsis Author <team name> <team name>

<Team Name>/ <SKNCOE>

Page 2

Hospital management system Software Requirements Specification <team name>

Version 6.0 <date>

Table of Contents
Description 1.0 Introduction 1.1 1.2 1.3 1.4 1.5 1.6 Purpose Scope Definition, Acronyms, and Abbreviations References Technologies to be used Overview Page No.

2.0

Overall Description 2.1 2.2 2.3 2.4 2.5 2.6 2.7 2.8 Product Perspective Software Interface Hardware Interface Product Function User Characteristics Constraints Architecture Design Use Case Model Description

<Team Name>/ <SKNCOE>

Page 3

Hospital management system Software Requirements Specification <team name>

Version 6.0 <date>

2.9

Class Diagram ........................................................................ Sequence Diagram s...............................................................

2.10

Database Design .................................................................... 2.11.1 2.11.2 ER Diagram ............................................................... Schema ......................................................................

2.12 Assumptions and Dependencies 3.0 Specific Requirements 3.1 3.2 Use Case Reports Supplementary Requirements

<Team Name>/ SKNCOE

Page 4

< Hospital Management System >

Version 6.0

Software Requirements Specification

1.0 Introduction:
To Provide an integrated Solution for the Hospital, which Helps in Efficient Management of the Hospital. Enhance Patient Care. Improve work efficiency. Enable the Growth of the Hospital
1.1 Purpose:

The purpose of this document is to describe all the requirements for the Hospital Patient Management System (HPMS). Its parameters and goals. This document describes the project's target audience and its user interface, hardware and software requirements. It defines how our client team and audience see the product and its functionality.

1 . 2 Scope:

The proposed software product is the Hospital Patient Management System (HPMS).
Basic Features:

Patient registration Appointments scheduling Billing and payments (cash, CC, insurance) Security of the whole sysem Pharmaceutical drugs/equipment Staff management (work roster, availability, scheduling, etc) Management functions (report generation, accounting, etc) System administration Resource allocation (booking rooms, operating theatres, etc)
1.3

Definitions, Acronyms, and Abbreviations: HTML (Hyper Text Markup Language): It is used to create static web pages. JSP (Java Server Pages): It is used to create dynamic web content. J2EE (Java 2 Enterprise Edition): It is a programming platform, belonging to the Java platform, which is used for developing and running distributed java applications.

WASCE (WebSphere Application Server Community Edition): It is an application server that runs and supports the J2EE and the web service applications. WSAD (WebSphere Studio Application Developer ): It is a designer toolkit which designed to develop more complex projects by providing a complete dynamic web service. DB2 (IBM Database 2): It is a database management system that provides a flexible and efficient database platform to raise a strong "on demand" business applications. HTTP (Hyper Text Transfer Protocol): It is a transaction oriented client/ server protocol between a web browser and a web server.

<team name>/ < SKNCOE >

Page 5

< Hospital Management System >

Version 6.0

< Hospital Management System > Software Requirements Specification <team name>

Version X.0 <date>

1
and store data.

XML (Extensible Markup Language): It is a markup language that was designed to transport

Ajax (Asynchronous Java Script and XML): It is a technique used in java script to create dynamic web pages.

3 4
5 6 7

Web 2.0: It is commonly associated with web applications which facilitate interactive information sharing, interoperability user-centered design and collaboration on the World Wide Web.

8 1.4 References:

<team name>/ < SKNCO E >

Page 6

< Hospital Management System > < Project scenario name > Software Requirements Specification <team name> Version X.0 <date>

Version 6.0

1.5 Technologies to be used:

1 1 1 1 1 2 3 4

J2EE: (Servlet, JSP, JAXP, Java Beans) Application architecture. JAVA: Application architecture. WASCE: (WebSphere Application Server Community Edition) Web Server DB2: IBM Database. Ajax: Asynchronous Java Script and XML. XML: Extension Markup Language. Web 2.0: RSS Feed 2.0. RAD 7.0: Development tool. Localization: 3 Languages - Hindi, Kannada, and English

<team name>/ < SKNCOE >

Page 7

< Hospital Management System > < Project scenario name > Software Requirements Specification <team name>

Version 6.0 Version X.0 <date>

1.6 Overview: The SRS will include two sections, namely:

-I- Overall Description: This section will describe major components of the system,
interconnections, and external interfaces.

-I- Specific Requirements: This section will describe the functions of actors, their roles in
the system and the constraints faced by the system.

2.0 Overall

Description:

2.1 Product Perspective:

< Enter the product perspective >

2.2 Software Interface:

-I- Front End Client: -I- Web Server: -I- Data Base Server: 4- Back End:

<team name>/ < SKNCOE>

Page 8

< Hospital Management System >

Version 6.0

< Project scenario name > Software Requirements Specification <team name>

Version X.0 <date>

2.3 Hardware

Interface:

4- Client Side: 4- Server Side:

2.4 Product 2.5 User

Functions:.

Characteristics:

2.6 Constraints: 2.7 Architecture 2.8 Use

Design:

Case Diagram : Diagram: Diagrams:

2.9 Class

2.10 Sequence

2.10.1 Database Design: 2.10.2 ER Diagram: 2.11 Assumptions

and Dependencies:

3. Specific Requirements:
3.1 Use Case Reports: 3.2 Supplementary Requirements: