A process model begins with a diagram of Events, Activities, Gateways, and Connections that are added using the BPMN editor. The model can be a simple flow chart, or it can be a complex process model with multiple linked process diagrams, Triggers, Artifacts, and Properties. Process elements can be visually separated into Groups or Pools, which can be further divided into Swimlanes.
Some elements can only be added to Processes. For example, Goals, KPIs, and Messages can be added to Processes using Outline view. They can then be modified using Properties view.
Additional elements can be added to the model by using WSDL artifacts. These web services can be thought of almost like building blocks. Each web service has a predefined function that can be added to a process model.
The following table lists the elements in the interface and where they are found.
|
Element Type |
Shown in the Diagram |
Shown in Outline Tree
View |
|
Activity |
Yes |
Yes |
|
Event |
Yes |
Yes |
|
Gateway |
Yes |
Yes |
|
Pool |
Yes |
Yes |
|
Lane |
Yes |
Yes |
|
Data Object |
Yes |
Yes |
|
Text Annotation |
Yes |
Yes |
|
Group |
Yes |
Yes |
|
Sequence Flow |
Yes |
Yes |
|
Message Flow |
Yes |
Yes |
|
Association |
Yes |
Yes |
|
Text |
Yes |
Yes |
|
Trigger/Result |
As decorations |
Yes |
|
Assignment |
No |
Yes |
|
Process |
No |
Yes |
|
Message |
No |
Yes |
|
CorrelationSet |
No |
Yes |
|
Correlation |
No |
Yes |
|
Goal |
No |
Yes |
|
Key Performance
Indicator |
No |
Yes |
ActiveVOS is
much more than a process modeling tool. It also builds software code as you
enter model elements. 100% of the interface elements—including the
diagram and its processes, properties, artifacts, and documentation—are
coded and ready for use by a technology architect as you create them.
The resulting system allows you to reverse engineer existing process models,
document existing processes using the reporting features, streamline system
integration, and publish the Application Programming Interface (