Fleckner und Simon Informationstechnik GmbH              http://www.FlecSim.de

4.1.3 ACQ 11 Technical requirements
Process ID  ACQ.11
Process Name

Technical Requirements

Process Purpose

The purpose of the Technical requirements process is to establish the technical requirements of the acquisition. This involves the elicitation of functional and non-functional requirements that consider the deployment life cycle of the products so as to establish a technical requirement baseline.

 
Process Outcomes

As a result of successful implementation of this process:

  1. the technical requirements, including environment effect evaluation, safety and security requirements where appropriate, are defined and developed to match needs and expectations;

  2. the current and evolving acquisition needs are gathered and defined;

  3. the requirements and potential solutions are communicated to all affected groups;

  4. a mechanism is established to incorporate changed or new requirements into the established baseline;

  5. a mechanism for identifying and managing the impact of changing technology to the technical requirements is defined; and

  6. the requirements include compliance with relevant standards, including environment effect evaluation, safety and security standards where appropriate.

NOTE: ISO/IEC 9126 may be a useful model to elicit technical requirements.

Base Practices

ACQ.11.BP1: Elicitate needs. Elicitate the needs of all relevant user groups. [Outcome 1]

ACQ.11.BP2: Define technical requirements. Define and develop the technical requirements and potential solutions (where relevant), including environment effect evaluation, safety and security,

performance, supportability requirements to match the needs and expectations of the relevant user groups. [Outcome 1]

NOTE 1: This may includethe categorization, prioritization and indication of requirements

the indication of mandatory requirements classification of requirements into functional areas

using defined End User types to describe the functional requirements within an organization.

ACQ.11.BP3: Identify acquisition needs. Gather and define the current and evolving acquisition needs. [Outcome 2]

ACQ.11.BP4: Ensure consistency. Ensure consistency of the technical requirements with the defined acquisition needs. [Outcome 2]

ACQ.11.BP5: Identify affected groups. Identify all groups to which the technical requirements and potential solutions should be communicated. [Outcome 3]

ACQ.11.BP6: Communicate to affected groups. Communicate the technical requirements and potential solutions to all affected groups. [Outcome 3]

NOTE 2: To ensure a better understanding

the requirements might be specified in business terms

simulation and exploratory prototyping techniques might be used.

ACQ.11.BP7: Establish a change mechanism. Establish a mechanism to incorporate changed or new technical requirements into the established baseline. [Outcome 4]

NOTE 3: This may include analyzing, structuring and prioritizing technical requirements according to their importance to the business.

ACQ.11.BP8: Track impact of changing technology. Define a mechanism for identifying and managing the impact of changing technology to the technical requirements and integrate the resulting

consequences into the technical requirements. [Outcome 5]

ACQ.11.BP9: Identify constraints and standards. Identify constraints and standards applicable to the technical requirements (e.g. Open Systems standards). [Outcome 6]

ACQ.11.BP10: Ensure compliance of stated requirements. Ensure that the technical requirements include compliance with identified relevant standards, including environment effect evaluation, safety and security standards where appropriate. [Outcome 6]

Output Work Products

13-17 Customer request [Outcome 1]

14-50 Stakeholder groups list [Outcome 1]

08-28 Change management plan [Outcome 4]

08-51 Technology monitoring plan [Outcome 5]

13-04 Communication record [Outcome 3]

17-00 Requirement specification [Outcome 6]

17-03 Customer requirements [Outcome 6]

13-24 Validation results [Outcome 6]

13-21 Change control record [Outcome 2]

14-01 Change history [Outcome 2]

14-02 Corrective action register [Outcome 2]

 
 

5.Process Capability Indicators

Level 2: Managed process

Level 3: Established process

Level 4: Predictable process

Level 5: Optimizing process