i am leacture and i need some educational materil

1. 1
Rift Valley University Bishoftu Campus
Department of Computer Science
Senior Project proposal
On
Rahel Pharmacy Information Management System (R-PIMS)
A Senior Project Research proposal submitted to Department of
Computer Science in partial fulfilment of the requirements for the
BSc Degree of Computer Science
By: -
1. Girma Kebebe
2. Temam Tibbeso
3. Fikadu Legese
4. Ibrahim Abduraman
Advisor: - ______________________
A Project proposal submitted to Department of Computer Science in
partial fulfilment of the requirements for the BSc Degree of Computer
Science
March, 2014/22
Bishoftu

2. 2
Abstract
This system is a web based pharmacy management system that the main Idea of this project is
to design and implement a web based system which will be used by any peoples for giving
information and data about drug. The proposed system changes the existing manual system in
to computerize by identify the existing system problem and improves it. This web based drug
order management system primary aim is to improve accuracy and enhance safety and
efficiency in the Rahel pharmacy. This system manages most drug related activities in Rahel
pharmacy. The system we have proposed is going through stage of life cycles: requirement
gathering, requirement analyzing, system designing, implementing, testing and maintaining.
For requirement gathering we use interview and observation in Rahel pharmacy. For
requirement analyzing and design we use UML modeling and Microsoft office Visio drawing.
And for implementation phase we used object oriented system analysis and design development
methodology. The expected outcome of this system is ability to insert, update, retrieve records,
display, and store and delete drug information from the database. This system is decreasing the
cost and time of data accessing process and it is going to be a user friendly system. It is very
easy to use and less time consuming. The system provides authentication, and this helps to
restrict unauthorized users.

3. 3
Table of Contents
CHAPTER ONE ............................................................................................................................................. 4
1.1. Introduction ......................................................................................................................................... 4
1.2. Background of the Organization.......................................................................................................... 4
1.3. Statement of the Problem ................................................................................................................... 4
1.4. Objectives of the project...................................................................................................................... 5
1.4.1. General objective.............................................................................................................................. 5
1.4.2. Specific objectives............................................................................................................................. 5
1.5. Scope and limitation of the project ..................................................................................................... 5
1.6. Significance of the project ................................................................................................................... 6
1.7. Methodology........................................................................................................................................ 6
1.7.1. Fact finding methodology ................................................................................................................. 6
1.7.2. System analysis methodology........................................................................................................... 7
1.7.3. Design methodology......................................................................................................................... 7
1.7.3. 1. System Design............................................................................................................................... 7
1.7.4. Implementation tools ....................................................................................................................... 8
1.7.4.1. Validation and Testing of the System ............................................................................................ 8
1.8. Feasibility study.................................................................................................................................... 9
1.8.1. Economic Feasibility.......................................................................................................................... 9
1.8.2. Technical Feasibility .......................................................................................................................... 9
1.8.3. Operational Feasibilities ................................................................................................................... 9
1.8.4. Legal Feasibility................................................................................................................................. 9
1.9. Budget and task schedule.................................................................................................................. 10
1.9.1. Time Estimation of the Project ....................................................................................................... 10
Table 1: project schedule.......................................................................................................................... 10
1.9.1 Budget Estimation of the Project..................................................................................................... 10
Table 2: Cost Estimation ........................................................................................................................... 10
1.10. References ....................................................................................................................................... 11
Group Members and Responsibilities....................................................................................................... 12
Table 3: project team management ......................................................................................................... 12
List of Table
Table 1: project schedule.......................................................................................................................... 10
Table 2: Cost Estimation ........................................................................................................................... 10
Table 3: project team management ......................................................................................................... 12

4. 4
CHAPTER ONE
1.1. Introduction
The study consists of support the property (drugs) information is accurately record all the
pharmacy system which was manual as our profession change to computerized way. Currently,
all activities of pharmacy system are going on manually, which lead to wastage of time, labor,
accuracy, and speed. Pharmacy System is the back bone of the medical health sector. So it should
be advanced and computerized to provide fast services for the community and also for other users
of the system like manager, pharmacist, store coordinator and cashier.
1.2. Background of the Organization
The pharmacy was started in 25/06/2005, the name of the organization that we have doing our
final project is Rahel Pharmacy information management system. This organization is placed at
the side of the Zukala Dire Jitu kebele, in Bishoftu city.
1.3. Statement of the Problem
As we gather the information from Rahel pharmacy manager, the current system of pharmacy is
manual system. Due to this, there are lot of problems. To update the record on manual system is
difficult because the record doesn’t have integrated checking mechanism. Therefore to update the
data we should check the inserted data available clearly that are in the paper.
General speaking the manual system of Rahel pharmacy drug management system has the
following problems:
 managing a very large pharmacy with records on papers will be tedious and difficult
to keep track of inventory with regards to the drugs in the stock inside the pharmacy.
 Since it is manual system quantity of drugs available based on the categories and their
functions can’t be easily known. Due to this the patient can’t get the drug they want.
 Difficulty of getting full information about drugs when needed immediately.
 Preparing report for each drug takes long time.
 It is difficult to identify which drugs are out dated or expired.
 The most sensitive data is lost because of they are paper based.
 Most of the time redundant data occur.

5. 5
1.4. Objectives of the project
1.4.1. General objective
The main objective of this project is to develop a Web Based Pharmacy Management System
which solves the above mentioned problems with the existing system.
1.4.2. Specific objectives
In order to achieve the main objective, we have the following specific objectives:-
 Previous System analysis.
 Current System design.
 To create fast and reliable system.
 To design a user friendly interactive system.
 Automating drug selling.
 To check decreasing and increasing items in stock.
 To delete or remove expired drugs.
 Printing the salled drug.
 To generate report with in short period of time.
1.5. Scope and limitation 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. It is
also interested to analyze the system in relation with customer interaction. The scope of this
project is Automation of viewing information about drug online system in order to buy drugs
for Bishoftu city and around here. Generally we come up with this project to implement a new
drug management system which can perform the entire specified task to the pharmacy with
minimum time, effort and resource need in addition with great efficiency and accuracy and
guarantee that the data will not lost or damaged easily.
Therefore the project is bounded on:-
 registering new drug and pharmacists
 Fast data processing and retrieval.
 To delivery drug system for the patient.
 To know expired drug, less quantity of the drug with patient that has credit remains.

6. 6
 To arrange the type of drug
 To access easy by search.
 To delete the item at the expired date.
 The system must be doing like set/update/delete/insert/search drug type of the item.
 Security that can keep the confidentiality of the data at rest as well as at communication
lines.
 Designing user friendly interface
1.6. Significance of the project
This new system that we are going to develop mostly concerned on information that required for
the drugs in pharmacy that enable them to manage the drug information but our system will not
include:
 The system can’t change in to computerized system completely, because it works hand in
hand documentation.
 Our system works only when a database is active and the network is available.
 The system can’t work in offline.
 Blind people are unable to use the system.
 The system does not support multi language.
 The system does not allow online drug shopping.
 No online payment
1.7. Methodology
1.7.1. Fact finding methodology
There are different methods of data collection methods. From those we used the following
methods respectively to collect data from the organization.
 Direct Observation: use this method to get the right information about the
organization and also understand by viewing how the existing system works.
 Interview: through interviewing the manager and another employee of the
organization and we get enough and reliable data which is important to do the project.
 Document analysis: we analyzing the manual resources of the organization how the
current system operates.

7. 7
1.7.2. System analysis methodology
There are different types of software development methodologies from this we used: -
 Object oriented system analysis and design methodology: Is software development
methodology by building self-contained modules or objects. This methodology has the
following futures increased reusability, increased extensibility, proved quality, and
reduced maintenance burden and managed complexity. Due to this we select OOSAD
methodology.
 Software development model: we use is iterative model because in iterative model you
can iterate back if error is occurring in one phase and we can return back to other phase
to fix errors at any phase of the project life cycle.
1.7.3. Design methodology
1.7.3. 1. System Design
System design involves three phases that is Conceptual design, Prototyping, and a detailed design.
 Architectural design. This will involve a database engine to store data, a web server, and
user interface and communication channel for exchanging data.
 Database design: This will involve Entity Relationship Diagrams (ERD). The entity-
relationship data model shows the relationships between the entities involved in the system
together with their attributes and indicates the number of occurrences an entity can exist
for a single occurrence of the related entity. Entity Relationship Diagrams (ERDs) are used
to model both the logical and physical database structure designs. ERDs are user-friendly
and they can provide a unified view of data, which is independent of any data model. ERDs
are also used to identify the data to be captured, stored and retrieved in order to support the
activities performed in the pharmacy management systems.
 Process design; involves the use of Data Flow Diagrams (DFDs). DFDs are charts which
show the movement of data through a system. DFDs are used to provide a detailed
representation of the system components and model the processes and conceptual level
design. DFDs are easier understood by technical and non-technical audiences when
presenting the system.

8. 8
1.7.4. Implementation tools
The prototype of the pharmacy management system will implemented using the following
software and hardware tools.
 Hardware Tools
 Paper, pen
 Computers i.e. Desktop and Laptop
 Flash Disk
 CD RW
 Software Tools
 Windows 10 Operating system: will be used for the system since it is readily available
in laboratories.
 Microsoft office Word 2013: -for documenting the corresponding deliverables
associated with the project
 Firefox, chrome browsers: -since our system is web based, it is very necessary
requirement.
 Edraw max 6.8 and UML star and MS-office Visio 2007: -for designing Unified
Modeling Language (UML) diagrams.
 Avast Antivirus
 xampp Server: - for database system
 Notepad++
1.7.4.1. Validation and Testing of the System
This involves testing the system by using the sample data collected, in order to check the errors.
The main reason for validation and testing is to (i) to ensure that the system meet the
requirements specification. (ii) To ensure that the system operates or functions according to the
demands of the users to satisfy their needs.

9. 9
1.8. Feasibility study
1.8.1. Economic Feasibility
An economic feasibility is a process of identifying the financial benefits and costs associated with
a development of a project. Rahel Pharmacy Information Management System is a worth making
project. This project is economically feasible in every sense that is takes less effortless time and
nominal cost of purchasing the tools for developing the software/web.
1.8.2. Technical Feasibility
It is possible to develop the system using simple platform. The proposed system can be easily
maintained and repaired technically; the system will be powerful to be applied by low skilled
users as much as possible. It is easily accessible by the people who can easily understand natural
languages. All the function of a project for communication can be implemented in the new system.
Hence the system is technically feasible.
1.8.3. Operational Feasibilities
This system is completely operational and can be successfully implemented. Rahel Pharmacy
Information Management System is easy to understand not only for any sophisticated users but
for the naïve users as well. It provides simple ambience in which user can feel free to work faster,
easier and more accurately. Therefore, it can be socially and behaviorally accepted too feasible.
1.8.4. Legal Feasibility
The project team members built the system without violating rules and regulations of the
governments as well as the organization. The system being built is for the importance of
productivity of the organization, so that the project is legally feasible. Legal feasibility determines
whether the proposed system conflicts with the legal requirement or not. Since the project needs
no copyright. Patenting and doesn’t intent to have any relation with anybody else’s intellectual
property right, it can be considered as a legally feasible project.

10. 10
1.9. Budget and task schedule
1.9.1. Time Estimation of the Project
Task name March
2022
March
2022
April
2022
May
2022
May
2022
Project proposal
Requirement
analysis
Design
Implementation
Testing and
maintenance
Table 1: project schedule
1.9.1 Budget Estimation of the Project
Type of Material quantity Each value(birr) Total Value(birr)
Laptop 1 20,000 20,000
Pen 4 15 60
White paper 200 1 200
Desktop 2 8,000 16,000
USB flash 2 300 600
CD RW 1 35 35
print 100 2 200
Taxi transport 4 1,000 4000
Phone call - 1,000 1,000
Using Internet - 1,000 1,000
Total 314 31,353 43,095
Table 2: Cost Estimation

11. 11
1.10. References
1. World Health Organization. World Health Statistics 2011 - Table 6: Health workforce,
infrastructure and essential medicines. Geneva, 2011. Accessed 21 July 2011.
2. Board of Pharmaceutical Specialties, Current Specialties
3. Al-Ghazal, Sharif Kaf (October 2003). "The valuable contributions of Al-Razi (Rhazes)
in the history of pharmacy during the Middle Ages" (PDF). Journal of the International
Society for the History of Islamic Medicine 2 (4): 9–11. ISSN 1303-667X.
OCLC 54045642.
4. Levey M. (1973), ‘Early Arabic Pharmacology’, E. J. Brill; Leiden.
5. History of Pharmacy Web Pages - Sweden´s oldest pharmacies
6. Burke JM, Miller WA, Spencer AP et al. (2008). "Clinical pharmacist competencies"
(PDF). Pharmacotherapy 28 (6): 806–815. doi:10.1592/phco.28.6.806.
7. BPS Approves Ambulatory Care Designation; Explores New Specialties in Pain and
Palliative Care, Critical Care and Pediatrics
8. Strand LM (1990). "Pharmaceutical care and patient outcomes: notes on what it are we
manage". Top Hosp Pharm Manage. 10 (2): 77–84. PMID 10128568.
9. Hepler CD, Strand LM (1990). "Opportunities and responsibilities in pharmaceutical
care". Am J Hosp Pharm. 47 (3): 533–43. PMID 2316538.
10. NBCH Action Brief: Specialty Pharmacy. Specialty Pharmacy December, 2013.
Accessed 27 October 2014.
11. Wild, D. Specialty Pharmacy Continuum Carving a Specialty Niche Within the ACO
Model." Volume 1 (Summer Issue). August, 2012.
12. Shane, RR (15 August 2012). "Translating health care imperatives and evidence into
practice: the "Institute of Pharmacy" report.” American journal of health-system
pharmacy: AJHP: official journal of the American Society of Health-System Pharmacists
69 (16): 1373–83. doi:10.2146/ajhp120292. PMID 22855102.

12. 12
Group Members and Responsibilities
Each part of tasks of the project will be delivered by collaborating with each of the group
members. Each group members have their own responsibility to complete the project
successfully.
The group members and responsibility are:
Table 3: project team management
ID NAME RESPONSIBILITY
0074/10 Girma Kebebe All activities
0072/10 Temam Tibbeso All activities
0212 /10 Fikadu Legese All activities
0016/10 Ibrahim Abduraman All activities