The requirements are the foundation, upon which the software process is built, and the Requirements Management (RM) process emerges as a systematic approach to find, document, organize, and track all system's requirements during the life cycle.
According to a SEI’s Study, the top two out of ten factors that contribute to the failure of system
development projects are requirements problems. These problems are mainly associated with an inadequate requirements specification and/or an insufficient requirements change management. Also the Standish Group's CHAOS report found that the major factors that cause software projects to fail are:
- Lack of user input
- Incomplete requirements specifications
- Changing requirement specifications.
Therefore, RM process is considered the cornerstone of the software lifecycle and CMMI identifies the enormous importance of the RM, granting the category of “Process Area” and placing it in the CMMI, staged representation, maturity level two. According to the CMMI, the Requirements Management major aim is establishing an agreement between the customer and the software team on the meaning of the requirements.
No comments:
Post a Comment