Thomas Ziebermayr

Thomas Ziebermayr
Software Competence Center Hagenberg | SCCH · Software Analytics and Evolution

Dr.

About

35
Publications
2,169
Reads
How we measure 'reads'
A 'read' is counted each time someone views a publication summary (such as the title, abstract, and list of authors), clicks on a figure, or views or downloads the full-text. Learn more
160
Citations
Additional affiliations
November 2015 - May 2016
Software Competence Center Hagenberg
Position
  • Head of Department
November 2015 - May 2016
Software Competence Center Hagenberg
Position
  • Head of Department

Publications

Publications (35)
Chapter
Due to different aspects, such as data, functionality, communication, and interaction, modelling information systems is a complex and challenging task. Each aspect in general calls for its own model, which has to be integrated in the overall system model. In this paper, we present the Hagenberg Business Process Modelling (H-BPM) method as a novel a...
Chapter
In this chapter, we give an overview of the different models, which extend the core process description of common business process modelling languages. We describe how the models are related to each other and how they can work together—the core process description language, the actor model, the user interaction (dialogue) model, the data model, and...
Chapter
An important issue concerning system architectures is how to guarantee that the executable behaviour of a particular model is exactly the same as intended by the system architect. Graphical notations seem intuitive enough to be well understood almost at first sight. However, they typically lack the precise mathematical basis that is required to ren...
Chapter
In most BPMLs, modality is implicitly expressed through the structure of the process flow, so all activities are (tacitly) obligatory, and whenever something should be optional, a gateway is used to split the process flow, which offers the possibility to execute the activity or to do nothing. In this chapter, we present a deontic classification of...
Chapter
Several BPMLs that primarily express the flow of activities provide only limited support for actor modelling. For example, BPMN and UML activity diagrams suggest rigid swimlane concepts to model roles and actors. Thus, in this chapter, we present a task-based approach for actor modelling, extended with deontic logic and speech act theory. An extens...
Chapter
In this chapter, we propose a generalised event concept for business process modelling which can increase flexibility for users in matters of communication, but also increases the number of different communication patterns for cross-organisation communication. We propose a combination of event trigger properties and different types of event pools....
Chapter
In this chapter, we summarise our work on the Hagenberg Business Process Modelling (H-BPM) method, a novel and homogeneous integration framework for business process modelling based on a rigorous semantics for BPMN 2.0 process diagrams, which also includes indispensable extensions in the form of horizontal refinements. The proposed extensions addre...
Chapter
In this chapter, we propose a typed approach to business process specification that supports the integration of workflow definition and dialogue programming and is also open to business process modelling. The resulting key artefact is called workflow chart and still models the control flow of business processes but puts more emphasis on user intera...
Conference Paper
Compared to business processes in other business domains, dynamic workflows in disaster management need a rather rigid allocation of work to actors. The work schedule must conform to available resources and their skills. Moreover, to ensure that each actor is able to quickly start working and to complete pieces of work rapidly, work must be distrib...
Book
This book presents a proposal for designing business process management (BPM) systems that comprise much more than just process modelling. Based on a purified Business Process Model and Notation (BPMN) variant, the authors present proposals for several important issues in BPM that have not been adequately considered in the BPMN 2.0 standard. It foc...
Conference Paper
Modelling business processes in general is a complex endeavour, as many different aspects such as the control flow, the management of data, event and message handling, actors and interaction, exception handling, etc. have to be taken into account, all of which require different models. This paper focuses on the horizontal integration of models for...
Book
In this chapter we present an Abstract State Machine (ASM) ground model designed to rigorously specify the semantics of Business Process Model and Notation (BPMN) Process Diagrams, based on the BPMN 2.0 standard [95]. However, we deviate from the standard in several points, having identified several inconsistencies as well as ambiguities there. Mor...
Chapter
In this chapter, we discuss the advantages and possible uses of a formal semantic model of a business process modelling language like the one presented in Chap. 4.
Chapter
While we deem the Business Process Model and Notation (BPMN) 2.0 standard an important milestone in the evolution of business process modelling , we found numerous ambiguities, gaps and inconsistencies in the semantics described there (even though it claims that “the BPMN execution semantics have been fully formalized” (in version 2.0) [95, p. 10])...
Chapter
This section provides an overview of related work concerning established approaches for business process modelling , formal representations of the Business Process Model and Notation (BPMN) and the suitability of BPMN for business process modelling regarding gaps and limitations.
Chapter
In this chapter we propose an approach for stepwise refinement of the rigorous semantics for Business Process Model and Notation (BPMN) Process Diagrams presented in Chap. 4. The suggested approach hence fills the gap between an Abstract State Machine (ASM) ground model and a common workflow engine, such as Red Hat JBoss [109], Activiti [5], Bonita...
Chapter
In this chapter, we discuss our approach, including the changes we propose for the Business Process Model and Notation (BPMN) . We further discuss future research work on several extensions to the core language which targets business process diagrams and primarily expresses the flow of activities.
Chapter
The semantic model for the Business Process Model and Notation (BPMN) 2.0 presented in Chap. 4 deviates from the OMG’s standard in several places. In this chapter, we discuss and justify those deviations. Furthermore, we discuss miscellaneous other features of BPMN 2.0 as it is and make further suggestions for improvements. A detailed specification...
Conference Paper
Full-text available
Software support for disaster management requires approaches for flexible and generic processes. The 'ministory approach' provides those properties and is therefore an appropriate concept to address the challenges of disaster management. This paper focuses on the implementation of the mini story approach in the context of disaster management. It pr...
Conference Paper
Full-text available
Workflow management systems provide support for structured processes and help to follow the defined business process. Although their importance has been proved by various applications over the last decades they are not appropriate for all use cases. Such workflow management systems are only applicable for domains where the process is well structure...
Conference Paper
In recent years awareness for disasters increases. Handling response and managing experiences becomes more important and require sufficient support. Existing systems does not support the entire disaster preparation and response cycle and lags behind current technical possibilities. Therefore we propose a system based on a simplified process model n...
Conference Paper
SOA governance is an accepted key factor for successful SOA implementation. A lot of approaches have been proposed for service handling and development guidance, but most of them build upon strict rules and processes. A strict rule corset defined by SOA governance might decrease the willingness to contribute a service, but a broad service offer is...
Article
In this article, we exemplified today's requirements in integrating test automation tools in terms of three integra-tion scenarios combining industrial strength tools in the area of test management, model-based testing and test executionThe article further sketches solutions for the three scenarios by introducing various integration concepts and by...
Article
Full-text available
Application integration via web portals is the most widely used and least expensive means for integrating enterprise applications and services. Component-based portals enable the composition of web pages from reusable portal components, where each component represents an independent application or service. This integration is often limited to compo...
Conference Paper
Full-text available
Software systems based on a service-oriented architecture (SOA) are partitioned into loosely coupled services. Services may be developed by different parties, deployed to different nodes and operated by different organizations. In an SOA services may evolve independently from one another, ideally without sacrificing interoperability. Supporting ser...
Conference Paper
Web portals are a means for presentation level integration of enterprise applications and services. We describe an approach for enhancing presentation level integration in Web portals by supporting communication between presentation level components. The approach is based on established standards in this area and allows the exchange of structured X...
Conference Paper
Web services represent an important technology for distributed applications and will replace various other technologies for distributed application development soon. A lot of problems of the early days of Web services are solved now. However, for authorization no appropriate solution is available and ready to use. We define requirements for authori...
Article
Web applications depend on many different infrastructure components such as Web Servers, Firewalls, or Application Servers. Furthermore these applications are accessed from different browser platforms on different hardware. Changing the infrastructure components affects the Web application architecture itself. Maintainable Web applications require...
Article
Within the scope of the netBanking.webServices project, four different products that support the development of Web Services were investigated. The products were selected together with the project partner. In this document, the results of the investigation are described. Following aspects of the products were investigated: Supported standards, serv...

Network

Cited By