CHAPTER III

METHODOLOGY

This chapter presents the system design of the proponent’s system.

SYSTEM DEVELOPMENT LIFE CYCLE (SDLC)

The Software Development Life Cycle (SDLC) is a framework defining tasks

performed at each step in the software development process. It is a structure followed by

a development team with in the software organization. It consists of a detailed plan

describing how to develop, maintain and replace the specific software. The life cycle

defines the methodology for improving the quality of the software and over all

development process. The proponents will use the Rational Unified Process Methodology

as a guide of processing the system flow.

EXTREME PROGRAMMING METHODOLOGY

 Figure 1: Extreme Programming Methodology

Figure 1: Shows the Extreme Programming Methodology Diagram used by the

proponents as their model for their system. It shows how the process works. Extreme

Programming (XP) is an agile software development methodology which is intended to

improve software quality and responsiveness to changing customer requirements.

Extreme Programming aims to provide iterative and frequent releases throughout the

project, allowing both members and customers to examine and review the projects

progress throughout the entire SDLC. It helps the proponents work together on

everything from requirements to code. Proponents work in pairs; pair programming and

never feel alone or forgotten. The whole process in XP is visible and accountable.

Proponents will commit what they will accomplish and show progress. The advantage of

Extreme Programming (XP) from the other methodologies is that it marks a departure

from the conventional programming approach. It stresses importance to individuals and

interactions over processes and tools, working software over documentation, customer

collaboration over contract negotiation, and responding to change over following a plan.

Release Plan

The proponents used release planning meeting that used to create a release plan

for the development team to estimate and create an initial end-to-end working system. It

gives an ideal week on how long the proponents would take to implement that story if

they absolutely nothing else to do. No dependencies, no extra work, but do include tests.

Iteration Plan

The proponents plans the task where the team is given direction every couple of

weeks. XP teams build software in two-week iterations, delivering running useful

software at the end of each iteration. During iteration planning, the customer presents the

features desired for the next two weeks.

Acceptance Test

The proponents use acceptance test for the customers to ensure that the overall

system contains all the required features. The acceptance tests should be done at each of

the iterations of the process to ensure that the new release contains all the features agreed

upon.

Stand-up Meeting
 The proponents stand must report at least three things; what was accomplished

yesterday, what will be attempted today, and what problems are causing delays. The daily

stand up meeting is not another meeting to waste people's time.

Pair Negotiation

The proponents continue two sets for design and implementation to yield the

bear solution.

Unit Test

The proponents are automated tests written during the coding phase

to test features. Unit tests are very important as it can save a large amount

of effort.

Pair Programming

The two proponents works on one computer. Pair programming is one of the

practices that distinguish the XP methodology. Each pair of programmers works together

to develop certain functionality. This increases software quality. In addition to a better

code quality, it helps with communicating knowledge.