2017•Unpublished venueRequires access

Guidelines for selecting agile development method in system requirements definition

Shinobu Komai, Hiroshi Nakanishi, Hamdani Saidi

Open publisher page 2 citations

Abstract

There are two IT system software development methods, namely Waterfall and Agile. In Waterfall, the development of software starts after all requirement definitions of the system are completed, while for Agile, software development starts when one of the functions is completed in the system requirement definition. There are very few research about the man-hour comparison between the Waterfall and Agile method. This paper shows how to decide Agile at the beginning of the requirement definition. The guideline for selecting Agile and conditions to undertake Agile development in system requirements definition provide and validate with opinions by Agile experts. Finally, consideration for selecting Agile development method in system requirements definition are drawn out from those results and industrial experiences.

About this research paper

What this paper is about

There are two IT system software development methods, namely Waterfall and Agile. In Waterfall, the development of software starts after all requirement definitions of the system are completed, while for Agile, software development starts when one of the functions is completed in the system requirement definition. There are very few research about the man-hour comparison between the Waterfall and Agile method. This paper shows how to decide Agile at the beginning of the requirement definition. The guideline for selecting Agile and conditions to undertake Agile development in system requirements definition provide and validate with opinions by Agile experts. Finally, consideration for selecting Agile development method in system requirements definition are drawn out from those results and industrial experiences.

Why it matters

OpenAlex reports 2 citations for this work. Citation counts describe recorded attention and do not establish research quality.

Key contribution

A contribution statement is not available in the OpenAlex record.

Method / approach

Method details are not available in the OpenAlex metadata.

Main findings

Findings are not separately available in the OpenAlex metadata.

Limitations

Limitations are not available in the OpenAlex metadata.

Applications

Application details are not available in the OpenAlex metadata.

Available abstract

There are two IT system software development methods, namely Waterfall and Agile. In Waterfall, the development of software starts after all requirement definitions of the system are completed, while for Agile, software development starts when one of the functions is completed in the system requirement definition. There are very few research about the man-hour comparison between the Waterfall and Agile method. This paper shows how to decide Agile at the beginning of the requirement definition. The guideline for selecting Agile and conditions to undertake Agile development in system requirements definition provide and validate with opinions by Agile experts. Finally, consideration for selecting Agile development method in system requirements definition are drawn out from those results and industrial experiences.

Key concepts: Agile software development, Waterfall, Waterfall model, Agile Unified Process, Requirement, Lean software development, Agile usability engineering, Requirements analysis

Related papers

Back to paper searchBrowse research topicsOriginal source
Guidelines for selecting agile development method in system requirements definition — Research Paper | ScholarLens