Search results

This paper reviews existing business process (BP) modeling languages that are widely used in the industry as well as recent research work on modeling and analysis of BPs in the service-oriented environment and Internetware-based software paradigm. BPs in such environment are different from traditional BPs due to loose coupling of partner services, dynamic and on-the-fly selection of partners and run-time process adaptability. The unique characteristics of these BPs require formal modeling of the requirements and constraints in each phase of their life cycle, including design phase, implementation and deployment phase and execution phase.

The paper first provides a categorization of typical user requirements in each phase of the BP life cycle. Then a detailed comparison of the selected languages with respect to their requirement modeling and analysis capabilities in each of the identified categories is provided. The paper also discusses new requirements engineering research challenges arising from future software needs and emerging trends in software engineering in the context of Web-services-based BPs and Internetware.

There is a need to have a framework that provides support for user requirements modeling and analysis for all the phases of BP life cycle in an integrated manner. Such a framework would be useful not only in resolving the inconsistencies between requirements across phases but also in addressing the issues related to BP evolution due to changes in user requirements over time. Moreover, with the Internet of things (IoT) adoption in BPM, there is a need to have an integrated environment that provides support for capturing the resilience requirements of enterprise BPs as well as the mobility constraints of the underlying IoT devices.

This paper reviews existing BP modeling languages and frameworks and discusses the new requirements engineering research challenges arising from future software needs and the emerging trends in BP management in the service-oriented environment and Internetware-based software paradigm.

Service‐oriented architecture is becoming increasingly important for healthcare delivery as it assures seamless integration internally between various teams and departments, and externally between healthcare organizations and their partners. In order to make healthcare more efficient and effective, we need to understand and evaluate its processes, and one way of achieving that is through process modeling. Modeling healthcare processes within a service‐oriented environment opens up new perspectives and raises challenging questions. The purpose of this paper is to investigate one of these questions, namely the suitability of web service orchestration and choreography, two closely related but fundamentally different methodologies for modeling web service‐based healthcare processes.

The authors use a case‐based approach that first developed a set of 12 features for modeling healthcare processes and then used the features to compare orchestration and choreography for modeling part of the scheduled workflow.

The findings show that neither methodology can, by itself, meet all healthcare modeling requirements in the context of the case study. The appropriate methodology must be selected after consideration of the specific modeling needs. The authors identified usability, capabilities, and evolution as three key considerations to assist with selection of a methodology for healthcare process modeling. Further, sometimes one method will not meet all modeling needs and hence the authors recommend combining the two methodologies in order to harness the benefits of modeling healthcare processes in a service‐oriented environment.

Although literature exists on process modeling of web services for healthcare, there are no criteria describing necessary features for micro‐level modeling, nor is there a comparison of the two leading service composition methodologies within the healthcare context. This paper provides some necessary formalization for process modeling in healthcare.

The purpose of this paper is to identify the relationships between process modeling and Industry 4.0, the strategic themes and the most used process modeling language in smart factories. The study also presents the growth of the field of study worldwide, the perspectives, main challenges, trends and suggestions for future works.

To do this, a science mapping was performed using the software SciMAT, supported by VOS viewer.

The results show that the Business Process Model and Notation (BPMN), Unified Modelling Language (UML) and Petri Net are the most relevant languages to smart manufacturing. The authors also highlighted the need to develop new languages or extensions capable of representing the dynamism, interoperability and multiple technologies of smart factories.

It was possible to identify the most used process modeling languages in smart environments and understand how these languages assist control and manage smart processes. Besides, the authors highlighted challenges, new perspectives and the need for future works in the field.

In data engineering, view formalisms are used to provide flexibility to users and user applications by allowing them to extract and elaborate data from the stored data sources. Conversely, since the introduction of EXtensible Markup Language (XML), it is fast emerging as the dominant standard for storing, describing, and interchanging data among various web and heterogeneous data sources. In combination with XML Schema, XML provides rich facilities for defining and constraining user‐defined data semantics and properties, a feature that is unique to XML. In this context, it is interesting to investigate traditional database features, such as view models and view design techniques for XML. However, traditional view formalisms are strongly coupled to the data language and its syntax, thus it proves to be a difficult task to support views in the case of semi‐structured data models. Therefore, in this paper we propose a Layered View Model (LVM) for XML with conceptual and schemata extensions. Here our work is three‐fold; first we propose an approach to separate the implementation and conceptual aspects of the views that provides a clear separation of concerns, thus, allowing analysis and design of views to be separated from their implementation. Secondly, we define representations to express and construct these views at the conceptual level. Thirdly, we define a view transformation methodology for XML views in the LVM, which carries out automated transformation to a view schema and a view query expression in an appropriate query language. Also, to validate and apply the LVM concepts, methods and transformations developed, we propose a viewdriven application development framework with the flexibility to develop web and database applications for XML, at varying levels of abstraction.

Ubiquitous web applications (UWA) are a new type of web applications which are accessed in various contexts, i.e. through different devices, by users with various interests, at anytime from anyplace around the globe. For such full‐fledged, complex software systems, a methodologically sound engineering approach in terms of model‐driven engineering (MDE) is crucial. Several modeling approaches have already been proposed that capture the ubiquitous nature of web applications, each of them having different origins, pursuing different goals and providing a pantheon of concepts. This paper aims to give an in‐depth comparison of seven modeling approaches supporting the development of UWAs.

This methodology is conducted by applying a detailed set of evaluation criteria and by demonstrating its applicability on basis of an exemplary tourism web application. In particular, five commonly found ubiquitous scenarios are investigated, thus providing initial insight into the modeling concepts of each approach as well as to facilitate their comparability.

The results gained indicate that many modeling approaches lack a proper MDE foundation in terms of meta‐models and tool support. The proposed modeling mechanisms for ubiquity are often limited, since they neither cover all relevant context factors in an explicit, self‐contained, and extensible way, nor allow for a wide spectrum of extensible adaptation operations. The provided modeling concepts frequently do not allow dealing with all different parts of a web application in terms of its content, hypertext, and presentation levels as well as their structural and behavioral features. Finally, current modeling approaches do not reflect the crosscutting nature of ubiquity but rather intermingle context and adaptation issues with the core parts of a web application, thus hampering maintainability and extensibility.

Different from other surveys in the area of modeling web applications, this paper specifically considers modeling concepts for their ubiquitous nature, together with an investigation of available support for MDD in a comprehensive way, using a well‐defined as well as fine‐grained catalogue of more than 30 evaluation criteria.

The definition of modeling languages is a key‐prerequisite for model‐driven engineering. In this respect, Domain‐Specific Modeling Languages (DSMLs) defined from scratch in terms of metamodels and the extension of Unified Modeling Language (UML) by profiles are the proposed options. For interoperability reasons, however, the need arises to bridge modeling languages originally defined as DSMLs to UML. Therefore, the paper aims to propose a semi‐automatic approach for bridging DSMLs and UML by employing model‐driven techniques.

The paper discusses problems of the ad hoc integration of DSMLs and UML and from this discussion a systematic and semi‐automatic integration approach consisting of two phases is derived. In the first phase, the correspondences between the modeling concepts of the DSML and UML are defined manually. In the second phase, these correspondences are used for automatically producing UML profiles to represent the domain‐specific modeling concepts in UML and model transformations for transforming DSML models to UML models and vice versa. The paper presents the ideas within a case study for bridging ComputerAssociate's DSML of the AllFusion Gen CASE tool with IBM's Rational Software Modeler for UML.

The ad hoc definition of UML profiles and model transformations for achieving interoperability is typically a tedious and error‐prone task. By employing a semi‐automatic approach one gains several advantages. First, the integrator only has to deal with the correspondences between the DSML and UML on a conceptual level. Second, all repetitive integration tasks are automated by using model transformations. Third, well‐defined guidelines support the systematic and comprehensible integration.

The paper focuses on the integrating direction DSMLs to UML, but not on how to derive a DSML defined in terms of a metamodel from a UML profile.

Although, DSMLs defined as metamodels and UML profiles are frequently applied in practice, only few attempts have been made to provide interoperability between these two worlds. The contribution of this paper is to integrate the so far competing worlds of DSMLs and UML by proposing a semi‐automatic approach, which allows exchanging models between these two worlds without loss of information.

This research work aims to expose the detailed construction of a framework for translation between Business Process Modeling and Notation (BPMN) and a citizen process language, named GERAL, so that BPMN and modeling non-experts can publicize their procedural information in an understandable and quality manner. The artifact is built in detail through epistemological rigor derived from empirical evidence and best practices related to the topic of understanding business processes, both based on well-established literature on the subject.

In the case of research involving the construction of an artifact, the design science research (DSR) methodology was used to conduct engineering with an emphasis on the scientific method; for evaluation, the authors used the case study methodology. Data collection is based on documentation analysis, questionnaire, interview and observation. The authors also use references associating DSR with case studies, for greater contextual rigor of the research.

This work presents findings and contributions, both new and also reinforcing others already present (1) use of the principles of Citizen/Plain Language improve instructional communication related to process modeling; (2) the citizen process language GERAL itself; (3) the BPMN pra GERAL guide for process translation; (4) qualitative findings from the observation of the use of the artifact in a real case, with non-experts and (5) a well-founded instance of building a notation with an emphasis on understanding, which can be replicated in other cases.

Future perspectives for conducting the research are presented. As a qualitative research instantiated involving a subjective construct, such as understanding, generalization is partially limited and should be interpreted as a transferability criterion. The evaluation involved participants with complete higher education and graduates, even though from areas not dedicated to process modeling or BPMN, being non-experts. The main indicator was understood with limitations in other aspects, such as formal semantics and precise executability.

The formative research showed improvements to the base artifact, the framework first version, which will consequently be reflected in the guide. The GERAL and the guide were very well received, and all participants were able to translate the proposed model effectively, despite small slips in second notation. The guide improved the participants' perception of transparency and understanding of business processes, making them aware of the benefits of this topic.

The output of the built and researched artifact are understandable models by non-experts in technical languages of business processes. It is an alternative for BPMN models and dubious/long texts. Almost unexpectedly, the guide and its principles awaken an appreciation of understandable procedural communication, that is, it builds an intrinsic motivation in the user of the importance of publicizing his processes and assists in compliance with current data disclosure laws. It also builds informational democratic values of better participation and data absorption, from translators to the target audience.

It presents a qualitative approach to deal with business process modeling and understanding; substantiates in detail, using well-established bases in the literature, the construction of a solution aimed at understanding business processes; offers a translation guide for non-experts and experts interested in disclosing and instructing their procedural information modeled in BPMN.

The paper proposes the development of a graphical architecture description language (ADL) that allows a better understanding of software architectures for nontechnical actors and purposes and, beyond, can serve as a communication tool between domain experts and IT experts, for instance, in a software development process.

The paper follows the methods and guidelines of design science research. By deriving characteristics and general requirements for ADLs from a research literature review and from industry standards, the paper provides a conceptual modeling approach for an ADL. The model design is based on typical requirements and suggestions derived from literature and related work. The application possibilities and advantages are then demonstrated with a usage scenario.

The paper elaborates a user-oriented ADL that makes software architecture comprehensible for stakeholders and end users. It provides a high level of abstraction and, thus, is not restricted to a particular domain. The paper also provides a corresponding modeling editor as well as an underlying catalogue with symbols and rules for the ADL.

As this is a conceptual study, the ADL has not been practically evaluated yet. Thus, the usefulness of this academic approach for the industry remains to be validated.

The elaborated ADL can serve as a language to visualize software architectures, particularly in the business domain, in a comprehensible manner. Still, it retains the structured character of ADLs to facilitate communication on an IT-near level. In including nontechnical actors, the approach broadens the overall application capabilities of ADLs.

The purpose of this paper is to propose a solution for automating the task of matching business process models and search for correspondences with regard to the model semantics, thus improving the efficiency of such works.

A method is proposed based on combining several semantic technologies. The research follows a design-science-oriented approach in that a method together with its supporting artifacts has been engineered. It application allows for reusing legacy models and automatedly determining semantic similarity.

The method has been applied and the first findings suggest the effectiveness of the approach. The results of applying the method show its feasibility and significance. The suggested heuristic computing of semantic correspondences between semantically heterogeneous business process models is flexible and can support domain users.

Even though a solution can be offered that is directly usable, so far the full complexity of the natural language as given in model element labels is not yet completely resolvable. Here further research could contribute to the potential optimizations and refinement of automatic matching and linguistic procedures. However, an open research question could be solved.

The method presented is aimed at adding to the methods in the field of business process management and could extend the possibilities of automating support for business analysis.

The suggested combination of semantic technologies is innovative and addresses the aspect of semantic heterogeneity in a holistic, which is novel to the field.

Automating the task of identifying process weaknesses using process models is promising, as many organizations have to manage a large amount of process models. The purpose of this paper is to introduce a pattern-based approach for automatically detecting potential process weaknesses in semantic process models, thus supporting the task of business process improvement.

Based on design research, combined with a case study, the authors explore the design, application and evaluation of a pattern-based process weakness detection approach within the setting of a real-life case study in a German bank.

Business process weakness detection can be automated to a remarkable extent using pattern matching and a semantic business process modeling language. A case study provided evidence that such an approach highly supports business process analysts.

The presented approach is limited by the fact that not every potential process weakness detected by pattern matching is really a weakness but just gives the impression to be one. Hence, after detecting a weakness, analysts still have to decide on its authenticity.

Applying weakness patterns to semantic process models via pattern matching allows organizations to automatically and efficiently identify process improvement potentials. Hence, this research helps to avoid time- and resource-consuming manual analysis of process model landscapes.

The approach is not restricted to a single modeling language. Furthermore, by applying the pattern matching approach to a semantic modeling language, the authors avoid ambiguous search results. A case study proves the usefulness of the approach.