Requirement Management Guide
What is requirements management?
Why is requirements management important?
How are requirements managed in an organization?
- Stakeholder roles and responsibilities
- Requirements gathering & management process
- Types of requirements
- Requirements artifacts
- Requirements naming and versioning convention
- Requirements prioritization
- Requirements traceability
- Requirements versioning
- Requirements baseline
Requirements Gathering Tools
Business analysts have to carry out requirement gathering and management; this process involves elicitation of requirements, capturing and prioritizing requirements, and then modeling and authoring them as well.
Different tools provide different means to illustrate, explain, and specify exactly what must be delivered to meet the stakeholders’ requirements.
There are a variety of tools that can be used for requirement gathering, depending on the kind of activity requirement gathering that you are undertaking.
For many of the requirement gathering techniques that are commonly deployed by business analysts, requirement management tools suffice, since they involve communication with stakeholders and ideation with the project team.
However, there are other aspects of requirements management such as process documentation, graphical illustrations, and detailed specifications to help in eliciting requirements, communicate proposals and decisions, provide details for the development process, and identify missing or incomplete requirements. These tools are usually called UML tools.
The main utilities of UML modeling tools are:
- Creation of UML diagrams such as use case, sequence diagrams, and activity.
- Preparation of process flow charts
- Creation of data models
- Generation of architecture diagrams