Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Section
titleProperties
Transclusion
documentNote Box referencing common Document Properties
idsBox

Section
level2
titlePrimary Actors

List the primary actors of the use case.

Primary actors use the system to create one of the purposed goals.

Section
level2
titleSecondary Actors

List the secondary actors of the use case.

Typical secondary actors are developers and administrators that support the system by maintaining or monitoring.

Section
level2
titleSupporting Actors

List the supporting actors of the use case.

Supporting actors of a system are only used by the system, but are not using the system (e.g. printers).

Section
level2
titleGoal Level

Define the level of abstraction of the use case.

Consider using the Use Case Level Macro.

Section
level2
titleFrequency

Define the expected frequency of use.

Dependent on the product this may be numbers like uses per visit/task of one user or uses per hour/day/week/month (of one/all user(s)). It is not important to compare two use cases by their frequency, it is important for the developer to get to know how often the function will be used by users of the system.

Section
level2
titleLevel

Specify the level of this use case in the containment hierarchy.

Consider to use the Level Macro to calculate this information based on the location of this document within the hierachy of use case documents.

Section
titleSections
Section
level2
titleDescription
Provide a description that sets the use case in a context without describing the steps of the use case.
Section
level2
titleSummary
Give a summary of the use case.
Section
level2
titlePreconditions
List the preconditions that have to be met that the use case can be triggered. You may use a table with two columns to name the precondition and describe it.
Section
level2
titlePostconditions
List the postcondition that will be met after the use case has been executed. The minimal postcondition is that is always met, all other conditions may be met in certain circumstances that will be specified. You may use a three column table to specify the name, the circumstances in which case the postcondition gets active and a description of the condition.
Section
level2
titleTriggers
List the triggers that initiate the use case. Use a two-column table with a name of the trigger and a description.
Section
level2
titleBasic Course

Describe the central course of events.

 This is usually a numbered list of steps.

Section
level2
titleAlternative Sequences

List the alternative, non-exceptional courses of events.

Usually add one section of each alternative and use a numbered list for the individual steps.

Section
level2
titleException Sequences

List the exceptional courses of events.

Usually add one section of each exception and use a numbered list for the individual steps.

Section
level2
titleExtension Points

List the extension points defined by this use case. These references describe the extension of the use case that extends another one.

Section
level2
titleTechnology and Data Variations

List the variations of the sequence due to technology or data constraints.

Section
level2
titleBusiness Rules

List the business rules related to the use case.

Section
level2
titleStakeholders

List the stakeholders interested in this use case.

Section
level2
titleSubordinate Use Cases

Large use cases may be split into smaller ones.

...