Methodology

Chapter 3

RESEARCH METHODOLOGY

This chapter presents the research methodology which includes the

sources of data, detailed methods that were used in the study, the tools for data

analysis, and the instruments that were used for data gathering.

System Design

The proponents chose the Prototyping model to demonstrate and clarify

the components of the proponent's proposed system to the users. The

proponents explained how this methodology model influenced the system's

design.

The Prototyping model is one of the most popularly used Software

Development Life Cycle Models (SDLC models). This model is used when the

customers do not know the exact project requirements beforehand. In this model,

a prototype of the end product is first developed, tested, and refined as per

customer feedback repeatedly till a final acceptable prototype is achieved which

forms the basis for developing the final product (GeeksforGeeks, 2024).

Prototyping Model is a software development model in which a prototype

is built, tested, and reworked until an acceptable prototype is achieved. It also

creates a base to produce the final system or software. It works best in scenarios

where the project’s requirements are not known in detail. It is an iterative, trial

and error method which takes place between developer and client (Martin, 2024).

The proponents used this methodology to achieve the goals and

objectives, as well as to develop and implement the proposed study.

 Methodology

Figure 3: Prototyping Model

Phase 1: Requirements Gathering and Analysis. A prototyping model

starts with requirement analysis. In this phase, the requirements of the system

are defined in detail (Martin, 2024).

In this phase, the proponents focused on gathering the essential features

and functionalities to be included in the initial prototype. This extensive study

allowed the proponents to identify and outline the essential system requirements,

ensuring that the prototype model met the user’s specific needs.

Phase 2: Quick Design. The second phase is a preliminary design or a

quick design. In this stage, a simple design of the system is created. However, it

is not a complete design. It gives a brief idea of the system to the user. The quick

design helps in developing the prototype (Martin, 2024).

The proponents conducted design reviews and looked for feedback to

ensure that the quick design was aligned with the user's desires and

expectations. This iterative feedback loop helped identify any potential gaps or

alterations needed to address the user's specific needs effectively.

Phase 3: Build a Prototype. In this phase, an actual prototype is designed

based on the information gathered from quick design. It is a small working model

of the required system (Martin, 2024).

 Methodology

The proponents focused on refining the prototypes, aiming to convert

them into a fully operational model. This involved translating conceptual ideas

into tangible components, enabling testing and validation of key functionalities.

Phase 4: User Evaluation. In this stage, the proposed system is presented

for an initial evaluation. It helps to find out the strength and weakness of the

working model. Comments and suggestions are collected from the customer and

provided to the developer (Martin, 2024).

During this phase, the user had an active role in testing the model. The

user evaluates its effectiveness, usefulness, and functionality in a regulated

setting. The development team carefully documented and examined the insightful

feedback from customers.

Phase 5: Refining Prototype. This phase will not be over until all the

requirements specified by the user are met. Once the user is satisfied with the

developed prototype, a final system is developed based on the approved final

prototype (Martin, 2024).

The proponents focused on implementing the feedback and

recommendations obtained during the preliminary phase of the user assessment.

The proposed study underwent several changes as the proponents carefully

worked to ensure that it met the expectations of all stakeholders and efficiently

handled the issues that were faced.

Phase 6: Implement Product and Maintain. Once the final system is

developed based on the final prototype, it is thoroughly tested and deployed to

 Methodology

production. The system undergoes routine maintenance for minimizing downtime

and preventing large-scale failures. (Martin, 2024).

The proponents implemented the final product by deploying the thoroughly tested

system into production. The system underwent routine maintenance, ensuring all

necessary configurations were in place for smooth operation and guaranteeing

effective operation over time.

Sources of Data

The primary source of data for this study was individual respondents. To

gather relevant data, the proponents conducted onsite surveys with sixty (60)

respondents and online surveys with forty (40) respondents, focusing on potential

users of the system. This direct engagement provided valuable firsthand

information critical to shaping the proposed study.

The online research and document analysis served as secondary data

sources, providing a foundation for the functionality and design of the proposed

study.

Instrumentation and Data Collection

For the instrumentation and data collection, the proponents used the

following tools:

Internet Research. Internet research is the process of using the Internet to

find information about a given topic. This can be done through search engines,

such as Google or Bing, or by visiting specific websites that deal with the subject

matter at hand. When conducting internet research, it is important to remember

that not all sources are created equal. It is important to evaluate each source for
 Methodology

its credibility and accuracy before using it as part of your research (Jordan, R.

2022). The proponents utilized the internet to collect related information about

the proposed system.

Observation. Observation is a way to gather data by watching people,

events, or noting physical characteristics in their natural setting. Observations

can be overt (subjects know they are being observed) or covert (do not know

they are being watched) (LibGuides: Qualitative Research: Observation, n.d).

The proponents collected various current systems, examining the operations and

processes, as well as the features, to gain a deeper understanding of how the

system worked. This analysis aided in enhancing the proposed system.

Onsite Survey. Onsite surveys can be conducted in various forms, such as

questionnaires, interviews, focus groups, and observation studies. These

surveying methods allow for the collection of qualitative and quantitative data,

which can be used to make decisions on how to better serve customers or

employees (Nyda, 2024). The proponents utilized this approach to assess the

proposed system based on the feedback from the respondents.

Online Survey. Online survey or internet survey, is one of the most

popular data-collection sources, where a set of survey questions is sent out to a

target sample and the members of this sample can respond to the right questions

over the World Wide Web. Respondents receive surveys via various mediums

such as email, embedded over website, social media etc (Bhat, 2023). The

proponents used online surveys to quickly gather data from a target sample via
 Methodology

email, websites, and social media. This method allowed for broad reach and

timely responses, facilitating the collection of relevant information for their study.

Tools for Data Analysis

In this study, the following instruments are used to analyze data:

Gantt Chart. A Gantt chart is a horizontal bar chart used in project

management to visually represent a project plan over time. Gantt charts typically

show you the timeline and status as well as who’s responsible for each task in

the project (TeamGantt, 2023). The proponents used the Gantt chart for the

schedule of developing the system.

System Usability Scale. Created by John Brooke in 1986, the System

Usability Scale (SUS) is a widely used tool for evaluating the usability of

software, websites, and other interactive systems. Since then, it has become a

standard method for assessing the overall user-friendliness of a product.

(Soegaard, 2024). The proponents used this tool to assess and evaluate the

user-friendliness and effectiveness of the proposed system or application.

Use-Case Diagram. A use case diagram is a visual summarization of

interactions and relationships within a system. These diagrams show a very

broad view of a system. They may show systems in computer software,

businesses or customer experiences. A use case diagram shows a model

scenario in which individuals interact with a system using a series of specialized

symbols and connectors (Indeed Editorial Team, 2022). The proponents used

this tool to illustrate how the users interacted with the system.
 Methodology

Ethical Consideration

Ethical considerations in research refer to guidelines and principles which

researchers must adhere to as they conduct their research. Research often

involves face-to-face interaction with people as researchers study behaviors and

test the effects of certain phenomena on a target population. Ethical

considerations dictate the nature of such interactions to ensure research is done

per the set rules and principles (Types & Examples, 2024).

Before conducting the information, the researchers got informed consent

from participants, confirming they agreed to participate in the study and

understood the objectives, processes, and possible risks. The consent form

acted as a trust agreement between researchers and participants. The

participants were guaranteed that their participation was completely voluntary,

without force, pressure, or persuasion, and they could withdraw at any time

without punishment. The participants' personal information and feedback

remained confidential and anonymous, and the data was used only for research

purposes. However, if a participant's safety was at risk, to ensure their safety,

some information might need to be disclosed. All ethical rules and regulations

were strictly followed throughout the research process. The researchers ensured

that personal information was protected in accordance with the Data Privacy Act

of 2012 (Republic Act No. 10173), and put security measures in place to stop

unwanted access while educating the participants about their rights as data

subjects, particularly having the right to access, update, and remove their

personal data. Additionally, the study followed software development guidelines,

 Methodology

including respect for intellectual property rights, compliance with open-source

licensing terms, and, if applicable, commitment to industry-specific standards

such as healthcare or financial services. Developers documented the software

development process, implemented secure programming practices to prevent

vulnerabilities, and considered data localization across worldwide use.

Throughout the study and any following data retention period, the proponents

also kept informed of and complied with any revisions or modifications to these

laws and regulations.