An introduction to the terminology and icons used in the Business Process Model. Provides a quick introduction to some Unified Modelling Language (UML) concepts and how they are applied in Enterprise Architect's Business Process Model.

A business process:

Process Models
Business Process Process:
A business process is a collection of activities designed to produce a specific output for a particular customer or market. It implies a strong emphasis on how the work is done within and organization, in contrast to a product's focus on what. A process is thus a specific ordering of work activities across time and place, with a beginning, an end, and clearly defined inputs and outputs: a structure for action.

Connections

•	Supply link from object Information. A supply link indicates that the information or object linked to the process is not used up in the processing phase. For example, order templates may be used over and over to provide new orders of a certain style - the templates are not altered or exhausted as part of this activity.
•	Supply link from object Resource. An input link indicates that the attached object or resource is consumed in the processing procedure. As an example, as customer orders are processed they are completed and signed off, and typically are used only once per unique resource (order).
•	Goal link to object Goal. A goal link indicates the attached object to the business process describes the goal of the process. A goal is the business justification for performing the activity.
•	Stateflow link to object Output
•	Stateflow link from event Event. A stateflow link indicates some object is passed into a business process. It captures the passing of control to another entity or process, with the implied passing of state or information from activity to activity.

Figure 1 : Workflow

Goal
Object:
A business process has some well defined goal. This is the reason the organization does this work, and should be defined in terms of the benefits this process has for the organization as a whole and in satisfying the business needs.

Connections
Goal link from activity Business Process. A goal link indicates the attached object to the business process describes the goal of the process. A goal is the business justification for performing the activity.

Information
Object:
Business processes use information to tailor or complete their activities. Information, unlike resources, is not consumed in the process - rather it is used as part of the transformation process. In formation may come from external sources, from customers, from internal organizational units and may even be the product of other processes.

Connections
Supply link to activity Business Process. A supply link indicates that the information or object linked to the process is not used up in the processing phase. For example, order templates may be used over and over to provide new orders of a certain style - the templates are not altered or exhausted as part of this activity.

Output
Object:
A business process will typically produce one or more outputs of value to the business, either for internal use of to satisfy external requirements. An output may be a physical object (such as a report or invoice), a transformation of raw resources into a new arrangement (a daily schedule or roster) or an overall business result such as completing a customer order.

An output of one business process may feed into another process, either as a requested item or a trigger to initiate new activities.

Connections
Stateflow link from activity Business Process

Resource
Object:
A resource is an input to a business process, and, unlike information, is typically consumed during the processing. For example, as each daily train service is run and actuals recorded, the service resource is 'used up' as far as the process of recording actual train times is concerned.

Connections
Supply link to activity Business Process. An input link indicates that the attached object or resource is consumed in the processing procedure. As an example, as customer orders are processed they are completed and signed off, and typically are used only once per unique resource (order).