El propósito de Acquisition Requirements Development (ARD), perteneciente al Nivel 2, es producir y analizar los requerimientos del cliente y del contrato.
Los requerimientos son la base para la elección y el diseño o configuración del producto adquirido. El desarrollo de los requerimientos incluye las siguientes actividades: (1) Análisis, validación y comunicación de las necesidades del cliente, expectativas y restricciones para obtener los requerimientos del cliente, los cuales constituyen un entendimiento de cómo satisfacer a las partes interesadas, (2) Desarrollo del ciclo de vida de los requerimientos del producto, (3) Establecimiento de los requerimientos del contrato respecto de los requerimientos del cliente a un nivel de detalle suficiente para ser incluido en el paquete y en el acuerdo del proveedor, (4) Desarrollo del concepto operacional y (5) Análisis de las necesidades y requerimientos, ambiente operacional y factores que reflejan las necesidades del cliente y del usuario final.
Los requerimientos incluidos en el paquete forman la base para evaluar las propuestas alternativas, para negociar con los proveedores y comunicarse con el cliente. Los requerimientos del contrato del proveedor son la línea de base del acuerdo del proveedor.
Los requerimientos son identificados y re-definidos durante el ciclo de vida del proyecto. Las decisiones de diseño, las acciones correctivas y la retroalimentación durante cada etapa del ciclo de vida del proyecto es analizada respecto del impacto en los requerimientos del contrato.
ARD se relaciona con las siguientes AP: REQM, SSAD, ATM, AVAL y RSKM.
Los objetivos específicos (SG), prácticas especificas (SP) y subprácticas de esta AP son:
SG 1 - Develop Customer Requirements
SP 1.1 - Elicit Stakeholder Needs
1.1.1 - Engage relevant stakeholders using methods for eliciting needs, expectations, constraints, and external interfaces.
SP 1.2 - Develop and Prioritize Customer Requirements
1.2.1- Translate the stakeholder needs, expectations, constraints, and interfaces into documented customer requirements. 1.2.2- Establish and maintain prioritization of customer requirements 1.2.3- Define constraints for verification and validation.
Producto de trabajo típicos:
Stakeholder needs, expectations, constraints and interfaces (SP 1.1) Prioritized customer requirements (SP 1.2) Customer constraints on the conduct of verification (SP1.2) Customer constraints on the conduct of validation (SP 1.2)
SG 2 - Develop Contractual Requirements
SP 2.1 - Establish Contractual Requirements
2.1.1- Develop functional requirements necessary for determination of alternative solutions and the development of the product by the supplier. 2.1.2- Develop interface requirements of the acquired product to other products in the intended environment. 2.1.3- Develop design constraints necessary for the determination of alternative solutions and the development of the product by the supplier. 2.1.4- Develop requirements for verification and validation of the product developed by the supplier. 2.1.5- Establish and maintain relationships among the requirements under consideration during change management and requirements allocation. 2.1.6- Identify non technical requirements 2.1.7- Establish and maintain a prioritization of contractual requirements
SP 2.2 - Allocate Contractual Requirements
2.2.1- Allocate requirements to supplier deliverables. 2.2.2- Allocate design constraints to supplier deliverables. 2.2.3- Document relationships among allocated requirements and design constraints. 2.2.4- Allocate requirements to suppliers.
Producto de trabajo típicos:
- External interface requirements (SP 2.1) - Contractual requirements (SP 2.1) - Contractual requirements priorities (SP 2.1) - Requirement allocation sheets (SP 2.2)
SG 3 - Analyze and Validate Requirements
SP 3.1 - Establish Operational Concepts and Scenarios
3.1.1- Develop operational concepts and scenarios that include functionality, performance, maintenance, support, and disposal as appropriate. 3.1.2- Define the environment in which the product will operate including boundaries and constraints. 3.1.3- Review operational concepts and scenarios to refine and discover requirements. 3.1.4- Develop a detailed operational concept, as candidate solutions are identified and products and product components solutions are selected by the supplier, that defines the interaction of the product, the end user, and the environment, and that satisfies the operational, maintenance, support, and disposal needs.
SP 3.2 - Analyze Requirements
3.2.1- Analyze stakeholder needs, expectations, constraints, and external interfaces to remove conflicts and to organize into related subjects. 3.2.2- Analyze requirements to determine whether they satisfy higher level requirements. 3.2.3- Analyze requirements to ensure that they are complete, feasible, realizable, and verifiable. 3.2.4- Analyze and propose the allocation of requirements to supplier deliverables. 3.2.5- Identify key requirements that have a strong influence on cost, schedule, functionality, risk, or performance. 3.2.6- Identify technical performance measures to be tracked during the acquisition 3.2.7- Analyze operational concepts and scenarios to refine customer needs, constraints, and interfaces and to discover new requirements.
SP 3.3 - Analyze Requirements to Achieve Balance
3.3.1- Use proven models, simulations, and prototyping to analyze the balance of stakeholder needs and constraints. 3.3.2- Perform a risk assessment on the requirements and design constraints. 3.3.3- Examine product life-cycle concepts for impacts of requirements on risks
SP 3.4 - Validate Requirements
3.4.1- Analyze the requirements to determine the risk that the resulting product will not perform appropriately in its intended-use environment. 3.4.2- Explore the adequacy and completeness of requirements by developing product representations and by obtaining feedback about them from relevant stakeholders. 3.4.3- Assess the product and product components as they are developed by the supplier in the context of the validation environment to identify issues and expose unstated needs and customer requirements.
Productos de trabajo típicos:
Operational, maintenance, support and disposal concepts (SP 3.1) Uses cases (SP 3.1) New requirements (SP 3.1) Requirements defects reports (SP 3.2) Proposed requirements changes to resolve defects (SP 3.2) Key requirements (SP 3.2) Technical performance measures (SP 3.2) Assessment of risks related to requirements (SP 3.3) Records of analysis methods and results (SP 3.4)
Resultado del Proveedor:
Requirements and validation methods (SP 3.4)
CONFIGURATION MANAGEMENT (CM)
El propósito de Configuration Management (CM), perteneciente al Nivel de Madurez 2, es establecer y mantener la integridad de los productos de trabajo usando la identificación de la configuración, control de la configuración, explicación del estado de la configuración, y auditorias de la configuración.
Los productos de trabajo relacionados a CM incluyen: productos entregados al cliente, productos de trabajo internos diseñados, productos adquiridos, herramientas, y otros ítems usados en la creación y descripción de estos productos de trabajo.
Esta área de proceso no solo aplica el manejo de la configuración en los proyectos, sino en los productos de trabajo de la organización (estándares, procedimientos y librerías de reutilización).
CM se relaciona con las siguientes áreas de proceso: AM, PP y PMC.
Los objetivos específicos (SG), prácticas especificas (SP) y subprácticas de esta AP son:
SG 1 - Establish Baselines
SP 1.1 - Identify Configuration Items
1.1.1- Select the configuration items and the work products that compose them based on documented criteria. 1.1.2- Assign unique identifiers to configuration items. 1.1.3- Specify the important characteristics of each configuration item. 1.1.4- Specify when each configuration item is placed under configuration management. 1.1.5- Identify the owner responsible for each configuration item.
SP 1.2 - Establish a Configuration Management System
1.2.1- Establish a mechanism to manage multiple levels of control 1.2.2- Store and retrieve configuration items in a configuration management system. 1.2.3- Share and transfer configuration items between control levels in the configuration management system. 1.2.4- Store and recover archived versions of configuration items. 1.2.5- Store, update, and retrieve configuration management records. 1.2.6- Create configuration management reports from the configuration management system. 1.2.7- Preserve the contents of the configuration management system. 1.2.8- Revise the configuration management structure as necessary.
SP 1.3 - Create or Release Baselines
1.3.1- Obtain authorization from the configuration control board (CCB) before creating or releasing baselines of configuration items. 1.3.2- Create or release baselines only from configuration items in the configuration management system. 1.3.3- Document the set of configuration items that are contained in a baseline. 1.3.4- Make the current set of baselines readily available.
Productos de trabajo típicos
Identified configuration items (SP 1.1) Configuration management system with controlled work products (SP 1.2) Configuration management system access control procedures (SP 12.) Change request database (SP 1.2) Baselines (SP 1.3) Description of baselines (SP 1.3)
Productos de trabajo del Proveedor
Product baselines (SP 1.3) Description of product baselines (SP 1.3)
SG 2 - Track and Control Changes
SP 2.1- Track Change Requests
2.1.1- Initiate and record change requests in the change request database. 2.1.2-Analyze the impact of changes and fixes proposed in change requests. 2.1.3-Review change requests to be addressed in the next baseline with relevant stakeholders and get their agreement. 2.1.4-Track the status of change requests to closure.
SP 2.2 - Control Configuration Items
2.2.1- Control changes to configuration items throughout the life of the product. 2.2.2- Obtain appropriate authorization before changed configuration items are entered into the configuration management system. 2.2.3- Check in and check out configuration items from the configuration management system for incorporation of changes in a manner that maintains the correctness and integrity of the configuration items. 2.2.4- Perform reviews to ensure that changes have not caused unintended effects on the baselines 2.2.5- Record changes to configuration items and reasons for the changes as appropriate.
Productos de trabajo típicos
Change requests (SP 2.1) Revision history of configuration items (SP 2.2) Archives of baselines (SP 2.2)
Producto de trabajo del Proveedor
Change requests (SP 2.1)
SG 3 - Establish Integrity
SP 3.1 - Establish Configuration Management Records
3.1.1- Record configuration management actions in sufficient detail so the content and status of each configuration item is known and previous versions can be recovered. 3.1.2- Ensure that relevant stakeholders have access to and knowledge of the configuration status of the configuration items. 3.1.3- Specify the latest version of the baselines. 3.1.4- Identify the version of configuration items that constitute a particular baseline. 3.1.5- Describe the differences between successive baselines. 3.1.6- Revise the status and history of each configuration item as necessary.
SP 3.2 - Perform Configuration Audits
3.2.1- Assess the integrity of the baselines. 3.2.2- Confirm that configuration management records correctly identify configuration items. 3.2.3- Review the structure and integrity of the items in the configuration management system. 3.2.4- Confirm the completeness and correctness of items in the configuration management system. 3.2.5- Confirm compliance with applicable configuration management standards and procedures. 3.2.6- Track action items from the audit to closure.
Productos de trabajo típicos
Revision history of configuration items (SP 3.1) Change log (SP 3.1) Status of configuration items (SP 3.1) Differences between baselines (SP 3.1) Configuration audit results (SP 3.2) Action items (SP 3.2)
Productos de trabajo del Proveedor
Revision history of product and supplier deliverables defined in the supplier agreement (SP 3.1) Change log (SP 3.1) Copy of the change requests (SP 3.1) Status of product and supplier deliverables (SP 3.1) Differences between baselines (SP 3.1) Supplier configuration audit results (SP 3.2)