 |
 |
 |
|
 |
|||
| RE 5.1: Allocation of User-Level Functional Units to Technical Functional Units |
RE5.1 - Allocation of Anwender-Level Funktionale Einheit to Technical Funktionale Einheit
 Contents
|
|
|---|
Product Flow
| From | Product | to | |||||||||||||||||||||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Activity | State | Chapter | Title | Activity | State | ||||||||||||||||||||||||||||||||||||
| RE2.3 | being proc. | All | Implementation Document: SW Module | - | - | ||||||||||||||||||||||||||||||||||||
| All | 
SW Module |
||||||||||||||||||||||||||||||||||||||||
| All | Implementation Document: Database | ||||||||||||||||||||||||||||||||||||||||
| All | 
Database |
||||||||||||||||||||||||||||||||||||||||
| RE3.2 | being proc. | 2 | System Architecture. System Structure |
- | -
| RE3.4 |
being proc. |
2 |
Software Architecture. |
Modularization/Database Design - |
-
| RE4.1 |
accepted |
All |
User Requirements |
- |
-
| - |
- |
2.1.3 |
System Architecture. |
Requirements Allocation RE5.1 |
being proc.
| - |
- |
All |
System Architecture |
RE9 |
External (1) submitted
| - |
- |
4 |
Software Architecture. |
Requirements Allocation RE5.1 |
being proc.
| - |
- |
All |
Software Architecture |
RE9 |
External (1) submitted
| |
Handling
This activity illustrates the relationships existing between the functional units from the user-level point of view and the functional units from the technical point of view.
For example, this allocation my be made when the source code is temporarily instrumented in an appropriate way, i. e. when it is upgraded by additional statements for the collection of information and when loadable software is generated from the instrumented source code. If the user now executes certain user-level tasks with this software by using the instrumented software it is possible to find out which technical functional units participated in the execution of a user-level task.
The results of this activity are used to set up the traceability of the requirements. The are documented in subproducts System Architecture.Requirements Allocation and Software Architecture.Requirements Allocation.
Note: (1) Customer
|
|
|
GDPA Online
Last Updated 01.Jan.2002
Updated by Webmaster
Last Revised 01.Jan.2002
Revised by Webmaster
|