Result

[Work on own experiences/completions]



E-6 Essence of Use Cases

Belong to:

Requirement-analysis-results

Is part of:

E-78 Preliminary study
E-20 Requirement specification

Description:

For each system use case describe a short essence.

Each system use case is described with:

  • name, use a noun and an active verb, for example "enter contract"
  • short description (1 - 3 sentences)
  • trigger (each system use case has only one technical trigger)
  • important results
  • listing of the commercial essences (commercial intentions)
If you describe system use cases like that, they get the status "described essential ".

Essential system use cases are a special form of use case description. They formulate no assumptions about technologies, implementation terms, development environments etc. and describe only the basic intention - so they are very abstract. For example: The use case "get money from the cash despenser" includes the steps "1. Entry credit card, 2. Entry PIN". To describe the essence for this use case you formulate in an abstract way "identify customer".

Result contains:

Tools:



Possible status:

Producing or changing from:

A-228 Requirement workshop
A-226 Requirement workshop

Is needed for:

A-7 Identify and Classify System Interfaces
A-200 Identify system use cases
A-229 Detail system use case
A-228 Requirement workshop
A-230 UML-business-class-model
A-246 Develop a Sub System Model and a first draft of the business class model, if necessary
A-86 Develop Dialogs and the Sequential Control
A-81 Identify and describe exceptions and possible errors
A-61 Produce/Define test cases
A-215 Develop a sequence or a collaboration diagram
A-206 Describe the system interface
A-260 Develop a domain architecture model

QS-Note:

  • Does each use case describe only the domain-specific essence?
  • Does each use case describe an individual, coherent business situation?

  • Patter/Example:

    : :



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