Scribd
Upload
2K views46 pages

Hospital Management System

This document provides an overview of a hospital management system project. It includes sections on the project description, pre-analysis of client requirements, system requirements, modules, data flow diagrams, use case diagrams, class diagrams, and test procedures. The project aims to develop a standalone application for hospital management with features like patient registration, doctor details, bill payment, and an easy to use interface.

Uploaded by

rahul
Copyright
© Attribution Non-Commercial (BY-NC)
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PPT, PDF, TXT or read online on Scribd
2K views46 pages

Hospital Management System

This document provides an overview of a hospital management system project. It includes sections on the project description, pre-analysis of client requirements, system requirements, modules, data flow diagrams, use case diagrams, class diagrams, and test procedures. The project aims to develop a standalone application for hospital management with features like patient registration, doctor details, bill payment, and an easy to use interface.

Uploaded by

rahul
Copyright
© Attribution Non-Commercial (BY-NC)
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PPT, PDF, TXT or read online on Scribd
You are on page 1/ 46

Hospital

Management
System
Project Guide:-
Prof. Manisha Jadhav.

Project Developed By:-


Vinod Jadhav
MCA V Roll No. 1205
PROJECT
DESCRIPTION
•Type Of Project: Stand-Alone

Application.
•Duration: 30 days.
System Life cycle Development
System Project progresses
Investigation through the first 3
phases of “SDLC”

Requirement
Analysis

Design

Coding

Testing

Implementation

Maintenanace
PRE-ANALYSIS
Client Requirement
• Good user friendly graphical
interface
• Security should be provided
• Easy retrieve the Database
• Easy payment options
• Fast and easy delivery of products
Requirement Determination
Techniques
• Structured Analysis.
• Technical Feasibility.
• Economical Feasibility.
• 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
OPERATING ENVIRONMENT
Client Side
•HARDWARE:
Pentium III or Higher,10GB HDD,128RAM.

•SOFTWARE:
Visual Studio 2005, SQL Server
Developer’s Side
•Hardware:
Pentium IV,256RAM,20GB HDD.

•Software:
Visual Studio 2005,
Windows Server 2003, SQL Server
Types Of Users

•Administrator Level.
Scope
•The System gives the details of patient.
•It shows the daily check up of all patient and
gives details about the doctors visiting timing
etc.
•This shows all details of doctors that are
available.
•This shows all stock of medicen.
Modules

•Registration and authentication


module for new Patient.
•Doctors details
• Bill Payment
SYSTEM REQUIREMENTS
Project Schedule
Activity Act. Name Predecessor No. of days

A Preliminary investigation Nil 6


B Requirement analysis Nil 9
C Designing A,B 15
Future Schedule
D Coding C 11
E Testing D 5
F Implementation E 3
G Maintenance F 2

Total Days 45
Risk Management

•Project Risk.

•Technical Risk.

•Non Technical Risk.


Feasibility Study

•Operational Feasibility.

•Technical Feasibility.

•Economical Feasibility.
Data Flow Diagram
Entity Relationship
Diagram
Use Case Diagram
Class Diagram
Object Diagram
Sequence Diagram
Activity Diagram
Table Design
Patient Table

Fields Data type Size Constraints

pat_id Char 10 Primary Key

pat_name Char 30 Not Null

Address VarChar 100 Not Null

PinCode Numeric 10 Not Null

Mob_no Numeric 12 Not Null

Date Date - Not Null


Inquiry Table

Fields Datatype Size Constraits

Enq_id Char 10 Primary Key

pat_id Char 10 Foreign key


TreatmentTable

Fields Datatype Size Constraints

tret_id Char 10 Primary Key

Pat_id Char 30 Foreign key

doc_id Char 30 Foreign key


Doctor Table

Fields Data type Size Constraints

Doc_id Char 10 Primary Key

Doc_name Char 30 Not Null

Address VarChar 100 Not Null

PinCode Numeric 10 Not Null

Mob_no Numeric 12 Not Null

J_Date Date - Not Null


Payment Table

Fields Data type Size Constraints

P_id Char 10 Primary Key

pat_id Char 30 Foreign key

Q_amt Numeric 10 Not Null

Disc_amt Numeric 10 Not Null

Final_amt Numeric 10 Not Null


Receipt Table

Fields Data type Size Constraints

Rec_id Char 10 Primary Key

P_id char 10 foreign

Pur_amt Numeric 10 Not Null


User Table

Fields Data type Size Constraints

Us_id Char 10 Primary Key

Pass char 10 Not Null

Con_pass char 10 Not Null


Department Table

Fields Data type Size Constraints

Dep_id Char 10 Primary Key

Dep_name char 20 Not Null

doc_id Char 10 Foreign Key


TEST PROCEDURES

 Testing :

Testing software is operating the software under controlled conditions to :

1. Verify that it behaves “as specified” ,


2. To detect errors , and
3. 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 Cases

Test Cases Expected Results

1.If Administrator enters correct Msg: ”Invalid Username or


username and invalid password Password”
or vice versa
2. If the password field is blank Msg: ”Please Enter Password”

3. If the administrator adds, Changes made must be


update any record correspondingly reflect in the
database
4. If input given to the field say Msg: ”Enter Only Alphabets”
Name is numeric
5. If In case user wants to delete Msg: ”Are you sure you want to
delete”
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.

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

3 www.google.com

You might also like