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. SUNNY SINHA DATE: 24th March 2011 AMIT SHARMA Page 2 . SUNNY SINHA and AMIT SHARMA. Mr. 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.

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. all the relationship and entities are only concern with that system only. So. Basically. the report has been prepared by keeping Medical Store in the mind. Page 3 .

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. Objective Our main concern is to develop system software for medical store for managing the records of medicines and other utilities of medical. This software will inform the user. 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. Whenever.SYSTEM SOFTWARE ENGINEERING 1. Page 4 . then owner can raise a new purchase order to supplier for next batch of medicines. 2. stock of a medicine reaches to minimum predefined level.

he gives order for that medicines with certain quantities. Manager asks the customer for cash payment for bill. 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. gel. ointment. 3.SYSTEM SOFTWARE ENGINEERING ENTITY RELATIONSHIP DIAGRAM (ERD) CUSTOMER Receipt/pay INVOICE Orders/purchase Generates ORDER Manages MEDICINE Assumptions: 1. etc. System software then generates a Billing/ Invoice for customer for purchasing the medicines. Page 5 . 2. Customer comes with a receipt of doctor for particular medicine. 4.

 Customer gives cash payment against of invoice that has generated.  Customer asks for some medicines and then system responds for medicines details.  System generates invoice for the order. Page 6 .SYSTEM SOFTWARE ENGINEERING CONTEXT LEVEL DIAGRAM CUSTOMER ORDER DETAILS INVOICE PAYMENT DETAILS 0.0 MEDICAL SHOP 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.

0 ORDER DETAILS ORDER CUSTOMER 3.SYSTEM SOFTWARE ENGINEERING DATA FLOW DIAGRAM CUSTOMER 1.0 INVOICE DETAILS INVOICE BILLING Page 7 .0 MASTER MANAGEMENT CUSTOMER MANAGEMENT MEDICINE 2.

If any of customers forget to take Doctor’s receipt and he/she ask for same medicine. referred by.0 Order details for maintain the orders DFD 3. Bill ID.0 depicts that MASTER MANAGEMENT store the Database for Customers as well as for Medicines. Particulars and Grand total of Bill. so we can provide the medicine by checking up of Database of Customer master. When a transaction is get completed. Page 8 . Our system will update the inventory level of medicines in Database. Invoice is calculated in two phase. Where header includes main contents of Invoice like Date.0 An invoice is been generated by system when transaction is completes. DFD 2. 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. Invoice is combination of both of these formats and then prints a copy for customer.SYSTEM SOFTWARE ENGINEERING Description DFD 1.

SYSTEM SOFTWARE ENGINEERING Relationship Forms Page 9 .

SYSTEM SOFTWARE ENGINEERING Page 10 .

SYSTEM SOFTWARE ENGINEERING Invoice master Page 11 .

Sign up to vote on this title
UsefulNot useful