1. Software
Project
Management
1

2. 1. Introduction of group with project title
2. Primary investigation
2.1 need of project - - - - - - - - - - - - - - - - - - - - - - - 4
2.2 project scope and disadvantages - - - - - - - - - - 6
2.3 Profile of organization chart - - - - - - - - - - - - - 8
2.4 exiting system - - - - - - - - - - - - - - - - - - - - - - - - 10
2.5 advantages and disadvantages of exiting - - - - 12
System
2.6 organization chart - - - - - - - - - - - - - - - - - - - - - 13
2.7 Function decomposition chart - - - - - - - - - - - - 14
2.8 Proposed system - - - - - - - - - - - - - - - - - - - - - - 15
2.9 Feasibility study - - - - - - - - - - - - - - - - - - - - - - - 17
3. Building a project plane for scratch
3.1 introduction(definition)
3.2 Planning activity.
3.3 Designing calendar
4. System requirement specification - - - - - - - - - - - - - - - - - - 18
5. Data flow diagram of system - - - - - - - - - - - - - - - - - - - - - - 21
5.1 context level - - - - - - - - - - - - - - - - - - - - - - - - - - 21
5.2 1st level - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 23
5.3 2nd level - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 24
6. Entity relationship diagram - - - - - - - - - - - - - - - - - - - - - - - 26
2

3. 7. Data dictionary - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 27
8. Cost estimation, schedule and assigning resources
(Phase-2)
Group introduction :-
Group no :- 16
No Roll no Name
1 123 Parmar Bhavesh
2 105 Dodha Ketan
3 168 Pathan Shahnavaj
4 162 Prajapati Yogesh
3

4. Need of system :-
In hospital management patient management and its data is
more important. In this data arrange and store in proper way for long time.
Its some needs are as under.
 This program is developed to make easy the routine work.
 Easy to find data or information.
 Save lot of manpower and time.
 System covers large number of people and try minimize data
redundancy.
 In this system process of summary report is main part, using the
computerized system.
4

5.  This process is become simple and small; you can immediately
getting the report for the query.
 This system provides interaction user friendliness and also less
paper work.
Project scope and limitation :-
Project scope :-
 Patient management of general O.P.D. in the general hospital,
Gandhinagar.
 In this you also stored patient’s report and you study on the
specific disease.
 We manage pharmacy department, general O.P.D. , and
patient management system. Combine we will that three
department through the server connection that use for without
paperwork we done every process easily.
Project limitation :-
 Data store 25 years only.
 In this system patient id is more impotent and without it can’t
manage this system.
5

6. Note : patient data store for 25 years only.
Profile :-
Name : General hospital management,
Gandhinagar.
Address : sector – 12,
Opp. Pathikashram,
Pin-382016
Phone number : 079-232221931-32
2321913
Fax : 079-23222733
Email id : cs-gnr@gujarat.gov.in
Slogan : we accept high risk obstetric patient at
this hospital.
6

7. Mission :-
We shall enhance the patient quality life through providing
specialized medical treatment at free and affordable rates to the poor
and the needy and preventive healthcare.
Vision :-
To be the part of network of finest public healthcare institution
in the state of Gujarat, providing quality medical care services with
the state of art technology with easy accessibility, affordability and
equity to the people of Gujarat and beyond.
7

8. Exiting system :-
 The existing system is computerized system. It is not fully
computerized system.
 Most allies are done manually in Hospital Management system.
 All reports are done manually.
 Information about patient is recorded computerized but in that
many problems.
 Data redundancy is more and data and information are not
arranges in proper structure and way.
 All information is difficult to remember to doctor about patients.
 Manually reports or other document are not save long time.
 Work load is more.
 Report and data searching problems.
8

9.  In use more manpower and time.
Advantages of exiting system :-
 Error will be less.
 It is comfortable with patient.
Disadvantages of exiting system :-
 Work load is more.
 Waste time, money, manpower.
 Many problems in find proper data or information.
 In many chances lost information and reports.
9

10. Organization chart :-
10

11. Government of
Gujarat
Health and family welfare
department
Medical department
Health department Education department
C.H.C( community P.H.C (primary
health center) helth center)
Civil hospital
Medical college
Civil surgeon Resident medical officer (R.M.O)
Doctors
Nurse & employees Other staff
Function decomposition chart :-
11

12. CIVIL General hospital
Labotarry Clinical risk Emergency Infection control Equipments
Pharmacy O.P.D. management
management management preparedness management management
management
General O.P.D.
Patient registration
Patient management Pharmacy management
management
Proposed system :-
12

13. In this hospital computerized system running. Therefore we give them
proposal to convert it into fully computerized system that use for searching
data. In this we manage three department Registration systems, General
O.P.D. , and Pharmacy department we combine that three department
through the server. Without paper work we have done every process. So it
is very speedily and easy to reporting.
In this proposed system we connecting receptionist and doctor with
help of server.
 Patients first go for case registration and registration his info and
take one token.
 Then patient take doctor treatment and prescription.
 Patient will take all prescription.
 That after patient takes some medicine and all reports.
Feasibility study :-
13

14. There are four types of feasibility .operational feasibility, technical
feasibility, economical feasibility, schedule feasibility. New system
feasibility given below:
1. operational feasibility :-
The new system aim is save manpower with minimize data
redundancy and data arrange in proper way. Proposed system is
useful to searching data so, it is user friendly. System will not require
any training. If you need any help related system then we will
provided guidance and help only. The system will be comfortable for
both user and patients.
2. technical feasibility :-
Patient data and information is important in any hospital.
Hospital is easy to purchase entire system requirements. The system
will be operationally comfortable for the company.
3. economical feasibility :-
The company is capable to requirement of proposed system. It‘s
advantages is more and helpful in improve profit. The system will be
economical feasible for the company.
4. schedule feasibility :-
14

15. Time is the most effective factor while making a project or system.
The project should be finished within the assigned time.
15

16. System requirement Specification :-
Hardware :-
 Developers requirement :-
 RAM 1 GB,
 Processor Intel i3 core,
 Hard disk 160 GB,
 User requirement :-
 Processor Intel i7 core,
 Hard disk 320 GB,
 RAM 3 GB,
Software :-
 Operating system : windows XP professional version 2002,
Service pack 2
 Ms Visualstudio.NET
 Data base : Microsoft ACCESS XP
Data flow chart :-
16

17. Patient
information
Registration
management
information
Doctor
Medicine & prescriptions
Patient data
O.P.D. management
Prescription
Pharmacy management
Data flow Diagram :-
17

18.  Context level DFD
Context level DFD for hospital management
Information Hospital Register case
Patient Medicines and
management Doctor
suggestion system Prescriptions
18

19.  0 LEVELDFD
0 level DFD for hospital management system
Information 1
payment Patient Information
patient Doctor
registration
system
Bill/token
Patient info
2
Patient report Prescription
Prescriptions
Patient info
Medicines, report
suggestion
3
Pharmacy
management
system
19

20.  1ST LEVEL DFD
1st level DFD for patient registrations system
Previous info
1.1
Information Patient Information
Patient Patient
information information
system
information
Bill token 1.1
Bill id information Bill
prepare information
Billcase
Billing information
information information
1.3
Patient details
information
Searching
system
20

21.  2ND LEVEL DFD
2nd level DFD for prepare prescriptions
Prescriptions 2.1 Diagnosis
Doctor Diagnosis
diagnosis Prescriptions information
Prescriptions
Study information
2.2 Diagnosis
Doctor study information
diagnosis details
Prescriptions
2.3 Doctor details Doctor
Doctor detail
details
and work
21

22.  3RD LEVEL DFD
3rd level DFD for pharmacy management system
Patient’s diagnosis
Find out pharmacy detail
Patient 3.1
Pharmacy Medicines
management details
system
Patient’s diagnosis
Give details about stocks
3.1 Pharmacy
diagnosis manage
medicine system department
22

23. ENTITY RELATIONSHIP DAIGRAM
Billing process Patient data
Previous history of patients if they will be come
information Patient data registration again
Bill
token
(case)
Information data Patient data
patient Say about diagnosis Check up All info Doctor
All prescription ,medicine, data Prescriptions & medicine
Medicine medicine
Pharmacy medicine Prescription
department
Store all info
Patient history
Page 1
23

24. Data dictionary :-
A data dictionary is a central storehouse of information of
about the system’s data. An analyst uses data dictionary to collect,
document and organize specific fact about system, including the
contents of data flow, data stores, entities and process.
1) Patient case :-
Filed name Type Size Constraint Description
P_id Number 10 Primary key Patient key
Case_no Number 10 Not null Case no
Date Date and - Not null Date
time
P_name Text Not null Patient name
P_add Text 50 Not null Patient address
P_age Number 2 Not null Patient age
Gender Yesno - Not null Patient sex
City Text 20 Not null Patient city
Phone Number 10 Allow null Patient phone no
Mobile Number 10 Allow null Patient mobile no
2) Patient history :-
Filed name Type Size Constraint Description
P_id number 10 Foreign key Patient key
Diseases Text 100 Not null Patient diseases
Report Text 256 Not null Reports
Prescription Text 256 Not null Prescription
24

25. 3) Doctor details :-
Filed name Type size Constraint Description
D_ id number 10 Primary key Doctor id no
D_name Text 20 Not null Doctor name
Visit_date Date & - Not null Doctor visit date
time
Degree Text 15 Not null Degree
D_address Text 56 Not null Address
D_phone number 10 Not null Doctor contact no
4) Pharmacy :-
Filed name Type size Constraint Description
M_name Text 20 Not null Medicine name
M_code number 15 Pk Medicine code
E_date date Not null Expire date
M_stock Number 20 Not null Stock
M_price Number 10 Not null Price
5) Bill :-
Filed name Type size Constraint Description
B_no Number 10 Pk Bill no
Total Number 10 Not null Cost(bill)
P_name Text 20 Not null Patient name
P_id Number 10 Fk Patient id no
25

26. 6) Diagnosis :-
Filed name Type size Constraint Description
D_name Text 20 Not null Disease name
D_study Text 256 About that
information
D_work Text 256 Use for doctor
26

27. Activity table :-
Acti Description Prece Durat Resources Opti Most Pessi Rema
vity dence ion mistic likely mistic rks
A Select project -
B Identify project - 1 week Project 1 week 1 week 1week
scope manager
C System planning B 1 week Analyst, pro. 1 week 1 week 1 week
Leader
D System analysis C 3 week Analyst, 3 week 3 week 4 week
magazine
E information 4 Analyst
gathering
F User requirements E 2 Analyst
G Problem F 3 Analyst
identification
H Proposed system C, G 4 Analyst, project
manager
I Feasibility study H 5 Analyst
J Data process D 2 week Data base 1 week 1 week 1week
modeling designer
K Data flow Analysis
L Relationship K Data base
diagram designer
M Data dictionary L Analysis,
Data base
designer
N Requirements 2 week Analyst, h/w, 2 week 2 week 2 week
specification s/w
O select hardware & N Printer, modem,
software Computer,
Server card
P Recruitment staff 3 week HR, 2 week 2 week 3 week
Q System design 4 week Designer, 4 week 4 week 5 week
programmer
R Module design Design,
programmer
S Program design R Designer
T Coding Q 5 week Programmer 3 week 3 week 4 week
U Module coding Programmer
V Sub module U Programmer
coding
27

28. W Testing T 1 week Programmer, 1 week 1 week 1 week
X Implementation W 1 week Computer, 1 week 1 week 1 week
modem,
preprogram,
project
manager
Y User training X, P 1 week Project 1 week 1 week 1 week
manager,
programmer
28

29. 29

30. 30