Hospital Management System

Hospital Management

System

Project Guide:-Project Guide:-

Prof. Manisha Jadhav.Prof. Manisha Jadhav.

Project Developed By:-Project Developed By:-

Vinod JadhavVinod Jadhav

MCA V Roll No. 1205MCA V Roll No. 1205

PROJECT DESCRIPTION

•Type Of Project: Stand-Alone Type Of Project: Stand-Alone Application.Application.

•Duration: 30 days.Duration: 30 days.

System Life cycle DevelopmentSystem Life cycle DevelopmentSystem Investigation

Requirement Analysis

Design

Coding

Testing

Implementation

Maintenanace

Project progresses through the first 3 phases of “SDLC”

PRE-ANALYSISPRE-ANALYSIS

Client Requirement

• Good user friendly graphical Good user friendly graphical interfaceinterface

• Security should be providedSecurity should be provided

• Easy retrieve the DatabaseEasy retrieve the Database

• Easy payment optionsEasy payment options

• Fast and easy delivery of productsFast and easy delivery of products

Requirement Determination Techniques

• Structured Analysis.Structured Analysis.

• Technical Feasibility.Technical Feasibility.

• Economical Feasibility.Economical Feasibility.

• Fact Finding Methods.Fact Finding Methods.

Existing System With Drawback

• There is no Stand-alone Application dedicated for Hospital Management System.• Everything is happened manually.• Easy payment options are not available

OPERATINGOPERATING ENVIRONMENTENVIRONMENT

Client Side

•HARDWARE:HARDWARE: Pentium III or Higher,10GB HDD,128RAM.Pentium III or Higher,10GB HDD,128RAM.

•SOFTWARE:SOFTWARE:

Visual Studio 2005, SQL Server Visual Studio 2005, SQL Server

Developer’s Side

•Hardware:Hardware:

Pentium IV,256RAM,20GB HDD.Pentium IV,256RAM,20GB HDD.

•SoftwareSoftware::

Visual Studio 2005, Visual Studio 2005,

Windows Server 2003, SQL ServerWindows Server 2003, SQL Server

Types Of Users

•Administrator Level.Administrator Level.

Scope

•The System gives the details of patient.The System gives the details of patient.

•It shows the daily check up of all patient and It shows the daily check up of all patient and gives details about the doctors visiting timing gives details about the doctors visiting timing etc.etc.

•This shows all details of doctors that are This shows all details of doctors that are available.available.

•This shows all stock of medicen.This shows all stock of medicen.

Modules

•Registration and authentication Registration and authentication module for new Patient.module for new Patient.

•Doctors detailsDoctors details

• Bill PaymentBill Payment

SYSTEM REQUIREMENTS

Project Schedule

ActivityActivity Act. NameAct. Name PredecessorPredecessor No. of daysNo. of days

A Preliminary investigation A Preliminary investigation Nil Nil 6 6

BB Requirement analysis Nil 9 Requirement analysis Nil 9

CC Designing Designing A,B A,B 15 15

Future ScheduleFuture Schedule

DD Coding Coding C C 11 11

EE Testing Testing D D 5 5

FF Implementation Implementation E E 3 3

GG Maintenance Maintenance F F 2 2

Total DaysTotal Days 4545

Risk ManagementRisk Management

•Project Risk.Project Risk.

•Technical Risk.Technical Risk.

•Non Technical Risk.Non Technical Risk.

Feasibility StudyFeasibility Study

•Operational Feasibility.Operational Feasibility.

•Technical Feasibility.Technical Feasibility.

•Economical Feasibility.Economical Feasibility.

Data Flow DiagramData Flow Diagram

Entity Relationship Entity Relationship DiagramDiagram

Use Case Diagram Use Case Diagram

Class DiagramClass Diagram

Object DiagramObject Diagram

Sequence DiagramSequence Diagram

Activity DiagramActivity Diagram

Table DesignTable Design

Patient TablePatient Table

FieldsFields Data type Data type Size Size ConstraintsConstraints

pat_idpat_id CharChar 1010 Primary KeyPrimary Key

pat_namepat_name CharChar 3030 Not NullNot Null

AddressAddress VarCharVarChar 100100 Not NullNot Null

PinCodePinCode NumericNumeric 1010 Not NullNot Null

Mob_noMob_no NumericNumeric 1212 Not NullNot Null

DateDate DateDate -- Not NullNot Null

Inquiry Table

FieldsFields DatatypeDatatype SizeSize ConstraitsConstraits

Enq_idEnq_id CharChar 1010 Primary KeyPrimary Key

pat_idpat_id CharChar 1010 Foreign keyForeign key

TreatmentTable

FieldsFields DatatypeDatatype SizeSize ConstraintsConstraints

tret_idtret_id CharChar 1010 Primary KeyPrimary Key

Pat_idPat_id CharChar 3030 Foreign keyForeign key

doc_iddoc_id CharChar 3030 Foreign keyForeign key

Doctor TableDoctor Table

FieldsFields Data type Data type Size Size ConstraintsConstraints

Doc_idDoc_id CharChar 1010 Primary KeyPrimary Key

Doc_nameDoc_name CharChar 3030 Not NullNot Null

AddressAddress VarCharVarChar 100100 Not NullNot Null

PinCodePinCode NumericNumeric 1010 Not NullNot Null

Mob_noMob_no NumericNumeric 1212 Not NullNot Null

J_DateJ_Date DateDate -- Not NullNot Null

FieldsFields Data typeData type SizeSize ConstraintsConstraints

P_idP_id CharChar 1010 Primary KeyPrimary Key

pat_idpat_id CharChar 3030 Foreign keyForeign key

Q_amtQ_amt NumericNumeric 1010 Not NullNot Null

Disc_amtDisc_amt NumericNumeric 1010 Not NullNot Null

Final_amtFinal_amt NumericNumeric 1010 Not NullNot Null

Payment TablePayment Table


Rec_idRec_id CharChar 1010 Primary KeyPrimary Key

P_idP_id charchar 1010 foreignforeign

Pur_amtPur_amt NumericNumeric 1010 Not NullNot Null

Receipt TableReceipt Table

User TableUser Table


Us_idUs_id CharChar 1010 Primary KeyPrimary Key

PassPass charchar 1010 Not NullNot Null

Con_passCon_pass charchar 1010 Not NullNot Null


Dep_idDep_id CharChar 1010 Primary KeyPrimary Key

Dep_nameDep_name charchar 2020 Not NullNot Null

doc_iddoc_id CharChar 1010 Foreign KeyForeign Key

Department TableDepartment Table

TEST PROCEDURES

Testing :

Testing software is operating the software under controlled conditions to :

1. Verify that it behaves “as specified” ,2. To detect errors , and3. To validate that what has been specified is what the user actually wanted.

(1) VERIFICATION : It is the checking or testing of items, including software for performance and consistency by evaluating the results against pre-specified requirements. In short, verification means: Are we building the system right ?

(2) ERROR DETECTION : Testing should intentionally attempt to make things go wrong to determine if things happen when they should not or things don’t happen when they should.

(3) VALIDATION : looks at the system correctness – i.e. the process of checking that what has been specified is what the user actually wanted. Validation means: Are we building the right system ?

Test CasesTest Cases Expected ResultsExpected Results

1.If Administrator enters correct 1.If Administrator enters correct username and invalid password username and invalid password or vice versaor vice versa

Msg: ”Invalid Username or Msg: ”Invalid Username or Password”Password”

2. If the password field is blank2. If the password field is blank Msg: ”Please Enter Password”Msg: ”Please Enter Password”

3. If the administrator adds, 3. If the administrator adds, update any recordupdate any record

Changes made must be Changes made must be correspondingly reflect in the correspondingly reflect in the databasedatabase

4. If input given to the field say 4. If input given to the field say Name is numericName is numeric

Msg: ”Enter Only Alphabets”Msg: ”Enter Only Alphabets”

5. If In case user wants to delete5. If In case user wants to delete Msg: ”Are you sure you want to Msg: ”Are you sure you want to delete”delete”

Test Cases

CONCLUSION

The objective of this project was to satisfy user’s requirements, successful implementation of the system, design a user-friendly and easy to operate the system.

The proposed requirements of the system have been fulfilled.

Speed and accuracy are satisfactory.

The project was very useful in case of acquiring practical knowledge

REFERENCES

1. [PRE01] Pressman, R.S., “Software Engineering”, A Practitioner’s Approach, Tata McGraw Hill, 6th Edition,2005.

3 www.google.com

2 An Integrated Approach to Software Engineering - Pankaj Jalote..

Hospital Management System

Documents

Transcript of Hospital Management System