SYSTEM SOFTWARE ENGINEERING

A PROJECT REPORT
On
“SYSTEM SOFTWARE FOR MEDICAL STORE”
For

“SYSTEM SOFTWARE ENGINEERING”

SUBMITTED TO

BY
SUNNY SINHA (091041)
AMIT SHARMA (091012)

IN FULFILLMENT OF
POST GRADUATE DIPLOMA IN MANAGEMENT (PGDM)
SYSTEM 2009-2011
MIT PUNE’s

MIT SCHOOL OF TELECOM MANAGEMENT

(MITSOT), PUNE
Submitted to: -

Prof. Archana Deshpande

Page 1
 SYSTEM SOFTWARE ENGINEERING

DECLARATION

I, Mr. SUNNY SINHA and AMIT SHARMA, Hereby declare that this project report is the
record of authentic work carried out by me and has not been submitted earlier to any University
or Institute for the award of any degree / diploma etc.

SUNNY SINHA AMIT SHARMA

DATE: 24th March 2011

Page 2
 SYSTEM SOFTWARE ENGINEERING

ABSTRACT

This report is actually prepared for Medical Store/Management. Here we have tried to identify
some entities and their relationship along with context level diagram and data flow diagram to
understand the system easily. Basically, the report has been prepared by keeping Medical Store
in the mind. So, all the relationship and entities are only concern with that system only.

Page 3
 SYSTEM SOFTWARE ENGINEERING

1. Objective

Our main concern is to develop system software for medical store for managing the
records of medicines and other utilities of medical.

2. Scope of projects

This software will be helpful for medical store owner/keeper to keep a track of record for
daily sales of medicines and maintain the stock of all medicines. Whenever, stock of a
medicine reaches to minimum predefined level. This software will inform the user, then
owner can raise a new purchase order to supplier for next batch of medicines.

In Our case we are maintaining the sales record of customer side. That who bought what
medicines and who had referred for these medicines (Doctor).

For future up gradation we have planned to cover Purchase orders record too and more
addition features to maintain Inventory.

Page 4
 SYSTEM SOFTWARE ENGINEERING

ENTITY RELATIONSHIP DIAGRAM (ERD)

Receipt/pay INVOICE
CUSTOMER

Orders/purchase Generates

ORDER Manages MEDICINE

Assumptions:
1. Customer comes with a receipt of doctor for particular medicine, ointment, gel, etc. he gives
order for that medicines with certain quantities.
2. Store owner/manager gives medicine as per the order is being placed. He enters the
information for billing purpose and that medicines are deducted from inventory.
3. System software then generates a Billing/ Invoice for customer for purchasing the
medicines.
4. Manager asks the customer for cash payment for bill.

Page 5
 SYSTEM SOFTWARE ENGINEERING

CONTEXT LEVEL DIAGRAM

CUSTOMER

ORDER
DETAILS
0.0
INVOICE
MEDICAL SHOP
PAYMENT DETAILS MANAGEMENT REPORT

MEDICINE DETAILS
MANAGEMENT

Assumptions
In our medical Shop management there are two main entities for the system

1) customer
2) management

In context level diagram the activities are shown as given in above diagram.

 Customer asks for some medicines and then system responds for medicines details.
 System generates invoice for the order.
 Customer gives cash payment against of invoice that has generated.

Page 6
 SYSTEM SOFTWARE ENGINEERING

DATA FLOW DIAGRAM

CUSTOMER
CUSTOMER
1.0

MASTER
MANAGEMENT MANAGEMENT
MEDICINE

2.0

ORDER
CUSTOMER DETAILS
ORDER

3.0

INVOICE
INVOICE DETAILS BILLING

Page 7
 SYSTEM SOFTWARE ENGINEERING

Description

DFD 1.0 depicts that MASTER MANAGEMENT store the Database for Customers as well as
for Medicines. If any of customers forget to take Doctor’s receipt and he/she ask for same
medicine, so we can provide the medicine by checking up of Database of Customer master.

When a transaction is get completed. Our system will update the inventory level of medicines in
Database.

DFD 2.0 Order details for maintain the orders

DFD 3.0 An invoice is been generated by system when transaction is completes. Invoice is
calculated in two phase. Header and footer

Footer manages the quantity of medicines and price unit for those medicines for the same Bill
Then it is aggregated and sends to main invoice.

Where header includes main contents of Invoice like Date, Bill ID, referred by, Particulars and
Grand total of Bill.

Invoice is combination of both of these formats and then prints a copy for customer.

Page 8
 SYSTEM SOFTWARE ENGINEERING

Relationship

Forms

Page 9
SYSTEM SOFTWARE ENGINEERING

Page
10
SYSTEM SOFTWARE ENGINEERING

Invoice master

Page
11