ISO 15288 Converted Model Business or Mission Analysis As stated in ISO/IEC/IEEE 15288:2023, [6.4.1.1] The purpose of the Business or Mission Analysis process is to define the business or mission problem or opportunity, characterize the solution space, and determine potential solution class(es) that could address a problem or take advantage of an opportunity. See detailed description in the INCOSE Handbook v.5, page 103 Prepare for business or mission analysis Define the problem or opportunity space Characterize the solution space Evaluate alternative solution classes Manage the business or mission analysis Stakeholder Needs and Requirements Definition As stated in ISO/IEC/IEEE 15288:2023, [6.4.2.1] The purpose of the Stakeholder Needs and Requirements Definition process is to define the stakeholder requirements for a system that can provide the capabilities needed by users and other stakeholders in a defined environment. See detailed description in the INCOSE Handbook v.5, page 107 Prepare for stakeholder needs and requirements definition Develop the operational concept and other lifecycle concepts Define stakeholder needs Transform stakeholder needs into stakeholder requirements Analyze stakeholder needs and requirements Manage the stakeholder needs and requirements definition System Requirements Definition As stated in ISO/IEC/IEEE 15288:2023, [6.4.3.1] The purpose of the System Requirements Definition process is to transform the stakeholder, useroriented view of desired capabilities into a technical view of a solution that meets the operational needs of the user. See detailed description in the INCOSE Handbook v.5, page 112 Prepare for system requirements definition Define system requirements Analyze system requirements Manage system requirements System Architecture Definition As stated in ISO/IEC/IEEE 15288:2023, [6.4.4.1] The purpose of the Architecture Definition process is to generate system architecture alternatives, to select one or more alternative(s) that frame stakeholder concerns and meet system requirements, and to express this in a set of consistent views. See detailed description in the INCOSE Handbook v.5, page 118 Prepare for architecture definition Conceptualize the system architecture Evaluate the system architecture Elaborate the system architecture Manage results of the architecture definition Design Definition As stated in ISO/IEC/IEEE 15288:2023, [6.4.5.1] The purpose of the Design Definition process is to provide sufficient detailed data and information about the system and its elements to enable the imple- mentation consistent with architectural entities as defined in models and views of the system architecture. See detailed description in the INCOSE Handbook v.5, page 124 Prepare for design definition Create the sytem design Evaluate the system design Manage results of design definition System Analysis As stated in ISO/IEC/IEEE 15288, [6.4.6.1] The purpose of the System Analysis process is to provide a rigorous basis of data and information for technical understanding to aid decision-�making across the life cycle. See detailed description in the INCOSE Handbook v.5, page 129 Prepare for system analysis Perform system analysis Manage system analysis Implementation As stated in ISO/IEC/IEEE 15288:2023, [6.4.7.1] The purpose of the Implementation process is to realize a specified system element. See detailed description in the INCOSE Handbook v.5, page 132 Prepare for implementation Perform implementation Manage results of implementation Integration As stated in ISO/IEC/IEEE 15288:2023, [6.4.8.1] The purpose of the Integration process is to synthesize a set of system elements into a realized system (product or service) that satisfies system requirements* architecture, and design. See detailed description in the INCOSE Handbook v.5, page 134 Prepare for integration Perform_integration Manage results of integration Verification As stated in ISO/IEC/IEEE 15288:2023, [6.4.9.1] The purpose of the Verification process is to provide objective evidence that a system or system element fulfils its specified requirements and characteristics. See detailed description in the INCOSE Handbook v.4, page 138 Prepare for verification Perform verification Manage results of verification Transition As stated in ISO/IEC/IEEE 15288:2023, [6.4.10.1] The purpose of the Transition process is to establish a capability for a system to provide services specified by stakeholder requirements in the operational environment. See detailed description in the INCOSE Handbook v.5, page 143 Prepare for the transition Perform the transition Manage results of transition Validation As stated in ISO/IEC/IEEE 15288:2023, [6.4.11.1] The purpose of the Validation process is to provide objective evidence that the system, when in use, fulfills its business or mission objectives and stakeholder requirements, achieving its intended use in its intended operational environment. See detailed description in the INCOSE Handbook v.5, page 146 Prepare for validation Perform validation Manage results of validation Operation As stated in ISO/IEC/IEEE 15288:2023, [6.4.12.1] The purpose of the Operation process is to use the system to deliver its services. See detailed description in the INCOSE Handbook v.5, page 152 Prepare for operation Perform operation Manage results of operation Support stakeholders Maintenance As stated in ISO/IEC/IEEE 15288:2023, [6.4.13.1] The purpose of the Maintenance process is to sustain the capability of the system to provide a service. See detailed description in the INCOSE Handbook v.5, page 154 Prepare for maintenance and logistics Perform maintenance Perform logistics support Manage results of maintenance and logistics Disposal As stated in ISO/IEC/IEEE 15288:2023, [6.4.14.1] The purpose of the Disposal process is to end the existence of a system element or system for a specified intended use, appropriately handle replaced or retired elements, and to properly attend to identified critical disposal needs. See detailed description in the INCOSE Handbook v.5, page 156 Prepare for disposal Perform disposal Finalize the disposal Alternative solution classes Identifies and describes the classes of solutions that may address the problem or opportunity. Analysis situations Analyses that arise from any stakeholder. Can originate from any life cycle process. Business or mission analysis strategy and approach Approaches, schedules, resources, and specific considerations required to perform business or mission analysis. Business or mission analysis report An account prepared for interested parties in order to communicate the status, results, and outcomes of the business or mission analysis activities. Business or mission analysis records and artifacts Permanent, readable form of data, information, or knowledge related to business or mission analysis. Critical performance measurement needs Identified information needs of the decision makers with respect to system-of-interest expectations. Critical performance measurement data Data provided for the identified system-of-interest measurement needs. Constraints on solution Externally imposed limitation on the system, its design, or implementation or on the process used to develop or modify a system. (ISO/IEC/IEEE 29148, 2018). Design definition strategy and approach Approaches, schedules, resources, and specific considerations required to perform design definition. Design definition report An account prepared for interested parties in order to communicate the status, results, and outcomes of the design definition activities. Design definition records and artifacts Permanent, readable form of data, information++ or knowledge related to design definition. Disposal strategy and approach Approaches, schedules, resources, and specific considerations required to perform disposal. Disposal procedure Presents an ordered series of steps to perform disposal. Disposal report An account prepared for interested parties in order to communicate the status, results, and outcomes of the disposal activities. Disposal records and artifacts Permanent, readable form of data, information, or knowledge related to disposal. Implementation strategy and approach Approaches, schedules, resources, and specific considerations required to perform implementation. Implementation report An account prepared for interested parties in order to communicate the status, results, and outcomes of the implementation activities. Implementation records and artifacts Permanent++ readable form of data, information, or knowledge related to implementation. Integration strategy and approach Approaches, schedules, resources++ and specific considerations required to perform integration. Integration procedure Presents an ordered series of steps to perform integration. Integration records and artifacts Permanent, readable form of data, information, or knowledge related to integration. Installation procedure Presents an ordered series of steps to perform transition. Integrated system or system element System or system element (product or service) that has been aggregated from system elements. Integration report An account prepared for interested parties in order to communicate the status, results, and outcomes of the integration activities. Installed system System (product or service) that has been installed in its operational environment. Life cycle concepts Articulation and refinement of the various life cycle concepts consistent with the stakeholder needs. Typical concepts include: acquisition concept; deployment concept; operational concept (OpsCon); support concept; retirement concept. Maintenance and logistics report An account prepared for interested parties in order to communicate the status, results, and outcomes of the maintenance activities. Maintained and sustained system System (product or service) that has been maintained for use in its operational environment. Maintenance and logistics strategy and approach Approaches, schedules, resources, and specific considerations required to perform maintenance. Maintenance and logistics procedure Presents an ordered series of steps to perform maintenance. Maintenance and logistics records and artifacts Permanent, readable form of data, information, or knowledge related to maintenance. Operational system System (product or service) being used in its operational environment. Operation report An account prepared for interested parties in order to communicate the status, results, and outcomes of the operation activities. Other validated artifacts Artifacts that are validated Operation strategy and approach Approaches, schedules, resources, and specific considerations required to perform operation. Operation procedure Presents an ordered series of steps to perform operation. Operation records and artifacts Permanent, readable form of data, information, or knowledge related to operation. Other verified artifacts Artifacts that are verified Problem or opportunity statement Description of the problem or opportunity. Should be derived from the organization strategy and provide enough detail to understand the gap or new capability that is being considered Requirements imposed on enabling systems Identified requirements for enabling systems of the system-of-interest. Stakeholder needs and requirements definition strategy and approach Approaches, schedules, resources, and specific considerations required to perform stakeholder needs and requirements definition. Stakeholder needs and requirements definition report An account prepared for interested parties in order to communicate the status, results, and outcomes of the stakeholder needs and requirements definition activities. Stakeholder needs and requirements definition records and artifacts Permanent, readable form of data, information, or knowledge related to stakeholder needs and requirements definition. Stakeholder identification List of individuals or organizations having a right++ share, claim, or interest in a system or in ist possession of characteristics that meet their needs and expectations. (Adapted from ISO/IEC/IEEE 15288, 2023) Stakeholder needs and requirements Structured collection of the requirements [characteristics, context, concepts, constraints and priorities] of the stakeholder and the relationship to the external environment. (ISO/IEC/IEEE 29148, 2018) System analysis strategy and approach Approaches, schedules, resources, and specific considerations required to perform system analysis. System analysis report An account prepared for interested parties in order to communicate the status, results, and outcomes of the system analysis activities. System analysis records and artifacts Permanent, readable form of data, information, or knowledge related to system analysis. System architecture description The fundamental conception of a system-of-interest in terms of its purpose, system qualities (such as feasibility, performance, safety, and interoperability), constraints, and design decisions and rationale. Identification of the architecture’s stakeholders and the stakeholders’ architecture-related concerns. (Adapted from ISO/IEC/IEEE 15289, 2019) System architecture definition strategy and approach Approaches, schedules, resources, and specific considerations required to perform system architecture definition. System architecture definition report An account prepared for interested parties in order to communicate the status, results, and outcomes of the system architecture definition activities. System architecture assessment report Provides results of system architecture assessments. It includes evaluation criteria. (Adapted from ISO/IEC/IEEE 15289, 2019) System architecture definition records and artifacts Permanent, readable form of data, information, or knowledge related to system architecture definition. System architecture rationale Rationale for architecture selection, technological/technical system element selection, and allocation between system requirements and architectural entities. System design description Describes the design of a system or element. (Adapted from ISO/IEC/IEEE 24765, 2017) System design rationale Rationale for design selection, system element selection, and allocation between system requirements and system elements. Includes rationale of major selected implementation options and enablers. System design assessment report Provides results of system design assessments. It includes evaluation criteria. (Adapted from ISO/IEC/IEEE 15289, 2019) System design characteristics Design attributes or distinguishing features that pertain to a measurable description of a product or service. (ISO/IEC/IEEE 15288, 2023) System interface definition Description of the interfaces between systems and system elements. (Adapted from ISO/IEC/IEEE 24765, 2017) System element description Applies the system architecture description to the low-level system configuration items and elements. It is at a level of detail to permit design, implementation, and test. (Adapted from ISO/IEC/IEEE 15289, 2019) System element System element (product or service) implemented consistent with its system element requirements. System requirements Structured collection of the requirements [functions, performance, design constraints, and other attributes] for the system and its operational environments and external interfaces. (ISO/IEC/IEEE 29148, 2018) System requirements definition strategy and approach Approaches, schedules, resources, and specific considerations required to perform system requirements definition. System requirements definition report An account prepared for interested parties in order to communicate the status, results, and outcomes of the system requirements definition activities. System requirements definition records and artifacts Permanent, readable form of data, information, or knowledge related to system requirements definition. System viewpoints views and models Definitions of viewpoints to document the procedures for creating, interpreting, analyzing, and evaluating architectural data. One or more views of the system. Each architectural view is a representation of the complete system from the perspective of one or more system concerns, for its stakeholders. (Adapted from ISO/IEC/IEEE 15289, 2019) Traceability mapping Records the relationship between two or more artifacts of the development process (e.g., requirements, functions, system elements, verifications, and validations, tasks). (Adapted from ISO/IEC/IEEE 24765++ 2017) Training materials Materials for the provision of formal and informal learning activities. (Adapted from ISO/IEC/IEEE 24765, 2017) Trained personnel Trained individuals or organizations that perform the operation, maintenance, or other functions of or for a system. Transition report An account prepared for interested parties in order to communicate the status, results, and outcomes of the transition activities. Transition strategy and approach Approaches, schedules, resources, and specific considerations required to perform transition. Transition records and artifacts Permanent, readable form of data, information, or knowledge related to transition. Verification strategy and approach Approaches, schedules, resources, and specific considerations required to perform verification. Verification procedure Presents an ordered series of steps to perform verification. Verified system requirements Set of system requirements that have been verified. Verified system architecture and design System architecture and design that has been verified. Verification criteria The verification criteria (the measures to be assessed), who will perform verification activities, and the verification environments of the system-of-interest. Verified system System (product or service) that has been verified. Verification report An account prepared for interested parties in order to communicate the status, results, and outcomes of the verification activities. Verification records and artifacts Permanent, readable form of data, information, or knowledge related to verification. Validation strategy and approach Approaches, schedules, resources, and specific considerations required to perform validation. Validation procedure Presents an ordered series of steps to perform validation. Validation records and artifacts Permanent, readable form of data, information, or knowledge related to validation. Validated stakeholder needs and requirements Set of stakeholder needs and requirements that have been validated. Validated system architecture and design System architecture and design that has been validated. Validation report An account prepared for interested parties in order to communicate the status, results, and outcomes of the validation activities. Validation criteria The validation criteria (the measures to be assessed), who will perform validation activities++ and the validation environments of the system-of-interest. Validated system System (product or service) that has been validated. Project Planning As stated in ISO/IEC/IEEE 15288:2023, [6.3.1.1] The purpose of the Project Planning process is to produce and coordinate effective and workable plans. See detailed description in the INCOSE Handbook v.5, page 70 Define the project Plan project and technical management Activate the project Project Assessment and Control As stated in ISO/IEC/IEEE 15288:2023, [6.3.2.1] The purpose of the Project Assessment and Control process is to assess if the plans are aligned and feasible, determine the status of the project, technical and process performance, and direct execution to ensure that the performance is according to plans and schedules, within projected budgets, to satisfy technical objectives. See detailed description in the INCOSE Handbook v.5, page 75 Plan for project assessment and control Assess the project Control the project Decision Management As defined by ISO/IEC/IEEE 15288:2023, [6.3.3.1] The purpose of the Decision Management process is to provide a structured, analytical framework for objectively identifying, characterizing and evaluating a set of alternatives for a decision at any point in the life cycle and select the most beneficial course of action. See detailed description in the INCOSE Handbook v.5, page 78 Prepare for decisions Analyze the decision information Make and manage decisions Risk Management As stated in ISO/IEC/IEEE 15288:2023, [6.3.4.1] The purpose of the Risk Management process is to identify, analyze, treat and monitor the risks continually. See detailed description in the INCOSE Handbook v.5, page 81 Plan risk management Manage the risk profile Analyze risks Treat risks that exceed their risk threshold Monitor risks Configuration Management As stated in ISO/IEC/IEEE 15288:2023, [6.3.5.1] The purpose of the Configuration Management process is to manage and control system elements and configurations over the life cycle. CM also manages consistency between a product and its associated configuration definition. See detailed description in the INCOSE Handbook v.5, page 87 Prepare for configuration management Perform configuration identification Perform configuration change management Perform configuration status accounting Peform configuration verification and audit Information Management As stated in ISO/IEC/IEEE 15288:2023, [6.3.6.1] The purpose of the Information Management process is to generate, obtain, confirm, transform, retain, retrieve, disseminate and dispose of information, to designated stakeholders. Information management plans, executes, and controls the provision of information to designated stakeholders that is unambiguous, complete, verifiable, consistent, modifiable, traceable, and presentable. Information includes technical, project, organizational, agreement, and user information. Information is often derived from data records of the organization, system, process, or project. See detailed description in the INCOSE Handbook v.5, page 91 Prepare for information management Perform information management Measurement As stated in ISO/IEC/IEEE 15288:2023, [6.3.7.1] The purpose of the Measurement process is to collect, analyze, and report objective data and information to support effective management and demonstrate the quality of the products, services, and processes. See detailed description in the INCOSE Handbook v.5, page 93 Prepare for measurement Perform measurement Quality Assurance As stated in ISO/IEC/IEEE 15288:2023, [6.3.8.1] The purpose of the Quality Assurance process is to help ensure the effective application of the organization's Quality Management process to the project. See detailed description in the INCOSE Handbook v.5, page 98 Prepare for quality assurance Perform product or service evaluation Perform process evaluations Manage QA records and reports Treat incidents and problems Acquisition need Identified need that cannot be met within the organization encountering the need or a need that can be met in a more economical way by a supplier. Breakdown structures Hierarchical representations of project aspects into smaller components providing the necessary frameworks to accomplish the project objectives and create the required deliverables. Candidate risks and opportunities Risks and opportunities that arise from any stakeholder. Can originate from any life cycle process. Candidate items for configuration management Items for configuration control. Can originate from any life cycle process. Candidate items for information management Items for information control. Can originate from any life cycle process. Configuration baseline Configuration information formally designated at a specific time during the life of a product, product component, service, or service component. (Adapted from ISO/IEC/IEEE 24765, 2017). Configuration management strategy and approach Approaches, schedules, resources, and specific considerations required to perform configuration management. Configuration management system System used to support and enable configuration management. Configuration management report An account prepared for interested parties in order to communicate the status, results, and outcomes of the configuration management activities. Configuration verification and audit report Provides results of configuration management verifications and audits to ensure adequate traceability, control, and visibility. It includes evaluation criteria. Configuration management records and artifacts Permanent, readable form of data, information, or knowledge related to configuration management. Decision situations Decisions that arise from any stakeholder. Can originate from any life cycle process. Decision register A repository that supports the availability for use and communication of all relevant decision information in a timely, complete, valid, and, if required, confidential manner. Decision management report An account prepared for interested parties in order to communicate the status, results, and outcomes of the decision management activities. Decision management strategy and approach Approaches, schedules, resources, and specific considerations required to perform decision management. Decision management records and artifacts Permanent, readable form of data++ information, or knowledge related to decision management. Disposed system System (product or service) that has been deactivated, disassembled, and removed from operations and been properly disposed. Information management strategy and approach Approaches, schedules, resources, and specific considerations required to perform information management. Information register A repository that supports the availability for use and communication of all relevant project information artifacts in a timely, complete, valid, and, if required, restricted manner. Information management report An account prepared for interested parties in order to communicate the status, results, and outcomes of the information management activities. Information management records and artifacts Permanent, readable form of data, information, or knowledge related to information management. Measurement needs Measurement needs from all applicable life cycle processes, including: critical performance measurement needs, organizational measurement needs, and project measurement needs. Measurement data Measurement data from all applicable life cycle processes, including: critical performance measurement data, organizational measurement data, and project measurement data. Measurement strategy and approach Approaches, schedules, resources, and specific considerations required to perform measurement. Measurement register A repository that supports the availability for use and communication of all relevant measures in a timely, complete, valid, and, if required, confidential manner. Measurement report An account prepared for interested parties in order to communicate the status, results++ and outcomes of the measurement activities. Measurement records and artifacts Permanent, readable form of data++ information, or knowledge related to measurement. Project assessment and control strategy and approach Approaches, schedules, resources, and specific considerations required to perform project assessment and control. Project assessment and control records and artifacts Permanent, readable form of data, information++ or knowledge related to project assessment and control. Project authorization request Request from the project to the organization to authorize the project. Project budget Estimate of the costs associated with a particular project. Includes labor, infrastructure, acquisition, and enabling system costs along with reserves for risk management. Project constraints Externally imposed limitation on the project developing or modifying a system. (ISO/IEC/IEEE 29148, 2018) Project control request Project directives based on action required due to deviations from the project plan. If assessments are associated with a decision gate, a decision to proceed or not to proceed, is taken. Project decision gate or review result Decision gate and review artifacts that are expected through conduct of the decision gate or technical review and that can be considered elements of exit criteria. (Adapted from ISO/IEC/IEEE 24748–8, 2019) Project lessons learned Project-related lessons learned. Results from an evaluation or observation of an implemented corrective action that contributed to improved performance or increased capability. A lesson learned also results from an evaluation or observation of a positive finding that did not necessarily require corrective action other than sustainment. Project human resource needs Identified human resource needs of the project. Project infrastructure Resources, facilities, personnel, and/or services that support the project. Project infrastructure needs Identified infrastructure needs of the project. Project measurement needs Identified information needs of the decision makers with respect to project expectations. Project objectives The objectives or goals for the project. Project measurement data Data provided for the identified project measurement needs. Project objectives Identified information needs of the decision makers with respect to project expectations. Project objectives The objectives or goals for the project. Project planning records and artifacts Permanent, readable form of data, information, or knowledge related to project planning. Project procedures Procedures from all applicable life cycle processes, including: integration procedure, verification procedure, installation procedure, validation procedure, operation procedure, maintenance and logistics procedure, and disposal procedure. Project reports Reports from all applicable project life cycle processes, including: acquisition report supply report, decision management report, risk management report, configuration management report, configuration verification and audit report, information management report, measurement report, quality assurance report, quality assurance evaluation report, business or mission analysis report, stakeholder needs and requirements definition report, system requirements definition report, system architecture definition report, system architecture assessment report, design definition report, system design assessment report, system analysis report, implementation report, integration report, verification report, transition report, validation report, operation report maintenance and logistics report, and disposal report. Project schedule A linked list of a project milestones, activities, and deliverables with intended start and finish dates May include a top-level milestone schedule and multiple levels (also called tiers) of schedules of increasing detail and task descriptions with completion criteria and work authorizations. Project status report or dashboard A linked list of a project’s milestones, activities, and deliverables with intended start and finish dates May include a top-level milestone schedule and multiple levels (also called tiers) of schedules of increasing detail and task descriptions with completion criteria and work authorizations. Project strategies and approaches Strategies/approaches for all applicable project life processes, including: acquisition strategy/approach, supply strategy & approach, project assessment and control strategy/approach, decision management strategy/approach, risk management strategy/approach, configuration management strategy/approach, information management strategy/approach, measurement strategy/approach, quality assurance strategy/approach, business or mission analysis strategy/approach, stakeholder needs and requirements definition strategy/approach, system requirements definition strategy/approach, system architecture definition strategy/approach, design definition strategy/approach, system analysis strategy/approach, implementation strategy/approach, integration strategy/approach, verification strategy/approach, transition strategy/approach, validation strategy/approach, operation strategy/approach, maintenance and logistics strategy/approach, and disposal strategy/approach. Quality assurance corrective action Action to eliminate the cause or reduce the likelihood of recurrence of a detected project nonconformity or other undesirable situation. (Adapted from ISO/IEC 19770–1, 2017) Quality assurance evaluation report Provides results of quality assurance evaluations. It includes evaluation criteria. (Adapted from ISO/IEC/IEEE 15289, 2019) Quality assurance records and artifacts Permanent, readable form of data, information, or knowledge related to quality assurance. Quality assurance report An account prepared for interested parties in order to communicate the status, results, and outcomes of the quality assurance activities. Quality assurance strategy and approach Approaches, schedules, resources, and specific considerations required to perform quality assurance. Quality assurance system System used to support and enable quality assurance. Risk management strategy and approach Approaches, schedules, resources, and specific considerations required to perform risk management. Risk register A repository that supports the availability for use and communication of all relevant risk information in a timely, complete, valid, and, if required, confidential manner. Risk management report An account prepared for interested parties in order to communicate the status, results, and outcomes of the risk management activities. Risk management records and artifacts Permanent, readable form of data, information, or knowledge related to risk management. Systems engineering management plan (SEMP) Presents how the project processes and activities are executed to assure the project’s successful completion, and the quality of the deliverable product or service. (Adapted from ISO/IEC/ IEEE 15289, 2019) System analysis request A request to conduct a system analysis. Change request Identified anomaly, required, or recommended enhancement to a project, from the time an idea is recorded until the disposition by a designated change authority. (Adapted from ISO/IEC/IEEE 24765, 2017). Change request_FromAcquirer Identified anomaly, required, or recommended enhancement to a project, from the time an idea is recorded until the disposition by a designated change authority. (Adapted from ISO/IEC/IEEE 24765, 2017). Derived Work Product (not a dedicated INCOSE handbook work product!): Change Requests can be separated in the request itself (from different sources internal and external) and (after analysis and approval) the derived Implementation Tasks, necessary for resolve. Change request_FromSupplier Identified anomaly, required, or recommended enhancement to a project, from the time an idea is recorded until the disposition by a designated change authority. (Adapted from ISO/IEC/IEEE 24765, 2017). Derived Work Product (not a dedicated INCOSE handbook work product!): Change Requests can be separated in the request itself (from different sources internal and external) and (after analysis and approval) the derived Implementation Tasks, necessary for resolve. Change request_FromProjectAssessment Identified anomaly, required, or recommended enhancement to a project, from the time an idea is recorded until the disposition by a designated change authority. (Adapted from ISO/IEC/IEEE 24765, 2017). Derived Work Product (not a dedicated INCOSE handbook work product!): Change Requests can be separated in the request itself (from different sources internal and external - here from internal project assessment) and (after analysis and approval) the derived Implementation Tasks, necessary for resolve. Change request_FromInformationManagement Identified anomaly, required, or recommended enhancement to a project, from the time an idea is recorded until the disposition by a designated change authority. (Adapted from ISO/IEC/IEEE 24765, 2017). Derived Work Product (not a dedicated INCOSE handbook work product!): Change Requests can be separated in the request itself (from different sources internal and external) and (after analysis and approval) the derived Implementation Tasks, necessary for resolve. Change request_ImplementationTask Identified anomaly, required, or recommended enhancement to a project, from the time an idea is recorded until the disposition by a designated change authority. (Adapted from ISO/IEC/IEEE 24765, 2017). Derived Work Product (not a dedicated INCOSE handbook work product!): Change Requests can be separated in the request itself (from different sources internal and external) and (after analysis and approval) the derived Implementation Tasks, necessary for resolve. Life Cycle Model Management As stated in ISO/IEC/IEEE 15288:2023, [6.2.1.1] The purpose of the Life Cycle Model Management process is to define, maintain, and assure availability of policies, life cycle processes, life cycle models, and procedures for use by the organization with respect to the scope of [ISO/IEC/IEEE 15288:2023]. See detailed description in the INCOSE Handbook v.5, page 51 Establish the life cycle processes Assess the life cycle processes Improve the life cycle processes Infrastructure Management As stated in ISO/IEC/IEEE 15288:2023, [6.2.2.1] The purpose of the Infrastructure Management process is to provide the infrastructure and services to projects to support organization and project objectives throughout the life cycle. See detailed description in the INCOSE Handbook v.5, page 54 Establish the infrastructure Maintain the infrastructure Portfolio Management As stated in ISO/IEC/IEEE 15288:2023, [6.2.3.1] The purpose of the Portfolio Management process is to initiate and sustain necessary, sufficient and suitable projects in order to meet the strategic objectives of the organization. See detailed description in the INCOSE Handbook v.5, page 57 Define and authorize projects Evaluate the portfolio of projects Terminate projects Human Resource Management As stated in ISO/IEC/IEEE 15288:2023, [6.2.4.1] The purpose of the Human Resource Management process is to provide the organization with necessary human resources and to maintain their competencies, consistent with business needs. See detailed description in the INCOSE Handbook v.5, page 60 Identify skills Develop skills Acquire and provide skills Quality Management As stated in ISO/IEC/IEEE 15288:2023, [6.2.5.1] The purpose of the Quality Management process is to assure that products, services and implementations of the quality management process meet organizational and project quality objectives and achieve customer satisfaction. See detailed description in the INCOSE Handbook v.5, page 63 Plan quality management Assess quality management Perform quality management corrective action and preventive action Knowledge Management As stated in ISO/IEC/IEEE 15288:2023, [6.2.6.1] The purpose of the Knowledge Management process is to create the capability and assets that enable the organization to exploit opportunities to re-�apply existing knowledge. See detailed description in the INCOSE Handbook v.5, page 67 Plan knowledge management Share knowledge and skills throughout the organization Share knowledge assets throughout the organization Manage knowledge skills and knowledge assets Human resource management records and artifacts Permanent, readable form of data, information, or knowledge related to human resource management. Human resource management report An account prepared for interested parties in order to communicate the status, results, and outcomes of the human resource management activities. Human resource management strategy and approach Approaches, schedules, resources, and specific considerations required to perform human resource management. Infrastructure management records and artifacts Permanent, readable form of data, information, or knowledge related to infrastructure management. Infrastructure management report An account prepared for interested parties in order to communicate the status, results, and outcomes of the infrastructure management activities. Infrastructure management strategy and approach Approaches, schedules, resources, and specific considerations required to perform infrastructure management. Knowledge management records and artifacts Permanent, readable form of data, information, or knowledge related to knowledge management. Knowledge management report An account prepared for interested parties in order to communicate the status, results, and outcomes of the knowledge management activities. Knowledge management strategy and approach Approaches, schedules, resources, and specific considerations required to perform knowledge management. Knowledge management system System used to support and enable knowledge management. Life cycle model management records and artifacts Permanent, readable form of data, information, or knowledge related to life cycle model management. Life cycle model management report An account prepared for interested parties in order to communicate the status, results, and outcomes of the life cycle model management activities. Life cycle model management strategy and approach Approaches, schedules, resources, and specific considerations required to perform life cycle model management. (--> required for LCMM itself)) Life cycle models Framework of processes and activities concerned with the life cycle that can be organized into stages, acting as a common reference for communication and understanding. (ISO/IEC/IEEE 15288, 2023) Organization infrastructure Resources, facilities, personnel, and/or services that support the organization. Organization infrastructure needs Identified organizational infrastructure needs. Organization lessons learned Organizational-related lessons learned. Results from an evaluation or observation of an implemented corrective action that contributed to improved performance or increased capability. A lesson learned also results from an evaluation or observation of a positive finding that did not necessarily require corrective action other than sustainment. Organization policies High-level direction at the organizational level consistent with the organization's strategies. (Adapted from ISO/IEC/IEEE 15289, 2019) Organization procedures Presents an ordered series of steps to perform a process, activity, or task for an organization. (Adapted from ISO/IEC/IEEE 15289++ 2019) Organization processes Set of interrelated or interacting activities that transform inputs into outputs for an organization. (Adapted from ISO/IEC/IEEE 15288, 2023) Organizational measurement data Data provided for the identified organizational measurement needs. Organizational measurement needs Identified information needs of the decision makers with respect to organizational expectations. Portfolio management records and artifacts Permanent, readable form of data, information, or knowledge related to portfolio management. Portfolio management report An account prepared for interested parties in order to communicate the status, results, and outcomes of the portfolio management activities. Portfolio management strategy and approach Approaches, schedules, resources, and specific considerations required to perform portfolio management. Project authorization Authorization from the organization to proceed per the agreed-to project plan. Project direction Organizational direction to the project. Includes sustainment of projects meeting objectives and redirection or termination of projects not meeting objectives. Project infrastructure Identified human resource needs of the project. Project infrastructure Resources, facilities, personnel, and/or services that support the project. Project portfolio Collection of projects that addresses the strategic objectives of the organization. (ISO/IEC/IEEE 12207, 2017) Qualified personnel Individuals equipped to perform duties on behalf of the organization, including officers, employees, and contractors. (Adapted from ISO/IEC/IEEE 24765, 2017) Quality management corrective action Action to eliminate the cause or reduce the likelihood of recurrence of a detected organizational nonconformity or other undesirable situation. (Adapted from ISO/IEC 19770–1++ 2017) Quality management criteria and methods Rules on which a judgment or decision can be based, or by which an organization can be evaluated. (Adapted from ISO/IEC/IEEE 15289, 2019) Quality management evaluation report Provides results of quality management evaluations. It includes evaluation criteria. (Adapted from ISO/IEC/IEEE 15289, 2019) Quality management records and artifacts Permanent, readable form of data, information, or knowledge related to quality management. Quality management report An account prepared for interested parties in order to communicate the status, results, and outcomes of the quality management activities. Quality management strategy and approach Approaches, schedules, resources, and specific considerations required to perform quality management. Quality management system System used to support and enable quality management. Records and artifacts Records from all applicable life cycle processes, including: acquisition records/artifacts, supply records/artifacts, life cycle model management records/artifacts, infrastructure management records/artifacts, portfolio management records/artifacts, human resource management records/artifacts, quality management records/artifacts, knowledge management records/artifacts, project planning records/artifacts, project assessment and control records/artifacts, decision management records/artifacts, risk management records/artifacts, configuration management records/artifacts, information management records/artifacts, measurement records/artifacts, quality assurance records/artifacts, business or mission analysis records/artifacts, stakeholder needs and requirements definition records/artifacts, system requirements definition records/artifacts, system architecture definition records/artifacts, design definition records/artifacts, system analysis records/artifacts, implementation records/artifacts, integration records/artifacts, verification records/artifacts, transition records/artifacts, validation records/artifacts, operation records/artifacts, maintenance and logistics records/artifacts, disposal records/artifacts, tailoring records/artifacts. Reused system or system element System or system element (product or service) reused by an organization consistent with ist system element requirements. Acquisition As stated in ISO/IEC/IEEE 15288:2023, [6.1.1.1] The purpose of the Acquisition process is to obtain a product or service in accordance with the acquirer's requirements. See detailed description in the INCOSE Handbook v.5, page 45 Prepare for the acquisition See detailed description in the INCOSE Handbook v.5, page 140 Advertise the acquisition and select the supplier See detailed description in the INCOSE Handbook v.5, page 141 Establish and maintain the agreement See detailed description in the INCOSE Handbook v.5, page 141 Monitor the agreement See detailed description in the INCOSE Handbook v.5, page 141 Accept the product or service See detailed description in the INCOSE Handbook v.5, page 142 Supply As stated in ISO/IEC/IEEE 15288:2023, [6.1.2.1] The purpose of the Supply process is to provide an acquirer with a product or service that meets agreed requirements. See detailed description in the INCOSE Handbook v.5, page 48 Prepare for supply See detailed description in the INCOSE Handbook v.5, page 49 Respond to a request for supply of products or services See detailed description in the INCOSE Handbook v.5, page 49 Establish and maintain an agreement See detailed description in the INCOSE Handbook v.5, page 49 Execute the agreement See detailed description in the INCOSE Handbook v.5, page 49 Deliver and support the product or service See detailed description in the INCOSE Handbook v.5, page 49 Accepted system or system element System or system element (product or service) accepted by an acquirer from a supplier consistent with the delivery conditions of the supply agreement. Acquired system or system element System or system element (product or service) delivered to the acquirer from a supplier consistent with the delivery conditions of the acquisition agreement. Acquisition agreement Mutual acknowledgment of terms and conditions under which a working relationship is conducted between an acquirer and a supplier. (Adapted from ISO/IEC/IEEE 15288, 2023). Acquisition payment Payments or other compensations for an acquired system. Acquisition records and artifacts Permanent, readable form of data, information, or knowledge related to acquisition. Acquisition report An account prepared for interested parties in order to communicate the status, results, and outcomes of the acquisition activities. Acquisition strategy and approach Approaches, schedules, resources, and specific considerations required to perform acquisition. Request for supply Acquirer’s request for information and commitments needed from the supplier that are required to be included in the potential supplier’s proposal. It announces the acquirer’s intention to potential bidders to acquire a specified system or system element (product or service). (Adapted from ISO/IEC/IEEE 15289, 2019) Supplied system or system element System or system element (product or service) delivered from a supplier to an acquirer consistent with the delivery conditions of the supply agreement. Supply agreement Mutual acknowledgment of terms and conditions under which a working relationship is conducted between a supplier and an acquirer. (Adapted from ISO/IEC/IEEE 15288++ 2023) Supply records and artifacts Permanent, readable form of data, information, or knowledge related to supply. Supply report An account prepared for interested parties in order to communicate the status, results, and outcomes of the supply activities. Supply response Prepared by a potential supplier to support the offer of a contract bid, including cost, schedule, risk statements, methodology to satisfy the request for supply, experiences and capabilities, any recommendations to tailor the request for supply or contract, and the signature of the supplier's approving authority. Informally, may be prepared within an organization. (Adapted from ISO/IEC/IEEE 15289, 2019) Supply strategy and approach Approaches, schedules, resources, and specific considerations required to perform supply. Variance or deviation or waiver request Request, temporary or permanent, to accept a configuration item or other designated item which, during production or after having been submitted for inspection, is found to depart from specified requirements, but is nevertheless considered suitable for use as is or after rework by an approved method. (Adapted from ISO/IEC/IEEE 24765, 2017) Tailoring As stated in ISO/IEC/IEEE 15288:2023, [Annex A.2.1] The purpose of the tailoring process is to adapt the life cycle processes included in this document [i.e. ISO/IEC/IEEE 15288:2023] to satisfy particular circumstances or factors that: a) surround an organization that is employing ISO/IEC/IEEE 15288 in an agreement; b) influence a project that is required to meet an agreement in which ISO/IEC/IEEE 15288 is referenced; c) reflect the needs of an organization in order to supply products or services. See detailed description in the INCOSE Handbook v.5, page 215 Identify and record the circumstances that influence tailoring Take due account of the life cycle structures recommended or mandated by standards Obtain input from parties affected by the tailoring decisions Make tailoring decisions Select and tailor the affected life cycle processes Organization tailoring strategy and approach Organization specific strategy and approach to tailoring required to incorporate new or updated external standards. Project tailoring strategy and approach Project specific strategy and approach to tailoring required to incorporate new or updated life cycle models. Tailoring records and artifacts Permanent, readable form of data, information, or knowledge related to tailoring. Agreements Agreements from all applicable life cycle processes, including: acquisition agreement and supply agreement. Enabler Enablers represent those typical inputs and outputs that enable, or assist in, the execution of the system life cycle processes. They either come in as an external (EXT) typical input or from one or more life cycle processes. They go into every system life cycle process and are shown in Figure 2.11. --> Not Used in the model, <<enables>> dependency used on BusinessObject (similar to InputTo). Controls Controls represent those typical inputs and outputs that control, or limit, the execution of the system life cycle processes. They either come in as an external (EXT) typical input or from one or more life cycle processes. They go into every system life cycle process and are shown in Figure 2.11. --> Not Used in the model, <<enables>> dependency used on BusinessObject (similar to InputTo). Situational Situational represents those typical inputs and outputs that are situational with respect to the execution of the system life cycle processes (i.e., they are invoked when needed). They can come from any life cycle process. They go into a select number of system life cycle processes, specifically: Decision Management, Risk Management, Configuration Management, Information Management, and System Analysis. Organization strategic plan The overall organization strategy, including the business mission or vision and strategic goals and objectives. Applicable laws and regulations International, national, or local laws or regulations. Standards This handbook and relevant industry, country, military, acquirer, and other specifications and standards. Includes new knowledge from industry sponsored knowledge networks. Enabling systems External systems that facilitate the life cycle activities of the SoI but are not a direct element of the operational environment. Supply payment Payments or other compensations for the supplied system. Source documents External documents relevant to the particular stage of the system of interest. Concept of operations (ConOps) At the organization level, addresses the leadership's intended way of operating the organization (ISO/IEC/IEEE 29148, 2018). Organization portfolio direction and constraints Organization direction and constraints related to the project portfolio. Business plan The overall organization business plan, including the business objectives. Customer satisfaction inputs Responses to customer satisfaction surveys or other instruments. Business or Mission Analysis Stakeholder Needs and Requirements Definition System Requirements Definition System Architecture Definition Design Definition System Analysis Implementation Integration Verification Transition Validation Operation Maintenance Disposal BO_ConstraintsOnSolution BO_RequirementsImposedOnEnablingSystems BO_TraceabilityMapping Project Planning Project Assessment and Control Decision Management Risk Management Configuration Management Information Management Measurement Quality Assurance BO_ChangeRequest BO_Reports BO_Procedures BO_Measurement Needs and Data BO_StrategyAndApproach Life Cycle Model Management Infrastructure Management Portfolio Management Human Resource Management Quality Management Knowledge Management BO_Records and Artefacts Acquisition Supply Tailoring IPO_Enabler&Controls_ALL To_External From_External System Life Cycle Processes