[The introduction of the Business Modeling Guidelines should provide an overview of the entire document. It should include the purpose, scope, definitions, acronyms, abbreviations, references, and overview of this Business Modeling Guidelines.]

1.1 Purpose

[Specify the purpose of this Business Modeling Guidelines.]

1.2 Scope

[A brief description of the scope of this Business Modeling Guidelines; what Project(s) it is associated with, and anything else that is affected or influenced by this document.]

1.3 Definitions, Acronyms and Abbreviations

[This subsection should provide the definitions of all terms, acronyms, and abbreviations required to properly interpret the Business Modeling Guidelines. This information may be provided by reference to the project Glossary.]

1.4 References

[This subsection should provide a complete list of all documents referenced elsewhere in the Business Modeling Guidelines. Each document should be identified by title, report number (if applicable), date, and publishing organization. Specify the sources from which the references can be obtained. This information may be provided by reference to an appendix or to another document.]

1.5 Overview

[This subsection should describe what the rest of the Business Modeling Guidelines contains and explain how the document is organized.]

2. Business Use Case Modeling Guidelines

2.1 General Guidelines

[The section describes which notation to use in the business use case model. For example, you may have decided not to use extends-relationships between business use cases.]

2.2 How to Describe a Business Use Case

[This section gives rules, recommendations, and style issues, and provides instructions on how to describe each business use case.]

2.3 How to Describe a Business Goal

[This section gives rules, recommendations, and style issues, and provides instructions on how to describe each business goal.]

3. Business Analysis Modeling Guidelines

3.1 General Guidelines

[[This section describes which notation to use in the business analysis model. For example, you may have decided not to use generalization-relationships between classes.]

3.2 How to Describe Business Systems

[This section gives rules, recommendations, and style issues, and provides instructions on how to describe each business system (if any).]

3.3 How to Describe a Business Use Case Realization

[This section gives rules, recommendations, and style issues, and provides instructions on how to describe each business use case realization.]

3.4 How to Describe a Business Worker

[This section gives rules, recommendations, and style issues, and provides instructions on how to describe each business worker.]

3.5 How to Describe a Business Entity

[This section gives rules, recommendations, and style issues, and provides instructions on how to describe each business entity.]

3.6 How to Describe a Business Event

[This section gives rules, recommendations, and style issues, and provides instructions on how to describe each business event.]

4. Business Rules Guidelines

[This section gives rules, recommendations, and style issues, and provides instructions on how to describe business rules, either in document form or in model form.]

5. UML Stereotypes

[This section contains or references specifications of Unified Modeling Language (UML) stereotypes and their semantic implications a textual description of the meaning and significance of the stereotype and any limitations on its use for stereotypes already known or discovered to be important for business, in general, or the type of business being modeled. The use of these stereotypes may be simply recommended or perhaps even made mandatory; for example, when their use is required by an imposed standard or when it is felt that their use makes models significantly easier to understand. This section may be empty if no additional stereotypes, other than those predefined by the UML and the Rational Unified Process, are considered necessary.]