8/9/2019 Ebx Ml Collaboration Modeling Met a Model
1/82
Draft Version 0.1
DO NOT DISTRIBUTE
Collaboration Modeling Metamodel
& UML ProfileDraft Version 0.1
1
2
3
4
5
6
1
8/9/2019 Ebx Ml Collaboration Modeling Met a Model
2/82
Contents
Document Revision History........................................................i
Executive Summary.................................................................iii
Preface.................................................................................... v
1. Introduction........................................................................1
2. The Business !erations "a! "etamode#..............................$
2.1 Model Abstract Syntax....................................................................3
2.1.1 Stereotypes and Tagged Values..............................................3
2.1.2 Well-formedness Rules...........................................................
2.2 Model Semant!cs............................................................................."
2.3 Model Management Abstract Syntax.............................................."
2.3.1 Stereotypes and Tagged Values.............................................."
2.3.2 Well-formedness Rules...........................................................#
2.$ Model Management Semant!cs.......................................................%
$. The Business Re%uirements &ie' "etamode#........................(
3.1 Model Abstract Syntax....................................................................&
3.1.1 Stereotypes and Tagged Values..............................................&
3.1.2 Well-formedness Rules.........................................................1#
3.2 Model Semant!cs...........................................................................1%
3.3 Model Management Abstract Syntax............................................1&
3.3.1 Stereotypes and Tagged Values............................................1&
3.3.2 Well-formedness Rules.........................................................2'
3.$ Model Management Semant!cs.....................................................2'
2
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
3
8/9/2019 Ebx Ml Collaboration Modeling Met a Model
3/82
). The Business !erationa# &ie' "etamode#..........................22
$.1 Model Abstract Syntax..................................................................22
$.1.1 Stereotypes and Tagged Values............................................22
$.1.2 Well-formedness Rules.........................................................3'
$.2 Model Semant!cs...........................................................................32
$.2.1 (us!ness Act!)!t!es................................................................33
$.2.2 Re*uest!ng (us!ness Act!)!ty................................................$1
$.2.3 +b,ect lo...........................................................................$1
$.2.$ (us!ness /ollaborat!on 0rotocol............................................$1
$.2. (+V-to-(RV Mapp!ng............................................................$1
$.3 Model Management Abstract Syntax............................................$2
$.3.1 Stereotypes and Tagged Values............................................$2
$.3.2 Well-formedness Rules.........................................................$3
$.$ Model Management Semant!cs.....................................................$3
*. The +unctiona# Service &ie' "etamode#..............................)*
.1 Model Abstract Syntax..................................................................$
.1.1 Stereotypes and Tagged Values............................................$
.1.2 Well-formedness Rules.........................................................3
.2 Model Semant!cs...........................................................................3
.2.1 Agent $
.2.2 (us!nessSer)!ce....................................................................$
.2.3 Ser)!ceTransact!on................................................................
.2.$ etor/omponent..............................................................
.2. (us!nessMessage..................................................................
.2." Messagen)elope.................................................................
.2.# (us!nessAct!onMessage........................................................
.2.% (us!nessS!gnalMessage........................................................
4
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
5
8/9/2019 Ebx Ml Collaboration Modeling Met a Model
4/82
.2.& Re*uest!ngSer)!ceTransact!on..............................................
.2.1' Respond!ngSer)!ceTransact!on.................................."
.2.11 Ser)!ce /ollaborat!on................................................."
.2.12 (us!nessAct!onMessage.............................................#
.2.13 lement4d..................................................................#
.2.1$ 4nformat!onnt!ty.......................................................#
.2.1 Messagen)elope......................................................#
.2.1" (us!nessAct!onMessage.............................................%
.2.1# (us!nessS!gnalMessage.............................................%
.2.1% 5nstructuredMessage................................................%
.2.1& StructuredMessage....................................................%
.3 Model Management Abstract Syntax 6 Semant!cs......................%
,. "ode# -otation..................................................................,1
".1 Stereotype otat!on......................................................................"1
".2 Model 7!agrams............................................................................"1
".2.1 (us!ness +perat!ons Map 7!agrams....................................."1
".2.2 (us!ness Re*u!rements V!e 7!agrams................................"3
".2.3 (us!ness +perat!onal V!e 7!agrams..................................."$
".2.$ unct!onal Ser)!ce V!e 7!agrams........................................""
".2. 4mplementat!on rameor V!e 7!agramsError Boo/mar/not de0ned.
. Bi#io3ra!hy......................................................................4
+i3ures
!gure 1. (+M Abstract Syntax.....................................................................3
!gure 2. (+M 4llustrat!on............................................................................."
!gure 3. (+M Model Management Abstract Syntax.....................................#
6
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
7
8/9/2019 Ebx Ml Collaboration Modeling Met a Model
5/82
!gure $. (+M Model Management 4llustrat!on.............................................%
!gure . (RV Abstract Syntax......................................................................&
!gure ". (RV 4llustrat!on............................................................................1%
!gure #. (RV Model Management Abstract Syntax....................................2'
!gure %. (RV Model Management 4llustrat!on............................................21
!gure &. (+V Abstract Syntax....................................................................23
!gure 1'. (+V 4llustrat!on............................................................................33
!gure 11. Re*uest!ng (us!ness Act!)!ty States............................................3"
!gure 12. Respond!ng (us!ness Act!)!ty States...........................................3#
!gure 13. (+V-to-(RV Syntax Map...............................................................$2
!gure 1$. (+V Model Management Abstract Syntax...................................$3
!gure 1. (+V Model Management 4llustrat!on............................................$$
!gure 1". SV Abstract Syntax.....................................................................$"
!gure 1#. xample 0rocess Area 7!agram..................................................."2
!gure 1%. xample (us!ness 0rocess Act!)!ty 7!agram................................"2
!gure 1&. xample (us!ness 5se /ase 7!agram.........................................."3
!gure 2'. xample (us!ness /ollaborat!on 7!agram..................................."$
!gure 21. xample /ommerc!al Transact!on 7!agram................................."
!gure 22. xample (us!ness collaborat!on protocol 7!agram......................""
8
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
9
8/9/2019 Ebx Ml Collaboration Modeling Met a Model
6/82
Document Revision History
0.1 8/11/2000 First draft translation of BCF 2.0 version 2.0
103
104
105
10
8/9/2019 Ebx Ml Collaboration Modeling Met a Model
7/82
Executive Summary
Business partners must collaborate if they are to remain competitive. A hih level ofcollaboration is possible !hen business partners lin" their businesses processes throuh aninterface of net!or" computer e#business services that enforce commercial tradin areements
modeled as collaborative e$chanes of business information% in areed se&uences and !ithinareed timeframes. A commercial tradin areement is modeled as a business process modele$pressed !ith the 'nified (odelin )anuae *'()+ and the ,b-ect Constraint )anuae*,C)+. he '() is a lanuae e$pressive enouh to specify the structure and behavior ofob-ects that interact in any conceptual domain of discourse. A process model% ho!ever% is aspecification of the structure and behavior of ob-ects interactin at business partner interfaces% aspecialied domain of discourse. his document describes an e$tension to '() to includebusiness process domain specific synta$ and semantics. his e$tension is termed the e#Business rocess (etamodel. he metamodel is oranied into the follo!in vie!s so thateach process model can be vie!ed from a number of perspectives.
The Business Operations Map (BOM) metamoe! the partitionin of business
processes into business areas and business cateories.
The Business Re"uirements Vie# (BRV) metamoe! the vie! of a business
process model that captures the re&uirements of a business collaboration protocol.
The Business Operationa! Vie# (BOV) metamoe!# the vie! of a business process
model that specifies the contract formation process for various types of commercialcontracts.
The $un%tiona! Ser&i%e Vie# ($SV) metamoe!# the vie! of a business process
model that specifies the electronic formation of commercial contracts usin an electronicmedium.
hese perspectives support an incremental model construction methodoloy and provide levels
of specification ranularity that are suitable for communicatin the model to businesspractitioners% business application interators and net!or" application solution providers.
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
11
8/9/2019 Ebx Ml Collaboration Modeling Met a Model
8/82
History
his document represents the concerted effort by the eb() Business rocess team to ensurethat the best of practice in system and process specification. he !or" stems from an effort
initiated in April 2000 !here several representatives of industry leaders met in eattle%3ashinton. 4urin this meetin 8 to 10 methodoloies !here analyed% and audited aainsteach other. he modelin elements of each methodoloy !ere identifies% classified andoranied into a metamodel !hich represented the nominal modelin elements re&uired tospecify an electronic commerce process and commercial collaboration. After several months ofintense evaluation and analysis% it !as determined that to construct a full metamodel andmethodoloy the !or" !ould re&uire more than one to t!o years to complete the !or". incethe Business Collaboration Frame!or" delevoped by 5difecs Commerce% 6nc represented acomplete unit of !or" and !as in use by the 7osettaet Consortium% eb() !ould use the BCFcontributed by 5difecs as the base and frame!or" for the eb() methodoloy% interate the!or" that had been accomplish to date and produce a specification in a matter of !ee"s in lieuof years. 3e o!e a debt of ratitude to all those !ho have participated in this !or" and to
5difecs Commerce for their contribution to this effort.
iv
12
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
13
8/9/2019 Ebx Ml Collaboration Modeling Met a Model
9/82
Preface
Business process models specify interoperable business processes that allo! businesspartners to collaboration. hese models are specified usin the 'nified (odelin )anuae*'()+ and the ,b-ect Constraint )anuae *,C)+. his document describes the '()
metamodel e$tension for specifyin business process models.
here are a number of reasons to use the '() and the ,C) to specify these models.
he '() provides a visual lanuae that eases the construction and interpretation of e#
business collaboration models.
he '() provides an e$tension mechanism so that domain specific% ob-ect#oriented
metamodels can be easily defined.
he ,C) is a prorammin lanuae independent method for e$pressin interity and
!ell#formedness constraints in metamodels and models.
he '() can be persisted usin (6 an () application. (odels are easy to share
and translate usin tools that provide (6 support.
Pur!ose of the Document
he purpose of this document is to define a business process metamodel. he metamodel isused to enforce the synta$ and semantics of business process models so that tools can be builtto construct% and applications can be built to e$ecute% compliant models.
Intended 5udience
he '() is a rich modelin lanuae that is e$pressive enouh to construct ob-ect models formany purposes% from many vie!points and !ithin many conte$ts. '() modelers !ho need to
specifically construct business process models must use this document to chec" the interityand compliance of their models. 6f an automated interity and compliance chec"er assists thesemodelers then that proram must chec" these models aainst the metamodel specified in thisdocument.
Prere%uisites
6t is assumed that the audience !ill be familiar !ith or have "no!lede of the follo!intechnoloies and techni&ues9
Business process modelin techni&ues and principles
he '() synta$ and semantics% the '() metamodel and the '() e$tension
mechanism
he ,C) synta$ and semantics
Sco!e of the Document
his document specifies a metamodel for constructin business process models.
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
14
8/9/2019 Ebx Ml Collaboration Modeling Met a Model
10/82
Sty#e Conventions
his document uses typoraphical and lanuae conventions to convey specific meanins.
Ty!o3ra!hica# Conventions
he use of a bold/italic fontindicates a '() or business process metamodel entity name.
6an3ua3e Conventions
his specification adopts the conventions e$pressed in the 65F:s17FC 211; % % % % % %% and in this document are to be interpreted as described in 7FC 211;.
5c/no'#ed3ements
ISO9 he follo!in terms are borro!ed from the 6, tandard specification for ,pen#546.
Business ,perational ie! *B,+
Functional ervice ie! *F+
Te!e%ommuni%ations Mana'ement $orum (TM$)9 he follo!in terms are derived from the(F documents.
Business ,perations (ap *B,(+. his is a eneraliation of the elecom ,perations
(ap *,(+ defined by the (F. A B,( is a super#cateory of an industry specificbusiness operations map such as the ,(.
he Fabricate% Assurance and Billin *FAB+ business areas used to create the top#level
nodes for services industries.
Supp! hain oun%i!.he follo!in terms are ta"en from the upply Chain Councildocuments.
Business ,perations (ap *B,(+. his is a eneraliation of the upply Chain
,perations 7eference *C,7+ model defined by the upply Chain Council. A B,( is asuper#cateory of a domain specific business operations map such as C,7.
he lan% ource% (a"e% 4eliver business areas are used to create top#level nodes for
4iscrete or Continuous oods upply Chains.
Eife%s ommer%e9 5difecs is administerin the creation of the Business CollaborationFrame!or" *BCF+ documents. he BCF is a collection of documents that prescribe the policy%architecture and specifications for e$ecutin business processes in electronic commerce% the6nternet for e#business.
1 8ttp9::.!etf.org
vi
15
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
16
17
8/9/2019 Ebx Ml Collaboration Modeling Met a Model
11/82
1. Introduction
Business partners collaborate by lin"in their plannin and e$ecution businessprocesses. his allo!s each partner to derive business efficiencies and to react &uic"erto customer demand. Business e$ecution processes span the end#to#end flo! of
products and information from consumer demand throuh product sourcin and bac" tofinal product consumption. 6n discrete or continuous oods industries% collaboration is aseries of source% ma"e and deliver business processes2e$ecuted by each businesspartner in the collaboration. ervice industries collaborate in a series of fulfill% assure andbill business processesDe$ecuted by each business partner in the collaboration.
Business partners implement business process lin"s throuh an interface of net!or"computer e#business services that enforce commercial tradin areements modeled ascollaborative e$chanes of business information% in areed se&uences and !ithinareed timeframes. A commercial tradin areement is modeled either as a Commercialransaction *C+ or a Business Collaboration rotocol *BC+. A C is are&uest/response e$chane of business information bet!een the initiator of thetransaction and the responder to the transaction re&uest. A BC is a choreoraph ofC:s !here either party to a tradin areement can initiate and respond to commercialtransactions until the terms of their areement are met. For e$ample% creatin apurchase order can be a C !here all the terms of an offer are accepted in a responseor it can be a BC !here the terms of an offer are accepted piecemeal in multipleresponses.
Business processes are partitioned% arraned and interrelated usin a Business,perations (ap *B,(+ to promote human understandin and to facilitate specificbusiness model confiurations *e.. build#to#order and build#to#stoc"+. he map andassociated process models can be incrementally constructed usin the (3 modelinmethodoloy.
rocess models are e$pressed usin the 'nified (odelin )anuae *'()+ and the
,b-ect Constraint )anuae *,C)+ both of !hich are standards maintained by the,b-ect (anaement roupE*,(+. he '() is a lanuae e$pressive enouh tospecify the structure and behavior of ob-ects that interact in any conceptual domain ofdiscourse. A process model% ho!ever% is a specification of the structure and behavior ofob-ects interactin business partner interfaces% a specialied domain of discourse. he'() metamodel *the model that defines the '() modelin lanuae+ is e$tended toinclude domain specific synta$ and semantics usin e$tension mechanisms "no! asstereotyping. A business process metamodel is thus defined as an e$tension of the '()metamodel by e$tendin the '() stereotype synta$ and semantics !ith the synta$ andsemantics of the business process domain. rocess models are then constructed usinthe synta$ of the metamodel. ools and applications that support the synta$ andsemantics of the business process metamodel !ill be able to support the construction
and e$ecution of business processes that e$ecute on the eb() compliant transports.
his document is a precise definition of the '() metamodel e$tension that facilitates thee$pression of a business processes as an ob-ect#oriented model. his e$tendedmetamodel is termed the e#Business rocess (etamodel. he metamodel is oranied
2 Taen from t8e Supply /8a!n +perat!ons Reference ;S/+R< model found at8ttp9::.supply-c8a!n.org.3 Taen from t8e Telecom +perat!ons Map ;T+M< found at8ttp9::.tmforum.org.$ 8ttp9::.omg.org
1
18
219
220
221
222
223224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
19
20
21
22
23
http://www.supply-chain.org/http://www.tmforum.org/http://www.supply-chain.org/http://www.tmforum.org/8/9/2019 Ebx Ml Collaboration Modeling Met a Model
12/82
into the follo!in vie!s so that each process model can be vie!ed from a number ofperspectives.
The Business Operations Map (BOM) metamoe! the partitionin of
business processes into business areas and business cateories.
The Business Re"uirements Vie# (BRV) metamoe! the vie! of a businessprocess model that captures the 'se Case scenarios% inputs% outputs% constraintsand system boundaries for commercial transactions and their interrelationships.
The Business Operationa! Vie# (BOV) metamoe!# the vie! of a business
process model that captures the semantics of business information entities andtheir flo! of e$chane bet!een roles as they perform business activities.
The $un%tiona! Ser&i%e Vie# ($SV) metamoe!# the vie! of a business
process model that specifies the net!or" component services and aents andtheir messae *data+ e$chane as interactions necessary to e$ecute and validatea business process.
hese perspectives support an incremental model construction methodoloy andprovide levels of specification ranularity that are suitable for communicatin the modelto business practitioners% business application interators and net!or" applicationsolution providers.
he B7% B, and F of a process model are net!or" communications protocolneutral.
.
2
24
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
25
8/9/2019 Ebx Ml Collaboration Modeling Met a Model
13/82
2. The Business Operations Map Metamodel
he Business ,perations (ap *B,(+ of a business process model specifies the 'seCase scenarios% input and output triers% constraints and system boundaries forbusiness areas% business processes% business collaboration protocols% commercial
transactions and their interrelationships. Business process are partitioned% arraned andinterrelated usin a B,( to promote human understandin and to facilitate specificbusiness model confiurations *e.. build#to#order and build#to#stoc"+.
his section specifies the abstract synta$ and semantics of a B,( model and modelmanaement pac"aes. he abstract synta$ of models is defined usin stereotypes andtaed values. he semantics of models are specified usin the truth semantics of !ellformed#formula e$pressed !ith ,C) e$pressions and !ith natural lanuae.
2.1 Model Abstract Syntax
2.1.1Stereotypes and Tagged Values
Fiure 1 specifies the modelin elements% and their interrelationships% thatare used to e$press the structure and behavior of ob-ects in a B,(model. 5ach element and interrelationship permitted in a B,( is definedin the metamodel specified in this section of the document.
D
26
287
288
289
290
291292
293
294
295
296
297
298
299
300301
302
303
27
8/9/2019 Ebx Ml Collaboration Modeling Met a Model
14/82
Business Operations Map Metamoe!
Businessas"base5lement Actiontate
timeoerform 9 ime5$pression
GGstereotypeHH
1
Icollaborates3ith
1
ransition
base5lement 7elationship
trier5vent 9 trin
transitionConditions 9 trin
concurrentransition 9 trin
GGstereotypeHH
BusinessrocessActivity(odel
base5lement Activityraph
GGstereotypeHH
Businessrocess
base5leme nt 'seCase
preconditions 9 trin
beins3hen 9 trin
definition 9 trin
ends3hen 9 trin
e$ceptions 9 trin
postconditions 9 trin
traceabili ty 9 trin
GGstereotypeHH
1
1
1
1
+i3ure 1. B" 5stract Syntax
BusinessProcess5
A business process is a 'se Case that is used to atherre&uirements about business processes. 6nputs to the businessprocess must be specified in the preconditions and outputs fromthe business process must be specified in the post#conditions.
Ta33ed &a#ues7
preconditions. reconditions are constraints that must besatisfied startin the 'se Case.
beginsWhen. 4escribe the initial event from the actor thatstarts a 'se Case.
definition. A set of simple sentences that state the actionsperformed as part of the 'se Case. 6ncludereferences to 'se Cases at e$tension points.
endsWhen. 4escribe the condition or event that causesnormal completion of the 'se Case.
5se cases s8ould cons!der t8e !nclus!on of measure= metr!c and meter parameters for abus!ness process. Measures are *uant!>able propert!es? a metr!c an express!on of someperformance calculat!on and a meter !s a compar!son of t8e metr!c to a benc8mar.
E
28
304
305
307
308
309
310
311
312
313
314
315
316
317
318
319
320
321
322
29
30
31
32
8/9/2019 Ebx Ml Collaboration Modeling Met a Model
15/82
exceptions. )ist all e$ception conditions that !ill cause the'se Case to terminate before its normalcompletion.
postconditions. ost#conditions are constraints that must besatisfied endin the 'se Case.
traceability. An e$plicit list of re&uirements% identified bycateory% that are either partially or completelysatisfied by this used case.
BusinessProcessActivityModel
A business process activity model specifies the behavioral aspectsof a business process. he model specifies a flo! of controlbet!een tas"s.
BusinessInterfaceTask
A business interface tas" is a tas" that is performed by one
business partner in collaboration !ith another business partnerperformin another business interface tas". A business process isdecomposed into business tas"s and business interface tas"s.
Ta33ed &a#ues7
timeToPerform. A tas" is !or" that is performed !ith respect totime. here may be a specific time !ithin !hichthe tas" must be performed.
5ssociations7
collaboratesWith. A business interface tas" is performed incollaboration !ith another business interface
tas". For e$amples% a tas" is performed in collaboration !ith a tas".
Transition
A transition is a directed relationship bet!een a client *source+ usecase and a supplier *taret+ use case. his relationship specifies aprocess transition to a taret business process use case trieredby the completion of a source business process *a state in !hichall the post#conditions of the use case are satisfied+ or trieredby a activity state transition !ithin the client *source+ use case.
he transition occurs only !hen transition conditions are satisfied.
Ta33ed &a#ues7
triggerEvent. he activity state transition !ithin the client*source+ use case definition activity raph thattriers the transition to the supplier *taret+ usecase.
transitionConditions. ransitionConditions are constraints thatmust be true in order for the transition to the
J
33
323
324
325
326
327
328
329
330
331
332
333
334
335
336
337
338
339
340
341
342
343
344
345
346
347
348
349
350
351
352
353
354
355
356
357
358
359
360
361
362
363
364
34
8/9/2019 Ebx Ml Collaboration Modeling Met a Model
16/82
supplier *taret+ use case to occur. heseconditions must be testable values on thebusiness data entities visible to the client*source+ use case and its definition activityraph.
concurrentTransition . A fla indicatin that the transition occurs
on an internal activity transition !ithin the client*source+ activity raph. Both the client *source+and supplier *taret+ !ill continue concurrently.
5ssociations7
SourceUseCaseA transition describes the trier event andconditions occurrin in the client *source+ usecase.
TargetUseCasehe supplier *taret+ use case is e$ecuted !henthe trier event and transition conditions occur!ithin the client *source+ use case.
2.1.2ell!for"edness #uleshe follo!in !ell#formedness rules apply to the B,( metamodel.
K1L he collaboratesWithassociation must be naviable from the clientuse case to the supplier use case only.
K2L Business process activity models must have one initial state and atleast one end state.
2.2 Model Semantics
he semantics of each element of the B,( metamodel is defined in this section.
Fiure 2 illustrates the interrelationships bet!een the B,( modelin elements.
Business6nterf aceas"BusinessrocessActiv ity (odel
1..M1 1..M1
Businessrocess
1
1
1
1
ransition1 0..MIsource1 0..M
Itaret 0..M1 0..M1
+i3ure 2. B" I##ustration
A business process is a se&uence of business tas"s performed by one businesspartner alone% and business interface tas"s performed t!o or more businesspartners. A business process activity model should only contain activity statesthat are either Business 6nterface as" specifications or that are interpreted asbusiness tas"s.
N
35
365
366
367
368
369
370
371
372
373
374
375
376
377
378
379
380
381
382
383
384
385
386
387
388
389
390
391
392
393
394
395
396
36
8/9/2019 Ebx Ml Collaboration Modeling Met a Model
17/82
5ach tas" can be further decomposed into activities. Business process can bedecomposed into sub#processes usin the OincludePassociation stereotypedefined in the '().
A transition relationship specifies a chane in state of a business process that istriered by the completion of some part of the business process. A transition
relates a source business process and a taret business process. he directionof the transition is from the source to the taret.
2.3 Model Management Abstract Syntax
he B,( model manaement oranies business process 'se Cases andbusiness process activity models into a frame!or" of business areas andprocess areas. hese modelin elements are oranied as loical% business areaand sub#process cateories arraned in a frame!or" for understandin theirinterrelationships. he frame!or" is termed a Business ,perations (ap *B,(+.
2.$.1Stereotypes and Tagged Values
Fiure D sho!s the metamodel for manain the B,( model. hemodelin elements used to manae and oranie these threespecifications are defined in this section.
Business,perations(ap
base5lement (odel
industryement 9 trin
GGstereotypeHH
BusinessArea rocessArea
BusinessCategory
base5lement ac"ae
cateory chema 9 trin
cateory 9 trin
GGstereotypeHH
+i3ure $. B" "ode# "ana3ement 5stract Syntax
he follo!in stereotypes and taed values are contained in the B,(manaement metamodel.
Business%perationsMap
A Business ,perations (ap is a frame!or" for understandinbusiness area sub#process interrelationships. his frame!or" istermed a Business ,perations (ap *B,(+.
BusinessArea
A business area is a cateory of decomposable business processareas. A business area collates business processes areas.
Q
37
397
398
399
400
401
402
403
404
405
406
407
408
409
410
411
412
413
414
415
416
417
418
419
420
421
422
423
424
38
8/9/2019 Ebx Ml Collaboration Modeling Met a Model
18/82
8/9/2019 Ebx Ml Collaboration Modeling Met a Model
19/82
A business operations map comprises business areas. he upply ChainCouncilNdefines plan% source% ma"e and deliver business areas in their upplyChain ,perations 7eference *C,7+ model. he model describes businessprocesses in the 4iscrete and Continuous oods upply Chain. heelecommunications (anaement ForumQdefines fulfill% assure and bill businessareas in their elecom ,perations (ap *,(+. he map describes business
processes in the ervices industry.
Business areas comprise process areas. A process area is a se&uence ofbusiness processes that implements a particular business model. Business areassuch as are t!odifferent business models that use many of the same business processes.
" 8ttp9::.supply-c8a!n.org.# 8ttp9::.tmforum.org.
;
41
451
452
453
454
455
456
457
458
459
460
461
42
43
44
http://www.supply-chain.org/http://www.tmforum.org/http://www.supply-chain.org/http://www.tmforum.org/8/9/2019 Ebx Ml Collaboration Modeling Met a Model
20/82
3. The Business Requirements View Metamodel
he Business 7e&uirements ie! *B7+ of a process model specifies the 'se Casescenarios% input and output triers% constraints and system boundaries for Commercialransactions *C:s+% Business Collaboration rotocols *BC:s+ and their
interrelationships.
his section specifies the abstract synta$ and semantics of the B7 of a C and BCmodel and model manaement pac"aes. he abstract synta$ of models is specifiedusin stereotypes and taed values. he semantics of models are specified usin thetruth semantics of !ellformed#formula e$pressed !ith ,C) e$pressions and !ithnatural lanuae.
3.1 Model Abstract Syntax
$.1.1Stereotypes and Tagged Values
Fiure J specifies the modelin elements and their interrelationships that
are used to e$press the structure and behavior of ob-ects in the B7 of aC and BC model. 5ach element and interrelationship permitted in aB7 is defined in the metamodel specified in this section of thedocument.
Business Re"uirements Vie# Metamoe!
Commercialransaction'seCase
re&uestinBusinessFunction 9 trin
respondinBusinessFunction 9 trin
artnerype
base5lement Cl ass
GGstereotypeHH
BusinessCollaboration
base5lement Collaborationpreconditions 9 trin
beins3hen 9 trin
definition 9 trin
ends3hen 9 trin
e$ceptions 9 trin
postconditions 9 trin
GGstereotypeHH
7ealie
base5lement 7elationship
GGstereotypeHH
1
0..n
Icollaboration
1
0..n
BusinessCollaborationUseCase
base5lement 'seCase
preconditions 9 trin
beins3hen 9 trin
definition 9 trin
ends3hen 9 trin
e$ceptions 9 trin
postconditions 9 trin
raceability 9 trin
record(etrics 9 Bool ean
GGstereotypeHH
0..n
1
Irealiation
0..n
Ibase1
+i3ure *. BR& 5stract Syntax
10
45
462
463
464
465
466
467
468
469
470
471
472
473
474
475476
477
478
479
480
46
8/9/2019 Ebx Ml Collaboration Modeling Met a Model
21/82
Business&olla'orationProtocol(se&as
A business collaboration protocol 'se Case is used to atherre&uirements for e#business collaboration protocol specifications.
Business&olla'oration
A business collaboration model specifies the input and outputrelationships bet!een business collaboration 'se Cases and
Aents. Aents provide input triers to 'se Cases and businesscollaboration 'se Cases can provide input triers and outputtriers to and from other business collaboration 'se Cases.
A business collaboration model captures business informationconstraints imposed by a specific partner type collaboration. Fore$ample% sendin a business document to a ' overnmentaency re&uires a tandard 6ndustry Classification *6C+ code tobe included !ith the business information.
Ta33ed &a#ues7preconditions. Conditions that must be true before startin the
'se Case.
beginsWhen. 4escribe the initial event from the actor thatstarts a 'se Case.
definition. A set of simple sentences that state the actionsperformed as part of the 'se Case. 6ncludereferences to 'se Cases at e$tension points.
endsWhen. 4escribe the condition or event that causesnormal completion of the 'se Case.
exceptions. )ist all e$ception conditions that !ill cause the'se Case to terminate before its normalcompletion.
postconditions. Conditions that must be true before endin the'se Case.
Business&olla'oration(se&ase
A business collaboration use case is an abstraction for a businesscollaboration protocol 'se Case and a commercial transaction'se Case. he abstraction permits the reuse of the businesscollaboration realiation relationship.
A completed use case assumes that some one of be created either as a service performed of aproduct created. Four appropriate classes of measure that can beapplied to use case performance9 &uantity measure% &ualitymeasure% time of performance measure and resource usae orconsumption measure. 5ach use case should have an identifiedset of appropriate measures. As a minimum% at least one &uantitymeasure should be employed.
11
47
481
482
483
484
485
486
487
488
489
490
491
492
493
494
495
496
497
498
499
500
501
502
503
504
505
506
507
508
509
510
511
512
513
514
515
516
517
518
519
520
521
522
48
8/9/2019 Ebx Ml Collaboration Modeling Met a Model
22/82
Ta33ed &a#ues7
preconditions. Conditions that must be true before startin the'se Case.
beginsWhen. 4escribe the initial event from the actor thatstarts a 'se Case.
definition. A set of simple sentences that state the actionsperformed as part of the 'se Case. 6ncludereferences to 'se Cases at e$tension points.
endsWhen. 4escribe the condition or event that causesnormal completion of the 'se Case.
exceptions. )ist all e$ception conditions that !ill cause the'se Case to terminate before its normalcompletion.
postconditions. Conditions that must be true before endin the'se Case.
traceability. An e$plicit list of re&uirements% identified by
cateory% that are either partially or completelysatisfied by this used case.
5ssociations7
realization. A business collaboration is a realiation of abusiness collaboration use case.
&o""ercialTransaction(se&ase
A commercial transaction 'se Case is used to atherre&uirements for commercial transaction specifications.
Ta33ed &a#ues7
reuestingBusiness!unction. he business function that isimplemented by the re&uestin business partner!ho is performin a role !ith respect to the usecase e.. rocurement.
respondingBusiness!unction. he business function that isimplemented by the respondin businesspartner !ho is performin a role !ith respect tothe use case e.. Fulfillment.
#eali)e
A relationship bet!een a business collaboration 'se Case and therealiation of a 'se Case.
5ssociations7
base. he base 'se Case for the collaboration in therealiation relationship.
12
49
523
524
525
526
527
528
529
530
531
532
533
534
535
536
537
538
539
540
541
542
543
544
545
546
547
548
549
550
551
552
553
554
555
556
557
558
559
560
561
562
563
50
8/9/2019 Ebx Ml Collaboration Modeling Met a Model
23/82
collaboration. he collaboration realiation for the base 'seCase.
PartnerType
A partner type is an actor in a business collaboration 'se Case.
artner types are (anufacturer% 4istributor% 7etailer% 5nd 'ser%Carrier and Financier8.
%T8!s l!st of partner types s8ould not be cons!dered complete. @ oe)er !t appears tosuBc!ent for Supply /8a!n 4ndustr!es. T8ere needs to be some eCort !nto ser)!ce or!ented!ndustr!es. !.e. - Telecom
1D
51
564
565
566
567
568
569
570
52
53
54
55
8/9/2019 Ebx Ml Collaboration Modeling Met a Model
24/82
5conomic (odelin 5lements
BusinessEntity
base5lement F Class
GGstereotypeHH
Business 5vent
base5lement F Class
GGstereotypeHH
Areement
base5lement F Class
Areementype 9 2trin
GGstereotypeHH
5conomic Contract
base5lement F Class
initiateCondition 9 2trin
terminationCondition 9 2trin
GGstereotypeHH
5conomic 5vent
base5lement F Class
measurement
GGstereotypeHH
4uality
base5lement relationship
GGstereotypeHH
Commitment
base5lement F Class
measure 9 2trin
due 9 4ate
GGstereotypeHH
7eprocityGHH base5lement relationship
GGstereotypeHH
5conomi c 7esourcebase5lement Class
measurement
location
GGstereotypeHH
5conomic 7esource
4efinition
base5lement F Class
GGstereotypeHHclassifies
classifies
+i3ure ,. Economic E#ements 5stract Syntax
1E
56
571
572
57
8/9/2019 Ebx Ml Collaboration Modeling Met a Model
25/82
8/9/2019 Ebx Ml Collaboration Modeling Met a Model
26/82
elements such as a date% event or systemmetric.
5ssociations7
establishes. An economic contract establishes t!o or morecommitments.
*cono"ic &o""it"ent
An economic commitmentis an obliation to perform an economicevent *that is% transfer o!nership of a specified &uantity of aspecified economic resource type+ at some future point in time.,rder line items are e$amples of commitments.
Ta33ed &a#ues7
measure. he of measurement of an economic resources
of the specified type to be transferred.due. he condition that determines !hen the transfer
of o!nership is promised to occur. his is an,C) constraint and may be defined by elementssuch as a date% event or system metrics.
5ssociations7
fulfills. Commitments may be fulfilled by economicevents.
from. A commitment is an obliation from one partnertype.
to. A commitment is an obliation to another partner type.
reciprocal. A commitment al!ays has reciprocityrelationships !ith one or more othercommitments.
specifies. Commitments specify economic resource types.
#eciprocity
7eciprocity is a mandatory relationship bet!een t!o or morecommitments. Commercial contracts re&uire reciprocalcommitments% called .
*cono"ic#esourceType
An economic resource typeis the abstract classification ordefinition of an 5conomic 7esource. For e$ample% in an 57system% 6tem(aster or roduct(aster !ould represent the5conomic 7esource ype that abstractly defines an 6nventory 6temor roduct. Forms of payment are also defined by economicresource types% e.. currency.
1N
60
614
615
616
617
618
619
620
621
622
623
624
625
626
627
628
629
630
631
632
633
634
635
636
637638
639
640
641
642
643
644
645
646
647
648
649
650
651
652
653
61
8/9/2019 Ebx Ml Collaboration Modeling Met a Model
27/82
5ssociations7
classifies. 5conomic resource types classify economicresources.
classifies. 5conomic 7esource ypes may have recursiverelationships% so that for e$ample broad
classifications li"e RproductR could roup smallerclassifications li"e Rproduct familyR% !hich in turncould have as members the specific RproductmastersR !ith =' numbers..
specifies. Commitments specify economic resource types.
*cono"ic#esource
An economic resourceis a &uantity of somethin of value that isunder the control of an enterprise% !hich is transferred from onepartner type to another in economic events. 5$amples are cash%inventory% labor service and machine service.
Ta33ed &a#ues7
measurement. he number and unit of the economic resource.'nit may be a unit of measure for products% aunit of time for services% or a currency for cash.
location" he location !here the economic resourcecurrently resides or is available.
5ssociations7
classifies. 5conomic resources are classified by economicresource types.
resource!lo#. 5conomic resources flo! from one partner typeto another via economic events.
Business*vent
A business eventis a sinificant chane in the state of one ormore entities !ithin a business% e.. the ta"in of an order or aprice chane.
*cono"ic*vent
An economic eventis the transfer of control of an 5conomic7esource from one partner type to another partner type.
5$amples !ould include sale% cash#payment% shipment% andlease.
Ta33ed &a#ues7
measurement. he number and unit of the economic resource.that is bein transferred.
1Q
62
654
655
656
657
658
659660
661
662
663
664
665
666
667
668
669
670
671
672
673
674
675
676
677
678679
680
681
682
683
684
685
686
687688
689
690
691
692
63
8/9/2019 Ebx Ml Collaboration Modeling Met a Model
28/82
5ssociations7
duality. 4ualityis a relationship bet!een 5conomic5vents% !here one is the leal or economicconsideration of the other. 5$amples include apayment for a product or service. 6f oneeconomic event occurs% but its dual or e$pected
consideration has not occurred% the ivinpartner type has an imputed claim aainst theta"in partner type for the value of the economicresources transferred.
fulfills. An economic event may fulfill a priorcommitment.
participation. At least t!o partner types must participate in aneconomic event% one to ive the economicresources% the other to ta"e them.
resource!lo#. 5conomic resources flo! from one partner typeto another via economic events.
+uality
4ualityis a relationship bet!een 5conomic 5vents% !here one isthe leal or economic consideration of the other. 5$amples includea payment for a product or service. 4uality relationships occurbet!een t!o or more economic events.
.
$.1.2ell!for"edness #ules
he follo!in !ell#formedness rules apply to the business re&uirementsvie! metamodel pac"ae.
K1L All associations bet!een partner types and business 'se Cases mustspecify the partner type as the source of the association and thesource association end must have a name that is the role of thepartner type !ith respect to the commercial transaction 'se Caseto !hich it interfaces.
K2L A commercial transaction 'se Case may not be used in an Oe$tendPassociation.
KDL Commercial transaction 'se Cases may not be the source of anOincludeP association.
KEL Compliant models must have all 'se Cases stereotyped asOBusinessCollaborationrotocol'seCaseP% to at least be eitherthe source of an OincludeP association or the taret of anOe$tendP association.
KJL he name of the association bet!een a partner type and a 'se Casemust be the name of input/output triers of the 'se Case.
18
64
693
694
695
696
697
698
699
700
701
702
703
704
705
706
707
708
709
710
711
712
713
714
715
716
717
718
719
720
721
722
723
724
725
726
727
728
729
730
731
732
733
734
65
8/9/2019 Ebx Ml Collaboration Modeling Met a Model
29/82
KNL All partner types in the model *classes stereotyped OartnerypeP+must be defined as partner types e.. (anufacturer% 4istributor%7etailer% Carrier% Financier and 5nd 'ser.
KQL 5conomic contracts must have at least t!o partner types asparticipants.
K8L 5ach economic contract must establish at least t!o commitments.
K;L 5ach commitment must have a reciprocity relationship !ith at leastone other commitment.
K10L 6f an economic event fulfills a prior commitment% the economicresource type of the economic resource transferred by theeconomic event must be compatible to the economic resourcetype promised in the commitment. means either thesame type or a subtype.of the type of the commitment.
3.2 Model Semantics
he semantics of each element of the B7 metamodel is defined in this section.Fiure Q illustrates the interrelationships bet!een the B7 modelin elements.
1;
66
735
736
737
738
739
740
741
742
743
744
745
746
747
748
749
750
67
8/9/2019 Ebx Ml Collaboration Modeling Met a Model
30/82
resource!lo#
Commercialransaction'seCase
GGstereotypeHH
Business Re"uirements Vie# Semanti%s
Businessas"
*from Business ,perations (ap (etamodel +
5conomic Contract
GGstereotypeHH
BusinessCollaborationUseCase
mapso
1..n
artnerype
1..n0..n 1..n
Iparticipates
0..n
Areem ent
GGstereotypeHH
2..M2..M
Commitment
GGstereotypeHH
12..M
12..M
establish
reprocity
BusinessCollaboration
11
Irealiation
11
Irole
1..n1..n
overns
0..M0..M
forms
5conomic 7esource 4efiniti on
GGstereotypeHH
classifies
0..M0..M
reserves
5conomic 5vent
GGstereotypeHH
0..M0..M
fulfills
0..M
1
0..M
1
results$n
1..M0..M
Iinitiator
1..M
duality
Iterminator
0..M5conomic 7esource
GGstereotypeHH
classifies
+i3ure . BR& I##ustration
A business collaboration use case maps to t!o business interface tas"s specifiedin a Business ,perations (ap. ,ne tas" is the oriinator of a commercialcontract and the other is a responder to the commercial contract. he businesscollaboration 'se Case can either be a business collaboration protocolspecification or a commercial transaction specification.
A commercial transaction specifies an initiatin business partner startin thecontract formation process by communicatin a business document re&uest to arespondin business partner. A respondin partner accepts the conditions of thecommercial contract in ero or more returnin business sinals *e.. anac"no!ledement of receipt+ follo!ed by an optional respondin businessdocument *e.. an ac"no!ledement of acceptance+;.
A business collaboration protocol choreoraphs commercial transactions !henthe contract formation process re&uires a number of re&uestin and respondinbusiness document e$chanes. For e$ample the creation of a purchase orderre&uest can be specified as a business collaboration protocol that choreoraphs
& (us!ness /ollaborat!on 0rotocol D ; Re*uest S!gnalE= ResponseF < G
20
68
751
752
753
754
755
756
757
758
759
760
761
762
763
764
765
766
767
69
70
8/9/2019 Ebx Ml Collaboration Modeling Met a Model
31/82
both a purchase order and notification of acceptance commercial transactions. 6nthese instances the respondin business partner does not accept the entirepurchase order offer in a response to the initial commercial transaction re&uest.6nstead the partner communicates line item acceptance of the purchase orderusin many notifications of acceptance over an areed period. he contract isformed !hen the initiatin business partner is a able to reconcile all the
notifications of acceptance !ith the oriinal purchase order re&uest.
A partner type performs a specific role in business collaboration. he partnerroles are not employee or oraniation titles.
A businessre&uirements use case should capture both the re&uirements forformin commercial contracts and the re&uirements for auditin the formation ofcommercial contracts. A commercial transaction models the start and end of acommercial contract formation process. his is not al!ays sufficient to capturethe start and end of an auditable commercial formation process. For e$ample% anoffer and acceptance contract is formed once an oriinatin partner receives theareed . he fact that the sendin partner does notreceive a verification of proper receipt for an acceptance business document is
immaterial to the formation of the contract. 6t may be important% ho!ever% if thesendin partner !ishes to retain an audit trail of the process for a receivin partyto verify proper receipt of the business document.
5conomic contracts carry t!o or more reciprocal commitments% !hich arepromises that future economic events !ill occur% specifyin particular economicresource types. Commercial contracts re&uire reciprocal commitments% called. ubse&uently% the promised economic events may fulfill thecommitments% transferrin o!nership of actual economic resources of thecommitted types from one partner type to another. For e$ample% a purchaseorder is an economic contract% typically committin one partner type to deliver aproduct or service of a specified type% and the other partner type to pay for it.he delivery of the product or service miht be the first economic event *fulfillinone commitment+ and obliatin *by the duality relationship+ the reciprocalpartner type to pay the committed price.
3.3 Model Management Abstract Syntax
he B7 model can be a business collaboration protocol 'se Case model or acommercial transaction 'se Case model% as !ell as business collaborations.
$.$.1Stereotypes and Tagged Values
Fiure 8 sho!s the metamodel for manain the B7 model. hemodelin elements used to manae and oranie these modelinelements are defined in this section.
21
71
768
769
770
771
772
773
774
775
776
777
778
779
780
781
782
783
784
785786
787
788
789
790
791
792
793
794
795
796
797
798
799
800
801
802
803
804
805
72
8/9/2019 Ebx Ml Collaboration Modeling Met a Model
32/82
Business Re"uirements Vie# Moe! Mana'ement
Business7e&uirementsie!
base5lement (odel
GGstereotypeHH
Commercialransaction'seCase
re&uestinBusinessFunction 9 trin
respondinBusinessFunction 9 trin
GGstereotypeHH
BusinessCollaboration
base5lement Collaboration
preconditions 9 trin
beins3hen 9 trin
definition 9 trin
ends3hen 9 trin
e$ceptions 9 trin
postconditions 9 trin
GGstereotypeHH
+i3ure 8. BR& "ode# "ana3ement 5stract Syntax
he follo!in stereotypes and taed values are contained in the B7model manaement metamodel.
Business#e,uire"entsVie-
he Business 7e&uirements ie! specifies the re&uirements forone or more business collaborations.
$.$.2ell!for"edness #ules
he follo!in !ell#formedness rules apply to the business re&uirementsvie! metamodel pac"ae.
K1L A business re&uirements vie! model contains one or moreCommercial ransaction 'se Case.
K2L 5ach Commercial ransaction 'se Case is realied by a BusinessCollaboration.
3.4 Model Management Semantics
he semantics of each element of the B7 model manaement metamodel isdefined in this section.
Fiure ; illustrates the interrelationships bet!een the B7 model manaementand model elements.
22
73
806
807
808
809
810
811
812
813
814
815
816
817
818
819
820
821822
823
824
74
8/9/2019 Ebx Ml Collaboration Modeling Met a Model
33/82
BusinessCollaboration
Business7e&uirementsie!
0..M0..M
BusinessCollaborationUseCase
11
+i3ure (. BR& "ode# "ana3ement I##ustration
A business re&uirements vie! is a model of the re&uirements of a sinlebusiness collaboration 'se Case and its realiations as business collaborations.
2D
75
825
826
827
828
76
8/9/2019 Ebx Ml Collaboration Modeling Met a Model
34/82
4. The Business Operational View Metamodel
he B, of a process model specifies the flo! of business information10bet!eenbusiness roles as they perform business activities. he business process specificationcan be formal an in the formation of offer/acceptance commercial contracts as !ell as
informal as in the announcement of ne! products.
his section specifies the abstract synta$ and semantics of the B, of a C and BCmodel and model manaement pac"aes. he abstract synta$ of models is specifiedusin stereotypes and taed values. he semantics of models are specified usin thetruth semantics of !ellformed#formula e$pressed !ith ,C) e$pressions and !ithnatural lanuae.
4.1 Model Abstract Syntax
he synta$ of e#business collaboration models comprises stereotypes andtaed values. he semantics of e#business collaboration models are specifiedusin the truth semantics of !ellformed#formula *specified as ,C) e$pressions+
and !ith lanuae.
.1.1Stereotypes and Tagged Values
Fiure 10 specifies the modelin elements and their interrelationships thatare used to e$press the structure and behavior of ob-ects in the B, of aC and BC model. 5ach element and interrelationship permitted in aB, is defined in the metamodel specified in this section of thedocument.
1' T8e use t8e term Hbus!ness !nformat!onI !s !ntens!onal as t8e (RV of a bus!ness processmust capture t8e semant!cs of bus!ness !nformat!on exc8anged and not t8e data format orstorage format of t8e !nformat!on t8at !s spec!>ed !n t8e SV.
2E
77
829
830
831
832
833
834
835
836
837
838
839
840
841
842
843
844
845
846
847
848
849
850
78
79
80
81
8/9/2019 Ebx Ml Collaboration Modeling Met a Model
35/82
5mployee7ole,raniational7ole
tructured4ocument
Commerc ialransactionActiv ity
base5lement Actiontate
timeoerform 9 ime5$pression
isConcurrent 9 Boolean
GGstereotypeHH
6nformation5ntity
base5lement Class
isConf idential 9 Boolean
isamperroof 9 Boolean
isAuthenticated 9 Boolean
GGstereotypeHH
7e&uestinBusinessActivity
retry Count 9 8atural8umber
is8on7epudiation,f 7eceipt7e&uired 9 Boolean
GGstereotypeHH7espondinBusinessActivity
is6ntelliibleChec"7e&uired 9 Boolean
GGstereotypeHH
Business%ctivity
base5lement Actiontate
isAuthoriation7e&uired 9 Boolean
is8on7epudiation7e&uired 9 Boolean
timeoerform 9 ime5$pression
timeoAc"no!lede7eceipt 9 ime5$pression
timeoAc"no!ledeAcceptance 9 ime5$pression
4ocument5nv elope
base5lement Class
GGstereotypeHHBusiness&ocument
base5lement Class
GGstereotypeHH
'nstructured4ocument
body 9 datay pe trin
Commercialransaction
base5lement Activ ityraph
isecureransport7e&uired 9 Boolean
GGstereotypeHH
1
Itransaction
1
Business)o!!a*oration+roto%o!
base5lement Activ ityraph
GGstereotypeHH
Businessartner
base5lement Class
GGstereotypeHH
2..M
Functional7ole
base5lement Class
GGstereotypeHH
1..M2..M 1..M
Ipartner Irole
+i3ure 14.B& 5stract Syntax
BusinessActivity11
he business activity is the state of a business action e$ecuted bya partner role durin commercial transaction. his is an abstractclass that is not a stereotype.
Ta33ed &a#ues7
$s%uthorization'euired. 6f a partner role needs authoriation tore&uest a business action or to respond to abusiness action then the sendin partner rolemust sin the business document e$chanedand the receivin partner role must validate this
business control and approve the authorier. Arespondin partner must sinal an authoriatione$ception if the sendin partner role is notauthoried to perform the business activity. Asendin partner must send notification of failed
11A bus!ness act!)!ty !s der!)ed from t8e 5MJ Act!on State model element. T8!s enablesmult!ple ex!t and entry trans!t!ons for t8e re*uest!ng and respond!ng act!)!ty states. A bus!nessact!)!ty !s notder!)ed from t8e 5MJ /all State model element t8at typ!cally models t8ebe8a)!or of an operat!on. An Act!)!ty state does not 8a)e an !nternal trans!t!on= ex!t act!on or ado act!)!ty. T8e entry act!on of a /all State !s a s!ngle call act!on.
2J
82
851
852
853
854
855
856
857
858
859
860
861
862
863
864
865
866
867
83
84
85
86
87
88
8/9/2019 Ebx Ml Collaboration Modeling Met a Model
36/82
authoriation if a respondin partner is notauthoried to perform the respondin businessactivity.
is(on'epudiation'euired"6f non#repudiation of oriin andcontent is re&uired then the business activitymust store the business document in its oriinal
form for the duration mutually areed to in atradin partner areement. A respondin partnermust sinal a business control e$ception if thesendin partner role has not properly deliveredtheir business document. A re&uestin partnermust send notification of failed business controlif a respondin partner has not properlydelivered their business document.
his property provides the follo!in auditcontrols9Verif senin' ro!e ientit (authenti%ate)1,erify the identity of the sendin role *employee
or oraniation+. For e$ample% a driver:s licenseor passport document !ith a picture is used toverify an individual:s identity by comparin theindividual aainst the picture.Verif %ontent inte'rit1- erify the interityof the oriinal content sent from a partner rolei.e. chec" that the content has not been alteredby a Drdparty !hile the content !as e$chanedbet!een partners.
timeToPerform. Both partners aree to perform a commercialtransaction !ithin a specific duration. Arespondin partner must e$it the transaction ifthey are not able to respond to a business
document re&uest !ithin the areed timeoutperiod. A sendin partner must retry acommercial transaction if necessary or mustsend notification of failed business control*possibly revo"in a contractual offer+ if arespondin partner does not deliver theirbusiness document !ithin the areed timeperiod. he time to perform is the duration fromthe time a business document re&uest is sent bya re&uestin partner role until the time arespondin business document is by the re&uestin partner role. Bothpartners aree that the business sinal
document or business action documentspecified as the document to return !ithin thetime to perform is the
12T8e (/ spec!>es d!g!tal s!gnatures for partner-to-partner non-repud!at!on of or!g!n andcontent.13T8e (/ spec!>es M7 or SA-1 message d!gest algor!t8ms and asymmetr!c encrypt!on topro)!de content !ntegr!ty.1$H0roperly rece!)edI !s legally de>ned !n a trad!ng partner agreement. Refer to t8e H/reateTrad!ng 0artner AgreementI commerc!al transact!on spec!>cat!on !n t8e (/.1T8!s !s not a bus!ness acceptance document.
2N
89
868
869
870
871
872
873
874
875
876
877
878
879
880
881
882
883
884
885
886
887888
889
890
891
892
893
894
895
896
897
898
899
900901
902
903
904
905
906
907
908
909
910
911
912
913
914
915
90
91
92
93
94
95
96
97
8/9/2019 Ebx Ml Collaboration Modeling Met a Model
37/82
in an on#line offer/acceptance contract formationprocess.
TimeTo%c)no#lege'eceipt" Both partners aree to mutuallyverify receipt of a re&uestin business document!ithin specific time duration. A respondinpartner must e$it the transaction if they are not
able to verify the proper receipt of a businessdocument re&uest !ithin the aree timeoutperiod. A sendin partner must retry acommercial transaction if necessary or mustsend notification of failed business control*possibly revo"in a contractual offer+ if arespondin partner does not verify properlyreceipt of a business document re&uest !ithinthe areed time period. he time toac"no!lede receipt is the duration from thetime a business document re&uest is sent by are&uestin partner until the time a verification ofreceipt is by the re&uestin
business partner. his verification of receipt is anaudit#able business sinal and is instrumental incontractual obliation transfer durin a contractformation process *e.. offer/accept+.
timeTo%c)no#ledge%cceptance" Both partners aree to theneed for a business acceptance document to bereturned by a respondin partner after there&uestin business document passes a set ofbusiness rules. he time to ac"no!ledebusiness acceptance of a re&uestin businessdocument is the duration from the time are&uestin partner sends a business documentuntil the time an ac"no!ledement of
acceptance is by there&uestin partner. A respondin partner muste$it the transaction if they are not able toac"no!lede business acceptance of abusiness document re&uest !ithin the areedtimeout period. A sendin partner must retry acommercial transaction if necessary or mustsend notification of failed business control*possibly revo"in a contractual offer+ if arespondin partner does not ac"no!ledeacceptance of a business document !ithin theareed time period.
#e,uestingBusinessActivityA re&uestin business activity is a business activity that isperformed by a partner role re&uestin commerce from anotherbusiness partner role.
Ta33ed &a#ues7
is(on'epudiation*f'eceipt'euired. Both partners aree tomutually verify receipt of a re&uestin business
2Q
98
916
917
918
919
920
921
922
923
924
925
926
927
928
929
930
931
932
933
934
935936
937
938
939
940
941
942
943
944
945
946
947
948949
950
951
952
953
954
955
956
957
958
959
960
961
962
963
964
965
966
99
8/9/2019 Ebx Ml Collaboration Modeling Met a Model
38/82
document and that the receipt must be non#reputable. A receivin partner must sendnotification of failed business control *possiblyrevo"in a contractual offer+ if a respondinpartner has not properly delivered their businessdocument.
on#repudiation of receipt provides the follo!inaudit controls.Verif responin' ro!e ientit*authenticate+1
erify the identity of the respondin role*individual or oraniation+ that received there&uestin business document.Verif %ontent inte'rit1/ erify the interityof the oriinal content of the business documentre&uest.
retryCount" Both partners aree to the number of times toretry a transaction !hen a time#out#e$ceptioncondition is sinaled. his parameter only
applies to time#out sinals and not businessprocess controls or document contente$ceptions.
#espondingBusinessActivity
A respondin business activity is a business activity that isperformed by a partner role respondin to another businesspartner role:s re&uest for commerce.
Ta33ed &a#ues7
is$ntelligibleChec)'euired. Both partners aree that arespondin partner role must chec" that are&uestin document is not arbled *unreadable%unintelliible+ before verification of properlyreceipt is returned to the re&uestin partner.erification of receipt must be returned !hen adocument is but it is preferable toalso chec" for arbled transmissions at thesame time in a point#to#point synchronousbusiness net!or" !here partners interact!ithout oin throuh an asynchronous serviceprovider.
Infor"ation*ntity
An information entity realies structured business information thatis e$chaned by partner roles performin activities in acommercial transaction. 6nformation entities include or referenceother information entities throuh associations.
1"T8e (/ spec!>es d!g!tal s!gnature for partner-to-partner non-repud!at!on of or!g!n andcontent.1#T8e (/ spec!>es M7 or SA-1 message d!gest algor!t8ms and asymmetr!c encrypt!on topro)!de content !ntegr!ty.
28
100
967
968
969
970
971
972
973
974
975
976
977
978
979
980
981
982
983
984
985
986987
988
989
990
991
992
993
994
995
996
997
998
999
1000
1001
1002
1003
1004
1005
1006
1007
1008
1009
1010
101
102
103
104
105
8/9/2019 Ebx Ml Collaboration Modeling Met a Model
39/82
8/9/2019 Ebx Ml Collaboration Modeling Met a Model
40/82
0unctional#ole1
A partner role is a functional role% an employee role or anoraniational role. 5ither an employee role or an oraniationalrole can perform a functional role.
An oraniational role must be performed by a conforminnet!or" component that provides a business service.
*"ployee#ole2
An employee for business/leal reasons can only perform anemployee role. 'sually the details of the employee must becaptured and stored/transmitted to another partner forauditin/liability purposes !hen the t!o partner roles are not in thesame oraniation.
&o""ercialTransaction
A commercial transaction is a set of business information andbusiness sinal e$chanes amonst t!o commercial partners thatmust occur in an areed format% se&uence and time period. 6f anyof the areements are violated then the transaction is terminatedand all business information and business sinal e$chanes mustbe discarded. Commercial transactions can be formal as in theformation of on#line offer/acceptance commercial contracts andinformal an in the distribution of product announcements.Commercial transactions can comprise sub#transactions.
Ta33ed &a#ues7
isSecureTransport'euired. Both partners must aree to
e$chane business information usin a securetransport channel. he follo!in securitycontrols ensure that business document contentis protected aainst unauthoried disclosure ormodification and that business services areprotected aainst unauthoried access. his is apoint#to#point security re&uirement. ote thatthis re&uirement does not protect businessinformation once it is off the net!or" and insidean enterprise. he follo!in are re&uirements forsecure transport channels.
uthenti%ate senin' ro!e ientit,1 erifythe identity of the sendin role *employee or
oraniation+ that is initiatin the role interaction
1&Spec!fy!ng a partner role !s a SV re*u!rement to create a netor component des!gn t8atcan support an employee as ell as an organ!Kat!on 8en perform!ng t8e spec!>ed bus!nessact!)!ty.2' Spec!fy!ng an employee role l!m!ts t8e number of netor component con>gurat!ons t8atmust be cons!dered !n t8e SV of t8e model. +nly spec!fy an employee role !f only an employeecan perform t8e spec!>ed bus!ness act!)!ty.21T8e (/ spec!>es d!g!tal cert!>cates and SSJ to )er!fy t8e !dent!ty of send!ng ;and rece!)!nges d!g!tal cert!>cates and SSJ to pro)!de po!nt-to-po!nt content !ntegr!ty.23T8e (/ spec!>es d!g!tal cert!>cates and SSJ for po!nt-to-po!nt encrypt!on and decrypt!on.
D1
121
1085
1086
1087
1088
1089
1090
1091
1092
1093
1094
1095
1096
1097
1098
1099
1100
1101
1102
11031104
1105
1106
1107
1108
1109
1110
1111
1112
1113
1114
1115
1116
1117
1118
1119
1120
1121
1122
1123
1124
1125
1126
1127
122
123
124
8/9/2019 Ebx Ml Collaboration Modeling Met a Model
42/82
&o""ercialTransactionActivity
A commercial transaction activity is a business collaborationprotocol activity that e$ecutes a specified commercial transaction.he commercial transaction activity can be e$ecuted more thanonce if the isConcurrentproperty is true.
Ta33ed &a#ues7
timeToPerform. Both partners aree to perform a commercialtransaction activity !ithin a specific duration.he oriinatin partner must send a failurenotification to a respondin partner on timeout. Arespondin partner simple terminates its activity.he time to perform is the duration from the timea commercial transaction activity initiates thefirst commercial transaction until there is atransition bac" to the initiatin commercialtransaction activity. Both partners aree that thebusiness sinal document or business actiondocument specified as the document to return!ithin the time to perform is the in an on#line offer/acceptancecontract formation process.
transaction. his property relates a specific commercialtransaction to a commercial transaction activity.he commercial transaction activity e$ecutes thecommercial transaction.
isConcurrent. 6f the commercial transaction activity isconcurrent then more than one commercialtransaction can be open at one time. 6f thecommercial transaction activity is not concurrent
then only one commercial transaction activitycan be open at one time.
+ocu"ent*nvelope
A document envelope is a container for structured andunstructured business documents.
.1.2ell!for"edness #ules
he follo!in !ell#formedness rules apply to the business operationalvie! metamodel pac"ae.
BusinessActivityK1L 6f non#repudiation is re&uired then the input or returned business
document must be a tamper#proofed entity.
K2L 6f authoriation is re&uired then the input business document andbusiness sinal must be an authenticated or a tamper proofedsecure entity.
2$T8!s !s not a bus!ness acceptance document.
D2
125
1128
1129
1130
1131
1132
1133
1134
1135
1136
1137
1138
1139
1140
1141
1142
1143
1144
1145
1146
1147
1148
1149
1150
1151
1152
1153
1154
1155
1156
1157
1158
1159
1160
1161
1162
1163
1164
1165
1166
1167
1168
1169
1170
126
127
8/9/2019 Ebx Ml Collaboration Modeling Met a Model
43/82
KDL he time to ac"no!lede receipt must be less than the time toac"no!lede acceptance if both properties have values.
timeoAc"no!lee7eceipt G timeoAc"no!leeAcceptance
KEL 6f the time to ac"no!lede acceptance is null then the time to perform
an activity must either be e&ual to or reater than the time toac"no!lede receipt.
KJL he time to perform a transaction cannot be null if either the time toac"no!lede receipt or the time to ac"no!lede acceptance is notnull.
KNL 6f non#repudiation of receipt is re&uired then the time to ac"no!ledereceipt cannot be null.
KQL he time to ac"no!lede receipt% time to ac"no!lede acceptanceand time to perform cannot be ero.
K8L 6f non#repudiation is re&uired at the re&uestin business activity% thenthere must be a respondin business document.
K;L he time to ac"no!lede receipt% time to ac"no!lede acceptanceand time to perform properties must be specified for both there&uestin and respondin business activities and they must bee&ual.
#e,uestingBusinessActivity
K10L here must be one input transition !hose source state verte$ isan initial pseudo state.
K11Lhere must be one output transition !hose taret state verte$ is afinal state specifyin the state of the machine !hen the activity is
successfully performed.
K12L here must be one output transition !hose taret state verte$ is afinal state specifyin the state of the machine !hen the activity isnot successfully performed.
K1DL here must be one output transition to an ob-ect state that in turnhas one output transition to a respondin business activity.
K1EL here must be ero or one input transition from an ob-ect statethat in turn has one input transition from a respondin businessactivity.
#espondingBusinessActivityK1JL here must be one input transition from an ob-ect state that in turn
has one input transition from a re&uestin business activity.
K1NL here must be ero or one output transition to an ob-ect state thatin turn has an output transition to a re&uestin business activity.
DD
128
1171
1172
1173
1174
1175
1176
1177
1178
1179
1180
1181
1182
1183
1184
1185
1186
1187
1188
1189
1190
1191
1192
1193
1194
1195
1196
1197
1198
1199
1200
1201
1202
1203
1204
1205
1206
1207
1208
1209
129
8/9/2019 Ebx Ml Collaboration Modeling Met a Model
44/82
%'3ect 0lo- State
K1QL he source and taret of an ob-ect flo! must not be the samebusiness activity.
K18L he source and taret of the re&uestin ob-ect flo! must beopposite to the source and taret of the respondin ob-ect flo!.
Infor"ation *ntity
K1;L he associations on an information entity must be areationrelationships !ith other information entities to form a partonomy% ahierarchical decomposable arranement of business documentparts.
K20L he information entity associations only must be naviable from acontainin entity to an element entity *has#part relationship+.
K21L Constraints on an information entity association must be specifiedon the role of the part *supplier+ !ith respect to the !hole *client+.
K22L he client and supplier of an entity association must not be thesame entity.
Business &olla'oration Protocol
K2DL A business partner cannot provide both the initiatin andrespondin roles of the same commercial transaction activity.
4.2 Model Semantics
he semantics of each element of the B, model metamodel is defined in thissection.
Fiure 11 illustrates the interrelationships bet!een the B, model elements.
DE
130
1210
1211
1212
1213
1214
1215
1216
1217
1218
1219
1220
1221
1222
1223
1224
1225
1226
1227
1228
1229
1230
1231
1232
131
8/9/2019 Ebx Ml Collaboration Modeling Met a Model
45/82
8/9/2019 Ebx Ml Collaboration Modeling Met a Model
46/82
or the transaction must be rolled bac" to a defined state before thetransaction !as initiated.
here are t!o business sinals that can be asynchronously returned tothe initiator of the commercial transaction9 a business sinal to verifyproper receipt of a business document re&uest and a business sinal to
non#substantively confirm the acceptance of a re&uestin businessdocument for business processin.
6f any of the time out parameters are e$ceeded% a time out e$ception mustbe thro!n. 6f the retryCountproperty on the respondin businessactivity is reater than ero then the commercial transaction must be re#initiated *or a notification of failed business control possibly revo"in acontractual offer must be sent+. All business sinals and businessdocuments returned after the transaction !as initiated and up until thetime out e$ception must be discarded. he recurrence property specifiesthe number of times a commercial transaction must be initiated. 6f therecurrent property value is D then the commercial transaction can beinitiated a total of E times *the first initiation plus D retries+. he time to
perform property specifies the time to perform a sinle commercialtransaction.
A respondin partner simply terminates if a timeout is thro!n. hisprevents respondin commercial transactions from hanin indefinitely.
A partner role that initiates an asynchronous commercial transaction doesnot need to receive any business sinals. A partner role that initiates asynchronous business transaction must be able to receive businesssinals and must bloc" until the flo! of control is returned. his should notpreclude the initiation and e$ecution of multiple concurrent commercialtransactions% ho!ever.
6f any business e$ceptions *includes neative receipt and acceptanceac"no!ledements+ are sinaled then the commercial transaction mustterminate. he commercial transaction must not be re#initiated even if theretryCountparameter is not ero. Commercial transactions must onlybe retried if a timeout e$ception is thro!n.
here are t!o business sinals that are used for on#line commercialcontract formation and auditin9
Ac"no!lede receipt business sinal. he '/546FAC model
radin artner Areement *A+ suests that a partnersshould aree on the point at !hich a messae can be RsaidR tobe properly received and this point should be !hen a receivinpartner can RreadR a messae. hey suest this should be the
point after !hich a messae passes a structure/ schemavalidity chec". ote that this is not a necessary condition forverifyin proper receipt% only accessibility is. he propertyisIntelligibleCheckRequiredallo!s partners to aree that amessae should be before its receipt is verified2J.
2T8!s !s t8e con)ent!on spec!>ed for Rosettaet commerc!al transact!ons.
DN
134
1246
1247
1248
1249
1250
1251
1252
1253
1254
1255
1256
1257
1258
1259
1260
1261
1262
12631264
1265
1266
1267
1268
1269
1270
1271
1272
1273
1274
1275
1276
1277
1278
1279
1280
1281
1282
1283
1284
1285
1286
1287
1288
1289
135
136
8/9/2019 Ebx Ml Collaboration Modeling Met a Model
47/82
Ac"no!lede acceptance business sinal. he '/546FAC
model A suests that partners should aree on the point at!hich a messae can be RsaidR to be accepted for businessprocessin and this point should be after the contents of abusiness document have passed a business rule validity chec".For e$ample% if 6 order 100000000000 copies of a sinle boo"
from Amaon 6 am assumin it !ill fail some business rulechec". hese business rules are often found in tradincontracts.
Fiure 12 and Fiure 1D sho! the valid activity states for re&uestin andrespondin partner roles respectively. he behavior of each role isdetermined by the values specified for each business activity.
Business models may find it convenient to develop commercialtransaction desin patterns to facilitate the development of theirspecifications *refer to BCFS8 for definitions+. he follo!in five property#value conventions for commercial transactions have proven useful in theapplication of the metamodel to e$istin business re&uirements.
1. Business ransaction
2. 7e&uest / Confirm
D. ?uery / 7esponse
E. 7e&uest / 7esponse
J. otification
N. 6nformation 4istribution
hese conventions are applied by stereotypin the re&uestin businessactivity !ith the follo!in synta$.
Transa%tion Stereotpe
Business ransaction OerviceransactionActivityP
7e&uest / Confirm O7e&uestConfirmActivityP
?uery / 7esponse O?uery7esponseActivityP
7e&uest / 7esponse O7e&uest7esponseActivityP
otification OotificationActivityP
6nformation 4istribution O6nformation4istributionActivityP
DQ
137
1290
1291
1292
1293
1294
1295
1296
1297
12
Top Related