CASESTUDY

Project Work Guidance
(For those who want to learn)
A Case Study Approach

(SY/TY BSc-Computer Science and TYBCA)
(For private circulation only)
Dr. Ravindrakumar D. Patil

Principal
Commerce, Management & Computer Science (C.M.C.S.) College
Udoji Maratha Boarding Campus, Gangapur Road, Nashik-422013
Page 2 of 61 -- Project Work Guidance Case Study
CONTENTS
Sr. Title Page

1 Idea Behind 03
2 Software Development Life Cycle(SDLC) 04
3 Software System Testing 07
4 Important Notes 09
5 Sample Case Studies
Petrol Pump Management System 10
Hospital Management System 32
M.V.P. Samaj’s, C.M.C.S. College, Nashik-13

Idea Behind
Students of Computer Applications and Computer Science (even other science students)
as well have to complete a course called Project Work during their graduation studies. I
do not know how many students have really understood, academic purpose and idea
behind this course. Over years, I have observed that students take up some work done by
earlier batch students and submit the same as their project work. Result is poor
performance in examination. But beyond that (which is really a concern) they have lost a
golden opportunity to search an independent topic, fight for understanding it, go through
all the steps of project work development and get an experience of working on a software
system development which is really important criterion to acquire a job. How can you
find a place (called job) in any industry, banks, company, office etc. without work
experience when everything now days is competitive.
Fault may be with anybody, present academic system, teachers or students. This is a
humble attempt to find our own solution. Success may, may-not follow. Who cares!
What a student should do?

For a project work, it is expected that students take up a real life day to day working
problem from an industry, banks, company, and office. For this they need to visit an
industry, banks, company, and office. Try understand the working by observing, talking
to people over there. Write down the whole working in your own words. Students of
Computer Applications as well as Computer Science are expected to follow Software
Development Life Cycle (SDLC) during their project work. So read a detail note on Software
Development Life Cycle (SDLC) given at the beginning. Also read a detail note on
Software System Testing. Every software system is to be tested before it is actually put to
use.
In a project work, you are supposed to develop a software system for a real life day to
day working problem from an industry, banks, company, office and put it to work.
Modus Operandi:
Two sample case studies are given in this booklet. A teacher will explain in detail the
sample case study in a class room. At the end of explanation, an independent (but similar)
case study will be given to you as home assignment. Every student should carry out
all the steps of software system development. To help you out, index is provided at the
beginning of each sample case study. Get your home assignment checked from the
concerned teacher. So two sample case studies will be explained in the class and each
student will complete two more home assignments.
Now you are ready to do your independent project work. Go and search for your own
problem and complete your software system.
Remember we have not included chapters 6 to 10 (see Index for details) in sample case
studies. But you will have to include all these in your project dissertation. So best of
luck and make your journey of learning through project work most enjoyable and
rewarding. We all thank Prof. Rajesh Nikam for his help project guide development.
Dr. Ravindrakumar D. Patil, Principal

Software Development Life Cycle (SDLC)

The Software Development Life Cycle (SDLC) is a well defined process by which a
software system is designed, developed and implemented.
It consists of following steps:

1. system analysis,
2. requirement analysis,
3. project management, and
.
This includes following phases:

1. Preliminary investigation:
a) Preliminary investigation starts on a request.
b) Main purpose of this phase is to understand the present status of existing system &
identify real problems in it.
This stage performed in 3 parts.
i. Request clarification:
Any request from employee and user department in any organization is not
clearly stated. Before any investigation can be considered, the project request
must be examined to determine the actual requirement. Hence request should
be clearly specified by the end user, which is called request clarrification.
ii. Feasibility study:
The main purpose of feasibility study is to determine whether the software
system requested is feasible or not.
There are three aspects of feasibility study are:
I. Technical Feasibility:
 This feasibility determines whether it is possible to develop the
project with available equipment, available software
technology and the manpower.
II. Economical Feasibility:
 This feasibility determines cost and benefits of the project.
 Check whether the benefits are achieved as compared
III. Operational Feasibility:
 In this case operational implementation cost is considered.
 During implementation, the training programs are arranged for
the users.
 The cost of the training program as well as the space requirement
for the implementation of the system and the other assets are
considered in it.
iii. Request approval:

If project is feasible then it is approved and project cost, priority is
decided.

2. System Analysis:
a) This is nothing but determination of the system requirements.
b) System analysis is a detailed understanding of all important facets of the
business process under investigation.
c) In system analysis, review of the existing procedures, information flow,
decision making and individual information needs at various levels in
different functional areas are done.
d) The analyst must try to get the answers to following:
i. What is an actual process?
ii. How it works?
iii. How many times any transaction has to be performed?
iv. What is the volume of data as well as transaction?
v. What are problems that arise in process?
vi. What are the solutions of these problem?
vii. Which are the number of reasons to arise the problems?
e) To get the answers the analyst must visit or contact number of persons who
are associated with the system or involved in the process.
f) System analyst must collect sample data & number of forms/ reports,
methods which are involved in the process.
3. System Design:
a) This stage defines the ways a software system will meet the requirements which
are identified during analysis of the current manual system.
b) This phase starts by identifying the reports and other output formats, documents
that system will produce.
c) Screen designing, report designing, output designing and form designing are
different parts of this phase.
d) The system design specification contains entity relationship diagram (ERD), data
flow diagram (DFD) and data dictionary.
e) At the time of designing database system, concept of normalization is used.
4. System Development/Coding:
a) In this phase detailed design is used to actually construct and build the software
system.
b) In this phase, program code with a proper programming language is written.
c) Preparation of documentation for each programs is done.
5. System Testing:
a) Basic aim of testing is to find the errors.
b) During this phase the system is used experimentally to ensure that software
system does not fail, but will run according to the specifications and in a way that
user has demands/wants.
c) In this phase, quality of the code is also checked and some of the standards are
applied.
d) It is checked to see if a software system produces correct and desired results.
6. System Implementation:
a) Implementation is a process in which you have to train the user first,
install the new application and run the actual software system with
the manual system.

b) Implementation also consists of hardware testing and software installation.
7. System Maintenance:
a) System should be maintained properly i.e. maintenance of software, hardware,
data as well as other technical equipment.
b) There is need to have a person who looks after the software system and maintain it
even during operation and production.
c) System maintenance may be required because of any of the following
reasons:
i.Minor changes in processing logic
ii.Errors detection during the processing
iii.Revision of the data input formats.
iv. Revision of report formats.

Software System Testing

Software testing is a critical element of software quality assurance and represents the
ultimate review of specifications, design and code generation. Basic aim of testing is to
find the errors. During this phase the software system is used experimentally to ensure
that software does not fail, but will run according to the specifications and in the way that
user requests. Sample test data is inputted for processing and results are tested. User
suggestions for modification in the software system are considered for changes. Software
system testing should be done by another person not from the team of developers.
Basic activities involved in the testing are:

 Checking individual program and its logic.
 Checking interface between various programs.
 Designing test cases for interface checking.
 Checking quality of the code and applying some standards.
 Checking whether software system produces correct and desired results.
Following software techniques are used for software testing:

 White box testing
 Black box testing
 Validation testing
 System testing
1. White Box Testing:

White box testing is also called as glass box testing. It is related with the
structure /internal logic of the program. During white box testing activity,
every statement of programs is executed at least once. All the independent
paths are also executed. Every logical decision is executed to check both
true and false conditions. All loops are executed at their boundaries.
Validations are also checked during this process.
2. Black Box Testing:

Black box testing is also called as behavioral testing. It focuses on the
functional requirements of the software. It is related to input and output
only and not related with the internal structure of the program. This testing
is also done so as to find errors such as,
 Initialization and termination errors.
 Behavior and performance errors.
 Incorrect and missing functions.
 Interface errors
 Errors in data structures and external database access.
3. Validation Testing:
Validation testing is done when we have to declare some validation
regarding our input screens. For e.g. suppose we have an input screen in
which we want to enter data between 1 to 31, so that in case the user enters
data above 31 or below 1, then it will show an error. This is called
validation testing.

4. GUI Testing:
GUI (Graphical User Interface) test verifies the alignment, font, images
and buttons, as per the requirements.GUI testing is also called Look and
Feel testing.
5. System Testing:
System testing begins once modules are integrated together for a
platform test in whole system environment. System testing can
occur in parallel with integration test especially with top-down
method.

Important Notes:
1) FOR SY BSc-Comp Sc Students, Project Work should include following chapters:
Chapter No.- 1 : Company Profile
Chapter No.- 2 : System Analysis
Chapter No.- 3: Requirement Analysis
Chapter No.- 4: Design (only following components)
 Entity Relationship Diagram
 Data Flow Diagram
 Data Dictionary
2) FOR TY BSc-Comp Sc Students, Project Work should include following chapters:

Chapter No.- 1 : Company Profile
 Use Case Diagram
 Class Diagram
 Sequence Diagram
 Activity Diagram
 Data Dictionary
Chapter No.-5: I/O Screens
Chapter No.-6: Reports
Chapter No.-7: Coding
Chapter No.-8 : Software System Testing
Chapter No.-9 : Implementation
Chapter No.-10: Bibliography
3) FOR TY BCA Students, Project Work should include following chapters:

Chapter No.-1 : Company Profile
 Data Flow Diagram
 Data Dictionary
Chapter No.-5 : I/O Screens
Chapter No.-6 : Reports
Chapter No.-7 : Coding
Chapter No.-8 : Software System Testing
Chapter No.-9 : Implementation
Chapter No.-10 : Bibliography

Page 10 of 61 -- Project Work Guidance Case Study: Petrol Pump Management System
Case Study-1
Petrol Pump Management System
Compiled by
Mr. Sagar P. Chitte

M.Sc. (Computer Science)

M.V.P.Samaj’s
Commerce Management & Computer Science (C.M.C.S.) College,
Udoji Maratha Boarding Campus, Gangapur road, Nashik 422 013
Index
Sr. No. Title Page-No

1 Company Profile 12
General Profile
Department Details
Department Under Study
2 System Analysis 13
Study of Present System
Introduction to proposed system
Scope of the system
3 Requirement Analysis 14
Feasibility Study
H/W & S/W Requirements
4. Design
Entity Relationship Diagram 15
Data Flow Diagram 16
Use Case Diagram 19
Class Diagram 22
Sequence Diagram 23
Activity Diagram 26
Data Dictionary 29
5. I/O Screens
6. Reports
7. Coding
8. Software System Testing
9. Implementation
Software System Installation
User Training & User Manual
Limitations of the Software System
Future Enhancements
10. Bibliography

Chapter-1: Company Profile
A PETROL PUMP SYSTEM
Petrol Pump is a place where people get fuel and lubricants for their vehicles.
Filling station is a facility which sells fuel and lubricants for motor vehicles.
Fuel dispenser is used to fill different types of fuels into vehicles and calculate the financial
cost of the fuel transferred to the vehicle. Most common fuels sold today are petrol, diesel
and gas.
Petrol Pump has following departments as:

1) Account
2) Purchase
3) Sales
Purchase department manages all purchases related transactions. It places order for fuel and
lubricants to different suppliers. Sales department manages all sales related transactions. It
manages quantity of a fuel and lubricant sold. It also manages PetroCard service. Account
department manages all financial transactions. It calculates all purchase amounts. It manages
other expenditure like electricity bill, salaries of all employees, maintenance of overall Petrol
Pump etc.
Petrol Pump provides many services as follows:
1) Petrol Pump provides different types of fuels for different types vehicles.
Fuels are:
Petrol
Speed Petrol
Diesel
Turbo Diesel
Gas
2) Petrol Pump provides different types of lubricants for different types of vehicles.
Some of the lubricants are listed below:
Castrol 2T
Castrol 4T etc.
3) Petrol Pump may provide tyre pressure service for filling air in vehicle wheels.
4) Petrol Pump also provides a PetroCard service. In this service Petrol Pump creates a
account for customer and issues a PetroCard. Customer has to give balance amount for
PetroCard. Once customer gets PetroCard then Next time when customer goes to Petrol
Pump then he do not have to pay money for fuel or lubricant. Fuel filler swaps a
customer’s PetroCard and calculated amount of the fuel transferred to a vehicle is
deducted from ones account. This will continue until there is balance amount on customer
account. Customer can renew a PetroCard as and when required.

Chapter-2: System Analysis
Study of a Present System: Working of a Typical Petrol Pump

The working of a Petrol Pump is to be obtained by visiting the actual Petrol Pump, talking to
the people working there. It is provided here for completeness of a case study.
A person goes to Petrol Pump. Petrol Pump may have fuel dispensers for different types of
fuels. Person goes to a fuel dispenser according the fuel he/she wants to fill. Fuel filler then
fills the fuel in a vehicle according to person’s request. Fuel dispenser calculates the
financial cost of the fuel transferred to the vehicle. Then customer pays the amount to the
fuel filler by cash or PetroCard. If customer wants then fuel filler gives bill to the customer.
As per the requirement customer may ask for lubricant for his/her vehicle.
Problems with present system:

 Present working of Petrol Pump is manual.
 Data is maintained in many registers manually. So data accuracy is minimum.
 Lot of paper work makes availability of information slow. Loss of document is possible.
 Record searching is time consuming and slow.
 Account details are calculated and maintained manually.
By computerization of the existing system, above drawbacks can be eliminated and best
results can be achieved.
Introduction to Proposed System
Scope & benefits of the proposed system:

 Large volume of data will be handled by the system.
 Various reports will be provided by the system.
 Security and integrity of database can be maintained.
 Proper management of all the manpower of the Petrol Pump is possible.
 Keeping record in detail of each transaction of the Petrol Pump is possible.
 Information unavailability due to loss of record is eliminated.
 Payment calculation of a supplier’s bill is easy and fast.
 Account maintenance of a Petrol Pump is easier.
 Efficient working of a Petrol Pump can be achieved.

Chapter-3: Requirement Analysis
Feasibility Study:
System analyst has to examine whether the developed computerized Petrol pump
management system is feasible from the point of view of operational, technical &
economical. System analyst has to also consider the feasibility factors at the time of
analyzing of system. The study of following points will prove if the proposed system is
feasible or not.
1. Technical Feasibility:
A computerized system will be technically more effective than the existing
manual system. Person who is presently handling manual system is going to handle the
computerized Petrol Pump Management system. The software system may be easy to
understand and use because this is as per the user requirement. The software system
produces reports as per the requirements of the end user. e.g. supplier order records, bills,
bill receipt reports. As various registers used in administrative Petrol Pump system,
transactions are to be authorized by the department, maintaining them on computer would
be an additional facility for them.
2. Economical Feasibility Study:

Economical Feasibility study analysis is most frequently used for evaluating the
effectiveness of a proposed system. The procedure is to determine the benefits and
savings that are expected from a proposed system and compare them with input costs.
The benefits may not be in the form of speed only but also in error handling, redundancy
control, availability of online information & reduction cost for stationary users.
3. Operational Feasibility Study:

Operational feasibility study addresses questions whether we can run the proposed
system with minimum hardware software setup and the demands of processing are
realistic? Can user operate it? Since this system is being developed for the Petrol Pump
management, every user will undergo training about use of the software system.
H/W and S/W Requirements:

To run this software system effectively & efficiently we will require the software like:
 Window 98 or upward version of operating system
 Java / PHP /Visual Basic/ DOTNET
 MS-ACCESS/ORACLE/MS SQL/MY SQL etc
The hardware requirement to run this software system efficiently is as follows,

 A PC with 512MB RAM, 180 GB HDD
 A printer

Chapter-4: Design
Entity Relationship Diagram:
Goes Petrol Pump

Customer Management Has Product Supply Supplier
to
System
Is a
Gives
To
Has
Pays
Lubricant Fuel
Employee To Salary Gives

Petrocard_order
Is a Supplier_bill
To Gives
Fuel filler Manager Accountant Pays
Customer_bill Gives Purchase_order

Data Flow Diagram:
Context Level DFD
Customer 0.0 Petro Card

Customer Customer
Details Details
Petrol Pump
Supplier
Supplier Details
Management Invoice Supplier
Bill Details System Details
Transaction All
Employee Employee
Details Reports
First Level DFD
Customer Details 1.0 Customer Details

Customer Customer
Master Data Supplier Details
Supplier Details Supplier
Supplier Entry
Process Employee Details
Employee
Employee Details
Employee Product Details
Product Details Product
Customer Details 2.0

Customer
Petro Card
Other Details Petro Card Petrocard_order
Employee Order
Order Details
Generation
Process

Product Details 3.0

Product
Purchase
Supplier Details Purchase
Supplier Order Purchase_order
Order Details
Generation
Other Details Process
Employee
Employee Details 4.0

Employee
Employee
Salary Details Salary
Other Details Salary
Accountant
Generation
Process
Purchase
Purchase_order Order Details
Supplier
Supplier_bill Bill Details Supplier
Invoice Report
Petrocard
Petrocard_order Order Details 5.0
Petro Card Customer
Customer Bill Bill Report
Customer_bill Details Report
Generation
Salary Salary Process All Reports
Details Manager
Supplier
Supplier Details
Transactions Employee
Product Product Report
Details
Customer
Customer Details
Employee
Employee Details

Second Level DFD
2.1
Petrocard order
Petrocard_order details
Customer
Petrocard bill
Accountant Other Bill details Customer_bill
Details Generation
Process
3.1
Purchase order
Purchase_order details
Supplier
Purchase bill
Other Bill details Suppliler_bill
Accountant
Details Generation
Process

Use Case Diagram:

System
Register Purchase
Order
Edit Purchase Cancel Purchase

Order Order
manager New Purchase

Order
supplier
Reject Product
Genrate Bill
Pays Bill
verify transaction
detaiils


Class Diagram:
Employee Salary

Sequence Diagram:



Activity Diagram:



Data Dictionary:
Product
Fields Data type Description Keys Size
prodid Number Product id PK 2
prodname Text Product name - 20
prod type Text Product type - 15
rate Number Product rate - 3,2
avail_qty Number Available quantity - 5
Customer
custid Number Customer id PK 8
custname Text Customer name - 30
custaddr Text Customer address - 50
mobile Number Mobile number - 10
phone Number Phone number - 12
Supplier

supid Number Supplier id PK 2
supname Text Supplier name - 30
offaddr Text Supplier office address - 50
phone1 Number Phone Number - 12
phone2 Number Phone Number - 12
Employee

empid Number Employee id PK 2
ename Text Employee name - 30
eaddr Text Employee address - 50
phone Number Phone Number - 12
etype Text Employee type - 20
salary Number Employee salary - 5,2
doj Date Date of joining - 10

Purchase_order
poid Number Purchase order id PK 8
supplierid Number Supplier id FK 2
Productid Number Product id FK 2
Qty Number Product Quantity - 5
podate Date Purchase order date - 12
Supplier_bill
Pobillid Number Purchase order bill id PK 8
Poid Number Purchase order id FK 8
sup_bill_amt Number Supplier bill amount - 6,2
other_amt Number Other amount - 4,2
totamt Number Total amount - 6,2
billdate Date Supplier bill date - 12
Petrocard_order

petrocardid Number Petro Card id PK 8
Custid Number Customer id FK 8
FromDate Date From date - 12
ToDate Date- To date - 12
petrocard_date Date Petro Card purchase date - 12
petrocard_bal Number Petro Card balance amount - 5,2
Customer_bill
custbillid Number Customer bill id PK 8
petrocardid Number Petro Card id FK 5
cust_bill_amt Number Customer bill amount - 5,2
other_amt Number Other amount - 4,2
totamt Number Total amount - 5,2
billdate Date Customer bill date - 12

Salary
esalid Number Employee salary id PK 8
empid Number Employee id FK 2
other_amt Number Other salary amount - 4,2
tot_sal Number Total salary amount - 5,2
sal_date Date Employee salary date - 12

Page 32 of 61 -- Project Work Guidance Case Study: Hospital Management System
Case Study-2
Hospital Management System
Compiled by
Smt. S. P. Bhamare-Pawar.
M.Sc. (Computer Science)

M.V.P.Samaj’s
Commerce Management & Computer Science (C.M.C.S.) College,
Udoji Maratha Boarding Campus, Gangapur road, Nashik 422 013
Index
Sr. No. Title Page No

1 Company Profile 34
General Profile
Department Details
Department Under Study
2 System Analysis 35
Study of Present System
Scope of the system
3 Requirement Analysis 36
Feasibility Study
H/W & S/W Requirements
4. Design
Entity – Relationship Diagram 37
Data Flow Diagram 38
Use Case Diagram 46
Class Diagram 47
Sequence Diagram 48
Activity Diagram 58
Data Dictionary 59
5. I/O Screens
6. Reports
7. Coding
8. Software System Testing
9. Implementation
Software System Installation
User Training & User Manual
Limitations of the Software System
Future Enhancements
10. Bibliography

Chapter-1: Company Profile
A HOSPITAL SYSTEM
Hospital is a medical institution where sick or injured people are given medical or
surgical help.
Hospital is an institution for the treatment, care, and cure of the sick and wounded, for the
study of disease, and for the training of physicians, nurses, and allied health care
personnel.
Hospital has many services:
 Cardiac Investigation
This test is related with heart. There are many diagnostic tests and procedures
available in hospital which help doctors ascertain whether one have a heart disease.
Many tests available such as Electrocardiogram (ECG), Chest X-Ray (CXR),
Echocardiography, Treadmill Testing etc.
 Radiology
Radiology employs the use of medical imaging to diagnose and treat nearly every
type of disease and injury that exists. Radiology is used in four different ways. It is
used for diagnosing illnesses and diseases, interventionist medicine, therapeutic
medicine, and nuclear medicine. Diagnostic radiology uses medical equipment to
determine whether a disease, illness or injury is present. Interventionist radiology
involves using medical imaging equipment to guide doctors while they perform
certain types of medical procedures. Radiation therapy is used to treat certain illnesses
and diseases by targeting certain cells, such as cancer cells, to be exposed to and
killed by radiation. Nuclear medicine involves administering medication that is
radioactive into the body. This helps to give doctors a clear picture about the function
of certain organs and body systems.
 Laboratory
A medical laboratory is a laboratory where tests are done on clinical specimens in
order to get information about the health of a patient. A laboratory requires expertise
from different fields like Hematology, Clinical Pathology, Genetics, Microbiology
etc.
 Pathology
Pathology is a medical specialty looking at disease processes and their cause. Body
tissue, blood and other body fluids are analyzed to assist medical practitioners in
identifying the cause and severity of disease, and to monitor treatment. Pathology is
the study of chemical and biochemical mechanisms of the body in relation to disease.
 ICU
An intensive care unit (ICU), critical care unit (CCU), intensive therapy unit or
intensive treatment unit (ITU) is a specialized department used in many countries'
hospitals that provides intensive care medicine. Many hospitals also have designated
intensive care areas for certain specialities of medicine, as dictated by the needs and
available resources.

Chapter-2: System Analysis
Study of a Present System: Working of a Typical Hospital

The working of a hospital is to be obtained by visiting the actual hospital, talking to the
people working there. It is provided here for completeness of a case study.
A person visits the hospital. He/She may be directed by the receptionist to the manager,
doctor or their representative for enquiry. Patients go to hospital & fill case paper, they are
then treated by the doctor.
Hospital is visited by specialized doctors. Doctor is permanent or visiting. According to case

paper, doctor treats patients. Number of services such as Cardiac Investigations, Radiology,
Laboratory, Pathology etc. available in the hospital. Patient is either OPD (Out Patient
Department) or IPD(In Patient Department). After getting treatment OPD patient pays the
bill to management. IPD patient occupies the ward. Ward contains number of rooms. It may
be genral, private, semi-prvate or ICU.
After getting treatment doctor prepares discharge card for IPD patient and sends to the
hospital management. Management generates bill, sends it to the patient. Patient then pays
the bill.
Problems with present system:

 Present working of hospital is manual.
 Data is maintained in many registers manually. So data accuracy is minimum.
 Process of manual filing of case paper and other information details is time consuming.
 Lot of paper work makes availability of information slow. Loss of document is possible.
 Records searching is time consuming and slow.
 Account details are calculated and maintained manually.
By computerization of the existing system, above drawbacks can be eliminated and best
results can be achieved.

Scope & benefits of the proposed system:
 Large volume of data will be handled by the system.
 Various reports will be provided by the system.
 Security and integrity of database can be maintained.
 Proper management of all the manpower of the Hospital is possible.
 Keeping record in detail of each doctor and patient of the Hospital is possible.
 Information unavailability due to loss of record is eliminated.
 Maintenance of discharge summary is easier
 Payment calculation of a doctor's bill is easy and fast.
 Account maintenance of a hospital is easier.
 Efficient working of a hospital can be achieved.

Chapter-3: Requirement Analysis
Feasibility Study:
System analyst has to examine whether the developed computerized hospital management
system is feasible from the point of view of operational, technical & economical. System
analyst has to also consider the feasibility factors at the time of analyzing of system. The
study of following points will prove if the proposed system is feasible or not.
1. Technical Feasibility:
A computerized system will be technically more effective than the existing
manual system The person who is presently handling manual system is going to handle
the computerized Hospital Management system. The software system may be easy to
understand and use because this is as per the user requirement. The software system
produces reports as per the requirements of the end user. e.g. Patient records, bills, bill
receipt reports. As various registers used in administrative hospital system, transactions
are to be authorized by the department, maintaining them on computer would be an
additional facility for them.
2. Economical Feasibility Study:

Economical Feasibility study analysis is most frequently used for evaluating the
effectiveness of a proposed system. The procedure is to determine the benefits and
savings that are expected from a proposed system and compare them with input costs.
The benefits may not be in the form of speed only but also in error handling, redundancy
control, availability of online information & reduction cost for stationary users.
3. Operational Feasibility Study:

Operational feasibility study addresses questions whether we can run the proposed
system with minimum hardware software setup and the demands of processing are
realistic? Can user operate it? Since this system is being developed for the Hospital
management, every user will undergo training about use of the software system.
H/W and S/W Requirements:

To run this software system effectively & efficiently we will require the software like:
 Window 98 or upward version of operating system
 Java / PHP /Visual Basic/ DOTNET
 MS-ACCESS/ORACLE/MS SQL/MY SQL etc
The hardware requirement to run this software system efficiently is as follows,

 A PC with 512MB RAM, 180 GB HDD
 A printer

Chapter-4: Design
Entity Relation Diagram:
test
Entity Relationship (ER) Diagram
1
Is for Specalization
1
m
Pat-test have
Patient Services m
m m
requires 1
Avails gets Treatement gives doctors
m m m m m
1 1 Hospital
Patient 1 1 is a
1 1 Has
to
M goto
is a 1
Discharge send Permanent Visiting
1
1 m
1 1 room
OPD IPD Occupies Bed m

m genral
1 1 m has
1
Pays contains contains private
Room type
1 1 semi
Bill Ward Is a
ICU

Context Level Diagram:
Context level Diagram
Patient detail
Patient Patient
Discharge detail
0.0
Room Bill details Management
Management
details Hospital
Management
Doctor System
Doctor Doctor duty Doctor
details schedule

First Level Diagram:
First level DFD

1.0
Patient details
Patient Patient
Patient Patient
details management Discharge detail
system
Patient allocation detail Room_Master
2.0
Treatment Get details
Doctor Treatment Treatment Detail
details

First Level Diagram continued:
Room charges
Room_Master
3.0
Bill no
Patient
Patient Bill Bill_master
admission Generation Amount detail
System
Patient status Patient
Discharge date
Doctor
Doctor’s charges
4.0
Discharge details
Send discha
Management Discharge Discharge_detail
-rge details

5.0
Doctor duty
Doctor
Doctor schedule
Doctor Doctor_details
details management
system Updated doctor
record
Ward details
Ward
6.0
Ward details
Patient Ward
Patient Ward
Details Maintenance
system

Patientdetails
Patient
Patients all
Roomdetails details
Room_master
report Patient
7.0
Bill_master Billdetails All
report Doctor
Report
Generation
patTreat
TreatmentDetails mentDetails
Ward Management
Report
Discharge_Details
Patientdischarge
details
Doctor_Details
doctordetails
Ward
Patientwarddetails

Second Level Diagram:
Second level DFD
1.1
Patient
Patient Patient
Patient allocation details
Patient
Admission Discharge detail
details
Process
ward status ward
Ward
Ward details
Ward details
Ward
1.2
Update ward status
Patient details ward
Patient Patient
Discharge
process
Patient discharge Patient
Doctor date
Doctor details

Second Level Diagram continued:
2.1
Visiting doctor Updated doctor
Visiting information Doctor_details
Doctor
details record
2.2
Updated doctor
Permanent
Permanent information Doctor_details
Doctor
Doctor doctor
detail
4.1
Updated ward
ward ward
ICU information
Ward
details ward

Second Level Diagram continued:
4.2
Updated ward
ward ward
General information
Ward
detail ward
4.3
Updated ward
ward ward
semi information
Ward
detail ward
4.4
Updated ward
ward ward
delux information
Ward
detail ward

UML DIAGRAM:
Use Case Diagram

Class Diagram
Patient
Hospital
Private int id 1..*
Private varchar name
+public int adddoctor()
Private int age
+public int addstaff()
Private char sex
+public void deldoctor()
Private date appdate
+public void delstaff()
1 +public int create() +public void editdoctor()
+public IsInpatient(int id) 1 +public void editstaff()
+public Ispatient(int id)
1 1..* Expenditure
1..*
Patient Float amt
1
Register TakesAppt. Int billno
1 Pat_test Public void givesalary(int id)
Appointment 1
Private int patientid Draw Salary 1
Date dt Private int id Doctors
Time tm Private int flag Private int id
1
+public void opappt() Private varchar name
+public void testappt() Private int age
+public void docappt() Private address
1 +public int getTest(int id) 1 Private char sex
+public int getOper(int id) Private float salary
Registration 1..* Public void drawsalary()
1
IssueBill
+public int register()
+public void allotBed(int id)
1
1 Bill
Float amt 1 Generate
Int billno Discharg
Allocate e Report
Bed Public float addTestCharges(int id)
Pubic float addOprCharges(int id)
Public float addApptCharges(int id)
1..* Public float addWardCharges(int id)
Ward 1 1
Private int wardno Discharge
Private int noBeds
Private varchar name Generate
Ward +public void dispWardStatus()
+public int bedStatus(int wardid) Report +public void dispAdDisReport(int id)
+public varchar getName(int bedno) +public void dispPatInfo(int id)
1 1
+public void dispBillReport(int id)
Display Patient Info 1

Sequence Diagram:
ADMISSION:
:Patient :Registration :Bill :Appointment
1:Create()
2:inpatient()
3:Register()
4:adApptCharg
es() 5:Date()
6:time()

DOCTOR_APPOINTMENT
:Patient :Bill :Appointment :Pat_test
1:ispatient()
2:addApptCharges()
3:Date()
4:time()
5:Docappt()

TEST_APPOINTMENT:
:Patient :Bill :Appointment :Pat_test
1:ispatient()
2:addTestcharges()
3:Date()
4:time()
5:testappt()

BED_ALLOTMENT:
:Registration :Bill :Ward :Discharge
1:add
Ward
Charg
2:allotBed()
es ()
3:getname()
4:dispWardStatus()

UNDERGO_OPERATION:
:Patient :Bill :Ward
1:ispatient()
2:addoprCharges()
3:getOpr()

DRAWSALARY:
:Hospital :Doctors :Expenditures
1:Isdoctor()
2:IsStaff()
3:DrawSalary()

PRESCRIBE_TEST:
:Doctors :Pat_test :Discharge
1:AddtestCharges()
2:GetTests()
3:AddisReport()

WARD_WISE_BED_STATUS:
:Patient :Ward :Discharge
1:IsPatient()
2:allotBed()
3:bedStatus()
4:dispWardStatus()

ADMISSION/DISCHARGE_REPORT:
:Patient :Pat_test :Discharge
1:Ispatient()
2:getTests()
3:GetOpen()
4:dispWardStatus()
5:dispAddi
sReport()

PATIENT_INFO:
:Patient :Register :Discharge
1:Ispatient()
2:dispWardStatus()
3:dispaddisReport()
4:dispPatientInfo()

Activity Diagram:




CASESTUDY

Uploaded by

CASESTUDY

Uploaded by

Project Work Guidance

(For those who want to learn)

A Case Study Approach

(For private circulation only)

Dr. Ravindrakumar D. Patil

Sr. Title Page

M.V.P. Samaj’s, C.M.C.S. College, Nashik-13

What a student should do?

Dr. Ravindrakumar D. Patil, Principal

M.V.P. Samaj’s, C.M.C.S. College, Nashik-13

Software Development Life Cycle (SDLC)

It consists of following steps:

This includes following phases:

There are three aspects of feasibility study are:

iii. Request approval:

M.V.P. Samaj’s, C.M.C.S. College, Nashik-13

M.V.P. Samaj’s, C.M.C.S. College, Nashik-13

b) Implementation also consists of hardware testing and software installation.

M.V.P. Samaj’s, C.M.C.S. College, Nashik-13

Software System Testing

Basic activities involved in the testing are:

Following software techniques are used for software testing:

1. White Box Testing:

2. Black Box Testing:

M.V.P. Samaj’s, C.M.C.S. College, Nashik-13

M.V.P. Samaj’s, C.M.C.S. College, Nashik-13

2) FOR TY BSc-Comp Sc Students, Project Work should include following chapters:

3) FOR TY BCA Students, Project Work should include following chapters:

M.V.P. Samaj’s, C.M.C.S. College, Nashik-13

Petrol Pump Management System

Mr. Sagar P. Chitte

M.V.P. Samaj’s, C.M.C.S. College, Nashik-13

Sr. No. Title Page-No

M.V.P. Samaj’s, C.M.C.S. College, Nashik-13

Chapter-1: Company Profile

A PETROL PUMP SYSTEM

Petrol Pump has following departments as:

M.V.P. Samaj’s, C.M.C.S. College, Nashik-13

Chapter-2: System Analysis

Study of a Present System: Working of a Typical Petrol Pump

Problems with present system:

Introduction to Proposed System

Scope & benefits of the proposed system:

M.V.P. Samaj’s, C.M.C.S. College, Nashik-13

Chapter-3: Requirement Analysis

2. Economical Feasibility Study:

3. Operational Feasibility Study:

H/W and S/W Requirements:

The hardware requirement to run this software system efficiently is as follows,

M.V.P. Samaj’s, C.M.C.S. College, Nashik-13

Entity Relationship Diagram:

Goes Petrol Pump

Employee To Salary Gives

Fuel filler Manager Accountant Pays

Customer_bill Gives Purchase_order

M.V.P. Samaj’s, C.M.C.S. College, Nashik-13

Data Flow Diagram:

Context Level DFD

Customer 0.0 Petro Card

First Level DFD

Customer Details 1.0 Customer Details

Customer Details 2.0

M.V.P. Samaj’s, C.M.C.S. College, Nashik-13

Product Details 3.0

Employee Details 4.0

M.V.P. Samaj’s, C.M.C.S. College, Nashik-13

Second Level DFD

M.V.P. Samaj’s, C.M.C.S. College, Nashik-13

Use Case Diagram:

M.V.P. Samaj’s, C.M.C.S. College, Nashik-13

Edit Purchase Cancel Purchase

manager New Purchase

M.V.P. Samaj’s, C.M.C.S. College, Nashik-13

M.V.P. Samaj’s, C.M.C.S. College, Nashik-13

M.V.P. Samaj’s, C.M.C.S. College, Nashik-13

M.V.P. Samaj’s, C.M.C.S. College, Nashik-13