CHAPTER II

METHODOLOGY

Research Methodology and Design

The evolutionary prototyping model is a system development method in which a

prototype is built, tested, and then reworked as necessary until an acceptable outcome is

achieved from which the complete system or product can be developed. This model

works best in scenarios where not all of the project requirements are known in detail

ahead of time. It is an iterative, trial-and-error process that takes place between the

researchers and the users. (Geeks for Geeks).

The researcher used evolutionary prototyping as their process in developing the

Radio Frequency Identification (RFID)-based vehicle monitoring system. According to

Runehov and Oviedo (2013), the evolutionary prototyping model is a software

development method where the developer or development team first constructs a

prototype. After receiving initial feedback from the customer, subsequent prototypes are

produced, each with additional functionality or improvements, until the final product

emerges. In this model, it is assumed that not all the requirements may be known at the

start of the development of the system. It is usually used when a system does not exist or

in a case of a large and complex system where there is no manual process to determine

the requirements. This model allows the users to interact and experiment with a working

model of the system known as an evolutionary prototype. The evolutionary prototype

gives an annual feel to the system.

 The researcher followed the System Development Life Cycles which has six (6)

phases that play dynamic roles and define the task to be completed at each step in the

software development process. Figure 3 illustrates the steps carried out in the SDLC

model. These steps are listed below.

5 cycles

Figure 3. Evolutionary Prototyping

Requirements Gathering. An evolutionary prototyping model begins with

requirement analysis and the requirements of the system are defined in detail. The client

is interviewed to know the additional components of the system.

The researchers identified some of the common problems that will help to find

and suggest some solutions. The researchers gathered the requirements and analyzed each

to identify the needed requirements for an automated monitoring system for the

organization.

Quick Design. When the requirements are known, a preliminary or rapid system

design is developed. It is not a detailed design; it only includes the important aspects of

the system that give an idea of the system. A quick design helps develop the

prototype.
 This is the phase where the fundamental work for actual programming and

implementation is done. After gathering all the requirements for the system, the

researchers made proper documentation. The involves specifying and designing the

project’s hardware and software requirements together with the inter-relation.

The researchers started the coding phase and deployed the software. The

programming ideas and algorithms which have been designed are written.

Build Prototype. Information gathered from quick design is modified to form the

prototypes, which represent the working model of the required system.

Visual Studio Ultimate 2012 was used by the researchers to design the system’s

user interface and actual coding, while My SQL was the database software of the system.

User Evaluation. The proposed system is then presented to the client for a

thorough evaluation of the prototype to identify and eliminate its strengths and

weaknesses. Comments and suggestions are collected from the client and made available

to the developer.

As part of the development process, the proposed system was presented to the

client to evaluate the prototypes, noting what needs to be added and also its strengths and

weaknesses. Remarks from the client were collected and analyzed by the researchers. The

prototype was carefully evaluated to see whether all existing processes, politics, and rules

in the organization were carefully integrated.

The following norms were used to determine the mean rating of the system.

Description Range
 Very Highly Recommended 4.21 – 5.00

Highly Recommended 3.41 – 4.20

Moderately Recommended 2.61 – 3.45

Low Recommended 1.81 – 2.65

Very Low Recommended 1.00 – 1.80

Refining Prototype. Once the client evaluates the prototype and if he is not

satisfied, the current prototype is refined according to the requirements. That is, a new

prototype is developed with the additional information provided by the clients. The new

prototype is evaluated just like the previous prototype. This process continues until all the

requirements specified by the client are met. Once the clients are satisfied with the

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

Engineer Product. Once the requirements are completely met, the client accepts

the final prototype. The final system is evaluated thoroughly followed by routine

maintenance on regular basis to prevent large-scale failures and minimize downtime.

DATA GATHERING TOOLS

The researchers will be doing an open-ended interview. Opening questions will be

asked and with follow-up questions to responses that warrant further elaboration and

identification of the functionality of the proposed system. Consequently, they are

relatively quick and easy to administer and may be of particular use if clarification of

certain questions is required or if there are likely to be literacy or numeracy problems

with the respondents. However, by their very nature, they only allow for limited
participant responses and are, therefore, of little use if 'depth' is required. It will be

participated by the Vehicle and Equipment Manager and other concerned individuals if

necessary.

The following data gathering tools were used toward the materialization of this

study.

INTERNET. the researchers another research tool the researchers that offer them

information and data over the world wide web. The Internet is important to the researcher

because it serves as their secondary source of data. They download and gather some ideas

that are needed in the proposed study.

QUESTIONNAIRE. It is a method used to collect information particularly in

conducting a survey. The researchers used this technique to determine the acceptability of

the system. It helps to determine the need of the system.

DATA GATHERING PROCEDURES

The main source of data desired is the strategy and progress of the system

remained the information derived in the discussion and interview. It will collect all of the

information in the Municipality.

The other sources of data are primarily from the different published resources like

articles on the internet, and books, that are connected to the research studies it will

concerning the requirements and the functionalities of the system.

 The questionnaire that will validate the research expert will be distributed to the

participants, the researchers assuming that the participants’ data gathered will be treated

with the utmost confidentiality.

DATA MANAGEMENT AND ANALYSIS

The analytical tools used in conducting the proposed study are Use Case,

flowchart, Database Schema, Entity Relationship Diagram, and Gantt chart which are

precisely discussed in this section for the development of the system.

The research uses the following tools for data analysis in gathering related

information in developing the Vehicle and Equipment Monitoring System.

Use Case. A use case is a methodology used in system analysis to identify, clarify

and organize system requirements. The use case is made up of a set of possible sequences

of interactions between system and users in a particular environment and related to a

particular goal. The method creates a document that describes all the steps taken by a user

to complete an activity. (See Appendix “E”)

Flowchart. A flowchart is a picture of the separate steps of a process in

sequential order. It is a generic tool that can be adapted for a wide variety of purposes and

can be used to describe various processes, such as a manufacturing process, an

administrative or service process, or a project plan. (See Appendix “C”)

Entity Relationship Diagram. The researchers used this as a tool to visualize a

relational database. 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

their properties (SmartDraw,1994-2022). (See Appendix “D”)

Gantt Chart. The researcher alternates 5 times that are used in project

management, one of the most popular and useful ways of showing activities (tasks or

events) displayed against time. (See Appendix “F”)