CHAPTER IV

PRESENTATION, ANALYSIS AND INTERPRETATION OF DATA

This chapter contains the analysis and interpretation of

all the data gathered by the researchers.

1. Problems Encountered in the Existing System of St.

Lazaru’s Pharmacy.

The St. Lazaru’s Pharmacy is currently using manual

system. By means of observation, investigation and

interviews the proponents found out the following

problems that they encountered:

• Listing all their stocks takes a lot of time because

it is just hand written and they list it only in

the logbooks

• The receipt that they provide is hand written only

and it includes the product name, quantity and

total price.

• The store sometimes become crowded because of the

large number of the customers in the store and the

cause is the slow transaction with the cashier.

• The manager sometimes gets the wrong inventory

reports.

1
2. Development and Description of the Sales and Inventory

System for St. Lazaru’s Pharmacy.

The proponents used the Software Development Life Cycle

(SDLC) for developing the project. Software Development

Life Cycle describe how the project organize based on

its standard and its seven stages. The lay-out of the

project and the scope of the operation are discussed

below:

Phase I – Planning

Phase I was conducted within 10 days, starting from

January 20, 2018 to January 30, 2018. The following

activities were accomplished by the proponents in this

phase of development:

1. The researchers analyzed the existing manual

system of the St. Lazaru’s Pharmacy to know what are the

things that they need for improvements.

2. The researchers also conducted an interview at

the store to get information, to understand their manual

system better and ask them what are the problems that

they encountered about their current manual system.

2
 3. The researchers also observed the facility and

the process that the store doing to transact with the

customer. Figure 1 shows the time table of when the

project started and ends.

SDLC January February March April

Activities 1 2 3 4 1 2 3 4 1 2 3 4 1 2 3 4

Planning

Software
Analysis
System Design

Development

Testing

Implementation

Maintenance

Figure 5

Gantt Chart

Phase II – Software Analysis

Phase II was conducted within 8 days starting from

January 31, 2018 to February 7, 2018 with the following

activities:

3
1. The researchers analyze the problems that encountered

by the company so they can know what to improve on

their current system.

2. The researchers start to identify what tools and

programming languages they’re going to use to develop

the proposed system.

Phase III – System Design

Phase III was conducted within 10 days starting from

February 8, 2018 to February 18, 2018. The activities

done in this phase were the following:

1. The researchers started to create a flowchart to

serves as a reference or guide to the researchers

when developing the proposed system.

2. The flowcharts have different symbols and shapes

and each represent different functionalities. So

that it will be easier to create the flowcharts.

4
 Cashier’s System

START

Get the order or

prescribe of the
customer.

Check the stock of

the product

No

Available?

Yes

Set the
quantity and
total price of
the product.

Payment

Manual issuing of
receipt.

End

Figure 2

Existing System Flowchart

5
 Manager’s System

Start

View whether
stocks or
reports

Stocks Reports

Choose a Choose a
product store report

Check the Check the

stocks of the transactions
product of the store

Manually list
Manually list
and calculate
the quantities
the total
of products
sales.

End End

Figure 3

Existing System Flowchart

6
 Start

HOME

Login
whether
cashier or
manager

Cashier Manager

Get the Whether add

order or products, View
prescribe Reports, Misc.
of the
customer.

Add/Edit of
View Miscellan
Check the products
Reports eous
product at and stocks
the POS

2 3 4
No
Available
?
Yes 6
Add and Set
the
quantity of
End
the product

Figure 4

Program Flowchart

7
 1 2

Add the Product

amount Name, Brand
Database
given of Name,
the Supplier,
customer Expiration
Date, Unit,
Price
Payment
Add
stocks
Print the
Receipt
Product
Name,
Invoice
6 Number,
Date of
Delivery,
Quantity

Edit
Stocks

Product
Name, Brand
Name,
Database Supplier,
Expiration
Date, Unit,
Price

Figure 5

Continuation of Program Flowchart

8
 3 4

Check Stocks Add Brand

Purchased
List Input
Brand

Store Report
Add Unit of
Measure
Add and Set
the Date
Input Unit
of Measure
Print the
Reports
Add Business
Type
6

Input
Business
Type

Add
Employees

Full name,
Username,
Password,
Gender,
Database
Position,
Branch,
Birthday,
Address,
Contact Number

Figure 6

Continuation of Program Flowchart

9
 5

Add Supplier

Name, Business
Type, Address,
Database
Contact
Personnel,
Contact Number

Figure 7

Continuation of Program Flowchart

10
Phase IV – Development

Phase IV was conducted from 2nd week of February 2018 to

4th week of March 2018. Development phase included the

following activities:

The Sales and Inventory System for St.Lazaru’s

Pharmacy used different programming languages such as:

Bootstrap. It helps the researchers to build and

create a responsive website that enables to view on

different devices.

Hypertext Markup Language (HTML). The standard

language for creating webpages and web-application with

the help of CSS (Cascading Style Sheet) in terms of

designs.

PHP. That is widely-used open source general-

purpose scripting language that is especially suited for

web development.

JavaScript. The language that is multi-paradigm and

alongside with HTML and CSS, JavaScript is one of the

three core technologies of World Wide Web content

engineering.

MySQL. The language that has capability of doing

the database management.

11
 Figure 3

Sample Database

Figure 4

Sample HTML Code

12
 Figure 5

Sample JavaScript Code

Figure 6

Sample PHP Code

13
 Phase V – Testing

Phase V was conducted from 1st week of March 2018

to 2nd week of April 2018. The developed system was

tested to check if it reaches the recommended

requirements for the system.

Phase VI – Implementation

Phase VI was conducted from 1st week of March 2018

to 2nd week of April 2018. The proposed system has many

recommendation and suggestions for improvements to be

used by other users.

Figure 7

Admin’s Page

14
 Figure 8

Cashier’s Page

Phase VII – Maintenance

Phase VII was conducted from 1st week of March 2018 to 2nd

week of April 2018. The following activities are the

following:

The researchers continued to check and maintain the system if

there were problems and that needs to be done.

Cost Benefit Analysis

A Cost Benefit Analysis was a process by which

business decisions are analyzed. The benefits of a given

situation or business-related action are summed, and then the

costs associated with taking that action are subtracted.

15
 Existing System Operating Cost (ESOC)

Table 3

Labor Expenses of the Existing System

EXPENSES PER YEAR

LABORER MONTHLY INCOME
(Annually)

Manager P 12,000.00 P 144,000.00

Cashier P 8,000.00 P 96,000.00

TOTAL LABOR EXPENSES P 240,000.00

16
Existing System Operating Cost

Table 4

Miscellaneous Expenses of Existing System

MISCELLANEOUS Expenses per

QUANTITY Price ₱
EXPENSES year

Electricity 1 P 2,000.00 P 24,000.00

Receipt and
3(Bundle) P 300.00 P 3,600.00
invoice

Ballpen 2 (Box) P 40.00 P 480.00

Water bill 1 P 1,000.00 P 12,000.00

Logbook 2 P 80.00 P 960.00

Internet 1 P 1,000.00 P 12,000.00

Stall Rental 1 P 2,500.00 P 30,000.00

TOTAL EXISTING MISCELLENEOUS EXPENSES P 83,040.00

Total of ESOC: P 323,040.00

17
 Proposed System Operating Cost (PSOC)

The following table will show the operational cost for

the propose system.

Table 5

Miscellaneous Expenses of Proposed System

MISCELLANEOUS Expenses per

QUANTITY Price ₱
EXPENSES year

Electricity 1 P 4,000.00 P 48,000.00

Water bill 1 P 1,000.00 P 12,000.00

Internet 1 P 1,000.00 P 12,000.00

Receipt and
5(Bundle) P 200.00 P 2,400.00
invoice

Stall Rental 1 P 2,500.00 P 30,000.00

Ballpen 1 (Box) P 20.00 P 240.00

Ink 1 P 200.00 P 2,400.00

TOTAL MISCELLANEOUS EXPENSES P 107,040.00

The Operational Cost for the Proposed System slightly

increased due to the addition of Electricity.

18
 Table 6

Labor Expenses of Proposed System

LABORER MONTHLY INCOME ANNUAL INCOME

Manager P 12,000.00 P 144,000.00

Cashier P 8,000.00 P 96,000.00

TOTAL LABOR EXPENSES P 240,000.00

Total of PSOC: P 347,040.00

19
 Proposed System Development Cost

Table 7

Software Development Cost

Miscellaneous Quantity Price ₱ Expenses per

year

Professional 1 P 15,000 P 15,000

Fee
Router 1 P 1,500 P 1,500

RJ 45 4 P 5 P 20

UTP Cable 10 P 10 P 100

System Unit 1 P 30,000 P 30,000

(AMD PRO A6-
9500 APU with
Radeon™ R5
Graphics (3.5
GHz up to 3.8
GHz, 500 GB
HDD, 8gb of
RAM)
PLDT WiFi 1 P 1,900.00 P 1,900.00
Repeater
(Wireless-N
2T2R up to
300Mbps,2.4GHz)
Receipt Printer 1 P 3,000.00 P 3,000.00
(384dots/line,
Thermal line,
up to
130mm/sec)
Total: P 51,520

20
 Table 8

Values of Figures for Cost Benefit Analysis Computation

Figure Value

ESOC 323,040.00

PSOC 347,040.00

Development Cost 51,520

Savings 24,000

Interest 5%

Table 9

Cost Benefit Analysis Table

Year Savings Interest PV CPV Mark

1 24,000 1.05 25,200 25,200 X

2 24,000 1.10 26,400 51,600 ✔

3 24,000 1.16 27,840 54,240 ✔

4 24,000 1.22 29,280 57,120 ✔

5 24,000 1.28 30,720 60,000 ✔

21
Payback Period

The formula for Payback Period is:

Payback Period = x + DC – CPV1x / PVfc

Where:

x – Number of X marks

DC – Development Cost

CPV1x – CPV of the last x mark

PVfc – PV of the first check mark.

Payback Period

= 1 + 51,520 – 25,000 / 51,600

= 1 + 0.51

= 1 + 6.16 or

= Payback Period is 1 years 6 months and 16 days

Net Present Value

The formula for Net Present Value is:

NPV = Last year of CPV – Development Cost

Computation:

Net Present Value

= 60,000– 51,520

= Net Present Value is 8,480

22
 Return of Investment

The formula for Return of Investment is:

ROI = Net Present Value / Development Cost * 100%

Computation:

Return of Investment

= 8,480 / 51,520 * 100%

= 0.164 * 100%

= Return of Investment is 16.4 %

3. Assessment of the Respondents on the Characteristics of

the Developed Sales and Inventory System For St.Lazaru’s

Pharmacy.

3.1 Functionality

Table 10 shows the result of the assessment made by the

two sets of respondents on the Sales and Inventory System For

St.Lazaru’s Pharmacy. based on its functionality. From the

table, it can be visualized the overall weighted mean of __

and interpreted in verbal description as “______”.

Table 10

Assessment of the Respondents on Functionality

3.2 Reliability

Table 11 shows the result of the assessment made by the two

sets of respondents on the Sales and Inventory System For

23
St.Lazaru’s Pharmacy. based on its reliability. From the

table, it can be visualized the overall weighted mean of __

and interpreted in verbal description as “______”.

Table 11

Assessment of the Respondents on Reliability

3.3 Usability

Table 12 shows the result of the assessment made by the

two sets of respondents on the Sales and Inventory System For

St. Lazaru’s Pharmacy. based on its usability. From the table,

it can be visualized the overall weighted mean of __ and

interpreted in verbal description as “______”.

Table 12

Assessment of the Respondents on Usability

3.4 Efficiency

Table 13 shows the result of the assessment made by the

two sets of respondents on the Sales and Inventory For

St.Lazaru’s Pharmacy. based on its efficiency. From the

table, it can be visualized the

overall weighted mean of __ and interpreted in verbal

description as “______”.

24
 Table 13

Assessment of the Respondents on Efficiency

3.5 Portability

Table 14 shows the result of the assessment made by the

two sets of respondents on the Sales and Inventory System For

St.Lazaru’s Pharmacy. based on its portability. From the

table, it can be visualized the overall weighted mean of __

and interpreted in verbal description as “______”.

Table 14

Assessment of the Respondents on Portability

3.6 Maintainability

Table 15 shows the result of the assessment made by the two

sets of respondents on the Sales and Inventory System For

St.Lazaru’s Pharmacy. based on its maintainability. From the

table, it can be visualized the overall weighted mean of __

and interpreted in verbal description as “______”.

Table 15

Assessment of the Respondents on Maintainability

Table 16

Summary of Evaluation of the Respondents on the Proposed

System

25
 Chapter V

SUMMARY, CONCLUSIONS AND RECOMMENDATIONS

This chapter contains the summary, conclusions and

recommendations.

Summary

This study is developed and created to help the Sales

and Inventory of St. Lazaru’s Pharmacy and improve their

existing system with the help of modern technology and

applications. This study aims to have a faster and easier

transaction, accurate checking of stocks and inventory of

items and viewing of every transaction and reports. The system

was developed using the System Development Life Cycle (SDLC)

that has seven phases: Phase I – Planning, Phase II – Software

Analysis, Phase III – System Design, Phase IV – Development,

Phase V – Testing, Phase VI – Implementation and Phase VII –

Maintenance.

The proposed system was developed with the help of

different programming languages such as Bootstrap, HTML,

JavaScript, PHP, and MySQL.

The study was conducted using a developmental type of

research. The data were gathered through interviews,

observations, investigations, research in the library and

internet search, and a survey questionnaire.

26
Findings of the study are as follows:

For the results and data gathered, the following

findings are presented:

1. To solve the problems of St. Lazaru’s Pharmacy in

their existing manual system, the researchers came up

with the solution to create a system that can do much

faster transaction, more accurate listing or checking

of stocks, and the managers can easily tract all the

transactions and reports.

2. The researchers developed the system using the phase

of System Development Life Cycle (SDLC). The proposed

system was also viewed by expert and non-expert.

3. The researchers provide a survey questionnaire that

will be answered by expert and non-expert based on

its characteristics: Functionality, Reliability,

Usability, Efficiency, Portability and

Maintainability.

Conclusion

Based on the findings, these are the following

conclusions:

1. The proposed system solved the problem in the existing

system of St. Lazaru’s Pharmacy and improved their

system.

27
 2. The researchers successfully developed the proposed

system by following the System Development Life Cycle

(SDLC).

3. The proposed system meets the ISO 3126-1 criteria

that’s why the proposed system can function well,

reliable, usable, effective, portable, and

maintainable.

Recommendations

Recommendations are based on the interviews, research

and the data gathered by the proponents. The following are

the recommendations for the proposed system:

1. The proposed system needs to be implemented to St.

Lazaru’s Pharmacy to know if the proposed system would

really help to improve the company.

2. The proposed system needs to still have development

and improvement to continue its service.

3. The proposed system needs to be monitored and secured

by the company and should be operated by authorized

personnel only.

28
 Appendix A

SOFTWARE ASSESSMENT FORM

SURVEY QUESTIONNAIRE

Name: ________________________________________________

Position / Designation: ______________________________

Direction: This questionnaire is to be answered by public

user, students and faculty of AMA Computer College,

Cabanatuan City.

Please rate the following statements as basis for your

assessment on the Sales and Inventory System For St.Lazaru’s

Pharmacy. Choose and put a check (/) what is/are applicable

based on verbal descriptions provided for in each item below.

SA = Strongly Agree

A = Agree

MA = Moderately Agree

DA = Disagree

SD = Strongly Disagree

29
1. Functionality

STATEMENT SA A MA DA SD

a. The system allows the manager to

add and edit products.
b. The system can print receipts and
sales reports.
c. The system allows the manager to
view all the transaction, stocks
and reports.
d. The system can notify the manager
if the product is running out of
stock.
e. The system allows the manager to
view the stocks and reports of
other branches.
2. Reliability

STATEMENT SA A MA DA SD

a. The system can provide accurate

information about the products.
b. The system gives more convenience
to the employees.
c. The system can give manager
accurate reports when checking
stocks.
d. The system shows the expiry date
of the product.
e. The system shows the date when
will the stocks be delivered.

30
3. Usability

STATEMENT SA A MA DA SD

a. The system is a user-friendly.

b. The system does not require an

advance computer skill.
c. The system is well-organized

d. The system can be used without

being oriented on how to use it.
e. The system can organize products
and transaction easily.

4. Efficiency

STATEMENT SA A MA DA SD

a. The system can save all the

transactions.
b. The system saves time for manager
and cashier.
c. The cashier can transact faster
to customers.
d. The system can keep all the
records and data’s.
e. It lessens the time of the
manager to determine the stocks.

31
5. Portability

STATEMENT SA A MA DA SD

a. The system can access in any

device.
b. The system can access anywhere
and anytime as long as there is
an internet connection.
c. Sales and Inventory can be done
thru online.
d. The system can run in any
browser.
e. The system can access through
smartphone.

6. Maintainability

STATEMENT SA A MA DA SD

a. The system can be used for a long

period of time.
b. The system allows the manager to
backup and restore.
c. Transactions are retrievable.

d. Only the authorized personnel can

access the system.
e. The system is easy to maintain.

Thank you very much!

John Levi Magdaraog

James Bryan Mateo

Timothy John Miranda

_____________________
Researchers

32
 Appendix B

SAMPLE CODE

<?php
//CONNECT AND GET THE DATABASE DATA
require '../core/dbconfig.php';
//DATE and TIME of CURRENT.. FORMATED
date_default_timezone_set("Asia/Manila");
$now = new DateTime();
$cNowDate = $now->format('F d,Y h:i:s A');
//SQL CONNECTION QUERY STATEMENT PREPARATION
$qry = $con->stmt_init();
// VARIABLES OF DATA
$bID = $_SESSION['branch'];
$uID = $_POST['uID'];
$prdID = $_POST['as_prdName'];
$ivNum = $_POST['as_ivNum'];
$deliver = $_POST['deliver'];
$d = new DateTime($deliver);
$dd = $d->format('F d, Y');
$qty = $_POST['qty'];
//SQL QUERY's
//References and Legendes
/*
ivNum = Invoice Number
uID = Shipping manager who added the Stocks to a specific PRoduct
prdID = to Specify the PRODUCT to products table on to the databse
*/
//SELECT QUERY
$s_product = "SELECT a.genName, b.uPrice, c.ivID FROM products a LEFT
JOIN product_details b ON b.prdID = a.prdID LEFT JOIN invoice c ON
c.prdID = a.prdID WHERE a.prdID='".$prdID."' ";
//INSERT QUERY
$i_stock = "INSERT INTO invoice(ivNumber, prdID, ivDate, qty, uID,
branch_id)
VALUES('".$ivNum."','".$prdID."','".$dd."','".$qty."','".$uID."','".$bI
D."')";
// PROCEED THE ACTION TO ADD/INSERT DATA TO DATABASE
if($qry->prepare($i_stock)){
$qry->execute();
audit($_SESSION['usrID'], $_SESSION['username'], "Added ". $qty ."
to product number ".$prdID, $_SESSION['branch']);
//SELECT THE PRODUCT SELECTED ON COMBO BOX
if($qry->prepare($s_product)){
$qry->execute();
$result = $qry->get_result();
if($result->num_rows > 0){
while($row = $result->fetch_row()){
//THIS PROCESS is TO GET THE PRODUCT PRICE TO INSERT THE TOTAL AMOUNT
OF INVOICE
$prdPrice = $row[1];
$invoice = $row[2];

33
 //UPDATE QUERY
$u_stock = "UPDATE invoice SET uPrice = '".$prdPrice."'
WHERE ivID='".$invoice."' ";
$u_product = "UPDATE product_details SET qty =
qty+'".$qty."' WHERE prdID='".$prdID."' ";
//UPDATE THE PRODUCT TOTAL AMOUNT
if($qry->prepare($u_stock)){
$qry->execute();
if($qry->prepare($u_product)){
$qry->execute();
echo "Success!";
}
}
//END OF UPDATE STOCK
}
}
//END OF SELECT PRODUCT
}

34
 Bibliography

Nations, Improve Your Understanding of Web Applications

https://www.lifewire.com/what-is-a-web-application-3486637

Budiu, Mobile: Native Apps, Web Apps, and Hybrid Apps

https://www.nngroup.com/articles/mobile-native-apps/

Alex Chaffee, what is a web application (or "webapp")?

http://www.jguru.com/faq/view.jsp?EID=129328

Tan, Library System with Web and Android based OPAC

http://www.studymode.com/essays/Library-System-With-Web-

And-38962705.html

35