ASPICE
-
-
-
-
-
-
- MAN.3.O.4 Interfaces within the project, and with other projects and organizational units, are identified and monitored
- MAN.3.O.3 The activities and resources necessary to complete the work are sizedand estimated
- HWE.1.O.6 Consistency and bidirectional traceability are established between system requirements and hardware requirements. Consistency and bidirectional traceability are established between system architectural design and hardware requirements
- ACQ.15.O.4 Any shortfalls in capability are identified and evaluated
- SWE.4.O.3 Software units are verified according to the software unit verification strategy and the defined criteria for software unit verification and the results are recorded
- SUP.10.O.4 Criteria for confirming implementation of change requests are defined
- PIM.3.O.6 Knowledge gained from the improvement is communicated within theorganization
- SPL.2.O.7 Confirmation of release is obtained
- SUP.9.O.3 Problems are analyzed and assessed to identify an appropriate solution
- SYS.1.O.3 A change mechanism is established to evaluate and incorporatechanges to stakeholder requirements into the baselined requirementsbased on changing stakeholder needs
- SUP.9.O.6 The status of problems and their trend are known
- REU.2.O.7 Feedback, communication, and notification mechanisms areestablished, that operate between affected parties
- HWE.1.O.8 The hardware requirements are agreed and communicated to all affected parties
- SUP.8.O.2 All configuration items generated by a process or project are identified, defined and baselined according to the configuration management strategy
- ACQ.12.O.4 The rights of the acquirer to assume, modify or evaluate, directly orindirectly Intellectual Property Rights are established
- ACQ.13.O.5 Requirements for the completion and acceptance of interim workproducts and release of payments are established
- SWE.4.O.4 Consistency and bidirectional traceability are established between software units, criteria for verification and verification results
- SUP.2.O.2 Criteria for verification of all required work products are identified
- ACQ.11.O.1 The technical requirements, including environment effect evaluation,safety and security requirements where appropriate, are defined anddeveloped to match needs and expectations
- SYS.2.O.1 A defined set of system requirements is established
- ACQ.11.O.6 The requirements include compliance with relevant standards,including environment effect evaluation, safety and security standardswhere appropriate
- SYS.2.O.8 The system requirements are agreed and communicated to all affectedparties
- ACQ.3.O.1 A contract/agreement is negotiated, reviewed, approved and awardedto the supplier(s)
- ACQ.11.O.2 The current and evolving acquisition needs are gathered and defined
- SWE.3.O.6 Software units defined by the software detailed design are produced
- PIM.3.O.5 The effects of process implementation are monitored, measured andconfirmed against the defined improvement goals
- MAN.6.O.3 An appropriate set of measures, driven by the information needs areidentified and/or developed
- SYS.4.O.4 System items are integrated up to a complete integrated system according to the integration strategy
- MAN.3.O.2 The feasibility of achieving the goals of the project with available resources and constraints is evaluated
- SUP.8.O.4 Modifications and releases are made available to affected parties
- SWE.2.O.2 The software requirements are allocated to the elements of thesoftware
- ACQ.4.O.4 Changes to the agreement, if needed, are negotiated between thecustomer and the supplier and documented in the agreement
- SYS.3.O.1 A system architectural design is defined that identifies the elements ofthe system
- MAN.3.O.6 Progress of the project is monitored and reported
- SWE.6.O.3 Test cases included in the software qualification test specification are selected according to the software qualification test strategy and the release plan
- SUP.9.O.5 Problems are tracked to closure
- SYS.2.O.6 Consistency and bidirectional traceability are established between stakeholder requirements and system requirements
- MAN.5.O.2 Appropriate risk management strategies are defined andimplemented
- ACQ.13.O.7 Requirements for ownership of interactions and relationships withsuppliers are defined
- SYS.2.O.7 The system requirements are evaluated for cost, schedule andtechnical impact
- SYS.3.O.3 The interfaces of each system element are defined
- ACQ.14.O.7 A CFP / ITT is prepared and issued in accordance with acquisition policies and which complies with relevant national, international andregulatory laws, requirements, and policies
- SYS.4.O.1 A system integration strategy consistent with the project plan, therelease plan and the system architectural design is developed tointegrate the system items
- SPL.1.O.4 Suitable staff are identified to perform the proposed work
- SYS.5.O.1 A system qualification test strategy including regression test strategy consistent with the project plan and release plan is developed to test the integrated system
- SUP.1.O.6 Management ensures that escalated non-conformances are resolved
- SUP.7.O.2 The standards to be applied for the development of the documentation are identified
- SWE.5.O.6 Integrated software items are tested using the selected test cases and the results of software integration test are recorded
- SYS.3.O.5 Consistency and bidirectional traceability are established between system requirements and system architectural design
- SUP.9.O.2 Problems are recorded, uniquely identified and classified
- ACQ.13.O.2 Requirements for the organizational, management, controlling, andreporting aspects of a project are defined
- SWE.1.O.8 The software requirements are agreed and communicated to allaffected parties
- ACQ.13.O.8 Rights for use and distribution of the product by the customer andsupplier are defined
- SYS.2.O.5 The system requirements are updated as needed
- ACQ.14.O.1 Rules are defined for proposal/tender invitation and evaluation which comply with the acquisition policy and strategy
- ACQ.11.O.3 The requirements and potential solutions are communicated to allaffected groups
- MAN.5.O.6 Appropriate treatment is taken to correct or avoid the impact of riskbased on its priority, probability, and consequence or other definedrisk threshold
- ACQ.4.O.2 All information, agreed upon for exchange, is communicated regularlybetween the supplier and customer
- HWE.1.O.2 Hardware requirements are categorized and analysed
- SWE.2.O.5 Consistency and bidirectional traceability are established betweensoftware requirements and software architectural design
- SWE.2.O.6 The software architectural design is agreed and communicated to allaffected parties
- SWE.5.O.8 Results of the software integration test are summarized and communicated to all affected parties
- SUP.9.O.4 Problem resolution is initiated
- SWE.6.O.1 A software qualification test strategy including regression test strategy consistent with the project plan and release plan is developed to test the integrated software
- ACQ.4.O.3 Performance of the supplier is monitored against the agreements
- REU.2.O.3 The domains in which to investigate reuse opportunities, or in which itis intended to practice reuse, are identified
- SPL.1.O.5 A supplier proposal is prepared in response to the customer request;and
- MAN.6.O.5 The required data is collected, stored, analyzed, and the resultsinterpreted
- SUP.2.O.1 A verification strategy is developed, implemented and maintained
- ACQ.11.O.4 A mechanism is established to incorporate changed or newrequirements into the established baseline
- SYS.1.O.2 Agreed stakeholder requirements are defined and baselined
- SUP.4.O.1 Management and technical reviews are held based on the needs ofthe project
- SUP.10.O.7 Approved changes are implemented and tracked to closure
- SUP.7.O.3 Documentation to be produced by the process or project is identified
- SPL.1.O.6 Formal confirmation of agreement is obtained
- ACQ.14.O.5 The project terms of reference for CFP / ITT are defined
- SUP.4.O.5 Problems are identified and recorded
- SYS.3.O.4 The dynamic behavior of the system elements is defined
- SWE.6.O.2 A specification for software qualification test of the integrated software according to the software qualification test strategy is developed that is suitable to provide evidence for compliance with the software requirements
- SUP.8.O.7 Storage of the configuration items is controlled
- SWE.3.O.3 The dynamic behavior of the software units is defined
- ACQ.14.O.2 The baseline technical and non-technical requirements are assembled to accompany the CFP / ITT
- SWE.2.O.1 A software architectural design is defined that identifies the elementsof the software
- SYS.3.O.6 The system architectural design is agreed and communicated to allaffected parties
- SUP.1.O.3 Non-conformances of work products, processes, and process activities with relevant requirements are identified, recorded, communicated to the relevant parties, tracked, resolved, and further prevented
- ACQ.12.O.3 Acceptance criteria and mechanisms for handling of breaches to thefulfillment of contract are established
- SUP.1.O.1 A strategy for performing quality assurance is developed, implemented, and maintained
- PIM.3.O.2 Issues arising from the organization's internal/external environmentare identified as improvement opportunities and justified as reasonsfor change
- SPL.1.O.2 Requests for proposal are evaluated according to defined criteria todetermine whether or not to submit a proposal
- SUP.10.O.5 Requests for change are analyzed, and resource requirements are estimated
- SPL.1.O.1 A communication interface is established and maintained in order torespond to customer inquiries and requests for proposal
- SYS.1.O.5 A mechanism is established for ensuring that customers can easilydetermine the status and disposition of their requests
- ACQ.3.O.3 Mechanisms for monitoring the capability and performance of thesupplier(s) and for mitigation of identified risks are reviewed andconsidered for inclusion in the contract conditions
- SUP.7.O.4 The content and purpose of all documentation is specified, reviewed and approved
- SWE.5.O.7 Consistency and bidirectional traceability are established between the elements of the software architectural design and the test cases included in the software integration test specification and between test cases and test results
- ACQ.3.O.2 The contract/agreement clearly and unambiguously specifies theexpectations, responsibilities, work products/deliverables and liabilitiesof both the supplier(s) and the acquirer
- SUP.10.O.2 Requests for changes are recorded and identified
- SWE.5.O.2 A software integration test strategy including the regression test strategy is developed to test the software unit and software item interactions
- ACQ.12.O.5 Warranties and service level agreements are provided for whereapplicable
- SWE.3.O.1 A detailed design is developed that describes software units
- SWE.1.O.3 The impact of software requirements on the operating environment is analyzed
- SPL.2.O.6 The product release is made available to the intended customer
- HWE.1.O.3 The impact of hardware requirements on the operating environment is analysed
- SWE.1.O.6 Consistency and bidirectional traceability are established between system requirements and software requirements; and consistency and bidirectional traceability are established between system architectural design and software requirements
- SYS.3.O.2 The system requirements are allocated to the elements of the system
- SYS.4.O.2 A system integration test strategy including the regression teststrategy is developed to test the system item interactions
- MAN.6.O.1 Organizational commitment is established and sustained to implementthe measurement process
- SUP.8.O.6 The completeness and consistency of the baselines is ensured
- SYS.4.O.7 Consistency and bidirectional traceability between the elements of the system architectural design and test cases included in the system integration test specification and bidirectional traceability between testcases and test results is established
- SUP.10.O.1 A change request management strategy is developed
- ACQ.12.O.2 An agreement, (contractual) terms and conditions are defined todescribe how the supplier will meet the needs and expectations
- SPL.2.O.3 The release documentation is defined and produced
- SWE.3.O.4 Consistency and bidirectional traceability are established between software requirements and software units; and consistency and bidirectional traceability are established between software architectural design and software detailed design; and consistency and bidirectional traceability are established between software detailed design and software units
- ACQ.3.O.4 Proposers/tenderers are notified of the result of proposal/tenderselection
- ACQ.13.O.9 Support and maintenance requirements are established
- SUP.10.O.6 Changes are approved and prioritized on the basis of analysis resultsand availability of resources
- SUP.1.O.4 Conformance of work products, processes and activities with relevant requirements is verified, documented, and communicated to the relevant parties
- SPL.2.O.5 Release approval is effected against defined criteria
- ACQ.13.O.1 Consistency between financial, technical, contractual and projectrequirements is established
- SWE.1.O.4 Prioritization for implementing the software requirements is defined
- HWE.1.O.1 The hardware requirements to be allocated to the hardware elements ofthe system and their interfaces are defined
- MAN.3.O.1 The scope of the work for the project is defined
- SWE.2.O.3 The interfaces of each software element are defined
- ACQ.12.O.1 A contractual approach is defined which is compliant with relevantnational, international and regulatory laws, guidance and policies
- ACQ.4.O.1 Joint activities, as agreed between the customer and the supplier, areperformed as needed
- REU.2.O.1 The reuse strategy, including its purpose, scope, goals and objectives, is defined
- HWE.1.O.7 The hardware requirements are evaluated for cost, schedule andtechnical impact
- SYS.5.O.3 Test cases included in the system qualification test specification are selected according to the system qualification test strategy and the release plan
- MAN.6.O.4 Measurement activities are identified and performed
- SYS.5.O.6 results of the system qualification test are summarized and communicated to all affected parties
- SWE.3.O.2 Interfaces of each software unit are defined
- SYS.4.O.5 Test cases included in the system integration test specification are selected according to the system integration test strategy and the release plan
- SUP.1.O.5 Authority to escalate non-conformances to appropriate levels of management is established
- PIM.3.O.7 The improvements made are evaluated and consideration given forusing the solution elsewhere within the organization
- ACQ.12.O.6 Provision for the suppliers to deliver other requirements (e.g. qualityplan, escrow arrangements etc.) is defined
- MAN.5.O.5 Risk measures are defined, applied, and assessed to determinechanges in the status of risk and the progress of the treatment activities
- SUP.2.O.5 Results of the verification activities are made available to the customer and other involved parties
- SUP.8.O.3 Modifications and releases of the configuration items are controlled
- PIM.3.O.1 Commitment is established to provide resources to sustainimprovement actions
- SWE.1.O.7 The software requirements are evaluated for cost, schedule andtechnical impact
- SUP.1.O.2 Quality assurance is performed independently and objectively without conflicts of interest
- MAN.3.O.7 Corrective action is taken when project goals are not achieved, andrecurrence of problems identified in the project is prevented.
- SWE.3.O.5 The software detailed design and the relationship to the software architectural design is agreed and communicated to all affected parties
- SWE.4.O.2 Criteria for software unit verification are developed according to the software unit verification strategy that are suitable to provide evidence for compliance of the software units with the software detailed design and with the non-functional software requirements
- SYS.2.O.2 System requirements are categorized and analyzed for correctnessand verifiability
- MAN.6.O.2 The measurement information needs of organizational andmanagement processes are identified
- SUP.4.O.4 Action items resulting from reviews are tracked to closure
- SUP.10.O.3 Dependencies and relationships to other change requests are identified
- ACQ.13.O.4 The needs for exchanging information between all affected parties areestablished
- SYS.4.O.8 Results of the system integration test are summarized andcommunicated to all affected parties
- SUP.7.O.6 Documentation is maintained in accordance with defined criteria
- SYS.1.O.1 Continuing communication with the stakeholder is established
- REU.2.O.5 Reuse proposals are evaluated to ensure the reuse product is suitablefor the proposed application
- REU.2.O.6 Reuse is implemented according to the reuse strategy
- PIM.3.O.3 Analysis of the current status of the existing process is performed,focusing on those processes from which improvement stimuli arise
- SUP.7.O.1 A strategy identifying the documentation to be produced during the lifecycle of the product or service is developed
- HWE.1.O.4 Prioritization of hardware requirements is defined
- MAN.6.O.7 The measurement process and measures are evaluated andcommunicated to the process owner
- SUP.7.O.5 Documentation is developed and made available in accordance with identified standards
- SWE.5.O.5 Test cases included in the software integration test specification are selected according to the software integration test strategy, and the release plan
- MAN.6.O.6 Information products are used to support decisions and provide anobjective basis for communication
- HWE.1.O.5 The hardware requirements are updated as needed
- SWE.4.O.5 Results of the unit verification are summarized and communicated toall affected parties
- MAN.5.O.1 The scope of the risk management to be performed is determined
- SWE.1.O.5 The software requirements are updated as needed
- ACQ.15.O.3 The suppliers which possess required qualification are short-listed fortender solution(s) evaluation
- SYS.5.O.5 Consistency and bidirectional traceability are established between system requirements and test cases included in the system qualification test specification and between test cases and test results
- ACQ.12.O.7 Recognized criteria for proprietary, regulatory and other productliabilities issues are established
- SWE.5.O.4 Software units and software items are integrated up to a complete integrated software according to the integration strategy
- SUP.4.O.3 Review results are made known to all affected parties
- MAN.3.O.5 Plans for the execution of the project are developed, implemented andmaintained
- SYS.2.O.4 Prioritization for implementing the system requirements is defined
- ACQ.14.O.4 RThe financial terms of reference for costs and payments for CFP / ITT are defined
- SPL.2.O.2 The release is assembled from configured items
- SUP.10.O.8 The status of all change requests is known
- SWE.6.O.5 Consistency and bidirectional traceability are established between software requirements and software qualification test specification including test cases and between test cases and test results
- SPL.2.O.4 The release delivery mechanism and media are determined
- SYS.4.O.3 A specification for system integration test according to the system integration test strategy is developed that is suitable to provide evidence for compliance of the integrated system items with the system architectural design, including the interfaces between system items
- SWE.4.O.1 A software unit verification strategy including regression strategy is developed to verify the software units
- REU.2.O.2 Each domain is assessed to determine its reuse potential
- ACQ.15.O.5 Any corrective action required by the acquirer is evaluated andperformed
- ACQ.15.O.2 Supplier capability determination is performed as necessary
- SWE.6.O.6 Results of the software qualification test are summarized and communicated to all affected parties
- ACQ.13.O.6 Potential risks are identified
- SYS.5.O.4 The integrated system is tested using the selected test cases and the results of system qualification test are recorded
- REU.2.O.8 The reuse program is monitored and evaluated
- SUP.2.O.3 Required verification activities are performed
- SWE.5.O.3 A specification for software integration test according to the software integration test strategy is developed that is suitable to provide evidence for compliance of the integrated software items with the software architectural design, including the interfaces between the software units and between the software items
- SWE.1.O.1 The software requirements to be allocated to the software elements ofthe system and their interfaces are defined
- ACQ.11.O.5 A mechanism for identifying and managing the impact of changingtechnology to the technical requirements is defined
- ACQ.14.O.3 The agreement (contractual) terms of reference and conditions for CFP / ITT are established
- SPL.2.O.1 The contents of the product release are determined
- SPL.1.O.3 The need to undertake preliminary surveys or feasibility studies isdetermined
- ACQ.13.O.3 Requirements for adequate staffing of projects by a competent team(e.g. resources with requisite legal, contractual, technical and projectcompetence) with clear responsibilities and goals are defined
- ACQ.14.O.6 The technical terms of reference for CFP / ITT are defined
- PIM.3.O.4 Improvement goals are identified and prioritized, and consequentchanges to the process are defined, planned and implemented
- SUP.2.O.4 Defects are identified, recorded and tracked
- SWE.6.O.4 The integrated software is tested using the selected test cases and the results of software qualification test are recorded
- SWE.1.O.2 Software requirements are categorized and analyzed for correctness and verifiability
- SYS.2.O.3 The impact of system requirements on the operating environment isanalyzed
- SUP.4.O.2 The status and products of an activity of a process are evaluated through joint review activities between the stakeholders
- SYS.1.O.4 A mechanism is established for continuous monitoring of stakeholderneeds
- SWE.5.O.1 A software integration strategy consistent with the project plan, release plan and the software architectural design is developed to integrate the software items
- SUP.9.O.1 A problem resolution management strategy is developed
- SYS.1.O.6 Changes arising from changing technology and stakeholder needs areidentified, the associated risks assessed and their impact managed
- ACQ.15.O.1 Criteria are established for qualifying suppliers
- MAN.5.O.3 Risks are identified as they develop during the conduct of the project
- SYS.4.O.6 System item interactions are tested using the selected test cases andthe results of system integration testing are recorded
- REU.2.O.4 The organization's systematic reuse capability is assessed
- SWE.2.O.4 The dynamic behavior and resource consumption objectives of thesoftware elements are defined
- SYS.5.O.2 A specification for system qualification test of the integrated system according to the system qualification test strategy is developed that issuitable to provide evidence for compliance with the system requirements
- SUP.8.O.1 A configuration management strategy is developed
- MAN.5.O.4 Risks are analyzed and the priority in which to apply resources totreatment of these risks is determined
- SUP.8.O.5 The status of the configuration items and modifications is recorded and reported
- SUP.10.O.9 Bi-directional traceability is established between change requests and affected work product
-
-
-
-
(SUP.7 Documentation - 13-01 Acceptance record)
-
(MAN.5 Risk Management - 13-20 Risk action request)
-
(ACQ.14 Request for Proposals - 17-00 Requirement specification)
-
(PIM.3 Process Improvement - 10-00 Process description)
-
(MAN.6 Measurement - 15-18 Process performance report)
-
(SUP.9 Problem Resolution Management - 08-27 Problem management plan)
-
(SWE.3 Software Detailed Design and Unit Construction - 13-04 Communication Record)
-
(ACQ.14 Request for Proposals - 02-01 Commitment/agreement)
-
(SUP.7 Documentation - 14-01 Change history)
-
(SWE.1 Software Requirements Analysis - 13-21 Change control record)
-
(SWE.2 Software Architectural Design - 13-04 Communication Record)
-
(SWE.1 Software Requirements Analysis - 13-19 Review Record)
-
(SUP.7 Documentation - 08-26 Documentation plan)
-
(SWE.6 Software Qualification Test - 13-19 Review Record)
-
(MAN.6 Measurement - 07-07 Risk measure)
-
(ACQ.14 Request for Proposals - 12-01 Request for proposal)
-
(SPL.2 Product Release - 13-06 Delivery record)
-
(SUP.4 Joint Review - 13-04 Communication Record)
-
(PIM.3 Process Improvement - 07-04 Process measure)
-
(SUP.10 Change Request Management - 13-19 Review Record)
-
(SWE.4 Software Unit Verification - 08-50 Test specification)
-
(SPL.2 Product Release - 11-04 Product release package)
-
(SUP.4 Joint Review - 13-07 Problem record )
-
(SPL.2 Product Release - 13-13 Product release approval record)
-
(SUP.1 Quality Assurance - 14-02 Corrective Action Register)
-
(SUP.8 Configuration Management - 14-01 Change history)
-
(SUP.2 Verification - 19-10 Verification strategy)
-
(ACQ.11 Technical Requirements - 08-28 Change management plan )
-
(SPL.1 Supplier Tendering - 13-04 Communication Record)
-
(SWE.6 Software Qualification Test - 08-52 Test plan)
-
(MAN.5 Risk Management - 08-20 Risk mitigation plan)
-
(ACQ.11 Technical Requirements - 14-01 Change history)
-
(SWE.1 Software Requirements Analysis - 11-04 Product release package)
-
(MAN.6 Measurement - 15-05 Evaluation report)
-
(SYS.1 Requirements Elicitation - 13-21 Change control record)
-
(SUP.7 Documentation - 13-19 Review Record)
-
(ACQ.13 Project Requirements - 02-00 Contract)
-
(HWE.1 Hardware Requirements Analysis - 13-19 Review Record)
-
(SWE.2 Software Architectural Design - 04-04 Software architectural design)
-
(MAN.5 Risk Management - 07-07 Risk measure)
-
(ACQ.12 Legal and Administrative Requirements - 10-00 Process description)
-
(SPL.2 Product Release - 11-03 Product release information)
-
(SUP.10 Change Request Management - 08-28 Change management plan )
-
(SUP.9 Problem Resolution Management - 15-01 Analysis report)
-
(SUP.1 Quality Assurance - 13-18 Quality record)
-
(ACQ.3 Contract Agreement - 02-01 Commitment/agreement)
-
(SPL.1 Supplier Tendering - 02-01 Commitment/agreement)
-
(ACQ.4 Supplier Monitoring - 02-01 Commitment/agreement)
-
(HWE.1 Hardware Requirements Analysis - 15-01 Analysis report)
-
(ACQ.11 Technical Requirements - 13-17 Customer request)
-
(SPL.2 Product Release - 11-07 Temporary solution)
-
(SYS.2 System Requirements Analysis - 13-19 Review Record)
-
(MAN.6 Measurement - 15-01 Analysis report)
-
(REU.2 Reuse Program Management - 15-13 Assessment/audit report)
-
(SYS.5 System Qualification Test - 13-22 Traceability record )
-
(ACQ.4 Supplier Monitoring - 13-14 Progress status record)
-
(SYS.4 System Integration and Integration Test - 08-52 Test plan)
-
(SPL.2 Product Release - 18-06 Product release criteria)
-
(REU.2 Reuse Program Management - 12-03 Reuse proposal)
-
(PIM.3 Process Improvement - 15-13 Assessment/audit report)
-
(SUP.1 Quality Assurance - 13-04 Communication Record)
-
(ACQ.3 Contract Agreement - 13-09 Meeting support record)
-
(SWE.5 Software Integration and Integration Test - 17-02 Build list)
-
(SUP.1 Quality Assurance - 18-07 Quality criteria)
-
(SWE.6 Software Qualification Test - 13-50 Test result)
-
(SYS.3 System Architectural Design - 13-04 Communication Record)
-
(PIM.3 Process Improvement - 08-29 Improvement plan)
-
(PIM.3 Process Improvement - 02-01 Commitment/agreement)
-
(SYS.4 System Integration and Integration Test - 13-22 Traceability record )
-
(SWE.3 Software Detailed Design and Unit Construction - 13-19 Review Record)
-
(MAN.6 Measurement - 07-05 Project measure)
-
(SUP.8 Configuration Management - 13-08 Baseline)
-
(PIM.3 Process Improvement - 15-16 Improvement opportunity)
-
(HWE.1 Hardware Requirements Analysis - 13-21 Change control record)
-
(SYS.2 System Requirements Analysis - 17-50 Verification criteria)
-
(PIM.3 Process Improvement - 05-00 Goals)
-
(SWE.3 Software Detailed Design and Unit Construction - 13-22 Traceability record )
-
(REU.2 Reuse Program Management - 15-07 Reuse evaluation report)
-
(REU.2 Reuse Program Management - 08-17 Reuse plan)
-
(ACQ.11 Technical Requirements - 13-21 Change control record)
-
(SWE.3 Software Detailed Design and Unit Construction - 04-05 Software detailed design)
-
(SUP.4 Joint Review - 13-09 Meeting support record)
-
(SWE.1 Software Requirements Analysis - 17-50 Verification criteria)
-
(SPL.1 Supplier Tendering - 13-15 Proposal review record)
-
(ACQ.4 Supplier Monitoring - 13-16 Change Request)
-
(MAN.5 Risk Management - 08-19 Risk management plan)
-
(ACQ.12 Legal and Administrative Requirements - 18-01 Acceptance criteria)
-
(SYS.3 System Architectural Design - 17-08 Interface requirements specification)
-
(ACQ.3 Contract Agreement - 02-00 Contract)
-
(SYS.5 System Qualification Test - 13-50 Test result)
-
(ACQ.13 Project Requirements - 13-19 Review Record)
-
(ACQ.11 Technical Requirements - 13-24 Validation results)
-
(SWE.2 Software Architectural Design - 13-19 Review Record)
-
(ACQ.14 Request for Proposals - 19-11 Validation strategy)
-
(HWE.1 Hardware Requirements Analysis - 17-08 Interface requirements specification)
-
(SWE.4 Software Unit Verification - 08-52 Test plan)
-
(SWE.6 Software Qualification Test - 13-04 Communication Record)
-
(MAN.6 Measurement - 07-08 Service level measure)
-
(REU.2 Reuse Program Management - 13-04 Communication Record)
-
(SYS.1 Requirements Elicitation - 08-19 Risk management plan)
-
(ACQ.12 Legal and Administrative Requirements - 02-00 Contract)
-
(SWE.6 Software Qualification Test - 13-22 Traceability record )
-
(MAN.3 Project Management - 14-02 Corrective Action Register)
-
(SYS.2 System Requirements Analysis - 13-04 Communication Record)
-
(SYS.2 System Requirements Analysis - 17-08 Interface requirements specification)
-
(SWE.5 Software Integration and Integration Test - 13-19 Review Record)
-
(PIM.3 Process Improvement - 08-00 Plan)
-
(ACQ.12 Legal and Administrative Requirements - 17-00 Requirement specification)
-
(ACQ.12 Legal and Administrative Requirements - 02-01 Commitment/agreement)
-
(REU.2 Reuse Program Management - 04-02 Domain architecture)
-
(SUP.4 Joint Review - 14-02 Corrective Action Register)
-
(SUP.2 Verification - 13-04 Communication Record)
-
(SYS.1 Requirements Elicitation - 13-19 Review Record)
-
(SUP.9 Problem Resolution Management - 13-07 Problem record )
-
(SUP.8 Configuration Management - 06-02 Handling and storage guide)
-
(SWE.2 Software Architectural Design - 17-08 Interface requirements specification)
-
(SYS.5 System Qualification Test - 08-50 Test specification)
-
(SYS.1 Requirements Elicitation - 17-03 Customer requirements)
-
(MAN.5 Risk Management - 14-02 Corrective Action Register)
-
(SYS.4 System Integration and Integration Test - 13-50 Test result)
-
(SWE.3 Software Detailed Design and Unit Construction - 11-05 Software unit)
-
(ACQ.12 Legal and Administrative Requirements - 14-02 Corrective Action Register)
-
(SWE.5 Software Integration and Integration Test - 01-50 Integrated software)
-
(SUP.9 Problem Resolution Management - 15-05 Evaluation report)
-
(SWE.5 Software Integration and Integration Test - 13-04 Communication Record)
-
(ACQ.15 Supplier Qualification - 18-50 Supplier qualification criteria)
-
(SWE.4 Software Unit Verification - 13-19 Review Record)
-
(ACQ.3 Contract Agreement - 13-04 Communication Record)
-
(MAN.3 Project Management - 08-12 Project Plan)
-
(SUP.8 Configuration Management - 13-10 Configuration management record)
-
(SPL.1 Supplier Tendering - 13-19 Review Record)
-
(SUP.2 Verification - 13-25 Verification results)
-
(SUP.1 Quality Assurance - 13-19 Review Record)
-
(SUP.4 Joint Review - 13-05 Contract review record)
-
(MAN.6 Measurement - 02-01 Commitment/agreement)
-
(MAN.6 Measurement - 03-06 Process performance data)
-
(SYS.3 System Architectural Design - 13-19 Review Record)
-
(SWE.1 Software Requirements Analysis - 13-22 Traceability record )
-
(MAN.6 Measurement - 07-04 Process measure)
-
(SPL.1 Supplier Tendering - 08-12 Project Plan)
-
(MAN.5 Risk Management - 15-09 Risk status report)
-
(PIM.3 Process Improvement - 16-06 Process repository)
-
(MAN.6 Measurement - 07-03 Personnel performance measure)
-
(REU.2 Reuse Program Management - 19-05 Reuse strategy)
-
(SPL.2 Product Release - 08-16 Release plan)
-
(SUP.2 Verification - 14-02 Corrective Action Register)
-
(MAN.3 Project Management - 15-06 Project Status Report)
-
(ACQ.3 Contract Agreement - 13-05 Contract review record)
-
(MAN.6 Measurement - 03-04 Customer satisfaction data)
-
(SWE.1 Software Requirements Analysis - 17-08 Interface requirements specification)
-
(MAN.3 Project Management - 14-09 Work Breakdown Structure)
-
(MAN.3 Project Management - 13-16 Change Request)
-
(ACQ.11 Technical Requirements - 14-02 Corrective Action Register)
-
(SUP.10 Change Request Management - 13-21 Change control record)
-
(ACQ.11 Technical Requirements - 14-50 Stakeholder Groups List)
-
(SUP.8 Configuration Management - 08-04 Configuration management plan)
-
(REU.2 Reuse Program Management - 09-03 Reuse policy)
-
(SUP.9 Problem Resolution Management - 15-12 Problem status report)
-
(SUP.1 Quality Assurance - 13-07 Problem record )
-
(REU.2 Reuse Program Management - 04-03 Domain model)
-
(MAN.3 Project Management - 13-04 Communication Record)
-
(SYS.2 System Requirements Analysis - 17-12 System requirements specification)
-
(ACQ.15 Supplier Qualification - 15-16 Improvement opportunity)
-
(SUP.1 Quality Assurance - 08-13 Quality plan)
-
(SWE.1 Software Requirements Analysis - 17-11 Software requirements specification)
-
(SUP.2 Verification - 13-07 Problem record )
-
(SYS.1 Requirements Elicitation - 08-20 Risk mitigation plan)
-
(SWE.1 Software Requirements Analysis - 15-01 Analysis report)
-
(PIM.3 Process Improvement - 15-05 Evaluation report)
-
(SUP.4 Joint Review - 15-01 Analysis report)
-
(SPL.1 Supplier Tendering - 12-04 Supplier proposal response)
-
(ACQ.11 Technical Requirements - 13-04 Communication Record)
-
(SYS.3 System Architectural Design - 13-22 Traceability record )
-
(MAN.3 Project Management - 13-19 Review Record)
-
(SWE.2 Software Architectural Design - 13-22 Traceability record )
-
(SUP.4 Joint Review - 15-16 Improvement opportunity)
-
(MAN.5 Risk Management - 14-08 Tracking system)
-
(SYS.4 System Integration and Integration Test - 13-19 Review Record)
-
(SUP.7 Documentation - 14-11 Work product list)
-
(MAN.6 Measurement - 07-02 Field measure)
-
(ACQ.15 Supplier Qualification - 14-02 Corrective Action Register)
-
(MAN.6 Measurement - 07-06 Quality measure)
-
(PIM.3 Process Improvement - 13-16 Change Request)
-
(SYS.2 System Requirements Analysis - 13-22 Traceability record )
-
(ACQ.11 Technical Requirements - 17-03 Customer requirements)
-
(SWE.5 Software Integration and Integration Test - 08-52 Test plan)
-
(SUP.8 Configuration Management - 08-14 Recovery plan)
-
(SWE.4 Software Unit Verification - 13-04 Communication Record)
-
(SYS.4 System Integration and Integration Test - 11-06 System)
-
(MAN.5 Risk Management - 08-14 Recovery plan)
-
(SUP.8 Configuration Management - 16-03 Configuration management system)
-
(SUP.4 Joint Review - 15-13 Assessment/audit report)
-
(ACQ.15 Supplier Qualification - 14-05 Preferred suppliers register)
-
(SYS.3 System Architectural Design - 04-06 System architectural design)
-
(HWE.1 Hardware Requirements Analysis - 17-HW01 Hardware requirements specification)
-
(MAN.5 Risk Management - 15-08 Risk analysis report)
-
(SYS.2 System Requirements Analysis - 13-21 Change control record)
-
(ACQ.4 Supplier Monitoring - 13-01 Acceptance record)
-
(SYS.5 System Qualification Test - 13-04 Communication Record)
-
(ACQ.4 Supplier Monitoring - 14-02 Corrective Action Register)
-
(MAN.6 Measurement - 07-01 Customer satisfaction survey)
-
(SYS.5 System Qualification Test - 08-52 Test plan)
-
(SUP.4 Joint Review - 14-08 Tracking system)
-
(ACQ.13 Project Requirements - 13-20 Risk action request)
-
(SYS.1 Requirements Elicitation - 13-04 Communication Record)
-
(SWE.4 Software Unit Verification - 15-01 Analysis report)
-
(ACQ.11 Technical Requirements - 17-00 Requirement specification)
-
(SWE.4 Software Unit Verification - 13-25 Verification results)
-
(MAN.3 Project Management - 14-06 Schedule)
-
(SPL.2 Product Release - 15-03 Configuration status report )
-
(SYS.2 System Requirements Analysis - 15-01 Analysis report)
-
(MAN.6 Measurement - 03-03 Benchmarking data)
-
(SYS.4 System Integration and Integration Test - 08-50 Test specification)
-
(ACQ.4 Supplier Monitoring - 13-09 Meeting support record)
-
(SYS.5 System Qualification Test - 13-19 Review Record)
-
(SUP.2 Verification - 18-07 Quality criteria)
-
(SWE.6 Software Qualification Test - 08-50 Test specification)
-
(HWE.1 Hardware Requirements Analysis - 13-04 Communication Record)
-
(HWE.1 Hardware Requirements Analysis - 13-22 Traceability record )
-
(SWE.5 Software Integration and Integration Test - 13-22 Traceability record )
-
(MAN.3 Project Management - 14-50 Stakeholder Groups List)
-
(ACQ.4 Supplier Monitoring - 13-19 Review Record)
-
(SUP.10 Change Request Management - 13-16 Change Request)
-
(SWE.5 Software Integration and Integration Test - 08-50 Test specification)
-
(PIM.3 Process Improvement - 06-04 Training material)
-
(ACQ.4 Supplier Monitoring - 13-04 Communication Record)
-
(ACQ.11 Technical Requirements - 08-51 Technology monitoring plan)
-
(ACQ.15 Supplier Qualification - 15-21 Supplier evaluation report)
-
(SWE.5 Software Integration and Integration Test - 13-50 Test result)
-
(ACQ.4 Supplier Monitoring - 15-01 Analysis report)
-
(SYS.4 System Integration and Integration Test - 13-04 Communication Record)
-
(SUP.4 Joint Review - 13-19 Review Record)
-
(SWE.5 Software Integration and Integration Test - 01-03 Software item)
-
(SWE.4 Software Unit Verification - 13-50 Test result)
-
(ACQ.13 Project Requirements - 17-00 Requirement specification)
-
(SYS.1 Requirements Elicitation - 15-01 Analysis report)
-
(SWE.4 Software Unit Verification - 13-22 Traceability record )
-
(PIM.3 Process Improvement - 13-04 Communication Record)
-
(SUP.9 Problem Resolution Management - SUP.9.BP6 Raise alert notifications)
-
(SWE.6 Software Qualification Test - SWE.6.BP4 Test integrated software)
-
(SWE.6 Software Qualification Test - SWE.6.BP3 Select test cases)
-
(SYS.3 System Architectural Design - SYS.3.BP7 Ensure consistency)
-
(ACQ.3 Contract Agreement - ACQ.3.BP3 Review contract/agreement for supplier capability monitoring)
-
(SPL.1 Supplier Tendering - SPL.1.BP7 Prepare supplier proposal response)
-
(SUP.1 Quality Assurance - SUP.1.BP1 Develop a project quality assurance strategy)
-
(SUP.10 Change Request Management - SUP.10.BP8 Establish bidirectional traceability)
-
(SUP.7 Documentation - SUP.7.BP7 Distribute documentation)
-
(SUP.10 Change Request Management - SUP.10.BP3 Record the status of change requests)
-
(SUP.8 Configuration Management - SUP.8.BP3 Establish a configuration management system)
-
(SYS.4 System Integration and Integration Test - SYS.4.BP6 Perform system integration test)
-
(SWE.1 Software Requirements Analysis - SWE.1.BP8 Communicate agreed software requirements)
-
(SWE.3 Software Detailed Design and Unit Construction - SWE.3.BP4 Evaluate software detailed design)
-
(SWE.6 Software Qualification Test - SWE.6.BP2 Develop specification for software qualification test)
-
(SPL.1 Supplier Tendering - SPL.1.BP8 Establish confirmation of agreement)
-
(SPL.2 Product Release - SPL.2.BP3 Establish a product release classification and numbering scheme)
-
(PIM.3 Process Improvement - PIM.3.BP4 Prioritize improvements)
-
(SWE.5 Software Integration and Integration Test - SWE.5.BP6 Perform software integration test)
-
(SWE.5 Software Integration and Integration Test - SWE.5.BP2 Develop software integration test strategy includingregression test strategy)
-
(HWE.1 Hardware Requirements Analysis - HWE.1.BP5 Establish bidirectional traceability)
-
(SPL.2 Product Release - SPL.2.BP13 Deliver the release to the intended customer)
-
(SUP.10 Change Request Management - SUP.10.BP5 Approve change requests before implementation)
-
(SUP.9 Problem Resolution Management - SUP.9.BP1 Develop a problem resolution management strategy)
-
(PIM.3 Process Improvement - PIM.3.BP9 Evaluate the results of the improvement project)
-
(MAN.3 Project Management - MAN.3.BP8 Define, monitor and adjust project schedule)
-
(MAN.6 Measurement - MAN.6.BP11 Communicate potential improvements)
-
(SUP.10 Change Request Management - SUP.10.BP2 Identify and record the change requests)
-
(MAN.6 Measurement - MAN.6.BP1 Establish organizational commitment for measurement)
-
(SWE.1 Software Requirements Analysis - SWE.1.BP6 Establish bidirectional traceability)
-
(SYS.4 System Integration and Integration Test - SYS.4.BP2 Develop system integration test strategy including regression test strategy)
-
(ACQ.14 Request for Proposals - ACQ.14.BP4 Define financial terms)
-
(SWE.5 Software Integration and Integration Test - SWE.5.BP4 Integrate software units and software items)
-
(SPL.2 Product Release - SPL.2.BP1 Define the functional content of releases)
-
(ACQ.13 Project Requirements - ACQ.13.BP7 Identify information needs)
-
(SYS.2 System Requirements Analysis - SYS.2.BP1 Specify system requirements)
-
(ACQ.13 Project Requirements - ACQ.13.BP13 Define ownership of relationships)
-
(MAN.3 Project Management - MAN.3.BP5 Define, monitor and adjust project estimates andresources)
-
(ACQ.11 Technical Requirements - ACQ.11.BP8 Track impact of changing technology)
-
(SUP.1 Quality Assurance - SUP.1.BP3 Assure quality of process activities)
-
(SUP.2 Verification - SUP.2.BP2 Develop criteria for verification)
-
(ACQ.12 Legal and Administrative Requirements - ACQ.12.BP5 Establish acceptance criteria)
-
(ACQ.3 Contract Agreement - ACQ.3.BP7 Communicate result to tenderers)
-
(MAN.5 Risk Management - MAN.5.BP5 Define risk treatment actions)
-
(SYS.1 Requirements Elicitation - SYS.1.BP2 Understand stakeholder expectations)
-
(REU.2 Reuse Program Management - REU.2.BP5 Evaluate reuse proposals)
-
(SUP.7 Documentation - SUP.7.BP4 Identify the relevant documentation to be produced)
-
(ACQ.11 Technical Requirements - ACQ.11.BP4 Ensure consistency)
-
(SWE.4 Software Unit Verification - SWE.4.BP4 Test software units)
-
(ACQ.13 Project Requirements - ACQ.13.BP14 Define rights for use and distribution)
-
(SUP.7 Documentation - SUP.7.BP2 Establish standards for documentation)
-
(ACQ.3 Contract Agreement - ACQ.3.BP2 Specify rights and duties)
-
(ACQ.14 Request for Proposals - ACQ.14.BP6 Define technical terms)
-
(ACQ.15 Supplier Qualification - ACQ.15.BP3 Short-list suppliers with required qualification)
-
(ACQ.15 Supplier Qualification - ACQ.15.BP4 Evaluate any shortfalls)
-
(SYS.4 System Integration and Integration Test - SYS.4.BP3 Develop specification for system integration test)
-
(SWE.3 Software Detailed Design and Unit Construction - SWE.3.BP6 Ensure consistency)
-
(SUP.7 Documentation - SUP.7.BP8 Maintain documentation)
-
(SUP.8 Configuration Management - SUP.8.BP6 Establish baselines)
-
(PIM.3 Process Improvement - PIM.3.BP8 Communicate results of improvement)
-
(MAN.6 Measurement - MAN.6.BP7 Analyze measures)
-
(SUP.2 Verification - SUP.2.BP3 Conduct verification)
-
(MAN.3 Project Management - MAN.3.BP4 Define, monitor and adjust project activities)
-
(SWE.3 Software Detailed Design and Unit Construction - SWE.3.BP1 Develop software detailed design)
-
(ACQ.11 Technical Requirements - ACQ.11.BP2 Define technical requirements)
-
(ACQ.4 Supplier Monitoring - ACQ.4.BP3 Review technical development with the supplier)
-
(ACQ.3 Contract Agreement - ACQ.3.BP1 Negotiate the contract/agreement)
-
(MAN.5 Risk Management - MAN.5.BP2 Define risk management strategies)
-
(SUP.1 Quality Assurance - SUP.1.BP4 Summarize and communicate quality assurance activitiesand results)
-
(SPL.1 Supplier Tendering - SPL.1.BP3 Establish customer proposal evaluation criteria)
-
(SUP.8 Configuration Management - SUP.8.BP7 Report configuration status)
-
(MAN.3 Project Management - MAN.3.BP9 Ensure consistency)
-
(SWE.6 Software Qualification Test - SWE.6.BP1 Develop software qualification test strategy including regression test strategy)
-
(ACQ.13 Project Requirements - ACQ.13.BP4 Define management requirements)
-
(ACQ.12 Legal and Administrative Requirements - ACQ.12.BP2 Consider relevant regulations)
-
(MAN.3 Project Management - MAN.3.BP1 Define the scope of work)
-
(REU.2 Reuse Program Management - REU.2.BP8 Monitor reuse)
-
(ACQ.11 Technical Requirements - ACQ.11.BP7 Establish a change mechanism)
-
(MAN.3 Project Management - MAN.3.BP10 Review and report progress of the project)
-
(SWE.2 Software Architectural Design - SWE.2.BP5 Define resource consumption objectives)
-
(SUP.8 Configuration Management - SUP.8.BP5 Control modifications and releases)
-
(SUP.4 Joint Review - SUP.4.BP5 Distribute the results)
-
(SWE.2 Software Architectural Design - SWE.2.BP7 Establish bidirectional traceability)
-
(ACQ.4 Supplier Monitoring - ACQ.4.BP5: Act to correct deviations)
-
(MAN.5 Risk Management - MAN.5.BP3 Identify risks)
-
(SYS.4 System Integration and Integration Test - SYS.4.BP7 Establish bidirectional traceability)
-
(SYS.3 System Architectural Design - SYS.3.BP3 Define interfaces of system elements)
-
(ACQ.11 Technical Requirements - ACQ.11.BP10 Ensure compliance of stated requirements)
-
(SUP.9 Problem Resolution Management - SUP.9.BP4 Diagnose the cause and determine the impact of the problem)
-
(REU.2 Reuse Program Management - REU.2.BP1 Define organizational reuse strategy)
-
(SUP.4 Joint Review - SUP.4.BP2 Establish a mechanism to handle review outcomes)
-
(SUP.2 Verification - SUP.2.BP5 Report verification results)
-
(SUP.4 Joint Review - SUP.4.BP4 Conduct joint reviews)
-
(SWE.6 Software Qualification Test - SWE.6.BP5 Establish bidirectional traceability)
-
(ACQ.15 Supplier Qualification - ACQ.15.BP2 Evaluate supplier)
-
(PIM.3 Process Improvement - PIM.3.BP2 Identify issues)
-
(ACQ.14 Request for Proposals - ACQ.14.BP3 Establish terms and conditions for CFP / ITT)
-
(SWE.2 Software Architectural Design - SWE.2.BP6 Evaluate alternative software architectures)
-
(ACQ.14 Request for Proposals - ACQ.14.BP8 Prepare and issue a CFP / ITT)
-
(SYS.2 System Requirements Analysis - SYS.2.BP5 Develop verification criteria)
-
(SPL.2 Product Release - SPL.2.BP4 Define the build activities and build environment)
-
(SWE.4 Software Unit Verification - SWE.4.BP1 Develop software unit verification strategy including regression strategy)
-
(SYS.3 System Architectural Design - SYS.3.BP2 Allocate system requirements)
-
(SPL.1 Supplier Tendering - SPL.1.BP4 Evaluate customer request for proposal)
-
(MAN.6 Measurement - MAN.6.BP4 Specify measures)
-
(SWE.4 Software Unit Verification - SWE.4.BP6 Ensure consistency)
-
(SWE.1 Software Requirements Analysis - SWE.1.BP4 Analyze the impact on the operating environment)
-
(SUP.1 Quality Assurance - SUP.1.BP2 Assure quality of work products)
-
(SYS.3 System Architectural Design - SYS.3.BP1 Develop system architectural design)
-
(SWE.5 Software Integration and Integration Test - SWE.5.BP9 Summarize and communicate results)
-
(SUP.9 Problem Resolution Management - SUP.9.BP3 Record the status of problems)
-
(SUP.2 Verification - SUP.2.BP1 Develop a verification strategy)
-
(SYS.5 System Qualification Test - SYS.5.BP7 Summarize and communicate results)
-
(ACQ.14 Request for Proposals - ACQ.14.BP7 Identify relevant regulations)
-
(ACQ.13 Project Requirements - ACQ.13.BP11 Identify risks)
-
(SYS.2 System Requirements Analysis - SYS.2.BP6 Establish bidirectional traceability)
-
(SWE.2 Software Architectural Design - SWE.2.BP1 Develop software architectural design)
-
(SYS.5 System Qualification Test - SYS.5.BP3 Select test cases)
-
(ACQ.13 Project Requirements - ACQ.13.BP6 Define responsibilities and goals)
-
(SYS.3 System Architectural Design - SYS.3.BP8 Communicate agreed system architectural design)
-
(SUP.10 Change Request Management - SUP.10.BP1 Develop a change request management strategy)
-
(ACQ.13 Project Requirements - ACQ.13.BP3 Define organizational requirements)
-
(SPL.2 Product Release - SPL.2.BP9 Define and produce the product release documentation/release notes)
-
(SPL.2 Product Release - SPL.2.BP5 Build the release from configured items)
-
(REU.2 Reuse Program Management - REU.2.BP4 Assess reuse maturity)
-
(ACQ.12 Legal and Administrative Requirements - ACQ.12.BP4 Ensure usage of agreed terms and conditions)
-
(ACQ.11 Technical Requirements - ACQ.11.BP3 Identify acquisition needs)
-
(SUP.1 Quality Assurance - SUP.1.BP5 Ensure resolution of non-conformances)
-
(ACQ.12 Legal and Administrative Requirements - ACQ.12.BP6 Establish escalation mechanisms)
-
(SYS.5 System Qualification Test - SYS.5.BP1 Develop system qualification test strategy including regression test strategy)
-
(SWE.2 Software Architectural Design - SWE.2.BP4 Describe dynamic behavior)
-
(PIM.3 Process Improvement - PIM.3.BP3 Establish process improvement goals)
-
(SWE.3 Software Detailed Design and Unit Construction - SWE.3.BP8 Develop software units)
-
(SWE.2 Software Architectural Design - SWE.2.BP9 Communicate agreed software architectural design)
-
(ACQ.14 Request for Proposals - ACQ.14.BP2 Assemble requirements)
-
(SWE.3 Software Detailed Design and Unit Construction - SWE.3.BP2 Define interfaces of software units)
-
(SUP.10 Change Request Management - SUP.10.BP6 Review the implementation of change requests)
-
(SPL.1 Supplier Tendering - SPL.1.BP5 Determine need for preliminary pre-studies)
-
(ACQ.13 Project Requirements - ACQ.13.BP9 Establish criteria for interim work products)
-
(ACQ.12 Legal and Administrative Requirements - ACQ.12.BP3 Agree on (contractual) terms and conditions)
-
(PIM.3 Process Improvement - PIM.3.BP6 Implement process changes)
-
(ACQ.13 Project Requirements - ACQ.13.BP2 Communicate with relevant groups)
-
(SUP.9 Problem Resolution Management - SUP.9.BP9 Analyze problem trends)
-
(SWE.1 Software Requirements Analysis - SWE.1.BP7 Ensure consistency)
-
(ACQ.13 Project Requirements - ACQ.13.BP1 Identify relevant groups)
-
(ACQ.13 Project Requirements - ACQ.13.BP12 Communicate risks)
-
(REU.2 Reuse Program Management - REU.2.BP6 Implement the reuse program)
-
(ACQ.15 Supplier Qualification - ACQ.15.BP1 Establish qualification criteria)
-
(SYS.5 System Qualification Test - SYS.5.BP2 Develop specification for system qualification test)
-
(SUP.9 Problem Resolution Management - SUP.9.BP8 Track problems to closure)
-
(SYS.4 System Integration and Integration Test - SYS.4.BP5 Select test cases)
-
(ACQ.12 Legal and Administrative Requirements - ACQ.12.BP8 Provide for warranties and service level agreements)
-
(SWE.5 Software Integration and Integration Test - SWE.5.BP7 Establish bidirectional traceability)
-
(ACQ.4 Supplier Monitoring - ACQ.4.BP1 Agree on and maintain joint processes)
-
(REU.2 Reuse Program Management - REU.2.BP2 Identify domains for potential reuse)
-
(SUP.10 Change Request Management - SUP.10.BP7 Track change requests to closure)
-
(SWE.5 Software Integration and Integration Test - SWE.5.BP3 Develop specification for software integration test)
-
(SWE.5 Software Integration and Integration Test - SWE.5.BP5 Select test cases)
-
(SUP.8 Configuration Management - SUP.8.BP4 Establish branch management)
-
(SYS.4 System Integration and Integration Test - SYS.4.BP1 Develop system integration strategy)
-
(SWE.1 Software Requirements Analysis - SWE.1.BP2 Structure software requirements)
-
(ACQ.13 Project Requirements - ACQ.13.BP15 Establish support and maintenance requirements)
-
(SUP.8 Configuration Management - SUP.8.BP9 Manage the storage of configuration items and baselines)
-
(SYS.2 System Requirements Analysis - SYS.2.BP4 Analyze the impact on the operating environment)
-
(PIM.3 Process Improvement - PIM.3.BP5 Plan process changes)
-
(ACQ.12 Legal and Administrative Requirements - ACQ.12.BP10 Establish criteria for liability issues)
-
(SPL.2 Product Release - SPL.2.BP12 Provide a release note)
-
(ACQ.4 Supplier Monitoring - ACQ.4.BP2 Exchange all agreed information)
-
(HWE.1 Hardware Requirements Analysis - HWE.1.BP3 Analyse hardware requirements)
-
(SPL.1 Supplier Tendering - SPL.1.BP2 Perform customer inquiry screening)
-
(SWE.4 Software Unit Verification - SWE.4.BP2 Develop criteria for unit verification)
-
(SWE.3 Software Detailed Design and Unit Construction - SWE.3.BP3 Describe dynamic behavior)
-
(ACQ.4 Supplier Monitoring - ACQ.4.BP4: Review progress of the supplier)
-
(ACQ.13 Project Requirements - ACQ.13.BP5 Identify required competency)
-
(MAN.6 Measurement - MAN.6.BP6 Retrieve measurement data)
-
(SUP.8 Configuration Management - SUP.8.BP2 Identify configuration items)
-
(SYS.2 System Requirements Analysis - SYS.2.BP7 Ensure consistency)
-
(SWE.3 Software Detailed Design and Unit Construction - SWE.3.BP7 Communicate agreed software detailed design)
-
(SYS.4 System Integration and Integration Test - SYS.4.BP8 Ensure consistency)
-
(MAN.5 Risk Management - MAN.5.BP1 Establish risk management scope)
-
(MAN.6 Measurement - MAN.6.BP2 Develop measurement strategy)
-
(SUP.8 Configuration Management - SUP.8.BP1 Develop a configuration management strategy)
-
(SUP.7 Documentation - SUP.7.BP6 Check documentation)
-
(SWE.2 Software Architectural Design - SWE.2.BP8 Ensure consistency)
-
(SUP.10 Change Request Management - SUP.10.BP4 Analyze and assess change requests)
-
(ACQ.11 Technical Requirements - ACQ.11.BP5 Identify affected groups)
-
(MAN.6 Measurement - MAN.6.BP5 Perform measurement activities)
-
(SPL.1 Supplier Tendering - SPL.1.BP6 Identify and nominate staff)
-
(PIM.3 Process Improvement - PIM.3.BP7 Confirm process improvement)
-
(SWE.4 Software Unit Verification - SWE.4.BP7 Summarize and communicate results)
-
(MAN.6 Measurement - MAN.6.BP8 Use measurement information for decision-making)
-
(ACQ.12 Legal and Administrative Requirements - ACQ.12.BP7 Establish management of intellectual property rights)
-
(SYS.5 System Qualification Test - SYS.5.BP5 Establish bidirectional traceability)
-
(MAN.5 Risk Management - MAN.5.BP6: Monitor risks)
-
(SWE.2 Software Architectural Design - SWE.2.BP2 Allocate software requirements)
-
(SYS.1 Requirements Elicitation - SYS.1.BP3 Agree on requirements)
-
(ACQ.3 Contract Agreement - ACQ.3.BP5: Approve contract/agreement)
-
(HWE.1 Hardware Requirements Analysis - HWE.1.BP4 Analyse the impact on the operating environment)
-
(SPL.2 Product Release - SPL.2.BP2 Define release products)
-
(SWE.3 Software Detailed Design and Unit Construction - SWE.3.BP5 Establish bidirectional traceability)
-
(HWE.1 Hardware Requirements Analysis - HWE.1.BP6 Ensure consistency)
-
(ACQ.12 Legal and Administrative Requirements - ACQ.12.BP9 Define provision for the suppliers)
-
(SYS.1 Requirements Elicitation - SYS.1.BP4 Establish stakeholder requirements baseline)
-
(SUP.4 Joint Review - SUP.4.BP3 Prepare joint review)
-
(SYS.2 System Requirements Analysis - SYS.2.BP3 Analyze system requirements)
-
(SWE.1 Software Requirements Analysis - SWE.1.BP5 Develop verification criteria)
-
(SUP.4 Joint Review - SUP.4.BP8 Identify and record problems)
-
(SWE.2 Software Architectural Design - SWE.2.BP3 Define interfaces of software elements)
-
(SPL.2 Product Release - SPL.2.BP8 Identify the packaging for the release media)
-
(ACQ.11 Technical Requirements - ACQ.11.BP6 Communicate to affected groups)
-
(SWE.1 Software Requirements Analysis - SWE.1.BP1 Specify software requirements)
-
(SPL.2 Product Release - SPL.2.BP7 Determine the delivery media type for the release)
-
(SWE.4 Software Unit Verification - SWE.4.BP3 Perform static verification of software units)
-
(ACQ.3 Contract Agreement - ACQ.3.BP4: Review contract/agreement for risk mitigation actions)
-
(SPL.2 Product Release - SPL.2.BP10 Ensure product release approval before delivery)
-
(MAN.5 Risk Management - MAN.5.BP7: Take corrective action)
-
(REU.2 Reuse Program Management - REU.2.BP7 Get feedback from reuse)
-
(SWE.5 Software Integration and Integration Test - SWE.5.BP1 Develop software integration strategy)
-
(MAN.3 Project Management - MAN.3.BP3 Evaluate feasibility of the project)
-
(SPL.2 Product Release - SPL.2.BP6 Communicate the type, service level and duration of support for a release)
-
(SUP.7 Documentation - SUP.7.BP5 Develop documentation)
-
(SUP.4 Joint Review - SUP.4.BP6 Determine actions for review results)
-
(MAN.6 Measurement - MAN.6.BP9 Communicate measures)
-
(SWE.5 Software Integration and Integration Test - SWE.5.BP8 Ensure consistency)
-
(ACQ.13 Project Requirements - ACQ.13.BP10 Establish payment requirements)
-
(SYS.3 System Architectural Design - SYS.3.BP5 Evaluate alternative system architectures)
-
(MAN.5 Risk Management - MAN.5.BP4 Analyze risks)
-
(MAN.6 Measurement - MAN.6.BP3 Identify measurement information needs)
-
(SWE.4 Software Unit Verification - SWE.4.BP5 Establish bidirectional traceability)
-
(SUP.4 Joint Review - SUP.4.BP1 Define review elements)
-
(MAN.3 Project Management - MAN.3.BP7 Identify, monitor and adjust project interfaces and agreed commitments)
-
(SUP.9 Problem Resolution Management - SUP.9.BP7 Initiate problem resolution)
-
(ACQ.12 Legal and Administrative Requirements - ACQ.12.BP1 Identify relevant regulations)
-
(MAN.3 Project Management - MAN.3.BP2 Define project life cycle)
-
(ACQ.14 Request for Proposals - ACQ.14.BP5 Define project terms)
-
(MAN.3 Project Management - MAN.3.BP6 Ensure required skills, knowledge, and experience)
-
(SWE.1 Software Requirements Analysis - SWE.1.BP3 Analyze software requirements)
-
(ACQ.3 Contract Agreement - ACQ.3.BP6 Award contract/agreement)
-
(SUP.2 Verification - SUP.2.BP4 Determine and track actions for verification results)
-
(SUP.9 Problem Resolution Management - SUP.9.BP5 Authorize urgent resolution action)
-
(SUP.9 Problem Resolution Management - SUP.9.BP2 Identify and record the problem)
-
(SYS.2 System Requirements Analysis - SYS.2.BP2 Structure system requirements)
-
(ACQ.14 Request for Proposals - ACQ.14.BP1 Define rules for CFP / ITT)
-
(HWE.1 Hardware Requirements Analysis - HWE.1.BP1 Specify hardware requirements)
-
(PIM.3 Process Improvement - PIM.3.BP1 Establish commitment)
-
(SYS.2 System Requirements Analysis - SYS.2.BP8 Communicate agreed system requirements)
-
(HWE.1 Hardware Requirements Analysis - HWE.1.BP7 Communicate agreed hardware requirements)
-
(SUP.7 Documentation - SUP.7.BP1 Develop a documentation management strategy)
-
(SWE.6 Software Qualification Test - SWE.6.BP7 Summarize and communicate results)
-
(ACQ.15 Supplier Qualification - ACQ.15.BP5 Perform corrective actions)
-
(SYS.4 System Integration and Integration Test - SYS.4.BP4 Integrate system items)
-
(SWE.6 Software Qualification Test - SWE.6.BP6 Ensure consistency)
-
(ACQ.11 Technical Requirements - ACQ.11.BP1 Elicit needs)
-
(ACQ.13 Project Requirements - ACQ.13.BP8 Define exchange of information)
-
(HWE.1 Hardware Requirements Analysis - HWE.1.BP2 Structure hardware requirements)
-
(SPL.1 Supplier Tendering - SPL.1.BP1 Establish communication interface)
-
(SYS.3 System Architectural Design - SYS.3.BP4 Describe dynamic behavior)
-
(SYS.5 System Qualification Test - SYS.5.BP6 Ensure consistency)
-
(SUP.7 Documentation - SUP.7.BP3 Specify documentation requirements)
-
(SYS.1 Requirements Elicitation - SYS.1.BP1 Obtain stakeholder requirements and requests)
-
(SYS.3 System Architectural Design - SYS.3.BP6 Establish bidirectional traceability)
-
(MAN.6 Measurement - MAN.6.BP10 Evaluate information products and measurementactivities)
-
(SYS.1 Requirements Elicitation - SYS.1.BP6 Establish customer-supplier query communication mechanism)
-
(SYS.5 System Qualification Test - SYS.5.BP4 Test integrated system)
-
(SYS.1 Requirements Elicitation - SYS.1.BP5 Manage stakeholder requirements changes)
-
(SPL.2 Product Release - SPL.2.BP11 Ensure consistency)
-
(SUP.1 Quality Assurance - SUP.1.BP6 Implement an escalation mechanism)
-
(REU.2 Reuse Program Management - REU.2.BP3 Assess domains for potential reuse)
-
(ACQ.11 Technical Requirements - ACQ.11.BP9 Identify constraints and standards)
-
(SUP.4 Joint Review - SUP.4.BP7 Track actions for review results)
-
(SUP.8 Configuration Management - SUP.8.BP8 Verify the information about configured items)
-
(SYS.4 System Integration and Integration Test - SYS.4.BP9 Summarize and communicate results)
-
(SYS.1.BP1 Obtain stakeholder requirements and requests - SYS.1.O.4 A mechanism is established for continuous monitoring of stakeholderneeds)
-
(SWE.5.BP1 Develop software integration strategy - SWE.5.O.1 A software integration strategy consistent with the project plan, release plan and the software architectural design is developed to integrate the software items)
-
(ACQ.12.BP5 Establish acceptance criteria - ACQ.12.O.3 Acceptance criteria and mechanisms for handling of breaches to thefulfillment of contract are established)
-
(04-04 Software architectural design - SWE.2.O.4 The dynamic behavior and resource consumption objectives of thesoftware elements are defined)
-
(06-02 Handling and storage guide - SUP.8.O.7 Storage of the configuration items is controlled)
-
(13-04 Communication Record - SPL.1.O.6 Formal confirmation of agreement is obtained)
-
(SUP.7.BP5 Develop documentation - SUP.7.O.5 Documentation is developed and made available in accordance with identified standards)
-
(13-09 Meeting support record - ACQ.4.O.1 Joint activities, as agreed between the customer and the supplier, areperformed as needed)
-
(17-00 Requirement specification - ACQ.13.O.9 Support and maintenance requirements are established)
-
(15-13 Assessment/audit report - PIM.3.O.3 Analysis of the current status of the existing process is performed,focusing on those processes from which improvement stimuli arise)
-
(13-04 Communication Record - SWE.4.O.5 Results of the unit verification are summarized and communicated toall affected parties)
-
(19-10 Verification strategy - SUP.2.O.1 A verification strategy is developed, implemented and maintained)
-
(17-00 Requirement specification - ACQ.14.O.4 RThe financial terms of reference for costs and payments for CFP / ITT are defined)
-
(15-01 Analysis report - MAN.6.O.5 The required data is collected, stored, analyzed, and the resultsinterpreted)
-
(SWE.2.BP3 Define interfaces of software elements - SWE.2.O.3 The interfaces of each software element are defined)
-
(08-20 Risk mitigation plan - MAN.5.O.4 Risks are analyzed and the priority in which to apply resources totreatment of these risks is determined)
-
(17-03 Customer requirements - SYS.1.O.1 Continuing communication with the stakeholder is established)
-
(02-00 Contract - ACQ.13.O.2 Requirements for the organizational, management, controlling, andreporting aspects of a project are defined)
-
(ACQ.14.BP7 Identify relevant regulations - ACQ.14.O.7 A CFP / ITT is prepared and issued in accordance with acquisition policies and which complies with relevant national, international andregulatory laws, requirements, and policies)
-
(ACQ.3.BP3 Review contract/agreement for supplier capability monitoring - ACQ.3.O.3 Mechanisms for monitoring the capability and performance of thesupplier(s) and for mitigation of identified risks are reviewed andconsidered for inclusion in the contract conditions)
-
(SPL.2.BP11 Ensure consistency - SPL.2.O.5 Release approval is effected against defined criteria)
-
(SPL.2.BP10 Ensure product release approval before delivery - SPL.2.O.5 Release approval is effected against defined criteria)
-
(04-05 Software detailed design - SWE.3.O.3 The dynamic behavior of the software units is defined)
-
(08-52 Test plan - SWE.5.O.1 A software integration strategy consistent with the project plan, release plan and the software architectural design is developed to integrate the software items)
-
(SWE.6.BP6 Ensure consistency - SWE.6.O.5 Consistency and bidirectional traceability are established between software requirements and software qualification test specification including test cases and between test cases and test results)
-
(13-18 Quality record - SUP.1.O.4 Conformance of work products, processes and activities with relevant requirements is verified, documented, and communicated to the relevant parties)
-
(11-06 System - SYS.4.O.4 System items are integrated up to a complete integrated system according to the integration strategy)
-
(02-00 Contract - ACQ.12.O.3 Acceptance criteria and mechanisms for handling of breaches to thefulfillment of contract are established)
-
(SWE.4.BP4 Test software units - SWE.4.O.3 Software units are verified according to the software unit verification strategy and the defined criteria for software unit verification and the results are recorded)
-
(SUP.8.BP1 Develop a configuration management strategy - SUP.8.O.1 A configuration management strategy is developed)
-
(17-00 Requirement specification - ACQ.13.O.1 Consistency between financial, technical, contractual and projectrequirements is established)
-
(14-06 Schedule - MAN.3.O.5 Plans for the execution of the project are developed, implemented andmaintained)
-
(13-16 Change Request - SUP.10.O.6 Changes are approved and prioritized on the basis of analysis resultsand availability of resources)
-
(19-05 Reuse strategy - REU.2.O.1 The reuse strategy, including its purpose, scope, goals and objectives, is defined)
-
(SUP.4.BP4 Conduct joint reviews - SUP.4.O.1 Management and technical reviews are held based on the needs ofthe project)
-
(14-08 Tracking system - MAN.5.O.5 Risk measures are defined, applied, and assessed to determinechanges in the status of risk and the progress of the treatment activities)
-
(ACQ.13.BP4 Define management requirements - ACQ.13.O.2 Requirements for the organizational, management, controlling, andreporting aspects of a project are defined)
-
(SWE.1.BP4 Analyze the impact on the operating environment - SWE.1.O.7 The software requirements are evaluated for cost, schedule andtechnical impact)
-
(13-19 Review Record - SUP.7.O.5 Documentation is developed and made available in accordance with identified standards)
-
(08-50 Test specification - SYS.4.O.5 Test cases included in the system integration test specification are selected according to the system integration test strategy and the release plan)
-
(10-00 Process description - ACQ.12.O.1 A contractual approach is defined which is compliant with relevantnational, international and regulatory laws, guidance and policies)
-
(15-05 Evaluation report - PIM.3.O.7 The improvements made are evaluated and consideration given forusing the solution elsewhere within the organization)
-
(13-04 Communication Record - PIM.3.O.6 Knowledge gained from the improvement is communicated within theorganization)
-
(SYS.3.BP3 Define interfaces of system elements - SYS.3.O.3 The interfaces of each system element are defined)
-
(MAN.6.BP8 Use measurement information for decision-making - MAN.6.O.6 Information products are used to support decisions and provide anobjective basis for communication)
-
(17-00 Requirement specification - ACQ.13.O.8 Rights for use and distribution of the product by the customer andsupplier are defined)
-
(ACQ.11.BP7 Establish a change mechanism - ACQ.11.O.4 A mechanism is established to incorporate changed or newrequirements into the established baseline)
-
(13-14 Progress status record - ACQ.4.O.2 All information, agreed upon for exchange, is communicated regularlybetween the supplier and customer)
-
(SYS.3.BP5 Evaluate alternative system architectures - SYS.3.O.1 A system architectural design is defined that identifies the elements ofthe system)
-
(15-13 Assessment/audit report - REU.2.O.4 The organization's systematic reuse capability is assessed)
-
(13-25 Verification results - SUP.2.O.2 Criteria for verification of all required work products are identified)
-
(SUP.1.BP1 Develop a project quality assurance strategy - SUP.1.O.1 A strategy for performing quality assurance is developed, implemented, and maintained)
-
(07-03 Personnel performance measure - MAN.6.O.4 Measurement activities are identified and performed)
-
(MAN.6.BP7 Analyze measures - MAN.6.O.5 The required data is collected, stored, analyzed, and the resultsinterpreted)
-
(13-04 Communication Record - SYS.4.O.8 Results of the system integration test are summarized andcommunicated to all affected parties)
-
(ACQ.4.BP1 Agree on and maintain joint processes - ACQ.4.O.4 Changes to the agreement, if needed, are negotiated between thecustomer and the supplier and documented in the agreement)
-
(REU.2.BP4 Assess reuse maturity - REU.2.O.4 The organization's systematic reuse capability is assessed)
-
(15-03 Configuration status report - SPL.2.O.2 The release is assembled from configured items)
-
(13-04 Communication Record - MAN.3.O.6 Progress of the project is monitored and reported)
-
(SYS.2.BP3 Analyze system requirements - SYS.2.O.1 A defined set of system requirements is established)
-
(SWE.2.BP6 Evaluate alternative software architectures - SWE.2.O.5 Consistency and bidirectional traceability are established betweensoftware requirements and software architectural design)
-
(17-02 Build list - SWE.5.O.4 Software units and software items are integrated up to a complete integrated software according to the integration strategy)
-
(SUP.8.BP4 Establish branch management - SUP.8.O.6 The completeness and consistency of the baselines is ensured)
-
(08-19 Risk management plan - MAN.5.O.4 Risks are analyzed and the priority in which to apply resources totreatment of these risks is determined)
-
(01-50 Integrated software - SWE.5.O.4 Software units and software items are integrated up to a complete integrated software according to the integration strategy)
-
(04-05 Software detailed design - SWE.3.O.2 Interfaces of each software unit are defined)
-
(SUP.7.BP1 Develop a documentation management strategy - SUP.7.O.1 A strategy identifying the documentation to be produced during the lifecycle of the product or service is developed)
-
(SUP.2.BP2 Develop criteria for verification - SUP.2.O.2 Criteria for verification of all required work products are identified)
-
(08-52 Test plan - SWE.4.O.1 A software unit verification strategy including regression strategy is developed to verify the software units)
-
(12-03 Reuse proposal - REU.2.O.4 The organization's systematic reuse capability is assessed)
-
(02-01 Commitment/agreement - PIM.3.O.1 Commitment is established to provide resources to sustainimprovement actions)
-
(15-13 Assessment/audit report - SUP.4.O.1 Management and technical reviews are held based on the needs ofthe project)
-
(13-19 Review Record - SUP.4.O.3 Review results are made known to all affected parties)
-
(13-50 Test result - SWE.6.O.4 The integrated software is tested using the selected test cases and the results of software qualification test are recorded)
-
(SWE.2.BP6 Evaluate alternative software architectures - SWE.2.O.3 The interfaces of each software element are defined)
-
(ACQ.15.BP4 Evaluate any shortfalls - ACQ.15.O.4 Any shortfalls in capability are identified and evaluated)
-
(17-00 Requirement specification - ACQ.12.O.2 An agreement, (contractual) terms and conditions are defined todescribe how the supplier will meet the needs and expectations)
-
(SWE.4.BP1 Develop software unit verification strategy including regression strategy - SWE.4.O.1 A software unit verification strategy including regression strategy is developed to verify the software units)
-
(16-06 Process repository - PIM.3.O.4 Improvement goals are identified and prioritized, and consequentchanges to the process are defined, planned and implemented)
-
(08-20 Risk mitigation plan - MAN.5.O.3 Risks are identified as they develop during the conduct of the project)
-
(04-06 System architectural design - SYS.3.O.1 A system architectural design is defined that identifies the elements ofthe system)
-
(13-21 Change control record - SYS.1.O.3 A change mechanism is established to evaluate and incorporatechanges to stakeholder requirements into the baselined requirementsbased on changing stakeholder needs)
-
(SWE.6.BP3 Select test cases - SWE.6.O.3 Test cases included in the software qualification test specification are selected according to the software qualification test strategy and the release plan)
-
(04-04 Software architectural design - SWE.2.O.5 Consistency and bidirectional traceability are established betweensoftware requirements and software architectural design)
-
(15-08 Risk analysis report - MAN.5.O.4 Risks are analyzed and the priority in which to apply resources totreatment of these risks is determined)
-
(ACQ.14.BP6 Define technical terms - ACQ.14.O.6 The technical terms of reference for CFP / ITT are defined)
-
(13-16 Change Request - SUP.10.O.5 Requests for change are analyzed, and resource requirements are estimated)
-
(ACQ.12.BP9 Define provision for the suppliers - ACQ.12.O.6 Provision for the suppliers to deliver other requirements (e.g. qualityplan, escrow arrangements etc.) is defined)
-
(04-05 Software detailed design - SWE.3.O.1 A detailed design is developed that describes software units)
-
(15-09 Risk status report - MAN.5.O.4 Risks are analyzed and the priority in which to apply resources totreatment of these risks is determined)
-
(08-50 Test specification - SYS.5.O.2 A specification for system qualification test of the integrated system according to the system qualification test strategy is developed that issuitable to provide evidence for compliance with the system requirements)
-
(02-00 Contract - ACQ.3.O.2 The contract/agreement clearly and unambiguously specifies theexpectations, responsibilities, work products/deliverables and liabilitiesof both the supplier(s) and the acquirer)
-
(07-07 Risk measure - MAN.6.O.7 The measurement process and measures are evaluated andcommunicated to the process owner)
-
(13-09 Meeting support record - ACQ.3.O.1 A contract/agreement is negotiated, reviewed, approved and awardedto the supplier(s))
-
(13-19 Review Record - SWE.2.O.5 Consistency and bidirectional traceability are established betweensoftware requirements and software architectural design)
-
(14-02 Corrective Action Register - ACQ.12.O.3 Acceptance criteria and mechanisms for handling of breaches to thefulfillment of contract are established)
-
(07-07 Risk measure - MAN.6.O.3 An appropriate set of measures, driven by the information needs areidentified and/or developed)
-
(SYS.2.BP6 Establish bidirectional traceability - SYS.2.O.6 Consistency and bidirectional traceability are established between stakeholder requirements and system requirements)
-
(SUP.7.BP3 Specify documentation requirements - SUP.7.O.2 The standards to be applied for the development of the documentation are identified)
-
(15-05 Evaluation report - PIM.3.O.3 Analysis of the current status of the existing process is performed,focusing on those processes from which improvement stimuli arise)
-
(14-02 Corrective Action Register - ACQ.4.O.4 Changes to the agreement, if needed, are negotiated between thecustomer and the supplier and documented in the agreement)
-
(SYS.5.BP3 Select test cases - SYS.5.O.3 Test cases included in the system qualification test specification are selected according to the system qualification test strategy and the release plan)
-
(REU.2.BP7 Get feedback from reuse - REU.2.O.8 The reuse program is monitored and evaluated)
-
(SPL.2.BP12 Provide a release note - SPL.2.O.6 The product release is made available to the intended customer)
-
(13-04 Communication Record - SUP.1.O.4 Conformance of work products, processes and activities with relevant requirements is verified, documented, and communicated to the relevant parties)
-
(14-02 Corrective Action Register - MAN.3.O.7 Corrective action is taken when project goals are not achieved, andrecurrence of problems identified in the project is prevented.)
-
(17-08 Interface requirements specification - SYS.2.O.1 A defined set of system requirements is established)
-
(13-50 Test result - SYS.4.O.6 System item interactions are tested using the selected test cases andthe results of system integration testing are recorded)
-
(SYS.4.BP8 Ensure consistency - SYS.4.O.7 Consistency and bidirectional traceability between the elements of the system architectural design and test cases included in the system integration test specification and bidirectional traceability between testcases and test results is established)
-
(ACQ.4.BP2 Exchange all agreed information - ACQ.4.O.2 All information, agreed upon for exchange, is communicated regularlybetween the supplier and customer)
-
(13-05 Contract review record - ACQ.3.O.1 A contract/agreement is negotiated, reviewed, approved and awardedto the supplier(s))
-
(SYS.4.BP3 Develop specification for system integration test - SYS.4.O.3 A specification for system integration test according to the system integration test strategy is developed that is suitable to provide evidence for compliance of the integrated system items with the system architectural design, including the interfaces between system items)
-
(SUP.8.BP9 Manage the storage of configuration items and baselines - SUP.8.O.6 The completeness and consistency of the baselines is ensured)
-
(SUP.2.BP1 Develop a verification strategy - SUP.2.O.1 A verification strategy is developed, implemented and maintained)
-
(MAN.6.BP4 Specify measures - MAN.6.O.3 An appropriate set of measures, driven by the information needs areidentified and/or developed)
-
(ACQ.4.BP3 Review technical development with the supplier - ACQ.4.O.3 Performance of the supplier is monitored against the agreements)
-
(SUP.9.BP5 Authorize urgent resolution action - SUP.9.O.4 Problem resolution is initiated)
-
(17-50 Verification criteria - SYS.2.O.2 System requirements are categorized and analyzed for correctnessand verifiability)
-
(13-07 Problem record - SUP.2.O.3 Required verification activities are performed)
-
(18-07 Quality criteria - SUP.1.O.1 A strategy for performing quality assurance is developed, implemented, and maintained)
-
(SUP.4.BP6 Determine actions for review results - SUP.4.O.4 Action items resulting from reviews are tracked to closure)
-
(SWE.3.BP4 Evaluate software detailed design - SWE.3.O.3 The dynamic behavior of the software units is defined)
-
(08-14 Recovery plan - SUP.8.O.7 Storage of the configuration items is controlled)
-
(08-27 Problem management plan - SUP.9.O.1 A problem resolution management strategy is developed)
-
(SYS.1.BP1 Obtain stakeholder requirements and requests - SYS.1.O.1 Continuing communication with the stakeholder is established)
-
(13-18 Quality record - SUP.1.O.3 Non-conformances of work products, processes, and process activities with relevant requirements are identified, recorded, communicated to the relevant parties, tracked, resolved, and further prevented)
-
(SPL.1.BP6 Identify and nominate staff - SPL.1.O.4 Suitable staff are identified to perform the proposed work)
-
(SPL.2.BP1 Define the functional content of releases - SPL.2.O.1 The contents of the product release are determined)
-
(SUP.8.BP4 Establish branch management - SUP.8.O.3 Modifications and releases of the configuration items are controlled)
-
(SUP.10.BP7 Track change requests to closure - SUP.10.O.8 The status of all change requests is known)
-
(SUP.1.BP2 Assure quality of work products - SUP.1.O.2 Quality assurance is performed independently and objectively without conflicts of interest)
-
(14-09 Work Breakdown Structure - MAN.3.O.4 Interfaces within the project, and with other projects and organizational units, are identified and monitored)
-
(06-02 Handling and storage guide - SUP.8.O.5 The status of the configuration items and modifications is recorded and reported)
-
(ACQ.11.BP1 Elicit needs - ACQ.11.O.1 The technical requirements, including environment effect evaluation,safety and security requirements where appropriate, are defined anddeveloped to match needs and expectations)
-
(SPL.2.BP9 Define and produce the product release documentation/release notes - SPL.2.O.3 The release documentation is defined and produced)
-
(13-07 Problem record - SUP.1.O.3 Non-conformances of work products, processes, and process activities with relevant requirements are identified, recorded, communicated to the relevant parties, tracked, resolved, and further prevented)
-
(13-19 Review Record - SUP.4.O.5 Problems are identified and recorded)
-
(08-19 Risk management plan - SYS.1.O.6 Changes arising from changing technology and stakeholder needs areidentified, the associated risks assessed and their impact managed)
-
(MAN.5.BP3 Identify risks - MAN.5.O.3 Risks are identified as they develop during the conduct of the project)
-
(13-50 Test result - SWE.5.O.6 Integrated software items are tested using the selected test cases and the results of software integration test are recorded)
-
(SWE.1.BP5 Develop verification criteria - SWE.1.O.2 Software requirements are categorized and analyzed for correctness and verifiability)
-
(MAN.3.BP4 Define, monitor and adjust project activities - MAN.3.O.7 Corrective action is taken when project goals are not achieved, andrecurrence of problems identified in the project is prevented.)
-
(SUP.8.BP9 Manage the storage of configuration items and baselines - SUP.8.O.7 Storage of the configuration items is controlled)
-
(ACQ.13.BP5 Identify required competency - ACQ.13.O.3 Requirements for adequate staffing of projects by a competent team(e.g. resources with requisite legal, contractual, technical and projectcompetence) with clear responsibilities and goals are defined)
-
(SUP.7.BP6 Check documentation - SUP.7.O.5 Documentation is developed and made available in accordance with identified standards)
-
(SWE.1.BP1 Specify software requirements - SWE.1.O.5 The software requirements are updated as needed)
-
(ACQ.4.BP2 Exchange all agreed information - ACQ.4.O.3 Performance of the supplier is monitored against the agreements)
-
(02-01 Commitment/agreement - ACQ.12.O.5 Warranties and service level agreements are provided for whereapplicable)
-
(SYS.4.BP9 Summarize and communicate results - SYS.4.O.8 Results of the system integration test are summarized andcommunicated to all affected parties)
-
(07-03 Personnel performance measure - MAN.6.O.7 The measurement process and measures are evaluated andcommunicated to the process owner)
-
(13-04 Communication Record - SYS.5.O.6 results of the system qualification test are summarized and communicated to all affected parties)
-
(SYS.1.BP2 Understand stakeholder expectations - SYS.1.O.2 Agreed stakeholder requirements are defined and baselined)
-
(08-14 Recovery plan - MAN.5.O.4 Risks are analyzed and the priority in which to apply resources totreatment of these risks is determined)
-
(SWE.3.BP1 Develop software detailed design - SWE.3.O.1 A detailed design is developed that describes software units)
-
(ACQ.3.BP1 Negotiate the contract/agreement - ACQ.3.O.1 A contract/agreement is negotiated, reviewed, approved and awardedto the supplier(s))
-
(17-08 Interface requirements specification - SWE.1.O.1 The software requirements to be allocated to the software elements ofthe system and their interfaces are defined)
-
(13-08 Baseline - SUP.8.O.5 The status of the configuration items and modifications is recorded and reported)
-
(13-19 Review Record - ACQ.13.O.1 Consistency between financial, technical, contractual and projectrequirements is established)
-
(11-04 Product release package - SPL.2.O.3 The release documentation is defined and produced)
-
(SUP.1.BP2 Assure quality of work products - SUP.1.O.4 Conformance of work products, processes and activities with relevant requirements is verified, documented, and communicated to the relevant parties)
-
(ACQ.13.BP12 Communicate risks - ACQ.13.O.6 Potential risks are identified)
-
(SWE.2.BP1 Develop software architectural design - SWE.2.O.1 A software architectural design is defined that identifies the elementsof the software)
-
(08-12 Project Plan - SPL.1.O.4 Suitable staff are identified to perform the proposed work)
-
(SWE.1.BP8 Communicate agreed software requirements - SWE.1.O.8 The software requirements are agreed and communicated to allaffected parties)
-
(08-50 Test specification - SWE.6.O.3 Test cases included in the software qualification test specification are selected according to the software qualification test strategy and the release plan)
-
(13-22 Traceability record - SYS.4.O.7 Consistency and bidirectional traceability between the elements of the system architectural design and test cases included in the system integration test specification and bidirectional traceability between testcases and test results is established)
-
(SUP.10.BP2 Identify and record the change requests - SUP.10.O.2 Requests for changes are recorded and identified)
-
(03-04 Customer satisfaction data - MAN.6.O.5 The required data is collected, stored, analyzed, and the resultsinterpreted)
-
(17-08 Interface requirements specification - SWE.1.O.3 The impact of software requirements on the operating environment is analyzed)
-
(13-16 Change Request - SUP.10.O.2 Requests for changes are recorded and identified)
-
(ACQ.13.BP10 Establish payment requirements - ACQ.13.O.5 Requirements for the completion and acceptance of interim workproducts and release of payments are established)
-
(MAN.3.BP7 Identify, monitor and adjust project interfaces and agreed commitments - MAN.3.O.4 Interfaces within the project, and with other projects and organizational units, are identified and monitored)
-
(SUP.10.BP1 Develop a change request management strategy - SUP.10.O.1 A change request management strategy is developed)
-
(SYS.2.BP7 Ensure consistency - SYS.2.O.6 Consistency and bidirectional traceability are established between stakeholder requirements and system requirements)
-
(13-04 Communication Record - SUP.1.O.5 Authority to escalate non-conformances to appropriate levels of management is established)
-
(SYS.3.BP6 Establish bidirectional traceability - SYS.3.O.5 Consistency and bidirectional traceability are established between system requirements and system architectural design)
-
(SUP.10.BP4 Analyze and assess change requests - SUP.10.O.9 Bi-directional traceability is established between change requests and affected work product)
-
(ACQ.12.BP10 Establish criteria for liability issues - ACQ.12.O.7 Recognized criteria for proprietary, regulatory and other productliabilities issues are established)
-
(ACQ.14.BP1 Define rules for CFP / ITT - ACQ.14.O.1 Rules are defined for proposal/tender invitation and evaluation which comply with the acquisition policy and strategy)
-
(PIM.3.BP8 Communicate results of improvement - PIM.3.O.6 Knowledge gained from the improvement is communicated within theorganization)
-
(14-05 Preferred suppliers register - ACQ.15.O.3 The suppliers which possess required qualification are short-listed fortender solution(s) evaluation)
-
(SWE.2.BP2 Allocate software requirements - SWE.2.O.2 The software requirements are allocated to the elements of thesoftware)
-
(02-00 Contract - ACQ.3.O.3 Mechanisms for monitoring the capability and performance of thesupplier(s) and for mitigation of identified risks are reviewed andconsidered for inclusion in the contract conditions)
-
(MAN.3.BP8 Define, monitor and adjust project schedule - MAN.3.O.7 Corrective action is taken when project goals are not achieved, andrecurrence of problems identified in the project is prevented.)
-
(17-08 Interface requirements specification - SYS.3.O.3 The interfaces of each system element are defined)
-
(SUP.1.BP4 Summarize and communicate quality assurance activitiesand results - SUP.1.O.4 Conformance of work products, processes and activities with relevant requirements is verified, documented, and communicated to the relevant parties)
-
(SPL.1.BP3 Establish customer proposal evaluation criteria - SPL.1.O.2 Requests for proposal are evaluated according to defined criteria todetermine whether or not to submit a proposal)
-
(14-09 Work Breakdown Structure - MAN.3.O.5 Plans for the execution of the project are developed, implemented andmaintained)
-
(SUP.9.BP8 Track problems to closure - SUP.9.O.6 The status of problems and their trend are known)
-
(14-09 Work Breakdown Structure - MAN.3.O.3 The activities and resources necessary to complete the work are sizedand estimated)
-
(08-20 Risk mitigation plan - MAN.5.O.6 Appropriate treatment is taken to correct or avoid the impact of riskbased on its priority, probability, and consequence or other definedrisk threshold)
-
(16-03 Configuration management system - SUP.8.O.1 A configuration management strategy is developed)
-
(13-21 Change control record - SYS.2.O.1 A defined set of system requirements is established)
-
(06-04 Training material - PIM.3.O.4 Improvement goals are identified and prioritized, and consequentchanges to the process are defined, planned and implemented)
-
(13-07 Problem record - SUP.9.O.2 Problems are recorded, uniquely identified and classified)
-
(13-21 Change control record - SYS.1.O.4 A mechanism is established for continuous monitoring of stakeholderneeds)
-
(13-09 Meeting support record - SUP.4.O.1 Management and technical reviews are held based on the needs ofthe project)
-
(REU.2.BP8 Monitor reuse - REU.2.O.6 Reuse is implemented according to the reuse strategy)
-
(SWE.1.BP1 Specify software requirements - SWE.1.O.1 The software requirements to be allocated to the software elements ofthe system and their interfaces are defined)
-
(ACQ.3.BP4: Review contract/agreement for risk mitigation actions - ACQ.3.O.3 Mechanisms for monitoring the capability and performance of thesupplier(s) and for mitigation of identified risks are reviewed andconsidered for inclusion in the contract conditions)
-
(14-01 Change history - SUP.7.O.6 Documentation is maintained in accordance with defined criteria)
-
(SUP.8.BP3 Establish a configuration management system - SUP.8.O.3 Modifications and releases of the configuration items are controlled)
-
(ACQ.13.BP11 Identify risks - ACQ.13.O.6 Potential risks are identified)
-
(ACQ.13.BP2 Communicate with relevant groups - ACQ.13.O.1 Consistency between financial, technical, contractual and projectrequirements is established)
-
(MAN.3.BP1 Define the scope of work - MAN.3.O.1 The scope of the work for the project is defined)
-
(SYS.5.BP5 Establish bidirectional traceability - SYS.5.O.5 Consistency and bidirectional traceability are established between system requirements and test cases included in the system qualification test specification and between test cases and test results)
-
(SWE.1.BP3 Analyze software requirements - SWE.1.O.7 The software requirements are evaluated for cost, schedule andtechnical impact)
-
(08-12 Project Plan - MAN.3.O.5 Plans for the execution of the project are developed, implemented andmaintained)
-
(08-50 Test specification - SWE.5.O.3 A specification for software integration test according to the software integration test strategy is developed that is suitable to provide evidence for compliance of the integrated software items with the software architectural design, including the interfaces between the software units and between the software items)
-
(13-10 Configuration management record - SUP.8.O.5 The status of the configuration items and modifications is recorded and reported)
-
(13-19 Review Record - SUP.4.O.4 Action items resulting from reviews are tracked to closure)
-
(REU.2.BP6 Implement the reuse program - REU.2.O.6 Reuse is implemented according to the reuse strategy)
-
(15-01 Analysis report - SWE.1.O.4 Prioritization for implementing the software requirements is defined)
-
(13-19 Review Record - MAN.3.O.2 The feasibility of achieving the goals of the project with available resources and constraints is evaluated)
-
(SWE.2.BP8 Ensure consistency - SWE.2.O.5 Consistency and bidirectional traceability are established betweensoftware requirements and software architectural design)
-
(SPL.2.BP1 Define the functional content of releases - SPL.2.O.3 The release documentation is defined and produced)
-
(PIM.3.BP6 Implement process changes - PIM.3.O.4 Improvement goals are identified and prioritized, and consequentchanges to the process are defined, planned and implemented)
-
(REU.2.BP2 Identify domains for potential reuse - REU.2.O.2 Each domain is assessed to determine its reuse potential)
-
(REU.2.BP7 Get feedback from reuse - REU.2.O.7 Feedback, communication, and notification mechanisms areestablished, that operate between affected parties)
-
(15-01 Analysis report - SYS.2.O.2 System requirements are categorized and analyzed for correctnessand verifiability)
-
(15-05 Evaluation report - MAN.6.O.5 The required data is collected, stored, analyzed, and the resultsinterpreted)
-
(08-12 Project Plan - MAN.3.O.4 Interfaces within the project, and with other projects and organizational units, are identified and monitored)
-
(08-17 Reuse plan - REU.2.O.5 Reuse proposals are evaluated to ensure the reuse product is suitablefor the proposed application)
-
(17-00 Requirement specification - ACQ.13.O.6 Potential risks are identified)
-
(07-02 Field measure - MAN.6.O.3 An appropriate set of measures, driven by the information needs areidentified and/or developed)
-
(14-50 Stakeholder Groups List - MAN.3.O.4 Interfaces within the project, and with other projects and organizational units, are identified and monitored)
-
(15-05 Evaluation report - PIM.3.O.5 The effects of process implementation are monitored, measured andconfirmed against the defined improvement goals)
-
(ACQ.4.BP1 Agree on and maintain joint processes - ACQ.4.O.2 All information, agreed upon for exchange, is communicated regularlybetween the supplier and customer)
-
(PIM.3.BP2 Identify issues - PIM.3.O.3 Analysis of the current status of the existing process is performed,focusing on those processes from which improvement stimuli arise)
-
(13-19 Review Record - SYS.1.O.5 A mechanism is established for ensuring that customers can easilydetermine the status and disposition of their requests)
-
(13-04 Communication Record - SWE.3.O.5 The software detailed design and the relationship to the software architectural design is agreed and communicated to all affected parties)
-
(07-03 Personnel performance measure - MAN.6.O.3 An appropriate set of measures, driven by the information needs areidentified and/or developed)
-
(15-05 Evaluation report - PIM.3.O.4 Improvement goals are identified and prioritized, and consequentchanges to the process are defined, planned and implemented)
-
(17-12 System requirements specification - SYS.2.O.1 A defined set of system requirements is established)
-
(ACQ.13.BP13 Define ownership of relationships - ACQ.13.O.7 Requirements for ownership of interactions and relationships withsuppliers are defined)
-
(SWE.3.BP2 Define interfaces of software units - SWE.3.O.2 Interfaces of each software unit are defined)
-
(18-50 Supplier qualification criteria - ACQ.15.O.1 Criteria are established for qualifying suppliers)
-
(11-05 Software unit - SWE.3.O.6 Software units defined by the software detailed design are produced)
-
(ACQ.4.BP4: Review progress of the supplier - ACQ.4.O.3 Performance of the supplier is monitored against the agreements)
-
(13-21 Change control record - SWE.1.O.7 The software requirements are evaluated for cost, schedule andtechnical impact)
-
(07-01 Customer satisfaction survey - MAN.6.O.3 An appropriate set of measures, driven by the information needs areidentified and/or developed)
-
(13-04 Communication Record - SUP.2.O.5 Results of the verification activities are made available to the customer and other involved parties)
-
(02-01 Commitment/agreement - ACQ.12.O.6 Provision for the suppliers to deliver other requirements (e.g. qualityplan, escrow arrangements etc.) is defined)
-
(SWE.3.BP5 Establish bidirectional traceability - SWE.3.O.4 Consistency and bidirectional traceability are established between software requirements and software units; and consistency and bidirectional traceability are established between software architectural design and software detailed design; and consistency and bidirectional traceability are established between software detailed design and software units)
-
(15-16 Improvement opportunity - PIM.3.O.7 The improvements made are evaluated and consideration given forusing the solution elsewhere within the organization)
-
(SYS.1.BP5 Manage stakeholder requirements changes - SYS.1.O.3 A change mechanism is established to evaluate and incorporatechanges to stakeholder requirements into the baselined requirementsbased on changing stakeholder needs)
-
(13-10 Configuration management record - SUP.8.O.2 All configuration items generated by a process or project are identified, defined and baselined according to the configuration management strategy)
-
(SUP.4.BP7 Track actions for review results - SUP.4.O.4 Action items resulting from reviews are tracked to closure)
-
(13-22 Traceability record - SYS.2.O.6 Consistency and bidirectional traceability are established between stakeholder requirements and system requirements)
-
(15-06 Project Status Report - MAN.3.O.6 Progress of the project is monitored and reported)
-
(13-06 Delivery record - SPL.2.O.6 The product release is made available to the intended customer)
-
(REU.2.BP1 Define organizational reuse strategy - REU.2.O.1 The reuse strategy, including its purpose, scope, goals and objectives, is defined)
-
(15-16 Improvement opportunity - ACQ.15.O.4 Any shortfalls in capability are identified and evaluated)
-
(08-14 Recovery plan - MAN.5.O.6 Appropriate treatment is taken to correct or avoid the impact of riskbased on its priority, probability, and consequence or other definedrisk threshold)
-
(SUP.9.BP7 Initiate problem resolution - SUP.9.O.4 Problem resolution is initiated)
-
(08-52 Test plan - SWE.6.O.1 A software qualification test strategy including regression test strategy consistent with the project plan and release plan is developed to test the integrated software)
-
(13-50 Test result - SWE.6.O.6 Results of the software qualification test are summarized and communicated to all affected parties)
-
(08-04 Configuration management plan - SUP.8.O.2 All configuration items generated by a process or project are identified, defined and baselined according to the configuration management strategy)
-
(02-00 Contract - ACQ.3.O.1 A contract/agreement is negotiated, reviewed, approved and awardedto the supplier(s))
-
(08-50 Test specification - SYS.5.O.3 Test cases included in the system qualification test specification are selected according to the system qualification test strategy and the release plan)
-
(ACQ.13.BP15 Establish support and maintenance requirements - ACQ.13.O.9 Support and maintenance requirements are established)
-
(SWE.1.BP2 Structure software requirements - SWE.1.O.2 Software requirements are categorized and analyzed for correctness and verifiability)
-
(13-50 Test result - SWE.4.O.5 Results of the unit verification are summarized and communicated toall affected parties)
-
(04-06 System architectural design - SYS.3.O.5 Consistency and bidirectional traceability are established between system requirements and system architectural design)
-
(SPL.2.BP8 Identify the packaging for the release media - SPL.2.O.4 The release delivery mechanism and media are determined)
-
(13-16 Change Request - SUP.10.O.3 Dependencies and relationships to other change requests are identified)
-
(SWE.5.BP3 Develop specification for software integration test - SWE.5.O.3 A specification for software integration test according to the software integration test strategy is developed that is suitable to provide evidence for compliance of the integrated software items with the software architectural design, including the interfaces between the software units and between the software items)
-
(13-19 Review Record - SYS.1.O.4 A mechanism is established for continuous monitoring of stakeholderneeds)
-
(PIM.3.BP9 Evaluate the results of the improvement project - PIM.3.O.7 The improvements made are evaluated and consideration given forusing the solution elsewhere within the organization)
-
(MAN.3.BP9 Ensure consistency - MAN.3.O.4 Interfaces within the project, and with other projects and organizational units, are identified and monitored)
-
(13-07 Problem record - SUP.9.O.3 Problems are analyzed and assessed to identify an appropriate solution)
-
(SUP.1.BP3 Assure quality of process activities - SUP.1.O.3 Non-conformances of work products, processes, and process activities with relevant requirements are identified, recorded, communicated to the relevant parties, tracked, resolved, and further prevented)
-
(SYS.2.BP3 Analyze system requirements - SYS.2.O.7 The system requirements are evaluated for cost, schedule andtechnical impact)
-
(04-06 System architectural design - SYS.3.O.2 The system requirements are allocated to the elements of the system)
-
(17-00 Requirement specification - ACQ.13.O.3 Requirements for adequate staffing of projects by a competent team(e.g. resources with requisite legal, contractual, technical and projectcompetence) with clear responsibilities and goals are defined)
-
(13-19 Review Record - SYS.5.O.5 Consistency and bidirectional traceability are established between system requirements and test cases included in the system qualification test specification and between test cases and test results)
-
(15-01 Analysis report - SYS.1.O.3 A change mechanism is established to evaluate and incorporatechanges to stakeholder requirements into the baselined requirementsbased on changing stakeholder needs)
-
(08-14 Recovery plan - SUP.8.O.1 A configuration management strategy is developed)
-
(15-09 Risk status report - MAN.5.O.5 Risk measures are defined, applied, and assessed to determinechanges in the status of risk and the progress of the treatment activities)
-
(SUP.7.BP7 Distribute documentation - SUP.7.O.5 Documentation is developed and made available in accordance with identified standards)
-
(SUP.4.BP5 Distribute the results - SUP.4.O.3 Review results are made known to all affected parties)
-
(18-06 Product release criteria - SPL.2.O.5 Release approval is effected against defined criteria)
-
(08-00 Plan - PIM.3.O.4 Improvement goals are identified and prioritized, and consequentchanges to the process are defined, planned and implemented)
-
(SYS.3.BP4 Describe dynamic behavior - SYS.3.O.4 The dynamic behavior of the system elements is defined)
-
(17-50 Verification criteria - SWE.1.O.2 Software requirements are categorized and analyzed for correctness and verifiability)
-
(MAN.3.BP5 Define, monitor and adjust project estimates andresources - MAN.3.O.7 Corrective action is taken when project goals are not achieved, andrecurrence of problems identified in the project is prevented.)
-
(SUP.8.BP4 Establish branch management - SUP.8.O.1 A configuration management strategy is developed)
-
(02-00 Contract - ACQ.12.O.4 The rights of the acquirer to assume, modify or evaluate, directly orindirectly Intellectual Property Rights are established)
-
(SYS.1.BP3 Agree on requirements - SYS.1.O.2 Agreed stakeholder requirements are defined and baselined)
-
(SWE.5.BP2 Develop software integration test strategy includingregression test strategy - SWE.5.O.2 A software integration test strategy including the regression test strategy is developed to test the software unit and software item interactions)
-
(SYS.5.BP4 Test integrated system - SYS.5.O.4 The integrated system is tested using the selected test cases and the results of system qualification test are recorded)
-
(SWE.1.BP3 Analyze software requirements - SWE.1.O.2 Software requirements are categorized and analyzed for correctness and verifiability)
-
(SYS.1.BP4 Establish stakeholder requirements baseline - SYS.1.O.3 A change mechanism is established to evaluate and incorporatechanges to stakeholder requirements into the baselined requirementsbased on changing stakeholder needs)
-
(SYS.5.BP2 Develop specification for system qualification test - SYS.5.O.2 A specification for system qualification test of the integrated system according to the system qualification test strategy is developed that issuitable to provide evidence for compliance with the system requirements)
-
(SUP.10.BP4 Analyze and assess change requests - SUP.10.O.3 Dependencies and relationships to other change requests are identified)
-
(08-12 Project Plan - MAN.3.O.3 The activities and resources necessary to complete the work are sizedand estimated)
-
(SUP.1.BP4 Summarize and communicate quality assurance activitiesand results - SUP.1.O.3 Non-conformances of work products, processes, and process activities with relevant requirements are identified, recorded, communicated to the relevant parties, tracked, resolved, and further prevented)
-
(13-19 Review Record - SUP.1.O.3 Non-conformances of work products, processes, and process activities with relevant requirements are identified, recorded, communicated to the relevant parties, tracked, resolved, and further prevented)
-
(07-02 Field measure - MAN.6.O.7 The measurement process and measures are evaluated andcommunicated to the process owner)
-
(SUP.8.BP4 Establish branch management - SUP.8.O.7 Storage of the configuration items is controlled)
-
(SPL.1.BP4 Evaluate customer request for proposal - SPL.1.O.2 Requests for proposal are evaluated according to defined criteria todetermine whether or not to submit a proposal)
-
(SWE.6.BP2 Develop specification for software qualification test - SWE.6.O.2 A specification for software qualification test of the integrated software according to the software qualification test strategy is developed that is suitable to provide evidence for compliance with the software requirements)
-
(SUP.8.BP7 Report configuration status - SUP.8.O.5 The status of the configuration items and modifications is recorded and reported)
-
(13-22 Traceability record - SWE.5.O.7 Consistency and bidirectional traceability are established between the elements of the software architectural design and the test cases included in the software integration test specification and between test cases and test results)
-
(13-16 Change Request - ACQ.4.O.4 Changes to the agreement, if needed, are negotiated between thecustomer and the supplier and documented in the agreement)
-
(ACQ.12.BP4 Ensure usage of agreed terms and conditions - ACQ.12.O.2 An agreement, (contractual) terms and conditions are defined todescribe how the supplier will meet the needs and expectations)
-
(13-04 Communication Record - SUP.4.O.3 Review results are made known to all affected parties)
-
(04-03 Domain model - REU.2.O.2 Each domain is assessed to determine its reuse potential)
-
(06-02 Handling and storage guide - SUP.8.O.4 Modifications and releases are made available to affected parties)
-
(SWE.4.BP5 Establish bidirectional traceability - SWE.4.O.4 Consistency and bidirectional traceability are established between software units, criteria for verification and verification results)
-
(02-00 Contract - ACQ.12.O.2 An agreement, (contractual) terms and conditions are defined todescribe how the supplier will meet the needs and expectations)
-
(17-00 Requirement specification - ACQ.13.O.5 Requirements for the completion and acceptance of interim workproducts and release of payments are established)
-
(07-04 Process measure - MAN.6.O.7 The measurement process and measures are evaluated andcommunicated to the process owner)
-
(SPL.2.BP2 Define release products - SPL.2.O.1 The contents of the product release are determined)
-
(13-15 Proposal review record - SPL.1.O.3 The need to undertake preliminary surveys or feasibility studies isdetermined)
-
(13-04 Communication Record - SYS.1.O.4 A mechanism is established for continuous monitoring of stakeholderneeds)
-
(ACQ.13.BP3 Define organizational requirements - ACQ.13.O.2 Requirements for the organizational, management, controlling, andreporting aspects of a project are defined)
-
(13-19 Review Record - SUP.10.O.7 Approved changes are implemented and tracked to closure)
-
(13-16 Change Request - SUP.10.O.7 Approved changes are implemented and tracked to closure)
-
(SUP.7.BP5 Develop documentation - SUP.7.O.4 The content and purpose of all documentation is specified, reviewed and approved)
-
(14-02 Corrective Action Register - SUP.4.O.3 Review results are made known to all affected parties)
-
(REU.2.BP5 Evaluate reuse proposals - REU.2.O.5 Reuse proposals are evaluated to ensure the reuse product is suitablefor the proposed application)
-
(13-05 Contract review record - SUP.4.O.2 The status and products of an activity of a process are evaluated through joint review activities between the stakeholders)
-
(08-19 Risk management plan - MAN.5.O.3 Risks are identified as they develop during the conduct of the project)
-
(ACQ.13.BP1 Identify relevant groups - ACQ.13.O.1 Consistency between financial, technical, contractual and projectrequirements is established)
-
(13-05 Contract review record - SUP.4.O.1 Management and technical reviews are held based on the needs ofthe project)
-
(SPL.1.BP7 Prepare supplier proposal response - SPL.1.O.5 A supplier proposal is prepared in response to the customer request;and)
-
(11-04 Product release package - SPL.2.O.6 The product release is made available to the intended customer)
-
(MAN.3.BP4 Define, monitor and adjust project activities - MAN.3.O.5 Plans for the execution of the project are developed, implemented andmaintained)
-
(13-07 Problem record - SUP.4.O.5 Problems are identified and recorded)
-
(08-19 Risk management plan - MAN.5.O.5 Risk measures are defined, applied, and assessed to determinechanges in the status of risk and the progress of the treatment activities)
-
(03-03 Benchmarking data - MAN.6.O.5 The required data is collected, stored, analyzed, and the resultsinterpreted)
-
(07-06 Quality measure - MAN.6.O.4 Measurement activities are identified and performed)
-
(ACQ.11.BP6 Communicate to affected groups - ACQ.11.O.3 The requirements and potential solutions are communicated to allaffected groups)
-
(SYS.3.BP8 Communicate agreed system architectural design - SYS.3.O.6 The system architectural design is agreed and communicated to allaffected parties)
-
(11-04 Product release package - SPL.2.O.2 The release is assembled from configured items)
-
(02-01 Commitment/agreement - ACQ.12.O.7 Recognized criteria for proprietary, regulatory and other productliabilities issues are established)
-
(MAN.5.BP1 Establish risk management scope - MAN.5.O.1 The scope of the risk management to be performed is determined)
-
(15-01 Analysis report - SYS.1.O.6 Changes arising from changing technology and stakeholder needs areidentified, the associated risks assessed and their impact managed)
-
(SWE.5.BP6 Perform software integration test - SWE.5.O.6 Integrated software items are tested using the selected test cases and the results of software integration test are recorded)
-
(13-19 Review Record - SWE.4.O.4 Consistency and bidirectional traceability are established between software units, criteria for verification and verification results)
-
(SWE.5.BP4 Integrate software units and software items - SWE.5.O.4 Software units and software items are integrated up to a complete integrated software according to the integration strategy)
-
(08-50 Test specification - SWE.6.O.2 A specification for software qualification test of the integrated software according to the software qualification test strategy is developed that is suitable to provide evidence for compliance with the software requirements)
-
(02-00 Contract - ACQ.13.O.7 Requirements for ownership of interactions and relationships withsuppliers are defined)
-
(SWE.6.BP1 Develop software qualification test strategy including regression test strategy - SWE.6.O.1 A software qualification test strategy including regression test strategy consistent with the project plan and release plan is developed to test the integrated software)
-
(02-01 Commitment/agreement - MAN.6.O.1 Organizational commitment is established and sustained to implementthe measurement process)
-
(15-07 Reuse evaluation report - REU.2.O.8 The reuse program is monitored and evaluated)
-
(MAN.5.BP6: Monitor risks - MAN.5.O.5 Risk measures are defined, applied, and assessed to determinechanges in the status of risk and the progress of the treatment activities)
-
(15-01 Analysis report - SYS.2.O.7 The system requirements are evaluated for cost, schedule andtechnical impact)
-
(ACQ.12.BP2 Consider relevant regulations - ACQ.12.O.2 An agreement, (contractual) terms and conditions are defined todescribe how the supplier will meet the needs and expectations)
-
(08-52 Test plan - SYS.4.O.1 A system integration strategy consistent with the project plan, therelease plan and the system architectural design is developed tointegrate the system items)
-
(02-01 Commitment/agreement - SPL.1.O.6 Formal confirmation of agreement is obtained)
-
(07-05 Project measure - MAN.6.O.7 The measurement process and measures are evaluated andcommunicated to the process owner)
-
(MAN.5.BP5 Define risk treatment actions - MAN.5.O.6 Appropriate treatment is taken to correct or avoid the impact of riskbased on its priority, probability, and consequence or other definedrisk threshold)
-
(08-50 Test specification - SWE.5.O.5 Test cases included in the software integration test specification are selected according to the software integration test strategy, and the release plan)
-
(13-19 Review Record - SYS.3.O.5 Consistency and bidirectional traceability are established between system requirements and system architectural design)
-
(07-07 Risk measure - MAN.5.O.5 Risk measures are defined, applied, and assessed to determinechanges in the status of risk and the progress of the treatment activities)
-
(SUP.10.BP6 Review the implementation of change requests - SUP.10.O.8 The status of all change requests is known)
-
(SUP.2.BP4 Determine and track actions for verification results - SUP.2.O.4 Defects are identified, recorded and tracked)
-
(02-01 Commitment/agreement - ACQ.14.O.3 The agreement (contractual) terms of reference and conditions for CFP / ITT are established)
-
(13-19 Review Record - SWE.6.O.5 Consistency and bidirectional traceability are established between software requirements and software qualification test specification including test cases and between test cases and test results)
-
(13-50 Test result - SWE.4.O.3 Software units are verified according to the software unit verification strategy and the defined criteria for software unit verification and the results are recorded)
-
(13-50 Test result - SWE.5.O.8 Results of the software integration test are summarized and communicated to all affected parties)
-
(13-20 Risk action request - MAN.5.O.1 The scope of the risk management to be performed is determined)
-
(15-16 Improvement opportunity - PIM.3.O.2 Issues arising from the organization's internal/external environmentare identified as improvement opportunities and justified as reasonsfor change)
-
(SYS.1.BP5 Manage stakeholder requirements changes - SYS.1.O.6 Changes arising from changing technology and stakeholder needs areidentified, the associated risks assessed and their impact managed)
-
(02-00 Contract - ACQ.13.O.4 The needs for exchanging information between all affected parties areestablished)
-
(13-20 Risk action request - ACQ.13.O.6 Potential risks are identified)
-
(SWE.3.BP7 Communicate agreed software detailed design - SWE.3.O.5 The software detailed design and the relationship to the software architectural design is agreed and communicated to all affected parties)
-
(04-02 Domain architecture - REU.2.O.2 Each domain is assessed to determine its reuse potential)
-
(MAN.6.BP9 Communicate measures - MAN.6.O.6 Information products are used to support decisions and provide anobjective basis for communication)
-
(SUP.9.BP4 Diagnose the cause and determine the impact of the problem - SUP.9.O.2 Problems are recorded, uniquely identified and classified)
-
(SWE.2.BP9 Communicate agreed software architectural design - SWE.2.O.6 The software architectural design is agreed and communicated to allaffected parties)
-
(PIM.3.BP7 Confirm process improvement - PIM.3.O.5 The effects of process implementation are monitored, measured andconfirmed against the defined improvement goals)
-
(MAN.5.BP4 Analyze risks - MAN.5.O.4 Risks are analyzed and the priority in which to apply resources totreatment of these risks is determined)
-
(02-00 Contract - ACQ.13.O.3 Requirements for adequate staffing of projects by a competent team(e.g. resources with requisite legal, contractual, technical and projectcompetence) with clear responsibilities and goals are defined)
-
(02-00 Contract - ACQ.13.O.6 Potential risks are identified)
-
(SWE.3.BP6 Ensure consistency - SWE.3.O.4 Consistency and bidirectional traceability are established between software requirements and software units; and consistency and bidirectional traceability are established between software architectural design and software detailed design; and consistency and bidirectional traceability are established between software detailed design and software units)
-
(15-13 Assessment/audit report - SUP.4.O.2 The status and products of an activity of a process are evaluated through joint review activities between the stakeholders)
-
(17-12 System requirements specification - SYS.2.O.5 The system requirements are updated as needed)
-
(MAN.3.BP4 Define, monitor and adjust project activities - MAN.3.O.3 The activities and resources necessary to complete the work are sizedand estimated)
-
(14-02 Corrective Action Register - MAN.5.O.6 Appropriate treatment is taken to correct or avoid the impact of riskbased on its priority, probability, and consequence or other definedrisk threshold)
-
(13-50 Test result - SYS.5.O.4 The integrated system is tested using the selected test cases and the results of system qualification test are recorded)
-
(SUP.1.BP5 Ensure resolution of non-conformances - SUP.1.O.6 Management ensures that escalated non-conformances are resolved)
-
(08-52 Test plan - SYS.5.O.1 A system qualification test strategy including regression test strategy consistent with the project plan and release plan is developed to test the integrated system)
-
(SWE.2.BP6 Evaluate alternative software architectures - SWE.2.O.1 A software architectural design is defined that identifies the elementsof the software)
-
(SUP.1.BP1 Develop a project quality assurance strategy - SUP.1.O.2 Quality assurance is performed independently and objectively without conflicts of interest)
-
(MAN.6.BP6 Retrieve measurement data - MAN.6.O.5 The required data is collected, stored, analyzed, and the resultsinterpreted)
-
(13-04 Communication Record - SPL.1.O.1 A communication interface is established and maintained in order torespond to customer inquiries and requests for proposal)
-
(02-00 Contract - ACQ.12.O.5 Warranties and service level agreements are provided for whereapplicable)
-
(14-02 Corrective Action Register - SUP.1.O.3 Non-conformances of work products, processes, and process activities with relevant requirements are identified, recorded, communicated to the relevant parties, tracked, resolved, and further prevented)
-
(15-01 Analysis report - ACQ.4.O.3 Performance of the supplier is monitored against the agreements)
-
(SPL.1.BP8 Establish confirmation of agreement - SPL.1.O.6 Formal confirmation of agreement is obtained)
-
(SUP.2.BP5 Report verification results - SUP.2.O.5 Results of the verification activities are made available to the customer and other involved parties)
-
(14-02 Corrective Action Register - SUP.1.O.5 Authority to escalate non-conformances to appropriate levels of management is established)
-
(ACQ.14.BP5 Define project terms - ACQ.14.O.5 The project terms of reference for CFP / ITT are defined)
-
(SYS.4.BP5 Select test cases - SYS.4.O.5 Test cases included in the system integration test specification are selected according to the system integration test strategy and the release plan)
-
(PIM.3.BP1 Establish commitment - PIM.3.O.1 Commitment is established to provide resources to sustainimprovement actions)
-
(SUP.9.BP8 Track problems to closure - SUP.9.O.5 Problems are tracked to closure)
-
(ACQ.15.BP1 Establish qualification criteria - ACQ.15.O.1 Criteria are established for qualifying suppliers)
-
(SPL.2.BP4 Define the build activities and build environment - SPL.2.O.2 The release is assembled from configured items)
-
(01-03 Software item - SWE.5.O.4 Software units and software items are integrated up to a complete integrated software according to the integration strategy)
-
(SPL.1.BP2 Perform customer inquiry screening - SPL.1.O.1 A communication interface is established and maintained in order torespond to customer inquiries and requests for proposal)
-
(07-06 Quality measure - MAN.6.O.7 The measurement process and measures are evaluated andcommunicated to the process owner)
-
(08-19 Risk management plan - MAN.5.O.1 The scope of the risk management to be performed is determined)
-
(SUP.10.BP4 Analyze and assess change requests - SUP.10.O.5 Requests for change are analyzed, and resource requirements are estimated)
-
(15-05 Evaluation report - MAN.6.O.7 The measurement process and measures are evaluated andcommunicated to the process owner)
-
(SPL.2.BP13 Deliver the release to the intended customer - SPL.2.O.7 Confirmation of release is obtained)
-
(SUP.9.BP9 Analyze problem trends - SUP.9.O.6 The status of problems and their trend are known)
-
(SUP.8.BP9 Manage the storage of configuration items and baselines - SUP.8.O.5 The status of the configuration items and modifications is recorded and reported)
-
(08-29 Improvement plan - PIM.3.O.4 Improvement goals are identified and prioritized, and consequentchanges to the process are defined, planned and implemented)
-
(SUP.1.BP2 Assure quality of work products - SUP.1.O.3 Non-conformances of work products, processes, and process activities with relevant requirements are identified, recorded, communicated to the relevant parties, tracked, resolved, and further prevented)
-
(13-07 Problem record - SUP.2.O.4 Defects are identified, recorded and tracked)
-
(02-00 Contract - ACQ.13.O.5 Requirements for the completion and acceptance of interim workproducts and release of payments are established)
-
(08-26 Documentation plan - SUP.7.O.1 A strategy identifying the documentation to be produced during the lifecycle of the product or service is developed)
-
(MAN.3.BP5 Define, monitor and adjust project estimates andresources - MAN.3.O.3 The activities and resources necessary to complete the work are sizedand estimated)
-
(15-01 Analysis report - SUP.9.O.3 Problems are analyzed and assessed to identify an appropriate solution)
-
(MAN.3.BP6 Ensure required skills, knowledge, and experience - MAN.3.O.3 The activities and resources necessary to complete the work are sizedand estimated)
-
(08-52 Test plan - SWE.5.O.2 A software integration test strategy including the regression test strategy is developed to test the software unit and software item interactions)
-
(ACQ.13.BP9 Establish criteria for interim work products - ACQ.13.O.5 Requirements for the completion and acceptance of interim workproducts and release of payments are established)
-
(13-21 Change control record - ACQ.11.O.2 The current and evolving acquisition needs are gathered and defined)
-
(13-04 Communication Record - SWE.2.O.6 The software architectural design is agreed and communicated to allaffected parties)
-
(17-03 Customer requirements - SYS.1.O.2 Agreed stakeholder requirements are defined and baselined)
-
(15-05 Evaluation report - PIM.3.O.2 Issues arising from the organization's internal/external environmentare identified as improvement opportunities and justified as reasonsfor change)
-
(PIM.3.BP5 Plan process changes - PIM.3.O.4 Improvement goals are identified and prioritized, and consequentchanges to the process are defined, planned and implemented)
-
(SUP.7.BP8 Maintain documentation - SUP.7.O.6 Documentation is maintained in accordance with defined criteria)
-
(SYS.2.BP4 Analyze the impact on the operating environment - SYS.2.O.3 The impact of system requirements on the operating environment isanalyzed)
-
(SUP.1.BP6 Implement an escalation mechanism - SUP.1.O.5 Authority to escalate non-conformances to appropriate levels of management is established)
-
(SYS.3.BP7 Ensure consistency - SYS.3.O.5 Consistency and bidirectional traceability are established between system requirements and system architectural design)
-
(15-07 Reuse evaluation report - REU.2.O.5 Reuse proposals are evaluated to ensure the reuse product is suitablefor the proposed application)
-
(SUP.8.BP5 Control modifications and releases - SUP.8.O.4 Modifications and releases are made available to affected parties)
-
(SWE.3.BP4 Evaluate software detailed design - SWE.3.O.1 A detailed design is developed that describes software units)
-
(15-01 Analysis report - SYS.2.O.4 Prioritization for implementing the system requirements is defined)
-
(ACQ.4.BP3 Review technical development with the supplier - ACQ.4.O.1 Joint activities, as agreed between the customer and the supplier, areperformed as needed)
-
(SUP.8.BP3 Establish a configuration management system - SUP.8.O.7 Storage of the configuration items is controlled)
-
(ACQ.11.BP8 Track impact of changing technology - ACQ.11.O.5 A mechanism for identifying and managing the impact of changingtechnology to the technical requirements is defined)
-
(03-06 Process performance data - MAN.6.O.6 Information products are used to support decisions and provide anobjective basis for communication)
-
(14-01 Change history - ACQ.11.O.2 The current and evolving acquisition needs are gathered and defined)
-
(08-13 Quality plan - SUP.1.O.2 Quality assurance is performed independently and objectively without conflicts of interest)
-
(14-11 Work product list - SUP.7.O.3 Documentation to be produced by the process or project is identified)
-
(SUP.10.BP7 Track change requests to closure - SUP.10.O.7 Approved changes are implemented and tracked to closure)
-
(SYS.2.BP5 Develop verification criteria - SYS.2.O.7 The system requirements are evaluated for cost, schedule andtechnical impact)
-
(MAN.6.BP3 Identify measurement information needs - MAN.6.O.2 The measurement information needs of organizational andmanagement processes are identified)
-
(11-07 Temporary solution - SPL.2.O.6 The product release is made available to the intended customer)
-
(ACQ.15.BP2 Evaluate supplier - ACQ.15.O.2 Supplier capability determination is performed as necessary)
-
(15-01 Analysis report - SWE.4.O.3 Software units are verified according to the software unit verification strategy and the defined criteria for software unit verification and the results are recorded)
-
(14-08 Tracking system - SUP.4.O.3 Review results are made known to all affected parties)
-
(ACQ.14.BP2 Assemble requirements - ACQ.14.O.2 The baseline technical and non-technical requirements are assembled to accompany the CFP / ITT)
-
(SYS.4.BP4 Integrate system items - SYS.4.O.4 System items are integrated up to a complete integrated system according to the integration strategy)
-
(SPL.2.BP13 Deliver the release to the intended customer - SPL.2.O.6 The product release is made available to the intended customer)
-
(13-07 Problem record - SUP.4.O.3 Review results are made known to all affected parties)
-
(13-25 Verification results - SWE.4.O.5 Results of the unit verification are summarized and communicated toall affected parties)
-
(14-01 Change history - SUP.7.O.5 Documentation is developed and made available in accordance with identified standards)
-
(ACQ.4.BP2 Exchange all agreed information - ACQ.4.O.1 Joint activities, as agreed between the customer and the supplier, areperformed as needed)
-
(SYS.2.BP1 Specify system requirements - SYS.2.O.1 A defined set of system requirements is established)
-
(17-00 Requirement specification - ACQ.12.O.4 The rights of the acquirer to assume, modify or evaluate, directly orindirectly Intellectual Property Rights are established)
-
(17-02 Build list - SWE.5.O.7 Consistency and bidirectional traceability are established between the elements of the software architectural design and the test cases included in the software integration test specification and between test cases and test results)
-
(SYS.5.BP1 Develop system qualification test strategy including regression test strategy - SYS.5.O.1 A system qualification test strategy including regression test strategy consistent with the project plan and release plan is developed to test the integrated system)
-
(13-19 Review Record - SWE.3.O.4 Consistency and bidirectional traceability are established between software requirements and software units; and consistency and bidirectional traceability are established between software architectural design and software detailed design; and consistency and bidirectional traceability are established between software detailed design and software units)
-
(15-01 Analysis report - SWE.1.O.2 Software requirements are categorized and analyzed for correctness and verifiability)
-
(13-04 Communication Record - SYS.3.O.6 The system architectural design is agreed and communicated to allaffected parties)
-
(07-08 Service level measure - MAN.6.O.7 The measurement process and measures are evaluated andcommunicated to the process owner)
-
(SYS.2.BP1 Specify system requirements - SYS.2.O.7 The system requirements are evaluated for cost, schedule andtechnical impact)
-
(15-07 Reuse evaluation report - REU.2.O.6 Reuse is implemented according to the reuse strategy)
-
(MAN.5.BP2 Define risk management strategies - MAN.5.O.2 Appropriate risk management strategies are defined andimplemented)
-
(08-19 Risk management plan - MAN.5.O.6 Appropriate treatment is taken to correct or avoid the impact of riskbased on its priority, probability, and consequence or other definedrisk threshold)
-
(13-22 Traceability record - SWE.2.O.5 Consistency and bidirectional traceability are established betweensoftware requirements and software architectural design)
-
(17-00 Requirement specification - ACQ.13.O.4 The needs for exchanging information between all affected parties areestablished)
-
(15-06 Project Status Report - MAN.3.O.4 Interfaces within the project, and with other projects and organizational units, are identified and monitored)
-
(SYS.2.BP4 Analyze the impact on the operating environment - SYS.2.O.7 The system requirements are evaluated for cost, schedule andtechnical impact)
-
(MAN.3.BP7 Identify, monitor and adjust project interfaces and agreed commitments - MAN.3.O.7 Corrective action is taken when project goals are not achieved, andrecurrence of problems identified in the project is prevented.)
-
(13-19 Review Record - SUP.1.O.2 Quality assurance is performed independently and objectively without conflicts of interest)
-
(13-16 Change Request - PIM.3.O.2 Issues arising from the organization's internal/external environmentare identified as improvement opportunities and justified as reasonsfor change)
-
(SUP.1.BP3 Assure quality of process activities - SUP.1.O.4 Conformance of work products, processes and activities with relevant requirements is verified, documented, and communicated to the relevant parties)
-
(MAN.3.BP3 Evaluate feasibility of the project - MAN.3.O.1 The scope of the work for the project is defined)
-
(13-04 Communication Record - SWE.5.O.8 Results of the software integration test are summarized and communicated to all affected parties)
-
(02-01 Commitment/agreement - ACQ.12.O.2 An agreement, (contractual) terms and conditions are defined todescribe how the supplier will meet the needs and expectations)
-
(16-03 Configuration management system - SUP.8.O.3 Modifications and releases of the configuration items are controlled)
-
(SUP.8.BP6 Establish baselines - SUP.8.O.2 All configuration items generated by a process or project are identified, defined and baselined according to the configuration management strategy)
-
(ACQ.11.BP5 Identify affected groups - ACQ.11.O.3 The requirements and potential solutions are communicated to allaffected groups)
-
(13-04 Communication Record - REU.2.O.7 Feedback, communication, and notification mechanisms areestablished, that operate between affected parties)
-
(08-19 Risk management plan - MAN.5.O.2 Appropriate risk management strategies are defined andimplemented)
-
(17-00 Requirement specification - ACQ.12.O.6 Provision for the suppliers to deliver other requirements (e.g. qualityplan, escrow arrangements etc.) is defined)
-
(ACQ.12.BP3 Agree on (contractual) terms and conditions - ACQ.12.O.2 An agreement, (contractual) terms and conditions are defined todescribe how the supplier will meet the needs and expectations)
-
(13-22 Traceability record - SWE.1.O.1 The software requirements to be allocated to the software elements ofthe system and their interfaces are defined)
-
(13-19 Review Record - MAN.3.O.7 Corrective action is taken when project goals are not achieved, andrecurrence of problems identified in the project is prevented.)
-
(PIM.3.BP4 Prioritize improvements - PIM.3.O.4 Improvement goals are identified and prioritized, and consequentchanges to the process are defined, planned and implemented)
-
(13-04 Communication Record - SUP.1.O.3 Non-conformances of work products, processes, and process activities with relevant requirements are identified, recorded, communicated to the relevant parties, tracked, resolved, and further prevented)
-
(11-03 Product release information - SPL.2.O.6 The product release is made available to the intended customer)
-
(SWE.1.BP7 Ensure consistency - SWE.1.O.6 Consistency and bidirectional traceability are established between system requirements and software requirements; and consistency and bidirectional traceability are established between system architectural design and software requirements)
-
(02-01 Commitment/agreement - ACQ.4.O.4 Changes to the agreement, if needed, are negotiated between thecustomer and the supplier and documented in the agreement)
-
(SWE.1.BP4 Analyze the impact on the operating environment - SWE.1.O.3 The impact of software requirements on the operating environment is analyzed)
-
(15-18 Process performance report - MAN.6.O.5 The required data is collected, stored, analyzed, and the resultsinterpreted)
-
(MAN.3.BP9 Ensure consistency - MAN.3.O.7 Corrective action is taken when project goals are not achieved, andrecurrence of problems identified in the project is prevented.)
-
(09-03 Reuse policy - REU.2.O.1 The reuse strategy, including its purpose, scope, goals and objectives, is defined)
-
(SYS.1.BP6 Establish customer-supplier query communication mechanism - SYS.1.O.5 A mechanism is established for ensuring that customers can easilydetermine the status and disposition of their requests)
-
(04-06 System architectural design - SYS.3.O.3 The interfaces of each system element are defined)
-
(13-19 Review Record - SUP.4.O.1 Management and technical reviews are held based on the needs ofthe project)
-
(SUP.8.BP3 Establish a configuration management system - SUP.8.O.2 All configuration items generated by a process or project are identified, defined and baselined according to the configuration management strategy)
-
(08-17 Reuse plan - REU.2.O.6 Reuse is implemented according to the reuse strategy)
-
(13-07 Problem record - SUP.9.O.4 Problem resolution is initiated)
-
(17-00 Requirement specification - ACQ.13.O.7 Requirements for ownership of interactions and relationships withsuppliers are defined)
-
(SPL.1.BP1 Establish communication interface - SPL.1.O.1 A communication interface is established and maintained in order torespond to customer inquiries and requests for proposal)
-
(SYS.4.BP1 Develop system integration strategy - SYS.4.O.1 A system integration strategy consistent with the project plan, therelease plan and the system architectural design is developed tointegrate the system items)
-
(13-19 Review Record - SYS.4.O.7 Consistency and bidirectional traceability between the elements of the system architectural design and test cases included in the system integration test specification and bidirectional traceability between testcases and test results is established)
-
(16-03 Configuration management system - SUP.8.O.4 Modifications and releases are made available to affected parties)
-
(17-00 Requirement specification - ACQ.14.O.6 The technical terms of reference for CFP / ITT are defined)
-
(17-00 Requirement specification - ACQ.12.O.5 Warranties and service level agreements are provided for whereapplicable)
-
(15-18 Process performance report - MAN.6.O.7 The measurement process and measures are evaluated andcommunicated to the process owner)
-
(REU.2.BP8 Monitor reuse - REU.2.O.8 The reuse program is monitored and evaluated)
-
(SUP.1.BP5 Ensure resolution of non-conformances - SUP.1.O.3 Non-conformances of work products, processes, and process activities with relevant requirements are identified, recorded, communicated to the relevant parties, tracked, resolved, and further prevented)
-
(07-04 Process measure - PIM.3.O.6 Knowledge gained from the improvement is communicated within theorganization)
-
(13-22 Traceability record - SWE.3.O.4 Consistency and bidirectional traceability are established between software requirements and software units; and consistency and bidirectional traceability are established between software architectural design and software detailed design; and consistency and bidirectional traceability are established between software detailed design and software units)
-
(ACQ.15.BP5 Perform corrective actions - ACQ.15.O.5 Any corrective action required by the acquirer is evaluated andperformed)
-
(02-01 Commitment/agreement - ACQ.3.O.1 A contract/agreement is negotiated, reviewed, approved and awardedto the supplier(s))
-
(14-06 Schedule - MAN.3.O.3 The activities and resources necessary to complete the work are sizedand estimated)
-
(02-00 Contract - ACQ.12.O.6 Provision for the suppliers to deliver other requirements (e.g. qualityplan, escrow arrangements etc.) is defined)
-
(13-08 Baseline - SUP.8.O.2 All configuration items generated by a process or project are identified, defined and baselined according to the configuration management strategy)
-
(MAN.6.BP11 Communicate potential improvements - MAN.6.O.7 The measurement process and measures are evaluated andcommunicated to the process owner)
-
(14-02 Corrective Action Register - SUP.4.O.4 Action items resulting from reviews are tracked to closure)
-
(SUP.8.BP5 Control modifications and releases - SUP.8.O.3 Modifications and releases of the configuration items are controlled)
-
(07-08 Service level measure - MAN.6.O.4 Measurement activities are identified and performed)
-
(13-04 Communication Record - ACQ.11.O.3 The requirements and potential solutions are communicated to allaffected groups)
-
(13-04 Communication Record - SYS.1.O.1 Continuing communication with the stakeholder is established)
-
(17-00 Requirement specification - ACQ.12.O.1 A contractual approach is defined which is compliant with relevantnational, international and regulatory laws, guidance and policies)
-
(ACQ.4.BP1 Agree on and maintain joint processes - ACQ.4.O.1 Joint activities, as agreed between the customer and the supplier, areperformed as needed)
-
(08-28 Change management plan - SUP.10.O.1 A change request management strategy is developed)
-
(15-01 Analysis report - SYS.1.O.2 Agreed stakeholder requirements are defined and baselined)
-
(13-22 Traceability record - SYS.3.O.5 Consistency and bidirectional traceability are established between system requirements and system architectural design)
-
(18-06 Product release criteria - SPL.2.O.7 Confirmation of release is obtained)
-
(13-01 Acceptance record - SUP.7.O.4 The content and purpose of all documentation is specified, reviewed and approved)
-
(13-07 Problem record - SUP.2.O.5 Results of the verification activities are made available to the customer and other involved parties)
-
(13-05 Contract review record - SUP.4.O.3 Review results are made known to all affected parties)
-
(SUP.9.BP3 Record the status of problems - SUP.9.O.6 The status of problems and their trend are known)
-
(08-20 Risk mitigation plan - SYS.1.O.6 Changes arising from changing technology and stakeholder needs areidentified, the associated risks assessed and their impact managed)
-
(MAN.3.BP5 Define, monitor and adjust project estimates andresources - MAN.3.O.2 The feasibility of achieving the goals of the project with available resources and constraints is evaluated)
-
(13-19 Review Record - SWE.5.O.7 Consistency and bidirectional traceability are established between the elements of the software architectural design and the test cases included in the software integration test specification and between test cases and test results)
-
(ACQ.13.BP6 Define responsibilities and goals - ACQ.13.O.3 Requirements for adequate staffing of projects by a competent team(e.g. resources with requisite legal, contractual, technical and projectcompetence) with clear responsibilities and goals are defined)
-
(SUP.8.BP8 Verify the information about configured items - SUP.8.O.6 The completeness and consistency of the baselines is ensured)
-
(08-50 Test specification - SWE.4.O.2 Criteria for software unit verification are developed according to the software unit verification strategy that are suitable to provide evidence for compliance of the software units with the software detailed design and with the non-functional software requirements)
-
(13-17 Customer request - ACQ.11.O.1 The technical requirements, including environment effect evaluation,safety and security requirements where appropriate, are defined anddeveloped to match needs and expectations)
-
(SWE.4.BP3 Perform static verification of software units - SWE.4.O.3 Software units are verified according to the software unit verification strategy and the defined criteria for software unit verification and the results are recorded)
-
(07-04 Process measure - MAN.6.O.4 Measurement activities are identified and performed)
-
(13-22 Traceability record - SWE.6.O.5 Consistency and bidirectional traceability are established between software requirements and software qualification test specification including test cases and between test cases and test results)
-
(08-13 Quality plan - SUP.1.O.1 A strategy for performing quality assurance is developed, implemented, and maintained)
-
(MAN.3.BP9 Ensure consistency - MAN.3.O.3 The activities and resources necessary to complete the work are sizedand estimated)
-
(13-25 Verification results - SUP.2.O.4 Defects are identified, recorded and tracked)
-
(MAN.6.BP9 Communicate measures - MAN.6.O.5 The required data is collected, stored, analyzed, and the resultsinterpreted)
-
(13-22 Traceability record - SWE.1.O.6 Consistency and bidirectional traceability are established between system requirements and software requirements; and consistency and bidirectional traceability are established between system architectural design and software requirements)
-
(08-26 Documentation plan - SUP.7.O.2 The standards to be applied for the development of the documentation are identified)
-
(17-03 Customer requirements - ACQ.11.O.6 The requirements include compliance with relevant standards,including environment effect evaluation, safety and security standardswhere appropriate)
-
(ACQ.13.BP14 Define rights for use and distribution - ACQ.13.O.8 Rights for use and distribution of the product by the customer andsupplier are defined)
-
(SWE.3.BP4 Evaluate software detailed design - SWE.3.O.2 Interfaces of each software unit are defined)
-
(SUP.10.BP5 Approve change requests before implementation - SUP.10.O.6 Changes are approved and prioritized on the basis of analysis resultsand availability of resources)
-
(13-19 Review Record - SWE.4.O.3 Software units are verified according to the software unit verification strategy and the defined criteria for software unit verification and the results are recorded)
-
(13-08 Baseline - SUP.8.O.3 Modifications and releases of the configuration items are controlled)
-
(SWE.1.BP2 Structure software requirements - SWE.1.O.4 Prioritization for implementing the software requirements is defined)
-
(ACQ.13.BP7 Identify information needs - ACQ.13.O.4 The needs for exchanging information between all affected parties areestablished)
-
(SYS.2.BP2 Structure system requirements - SYS.2.O.4 Prioritization for implementing the system requirements is defined)
-
(13-16 Change Request - MAN.3.O.7 Corrective action is taken when project goals are not achieved, andrecurrence of problems identified in the project is prevented.)
-
(SWE.5.BP9 Summarize and communicate results - SWE.5.O.8 Results of the software integration test are summarized and communicated to all affected parties)
-
(04-04 Software architectural design - SWE.2.O.2 The software requirements are allocated to the elements of thesoftware)
-
(SPL.2.BP7 Determine the delivery media type for the release - SPL.2.O.4 The release delivery mechanism and media are determined)
-
(13-04 Communication Record - ACQ.4.O.1 Joint activities, as agreed between the customer and the supplier, areperformed as needed)
-
(15-16 Improvement opportunity - SUP.4.O.3 Review results are made known to all affected parties)
-
(07-01 Customer satisfaction survey - MAN.6.O.7 The measurement process and measures are evaluated andcommunicated to the process owner)
-
(MAN.3.BP10 Review and report progress of the project - MAN.3.O.7 Corrective action is taken when project goals are not achieved, andrecurrence of problems identified in the project is prevented.)
-
(15-13 Assessment/audit report - PIM.3.O.5 The effects of process implementation are monitored, measured andconfirmed against the defined improvement goals)
-
(15-21 Supplier evaluation report - ACQ.15.O.2 Supplier capability determination is performed as necessary)
-
(MAN.3.BP6 Ensure required skills, knowledge, and experience - MAN.3.O.7 Corrective action is taken when project goals are not achieved, andrecurrence of problems identified in the project is prevented.)
-
(SPL.2.BP3 Establish a product release classification and numbering scheme - SPL.2.O.2 The release is assembled from configured items)
-
(15-01 Analysis report - MAN.6.O.2 The measurement information needs of organizational andmanagement processes are identified)
-
(11-03 Product release information - SPL.2.O.1 The contents of the product release are determined)
-
(13-08 Baseline - SUP.8.O.4 Modifications and releases are made available to affected parties)
-
(SWE.3.BP8 Develop software units - SWE.3.O.6 Software units defined by the software detailed design are produced)
-
(SWE.2.BP8 Ensure consistency - SWE.2.O.6 The software architectural design is agreed and communicated to allaffected parties)
-
(ACQ.12.BP1 Identify relevant regulations - ACQ.12.O.1 A contractual approach is defined which is compliant with relevantnational, international and regulatory laws, guidance and policies)
-
(ACQ.4.BP4: Review progress of the supplier - ACQ.4.O.1 Joint activities, as agreed between the customer and the supplier, areperformed as needed)
-
(SWE.2.BP8 Ensure consistency - SWE.2.O.2 The software requirements are allocated to the elements of thesoftware)
-
(17-00 Requirement specification - ACQ.14.O.5 The project terms of reference for CFP / ITT are defined)
-
(04-04 Software architectural design - SWE.2.O.1 A software architectural design is defined that identifies the elementsof the software)
-
(18-07 Quality criteria - SUP.2.O.2 Criteria for verification of all required work products are identified)
-
(14-08 Tracking system - MAN.5.O.6 Appropriate treatment is taken to correct or avoid the impact of riskbased on its priority, probability, and consequence or other definedrisk threshold)
-
(06-04 Training material - PIM.3.O.6 Knowledge gained from the improvement is communicated within theorganization)
-
(13-15 Proposal review record - SPL.1.O.4 Suitable staff are identified to perform the proposed work)
-
(17-00 Requirement specification - ACQ.11.O.6 The requirements include compliance with relevant standards,including environment effect evaluation, safety and security standardswhere appropriate)
-
(SUP.2.BP3 Conduct verification - SUP.2.O.3 Required verification activities are performed)
-
(07-05 Project measure - MAN.6.O.3 An appropriate set of measures, driven by the information needs areidentified and/or developed)
-
(SWE.5.BP7 Establish bidirectional traceability - SWE.5.O.7 Consistency and bidirectional traceability are established between the elements of the software architectural design and the test cases included in the software integration test specification and between test cases and test results)
-
(13-50 Test result - SYS.4.O.8 Results of the system integration test are summarized andcommunicated to all affected parties)
-
(13-13 Product release approval record - SPL.2.O.5 Release approval is effected against defined criteria)
-
(MAN.3.BP8 Define, monitor and adjust project schedule - MAN.3.O.5 Plans for the execution of the project are developed, implemented andmaintained)
-
(14-02 Corrective Action Register - SUP.2.O.4 Defects are identified, recorded and tracked)
-
(13-19 Review Record - ACQ.4.O.2 All information, agreed upon for exchange, is communicated regularlybetween the supplier and customer)
-
(08-16 Release plan - SPL.2.O.3 The release documentation is defined and produced)
-
(02-00 Contract - ACQ.13.O.8 Rights for use and distribution of the product by the customer andsupplier are defined)
-
(08-16 Release plan - SPL.2.O.1 The contents of the product release are determined)
-
(SWE.3.BP4 Evaluate software detailed design - SWE.3.O.4 Consistency and bidirectional traceability are established between software requirements and software units; and consistency and bidirectional traceability are established between software architectural design and software detailed design; and consistency and bidirectional traceability are established between software detailed design and software units)
-
(SWE.2.BP7 Establish bidirectional traceability - SWE.2.O.5 Consistency and bidirectional traceability are established betweensoftware requirements and software architectural design)
-
(ACQ.11.BP9 Identify constraints and standards - ACQ.11.O.6 The requirements include compliance with relevant standards,including environment effect evaluation, safety and security standardswhere appropriate)
-
(SUP.8.BP9 Manage the storage of configuration items and baselines - SUP.8.O.4 Modifications and releases are made available to affected parties)
-
(SYS.3.BP1 Develop system architectural design - SYS.3.O.1 A system architectural design is defined that identifies the elements ofthe system)
-
(17-11 Software requirements specification - SWE.1.O.1 The software requirements to be allocated to the software elements ofthe system and their interfaces are defined)
-
(SWE.6.BP4 Test integrated software - SWE.6.O.4 The integrated software is tested using the selected test cases and the results of software qualification test are recorded)
-
(13-18 Quality record - SUP.1.O.2 Quality assurance is performed independently and objectively without conflicts of interest)
-
(15-12 Problem status report - SUP.9.O.6 The status of problems and their trend are known)
-
(02-00 Contract - ACQ.13.O.1 Consistency between financial, technical, contractual and projectrequirements is established)
-
(14-08 Tracking system - SUP.4.O.4 Action items resulting from reviews are tracked to closure)
-
(SYS.2.BP1 Specify system requirements - SYS.2.O.5 The system requirements are updated as needed)
-
(SWE.4.BP7 Summarize and communicate results - SWE.4.O.5 Results of the unit verification are summarized and communicated toall affected parties)
-
(SUP.4.BP2 Establish a mechanism to handle review outcomes - SUP.4.O.3 Review results are made known to all affected parties)
-
(MAN.3.BP10 Review and report progress of the project - MAN.3.O.6 Progress of the project is monitored and reported)
-
(SUP.8.BP5 Control modifications and releases - SUP.8.O.5 The status of the configuration items and modifications is recorded and reported)
-
(15-01 Analysis report - SWE.1.O.7 The software requirements are evaluated for cost, schedule andtechnical impact)
-
(SYS.3.BP7 Ensure consistency - SYS.3.O.1 A system architectural design is defined that identifies the elements ofthe system)
-
(08-28 Change management plan - ACQ.11.O.4 A mechanism is established to incorporate changed or newrequirements into the established baseline)
-
(ACQ.3.BP7 Communicate result to tenderers - ACQ.3.O.4 Proposers/tenderers are notified of the result of proposal/tenderselection)
-
(SUP.10.BP4 Analyze and assess change requests - SUP.10.O.4 Criteria for confirming implementation of change requests are defined)
-
(13-22 Traceability record - SYS.5.O.5 Consistency and bidirectional traceability are established between system requirements and test cases included in the system qualification test specification and between test cases and test results)
-
(15-13 Assessment/audit report - REU.2.O.3 The domains in which to investigate reuse opportunities, or in which itis intended to practice reuse, are identified)
-
(ACQ.4.BP4: Review progress of the supplier - ACQ.4.O.4 Changes to the agreement, if needed, are negotiated between thecustomer and the supplier and documented in the agreement)
-
(13-10 Configuration management record - SUP.8.O.7 Storage of the configuration items is controlled)
-
(SYS.1.BP4 Establish stakeholder requirements baseline - SYS.1.O.2 Agreed stakeholder requirements are defined and baselined)
-
(SYS.2.BP8 Communicate agreed system requirements - SYS.2.O.8 The system requirements are agreed and communicated to all affectedparties)
-
(14-50 Stakeholder Groups List - ACQ.11.O.1 The technical requirements, including environment effect evaluation,safety and security requirements where appropriate, are defined anddeveloped to match needs and expectations)
-
(SUP.4.BP4 Conduct joint reviews - SUP.4.O.2 The status and products of an activity of a process are evaluated through joint review activities between the stakeholders)
-
(SUP.4.BP8 Identify and record problems - SUP.4.O.5 Problems are identified and recorded)
-
(SUP.9.BP2 Identify and record the problem - SUP.9.O.2 Problems are recorded, uniquely identified and classified)
-
(08-04 Configuration management plan - SUP.8.O.1 A configuration management strategy is developed)
-
(SYS.4.BP6 Perform system integration test - SYS.4.O.6 System item interactions are tested using the selected test cases andthe results of system integration testing are recorded)
-
(07-04 Process measure - MAN.6.O.3 An appropriate set of measures, driven by the information needs areidentified and/or developed)
-
(PIM.3.BP3 Establish process improvement goals - PIM.3.O.3 Analysis of the current status of the existing process is performed,focusing on those processes from which improvement stimuli arise)
-
(SWE.1.BP5 Develop verification criteria - SWE.1.O.7 The software requirements are evaluated for cost, schedule andtechnical impact)
-
(SYS.3.BP7 Ensure consistency - SYS.3.O.2 The system requirements are allocated to the elements of the system)
-
(ACQ.3.BP5: Approve contract/agreement - ACQ.3.O.1 A contract/agreement is negotiated, reviewed, approved and awardedto the supplier(s))
-
(10-00 Process description - PIM.3.O.4 Improvement goals are identified and prioritized, and consequentchanges to the process are defined, planned and implemented)
-
(ACQ.4.BP3 Review technical development with the supplier - ACQ.4.O.4 Changes to the agreement, if needed, are negotiated between thecustomer and the supplier and documented in the agreement)
-
(SYS.4.BP7 Establish bidirectional traceability - SYS.4.O.7 Consistency and bidirectional traceability between the elements of the system architectural design and test cases included in the system integration test specification and bidirectional traceability between testcases and test results is established)
-
(ACQ.11.BP3 Identify acquisition needs - ACQ.11.O.2 The current and evolving acquisition needs are gathered and defined)
-
(ACQ.12.BP6 Establish escalation mechanisms - ACQ.12.O.3 Acceptance criteria and mechanisms for handling of breaches to thefulfillment of contract are established)
-
(15-16 Improvement opportunity - PIM.3.O.3 Analysis of the current status of the existing process is performed,focusing on those processes from which improvement stimuli arise)
-
(MAN.6.BP2 Develop measurement strategy - MAN.6.O.1 Organizational commitment is established and sustained to implementthe measurement process)
-
(13-19 Review Record - SWE.1.O.6 Consistency and bidirectional traceability are established between system requirements and software requirements; and consistency and bidirectional traceability are established between system architectural design and software requirements)
-
(04-04 Software architectural design - SWE.2.O.3 The interfaces of each software element are defined)
-
(13-04 Communication Record - SWE.6.O.6 Results of the software qualification test are summarized and communicated to all affected parties)
-
(17-00 Requirement specification - ACQ.12.O.7 Recognized criteria for proprietary, regulatory and other productliabilities issues are established)
-
(13-24 Validation results - ACQ.11.O.6 The requirements include compliance with relevant standards,including environment effect evaluation, safety and security standardswhere appropriate)
-
(SWE.4.BP6 Ensure consistency - SWE.4.O.4 Consistency and bidirectional traceability are established between software units, criteria for verification and verification results)
-
(02-01 Commitment/agreement - ACQ.12.O.4 The rights of the acquirer to assume, modify or evaluate, directly orindirectly Intellectual Property Rights are established)
-
(13-04 Communication Record - ACQ.3.O.4 Proposers/tenderers are notified of the result of proposal/tenderselection)
-
(07-05 Project measure - MAN.6.O.4 Measurement activities are identified and performed)
-
(13-25 Verification results - SUP.2.O.5 Results of the verification activities are made available to the customer and other involved parties)
-
(13-07 Problem record - SUP.9.O.5 Problems are tracked to closure)
-
(13-04 Communication Record - MAN.3.O.4 Interfaces within the project, and with other projects and organizational units, are identified and monitored)
-
(13-21 Change control record - SWE.1.O.5 The software requirements are updated as needed)
-
(SUP.8.BP3 Establish a configuration management system - SUP.8.O.6 The completeness and consistency of the baselines is ensured)
-
(13-07 Problem record - SUP.1.O.5 Authority to escalate non-conformances to appropriate levels of management is established)
-
(13-01 Acceptance record - ACQ.4.O.3 Performance of the supplier is monitored against the agreements)
-
(SWE.6.BP7 Summarize and communicate results - SWE.6.O.6 Results of the software qualification test are summarized and communicated to all affected parties)
-
(SYS.5.BP7 Summarize and communicate results - SYS.5.O.6 results of the system qualification test are summarized and communicated to all affected parties)
-
(07-06 Quality measure - MAN.6.O.3 An appropriate set of measures, driven by the information needs areidentified and/or developed)
-
(13-21 Change control record - SUP.10.O.9 Bi-directional traceability is established between change requests and affected work product)
-
(13-08 Baseline - SUP.8.O.6 The completeness and consistency of the baselines is ensured)
-
(13-19 Review Record - SYS.2.O.6 Consistency and bidirectional traceability are established between stakeholder requirements and system requirements)
-
(13-04 Communication Record - SYS.2.O.8 The system requirements are agreed and communicated to all affectedparties)
-
(ACQ.4.BP5: Act to correct deviations - ACQ.4.O.4 Changes to the agreement, if needed, are negotiated between thecustomer and the supplier and documented in the agreement)
-
(13-25 Verification results - SUP.2.O.3 Required verification activities are performed)
-
(MAN.5.BP6: Monitor risks - MAN.5.O.6 Appropriate treatment is taken to correct or avoid the impact of riskbased on its priority, probability, and consequence or other definedrisk threshold)
-
(MAN.3.BP9 Ensure consistency - MAN.3.O.5 Plans for the execution of the project are developed, implemented andmaintained)
-
(SWE.2.BP6 Evaluate alternative software architectures - SWE.2.O.4 The dynamic behavior and resource consumption objectives of thesoftware elements are defined)
-
(13-19 Review Record - SUP.7.O.4 The content and purpose of all documentation is specified, reviewed and approved)
-
(13-04 Communication Record - ACQ.4.O.2 All information, agreed upon for exchange, is communicated regularlybetween the supplier and customer)
-
(13-16 Change Request - SUP.10.O.4 Criteria for confirming implementation of change requests are defined)
-
(SUP.9.BP1 Develop a problem resolution management strategy - SUP.9.O.1 A problem resolution management strategy is developed)
-
(MAN.6.BP5 Perform measurement activities - MAN.6.O.4 Measurement activities are identified and performed)
-
(13-22 Traceability record - SWE.4.O.4 Consistency and bidirectional traceability are established between software units, criteria for verification and verification results)
-
(15-01 Analysis report - SWE.1.O.3 The impact of software requirements on the operating environment is analyzed)
-
(13-19 Review Record - SUP.1.O.4 Conformance of work products, processes and activities with relevant requirements is verified, documented, and communicated to the relevant parties)
-
(SYS.2.BP2 Structure system requirements - SYS.2.O.2 System requirements are categorized and analyzed for correctnessand verifiability)
-
(ACQ.12.BP7 Establish management of intellectual property rights - ACQ.12.O.4 The rights of the acquirer to assume, modify or evaluate, directly orindirectly Intellectual Property Rights are established)
-
(17-00 Requirement specification - ACQ.14.O.2 The baseline technical and non-technical requirements are assembled to accompany the CFP / ITT)
-
(14-02 Corrective Action Register - SUP.4.O.5 Problems are identified and recorded)
-
(14-02 Corrective Action Register - ACQ.15.O.5 Any corrective action required by the acquirer is evaluated andperformed)
-
(SYS.3.BP2 Allocate system requirements - SYS.3.O.2 The system requirements are allocated to the elements of the system)
-
(SUP.9.BP6 Raise alert notifications - SUP.9.O.4 Problem resolution is initiated)
-
(08-50 Test specification - SYS.4.O.3 A specification for system integration test according to the system integration test strategy is developed that is suitable to provide evidence for compliance of the integrated system items with the system architectural design, including the interfaces between system items)
-
(SYS.4.BP2 Develop system integration test strategy including regression test strategy - SYS.4.O.2 A system integration test strategy including the regression teststrategy is developed to test the system item interactions)
-
(13-20 Risk action request - MAN.5.O.6 Appropriate treatment is taken to correct or avoid the impact of riskbased on its priority, probability, and consequence or other definedrisk threshold)
-
(ACQ.12.BP8 Provide for warranties and service level agreements - ACQ.12.O.5 Warranties and service level agreements are provided for whereapplicable)
-
(02-00 Contract - ACQ.12.O.1 A contractual approach is defined which is compliant with relevantnational, international and regulatory laws, guidance and policies)
-
(SUP.8.BP4 Establish branch management - SUP.8.O.4 Modifications and releases are made available to affected parties)
-
(04-06 System architectural design - SYS.3.O.4 The dynamic behavior of the system elements is defined)
-
(SYS.2.BP5 Develop verification criteria - SYS.2.O.2 System requirements are categorized and analyzed for correctnessand verifiability)
-
(17-08 Interface requirements specification - SYS.2.O.3 The impact of system requirements on the operating environment isanalyzed)
-
(13-25 Verification results - SWE.4.O.3 Software units are verified according to the software unit verification strategy and the defined criteria for software unit verification and the results are recorded)
-
(13-09 Meeting support record - SUP.4.O.2 The status and products of an activity of a process are evaluated through joint review activities between the stakeholders)
-
(SUP.10.BP6 Review the implementation of change requests - SUP.10.O.7 Approved changes are implemented and tracked to closure)
-
(13-19 Review Record - SPL.1.O.2 Requests for proposal are evaluated according to defined criteria todetermine whether or not to submit a proposal)
-
(13-06 Delivery record - SPL.2.O.7 Confirmation of release is obtained)
-
(11-03 Product release information - SPL.2.O.4 The release delivery mechanism and media are determined)
-
(12-01 Request for proposal - ACQ.14.O.7 A CFP / ITT is prepared and issued in accordance with acquisition policies and which complies with relevant national, international andregulatory laws, requirements, and policies)
-
(SUP.1.BP6 Implement an escalation mechanism - SUP.1.O.6 Management ensures that escalated non-conformances are resolved)
-
(ACQ.14.BP8 Prepare and issue a CFP / ITT - ACQ.14.O.7 A CFP / ITT is prepared and issued in accordance with acquisition policies and which complies with relevant national, international andregulatory laws, requirements, and policies)
-
(ACQ.11.BP2 Define technical requirements - ACQ.11.O.1 The technical requirements, including environment effect evaluation,safety and security requirements where appropriate, are defined anddeveloped to match needs and expectations)
-
(SWE.5.BP8 Ensure consistency - SWE.5.O.7 Consistency and bidirectional traceability are established between the elements of the software architectural design and the test cases included in the software integration test specification and between test cases and test results)
-
(13-20 Risk action request - MAN.5.O.2 Appropriate risk management strategies are defined andimplemented)
-
(MAN.6.BP10 Evaluate information products and measurementactivities - MAN.6.O.7 The measurement process and measures are evaluated andcommunicated to the process owner)
-
(PIM.3.BP2 Identify issues - PIM.3.O.2 Issues arising from the organization's internal/external environmentare identified as improvement opportunities and justified as reasonsfor change)
-
(SUP.1.BP3 Assure quality of process activities - SUP.1.O.2 Quality assurance is performed independently and objectively without conflicts of interest)
-
(13-21 Change control record - SUP.10.O.8 The status of all change requests is known)
-
(SUP.10.BP3 Record the status of change requests - SUP.10.O.8 The status of all change requests is known)
-
(SWE.2.BP5 Define resource consumption objectives - SWE.2.O.4 The dynamic behavior and resource consumption objectives of thesoftware elements are defined)
-
(SUP.7.BP2 Establish standards for documentation - SUP.7.O.2 The standards to be applied for the development of the documentation are identified)
-
(MAN.6.BP1 Establish organizational commitment for measurement - MAN.6.O.1 Organizational commitment is established and sustained to implementthe measurement process)
-
(17-00 Requirement specification - ACQ.12.O.3 Acceptance criteria and mechanisms for handling of breaches to thefulfillment of contract are established)
-
(07-08 Service level measure - MAN.6.O.3 An appropriate set of measures, driven by the information needs areidentified and/or developed)
-
(17-08 Interface requirements specification - SWE.2.O.3 The interfaces of each software element are defined)
-
(SWE.2.BP4 Describe dynamic behavior - SWE.2.O.4 The dynamic behavior and resource consumption objectives of thesoftware elements are defined)
-
(15-01 Analysis report - SYS.2.O.3 The impact of system requirements on the operating environment isanalyzed)
-
(08-04 Configuration management plan - SUP.8.O.7 Storage of the configuration items is controlled)
-
(SPL.1.BP5 Determine need for preliminary pre-studies - SPL.1.O.3 The need to undertake preliminary surveys or feasibility studies isdetermined)
-
(08-20 Risk mitigation plan - MAN.5.O.5 Risk measures are defined, applied, and assessed to determinechanges in the status of risk and the progress of the treatment activities)
-
(SYS.2.BP3 Analyze system requirements - SYS.2.O.2 System requirements are categorized and analyzed for correctnessand verifiability)
-
(15-16 Improvement opportunity - PIM.3.O.4 Improvement goals are identified and prioritized, and consequentchanges to the process are defined, planned and implemented)
-
(13-50 Test result - SYS.5.O.6 results of the system qualification test are summarized and communicated to all affected parties)
-
(12-04 Supplier proposal response - SPL.1.O.5 A supplier proposal is prepared in response to the customer request;and)
-
(14-02 Corrective Action Register - ACQ.11.O.2 The current and evolving acquisition needs are gathered and defined)
-
(08-00 Plan - PIM.3.O.7 The improvements made are evaluated and consideration given forusing the solution elsewhere within the organization)
-
(06-02 Handling and storage guide - SUP.8.O.3 Modifications and releases of the configuration items are controlled)
-
(ACQ.11.BP10 Ensure compliance of stated requirements - ACQ.11.O.6 The requirements include compliance with relevant standards,including environment effect evaluation, safety and security standardswhere appropriate)
-
(SYS.5.BP6 Ensure consistency - SYS.5.O.5 Consistency and bidirectional traceability are established between system requirements and test cases included in the system qualification test specification and between test cases and test results)
-
(08-52 Test plan - SYS.4.O.2 A system integration test strategy including the regression teststrategy is developed to test the system item interactions)
-
(MAN.3.BP2 Define project life cycle - MAN.3.O.1 The scope of the work for the project is defined)
-
(02-00 Contract - ACQ.13.O.9 Support and maintenance requirements are established)
-
(SUP.8.BP3 Establish a configuration management system - SUP.8.O.1 A configuration management strategy is developed)
-
(SUP.8.BP3 Establish a configuration management system - SUP.8.O.4 Modifications and releases are made available to affected parties)
-
(13-19 Review Record - SUP.4.O.2 The status and products of an activity of a process are evaluated through joint review activities between the stakeholders)
-
(SUP.9.BP4 Diagnose the cause and determine the impact of the problem - SUP.9.O.3 Problems are analyzed and assessed to identify an appropriate solution)
-
(SWE.2.BP6 Evaluate alternative software architectures - SWE.2.O.2 The software requirements are allocated to the elements of thesoftware)
-
(SUP.7.BP4 Identify the relevant documentation to be produced - SUP.7.O.3 Documentation to be produced by the process or project is identified)
-
(ACQ.14.BP3 Establish terms and conditions for CFP / ITT - ACQ.14.O.3 The agreement (contractual) terms of reference and conditions for CFP / ITT are established)
-
(15-01 Analysis report - SUP.4.O.3 Review results are made known to all affected parties)
-
(ACQ.3.BP2 Specify rights and duties - ACQ.3.O.2 The contract/agreement clearly and unambiguously specifies theexpectations, responsibilities, work products/deliverables and liabilitiesof both the supplier(s) and the acquirer)
-
(SUP.10.BP2 Identify and record the change requests - SUP.10.O.3 Dependencies and relationships to other change requests are identified)
-
(17-00 Requirement specification - ACQ.13.O.2 Requirements for the organizational, management, controlling, andreporting aspects of a project are defined)
-
(02-00 Contract - ACQ.12.O.7 Recognized criteria for proprietary, regulatory and other productliabilities issues are established)
-
(SUP.4.BP1 Define review elements - SUP.4.O.1 Management and technical reviews are held based on the needs ofthe project)
-
(SUP.10.BP8 Establish bidirectional traceability - SUP.10.O.9 Bi-directional traceability is established between change requests and affected work product)
-
(SWE.1.BP1 Specify software requirements - SWE.1.O.7 The software requirements are evaluated for cost, schedule andtechnical impact)
-
(SWE.4.BP2 Develop criteria for unit verification - SWE.4.O.2 Criteria for software unit verification are developed according to the software unit verification strategy that are suitable to provide evidence for compliance of the software units with the software detailed design and with the non-functional software requirements)
-
(SWE.1.BP6 Establish bidirectional traceability - SWE.1.O.6 Consistency and bidirectional traceability are established between system requirements and software requirements; and consistency and bidirectional traceability are established between system architectural design and software requirements)
-
(08-12 Project Plan - MAN.3.O.1 The scope of the work for the project is defined)
-
(15-05 Evaluation report - SUP.9.O.3 Problems are analyzed and assessed to identify an appropriate solution)
-
(11-03 Product release information - SPL.2.O.3 The release documentation is defined and produced)
-
(SWE.3.BP3 Describe dynamic behavior - SWE.3.O.3 The dynamic behavior of the software units is defined)
-
(13-01 Acceptance record - SUP.7.O.5 Documentation is developed and made available in accordance with identified standards)
-
(10-00 Process description - ACQ.12.O.3 Acceptance criteria and mechanisms for handling of breaches to thefulfillment of contract are established)
-
(ACQ.13.BP8 Define exchange of information - ACQ.13.O.4 The needs for exchanging information between all affected parties areestablished)
-
(07-07 Risk measure - MAN.6.O.4 Measurement activities are identified and performed)
-
(MAN.5.BP5 Define risk treatment actions - MAN.5.O.5 Risk measures are defined, applied, and assessed to determinechanges in the status of risk and the progress of the treatment activities)
-
(18-01 Acceptance criteria - ACQ.12.O.3 Acceptance criteria and mechanisms for handling of breaches to thefulfillment of contract are established)
-
(SWE.2.BP8 Ensure consistency - SWE.2.O.1 A software architectural design is defined that identifies the elementsof the software)
-
(14-02 Corrective Action Register - SUP.1.O.6 Management ensures that escalated non-conformances are resolved)
-
(11-04 Product release package - SWE.1.O.8 The software requirements are agreed and communicated to allaffected parties)
-
(15-01 Analysis report - SUP.4.O.5 Problems are identified and recorded)
-
(SWE.5.BP5 Select test cases - SWE.5.O.5 Test cases included in the software integration test specification are selected according to the software integration test strategy, and the release plan)
-
(14-08 Tracking system - SUP.4.O.5 Problems are identified and recorded)
-
(SWE.6.BP5 Establish bidirectional traceability - SWE.6.O.5 Consistency and bidirectional traceability are established between software requirements and software qualification test specification including test cases and between test cases and test results)
-
(05-00 Goals - PIM.3.O.4 Improvement goals are identified and prioritized, and consequentchanges to the process are defined, planned and implemented)
-
(SYS.3.BP7 Ensure consistency - SYS.3.O.6 The system architectural design is agreed and communicated to allaffected parties)
-
(MAN.5.BP3 Identify risks - MAN.5.O.2 Appropriate risk management strategies are defined andimplemented)
-
(08-00 Plan - PIM.3.O.2 Issues arising from the organization's internal/external environmentare identified as improvement opportunities and justified as reasonsfor change)
-
(14-01 Change history - SUP.8.O.3 Modifications and releases of the configuration items are controlled)
-
(SUP.8.BP2 Identify configuration items - SUP.8.O.2 All configuration items generated by a process or project are identified, defined and baselined according to the configuration management strategy)
-
(SPL.2.BP6 Communicate the type, service level and duration of support for a release - SPL.2.O.3 The release documentation is defined and produced)
-
(ACQ.14.BP4 Define financial terms - ACQ.14.O.4 RThe financial terms of reference for costs and payments for CFP / ITT are defined)
-
(19-11 Validation strategy - ACQ.14.O.1 Rules are defined for proposal/tender invitation and evaluation which comply with the acquisition policy and strategy)
-
(MAN.3.BP8 Define, monitor and adjust project schedule - MAN.3.O.3 The activities and resources necessary to complete the work are sizedand estimated)
-
(ACQ.3.BP6 Award contract/agreement - ACQ.3.O.1 A contract/agreement is negotiated, reviewed, approved and awardedto the supplier(s))
-
(REU.2.BP3 Assess domains for potential reuse - REU.2.O.3 The domains in which to investigate reuse opportunities, or in which itis intended to practice reuse, are identified)
-
(SUP.4.BP3 Prepare joint review - SUP.4.O.1 Management and technical reviews are held based on the needs ofthe project)
-
(ACQ.11.BP4 Ensure consistency - ACQ.11.O.2 The current and evolving acquisition needs are gathered and defined)
-
(SPL.2.BP5 Build the release from configured items - SPL.2.O.2 The release is assembled from configured items)
-
(ACQ.15.BP3 Short-list suppliers with required qualification - ACQ.15.O.3 The suppliers which possess required qualification are short-listed fortender solution(s) evaluation)
-
(15-16 Improvement opportunity - SUP.4.O.4 Action items resulting from reviews are tracked to closure)
-
(08-51 Technology monitoring plan - ACQ.11.O.5 A mechanism for identifying and managing the impact of changingtechnology to the technical requirements is defined)
-
- SPL Supply Process Group
- SPL.2 Product Release
- SPL.1 Supplier Tendering
- SWE Software Engineering Process Group
- SWE.3 Software Detailed Design and Unit Construction
- SWE.4 Software Unit Verification
- SWE.5 Software Integration and Integration Test
- SWE.2 Software Architectural Design
- SWE.6 Software Qualification Test
- SWE.1 Software Requirements Analysis
- REU Reuse Process Group
- REU.2 Reuse Program Management
- SYS System Engineering Process Group
- SYS.4 System Integration and Integration Test
- SYS.2 System Requirements Analysis
- SYS.1 Requirements Elicitation
- SYS.5 System Qualification Test
- SYS.3 System Architectural Design
- PIM Process Improvement Group
- PIM.3 Process Improvement
- ACQ Acquisition Process Group
- ACQ.14 Request for Proposals
- ACQ.3 Contract Agreement
- ACQ.15 Supplier Qualification
- ACQ.13 Project Requirements
- ACQ.4 Supplier Monitoring
- ACQ.12 Legal and Administrative Requirements
- ACQ.11 Technical Requirements
- MAN Management Process Group
- MAN.5 Risk Management
- MAN.3 Project Management
- MAN.6 Measurement
- HWE Hardware Engineering Process Group
- HWE.3 Verification against Hardware Design
- HWE.2 Hardware Design
- HWE.1 Hardware Requirements Analysis
- HWE.4 Verification against Hardware Requirements
- SUP Supporting Process Group
- SUP.10 Change Request Management
- SUP.8 Configuration Management
- SUP.4 Joint Review
- SUP.1 Quality Assurance
- SUP.7 Documentation
- SUP.9 Problem Resolution Management
- SUP.2 Verification
- Overview - Process Reference Model
- Overview - Extended