Starter Process Diagram
The Starter Process Diagram Pattern creates a Business Process with a nested diagram that contains a Start Event, two Activities and an End Event. Best practice is to position the diagram and its elements as nodes below the owning Business Process.

Figure 1. Shows two Activities connected by Control Flows.

Figure 2. Shows the nesting of the diagram and elements below the Process.
Discussion
The purpose of the pattern is to allow Process Analysts,.Business Analysts and other stakeholders to create and view a basic Business Process. The pattern will act as a starting point and the expectation is that new elements will be added to the diagram.

The pattern can be used at any point in an initiative but is typically used early on when either the baseline (current state) processes are being drawn or the target (future state) processes are being defined.  It is quite common for an organization to embark on an initiative to detail all the baseline (current state) processes at an enterprise or business unit level so these are available and can be reused by multiple projects.

The following is a list of some things you may want to do when working with this pattern.
·	Rename the Package and diagram to suit the process being modeled.
Rename the items in the diagram to suit the process being modeled.
Change the types of the Activities and Start and End Events using the Element Properties window or the Tagged Values Window as required.
Add notes to the Activities and other elements to provide a more detailed description or explanation.
Add Pools and Lanes if required using drag-and-drop lanes from the Toolbox.

The following is a list of some of the next steps available when applying the pattern.
·	Create drill-down from Activities by adding a child diagram which will make the element composite and allow a user to click-through to the next level in a process.
Create documentation automatically with the document generator using built-in or user defined templates.
Create a simulation of the diagram using the built in simulator available from the simulation window.
Create a simulation using the BPSim facility which allows sophisticated analysis of the process.
Create Trace relationships between the Activities and other elements in the repository including up-process elements such as Drivers, and Goals and down-process elements such as Use Cases, User Stories, Components.
Create a Business Rule Task and relate this element to a Decision defined in a Decision model using the Decision Model and Notation (DMN) facility.
Create Pools if there are other organizations that are part of the process but are external to the organization in focus.

Useful Workspace Layouts Core | Core Modeling. Wide View
Reference
The following are some of the tools that will be helpful when working with this pattern.
Business Process Diagram
Business Process Toolbox Pages
Model Simulation
Run Model Simulation
Business Process Simulation (BPSim)
Working with Diagrams
Baseline Tool
Specification View
Document Window

The following are some of the tools that will be helpful when working with this pattern.
Document Generator
The Document Generator is a powerful facility in Enterprise Architect that allows a Database Engineer or other stakeholder to create high quality corporate or technical documentation directly from the model, suitable for internal or external audiences. For more details see the Documentation help topic or the more general topic on Model Publishing.
Specification View
The Specification View can be used as a way of working with any element type in a spreadsheet or word process view. It is particularly useful when there are a large number of elements as is typically the case when describing a system of any appreciable size. For more details see the Specification View help topic.
Document Window
The Document Window is a powerful tool for generating, reading and editing narrative style information for an element. There are two tabs: the Dynamic Document Tab and the Linked Document Tab. The Dynamic Document tab generates documentation automatically from element information and the Linked Document tab cab be used for reading and editing an element's linked document. For more details see the Document Window help topic.
Relationship Matrix
The Relationship Matrix provides a spreadsheet like view of two groups of elements and the relationships that exist between them. It can be a used as a powerful analysis mechanism to visually indicate how elements are related to each other and to discover which elements are missing relationships. For more details see the Relationship Matrix  help topic.
Traceability Window
The Traceability Window automatically displays the relationships that exist between Use Cases and other model elements including up-process and down-process elements. The traceability tree view can be conveniently expanded to see deeper relationships and elements displayed in the window can be located in all diagrams in which they appear. For more details see the Traceability Window  help topic.
BPMN Business Process Diagram
Business Process Diagrams are part of the Business Process Model and Notation (BPMN) standard and allow a modeler to document a business process, including the way the process starts, what work is performed and how it ends. Gateways and connecting lines determine the sequence of activities. Current state and Future state process models can be created and managed in Enterprise Architect. The diagrams can be organized into a process hierarchy allowing drill down from high level to lower level diagrams. BPMN is emerging as an important standard for modeling business processes and has gained much traction with business and technical communities. It can be automatically generated to the Business Process Execution Language (BPEL), which is an XML based language that can be ingested by a number of orchestration engines. For more details see the BPMN Business Process Diagram help topic.
Model Simulator
Model Simulation brings your behavioral models to life with instant, real-time behavioral model execution. Coupled with tools to manage triggers, events, guards, effects, breakpoints and simulation variables, plus the ability to visually track execution at run-time, the Simulator is a powerful means of 'watching your behavioral models in action' and verifying their correctness. With Simulation you can explore and test the dynamic behavior of models.  For more details see the Model Simulation help topic.
Business Process Simulation (BPSim)
The BPSim facility provides a way of simulating processes written in Business Process Model and Notation (BPMN), providing valuable results that can be used in process analysis. The BPMN models are augmented with extra data as parameters to the simulation. It allows structural and capacity analysis to be performed, providing for pre and post execution optimization. Enterprise Architect allows you to construct the Process models and enter the appropriate data, which is then sent to an internal or external BPSim Simulation engine.  For more details see the Business Process Simulation (BPSim) help topic.
Element Discussions
The Element Discussion facility is a fully featured collaboration tool allowing modelers and model viewers and reviewers to communicate with each other directly inside the repository. Modelers using the full client or occasional viewers using WebEA can both post and reply to discussions and communicate and engage in chat. For more details see the Element Discussions help topic.
Diagram Layout
The Diagram Layout tool allows you to layout an entire diagram, selected elements or sections of a diagram to make it more visually appealing or meaningful to a particular audience. There are a wide range of layout types to choose from and some types have filters that can be applied. For more details see the Diagram Layout help topic.
Pan and Zoom
The Pan and Zoom facility is one of the tools that can be used to navigate around a large diagram. Often the resolution of a diagram must be reduced to ensure it is wholly visible but by using the Pan and Zoom window you can leave the diagram at a readable resolution and pan around to areas of interest zooming in when necessary. For more details see the Pan and Zoom help topic.
Diagram Legends
The Diagram Legend facility is useful for manually or automatically changing the appearance of elements and connectors on a diagram. A legend can be added from the Common Toolbox and configured to codify the fill and line color and line thickness. This is a powerful way to add meaning and expression to a diagram and is particularly expressive when applied automatically based on element or connector properties. It can be used with a number of specialized diagrams such as roadmaps to create a powerful visualization.  For more details see the Diagram Legends help topic.
Baseline Tool
The Baseline Tool can capture a snapshot of a selected Package at a point in time and then at a later time the repository can be compared to this (or another baseline) for the purpose of determining what has changed. Any number of baselines can be created and labeled and there is a baseline comparison tool which displays the differences between the baseline and the model and allows the modeler to revert a change in the model to a baseline at a granular level. For more details see the Baseline Tool help topic.
Linked Documents
Linked Documents provide a way of incorporating extensive and highly formatted documentation for an element. While an elements notes are a useful place to provide brief and visible information about an element a Linked Document can be used to create extensive documentation for an element including all the features you available in a typical word processing tool such as: Paragraph Formatting, Header and Footers, Table Images, Tables of contents and much more. For more details see the Linked Documents help topic.
Artifact
An Artifact can be used as a placeholder for a Financial Analysis file or web address such as a spreadsheet or document that resides external to the repository. The Artifact element can be hyper-linked to the external document allowing it to be launched from within Enterprise Architect. This provides a convenient way to reference the document inside the model for example by linking other elements such as Requirements to the document. For more details see the Artifact help topic.

© 2000 - 2018  Sparx Systems Pty Ltd.  All rights Reserved.