Provide a description that sets the use case in a context without describing the steps of the use case.

Give a summary of the use case.

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.

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.

List the triggers that initiate the use case. Use a two-column table with a name of the trigger and a description.

Describe the central course of events.

 This is usually a numbered list of steps.

List the alternative, non-exceptional courses of events.

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

List the exceptional courses of events.

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

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

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

List the business rules related to the use case.

List the stakeholders interested in this use case.

Large use cases may be split into smaller ones.