A Case Study of Requirements Elicitation Process with Changes
2010
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.
Keywords:
- Pattern recognition
- Artificial intelligence
- Systems engineering
- Non-functional testing
- Computer science
- Software requirements specification
- Vision document
- Requirements elicitation
- Non-functional requirement
- Requirements management
- Business requirements
- Requirements analysis
- Requirements engineering
- Process management
- Requirement
- Correction
- Source
- Cite
- Save
- Machine Reading By IdeaReader
16
References
3
Citations
NaN
KQI