[ASEP-Prep] #5. Technical Processes – System Realization, Deploy and Use

Technical Processes part 2

4-7 Implementation Process

According to the ISO/IEC/IEEE 15288 standard, the purpose of the implementation process is to realize specific system elements. This process involves activities not only at the production stage but also at other stages to ensure that the elements can be produced and prepare them for one stage of production or another. For example, supporting infrastructure may need to be defined or upgraded for a particular phase of activity.

During the implementation process, engineers follow assigned and derived requirements to fabricate, code, or build each individual element described in the system element description. Requirements of system elements are verified and stakeholder requirements are validated. If subsequent configuration audits uncover inconsistencies, iterative, recursive interaction with preceding activities or processes takes place, as necessary, to correct the problems. The process is based on the design and architecture of system elements and their actual implementation, including defined interfaces.

  • IPO
This image show IPO diagram of Implementation Process that is one of Technical Processes

4-8 Integration Process

According to the ISO/IEC/IEEE 15288 standard, the integration process aims to synthesize system elements into a realized system that satisfies the system requirements. This process assembles system elements such as hardware, software, and operational resources and verifies the static and dynamic aspects of the interfaces and interactions between them. We proactively address potential integration issues early in the project through modeling, analysis, and simulation, and prevent problems that may arise during system realization through early interaction with the system definition process. The integration process is closely linked to the Verification and Validation (V&V) process and includes assessing the maturity of elements to be integrated, verifying the correct implementation of system requirements and architecture, and confirming whether stakeholder needs are met. This process also ensures that the boundaries between all system elements are correctly identified and described, and reviews that all functional and performance requirements are met.

  • IPO
image 29

4-9 Verification Process

According to the ISO/IEC/IEEE 15288 standard, the purpose of the Verification process is to demonstrate by objective evidence that a system, system element, or artifact meets specified requirements and characteristics. This process can be applied to a variety of engineering artifacts, including stakeholder requirements, system requirements, models, simulations, architectures, design characteristics, and verification procedures. The key checks are whether the deliverables are produced precisely according to requirements, whether defects were introduced during the conversion process, and whether the verification method selected can effectively detect anomalies. Verification ensures that the product was built exactly as designed, while validation ensures that the product was actually built as needed. This is an essential step in developing a reliable product.

  • IPO
image 30

4-10 Transition Process

According to the ISO/IEC/IEEE 15288 standard, the transition process aims to establish the ability of the system to provide services that meet the requirements of stakeholders in its operational environment. This process integrates the system as part of the organization’s systems, business processes, and capabilities, enabling the organization to benefit from the use and maintenance of system services. The transition process is coordinated with verification and validation activities in the operational environment and coordinates operation and maintenance activities for new systems and services. It also involves the disposal of systems and resources that are no longer needed. This process identifies gaps in system requirements and design, and drives changes to initial stakeholder and system requirements as needed. It helps organizations efficiently integrate systems and meet the needs of end users.

  • IPO
image 31

4-11 Validation Process

According to the ISO/IEC/IEEE 15288 standard, the purpose of the validation process is to demonstrate by objective evidence that the system meets business or mission objectives and stakeholder needs and requirements when used in practice. This process ensures that appropriate deliverables or entities tailored to stakeholder needs can achieve their objectives in the intended operating environment when realized. Validation verifies: 1. that an appropriate artifact or entity has been created, 2. that this artifact can achieve its purpose when operated by the intended users, and 3. that the system is free from unintended uses. can protect it. Verification ensures that the product was manufactured as intended, while validation ensures that the product is the correct product. This is an important step in evaluating the actual performance of your system.

  • IPO
image 32

4-12 Operation Process

According to the ISO/IEC/IEEE 15288 standard, the purpose of the operational process is to utilize the system to provide services. This process focuses on service delivery of the system to benefit the operating organization and is often parallel to the maintenance process. In operation, systems act as a critical part of the organization, collaborating with human operators and other systems to contribute to business or mission analysis. This process can identify gaps in the system’s requirements and design, supplement the initial requirements and drive changes as needed.

  • IPO
image 33

4-13 Maintenance Process

According to the ISO/IEC/IEEE 15288 standard, the purpose of the maintenance process is to ensure that the system continues to maintain its ability to provide service. This process focuses on ensuring that the system can continue to provide services to the operating organization and is often parallel to the operational process. Maintenance includes operational support, logistics, and material management to ensure that the system’s services continue to maintain satisfactory quality, performance, and availability. This process can identify gaps in the system’s requirements and design, drive necessary changes, and complement initial stakeholder and system requirements.

  • IPO
image 34

4-14 Disposal Process

According to the ISO/IEC/IEEE 15288 standard, the objectives of the disposal process are to terminate the existence of a system or system element for its specified use, appropriately dispose of replaced or retired elements, properly manage waste, and appropriately address critical disposal requirements. It’s about dealing with it. This process generates requirements and constraints that balance stakeholder needs and desires and design considerations, including environmental considerations. The disposal process is applicable at any point in the life cycle, returns the environment to an acceptable state and ensures environmentally sound disposal of all system elements and waste, subject to legal and organizational constraints. Additionally, we document required disposal activities and maintain records to support external oversight or monitoring by regulatory agencies.

  • IPO
image 35


[ASEP-Prep] #1. What is System LIFE CYCLE?

[ASEP-Prep] #2. Agreement and Enabling Processes

[ASEP-Prep] #3. Technical Management Processes

[ASEP-Prep] #4. Technical Processes – Concept and System Definition

[ASEP-Prep] #6. Quality Characteristics

[ASEP-Prep] #7. SYSTEMS ENGINEERING ANALYSYS AND METHODS

[ASEP-Prep] #8. SE METHODOLOGY CONSIDERATIONS

Leave a Comment