Вы находитесь на странице: 1из 60

DEPARTMENT OF INFORMATION

TECHNOLOGY
 INTRODUCTION
 OBJECT ORIENTED SYSTEM ANALYSIS
 OBJECT ORIENTED SYSTEM DESIGN
 SYSTEM IMPLEMENTATION
 TESTING
 CONCLUSION
 RECOMMENDATION

1
 Pharmacy management system is a management
system that is designed to improve accuracy, safety
and efficiency in the pharmaceutical store.
 It is a computer based system which helps the
Pharmacist to improve inventory management, cost,
medical safety etc.

1
 The system allows the user to enter a manufacturing
and expiry date for a particular product or drug
during opening stock and sales transaction.
 The pharmacist may want to generate report for the
movement of drugs in and out of the pharmacy,
getting information about the drugs.

2
3
 At present, manual system is being utilized in the
pharmacy. It requires the pharmacist to manually
monitor each drug that is available in the pharmacy.
 This usually leads to mistakes as the workload of the
pharmacist increases.

3
3
 The pharmacy has a very large customer base.
 These customers tend to visit the pharmacy for services mostly.

 At this period, the number of customers that patronize the pharmacy


is increase, thereby making the workload of the pharmacists much
more tedious.
 This case makes it difficult for the pharmacist to attend the
customers in a short period.

4
4
1.2 STATEMENT OF THE PROBLEM

 Pharmacy management has kept paper record in filing


cabinets.
 Managing a very large pharmacy with records on papers will
be tedious and difficult to keep track of inventories with
regards to the drugs in the store.

5
6
 The pharmacist has to order drugs to reload the
diminishing stock.
 In addition, ordering of drugs is being carried out
manually

6
7
GENERAL OBJECTIVES
 To develop a software system for the effective management of
a pharmaceutical store.
SPECIFIC OBJECTIVES
 To reduce traditional paper base system

 Ensuring effective policing by providing statistics of the drugs


in stock.
 To update the drugs in stock.

7
8
 Improving the efficiency of the system by ensuring
effective monitoring of services and activities.
 To ensure that there exists a level of restricted access
based on functionality and role.
 To provide optimal drug inventory management by
monitoring the drug movement in the pharmacy.

8
9
 To ensure that the system is user friendly.
 To be able to generate report within a specified period
of time.
 Easily search and update information

9
9
 Guha pharmacy, which locate on Piazza Gondar
Ethiopia beside Quara Hotel.
1.5 SCOPE OF THE PROJECT
Store Medicine data
Search Medicine data
Update, delete, and Edit medicine information
Generate report on medicine

10
10
CONT…..

Give alert for the user when medicine item is low


Changing login password
Prepare bill for the medicine
Gives information for pharmacy organization

11
11
1.6 CURRENT SYSTEM

 The current Pharmacy system were manually base


system which is almost all works on the pharmacy
organization is accomplished by papers.
 Medicine data search on the cabinet in order to buy,
audit, and other related works
 The medicine does not known , when the number of
medicine in the pharmacy is low.

12
12
CONT…..

 Data security, the data can be accessed anyone who


entered to the pharmacy house as friends,
 The current system of the pharmacy does not work in
computerised system.
.

13
13
1.7 PROPOSED SYSTEM
The system would improve management services
and productivity.
The system would enhance User/System interface.
The system would be cost effective.
The system would improve information quality and
accessibility.

14
14
1.8 SYSTEM DEVELOPMENT METHODOLOGY

 System development methodology refers to the frame work


that is used to structure plan and control the flow of
developing an information system .
 For this project we used object oriented software
development methodology. It has the following advantages.
 Object-oriented systems development is a way to develop
software by building self-contained modules or objects
that can be easily replaced, modified, and reused.

15
15
CONT…
 Software is a collection of discrete objects that
encapsulate their data as well as the functionality to
model real-world "objects."
 Each object has attributes (data) and methods
(functions).
 Objects are grouped into classes; in object-oriented
terms, we discover and describe the classes involved in
the problem domain.

16
15
1.9 DATA COLLECTION METHODOLOGY

 Data collection is the most important part in our project


to find the main requirement of the system and to
understand how the system does. Among the methods
that were used are:
 Observation: to analyse the organization work processes
 Document analysis: to get information about background
of the organization.

17
15
CONT…
 Interviews: A qualitative form of interview was
conducted in the pharmacy to know the equipment
needed, and the mode of operation of the old system.
 Collecting and analysing existing materials on the
project topic, written by different expert.

18
15
1.10 PROGRAMMING AND DATABASE TOOLS

 PHP
 HTML
 Java script
 CSS
 MySQL
 WampServer

19
15
2. OBJECT ORIENTED SYSTEM ANALYSIS
SYSTEM ANALYSIS:
 The study of sets of interacting entities, including
computer systems analysis
 Is a methodology that involves the application of
systematic approaches to collects facts about an
existing system with the aim of improving it or
replacing it with more efficient system within the
context of the available resources.

20
16
2.1 ANALYSIS OF EXISTING SYSTEM

 Before we analyse the design of the proposed system, we


need to carefully highlight the problems,
 Below, some of the problems associated with the existing
system;
The state of drugs in stock is manually checked.
Mistake of selling expired drugs to customers
Too much workload on employees
Filing cabinet in the pharmacy with paper record.

21
17
2.2 ANALYSIS OF PROPOSED SYSTEM
 From the problems listed in the existing system, the
implementation of the proposed system shall focus on;
Pharmacists having access to the proposed system at any
time.
Ensuring effective policing by providing statistics of the
drugs in stock.
Improving the efficiency of the system by ensuring effective
monitoring of services and activities.
Generating report within a specified period of time.
Reducing the employees workload.

22
18
SYSTEM REQUIREMENT SPECIFICATION
 A requirement specification is used to prepare
requirement specification before starting the actual
design.
 This enables the designer to have a clear idea about the
structure and content of the information system.

23
CONT…

 A well-designed, well-written SRS accomplishes


four major goals:
 It provides feedback to the customer
 It decomposes the problem into component parts.
 It serves as an input to the design specification.
 It serves as a product validation check.

24
FUNCTIONAL REQUIREMENTS
 The function what the system do is
Store Medicine data’s
Search Medicine data effectively
Update, delete, and Edit medicine information
Generate report on medicine
Prepare bill for the medicine
Gives navigation or information for pharmacy
organization
Give alert for the user when medicine item is low
Changing login password

25
19
NON-FUNCTIONAL REQUIREMENTS

 Usability: Any familiar in using windows operation can


operate the system since it has user friendly user interface
 Reliability: The pharmacy system is available based on the
user needs,
 Performance : The pharmacy management system operates its
function in small amount of time which is less than two
seconds
 User interface the user interface is friendly which is easy to
use

26
19
CONT…

 Operation: the pharmacy management system is


operated and controlled by the System Admin for safe
work.
 Supportability : This pharmacy management system
operates in any version of windows operating system.

27
SYSTEM MODELS

pharmacy management system is based different model


view to represent the system in understandable way
such as in
use case models,
object models,
Activity diagrams, and
sequence diagrams.

28
19
USE-CASE DIAGRAMS

show the various activities the users can perform on the


system. The System is something that performs a
function
Use cases
 A use case describes the sequence of events of some
types of users
Actors
 An actor represents a type of users of the system or
external systems

29
19
CONT….

Use case diagram

30
19
SEQUENCE DIAGRAM

 Showing the sequence of interactions among objects and


used to represent or model the flow of messages, events and
actions between the objects or components of a system
 Destroy Element : Represents the destruction of a header
element
 Message: A simple message between header elements

31
19
Sequence diagram for add user
32
19
CLASS DIAGRAM
 A class diagram in the Unified Modelling Language
(UML) is a type of static structure diagram that
describes the structure of a system by showing the
system's classes, their attributes, operations (or
methods), and the relationships among objects (Ambler
2004).

33
19
CONT….

Class diagram
34
19
ACTIVITY DIAGRAM
 Activity diagrams are used to document the logic of a
single operation/method, a single use case, or the flow
of a business process.
 Activity diagrams essentially a flowchart showing
flow of control from activity to activity

35
19
CONT….

Activity diagram for pharmacy manager


36
19
3. OBJECT ORIENTED SYSTEM DESIGN
 System design:-is an abstract representation of a system
component and their relationship.
 Which describe the aggregated functionality and
performance of the system.
 Also the overall plan or blueprint for how to obtain
answer to the question being asked.

37
19
CONT….

 Consists of design activities that produce system


specifications satisfying the functional requirements
that were developed in the system analysis process.
 Specifies how the system will accomplish.

38
19
3.1 DATABASE DESIGN
 Is a shared collection of data that are related or files that
are to meet the immediate need of authorized users.
 These data may be in form of text, numeric, date or
encoded images.
 Database Design can be:-
Conceptual design
Physical design

39
19
3.1.1 Conceptual design
Conceptual design is the first stage in the database
design process.
 The goal at this stage is to design a database that is
independent of database software and physical
details.
 The output of this process is a conceptual data
model that describes the main data entities, attributes,
relationships, and constraints of a given problem
domain.
40
19
CONT...

 It is a high-level data model of the specific


application area.
 It describes how different entities are related to
each other. It also describes what attributes
(features) each entity has.

41
19
ER- DAIGRAM
 An entity-relationship diagram (ERD) is a data
modeling technique that graphically illustrates an
information systems entities and the relationships
between those entities.
 The elements of an ERD are:
 Entities
 Relationships
 Attributes

42
19
3.1.2 PHYSICAL DESIGN

 The goal of the last phase of database design and


physical design is to implement the database.
 At this phase one must know which database
management system (DBMS) is used

43
19
4. SYSTEM IMPLEMENTATION
 System implementation is a stage in system life cycle
whereby a new system is developed, installed and
made ready for use.
 Is a very essential stage in which its success
determines to a great extent the success of the new
system.
 At this instance, after all done the system is
accordingly ready to be implemented (Pharmacy
Management System).

44
19
4.1 SYSTEM TESTING AND DEBUGGING
 System testing deals with the real life testing of the
system to determine how far it has gone in carrying out
the expected task.
 Debugging has to do with fixing of errors encountered
during program execution.
 This was carried out in two phases.
First the source code testing which examine the logic
of the program.

45
19
CONT…

 Secondly,the specification testing which involves the


examination of the system as regard to what it should
do and how it should be done given specific
conditions.

46
19
4.2 SYSTEM DOCUMENTATION

 System documentation is a critical aspect of


implementation process.
 It describes the working of components and serves as
a method of communication between application
developers and users.
 It also helps future analysis of application either by
the same or different system analysts and developers

47
19
4.1.1 HARDWARE REQUIREMENT

A minimum hard disk space of 20GB


RAM size of min. 1GB
 CPU
 Monitor
Mouse
Keyboard

48
19
4.1.2 SOFTWARE REQUIREMENT

 Windows operating system such as Windows 10,


Windows 7.
 E draw max
 Browser
 Snipp tools
 Wamp server

49
19
SYSTEM MAINTENANCE

 Maintenance is a continuous process of making


modifications and upgrading the application.
 There are two different ways by which this
application can be maintained. They include:
 Additive or Enhancement maintenance:
 As business processes change, applications that
support these processes must evolve to reflect these
changes.

50
19
CONT...

 Corrective maintenance:
 This is required in the event that an error occurred
when the application is in use.
 Corrections must be made to changes discovered that
can cause functioning of the system.

51
19
TESTING APPROACH

 In this project work the team has been identified


some basic testing approaches for conducting testing
on the software.
 The following are the approaches selected for testing
this project.
White-box testing: tests internal structures or workings
of a program

52
19
CONT...

 Integration testing: The modules which are found in


our project combined and tested together to see
whether they are working or not.
 System testing: This is to check whether the system
works accurately and efficiently before live
operation commences.

53
19
CONT...

Black-box testing: in this approach the tester


examines functionality without seeing the source code.
Validation: our system can be tested as it can generate
error message when the user insert in appropriate data
type.

54
19
TESTING SCHEDULE

 Unit test :- Throughout the system development


 Black box testing :- After creating systems interfaces
 System test :- After testing unit test up to
implementation
 Integration test :- After testing each module
 White box testing :- After writing code
 Validation testing :- Starting from creating interface
up to implementation

55
19
5. CONCLUSION AND RECOMMENDATION
5.1 CONCLUSION
 Pharmacy management system is designed to improve the
accuracy, enhance safety and efficiency in the pharmaceutical
store.
 It is a computer based system which helps the Pharmacist to
improve inventory management, cost, medical safety etc.
 Effective implementation of this system take care of the basic
requirements of the pharmacy management system because it
is capable of providing easy and effective storage of
information related to activities happening in the fixed area.

56
19
5.2 RECOMMENDATION

 Itis recommended that the new system should be


used with the necessary specifications of the system
requirements and provision for an uninterrupted
connection throughout the operation.
 There should also, basic computer knowledge for the
users to use the system.
 System be improved specially in the area of large
drug managing and bill process.

57
19