RE.3.3.13 User Demand



		RE.3.3.13 User Demand (UDem)

Anwenderbedarf

Contents
Introduction
Document Index
Document Structure

Contents		Introduction Document Index Document Structure

Introduction

The actual state and the target state of the software to be processed are described in the product User Demand. It includes possibilities of how to get from the actual state to the target state, and also the results of the investigations about the planned reverse engineering measure and if it can be realized from the technical and economic viewpoint.

This product exists for the system to be processed. If the software to be processed is one single SW Unit then it exists on the SW Unit level.

Document Index

1. General Information
2. Actual Status
3. Current Analysis
4. Possible Solutions
5. Technical Feasibility
6. Economic Efficiency

Document Structure

1. General Information

See schema 1. General Information.

2. Actual Status

All information derived from the actual state inventory is listed here. An explicit representation is possible, or the place it can be found is given. When an appropriate structuring takes place it is practical to differentiate between predominantly software-oriented information-either technical or user-level-or to differentiate between the degree of abstraction of the information. Also, it is helpful, when the relationships between the found information are already shown.

3. Current Analysis

The weak points in the existing source code and in the other existing system and software documentation are illustrated. As far as possible, the cause of the weak points is also explained.

4. Possible Solutions

It is described how the weak points discovered in the current analysis can be eliminated.

5. Technical Feasibility

This describes if the basic Technical Requirements for the realization of the planned reverse engineering measure can be met.

Depending on the number and size of the planned measures it is necessary to clear up if the source code is completely available, if loadable software can be generated from the source code, and if user-level information is sufficiently available.

6. Economic Efficiency

The results of the investigation of economic efficiency for the planned reverse engineering measure are represented.

There are no more subdivisions for product User Demand because this would lead to definitions with regard to the methodical procedure in subactivities that are not intended.

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