Hospital management system created as a java NetBeans project in which Java, MySql are used. The slides comprise of all the UML diagrams.

1. HOSPITAL
MANAGEMENT
SYSTEM
CREATED BY-
NEELAM PRIYA AND UNNATI MATAI

2. INDEX
• PROBLEM STATEMENT
• USE-CASE MODEL
• DATA FLOW DIAGRAM
• ACTIVITY DIAGRAM
• SEQUENCE DIAGRAM
• COLLABORATION DIAGRAM
• CLASS DIAGRAM
• COMPONENT DIAGRAM
• DEPLOYMENT DIAGRAM

3. SOFTWARE REQUIREMENTS
FRONT-END : NETBEANS 8.0.1
BACK-END : MYSQL DATABASE
Presentation : MS POWERPOINT-2013

4. PROBLEM STATEMENT
Our HOSPITAL MANAGEMENT SYSTEM is aimed to the Self-diagnosis
with hospital management system is to provide a self-test to the
patient, if hospitals are not available in near places. This system
provides an additional facility, that is patient can interact with an
appropriate doctor through online chatting or Discussion forum. This
system includes registration of patients, storing their details into the
system, and also computerized billing in the pharmacy, and labs.

5. SCOPE
The purpose of the project is to provide a self-test to the patient, if
hospitals are not available in near places. Patient can get appropriate
suggestions to his problem. This application generates a report
regarding patient’s health condition. That report may contain patient
disease name, his symptoms intensity level and the suggestion
provided by system.
The goal of any system development is to develop and implement the
system cost effectively; user-friendly. This suggestion may be in the two
forms. First suggestion may be an appropriate medicine based on
symptom Intensity level; second suggestion may be a specialized doctor
meeting that means his disease may be in a critical state. The first step
in system development life cycle is the identification of need of change
to improve or enhance an existing system. Many problems were
identified during the initial study of the existing system.

6. USE CASE DIAGRAM

7. DATA FLOW DIAGRAM
A diagram to show how data is captured, processed , stored
and distributed within a system.

8. LEVEL-0 DATA FLOW DIAGRAM

9. LEVEL-1 DATA FLOW DIAGRAM

10. LEVEL-2 DATA FLOW DIAGRAM

11. ACTIVITY DIAGRAM
• Activity diagram are the flowcharts, showing the flow of control
from activity to activity.
• Activity diagrams represent the business and operational work
flows of a system.

12. ACTIVITY DIAGRAM FOR
UPDATING DISEASES

13. An “Interaction diagram" that models a single scenario executing
in the system.
-perhaps 2nd most used UML diagram (behind class diagram)
SEQUENCE DIAGRAM

14. SEQUENCE DIAGRAM FOR
SELF-DIAGNOSIS

15. COLLABORATION DIAGRAM
• Is an interaction diagram that emphasizes on structural
organization of objects that send and receive messages.
• Graphically, is a collection of vertices and arcs.
• Describes a specific scenario.
• Shows association among objects along with interaction.
• Same as sequence, but shown in a different way.

16. COLLABORATION DIAGRAM TO
SPECIFY SYMPTOMS

17. CLASS DIAGRAM
• A class diagram describes the types of objects in the system
and the various kinds of static relationships that exist among
them.
• A graphical representation of a static view on declarative static
elements.
• A central modelling technique that runs through nearly all
object-oriented methods.
• The richest notation in UML.

18. CLASS DIAGRAM

19. COMPONENT DIAGRAM

20. DEPLOYMENT DIAGRAM

21. FINAL DEMONSTRATION...