How does it relate to other requirements engineering (RE) or requirements management (RM) processes?
Figure 1: Requirements Engineering Processes Figure 1 identifies five key processes of requirements engineering and their interrelationships. This is premised on an evolutionary development approach where each of the processes would be repeated for each spiral (planned release) of the software effort. There is a dichotomy (evident from the past five years of literature) relating to the role of RM versus other requirements engineering processes. In much of the literature, RM is now viewed as the all-encompassing oversight process that ties the other four processes together to form a cohesive and effective requirements engineering discipline. Yet in many cases, RM is regarded as the last process in a sequence of requirements activities that relates primarily to requirements changes, and is not implemented until after the initial requirements baseline has been established. In this view, RM is ongoing while the other processes are implemented once at the beginning of the project. The DACS
Related Questions
- What does a typical engineering org chart look like for a SaaS company all the way from CTO down to engineers?
- What are the requirements for the M.S.C.E. with a concentration in Construction Engineering and Management?
- How does it relate to other requirements engineering (RE) or requirements management (RM) processes?
