Expressiveness and Understandability Considerations of Hierarchy in Declarative Business Process Models

Stefan Zugal, Pnina Soffer, Jakob Pinggera, Barbara Weber

Research output: Chapter in Book/Report/Conference proceedingBook chapterResearchpeer-review

Abstract

Hierarchy has widely been recognized as a viable approach to deal with the complexity of conceptual models. For instance, in declarative business process models, hierarchy is realized by sub-processes. While technical implementations of declarative sub-processes exist, their application, semantics, and the resulting impact on understandability are less understood yet-this research gap is addressed in this work. In particular, we discuss the semantics and the application of hierarchy and show how sub-processes enhance the expressiveness of declarative modeling languages. Then, we turn to the impact on the understandability of hierarchy on a declarative process model. To systematically assess this impact, we present a cognitive-psychology based framework that allows to assess the possible impact of hierarchy on the understandability of the process model.
Original languageEnglish
Title of host publicationLecture Notes in Business Information Processing
Number of pages15
Volume113
PublisherSpringer Berlin Heidelberg
Publication date2012
Pages167-181
DOIs
Publication statusPublished - 2012
Externally publishedYes
Event24th International Conference on Advanced Information Systems Engineering - Gdansk, Poland
Duration: 25 Jun 201229 Jun 2012

Conference

Conference24th International Conference on Advanced Information Systems Engineering
CountryPoland
CityGdansk
Period25/06/201229/06/2012
SeriesLecture Notes in Business Information Processing
ISSN1865-1348

Keywords

  • Cognitive Psychology
  • Declarative Business Process Models
  • Hierarchy
  • Understandability

Fingerprint Dive into the research topics of 'Expressiveness and Understandability Considerations of Hierarchy in Declarative Business Process Models'. Together they form a unique fingerprint.

Cite this