 |
 |
 |
|
 |
|||
 |
HW.1 Activities of Hardware Generation (SD 4-HW to SD 7-HW)
Activities of Hardware Generation (SD 4-HW to SD 7-HW)
Hardware development within the scope of the V-Model is based on activities at system level and segment level and also on activities that are relevant for each HW Unit:
- SD 4-HW: HW Preliminary Design
- SD 5.1-HW: Generation of Detailed Designs for HW Components/HW Modules
- SD 6-HW: HW Realization
- SD 7-HW: HW Integration
HW.2 Products of the Hardware Generation
HW Architecture, set of graphs, Realization Documents, and Analysis Report are combined for hardware products. This also includes Hardware Requirements that are representing part of the Technical Requirements.
The product design for these products is listed in section HW.6 Product Schemas, together with the explanations.
HW.2.1 Hardware-Requirements (as part of the Technical Requirements)
The Hardware Requirements cover all requirements made of the HW Unit which are relevant for the design, realization and later use. With respect to the last named aspect in particular the requirements made of assessability and maintainability requirements are formulated as well.HW.2.2 HW Architecture
In the HW Architecture, the decomposition of the HW Unit into single logical blocks, the individual HW Components and the Modules and the functionality and interaction of these parts is described. In the requirements allocation what is shown is which design elements cover which requirements.The HW Architecture contains the results of both the preliminary and the detailed design of the HW Unit.
HW.2.3 Engineering Drawing Set
TheHW.2.4 Realization Documents
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.
HW.2.5 Analysis Report
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).
HW.3 Submodel Quality Assurance (QA)
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 Engineering Drawing Set consistent with the HW Architecture?
- Is the set of graphs sufficient in order to be used for the realization or as a plan?
- Documents about Realization
- Are the Realization Documents consistent with the Engineering Drawing Set and HW Architecture?
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.
HW.4 Submodel Configuration Management (CM)
The following contains explanations about the use of the configuration management.
- 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.
HW.5 Submodel Project Management (PM)
The activities of the project management can also be transferred to the hardware development.
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/).
HW.6 Product Schemas
|
|
|
This page online • GDPA Online • Last Updated 03.Mar.2004 by C. Freericks |