Requirements management is a core function of the BA on projects. There is a great deal written about requirements. This article aims to list some key concepts and provide pointers to further information.
- The purpose of requirements is to ensure the project understand its objectives and to act as a checkpoint for design, development and validation activities.
- Requirements for projects are often complex and involve multple project stakeholders. Requirements are not always met due to time, cost and quality constraints. It is wise to plan your requirements management process at the early stages of a project.
- Constraints are not requirements, but often constraints and requirements are managed together.
- Requirements should be validated by the project sponsor.
- There are a number of tools for documenting and defining requirements. Some of these include but are not limited to UML and BPMN.
- Requirements are often categorized in a number of ways. These categorizations include functional and non-functional, mandatory or optional, and others including Kano analysis.
- Requirements are a critical part of the software development lifecycle. The typical stages of a waterfall SLDC are: Business Case, Business Requirements,
Solution Architecture or System Specification, Solution Design, Solution Construction, Solution Validation (testing) and Implementation.
This article is a stub. You know the drill. We'd love you to expand it.