Paper detail

Investigating Differences between Graphical and Textual Declarative Process Models

Declarative approaches to business process modeling are regarded as well suited for highly volatile environments, as they enable a high degree of flexibility. However, problems in understanding declarative process models often impede their adoption. Particularly, a study revealed that aspects that are present in both imperative and declarative process modeling languages at a graphical level-while having different semantics-cause considerable troubles. In this work we investigate whether a notation that does not contain graphical lookalikes, i.e., a textual notation, can help to avoid this problem. Even though a textual representation does not suffer from lookalikes, in our empirical study it performed worse in terms of error rate, duration and mental effort, as the textual representation forces the reader to mentally merge the textual information. Likewise, subjects themselves expressed that the graphical representation is easier to understand.

preprint2015arXivOpen access

Signal facts

What is known right now

Open access2 authors1 topic

Next steps

Decide what to do with this paper

Use like or dislike for the fast social read. The more specific scholarly feedback stays available below when needed.

Log in to curate

Reading frame

Keep the important context close to the paper

Keep the important signals around this paper in one place: votes, save state, collection context, reviews and the metadata you need before deciding what to do next.

Institutions

Add specific reaction

Move through the context

Research map

Open full explorer

Move through nearby people, institutions, topics and adjacent work without leaving the paper page.

Building this map preview

BZPEER is loading the nearby papers, people, topics and institutions for this page.

Structured reviews

0 review(s)

ContributeLeave structured feedbackUse the review template when you have a concrete strength, concern or method question.Open review form

No structured reviews yet. High-signal critique starts here.

Work discussion

0 comment(s)

DiscussAdd a high-signal commentKeep quick notes, caveats and replication pointers separate from formal reviews.Open comment form

No discussion yet. The first strong comment sets the tone.