Professional Documents
Culture Documents
ADBMS21 En222
ADBMS21 En222
Number ID Number
Name
First Name Last Name
1 ENYEW MEKETE RU/0635/14
2 AYANA GEBREYESUS RU/3560/14
3 YOHANNIS YENEAKAL RU/1731/14
4 DAWIT SOLOMON RU/0506/14
5 BETELHEM GETNET RU/1801/14
1
Table of content
CHAPTER: 1 Introduction
1.1 introduction ………………………………………………………………………………. 3
1.2 Feasibility study …………………………………………………... ………………… 5
1.2.1 Operational feasibility ……………………………………………….5
1.2.2 Technical feasibility ………………………………………………………7
1.2.3 Cost/Benefits ……………………………………………………………..…7
1.3 System Analysis ………………………………………………………………………..…… 9
1.4 System requirements
1.4.4 Hardware requirement ……………………………………………10
1.4.2 Software requirement ……………………………………………10
1.5 Data flow Diagram …………………………………………………………………….…. 11
2
4.5 Reference……………………………………………………………………………….39
CHAPTER: 1
INTRODUCTION
Pharmacy Database Management System
1.1 Introduction
The main aim of the project is the management of the database of the
Pharmaceutical shop. This is done by creating a database of the
available medicines in the shop. The database is then connected to the
main program by using interconnection of the Visual Basic program
and the database already created.
3
2. Sales and Billing: Implement a module to facilitate smooth
transactions, generate invoices, and manage billing for products sold
to customers.
3. Prescription Management: Develop functionality to handle
prescriptions, including recording prescription details, linking them to
specific patients, and maintaining a record of prescribed medications.
4. Supplier Management: Enable the system to manage details of
pharmaceutical suppliers, including contact information, product
catalogs, and past transactions.
5. Customer Management: Implement a feature to maintain a
customer database, store customer purchase history, and manage
customer profiles and prescription records.
6. Reporting and Analytics: Provide tools for generating reports on
sales, inventory levels, and financial summaries. This can help in
making informed decisions and identifying trends.
7. Security and Access Control: Ensure the system is equipped with
access controls, authentication mechanisms, and data encryption to
safeguard sensitive information.
4
3. Compliance and Regulatory Adherence: Help the pharmacy adhere
to industry regulations, such as record-keeping requirements,
prescription handling, and inventory management practices.
4. Enhanced Customer Service: Improve customer service through
better prescription management, quick and accurate billing, and
efficient service delivery.
5. Data Security and Integrity: Safeguard sensitive customer and
prescription data, ensuring confidentiality and compliance with data
protection regulations.
6. Business Insight and Decision Support: Provide tools for analyzing
sales, inventory turnover, and customer behavior to aid in strategic
decision-making and operational planning.
7. Scalability and Adaptability: Design the system to be scalable,
allowing for future expansion of features and adaptability to changes
in the pharmacy's operations.
These specific and general objectives pave the way for the successful
development and implementation of a pharmacy management system.
Clear objectives help in guiding the development process, ensuring
that the system meets the requirements of the pharmacy and its
stakeholders.
5
Application:
6
1.2 Feasibility Study
7
development of a computerized system. It is common knowledge that
computer installations have something to do with turnover, transfers,
retraining, and changes in employee job status. Therefore, it is
understood that the introduction of a candidate system requires special
effort to educate, sell and train the staff on new ways of conducting
business.
8
1.2.2 Technical feasibility
benefits and savings that are expected from a candidate system and
9
on-going effort that improves in accuracy at each phase in the
Costs:
Benefits:
Avoids tedious typing task
Faster document retrieval
Saving storage space
Keeps data secure
Easy to use, update and maintain
10
1.3 System Analysis
It is the most creative and challenging phase of the system life cycle.
The analysis phase is used to design the logical model of the system
whereas the design phase is used to design the physical model.
After the forms were designed, the next step was to specify the
data to be inputted, calculated and stored individual data items and
calculation procedure were written in detail. File structure such as
paper files were selected the procedures were written so as how to
process the data and procedures the output during the programming
phase. The documents were design ion the form of charts.
11
the description of the procedure for carrying out operations on the
given data.
flow and transform that are applied as data moved from input to output. The DFD are
partitioned into levels that represent increasing information flow and functional
details. The processes, data store, data flow, etc. are described in Data Dictionary.
12
13
CHAPTER: 2
CONCEPTUAL DESIGN
Data Dictionary
2.1 Entity with their description:
Patients: represents individuals who receive medication from the pharmacy.
Medications: represents the drugs that the pharmacy stocks and dispenses.
Doctor: represents a person who sees and wrote a prescription for the patient.
14
Insurance Information: the patient's insurance information.
Prescriptions:
Patient: the name of the patient for whom the prescription was written.
Medications:
Customer:
15
Name: the name who represents the customer.
Suppliers:
Employees:
Pharmacy:
Doctor:
16
E- mail: email address of the doctor.
Pharmacy:
have customers
Stocks a medication.
Employee:
Check prescriptions.
Medication:
Ordered to patients.
Prescription:
Prescribed a medication.
Patient:
Bought medication.
Doctor:
Writes a prescription.
Customer:
Purchases a medication.
Supplier:
17
Supplies a medication.
18
2.4 ER-Diagram
19
2.5 Mapping ER diagram to relational model
Patients:
Employee:
Customer:
Prescription:
Medication:
Pharmacy:
Supplier:
Doctor:
20
Doctor-ID Doctor Name Speciality Email Phone-no
21
(02, 'Mered Demere', 'DB', '09', '0978543267',
'Mereddemere23@amail.com'),
(03, 'Eshetu Selamu', 'DB', '04', '0922456874',
'Eshetuselam7@gmail.com'),
(04, 'Yabsira Lema', 'DB', '06', '0918114354',
'Yebsiralema065@gmail.com')
);
22
name VARCHAR(255),
address VARCHAR(255),
phone_number VARCHAR(20)
);
23
SELECT * FROM tablecustomer;
END
CREATE PROCEDURE insert_customer
AS
BEGIN
INSERT INTO customer (name, address, phone)
VALUES ('Meaza Yalew', 'DB,Kebele 04', '0967676767'),
('Yared Gizat', 'DB,Kebele 05', '0934256784'),
('Semira Ahmed', 'DB,Kebele 03', '0987341234'),
('Omar Kedir', 'DB,Kebele 09', '0912345678');
END
EXEC insert_customer;
24
BEGIN
CREATE TABLE medication (
medication_id INT PRIMARY KEY,
supplier_id INT,
name VARCHAR(255),
manufacturer VARCHAR(255),
description VARCHAR(255),
dosage VARCHAR(255),
stock_quality INT,
price DECIMAL(10, 2),
pharmacy_id INT,
FOREIGN KEY (supplier_id) REFERENCES supplier(supplier_id),
FOREIGN KEY (pharmacy_id) REFERENCES pharmacy(pharmacy_id)
);
INSERT INTO medication (medication_id, name, description, dosage, stock_quality,
price)
VALUES (001, 'Parastamol', 'Headache', '250', '50', '12 box'),
(002, 'Burfin', 'Headache, Toothache', '250', '100', '15 box'),
(003, 'Amocsasilin', 'Antibiotc', '250,500', '58', '10 box'),
(004, 'Ampicilin', 'Antibiotc', '250', '50', '7 box'),
(005, 'Cefximene', 'Antibiotic', '250', '60', '5 box');
END
EXEC insret_medication;
25
Lname String 3-20 Last name of the Not NULL
member
D.O.B Date Birth date of the Not NULL
member
Addre 5-12 Location of the Not NULL
ss pharmacy
Phone int 10 Phone number Not NULL
no
Email varch 10-27 Email address Not NULL
ar
Data Dictionary outlining
CHAPTER :3
Logical Design
3.1 Validating model with Normalization
Pharmacy
Supplier
Supplier ID Supplier Name Address Phone no
1001 ZAF Pharmaceutical Addis Ababa 0916542345
PLC
1002 Cadila Pharmaceutical Addis A BABA 0928458432
PLC
1003 Bilham Addis Ababa 0981949596
Pharmaceutical PLC
1004 Chief Drug Store Diredaw 0945676767
26
Customer
Custom-ID Customer Address Phone-no
Name
1 Meaza Yalew DB,Kebele 04 0967676767
27
Patient
Patien Patient Date of Address Pho-no Insurance
t -ID Name Birth informatio
n
001 Elsa 25/06/1983 DB,Kebele 07 0923164589 Yes
Wondese
n Abebe
002 Ferehiwot 16/07/1995 Dessie,Kebele 0918030454 No
Tamrat 05
Tiruneh
003 Abera 09/04/1989 Dessie,Kebele 0978453442 Yes
Aschalew 10
Kebede
004 Alemu 05/06/1990 DB,Kebele 08 0978623944 Yes
Getachew
Ayale
Medication
M
ed-
Name Descriptio Dosag Pric Stock Manufactu
ID n e e quanti rer
ty
00 Parastam Headache 250 50 12 box AA.P.M
1 ol
00 Burfin Headache,Tootha 250 100 15 box AD.P.M
2 che
00 Amocsasil Antibiotc 250,500 58 10 box AD.P.M
3 in
00 Ampicilin Antibiotc 250 50 7 box AA.P.M
4
00 Desprine Headache 100 100 8 box AD.P.M
4
00 Cefximen Antibiotic 250 60 5 box AA.P.M
5 e
Doctor
Doctor- Doctor Name Speciality Phone- Email
ID DOC DOC Lname no
Fname
28
01 Seifu Abeje Cadiologist
0911245697 Seifuabeje5665@ga
mail.com
02 Dsalegn Maru Dermatiologist 0956325369 Desalegnmaru7895@
gamail.com
03 Selam Mohammed Pthologist 0942378694 Selammohammed35
53@gamail.com
04 Rediet Getaneh Orthopedist 0977456672 Redietgetaneh@gam 2/7
/20
ail.com 14
29
3.3 First Normal form (1NF)
1NF of Pharmacy
1 NF of prescription
Prescription- Patient Medication Dosage(mg) Frequency
ID Patient Patient Patient
Fname Midname Lname
0001 Elsa Wondesen Abebe Panadol 250 Two times a
day
0002 Ferehiwot Tamrat Tiruneh Amocsasilin 100 3 times a day
0003 Abera Aschalew Kebede Ampcilin 500 Bede time
0004 Alemu Getachew Ayele Deprine 400 2 Times a
day
1 NF Supplier
Supplier-ID Supplier Name Address Phone number
1001 ZAF Pharmaceutical Addis Ababa 0916542345
PLC
1002 Cadila Addis Ababa 0928458432
Pharmaceutical PLC
1003 Bilham Addis Ababa 0981949596
Pharmaceutical PLC
1004 Chief Drug Store Diredawa 0945676767
1NF of Patient
30
e h
001 Elsa Wondese Abebe 25/0 DB 07 092316458 Yes
n 6/19 9
83
002 Ferihioet Tamrat TIRUN 16/0 Dessi 05 091803045 No
EH 7/19 e 4
95
003 Abera Aschalew Kebed 09/0 Dessi 10 097845344 Yes
e 4/19 e 2
89
004 Alemu Getache Ayele 05/0 DB 08 097862394 Yes
w 6/19 4
90
1NF Customer
Custe CustOmer Name Address Phone no
mer-ID Customer-Fname CustomerMname City Kebele
1 Meaza Yalew DB 04 09676767
1NF of Medication
Medication Name Description Dosage Price
-ID
001 Parastamol Headache 250 50
31
002 Brufin Headache 250 100
002 Brufin Toothache 250 100
003 Amocsacilin Antibotic 250,500 58
004 Ampcilin Antibotic 250 50
004 Desprine Headache 100 100
005 Cefximene Antibotic 250 60
32
1NF of Doctor
Docto Doctor Name Speciality Phone no Email
r-ID Doctor Doctor
fname Lname
01 Seifu Abeje Cardiologist 091124569 Seifuabeje5665@gamail.com
7
02 Desaleg Maru Dermatologis 095632536 Desalegn7895@gamail.com
n t 9
03 Selam Mohamme Pathologist 094237869 Selammohammed@gamail.co
d 4 m
04 Rediet Getaneh Orthopedist 097745667 Redietgetaneh@gamail.com
2
1NF of Employee
Emp Empl Employe address Phone no E-Mail
loye oyee e lname cit Kebel
e ID fname y e
01 Eden Solomon DB 02 0983476213 Edensolomon1212@gmail.c
om
02 Mered Demere DB 09 0978543267 Mereddemere23@amail.com
03 Eshetu Selamu DB 04 0922456874 Eshetuselam7@gmail.com
04 Yabsira Lema DB 06 0918114354 Yebsiralema065@gmail.com
Employee Phar
Employee ID Pharmacy ID
33
2NF of Patient
Patient info
Patient ID Patient Patien Date of Address Phone no Patient
fname lname Birth insurance
Doctor info
Patient ID Doctor ID
Employee Phar
Employee ID Pharmacy ID
3NF of Patient
Patient info
Patient ID Patient Patien Date of Address Phone no Patient
fname lname Birth insurance
Doctor info
Patient ID Doctor ID
34
Based on the above samples of 2NF & 3NF we can sketch
the others, but for now we should passed to the other scenario.
Patient:
Patient ID Doctor ID
Employee:
Employee ID Pharmacy ID
Customer:
Customer ID Phone noID
Prescription:
Prescription ID Custom ID Employee ID Patient ID
Medication:
Medication ID Supplier ID Pharmacy ID
Pharmacy:
Pharmacy ID Pharmacy name
Supplier:
Supplier ID Phone no
35
Doctor:
Doctor ID Phone no
CHAPTER: 4
Physical database design
4.1 Physical database design
36
4.2 Implementation and Testing
37
38
39
40
41
4.3 Defining SQL Server backup and restore
The SQL Server backup and restore technique involves steps for creating
backups, restoring databases, and saving a valid backup copy in a different
location. It is a built in SQL Server feature, useful for disaster recovery plans.
The backup and restore process in SQL Server involves three main steps:
1. Backing up the desired SQL Server database
2. Transferring the backup files to another location, usually a remote
location to avoid risk of a hard drive failure along with possible software
problems (e.g. virus attacks)
3. Restoring the database on SQL Server to ensure that the database backup
is valid and to verify integrity.
Restoring a database backup will ensure that in case of a disaster, the restore
process will be successful with no errors or problems in general. The SQL
Server backup and restore process requires constant testing of backed up files to
provide reliable disaster recovery plan. If the backups are not being tested, they
might turn out to be bad files that can’t be used for data recovery.
42
43
44
4.4 Conclusion
45
4.5 Reference
http://www.google.co.in
http://www.wikipedia.com
http://www.doi.org/10.2215/kej.2017.08.008
THE END!
46