Chapter 4

Methodology

This chapter describes the methodology of both research and development. The

research methodology included the data collection tools used while the development

methodologies included the system development techniques and tool in gathering

requirements. Also included in this chapter is a finalized detailed project schedule with

deliverables to be achieved at the end of the entire project.

Research Method and Techniques

Descriptive Quantitative method is a comprehensive summarization in everyday

terms of specific events experienced by individuals or group of individuals. The

proponents conducted descriptive quantitative methods to collect as much data to capture

all the procedures in the event. This method can gather all information’s that the

researchers need to be inserted in the proposed system. It helps the researchers to know

the processes inside the establishments in Barangay Patubig.

The proponents used the ISO/IEC FURPS Software Quality Characteristics to

develop the proposed project. FURPS represents a model for classifying software quality

attributes: functionality, usability, reliability, performance, supportability.

Data Gathering Instruments

The proponents used the following capability in gathering data.

Observation. The proponents gathered information by asking the employees

about their current process in the different establishments in Barangay Patubig. The

proponents observed the different establishments in Barangay Patubig on how they

perform contact tracing. The proponents observed that the staff provided thermal scanner.

They are recording it using pen and paper and keep it in case there is a Covid outbreak.

Survey Questionnaire. The proponents gathered responses from the respondents

using a written medium. First, the staff tested and used the proposed system and then the

proponents presented a questionnaire that contains the functionality of the system, if the

system is usable, if it’s reliable to use, if the system performance are all good and if

security of the system are secured. The proponents used the ISO/IEC standards to be able

to measure the develop system using the following FURPS: functionality, usability,

reliability, performance and supportability.

Internet Research. The proponents also conducted internet research to gather

more data and topics that are related to the study. The researchers also used some

websites such as Google Scholar, IEEE xplore, Sci-Hub, Sciencedirect, Researchgate and

etc. The proponents used this websites to have more ideas related to Contact Tracing

System and to get more ideas on what system they should develop to satisfy the needs of

their beneficiary.

Interview. The proponents conducted an interview to Saiver 668 store. Ms.

Geraldine Baltazar and Mr. Jerry Vergara are the interviewees. Ms. Geraldine Baltazar is

the one responsible for the point of sales and Mr. Jerry Vergara is the one who often do

the inventory. This interview was done to have more ideas and to understand the problem

of the current process of the Saiver 668 Store.

Systems Development Process

With this study, the researchers used the Agile Modeling Software Development.

This method supports the simplicity of the flow of this study. Agile modeling is a

practice-based methodology which aims to provide thorough information of the project,

but not to the point of having an over-complicated and unnecessary details. 

 In Agile Modeling driven development, the researchers distinguished the high-

level scoped problems and requirements needed and used it to process the flow of the

study. With this method being used, it made the flow of the work more accurate, while

retracting data that are irrelevant and updating or inserting new and more significant

materials needed by the study.  This simple method acquires the best data needed for the

system and documentation to fulfill its requirements.

Figure 4.1 Agile Methodology

 Initial Requirements Envisioning. It is where the roots of the study start and

where the researchers gathered the major data needed by the study.

In this phase, the researchers gathered personal data based on contact tracing

form, the Estbalishments’s business process, the general information of the

Estbalishments’s organizational team, and the background information of the business

that will support the start of the project. This is the phase where the bulk of the details are

accumulated and retracted later.

Iteration Planning. It is the part where the computer program and project

documentation are being plotted and planned. 

In this phase, the details and information that are gathered during the first phase

such as unnecessary processes are being filtered and updated for the gain of the study.

The time and schedule for making the study are being set. The process of the current

Contact Tracing of the Establishment is being analyzed and the general improvement is

being plotted following the business’s current process.

Modeling Development and Analysis. The plan is being applied and the

construction of the documents and program starts. This is the critical time where data are

being filtered one-by-one; whether it is needed or not.

It is where the researchers started the technical work after gathering the

requirements and information from the planning that has been done in the previous

phases. This phase is where the computer program using Microsoft Visual Studio 2012

has been developed and simulated, following the documentation of the study.
 Testing and Analysis. It is where the study is being tested for problems, failures,

or incorrect practices or flow that may mislead the flow of the process.

In this phase, the computer program that is being developed according to the

standards is debugged and updated for new features that the study needed, as well as the

revisions of the documents of the study. This is where the biggest period the project went.

It took numerous trial and error, deletion of old data to update it with new and more

eminent data to develop the study. This process is also where the researchers allowed the

client to have a test run on the system and afterward the client will answer a survey that

will determine if the system met the requirements and standards.

Production. It is where the study has already been refined and ready for

production and demonstration for the client. In this phase, the researchers have

successfully fulfilled the prerequisites of the study. The project has already been

demonstrated and deployed for the client to use.

Requirements Analysis

Economic Feasibility. It shows wethear the proposed project can be funded by

the beneficiaries since the project can help the Barangay to improve their Contact Tracing

or if the proposed project is possible to implement in different Establishments in

Barangay Patubig which has difficulties in their current manual process.

Operation Cost. Operation costs are the total expenses that related to the

operation of the business.

 Table 4.1
Operation Cost (Existing manual process)
Items Quantity Unit Total
Price
A. Personnel staff (It is already
included in
their salary)
B. Supplies Log book 2 85.00 170.00

Ball pen(5 each) 1 dozen 50.00 50.00

Ink 2 335.00 335.00

(per
month)
Folder 1 dozen 10.00 120.00

Ream 2 reams 200.00 400.00

Bond paper(short)
Total Supplies Cost 1,075

C. Equipment Desktop Computer 2 14.500.00 29,000.00

Printer 1 7,000.00 7,000.00

(Already
acquired by
the client)

Stapler 1 330.00 330.00

Wired 1 838.00 838.00

Barcode Scanner
Total 1,168.00
 Equipment Cost
Summary A. Personnel 0.00
B. Supplies 1,365.00
C. Equipment 1,168.00

Total Annual Cost 2,533.00

Table 4.2

Operation Cost (Proposed Project)

Items Quantity Unit Total

Price
A. Personnel Staffs (It is
already
included
in their
salary)
B. Supplies Ream bond paper 2 reams 200.00 400.00

Staple Wire 2 boxes 20 40.00

Ink 2 335.00 335.00

(per
month)
Folder 1 dozen 10.00 120.00

Total Supplies Cost 895.00

C. Equipment Wireless Barcode 1 1,100.00 1,100.00

Scanner
RFID Reader 1 400.00 400.00
Desktop Computer 2 14.500.0 29,000.00
0

Printer 1 7,000.00 7,000.00

(Already
acquired
by the
client)
Stapler 1 330.00 330.00
Total Equipment 1,830.00
Cost
Summary A. Personnel 0.00
B. Supplies 895.00
C. Equipment 1,830.00
Total Annual Cost 2,725.00
Table 4.3

Operation Cost (Project Development)

Items Quantity Unit Total

Price
A. Hardware Laptop 1 30,000.00 30,000.00

Laptop Specs. Processor: Intel

Core i5-8250 CPU
@ 1.60GHz (8
CPU’s), ~ 1.8GHz
RAM: 6gb Memory
OS: Windows10
Home Single
Language 64-bit
(10.0, Build 16299)
Hard Disk: 500gb
HDD
Printer 7,000.00 (Already
acquired by
the client)
Total Cost 0.00
B. Software SQLServer 1 35,000.00 (Already
Management acquired by
Studio 2012 the client)

Total Cost 0.00

C. Labor Programmers Per 12,000.00 72,000.00
Salary Month
(adv. 6
months)
Total Cost 72,000.00
D. Supplies Ream bond paper 1 230.00 230.00

Printer Ink 1 335.00 335.00

(Already
acquired by
the client)
Total Cost 0.00
Summary A. Hardware 0.00
B. Software 0.00
C. Labor 72,000.00
D. Supplies 0.00

Total cost 72,000.00

 Cost Benefit Analysis. Project cost benefits shows that the existing manual

process is 2,533.00 pesos and the cost of proposed project is 2,725.00 pesos It has an

annual cost of 192.00 pesos. The proposed project will only cost 192.00 pesos to produce

a system that will help the company through their current manual process.

Table 4.4
Project cost and Benefits
Existing manual process 2,533.00

Proposed Project 2,725.00

Annual Cost 192.00

Table 4.5
System Development Cost Analysis
Proposed System 2,725.00

Development Cost 72,000.00

Total Annual Cost 74,725.00

Operational Feasibility. This will measure how well the proposed new system

solves the problems and how it satisfies the requirements identifies in system phase

development. The proposed project will help the company to improve their manual

process of doing the inventory and make it electronically. Performance tracking can also

help them because it can minimize their work since they grade their staff by just

observing them and it will take time to do it. By using the proposed project, they can

track the performance of the staff using the assist points coming from the price of the

products that the customers bought.

Fishbone Diagram. This diagram shows the causes and effects that will be

encountered by the proposed system.

 Figure 4.2 Fishbone Diagram

Schedule feasibility. Schedule feasibility ensures that a project can be completed

before the project or technology becomes obsolete or unnecessary. The proponents

planned the schedule on when they will do the project. The proponents planned to finish

the project within 6 months starting from August 2019 to January 2020. Unfortunately

the project was not finished on time, instead the project was finished on February 2020.

Gantt Chart. Gantt chart is a type of bar chart that illustrates a project schedule.

It illustrates the start and finish dates of the terminal and summary of elements of a

project.
 AUG SEPT OCT NOV DEC JAN FEB MAR APRL
Plan of Activities
1 2 3 4 1 2 3 4 1 2 3 4 1 2 3 4 1 2 3 4 1 2 3 4 1 2 3 4 1 2 3 4 1 2 3 4
Strategy Planning
Data Gathering
System Analysis and
Design
Chapter 1-Introduction
Introduction
Project context
Purpose and description of
the project
Objectives of the project
Scope and limitations of the
project
Significance of the project
Chapter 2 –
Review of Related
Literature and Studies
Theoretical background
Related literature
Related studies
Chapter 3 –
Technical Background
Technicality of the project
Details of the technologies
to be used
How the project will work?
Chapter 4 –
Methodology of the Study
Research Methods and
Techniques
System Development
Process
Requirement Analysis
Requirements
Documentation
Design of Software
Chapter4.6
Table 5 – Summary,
Discussion &
Recommendation
Gantt Chart of Activities(Documentation)
Table 4.7
Gantt Chart of Activities (Proposed Project)
Plan of AUG SEPT OCT NOV DEC JAN FEB MAR APRIL
Activities 1 2 3 4 1 2 3 4 1 2 3 4 1 2 3 4 1 2 3 4 1 2 3 4 1 2 3 4 1 2 3 4 1 2 3 4
Strategy
Planning
Data
Gathering
System
Analysis and
Design
Part 1- File
Maintenance
Account
Management
Inventory
Management
Point of Sales
Part 2 -
Transactions
Sales
Transactions
Inventory
Maintenance
Staff Points
Management
Stocks
Management
Part 3 -
Reports
Dashboards
Records
Requirements Documentation

This section presents the initial design of the system by discussing its major

components and their interactions. These components and their interactions are

graphically represented using design tools such as input-process-output model, data flow

diagram, system flowchart and use case model.

Input – Process – Output Model. This will show how the proponents gather data

and information and turn into a process of system and produce an output.
 Figure 4.3 Input-Process-Output

Data Flow Diagram. It illustrates how data is processed by a system in terms of

inputs and outputs. As its name indicates, its focus is on the flow of information, where

data comes from, where it goes and how it gets started.

Figure 4.4 Data Flow Diagram Level 0

Figure 4.5 Data Flow Diagram Level 1
Figure 4.6 Data Flow Diagram Level 2
 System Flow Chart. System flowcharts are a way of displaying how data flows

in a system and how decisions are made to control events. System flowcharts show

decisions that change the flow of program logic. 

Figure 4.7 System Flow Chart (Login)

 Figure 4.9 System Flow Chart (Point of

sales)

Figure 4.8 System Flow Chart (Business

Dashboard )
 Figure 4.11 System Flow Chart (Cancel Transaction)

Figure 4.10 System Flow Chart (Cancel Item)

Figure 4.12 System Flow Chart (Inventory)
 Figure 4.13 System Flow Chart (Supplier and

Restocks)

Figure 4.14 System Flow Chart (Add Product to Supplier)

 Figure 4.15 System Flow Chart (Receive Order)

Figure 4.16 System Flow Chart (Order History)

 Figure 4.17 System Flow Chart (User Accounts)

Figure 4.18 System Flow Chart (Transaction)

Figure 4.19 System Flow Chart (Employee Overview)
 Use Case Diagram. It is a graphic depiction of the interactions among the

elements of a system.  It can identify the different types of users of a system and the

different use cases and will often be accompanied by other types of diagrams as well. The

use cases are represented by either circles or ellipses.

CHECKING
INVENTORY

RESTOCK PRODUCTS

MANAGE INVENTORY

DECLARE PRODUCTS
FOR SUPPLIERS

RECEIVE PRODUCTS

VIEW RESTOCK
HISTORY
INVENTORY

Figure 4.20 Use Case Diagram

 MANAGE POS

TRANSACT WITH
CUSTOMERS

INPUT PRODUCTS

PROCESS PAYMENTS
OF POS

Figure 4.21 Use Case Diagram

CASHIER

MANAGE USERS

MANAGE POS

MANAGE REPORTS

MANAGE/MODIFY
PRODUCTS

CHECKING
INVENTORY

MONITOR SALES

ADMIN&SUPERVISOR

Figure 4.22 Use Case Diagram

Design of Software

Design Software is the process of designing the elements of a system such as the

architecture, modules and components, the different interfaces of those components and

the data that goes through that system. It also includes the process of defining software

methods, functions, objects, and the overall structure and interaction of codes so that  the

resulting functionality will satisfy users requirements.

Entity Relationship Diagram or ERD. An entity relationship diagram (ERD)

shows the relationships of entity sets stored in a database. An entity in this context is an

object, a component of data. An entity set is a collection of similar entities. These entities

can have attributes that define its properties.

Figure 4.23 Entity Relationship Diagram
 Figure 4.24 Entity Relationship Diagram

Data Dictionary. It is a document describing a database or collection of database. It also

an integral component of a database management systems that is required to determine its

structure.
tblUserAccounts
Field Data Type Description Table
ID Varchar(150) RFID of User
Username Varchar(50) Unique Username of User 4.8
Password Varchar(50) Password of User
FirstName Varchar(150) First Name of User
MiddleName Varchar(150) Middle Name of User Data
LastName Varchar(150) Last Name of User
MobileNumber Varchar(150) Mobile Number of User
Email Varchar(150) Email Address of User
UserLevel Varchar(50) User Level of the User
Position Varchar(50) Company Position
Street Varchar(150) Street Address
Brgy Varchar(150) Brgy Address
[City/Municipality] Varchar(150) City/Municipality Address
[Metro/Province] Varchar(50) State Address
Image Varchar(150) Image of User
Status Varchar(50) Status of User

Dictionary (tblUserAccounts)
Table 4.9

tblTransactionDetails
Field Data Type Description Data
ItemID varchar(150) ID of Product
TransID int Transaction ID
ItemName varchar(150) Product Name
ItemQty int Product Quantity
ItemSubtotal numeric(18, 2) Product Subtotal
ItemPrice numeric(18, 2) Product total amount
AssistID varchar(150) Assist ID for Points
AssistPoints int Assist Points for Staffs
Date varchar(50) Date of the transaction

Dictionary (tblTransactionDetails)

Table 4.10

Data Dictionary (tblTransaction)

tblSuppProdCart
Field Data Type Description
CartID int Unique ID of Cart
ProdID varchar(150) Product ID
ProdName varchar(150) Product Name
SuppName varchar(150) Supplier Name
Quantity Int Product Quantity
Table 4.11

Data
tblSuppliers
Field Data Type Description

ID int Unique ID of User

Name Varchar(150) Name of the Supplier
Contact Varchar(150) Contact for the Supplier
Street Varchar(150) Street Address
Brgy Varchar(150) Brgy Address
[City/Municipality] Varchar(150) City Address
[Metro/Province] Varchar(150) State Address
Status Varchar(150) Status of User

Dictionary (tblSuppProdCart)

Table 4.12

Data
tblTransaction
Field Data Type Description
ID int Transaction ID
ItemQty int Product Quantity
Amount numeric(18, 2) Transaction Amount
EmployeeID varchar(150) Employee ID Transacted
EmployeeName varchar(150) EmployeeName
Transacted
Date varchar(150) Date of Transaction
Status varchar(50) Status of Transaction
Change numeric(18, 2) Change
Time varchar(150) Time of Transaction
AmountTendered numeric(18, 2) Amount Tendered

Dictionary (tblSuppliers)
Table 4.13

tblSupplierProducts Data
Field Data Type Description
PKey int Unique ID of the table
SupplierID Varchar(150) ID of the Supplier
SupplierName Varchar(150) Name of the Supplier
ProductID Varchar(150) ID of the Product
ProductName Varchar(150) Name of the Product
SupplierLocation Varchar(150) Address of the Supplier

Dictionary (tblSupplierProducts)

Table 4.14

Data Dictionary (tblRecorderDetails)

tblReorderDetails
Field Data Type Description
[Primary] int Unique ID of the table
OrderID varchar(150) Order ID
ProdID varchar(150) Product ID
ProdName varchar(150) Product Name
SuppID varchar(150) Supplier ID
SuppName varchar(150) Supplier Name
Qty Int Product Quantity
PricePerItem varchar(150) Price per Item
Status varchar(150) Order Status
EmpIDRecieve varchar(150) Employee ID who recieved
QtyRecieved Int Quantity Recieved
Date Received varchar(150) Date the order is
completed
Amount numeric (18,2) Amount Paid
Note varchar(150) Note
Table 4.15

Data
tblProducts
Field Data Type Description
ID varchar(150) Barcode ID of the product
Name varchar(150) Name of the Product
Brand varchar(150) Product Brand
Color varchar(150) Product Color
Description varchar(150) Product Description
Quantity int Product Quantity
Price numeric (18,2) Product Price
ReorderLevel Int Reorder level of the
product

Dictionary (tblProducts)

Table 4.16

Data Dictionary (tblProdChart)

tblProdChart
Field Data Type Description
PrimKey Int Unique ID of the table
ID varchar(150) ID of the Product
Name varchar(150) Product Name
Qty Int Product Quantity

Table 4.17

Data Dictionary (tblEmployees)

 tblChart
Field tblEmployees
Data Type Description Table
Field
PrimKey Data Type
Int Unique Description
ID of the table
ID
ID varchar(150)
varchar(150) ID of the
Employee’sEmployee
ID 4.18
FirstName
EmployeeName varchar(150)
varchar(150) Employee’s Full
Employee’s FirstName
Name
MiddleName
AssistPoints varchar(150)
Int Employee’s Middle Name
Employee’s Assist Points Data
LastName varchar(150) Employee’s Last Name
MobileNumber varchar(150) Employee’s
MobileNumber
Position varchar(150) Employee’s Position
Street varchar(150) Street Address
Brgy varchar(150) Brgy Address
[City/Municipality] varchar(150) City Address
[Metro/Province] varchar(150) State Address
Image varchar(150) Image of the Employee

Dictionary (tblOrderList)

Table 4.19

Data Dictionary (tblChart)

tblOrderList
Field Data Type Description
OrderID Int Order ID of Reorder
Details
QtyOrdered Int Quantity Ordered
EmployeeID varchar(150) ID of the Employee
EmployeeName varchar(150) Name of the Employee
QtyRecieved Int Quantity Recieved
DateOrdered varchar(150) Date Ordered
DateRecieved varchar(150) Date Received
Status varchar(150) Status of the Order
Note varchar(150) Note
GrandTotal Numeric(18,2) Grand Total of the Order
EmpIDRecieve varchar(150) Employee ID who
recieved
SupplierID varchar(150) ID of the Supplier
SupplierName varchar(150) Name of the Supplier
Table 4.20

Data Dictionary (tblCart)

tblCart
Field Data Type Description
ID varchar(150) Product ID
Name varchar(150) Product Name
Quantity Int Product Quantity
Subtotal Numeric(18,2) Product Subtotal
Total Numeric(18,2) Product Total
Table
AssistID varchar(150) Staff’s Assist ID
4.21

Data Dictionary (tblAssistPoints)

Table 4.22

tblAuditTrail Data
Data Field tblAuditDetails
Data Type Description
Field
TrailID Data Type
Int Unique Description
ID of the Table
TrailDetailsID
UserID Int
Varchar(150) ID of theIDlogged
Unique of theintable
User
TrailID
UserName Int
Varchar(150) ID of the parent
Username of thetable
User
UserID
FirstName Varchar(50)
Varchar(150) ID ofName
First the User logged
of the Userin
FullName
LastName Varchar(150) NameName
Last of theofUser
the User
Action
DateIn Varchar(150) Action
Date of theinUser
logged
Date
TimeIn Datetime
Varchar(150) Date of
Time the process
logged in
DateOut Varchar(150) Date logged out
TimeOut Varchar(150) Time logged out

Dictionary (tblAuditTrail)

tblAssistPoints
Field Data Type Description Table
PrimaryK int Unique ID of the Table
TransactionID varchar(150) Transaction’s ID 4.23
ItemID varchar(150) Product ID
ItemName varchar(150) Product Name Data
AssistID varchar(150) Employee ID
EmployeeName varchar(150) Employee Name
Date date Date of transaction
AssistPoints int Assist Points for Sales
Amount Numeric (18,2) Amount of the transaction
Qty int Product Quantity

Dictionary (tblAuditDetails)
System Testing Evaluation

The evaluation of the Point of Sales and Inventory and Staff Performance Tracking for

Saiver Store with Barcode Scanner and RFID is an important part of this project. The staff of the

company need to test the performance levels of the system in terms of its functionality, usability,

reliability, performance, and security. Through this, the proponents will identify whether the

functionality requirements meet the expected response of evaluation criteria or not. The list of

table below shows the result of the five indicators of the system.

Table 4.24

Weighted Mean and Description of the Respondents’ Response on the System Functionality Test

Indicators Weighted Description

Mean
1. All the function keys on the 4.73 Excellent
system are working.

2. All the system sections are 4.82 Excellent

working.

3. The program loads quickly. 4.64 Excellent

4. Overall, the system is usable. 4.82 Excellent

General Weighted Mean 4.75 Excellent

Table 25 shows the weighted mean and the description made by the respondentsin terms

of functionality. Four indicators has been used to evaluate the functionality of the proposed
system. Based on the computation, the weighted means were 4.73, 4.82, 4.64 and 4.82

respectively. The general weighted mean was 4.75 and described as “Excellent”.

Table 4.25

Weighted Mean and Description of the Respondents’ Response on the System Usability Test

Indicators Weighted Description

Mean
1. The system is easy to use. 4.36 Very Good

2. Text is clear and printed 4.55 Excellent

suitable for target audience.

3. The system can be used with 4.45 Very Good

ease.

4. Overall, the system is user 4.45 Very Good

friendly.

General Weighted Mean 4.45 Very Good

Table 26 presents the weighted mean and the description made by the respondents in

terms of system usability. Four indicators has been used to evaluate the system. Based on the

computation, the weighted means were 4.36, 4.55, 4.45 and 4.45 respectively. The general

weighted mean was 4.45 and described as “Very Good”.

Table 4.26

Weighted Mean and Description of the Respondents’ Response on the System Reliability Test

Indicators Weighted Description

Mean
1. Consistency with interface. 4.64 Excellent

2. The system is efficient. 4.73 Excellent

3. Run without errors that disrupt 4.82 Excellent

program function.

4. The system gives accurate 4.82 Excellent

information.

5. Overall, the system provides 4.64 Excellent

reliable information.

General Weighted Mean 4.73 Excellent

Table 27 exhibits the weighted mean and the description made by the respondents. Five

indicators has been used to evaluate the reliability of the proposed system. Based on the

computation, the weighted mean of the indicators were 4.64, 4.73, 4.82, 4.82 and 4.64

respectively. The general weighted mean was 4.73 and described as “Excellent”.
Table 4.27

Weighted Mean and Description of the Respondents’ Response on the System Performance Test

Indicators Weighted Description

Mean
1. The system load faster. 4.45 Very Good

2. The information provided is 4.45 Very Good

easy to understand.

3. Provides record quickly. 4.45 Very Good

4. The system can transact well. 4.36 Very Good

5. Overall, the performance of 4.45 Very Good

the system is all good.

General Weighted Mean 4.43 Very Good

Table 28 presents the weighted mean and the description made by the respondents. Five

indicators has been used to evaluate the performance of the proposed system. Based on the

computation, the weighted mean of the indicators were 4.45, 4.45, 4.45, 4.36 and 4.45

respectively. The general weighted mean was 4.43 and described as “Very Good”.
Table 4.28

Weighted Mean and Description of the Respondents’ Response on the Security Test

Indicators Weighted Description

Mean
1. The contents of the sales and 4.64 Excellent
inventory are secured.

2. Data and reports are only 4.73 Excellent

visible to authorized users.

3. The system has a section 4.36 Very Good

strictly for administrator only.

4. The section has a section 4.55 Excellent

strictly for staff only.

5. Overall, the system is secured. 4.64 Excellent

General Weighted Mean 4.58 Excellent

Table 29 illustrates the weighted mean and the description made by the respondents. Five

indicators has been used to evaluate the security of the proposed system. Based on the

computation, it shows that the weighted mean of the indicators were 4.64, 4.73, 4.36, 4.55 and

4.64 respectively. The general weighted mean was 4.58 and described “Excellent”.
Table 4.29

Summary of the Weighted Mean and Description of the Program Evaluation Test

Indicators Weighted Description

Mean
1. System Functionality Test 4.75 Excellent

2. System Usability Test 4.45 Very Good

3. System Reliability Test 4.73 Excellent

4. System Performance Test 4.43 Very Good

5. System Security Test 4.58 Excellent

General Weighted Mean 4.59 Excellent

Table 30 showed the summary of the weighted mean of the Five Indicators. As shown in

the table, the weighted mean of the respondents ranged from 4.43 to 4.75. The weighted mean of

4.75 is the highest from System Functionality Test, followed by 4.73 from system Reliability

Test, 4.58 from System Security Test, 4.45 from System Usability Test, and 4.43 from System

Performance Test. Over all, the general weighted mean of the system evaluation is equal to 4.59

presented as “Excellent”. The result of the evaluation shows that the system is Usable.