Applying knowledge principles to requirements management.

Abstract

Requirements management is gathering, defining, modeling, analyzing, documenting, communicating and managing of all stakeholder wishes and needs into a software product. The field of requirements management is full of challenges. Both practitioners and scientists are struggling with challenges, including questions like “how to improve requirements transferability?”, “how to define requirements generic?”, “how to make requirements understandable for different stakeholders?”, and “how to track requirements during software development?”. 80% of outsourcing projects fail because of poor requirements management. Software development depends on requirements management. Incorrect or missing requirements lead to incorrect or missing functionality. Applying principles of knowledge management to requirements management has a potential to increase readability, understandability, correctness, completeness, and transferability of requirements. Furthermore, scientists have indicated a potential to elicit and define requirements faster, and at reduced costs when applying knowledge management principles. This is achieved by making requirements management including processes, steps, techniques, and deliverables more efficient, correct, and inline with stakeholder wishes and needs.