 |
 |
 |
|
 |
|||
| RE 1.2: Recording of Current Analysis |
RE1.2 - Ist-Analyse durchführen
 Contents
|
|
|---|
Product Flow
| From | Product | to | |||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Activity | State | Chapter | Title | Activity | State | ||||||||||||||||||
| External (1) | - | All | Available source code | - | -
| External (1) |
- |
All |
Further information (2) |
- |
-
| RE1.1 |
being proc. |
2 |
User Demand. |
Actual Status - |
-
| - |
- |
3 |
User Demand. |
Current Analysis RE1.3 |
RE1.4 RE1.5 being proc.
| |
Handling
In the actual status analysis, the actual status of the existing source code and all other available system and software documentation is assessed from reverse engineering aspects. In this connection, weak points in the source code are detected, which might be improved by means of the planned reverse engineering measures, for example
- in the SW Architecture,
- in the sequence and data structures,
- in the layout and
- in the commenting,
- missing documents,
- incomplete documents or
- deviations from the current status of the software.
The results of this activity are documented in the product User Demand.Current Analysis.
Notes (1) Customer
(2) Other system and software documentation and all other available information.
|
|
|
GDPA Online
Last Updated 01.Jan.2002
Updated by Webmaster
Last Revised 01.Jan.2002
Revised by Webmaster
|