drug store mangement documentation

Drug Management System 2016 June 11, 2016
1
CHAPTER ONE
INTRODUCTION
1. Introduction
Our Application will develop, to implement in an organization’s existing manual system.
This project will replace, and will retain the present functionality available in the current
system. The specific purpose of this system is to store, distribute and process information
about drugs.
The drug Information Management system is manually difficult, because it causes
information inconsistency and data integrity problem. To overcome this information
inconsistency and integrity we need to have a computerized data management system.
Drug management system is a system that used to control the existing system which is
done manually. We have taken the drug management system, to change the existing
system from manually to computer based application system. The efficiency of the
Policing function and the effectiveness with which it tackles the improper and corrupted
managing of drugs depends on what quality of information it can derive from its existing
records and how fast it can have access to it.
1.1 Background
Desktop application is an application that runs stand alone in a desktop or laptop
computer. Contrast with "Web-based application," which requires the Web browser to
run. The term may be used to contrast desktop applications with mobile applications that
run in smartphones and tablets.
Desktop applications relay support all phases of distributing and managing of drugs. Our
proposed desktop application offersto the store an opportunity to search needed drugs on
its storage.

2
Based on the existing manually searching for drugs, the project team decides to change
this manually of searching of drug into a desktop application providing management of
drug and distribution functionality well programmed The store has to input the products
and the desired start and end in time. The system to be designed provides much
information regarding to the drugs. The first frame the user interacts with the front page
that has two buttons those buttons allow the user to login as owner and staff. Owner page
you containing the way to essential to other information’s. It consists of information of
about the general overview of the drugs management system and about staff
information.Staff page you containing the way to essential to other information’s. It
consists of information of about the overview of the drugs management system and
saleing products .
1.2 Statement of problem in drug management system
This project is aimed to automate the drug management system. This project is
developed mainly to manage, distribute and store drugs in an appropriate way. The
purpose of the project entitled as drug management system is to computerize the
Management of drug to develop software which is user friendly, simple, fast, and cost –
effective. It deals with the collection of drugs information, distribution details, etc.
Traditionally, it was done manually. The main function of the system is to register and
store drugs data and retrieve these data as and when required, and also to manipulate
these details meaningfully. The importance:
1. Efficiently maintains the details about the drug
2. Simultaneously updates changes made to any data, item in the entire data base.
3. It is faster than manual system.

3
4. The goal of any system development is to develop and implement the system cost
effectively; user-friendly and most suited to the user’s analysis is the heart of the
process.
5. This function of drug Management Information System deals with registering the
new drug and giving unique batch Identification Number to the drug. This number is
unique throughout the System for identifying the drug.
6. Analysis is the study of the various operations performed by the system and their
relationship within and outside of the system. During analysis, data collected on the
files, decision points and transactions handled by the present system.
7. Different kinds of tools are used in analysis of which interview is a common one.
8. The drugs batch identification number is also created for the distribution of the drug.
This is also a part of registering the drug till it reaches its destination which is the
pharmacy.
1.3 Objective of the project
The ultimate aim of the study is to automate the routine function of drug management
system and overcome the problems associated with the manually function organization.
The aim and objectives are to handle the following;
1. To change the existing manuals system by introducing a computerized
system.overcome the problems associated with the manually function organization.
2. To reduce human dependability and lapses.
3. To design a system for easy information storage update and retrieval.
4. To bring into focus the important of computer in drug management.

4
6. To improve the operational speed for faster calculation of sentences.
7. To provide facility for good access to date store in the data base.
1.3.1 General objective
The general objective of this project is to develop and implement anautomate desktop app
that provides full information and distribution about drugs and with all its inventory
system.
1.3.2 Specific objectives this project
 To prepare reports in simple way.
 To provide secured information.
 To improve data availability
 To update data easily
 To secure the organization data.
 To keep data integrity.
 To keep data consistency.
 To minimize the number of workers those are assigned to one task.
 To save time.
 To retrieve any information regarding the drug in a short period of time.
 To keep track of drug information.
1.4SCOPE OF THE PROJECT
The scope of the project is concentrating on how to manage the drug distribution and its
inventory activities and applications of the drug in easy, efficient, and functional way.
The following lists are in our scope:
 To Register and allow drugs general information.

5
 To allow the staff members and the administrator to login.
 To Keep track of the drug.
 To activate new information sharing among staff,
 To check drug transfer information,
 To Update record of drug,
 To add new records of drug.
1.4.1Significance
Organizations are going through tremendous changes to create environments where
everyone can contribute their best, where customer requirement are not only meet but
exceeded and where strategically planned with competitive advantage, efficiency,
effectiveness, productivity, quality and customer satisfaction are taken as critical success
factors. This study was important in order to give more valuable in servicing organization
with an appropriate drug management system that resolve the problem arises to them.
Some benefits of this project are:
 Time-saving - pharmacist can save their time much; they don’t need to go to all
over the stock anymore.
 Full Access Information – the user can know and compare the latest price and
other related information from each agent specifically.
 Reduced cost – electronic transaction enables faster processing cost, and can help
to minimize errors often associated with paper based systems.
 Attract to new customer and markets – the system provides a new sales channel
opening up many new opportunities for suppliers.
1.4.2 Methodology
A methodology is usually a guideline system for solving a problem, with specific
components such as phases, tasks, methods, techniques and tools. A methodology can be

6
considered to include multiple methods, each as applied to various facets of the whole
scope of the methodology. The research can be divided between two parts; they are
qualitative research and quantitative research.
Qualitative methods, as the name indicates, are methods that do not involve measurement
or statistics. It focuses only the quality of the project that you develop.
Quantitative Method: is a research method that relies less on interviews, observations,
and small numbers of questionnaires, focus groups, subjective reports and case studies
but is much more focused on the collection and analysis of numerical data and statistics.
1.4.3 Requirement in developing the system
1.4.3.1 Software requirements
For successful completion of our system we will use the following software
requirement. These are:-
 MySQLjdbc deriver :-
 Xampp:-
 apache
 Netbean -
 php , and JavaScript application.
 Microsoft Office Word 2013 and Microsoft Word: mac 2011.
 Microsoft Office PowerPoint 2013 and Microsoft PowerPoint: mac 2011.
 Operating system and Windows10 or further versions
 Edraw max 6.0
1.4.3.2Material requirements
 Computer/laptop with more than 320GB hard disk, more than 4GB RAM.

7
 Pencil
 Pen
 CD/DVD
 Paper
 Flash drive
1.5Current system
The existing system of the drug management system in the store works manually (uses
stock management system manually which takes time, human labors, data inconsistency
and integrity). Details of work procedure takes time create work load to the workers,
manager, not reliable and data can be lost.
1.5.1Problems of the Existing system
The problems of the existing system are described using manual system framework. This
framework is used only to identify the problems within an existing information system.
Therefore the problems indicated are the main reason for the introduction of
computerized system. The Existing system has different problems. The problems that
faced the Existing system are:-
 It is difficult knowing materials information from the manual system
 It is difficult to update specific material information from manual system
 It is difficult knowing of total Products stored
 It is difficult knowing which and when the Record manager is taken the material
 It is difficult knowing how many goods In and Out from the Store.
Performance:
 The current working system has a low level of throughput as viewed under
globalization era.

8
 It can only provide required information of the users after a long period of time
(takes a lot of time to perform a specific task).
 Materials registration, viewing information etc.
 It is difficult to produce needed information to the users as required with accurate
time.
 Data is not accurately captured, contains errors
 Data is not flexible – not easy to meet new information needs from stored data
because the databases that are used currently are limited to a specific record.
Security: Too little security or control
 Input data is not adequately edited
 Ethics are breached on data or information – refers to data or information getting
to unauthorized people
 Data privacy regulations or guidelines are being violated
Efficiency: Information generated with some sort of anomalies and there is
no way of checking data redundancy because checking data is manually.
Service: The system is inflexible to new or exceptional situations, changes, and it is not
coordinated with other systems.
1.6Overview of the new system
The proposed system converts the existing manual system in to a computerized drug
management system. This desktop application helpsto easily manage different drugs and
organize data without consuming time. The usercan also accomplish tasks in minimum
time requirement, arrange and manage tasks and user profiles. The new system is

9
designed usingNetbean 7.3 with xamppserver. The system can be able to register new
drugs according to the drug, Updating drug information and approve information and add
drug information it can be able to prepare reports as needed. The Manager should control
the organization wisely and efficiently. User is able to view,apply and approvals any
information that is given by the desktop application. So this new system provides fast and
easy access to the administrators and users, finance. The new system can be useful for
drug registration. It will avoid the complexity and wastage of time that the user. This new
system will have several advantages like: -
 A user friendly interface (the user can use our application easily without
difficulty).
 Fast access.
 Accurate and Clear data storage.
1.6.1Functional Requirements
Functional requirements are the intended behaviors of the system. This behavior may
express as services, tasks or functions that the system is required to perform. Functional
requirement define what the system is supposed to do. Our application will be developed
to Manage and process the data by using the required data base. The database of the
system provides the following functionality:
1.6.1.1 Data entry
The data entry is the functionality that is used to enter the data of the drug in to the
system. The system serves different interface that can manage data entry mechanisms in
drug Management System in drug store.
The main data entries are the following:
 Recording the description of drug

10
 Update data
 Login
 Search the needed drugdata by using their batch no
1.6.1.2 Data processing
The system on input data will provide the following data:
 Saving the product data
 Update data
 Clear the data
 Generating report
 Search requested drug’s data
 Exit
1.6.1.3Report generation
 Total number of product that are sealed and unsealed in the stock
 Products with the required registration date, name, quality, Quantity, Model, cost,
expiry date…etc.
 Total number of drugs that are stored by their pharmacological order
 Total number of drugs that are sale from drug store.
1.6.2 Non Functional Requirements
Non-functional requirement is a requirement thatspecifiescriteria that can be used to
judge the operation of a system, rather than specific behaviors. Non-functional
requirements define how a system is supposed to be. Non-functional requirements are
often called qualities of a system. Other terms for non-functional requirements are
"constraints", "quality attributes”, “Quality goals" and "quality of service requirements".
Qualities, that is, nonfunctional requirements, can be divided into two main categories.

11
1. Execution qualities, such as security and usability, which are observable at run time.
2. Evolution qualities, such as testability, maintainability, extensibility and scalability,
which are embodied in the static structure of the software system.
Performance:
Computer performance is characterized by the amount of useful work accomplished by a
Computer system compared to the time and resources used. The performance of software
is measured in terms of space and time. So it is fast in accepting inputs and displays the
result. Depending on the context, good computer performance may involve one or more
of thefollowing:
 Short response time for a given work
 Rate of processing work
 Low utilization of computing resource
 High availability of the computing system or application
 High bandwidth / short data transmission time
1.6.2.1 Security
In order to make the system safe from an authorized access and modification, the system
uses a log in account to differentiate among the different users of the system on the
organization Side. This enables the system to verify who has logged in using the correct
logging account provided and display the right form associated with that user.
The technology that the system is going to be built on gives a robust security handling
and User authentication facilities. Access is controlled through proper password
verification Facilities which the database and the server require. The security service
provided by the system will maintain the security, confidentiality and integrity of the
system. Users will have their own password and username through which they could gain
access to. The security provided includes giving users a higher confidentiality. Security is

12
addressed using proper authentication. Generally this system introduces a proper
authentication and accountability through proper authentication requirement to that
aspect. Authorization is the mechanism by which a system determines what level of
access particular authenticated user should have to secure data controlled by the system.
The proposed system provides authorization facilities by determining whether a user is
authorized to access a data, a user are authorized to perform an operation and a user is
authorized to perform operation on a resource.
1.6.2.3Usability
Usability is a term used to denote the ease with which people can employ a particular tool
Other human-made object in order to achieve a particular goal. Usability can also refer to
The Methods of measuring usability and the study of the principles behind an object's
perceived
Efficiency or elegance. Usability often refers to the elegance and clarity with which the
interaction with a computer Program. The term is also used often in the context of
products and knowledge transfer. The Primary idea of usability is that an object designed
with a generalized users' psychology and physiology in mind is, for example:
 More efficient to use—it takes less time to accomplish a particular task
 Easier to learn—operation can be learned by observing the object
 More satisfying to use
1.6.2.4Backup
A backup or the process of backing up refer to making copies of data so that these
additional copies may be used to restore the original after a data loss event. These
additional copies are typically called "backups." Backups are useful primarily for two
purposes. The first is to restore a state following a disaster (called disaster recovery). The
second is to restore small numbers of files after they have been accidentally deleted or
corrupted. Data loss is also very common.

13
CHAPTER TWO
LITERATURE REVIEW
2.1Introduction
The use of computers in pharmacy has expanded rapidly over the last 4 years. They have
changed both institutional and community practice dramatically. They have changed both
institutional and community practice dramatically. Computers have automated many of
the traditional technical functions of pharmacist, enabling them to increase their clinical
activities. The working conditions of the community pharmacist have also undergone
unprecedented changes as a result of computerization. For example, prescription refills,
which may account for three quarters or more of drug stores. As the 1990s begin, it is
difficult to find many drug stores which do not have some sort of computer. Many, in fact
have several. Computerization has extended beyond the Pharmacy department into the
remainder of the store. Inventory management, point-of sale information and virtually
any other function within a drug store which lends itself to automation has been
computerized.
Generally, Drug Management System is a system that consists of data entry, retrieval and
stock monitoring facility, tracking drug dispensing pattern, generating of reports and
other. Drug Management System focuses on pharmacy store operation and how it
manages department dispensary (internal). The system covers typical operations like
receiving informationfrom suppliers, processing departments' medication requests,
distributing medication todepartments returning expired medication to suppliers. Drug
Management System is drug stock inventory system that consists of data entry, retrieval
and monitoring stock facility.

14
2.2 Inventory Management
Every organization should be sensitive and wise in dealing with their inventory.
Systematic and efficient management in managing inventory will benefit not only from
the aspect ofmanagement but also other aspects such as reduce costs and production
organization.Thomas C. Harrington (1990) in articles related to "Implementing an
Effective Inventory Management System" emphasizes the element of control important in
effective inventory management. "A professional discipline that is primarily concerned
with the management of document-based information systems. The application of
systematic and scientific controls to recorded information required in the operation of an
organization's business" (Priscilla Emery, 2005)
From the quotes above, we conclude that the control element inventorymanagement is an
important aspect in developing the system associated with inventory management.
Effective inventory control and systematically in an organization can facilitate the
management of the organization in manage inventory, make decisions, plan and control
the flow or stock articles and reports.
2.3 Terminologies in the Inventory
According to Waters (1999) there is some terminology commonly used in inventory.
Table 2.1 shows some of the terminology summarized in table form.
Table 2.1:Terminology in the Inventory
Term Summary of purpose
Stock All items or materials stored within the organization.
Inventory List of items contained in the stock. Refer to the list of stocks and
the stock itself.
Item One of the products kept in stock, is an input in inventory.
Unit Standard size or quantity of the items in the catalog.

15
Control inventory Activities or procedures used to ensure that the correct amount
should be kept in stock.
2.4 Comparison of Current System
Evaluation of the inventory systems are already in the market are intended to identify
relevant information such as features and certain elements in the inventory system to be
applied in drug management system development will be developed soon.
Identifying needs is important in the development of the system. According toHolbrook
(1990), it can be defined as the desire to identify user in determining what needs to be
developed in the system 141. Some specific method and approaches used to obtain
information suitable to be applied in the development of drug management system.
Developers have used benchmarking method to analyze the existing inventory systems
has developed or sold by developers. Benchmarking is defined as the process of
identifying, learning and modifies the normal processes of other organizations in which
only help organizations improve performance (AQPC, 2005).
Comparison was carried out on the current drug management system was developed
which will provide guidance in applying best feature of the current inventory system
(AQPC, 2005). Developers will focus on the two current inventory systems such as Drug
Management System and Magic Inventory Software

16
CHAPTER THREE
SYSTEM DESIGN
3.1 System Design
System design is the process of defining the architecture, components, modules,
interfaces, and data for a system to satisfy specified requirements through system
modeling. One could see it as the application of systems theory to produce development.
The design of this system will be user friendly. It shall be designed in such a way that
employees will be able to navigate easily through the information supplied on the system.
In other words, system design consists of design activities that produce system
specifications satisfying the functional requirements that were developed in the system
analysis process. System design specifies how the system will accomplish. System design
is the structural implementation of the system analysis.
PROJECT
PLANNING
REQUIREMENT
GATHERING
PROJECT
DEVELOPMENT &
INTERFACE DESIGN
IMPLEMENTATION
AND SYSTEM
TESTING
MAINTENANCE
AND
UPGRADING

17
3.2Database Specification
The database system used to implement the back-end of the system is MySQL. Access to
the system was made possible by a graphical interface(phpMyadmin) with a XAMPP.
The database name is drugstore and the structure of the data tables in the database are as
follows:
1. Administrator
2. Drug
3. Casher
4. Company
5. Sale
6. staff
Table 3.1 Administrator
Field Type Null KEY Default Length
first name Varchar No None 50
last name Varchar No None 50
user name Varchar No None 30
password Varchar No None 30
gender Varchar No None 10
Table 3.2 Drug
drug_numb
er
Int No PRI None 10
drug_name Varchar No None 55
Drug_quant
ity
Varchar No None 1000

18
price Varchar No None 10
category Varchar No None 24
Company_
name
Varchar No None 50
image longblob No None
prescription Varchar No None 1000
Table 3.3 Casher
Id_number Int No PRI None 10
First_name Varchar No None 50
Last _name Varchar No None 50
Age Int No None 10
Gender Varchar No None 11
Phone_
Number
Int No None 20
Username Varchar No None 50
Password Varchar No None 50
Image Longblob No None
Table 3.4 Company
Company
name
Varchar No 45
Country Varchar No None 45

19
Email Varchar No None 45
City Varchar No None 50
Phone_
number
Int No None 15
Pobox Varchar No None 40
Fax Varchar No None 50
Tin_
number
Varchar No None 50
Table 3.5 Sale
Field Type Null KEY Default length
Sale_ number Int No None 11
Sale_ date Varchar No None 50
Sale_time Varchar No None 50
Drug_ name Varchar No None 50
Drug_quantity Int No None 11
Seller Varchar No None 50
Price Varchar No None 50
Id_ number Varchar No None 50
First_ name Varchar No None 50
Sur_ name Varchar No None 50
Last_ name Varchar No None 50
Age Int No None 11

20
House
number
Varchar No None 50
Subcity Varchar No None 50
Kebele Varchar No None 50
Mobile Int No None 11
Table 3.6 Staff
Field Type Null KEY default Length
Id_ number Int No None 10
First name Varchar Yes Null 45
Last name Varchar yes Null 45
Geneder Varchar No None 45
Age Int No None 11
Phone_number Int No None 20
Address Varchar No None 45
User name Varchar No None 45
Password Varchar No None 45
Image Longblob No None
3.3Architecture System Diagram
The Proposed subsystem will be implemented in client architecture. User is
can access the system by fill the required input on the login form and then
submit it then request of the user will be sent to database the system will
give response based on the user request . From this description the of the
system is depicted diagrammatically

21
Fig 3.1 Architecture design
3.3 UML (Unified Modeling Language)
 The UML is an international industry standard graphical notation for describing
software analysis and designs.
 When a standardized notation is used, there is little room for misinterpretation and
ambiguity.
 Therefore, standardization provides for efficient communication (a.k.a. “a picture is
worth a thousand words”) and leads to fewer errors caused by misunderstanding.
 The most useful, standard UML diagrams are: use case diagram, class diagram,
sequence diagram, state chart diagram, activity diagram, component diagram, and
deployment diagram.

22
 We only briefly present the basics of UML class diagrams here, and compare them
with ER diagrams. In some ways, class diagrams can be considered as an alternative
notation to ER diagrams.
 Operations aren`t specified in ER diagrams.
3.3.1 Use case Diagram
Use cases describe the behavior of the system when one of these actors sends one
particular stimulus. This behavior is described textually. It describes the nature of the
stimulus that triggers the use case; the inputs from and outputs to other actors, and the
behaviors that convert the inputs to the outputs. The text of the use case also usually
describes everything that can go wrong during the course of the specified behavior, and
what remedial action the system will take. Use case diagrams are used for documenting
the system’s behavior from the user’s point of view. Those diagrams are used to identify
the processes/ functions and the main elements which form the system. The
processes/functions are called use cases and the main elements are called actors. The
diagram also shows the interactions that occur with each of the actors, with each use case.
According to Files, “Use cases are an extremely important aspect of UML modeling.
They allow developers to understand software systems from the user's perspective, and
cause the whole system architecture to be driven by what the user wishes to do with the
system”. Use case diagram (B. Meyer 1997) illustrates a set of use cases for a system, the
actors of these use cases, the relations between the actors and these use cases, and the
relations among the use cases. The UML notation for a use has the following three
elements.
 An oval represents a use case,
 A stick figure represents an actor,
 An arrow between an actor and a use case represents that the actor initiates and/or
participates in the process.

23
Informally speaking, a use case is a story or a case of using a system by some users to
carry out a process. A bit more precisely speaking, a use case describes the sequence of
events of some types of users, called Actors, using some part of the system functionality
to complete a process.
An Actor represents a coherent set of roles that are entities external to the system can
play in using the system, rather than representing a particular individual. An actor
represents a type of users of the system or external systems that the system interacts with.
In our project we have three actors each has its own activities /use cases.
Fig 3.2 Use case diagram
3.3.1.1 UseCase Diagram Description

24
Table 3.7 Use case description for login
User Case Name Login
ACTOR Admin(manager), Staff ,
Pre-condition the actor should have user name and password
Main flow 1. The admin(manager) open the system and click login
2.the system display login screen
3.the user enter username and password to login
4.the system check validity username and password
5. the system login the user in
Post condition User to access the required page
Alternative flow
of event
4.1. the user didn’t type of the correct displays
username/password Or Do not have an account.
4.2. The system display the corresponding error try again
message.
Table 3.8 Use case description for giving username and password for the users
Use Case Name Creating users for username and password information.
Actor Admin(manager)
Description The admin(manager) create an account forpharmacist, and
cashier.And also updates and deletes account.

25
Main Flow 1. The admin open the system and click login.
2. The system display login form.
3. Admin enters username and password.
4. The system checks validity username and password.
5. Admin enters the main page then click on the displayed
main page.
6. The system displays the registration form for the pharmacist
and cashier.
7. The administrator fills the form based on the given data.
8. The system checks valid value for each entry.
9. The system display users registered successfully message.
Post Condition Users given username and password, is performed
successfully.
Alternate Event
Flow
4.1 The admin didn’t type of the correct username and
password or don’t have account.
4.2 The system display error message.
8.1 The admin didn’t fill the correct value or missing some
forms.
8.2 System display error message in order to fill it again or to
fill it order valid value.
Table 3.9 Use case description for viewing drug record

26
UseCase Name view drug record
Actor owner, Pharmacist
Description to secure the information from an unauthorized access; to get full
access in the activity
Pre-Condition Allows the owner to view new changes based on the daily record.
Main Flow 1. Manager and pharmacist open the system and click login.
2. The system displays the login form.
3. The owner and pharmacist enter username and password.
4. The system checks the validity of the manager and pharmacist
username and password.
5. Manager and pharmacist enter the main page and click on view
drug record form.
6. The system display form.
7. Manager and pharmacist display the drug record form.
8. Then display drug record for the manager and pharmacist.
Post Condition owner and Pharmacist notify it is displayed successfully.
Alternative
case
1.The manager and pharmacist didn’t type the correct username
and password, or do not have an account
2. The system display corresponding error and try again message.

27
Table 3.10 Use case description for view transfer information
Use case name Adding drug information
Actor Pharmacist and owner
Description Pharmacist and owner add information of the drug.
Pre-Condition Pharmacist and manager should have username and password.
Main Flow 1. The manager and pharmacist open the system click login.
3. The manager and pharmacistenter username and password.
4. The system checks the validity of username and password
authenticated and authorized.
4. The manager and pharmacist is authenticated and authorized for
the tasks the system display the drug information.
5. The admin initiate register on drug.
6. The system display controller.
7. The admin view transfer desired information
8. The admin view transfer information successfully.
Post Condition The admin view transfer information successfully.
alternative case Step 1-2 remain the same
4.1.The admin didn’t type the correct username and password, or

28
do not have an account
4.2. The system display corresponding error and try again
message.
Table 3.11 use case description for add record
USE CASE name Add record
Actor Admin
Description To secure information
Pre-Condition
the actor should login into the system
Main Flow 1.The admin open the system and click login.
3.Theadmin enters username and password.
5. The admin enter the main page click on add record of drug
information.
7. The admin add record desired information and save it.
8.Theadmin display a message that indicates drug information
adding is successfully finished.
Post condition The admin add record of the drug information successfully.
alternative case 4.1.The admin didn’t type the correct username and password, or

29
message.
Table 3.12Usecase description for deleting records
Use case name Delete records
Actor Admin
Description The Administrator must be able to remove drug information.
Pre-Condition
the admin should login into the system
Flow event 1.The admin open the system and click login.
3. The admin enters username and password.
5. The admin enter the main page click on remove record of the
drug information.
7. The admin remove record desired information and save it.
8.The admin display a message that indicates drug’s information
remove record is successfully finished.
Post condition The admin remove record of the drug information successfully.

30
3.3.2 Class Diagram
The class diagram describes the attributes and operations of a class and also the
constraints imposed on the system. The class diagrams are widely used in the modeling
of object oriented systems because they are the only UML diagrams which can be
mapped directly with object oriented languages.
The class diagram shows a collection of classes, interfaces, associations, collaborations
and constraints. It is also known as a structural diagram.
So the purpose of the class diagram can be summarized as:
 Analysis and design of the static view of an application.
 Describe responsibilities of a system.
 Base for component and deployment diagrams.
 Forward and reverse engineering
alternative case
4.1.The admin didn’t type the correct username and password, or
message.

31
Fig 3.3 Class diagram
3.3.3 Sequence Diagram
Sequence diagrams are used to model the logic of usage scenarios or the description of
the potential way the system used. Sequence diagrams are a great way to validate and
flesh out the logic of use case scenarios and to document the design of the system.
Dormitory system has the following sequence diagrams

32
Fig 3.4 Sequence diagram for admin login

33
Fig 3.5Sequence diagram for create user
Fig 3.6 Sequence diagram for employee

34
Fig 3.7 Sequence diagramfor drug insert
Fig 3.8 Sequence diagramfor Insert Company

35
Fig 3.9 Sequence diagramfor casher
Fig 3.10 Sequence diagramfor record

36
3.3.4 Activity Diagram
UML(Unified Modelling language) activity diagram used to document logic of single
operation or method, a single use case or the flow of business process and show how
those activities depend on one another the field circle represent the starting point of the
activity diagram and the field circle with border represent the end point. The diamond
represent decision point called branch the arrow represent the transition between two
activity and the text on the arrow represent condition that must be fulfilled to process of
the transition.

37
Fig 3.11 Activity diagram for admin

38
Fig 3.12 Activity diagram for casher

39
CHAPTER FOUR
RESULTS AND DISCUSSIONS
4.1 Introduction
Implementation is the realization of an application, or execution of a plan, idea, model,
design, specification, standard, algorithm, or policy.The implementation document helps
users on how to work with the system. It acts as a user manual. And it helps users not to
be confused with the system. It includes sample forms and some selected fragment code.
It gives the users a brief over view of the system.
In computer science, an implementation is realization of technical specification or
algorithm as program, software component, or other computer system through computer
programming and deployment.
4.2System Constraints on Implementation
The main constraints of the implementation are:
 Difficult to get the required software to fit our machines.
 Virus attack on our data during the implementation and testing phase.
 On high level cleanliness personal if browse to low level cleanliness operation
they cannot go back to the high level cleanliness because if we grant is button the
low level cleanliness personal can access the high level operation too
 We tried to put user login within one login frame (combo box system) but the user
are from different class so that we cannot put the user in one system
4.3 System Implementation Structure
System implementation structure will show the overall hierarchy of how the system is
implemented and which operation is visible to whom an authorized person to see.
The implementation structure starts by showing what will be displayed when the desktop
application start to run.
 It shows the user to select from owner and staff. And login into the system as one of
the provide login users.

40
Fig 4.1 Front page
 If we select Owner user to go to the main page of the owner we should entry the
correct username and password this is to authenticate if you are the owner or not.
 String sql = "select* from adminstrater where user_name=? and password=?";
Fig 4.2 Owner login
 If we select staff user log as casher and pharmacist of the staff should entry the
correct username and password this is to authenticate if you are the staff or not.

41
 String sql = "select* from casher (pharmacist) where user_name=? and password=?";
Fig 4.3Staff login
 Main page of the owner in this page there are a link that can create user, view staff
profile, medicine, companies, sale, sale record and search for drug
Fig 4.4Main page of the owner
 This is one of the link of the owner view the profile of the staff, delete the staff and
insert (create user) staff.

42
Fig 4.5 Staff profile
 This is one of the links of the owner view the profile of the Company, delete the
Company and insert Company.
Fig 4.6Company profile
 This is one of the links of the owner and pharmacist view the profile of the drug,
delete the drug and insert drug.

43
Fig 4.7 Drug profile
 Sale page what it do is it fetch drug information when a drug is be sold and it will
record customer information
Fig 4.8 Sale

44
CHAPTER FIVE
CONCLUSION AND RECOMMENDATION
5.1 Conclusion
The development of desktop application Drug Management System involved many
phases. The approach used in is project is a top-down one concentrating on what first,
then how and moving to successive levels of details.
The first phase started with a detailed study of the problems and prospects of a lot of
paper work in drug management. In the course of this study, many problems were
discovered to have hindered the effectiveness of the existing manual system. These
problems, information needs and activities were documented and later used as the basic
phase was concerned primarily with the specification’s drug store sector.
During this phase, strict adherence was made on proven software engineering principles
and practice. To implement this design, a computer program was then written in Android
studio and NetBeans.
It is hoped that effective implementation of this software product would eliminate many
problems discovered during systems investigation.
5.2 Recommendation
It is known that for any meaningful computer based information management to be
integrated into any organization, proper training and oriented has to be given both to the
staff and management. Proper training should be given to the data entry staff on how to
handle the computer hardware especially during backup processes. In particular,
electronic storage media are usually sensitive to change in temperature or pressure and as
such, data can be lost very easily. The staff should also be highlighted on the need and
advantage of the system and how it will equally assist them in their various field of work.
They should also be informed of the cost of maintaining this new system so that they will
handle it with all carefulness. Training materials should not be presented in formal way
but with procedures like policies and form etc., they should be circulated to the
personnel. This will at the end generate appreciation and needed interest to operate the
system.

45
The team recommends the following key points 
 Try to develop the system with more advanced like to connect with internet and to
make easer for the user to buy drugs online to view prescription about drug and so on
 And also make it mobile app like android or ios operating system compatible if it is
like this the user can access the database or webpage from everywhere which is not
comfortable to use desktop or laptop
 For the new developers try to make it more than us keep it up 

46
REFERENCES
List all the materials and resources you used for your project.
Books
1. Bell. D. (2000).Software engineering A programming Approach. (3rd edition) USA:
Pearson Education limited
2. Kimberly, M.S. (1992).The Relational Database Advisor. (1st edition)USA:
WindcrestBooks.
3. Beginning PHP5, Apache, MySQL Web Development, Waley publishing, Inc
4. PHP5 and MySQL® Bible, Tim Converse and Joyce Park with Clark Morgan, Inc
Internet Sites 
 www.google.com 
 www.YouTube.com 
 www.codeproject.com 
 www.sourcecodester.com 
 www.bossesdayText.com
 www.slideshare.com
 www.social network of theworld.com

47
APPENDIXES
Appendixes A. table staff clicked to show data on the table with image
try{
int row =Table_staff.getSelectedRow();
String Table_click=(Table_staff.getModel().getValueAt(row,0).toString());
String sql = "select *from staff where id_number='"+Table_click+"'";
pst=conn.prepareStatement(sql);
rs=pst.executeQuery(sql);
if (rs.next()){
String add1 =rs.getString("id_number");
txt_id.setText(add1);
String add2 =rs.getString("first_name");
txt_firstname.setText(add2);
String add3 =rs.getString("last_name");
txt_lastname.setText(add3);
String add4 =rs.getString("gender");
txt_sex.setText(add4);
String add5 =rs.getString("age");
txt_age.setText(add5);
}
}catch(Exception e){
JOptionPane.showMessageDialog(null,e);
} int row =Table_staff.getSelectedRow();
String Table_click=(Table_staff.getModel().getValueAt(row,0).toString());
try{
conn= javaconnect.ConnecrDb();

48
String sql = "select image from staff where id_number= '"+Table_click+"'";
rs=pst.executeQuery(sql);
if(rs.next()){
byte[]imagedata =rs.getBytes("image");
format=new ImageIcon(imagedata);
image.setIcon(format);
}}catch(Exception e){
e.printStackTrace();
}
}
Appendixes B .login foe admin or manager
String sql = "select* from adminstrater where user_name=? and password=?";
try{
pst.setString(1,txt_username.getText());
pst.setString(2,txt_password.getText());
rs=pst.executeQuery();
if (rs.next()){
String add1 =rs.getString("first_name");
txt_username.setText(add1);
String add2 =rs.getString("last_name");
txt_username.setText(add2);
JOptionPane.showMessageDialog(null,"welcome ADMIN "+add1+" "+add2);
MAIN w=new MAIN();
w.setVisible(true);

49
}
else {
JOptionPane.showMessageDialog(null,"inavalid username or
password","accessdeined",JOptionPane.ERROR_MESSAGE);
}
}
catch (SQLException | HeadlessExceptione){
JOptionPane.showMessageDialog(null,e);
}
close();
}

drug store mangement documentation

Recommended

Recommended

More Related Content

What's hot

What's hot (20)

Viewers also liked

Viewers also liked (9)

Similar to drug store mangement documentation

Similar to drug store mangement documentation (20)

Recently uploaded

Recently uploaded (20)

drug store mangement documentation