 |
 |
 |
|
 |
|||
| RE 1.3: Definition of Possible Solutions |
RE1.3 - Lösungsvorschläge formulieren
 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 - |
-
| RE1.2 |
being proc. |
3 |
User Demand. |
Current Analysis - |
-
| - |
- |
4 |
User Demand. |
Possible Solutions RE1.4 |
RE1.5 being proc.
| |
Handling
In this activity it is investigated and specified how the weak points detected during an actual state analysis can be eliminated. The following typical reverse engineering activities might be appropriate:
- reformatting the source code to improve the layout,
- restructuring the sequence structures, e. g. by taking into consideration the principles of structured programming,
- rationalization of data, e. g. by eliminating redundancies,
- recommenting the source code from a user-level point of view,
- remodularization to improve the software architecture,
- restoring and documenting the technical viewpoint (e. g. SW Design: Module, SW Design: Database, SW Architecture, Technical Requirements),
- restoring and documenting the user-level viewpoint (User Demand).
The results of this activity are documented in the product User Demand.Possible Solutions.
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
|