AY 2024 Systems Integration - SEM4607 PDF

SIT Internal SEM4607 Systems Integration, Verification & Validation Topic 03: Systems Integration AY 2024/25 TRI 2 Assoc Prof Ng Bor Ki...

SIT Internal SEM4607 Systems Integration, Verification & Validation Topic 03: Systems Integration AY 2024/25 TRI 2 Assoc Prof Ng Bor Kiat Adj Assoc Prof Harry Lim [email protected] SEM4607 - AY2320  SIT Internal Systems Integration, Verification and Validation Module Outline 1. Systems Engineering Overview 5. Industry Application Sharing 2. Systems Engineering Process Fundamentals Requirements 4. Verification & Validation Architecture 3. Systems Implementation & Integration Design Specifications [Source: https://en.wikipedia.org/wiki/V-Model] V-Model System Development Process  SIT Internal Systems Integration: Introduction In the engineering of new complex systems with many interacting components, testing at the system level cannot begin until the system has been fully assembled and demonstrated to operate as a unified whole. The likelihood that some of the interfaces among the elements may not fit or function properly, or that one or more interfaces among them may fall outside prescribed tolerances, is usually high. It is only the very simplest systems that are assembled without testing at several intermediate levels of aggregation. Thus, experience has shown that no matter how thoroughly the individual components have been tested, there are almost always remaining unforeseen incompatibilities that do not reveal themselves until the system elements are brought together. Such discrepancies usually require changes in some components before the integrated system works properly. These changes, in turn, frequently require corresponding alterations in test equipment or procedures and must be reflected in all relevant documentation. [Source: System Engineering: Principles and Practice, Andrew P. Saga]  SIT Internal Outline: Topic #3 Systems Implementation & Integration System Interface System Configuration System Level Integration Process activities Example of RTS Integration  SIT Internal Systems Implementation ISO/IEEE 15288: The purpose of the implementation is to realize a specific system element. Implementation Process: Creates and fabricates system element (hardware/software) conforming to that element’s detailed description (e.g. system design document: Requirement allocated, interfaces etc) Product development team carry out fabrication, make sure individual element meets specified materials, processes, standards required in the design document. The design concept is realized during the system implementation phase. If the system is a hardware-based system, this implementation is only a prototype (i.e., the first instance of the system built) that must be reproduced during the system Production phase. At the completion of the system Implementation phase, all individual components of the overall system should be available and functioning. During system implementation, IV&V efforts are directed toward those emerging subsystems, their verification against system requirements and their refinement. As requirements are verified with respect to implemented components, they should also be validated against stakeholder needs. This validation should be a continuous process. Whenever subsystem or component definition and specificity permit, the associated requirements should be validated.  SIT Internal Systems Integration ISO/IEEE 15288: 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. Integration process: Progressively assembling the implemented system elements that compose the SOI and verifying the correctness of interfaces between the implemented system elements. Strong focus on the interfaces to ensure the intended operation of the system elements and interoperation with other systems. Integration process work closely with V&V processes and iterated with the V&V processes: Verification process to check the correct implementation of architecture characteristics and design properties. Validation process to check that individual system elements provide the function intend.  SIT Internal Integration Process Integration Phase IPO Diagram Systems Interface Developmental Configuration [Source: INCOSE SEH Figure 4.12]  SIT Internal Inputs to Integration Process: 1. Systems Interface 2. Systems Configuration  SIT Internal Systems Interface What are systems interfaces ? Subsystem #1 Subsystem #2 Systems / subsystems are boxes.. Interfaces are connecting lines.. but they are important part of entire system and they form the system architecture. Interface are more than “lines connecting the boxes” and they are components of a system or product. 10  SIT Internal Example of Interfaces Mechanical Electrical Software 11  SIT Internal Interface Management: Motivation  SIT Internal Systems Interface: Questions Who owns the interface ? How the interface is being managed ?  SIT Internal Interface Ownership Project Manager vs System Engineer System engineer has to establish accountability for the technical work to be performed, take technical leadership. Without technical leadership, there will be lack of compatibility and interoperability resulting to chaos and conflicts. Interfaces ownership implies being accountable for specification, design implementation and its control. If upgrading an existing (legacy) system, the existing system may dictate the interface requirement for the new system upgrade.  SIT Internal Interface Management Interface management includes the activities of defining, controlling, and communicating the information needed to enable unrelated objects (including systems, subsystem, equipment, software, and data) to function together. Most new systems or services require external interfaces with other systems or services. All of these interfaces must be defined and controlled in a way that enables efficient use and change management of these systems or services. Practice of interface management begins at design and continues through operations and maintenance. Convenient to distinguish three different types: 1) Connectors: Transmission of electricity, fluid, force, and so on, between components; 2) Isolators: Inhibit of interactions 3) Converters: Alter the form of the interaction medium.  SIT Internal Interface Management: ICD Interface management is done through an Interface Control Document (ICD) for hardware interfaces and Interface Design Description (IDD) for software interfaces. ICD / IDD records all interface information (such as drawings, diagrams, tables, and textual information), details and describe the interface or interfaces between subsystem or to a system or subsystem. Software Interface Electrical Interface Mechanical Interface  SIT Internal Interface Management Process Example Source: NASE SE Handbook)  SIT Internal Systems Developmental Configuration From moment of system inception, stakeholders, developers and others beginning making system development decisions that evolves over time. Must capture the state of the evolving system design solution that represents a “snapshot in time” of technical decisions, such as stakeholder operational needs, use cases, required operational capabilities, physical implementation etc. As system evolve and mature at key staging points throughout the system life cycle phases, review, documentation (e.g. specifications, architecture, designs, drawings etc) , prototypes, models, simulations.. evidence information evolves and they represent time-dependent interactions of operational, physical entities or components that require unique configuration identification, version and time stamp: Configuration A, Version 1.1, Month/Day/Year. Developmental configuration of the system or product evolves as technical reviews are conducted throughout the project. A Configuration Manager define a strategy that identifies when and how the developmental configuration if the evolving system design solution and configurations will be identified, captured, reviewed, approved, baselined, release and controlled. These are documented as part of System Engineering Development Plan and Configuration Management Plan.  SIT Internal Configuration What is configuration ?  SIT Internal Configuration Management (CM) Configuration Management Process for establishing and maintaining consistency of a product's performance, functional, and physical attributes with its requirements, design, and operational information throughout its life. Practice of handling changes systematically so that a system maintains its integrity over time. Configuration Item Configuration Item (CI) is the basic building block (element). Each CI characteristics and interfaces to other building blocks is defined and controlled to ensure its proper operation within the system as a whole. Distinguish between Hardware Configuration Item (HWCI) and Computer Software Configuration Items (CSCI) because of basically different processes used in defining and controlling their design.  SIT Internal Configuration Items (CI) HWCI / CSCI CI Records CM Tools (Source:http://www.qstar2k.co.uk/config uration_management.html#!prettyPhoto)  SIT Internal Configuration Baselines Configuration Baselines A baseline is a reference point in the development life cycle marked by the completion and formal approval of a set of predefined work products. The objective of a baseline is to reduce a project’s risk to uncontrolled change by fixing and formally change controlling various key deliverables at critical points in the development life cycle. Baselines are also used to identify the aggregate of software and hardware components that make up a specific release of a system. A stable reference for future work.  SIT Internal Configuration Baselines Different configuration baselines in system engineering process:  SIT Internal Configuration Change Control During system development, there is a needs for flexibility in configuration change. Price to pay for the change as changes affect related sub-systems and a great deal of system engineering analysis, test and evaluation is required. When system configuration is frozen, and formal changes control procedures are imposed to deal with the modifications. (Typically it is imposed after successful completion of CDR) Engineering Change notice is required. It is a document authorizing and recording design changes and contains the justification for changes made to a component or system. This is to ensure traceability from one configuration baseline to another. Change control process – Engineering Change Proposal (ECP)  SIT Internal Engineering Change Proposal (ECP) Configuration Manager Report System Engineer 26  SIT Internal Integration Process Activity: Integration Readiness Review 1. Prepare Integration 2. Perform Integration 3. Manage Results of Integration  SIT Internal Prepare Integration Define critical checkpoints to provide assurance of the correct behavior and operation of interfaces and functions of the system elements. What are checkpoints ? Establish the integration strategy that minimizes integration time, costs and risks with an optimized sequence order of assembly for system elements based on the system architecture, integration approach and techniques. Bottom up, top down, big bang, incremental. Usage of simulators, virtual hardware-in-loop simulators, software testers. Identify integration constraints Location, safety, availability Acquisition of the enablers Rental, development or acquisition (often long lead time items / qualification required) of enablers. Example of enablers: tools or facilities  SIT Internal Integration Readiness Review Conduct of integration readiness review before the conduct of the actual integration to ensure all system elements and integration environment are ready (available, verified and configured) to start integration. Example of required documents: ❖ Integration Plan ❖ Integration Procedures ❖ System element requirement specifications ❖ System element description documents ❖ System element interface descriptions ❖ Manual of test environment  SIT Internal Example of System Integration Documents (Source: System Integration, verification and Validation, Airbus)  SIT Internal Perform Integration Successively integrate system element configurations (System Configuration Items) until the complete system is synthesized. E.g. For bottom-up integration strategy, begin with Part level into higher levels of abstraction: Part, sub-assembly, Assembly, Sub-system, Product. Assemble the verified and validated system elements to form the incremental aggregate using the defined assembly procedures, the related integration enabling systems and the ICDs. Invoke the system V&V process to check the assembled system for their correct functioning and correct implementation of architectural characteristics and design properties / requirements. 3 1  SIT Internal Example of Systems Integration Strategy  SIT Internal Manage Results of Integration Identify and record the results of integration. Updated integrated system elements with updated system architecture, design, system and interfaces requirements. Maintain the record of configuration updates (new baseline). Record anomalies observed during integration process such as corrective actions or improvements. Update the integration strategy and schedule according to the progress of the project. Coordinate integration activities with the programme manager for scheduling, configuration manger for version, baselines etc.  SIT Internal Summary: V-Model Focus on middle and moving to right hand side on the Implementation and Integration: System Interfaces System Configuration Integration Process activities [Source: RTB#3]  SIT Internal SIT Internal Johor Bahru–Singapore Rapid Transit System (RTS) 2 https://en.wikipedia.org/wiki/Johor_Bahru%E2%80%93Singapore_Rapid_Transit_System  SIT Internal SIT Internal Project Problem Statement: SEEMS cohort students have started a systems engineering consultancy company (ABC) in Singapore to carry out a domain analysis and stock take of the RTS progress. The problem statements call for ABC to carry out the consultancy services in 2 phases: In Phase 1 (project 1 requirement): ABC is to review the requirement statements, conceptualisation and business case considerations, responsibility and requirement allocation, systems architecture design, systems integration requirements etc. of the project, and to make early observations and recommendation on the need and areas where validation of the project requirements may be needed. In Phase 2 (project 2 requirement): ABC is to propose a project systems integration, validation and verification (SIV&V) plan by highlighting the importance and functionality and criticality of the major sub- systems listed below, and areas where verification tests should be carried out to ensure the systems interoperability, performance, reliability, availability, maintainability and safety etc. of these sub systems so that the RTS can perform and deliver the services to meet the requirements as an integrated system- of-systems. Major RTS sub-systems 1. Rolling stock system 2. Signalling system 3. Communication system 4. Permanent way systems 5. Power supply system