LAB FILE

SOFTWARE ENGINEERING LAB BCA

504
PROJECT ON
HOSPITAL MANAGEMENT SYSTEM

SUBMITTED TO:
Mr. Bhavya Alankar
Mr. Gaurav
SUBMITTED BY:
Anuj kumar sumayya Rasheed and
shivani aggarwal
 INDEX
1-Project Profile
2-Existing System
3-Need For New System
4-Hardware And Software Requirement
5- Hardware Requirement
6- System Features
7- Functional Requirement
8- Non Functional Requirement
9- User Requirement
10- Feasibility Study Report
11- Software Requirement Specification (Srs)
12- Model Implementation
13- Reason For Choosing Water Fall Model
14- Process Description
15- Process Algorithm
16- Post Implimenation Review
17- Dfd
18- Entity Relationship Digram
19- Project Features
20- User Classes And Characteristics
21- Future Enhancement
22- Screen Shots
 ACKNOWLEDGEMENT

I would like to extend our heartiest thanks with a

deep sense of
gratitude and respect to all those who provides me
immense help and guidance during my training
period.
I would like to thank my Project Leader Mr. Gaurav
and Mr Bhavya Alankar for providing a vision
about the system. I have been greatly benefited
from their regular critical reviews and inspiration
throughout my work.
I would like to express my sincere thanks to our
Head of Department who gave me an opportunity
to undertake such a great challenging and
innovative work. I am grateful to them for their
guidance, encouragement, understanding and
insightful support in the development process
Last but not the least I would like to mention here
that I am greatly indebted to each and everybody
who has been associated with my project at any
stage but whose name does not find a place in this
acknowledgement.
 Project Profile
Project title :- Hospital Management System
Objective :- To Maintain Details Of Patient ,store
and display.
Front-and Tool :- C++
Application-Type :- Windows Application
OS Platform :- Windows 8
Internal guide :- Mr. Gaurav Kumar
Developed By :- Anuj, Shivani And Sumayya.

Existing System
The existing system is manual.
The manual system is more error prone.
It is very costly.
Immediate response to the queries is difficult
and time
consuming.
Difficult to maintain record and more paper
work is
required.
Report generation is difficult.
The system is not secured.
More men power are needed .
 Need For New System
To provide computerized data storage facility.
We can search easily any record.
The new system requires less time for
completion of any
work.
All the records of patients are updated in the
new
system.
The system is user friendly and any one
having computer
knowledge can handle it easily.
Suitability for computerized data entry.
Maintaining
stock, Patients information, Store information.
New system is provided security against
unauthorized us
 Hardware and Software
Requirement
HARDWARE (Recommended)
Processor :- Pentium IV & Above
Hard disk Capacity :- 2 GB
RAM :- 512 MB
SOFTWARE(Recommended)
Platform: C++
Programming language: C++
Operating System: Windows 8
Project Type: Desktop Application

Hardware Requirement
Processor : Intel Pentium 4
RAM : 512 MB RAM
Monitor : 1 5Colour Monitor
Processor Speed : 1.7 GHZ
 Hard disk : 1.44 MB FDD
CD Drive : 52- X CD ROM
Keyboard : Mercury 110 Keys
Mouse : Logitech Mouse

System Features
Proposed Database is intended to store,
retrieve, update, and manipulate information
related to Patients which include
Personal Details.
Searching by blood group.
Searching by city.
Storing the details of patients.
Displaying the deatails.
Updating the details.
Deleting .

Functional Requirement
The software must allow input of patients data
from
Administrator & secured access at , and from
the data
streaming real-time monitoring equipment.
 The project must request username and
password for access to data, only after
authentication will allow access to the system.
The project must require high levels of error
correction and
input validation.
The project must allow browsing by the
Director & Staff of
Hospital To Access And update information of
patients .
The project must identify the Patients & Staff .
The software to be developed must operate
without interruption twenty-four hours a day.

Non Functional Requirement

The software interface must follow design
conventions which allow for familiar location of
menus, etc.
Input errors will be returned in red with
appropriate message box.
More than three attempts at login and failure
will produce a red flag to system administrator.
Response Time Should be minimum.
No of daily system downs Should not more
than 10.
System should Automatically Update After
Every Transaction
 User Requirement
The User Of system are Staff and Managers of
the store.
The members share assumed to have basic
knowledge of
computer & internet browsing While
administrator of system should have more
knowledge so he/she can resolve small
problems and perform informations.
The user manual ,installation guide and other
related material should be sufficient to educate
the user how to use and maintain the system.
 Feasibility Study Report
In the Economic Feasibility study of the system it
was noticed
that the existing manual system of Maintaining
patientss and records of details, list of medical
details, report and supplier wise medicine reports
consumes a lot of time and
money. The manual process involved a set a things
like,
Maintaining suppliers and records of patients, list
of personal details, stock of medicine, daily
purchase report and supplier wise reports and
creation of different reports paper by hand in
writing and then get it typed or printed computer
printer.
After getting the master copy of the all these, n
number of photo copies of the same should be
generated for each supplier and medicine and
some extra copies. And those copies are to
maintain for long time.
Now if we analyze the cost involved in the above
described manual process of medical stock
management system, we find that we have the
following expenditures for medical stock
management system.
Cost of registers
Cost of typing reports
Cost of photo copying / printing different
reports.
Cost in terms of the precious time lost in the
process
Maintaining suppliers and records of
medicines, list of supplier, stock of
medicine, daily purchese report and supplier
wise medicine reports.
If we compare the cost of the manual system of
medical stock
management with that of the automated medical
stock management, we can clearly make out that
in the cost benefit analysis there no question of
costs outweighing the benefits. The proposed
system is economically feasible from both
Developers point of view and Users point of view.
So, in the end of the Economic Feasibility Study, I
came to the
Conclusion that automated managing of medical
stock management is much cheaper and beneficial
in all respects.

Software Requirement
 Specification
(SRS)
Purpose
This document outlines the software
requirements for the
Medical store management system. It describes
the functional and non-functional
requirements, modeling requirements,diagrams
and user profiles of the proposed system.
The Medical stock Management System
enables to maintain computerized Record Of
Supplier and Medicine. Its also perform quick
search for their products, Manages Stock And
Keep record of Supplier and Medicine. This SRS
provides detailed information on the internal
and external view of the system as well as
interfaces required by Medical stock
management System.
 MODEL IMPLEMENTATION
Water fall model is used to develop this project

Reason For Choosing Water Fall

Model
This is small project and requirements are well
understood.
This model is simple and easy to understand
and use.
Waterfall model is simple to implement and
also the amount of resources required for it are
minimal.
It is easy to manage due to the rigidity of the
model-each phase has specific deliverables
and a review process.
In this model, output is generated after each
stage (as seen
before), therefore it has high visibility. The
client and project manager gets a feel that
there is considerable progress. Here it is
important to note that in any project
psychological factors also play an important
role.In this model phases are processed and
completed one at a
time. Phases do not overlap.
This Project Is Conversion From Manual To
Automatic
 Process Description
Login Process :-This process checks the
authentication and
able to access the application
Input process :-User gives the information about
Patients details.

Display Process:- It will display the details of

patients.
Process Algorithm
Step 1:- Start
Step 2:- Enter current date.
Step 3:- Choose from the options.
Step 4:- Enter details of new patient.
Step 5:- Or update the existing.
Else search by city or blood group.
Step 6:- Delete entry .
Step7:- Recycle bin.
Step 8:- About.
Step 9:- Exit.
 POST IMPLIMENATION REVIEW
After the system is implemented and
Conversion is
completed, a review of the personal is good.
They are
Satisfied with this Software facility.
Less man power, provide information timely.
Save data entry and duplication work.
Timing and also resources allocation for data
entry, it
fills the gap between data entry.
Provide the lock system and password
protection so it is
reliable.
DFD
ENTITY RELATIONSHIP DIGRAM
 Project
features
There Will be
one user
Accessing
System.
Manager : Who will act As Administrator
The Features for manager are
Add ,delete update any patients details
Manage information i-e(input, update,
search,delete )

User Classes and Characteristics

User Of project include manager and staff
Staff Which act as administrator and controlling
overall system
Operating environment
 This project will be operating in windows
environment.
The only requirement For using this project is
having machine.
Design and implementation constraints
This project is developed using java. on the
back hand for
database we are using MySql . The product is
Accomplished With the login facility for user.

User Documentation
This project will include a user manual. The user
manual include
Complete overview of the product, Configuration of
the Tool used technical details, backup procedures
and Contact

FUTURE ENHANCEMENT

There is one segment named lab unit needed

computer
system to improve work .In this system, we
tried to make a simple application for user. We
can change our system day by day as per the
user requirements will be changed. In future
we want to implement below point in our
system.
We convert our system into website.

SCREENSHOTS
LOGIN
PAG