 |
 |
 |
|
 |
|||
| RE 4.1: Restoring the User Requirements |
RE4.1 - Anwenderforderungen 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 |
- |
-
| - |
- |
All |
User Requirements |
RE4.2 |
RE5.1 RE5.2 RE8.2 RE9 External (1) submitted
| |
Handling
This activity restores the requirements that are met by the system (or the SW Unit, in case the subject of the order is one individual SW Unit) from a user-level point of view.
Since it will normally not be possible to derive the required information from the source code it is necessary to get the information by evaluating all available user-level information sources. This can include the reading of all available documents containing information about the user-level system aspects and also interviewing the persons with special know-how of the system.
The objective of this evaluation is to obtain the user-level structure of the system function as seen from the user's point of view, whereby the total function of the system must be described as "business processes" that are classified into "areas" (e. g. "Mailing and Communication", "IT Security", "Man-Machine Interface" or "Office Functions").
The results of this activity are documented in the product User Requirements.
Notes (1) Customer
(2) Existing 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
|