A case study of requirements elicitation process with changes

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

Research output: Contribution to journalArticle

4 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 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.

Original languageEnglish
Pages (from-to)2182-2189
Number of pages8
JournalIEICE Transactions on Information and Systems
VolumeE93-D
Issue number8
DOIs
Publication statusPublished - Jan 1 2010

Fingerprint

Requirements engineering
Software architecture

All Science Journal Classification (ASJC) codes

  • Software
  • Hardware and Architecture
  • Computer Vision and Pattern Recognition
  • Electrical and Electronic Engineering
  • Artificial Intelligence

Cite this

A case study of requirements elicitation process with changes. / Nakatani, Takako; Hori, Shouzo; Ubayashi, Naoyasu; Katamine, Keiichi; Hashimoto, Masaaki.

In: IEICE Transactions on Information and Systems, Vol. E93-D, No. 8, 01.01.2010, p. 2182-2189.

Research output: Contribution to journalArticle

Nakatani, Takako ; Hori, Shouzo ; Ubayashi, Naoyasu ; Katamine, Keiichi ; Hashimoto, Masaaki. / A case study of requirements elicitation process with changes. In: IEICE Transactions on Information and Systems. 2010 ; Vol. E93-D, No. 8. pp. 2182-2189.
@article{606ff1ce45084e188560f31b89862aef,
title = "A case study of requirements elicitation process with changes",
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 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.",
author = "Takako Nakatani and Shouzo Hori and Naoyasu Ubayashi and Keiichi Katamine and Masaaki Hashimoto",
year = "2010",
month = "1",
day = "1",
doi = "10.1587/transinf.E93.D.2182",
language = "English",
volume = "E93-D",
pages = "2182--2189",
journal = "IEICE Transactions on Information and Systems",
issn = "0916-8532",
publisher = "一般社団法人電子情報通信学会",
number = "8",

}

TY - JOUR

T1 - A case study of requirements elicitation process with changes

AU - Nakatani, Takako

AU - Hori, Shouzo

AU - Ubayashi, Naoyasu

AU - Katamine, Keiichi

AU - Hashimoto, Masaaki

PY - 2010/1/1

Y1 - 2010/1/1

N2 - 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.

AB - 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.

UR - http://www.scopus.com/inward/record.url?scp=77956032522&partnerID=8YFLogxK

UR - http://www.scopus.com/inward/citedby.url?scp=77956032522&partnerID=8YFLogxK

U2 - 10.1587/transinf.E93.D.2182

DO - 10.1587/transinf.E93.D.2182

M3 - Article

VL - E93-D

SP - 2182

EP - 2189

JO - IEICE Transactions on Information and Systems

JF - IEICE Transactions on Information and Systems

SN - 0916-8532

IS - 8

ER -