Model-Driven Development and Business Process Modeling Applied to Personal Productivity in the Consumer Mobile App Market

2015 ◽  
Author(s):  
Max Bancora ◽  
Davide Ripamonti ◽  
Andrea Vaccarella ◽  
Marco Brambilla
Keyword(s):  
Business Process ◽  
Process Modeling ◽  
Business Process Modeling ◽  
Mobile App ◽  
Model Driven Development ◽  
Model Driven ◽  
Personal Productivity

Research on the Business Process Modeling Based on Domain-Specific Modeling Meta-Model Driven

2011 ◽  
Vol 101-102 ◽  
pp. 860-863
Author(s):  
Lei Chen ◽  
Hong Fei Zhan ◽  
Jun He Yu ◽  
Zhong Ren Jiang ◽  
Chen Jian Lei
Keyword(s):  
Business Process ◽  
Process Modeling ◽  
Business Process Modeling ◽  
Model Driven Architecture ◽  
Meta Model ◽  
Model Driven ◽  
Domain Specific ◽  
Property Relationship ◽  
Domain Specific Modeling ◽  
Specific Modeling

To decrease the difficulty of business process modeling, the domain-specific modeling (DSM) method and the frame of model driven architecture (MDA) were discussed in this paper. By applying DSM and MDA, the meta-model consisting of domain schema and domain template was established to simplify the business process. Then the character property, relationship property and operation of business-process-oriented DSM (BP-DSM) meta-model were described. The meta-model and application template would be consummated by continuous instantiation and abstraction of the domain concepts. By extracting and accumulating a large number of enterprises' templates within the same industry, the industry-oriented model template would be ultimately established.

scholarly journals Influence of diagram layout and scrolling on understandability of BPMN processes: an eye tracking experiment with BPMN diagrams

2021 ◽  
Author(s):  
Daniel Lübke ◽  
Maike Ahrens ◽  
Kurt Schneider
Keyword(s):  
Eye Tracking ◽  
Business Process ◽  
Process Modeling ◽  
Business Models ◽  
Business Process Modeling ◽  
Process Models ◽  
Software Systems ◽  
Process Diagrams ◽  
Style Guides ◽  
Important Activity

AbstractBusiness process modeling is an important activity for developing software systems—especially within digitization projects and when realizing digital business models. Specifying requirements and building executable workflows is often done by using BPMN 2.0 process models. Although there are several style guides available for BPMN, e.g., by Silver and Richard (BPMN method and style, vol 2, Cody-Cassidy Press, Aptos, 2009), there has not been much empirical research done into the consequences of the diagram layout. In particular, layouts that require scrolling have not been investigated yet. The aim of this research is to establish layout guidelines for business process modeling that help business process modelers to create more understandable business process diagrams. For establishing benefits and penalties of different layouts, a controlled eye tracking experiment was conducted, in which data of 21 professional software developers was used. Our results show that horizontal layouts are less demanding and that as many diagram elements as possible should be put on the initially visible screen area because such diagram elements are viewed more often and longer. Additionally, diagram elements related to the reader’s task are read more often than those not relevant to the task. BPMN modelers should favor a horizontal layout and use a more complex snake or multi-line layout whenever the diagrams are too large to fit on one page in order to support BPMN model comprehension.

BRIDGING THE GAP BETWEEN BUSINESS MODELS AND WORKFLOW SPECIFICATIONS

2004 ◽  
Vol 13 (03) ◽  
pp. 289-332 ◽  
Author(s):  
JULIANE DEHNERT ◽  
WIL M. P. VAN DER AALST
Keyword(s):  
Information System ◽  
Business Process ◽  
Process Modeling ◽  
Business Models ◽  
Formal Semantics ◽  
Business Process Modeling ◽  
Modeling Language ◽  
Correctness Criterion ◽  
Process Chains ◽  
Selection Of

This paper presents a methodology to bridge the gap between business process modeling and workflow specification. While the first is concerned with intuitive descriptions that are mainly used for communication, the second is concerned with configuring a process-aware information system, thus requiring a more rigorous language less suitable for communication. Unlike existing approaches the gap is not bridged by providing formal semantics for an informal language. Instead it is assumed that the desired behavior is just a subset of the full behavior obtained using a liberal interpretation of the informal business process modeling language. Using a new correctness criterion (relaxed soundness), it is verified whether a selection of suitable behavior is possible. The methodology consists of five steps and is illustrated using event-driven process chains as a business process modeling language and Petri nets as the workflow specification language.

Sign in / Sign up

Export Citation Format

Share Document