Good Health SRS

8/8/2019 Good Health SRS

1/15

ER Diagram for the Hospital Management System

SOFTWARE REQUIREMENT SPECIFICATION ON

GOODHEALTH HOSPITAL MANAGEMENT SYSTEM

Prepared by:Shyam Narayan Gupta


2/15


TABLE OF CONTENTS

1. INTRODUCTION

1.1. Current System1.2. Envisioned System1.3. Scope

2. OVERALL DESCRIPTION

2.1 . Functional Requirements2.2. Non-Functional Requirements2.3. Hardware2.4. Software

3. UML DIAGRAMS

3.1. Use case diagram3.2. Class diagram3.3. Object diagram3.4. Sequence diagram3.5. Activity diagram3.6. Component diagram

4. TEST CASE

5. E-R DIAGRAM AND NORMALIZATION

1.3. Scope:


3/15


This application will enable the Desk Officers to check the availability of thedoctor, register the patients and generate bills of outpatients according to theservices utilized by them.Will facilitate administrators to modify, create and delete the doctors andmedicines information available.


4/15


2. OVERALL DESCRIPTION

2.1 . Functional Requirements:

LOGIN PAGE:

Name: L ogin page

Description: Displays a user interface for logging onto the system.

Actors: Administrators and Desk Officers

Functions available:

a. Logon: Fires the logon routine with the user name and password,assigns the required rights, and updates the relevant sessionvariables.

b. Exit: Closes the web page.

Preconditions: Administrator/Desk Officer enters the correct usernameand password.

Post conditions: After entering correct username and password, itshows relevant page.

Non-functional requirements: The software system should not takemore time for logging the page.

ADMINISTRATION PAGES:

Name: M edical Staff

Description: Displays a user interface to maintain the list of doctors andallows the addition/deletion/modification of data for medical staff.M edical staff can include doctors, junior/resident doctors, nurses, wardboys/assistants.

Actors: Administrators


a. ListAll: L ist all medical staff grouped by type.


5/15


b. Search: Allows searching for a medical staff by name.c. Add a New Staff Member: Allows addition of a new staff member.d. Delete a Staff Member: Deletes a staff member from the database.e. Edit Staff Member Details: Edits a staff member details.

Preconditions: Administrations would get a list of medical staff. Post conditions: According to the requirement the administrator canadd, edit or delete the list.

Non-functional requirements: The software system should not takemore time to load the list of medical staff.

Name: P harmacy

Description: Displays a list of medicines in the pharmacy.

Actors: Administrators


a. ListAll: L ist all the medicines offered by the laboratory.b . Add a New Medicine: Add a new medicine to the pharmacy.c . Delete an Existing Medicine: Deletes an existing medicine fromthe pharmacy d . Modify Medicine Details: Allows modification of a medicine inthe pharmacy.

Preconditions: Administrations would get a list of medical staff. Post conditions: According to the requirement the administrator can

add, edit or delete the list.

Non-functional requirements: The software system should not takemore time to load the list of medical staff.

DESK OFFICER PAGES:

Name: Outpatient

Description: P rovides various functions for an out-patient.

Actors: Desk Officer


6/15


7/15


2.3.Hardware Requirements:

Network : HP /Compaq Intel-based Server or NT/2000 H P /Compaq Intel-

based Server. W orkstations:

At a minimum, the system will function within the parameters of the all Desktop configuration(s) P entium 4, 3.2GHz, 512 MB RAM .

2.4. Software Requirements:

Operating system : Windows X P B ack end : M icrosoft SQ L Server 2005Front end : Net B eans IDE 6.1 B rowser : Internet explorer


8/15


3. UML DIAGRAMS

3.1. Use case diagrams:

Use case for administrator:


9/15


Use case for Desk officer:


10/15


3.2.Class diagrams:

Class diagram of administrator:


11/15


Class diagram of Desk officer:


12/15


4. TEST CASE

Test case for administrator:

Test case for Desk Officer:

S.NO

TEST CASE

ACTUAL TEST RESULT

EXPECTED TEST

RESULT 1.

2.

3.

Login: Administrators with a user name and password will access thesite.

Clicking Doctors and staff tab

Clicking Medicines tab

Valid Username & password

Invalid Login(Either invalid username,invalid password or bothinvalid username and invalid

password)

Administrator moves todoctors and staff tab

Administrator moves toMedicines page.

Will lead theadministrators to their

personal page.

Will get an error messageThat the login isunsuccessful and will ask to enter it again.

List all doctors and staff details which allowsaddition, deletion andmodification.

Lists all Medicinesdetails which allowsadministrator to add,delete and edit themedicines details.


13/15


S.NO TEST CASE ACTUAL TEST RESULT EXPECTED TESTRESULT

1

2.

3.

Login ID: Only Desk Officer with a login ID and passwordcan enter

Desk Officer takes patientid(unique code) from theexisting patients.

Desk Officer registers the patientif he/she is a new patient.

Valid Login ID

Invalid Login ID(Either invalid username,invalid password or bothinvalid username and invalid

password)

Enters the patient id. If Unique Code is valid.

Enters the name, age, heightand other details.

Will be allowed to accessthe site.

Message to be displayedInvalid username.

Generates appointmentnumber depending on theavailability of the doctor and type of doctor selected.

If all the details are enteredwith out any errors theapplication should generatea unique patient id number.Also, the patients are giventhe appointment number depending upon theavailability of the doctor and type of doctor selected.


14/15


Has a {1:n}

Avails{1:n Has a[1:N]

Visits[1:1] Avail [1:n]

Is Raised By {1:1} Avail [1:n]

Paid By{1:n}

Is Raised By[1:n}Admitted To{1:1}

Paid By{1:n}

An Assigned To[1:n]

Belong To[1:n]

Time

Code Location

Site

In patient visit Charges

Working Hours

Emergency Contact

Type (Doctor/Junior

Doctor?Nurse)

Patient Value

Service Availed Normal

Re ort

Patient

Code

Descriptio

Char e

Name

Salt Base

Price

Stock Leve

Re-order Level

Code

Descriptio

Daily Charg

Lab

User

Bill

Login

Password

First Name

Last Name

Bill

Billing

IsPaid

PharmacyMedicine

Wards

Medical Staff

Name

Adderss

Type (Doctor/Junior Doctor?Nurse)

Emergency Contact

Working

In patient visit Charges

Outpatient visit Charges

Beds

Code Status

NameAddress


15/15


S.NO TOPIC DATE TEAM MEMBERS

1.

2.

3.

4.

5.

INTRODUCTION Existing System Proposed System Scope

OVERALL DESCRIPTION Functional requirements Non-Functional

requirements Hardware Software

UML DIAGRAMS Use case Diagram Class Diagram

Object Diagram Sequence Diagram Activity Diagram Component Diagram

TEST CASE

E-R DIAGRAM

19-10-2009

21-10-2009

21-10-2009

to25-10-2009

26-10-2009

28-10-2009

Shyam Narayan Gupta

Documents

Good Health SRS