HW.6.2 HW Architecture



		HW.6.2 HW Architecture (HwArc)

HW-Architektur

Contents
Introduction
Document Index
Document Structure

Contents		Introduction Document Index Document Structure

Introduction

In the HW Architecture, the decomposition of the HW Unit into single logical blocks, the individual HW Components and the HW 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.

Document Index

Document Structure

1. General Information

1. General Information
2. Solution Proposals
3. Structure of the HW Unit
3.1 Overview of the HW Components/HW Modules of the HW Unit
3.2 Criticality of the HW Components/HW Modules
3.3 Bridge Plan
3.4 Address Map
3.5 Content of Programmable Components
3.6 User References
3.7 Individual Descriptions
4 Allocation of Requirements
A Appendix
See schema 1. General Information.

2. Solution Proposals

This section contains a description as well as an evaluation of possible HW Unit architectures. Solution proposals for the architecture of HW Units are illustrated. They roughly describe the decomposition of the HW Unit into processes, HW Components and HW Modules. The advantages and disadvantages are illustrated for each individual solution proposal (e. g. with regard to performance input and output, reusability, etc.); the feasibility is illustrated as well. The selection of a solution proposal is documented and explained.

3 Structure of the HW Unit

The modularization reports on the decomposition of a HW Unit in HW Components and HW Modules. This section also contains a preliminary design (block diagram) of the HW Unit. Timing diagrams or sections of the flow diagram are included in order to explain the text sections.

3.1 Overview of the HW Components/HW Modules of the HW Unit

All HW Modules/HW Components are listed together with their identifiers and with a long name. Apart from this a graphical representation (block diagram) should be selected that illustrates the "consists-of" hierarchy.

3.2 Criticality of the HW Components/HW Modules

Each HW Component/HW Module is allocated a criticality level in the form of a table. The criticality level is derived from the criticality of the function realized in the HW Component/HW Module.

3.3 Bridge Plan

This contains the description of the bridge versions (e. g. jumpers).

3.4 Address Map

The allocation of the address area of the HW Unit with individual functions is illustrated.

3.5 Content of Programmable Components

Logical equations of the individual programmable components are structured into sub-items.

3.6 User References

Characteristic features in connection with the use of this HW Unit in a device or in other, already existing HW Units. A description of insertion versions and information about wiring are also included.

3.7 Individual Descriptions

Each HW Component and each HW Module are individually described. In order to make the text sections more clear, timing diagrams or flow diagram sections are included as well.

3.7.m HW Component or HW Module (m) Note: "m" is used for giving HW Components or HW Modules consecutive numbers.

3.7.m.1 Description of the HW Component/HW-Module The HW Component/the HW Module is defined by a short performance description and the utilized resources.

3.7.m.2 Characteristics

3.7.m.2.1 Mechanical Characteristics

List of the most important mechanical data (e. g. measurements, jumpers).

3.7.m.2.2 Electrical Characteristics

List of the most important electrical data (performance requirements, temperature).

4 Allocation of Requirements

The relationship to the hardware requirements will be defined. It must be documented if all requirements can be met and how the requirements can be broken down to HW Components/HW Modules.

A Appendix

Bibliography and reference to data manual, descriptions and other documents.

GDPA Online Last Updated 01.Jan.2002 Updated by Webmaster Last Revised 01.Jan.2002 Revised by Webmaster