5 Part 5: V-Modell Reference Work Products

5.3 Products

5.3.10 System Design

5.3.10.9 Hardware Implementation, Integration and Evaluation Concept

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

Activity: Preparing Hardware Implementation, Integration and Evaluation Concept

Participating: Hardware Developer, Safety Manager

Purpose

The »Hardware Implementation, Integration and Evaluation Concept defines the developoment and completion process for the »Hardware Unit of the system. It provides particularly the »Hardware Developer and the »Inspector with guidelines for their tasks.

The concept describes design guidelines, documentation specifications, procedures, tools and environments for the implementation, installation, integration and testing of hardware elements in detail. This includes the description of the generation and compilaiton of source files (e.g. VHDL Code) and loading and installation procedures for programmable logic.

The contents of the hardware implementation, integration and evaluation concept shall be consistent with the »Hardware 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.

The »Hardware Architect is responsible for the preparation of the system. He will be supported by the Hardware Developer who is finally responsible for the completed system. Depending on the quality assurance specifications, the test products for the individual hardware elements will be prepared.

Is generated by

System Implementation, Integration and Evaluation Concept, System Architecture (see product dependency 4.4)

Enabling System Implementation, Integration, and Evaluation Concept, Enabling System Architecture (see product dependency 4.5)

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

Generates

Evaluation Report Usability, Evaluation Specification Usability, Hardware Component, Hardware 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.6)

Evaluation Report Usability, Evaluation Specification Usability, Market Survey for Off-the-Shelf Products, External Hardware Module, External Hardware Module 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.7)

Evaluation Report Usability, Evaluation Specification Usability, Hardware Module, Hardware 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.8)

Depends on

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

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

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

5.3.10.9.1 Realization Procedures and Environments

The programmable logic of a »Hardware Unit should be realized in a suitable environment within the scope of a defined development process.

Tools, like cutting machines or CAE synthesis tools, and command procedures for compiling and binding programmable logic shall be defined.

The realization process and realization environment do not describe the production of »Hardware Modules.

5.3.10.9.2 Integration Procedures and Integration Plan

The architecture of a »Hardware Unit specifies the required hardware element types and the structure of the hardware unit. For integration planning, the concrete hardware elements to be developed and the integration sequence shall be derived from the »Hardware Architecture, and a suitable integration process shall be defined.

Integration procedures specify the integration environment and the integration tools. This includes, but is not limited to, the description of the soldering process, assembly and activation. In addition informal, functional, environmental and EMC tests will be described, and test tools will be specified.

The integration plan defines the integration architecture and the sequence of the integration steps. It specifies the hardware elements to be realized for the hardware element types defined in the hardware architecture and determines the integration sequence.

5.3.10.9.3 Installation Procedures and Target Environments

The development process also includes the identification of the required target environment and the description of the installation process. All target environments for the programmable logic of a »Hardware Unit shall be identified, and the installation procedures shall be specified. The Project Manual specifies conditions for the target environments to be supported.

In hardware development, target environments are hardware elements, like storage or logic process modules. Target environments may include 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.9.4 Evaluation Procedures and Strategy

A general evaluation strategy and a concrete test process shall be specified for all hardware elements. In this connection, economic efficiency, availability of test facilities, 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 evaluation procedure will be developed in the respective hardware element evaluation specifications.

The evaluation strategy will be derived from the evaluation strategy in the higher implementation, integration and evaluation concept and the specifications in the Project Manual and the »QA Manual. It specifies general rules and criteria for the execution of hardware element tests. Particularly the demonstrations and framework conditions required explicitly by the acquirer shall be taken into account in 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.9.5 Hardware Elements to be Evaluated

The evaluation of a hardware element is expensive and not always required. In order to adapt the effort to the requirements of individual projects, the »Hardware Architect has - based on the specifications in the Project Manual and the specified evaluation strategy - the possibility to determine which hardware elements of the »Hardware Unit shall be evaluated. Critiera for the necessity of an evaluation may include the following: criticality and complexity of the hardware element and its central role within the hardware unit. If hardware elements are classified as not to be evaluated, a rationale shall be included.

5.3.10.9.6 Safety and Security Relevant Hardware Elements and Safety and Security Measures

For every hardware element, it shall be determined if it has a risk potential, how high is this risk potenital, to which safety and security level it belongs and whether the execution of a hazard and safety analysis is required. The safety and security requirements to be fulfilled will be derived from the »Hardware Specification of the hardware element.

Hardware elements critical for safety and security are elements which are of critical importance for fulfilling the safety and security requirements, i.e., the risk assessment/danger potential of which exceeds a prespecified threshold level.