Previous Next Functional Tool Requirements Homepage  
System Development Submodel  
SSD26 - Supporting Use Case Modeling  

  LSE26 - Use-Case-Modellierung unterstützen

Contents  
  • 1 Allocation to V-Model and Methods Allocation
  • 2 Brief Characteristics
  • 3 Requirements
  •       3.1 Requirements for Interfaces
  •       3.2 Requirements for the Methods Support
  •       3.3 Requirements for Functions
  •       3.4 Other Requirements

    • 1 Allocation to V-Model and Methods Allocation

    V-Model

    SD1.1 - Recording of Actual Status and Analysis

  • User Requirements.Actual Status and Current Analysis

    • SD1.2 - Description of Application System

  • User Requirements.Preliminary System Description

    • SD1.4 - Definition of Marginal Conditions

  • User Requirements.Marginal Conditions

    • SD1.5 - User-Level System Structure

  • User Requirements.Utilization

    • Method

    UCM - Use Case Modeling

    2 Brief Characteristics

    This service unit defines the requirements for tools used to support the object-oriented method UCM - Use Case Modeling.

    3 Requirements

    3.1 Requirements for Interfaces

    SSD26.I.1 Granularity The exchange of control parameters with SWFM01 - Workflow Management is possible for individual closed function packages of the tool by means of a disclosed, documented interface.
    SSD26.I.2 Input Interface to SSD22 - Supporting Class/Object Modeling It is possible to access information about class/object structure defined with SSD22 via the object management.
    SSD26.I.3 Input Interface to SSD27 - Supporting State Modeling in the Object-Oriented Field It is possible to access information about dynamic models defined with SSD27 via the object management.
    SSD26.I.4 Input Interface to SSD28 - Supporting Interaction Modeling It is possible to access information about interaction models defined with SSD28 via the object management.
    SSD26.I.5 Input Interface to SSD29 - Formal Specification It is possible to access information about specifications defined with SSD29 via the object management.
    SSD26.I.6 Input Interface to SSD30 - Formal Verification It is possible to access information about verifications realized with SSD30 via the object management.
    SSD26.I.7 Input Interface to SSD31 - Analysis of Covert Channels It is possible to access information about the analysis of covert channels realized with SSD31 via the object management.

    3.2 Requirements for the Methods Support

    SSD26.M.1 UCM - Use Case Modeling
    SSD26.M.1.1 Symbols
    SSD26.M.1.1.1 Actors A symbol is available for the representation of actors.
    SSD26.M.1.1.2 Use Cases A symbol is available for the representation of Use Cases.
    SSD26.M.1.1.3 Systems A symbol is available for the representation of systems as professional units.
    SSD26.M.1.1.4 Relationships Symbols are available for the representation of relationships between actors and use cases as well as for the relationships between use cases to each other.
    The relationship between use cases can be identified to see if it is an "extend"- or a "use" relationship.
    SSD26.M.1.2 Names It is possible to allocate identifying names for actors, use cases and relations.
    SSD26.M.1.3 Use Case Diagrams It is possible to represent the use cases making up a professional unit in a system symbol. The actors related with the use cases can be arranged outside of the system symbols, they access the use cases in this unit from outside.
    SSD26.M.1.4 Specification of Use Cases It is possible to specify Use Cases in text form.
    SSD26.M.1.5 Additional Descriptions It is possible to specify actors and relations in more detail by means of additional text descriptions.

    3.3 Requirements for Functions

    none

    3.4 Other Requirements

    SSD26.O.1 Upward Compatibility It must be possible to process objects that were generated with an older release of the tool with the later release of that tool, without loss of information and functionality.
    SSD26.O.2 Procedural Command Language The tool has a procedural command language that can be applied by the user to generate and run macros or procedures.
    SSD26.O.3 Complexity There is no limitation of the complexity caused by the tool itself.

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