What are the principal components of a textual use-case description?

What are the principal components of a textual use-case description?
Answer: Name: The name of the use case.
Brief Description: A brief description of the role and purpose of the use case.
Flow of events: A textual description of what the system does in regard to the use case (not how specific problems are solved by the system). The description is understandable by the customer.
Special requirements: A textual description that collects all requirements, such as non-functional requirements, on the use case, that are not considered in the use-case model, but that need to be taken care of during design or implementation.
Preconditions: A textual description that defines a constraint on the system when the use case may start.
Post conditions: A textual description that defines a constraint on the system when the use cases have terminated.
Extension points: A list of locations within the flow of events of the use case at which additional behavior can be inserted using the extend-relationship.