Which statement accurately describes traceability across stakeholder needs and development artifacts?

Which statement accurately describes traceability across stakeholder needs and development artifacts?

• A. It only ensures design is traceable to code.
• B. It ensures stakeholders' needs are linked through requirements to design, implementation, and validation artifacts.
• C. It is unnecessary once baselines are established.
• D. It is achieved only by documenting test cases.

Answer: (B)

Traceability across stakeholder needs and development artifacts means creating a continuous, auditable link from what stakeholders require all the way through to the design decisions, the implemented code, and the validation activities. It’s about showing that every need is addressed and that each artifact along the development life cycle can be traced back to a specific requirement or stakeholder intent, and that changes can be analyzed for impact across the chain. The best statement reflects that complete chain: stakeholders’ needs are linked through requirements to design, implementation, and validation artifacts. This captures the end-to-end traceability that CMMI emphasizes, ensuring alignment from initial needs through to delivery and verification. Why the other ideas don’t fit as well: focusing only on design to code narrows the traceability to a subset of the chain and misses the original needs and later validation steps. Thinking traceability becomes unnecessary after baselines ignores the ongoing need to manage changes and confirm continued alignment as the project evolves. Relying only on documenting test cases misses the broader linkage back to stakeholder needs and the full set of development artifacts, providing at most partial traceability.

Traceability across stakeholder needs and development artifacts means creating a continuous, auditable link from what stakeholders require all the way through to the design decisions, the implemented code, and the validation activities. It’s about showing that every need is addressed and that each artifact along the development life cycle can be traced back to a specific requirement or stakeholder intent, and that changes can be analyzed for impact across the chain.

The best statement reflects that complete chain: stakeholders’ needs are linked through requirements to design, implementation, and validation artifacts. This captures the end-to-end traceability that CMMI emphasizes, ensuring alignment from initial needs through to delivery and verification.

Why the other ideas don’t fit as well: focusing only on design to code narrows the traceability to a subset of the chain and misses the original needs and later validation steps. Thinking traceability becomes unnecessary after baselines ignores the ongoing need to manage changes and confirm continued alignment as the project evolves. Relying only on documenting test cases misses the broader linkage back to stakeholder needs and the full set of development artifacts, providing at most partial traceability.