@inproceedings{a4bcdc636a974614a1e2351ea6c5894b,
title = "A case study: Requirements elicitation processes throughout a project",
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.",
author = "Takako Nakatani and Shouzo Hori and Naoyasu Ubayashi and Keiichi Katamine and Masaaki Hashimoto",
year = "2008",
doi = "10.1109/RE.2008.46",
language = "English",
isbn = "9780769533094",
series = "Proceedings of the 16th IEEE International Requirements Engineering Conference, RE'08",
pages = "241--246",
booktitle = "Proceedings of the 16th IEEE International Requirements Engineering Conference, RE'08",
note = "16th IEEE International Requirements Engineering Conference, RE'08 ; Conference date: 08-09-2008 Through 12-09-2008",
}