Research on Conversion from UML Activity Diagram to Procedure Blueprint

2011 ◽  
Vol 135-136 ◽  
pp. 766-769
Author(s):  
Jian Bin Liu ◽  
Tie Qiang Li
Keyword(s):  
Process Modeling ◽  
Model Transformation ◽  
Data Exchange ◽  
Modeling Language ◽  
Static Structure ◽  
General Transformation ◽  
Activity Diagram ◽  
Transformation Rules ◽  
Static Modeling ◽  
Uml Activity Diagram

UML, as an international standard, is not suitable for static modeling of the program procedure. While Procedure Blueprint is a visual process modeling language and is suitable for modeling the procedure, which can supplement the UML deficiencies during the process of modeling the program static structure. In this paper, taking XMI as a common data structure and a data exchange bridge, proposed the general transformation idea, the transformation rules and the transformation algorithm from activity diagram to the procedure blueprint. This has laid the foundations for achieving the model transformation at last.

Evolution in Model-Driven Software Product-Line Architectures

2009 ◽  
pp. 1280-1312 ◽  
Author(s):  
Gan Deng ◽  
Jeff Gray ◽  
Douglas C. Schmidt ◽  
Yuehua Lin ◽  
Aniruddha Gokhale ◽  
...  
Keyword(s):  
Model Transformation ◽  
Software Product Line ◽  
Product Line ◽  
Domain Model ◽  
Modeling Language ◽  
Model Driven ◽  
Transformation Rules ◽  
Domain Evolution ◽  
Software Product

This chapter describes our approach to modeldriven engineering (MDE)-based product line architectures (PLAs) and presents a solution to address the domain evolution problem. We use a case study of a representative software-intensive system from the distributed real-time embedded (DRE) systems domain to describe key challenges when facing domain evolution and how we can evolve PLAs systematically and minimize human intervention. The approach uses a mature metamodeling tool to define a modeling language in the representative DRE domain, and applies a model transformation tool to specify model-tomodel transformation rules that precisely define metamodel and domain model changes. Our approach automates many tedious, time consuming, and error-prone tasks of model-to-model transformation, thus significantly reducing the complexity of PLA evolution.

Modeling the Resource Perspective of Business Processes by UML Activity Diagram and Object Petri Net

2011 ◽  
pp. 203-229 ◽  
Author(s):  
Kamyar Sarshar ◽  
Peter Loos
Keyword(s):  
Petri Net ◽  
Process Modeling ◽  
Organizational Context ◽  
Business Processes ◽  
Real Life ◽  
Activity Diagram ◽  
Uml 2.0 ◽  
Resource Perspective ◽  
Uml Activity Diagram ◽  
Object Petri Net

Given that business processes are performed in an organizational context, it is essential that process modeling notations provide proper mechanisms to represent the resources perspective of business processes. After relating the resource perspective within a framework to other business process perspectives and discussing the lifecycle resource models undergo, this contribution introduces the UML 2.0 activity diagrams as well as object Petri nets regarding their approach to model the resource perspective of business processes. Afterwards, the application of the notations is illustrated by a real-life process of the health-care domain. The following comparison of the notations indicates the benefits and the limitations of both notations.

Evolution in Model-Driven Software Product-Line Architectures

2009 ◽  
pp. 102-132 ◽  
Author(s):  
Gan Deng ◽  
Douglas C. Schmidt ◽  
Aniruddha Gokhale ◽  
Jeff Gray ◽  
Yuehua Lin ◽  
...  
Keyword(s):  
Model Transformation ◽  
Product Line ◽  
Domain Model ◽  
Modeling Language ◽  
Model Driven Engineering ◽  
Model Driven ◽  
Transformation Rules ◽  
Domain Evolution ◽  
Software Product

This chapter describes our approach to model-driven engineering (MDE)-based product line architectures (PLAs) and presents a solution to address the domain evolution problem. We use a case study of a representative software-intensive system from the distributed real-time embedded (DRE) systems domain to describe key challenges when facing domain evolution and how we can evolve PLAs systematically and minimize human intervention. The approach uses a mature metamodeling tool to define a modeling language in the representative DRE domain, and applies a model transformation tool to specify modelto- model transformation rules that precisely define metamodel and domain model changes. Our approach automates many tedious, time consuming, and error-prone tasks of model-to-model transformation, thus significantly reducing the complexity of PLA evolution.

Business Process Modeling

2012 ◽  
pp. 32-50 ◽  
Author(s):  
Donald R. Chand ◽  
Alina M. Chircu
Keyword(s):  
Business Process ◽  
Process Modeling ◽  
Process Management ◽  
Business Processes ◽  
Business Process Modeling ◽  
Modeling Tools ◽  
Activity Diagram ◽  
It Systems ◽  
Business Process Modeling Notation ◽  
Uml Activity Diagram

This chapter presents a variety of business process modeling notations that range from programming logic flowcharts to the new standard, BPMN (Business Process Modeling Notation), as put forth by the Business Process Management Initiative (BPMI) (http://www.bpmi.org). Specifically, it discusses (1) the use of unstructured programming flowcharts in modeling business processes and their adaptation in process flow diagramming notation, (2) the UML activity diagram, and (3) BPMN, a comprehensive notation for documenting and modeling complex business processes. Using simple examples, this chapter brings out the inherent complexity of modeling business processes and the need for modeling tools that synchronize and align the mental models of business users, process analyst and information technology (IT) systems developers in order to correctly represent the intended process.

A Based-Rule Method to Transform CIM to PIM into MDA

2016 ◽  
Vol 6 (2) ◽  
pp. 11-24 ◽  
Author(s):  
Yassine Rhazali ◽  
Youssef Hadi ◽  
Abdelaziz Mouloudi
Keyword(s):  
Model Transformation ◽  
State Diagram ◽  
Use Case ◽  
Activity Diagram ◽  
Design Models ◽  
Transformation Rules ◽  
Interesting Part ◽  
Uml Diagrams ◽  
Rule Method ◽  
Use Case Diagram

The model transformation is the most interesting part into MDA. Indeed, two transformations exist between three levels of MDA. Most searches cover the transformation from PIM to PSM. However, a little of approaches allow transforming CIM to PIM. This paper represents an approach allows mastering transformation from CIM to PIM into MDA. This approach is based on good CIM level through selected rules allowing provide rich models that facilitate the transformation to PIM level. Afterwards, the authors determine a concentrated PIM level with main design models established through use case diagram, state diagram, and package diagram. Next, to ensure a semi-automatic transformation from CIM to PIM the researchers specify a set of well-chosen transformation rules. For respecting MDA approach the authors consider the business dimension in CIM level by using business modeling standards of OMG (BPMN and activity diagram). However, the researchers focus on UML diagrams to establish PIM models because UML is recommended by MDA in PIM level.

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