Chapter 3

RESEARCH METHODOLOGY AND PROCEDURES

This chapter presents the methodology, research design, respondents of

the study, data gathering instruments to be used, and data gathering

procedures.

Software Development Methodology

In software development, RAD (Rapid Application Development) is a

concept that was born out of frustration with the waterfall software design

approach which too often resulted in products that were out of date or

inefficient by the time they were actually released. The term was inspired by

James Martin, worked with colleagues to develop a new method called Rapid

Iterative Production Prototyping (RIPP). In 1991, this approach became the

premise of the book Rapid Application Development.1

The researchers decided to make use of Rapid Application Development

(RAD) model because RAD methodology enables quick development of software

products by using Computer Aided Software Engineering (CASE) tools , in

combination with methods of iterative development and rapid prototyping. It

aims at reducing the time involved in the planning phase. It drastically reduces

the time required for software development, usually taking somewhere between

30 to 90 days for the complete development life cycle.2

1 Margaret Rouse, Rapid Application Development. Retrieved on April 20, 2017 6:40pm from
<searchsoftwarequality.techtarget.com/definition/rapid-application-development>
2 Prashant Magar (February 1, 2013). Retrieved on April 25, 2017 5:57pm from
<http://www.buzzle.com/articles/advantages-of-rapid-application-development.html>
 Rapid application development is a form of agile software development

methodology. Unlike Waterfall methods, RAD emphasizes working software and

user feedback over strict planning and requirements recording.

In other words, RAD is less talk, more action. Oh, and testing. Lots and

lots of testing.

While RAD de-emphasizes strict planning, there are still a handful of

steps or phases each development project goes through when using the rapid

application development methodology, which we’ll discuss below.

RAD methodology also describes a method of software development

which heavily emphasizes rapid prototyping and iterative delivery. The RAD

model is, therefore, a sharp alternative to the typical waterfall development

model, which often focuses largely on planning and sequential design

practices. First introduced in 1991 in James Martin’s book by the same name,

rapid application development has become one of the most popular and

powerful development methods, which falls under the parental category of agile

developmental techniques.

Perhaps the biggest advantage of RAD is its inherent synergy with the

requirements of medium itself: software. Whereas other forms of creation, such

as a towering skyscraper or a sleek new automobile, require meticulous

planning and logical development, the very essence of software is both

malleable and in constant evolution. Since code itself – and by extension, the
software which is powered by said code – can be morphed quickly and easily

during development, software is inherently adaptable, lending itself well to

iteration and experimentation.

By utilizing a rapid application development method, designers and

developers can aggressively utilize knowledge and discoveries gleaned during

the development process itself to shape the design and or alter the software

direction entirely.

Its advantages are:

a. Measurable Progress. With frequent iterations, components, and

prototypes coming down the pipe, progress on the overall project,

as well as lesser segments, can be easily measured and evaluated

to maintain schedules and budgets.

b. Quickly Generate Productive Code. As a larger percentage of active

software developers move into multi-discipline roles (i.e. full-stack

developers), a RAD methodology allowed skilled team members to

quickly produce prototypes and working code to illustrate

examples that might otherwise take weeks or months to see the

light of day using a slower development technique.

c. Compartmentalization of System Components. Much in the same

way that object-oriented programming practices keep objects and

components quarantined from one another, RAD inherently has

the same beneficial impact on the components generated during

development. By the forcing designers and developers to create

 components that are functional and independent on their own, to

be used in an iterative release or prototype, each element within

the overall software system is compartmentalized and therefore

easily modified as the needs of the software evolve.

d. Rapid, Constant User Feedback. As discussed above, obtaining

relevant user feedback during development is invaluable. RAD

methodologies allow a near-constant user interfacing and feedback

through frequent iterations and prototype releases, giving the

entire team priceless evaluation and criticism when it’s needed

most.

e. Early Systems Integration. While most waterfall method software

projects must, by their very nature, wait until the tail end of the

lifecycle to begin integrations with other systems or services, a

rapidly developed application becomes integrated almost

immediately. By requiring early integrations within a prototype, a

RAD system quickly identifies any errors or complications within

integrations and forces immediate resolutions.

Simple Adaptability. During development, software is a fairly malleable

form. Since code can be changed that dramatically alters the entire system or

generates new components, it is to the advantage of the development team to

make use of this flexibility early and often, by iterating and prototyping

potential concepts or ideas throughout development.

Rapid Application Development (RAD) Diagram

Four Phases of RAD:

1. Planning Requirements. During this initial stage, designers, developers,

and users come to a rough agreement on project scope and application

requirements, so that future stages with prototyping can begin. 3

In this phase, the researchers made a study on how the system

will work with its planned features and functionalities along with the

requirements needed of the proposed system. The researchers also made

coordination with the owner of the County State Hotel District 04,

Tumauini Isabela and discussed with them about the system.

2. User Design. User feedback is gathered with heavy emphasis on

determining the system architecture. This allows initial modeling and

prototypes to be created. This step is repeated as often as necessary as

the project evolves.4

3 Andrew Powell-Morse November 23, 2016, Rapid Application Development (RAD): What Is It
And How Do You Use It? Retrieved on April 25, 2017 5:53pm from
<https://airbrake.io/blog/sdlc/rapid-application-development>
4 Ibid
 In this phase, the researches constructed a prototype of the

proposed system. This prototype shows what the system would look like

and what features and functionality it would possess based on the needs

of its users.

3. Rapid Construction. Once basic user and system design has begun, the

construction phase is where most of the actual application coding,

testing, and integration take place. Along with User Design, the Rapid

Construction phase is repeated as often necessary, as new components

are required or alterations are made to meet the needs of the project. 5

In this phase, the researchers will now do the coding of the system.

Testing and debugging of the proposed system will be done frequently

and so with the iteration of the proposed system until it satisfies the

user’s needs.

4. Cutover. The final Cutover (or Transition) stage allows the development

team time to move components to a live production environment, where

any necessary full-scale testing or team can take place. 6

In this phase, the proposed system will already be deployed to the

County State Hotel District 04, Tumauini Isabela. After series of tests

and iterations. The researcher will also include trainings or seminars to

the users regarding about the proper usage of the proposed system.

5 Andrew Powell-Morse November 23, 2016, Rapid Application Development (RAD): What Is It
And How Do You Use It? Retrieved on April 25, 2017 5:53pm from
<https://airbrake.io/blog/sdlc/rapid-application-development>

6 Ibid
 Maintenance will also be implemented to ensure that the system

responds well to the needs of the users only for a limited period of time.

Data Gathering Techniques

In order to gather sufficient and accurate information regarding the

subject matter, and determine the actual problem confronting the existing

student profiling system, the researchers decided to use the following

instruments:

Interview. The researchers conducted an interview with the manager

Pienita B. Bangloy CSH. It is used to supplement primary source of data on the

requirements that will be used in the proposed system. It also gave the

researchers the understanding and the opportunity for clarification purposes

and played a big role for the accomplishment of the study by asking questions

directly.

Observation. Observations were also conducted, for the researchers

believe that it is an excellent way of obtaining data. Observational findings are

considered strong in validity because the researchers had personally witnessed

the actual scenario of County State Hotel.

Internet. The researchers searched relevant information needed to this

study. This method is essential to locate some data readily available to the

Internet.

Data Gathering Procedure

 The researchers had come up with three research titles for their study

and waited for the approval of their professor, Mr. Michael Kit Pobre. In the

latter, the agreed proposed research title is the Hotel Management System. This

system focuses on the customer’s statement of account. After the approval, the

researchers asked for a referral letter from their adviser addressed to Mrs.

Pienita B. Bangloy, owner duly signed by their adviser Mr. Michael Kit Pobre

which will be submitted in their chosen establishment which is the County

State Hotel District 04, Tumauini Isabela. The researchers had showed the

referral letter to the owner, Mrs. Pienita B. Bangloy for the confirmation. After

the confirmation of the owner, the researchers immediately observe the existing

system that they are currently using. After their observation, the researchers

then conducted an interview and asked the owner, Mrs. Pienita B. Bangloy

about several problems they encountered from their current system which is

manual system or paper-based system.

The researchers interviewed and distributed a questionnaire to Mrs.

Pienita B. Bangloy, the Owner of the County State Hotel for supporting

documents and for the clarifications and validations of data needed by the

researchers in the fulfillment of their study.

Selection and Description of the Respondent

First, the researchers approach the County State Hotel Owner, Mrs.

Pienita B. Bangloy and asked permission to conduct the study during free time

and convenient time of the personnel in charge.

 The respondent of this study is Mrs. Pienita B. Bangloy, Owner of County

State Hotel who gave us privileges to collect information about their existing

system. She had showed the processes and procedures being conducted in the

recording of customer’s statement of account. He also provided the researchers

with the valuable information regarding their present system. The researchers

also asked them direct questions for additional data to be gathered.

The researchers are confident that the respondent can supply the

information needed for she has sufficient knowledge in answering the

necessary data asked.