PHARMAHEALTH

SYSTEM
PROPOSAL

PHARMAHEALTH SYSTEM Page | 1

 Table of Contents

Executive Summary.................................................................4

Background of the Company..................................................4

I. System Request...............................................................................5
 Project Sponsor...........................................................5
 Business Need............................................................5
 Business Requirements..............................................5
 Business Value............................................................6

II. Feasibility Study...............................................................................7

 Technical Feasibility...................................................7
 Organizational Feasibility...........................................8
 Economic Feasibility...................................................9-10

III. Project Plan.....................................................................................11

 Project Methodology..................................................11-12
 Work breakdown Structure........................................13-14
 Project Work Plan......................................................15
 Reporting Structure....................................................16
 Staffing Plan...............................................................17
 Gantt Chart.................................................................18

PHARMAHEALTH SYSTEM Page | 2

 IV. Requirement Definition..................................................................19-20
 Functional Requirement.............................................19
 Process-Oriented...................................................19
 Information-Oriented..............................................19


Non-Functional Requirement..................................20
 Operational............................................................20
 Performance..........................................................20
 Security..................................................................20
V. Use Case Analysis..........................................................................21-34
VI. Process Model.................................................................................35-36
 Context Diagram.........................................................35
 Data Flow Diagram.....................................................36

VII. Data Model........................................................................................37

 Entity Relationship Diagram.......................................37

VIII. Architecture Design........................................................................38

IX. Hardware/Software Specification..................................................39-40
X. Interface Design...............................................................................41-76
XI. Physical Process Model..................................................................77
XII. Physical Data Model........................................................................78

PHARMAHEALTH SYSTEM Page | 3

 Executive Summary

This proposal provides an analysis and evaluation of the development system

as to its efficiency and effectively in the transactions and production processes. Way
of analyzing and development include the technical and organizational feasibility
particularly the software cycle. Operational cycle was also need. This proposal
provides easy access and continuous transactions by anytime.

Background of the Company

PharmaHealth Company is one of the leading companies in Pharmaceutical

industry, it has 3 respective offices including; Admin Management Office, Employee
Management Office, and Store Management Office. They are dealing with generic
and brand medications and medical devices. They are subject to a variety of laws
and regulations that govern the patenting, testing, safety, efficacy and marketing of
drugs. This company runs almost decades in service and still counting together with
satisfied customers and investors.

Employees are will mannered and most recommended according to their

expertise as well as the manager and the owner of this company. They have one
goal “to give the care you deserve”. The company works hard to provide millions of
people that need medicine for their health. PharmaHealth is well known entire of
Asia they bring safety standard medicine with the support and help of medicine
expert. They discover, develop, and produce and market drugs, Pharmaceutical
drugs for use as medications to be administered to patient that suffer from sickness
this is to aim to cure them, vaccinate them, or alleviate the symptoms.

PHARMAHEALTH SYSTEM Page | 4

 I. System Request

This chapter illustrates the business reasons and purpose for

developing a system and the value that the system is expected to
provide.

Project Sponsor

The Project Sponsor by Mr. Jose Q. Candia JR.MSCS. He is

the Quality Assurance/Head Director of PHARMAHEALTH COMPANY.
Secondary project sponsors are the Quality Head designated in each
pharmaceuticals branches.

Business Need

This system had been proposed with the hope to improve and
ensure the flow of operations in PharmaHealth Company, to organize its
entry and records, to control the Management of the System which
include the Record Management Office, the Sales Report Management
Office, Payroll Management Office and the Inventory Management Office.
The PharmaHealth Company will have a better and convenient way of
controlling, managing the operations and the processing inside the
Company through this system. A well-chosen system will increase the
Pharmaceutical efficiency, save the valuable time and lead to a better way,
‘Customer Satisfaction Is Our Ultimate Goal ‘.

Business Requirement

Users Especially Administrators will be able to monitor documents

of all the transactions that is happening in the PharmaHealth specially
those events with regards to storing relevant information of medicines,
and also generates report on information as output documents. The

PHARMAHEALTH SYSTEM Page | 5

 PharmaHealth System provides different types of services and those
events with regards to pharmacy transactions. The specific functionality
of this system are as follows.

The features about Pharmacy Administration are:

 Improving processes, product and system.

 Procedure, Instructions and Records.
 Provide online and offline access to all documents.
 Organize and monitors transactions anytime.
 Approves authorized documents.
 Download upload documents.

Business Value

We hope that there will be a decrease of failures within the

Company. No unnecessary anomalies in the management system will
going to happen specifically in the management of the staffs. Also,
with regards to this development, it can be seen as one of the best
technique an employee must possess because it can advantage for
the company against other companies running their business that
needs to focus and spend a hundred percent of attention and efforts
because we talk about health assurance. By summary, this proposed
system will improve efficiency of our service and the ability to produce
a designed or intended result within the circle of the management of
which combined would then open significant and relevant changes in
increasing the profit and good name or reputation of PharmaHealth
Company.

PHARMAHEALTH SYSTEM Page | 6

 II. Feasibility Study

This chapter presents the risk factors and analysis upon

developing the said system to implement it with success.

Technical Feasibility

PharmaHealth System project is technically, lacking’s and other

anomalies causing both high and low risk hazards are still evidently
exists.

Familiarity with the Application

The user of this system can understand, since it has a basic

functions to this application with database system. And also, the user will
have difficulty in using a new method, but after the users have been
clearly introduced the database system, they would find the system easy
and useful since it will have lesser time to do the assigned tasks. The
team is so familiar with this application system, because they are the
one who developed this system, and it can be advantage for the
members of other staff of PharmaHealth Company with their expertise.

Familiarity with Technology

The company has enough knowledge on how to operate a simple

application system but on the back-end side of the system. Thye process
of the business had not been changed totally but sufficiently improved
with the use of technology. At last, there are consultants are willing to
advice and give help in the application occurs, and if the management
could no longer solve the anomalies within the company.

PHARMAHEALTH SYSTEM Page | 7

 Project Size

This project size has a probability.

The project PharmaHealth System is a huge project. This system

has a feature such as attendance for employees, sorting products, and
inputting information’s, calculating sales, inventory and login is
manageable. The project time frame slightly at risk as the business
would still run on such matter. The CREED DEVELOPERS Company is
the responsible for the completion and process of the project.

Organizational Feasibility

The PharmaHealth System project is organizationally feasible,

since it is very aligned to the objectives brought by the Quality
Assurance of the company. From an organizational vision, this project
has a low risk, it is due to the fact that the project is very aligned to the
company’s objectives because it will accelerate the organization and
transactions before. If there are problems or lacking’s that needs to be
improved, immediate actions would then be conducted.

Project Champions

Quality Assurance Director of the PharmaHealth Company Mr.

Jose Q. Candia Jr, MSCS has the power and resources to assume the
project had the condition and assets to succeed.

Senior Management

The Quality Assurance Department of the company has agreed

that the system will be useful. Thus, the department is encouraging
everyone to let and allow the use of the system.

PHARMAHEALTH SYSTEM Page | 8

 Users

The main user of this system are the staffs who are in charge in
the areas of PharmaHealth Company which include the Admin, Store
Manager, Hr manager, Drug Manager, Accountant, and the Employees.
The name and progress of the said company lies in their hands based
on their expertise on the entire processes. They will be the one will be
the proof if the system that is provided by the developers is successful.

Project Economic Feasibility

In this feasibility it presents the cost and benefits of a system.

Table 1. COST-BENEFIT ANALYSIS

2021 2022 2023 2024 Total

Benefits
Increase sales 50,000 50,500 60,000 160,500
Reduction in Customer 10,000 10,000 10,000 30,000
Complaint
Reduce inventory Cost 8,000 8,000 8,000 24,000
Total Benefits 68,000 68,500 78,000 214,500

Development Cost
2 Server 95,000 0 0 0 95,000
2 Printer 20,000 0 0 0 20,000
Software Licenses 10,000 0 0 0 10,000
Server Software 33,000 0 0 0 33,000
Development Labor 42,000 0 0 0 42,000
Total Development 200,000 0 0 0 200,000
Cost

Operational Cost
Hardware 30,000 35,000 35,000 100,000
Software 15,000 10,000 17,000 42,000
Operational Labor 50,000 55,000 55,000 160,000
Total Operational Cost 95,000 100,00 107,000 302,000
0
Total Cost 200,000 20,000 22,000 26,000 268,000
Total Benefits-Total Cost (200,000) 75,000 78,000 81,000 34,000
Cumulative Net Cash (200,000) (125,000 (47,000 34,000
Flow ) )
Return on Investment 12.687% (34,000 /
(ROI) 268,000)
Break Even Point(BEP) 2.58 years (2 years of
negative cash flow +
(47,000 / 81,000 - 58)

PHARMAHEALTH SYSTEM Page | 9

 BEP = That Year’s Net Cash Flow – That Year’s Cumulative Net Cash
Flow / That Year’s Net Cash Flow

BEP = 81,000 – 34,000 / 81,000 = 47,000

81,000
BEP = 2 + 47,000 / 81,000 = 2.580 Years

ROI = Total benefits – Total Cost / Total cost

ROI = 302,000 – 268,000 / 268,000 = 34,000 / 268,000 =

12.687%

Development Cost Operational Cost

 Marketing Analysis.  Expenditures for Staffing.

 System Development  Hardware Maintenance
Training.  Software Procurement.
 Hardware and Software.  Operational Team
 Consultant Fees. Salaries.
 Customer Surveying.  Payroll.

Tangible Benefits Intangible Benefits

 Increased Revenue.  Increased Data Accuracy.

 Reduced Inventory Levels.  Higher Levels of
 Hardware Cost Savings. Customer Service.
 Cash Flow.  Improved access to more
 Software Cost Savings. accurate and timelier
operational data.
 More rapid access to info.

PHARMAHEALTH SYSTEM Page |

10
 III. Project Plan

Project Methodology

The team decided to utilize the iterative waterfall development in developing

the system. Waterfall has specials ways to divide the task and provide feedback
paths from every phase which is analysis, requirement, design, implementation,
verification phases in order to get some idea from the user by developing the system.

Planning

Analysis

Design

Implementation

Verification

System
Version

Figure 1. Waterfall Development Model.

PHARMAHEALTH SYSTEM Page |

11
 Figure 1 shows that in Project Plan, it starts with Planning then all Analyst will
analyze how to execute the Plan. Analyst may will create new plan to work the
project more easily. After Analyzing, they will proceed to make design to the project.

They should meet all needs of the client, if there was changes, they back to
analyze the system if where they put it back to the project. And if the design of the
project is all good now, the maker of the project will start the implementation to the
client with the approval to them.

If the implementation of the Project started, there will be a possible that it has
lot of changes to the project. The Maker or the Infrastructure team will take this job.
They will go back to analyze the possible changes and make the changes of what
clients do need.

PHARMAHEALTH SYSTEM Page |

12
 Work Breakdown Structure

PharmaHealth Development System

Planning Phase Analysis Phase

 Figure 2. Work Breakdown Structure

PHARMAHEALTH SYSTEM Page |

13
 Figure 2 shows how the work of system distribute, as what we said in the
figure 1, making of the project starts with the planning. In planning phase, we will
having a system request to client and to our head to make a system. Then after
system request, feasibility study must be here, to study how to work the system
successfully. And then after that, the main project plan will take place with the
presence of the Project Manager.

Analyst will take place to make analyze of the project after planning, in
analyzing there will be Requirement Definition, Use Case Analysis, Process Model
and Data Model. These terms will help the Analyst to manage more the project more
organize so that Infrastructure team will have basis to make the project.

Design Phase will start to make the project. They design first the Architecture
of the system, Hardware Software Specification, Data and Process Model and
Making of Interface Design. These are the prior plan to the programmers or the
Infrastructure team to start creating the Project.

PHARMAHEALTH SYSTEM Page |

14
 Table 2. Project Work Plan –This work plan serve us the work designation if every each workers of this system.

Tasks Responsible Start End Days Status

Planning Phase Responsible Start End Days Status
Project Sponsor Rene Ray Dipay 02/03/2021 08/03/2021 6 Closed
Identification of
Niecy Reguiras, Jelyn Kilaton,
Organizational Need, 13/03/2021 19/03/2021 7 Closed
Dina Lindog, Jonalyn Tampos
Requirements, Values
Analysis Phase
Technical Feasibility Shenna Mae Adiong 13/03/2021 20/03/2021 8 Closed
Economic Feasibility Shenna Mae Adiong 13/03/2021 20/03/2021 8 Closed
Organizational Feasibility Shenna Mae Adiong 13/03/2021 20/03/2021 8 Closed
Requirements Definition Angelita Romanillos & Janice Sandig 13/03/2021 20/03/2021 8 Closed
Use Case Charlyn Solis & Irish Asumbrado 13/03/2021 20/03/2021 8 Closed
Design Phase
Develop Data Flow /
Romel Cagas Closed
Context Diagram
Develop Architectural Design Elesar Laborte Closed
Develop Entity Relation
Diagram Jhonel Vertudazo & Crisanto Mapalad 13/03/2021 21/03/2021 9 Closed
Develop Interface Design Elesar Laborte Closed
Identify Hardware/
Jhonel Vertudazo & Crisanto Mapalad Closed
Software Specification
Implementation
System Performance Ivy Grace Dianopra Open
Coding Jhonel Vertudazo & Crisanto Mapalad Open
Testing Plan Ivy Grace Dianopra, Romel Cagas Open
Jhomar Etulle,Jhonel Vertudazo,
Software Package Crisanto Mapalad
Open
Develop Modules Jhomar Etulle Open
Report Problem Anna Lee Delos Ama Open

PHARMAHEALTH SYSTEM Page | 15

 Jhomar Etulle
Irish Asumbrado Requirement Analyst Change
Crisanto Mapalad Infrastructure Leader
Shenna Adiong Business Analyst Management Analyst
Jhonel Vertudazo
Assistant

Charlyn Solis
Dina Lindog AssistantAssistant Ivy Grace Dianopra
Assistant

Jonalyn Tampos Staff Angelita Romanillos Anna Lee Delos Ama Staff
Elesar Laborte Staff
Staff

Niecy Reguiras Staff Janice Sandig Staff

Rommel Cagas
Staff

Jelyn Kilaton Staff

Figure 3. Report Structure

In the figure above shows the position set up to organize the team.

Figure 3 shows the Rank and Position of each worker our company. There
are departments in our company to work with this project. Project Manager Rene
Ray Dipay will manage every work of all Departments
PHARMAHEALTH SYSTEM Page |
16
Table 3. Staffing Plan

Role Description Assign to

Project Manager Overseas the project success and Rene Ray Dipay
manage all the different components
which go into the project
Technical Lead Lead to solve problem in terms of Jhomar Etulle,
hardware and software issues. Crisanto Mapalad,
Shenna Adiong
Front-end developer Responsible of contacting the client to Jhonel Vertudazo,
decide and choose the best Interface Elesar Laborte
design that is suited for the clients
need.
Back-end developer Responsible for developing Crisanto Mapalad
system data queries to
support the front end
developer.
Quality Assurance Survey for the user/s feedback. And Irish Asumbrado,
lead make a report for the system upgrade. Janice
Sandig,
Jelyn Kilaton
Quality Assurance Solve for software errors Crisanto Mapalad,
Maintenance and maintaining the quality of Jhonel Vertudazo
a system.
Tester Conduct a manual test to insure that Jonalyn Tampos,
the system works well. Niecy Reguiras,
UI Designer Preparing for User Interface design. Elesar Laborte,
Rommel Cagas
Context/Data Responsible for showing the entities Angelita
that interact with it. Romanillos,
Flow Diagram
Developer Ivy
Grace Dianopra
Entity Responsible of describing or showing Crisanto Mapalad,
how the entities relate to each other. Jhonel Vertudazo
Relationshp
Diagram Developer
Full-Stack developer This can improve solution and provide Crisanto Mapalad,
best suited way to resolve errors. Jhonel Vertudazo,
Jhomar Etulle
Problem Report Assign to make a report for errors and Jhomar Etulle,Ivy
solution. Grace Dianopra,
Anna Lee Delos
Ama

In the Table 3 above it describe the team and each activities to be done according to
assign area.
PHARMAHEALTH SYSTEM Page |
17
 Table 4. Gantt chart

Activities Jan Feb Mar Apr May

Planning

Overall Analysis

Develop Front/ Back End

Enhance UI Design

Develop Context/Data Flow Diagram

Develop Entity Relationship Diagram

Completed System

Test /Training Plan

Documentation

In the table 4 above shows how many months the system must done
according to the plan.

PHARMAHEALTH SYSTEM Page |

18
 IV. Requirement Definition
In this chapter show the requirement that should be used in a system.
Functional Requirements

1. Log in Username
1.1 The username required login form to the user as the user’s details.
1.2 The system can verify if the username is already existed.
1.3 The system required to allow user to save the following input details

2. Search
2.1 The system will allow users to search products sited in POS/BILL, purchase,
livestock, medicines, accounts, salary templates, payrolls and also the
attendance.

3. Review
3.1 The system can view real- time entries of POS/BILL to identify the
following billing totals.
3.2 The system allows users to view medicines status and availability.
3.3 The system allows users to review or add new expenses.
3.4 The system allows users to view purchase status and the total purchased.
3.5 The system allows users to view and show livestock entries.
3.6 The system allows users to view user information and enable to make payment.

4. Purchase
4.1 The system will enable user to create a user’s account that will store on
the user’s data and payment information.
4.2 The system will enable users to specify the options to review item.
4.3 The system will enable users to collect and verify payment information,
once payment is verified, saving process will begin.

5. Update and delete

5.1 The users can edit and the livestock updates.
5.2 The admin can adjust and delete the availability of items.
5.3 The admin can review name, batch expiry date, prices, quality products and
the incomes.
5.4 The admin can update and delete details account.
5.5 The admin can update and delete the salary template.
5.6 The admin can edit and delete theme customization.

6. Add
6.1 The system will allow admin to add new bill total to the customer.
6.2 The system will allow admin to add new purchase product.
6.3 The system will allow admin to add new medicine products.
6.4 The system will allow admin to add and create new account.
6.5 The system will allow admin to add new salary template.
6.6 The system will allow users to add attendance.

PHARMAHEALTH SYSTEM Page |

19
Nonfunctional Requirements

1. Appearance

1.1 The database will have constructed to facilitate search by user’s

medicines, type, availability and price.

1.2 The system will run on any Web Browser

1.3 Due to error interruption, the users will be able to repudiate details

2. Functions

2 1. Users speed will be monitored

2.2 Users satisfies the Service

3. Security

3.1 User information will be secured

3.2 Documents reports of employee will be secured

3.3 Inventory also will be secured

3.4 The system will be secured through Login Form

PHARMAHEALTH SYSTEM Page |

20
V. Use Case Analysis

USE CASE NAME: Login Page ID:UC-01 Priority: High

Actor: Employee, Admin & Store Manager.

Description: The user will login to check and manage the system like purchase, payroll, inventory,
payment and etc.
Trigger: The user will login to the system with their perspective user and password.

Type: External Temporal

Preconditions:
1. The user must input password and username to login
2. The user must use internet connection to login
3. Admin give default username and password, User must change the password before proceeding to
their perspective transaction.
4.
Normal Course: Information for
Steps:
1. User will go visit to website address of the system
2. Then, User will log-in according to their role like Admin, Employee -This system has a
or Store Manager. categories to choose
when you go to login
page

3. User input their Username and Password. -Admin give default

password, it must be
change by User.
4. Lastly, User clicks the login button to proceed to other page.

Alternative Course:

1.

Post conditions:
1. If the User enters to the system with default password, password must change for Security.

Exceptions:
1. If User is computer illiterate, Admin gives form that helps user to interact to the system.

Summary Inputs Source Output Destination

User Name Admin Notice about Attendance Form
successful login page
Password Employee
Store Manager

PHARMAHEALTH SYSTEM Page |

21
USE CASE NAME: CREATE ATTENDANCE ID:UC-02 Priority: High

Actor: Employee, Admin and Store Manager

Description: All workers in the company will have an attendance. Admin will take in-charge
and manage the attendance of all Employees.

Trigger: This process activate when workers of company will go to attendance form after
they login.

Type: External Temporal

Preconditions:
1. All workers should login in the system of the company first.
2. Workers are not allowed to take attendance using another account.
3. After Login in system , workers should go to attendance form

Normal Course: Information for

Steps:
1. User must login in the system first.
2. Then User must go to attendance form and take attendance

Alternative Course:

1. Take attendance in Log form slip

2. Pass the Log form slip to Admin
3.Admin take the system and transfer it to system

Post conditions:

Exceptions:
1. If the User are computer illiterate, Admin will give a Login form slip for their information.
After that, Admin will put the form to system.

Summary Inputs Source Output Destination

User’s Attendance Employee Notice of Attending Main Form
Form
Admin Dashboard
Store Manager

PHARMAHEALTH SYSTEM Page |

22
USE CASE NAME: Create POS/BILL ID:UC-03 Priority: High

Actor: Employee, Admin & Store Manager.

Description: Employee take initiation of creating Points of Sale, Admin & Store Manager will take in
charge of managing and the record of the Sales.
Trigger: This process occurs when employee create Point Of Sales Bill. Then Admin & Store
Manager will record and manage the

Type: External Temporal

Preconditions:
1. Employee must make initiation to create Point Of Sales. Because they are designated to do it.
2. Employee must input the complete information of Point Of Sales.
3. Input of this process must be true.

Normal Course: Information for

Steps:
1. Employee must Login in System first.
2. After, Employee must go to Create Point of Sales and Initiate to
make it
3. Then Admin and Store Manager will receive the record and take
management of it.

Alternative Course:

1. If there will trouble shoot it creating points of Sales, Employee

execute it in papers.
2. Then if the system will work again, Employee will input it
again.
3.

Post conditions:
1. After submitting the Point of Sales, make sure that the information’s are all correct

Exceptions:
1. If Blackout of electricity , All employees make Points of Sales in papers and put it when
the electricity will back
2. If the Employee are Computer Illiterate, use papers instead with the format of Point Of Sales.

Summary Inputs Source Output Destination

Sales Employee Sales Record Admin Department
Sales Summary Store Manage

PHARMAHEALTH SYSTEM Page |

23
USE CASE NAME: Add Purchase ID:UC-04 Priority: Medium

Actor: Admin & Store Manager

Description: The Admin add product purchases

Trigger: Admin request to have additional purchases to Store Manager

Type: External Temporal

Preconditions:
1. The Admin must make request through email or in paper works to the Store Manager
2. User must be log in to the Admin Category
3. Admin must be consistent of adding purchases with their request and it should be
match of what you request by papers that they put in the system
Normal Course: Information for
Steps:
1. If the user is Admin, User must login to the Admin category.
2. Then, Admin will make request to the Store Manager to make
additional purchases by papers or through email.
3. After that , Admin will make Additional Purchases with the a
Approve of Store Manager
4. And Store manager will get the record of Additional
Purchases from Admin.

Alternative Course:

1. If there will be a Blackout , Admin make paper works to make

request to Store Manager
2. Then if the Store Manager approves the request, Admin will make
purchases if the electricity will back.

Post conditions:
1. Admin must input matches of their request to the Store Manager to avoid purchases
corruption

Exceptions:
1. If Blackout of electricity , Admin make Request in papers and put it when the electricity
will back
2. If the Employee are Computer Illiterate, use papers instead with the format of
Adding Purchases but with the approval of Store Manager

Summary Inputs Source Output Destination

Purchase Id Admin Purchase Reciept Store Manager
List of Purchase Purchase Account Purchase Data Table.

PHARMAHEALTH SYSTEM Page |

24
USE CASE NAME: VIEW LIST OF STOCKS ID:UC-05 Priority: Medium

Actor: Store Manager & Admin

Description: The admin create the list of stocks and specifies the stock enter making such
as list of sold stocks, availability of stocks and damage stocks.

Trigger: The admin creates list of stocks is recorded.

Type: External Temporal

Preconditions:
1. The admin view list of stock is recorded by Store Manager
2. The admin view list of stocks by Store Manager and check this input is accurate.
3. The stocks should be match in physical stocks

Normal Course: Information for

Steps:
1. The admin view the list of stocks after Store manager creates it
2. The Admin verifies the list of damage stocks Stocks id
3. The Admin verifies the list of sold stocks List of damage
4. And the Admin verifies the list of availability of stocks stocks
5 List of sold stocks
List of available
stocks
Alternative Course:

1. If the system get damage, the Store Manager creates list of stocks
by papers and put it in the system
2. Admin Verifies the list of damage stocks by manual and physical
inspection
3. Admin Verifies the list of sold stocks by manual.
4. Admin Verifies the list of availability of stocks by manual
5. And Store Manager put it in the system if the system back to the
normal so that it can be view again to the system

Post conditions:
1. The list of stocks is shared in the system
2. The list of the stocks is come from the record and list manager
3. The add admin is notified of date of return stocks and damage stocks
4. Only Store Manager and Admin can view the list of Stocks

Exceptions:
1. If Blackout of electricity, Store Manager record all Stocks by manual and make copy
for Admin.
2. If the Store Manager are Computer Illiterate, create stocks by manual and Give it to Admin
so that they have manual record to view with the approval of Store Manager

Summary Inputs Source Output Destination

List of stocks sold id Admin sold stock Stocks Admin
stocks record
List of damages stock Damage stock record List Stock Manager
List of availability of Record of availability List Record List
stock
List of stock Record of stock form Stock Record Table

PHARMAHEALTH SYSTEM Page |

25
USE CASE NAME: CREATE LIST OF ID:UC-06 Priority: High
MEDCAL INVENTORY
Actor: Admin

Description: The admin create an inventory and specifies inventory information such as
payments, medicine, POS/BILL and other.
Trigger: 1. The admin creates inventory

Type: External Temporal

Preconditions:
1. The admin creates inventory is clear
2. The admin creates inventory is very well done
3. The admin creates inventory is recovered
4.
Normal Course: Information for
Steps:
1. The admin creates inventory
2. The system verifies record of sold medicine Inventory id
3. The system verifies the availability of the medicine List of sold medicine
4. The system verifies record of payments List of available
5. The system verifies record of damage stocks. stocks
6. The system verifies the budget. List of payments
List of damage stock
List of budget
Alternative Course:

1. The admin inventory has records of damage stocks

2. The system gives list of damage stock to the manager
3. The manager fixed the problem
4.
5.
Post conditions:
1. The inventory stored in the system
2. The inventory is come from the recorded of stocks exception
3. The inventory is exclusive for the record and list of damage stocks, availability of
stocks only.
4. The system display message double quotation the inventory is only for pharmahealth
system.

Exceptions:
1. The inventory is exclusive for the record and list of damage stocks, availability of
stocks only.
2. The system display message double quotation the inventory is only for pharmahealth
system.

Summary Inputs Source Output Destination

Inventory id Admin Inventory Admin
List of sold medicines Medicine account Inventory form Inventory table
List of available stocks Stocks account Inventory form Inventory table
List of payments Payments record Inventory form Inventory table
List of damage stocks Stock account Inventory form Inventory table
List of budget Budget account Inventory form Inventory table

PHARMAHEALTH SYSTEM Page |

26
USE CASE NAME: Create List Of Expenses ID:UC-07 Priority: Medium

Actor : Admin

Description: This process shows the expenses of the Company

Trigger: Admin create list of expenses in the expenses form.

Type: External Temporal

Preconditions:
1. Have expenses record
2. Admin must collect all expenses data
3. It must be true and matches with the balance of Company

Normal Course: Information for

Steps:
1. Admin must collect all expense data in every aspect, like
operational expenses. .
2. Create list of Expenses with the collected data
3. And Save it for Financial management purposes

Alternative Course:

Post conditions:
1. Check data if this is true and matches to the data that collected

Exceptions:
1. If Blackout of electricity, Admin create list of expenses by manual and put it in the system if
the electricity will back

Summary Inputs Source Output Destination

List of Expenses Admin Expenses Record List of Expenses Table
Type of Expenses Store Manager

PHARMAHEALTH SYSTEM Page |

27
USE CASE NAME: Create List Of Salary ID:UC-08 Priority: Medium

Actor : Admin

Description: Admin create Salary template for all workers of the company.

Trigger: Admin create list of salary in the list of Salary form.

Type: External Temporal

Preconditions:
1. Admin must collect Daily Time Record of all Workers
2. It must be true and matches with the working days of the Workers
3. Workers must submit other papers for salary request

Normal Course: Information for

1. Admin will collect DTR from workers to calculate the salary Steps:
2. Admin create list of salary
3. And Save it for the preparation for payment .

Alternative Course:
1. Admin will collect DTR from workers to calculate the salary
2. Admin create list of salary by manual
3. Save it for the preparation for payment

Post conditions:
1. Check data if this is true and matches to the data that collected

Exceptions:
2. If Blackout of electricity, Admin create list of manual by manual and put it in the system if the
electricity will back

Summary Inputs Source Output Destination

List of Expenses Admin Salary Record List of Salary Table
Type of Expenses DTR
List of Salary

PHARMAHEALTH SYSTEM Page |

28
USE CASE NAME: Make Payment(Salary) ID:UC-09 Priority: Medium

Actor : Admin, Store Manager

Description: Admin release salary payment to Store Manager first then Store manager will direct give
it to the employees with their payroll.
Trigger: Admin release salary payment to Store Manager

Type: External Temporal

Preconditions:
1.Admin must give copy of list of salary template
2.Admin must not delayed in giving the list of salary

Normal Course: Information for

1. Admin will give the payment of salary to Store Manager Steps:
2. Then Store Manager will directly give the salary to
employee with their respective payrolls .
3. And Store Manager make sure that there are signatures in the
payroll for the record of Payment Salaries
Alternative Course:

Post conditions:
1. After release of Payment Salaries, Employee must have signature to their payrolls for records
purposes

Exceptions:

Summary Inputs Source Output Destination

List of Salary Admin Records of Salary for Record of Payment
Employees Table
List of Employees Store Manager
List of Salary

PHARMAHEALTH SYSTEM Page |

29
USE CASE NAME: Payroll ID:UC-10 Priority: Medium

Actor : Employees

Description: Payroll serves as the document to receive the salary for the employees of the Company

Trigger: Store Manager sends payment to the Employees , and Employees can see their salaries in
the Payroll

Type: External Temporal

Preconditions:
1. Employees must be not always late and tardy
2. Store manager must provide the Payroll of the Employees

Normal Course: Information for

1. Employees Login and go to Payment process Steps:
2. Employees will see the salary that they have.
3. Employees claimed the salary to the Store Manager .

Alternative Course:

Post conditions:
1. If the Salary is lack, make queries to the Store Manager or Admin.

Exceptions:

Summary Inputs Source Output Destination

Admin Payment of Salary Employee
Store Manager Payroll with Signature
List of Salary

PHARMAHEALTH SYSTEM Page |

30
USE CASE NAME: Add Purchase ID:UC-11 Priority: Medium

Actor: Admin

Description: The admin add purchase and store Manager Record it.

Trigger: The admin add Purchase

Type: External Temporal

Preconditions:
1. The Admin add purchase is recorded
2. The admin add purchased is registered
3. The add purchase notifies the purchase and expiry date
4.

Normal Course: Information for

Steps:
1. The admin add Purchase
2. The system verifies the purchase Purchase I.D
3. The system notifies the purchase and expiry date. List of Purchase
4. List Purchase with
5. expiry date.

Alternative Course:

1. The admin add Purchase by manual

2. The system verifies the purchase by manual and physical
inspection
3.If the system back to normal , input the purchases to the system
The system notifies the purchase and expiry date.

Post conditions:
1. The add purchase is stored in the system
2. The list of Purchase is notified of expiry date.
3.

Exceptions:
1. The add purchase is exclusive only as recommended
2. The system displays message “exclusive only as recommend”.
3.
Summary Inputs Source Output Destination
Purchase Id Admin Purchase Admin
List of Purchase Purchase Account Purchase Form Purchase Table.

PHARMAHEALTH SYSTEM Page |

31
USE CASE NAME: ADJUSTMENT OF STOCKS ID: UC-12 Priority: High
Actor: Store Manager and the Admin
Description: The Store Manager will look to the stocks remaining. The system will automatically check the
stock that has been sold out and the available medicine stocks.
Trigger: The Store Manager will adjust for the Point of Sales and for the Add Purchase of the stocks.

Type: External Temporal

Preconditions:
1. The Store Manager should cooperate to the admin to meet the exact lists of the stock’s adjustment.
2. The Store adjustment must be updated.

Normal Course: Information for

Steps:
1. The Store Manager can access the admin. Store Manager ID
2. The system verifies the login management.
3. The store manager can review the lists of the stocks Lists of medicines
to be adjusted. adjusted
4. The store manager can change the lists of the stocks if
there will be a stock that is not yet to be order.
5. The store manage will finalize the lists of stocks to
be adjusted. Lists of adjusted
stocks
Alternative Course:

1. The Store Manager and the Admin did not meet and coincide
the lists of stocks adjustment.
a.)) if the stock is already existed, the system will automatically
reject the same stock entry.

b.)) the system will give information if the stocks already its
minimum and maximum quantity of stocks.
Postconditions:
1. all the purchase and adjusted medicines are fully secured in the systems and,
2. if the files of the medicines are accidentally deleted by the store manager or the admin it can
be restored any time.

Exceptions:
1. the record of the purchased and adjusted medicines can be access only by the store
manager only if,
2. the admin will allow the store manager to access the system.

Summary Inputs Source Output Destination

Store manager ID Store Manager Can Access the system Medicine Records
Lists of medicines Store Manager The Store Manager can Admin
categorize easily trace the Files
List of adjusted and Store manager Hardcopy of a
purchased medicines purchase Medicines
List of quantity of Admin Total Number of
medicines Purchase medicine
List of medicines Employee Recorded in the system
damages
List of Amount of Admin Transparency of record Inventory
expenses

PHARMAHEALTH SYSTEM Page |

32
USE CASE NAME: CREATE INVENTORY ID:UC-13 Priority: High

Actor: Admin

Description: The store manager create an inventory matches with the Admin’s inventory
summary
Trigger: 1. The admin creates inventory

Type: External Temporal

Preconditions:
1. The admin creates inventory is clear
2. The admin creates inventory is very will done
3. The admin creates inventory is recovered
4.
Normal Course: Information for
Steps:
1. The Store Manager creates inventory with Admin’s inventory
2. The system verifies record of sold medicine Inventory id
3. The system verifies the availability of the medicine List of sold medicine
4. the system verifies record of payments List of available
5. the system verifies record of damage stocks. stocks
6. The system verifies the budget. List of payments
List of damage stock
List of budget
Alternative Course:

1. The admin inventory has records of damage stocks

2. The system gives list of damage stock to the manager
3. The manager fixed the problem
4.
5.
Post conditions:
1. The inventory stored in the system
2. The inventory is come from the recorded of stocks exception
3. The inventory is exclusive for the record and list of damage stocks, availability of
stocks only.
4. The system display message double quotation the inventory is only for pharmahealth
system.

Exceptions:
1. The inventory is exclusive for the record and list of damage stocks, availability of
stocks only.
2. The system display message double quotation the inventory is only for pharmahealth
system.

Summary Inputs Source Output Destination

Inventory id Admin Inventory Admin
List of sold medicines Medicine account Inventory form Inventory table
List of available stocks Stocks account Inventory form Inventory table
List of payments Payments record Inventory form Inventory table
List of damage stocks Stock account Inventory form Inventory table
List of budget Budget account Inventory form Inventory table

PHARMAHEALTH SYSTEM Page |

33
USE CASE NAME: Change Password ID:UC-14 Priority: Low

Actor: Admin

Description: The Admin is the only one that can change password of the system, Employees
account and Store Manager’s Account.
Trigger: The admin add Purchase

Type: External Temporal

Preconditions:
1. Changing password with request to the Admin
2. Must have a valid reason for changing password
3. The add purchase notifies the purchase and expiry date
4.

Normal Course: Information for

Steps:
1. Users have a request approval to the admin of changing
password Purchase I.D
2. Admin execute the changing password if approve List of Purchase
3. Admin gives the new password to the User who demand for it List Purchase with
expiry date.

Alternative Course:

Post conditions:
1. Can change password twice a month
2. Make letter request to Admin for reason of changing password if the User exceed 2
changing passwords
3.

Exceptions:
1. Admin forgot password, they can change their own without letter
2. Progammers of the system, they can go through without password with the consent of
Admin

Summary Inputs Source Output Destination

Changing Request Admin Notification of User
Resetting Password
Reason to Change Change Password
Form

PHARMAHEALTH SYSTEM Page |

34
VI. Process Model

Context Diagram

Figure 4. Context Diagram

The Figure 4 shows main process of the system by Diagram. The

process of the starts with these 3 major entities, Employee Entity, Admin Entity and
Store Manger Entity.

PHARMAHEALTH SYSTEM Page |

35
Data Flow Diagram Level 0 DFD

Figure 5.Data Flow Diagram

The Figure 5 shows the flow of the system. Also it shows all the processes of the system and its Data Store

PHARMAHEALTH SYSTEM Page | 36

VII. Data Model

Entity Relationship Diagram

PHARMAHEALTH SYSTEM Page | 37

 VIII. Architecture Design

Client computer
Collect
data
Display

Internet

Admin management Store management

System
Employee management System

Data Based

Figure 6: Architecture Design

Figure 6 shows how the system was construct. It helps to have visual plan of the
System

PHARMAHEALTH SYSTEM Page |

38
 IX. Hardware/Software Specification

Operational Requirement

Table 5

Type of Requirement Definition Requirement

Technical Environment Special hardware, software,  The system will work
Requirement and network requirement over the web
imposed by pharmacy. environment.
System Integration Speed up company process  The system will able
Requirement extent to which the system to view, print, and
operate with the other System past the information.
Portability Requirements The expanse of the system will  Pharma health
need to operate by the System by performing
employee of health center. by any operating
system.
Maintainability Requirement Insuring the system update to  The system must be
improve the needs of up to date in what
environment. company need.
The table 5 above specifies the operation environment in which the system must
perform and how those may change over time. This includes operation systems,
system software, and other information system with which the system must interact.

Performance Requirement

Table 6

Type of Requirement Definition Requirement

Speed Requirement In every performance in its  The system
function must be on time. performance should
be 3 seconds or less
in every affair over
the network.
Capacity Requirement The expected number of user  It must be refer in the
will use. company employees.
Availability and Reliability The availability use of a system  The system must
Requirement operates by the users in which be 12/7.
they can manage.  The system will have
99% uptime
performance.
The table 6 above focuses on performance issues such as response time, capacity, and
reliability. Each requirement must be measurable so that a benchmark comparison can be
made.

PHARMAHEALTH SYSTEM Page |

39
Security Requirement

Table 7

Type of Requirement Definition Requirement

System Value Estimates The system data can estimates  The system in not
the value surrounding of the mission critical, but a
system system is estimated
to cost.
Access Control Requirement Limitations on who can use the 
system and it can be access
data input.
Encryption and
Authentication Requirement

Virus Control Requirement To control the spread of  The user devices it

viruses. must scan.


The table 7 above shows security requirement to be met. Generally security is

the ability to protect to information system from disruption and data loss, whether by an
intentional act a random event.

Hardware and software Specification

Table 8

Area Standard Client Standard Web Server

Operating System  Windows  Windows
 Chrome
 browser
hardware  4.00 GB Disk drive  8.00 GB Disk drive
 Intel(R) Core  Intel(R) Core



The table 8 describes what hardware and software are needed to support the
application.

PHARMAHEALTH SYSTEM Page |

40
 X. Interface Design

ADMIN ACCESS

PHARMAHEALTH SYSTEM Page |

41
PHARMAHEALTH SYSTEM Page |
42
PHARMAHEALTH SYSTEM Page |
43
PHARMAHEALTH SYSTEM Page |
44
PHARMAHEALTH SYSTEM Page |
45
PHARMAHEALTH SYSTEM Page |
46
PHARMAHEALTH SYSTEM Page |
47
PHARMAHEALTH SYSTEM Page |
48
PHARMAHEALTH SYSTEM Page |
49
PHARMAHEALTH SYSTEM Page |
50
PHARMAHEALTH SYSTEM Page |
51
PHARMAHEALTH SYSTEM Page |
52
PHARMAHEALTH SYSTEM Page |
53
PHARMAHEALTH SYSTEM Page |
54
PHARMAHEALTH SYSTEM Page |
55
PHARMAHEALTH SYSTEM Page |
56
PHARMAHEALTH SYSTEM Page |
57
STORE MANAGER ACCESS

PHARMAHEALTH SYSTEM Page |

58
PHARMAHEALTH SYSTEM Page |
59
PHARMAHEALTH SYSTEM Page |
60
PHARMAHEALTH SYSTEM Page |
61
PHARMAHEALTH SYSTEM Page |
62
PHARMAHEALTH SYSTEM Page |
63
PHARMAHEALTH SYSTEM Page |
64
PHARMAHEALTH SYSTEM Page |
65
PHARMAHEALTH SYSTEM Page |
66
PHARMAHEALTH SYSTEM Page |
67
PHARMAHEALTH SYSTEM Page |
68
PHARMAHEALTH SYSTEM Page |
69
PHARMAHEALTH SYSTEM Page |
70
PHARMAHEALTH SYSTEM Page |
71
EMPLOYEE ACCESS

PHARMAHEALTH SYSTEM Page |

72
PHARMAHEALTH SYSTEM Page |
73
PHARMAHEALTH SYSTEM Page |
74
PHARMAHEALTH SYSTEM Page |
75
 XI. Physical Process Model

PHARMAHEALTH SYSTEM Page | 76

 XII. Physical Data Model

PHARMAHEALTH SYSTEM Page | 77