A case study: Requirements elicitation processes throughout a project

Takako Nakatani, Shouzo Hori, Naoyasu Ubayashi, Keiichi Katamine, Masaaki Hashimoto

Research output: Chapter in Book/Report/Conference proceedingConference contribution

15 Citations (Scopus)

Abstract

Requirements changes sometimes cause a project to fail. A lot of projects now follow incremental development processes so that new requirements and requirements changes can be incorporated as soon as possible. These processes are called integrated requirements processes which integrate requirements processes with other development processes. We have investigated the requirements processes of a project from beginning to end, both quantitatively and qualitatively. Our focus is to clarify the types of requirements based on the components contained within a certain portion of the software architecture. Each type reveals its typical requirements processes through its rationale. The case studied is a system to manage the orders and services of a restaurant. In this paper, we introduce the case and describe the types of requirements processes. Then we discuss the reasons why we could not elicit all the requirements in the early development processes.

Original languageEnglish
Title of host publicationProceedings of the 16th IEEE International Requirements Engineering Conference, RE'08
Pages241-246
Number of pages6
DOIs
Publication statusPublished - 2008
Externally publishedYes
Event16th IEEE International Requirements Engineering Conference, RE'08 - Barcelona, Catalunya, Spain
Duration: Sep 8 2008Sep 12 2008

Other

Other16th IEEE International Requirements Engineering Conference, RE'08
CountrySpain
CityBarcelona, Catalunya
Period9/8/089/12/08

All Science Journal Classification (ASJC) codes

  • Software
  • Electrical and Electronic Engineering

Fingerprint Dive into the research topics of 'A case study: Requirements elicitation processes throughout a project'. Together they form a unique fingerprint.

Cite this