Result

[Work on own experiences/completions]



E-38 Activity Diagram

Belong to:

Design-results

Is part of:

E-154 List of candidates of secondary system use cases
E-153 System use case model
E-69 Architecture- and program description

Description:

Acitivity diagrams represent all possible activity flows of an application in a graphical view, i.e. a special part with temporal and technical limits.

All activity flows which are described in system use cases, scenarios or text (which could be defined unclear) are described by activity diagrams in a complete and formal manner.

Elements of the activity-diagrams are at least:

  • Activities,
  • Transitions, i.e. crossings between the activities,
  • Start- and final point,
  • and also to split of and to synchronize controll flows
The activity considers three different flows:
  • guilty core/main flow (best case)
  • guilty variants (alternatives)
  • exceptions and error flows.
At a starting point to model an activity diagram the essential steps from the Essence of Use Cases can be used very well. To do this, use UML-activity-diagrams or similar notations.

Result contains:

Tools:


Possible status:

  • only core/main flow is described
  • core/main flow and variants are described
  • core/main flow, variants and exceptions are described

  • Producing or changing from:

    A-229 Detail system use case
    A-245 Describe business processes
    A-269 Optimize and consolidate the business use case sequences
    A-248 Modeling business use case sequences
    A-86 Develop Dialogs and the Sequential Control
    A-270 Describe business use cases in detail
    A-271 Identify the organisational assignment and reorganise the dependencies, if necessary

    Is needed for:

    A-68 Modelling Interaction Models
    A-26 Specify a dialog
    A-233 Develop a use case model with associations between system use cases
    A-269 Optimize and consolidate the business use case sequences
    A-270 Describe business use cases in detail
    A-61 Produce/Define test cases
    A-273 Develop a business use case model

    QS-Note:

    Patter/Example:

    OEP - Object Engineering Process, v2.0, 06.11.2006 11:08:50, Copyright © 2003 by oose.de eG