The process of assigning requirements to solution components and releases to best achieve the objectives is called:

Requirements allocation is the process of assigning requirements to solution components and releases to best achieve the objectives. This involves distributing responsibilities for fulfilling requirements among various parts of the solution, which can include business processes, software applications, and hardware components. It is a critical step in the design definition phase, ensuring that the solution design is complete and that there is a clear plan for implementing each requirement within a specific release or iteration.

A. requirements classification schema. This is a framework used to categorize requirements based on predefined attributes (e.g., priority, source, type), not the process of assigning them to solution components.
B. requirements traceability. This involves linking requirements to other artifacts (like test cases or design elements) to manage their lifecycle and dependencies, not the act of assigning them.
D. requirements architecture. This refers to the structure of all requirements and their interrelationships, providing a cohesive model, rather than the process of distributing them among solution components.

1. IIBA

A Guide to the Business Analysis Body of Knowledge (BABOK Guide)

Version 3

2015. Section 7.4.4.3

"Allocate Requirements

" states

"Requirements allocation is the process of assigning requirements to solution components and releases to best achieve the objectives." (p. 156).

2. Wiegers

K.

& Beatty

J. Software Requirements

3rd Edition

Microsoft Press

2013. While not an IIBA publication

this is a foundational academic text. Chapter 15

"Allocating Requirements

" discusses the process of partitioning requirements among software

hardware

and human subsystems

which aligns directly with the concept of requirements allocation. (This is a widely used text in university software engineering curricula).