reconciling uml and bpmn models in updm€“ jfcom and strike coi for documenting joint close air...
TRANSCRIPT
Approved for Public Release: 09-4979
Fatma Dandashi
Mitre Corp.
Reconciling UML and BPMN Models in UPDM
Approved for Public Release: 09-4979
Market Need
■ Architects have a need to model business processes us ing BPMN– BPMN provides richer semantics vs. UML Activity mod els
■ UPDM architects have a need to develop behavioral m odels using BPMN (within their UPDM architectures)
■ (UML based) SoaML tool vendors have a need to integr ate SoaML and BPMN
2
Approved for Public Release: 09-4979
Problem Statement
■ Existing OMG specs provide no capabilities to tightly link UML (including derivatives – UPDM, SoaML, etc.) and BPMN. By “tightly” we mean:– BPMN elements need to be stored within UML (UPDM)
packages
– UML (UPDM) relations need to target/start from BPMN elements
– UML (UPDM) elements can reference BPMN elements
– BPMN elements can be extended to fit UPDM – addition al UPDM properties
– BPMN elements can reference UPDM elements
3
Approved for Public Release: 09-4979
Goal
■ There is a market need to define links between elemen ts in UML/UPDM/SoaML models and BPMN models, along with an interchange format that can convey all these links
■ Users should be able to develop one model, rather that multiple, loosely coupled models
4
Approved for Public Release: 09-4979
Solution Statement
■ Definition: BPMN as a UML profile with notation – the BPMN meta model is retained and there is also a UML profi le for BPMN –with a mapping between the two. BPMN should l ook the same in either case.
■ Proposed Solution: Create a UML profile for BPMN to enable an architect to utilize BPMN for modeling operational/business architecture views. – The proposed RFC defines a mechanism to link elemen ts in
UPDM models, UML models, and BPMN models, along wit h an interchange format that conveys all these links
5
Not proposing that we define/resolve/agree on what is " the right way" to " integrate BPMN and
UML models" in general
Approved for Public Release: 09-4979
DoD UPDM Requirements
■ Ability to model BPMN elements in UML models, made necessary by the DoD requirement to enable:– Integrating the models in UML tools
– Exchanging these integrated models between UML tool s
6
Approved for Public Release: 09-4979
DoD Position Statement
■ For UPDM, UML is essentially used as an infrastructure for integrating various Enterprise Architecture (EA) viewpo ints such as capabilities, systems, organizations, informa tion, etc.– Based on OMG and market facts, there are currently no
infrastructures (other than UML profiles) at the OM G to enable the EA integration
■ DoD backs the intention to create a UML profile for BP MN in order to utilize BPMN for modeling some of the DoDAF/UPDM views
7
Approved for Public Release: 09-4979
Discussion (1 of 4)
■ DoDAF v 2 calls for Fit for Purpose Presentation & Models– Architects should be able to
use modeling notation that is appropriate or “fit” for the purpose or audience
8
Modeling Notation
BPMNUML
SysML...
Approved for Public Release: 09-4979
Discussion (2 of 4)■ DoD components now use BPMN for modeling operational
views, e.g.,– JFCOM and Strike CoI for documenting Joint Close Ai r Support
(JCAS) Scenario
– BTA for documenting DoD’s Business Enterprise Archi tecture (BEA)
■ Currently in UPDM, there is no automated mechanism for operational users (using BPMN) and system integrators (using UML) to link requirements/operational models to systems/solution models, such that:– Forward traceability between operational and system models is
maintained to ensure coverage of requirements
– Backward traceability from system to operational mo dels is maintained to ensure validity of solution
■ Creating a UML profile for BPMN would allow reusing BP MN within UPDM, in the same manner that SysML and SoaML are reused
9
Approved for Public Release: 09-4979
Discussion (3 of 4)
■ Some UML tool vendors are already providing support forBPMN within their tools– Military: DoD/NATO ISAF* application - two separate models:
the process model is in BPMN, the data model is in UML. “need for well-defined links between BPMN messages (i.e., specific or generic data put/gets) and UML object representatio ns of those data objects. .. Subsequently having SVs that link th ese UML class/objects to specific systems and SOA servic es. ”
– Commercial: “Native integration between BPMN and UP DM is a worthy goal as we lose the native link using tools today. So for example, we cannot query for impact analysis betwee n OV-2 and OV-5 (as BPMN) using a native UPDM implementati on. It has to be chained via meta-model transformation.”
■ Each vendor/user is defining their own path forward. T hisprevents common mapping and interchange
10
Approved for Public Release: 09-4979
Discussion (4 of 4)
■ Several exchange mechanisms for BPMN exist:– Two exchange mechanisms for BPMN are being develope d by
OMG: BPMN XMI and XML Schema serialization
■ Defining a UML profile for BPMN and utilizing profile within UPDM enables:
■One format for exchange across UML/SysML tools (the se are the UPDM submitters) with UML XMI
11
Approved for Public Release: 09-4979
UPDM 1 + BPMN = UPDM 2
UPDM v2UPDM v2
UPDM L1
SoaML
UML
UPDM L0SysML
BPMN v2
UPDM v1UPDM v1
UPDM L1
SoaML
UML
UPDM L0SysML
12
Approved for Public Release: 09-4979
UPDM v2 with BPMN-SoaML Integration
UPDM v2-beforeUPDM v2-before
UPDM L1
SoaML
UML
UPDM L0SysML
BPMN v2
UPDM v2-afterUPDM v2-after
UPDM L1
SoaML
UML
UPDM L0SysML
BPMN v2
13
Approved for Public Release: 09-4979
Deliverables
■ UML-BPMN mapping
■ UML extensions for BPMN structures (a UML profile)
■ XSLT transformation between UML and BPMN models, based on UML-BPMN mapping
14
Approved for Public Release: 09-4979
Work Completed so far
■ UML – BPMN mapping
■ Draft UML profile for BPMN
■ Draft spec for “UML profile for BPMN” (autogenerated)
15
Approved for Public Release: 09-4979
How does this affect UML tool vendors
■ UML Profile for BPMN will provide the ability to defin e integrated models, linking software architectures to h igher level business processes
■ UML Profile for BPMN will allow interchange of UML mo dels across UML tools
16
Approved for Public Release: 09-4979
How does this affect BPMN tool vendors
■ Impact on the "business" world is minimal-to-none, since this standard affects UML tool vendors only. Business analysts that care little about UML will see absolut ely no change
■ BPMN tool vendors will have a standard means for converting their models to UML, given there is a stand ard mapping and XSLT transformations
17
Approved for Public Release: 09-4979
Target Users for BPMN Profile
■ UML modelers and architects who want to introduce BPMN diagrams in their models. BPMN has richer semantics, an d business-user friendly notation and semantics for model ing business processes within an architecture model
■ Business Analysts (indirect audience)- Definition of the BPMN profile defines a common mapping to UML, which helps to hand-off BPMN diagrams to UML modelers in a common way. This provides model traceability from syst em design and solution architecture models back to busine ssmodels
■ Organizations currently using UML and BPMN tools with a need for model interchange
18
Approved for Public Release: 09-4979
BMI View in General
■ UML modelers and UPDM modelers have expressed their need to use both BPMN and UML in a single model
■ Discussion ensued within the BMI concerning possible methods for meeting the requirement. The table below captures informal results of those discussions
19
http://www.doodle.com/q3v57nx7tmp7ce27
Not in time for UPDM v2.0
They remain separate standards
BPMN is a UML profile with notation
Create is a unified model encompassing both
Semantic models with UML and BPMN viewpoints
BPMN replaces UML activity diagrams
BPMN grows to make UML not required
BPMN and UML are separate models, mapped with QVT
There are ways to make links between them
Other
2 5 15 8 4 0 2 3 0
Approved for Public Release: 09-4979
Current supporters
■ Armstrong Process Group
■ Artisan (vendor)
■ Canadian National Defence
■ KnowGravity (vendor)
■ MEGA (vendor)
■ Model Driven (vendor)
■ No Magic (vendor)
■ Mitre
■ Oose Innovative Informatik GmbH
■ Sandia National Laboratories
■ Sodius (vendor)
■ Softeam (vendor)
■ Sparx Systems (vendor)
■ US DoD
20
Approved for Public Release: 09-4979
Next steps
■ Get agreement within OMG that a “UML profile for BPMN” is a solution for this problem scope/audience
■ Find a TaskForce for “UML profile for BPMN”
■ Polish the mapping/profile/spec. Create XSLT
■ Issue RCF for the next TC meeting (March, 2010)
21
Approved for Public Release: 09-4979
Summary
■ The proposed RFC defines a mechanism to link element s in UPDM models, UML models, and BPMN models, along wit h an interchange format that can convey all these links
■ The UPDM requirements are:– BPMN elements need to be stored within UPDM package s
– UPDM relations need to target/start from BPMN eleme nts
– UPDM elements can reference BPMN elements
– BPMN elements can be extended to fit UPDM
– BPMN elements can reference UPDM elements
22
Not proposing that we define/resolve/agree on what is " the right way" to " integrate BPMN and
UML models" in general
Approved for Public Release: 09-4979
Definitions
■ Business Process Model and Notation (BPMN)– Supports business users by providing a notation tha t is
intuitive (for business/military users), yet able t o represent complex process semantics
■ Unified Modeling Language (UML) – The way the world (systems and software engineers) models
application structure, behavior, and architecture
■ Unified Profile for DoDAF/MODAF (UPDM)– Provides industry standard UML representation of
DoDAF/MODAF architecture models
24