Evaluate the deployed solution using valuation techniques in order to determine how well the solution meets the business case and value proposition.
Evaluate product options and capabilities by using decision-making and valuation techniques in order to determine which requirements are accepted, deferred, or rejected.
Monitor requirements throughout their lifecycles using a traceability artifact or tool in order to ensure the appropriate supporting requirements artifacts (such as models, documentation, and test cases) are produced, reviewed and approved at each point in the lifecycle.
Define strategy for requirements traceability using traceability tools and techniques in order to establish the level of traceability necessary to monitor and validate the requirements.
Obtain stakeholder sign-off on the developed solution using decision-making techniques in order to proceed with deployment.
Analyze, decompose, and elaborate requirements using techniques such as dependency analysis, interface analysis, and data and process modeling in order to collaboratively uncover and clarify product options and capabilities.
Track requirements using a traceability artifact or tools, capturing the requirements’ status, sources and relationships (including dependencies), in order to provide evidence that the requirements are delivered as stated.
Review the business case, and the project goals and objectives, in order to provide context for business analysis activities.
Elicit or identify requirements, using individual and group elicitation techniques in order to discover and capture requirements with supporting details (e.g., origin and rationale).
Analyze and communicate the solution’s identified gaps and deltas using quality assurance tools and methods in order to enable stakeholders to resolve discrepancies between solution scope, requirements, and developed solution.
Elaborate and specify detailed metrics and acceptance criteria using measurement tools and techniques for use in evaluating whether the solution meets requirements.
Determine stakeholder values regarding the product, using elicitation techniques in order to provide a baseline for prioritizing requirements.
Validate the solution’s test results, reports, and other test evidence against the requirements acceptance criteria in order to determine whether the solution satisfies the requirements.
Define business metrics and acceptance criteria by collaborating with stakeholders for use in evaluating when the solution meets the requirements.
Validate requirements using tools and techniques such as documentation review, prototypes, demos, and other validation methods in order to ensure requirements are complete, accurate and aligned with goals, objectives, and value proposition.
Identify stakeholders by reviewing goals, objectives, and requirements in order that the appropriate parties are represented, informed and involved.