Usage of unique diagram names

Revision date:

Purpose

All diagrams should have different names in your process landscape to avoid confusion.

Description

Every diagram’s name should be unique and the name should reflect the purpose of the process in your process landscape. The name can also be a pattern of numbers. For example, if an employee summarized an order, (including “Write a bill” and “Refill the warehouse stock”), the name of the process could be “Handling of Orders.” If there are many models, giving each model a number may be helpful to quicker find a process. An example for this hierarchic labeling style  would be a parent diagramm called  “1.4 Handling of Orders,” and one of its child diagrams labeled “1.4.1 Invoice of an Order.”