# Business Modeling Guidelines Template

## Cover Page

- ``Project Name``
- `Business Modeling Guidelines`
- `Version`1.0``

## Revision History

| Date | Version | Description | Author |
| --- | --- | --- | --- |
| ``dd/mmm/yy``|``x.x``|`<details>`|`<name>` |

## Ownership & Collaboration

- Document Owner: Environment Engineer
- Contributor Roles: Business Process Analyst, System Analyst
- Automation Inputs: Modeling standards, notation policies
- Automation Outputs: `business-modeling-guidelines.md` with sections 1–5

## 1 Introduction

> Explain purpose, scope, terminology, references, and structure for these guidelines.

### 1.1 Purpose

### 1.2 Scope

### 1.3 Definitions, Acronyms, and Abbreviations

### 1.4 References

### 1.5 Overview

## 2 Business Use-Case Modeling Guidelines

### 2.1 General Guidelines

> Define notation, modeling conventions, and diagram usage.

### 2.2 How to Describe a Business Use Case

> Provide style rules, required sections, and traceability expectations.

### 2.3 How to Describe a Business Goal

> Outline structure and evaluation criteria for business goals.

## 3 Business Analysis Modeling Guidelines

### 3.1 General Guidelines

> Describe modeling notation and constraints for the analysis model.

### 3.2 How to Describe Business Systems

### 3.3 How to Describe a Business Use-Case Realization

### 3.4 How to Describe a Business Worker

### 3.5 How to Describe a Business Entity

### 3.6 How to Describe a Business Event

> For each artifact, list recommended sections, naming conventions, and modeling examples.

## 4 Business Rules Guidelines

> Explain documentation approach for business rules (documents vs. model elements) and quality checks.

## 5 UML Stereotypes

> Record custom stereotypes, semantics, and usage constraints relevant to business modeling.

## Appendices (Optional)

> Attach examples, modeling checklists, or reference diagrams.

## Agent Notes

- State notation and diagramming rules so automation can generate models consistently.
- List validation checks that must pass before business models are approved.
- Verify the Automation Outputs entry is satisfied before signaling completion.
- Document notation rules so automated modeling stays consistent.
- List validation steps that must pass before publishing business models.