You are on page 1of 5

METHODOLOGY

Research Design

This Study used a descriptive developmental research the furnished

narrative information on research, development, test, and evaluation. Specially, it

used the agile model as basis in the design and development of the job portal

system.

Agile methodology is an approach to the project management which helps

to respond to the unpredictability of building software through incremental,

iterative work cadences, known as sprints. This methodology was developed to

deal with situation where the waterfall model fails. The biggest drawback of

waterfall model is that it assumes that every requirement of the project can be

identified before any design or coding occurs.

Agile methods gives you the flexibility to plan only which you surely know

and leaves the rest of planning for next iteration. Agile are good at reducing

overheads, such as, rationale, justification, documentation and meetings,

keeping them as low as is possible. And, that is why agile methods benefits small

teams with constantly changing requirements, rather more than larger projects.

Face to face communications, agile method give more emphasison having

the face to face communication between the user/customer and the developers

to make sure there is no room left for any kind of confusion in understanding

requirement and inputs (navneetjha 2012).

The developers choose the agile methodology because as at the end of

each stage, the logical program, designed to cope and adapt to new ideas from
the outset, allows changes to be made easily. With Agile, changes can be made

if necessary without getting the entire system re-written.

The following are the phase of Agile model:

Defining the Initial Requirement Phase. The first phase where the start of

development is to gather information such requirement of the system. One of the most

important tasks in the development of the software using the agile method is gathering

and defining the requirements for the project requirements analysis is a rather broad

field of software engineering and project management (Jim Rising 2009).

After the gathering and analysis of the requirements its up to the next phase in the

agile methodology to apply it to the beginning the iteration. Once everything is clear

make sure you get a sign off from the client on the requirement (Ten Step Inc, 2012).

The developers will have to observe the existing process involved in job posting of

Public Employment Services Office (PESO), job inquiry of jobseekers, employment

guidance and skill matching of the Department of Labor and Employment. The

developers will also have an interview in the company in terms of transferring Projects,

Progress report and other files to the other section of the company. And to gather datas

for the hardware, software, requirements, functional and non-functional features. This

phase will specify the problems and the objectives which clearly seek by the

developers.

Begin Iteration Phase. The next phase is the planning and designing system.

Planning and designing system is a phase that emphasizes how the system will perform

the requirements which is identified in the first phase.

In the planning and designing phase, a plan is developed for how the system will
implement the requirements. The plan is expressed using a design method and

notation. Many methods and notations for software design have been developed

(Software Engineering 2009).

In this phase, UML (Unified Modeling Language) is popular for use for

communication with every other page in addition to be documentation created for the

project sponsor. At the end of the phase, a solid plan will be defined for use in

development and a working prototype may be created based on the project (Agile-

model.com 2011).

The developer will prepare the usef0interface design which is the wireframe,

database design and the architecture design of the system.

Build and unit Test Phase. This phase involved of the actual development of the

system and the unit testing. The development and coding of the project may begin even

if the design phase is still ongoing or it may not and waits for the previous phase to

finish its task and then start with and development. And during the development, couple

of unit test will be done on the system.

This phase will initiate while the design phase is still ongoing. Depending on the

complexity of the project; however, this can be one of the most expensive and time

consuming phases of any software development project (The Coding Phase 2004).

By compiling and correcting the errors, all syntax error and removed by the unit test.

Syntax errors are the easy ones to rectify. The logical errors in the programs are the

difficult ones to identify and then rectify. By logical error, we mean, the program behaves

in a way that its not expected to behave.

The role of testers is to identify the logical errors and various stages (Nagoji 2011).
As a result, early feedback from those developing the project is the key to avoiding

significant mistakes that can result in missed deadlines or costly rework. With

requirements gathered, the analysis and design phase, the developers are ready to

build the system and test it by them.

User Evaluation Phase. The final phase in the development of the system is to test

the system in order to implement more and debug more errors in every client

environment.

The user evaluation phase is should be done from the perspective of the system

provider. Because it is nearly impossible to duplicate every possible clients environment

and because systems are released with yet-to-be-discovered errors, the client plays an

important, though reluctant, role in testing (Ronald LeRoiBurback 2008).

In this Phase, the system must be tested by different individuals to find errors to fix.

Continuous testing system will drive the system to a free error bugs. After this phase,

the next will be the change requested which is not phase but decision point in the

project life cycle where client decides whether they need more changes to the products

or not based on the evaluation done in the last stage. If they are happy with the system

and are ready to accept this as a final product, then the system may go the final phase

of system test.

Final System Test Phase. Final system and acceptance testing should be

performed t this point, although as the developer pointed out earlier the majority of

testing should be done during construction iterations.

It is often assumed that the developers and QA tester will develop a system that

precisely meets all defined business requirements. However, real-time complexies and
vast data combinations, limit the spelling out of all business requirements explicity at

such an early stage of a project life cycle.

After the development of test cases, testers execute them and pass or fail them

depending on the expectations of the test cases. When the results do not meet the

expected behavior or the system is unstable, testers raise defects for the developers to

resolve. Once all those cases have completed successfully and all major defects have

been resolve, user acceptance tester may run a regression cycle where the code is

frozen to ensure the final code base is stable, working as per requirements, and defect

free. Once testing is completed, result of the testing are documented.

Through and comprehensive user acceptance testing is vital to ensure the success

of software development. It confirms that the software will meet particular business and

functional requirements, and helps to ensure customer satisfaction (Pierson

Requirements Group, Inc. 2009).