HOSPITAL

MANAGEMENT

SYSTEM

CREATED BY-

NEELAM PRIYA AND UNNATI MATAI

INDEX

• PROBLEM STATEMENT

• USE-CASE MODEL

• DATA FLOW DIAGRAM

• ACTIVITY DIAGRAM

• SEQUENCE DIAGRAM

• COLLABORATION DIAGRAM

• CLASS DIAGRAM

• COMPONENT DIAGRAM

• DEPLOYMENT DIAGRAM

SOFTWARE REQUIREMENTS

FRONT-END : NETBEANS 8.0.1

BACK-END : MYSQL DATABASE

Presentation : MS POWERPOINT-2013

PROBLEM STATEMENT

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

SCOPEThe purpose of the project is to provide a self-test to the patient, ifhospitals are not available in near places. Patient can get appropriatesuggestions to his problem. This application generates a reportregarding patient’s health condition. That report may contain patientdisease name, his symptoms intensity level and the suggestionprovided by system.

The goal of any system development is to develop and implement thesystem cost effectively; user-friendly. This suggestion may be in the twoforms. First suggestion may be an appropriate medicine based onsymptom Intensity level; second suggestion may be a specialized doctormeeting that means his disease may be in a critical state. The first stepin system development life cycle is the identification of need of changeto improve or enhance an existing system. Many problems wereidentified during the initial study of the existing system.

USE CASE DIAGRAM

DATA FLOW DIAGRAM

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

LEVEL-0 DATA FLOW DIAGRAM

LEVEL-1 DATA FLOW DIAGRAM

LEVEL-2 DATA FLOW DIAGRAM

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.

ACTIVITY DIAGRAM FOR UPDATING DISEASES

An “Interaction diagram" that models a single scenario executing

in the system.

-perhaps 2nd most used UML diagram (behind class diagram)

SEQUENCE DIAGRAM

SEQUENCE DIAGRAM FOR SELF-DIAGNOSIS

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.

COLLABORATION DIAGRAM TO SPECIFY SYMPTOMS

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.

CLASS DIAGRAM

COMPONENT DIAGRAM

DEPLOYMENT DIAGRAM

FINAL DEMONSTRATION...