MEDICAL STORE MANAGEMENT SYSTEM

This topic is covered under Data modelling and implementation. This project looks after an efficient billing management in a medical store. it includes a flow chart, data flow diagram, normalization etc.

1. DATA MODELING AND IMPLEMENTATION
MEDICAL STORE
MANAGEMENT SYSTEM
Course ID: CS 457 H
Student ID:17233
Student Name: Aniket Choudhury

2. CONTENT
Narrative of project
Project Plan
Flow Chart
Context Diagram(Level 0)
Data flow Diagram(Level 1)
Data flow Diagram(Level 2)
Data Dictionary
Entity Relationship Diagram
Data Model Diagram(DMD)
Normalization
SQL script & Output Report
Advantage & Disadvantage
References
Conclusion

3. NARRATIVE OF PROJECT
This project is to design medical store management
system. The main focuses is on the billing area. This
system identifies whether the customer is eligible for the
discounts or not. This is done by checking the existing
database for whether the customer is registered. If the
customer is a member then he can enjoy the discounts and
offers. In case if the customer is not a member and is
willing to be a member then he is issued a membership
after storing his information in the database.

4. FLOW CHART

5. CONTEXT DIAGRAM(LEVEL 0)

6. DATA FLOW DIAGRAM(LEVEL 1)

7. DATA FLOW DIAGRAM(LEVEL 2)

8. Entity Name Attribute name Description
Owner Owner_id Owner identifier
Owner First_name Owner first name
Owner Last_name Owner last name
Owner Contact_NO Owner contact
Medical Store Medicine_code Medicine identifier
Medical Store Quantity Amount of medicine
Medical Store Medicine_type Type of medicine
Medical Store Medicine_name Name of medicine
Medical Store MFG_date Date of manufacture
Medical Store Exp_date Date of expiration
Medical Store Price Cost
Mmember Member_id Unique id of member
Mmember Last_name Member last name
Mmember Start_date Membership start date
Mmember End_date Membership end date
Mmember Contact_no Contact of member
Billing_Info Customer_id Customer identifier
Billing_Info Customer_name Customer name
Billing_Info Address Customer address
Billing_Info Contact_no Customer contact
Memployee E_id Employee identifier
Memployee E_name Employee name
Memployee Address Employee address
Memployee Contact_no Employee contact
Memployee Job Employee role
Memployee Salary Employee salary
DATA DICTIONARY

9. ENTITY RELATIONSHIP DIAGRAM

10. DATA MODEL DIAGRAM(DMD)

11. NORMALIZATION(1
ST
NORMAL FORM)
OWNER = #OWNER_ID + FIRST_NAME + LAST_NAME + CONTACT_NO
MEDICAL STORE = #MEDICINE_CODE + QUANTITY + MEDICINE_TYPE +
MEDICINE_NAME + MFG_DATE + EXP_DATE +MFG_BY + PRICE
MMEMBER = #MEMBER_ID + LAST_NAME + START_DATE + END_DATE +
CONTACT_NO
MEMPLOYEE = #E_ID + E_NAME + STREET_NO + APT_NO + CITY +
CONTACT_NO + JOB + SALARY
BILLING _INFO = #CUSTOMER_ID + CUSTOMER_NAME + STREET_NO +
APT_NO + CITY + CONTACT_NO

12. NORMALIZATION(2
ND
NORMAL FORM)
OWNER = #OWNER_ID + FIRST_NAME + LAST_NAME + CONTACT_NO
MEDICAL STORE = #MEDICINE_CODE + QUANTITY + MEDICINE_TYPE +
MEDICINE_NAME + MFG_DATE + EXP_DATE +MFG_BY + PRICE
OWNED BY = #OWNER_ID + #MEDICINE_CODE
MMEMBER = #MEMBER_ID + LAST_NAME + START_DATE + END_DATE +
CONTACT_NO
REGISTER = #M_CODE + #ID
MEMPLOYEE = #E_ID + E_NAME + STREET_NO + APT_NO + CITY +
CONTACT_NO + JOB + SALARY
WORK FOR = #E_ID + #MEDICINE_CODE
BILLING _INFO = #CUSTOMER_ID + CUSTOMER_NAME + STREET_NO + APT_NO +
CITY + CONTACT_NO
GENERATES = #CUSTOMER_ID + #MEDICINE_CODE

13. SQL SCRIPT & OUTPUT REPORT(1)
Customer is searching for a medicine called droxyl 500 that is available and
the cost is $11

14. SQL SCRIPT & OUTPUT REPORT(2)
Is the customer a valid member?
This is checked by member id or the phone number

15. SQL SCRIPT & OUTPUT REPORT(3)
As the customer is a valid member he receives a discount of 5%.

16. SQL SCRIPT & OUTPUT REPORT(4)
Suppose the customers membership id is expired and he renews the
membership

17. SQL SCRIPT & OUTPUT REPORT(5)
Suppose customer is searching for a medicine called cefakind 250 which is
not available

18. SQL SCRIPT & OUTPUT REPORT(6)
Customers Final bill receipt

19. ADVANTAGES
This system provides an easy way for the casher
to determine whether the customer is a valid
member so that he can provide them with
discount.
This system is also provides great help to the
casher to add or update new or existing members
respectively

20. DISADVANTAGE
As every coin has a two side this system also
suffers from disadvantage.
Multiple medicines can not be checked for a
customer.

21. CONCLUSION
This system provides an easy way for the operator
to interact with the database and to manipulate
the data in the database.
The operator can add, delete and update the
records in the database with ease.

22. REFERENCES:
1.https://en.wikipedia.org/wiki/Data_flow_diagram
2. Data Modeling Technical Publication
3. Data Structure Techmax Publication
4. https://www.youtube.com/watch?v=m6eQ8OQ7haU
5.https://en.wikipedia.org/wiki/Entity–relationship_model
6. https://docs.oracle.com/en/