0% found this document useful (0 votes)
89 views13 pages

Chapter 3 For Voting System

The document describes the methodology used for developing a voting system. It discusses the research design, which used a survey methodology to gather requirements. It also describes the sources of data, which included surveys distributed to school administrators and guidance counselors. Finally, it discusses the instruments and data collection techniques used, such as survey questionnaires, to gather the necessary data to define the system requirements.

Uploaded by

Arthan Kyle
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
89 views13 pages

Chapter 3 For Voting System

The document describes the methodology used for developing a voting system. It discusses the research design, which used a survey methodology to gather requirements. It also describes the sources of data, which included surveys distributed to school administrators and guidance counselors. Finally, it discusses the instruments and data collection techniques used, such as survey questionnaires, to gather the necessary data to define the system requirements.

Uploaded by

Arthan Kyle
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
You are on page 1/ 13

CHAPTER 3

METHODOLOGY

This chapter presents the research method use, the sources

of data, instruments and data collection and the tools for the

analysis of data gather

I RESEARCH DESIGN

The developers use the survey research design to gather

information regarding how the Voting System should be

formulate and implement. It involves procedures use in order

to learn new insights with the existing problems and to

discover answers to questions through the application of

scientific procedures.

Survey research may have its roots in English and

American “social surveys” conducted around the turn of the

20th century by researchers and reformers who wanted to

M ANGALDAN N ATIONAL H IGH S CHOOL – S ENIOR H IGH S CHOOL


1
document the extent of social problems such as poverty

(Converse, 1987)

Survey research is defined as "the collection of

information from a sample of individuals through their

responses to questions" (Check & Schutt, 2012)

In contrast to survey research, a survey is simply a data

collection tool for carrying out survey research. Pinsonneault

and Kraemer (1993) defined a survey as a “means for

gathering information about the characteristics, actions, or

opinions of a large group of people” Surveys can also be used

to assess needs, evaluate demand, and examine impact

(Salant & Dillman, 1994).

Extreme Programming is a software development

methodology designed to improve the quality of software and

its ability to properly adapt to the changing needs of the

customer or client. During the mid and late nineties, while

working on the Chrysler Comprehensive Compensation

System (C3) to help manage the company’s payroll, software

M ANGALDAN N ATIONAL H IGH S CHOOL – S ENIOR H IGH S CHOOL


2
engineer Ken Beck first developed the Extreme Programming

methodology. 

The developers used Extreme Programming in the design of

the system.

The figure shows the flows of the procedures of phases of

Extreme Programming. It includes the following phases:

Figure 3.1 Phases of Extreme Programming

Software development life cycle or SDLC for short is a

methodology for designing, building, and maintaining

information and industrial systems (Bassil, 2012).

Phase 1- Release Plan. the first stage, is when the

customer meets the development team and presents

M ANGALDAN N ATIONAL H IGH S CHOOL – S ENIOR H IGH S CHOOL


3
the requirements in the form of user stories to describe the

desired result. The team then estimates the stories and

creates a release plan broken down into iterations needed to

cover the required functionality part after part. If one or more

of the stories can’t be estimated, so-called spikes can be

introduced which means that further research is needed. The

developers planned the layout, coding, and functions of the

finished system. The developers will also plan decisions and

prioritization and only the programmers are responsible for

task estimation and development execution.

Phase 2- Iteration Plan. Iteration planning is

the process of discussing and planning the next cycle, phase

or iteration of a software application that is under

development. It is conducted through a meeting of the entire

software development team at the starting point of

each iteration to formally plan technical and non-

technical processes.

M ANGALDAN N ATIONAL H IGH S CHOOL – S ENIOR H IGH S CHOOL


4
The developers will think a way that the system is useful

for the client preferences. The developers will produce that

iteration's plan of programming tasks.

Phase 3- Acceptance Test. The acceptance test

plan or system test plan is based on the requirement

specifications and is required for a

formal test environment. Acceptance evaluates the

functionality and performance of the entire application and

consists of a variety of tests like.

The developers will be testing with respect to user needs,

requirements, and business processes conducted to determine

whether a system satisfies the acceptance criteria and to

enable the user, customers or other authorized entity to

determine whether to accept the system.

Phase 4- Stand Up Meeting. used to communicate

problems, solutions, and promote team focus.

Everyone stands up in a circle to avoid long discussions. It is

more efficient to have one short meeting that every one is

M ANGALDAN N ATIONAL H IGH S CHOOL – S ENIOR H IGH S CHOOL


5
required to attend than many meetings with a few developers

each.

The developers will have meetings to improve

communications, eliminate other meetings, identify

impediments to development for removal, highlight and

promote quick decision-making, and improve the

Development Team's level of knowledge.

Phase 5- Pair Negotiation The term pair negotiation is

used to describe how two pair programmers arrive at the

best solution together. When pairing is working at its best,

each person brings to the partnership his or her own set of

skills, abilities, and outlooks and both partners share the

same goal for completing the task.

The developers will combine two sets of skills for design

and implementation and acquiring and/or improving skills

while delivering value through working with another.

Phase 6- Unit Test. determine whether a given feature

works as intended. Programmers write as many automated

M ANGALDAN N ATIONAL H IGH S CHOOL – S ENIOR H IGH S CHOOL


6
tests as they can think of that might "break" the code; if all

tests run successfully, then the coding is complete. Every

piece of code that is written is tested before moving on to the

next feature.

The developers tested the system to build confidence

that the code works correctly. Tests also provide the safety net

enabling pairs of programmers to make changes to any piece

of code in the system without

fear.

Phase 7- Pair Programming. is an Agile technique

originating from Extreme programming (XP) in which two

developers team together and work on one computer. The two

people work together to design, code and test user stories.

Ideally, the two people would be equally skilled and would

each have equal time at the keyboard.

The developers cooperated with each other to ensure

developing higher quality code, faster while also reducing risk

and spreading knowledge in an organization. With pair

M ANGALDAN N ATIONAL H IGH S CHOOL – S ENIOR H IGH S CHOOL


7
programming, two software developers work on one computer,

collaborating on the same design, algorithm, code, or test.

Phase 8 – Code. is the phase during which the actual

code is created by implementing specific XP practices such as

coding standards, pair programming, continuous integration,

and collective code ownership (the entire list is described

below).

The developers will check or revise the code simplicity

and clarity, expecting changes in the customer's requirements

as time passes and the problem is better understood, and

frequent communication with the user and among

programmers.

II SOURCES OF DATA

In order for the developers to identify the contents and

features to be integrate in the Guidance Records System, data

were gather through one sources; the primary sources of data.

The primary source of data were gathered through giving

survey questionnaires to the school’s principal Dr. Leo E.

M ANGALDAN N ATIONAL H IGH S CHOOL – S ENIOR H IGH S CHOOL


8
Blaquir and the school’s assistant principal Mr. Melvin M.

Callanta. The survey questionnaires were also hand to the

guidance counselors Ma’am Melissa Ines D. De Guia and

Ma’am Maria Amor Vena E. Biagtan.

III INSTRUMENTS AND DATA COLLECTION

Different techniques were use to define the requirements in

the development of the system. These techniques are

important in gathering the data requirements of the system

that was essential for the success of the system. The

developers also gathered information through survey

questionnaires. Preliminary questions were asked to elicit

pertinent information and specifications need in the system

development.

Survey Questionnaire. A survey questionnaire is a set

of questions used in a survey. The survey questionnaire is a

type of data gathering method that is utilized to collect,

M ANGALDAN N ATIONAL H IGH S CHOOL – S ENIOR H IGH S CHOOL


9
analyze and interpret the different views of a group of people

from a particular population (Rancour,2014).

The developers conducted a survey questionnaire with

the guidance counselors. The succeeding surveys were mainly

focused on the developed system’s user-friendliness, usability,

information, and design and navigation (shown in Appendix

E).

IV TOOLS FOR DATA ANALYSIS

The researchers used different tools in analyzing gathere

data. These include:

Wireframe. are a simplified visual guide that represents the

skeletal framework of a website. Prior to the design,

wireframes are usually presented in black and white, and do

not define any visual style, typography or imagery. Similarly,

in wireframes, we define the pages and the functionality

forms, video, image galleries, navigation, etc) required to

achieve the goals of your website (Jartos, 2017).

The developers use wireframe to represents the skeletal

M ANGALDAN N ATIONAL H IGH S CHOOL – S ENIOR H IGH S CHOOL


10
framework of the user interface and also used in arranging

elements to accomplish particular purpose (shown in

Appendix F).

Data Flow Diagram. Data Flow Diagram (DFD) is a graphical

representation of the “flow” of data through an information,

modeling its process aspects. Often it is a preliminary step

used to create an overview of the system that can later be

elaborated. DFDs can also be used for the visualization of

data processing (structured design) and show what kind of

information will be input to and output from the system,

where the data will come from and go to, and where the data

will be stored ( Scheel and Foldager, 2015).

The developers use data flow diagram because it is simple

way to comprehend the flow of the data through the system. It

is a guide to in identifying the related processes and detailed

information that passes through the system (shown in

Chapter 4, part II).

M ANGALDAN N ATIONAL H IGH S CHOOL – S ENIOR H IGH S CHOOL


11
Visual Table of Contents. Visual Table of Contents

(VTOC) diagram and it is used to develop a top-down

hierarchical structure through which systems functions and

their relationships can be observed, discussed, and better

understood. The second type is frequently called an IPO

diagram because it describes the input, output, and process

components for a given function (Frantiska, 2017).

The developers used the visual table of contents to

identify the various systems functions and their relationships

can be observed, discussed, and better understood (shown in

Chapter 4, part II).

Likert Scale. Likert Scale assumes that the

strength/intensity of an attitude is linear, i.e. on a continuum

from strongly agree to strongly disagree, and makes the

assumption that attitudes can be measured (McLeod, 2019).

The developers used Likert Scale to measure the

opinions of the respondents and to identify when its strongly

agree to strongly disagree

M ANGALDAN N ATIONAL H IGH S CHOOL – S ENIOR H IGH S CHOOL


12
(shown in Chapter 4, part IV).

M ANGALDAN N ATIONAL H IGH S CHOOL – S ENIOR H IGH S CHOOL


13

You might also like