Domain Specific Business Process Modeling in Practice (original) (raw)
Related papers
Practitioners View on Domain Specific Business Process Modeling
Proceedings of the 2011 Conference on Databases and Information Systems Vi Selected Papers from the Ninth International Baltic Conference Db Is 2010, 2011
Practitioners view on modeling with Domain Specific Languages (DSLs) is presented in this paper. It is shown, that unlike general-purpose modeling languages (UML [1], BPMN [2]), DSLs provide means for concise representation of semantics of the particular business domain, enabling development of consistent and expressive business process models. Resulting models can be used not only as specifications for information systems, but also for generation of implementation artifacts, creating documentation, testing and for other purposes. Thus one of the most principal goals of Model Driven Architecture (MDA [3]) -the development of model-based information system -is achieved. specification (as specification language is not sufficient), they must be incorporated directly into the source-code of the system, and, in case of automatically generated source-code serious problems can arise. CASE tools are also quite conservative and slow to catch up the fast development of the programming technologies. As a result, only a fraction of applications can be generated from specifications.
A methodology for domain-specific business process modelling and implementation
International Journal of Business Process Integration and Management, 2009
Design and implementation of a business process in an enterprise often requires three groups of experts: business analysts, solution architects and developers. They collaborate to transform a high-level business process to a final executable system based on e.g. BPEL. Since enterprises often utilise their own domain concepts and use technologies in their own specific ways, standard modelling notations and transformations are insufficient. In this paper, we present a methodology to support and semi-automate the transformation of models into an implementation. It advocates the use of a set of domain-specific modelling languages explicitly designed for an enterprise where each language is tailored for the use of one of the three groups of experts. This enables creation of precise and machine-readable models by using domain concepts familiar to the experts. Further, the domain knowledge required for transforming models from one language to another is captured as reusable transformation patterns.
Domain Specific Languages for Business Process Management: a Case Study
Nowadays, more and more issues need to be considered when implementing tools for domain specific languages with an orientation to the business process management. It is not enough to build just an editor for the language, various specific services need to be provided as well. In this paper, we describe our approach how to develop new domain specific languages for the mentioned field and their support tools. A description of, so called, transformation-driven architecture is outlined as well. It is shown how to use principles of the architecture in developing tool building platforms. Two domain specific languages together with tools implementing them are described as an example.
Business Processes Modelling with DSM Platform at Integrated Systems Development
The first and most labor-consuming stage of information systems development is an analysis stage. At this stage the set of different formal models describing systems domains, different aspects of the created system functioning is created. The model-centric approach focuses attention on the models at the each stage of the development process. Modelling tools are used by developers and experts in specific domains. These tools must be affordable for different specialists. Created models must be clarity and understandable for all developers and domain experts. This feature is supported with domain-specific modelling tools. Language workbenches include means for domain-specific languages creation. Modelling with DSM platform is more suitable for the domain experts, system and business analysts. Different tasks of the system design and development request specific formalizing means needed for modeling. Different modelling languages and tools are used by analysts. They need to support continuity of development stages, reusability of created models for the solution of different tasks. DSM platforms provide model transformations, translation of models from one modelling language to another. These tasks are important for large projects of complex information systems development. The basis of language toolkits creation is metamodeling. The tools of MetaLanguage DSM platform, allowing designing domain specific languages and models for different domains, to transform models at systems integration, are described. Examples of metamodels and models, transformation rules are presented.
Business process modeling languages for information system development
2009
It is known that different process models are used during various phases of the Business Process Modeling (BPM) life cycle. Many efforts have been introduced to overcome the disintegration between these process models to provide a standard process model for design and execution. However this integration is still a problem that mazes the researches in this field till now. This paper discusses the problem of translation between process models, which known as the conceptual mismatch. Different perspectives are described considering the case of Business Process Modeling Notation (BPMN) vs. Business Process Execution Language (BPEL).
The Goal-Based Selection of the Business Process Modeling Language
Lecture Notes in Business Information Processing, 2016
Business process models are an essential issue of enterprise modeling because business process modeling is the means for performing a wide range of tasks, such as documentation, communication, business improvement, and capturing requirements for software design up to creation of executable process descriptions. Nowadays a wide range of general purpose business process modeling languages are used for handling these tasks. Constantly also a number of the general purpose modeling language extensions and domain specific modeling languages (DSL) are being developed. Thus, obviously, the universal business process modeling language that would be suitable for all the modeling purposes does not (yet) exist. In such a situation the modeler is faced with the problem of choosing a business process modeling language suitable for a certain modeling purpose. This paper proposes to base the choice of the language on a formalized business process modeling goal and a three dimensional business process modeling framework. The paper also describes how to use the proposed framework to measure the modeling language conformity to a certain modeling goal using a general business process element taxonomy and metrics.
Business process management with unified modeling language
WSEAS Transactions on …, 2007
The evolution of Enterprise Information Systems(EIS) has been shift from data-centric information systems to process-centric information systems in last decade. Business Process Management(BPM), extension of Workflow Management(WFM) contains methods, techniques and tools to support the design, enactment, management and analysis of business process. Petri Nets(PN) are used like standard for BPM and WFM technology. Our approach is to define a methodology for analyze, design, implement, maintain EIS only with Computer Aided Software Engineering(CASE) tools, according to Model Driven Architecture(MDA) from Platform Independent Models(PIMs) to Platform Specific Models(PSMs). In our approaches we proposed an extension of Object Constraint Language(OCL), Complete Constraint Language(CCL) in idea to use the Activity Diagram(AD) from Unified Modeling Language(UML) as formal basis for BPM and WFM technology, respectively Entity Relationship-Stored Procedures(ER-SP), an extension of ER(Entity Relationship) model for conceptual, syntactic and semantic modeling of relational databases in idea to create a link between external to physical models.
Business process modeling languages
ACM Computing Surveys, 2010
Requirements capture is arguably the most important step of software engineering and yet the most difficult and the least formalized one [Phalp & Shepperd,2000]. Enterprises build information systems to support their business processes. Software engineering research has typically focused on the development process, starting with user requirements-if that-with business modeling often confused with software system modeling [Isoda, 2001]. Researchers and practitioners in management information systems have long recognized that understanding the business processes that an information system must support is key to eliciting the needs of its users (see e.g. [reference]), but lacked the tools to model such business processes or to relate such models to software requirements. Researchers and practitioners in business administration have long been interested in modeling the processes of organizations for the purposes of understanding, analyzing, and improving such processes [reference], but their models were often too coarse to be of use to software engineers. The advent of eCommerce and workflow management systems, among other things, have led to a convergence of interests and tools, within the broad IT community, for modeling and enabling business processes. In this paper, we present an overview of business process modeling languages. We first propose a categorization of the various languages. Then, we describe representative languages from each family.
WICT 2008: 1st National ICT Conference, 2008
In Business-Driven Development (BDD), business process models are produced by business analysts. To ensure that the business requirements are satisfied, the IT solution is directly derived through a process of model refinement. If models do not contain all the required technical details or contain errors, the derived implementation would be incorrect and the BDD lifecycle would have to be repeated. In this project we present a functional domain specific language embedded in Haskell, with which: 1) models can rapidly be produced in a concise and abstract manner, 2) enables focus on the specifications rather than the implementation, 3) ensures that all the required details, to generate the executable code, are specified, 4) models can be transformed, analysed and interpreted in various ways, 5) quality assures models by carrying out three types of checks; by Haskell"s type checker, at construction-time and by functions that analyse the soundness of models, 6) enables users to define quality assured composite model transformations.
A Unified View of Business Process Modelling Languages1
Understanding and specifying business processes is a challenge. Many different approaches have been developed, each with their own specific business process modelling languages designed to meet a business specific requirements. In practice, however, multiple business process languages are often being used within one and the same enterprise. This paper proposes a universal and language independent abstraction of the concepts of today's mainstream business process modelling languages, in a unified ontology based on an analysis of seven popular business process modelling approaches. Generic concepts are identified and a unified meta-model designed. An ontological analysis of the representational capability of this meta-model is examined in relation to the Bunge-Wand-Weber ontology. This meta-model is open to further extensions such as incorporating requirements or extending into a knowledge base.