A Case Study of Requirements Elicitation Process with Changes

Takako NAKATANI  Shouzo HORI  Naoyasu UBAYASHI  Keiichi KATAMINE  Masaaki HASHIMOTO  

IEICE TRANSACTIONS on Information and Systems   Vol.E93-D   No.8   pp.2182-2189
Publication Date: 2010/08/01
Online ISSN: 1745-1361
DOI: 10.1587/transinf.E93.D.2182
Print ISSN: 0916-8532
Type of Manuscript: PAPER
Category: Software Engineering
requirements engineering,  requirements elicitation process,  case study,  

Full Text: PDF(748.4KB)>>
Buy this Article

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 function to integrate requirements processes with other developmental processes. We have quantitatively and qualitatively investigated the requirements processes of a specific project from beginning to end. Our focus is to clarify the types of necessary requirements based on the components contained within a certain portion of the software architecture. Further, each type reveals its typical requirements processes through its own rationale. This case study is a system to manage the orders and services of a restaurant. In this paper, we introduce the case and categorize its requirements processes based on the components of the system and the qualitative characteristics of ISO-9126. We could identify seven categories of the typical requirements process to be managed and/or controlled. Each category reveals its typical requirements processes and their characteristics. The case study is our first step of practical integrated requirements engineering.