|SD 1.7: Realization of Requirements Controlling|
|From||Product||to||Methods||Tool Req.||Ext. Norms|
|SD2||accepted||Existing||System Architecture (1)||-||-|
+ "Chapter" are extra columns from the original printed version of GD 250User Requirements with regard to feasibility and profitability; it is based on the initial architectural considerations or on a concrete system architecture. In this connection, the technical and organizational marginal conditions as external specifications have to be taken into consideration.(2)
The User Requirements are analyzed on the basis of the following criteria:
The results of the requirements controlling must be documented in a Protocol. At the instigation of the project management, these results must be considered in the User Requirements, and later also in the Technical Requirements (activity PM6 - Phase Review).
Requirements controlling requires a dialog between users and representatives of the customers. In case the creators of the requirements documents do not agree with the change proposals, the project management has to see to it that a decision is made by the corresponding instances in charge.
|Pre-tailoring Forms||SD Products||Implementing
|Small Administrative IT Projects|
|Medium Administrative IT Projects|
|Large Administrative IT Projects|
|Small/Medium Technical-Scientific IT Projects|
|Large Technical-Scientific IT Projects|
|Selection, Procurement and Adjustment of Off-the-Shelf Products|
Always required under given circunstances
Description of data or database only
(2) These may be defined as special specifications of the user area (IT Equipment, house standards) within the scope of a cross-sectional support.
|GDPA Online Last Updated 01.Jan.2002 Updated by Webmaster Last Revised 01.Jan.2002 Revised by Webmaster|