Knowledge and management of software requirements

Abstract

In software engineering, requirements from customers, users, and stakeholder are initial information for software development process. The requirements elicited and gained are defined, classified, refined, and stored systematically according to needs management principles. Therefore, the requirements would be correct and ready to be used in the next step of development process. This process is called Software Requirements Engineering. If the gained software requirements are incorrect, lack quality, or are managed unsystematically, they could lead to project failure and low-quality software product which cannot meet the needs of users and stakeholders. For these reasons, this article proposed an overview of software requirements and an approach for software requirements management, level of software requirements, quality of software requirements and understanding of quality aspect, common problems of requirements elicitation, and awareness of impact and damage due to incorrect or low quality requirements. Success factors of software requirements management and 1-10-100 rules are also discussed. Finally, the article addresses roles and goals of software requirements management team.