7. Rquirements Analysis & Design Definition

A knowledge area describes how business analysts structure, model, verify, and validate requirements and designs, explore solution alternatives, and recommend the option that yields the greatest potential value.

The Requirements Analysis and Design Definition (RADD)

Focus on understanding and defining the need (the what and why).

Requirements

Focus on the solution and how that need will be satisfied (the how).

Designs

A core task of RADD: Analyze, synthesize, and refine elicitation results into formal requirements and designs.

Specify and Model Requirements

A core task of RADD: Ensure requirements/designs meet quality standards (internal consistency, usability, syntax).

Verify Requirements

A core task of RADD: Ensure requirements/designs align to business goals and deliver real business value.

Validate Requirements

A core task of RADD: Fit all models and requirements together into a cohesive, harmonized whole.

Define Requirements Architecture

A core task of RADD: Identify tactical solution approaches (Create, Purchase, Combine) and allocate requirements.

Define Design Options

A core task of RADD: Compare design options (benefits vs. costs vs. risks) and recommend the best path.

Analyze Potential Value & Recommend Solution

What 2 main formats do models use?

1. Matrices

2. Diagrams

Uniform, structured data tables

Matrices

Visual representations of boundaries, hierarchies, and flows

Diagrams

The set of standards, notations, and guidelines defining how requirements will be represented for a specific stakeholder group

Viewpoint (The Template/Convention)

The actual instantiated requirements and diagrams produced for a specific system using that viewpoint.

View

Proves lineage (linking a requirement back to a business objective).

Traceability

Proves cohesion (how all parts fit together into a functioning system).

Architecture

The process of assigning requirements to specific solution components, organizational units, job roles, or staged releases to maximize value delivery.

Requirements Allocation

Benefits minus Costs (accounting for risk and uncertainty)

Value Calculation

The value of the best alternative not selected.

Opportunity Cost

What is the primary difference between requirements verification and requirements validation?

Verification ensures requirements meet quality and notation standards; validation ensures requirements deliver business value and align with business goals.