Introduction to bizagi
This presentation is the property of its rightful owner.
Sponsored Links
1 / 34

Introduction to BizAgi PowerPoint PPT Presentation


  • 414 Views
  • Uploaded on
  • Presentation posted in: General

Introduction to BizAgi. User Interface (Summary). The user interface for BizAgi resembles Office It uses a similar ribbon The Palette contains the various symbols (Flow, Artifacts, Swimlanes , Connections) Draw these on the visual palette

Download Presentation

Introduction to BizAgi

An Image/Link below is provided (as is) to download presentation

Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author.While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server.


- - - - - - - - - - - - - - - - - - - - - - - - - - E N D - - - - - - - - - - - - - - - - - - - - - - - - - -

Presentation Transcript


Introduction to bizagi

Introduction to BizAgi


User interface summary

User Interface (Summary)

  • The user interface for BizAgi resembles Office

    • It uses a similar ribbon

  • The Palette contains the various symbols (Flow, Artifacts, Swimlanes, Connections)

    • Draw these on the visual palette

  • The Elementproperties section allows you to configure the selected element


User interface illustration

User Interface (Illustration)


Creating a new model

Creating a New Model

  • Click File, New to create a new BizAgi model

  • The design surface shows a process with a single pool

    • Use the Basic properties to give the process a name

    • Drag the Laneicon to the design surface to create a swim lane

      • Use the element properties to name each swim lane


Creating the model

Creating the Model

  • Use the Palette to drag symbols to the diagram


Events

Events

  • Fire as a result of something happening

    • A message is received

    • A period of time elapses

    • An exceptional conditional arises

  • We typically perform an action in response to an event


Events1

Events

  • Fire as a result of something happening

    • A message is received

    • A period of time elapses

    • An exceptional conditional arises

  • We typically perform an action in response to an event


Event types

Event Types

  • Message – Arrives from a participant

  • Timer – Process starts at a period in time

  • Rule (conditional)– Triggers when a rule becomes true


Event types 2

Event Types (2)

  • Link – Connect the end event of one process to the start of another process

  • Multiple – Multiple ways of triggering the process

  • Exception – An error

  • End events


Message events

Message Events

  • Messages are typically sent by one participant and received by another

    • Send sales order information that is received by accounting to check credit

  • The event can be thrown or caught

    • Sending a message means throwing a message

    • Receiving a message means catching a message

    • See MessageThrowCatch in EventSamples


Message throw catch example

Message Throw Catch Example


Timer events

Timer Events

  • The event fires a specific time or cycle

    • Only applicable to start or intermediate events

    • In BizAgi, use the Element properties to set the timer to a date or cycle

  • Examples

    • Time delay to approve credit

    • Wait for payment date

    • Start payroll process every two weeks

    • See Timer in EventSamples


Conditional events

Conditional Events

  • Events that fire when an external condition becomes true or false

    • Process A/P checks on Mondays

      • We could also implement this as a timer

    • Inventory below threshold – generate order request

    • Only applicable to start or intermediate events

    • See Conditional in EventSamples


To create an event

To Create an Event

  • First, drag the event icon to the designer surface

  • Right-click on the event and set the event type


Gateways 1

Gateways 1

  • Gateways are used to depict decisions or merges

  • Types

    • Exclusive (XOR)

      • Only one output (alternative) flow is allowed

      • Gateways diverge or converge

    • Inclusive (OR)

      • A default output flow must be specified

    • Parallel for / join (AND)


Gateways 2

Gateways (2)

  • Event-based gateways

    • These are (Exclusive) gateways that rely on external messages


Gateway xor example

Gateway – XOR Example

  • Exclusive XOR Decision

    • See ExclusiveGatewayin EventSamples


Gateway or

Gateway - OR

  • Inclusive OR decision


Gateway example 3

Gateway – Example 3

  • Parallel Forking – All sequence flows drawn out of the gateway are taken


Processes and tasks

Processes and Tasks

  • A process is a network of steps

  • A process can be marked as having a sub-process

  • To mark an activity has having a sub process, right-click the activity and click Transform to subprocess


Sub processes illustration 1

Sub Processes – Illustration (1)


Data objects

Data Objects

  • First, we are not talking about a database or physical data

    • We are talking about information about a process

  • Data objects are attached to a sequence or message flow with a dashed line


Data objects illustration

Data Objects (Illustration)


Text annotation

Text Annotation

  • Contains descriptive text about a process

  • A line connects the annotation to the activity


Workflow patterns introduction

Workflow Patterns (Introduction)

  • In this second section of the lecture, we talk about simple and complex workflow patterns

  • Much of this is derived from the AIFB paper (Modeling Workflow Patterns) in this lecture


Sequence pattern

Sequence Pattern

  • Tasks are executed in sequence (one after another)


Parallel split

Parallel Split

  • This is a logical AND gateway

  • The parallel branches are executed concurrently


Parallel split example

Parallel Split (Example)


Synchronization

Synchronization

  • Two or more different branches get merged into a single branch

    • All merged branches must be completed before the process can continue (Implied)

    • Synchronization can occur because of a parallel split


Synchronization illustration

Synchronization (Illustration)


Exclusive choice

Exclusive Choice

  • Here, we are making a decision with mutually exclusive outcomes

    • (Only one outcome is possible)


Exclusive choice example

Exclusive Choice (Example)


Simple merge

Simple Merge

  • A point in a process where two or more branches are merged into a single branch

  • The initial branches are created via some type of choice


Simple merge example

Simple Merge (Example)


  • Login