Previous Next V-Model Official Homepage by IABG  
RE Homepage  
RE.3.3.1 User Requirements (UReq)  


  • Introduction
  • Document Index
  • Document Structure
  • Introduction

    The User Requirements describe the user-level aspects of the System. These aspects have to be documented with regard to the application environment. The User Requirements are the basis for the acceptance of the System by the customer.

    The User Requirements contain the documentation of the recording of actual status and current analysis as well as the threat and risk analysis, the documentation of the IT security objectives and the IT security measures, the definition of user-level requirements, and the marginal conditions.

    To mark requirements a formalism is needed which allows each requirement to be identified in a unique way; so a unique reference will be possible from the architecture and design documents (acknowledgment principle).

    When stating requirements care must be taken to describe only "WHAT" a task is to accomplish, not "HOW" it is going to be accomplished. Furthermore, what must be taken into consideration is that requirements have to be assessable, unique, consistent, and free of hidden design decisions.

    The term "System" also comprises the term "procedure".

    Document Index

    1. General Information
    2. User-level Requirements
          2.1. Preliminary System Description
          2.2. Organizational Embedding
          2.3. Utilization
          2.4. External Interfaces
          2.5. Description of the Functionality

    Document Structure

    1. General Information

    See schema 1. General Information.

    2. User-level Requirements

    2. 1. Preliminary System Description

    In this case, the preliminary system description must fulfill the following criteria in the form of an overall horizon:

    2. 2. Organizational Embedding

    This chapter contains a description of the organizational sphere of the System: the structure and process organization of the user, user classes, responsibilities and competence during operation, and the additional equipment of the user.

    2. 3. Utilization

    This contains a description of the requirements for operation and use of the System, e. g. for mobile or stationary operation, operation times, communication between user and System, the extent of the services to be automatically made available by the System.

    2. 5. External Interfaces

    Requirements for the external interfaces to neighboring systems and, in particular, for the man-machine interface have to be documented.

    Requirements with regard to ergonomics must also be taken into consideration. The technical design of the user interface is defined within the scope of the Technical Requirements.

    2. 6. Description of the Functionality

    This chapter describes the user-level structure of the System functionality from a user's point of view:


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