reflects the entire realization of the HW Unit. It contains all information and documents required for manufacturing the HW Unit. Apart from the drawings, this includes part lists, wiring diagrams, etc., also information about parameter settings, adjustments, etc.
The Realization Documents include information about installation, integration, security handling, etc. of the HW Unit which must be generated and specified during the realization.
The Realization Documents contain details concerning installation, integration, security handling etc. of the HW Unit, which were drafted or established as part of the realization.
If required, certain analysis and proof calculation will be made in cases when the requirements for the HW Unit are particularly high. They will be documented in the Analysis Report(s).
The following includes explanations about the use of submodel QA.
HW.3.1 QA Products
The regulations of submodel QA have to be applied to the hardware.
HW.3.2 QA Assessments
As in activity QA4.2 - Assessment of the Content of the Product, special assessments are required for hardware. (This must already be observed on system level.) The assessments are the same for HW Units.
In the "Product" checklists of the Assessment Specification, the following items have to be completed:
- HW Architecture
- Does the HW Architecture meet the user requirements as well as the technical requirements?
- Are the interfaces between software and hardware consistent?
- Does the HW Architecture include the preliminary and detailed design of the HW Components in a sufficiently detailed way?
- Engineering Drawing Set
- Is the set of graphs sufficient in order to be used for the realization or as a plan?
- Documents about Realization
HW.3.3 Design of Assessment Tools
According to expensive assessment tools, the realization should take place in a simplified form and as a separate project, according to the V-Model.
The following contains explanations about the use of the configuration management.
The activities of the project management can also be transferred to the hardware development.
- The configuration management describes regulations that have to be specified not only for this submodel, but also for the entire lifecycle, and have to include the development, production, utilization and maintenance phases.
- Depending on the success of the development, volume and procedure of the CM will be different in order to find a sensible compromise between cost, time and traceability of changes. The possibility to consider the changes in the customer's requirements during the development and to make them comprehensible must be guaranteed by means of appropriate measures, e. g. documentation of related configurations.
In chapter 3.1.4 of the Project Plan, Baselines, baselines must also be defined with regard to "relational configurations) (cf. submodel CM), in case this has been correspondingly specified in higher ranking regulations (e. g. /STANAG 4159/).