1. Introduction
A brief description of the purpose of the Business Use Case Model.

2. Survey Description
A summary list of business goals, business actors and business use cases as they are arranged below. This section should also describe basic facts about the business, such as the business idea and the markets in which the business operates.

3. Business Use-Case Model Hierarchy
This section presents the use-case packages hierarchically, explains the dependencies among them, and shows the content of each package recursively. If the model has several levels of packages, those at the top-level are presented first. The packages within these are presented next, and so on, all the way down to the packages at the bottom of the hierarchy. For each package include:

• Its Name.
• A Brief Description explaining the package's function and role in the system. The description must be understandable to any developer who wants to use the package.
• A list of business goals owned by the package, including the name and brief description of each business goal.
• A list of the business use cases owned by the package, including the name and brief description of each business use case.
• A list of business actors owned by the package, including the name and brief description of each business actor.
• A list of relationships owned by the package, including the name and brief description of each relationship.
• A list of the packages directly owned by the package, with each package presented in the same hierarchical manner as above.

4. Diagrams of the Business Use-Case Model
Diagrams, primarily use-case diagrams, of the entire use-case model are included here.  There should be at least one diagram to provide a high-level overview of the business goals, one to provide a high-level overview of the core business use cases and one to provide an overview of the significant business actors.