Beruflich Dokumente
Kultur Dokumente
Metastorm
Page 1 of 355
Class Logistics
Page 2 of 355
Page 3 of 355
Consulting Support
Support..351
351 - 352
Next Steps Plan353 - 353
Additional Reading...354 - 355
Notes
_______________________________________________
_______________________________________________
_______________________________________________
_______________________________________________
_______________________________________________
_______________________________________________
Page 4 of 355
Introductions
Name
Organization
Position
Background
Modeling
g Experience
p
Current / Planned Projects
Specific Objectives / Expectations
1999 - 2007 Metastorm, Inc.
Organization
Model
Inventory of
business actors
(i.e. who)
involved in/with
the business
domain with
parent/child
relationships
Markets
Organizations
Roles
People
10
Page 5 of 355
11
Process Model
12
Page 6 of 355
Communication Model
Frames Business
Processes in the
context of their
initiating Events,
involved Actors
and produced
Deliverables
13
Workflow Model
14
Page 7 of 355
Opportunity Model
Inventories
Opportunities (i.e.
why)
why ) for the business
domain with
parent/child
relationships
Opportunity
Categories
Opportunities
15
Problem Model
Inventories
Problems (i.e.
why) for the
business domain
with parent/child
relationships
Problem
Categories
Problems
16
Page 8 of 355
Model Interpretation
Textually renders all
models remaining
consistent with
ith all visually
is all
depicted information
Objects
Object Properties
Object Associations
17
Association Grid
18
Page 9 of 355
19
20
Page 10 of 355
ProVision Basics
Metastorm
Structure, Navigation,
Desktop
p
& Preferences
22
Page 11 of 355
Metastorm
ProVision Structure
Who
(Actors)
Where
Why
When
What
How
24
Page 12 of 355
1
Complete Order
Expedite
Order?
Model
Completed
Order
Objects are placed in models to describe the models subject. Each model
contains multiple objects. Each model visually presents the relationships
between the objects in the model. Objects can be shared across models.
1999 - 2007 Metastorm, Inc.
25
Notebooks
Notebook
Model
26
Page 13 of 355
Repositories
Notebook
Repository
27
Repositories
Repository
28
Page 14 of 355
Objects
An object is a business concept
that can appear in a model as a
shape, a line, or a label on a line
Repository
1
belongs to
contains
Notebook
belongs to
contains
belongs to
contains
Object
appears
pp
in
includes
Model
*
is the subject of
describes
29
Models
A model is a graphical
representation of a selected object
Repository
1
belongs to
contains
*
Notebook
belongs to
contains
belongs to
contains
Object
*
appears in
includes
Model
*
is the subject of
describes
30
Page 15 of 355
Notebooks
A notebook contains objects and
models that describe a business at
some point in time
Repository
1
belongs to
contains
Notebook
belongs to
contains
belongs to
contains
Object
appears in
includes
Model
*
is the subject of
describes
Different projects
Different business domains
Different project phases
Different implementation phases
31
Repositories
A repository can be thought of as a
book case containing notebooks
Repository
1
belongs to
contains
*
Notebook
belongs to
contains
belongs to
contains
Object
*
appears in
includes
Model
*
i th
is
the subject
bj t off
describes
32
Page 16 of 355
Files
Object
*
appears in
includes
is the subject of
describes
Model
*
containsbelongs to
1
*
containsbelongs to
File
1
alternative
for
Logically equivalent
Smaller size
Excellent for backups / emailing
Save options not as robust
Only notebooks support automatic
(instant) save
Notebook
*
contains belongs to
1
Repository
33
Metastorm
ProVision Navigation,
Desktop & Preferences
Page 17 of 355
1
belongs to
contains
*
Notebook
belongs to
contains
belongs to
contains
Object
j
appears in
includes
*
1
Model
*
is the subject of
describes
}
}
Repository
Inventory Control
Non
Non-graphical
graphical means of access to
contents of a notebook
Shows models and objects within
the open notebook
Shows usage of objects across
models (where used)
35
Index Bar
Repository
Bar
Other Bars
Workarea tabs
36
Page 18 of 355
Active Model
Index Bar
Inventory
Control
(8 views)
(tabs)
37
Preferences control
which of 8 inventory
views are displayed
1999 - 2007 Metastorm, Inc.
38
Page 19 of 355
ProVisionEA
Navigator
Create a model by navigating
object associations
Methodology Modelers
model object associations
ProVision BPA
Parent/Child Modelers
model object structure
1999 - 2007 Metastorm, Inc.
39
Component Models
describe the object
(object is/can be the
subject)
Menu includes
additional operations
for the object (delete,
exclude, style, etc.)
40
Page 20 of 355
41
Directory Structure
Program Files\Proforma\
ProVision999
Documentation
Export
Licenses
Li
Program
Gallery
Portal
Thumbnail
PVData
v999
Sample
your repository
pvw00001.~db
pvw00001.!db
Page 21 of 355
Must be connected to
the Internet for access
Most documents also
placed in installation
directory, accessed via
the Start menu
1999 - 2007 Metastorm, Inc.
43
ProVision Preferences
Controls Individual
Preferences
Launched with the Tools |
Preferences menu option
Settings on tabs have
specific scope
Open Notebook
Application
Scope of Settings:
Model Management......Notebook
I
Inventory
t
Control
C t lT
Tabs.....Notebook
b
N t b k
Save Options..Application
Tool Tips and Status Bar. Notebook
Visible Indicators....Notebook
Interface Tool Defaults. Application
Font Selection.Application
LDAP Authentication.Application
Dimensions.....Notebook
44
Page 22 of 355
Metastorm
Notes
_______________________________________________
_______________________________________________
_______________________________________________
_______________________________________________
_______________________________________________
_______________________________________________
46
Page 23 of 355
Exercises
Each exercise is designed to reinforce key concepts in the corresponding section of the
course. Your exercise answers may vary from those offered here. This is to be
expected since most of the exercises require inference and judgment calls. The
importance of these exercises is not to match the sample answers exactly, but rather to
clarify understanding of the concepts and to raise questions on misunderstandings.
Page 24 of 355
Inventory Bar
Active Model
or Explorer
Page 25 of 355
Page 26 of 355
Page 27 of 355
The Sample repository and all of its notebooks are now available for use. The Guided
Tour notebook will be utilized for this exercise, so it should be opened.
In the Explorer window, click the plus sign in front
of the Sample repository and then double-click the
Notebook icon
in front of the Guided Tour
notebook to open it. When the notebook is open,
its icon will change from
to
On the Model tab in the Links group box, click the check boxes for Render link
intersections with speed bumps and Automatically position objects when
they are linked in parent/child models.
Page 28 of 355
On the Inventory tab, click the check boxes to enable ONLY the Model
Inventory, Object Inventory, Project Inventory and Table Inventory.
No changes are needed, but examine the Save / File tab. Notice that the Save
mode is set to Automatic (lazy commit).
This causes ProVision to
automatically save your modeling and object changes as soon as computer
resources are available, which is usually extremely fast. Therefore, when editing
Notebooks, there is no need to explicitly Save work.
When working with Files rather than Notebooks, use either the Timed or
Manual options for saving work.
Page 29 of 355
On the Indicators tab, check ALL the indicators so that you will maximize the
displayed information. At the model level, you can turn off Indicators for objects
in that model.
Feel free to examine the other tabs in the Preferences dialog and use Help if
there are any questions.
Page 30 of 355
Page 31 of 355
This Business Interaction Model depicts the actors who act as Suppliers,
Customers, Competitors or are Internal to Order Management and their key
responsibilities (i.e. business interactions) with each other.
Notice the drop down list box in the upper left corner of this model. This list can
be used to associate Business Processes to the Business Domain that is the
subject of this model. Use this drop down to select the Fill Order (Business
Process Fill Order) item. This means that the Fill Order Business Process is
a child of the Order Management Business Domain.
After selecting the Fill Order Business Process in this drop down list, notice
that Sub-Assembly Suppliers and its business interactions are ghosted in the
Page 32 of 355
Competitors Region. This means that this actor is not involved with the
Business Process: Fill Order.
Page 33 of 355
Right-click on the Fill Order name in the drop down list (upper left of the
Modeling Window) to display that objects context menu and then select Process
Modeler to launch that model for the Fill Order business process.
Notice that this model depicts the child activities and sub-activities of the Fill
Order Business Process.
Right-click on Fill Order to display that objects context menu and then select
Component Models: Workflow Model (existing model) to launch that nested
workflow model for the Fill Order business process.
Page 34 of 355
Notice that this model depicts for the Fill Order Business Process the child
activities, the responsible actors (as swimlanes), decision points, hand-offs,
workflows, deliverables (inputs/outputs), etc.
Right-click on the 6 Build Product activity to display its context menu and select
Component Models: Workflow Model (existing model).
The Models
describe this object
launch existing models.
Notice that this model depicts for the Build Product Activity the child activities,
the responsible actors (as swimlanes), decision points, hand-offs, workflows,
deliverables (inputs/outputs), etc. The small model in the middle of this model
is a thumbnail view of the 6.3 Assemble Order activity. The 6.3 Assemble
Order activity also has a nested workflow model.
Close each of the 5 models that were opened in this exercise by using the lower
in the upper right corner.
close button
Window/Close All from the main menu bar.
Page 35 of 355
47
Notes
_______________________________________________
_______________________________________________
_______________________________________________
_______________________________________________
_______________________________________________
_______________________________________________
48
Page 36 of 355
Metastorm
Organization Modeler
In ProVision
50
Page 37 of 355
Parent/Child Models
Parent/child representation of object structure
51
Organization Model
Markets
Organizations
Roles
People
52
Page 38 of 355
Model Interpretation
53
Widget
Manufacturers
Widget
Central
Widget City
Quality
Widgets
Organization
Field
Operations
Product
Development
Assembly
Operations
Production
Production
Control
Marketing
Inventory
Management
Finance
Packaging
Role
Assembly
Worker
Supervisor
Quality
Inspector
54
Page 39 of 355
55
Notes
_______________________________________________
_______________________________________________
_______________________________________________
_______________________________________________
_______________________________________________
_______________________________________________
56
Page 40 of 355
Metastorm
Notes
_______________________________________________
_______________________________________________
_______________________________________________
_______________________________________________
_______________________________________________
_______________________________________________
58
Page 41 of 355
Case Study
Professional Retreats Corporation (PRC) is a luxury hotel chain that specializes in
business conferences coupled with a resort atmosphere. An area within PRC,
Conference Administration, provides first-class services and handles all of the logistics
required to prepare for the conferences. This provides customers with one-stop
shopping convenience.
The key offerings for Conference Administration are conferences. A conference involves
numerous sessions conducted over one or more days where speakers present ideas,
opinions and products to attendees. The conference sessions range from grand hall
keynote speeches to small workshops. A conference may involve several hundred to
several thousand attendees.
Although all conferences include sessions, some will support vendor demonstrations of
new product offerings.
The primary revenue stream comes from conference services. Conferences typically
involve a host of peripheral activities such as meetings and banquets. Most importantly
for PRCs revenue stream, a conference books hotel rooms.
Lodging (hotel) management is a major underlying mechanism of Conference
Administration. Although many of the room bookings come from business people
participating in conferences and other activities, the hotels also cater to non-business
guests on vacation. Most PRC sites are located on ocean-front property.
PRCs one-stop-shopping style is very visible to conference attendees. A conference
attendee can register for a PRC-managed conference and have all related logistics
handled by Conference Administration. This includes coordinating flight reservations
with travel agencies, renting vehicles from car rental agencies, and coordinating
entertainment activities such as local tours, plays, etc.
Conference Administration has several types of customers. The Lodging Managements
customer is the guest. Guests are customers who lodge with PRC. The customers on
the conference side of the business are sponsors that book conferences and
participants in those conferences (i.e. speakers, exhibitors and attendees). Sponsors
request and fund conferences. They define the requirements of the conferences and
Conference Administration handles the details. Conference Administration will provide
the sponsor with status information to keep abreast of the conference progress.
Participants simply enroll in a conference. Conference Administration will handle the
transportation, lodging, etc. details and provide the participant with conference
enrollment that includes travel itinerary information.
In summary, Conference Administration provides a headache-free answer for business
and leisure activities. It will coordinate flight and vehicle reservations, coordinate
entertainment activities, administer conferences, allocate space in facilities, reserve the
appropriate equipment, reserve blocks of hotel rooms for the conference and manage
numerous other supporting activities.
Page 42 of 355
Inventory View
(title reflects selected tab)
Explorer or
Active Model
Page 43 of 355
For this exercise, first create a repository containing a notebook to house the
who/what/when/where/why/how objects and the models that visually describe them.
The repository will be named Professional Retreats, and the notebook will be named
Conference Administration. Do the following:
Ensure that ProVision is open and that the Repository View window is visible.
The Repository View window may be opened by clicking on the Repository Bar
in the Index Bar on the left. (If the Index Bar is not displayed, depress the Index
button
Using the Repository | New | Repository menu option (at the top of your
screen), invoke the Repository Creation Wizard dialog.
In Step 1 of the wizard, accept the default radio button to create a single-user
repository. [Multi-user repositories will be covered later in the course.]
In Step 2 of the wizard, specify the path: C:\PVDATA\v60\PRC (note that v60 is
assumed here, but use the version number that is installed). This is the MS
Windows directory where the new repository will be stored.
In Step 3 of the wizard, name the repository Professional Retreats. This is the
name that will appear in the Repository View. You may optionally include a
description, if you wish.
Page 44 of 355
on
the
Model
Inventory
tab
to display an alphabetical
listing of the models by type in the new notebook. Notice that all counts are zero
because you have not yet created any models in the notebook.
Some Preferences are set per Repository. For the new repository, use the
Tools | Preferences menu option, open the Preferences dialog and on the
Model tab, set the Links options as in the following example.
Page 45 of 355
As the exercises progress, models will be created, manipulated and published and
toolbars (or menus) will be utilized to invoke the appropriate functionality. An example
of a typical ProVision window configuration supporting these activities follows.
Menu
Status Bar
Toolbars
Active Model
Page 46 of 355
Ensure the Repository is displayed in the Index Bar. If the Index Bar is not
displayed, depress the Index button
then click the Repository Bar.
Click the plus sign in front of the Professional Retreats repository to reveal
the Conference Administration notebook. Double click the notebook to
open it.
Now, click on the Inventory Bar in the Index Bar, and click on the Model
Inventory tab
Page 47 of 355
In the Select
Organization.
Subject
for
Organization
Modeler
dialog,
select
In the Enter the name for a new Organization edit box, enter Professional
Retreats Corporation, and then click
. This accomplishes two
tasks: (1) the organization is created in the notebooks inventory, and (2) the
Organization Modeler is launched with that subject.
Next, add the first layer of organizations below Professional Retreats Corporation.
Adding main objects to a model can be accomplished by invoking the Add or
Select Object dialog. This dialog is launched in either of three ways. Two
are presented here; the 3rd alternative is discussed a bit later.
1) The easiest technique is to position the mouse in an open area of the
model where the object(s) should be added and then draw a small box with
the left mouse.
2) An alternative is to utilize the Object Creation toolbars main object button
. For the Organization Modeler, the tool tip for the main object button will
say Organization. Click the button and position the mouse in an empty area
of the model where you want to add the object, and then click once again.
In the Add or Select Object
dialog, select Organization,
then click
.
In the Power Add dialog, enter
the following 6 Organizations
(separate entries by pressing
Page 48 of 355
ENTER):
Finance
Facilities Management
Marketing
Conference Management
Lodging Management
Sales
Page 49 of 355
To maintain the appearance of the model, click on the Auto Layout button
on the main toolbar.
dialog.
The Auto Layout Instructions dialog offers 3 options and 4 layout formats
for hierarchy models like the Organization model. For now, keep the default
selections for options and format.
checkbox is checked, uncheck it
However, if the
since you want to auto layout the entire model.
Click OK to close the dialog and auto layout the model. If Auto Layout does
not work, click the Object (selector)
button on the Object Creation
toolbar first before trying Auto Layout again.
Once the initial organizations are defined, include the roles in the model.
Position the mouse in an open area of the model below the child
organizations and draw a small box with the left mouse or, if preferred, utilize
the Object (selector)button
on the Object Creation toolbar, or the Model
Palette per the previous instructions. Either technique will launch the Add or
Select Object dialog.
In the Add or Select Object dialog select Role, and then click
.
Page 50 of 355
In the Power Add dialog, enter the following 7 Roles (separate entries by
pressing ENTER):
Conference Manager
Reservation Specialist
Sales Rep
VP Sales
Click OK or press ENTER again when you have finished entering all the roles.
Place the mouse over an unattached role, hold down the mouse button, and
drag to its immediate parent to establish a parent-child link. The role-toorganization parentage is shown in the following example. Attach all roles to
their appropriate parent organization as below.
Page 51 of 355
To maintain the appearance of the model, right click in an open area of the
model and select Auto Layout from the context menu. This will launch the
Auto Layout Instructions dialog.
This time, experiment with all 4 layout formats
offered by the Auto Layout Instructions
dialog for hierarchy models like the
Organization model.
checkbox is checked,
Remember, if the
uncheck it since you want to auto layout the entire model. If Auto Layout does
not work, click the Object (selector)
first before trying Auto Layout again.
Page 52 of 355
Review the interpretation and notice that the model graphics and the
interpretation are synchronized. The items listed in the interpretation are
live, meaning you can double-click on them and invoke their detail dialogs,
just as you can in the model itself.
Close the interpretation and maximize the organization model.
This completes the Organization Model exercise.
Page 53 of 355
59
Select a subject
Launch the model
Add objects into the model
Create parent/child links
60
Page 54 of 355
Metastorm
62
Page 55 of 355
Delete
Delete
Permanently removes object /
model / grid
Confirmation dialog
Can not Undo
Dialog displays delete (destroy)
implications
Delete object
Delete model
Deletes model including custom
layout and drawing objects
Does not delete component objects
or associations
1999 - 2007 Metastorm, Inc.
63
Exclude
Exclude
64
Page 56 of 355
Hide
Hide
Visually removes object from
model
Can undo
(via Edit > Show Hidden)
Temporary (else delete /
exclude)
No effect on interpretation
No delete / exclude implications
Used for presentation purposes
65
Clone
Clone
Immediately
after cloning
Sales Rep
Sales
Sales
Rep*
After changes
applied
Inside
Sales
Rep
Sales
Rep
Sales
Manager
Sales
Sales
Rep
Sales
Manager
66
Page 57 of 355
67
Search Tool
Set Limits
Object Types
Dimensions
68
Page 58 of 355
Located under
Tools menu
Perform Search
first to understand
impact of Replace
69
Association Grid
Relates who, what, when,
where, why, and how objects
together
Hundreds of associations
available
Example shows where
business processes are
performed
Filtering options (rows or
columns eliminated)
Model interpretation includes
associations
Publishable
Various export options (e.g. MS
Excel, MS Access)
1999 - 2007 Metastorm, Inc.
70
Page 59 of 355
Key Associations
Artifacts Links to files created by other applications, links
to web pages or links to generate e-mail messages. May
b associated
be
i t d with
ith multiple
lti l objects.
bj t
Rules - Policies, conditions or triggers. May be associated
with multiple objects.
Issues - Issues for resolution. May be associated with
multiple objects.
Artifacts, Rules and Issues are associated the same as other objects
via the Associations tab on the details dialog for each object
71
72
Page 60 of 355
Artifact Details
Name artifact
Describe artifact (optional)
Specify the object location (path and file name or URL address)
(press the ... button to browse for a file)
(press the UNC format button to convert the location to the
universal naming convention format to replace device names)
Specify the type (EMail will launch your email subsystem)
Designate whether to launch files internally in ProVision
(only OLE compliant files can be launched internally).
1999 - 2007 Metastorm, Inc.
73
Rule Detail
Add new
Delete existing
Modify existing
Select existingg
74
Page 61 of 355
Issue Detail
Add new
Delete existing
Modify existing
Select existing
75
Defining Notes
Notes
Applies to a single
object or model
Labeled remarks
and/or reminders
Add new
Delete existing
Modify existing
Name
Text
Notification Time
Search only
occurs during
notebook open
Generates an
Alert
76
Page 62 of 355
Prior
Next
Home (in Explorer)
Index (toggles Index Bar)
Context Help
1999 - 2007 Metastorm, Inc.
77
Model Toolbar
Print
Print Preview
Zoom Closer
Zoom Away
Zoom Area
Fit to View
Pan
Auto Layout
Link Style
Default
Number
Interpret
Layers
1999 - 2007 Metastorm, Inc.
78
Page 63 of 355
Controlling Toolbars
Style Tab
Check box to display
toolbar
Controls tooltips
Controls Flat Look
Can create Custom
Toolbars
If modified, can
Reset standard
toolbars
1999 - 2007 Metastorm, Inc.
79
Toolbar Configuration
Configuration Tab
Provides Description of
selected toolbar button
Allows drag-and-drop of
buttons to custom (or
standard) toolbars
80
Page 64 of 355
Metastorm
Notes
_______________________________________________
_______________________________________________
_______________________________________________
_______________________________________________
_______________________________________________
_______________________________________________
82
Page 65 of 355
Page 66 of 355
In this exercise, use the edit capabilities within ProVision to extend the Fill Order
workflow model. First, ILLUSTRATE the Delete operation by simply examining the
Confirm Destroy dialog, but CANCEL to leave this component in the model.
Place the mouse over the 1 Complete Order activity and click the right mouse
button once to reveal its context-sensitive menu.
Select Delete from the pop-up menu to invoke the Confirm Destroy dialog.
Read the Confirm Destroy dialog information. This dialog provides a listing of
all of the activitys related components that would be permanently deleted and
provides information regarding the components usage in other models (examine
the Detach and Where Used tabs). To leave these components in the notebook,
click
Back in the workflow model, click once on the 1 Complete Order activity to
select it.
Select the Edit | Hide menu option to visually remove the 1 Complete Order
activity and its workflows from view. The Hide operation, being temporary, does
not alter the models interpretation.
Page 67 of 355
Select the Edit | Show Hidden menu option to restore the activity and its
workflow.
and then
Right click on Rules (Adherence), select Create, and in the Power Add dialog
box, enter Preferred Customers, hit Enter, and click OK.
Page 68 of 355
Under Rules, double click on the Preferred Customers rule and enter the
description, Preferred Customers will receive priority handling of their order
through shipment in the Rule dialog box. Click OK.
In the All Objects section, click in the box for Preferred Customers to associate
this new rule to the Submit Order activity. In the Selected Objects section,
Page 69 of 355
expand the plus sign in front of Rules to see that this rule is associated to this
activity.
When an object is interpreted, rules associated with it will interpret. This will now be
illustrated for 2 Submit Order.
on the Main toolbar to display the interpretation for the Fill
Click interpret
Order workflow model.
Click on the 2 Submit Order activity in the model to position the interpretation to
that object.
Notice that the rule interprets for that activity (see example below).
Page 70 of 355
Artifacts embed links to other application objects and these links can be assigned to
either model objects or models themselves. This is useful if there are other applications
containing information pertinent to an object or a model that you want to reference
rather than duplicate.
In the Fill Order Workflow Model, double click on the 2 Submit Order activity to
bring up the Activity: Submit Order dialog box and select the Associations tab.
In the All Objects section, expand the plus sign in front of Artifacts
(Attachment) to view the current artifacts available for association to the objects
in this notebook.
Right click on Artifacts, select Create, and in the Power Add dialog box, enter
Getting Started with ProVision, hit Enter, and click OK.
Page 71 of 355
In the All Objects section, click in the box for Getting Started with ProVision to
associate this new artifact to the Submit Order activity. In the Selected Objects
section, expand the plus sign in front of Artifact to see that this artifact is
associated to this activity.
Page 72 of 355
To complete the link to the artifact, under Artifacts in the Selected Objects
section, double click on Getting Started with ProVision to bring up the Artifact
dialog box.
Page 73 of 355
In the Fill Order workflow model, click the Models describe this object
indicator at the bottom of the 2 Submit Order activity and click on the document
name to launch the Getting Started with ProVision document.
After browsing through this document, close it by clicking on the LOWER close
in the upper right corner.
button
ProVision itself.
In the Search dialog, enter america in the Find What edit box.
Page 74 of 355
Ensure the Name check box is selected in the Look At: area, and the Match
Any Part radio button is selected in the Criteria area.
Click the Only search active model and Mark Matches check boxes in the
Special area.
Click the Search button to begin the search. ProVision reports that two objects
matching the search criteria were found. It also places a checkmark indicator
on each matching object.
Click the check mark indicators
on the two identified locations to remove
them. (Select Edit | Unmark All to remove all check marks).
This completes the ProVision Editing & Key Associations exercise.
Page 75 of 355
83
84
Page 76 of 355
Metastorm
Object Appearance
86
Page 77 of 355
Metastorm
Object Appearance
Bold Text
It li i T
Italicize
Textt
Underline Text
Set Font Color
Set Rounding
Set Shadow
Set Object Color
88
Page 78 of 355
89
Build Product
90
Page 79 of 355
91
92
Page 80 of 355
Gallery Bar
You can view or modify the
graphics stored Gallery.
93
Orientation Tools
Bring to Front
Send to Back
Bring Forward
Send Backward
Rotate Shape 90 Degrees
Flip Horizontally
Flip Vertically
Align Left
Align Right
Align Top
Align Bottom
Align Horizontal Centers
Align Vertical Centers
Space Horizontally
Space Vertically
Make Same Width
Make Same Height
Make Same Size
94
Page 81 of 355
Format Menu
95
Drawing Toolbar
Add Rectangle
Add Ellipse
Add Polygon
Add Triangle
Add Diamond
Add Hexagon
Add Line
Add Link
Add Text
96
Page 82 of 355
Metastorm
Model Settings
98
Page 83 of 355
99
100
Page 84 of 355
101
102
Page 85 of 355
103
104
Page 86 of 355
105
106
Page 87 of 355
Model Associations
Artifacts
Capabilities
Issues
Rules
Standards
107
108
Page 88 of 355
Metastorm
Notes
_______________________________________________
_______________________________________________
_______________________________________________
_______________________________________________
_______________________________________________
_______________________________________________
110
Page 89 of 355
ProVision allows you to change the visual attributes of any modeling object, and the
arrangement of the objects in the model.
from the menu bar to hide the
Select View -- Show Indicators
indicators (e.g.
) that appear on the lower center portion of the objects.
Again, select View -- Show Indicators from the menu bar to now show the
indicators (e.g.
) that appear on the objects. This option toggles the setting.
Page 90 of 355
ProVision allows you to change the appearance of the lines in your model.
Select View -- Toolbars and then check the
Orientation Tools. This will open the Orientation
toolbar. Its default position is below the model
tabs.
Page 91 of 355
Select Edit -- Undo Style to place the name in the center of the Complete
Order activity again.
Click in an open area of the modeler to deselect the Complete Order activity.
[To hide this toolbar, Select View -- Toolbars and then uncheck the Object
Styles.]
You will now add a graphical adornment to the Fill Order workflow model and modify its
style settings.
Ensure that the Gallery Bar appears in the Index Bar. If it does not appear,
select View/Index Bar and check the Gallery Bar to enable it.
Page 92 of 355
Select the octagon by clicking on it once. Grab the bottom handle and stretch
the octagon until it is as deep as it is wide.
&
p
o
t
S
Double-click the mouse on the shape to open its Drawing Description dialog.
!
w
e
i
v
e
R
In the dialog, enter the name Stop and Review! to display this
within the shape. Click OK to close the dialog.
Click the right mouse button on the shape to display its shortcut
menu, and then select Style from the menu. The Style dialog for
the shape is displayed.
The Style dialog contains all of the visual properties for a selected object, link, or
adornment. Notice that the example object in the dialog displays the default style
settings for the new shape. Changes will be made to these default settings.
The Text tab is displayed first by default. On this tab, use the Color
dropdown to change the font color to black. Note how the change
is immediately reflected in the example area.
Check the Underlined checkbox to underline the name.
Click the Centered radio button within the Vertical Justification
area.
Select the Shape tab in the dialog.
In the Shape area of the dialog, use the Color dropdown to change the shape
color to red.
Click the Gradient Color
Fill button to launch the
Gradient Selection dialog.
Select the Angled Styles
radio button or make a different gradient selection, if desired.
Click OK twice to close the dialogs and save your changes.
Verify the style changes in the model.
Page 93 of 355
Select View -- Toolbars and then check the Drawing Tools. This will open the
Drawing toolbar. Its default position is below the Index Bar.
Grab each end of the link and place it at different points along the border of
each object to arrange as desired.
Drag the drawing and/or the Ship Components activity around the model.
Notice that the link adjusts to keep the line attached.
To hide the Drawing Tools toolbar, click the View -- Toolbars menu option to
launch the Toolbar Customization dialog and then uncheck Drawing Tools.
Close the Fill Order Workflow Model by clicking the lower close button
upper right corner. The upper button will close ProVision.
in the
Page 94 of 355
3. Why should you not use the rubber band link to draw a line
between objects?
4. Can models have associations?
111
Object
Obj t Appearance
A
112
Page 95 of 355
Notes
_______________________________________________
_______________________________________________
_______________________________________________
_______________________________________________
_______________________________________________
_______________________________________________
113
Notes
_______________________________________________
_______________________________________________
_______________________________________________
_______________________________________________
_______________________________________________
_______________________________________________
114
Page 96 of 355
Actors
Regions
Business Interactions
Deliverables
116
Page 97 of 355
Shows organizational
boundaries
Interactions between internal
and/or external actors
Consumes resources
Produces products/services
Feedback (optionally)
Concentrates on interactions
and responsibilities of actors
Internal players
Customers
Suppliers
Competitors / Regulators
Support Organizations /
Other Parties
117
Notes
_______________________________________________
_______________________________________________
_______________________________________________
_______________________________________________
_______________________________________________
_______________________________________________
118
Page 98 of 355
Metastorm
Example
120
Page 99 of 355
Actors
Major Players
Research
Community
Product
Development
Capital
Markets
Types of actors
Finance
Component
Vendors
1999 - 2007 Metastorm, Inc.
Markets
Organizations
Roles
People (possible)
Systems (possible)
121
Actor
Market
Organization
Role
Person
122
Markets
A set of people or organizations which are
managed in a similar manner
Category of people or organizations
usually external to the enterprise
Same interactions with the business
domain
Managed in the same way
Market Segments
Similar wants and needs
Common p
purchasing
gp
patterns
Industries
Productive or profit-making enterprises
Concentrate on a business or discipline
(e.g., automotive, aerospace)
123
Organizations
A formalized set of people
usually internal to the enterprise
(e.g. company, division,
department) having a common
mission
mission
Organization structure (vertical)
view of the business
Inside the business domain Identifies organizational units
responsible for performing work
within the scope
Outside the business domain id tifi iinternal
identifies
t
l customers,
t
suppliers, and support
organizations
Identifies the stakeholders for
BPA project
(organizations inside the business
domain)
1999 - 2007 Metastorm, Inc.
Structure
High-level for Business
Interaction Model
Can be decomposed (partitioned)
Arranged hierarchically
Multiple parentage supported
(matrix / dotted line relationships)
BIM includes organization units at
the appropriate level
Qualit y
W idget s
F inance
Market ing
Production
Product
Developm ent
F ield
Operations
124
Roles
Category of people performing a
defined set of business
responsibilities
Type of employee
Type of individual customer / supplier
Type of contract person
125
Business Domain
126
Customers
Receive products and services from the
business domain or competitors
Have needs and wants concerning the
products and services
May consume or resell products
Typically includes external customers
(markets and roles),
internal customers (organizations and
roles)
1999 - 2007 Metastorm, Inc.
127
Suppliers
Provide resources to the business domain
or to competitors
View
Vi
th
the b
business
i
d
domain
i as a customer
t
Should try to meet the needs and wants of
the business domain
May produce or resell supplied products
Typically includes external customers
(markets and roles),
internal customers (organizations and roles)
1999 - 2007 Metastorm, Inc.
128
Competitors
Market Competitor
Resource Competitor
129
Business Interactions
130
Business Interaction
A relationship
p between two actors
where specific goods, services,
and/or information is exchanged
May involve internal and/or external
actors
Concerned with relationship not discrete
flows
Major focus for improving efficiency and
effectiveness
131
Business Interaction
132
Sources Perspective
Priority
Importance in competing for this customer
Higher priority indicates more resources invested in capturing and
satisfying customer
Competitive advantage
Factors such as price, quality or timeliness which are meaningful
to the recipient (customer)
Producer/Reseller
1999 - 2007 Metastorm, Inc.
133
Recipients Perspective
Satisfaction Rating
Evaluates the performance of the source (supplier)
Evaluates the performance of the deliverable
Needs/Wants
Performance requirements of the source or deliverable
Consumer/Reseller
134
135
Environmental Influence
A factor that affects enterprise strategy
Which markets to pursue
Which goals to prioritize
How processes function
Limit ed Oil
Supply
Global
W arm ing
Government regulations
Economic / Demographic factors
Cultural factors
Political factors
136
Metastorm
Development Approach
1. Identify actors within the business
domain
2. Identify customers
3. Identify customer interactions
4. Identify suppliers
5. Identify supplier interactions
6. Develop internal interactions
7. Identify competitors / regulators /
support organizations / external
parties
138
Identify actors
Sponsors and stakeholders
Islands of authority
Highest level organizations
fully within scope
Optionally identify
organizations
i ti
ffor multiple
lti l
locations
Functional organization or
role operating at multiple
sites
139
Identify Customers
Customers
Receive products and services from business domain
May be within company, but outside domain
Type
Markets Defined market segments, categories of customers
Organizations external to the enterprise
Organizations
Organizations internal to the enterprise
Roles Categories of internal or external individuals
140
Feedback
Directs effort of business domain
141
Identify Suppliers
Suppliers
Provide resources to the business domain
May be within company, but outside domain
Type
Markets
Defined supplier segments, categories of suppliers
Organizations external to the enterprise
Organizations internal to the enterprise
Roles Categories of internal or external individuals
acting
ti as suppliers
li
142
Resources
Required to produce products and
services
Many types (e.g.
(e g material,
material
information, financing, personnel,
facilities)
Feedback
Help supplier meet requirements
1999 - 2007 Metastorm, Inc.
143
Deliverables
IIntermediate
t
di t workk
products between
resources and
products/services
144
Identify Competitors
Market Competitor
Identify competing actor
Identifyy competing
p
g
product/service
Pair with targeted
customer(s)
Resource Competitor
Identify competing actor
Identify resource competition
Pair with affected supplier(s)
145
Select a subject
Launch the model
Add actors into the model
Create business interactions
Region
Actor
Business Interaction
Deliverable
146
Metastorm
Notes
_______________________________________________
_______________________________________________
_______________________________________________
_______________________________________________
_______________________________________________
_______________________________________________
148
DESCRIPTION
1. Read the following textual business scenarios describing Conference Administrations environment and business interactions.
2. Identify the two actors involved in each scenario and find them on the provided partially completed BIM.
3. Identify the direction of the interaction (responsibility) between the actors.
4. Label the interaction, by specifying a deliverable, which captures the relationship
semantics between the actors.
Two examples have been provided below.
Example Scenario 1 details: Conference Management coordinates flight reservations
(the airline, the dates and times of arrivals and departures, seat assignments, etc.) by
interfacing with Travel Agencies for their customers. This type of reservation may be
handled through PRCs one-stop-shopping concept. However, Conference Administration will not get involved past the reservation stage.
Example Scenario 2 details: Within Conference Administration, Conference Management requests facilities with specific characteristics from Facilities Management. Initially,
the availability of facilities is provided to help with conference planning, and ultimately the
facilities themselves are provided per the committed conference schedule.
Example 1
Example 2
Using the BIM example above as the exercise worksheet, read each of the following six
textual scenarios (3 8) and fill in the appropriate business interaction link details.
Scenario 3 details: Conference Management coordinates car rental reservations by
interfacing with Car Rental Agencies for their customers. This type of reservation may
be handled through PRCs one-stop-shopping concept. However, Conference Administration will not get involved past the reservation stage.
Scenario 4 details: Conference Management coordinates contracted entertainment
(outings, tours, concerts, etc.) provided by Entertainment Vendors in support of each
conference.
Scenario 5 details: Sponsors are organizations that define and fund a conference.
Conference sponsors interact with Sales to understand and submit requests for conferences. After conferences are scheduled, sponsors will receive confirmations containing
session, equipment, lodging, facility, and entertainment schedules and pricing from
Sales.
Scenario 6 details: Within Conference Administration, Sales formalizes Sponsor requests, producing conference orders for Conference Management to schedule. Conference Management, in response to this request from Sales, will schedule the conference and provide the scheduled conference to Sales.
Scenario 6
Scenario 5
Scenario 8
Scenario 7
Scenario 3
Scenario 4
This creates the subject business domain and opens the Business Interaction Modeler at the same time. Before you add actors to the model, correctly name the center
region of the model.
Double-click in the Business Domain region to invoke the Region Detail dialog.
Replace the regions name with the name, Conference Administration.
You will now include organizations in the model. You can move them to the appropriate
region afterwards.
Place your mouse in the center of the region labeled Conference Administration. Click and drag diagonally to draw a small box. The Add or Select Object
dialog appears when you release the mouse button.
Alternately, this dialog can also be invoked by first clicking the Organization button
on the Object Creation toolbar and then clicking on the area of the
model where you want to add an actor.
In the Add or Select Object dialog, select Organization to add or select objects
of this type.
If you performed the earlier exercise that defined PRCs organizational structure, you
will select some of those organizations for inclusion in this model. If these organizations
do not exist, you will need to add these organizations. If you are in doubt, try selecting
them first.
Click either
or
whether the organizations already exist or not.
In the Power Select or Power Add list box, select or add the following organizations. For multiple selections, hold down the CTRL key.
Sales
Facilities Management
Conference Management
Lodging Management
Marketing
Finance
Click OK when you have finished selecting/adding the organizations. The organizations will appear overlaid in the model. Click and drag each organization
to position them, which includes moving them to the appropriate region.
You will now include in the model the other actors that are external to the Conference
Administration business domain.
Click and drag the mouse in the Suppliers region of
the model to invoke the Add or Select Object dialog
that allows you to add or select additional actors.
In the Add or Select Object dialog, select Market to
add objects of this type to the model.
Select
to the model.
Now that you have identified the major internal and external actors for Conference
Administration, you can add the business interactions that exist between them.
on the Object Creation toolbar to add Business In Select the link button
teractions. Notice that the cursor changes when positioned over an actor in the
model.
Place the mouse over Sales within the Conference Administration region, hold
down the mouse button, and drag to Sponsor in the Customers region to establish a business interaction.
Double-click the new business interaction to open its dialog.
In the Name edit field, enter Conference Confirmation, then click OK.
Click OK to close the Business Interaction dialog.
As above, you will now add the other business interactions. When you have completed
adding all of the business interactions listed below, your model should look similar to the
following example.
Notice that Facilities Management provides Facilities to both Conference Management
and Lodging Management. Once the deliverable, Facilities, has been added, you
should select it from the Deliverable drop-down list rather than trying to add it a second
time.
To
Deliverable
Sales
Marketing
Sales Forecast
Sales
Sponsor
Conference Confirmation
Conference Management
Sales
Scheduled Conference
Conference Management
Participant
Conference Enrollment
Conference Management
Finance
Sponsor Charges
Facilities Management
Conference Management
Facilities
Facilities Management
Lodging Management
Facilities
Lodging Management
Conference Management
Block Reservation
Lodging Management
Finance
Guest Charges
Lodging Management
Guest
Lodging
Travel Agency
Conference Management
Flight Reservation
From
To
Deliverable
Conference Management
Entertainment Vendor
Conference Management
Contracted Entertainment
Sponsor
Participant
Conference Advertising
Click on any object in the model to position the interpretation to that object, including the business interactions.
Review the interpretation and notice that the model graphics and the interpretation are synchronized. The items listed in the interpretation are live, meaning
you can double-click on them and invoke their detail dialogs, just as you can in
the model itself.
Close the interpretation and maximize the business interaction model.
This completes the ProVision Business Interaction Modeler exercise.
149
Actors
Regions
Business Interactions
Deliverables
150
Metastorm
Process Identification
Business Process Scope
& Context
using Communication Model
152
Process Characteristics
Supplier
Input
Initiating
I
iti ti Event/
E
t/
Input Deliverable
Process
Business
Process
Output
Customer
Terminating
T
i ti Event/
E
t/
Output Deliverable
Supplier
Types
Customer
Types
Market
Market
Organization
Organization
Role
Role
Person
Person
System
Business Process:
Process
A set of sequentially related activities that
produce a product, service or deliverable.
System
Process
1999 - 2007 Metastorm, Inc.
153
Product
Management
Operations
Marketing
Sales
Actor types
High-level
Organizations
Customer
Support
...
Mid-level
Organizations
Mid-level processes
100-500
Roles
Detail-level processes
(1000s)
User-system interfaces
System-system interfaces
Systems
Automated processes
(1000s)
1999 - 2007 Metastorm, Inc.
154
Convert
Sequence (series) of activities
Goal-directed
Produce
155
Scoping a Process
Process Context Model created with Communication
Modeler
156
Input Deliverable
Event
Event
Output Deliverable
Actor
Address Change
g Received/
Output Deliverable
Business Process
157
Make use of
what is
already
known
158
Business Interactions
Product
Business
Domain
Customer
159
Business
Domain
Customer
To Communication:
"Order Received"/Order
Order Acknowledgement
Order Rejection
Business Domain
Product Shipment
Customer
"Payment Received"/Payment
160
Event
A significant occurrence which
obligates the business domain to take
action
Purpose of Event Identification
Identifies starting point for business
processes
Partitions business domain into meaningful
and manageable chunks of work
Types of events
Signal (most common)
Time
Change
1999 - 2007 Metastorm, Inc.
161
Signal Event
"Request Submitted"/Request
"Funds Submitted"/Funds
Business
Domain
"Transaction Cancelled"/Transaction ID
Customer
162
Time Event
Product Shipment
Customer
Business
Domain
Internally detected
Examples
Scheduled
Time to Ship Product
Absolute
Month Ends
Relative
Payment Overdue
1999 - 2007 Metastorm, Inc.
163
Change Event
Order Acknowledgement
Order Rejection
Customer
Business
Domain
164
Process Identification
Internal (interim)
produced for internal consumption
has value added as it proceeds through a process
facilitates the production of external deliverables
165
Deliverable Production
Request Acknowledgement
Advice
Account Statement
Business
Domain
Customer
External Deliverables
to Customer
Internal Deliverables
External Deliverables
166
Process Identification
167
Supplier
Business
Domain
Examined to discover
Signal events
Time events
Change events
Resource inputs
168
Process Identification
Business
Interaction
Communications
Material
Supplier
Business
Domain
Order
"Order Acknowledged"/Order Acknowledgement
"Order Rejected"/Order Rejection
Supplier
Business Domain
Material Return
"Invoice Received"/Invoice
Payment
169
170
Eventt Type
E
T
Signal
Signal
Eventt Name
E
N
Order Submitted
Payment Submitted
Signal
Order Canceled
Time (Scheduled)
Time to Ship
Ti
Time
(Relative)
(R l ti )
P
Payment
tO
Overdue
d
Change
Order Invalid
Change
Change
171
Type
Deliverable Name
External
Order Acknowledgement
External
Order Rejection
External
Product Shipment
External
Invoice
Internal
Approved Order
Internal
Scheduled Order
172
Events
Deliverables
Order Submitted
Order Acknowledgement
Payment Submitted
Invoice
Approved Order
173
Processes
Order
Order Submitted
Submitted
???
Payment Submitted
???
???
???
???
Deliverables
Order Acknowledgement
Approved Order
???
Invoice
???
174
Order
Order Submitted
Submitted
Approved Order
Identify Process
External
Deliverable
Order Submitted
Accept
Order
Event
Order Acknowledgement
Internal
Deliverable
Process
Approved Order
175
Accept
Order
Submitted/Order
Order Submitted
Source of
Event
Signal Events
Input Deliverable
Order Acknowledgement
Approved Order
176
Process Identification
Deliverable
Recipient
Approved Order
Accept
Order
Order
Submitted/OrderOrder
"Order
Received"/Received
Order Acknowledgement
Deliverable
Recipient
Production
Manufacturing
Company
Bi-Directional
Communication
(read clock-wise)
External
Deliverable
177
Accept
Order
Order
Submitted/OrderOrder
"Order
Received"/Received
Order Acknowledgement
Approved Order
Production
Manufacturing
Company
Participating Actors
Internal to Process
178
Accept
Order
Submitted/Order Order
"OrderOrder
Received"/Received
Order Acknowledgement
Production
Manufacturing
Company
Order Submitted
Minor
Events
Order Acknowledgement
Approved Order
Minor
Deliverable
Order Invalid
Credit Limit Exceeded
Minor Events
Order Rejection
(a type of Order
Acknowledgement)
Minor Deliverables
Produced inside a process
(at a lower level of detail)
Produced as a by-product
of a process
Part of another deliverable
179
Name Process
"Payment Submitted"/Payment
Accept
Paymentt
P
Event
Process
Internal
Deliverable
180
Accept
Payment
Manufacturing
Company
Accounts
Receivable
Internal
Deliverable
Source of
Event
System
Recipient
181
Product Ships
"Product Ships"
Shipping &
Receiving
Invoice
Shipment
Event
Invoice
Deliverable
Manufacturing
Company
Accounting
182
Accept
Order
Approved Order
Manufacturing
Customer
Production
Field
Operations
Finance
183
Final Mapping
Events
Order Submitted
Deliverables
Processes
Accept Order
Order Acknowledgement
Approved Order
Payment Submitted
Accept Payment
Product Ships
Inventory Reorder
Point Reached
Accept Order
(modified)
Reorder Notification
Approved Order
184
Initiating Events
Name process/activity
Determine involved actors
Signal events
Time events
Change events
Deliverables Produced
Sources events/deliverables
Receives events/deliverables
Participates internally in process
185
186
Metastorm
Communication Modeler
in ProVision
188
189
A ti it
Activity
Business Domain
Business Process
Equipment
Facility
Location
Market
Organization
Person
Role
System
Topic
190
Adding Objects
Possible Components for
Communication Models For Business Process Context
Models
What Is Done
Components
Activity
Business Domain
Business Process
Who Does It
Market
Organization
Person
Role
Store
System
Where Its Done
Equipment
Facility
Location
What
Wh t is
i done
d
Who does it
191
Communication Links
Deliverable to Right
Event to Right
Accept
Product
Return
Manufacturing
Company
Deliverable to Left
Communication Links
Artifacts
Issues
Rules
Standards
System Interactions
192
Scoping
Business
Processes
Depicting Systemto-System
Communications
1999 - 2007 Metastorm, Inc.
193
Notes
_______________________________________________
_______________________________________________
_______________________________________________
_______________________________________________
_______________________________________________
_______________________________________________
194
Metastorm
Notes
_______________________________________________
_______________________________________________
_______________________________________________
_______________________________________________
_______________________________________________
_______________________________________________
196
at the bottom to
In the Enter the name for a new Business Process edit box, enter Arrange
Conference and click
This creates the subject business process and opens the Communication Modeler at
the same time. Include the business process, Arrange Conference, in the model.
Place the mouse in the center of the model and click and drag diagonally. The
Add or Select Object dialog appears when the mouse button is released.
In the Add or Select Object dialog, select Business Process to add or select
objects of this type.
When Arrange Conference was identified as the subject for the communication
model, ProVision automatically added Arrange Conference as a business
process object in the notebook. Select that object from the drop down list in the
dialog and click OK.
Center the Arrange Conference business process in the model.
Now include actors in the model. The actors are of two types, Markets and
Organizations, so include them in two steps. If the earlier Organization and Business
Interaction exercises were completed, select the actors for inclusion in this model. If
these actors do not exist because they were not previously created, add them. If in
doubt, try selecting them first.
Place the mouse in an open area of the model and click and drag diagonally.
The Add or Select Object dialog appears when the mouse button is released.
In the Add or Select Object dialog, select Market to add or select objects of this
type.
Click either
or
on the dialog based upon
whether the markets already exist (if the Power Select button is not enabled, then
no Markets currently exist in the notebook).
In the Power Select or Power Add list box, select or add the following markets.
For multiple selections, hold down the CTRL key.
Sponsor
Entertainment Vendor
Click OK when finished selecting/adding the markets. Click and drag each
market to an appropriate position surrounding the business process, Arrange
Conference. See the following example.
Repeat these steps (selecting Organization) to include the following
organizations.
Sales
Conference Management
Facilities Management
Lodging Management
Now that the participating actors for Arrange Conference have been identified, add the
communications that exist between them and any applicable events and deliverables.
Select the Link Selector button
which is the last button on the Object
Creation toolbar. Notice that the cursor changes when positioned over an object
in the modeler.
Place the mouse over Sponsor, hold down the mouse button, and drag to
Arrange Conference to establish a communication.
Double-click the new communication to open its Communication Description
dialog. See the following example.
For the Deliverable(to left object) field, click the Add button
Deliverable Detail dialog.
to open the
In the Name edit field, enter Conference Schedule, then select OK.
For the Event(to right object) field, click the Add button
Detail dialog.
In the Name edit field, enter Conference Request Received, then select OK.
For the Deliverable(to right object) field, click the Add button
Deliverable Detail dialog.
to open the
In the Name edit field, enter Conference Request, then select OK.
Click OK to close the Communication Description dialog.
The initiating event and external deliverable for Arrange Conference have now been
included in the model. There are five other participating actors who contribute internally
to Arrange Conference. Their participation can be denoted with communications
without events, deliverables, or directional arrows. Now add the communications that
simply denote participation.
Select the Link Selector button
Place the mouse, in turn, over each of the participating actors, Sales,
Conference Management, Facility Management, Lodging Management, and
Entertainment Vendor, hold down the mouse button, and drag to Arrange
Conference to establish the communications.
Double-click each new communication to open its Communication
Description dialog. For these communications, since they are representing
participation only, events and deliverables do not need to be defined.
However, immediately under the preview area at the top
option for each side
of the dialog, click the no arrow
of the communication to eliminate the arrowheads and
close the Communication Description dialog.
Format the communications as desired. The link style for
each communication (direct, squared, or rounded) can be
changed with the Link Style
toolbar button found in
the Orientation Toolbar. See the example model at the beginning of this
exercise for an example layout.
To interpret the model, click the interpret button
Toolbar or select Interpret from the Tools menu.
Review the interpretation and notice that the model graphics and the
interpretation are synchronized. The items listed in the interpretation are live,
meaning double-clicking on them invokes their detail dialogs, just as within the
model itself.
Close the interpretation and maximize the communication model. This can be
done easily by clicking the interpret button
twice. The first click will position
the interpretation below the model and the second click will close the
interpretation and maximize the model.
This completes the ProVision Communication Modeler exercise.
197
198
Metastorm
Process Modeler
in ProVision
200
Process Modeler
Represents parent/child object
structure for work.
Business Domain
Business Process
Activity
201
General Structure
Legend
Business Domain
Business Process
Activity
202
*
*
Workflow Model
subject
Business Process
or
*
*
*
Workflow Model
component
Activity
only
*
203
Identify Activities
Maintain a consistent level of
abstraction
Activity heuristics
Decomposition Approach
Traverse business process
start with process event
identify activities (process
steps )
identify customer and
supplier activities or use
source/sink
end with deliverables
Receive Order
Check Order
Correctness
Authorize
Order
Time bounded
Produce business-visible
deliverable
May be further partitioned
(later)
Approve Order
Schedule Order
Correct Order
Check
Customer Credit
Acknowledge
Order
204
Pros
Cons
Flexibility
205
206
Metastorm
Notes
_______________________________________________
_______________________________________________
_______________________________________________
_______________________________________________
_______________________________________________
_______________________________________________
208
This process model should be built in the Conference Administration notebook in the
Professional Retreats repository.
If this
notebook is not open, open it now. If needed,
detailed steps follow.
Click on the Repository Bar, and then
click the plus sign in front of the
Professional Retreats repository to
reveal the Conference Administration
notebook. Double click the notebook to open it.
Click on the Inventory Bar in the Index Bar, and click on the Model Inventory
tab
Double-click the Process Modeler folder in the Model Inventory to invoke the
dialog to specify the subject for the model and launch the modeler.
Select Business Domain for the type of object the model is describing and
select Conference Administration and then click
Now that the Process Model for the Conference Administration business domain
exists, add some example child Business Processes, those being:
Arrange Conference
Begin Conference
Enroll Attendee
Cancel Enrollment
Utilize Facility
Clean Facility
End Conference
Link them to their parent, the Conference Administration business domain. Note that
the business process, Arrange Conference, already exists. If needed, detailed steps
follow the example Process Model below.
Place the mouse in the center of the model and click and drag diagonally. The
Add or Select Object dialog appears when the mouse button is released.
In the Add or Select Object dialog, select Business Process to add or select
objects of this type.
If the Communication Model exercise was performed, the Arrange Conference
business process will already exist in the notebook. If so, select it from the drop
down list in the dialog and click OK to add it to the Process Model.
Link the Arrange Conference business process as a child of the Conference
Administration business domain by using a parent/child link
connection from child to parent).
(draw the
The other business processes do not exist yet so they should be Power Added
(see the list above).
After inclusion in the Process Model, also link these business processes to their
parent, the Conference Administration business domain.
Use Auto Layout
above. If Auto Layout does not work, click the Object (selector)
the Object Creation toolbar first before trying Auto Layout again.
button on
Now add child Activities for the Arrange Conference business process. This will
illustrate how business processes can be composed of lower-level activities and will
later be used to illustrate how ProVision synchronizes Process Models and Workflow
Models.
The child activities for the Arrange Conference business process are:
Schedule Conference
After linking the child Activities to their parent Business Process, the complete model
from Business Domain to Business Processes to Activities should have the same
contents as the example below. To match the layout, use the Fork Top Down Auto
Layout option.
209
210
Metastorm
Workflow Modeler
in ProVision
(Basic)
Activity
Workflow lane (Actor)
Workflow
Source / Sink
Deliverable
Event
Decision Point
Junction
212
213
Component activities
Flow of work between activities
Events (initiate process)
Work sequence (control flow)
Deliverables (activity value-add)
214
Process disconnects
Inefficiencies
Bottlenecks
Redundancies
Operational Problems / Opportunities
Process redesign
O
Organizational
i ti
l restructuring
t t i
Job redefinition
Application system redevelopment
215
216
217
Source / Sink
Source
A starting point in a workflow model
Used to identify boundary of model with input
d li
deliverable
bl and/or
d/ initiating
i iti ti eventt
Workflow lane denotes initiator
Sink
An ending point in a workflow model
Used to identifyy boundary
y of model with final
deliverable production
Workflow lane denotes recipient of
deliverable
218
Activity
A step in a process assigned
to a particular actor for
performance
performance
Receive Order
Approve Order
Schedule Order
Internal
External (if of interest)
Acknowledge
Order
219
Activity Properties
Additional Properties
Name
Logic
Inputs/outputs (CRUD C t Read,
Create,
R d U
Update,
d t D
Delete)
l t )
Goals targeted
Deliverables produced
Locations where performed
Measured with
Opportunities for
Problems with
Qualifications required
Systems implemented by
Components implemented by
Business Terminology
Description
Statement of purpose or
responsibility
p
y (g
(goal attained))
Description of
transformation/value add
220
Activity Timing
Timing Attributes for Activities
In-queue Time
Before work begins
No resource costs
Work Time
Time doing useful work
Resource costs accumulated
Out-queue Time
After work is completed but before
deliverable is passed on
No resource costs
221
Activity Costing
Cost Types
Di
Directt costs
t - Incurred
I
d each
h ti
time th
the activity
ti it iis
performed
Indirect costs - Incurred over an interval of time
without regard to frequency of activity
Resource costs - Incurred by a role,
organization, system, equipment, or facility
during work & work delay time
222
Responsible Actors
Workflow Lanes
Horizontal bands show responsible actor
Internal
Responsible actor within the business
domain
External
Responsible actor outside of the business
domain
223
Control flow
224
Workflow Properties
Approve Order
Schedule Order
225
Deliverable
A produced, value-add work product
Produced by a business process/activity
May be external or internal
External
provided to/from customers
(workflows for customer interactions)
provided by/to suppliers
(workflows for supplier interactions)
Interim (Internal-only)
produced
p
for internal consumption
p
has value added as it proceeds through a
process
facilitates the production of external
deliverables
226
Event
Initiates a business process or activity
Types of events
Signal
Incoming request from external actor
(e.g. order received)
Change
Threshold transition for internal deliverable
(e.g. low inventory)
Time
Time-based trigger
gg of significance
g
to business
(e.g. year-end, 90-days after sale)
227
Decision Point
228
Junction
Divergent Junction
Splits a workflow deliverable
and passes control to several
subsequent activities
simultaneously
i l
l ((assuming
i
equal workflow transit times)
Convergent Junction
Can synchronize and combine
workflow
kfl
deliverables
d li
bl before
b f
control is passed to the
subsequent activity
229
Business
Process
Activity
Event
Source
Workflow
Sink
Deliverable
Workflow Lane
(Responsible Actor)
230
Loop
Back
Decision
Points
Junction
(Divergent)
231
232
Metastorm
Notes
_______________________________________________
_______________________________________________
_______________________________________________
_______________________________________________
_______________________________________________
_______________________________________________
234
Notes
_______________________________________________
_______________________________________________
_______________________________________________
_______________________________________________
_______________________________________________
_______________________________________________
235
Notes
_______________________________________________
_______________________________________________
_______________________________________________
_______________________________________________
_______________________________________________
_______________________________________________
236
Spon sor
"Conference Request
Received"/Conference Request
Be gi n
Sal es
Develop
Conference
Order
Conference Managem ent
Present
Conference
Schedule
Conference Order
Conference Schedule
Develop
Conference
Requ irem ents
Schedule
Conference
Equipment Requirem ents
Sessions Requirements
Provi de Lodging
Avai l abi li ty
Lodging Availability
Provi de Faci li ty
Avai l abi li ty
Facility Availability
Provi de
Entertai nm ent
Avai l abi li ty
Entertainm ent
Availability
The workflow model should be built in the Conference Administration notebook in the
Professional Retreats repository. If this notebook is not open, open it now. If needed,
detailed steps follow.
Click on the Repository Bar, and then
click the plus sign in front of the
Professional Retreats repository to
reveal the Conference Administration
notebook. Double click the notebook to
open it.
Now, click on the Inventory Bar in the
Index Bar, and click on the Model Inventory tab
display the models.
at the bottom to
If the previous Communication Model exercise has been completed, then it can be
utilized to launch the workflow model and pre-populate it with workflow lanes. If the
previous Communication Model exercise was not completed, proceed to the next page.
If the Communication Model exercise was completed, use it as the starting point for
the workflow model.
If the Arrange Conference communication model
is not already open, then click the plus sign in front
of the Communication Modeler folder in the
Model Inventory to show the existing
communication models. Double-click on Arrange
Conference(Business Process:) to launch the
communication model previously built.
The
business
process,
Arrange
Conference, displayed in the middle of the communication model, is the desired
subject for the workflow model. Right-click on this business process in the
communication model to display its context menu and then select Workflow
Modeler to launch a workflow model with this business process as the subject.
Notice that the actors, depicted as workflow lanes, have been supplied
automatically. If the Process Model exercise was completed, the child activities
will also be present below the workflow lanes.
Arrange the sequence of the workflow lanes (actors) into the following sequence:
Sponsor, Sales, Conference Management, Lodging Management, Facilities
Management, and then Entertainment Vendor. The workflow lane order is
changed by selecting a workflow lanes icon (i.e. picture on the left in the
workflow lane) and dragging vertically. To move a lane to the top, the topmost
lane must be moved down.
The next two (2) pages of the exercise cover adding the workflow lanes (actors) if
the Communication Modeler Exercise was NOT completed. Therefore, these two
pages can be skipped.
Skip the next 2 pages of this exercise if you are using the Arrange Conference
communication model to launch the workflow model with pre-defined workflow lanes,
per the above instructions.
If you DID NOT perform the previous Communication Model exercise, perform the
following steps on this page and the next:
Double-click on the Workflow Modeler folder in the Model Inventory to display
the Select Subject for Workflow Modeler dialog that will allow you to specify the
subject and launch the workflow model.
Click Business Process, enter Arrange Conference as the name, and click
to launch the model.
button once
Using the Object Creation toolbar, click the Workflow Lane
and then click inside the model to invoke the Add or Select Object dialog.
Depending on which, if any, of the previous exercises were completed, the actors
(workflow lanes) utilized for the workflow model may or may not exist. If the actors
exist, you will Power Select them; otherwise, you will Power Add them. If in doubt,
try selecting them first. Since there are two (2) types of actors, markets and
organizations, you will have to perform the operation twice.
either
or
Sales
Conference Management
Facilities Management
Lodging Management
Sponsor
Sales
Conference Management
Lodging Management
Facilities Management
Entertainment Vendor
The workflow model for Arrange Conference should now contain 6 workflow lanes,
either by having them provided via the Communication Model or adding them directly.
These represent the actors that have responsibilities in the Arrange Conference
business process. Also, if the Process Model exercise was completed, the 7 child
activities will also be present below the workflow lanes.
The Arrange Conference business process begins with the receipt of a Conference
Request from a Sponsor. Represent this starting point by adding a Source to the
model in the Sponsor workflow lane (in the upper left corner).
Select the Source/Sink button
Click the mouse button once in the Sponsor workflow lane of the modeler.
In the Add Object dialog, select Source to first add the starting point to the
model.
The Arrange Conference business process ends with the receipt of a Conference
Schedule Presentation by the Sponsor. Represent this ending point by adding a Sink
to the model in the Sponsor workflow lane (in the upper right corner).
Select the Source/Sink button
Click the mouse button once in the Sponsor workflow lane of the modeler.
In the Add Object dialog, select Sink to add the ending point to the model.
With the definition of the starting and ending points for the Arrange Conference
business process the upper-most workflow lane, Sponsor, should look similar to the
example below.
Spon sor
Sales receives the Conference Request from the Sponsor. Sales transforms the
rough Conference Request into a Conference Order that can be provided to
Conference Management for further development. This value-add transformation is
known as the Develop Conference Order activity.
As previously noted, if the Process Model exercise was completed, the seven child
activities will already be present in the workflow model positioned below the workflow
lanes since ProVision doesnt know which activity belongs to which workflow lane (i.e.
ProVision doesnt yet know who is responsible for each activity). If the Process Model
was not completed, then each child activity must be added and positioned in the correct
workflow lane.
The next steps assume that the Process Model exercise was performed but, if it was
not, simply add and position the child activities rather than simply moving them to the
correct workflow lane.
Reposition the Develop Conference Order activity from the bottom of the model to the
Sales workflow lane, on the left-hand side, and connect it with the Source in the
Sponsor workflow lane by drawing a workflow. If needed, details follow.
Locate the Develop Conference Order activity below the bottom workflow lane
and drag and drop it into the Sales workflow lane as in the example below.
Notice that the Action Pending
indicator disappears from the bottom of the
activity as it is assigned to a workflow lane. This corresponds to a change in the
workflow models interpretation whereby Sales has been assigned responsibility
of the activity. The top two workflow lanes should now look similar to the
example below.
Spon sor
Sal es
Develop
Conference
Order
To add the workflow between the Sponsor and Sales, click the Link (selector)
button
Place the mouse over the Source in the Sponsor region, hold down the mouse
button, drag to Develop Conference Order within the Sales region and release
the mouse button to create a workflow.
Double-click the newly created workflow to open its Workflow Description dialog
(see example).
If the Communication Model exercise was completed, the necessary event and
deliverable that should be selected for this workflow has previously been created.
However, if the Communication Model exercise was not performed, the event and
deliverable needs to be added.
If you completed the Communication Model exercise, do the following three (3) steps.
next to the Deliverable name and select the
Click the Drop-down button
deliverable, Conference Request.
Click the Drop-down button
next to the Event name and select the event,
Conference Request Received.
Click OK to close the open dialog to return to the workflow model and skip the
next three (3) steps.
If the Communication Model exercise was not performed, do the following three (3)
steps.
Spon sor
"Conference Request
Received"/Conference Request
Sal es
Develop
Conference
Order
After Sales receives the Conference Request from the Sponsor, they transform the
rough Conference Request into a Conference Order that can be provided to
Conference Management for further refinements. These refinements by Conference
Management, known as the activity Develop Conference Requirements, involve
defining the Equipment, Session, Lodging, Facility, and Entertainment
Requirements for the conference.
However, Conference Management must seek help in fulfilling the Lodging, Facility,
and Entertainment Requirements by asking for support from Lodging Management,
Facilities Management, and Entertainment Vendors, respectively. If the Process
Model exercise was completed, these activities already exist and are located at the
bottom of the model.
Again, the next steps assume that the Process Model exercise was performed but, if it
was not, simply add and position the child activities rather than simply moving them to
the correct workflow lane.
Drag and drop the Develop Conference Requirements, Provide Lodging
Availability, Provide Facility Availability, and Provide Entertainment
Availability activities into the workflow lanes as shown in the following model.
You will need to stretch the Conference Management workflow lane to provide
additional space, as both a convergent junction and another activity will be added
to that workflow lane later.
Again notice that as an activity is moved to a workflow lane, its Action Pending
indicator disappears from the bottom of the activity. This corresponds to a
change in the workflow models interpretation whereby the workflow lane (actor)
has been assigned responsibility of the activity.
Spon sor
"Conference Request
Received"/Conference Request
Sal es
Develop
Conference
Order
Conference Managem ent
Develop
Conference
Requ irem ents
Next add a (convergent) junction to the Conference Management workflow lane so that
the workflow can be attached correctly.
Select the Junction button
from the Object Creation toolbar. Notice that
the cursor changes when positioned over an open area of the model.
Place the mouse to the lower right in the Conference Management workflow
lane and click to add a junction. The Conference Management workflow lane
should look similar to the example below.
Conference Managem ent
Develop
Conference
Requ irem ents
As stated previously, Conference Management, with help, deals with the equipment,
session, lodging, facility, and entertainment needs for the conference. Depict this by
adding the workflows between the activities in the Conference Management, Lodging
Management, Facilities Management, and Entertainment Vendors workflow lanes.
The workflow model should be similar to the following example upon completion of
these steps. Detailed steps follow the example.
Spon sor
"Conference Request
Received"/Conference Request
Sal es
Develop
Conference
Order
Conference Managem ent
Develop
Conference
Requ irem ents
Sessions Requirements
Provi de Lodging
Avai l abi li ty
Provi de Faci li ty
Avai l abi li ty
Facility Availability
Provi de
Entertai nm ent
Avai l abi li ty
Entertainment
Availability
Lodging Availability
To
Deliverable
Develop Conference
Order
Develop Conference
Requirements
Conference Order
Develop Conference
Requirements
Junction
Equipment
Requirements
Develop Conference
Requirements
Junction
Session Requirements
Develop Conference
Requirements
Provide Lodging
Availability
Lodging Requirements
Develop Conference
Requirements
Provide Facility
Availability
Facility Requirements
Develop Conference
Requirements
Provide Entertainment
Availability
Entertainment
Requirements
Provide Lodging
Availability
Junction
Lodging Availability
Provide Facility
Availability
Junction
Facility Availability
Provide Entertainment
Availability
Junction
Entertainment
Availability
Return the mouse to default mode by clicking in an open area of the model, or by
selecting the Default button
Conference
Schedule
Presentation
Spon sor
"Conference Request
Received"/Conference Request
Sal es
Develop
Conference
Order
Conference Managem ent
Present
Conference
Schedule
Conference Order
Conference Schedule
Develop
Conference
Requ irem ents
Schedule
Conference
Equipment Requirements
Sessions Requirements
Provi de Lodging
Avai l abi li ty
Provi de Faci li ty
Avai l abi li ty
Facility Availability
Provi de
Entertai nm ent
Avai l abi li ty
Entertainm ent
Availability
Lodging Availability
Drag and drop the Schedule Conference and Present Conference Schedule
activities into the workflow lanes as shown in the previous model, assuming the
Process Model exercise was performed. If it was not, simply add and then
position these child activities.
Click the Link (selector)
To
Deliverable
Junction
Schedule Conference
{none}
Schedule Conference
Present Conference
Schedule
Conference Schedule
Present Conference
Schedule
Sink
Conference Schedule
Presentation
Return the mouse to default mode by clicking in an open area of the model, or by
selecting the Default button
See the
The final deliverable supplied to the Sponsor in the workflow model is the Conference
Schedule Presentation. Yet, earlier, for the same Business Process, the final
deliverable supplied to the Sponsor in the communication model is the Conference
Schedule. This discrepancy was the result of understanding the process more fully
during the detailed workflow discussions, which can be rather typical.
Synchronize these 2 models by updating the Communication Model with the correct
output deliverable, as depicted below.
Right-click on the Sponsor swimlanes icon, select Where Used from the context
menu, can then click Communication Modeler: Arrange Conference to launch
this model.
Double click on the communication link between Sponsor and Arrange
Conference to launch the details dialog.
Using the drop down list for the Conference Schedule deliverable, select
Conference Schedule Presentation and click OK to close the dialog. Your
Communication Model is now consistent with the Workflow Model.
"Conference Request
Received"/Conference Request
Conference Schedule Presentation
Arrange
Conference
Sponsor
Another option is to take the position that the Communication Models, which were built
to frame Business Processes in order to set up the Workflow Models, are no longer
needed once the Workflows are complete. These Communication Models can then be
deleted and only the Workflow Models can be maintained. This option is a good
example of an interim deliverable used to facilitate a final deliverable.
This completes the Basic Workflow Model exercise.
2.
3.
4.
5.
6.
7.
237
Activity
Workflow lane (Actor)
Workflow
Source / Sink
Deliverable
Event
Decision Point
Junction
238
Metastorm
Workflow Modeler
in ProVision
(Intermediate)
Activity Alias
Store
Bridge
Bar (BPMN Pool Separator)
Context Object
240
Activity Alias
241
Activity Collaboration
Collaboration
Multiple actors often
collaborate together during
performance of an activity
Multiple choices for
representation
Use aliases and align
vertically
Use aliases with junctions to
synchronize inputs and
outputs
Define collaborators as
resources and display as
activity properties
242
Activity Collaboration
Interpretation
243
Activity Collaboration
Collaboration as Alias
Option 2
Interpretation
Activity Collaboration
Collaboration as Properties
Interpretation
245
Store
Consolidate
Conference
Requirements
Conference
Requirements
Conference
Store
An aggregation of deliverables maintained by, and
provided to, activities in a business process
Can hold deliverables for later use
Can serve the purpose of a queue
Supported in workflow simulations to define pull versus
push situations
246
Bridge
Bridge
Approve Credit
Credit Approval
to Orde r
Da taba se
Credit Approval
fro m
Ap prove
Credit
Order
Database
247
248
Context Objects
Receive Order (In)
Acknowledge Order (Out)
Schedule Order (Out)
249
Context Object
Touch Points
Parent Object
Child Context
Object
Found in a child
workflow model
Depicted with a dashed
outline
Represents the
connection point in the
parents model
Workflow lane position
owned by the parent
Workflow synchronized
between child and
parent
Workflow changes
allowed in the child or
parent
250
Connected to 3
Context Objects
251
252
253
Scenario Recruitment
254
Approach
1. ~~~~~~~
2. ~~~~~~~
3. ~~~~~~~
4. ~~~~~~~
5. ~~~~~~~
4.Determine
4
Determine activity sequence
5.Develop child workflow
models
255
256
2. Identify Actors
257
3. Identify Activities
Actor Approach
Examine each actor
Identify its responsibility(ies)
within the process
Partition responsibilities into
activities
Time bounded
Initiated by significant businessvisible event
Produce business-visible
deliverable
Pass/receive work to/from other
actors
May be further partitioned
(later)
258
3. Identify Activities
Context Approach
Identify activities within actor which:
respond to input
produce outgoing deliverable
perform intermediate
transformations from input to output
259
3. Identify Activities
Decomposition Approach
Traverse business process
start with process event
identify
id tif activities
ti iti
(process steps )
identify customer and
supplier activities or use
source/sink
end with deliverables
Acknowledge
A
k
l d
Orde r
Authorize
Order
Schedule
S
h d l
Order
Check Order
Correctness
1999 - 2007 Metastorm, Inc.
App rove
A
Order
Receive
R
i
Orde r
Correct Order
Che ck
Customer
Cred it
260
Out-going Workflows
Show conditional deliverables /
branching with a decision point
Deliverables
Identify deliverable for signal
events
Deliverable identifies value-add
(purpose) of source activity
Usually do not try to graphically
depict all inputs (data flow) and
resources
1999 - 2007 Metastorm, Inc.
261
262
Additional Components
Store
Bridge End
Bridge Start
263
Responsible Actor
Market
Organization
Role
Person (possible)
System
Development Approach
Activity
Internal
External (or use
Source / Sink)
Workflow
Event
Deliverable
Decision Point Discriminator
Actor approach
Context approach
Decomposition approach
Decision Point
Source / Sink
Junction
1999 - 2007 Metastorm, Inc.
Activity Alias
Store
Bridge
B
Bar
Context Object
Determine workflows
Develop child workflow models
264
265
Notes
_______________________________________________
_______________________________________________
_______________________________________________
_______________________________________________
_______________________________________________
_______________________________________________
266
Metastorm
Notes
_______________________________________________
_______________________________________________
_______________________________________________
_______________________________________________
_______________________________________________
_______________________________________________
268
"Conference Request
Received"/Conference Request
Sal es
Develop
Conference
Order
Conference Managem ent
Conference Order
Develop
Conference
Requ irem ents
The activity begins with the initiating event Conference Request Received and the
receipt of the deliverable Conference Request. The activitys value-added contribution
to the Arrange Conference business process is that it converts the Conference
Request into a Conference Order, which is in a form usable by Conference
Management for defining equipment, session, lodging, facility, and entertainment
requirements.
Beginning with the starting and ending points for the Develop Conference Order
activity, identify the sub-activities, their responsible actors, and decision points that
graphically describe this activity based upon the following detailed description. A work
area is provided below for pen-or-pencil development of these details.
Sales Rep
Credit Analyst
Conference Order
Conference Management
Develop
Conference
Requirements
Notes
A possible solution for the Develop Conference Order workflow model follows. Utilize
this example to build a nested workflow model for this activity in ProVision. Detailed
instructions begin on the next page.
Sponsor
"Conference Request
Received"/Conference Request
Financial Options
Sales Rep
Define
Conference
Objectives
Determine
Financial
Options
Conference Objectives
Determine
Executive Tasks
Credit Analyst
Validate
Sponsor Credit
Generate
Conference
Order
No
Credit Ok?
Yes
Conference Order
Conference Management
Develop
Conference
Requirements
As this exercise first illustrates nesting a workflow model for the Develop Conference
Order activity, you must have completed the prior workflow model exercise as a starting
point for this one.
Ensure the Repository is displayed in
the Index Bar. If the Index Bar is not
displayed, depress the Index button
on the Navigation Tools toolbar
and then click the Repository button.
Click on the Repository Bar, and then click the plus sign in front of the
Professional Retreats repository to reveal the Conference Administration
notebook. Double click the notebook to open it.
Now, click on the Inventory button in the Index Bar, and click on the Model
Inventory tab
Expand the Workflow Modeler folder on the Model Inventory tab by clicking
on its plus sign.
Double-click on the Arrange Conference(Business Process:) model in the
Workflow Modeler folder.
An example of this workflow model, which was created in the prior workflow model
exercise, is included below.
Conference
Schedule
Presentation
Spon sor
"Conference Request
Received"/Conference Request
Sal es
Develop
Conference
Order
Conference Managem ent
Present
Conference
Schedule
Conference Order
Conference Schedule
Develop
Conference
Requ irem ents
Schedule
Conference
Equipment Requirem ents
Sessions Requirements
Provi de Lodging
Avai l abi li ty
Provi de Faci li ty
Avai l abi li ty
Facility Availability
Provi de
Entertai nm ent
Avai l abi li ty
Entertainm ent
Availability
Lodging Availability
Notice that ProVision provides you with context information from the parent
model. Initially this includes the input Source object, in the Sponsor workflow
lane, and the output Develop Conference Requirements activity, in the
Conference Management workflow lane. See the example is below.
You will now add additional workflow lanes (actors) to the model. If you performed the
earlier exercise that defined PRCs organizational structure, you will select two roles for
inclusion in this model. If these roles do not exist, you will add the roles. If you are in
doubt, try selecting them first.
Click on the Workflow Lane
button
in the Object
Creation Toolbar and click
in the model to invoke the
Add or Select Object dialog.
In the Add or Select Object
dialog, select Role as the
Type
and
click
either
or
on the dialog based upon whether the roles already exist or not.
In the Power Select or Power Add list box, select or add the following roles. For
multiple selections, hold down the CTRL key.
Sales Rep
Credit Analyst
After including these actors in the model, drag and drop them, if necessary, to
place them in the following order:
Sponsor
Sales Rep
Credit Analyst
Conference Management
Stretch the Sales Rep workflow lane to provide additional room for its four (4)
sub-activities (see example below).
button to add
Position the activities as in the example below. The example also contains the
decision point and sink that will be added next.
Sponsor
Sales Rep
Define
Conference
Objectives
Determine
Financial
Options
Generate
Conference
Order
Determine
Executive Tasks
Credit Analyst
Validate
Sponsor Credit
Credit Ok?
Conference Management
Develop
Conference
Requirements
Click OK to close the decision point dialog and save your changes.
Add a sink to the model.
on the Object Creation toolbar. Notice that
Click the Source/Sink button
the cursor changes when positioned over an open area of the model.
Place the mouse to the right of the Source in the Sponsor workflow lane, click to
invoke the Add Object dialog, and add a Sink.
You are now ready to add the workflows to the model. An example of the final layout for
the nested Develop Conference Order workflow is provided below.
Sponsor
"Conference Request
Received"/Conference Request
Financial Options
Sales Rep
Define
Conference
Objectives
Determine
Financial
Options
Conference Objectives
Determine
Executive Tasks
Credit Analyst
Validate
Sponsor Credit
Generate
Conference
Order
No
Credit Ok?
Yes
Conference Order
Conference Management
Develop
Conference
Requirements
Connect the context objects, the activities, the decision point, and the sink with
button on the Object Creation
workflows by first clicking on the Workflow
toolbar and then dragging from the start object to the end object as listed in the
table below (or, if you prefer, simply use the model example above).
Note: ProVision will automatically add decision point discriminators to output
workflows as they are drawn using the same order the discriminators are listed
for the Decision Point. It
is therefore easiest to add
the workflows in that
order. If you forget to do
this, you can change the
discriminator assignment
on a workflow by doubleclicking on the workflow
(the link) to launch the
Workflow
Description
dialog and selecting the correct discriminator from the drop down list under the
decision point graphic.
Workflows
From
Source:
Sponsor
To
Activity:
Define Conference
Objectives
Event/
Deliverable/
Discriminator
Event:
Conference Request
Received
Deliverable:
Conference Request
Activity:
Define Conference
Objectives
Activity:
Determine Executive
Tasks
Deliverable:
Conference Objectives
Activity:
Determine Executive
Tasks
Activity:
Validate Sponsor Credit
Deliverable:
Executive Conference
Tasks
Decision Point:
Credit OK?
Activity:
Generate Conference
Order
Discriminator: Yes
Decision Point:
Credit OK?
Activity:
Determine Financial
Options
Discriminator: No
Activity:
Determine Financial
Options
Sink:
Sponsor
Deliverable:
Financial Options
Activity:
Generate Conference
Order
Activity:
Develop Conference
Requirements
Deliverable:
Conference Order
Deliverable:
Sponsor Credit Status
Deliverable:
Sponsor Credit Status
Review the interpretation and notice that the model graphics and the
interpretation are synchronized. The items listed in the interpretation are live,
meaning you can double-click on them and invoke their detail dialogs, just as you
can in the model itself.
Close the interpretation and maximize the workflow model.
Click the Fit to View
Close this workflow model using the lower of the two Close
upper right of the ProVision window.
buttons in the
You should be back to the Arrange Conference workflow model. If not, just click
on its tab to activate it.
While the workflow model was being built, a hierarchy of activities was also constructed.
You will now see this hierarchy using the Process Modeler.
Double-click the Process Modeler folder on the Model Inventory tab
in the
Inventory View to launch the Select Subject for Process Modeler dialog (or
use the Modeler menu). See the dialog example below.
In this Select Subject for Process Modeler dialog, select Business Process
and select the existing business process Arrange Conference.
Click
Conference.
Arranged.
Arrange
Conference
Develop
Conference
Requirements
Develop
Conference
Order
Present
Conference
Schedule
Provide
Entertainment
Availability
Provide
Facility
Availability
Provide
Lodging
Availability
Schedule
Conference
Define
Conference
Objectives
Determine
Executive
Tasks
Determine
Financial
Options
Generate
Conference
Order
Validate
Sponsor
Credit
Right-click in an open area of the model and select Expand All from the context
menu.
Right-click in an empty area of the model to display the models context menu,
button on the
and select View | Auto Layout, or click the Auto Layout
Orientation toolbar. Choose Fork Top Down and Sort by Name and Number to
automatically arrange the model as above. Note, Reposition Objects must be
checked to enable the layout options, such as Fork Top Down.
This completes the standard portion of the Workflow Model exercise. The
supplemental exercises provided below can be performed after class or as time
permits during class.
Spon sor
"Conference Request
Received"/Conference Request
Sal es
Sponsor
"Conference Request
Received"/Conference
Request
Present
Conference
Schedule
Financial Options
Sales Rep
Define
Conference
Objectives
Determine
Financial Options
Conference Objectives
Determine
Executive Tasks
Credit Analyst
Generate
Conference
Order
No
Validate Sponsor
Credit
Credit Ok?
Conference Order
Yes
Conference Management
Develop
Conference
Requirements
Conference Schedule
Conference Order
Develop
Conference
Requ irem ents
Schedule
Conference
Equipment Requirem ents
Sessions Requirements
Provi de Lodging
Avai l abi li ty
Provi de Faci li ty
Avai l abi li ty
Facility Availability
Provi de
Entertai nm ent
Avai l abi li ty
Entertainm ent
Availability
Lodging Availability
option to
In the Select Model or Model Scenario list, click the plus sign in front of
Workflow Modeler to display all available workflow model thumbnails.
Select
the
Develop
Conference
Order(Activity)
thumbnail
and
click
Accept the defaults (i.e. Renumber in order clicked, Numeric Style, and Auto
Increment), but set the Next number to 1.
Click on each of the activities in the Arrange Conference workflow model in
sequence to number them. Start with the Develop Conference Order activity,
which is represented with its thumbnail view if you completed the previous
thumbnail exercise. Present Conference Schedule should be the seventh (7th)
activity.
Navigate to the nested workflow model for Develop Conference Order by
clicking on its Models describe this object
the thumbnail) and selecting
1.1
Define
Conference
Objectives
The numbers added can be used to control the order of the interpretation. As two
workflow models are affected, both models need to be set to utilize the number for
ordering.
Using the Tools menu, select Interpretation Options to invoke the Workflow
Modeler Interpretation Settings dialog for the active model (do this twice, once
for each workflow model).
In the Ordering group box on the Detail
Level tab, select by Number,Name.
Interpret
each model to verify that
the activities are listed in their numerical order.
The numbers added to the activities are also visible in the Process Model view for
those activities.
Activate the Arrange Conference process model. If this model is already open,
simply click on its tab. Otherwise, launch this model.
The model should appear similar to the example below if the Hierarchy Top
Down layout option is selected using Auto Layout.
Again, note that
layout options, such as Hierarchy Top Down.
If the activities are not visually displayed in numeric order as below, drag-anddrop them roughly into the desired order and repeat Auto Layout.
Arrange
Conference
1.1
Define
Conference
Objectives
1.2
Determine
Executive
Tasks
1
Develop
Conference
Order
2
Develop
Conference
Requirements
3
Provide
Lodging
Availability
1.3
Validate
Sponsor
Credit
1.4
Determine
Financial
Options
1.5
Generate
Conference
Order
4
Provide
Facility
Availability
5
Provide
Entertainment
Availability
6
Schedule
Conference
7
Present
Conference
Schedule
Spon sor
"Conference Request
Received"/Conference Request
Be gi n
Sal es
Develop
Conference
Order
Conference Managem ent
Present
Conference
Schedule
Conference Order
Conference Schedule
Develop
Conference
Requ irem ents
Schedule
Conference
Equipment Requirements
Sessions Requirements
Provi de Lodging
Avai l abi li ty
Lodging Availability
Provi de Faci li ty
Avai l abi li ty
Facility Availability
Provi de
Entertai nm ent
Avai l abi li ty
Entertainm ent
Availability
Notes
Modification 1: The SMEs noted that a step seems to be missing. Before the
conference can be scheduled, the availability of all requirements must be confirmed by
Conference Management, since availability is coming from multiple sources. After this
step, there are 3 possible dispositions: (1) the requirements can be met and scheduling
can proceed, (2) the requirements are not all available and another attempt should be
made to develop conference requirements by meeting the objectives defined in the
conference order utilizing a different set of requirements, or (3) the requirements can not
be met and no further effort should be expended (i.e. scheduling of the conference is
not attempted).
Sketch out these refinements in the model below:
Conference
Schedule
Presentation
Sponsor
"Conference Request
Received"/Conference Request
Sal es
Develop
Conference
Order
Conference Schedule
Present
Conference
Schedul e
Conference Order
Schedul e
Conference
Develop
Conference
Requirements
Equipment Requirements
Sessions Requirements
Lodging Management
Lodging Requirements
Provi de Lodgi ng
Avail abi lity
Facility Requirements
Facility Availability
Provi de
Entertainment
Avail abi lity
Entertainm ent
Availability
Lodging Availability
Entertainment Vendor
Entertainment Requirements
Sponsor
"Conference Request
Received"/Conference Request
Sal es
Develop
Conference
Order
Conference Schedule
Present
Conference
Schedul e
Conference Order
Develop
Conference
Requirements
Schedul e
Conference
Yes
No - Try Again
Requirements Met?
No - Give Up
Confi rm
Requirement
Avail abi lity
Sessions Requirements
Lodging Management
Lodging Requirements
Provi de Lodgi ng
Avail abi lity
Facility Requirements
Facility Availability
Provi de
Entertainment
Avail abi lity
Entertainm ent
Availability
Lodging Availability
Entertainment Vendor
Entertainm ent Requirements
Modification 2: The SMEs noted that the last step in the model, Present Conference
Schedule, is more of a collaboration between Sales and the Sponsor wherein the
conference requirements and schedule are reviewed together. After this review, two
major dispositions can occur: (1) the conference schedule is accepted by the Sponsor,
or (2) modifications are made to the conference request and the process steps are
repeated.
Sketch out these refinements in the model below:
Sponsor
"Conference Request
Rec eived"/Conference Request
Sales
Develop
Conference Order
Conference Order
Conference Management
Conference Schedule
Schedule
Conference
Develop
Conference
Requirements
Equipment Requirements
Ses sions Requirements
Lodging Management
Lodging Requirements
Provide Lodging
Availability
Facility Requirements
Provide Facility
Availability
Facilities Management
Entertainment Vendor
Entertainment Requirements
Provide
Entertainment
Availability
Lodging
Availability
Facility
Availability
Entertainment
Availability
"Conference Request
Rec eived"/Conference Request
Sales
Develop
Conference Order
Ok?
Yes
Review
Conference
Requirements &
Schedule
Conference Order
Conference Management
Conference Schedule
Schedule
Conference
Develop
Conference
Requirements
Equipment Requirements
Ses sions Requirements
Lodging Management
Lodging Requirements
Provide Lodging
Availability
Facility Requirements
Provide Facility
Availability
Facilities Management
Entertainment Vendor
Entertainment Requirements
Provide
Entertainment
Availability
Lodging
Availability
Facility
Availability
Entertainment
Availability
To complete this supplemental exercise, modify the existing Workflow Model for the
Business Process: Arrange Conference using the combined changes illustrated
below. Update notes are provided.
The examples below do not assume the completion of the two previous
Supplemental Exercises. Therefore, the examples do not include the thumbnail
that may have been inserted in Supplemental Exercise 1 and do not include
numbering which may have been added in Supplemental Exercise 2.
Sponsor
Review
Conference
Requirements &
Schedule
"Conference Request
Received"/Conference Request
"Requirements Unmet"
No - Try Again
Accepted Schedule
Requirements Met?
No - Give Up
Yes
Develop
Conference
Requirements
Met"
Schedule
Conference
Conference Order
Yes
"Requirements Unmet"
Conference Management
Ok?
Review
Conference
Requirements &
Schedule
Conference Schedule
Develop
Conference
Order
"Requirements
Sales
Confirm
Requirement
Availability
Equipment Requirements
Sessions Requirements
Lodging Management
Lodging Requirements Provide Lodging
Availability
Facilities Management
Facility Requirements
Provide Facility
Availability
Entertainment Vendor
Entertainment Requirements
Provide
Entertainment
Availability
Lodging
Availability
Facility
Availability
Entertainment
Availability
workflow
model
in
the
Conference
Because of the addition of the workflow input into the Develop Conference
Order activity, its child workflow must also be updated. That is, the OK? decision
point context object should be connected to the Define Conference Objectives
child activity in the nested model (see below).
Spons or
"Conference Request
Received"/Conference Request
Sales
Ok?
"Conference Request
Changed"/Conference
No Request Change
Sales Rep
Financial Options
1
Define
Conferenc e
Objectives
4
Determine
Financial
Options
Conference Objectives
2
Determine
Executive Tasks
Credit Analyst
3
Validate Sponsor
Credit
5
Generate
Conferenc e
Order
No
Credit Ok?
Yes
Conference Order
Conferenc e Management
Develop
Conferenc e
Requirements
269
Activity Alias
Store
Bridge
Bar (BPMN Pool Separator)
Context Object
270
Dimensions
Metastorm
in ProVision
Section Objectives
272
Dimension Types
United States
EMEA
Asia Pacific
Time / Phase
Location / Region / Country
Version / Release
Market / Channel / Brand
Behind-the-scene objects
j
only
y
found in Navigator
Defined in Object Inventory
Com plete Order
[v1,US]
v1, US
v2, US
v1, EMEA
273
Why Dimensions?
Before Dimensions in ProVision
Termination
Policy
[FY07]
Termination
Policy
[FY09]
274
275
Detail Dimensions
Dimension Details
Launch dialog from
Object Inventory or
click Modify from
Dimension Type dialog
Add abbreviation
and description
Abbreviations display
instead of Name
(controlled by
Preferences)
f
)
276
Configure Dimensions
Com plete Order
[EMEA,US,P2]
Configure Dimensions
to create a Projection
Launch dialog from
Object Inventory or
objects context menu
Only affects selected
object
Multiple dimensions
for same dimension
type allowed
Base object name,
combined with
Dimensions, is unique
in notebook
1999 - 2007 Metastorm, Inc.
277
Create Projection
When creating projections
Launch dialog from Object
Inventory or objects context
menu
Creates new projection with
same properties & doesnt
alter other projection
Multiple dimensions for same
dimension type allowed
Can not have 2 projections
with same dimensions
Projections are automatically
added to appropriate
Parent/Child modelers
278
Substitute Projection
Substitute Projection
Launch dialog in model from objects context menu
Inserts replacement projection directly in place of selected object
Adopts
p ((creates)) any
y links
previously connected to
replaced object (no other
changes made)
If replacement in a Parent/Child
model, replaced object loses
parentage
g
Remember that activityy usages
in workflow models are
synchronized with process
models (which are parent/child
models)
279
Preferences Dimensions
Name format
Delimiter / Grouping
symbols
Where-used
280
281
Metastorm
Click on the Inventory Bar in the Index Bar and click on the Object
at the bottom to display the 3 folders for Links,
Inventory tab
Objects & Supplemental Objects.
Click the plus sign beside the Objects folder to reveal the existing object
types in alphabetical order.
Double-click the Dimension Types folder to launch the Power Add
dialog for Dimension Types.
Using the Power Add dialog, add
a Dimension Type of Region.
Asia Pacific
Europe, Middle East & Africa
United States of America
The currently defined Fill Order business process depicts the process applicable in the
US. There is a need to have the Fill Order business process mapped for both EMEA
and AP.
5. Assign the US Dimension to the current Fill Order business process.
needed, follow the detailed steps below.
If
6. Create another Projection for the Fill Order business process for the EMEA
Dimension. If needed, follow the detailed steps below.
Click OK to close the dialog, return to the Object Inventory and notice
that there are now 2 Fill Orders, one for EMEA and one for US.
7. Examine the workflow model for Fill Order (US) and then create an identical
workflow model for Fill Order (EMEA). If needed, follow the detailed steps
below.
at the
On the Inventory Bar, click on the Model Inventory tab
bottom to display the modeller folders listed alphabetically.
Click the plus sign beside the Workflow Modeler folder to reveal the
existing workflow models.
Double-click the workflow model whose subject is Fill Order (US)
(Business Process:) to open this model. This is the model that will be
used as the starting point for the Fill Order (EMEA) model.
Double-click the Workflow Modeler folder to launch the Select Subject
for Workflow Modeler dialog.
At the top, for What type of object is the model describing?, click
on Business Process.
Under Select an existing Business Process, double-click Fill Order
(EMEA) to launch this (for now empty) model. Notice the title of the
model is: Workflow Modeler (Business Process: Fill Order (EMEA). Also
notice that the Workflow Modeler folder in the Model inventory now lists
the new model.
Under the Workflow Modeler folder in the model Inventory, drag the Fill
Order (US) workflow model and drop it in an open area of the empty Fill
Order (EMEA) workflow model. This will launch the Add Objects dialog.
In the Add Objects dialog, click OK to include all the objects in the US
version.
Click the Fit to View
Initially, of course, the workflow models look the same since one was copied from
the other. However, only some of the objects are actually shared between versions
of the models because of the way the workflow objects are defined.
For example, the Activities in both models are actually different Activity Usage
objects. This means the base information is shared, such as the information is
shared, such as the information on the Definition, Properties, Logic Editor, Function,
Associations and Notes tabs. But the other information, such as that on the Timing,
Resources, Cost Elements, and Recipe tabs, are not shared. This last group of
information varies by instance Activity Usage irrespective of Dimensions.
The workflow links, like all link, are defined with a start and end object. Since
workflow links connect different objects, they, too, are different in the two models.
That is, changes to a workflow link in one model will not change the seemingly
corresponding workflow link in the other model because the workflow link is not
actually shared between the two models. Note that this is in contrast to other links,
like the communication link, that can appear in multiple communication models (or
Navigators) because the same start and end objects can appear in multiple models.
An Activity Usage appears in a single Workflow Model because the parent is different
in each workflow model.
Some objects are shared across the two models. For example, the workflow lane
objects (e.g. Markets and Organizations) are shared. Changes to one of these
objects will directly impact the other model.
For completeness, Stores can be shared among workflow models but Sources, Sinks,
Decision Points, Junctions and Bars are not shared.
8. To illustrate the use of Dimensions, make the following changes to the Fill
Order (EMEA) workflow model.
a) Assume EMEA doesnt expedite orders so eliminate the Expedite Order?
Decision point.
b) In EMEA, assume Schedule Order is manually performed by the
Scheduling organization.
c) In EMEA, assume both the Approve Credit and Schedule Order
activities are substantially different so they need a different set of base
properties (i.e. they need an EMEA projection). Correspondingly, the
Approve Credit and Schedule Order activities for the US should be
changed to be US projections.
Reconnect the workflow that begins with the Expedited Order? Decision
point to the Complete Order activity usage.
Delete the Expedited Order? Decision point. This will also delete the
workflow between Complete Order and the decision point.
Select Organization for the Type and enter Scheduling in the Objects text
field to add this organization. If this organization already existed, it could be
selected. If necessary, position this workflow lane next to the Order Entry
System workflow lane using drag and drop.
Drag and drop the Schedule Order activity usage from the Order Entry
System to the Scheduling workflow lane.
Check the box in front of United States of America to assign that Region
to the Projection. Click OK to close the dialog.
Check the box in front of Europe, Middle East and Africa to assign that
Region to the Projection. Click OK to close the dialog. There are now two
projections for Approve Credit, one for the US and the other for EMEA.
Repeat these steps for the Schedule Order activity usage so that there are
two projections for Schedule Order, one for the US and the other for EMEA.
In the Fill Order (EMEA) workflow model, right-click on the Approve Credit
(US) activity usage and select Dimensions | Substitute Projection to
launch the Projection Selector dialog.
Repeat these steps to substitute the EMEA projection for Schedule Order
(US).
The Build Product activity has a nested workflow model and it is found in Fill Order
in both the US and EMEA versions. The context objects are literally different
instance objects, so the connection points in the EMEA context have never been
specified. Remember that workflow links are defined by their start and end objects.
9.
Connect the context objects appropriately in the workflow model for Build
Product launched from the Fill Order (EMEA) workflow model after using
the US context to understand the sequences. If needed, follow the detailed
steps below.
Launch the Build Product workflow model from the Fill Order (US)
workflow model.
Launch the Build Product workflow model from the Fill Order (EMEA)
workflow model.
Close the three workflow models, Build Product, Fill Order (EMEA), and
Fill Order (US).
If more substantial changes are needed for Build Product, creating Projections for
US and EMEA can be done first just like Approve Credit and Schedule Order.
However, allowing Build Product to exist in several contexts is supported in
ProVision without needing Dimensions as long as its insides (e.g. children and
their internal linkage) remain identical.
Note: when Projections are utilized in models, it is sometimes necessary to enlarge
the projection so that its full name is visible. The Auto Resize button
end of the Model Tools toolbar is ideal for this task.
at the
Dimensions Quiz
Please answer the following questions:
1.
2.
Why can two different perspectives of an object not have the same
assigned dimensions?
3.
4.
5.
p y of dimensions for a p
projection?
j
How do yyou control the display
6.
283
Section Objectives
284
Metastorm
Process Redesign
Principles
286
Simpler is Better
Avoid Over-engineering
Work
W kh
hard
d tto simplify
i lif
Simple Processes
Less Costly
More Flexible
287
Advantages
Fewer Communication Delays
Lower Management Overhead
Better Customer Response
288
289
Different markets
Different situations
Resource variations
Special customer requests
290
Work off
off-loaded
loaded from / to customers and suppliers
Specialized capabilities
More cost-efficient
291
Reduce Audits
Reviews and Inspections
Design quality into the process
Identify
Id if problems
bl
when
h they
h
occur
Downstream inspection
breaks down team spirit
does little to improve quality
adds higher rework costs
292
Division of tasks
Specialization of labor
Unskilled work force
No need for communication
Task Inter-relationships
n(n-1)/2
293
Eliminates/minimizes hand-offs
Reduces delays, errors and rework
294
Information
Require only the data which cannot be captured elsewhere
295
296
Automate Appropriately
Avoid Costly Automating for
Automations Sake
Weigh
g automation benefits against
g
costs
Technology acquisition
System development and maintenance
Work force training
Obsolescence
297
Notes
_______________________________________________
_______________________________________________
_______________________________________________
_______________________________________________
_______________________________________________
_______________________________________________
298
Metastorm
Process Improvement
Process Improvement
Opportunity Driven
Incremental
Parent/child representation of
opportunities for the business
domain
Opportunity Model
p
Keyy driver for process
improvement
Organizes opportunities by
category/sub-category
Multiple parentage allowed
Visually depicts all levels of
parents/children but no other
p
associations
Model interpretation includes
other associations (e.g.
processes, actors, deliverables)
301
Opportunity
A chance for improvement in a business process that allows goals to
be attained (fully or partially)
Opportunity Analysis
Goal
G l Att
Attainment
i
t
Goals met (supported) by the opportunity
Priority of these goals
Cost (Impact)
Implementation (one time) costs
On-going costs
Benefit (Impact)
Immediate (one time) benefits
On-going benefits
Risk (Impact)
Cost
Probability
1999 - 2007 Metastorm, Inc.
302
Problem
A factor which negatively affects the businesss ability to
attain its goals
goals
Result from
Poorly designed (not designed) process
Invalid assumptions
Environmental influences
Serve as a source for process improvement or reengineering
opportunities
303
Problem Model
Parent/child representation of
business problems
Problem resolution improves
processes
p
Organizes problems by
category/sub-category/root
cause
Multiple parentage allowed
Visually depicts all levels of
parents/children but no other
p
associations
Model interpretation includes
other associations (e.g.
processes, actors, deliverables)
304
Practice Workshop
Metastorm
Practice Workshop
Notes
_______________________________________________
_______________________________________________
_______________________________________________
_______________________________________________
_______________________________________________
_______________________________________________
306
Practice Workshop
This workshop will allow each participant to reinforce the modeling concepts presented
in the class, gain additional expertise in selected model types, and aid in the definition of
his/her Next Steps Plan.
Generally, there are three ways to be organized for this Practice Workshop: (1) as an
individual, (2) as a member of a small team, or (3) with the entire class working
together. The instructor will cover the trade-offs with these approaches and the best
one will be selected. The instructor will also establish the amount of time to allocate to
this Practice Workshop.
The following model types have been presented and each participant should
theoretically be comfortable creating any one of them for their area of expertise:
Organization
Business Interaction
Communication
Process
Workflow
Opportunity
Problem
There probably isnt enough time to create examples of all those model types during the
Practice Workshop, so the participant should work with the instructor to determine how
best to spend the allocated time. This includes identifying the models that will be
(partially) developed and the sequence of development.
By all means, real-life scenarios should be addressed so that the participant jump
starts work similar to what he/she will address on their job.
In this Practice Workshop, ProVision is typically used live to capture the models as they
are developed. However, if it is more convenient, a white board or something similar
can be utilized instead. The emphasis of this Practice Workshop should be on the
concepts of business modeling, not necessarily the details of ProVisions support for
those models.
Finally, if time permits, participants will present their work to the rest of the class at the
end of the workshop.
Metastorm
Model Checking,
Publishing & Reporting
in ProVision
308
Completeness
Checker
in ProVision
309
310
Completeness View
311
Completeness View
Double-click to launch
details dialog &
make corrections
312
Spell Checker
Several ways to Launch
Spell Checker
in ProVision
313
Spelling Correction
Functions
314
Interpretation
Several ways to Launch
Displays Left & Right or
Interpreter
in ProVision
315
Interpretation
Displays Top & Bottom
316
Interpretation
Objects follow
317
Interpretation Options
in ProVision
318
5 Text Types:
Name
Label
Description
Detail
Minor Detail
319
320
Page
g
Margins
Header/Footer
Positions
Page Numbering
Orientation
321
Printing Options
Page Setup Specify page
appearance options
Print Setup Choose printer
options
Print Preview View page(s) before
printing
Printing Options
in ProVision
322
323
324
325
326
Publisher
Creates publication of modeling results
Publication can include:
Models
M
d l
Interpretations
Grids
Charts
Artifacts
Publisher
in
ProVision
Destinations
for publication
Default printer
HTML (compile option)
MS Word
327
Create Folder
Define Content
Publish
p
with
Invoke options
Right-Click Context
Menu
328
329
330
Publish Dialog
Same dialog for both
Project Inventory Folder
Publish and File Menu
Publish
Target:
Default Printer
HTML (compile option)
MS Word
331
Publish Settings
332
Overrides to:
Header/Footer
333
Overrides to:
Header/Footer
Page
334
Overrides to:
Header/Footer
Page
Margins
335
336
Style Sheets
337
338
Additional Controls
Document Path
Template Path
Use Template Header
Use Template Footer
Use Object Templates
Include Objects
j
in TOC
Publish Subfolder Intros
Generate Glossary
For Glossary, select
Object Types to include
1999 - 2007 Metastorm, Inc.
339
340
Crystal Reports
BusinessObjects
Crystal Reports
Easy-to-use reporting
& analysis tool
Built-in execution
Crystal Reports
separately licensed to
build additional
custom reports
ProPacks available
Specialized Topics
Six Sigma
Portfolio Mgmt
341
Crystal Reports
Select Report
then
342
Crystal Reports
Controls for Export, Print, First, Previous, Next, Last, Find Text, Zoom
1999 - 2007 Metastorm, Inc.
343
Metastorm
Notes
_______________________________________________
_______________________________________________
_______________________________________________
_______________________________________________
_______________________________________________
_______________________________________________
345
Notes
_______________________________________________
_______________________________________________
_______________________________________________
_______________________________________________
_______________________________________________
_______________________________________________
346
or the Tools |
Click
to execute the Completeness Checker for the Quality Widgets
Organization Model.
Click the Properties tab and then enter a Premium Usage Cost of $75/hour
and a Usage Cost of $50/hour for Assembly Operations, as below.
To facilitate exercising the Spell Checker (coming up next), click the Definition
tab and include a couple of misspelled words in the Description of Assembly
Operations, by adding:
If your model does not fit on a single page, press the Two Page button to see a
side-by-side presentation of how the model will look when printed.
Click
Click
Select File | Page Setup to display the Page Setup dialog. The
Header/Footer tab is displayed first by default, with the Header
being the default option.
Click the Footer radio button at the lower right corner of the dialog. Note that the
page number is displayed by default at the bottom right of the model. Make any
changes you desire.
Click anywhere in the Center Text area.
button to insert the current time in the Center Text area.
Click the
This time will be displayed at the bottom center of a printed model, and will
indicate the time the model is printed (it is synchronized with your computers
clock). Click OK to save your changes.
Select File -- Print Preview to view the model as it will be printed. Click the
button if necessary to verify the addition of the date,
Zoom In
and click
ProVision provides a textual interpretation for each of its models. The model interpreter
takes the modeling constructs and their supporting descriptions/properties and presents
this information in a narrative format, with complete consistency between the two views.
If the paper-work has been completed, the details presented by the interpreter exceed
the information in the model. Preview this capability.
Ensure the Quality Widgets organization model is the active model.
Click the Interpreter button
on the Main toolbar. ProVision opens a new
window, which displays a narrative description of the organization model, and
positions the interpretation to the right of the model.
Click the Interpreter button
again and notice that the interpretation is now
positioned below the model. A third click toggles the interpretation side-by-side
with the model, as before.
Click once on the Assembly Operations organization.
Notice that the
interpretation is repositioned on this organization. When published to HTML, the
same functionality is provided.
Illustrate Status Bar functionality.
Ensure that ProVision is displaying the Status Bar. If not, use the View | Status
Bar menu option to display it.
Slowly drag your mouse over the components in the interpretation. Notice that
the status bar shows the name of each component as the mouse passes over
that object (assuming you set your Preferences to display the object names on
the Status Bar).
menu option.
The Detail Level tab allows you to modify the objects and/or object properties
that will be interpreted as well as control the sequence in which the objects
are interpreted.
The Fonts tab allows you to modify the look of the text.
The Header/Footer tab allows you to modify header and footer information.
The Page tab allows you to modify page properties such as margins, page
numbering and orientation.
Click
Select HTML from the Target drop-down list at the top of the dialog. Check the
Use compiled Html check box on the upper right-hand portion of the dialog.
This compiles your HTML into a single (large) file and provides an additional
Search capability (courtesy of Microsoft).
Enter information of your choice in the Author Information area of the dialog (or
see example above).
to close the Modify Publish List dialog and return to the
Click
Publish Executive Summary dialog.
Click
.
Use 40, 25, and 3, respectively, in the Initial Scale (percent), Zoom Increment
(percent), and Zoom Max Level fields and check the Include Fit to View Image
box. These settings are just suggestions and you are free to choose other
parameters. Once you examine the HTML, you will see the impact of these
settings.
to close the Setup Scaling Options / Style Sheets dialog and
Click
return to the Publish Executive Summary dialog.
Click
Once the generation is complete, ProVision launches the compiled HTML file so
you can view the document (see example below).
Expand the Business Interaction Modeler menu and select Quality Widgets to
display the Business Interaction Model.
Click on the Finance actor to position the interpretation to that object (see above
example).
Browse through the models in the publication and experiment with the built-in
model-to-model navigation (for example, nested workflow models navigate like in
ProVision).
After review, close the compiled HTML file and return to ProVision.
This completes the ProVision Model Checking & Publishing exercise.
347
Notes
_______________________________________________
_______________________________________________
_______________________________________________
_______________________________________________
_______________________________________________
_______________________________________________
348
Metastorm
Working Together
in ProVision
g Objects
j
&
Sharing
Models
350
Repositories
Repository
1
belongs to
contains
*
Notebook
belongs to
contains
belongs to
contains
Object
*
appears in
includes
Model
*
is the subject of
describes
351
Repositories
3 types of Repositories
Single
g User
Teamwork
Knowledge Exchange
352
Notebooks
Repository
1
belongs to
contains
*
Notebook
belongs to
contains
belongs to
contains
Object
appears in
includes
*
1
Model
Different projects
Different
Diff
b
business
i
d
domains
i
Different project phases
j
of
is the subject
describes
353
Notes
_______________________________________________
_______________________________________________
_______________________________________________
_______________________________________________
_______________________________________________
_______________________________________________
354
Metastorm
A Merge Scenario
Independent Users
Models built in ProVision without regard to other work (i.e. no prior
sharing of notebook contents)
Discover need to combine models and objects so sharing can begin
Merge brings models & objects together
Merge invoked with
Drag & drop notebook onto another notebook
Drag & drop models or objects from inventory onto notebook
Import from file
Export can be
used to create
.PVW file with any
subset of models
1999 - 2007 Metastorm, Inc.
356
Merge
Merge can ONLY match on EXACT object names
After Merge, notebook contents can be Shared
Merge
Supports 3 methods
Replace
Combine
Rename
357
Merge - Replace
Imported
Original
Activity: Prioritize
Request
Activity: Prioritize
Request
Activity: Prioritize
Request
Stereotype:
<automated>
Stereotype:
<automated>
Stereotype: (null)
Work Time: 2
minutes
Associated to Goal:
Do Better
Associated to Goal:
Do Better
Associated to Goal:
Do Better
Goal: Do Better
Goal: Do Better
Goal: Do Better
Priority: (null)
Priority: (null)
Priority: Low
Category: Supplier
Category: Supplier
Category: Customer
Perception: Internal
Perception: Internal
Perception: External
358
Merge - Combine
Merge Combine Behaviour with Priority on Imported
Imported
Original
After Merge - Combine
Activity: Prioritize
Request
Activity: Prioritize
Request
Activity: Prioritize
Request
Stereotype:
<automated>
Stereotype:
<automated>
Stereotype: (null)
Type: (null)
Type: (null)
Associated to Goals:
Do Better & Simplify
Associated to Goals:
Do Better, Simplify
& Faster
Associated to Goal:
Faster
Goal: Do Better
Goal: Do Better
Goal: Simplify
Goal: Simplify
Goal: Faster
Goal: Faster
359
Merge - Rename
Original
Activity: Prioritize
Request
Activity: Prioritize
Request
Activity: Prioritize
Request
Associated to Goals:
Do Better &
Simplify
Associated to Goals:
Do Better & Simplify
Associated to
Goals: Simplify &
Faster
Activity: Prioritize
Request*
Goal: Do Better
Associated to Goals:
Simplify* & Faster
Goal: Simplify
Goal: Simplify
Goal: Do Better
Goal: Faster
Goal: Simplify
Goal: Simplify*
Goal: Faster
1999 - 2007 Metastorm, Inc.
360
Metastorm
362
Log On
Shared repositories require users to log on
as security permissions will be applied
Log On to Knowledge
Exchange Repository
Enter user ID & password
ProVision can remember
your user ID & password, if
desired
Can change password
363
Check-Out
Check-out Models and Objects from Notebook
for Update or Read-Only
Individual Repositories
(or TeamWork)
(Local Single-User)
Single User)
364
Specify source
365
366
Step 4
Specify destination
Usually a local notebook
367
2.
When you lock a model during check-out, what happens to the objects
in that model?
3.
4.
5.
368
Team members
Use local copy of notebook
Access
A
notebook
t b k with
ith allll locked
l k d and
d
reference (read-only) models and objects
Make changes, deletions and additions to
agreed upon models and objects
Coordinate all object deletes and renames
with other team members
Check in changes
369
Check-In
After Updates, Check-In Models and Objects to Notebook
Multi-User Repository
(Knowledge Exchange or TeamWork)
Locks are released upon check-in
Individual Repositories
(Local Single-User)
370
371
Approved
Notebook
Copy
Viewed Models
Development Repository
Production Repository
372
Inventory
Model
View only
Interpretation
1999 - 2007 Metastorm, Inc.
373
Knowledge Exchange
374
Manage Backups
Administrator-only Functions
Manage Notebook Backup Versions
Wh
When necessary, recover previous
i
notebook
t b k version
i
Updates subsequent to notebook version will be lost
Subsequent updates may be recovered with Export/Import (Merge)
from backup notebook versions
375
Maintain Gallery
Team
(Shared)
Repository
Synchronize galleries
After changes applied to
the shared repository
Changes can originate from
a team members
repository
Team Gallery
376
Metastorm
The
In Step 1 of the wizard, ensure the radio button for One of the following
connected repositories: is selected (it is the default selection), select the Sample
repository, and click
In Step 2 of the wizard, check the Convert the copy to a multi-user repository
checkbox, and click
In Step 4 of the wizard, enter TeamWork Exercise for the repository name and
This repository will be used as an exercise on Teamwork functionality. in the
description, and click
In Step 5 of the wizard, enter and confirm a Password that you can remember.
The administrators User ID will be Administrator (unless you change it), and
click
After the notebook opens, select the Repository | Administration menu option
from the main menu. The Repository Administration dialog is invoked.
These are all the Administrator steps that are necessary for this exercise. Only if
interested, browse the other tabs in the Repository Administration dialog. Use
Help to answer any questions. When finished, close the dialog by clicking OK.
Its now time to check-out a model and make modifications using the Developer ID.
Double-click on the Guided Tour notebook in the TeamWork Exercise
repository to invoke the TeamWork Exercise Log On dialog.
Enter the Developer User ID and Password, uncheck the Modify the
repository directly or perform administrative functions checkbox, and click
OK.
Browsing the notebook for models and objects to check-out does not require
exclusive rights to the repository. If this logon option is left checked, access to
the notebook will be denied since the Developer rights do not permit direct
updates or administrative functions to be performed.
Once logged on under the Developer User ID, notice that all objects in an open
model have an Access restrictions for this object indicator
. This means
that the objects and models may not be changed directly; rather, they must first
be checked out. Upon check-out, update, and check-in, an automatic version will
be created so that changes can be rolled back, if necessary.
For this exercise, check-out the Fill Order workflow model and make changes to the
Ship Product activity.
Ensure the Inventory View is displayed in the Index Bar. If the Index View is not
on the Main toolbar and then click the
displayed, depress the Index button
Inventory button Press the Model Inventory tab
in the Inventory View to
see an alphabetical listing of the modelers within ProVision.
Click the plus sign beside the Workflow Modeler folder to reveal the existing
workflow models.
Right-click the Fill Order (Business Process:) workflow model and select
Check out from the context menu to invoke the Check-out Wizard dialog.
In Step 1, scroll down the list of models and notice that the Workflow Model, Fill
Order is selected and is set for Lock. Locked is the default, unless it is currently
locked by another user.
Another way to invoke this dialog is by right clicking on a notebook and selecting
Checkout or through the Interface | ProVision Objects | Check out menu
option.
Still in Step 1, click the Objects tab, scroll down the list of object types, click the
plus sign in front of Goals and then check the box in front of Goals. Notice that
all goals are selected for Lock. This will include all goals in the check-out as well
as the Fill Order workflow model.
Notice the 2 options at the bottom of the dialog. They specify that:
Any nested workflow (or statechart) models will be included in the checkout
Actors that are the swimlanes (workflow lanes) will be checked out as readonly
Proceed to Step 2 of the Check-out Wizard where you can review the models
and objects that have been selected for check-out.
Click on the Objects tab and then expand the list for Goals, Markets,
Organizations, and Roles. Notice that the Goals will be locked but that the
swimlane actors will be read-only.
Proceed to Step 3 of the Check-out Wizard and add the comment, Fill Order
will be modified for the TeamWork exercise.
Proceed to Step 4 of the Check-out Wizard and then click the radio button in
front of the To a connected ProVision repository option.
Select Sample as the target repository and enter Fill Order Update as the
name of the notebook.
Click
Re-launch the Fill Order workflow model and click on the lock indicator
on
the Submit Order activity to display its check-out information. After reading this
information, close the dialog.
Look at the Model Inventory and expand the list under Workflow Modeler.
Notice that there are 3 workflow models, Fill Order and its children.
Launch the Fill Order workflow model and notice that the objects in the model
contain a red check
repository.
Right-click on the activity, 7 Ship Product, and select Workflow Modeler from
its context menu to open its workflow model.
Build the model below for 7 Ship Product by adding the junction, the 2 new
activities, the 2 new swimlanes (include Field Operations but create Carrier),
and the workflows with their deliverables.
In addition to building the Ship Product workflow model, also associate some goals
checked out with the new activities.
Double-click on the Determine Method of Shipment activity to invoke its detail
dialog, select the Associations tab and then in the All Objects section, click on
the plus sign in front of Goals.
Notice that the Goals you checked out are available for associations.
For the Determine Method of Shipment activity, check the P.2.1.1 Decrease
Material Handling goal to associate it with this activity. It will appear in the
Selected Objects list under Goals.
Using the same technique, associate the Pick Up & Deliver Shipment activity
with both the L.2 Integrate Systems and P.2.1.3 Reduce In-Transit Time goals.
This completes the changes you will make to your checked out model.
After the changes are complete, it is time to check-in the modifications to the
TeamWork Exercise repository.
In the Repository View, right-click on the Fill Order Update notebook in the
Sample repository and select Check in from its context menu. This will invoke
the Check-in Wizard.
In Step 1 of the Check-in Wizard, accept the default radio button that will check
the objects into the location they were originally checked out from.
In Step 2 of the Check-in Wizard, enter the comment, The Ship Product
workflow has been added. And accept the default radio button that will release
the locks (will not keep the objects checked out).
In Step 3 of the Check-in Wizard, commit the check in.
You will be required to log on to the TeamWork Exercise repository. Enter your
Password (the User ID is supplied by ProVision) and complete the check in.
Notice that Modify the repository directly or perform administrative
functions is checked as a default to prevent other users from accessing the
repository and modifying objects during Check-In. Leave this box checked.
Next, examine the state of the TeamWork Exercise repository after the check in.
Click the plus sign in front of the Guided Tour notebook in the TeamWork
Exercise repository. You will see a Version 1, which is the automatic backup
made by ProVision before check-in.
Double-click the Guided Tour notebook in the TeamWork Exercise repository to
open it.
Log on with your Developer User ID and uncheck the Modify the repository
directly or perform administrative functions check box, since developers do
not have administrative access rights.
Verify that your workflow model changes to the 7 Ship Product activity have
been applied and that the locks on the objects have been released (the lock
indicators
should have been removed).
Also verify the goal assignments to the activities you added. This can be done
easily by using the Table Inventory within the Inventory View. Select the Table
Inventory tab, click the plus sign in front of the Association Grids folder and
also the Activities folder, and then double-click the Goal (Pursuit) option to
launch the Object Association from Activity to Goal grid.
Examine this grid to verify the goal associations you made to the two new
activities. An example of the grid follows. (Interpreting the workflow model will
list the associated goals under each activity interpretation. Interpreting a goal
model will list the associated activities under each goal interpretation).
Notice that the grid is protected, that is, you cannot make changes directly.
This is because you are logged on under the Developer ID and would have to
check out the objects before making modifications.
378
Notes
_______________________________________________
_______________________________________________
_______________________________________________
_______________________________________________
_______________________________________________
_______________________________________________
379
Notes
_______________________________________________
_______________________________________________
_______________________________________________
_______________________________________________
_______________________________________________
_______________________________________________
380
Metastorm
Where
Why
When
What
How
382
ProVision Structure
Repository
Bookcase of notebooks
Visible to operating system
Notebook
Repository
File
contains
*
equivalent
form
Notebook
belongs to
contains
belongs to
contains
*
appears in
includes
*
1
Object
Who, what, when, where, why, or
how concept of business or
systems
Object
Model
Model
*
is the subject of
describes
383
Modeler Support
Specific
modelers
covered
in course
material
384
Organization
Model
Inventory of
business actors
(i.e. who)
involved in/with
the business
domain with
parent/child
relationships
Markets
Organizations
Roles
People
385
386
Process Model
387
Communication Model
Frames Business
Processes in the
context of their
initiating Events,
involved Actors
and produced
Deliverables
388
Workflow Model
389
Opportunity Model
Inventories
Opportunities (i.e.
why)
why ) for the business
domain with
parent/child
relationships
Opportunity
Categories
Opportunities
390
Problem Model
Inventories
Problems (i.e.
why) for the
business domain
with parent/child
relationships
Problem
Categories
Problems
391
Model Interpretation
Textually renders all
models remaining
consistent with
ith all visually
is all
depicted information
Objects
Object Properties
Object Associations
392
Association Grid
393
Who
Organization
YES
Business Interaction
YES
Why
Where
What
Done
When
What
Produced
How
YES
Process
YES
Communication
YES
Workflow
YES
Possible
Opportunity
YES
Problem
YES
YES
YES
YES
YES
YES
YES
YES
394
Establish Strategy
gy
Business Relationships, Opportunities, Problems
395
396
397
398
399
Course Objectives
You have learned to
Business Process Modeling
g
Articulate the concepts used to
model business processes in the
context of their business
environment
Put into practice a set of modeling
techniques for capturing,
communicating and verifying current
(as-is) and redesigned (to-be)
b i
business
processes
Identify the purpose, strengths and
weaknesses of each type of model
Develop a Next Steps Plan for
utilizing appropriate techniques &
ProVision features on your job
1999 - 2007 Metastorm, Inc.
using
g ProVision
Create, maintain, and
publish business process &
supporting models
Organization Model
Business Interaction Model
Communication Model
Process Model
Workflow Model
Opportunity Model
Problem Model
400
Metastorm
Additional Support
402
Goal Model
Platform Model
Systems Interaction Model
Data Model
Translator
Navigator
Enterprise Framework
403
A-1, 2
OV-1, 2, 3, 4, 5, 6a, 6b, 6c, 7
SV-1, 2, 3, 4, 5, 6, 7, 8, 9, 10a, 10b, 10c, 11
TV-1, 2
5
Days
1999 - 2007 Metastorm, Inc.
404
Modeling Language
Custom Objects & Links
Frameworks
Layers
Service Oriented Architecture Support
Navigator
Navigator Model
Navigation Report
Navigation Grid
Publication
Interpretation Templates
Translator
1
Day
1999 - 2007 Metastorm, Inc.
405
Statechart Model
Data to Process Mapping (CRUD)
Transition to System Design
2
Days
1999 - 2007 Metastorm, Inc.
406
1
Day
1999 - 2007 Metastorm, Inc.
407
408
409
410
411
412
Enterprise
E
t
i A
Architecture
hit t
Business Architecture
Business Transformation
System Requirements Analysis
Metastorm Advantages
Accelerated project structures documented in ProGuide
Metastorms
Metastorm
s Best Practices for Business & System Modeling
Repeatable proven approach
Model-based deliverables
Team consensus via facilitated workshops
Guaranteed results, delivered quickly in ProVision
1999 - 2007 Metastorm, Inc.
413
Project Plan
Teach, Do, Teach you to do
Identify candidate projects and participants
Onsite education and training
Management
M
tO
Overview
i
Concept and tool training
Business Modeling Projects
Completed high-quality business models
Mentoring of project team
414
ProPath Advantages
Enable a quick start to modeling and analyzing your business processes
Use industry Best Practices to improve your current processes
Provide for continuous improvement using industry standard metrics
1999 - 2007 Metastorm, Inc.
415
416
417