5 Part 5: V-Modell Reference Work Products

5.3 Products

5.3.10 System Design

5.3.10.7 System Implementation, Integration and Evaluation Concept

Responsible: System Architect (when using process module System Development)

Activity: Preparing System Implementation, Integration and Evaluation Concept

Participating: System Integrator, Hardware Developer, Software Architect, Safety Manager

Purpose

The »System Implementation, Integration and Evaluation Concept defines the realization and completion process for a system. It provides particularly the »System Integrator and the »Inspector with guidelines for their tasks.

The concept describes procedures, tools and environment for installation, integration and tests of system elements and systems in detail. At system level, the integration is based on the units developed within the scope of hardware and software development and the implementation of external units identified in the architecture. Depending on the complexity of the realization process or the heterogenity of the system to be developed, the concept may cover the entire system development or deal exclusively with the higher hierarchy levels down to unit level. In the latter case, an individual concept will be prepared for the development of Hardware and »Software Units.

The contents of the system implementation, integration and evaluation concept shall be consistent with the corresponding architecture. The design decisions made shall be implemented in a suitable manner. With respect to organization and framework conditions, the concept is determined by specifications in the Project Manual. For the scheduling of the integration and test process, the concept shall be coordinated with the »Integration and Evaluation Plan System Elements in the »Project Plan.

The »System Architect is responsible for the preparation of the concept. He will be supported by the System Integrator, who is finally reponsible for the completed system.

Integration and testing require a balanced strategy with regard to acquirer specifications, available integration and demonstration assets and the minimization of redundancies regarding the necessary compliance demonstration activities.

Normally, the environment to be used will be described in this concept. However, if an environment is required for the long-term support of the system life cycle, the environment shall be realized as independent »Enabling System.

Depending on the evaluation specifications, the test products for the individual system elements will be prepared.

Is generated by

Overall System Specification (see product dependency 4.26)

Project Manual, Overall System Specification (see product dependency 4.27)

Generates

Evaluation Report Usability, Evaluation Specification Usability, Evaluation Report Usability, Evaluation Specification Usability, Hardware Architecture, Hardware Unit, Hardware Specification, Hardware Implementation, Integration and Evaluation Concept, Evaluation Report System Element, Evaluation Procedure System Element, Evaluation Specification System Element, Data Protection Concept, Information Security Concept, Safety and Security Analysis (see product dependency 4.4)

Evaluation Report Usability, Evaluation Specification Usability, Software Implementation, Integration and Evaluation Concept, Software Architecture, Software Unit, Software Specification, Evaluation Report System Element, Evaluation Procedure System Element, Evaluation Specification System Element, Data Protection Concept, Information Security Concept, Safety and Security Analysis (see product dependency 4.15)

Evaluation Report Usability, Evaluation Specification Usability, Market Survey for Off-the-Shelf Products, External Unit, External Unit Specification, Make-or-Buy Decision, Evaluation Report System Element, Evaluation Procedure System Element, Evaluation Specification System Element, Data Protection Concept, Information Security Concept, Safety and Security Analysis (see product dependency 4.20)

Evaluation Report Usability, Evaluation Specification Usability, Evaluation Report System Element, Evaluation Procedure System Element, Evaluation Specification System Element, Segment, System Specification, Data Protection Concept, Information Security Concept, Safety and Security Analysis (see product dependency 4.23)

Depends on

External Hardware Module, Hardware Unit, Hardware Component, Hardware Module, Hardware Implementation, Integration and Evaluation Concept, External Software Module, Software Implementation, Integration and Evaluation Concept, Software Unit, Software Component, Software Module, External Unit, Segment, System (see product dependency 5.38)

Hardware Implementation, Integration and Evaluation Concept, Software Implementation, Integration and Evaluation Concept, Project Plan (see product dependency 5.39)

Hardware Implementation, Integration and Evaluation Concept, Software Implementation, Integration and Evaluation Concept, QA Manual, Enabling System Implementation, Integration, and Evaluation Concept (see product dependency 5.43)

5.3.10.7.1 Realization Procedures and Environment

A system element should be realized within the scope of a suitable environment and a defined realization process. At system level, however, this aspect is of subordinate importance. Realization procedures are mainly executed at hardware and software level.

5.3.10.7.2 Integration Procedures and Integration Plan

Integration procedures specify the integration environment and the integration tools. The integration plan defines the integration architecture and the sequence of the integration steps. It specifies the system element instances to be realized for the system element types defined in the architectures and determines the integration sequence.

For every Hardware or »Software Unit specified in the integration architecture, it will be determined if an independent implementation, integration and evaluation concept must be prepared or if the concept of the higher system specifies the development process down to process module level.

5.3.10.7.3 Installation Procedures and Target Environment

The development process also includes the identification of the required target environment and the description of the installation process. All target environments which may be used by the system in the different development phases shall be identified, and the installation procedures shall be specified. The Project Manual specifies conditions for the target environments to be supported. Frequently specified target environments include, but are not limited to, the development environment, a separate evaluation environment and an integration environment for simulating the final target platform.

The installation procedure and the required tools will be described for every identified target environment. The description of the procedure for installing the system on the target platform is based on the contents of this subject. It will be prepared within the scope of the logisitc »In-Service Documentation and delivered to the acquirer.

5.3.10.7.4 Evaluation Procedures and Strategy

A general evaluation strategy and a concrete test process shall be specified for all system elements. In this connection, economic efficiency, availability of evaluation environments, testability or test duration are important factors.

The test process specifies algorithms, test tools and test methods to be used for executing the tests. The concrete test procesure will be developed in the respective system element evaluation specifications.

The evaluation strategy will be derived from the specifications in the Project Manual and the »QA Manual. It specifies general rules and criteria for the execution of system element tests. Particularly the demonstrations and framework conditions required by the acquirer shall be taken into account for the evaluation strategy.

The evaluation strategy should be examined especially with regard to redundancy and risk reduction and with regard to the availability of existing tools.

5.3.10.7.5 System Elements to be Evaluated

The test of a system element is expensive and not always required. In order to adapt the effort to the requirements of individual projects, the »System Architect shall - based on the specifications in the Project Manual and the specified evaluation strategy - determine which system elements are to be tested.

Critiera for the necessity of a test may include the following: safety and security issues and complexity of the system element and its central role within the system. If system elements are classified as not to be tested, a rationale shall be included.

5.3.10.7.6 Safety and Security Relevant System Elements and Safety and Security Measures

See Safety and Security Relevant System Elements and Safety and Security Measures in product Enabling System Implementation, Integration, and Evaluation Concept.