Integrated Framework for Seamless Modeling of Business and Technical Aspects in Process-Oriented Enterprise Applications

Abstract

The different views and modeling techniques of both the business analysts and software developers are a common problem in business process modeling. Various modeling approaches result in communication problems, as well as redundancies and inconsistencies in system documentation. Thus, when modeling process-oriented enterprise applications seamless support of both expert groups is necessary. However, current business process management and workflow technologies are not fully integrated with user interaction, nor do they offer an appropriate data model. Based on the requirements of two industrial projects, we developed an integrated framework that combines the best practices from process-oriented and form-based approaches to overcome these shortcomings. The described framework supports the submit/response-style interaction paradigm and is independent of modeling languages and tools. In this work, we will present a detailed description of the proposed framework, its application to an industrial project and a discussion of related work.

Towards functional safety and security for adaptive and flexible business processes

“…The number of models required for different aspects makes modelling information systems a complex endeavour . In addition, those models are generally related to different abstraction layers, leading to discrepancies when integrating them . In previous works, we present a concept for designing BPM systems, called the Hagenberg Business Process Modelling (H‐BPM) method, where business process modelling is seen as a first step, but when it comes to process execution, much more is needed for full‐scale software support; users (workers) need to be added to the model, with issues from access control to user interfaces, and business data as well as cross‐platform communication concepts have to be integrated.…”

A Design Theory for Cognitive Workflow Systems

“…Thus, a work°ow that supports knowledge sharing and enables the use of cognitive skills is required. The work°ow must also be designed such that it addresses di®erent views, including those of business analysts and software developers [18], and connects the knowledge to work, processes, and the context of work.…”