Previous Next V-Model Official Homepage by IABG  
Header  
SD 1.7: Realization of Requirements Controlling  

  SE1.7 - Forderungscontrolling durchführen

Contents  
  • Product Flow
  • Handling
  • Roles
    		•  
  • Tools Requirements
  • External Norms
  • Pre-Tailoring forms

    • Product Flow

    From Product to Methods Tool Req. Ext. Norms
    Activity State Chapter Title Activity State
    External - All Marginal Conditions - -      
    SD1.6 accepted Existing User Requirements - -    
    SD2 accepted Existing System Architecture (1) - -    
    - - All Protocol PM6 -    

    + "Chapter" are extra columns from the original printed version of GD 250

    Handling

    Requirements controlling is used for the evaluation of the defined User 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 analysis results may end up in suggestions for the modification/reduction of requirements. Advantages resulting from a modification/reduction of the initial requirements have to be documented. It must be ascertained that the modification/reduction of User Requirements does not endanger the reaching of all project goals.

    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.

    ---------- The following part is an extension of the original printed version of GD 250 -----------

    Roles

    Role Participation
    Project Leader cooperating
    System Analyst cooperating
    System Designer cooperating
    User responsible

    Tools Requirements

    None defined

    External Norms

    None defined

    Pre-Tailoring forms

    Pre-tailoring Forms SD Products Implementing
    Conditions
    Small Administrative IT Projects                                         SD1.7 x More Complex Dat    
    Medium Administrative IT Projects                                         SD1.7 x More Complex Dat    
    Large Administrative IT Projects                                         SD1.7 x More Complex Dat    
    Small/Medium Technical-Scientific IT Projects                                         SD1.7 x More Complex Dat    
    Large Technical-Scientific IT Projects                                         SD1.7 x More Complex Dat    
    Selection, Procurement and Adjustment of Off-the-Shelf Products                                   SD1.7 x Basic Requirements          

    Matrix Entries:

    Always required
    Always required under given circunstances
    Not required
    Description of data or database only

    Notes

    (1) The System Architecture is input information when a requirements controlling is to be realized on the basis of an actual architecture proposal.

    (2) These may be defined as special specifications of the user area (IT Equipment, house standards) within the scope of a cross-sectional support.

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