 |
 |
 |
|
 |
|||
| RE 3.1: Restoring the System Architecture |
RE3.1 - Systemarchitektur wiedergewinnen
 Contents
|
|
|---|
Product Flow
| From | Product | to | |||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Activity | State | Chapter | Title | Activity | State | ||||||||||||||||||
| External (1) | - | All | Further information (2) | - | -
| RE1.5 |
accepted |
All |
User Demand |
- |
-
| - |
- |
2 |
System Architecture.System Structure |
RE3.2 |
being proc.
| - |
- |
All |
Operational Information : |
User Manual Diagnosis Manual Operator Manual Other Application Information RE3.4 |
being proc.
| |
Handling
This activity recovers the technical structure of the system, based on further information (at best configuration documents) and by using the information from product User Demand. Since normally the term "segment" is not applied for existing systems, the system is described as directly structured into SW Units, HW Units, and non-IT parts.
The results from this activity are documented in the product System Architecture.System Structure. The technical system structure is integrated into the Information for the Operator Manual . Information about the diagnosis environment and diagnostic measures are documented in the Diagnosis Manual.
Notes (1) Customer
(2) Existing system and software documentation, at best existing configuration documents.
|
|
|
GDPA Online
Last Updated 01.Jan.2002
Updated by Webmaster
Last Revised 01.Jan.2002
Revised by Webmaster
|