The purpose of Technical Solution is to design, develop, and implement solutions to requirements. Solutions, designs, and implementations encompass products, product components, and product-related lifecycle
processes either singly or in combinations as appropriate.
The Technical Solution process area is applicable at any level of the product architecture and to every product, product component, productrelated life-cycle process, and service. The process area focuses on the
following:
· Evaluating and selecting solutions (sometimes referred to as "design approaches," "design concepts," or "preliminary designs") that potentially satisfy an appropriate set of allocated requirements
· Developing detailed designs for the selected solutions (detailed in the context of containing all the information needed to manufacture, code, or otherwise implement the design as a product or product component)
· Implementing the designs as a product or product component Typically, these activities interactively support each other
. Some level of design, at times fairly detailed, may be needed to select solutions.
Product-component prototypes may be used as a means of gaining sufficient knowledge to develop a technical data package or a complete set of requirements.
Technical Solution specific practices apply not only to the product and product components but also to services and product-related life-cycle processes. The product-related life-cycle processes are developed in
concert with the product or product component. Such development may include selecting and adapting existing processes (including standard processes) for use as well as developing new processes.
Processes associated with the Technical Solution process area receive the product and product-component requirements from the requirements management processes. The requirements management processes place the requirements, which originate in requirements development processes, under appropriate configuration management and maintain their traceability to previous requirements.
For a maintenance or sustainment organization, the requirements in need of maintenance actions or redesign may be driven by user needs or latent defects in the product components. New requirements may arise from changes in the operating environment. Such requirements can be uncovered during verification of the product(s) where actual performance can be compared against the specified performance and unacceptable degradation can be identified. Processes associated with the Technical Solution process area should be used to perform the maintenance or sustainment design efforts.
Specific and Generic Goals
SG 1 Select Product-Component Solutions
Product or product-component solutions are selected from alternative solutions.
SG 2 Develop the Design
Product or product-component designs are developed.
SG 3 Implement the Product Design
Product components, and associated support documentation, are implemented from their designs.
GG 3 Institutionalize a Defined Process
The process is institutionalized as a defined process.
Practice-to-Goal Relationship Table
SG 1 Select Product-Component Solutions
SP 1.1 Develop Detailed Alternative Solutions and Selection Criteria
SP 1.2 Evolve Operational Concepts and Scenarios
SP 1.3 Select Product-Component Solutions
SG 2 Develop the Design
SP 2.1 Design the Product or Product Component
SP 2.2 Establish a Technical Data Package
SP 2.3 Design Interfaces Using Criteria
SP 2.4 Perform Make, Buy, or Reuse Analyses
SG 3 Implement the Product Design
SP 3.1 Implement the Design
SP 3.2 Develop Product Support Documentation
GG 3 Institutionalize a Defined Process
GP 2.1 (CO 1) Establish an Organizational Policy
GP 3.1 (AB 1) Establish a Defined Process
GP 2.2 (AB 2) Plan the Process
GP 2.3 (AB 3) Provide Resources
GP 2.4 (AB 4) Assign Responsibility
GP 2.5 (AB 5) Train People
GP 2.6 (DI 1) Manage Configurations
GP 2.7 (DI 2) Identify and Involve Relevant Stakeholders
GP 2.8 (DI 3) Monitor and Control the Process
GP 3.2 (DI 4) Collect Improvement Information
GP 2.9 (VE 1) Objectively Evaluate Adherence
GP 2.10 (VE 2) Review Status with Higher Level Management
