Chapter 3

METHODOLOGY

This chapter includes the project design, project development, operation and

testing procedure, and the evaluation procedure of the system.

Project Design

The study focuses on the development of a Web-Based IT Help Desk or Job

Order System, a web-based system that assists Glory Philippines Incorporation

employees with technical support requests in order to avoid long hours of manual

approval from various departments.

Figure 12. Block Diagram of the Web-System

46

Figure 12 depicts the web-based system's block diagram. When no user accounts

are found, a login credential must always be requested. The web-based system must

include features such as the ability to file job order requests, assign technical team

support, send email notifications about request status, and provide rate-based delivery

and report quality. The department head must be notified when a new file job order

request is submitted. Technical support teams can be assigned by FEM/MIS. XAMPP

Server will serve as the centralized database infrastructure, storing and retrieving all data

as well as server-side executions.

Figure 13. Use Case Diagram of the Web-Based System

47

Figure 13 represents the web-based system's use case diagram, which depicts the

various actions performed by the system and its interaction with users. The system is

made up of four (4) external actors and six (6) actions that can be carried out in the web-

based system. The requestor, FEM/MIS, department head, and admin head are the

external actors who represent the various user access privileges on the system. Each

action on the system can only be performed with the appropriate privilege.

Figure 14. Context Diagram of the System

Figure 14 depicts the context diagram, which depicts the system's overview

functionalities. Requestors will be able to login to their accounts, request job orders, rate

jobs such as delivery and report quality, and receive email notifications about the status

of their requests. FEM / MIS will be able to login to their account, view a user's job

rating, and update their records with the assigned technical team supports. Administrators
48

and Department Heads are responsible for reviewing and approving data submitted to the

system.

Project Development

Every project must adhere to a set of standard procedures during development to

ensure its success and completion. Because this research project involves the creation of a

mobile application, a software development life cycle (SDLC) and the models it

incorporates have been considered. Figure 19 depicts the evolutionary prototyping model

that will be used in this study. The main goal of evolutionary prototyping is to create a

very robust prototype of the software application in a structured manner. The model also

reduces significant risk to the project's success because each iteration constantly refines

the prototype, making it ideal for research projects.

Figure 19. Evolutionary Prototyping Model

49

Following the principles and approach of evolutionary prototyping, the system's

development will go through the six (6) stages of the model.

Requirements Stage will create an initial list of requirements and specifications

based on the study's objectives.

Design Stage shall plan the internal and external system components. The initial

design will be created during the first iteration, which will focus on the web-based

system's basic cores and logic modules. The visualization component of the web-based

system would then be designed in the second iteration. If improvements are required,

further iterations will be carried out.

Implementation Stage shall translate the physical designs into software codes.

Each specification from the design shall be applied to the overall program structure. The

mobile application shall be developed using React Native. Server-side scripting shall be

developed using Node.js where the mobile application shall send or request data from the

system. Google Cloud Vision API shall be use for image content analysis where the

processed result will be retrieved by the mobile application. The NoSQL database design

shall be implemented and deployed in Firebase Cloud Firestore. Google Firebase shall

serve as the centralized cloud infrastructure for the system.

Implementation Stage physical designs must be translated into software codes.

Each design specification must be applied to the overall program structure. PHP will be
50

used to create the web-based system. JavaScript will be used to develop server-side

scripting where the web-based system will send or request data from the system.

Tailwind CSS, Flowbite, and Bootstrap will be used to create the stylesheet language. In

XAMPP Server, the MySQL database design must be implemented and deployed. The

centralized database infrastructure for the web-based system will be provided by XAMPP

Server.

Testing Stage shall check each function implemented in the web-based system

against its specification to ensure that it performs the intended action.

Evaluation Stage determine whether the web-based system met the project's

requirements and specifications. This stage also identifies key areas for improvement in

order to determine whether more iterations are required and to adjust the time schedule

accordingly.

Deployment Stage is the point at which the project has been completed and is

ready to be deployed in various environments. The web-based system will be made

public within the company.

Operation and Testing Procedure

Each software build must include software testing to ensure the application's

quality. The developed web-based system must be tested for functionality, dependability,

and portability.
51

Functional Testing shall be performed to check the features or functionalities of

the application. This is to ensure that each software component performs the expected

output. The following steps shall be taken for each iteration:

1. Distinguish the functions of each software build.

2. Create input data based on the specifications of the function.

3. Identify the output data based on the specifications of the function.

4. Execute the test cases.

5. Compare the actual result from the expected result.

6. Determine the postcondition.

7. Evaluate if the test passes or fail.

A test case form shall be utilized to record each functional test performed. The

results shall be analyzed to determine the effectiveness of the system. Table 2 shows the

test case form.

Functional Testing must be performed to verify the system's features or

functionalities. This is done to ensure that each software component produces the

expected results. For each iteration, the following steps must be taken:

1. Differentiate between the functions of each software build.

2. Create input data based on the function's specifications.

3. Determine the output data based on the function specifications.

4. Carry out the test cases.

5. Contrast the actual and expected results.

52

6. Find the postcondition.

7. Determine whether the test passed or failed.

Each functional test must be documented using a test case form. The results will

be analyzed to determine the system's effectiveness. The test case format is shown in

Table 2.

Test Scenario Remarks

Test Case

Test Steps

Expected Result Actual Result

Postcondition

Table 2. Test Case Form

Reliability Testing must be performed to evaluate the system's performance

under specified environmental conditions. For each iteration, the following steps must be

taken:

1. Run the web-based system several times in desktop PC and android phones

environments to see if the system produces the same output and results each time.

2. Count the total number of cases that failed and the total number of cases that are

being considered.

3. Calculate the failure probability.

53

Portability Testing must also be performed to ensure the system's adaptability,

installability, replaceability, and coexistence. For each iteration, the following steps must

be taken:

1. Run the web-system on various operating system versions.

2. Run the web-based system on various desktop PC and android devices.

Evaluation Procedure

The developed web-based system will be evaluated using the ISO 25010 quality

software standard criterion. 5 software engineers or developers, 10 information

technology professionals, and 15 end users will evaluate the web-based system. The

following is the evaluation procedure:

1. Each respondent will be given a software evaluation form to use in measuring the

system's performance.

2. The research objectives will be discussed, and a demonstration will be performed

to demonstrate the system's functionality.

3. The application will be requested of each respondent.

4. The respondents will also be asked to rate the system in terms of the ISO 25010

standard evaluation criteria using a Likert scale rating system, as shown in Table

3, with 5 being the highest and 1 being the lowest.

54

Scale Descriptive Rating

4 Highly Acceptable
3 Very Acceptable
2 Fairly Acceptable
1 Not Acceptable

Table 3. Likert Scale in Rating the System

1. Based on the collected evaluation, the overall mean ratings for each criterion shall

be computed.

2. Using the scale shown in Table 4, the evaluation results must be translated into

qualitative interpretation.

Scale Descriptive Rating

4.51 to 5.00 Excellent
3.51 to 4.50 Very Good
2.51 to 3.50 Good
1.51 to 2.50 Fair
1.00 to 1.50 Poor

Table 4. Scale Range and the Equivalent Descriptive Rating