The Value of Roles in Modeling Business Processes

Pavel Balabko, Nicolas Clément, Alain Wegmann
2004
Article de conférence

Résumé

Rapid business changes require companies to make rapid changes in business processes and ultimately in BPS systems. These changes can be done rapidly if business modelers understand the base roles of business processes and relationships between these roles. In this paper we present an alternative to the traditional business processes modeling approaches. In our approach we make explicit roles present in business processes. This facilitates business process reengineering and improves the alignment between business and supporting systems.

Official source

https://infoscience.epfl.ch/record/55772?ln=fr

À propos de ce résultat

Cette page est générée automatiquement et peut contenir des informations qui ne sont pas correctes, complètes, à jour ou pertinentes par rapport à votre recherche. Il en va de même pour toutes les autres pages de ce site. Veillez à vérifier les informations auprès des sources officielles de l'EPFL.

Concepts associés

Chargement

Publications associées

Chargement

Publications associées (14)

Capturing Design Rationale with Functional Decomposition of Roles in Business Processes Modeling

Pavel Balabko, Nicolas Clément, Alain Wegmann

Enterprises need to create and maintain the fit between their business processes and their business process support (BPS) systems. This frequently requires re-engineering of business processes. If the business processes design ration-ales are made explicit, the re-engineering of the existing business processes is easier. Making the design rationales ex-plicit is useful to understand why things exist as they are, and to understand if and how they can be changed. The most common way to capture design rationales is to list the design decisions underlying the business process. In the method proposed in this publication, we capture design rationales through role modeling. We document the design rationales for each role in the analyzed business process. The roles are described as the compositions of base func-tionalities. A base functionality is the specification of a role (or of a part of a role) from the viewpoint of one of the specific specialists who design the business process. These base functionalities are composed together to describe the roles of the participants to the business process. As a result, a business process modeler can understand who is respon-sible of what in the business processes. In collaboration with the specialists, the business modeler can then ensure that no important part of the business process is missing or is unnecessary. Thanks to this work, the business process can be verified before being automated with the BPS system.

2005

Chargement

, ,

Service modeling is an important step in designing service-oriented systems. There are multiple levels of design because service sci-ence includes both the business rationale and the IT implementation ofthe services. As business and IT perspectives differ, the modeling tech-niques are different, and often the respective modeling languages aredisconnected or ad-hoc. We propose a new service-modeling approachfor connecting the business modeling and the web service modeling bypresenting these two perspectives in a single model. We present a multi-stage modeling process for capturing different perspectives and creatingmodels iteratively by working with levels of abstraction from higher tolower. The model is then used as an input in order to generate a RESTAPI specification in the OpenAPI format to feed the next stages of theservice life-cycle.

2018

Chargement

The Role of Synthesis Constraints in Role Modeling

Pavel Balabko, Alain Wegmann

To reuse existing specifications and increase the speed of development, modern development methods widely use design patterns and collaborations. Both, design patterns and collaborations, use the concept of role as a basic modeling concept. To specify models where one object may play several roles, a synthesis operation (the composition of two base roles in a third role) has to be specified. All role-based approaches have difficulties specifying role synthesis. As a consequence, synthesis is never specified without the description of the actual implementation of the synthesis. To specify synthesis at a higher level of abstraction, independent of implementation, requires the proper understanding of relationships between roles, when they are put together in one common context. In this paper we define the concept of synthesis constraints that shows relations between roles. We show how synthesis constraints can be used to specify the role synthesis operation. Using synthesis constraints allows a designer to make explicit his decisions about how the synthesis is done in an abstract and implementation independent way. Specifying synthesis with synthesis constraints is a powerful technique that can be used in many different domains, especially in business engineering. The use of roles allows a developer to specify separately certain concerns of a business system. This enables the discovery of new business models for a business system by means of different disassembling and assembling of roles.

2002

Chargement

Afficher plus