Skip to main content

MSF for CMMI Process Improvement

Go Search
Home
  
MSF for CMMI Process Improvement > Wiki Pages > Activity - Allocate Product Component Requirements  

Activity - Allocate Product Component Requirements

Activity Information

Allocate Product Component Requirements

Description

Allocation of the product requirements (functional, interface, security, safety, or operational) to components depends on the selection of the architecture, or technical, solution. One product requirement may be covered by more than one component, and which component(s) will address a requirement may change depending on the selected architecture. If more than one component is to address a single product requirement, then the requirement is split into the appropriate parts prior to allocation to the separate components.

Attributes

Element Categories[CMMI Track 2] Planning, [CMMI Level 3] RD SP 2.2
When

After product requirements are baselined.

Entry Criteria

Architectural Solution Selected:
The architectural solution has been selected.

Functional Requirements Baselined:
The functional requirements are reviewed, approved, and baselined.

Interface Requirements Baselined:
The interface requirements are reviewed, approved, and baselined.

Security Requirements Baselined:
The security requirements are reviewed, approved, and baselined.

Safety Requirements Baselined:
The safety requirements are reviewed, approved, and baselined.

Operational Requirements Baselined:
The operational requirements are reviewed, approved, and baselined.

Exit Criteria

Product Component Requirements Allocated:
The product component requirements have been derived from product requirements and are allocated to components.

Is RequiredYes

Steps

  1. Analyze Product Requirements:

    Analyze the product requirements. Record initial recommendations for allocation to components.
  2. Analyze Architecture:

    Analyze the architectural solution. Compare component interaction contained in the architecture to the added functionality in the product requirements.
  3. Match Product Requirements to Components:

    Match each product requirement to one or more component in preparation for allocation.
  4. Derive Product Component Requirements:

    For those product requirements that are to be addressed by more than one component, split the functionality of the requirement into the appropriate pieces for each of the components. Optionally, some product requirements that are addressed by a single component might also need to be broken out into multiple product component requirements to provide additional detail or facilitate incremental development.
  5. Allocate Requirements to Components:

    Allocate the product component requirements to the components.

Inputs and Outputs

WorkProductInputOutputAllowable States
RequirementActive

Successors

TypeNameDependency Type
Define Functional RequirementsFinish-Start
Define Interface RequirementsFinish-Start

Last modified at 12/19/2007 10:37 AM  by Administrator