Towards Configurable Process Visualizations with Proviado

Ralph Bobrik Thomas Bauer

University of Ulm, DBIS, D-89069 Ulm DaimlerChrysler, GR/EPD, D-89013 Ulm

ralph.bobri[email protected] thomas.tb.bauer@daimlerchrysler.com

Abstract

alized or adaptable process drawings, which is par-

ticularly important for large processes. In the Pro-

viado project we are developing a comprehensive

framework for this purpose. It allows for flexible proc-

ess visualization along three dimensions: process

views, process notations, and process representation

forms. In this paper we summarize selected concepts

and features of the Proviado demonstrator.

1. Motivation

Business process (BP) implementations are often scat-

particular BP. Each of them needs a different view on

the process with a personalized visualization and an

adapted granularity of information. For example, while

managers usually prefer an abstract overview of the

process, process participants need a more detailed view

on the process parts they are involved in.

In order to elaborate basic requirements for BP

visualization we conducted several case studies in the

automotive domain [1]. This, in turn, has led us to three

dimensions for realizing configurable BP visualiza-

model. Third, different diagram types (e.g., process

graph, swim lane, calendar, Gantt, table) should be

supported.

Current approaches do not provide this degree of

flexibility. While some of them focus on general issues

related to process visualization [5,6,7], others deal with

more specific aspects like process graph layouting [8].

In existing PAIS, process models are usually presented

to the user in exactly the same way as they have been

drawn by the process designer [3]. Recently, BP mod-

The Proviado framework aims at flexible and configur-

able BP visualizations. In particular, it enables BP

visualizations which are adaptable to the needs of dif-

ferent user groups along the aforementioned dimen-

sions [1]. For realizing a particular drawing of a BP

model or BP instance respectively, a visualization

model has to be specified separately from the process.

Among other things, a visualization model allows to

configure which process elements are to be displayed

and which notation shall be used. This configuration

and graph aggregation. The reduction operation can be

used to remove process objects from a process model.

As an example consider Fig. 1 where activities E, F

and G are removed from the given process model and a

new control edge is inserted instead. Fig. 1 also gives

an idea of the aggregation operation. Aggre-

gate(B,C,H,K), for example, aggregates four activities

by replacing them with one abstract node. Depending

on the concrete structure of the sub-graph induced by

the set of activities to be aggregated, different graph

lar, relations to satellite objects (e.g., data elements,

org. roles) have to be preserved (cf. Fig. 1) and attrib-

ute values for the abstract activity node resulting from

the aggregation have to be calculated. Finally, aggrega-

tion operations are provided for all process aspects

including data flow, and actor assignments.

It is important to mention that view building opera-

tions as provided by Proviado maintain a well-

structured process model if desired. However, to intro-

duce additional flexibility for BP visualizations, opera-

concept allows us to define which process elements

shall be displayed, the Template Mechanism (for de-

tails see [2]) enables us to configure the graphical ap-

pearance of the different elements. In this context a

template represents the concrete notation (i.e., the sym-

bols) to be used for visualizing a particular process

element (e.g., activity, data object). Its graphical ap-

pearance (e.g., shape, arrow) is described based on

Scalable Vector Graphics (SVG). By using this XML-

tionship between symbol definition and data fields.

Required data transformations (e.g. date format conver-

sion) can be realized via ECMA-Script expressions.

Altogether, a complete notation for BP visualization

consists of a set of templates. More precisely, each

process element has to be linked to a template. This

link can be established statically (i.e., remain un-

changed) or dynamically based on selected process

data (e.g., the runtime status of the process element).

The latter allows, for instance, to use different symbols

concept personalized BP visualizations become possi-

ble. While non-relevant process elements can be re-

moved or aggregated with other objects, the visualiza-

tion of relevant process elements can be adapted to

specific user or application needs.

For illustration purposes we consider a change request

(CR) process from the automotive domain. The base

process model is depicted in Fig. 2. It comprises activi-

ties and their assignment to five process phases. Fur-

thermore, control and data flow, exceptional paths, role

assignments, and IT system resources are depicted.

Assume that this process shall be visualized for an

actor from the engineering domain. For this purpose

realized by applying the following view operations:

Aggregation:

{1, 2}, {11, 12, 13, 14, 15}

Reduction: {3}, {4, 5}, {10}, {17, 18}, {20}, {21}

DeleteEdge: {22, 23, 24}, {25, 26}

The resulting process view would still contain a

large number of satellite nodes (representing actors,

systems, etc.) which usually shall not be displayed. Our

visualization model allows to omit such nodes and to

assign their data values to other visualization objects,

Other data like a detailed CR description can be ac-

cessed via a tooltip. Finally, activities which are of

particular importance for engineers are highlighted.

Note that the created process drawing as depicted in

Fig. 3 constitutes one possible visualization of our base

thermore, new process views (with same or different

appearance) can be easily realized. For example, for

managers each of the five phases of the CR process (cf.

Fig. 2) could be aggregated to one single activity and

only information about deadlines, delays, resources,

and the final decision be visualized.