Please enable JavaScript.

Coggle requires JavaScript to display documents.

IVV (Integration (Plan (Purpose of the plan and concerned system and/or…

- - - - Advantages: No need for drivers/launchers to simulate absent system elements for verification purposes
      - Disadvantages: Interface errors are detected late; it may be difficult to detect, diagnose and locate remaining errors/faults/defects/flaws in the global system; expensive and inefficient to fix any issues.
      - "Big-bang integration". All the delivered implemented system elements are assembled in only one step; after each implemented system has been verified individually, the system elements are integrated concurrently
      - Application: Should be reserved for simple systems, with few interactions and few system elements, where technological risk is low
    - - The delivered implemented system elements are assembled as they become available, after each implemented system element has been verified individually
      - Advantage: Allows quick start of the integration
      - Disadvantage: Necessitates a lot of drivers/launcher to stimulate absent system elements; not efficient with respect to technical, means and cost aspects because it requires modification of the integration plan every time a system element is integrated
      - Application: Should be reserved for well-known and controlled systems without technological risk
    - - In a predefined order, one or few implemented system elements are added to an already integrated increment of system elements
      - Advantages: Allows for early detection of interface errors, and facilitates locating remaining errors/faults/defects/flaws in the new increment.
      - Disadvantages: Necessitates a certain number of drivers/launchers to stimulate absent system elements
      - Application: Applies to any type of system architecture
    - - Implemented system elements are assembled by subsets( a subset is an aggregate), and then subsets are assembled together.
      - Advantages: Parallel integration of aggregates or (sub) systems is possible;
      - Constraint: Necessitates a system architecture defined with (sub) systems; applies well to products with functional or transactional chains
      - Application: Applies to system architectures composed of (sub) systems; applies well to products with functional or transactional chains
    - - Starts with system elements related to the overarching framework of the SOI; continues with system elements performing core or detailed functions/transformations of the system; ends with system elements performing more detailed functions or close to acquisition (from sensors) and distribution or physical commands(onto actuators).
      - Advantage: Early availability of a skeleton of the system that allows detecting and easily locating remaining errors/faults/defects/flaws; test cases for verification actions are close to reality; does not need many drivers
      - Disadvantage: A lot of stubs to create; difficult to check efficiently and exhaustively at the lowest level system elements and interfaces with test cases from the operator's /users level.
      - Application: Mainly used in intensive software systems, or in systems with human operators or users that pilot or interface with command-control (sub) systems.
    - - Starts with system elements performing very detailed functions or dealing with acquisition(from sensors) and distribution or physical commands( onto actuators); continues with system elements performing detailed or core functions of the system; ends with system elements related to overarching framework of the SOI
      - Advantage: No or few stubs to create; early detection of implementation errors/faults/defects/flaws; test cases to check interfaces and functions are easy to define.
      - Disadvantage: Lower level system elements are solicited a lot of higher test cases; absent system elements from the upper levels are replaced by drivers/launchers to be created
      - Application: This is physically the only way to integrate hardware; also applies to software intensive systems.
- - - - Logical Aspect
        
        The input-output flow and the function that carries it
        
        Logical Interface consists of an input flow, an output flow or a bi-directional flow between two functions of the system so that they may exchange material, energy and/or information
      - Physical Aspect
        
        The physical link, made of technology, that transports the input-output flow
        
        Physical interface is the physical link or port that binds two system elements within the SOI or one system element of the SOI with an element external to the SOI. A physical interface may be considered a system element.
- - - - Study and identify potential emergent behaviours or properties(expected or unexpected) that may happen when integrating system elements. This has to be carried out to avoid late detection, in particular, of threats or hazards that could be generated by the system due to interations of system elements
      - The definition of interfaces is concerned with integration; the physical aspects of interfaces(physical connection) are concerned with assembly of system elements; the logical aspects of interfaces(input-output flows and interactions) are concerned with functions performance of integration aggregates(sets of system elements)
      - Architectural characteristics such as modularity facilitate the integration
      - The integration of the system in the context of use(existing environment) influences the interface definition;
      - From the integration strategy definition, provide feedback and recommendations through analysis of logical and physical models of concerned system to possibly ease the future integration
      - When errors/faults/defects/flaws concerning architecture( in particular with interfaces) have been identified during performance of the integration process, the architecture definition process corrects the concerned architecture items.