Page 1 of 28

INFS 770 Methods for Information Systems Engineering:

Knowledge Management and E-Business
Sring !00"
#r$ %arry Kers&h'erg
Information Systems #eartment
(eorge Mason )ni*ersity
+'stra&t$ In his seminal article, A Framework for Information Systems Architecture, JA !achman cut
through the confusion an" am#iguity surroun"ing the conce$t of system architectures #y reali%ing that no
single mo"el coul" ca$ture all the im$ortant features of an enter$rise or its systems Instea", a "ifferent
mo"el is re&uire" "e$en"ing #oth on who the mo"el is for an" on what &uestion that in"i'i"ual wants
answere" a#out the system (he initial framework consiste" of three $ers$ecti'es) the owner, the "esigner,
an" the #uil"er, an" three &uestions) what, how, an" where *ater, !achman e+$an"e" the framework to
inclu"e the a""itional &uestions of who, when, an" why

For each com#ination of $ers$ecti'e an" &uestion, there are can #e se'eral com$eting metho"ologies for
mo"eling the im$ortant features of the system Some metho"ologies are argua#ly #etter than others at
ca$turing an" communicating $ertinent information (his $ro,ect will focus in on the owner-s 'iew of how
the organi%ation works) #usiness $rocess mo"els .e will e+amine 'arious $rocess mo"eling techni&ues,
such as I/0F, 12*, an" 3P24, to "etermine their suita#ility, s$ecifically for mo"eling the #usiness
$rocesses of an e5#usiness .e will e+amine how $rocess mo"els ca$ture #usiness rules an" how they
relate to other com$onents of the architecture, such as ontologies .e will also in'estigate how well
'arious $rocess mo"els su$$ort the "ocumentation an" "e'elo$ment of we# ser'ices
,ro&ess Modeling for E-Business
(homas /ufresne
James 2artin
Page 2 of 28
Contents
3usiness Process 2o"els6
Process 2o"eling 3enefits6
3usiness Process Architecting7
2o"eling 8riteria7
3usiness Process 2o"eling 2etho"ologies9
Process 2o"eling 2etho"ologies9
Flow 8harts9
/ata Flow /iagrams:
8ontrol Flow /iagrams:
Functional Flow 3lock /iagrams;
<antt = P0>( /iagrams8
I/0F8
(he 2o"ern 2etho"s?
1nifie" 2o"eling *anguage @12*A1B
3usiness Process 2o"eling 4otation @3P24A1B
3usiness Process 2anagement11
3usiness Process 2anagement System11
Pi 8alculus an" Process 2o"eling16
3usiness Process 2anagement Initiati'e @3P2IA17
3usiness Process 2o"eling *anguage @3P2*A19
3usiness Process 2o"eling 4otation @3P24A1:
3usiness Process Cuery *anguage @3PC*A18
Process Status 8ommunication18
A 8ase Stu"y using 3P2*18
3P24 >e$resentation2B
3P0*7.S2B
e#D2* 3PSS22
Entologies22
Entologies an" Process 2o"eling22
Entological 0ngineering an" 053usiness26
*inking 05#usiness to E$erating Processes27
Process 2o"eling an" .e# Ser'ices27
.e# Ser'ices for 3usiness Process /esign29
.e# Ser'ices an" 3usiness Process 2anagement2:
8onclusion2:
.orks 8ite"2;
Ether >eferences28
Page 6 of 28
Business Process Models
3efore we can a"e&uately "iscuss the $ros an" cons of 'arious #usiness $rocess mo"eling metho"ologies, it will #e
hel$ful to "iscuss some generic attri#utes of #usiness $rocess mo"els, as well as i"entify some of the features that
one might like in a #usiness $rocess mo"eling metho"ology
As mentione" a#o'e, #usiness $rocess mo"els "escri#e how a #usiness works, or more s$ecifically, how they
accom$lish missions, acti'ities, or tasks @henceforth referre" to as tasksA A single mo"el shows how a #usiness
accom$lishe" a single task It woul" take many $rocess mo"els to fully "etail the hows of most real worl"
enter$rises
A single $rocess can #e &uite in'ol'e" It can consist of many actors @$eo$le, organi%ations, systemsA $erforming
many tasks In or"er to accom$lish the o'erall task, the actors must com$lete s$ecifie" su#5tasks in a coor"inate"
manner Sometimes, these su#5tasks can #e $erforme" in $arallel Sometimes they are se&uential Some $rocesses
re&uire re$etition of su#5tasks 2ost $rocesses ha'e "ecision $oints where $rocess flow can #ranch "e$en"ing on
either the con"ition of the system or the $articular $rocess e+ecution In coo$erati'e $rocesses actors must $ass
information (his information transfer can #e the trigger for an actor to #egin a su#5task Ether triggers are
$ossi#le, such as time or interru$ts Some $rocesses are a"5hoc (hat is, the su#5tasks "o not ha'e well "efine"
triggers Actors may not nee" to com$lete all of a su#task #efore they or another actor start work on another
"e$en"ent su#task Finally, a $rocess can look "ifferently when "escri#e" from the 'iew$oint of "ifferent actors A
#usiness $rocess mo"eling metho"ology nee"s to #e a#le to re$resent these "ifferent as$ects of a $rocess
"escri$tion A goo" metho"ology will $resent the re$resentation in a manner that is easily transferre" into the tacit
knowle"ge of the 'iewer
Process Modeling Benefits
(here are many $otential uses of $rocess mo"els F3rowning 2BB2GH
@aA Program $lanning
@#A 3aseline for continuous im$ro'ement
@cA Inowle"ge retention an" learning
@"A Process 'isuali%ation
@eA (raining
@fA Framework for metrics
@gA 8om$liance, au"it, an" assessments
@hA Program e+ecution
0'en though there are many #enefits to mo"eling #usiness $rocesses, it is rarely "one, an" when "one at all, not
"one 'ery well 2any com$anies ha'e ma"e efforts to "ocument their $rocesses, #ut 'ery few ha'e #uilt @an"
committe" to im$ro'e an" learn fromA useful $rocess mo"els Fi#i"G (he $rocess mo"els that "o e+ist are often
not well integrate" an" lea'e out key information that woul" fully "escri#e the $rocess (here is a nee" for #etter
tools an" techni&ues for mo"eling #usiness $rocesses an" kee$ing them in synch with actual #usiness acti'ities
0'en when a $ro,ect has a goo", well5"ocumente" $rocess, it is often too "ifficult to ca$ture lessons learne" from
the on5going $ro,ect an" imme"iately u$"ate the $rocess mo"el FFagerstrom et al 2BB2G Inowle"ge in the
$ro,ect is a""e" as the $ro,ect $rogresses As a result, earlier5ma"e "ecisions can #e consi"ere" unreasona#le at a
later stage It is im$ortant that the $rocess su$$orts e+change of "esign knowle"ge Fi#i"G
(his is 'ery true in con'entional $ro,ects, #ut e'en more "ifficult to accom$lish in we#5#ase" enter$rises where the
acti'ities occur in Internet time an" the acti'ity interfaces often lie at the #oun"ary #etween e5#usinesses Since
the e5#usiness is more a#stract than a con'entional #usiness, it is more "ifficult to "o management #y walking
aroun" @23.AA Instea" you will nee" a $rocess mo"el to "o the walking *ater we will "escri#e a 3usiness
Process 2anagement System @3P2SA a$$roach that will facilitate the 23.A techni&ue of making a #usiness
#etter meet its goals an" o#,ecti'es
Page 7 of 28
Business Process Architecting
An architecture is the arrangement of function an" feature that achie'es a gi'en o#,ecti'e F>ing 2BB1G It is
claime" that a #usiness $rocess must not merely #e engineere", #ut shoul" #e architecte" gi'en the 'ery com$le+
an" fu%%y nature of #usiness $rocesses F3iemans et al 2BB1G (hey go on further to sayH
0ngineers are traine" to "esign systems such as #ri"ges, com$uters, an" aircraft in a well5structure"
manner Jowe'er, the "esign of #usiness $rocesses has not yet mature" to this le'el .e argue that
the com$le+ity of #usiness $rocesses is the ma,or causeK 3usiness $rocess architecting, the high5
le'el, functional "esign of #usiness $rocesses, is more an art than a science Fi#i"G
(hey gi'e se'eral reasons for this e+traor"inary com$le+ity of #usiness $rocessesH
@aA they in'ol'e se'eral knowle"ge "omains
@#A they o$erate on 'astly "ifferent time scales
@cA they are often nearly in"e$en"ent
@"A $eo$le nee" years of training #efore they can un"erstan" them or reason a#out them
@eA a common frame of reference among the many stakehol"ers "oes not e+ist
@fA they ha'e many uncontrolle" mo"ifications
Further com$licating the $ro#lem is the fact that #usiness $rocesses can change autonomouslyH (he $eo$le that
are $art of a #usiness $rocess might mo"ify this $rocess, without any e+$licit "esign Fi#i"G In their $a$er, they
gi'e three elements nee"e" for constructing #usiness $rocess mo"els First, we nee" a more on this later
"e'elo$ment strategy that "etermines the or"er in which "esign ste$s are taken Secon", we nee" mechanisms to
structure a mo"el @(heir $a$er is unclear on e+actly what they mean #y mechanisms (hey make reference to
mo"eling styles #ut this a$$ears to #e a non sequiturA (hir", we nee" a mo"eling language (he rest of their
$a$er "escri#es "ifferent techni&ues for "e'elo$ing the $rocess mo"el
(hey "escri#e three "ifferent mo"eling strategies that can #e em$loye"H $rocess5oriente", resource5oriente", an"
"ata5oriente" Process5oriente" strategy starts with the workflow of an organi%ation @ie, the #eha'iorA (he
resources or roles within an organi%ation are mo"ele" first in the resource5oriente" a$$roach (he "ata5oriente"
strategy starts #y first "escri#ing the "ata items that com$rise the in$uts an" out$uts of the #usiness $rocess (he
$a$er "oes not suggest one strategy that is #est #ut rather that the a$$ro$riate strategy will "e$en" on the
situation an" often a hy#ri" strategy works well
Modeling Criteria
Stefan Ja#erl has "e'elo$e" a set of se'en criteria for e'aluating $rocess mo"eling metho"ologies FJa#erlGH
It must #e a#le to mo"el all the com$le+ities of #usiness $rocesses liste" a#o'e, to inclu"eH
Se&uencing
3ranching
*oo$ing
8oncurrency 8onstructs L fork an" synchroni%e
(imeouts
/ea"lines
Faults
Aggregation
It must ha'e a means of "istinguishing roles an" assigning them the 'arious tasks
(here must #e an unam#iguous gra$hical re$resentation of the language
It must ha'e a transaction mo"el that allows for the "escri$tion of how a $rocess can #e un"one
It must s$ecify how $rocess instances will #e triggere" an" i"entifie" throughout their e+ecution
Page 9 of 28
It must ha'e a means of s$ecifying the characteristics of the #usiness $rocess that woul" #e of interest
to e+ternal users (his woul" inclu"e things like &uality of ser'ice an" $ricing
(he language shoul" not mi+ in "etails of communications $rotocols
(he first three criteria are im$ortant for o#taining the first se'en #enefits i"entifie" #y 3rowning (he secon"
grou$ of three is essential for automating $rocess e+ecution #etween coo$erating, yet se$arate organi%ations (he
last criterion kee$s the $rocess mo"els at the right le'el of a#straction
Business Process Modeling Methodologies
Peo$le ha'e #een mo"eling $rocesses for many years (hey ha'e not always calle" their mo"els 3usiness Process
2o"els #ecause often, they were not "escri#ing what they thought of as #usiness $rocesses (hat sai", the
techni&ues they use" can an" ha'e #een a$$lie" to "escri#ing how organi%ations $erform their work (hese
mo"els can #e use" to train new em$loyees (hey can #e as ai"s in re5engineering $rocesses (hey can #e use" to
"e'elo$ simulations to test the $rocesses on in$uts that ha'e not occurre" in real life Finally, they can #e use" to
"e'elo$ systems to automate the $rocesses they mo"el In the last case, $rogrammers may use the $rocess mo"el as
a gui"e in "e'elo$ing the information system or more recently, some $rocess mo"els can #e run though $rocess
e+ecution engines that automate the $rocess "irectly from the mo"el
In a""ition to ha'ing many uses, $rocess mo"els can #e create" or $resente" using many "ifferent metho"ologies
0ach metho"ology has a "ifferent history 2any ha'e a "ifferent way of looking at $rocesses #ase" u$on the
$ur$ose they were originally create" for Some are more or less rea"a#le #y non$rofessionals Some are more or
less useful for #usiness $rocess mo"eling
(he following is a #rief "escri$tion of some of the more $rominent $rocess mo"eling metho"ologies
Process Modeling Methodologies
Flow Charts
Flow charts originate" in, or were a"o$te" 'ery early #y, the $rogramming community Programmers use" them to
"escri#e the logic, or $ath of e+ecution, within an e+ecuting $rogram Flow chart sym#ology an" semantics is
restricte" to the limite" num#er of atomic control structures a'aila#le to $rogrammers Flow charts were
"e'elo$e" to "e$ict the $ath of e+ecution within a single $rocess (hey "o not ha'e the e+$ressi'e $ower to
$ro$erly mo"el grou$s of coo$erating $rocesses
Page : of 28
Figure - +NSI Flow .hart E/amle
[deming.eng.clemson.edu/pub/tutorials/qctools/fowm.htm]
Data Flow Diagrams
/ata Flow /iagrams @/F/sA ha'e their #irth, or at least their coming of age, in (om /e2arco-s #ook, Structured
Analysis and Systems Specifications @Mour"on Inc, 1?;8A As can #e inferre" from the name, /F/s concentrate
on the "ata in an information system (hey show the se&uence of $rocessing ste$s tra'erse" #y the "ata 0ach ste$
"ocuments an action taken to transform or "istri#ute the "ata /F/s are easy to rea", making it $ossi#le for
"omain e+$erts to create an" or 'ali"ate the "iagrams /F/s "o not $ro'i"e the ca$a#ility to "escri#e $rocess
se&uencing or $rocess control mechanisms
Control Flow Diagrams
8ontrol flow "iagrams @8F/A are similar to /ata Flow /iagrams e+ce$t they are commonly use" where the
a$$lication is more e'ent5"ri'en than "ata5"ri'en (hey are an enhancement to the /e2arco style "ata flow
"iagrams (he most common style of 8F/ is $erha$s the Jatley5Pir#hai "iagram FJatley et al 2BBB, an" also see
htt$H==www$sarecom=G (he 8F/ a$$roach is #ase" on classical structure" analysis techni&ues an" finite state
machine theory an" merges the two together into a unifie" whole A""itional information is containe" in control
s$ecifications @8SP08sA that contain the finite state machine structures (he finite state machines are use" to
control the #eha'ior of the com$anion "ata flow "iagrams @/F/sA An e+am$le of a com#ine" /F/=8F/ is shown
in Figure 2 (he soli" lines re$resent "ata flows while the "ashe" lines re$resent control flows
Page ; of 28
Figure ! .om'ined #ata0.ontrol Flow #iagram 1#F#0.F#2
Fhtt$H==wwwtur#ocasecom=featureshtmlG
Functional Flow Block Diagrams
(he functional flow #lock "iagram @FF3/A is wi"ely use" in classical systems engineering to show the or"er of
e+ecution of system functions As such, it shows the $ro$er se&uencing in terms of $rece"ence @function A must
ha$$en #efore function 3A an" concurrency @function 8 can occur at the same time as function /A (he concurrent
functions can #e either $arallel @A4/ gateA or alternati'e $aths @E> gateA A ty$ical format for the FF3/ is shown
in Figure 6
Page 8 of 28
Figure " Fun&tional Flow Blo&3 #iagram 1FFB#2 Format
F/A1 2BBBG
Gantt / PERT Diagrams
Jenry <antt in'ente" the chart that #ears his name in 1?1; Je was working for the 4a'y an" wante" a metho" to
sche"ule the tasks associate" with shi$ construction Jis charts "e$icte" each task as a hori%ontal #ar who-s length
was "etermine" #y the e+$ecte" "uration of the task (hese sim$le charts showe" #oth logic an" se&uencing
(he 1S 4a'y create" P0>( charts in the 1?9Bs (hey #asically ca$ture the same information as <antt charts, #ut
where the <antt charts $ro'i"e a goo" 'isuali%ation of task "urations, P0>( charts "o a #etter ,o# $resenting
se&uencing, es$ecially when the se&uencing is com$licate"
In general, #oth <antt an" P0>( charts are use" for $ro,ect management (hey are sel"om use" for $rocess
mo"eling (hey ha'e no means to "escri#e any information a#out a $rocess than the se&uencing of tasks, although
some mo"ern tools allow the association of resources to tasks (hey "o not su$$ort the mo"eling in$ut = out$ut
information or material nor "o they $ro'i"e a means to mo"el control mechanisms
DEF
Pro#a#ly the most common techni&ue of tra"itional #usiness $rocess mo"eling is I/0F (here are se'eral ty$es of
I/0F mo"els (he most familiar is I/0FB I/0FB mo"els are acti'ity mo"els (hey mo"el the tasks $erforme"
#y an organi%ation, to inclu"e the in$uts, out$uts, an" controls of each task (asks, or acti'ities, can #e shown as
high le'el tasks which "ecom$ose into su#5tasks In$uts, out$uts, an" controls can also #e aggregate" into grou$s
.hile I/0FB mo"els can a$$ear to show the se&uence of acti'ities, this is only a $erce$tion 4o tem$oral
relationshi$ is im$lie" #y the arrangement of acti'ities in the "iagram Process "etails are ca$ture" in I/0F6
"iagrams Figure 7 shows an e+am$le of an I/0F6 "iagram
Page ? of 28
Figure 4 e/amle I#EF" #iagram
Ene of the uni&ue features of I/0F mo"eling is that I/0F e+$licitly recogni%es the fact that $rocess "escri$tions
can 'ary "e$en"ing on the $oint of 'iew from which they are generate"
The Modern Methods
(he a#o'e re$resent ,ust a fraction of the metho"ologies use" o'er the last thirty years to "ocument #usiness
$rocesses As $art of his Ph/ research, 3art5Jan Jommes has i"entifie" twenty "ifferent techni&ues an" o'er 69B
"ifferent $rocess mo"eling tools .hile many of these techni&ues are still use" in $ractice, most "o not meet e'en
the first three of Ja#erl-s criteria, let alone the criteria essential for mo"eling $rocesses for automate" e+ecution A
new set of metho"ologies is un"er "e'elo$ment to meet the nee"s of mo"ern e5#usinesses e#P2*org i"entifies
these metho"ologies as e#P2*, 3P2*, D*A4<, .SF*, 3P0*7.S, 0/E8, DP/*, an" 12* 2B, howe'er
3P0*7.S is a colla#oration #etween the "e'elo$ers of D*A4< @2icrosoftA an" .SF* @I32A, so D*A4< an"
.SF* are really no longer conten"ers
(he .orl" .i"e .e# 8onsortium @.68A is "e"icate" to "e'elo$ing the full $otential of the .e# (o this en", they
are $ro$onents of .e# Ser'ices .e# Ser'ices are an o$erating system an" $rogramming language in"e$en"ent
metho" of "istri#ute" com$uting (hey are an a$$lication5to5a$$lication $rotocol (he .e# Ser'ices Acti'ity of
.68 is working to $u#lish s$ecifications for .e# Ser'ices that will s$ee" their "e$loyment an" im$ro'e their
chances of success .ithin the .e# Ser'ices Acti'ity, there are four working grou$s) the .e# Ser'ices
Architecture .orking <rou$, the D2* Protocol .orking <rou$, the .e# Ser'ices /escri$tion .orking <rou$,
an" the .e# Ser'ices 8horeogra$hy .orking <rou$ (he .e# Ser'ices 8horeogra$hy .orking <rou$ is working
towar"s a stan"ar" for orchestrating the interaction of 'arious we# ser'ices in the com$letion of a #usiness $rocess
!nified Modeling "anguage #!M"$
(he 12* came from the works of E#,ect Eriente" Analysis an" /esign $ro$onents In the early ?B-s, se'eral
researchers ha" "e'elo$e" similar, yet incom$ati#le re$resentations for "escri#ing o#,ect oriente" software systems
Page 1B of 28
Se'eral of the lea"ers in the fiel" got together, forme" the E#,ect 2o"eling <rou$ @E2<A an" fuse" their
com$eting metho"ologies into a unifie" one Jence the name (he 12* actually consist of a num#er of "ifferent,
loosely cou$le" ty$es of mo"els 0ach mo"el is for a "ifferent $ur$ose 8lass mo"el are use" to ca$ture
relationshi$s among the entities in the "omain 1se 8ase "iagrams are use" to ca$ture re&uirements Se&uence
"iagrams ca$ture $rocess flow Package "iagrams ca$ture "etails of "e$loyment Ef all the "ifferent "iagrams,
12* Se&uence "iagrams are #est for ca$turing $rocess "escri$tions .hile originally "e'elo$e" for software
engineering, 12* se&uence "iagrams meet many of the criteria i"entifie" #y Ja#erl (heir #iggest "raw#ack
howe'er is the lack of an aggregation construct
Figure 5 E/amle )M% Se6uen&e #iagram
Fhtt$H==wwwsmart"rawcom=resources=e+am$les=software=uml:htmG
Business Process Modeling %otation #BPM%$
(he 3usiness Process 2o"eling 4otation @3P24A is a relati'ely new techni&ue for "e'elo$ing $rocess mo"els It
was recently $u#lishe" #y the 3usiness Process 2anagement Initiati'e @3P2IA as a "raft s$ecification s$ecifically
for mo"eling #usiness $rocesses (he 3P24 has a corres$on"ing formal D2*5#ase" language calle" 3usiness
Process 2o"eling *anguage @3P2*A Since this techni&ue is the main focus of this $a$er, the 3P24 an" 3P2*
are "escri#e" in much greater "etail in a later section
Business Process Management
.elcome to the worl" of 3usiness Process 2anagement @3P2A, where gran"iose claims are #eing ma"e how 3P2
is going to sa'e the worl" of #usinessNit will succee" where all other initiati'es ha'e faile" @like 8om$uter Ai"e"
Page 11 of 28
2anufacturing @8A2A, (otal Cuality 2anagement @(C2A, 3usiness Process >eengineering @3P>A, Si+ Sigma, the
Fifth /isci$line, an" so onA FSmith an" Fingar, Internet .orl", 2ay 2BB2G (he latest #ook #y Jowar" Smith
@Business Process ManagementThe Third Wave,
1
an" see also www#$m6comA is chock full of $ronouncements
on the won"ers of this new a$$roach Ef course, he fails to $ro'i"e much e'i"ence to #ack u$ his assertions F>ing
2BB6G
.e will e+$lore this worl" of 3P2 to "isco'er how it will #enefit the worl" of 053usiness an" how it im$acts the
"omain of Inowle"ge 2anagement 3usiness Process 2o"eling @another 3P2A is key to making 3P2 @the
management ty$eA li'e u$ to its e+$ectations 1nlike $re'ious a$$roaches, it is claime" that 3P2 can create a
single "efinition of a #usiness from which alternati'e 'iews of that $rocess can #e crystalli%e" F2a+ 2ore, #ook
re'iew on ama%oncom for BPM-The Third WaveG 3P2 claims to mo'e us from "ata $rocessing to $rocess
$rocessing
Ene of its multi$le strengths is that it synthesi%es an" e+ten"s $re'ious $rocess re$resentation an"
colla#oration technologies an" techni&uesNsuch as reengineering, 0AI, workflow management,
ser'ice5oriente" architecture, D2* an" .e# ser'ices, (C2, Si+ Sigma, an" systems thinkingN
into a unifie" a$$roach (he entire a$$roach is foun"e" on $rocess calculus, in $articular one form
of this calle" Pi5calculus Fi#i"G
(his $a$er will attem$t to sift through the hy$e an" gi'e an o'erall assessment of how 3P2 can an" shoul"
su$$ort an 053usiness .e will #e looking at the 'arious $ro"ucts from the 3usiness Process 2anagement
Initiati'e @3P2IANnamely the 3usiness Process 2o"eling *anguage @3P2*A an" the 3usiness Process 2o"eling
4otation @3P24A Fwww#$miorgG .e will also look at other metho"s an" tools for mo"eling a set of #usiness
$rocesses
Business Process Management &'stem
(he so5calle" 3usiness Process 2anagement System @3P2SA is central to this re'olution in the way #usinesses will
o$erate in the future Jowar" Smith "escri#es a 3P2S as a single, unifie" mo"eling, integration, an" e+ecution
en'ironment that can #e a$$lie" to the im$lementation of literally any #usiness $rocess FSmith an" Fingar,
Internet .orl", 2ay 2BB2G Je says that 3P2S can #e thought of as an Oengine for $rocesses- an" thatH
(he 3P2S $ro'i"es the mechanisms to stitch a$$lication com$onents together to automate an"
share strategic an" o$erational #usiness $rocesses, in a managea#le an" fle+i#le way 3y
com$arison, in the way that the >elational /ata#ase 2anagement System @>/32SA ena#les the
sharing of #usiness "ata among a$$lications an" com$anies @using a common language calle"
SC*A, the 3P2S ena#les the sharing of #usiness $rocesses @using a common language calle"
3PC*A Fi#i"G
Figure : shows how the 3P2S #rings together legacy integration with ne+t generation #usiness $rocess
colla#oration, ,oining these two worl"s with #usiness $rocess automation Fi#i"G (his will #ring together
workflow management a$$lications an" the human acti'ities while the #usiness $rocesses are #eing manage" an"
"irecte" #y the 3P2S 4ew a$$lications can #e written that interact with an" transform the whole $rocess, from
en" to en", without requiring software engineering Fi#i", em$hasis a""e"G In the new worl" of $rocess5centric
information technology, a$$lications will conform to software architectures that align more rea"ily with #usiness
acti'ityNe'en across #usiness #oun"aries
1
(he first two wa'es are (aylorism an" #usiness $rocess reengineering
Page 12 of 28
Figure 7 8he Business ro&ess management system
FSmith an" Fingar, Internet .orl", 2ay 2BB2G
0nter$rise A$$lication Integration @0AIA su$$orts "iscrete a$$lication e'ents, whereas 3usiness Process
Integration @3PIA han"les e+ten"e" acti'ity se&uences, long5li'e" $rocesses, com$ensating transactions, failures
an" cancellations "ri'en #y #usiness re&uirements, or con"itions outsi"e the control of I( (hese integrate"
$rocesses inclu"e sim$le mechanisms to #ack out of failure con"itions e'en when such roll#acks are not su$$orte"
#y #ack5en" 0>P systems Fi#i"G
In the future it will #e necessary to integrate the 3P2S with a 3usiness Entology 2anagement System @3E2SA,
#ut accor"ing to Jowar" Smith, the time was not &uite right to stan"ar"i%e this as$ect of the $ro#lem since
further inno'ation is re&uire" F$ri'ate communicationG Je further says that .e took a ste$, from "ata, to
$rocess @some say that-s a huge ste$ an" some say it-s a small ste$A #ut we coul" not take a larger ste$ to the
ontology mo"el (he 3P2 a$$roach is a#out reengineering reengineeringH
Instea" of reengineering $rocesses in one fell swoo$ an" then cementing the new mo"els in co"e,
com$anies shoul" "esign $rocesses that can #e change" on the fly an" software thatPs fle+i#le
enough to su$$ort those changes In the Qthir" wa'e of #usiness5$rocess management,Q the authors
write, im$lementing a new $rocess is as easy as &uerying a "ata#ase FI48 2aga%ine, ref t#"G
3P2 is a#out creating a $rocess5manage" enter$rise <0 seems #e stri'ing towar"s this goalH /igiti%ation Fof
$rocessG re$resents a re'olution that may #e the greatest o$$ortunity for growth that our com$any has e'er seen
F<0 2BB1 Annual >e$ortG /o not mistake 3P2 for some new Okiller a$$- or some fashiona#le new #usiness
theory It is a foun"ation u$on which com$anies can "e$en" as surely as they "e$en" on "ata#ase management
to"ay FSmith et al 2BB6G
3y $lacing #usiness $rocesses on center stage, cor$orations can gain the ca$a#ilities they nee" to
inno'ate, reenergi%e $erformance an" "eli'er the 'alue to"ay-s markets "eman" A $rocess5
manage" enter$rise makes agile course corrections, em#e"s si+ sigma &uality an" re"uces
cumulati'e costs across the 'alue chain F#$m6org, a#out the #ook $ageG
(here are some high $raises for 3P2, an e+am$le #eing the nine re'iews on ama%oncom gi'ing Smith-s (hir"
.a'e #ook a $erfect fi'e stars Jowe'er, there is one re'iewer who ga'e it only one starH (his #ook con'erges an
ama%ing num#er of #u%% wor"s into an o'erly long sales #rochure that lacks su#stance, rationale or $roof
regar"ing the #enefits of 3P2 /angerously @for youA it ignores the threats of 3P2 (he single negati'e re'iew
goes on further to sayH
Page 16 of 28
Similar to 3P2Ps three $re"ecessors 8E3E*, 8I2, an" 3P>, this Qthir" wa'eQ claims that a
higher or"er of com$uteri%e" logic is the key to continual a"a$tation for ma+imi%ing customer
'alue 1nfortunately @for youA it "oes not clarify how 'alue is to #e create" also for in'estors,
su$$liers an" em$loyees Further, in "eclaring Q#usiness is $rocessQ it $otentially "i'erts your
em$loyees from le'eraging your only strategic asset 555 em$loyee learning an" colla#oration
(hir"ly, while e+tolling the #enefits of highly mallea#le $rocesses, it ignores the $ro#lem of
managing multi$le changes while ensuring enter$rise integrity 555 a critical $ro#lem a""resse" #y
the in"ustrial $rocess control in"ustry more than three "eca"es ago F>ing, ama%oncom #ook
re'iewG
As you can see, there is a large "egree of enthusiasm for the 3P2S a$$roach 3ut there is also a cautionary flag
#eing wa'e" (here ha'e #een many $romise" sil'er #ullets in the $ast, an" it woul" #e wise to take this roa"
slowly an" carefully to a'oi" the $itfalls of the $ast As Ste'e (owers says in his re'iew of this #ook on
ama%oncom, this is the #iggest thing to hit the $rocess scene since 1??6
Pi Calculus and Process Modeling
3usiness Process 2anagement is re$orte"ly #ase" on $i calculus (he $i5calculus $ro'i"es a conce$tual
framework for un"erstan"ing mo#ility, an" mathematical tools for e+$ressing systems an" reasoning a#out their
#eha'ior FSangiorgi 2BB1G (he $i5calculus "iffers from other techni&ues for mo"eling #eha'ior mainly in its
treatment of mo#ilityH
(he mo'ement of a $iece of "ata insi"e a com$uter $rogram is treate" e+actly the same as the transfer
of a message 5 or in"ee" an entire com$uter $rogram 5 across the internet Ene can also "escri#e
networks which reconfigure themsel'es (he calculus is 'ery sim$le #ut $owerful) its most $rominent
ingre"ient is the notion of a name Its theory has two im$ortant ingre"ientsH the conce$t of #eha'ioral
@or o#ser'ationalA e&ui'alence, an" the use of a new theory of ty$es to classify $atterns of interacti'e
#eha'ior (he internet, an" its communication $rotocols, fall within the sco$e of the theory ,ust as
much as com$uter $rograms, "ata structures, algorithms an" $rogramming languages F2ilner 1???G
Accor"ing to Jowar" Smith, Pi5calculus has #een chosen as the foun"ation for the new O#usiness com$uter-
FSmith et al 2BB6G Pi calculus @or $rocess calculusA is an e+tension of the lam#"a calculus that has #een the
#asis for com$uting for "eca"es
Pre'ious theories in com$uter science, nota#ly the *am#"a calculus, focuse" on the #eha'ior of much
sim$ler com$uter systems, where there is either a single threa" of e+ecution or a set of $arallel #ut
non5interacting tasks Such algorithms are $roce"ural, se&uential, goal5oriente", hierarchical an"
"eterministic All of to"ay-s well5known $rogramming languages can #e stu"ie" using *am#"a5
calculusK 3y contrast, in $rocess theories such as Pi5calculus, the main focus is on systems that
interact an" interru$t one another, where there are many "ee$ly neste" in"e$en"ent, #ut coor"inate",
interacting threa"s of e+ecution 3usiness $rocesses are an e+am$le (he "ifferences #etween these
theories are striking, for e'en our notion of what constitutes a common5sense inter$retation of data
an" value has change" utterly
In con'entional com$uter languages there e+ists the conce$t of a ty$e KintegerKstringK 3y
contrast, in languages "eri'e" from Pi5calculus, ty$es re$resent #eha'ioral $atternsK it i"entifies the
conce$ts that un"er$in a wi"e 'ariety of concurrent systemsKwhere $rocess is the new first5class
entityK (his $ers$ecti'e gi'es the thir" wa'e of $rocess management its inherent a#ility to capture
descri!e and manage whole processes L not ,ust integration #etween e+isting algorithmic $roce"ures
written in con'entional software languagesK Fi#i", em$hasis in originalG
(he key to making $rocesses managea#le un"er this new scheme of 3P2S is to make the software a$$lications
$rocess5aware as o$$ose" to #eing "ata5aware (his tra"itional focus on "ata limits the a#ility of the software
engineer to $ro'i"e tools to the su$$ly chain manager to hel$ manage real #usinesses Fi#i"G (he new software
engineer nee"s to incor$orate the conce$ts of $i5calculus to achie'e this $rocess5awareness for their a$$lications
Page 17 of 28
Business Process Management Initiative (BPMI)
(he 3P2I is in'ol'e" in acti'ities to "e'elo$ technologies that su$$ort the enter$rise in #ecoming $rocess5
oriente" 3P2Iorg was starte" #y Intalio, Inc in August 2BBB
3P2Iorg @the 3usiness Process 2anagement Initiati'eA is a non5$rofit cor$oration that em$owers
com$anies of all si%es, across all in"ustries, to "e'elo$ an" o$erate #usiness $rocesses that s$an
multi$le a$$lications an" #usiness $artners, #ehin" the firewall an" o'er the Internet (he
Initiati'ePs mission is to $romote an" "e'elo$ the use of 3usiness Process 2anagement @3P2A
through the esta#lishment of stan"ar"s for $rocess "esign, "e$loyment, e+ecution, maintenance,
an" o$timi%ation 3P2Iorg "e'elo$s o$en s$ecifications, assists I( 'en"ors for marketing their
im$lementations, an" su$$orts #usinesses for using 3usiness Process 2anagement technologies
F#$miorgG
3P2* an" 3PC* are two o$en stan"ar"s "e'elo$e" #y 3P2I that will ena#le the management of e5#usiness
$rocesses using a 3usiness Process 2anagement System @3P2SA (he sco$e of 3P2I is shown in Figure ;
Figure 7 S&oe of B,MI
F3P2* 1B1H Im$lementing the 3P2* S$ecificationG
Business Process Modeling "anguage #BPM"$
(he 3usiness Process 2o"eling *anguage @3P2*A is a meta5language for the mo"eling of #usiness $rocesses
F#$miorgG It is com$are" to D2* which is a meta5language for the mo"eling of #usiness "ata 3P2* $ro'i"es
an a#stracte" e+ecution mo"el for colla#orati'e R transactional #usiness $rocesses #ase" on the conce$t of a
transactional finite5state machine Fi#i"G
(he essential feature of 3P2* is that it has a common $u#lic interface an" $ri'ate im$lementations (he $u#lic
interface is e+$ose" to #usiness $artners to allow the e+$loitation of the strengths of each se$arate com$any in a
larger colla#orati'e effort (he crown ,ewels of the cor$oration are em#e""e" in the $ri'ate im$lementations
Page 19 of 28
within 3P2* (he $u#lic interface of 3P2* can #e "escri#e" as e#D2* #usiness $rocesses or >osetta4et Partner
Interface Processes, in"e$en"ently of their $ri'ate im$lementations
(he 3P2* re$resents #usiness $rocesses as the interlea'ing of control flow, "ata flow, an" e'ent flow, while
a""ing orthogonal "esign ca$a#ilities for #usiness rules, security roles, an" transaction conte+ts Fi#i"G 3P2*
offers e+$licit su$$ort for synchronous an" asynchronous "istri#ute" transactions (here is $ro'ision for using it as
an e+ecution mo"el In other wor"s, the 3P2* for the #usiness is what runs the #usiness while in its e+ecution
mo"e (his is what allows for its great fle+i#ility in a"a$ting to changing #usiness situations
(he 3P2* was "e'elo$e" #y the 3usiness Process 2anagement Initiati'e @3P2IA an" is "ocumente" in a ?: $age
$ro$ose" recommen"ation 3P2* has an D2* synta+ as shown in Figure 8
Figure 9 B,M% &ode e/amle
F3P2* 1B1H Im$lementing the 3P2* S$ecificationG
3P2* has the following uni&ue features Fi#i"GH
@aA en"5to5en" $rocess mo"eling
@#A control5flow="ata5flow se$aration
@cA $ro"uce=consume messaging
@"A "ynamic control5flow
@eA trans$arent $ersistence
@fA em#e""e" #usiness rules
@gA neste" $rocesses
@hA "istri#ute" transactions
@iA $rocess5oriente" e+ce$tion han"ling
@,A un"erlying mathematical mo"el
Its un"erlying mathematical #asis is $i5calculus Pi5calculus is also use" #y 2icrosoft-s D*A4< an" has the
following featuresH
@aA consistency checking
@#A "ea"lock "etection
@cA #ottleneck "etection
@"A ena#le $rocess o$timi%ation
Since 3P2* is e+ecuta#le, it #ri"ges the ga$ #etween tra"itional $rocess mo"eling an" #usiness e+ecution It can
#e use" #y #oth #usiness analysts an" software engineers Since 3P2* is #ase" on D2* it is really not inten"e" to
Page 1: of 28
#e use" "irectly as a $rogramming language Instea" it is inten"e" that human analysts woul" use the
corres$on"ing 3usiness Process 2o"eling 4otation @3P24A which $ro'i"es the easy5to5use front5en" to facilitate
human un"erstan"ing Since the 3P24 is "irectly tie" to the un"erlying 3P24, there is nothing lost in the
translation from the mo"el "iagram to the $rocess e+ecution
Business Process Modeling %otation #BPM%$
(he 3usiness Process 2o"eling 4otation @3P24A is what a #usiness $rocess analyst will use to "esign e+ecuta#le
#usiness $rocesses (he 3P24 "irectly translates into 32P* that is then e+ecute" using an e+ecution engine
Figure ? shows an e+am$le of how 3P24 an" 3P2* relate to each other
Figure : Maing from B,MN to B,M%
F3P2* 1B1H Im$lementing the 3P2* S$ecificationG
Figure 1B shows an e+am$le of a relati'ely com$le+ #usiness $rocess that in'ol'es or"er management, in'entory
management, $ro"uction management, an" logistics management Figure 11 shows a sim$le e+am$le of an e5mail
'oting $rocess using 3P24
Page 1; of 28
Figure -0 B,MN e/amle
F3P2* 1B1H Im$lementing the 3P2* S$ecificationG
Figure -- E-Mail ;oting ,ro&ess in B,MN Style
F3P24 S$ecificationG
Page 18 of 28
Business Process (uer' "anguage #BP("$
(he 3PC* s$ecification is still un"er "e'elo$ment an" is not a'aila#le for $u#lic re'iew yet (herefore it is
"ifficult to say much a#out it Jowe'er, here is what the 3P2I we#$age says a#out 3PC*H
(he 3usiness Process Cuery *anguage @3PC*A is a management interface to a #usiness $rocess
management infrastructure that inclu"es a $rocess e+ecution facility @Process Ser'erA an" a $rocess
"e$loyment facility @Process >e$ositoryA (he 3PC* interface to a Process Ser'er ena#les #usiness
analysts to &uery the state an" control the e+ecution of $rocess instances manage" #y the Process
Ser'er (his interface is #ase" on the Sim$le E#,ect Access Protocol @SEAPA (he 3PC* interface
to a Process >e$ository ena#les #usiness analysts to manage the "e$loyment of $rocess mo"els
manage" #y the Process >e$ository (his interface is #ase" on the /istri#ute" Authoring an"
Sersioning Protocol @.e#/ASA Process mo"els manage" #y the Process >e$ository through the
3PC* interface can #e e+$ose" as 1//I ser'ices for $rocess registration, a"'ertising, an"
"isco'ery $ur$oses F#$miorgG
Process &tatus Communication
.f5D2* from .f28 is another technology like 3PC* that a""resses the "ynamic communication #etween
$rocesses .hy woul" a #usiness want $rocesses to communicate with each otherT If a #usiness has a large
$rocess that consists of .e# Ser'ices from "ifferent organi%ations, "ecision makers may want to know how far
along the $rocess has $rogresse" towar"s its e+$ecte" outcome (he 3PC* can #e use" to make this &uery of an
on5going $rocess (he .e# Ser'ices themsel'es can use 3PC* to &uery the status of other .e# Ser'ices Process
metrics can #e collecte" form 'arious instantiations of $rocesses to "etermine which $rocess is working more
efficiently Process im$ro'ement initiati'es can use these metrics to i"entify areas for im$ro'ement or when to
shut "own o#solete $rocesses (he #usiness intelligence gathere" using 3PC* can #e use" to "ynamically
manage the enter$rise in a matter of hours com$are" to the ol" way which coul" takes weeks or months
A Case Study using BPML
In 2BB1, the Software 0ngineering 8enter of the Fe"eral 8IE 8ouncil s$onsore" se'eral $ilot $ro,ects in e5
go'ernment 05go'ernment is the $u#lic sector e&ui'alent of e5#usiness <o'ernment #usiness $rocesses are as
com$le+ an" as "i'erse as cor$orate $rocesses an" for the most $art, what is true for e5#usiness hol"s true for e5
go'ernment In the area of $rocess mo"eling, there are no significant "ifferences 1sing an e5go'ernment
e+am$le allows us to get access to more "etail than might #e a'aila#le for a real worl" e5#usiness case
Ene of the $ilot $rograms in'ol'e" the "e'elo$ment of a Fe"eral <rants Architecture (he fe"eral go'ernment
o'ersees the annual "istri#ution of #illions of "ollars of grants to uni'ersities, foun"ations, cor$orations, an"
in"i'i"uals (his o'ersight is "istri#ute" throughout "o%ens of fe"eral agencies an" "e$artments 0ach
organi%ation has its own uni&ue $roce"ures for the a$$lication, awar"ing, tracking, an" $ayment of grants (his
"u$lication of function makes the system confusing an" wasteful (he Fe"eral <rants Architecture is an attem$t to
create an e5go'ernment solution that stan"ar"i%es an" streamlines the management of fe"eral grants
(he 2I(>0 8or$oration "e'elo$e" a Fe"eral <rants Pilot Architecture using /o/-s 87IS> Architecture
Framework 2I(>0 "i" not $ro"uce any $rocess mo"els for this architecture Instea", they chose to "o acti'ity
mo"eling using I/0FB As "iscusse" in the section on I/0F, I/0FB mo"els are 'ery similar to $rocess mo"els
(hey show tasks an" task se&uences, #ut they "o not show logic Figure 12 shows the acti'ity hierarchy create" #y
2I(>0
Page 1? of 28
Figure -! Federal (rants +&ti*ity <ierar&hy .hart 1MI8=E !00-2
Figure -" Federal (rants +&ti*ity #iagram 1MI8=E !00-2
Page 2B of 28
BPMN Representation
2o"eling this system in 3P24 is not a straightforwar" acti'ity (he mo"eler must make many "ecisions,
such as what le'el of "etail to show on a gi'en chart, what $ools an" lanes to create, how to lay out the in"i'i"ual
com$onents (his is a "iagram of the o'erall $rocess of grant a"ministration A""itional "etails for su#5$rocesses
will #e $ro'i"e" in a""itional "iagrams 4ote that the Fe"eral 8ommons, as en'isage" #y 2I(>0, "oes not
$ro'i"e much functionality
Figure -4 Federal (rants +&ti*ity Modeled )sing B,MN 1to le*el2 1MI8=E !00-2
A more interesting an" argua#ly soun"er architecture woul" #e for the Fe"eral 8ommons to #e the sole interface of
the $u#lic to the <rants $rocess (he 8ommons coul" communicate 'ia .e# Ser'ices to Fe"3i%E$$s, the <rant
A"ministrators, an" the Payment Agents
BPE")*&
Pro#a#ly the #iggest conten"er to 3P2* for the crown of .e# Ser'ices 8horeogra$hy *anguage is 3P0*7.S Its
hea'yweight #acking from I32 an" 2icrosoft, gi'e it an e+cellent chance of success
.e# ser'ices #y themsel'es ,ust $erform atomic actions (hey take in a grou$ of in$uts an" $ro'i"e some out$ut
In or"er to ha'e .e# Ser'ices coo$erate to $ro'i"e a greater "egree of ser'ice, there nee"s to #e a means of
s$ecifying the interaction of coo$erating ser'ices 3P0*7.S $ro'i"es this means It s$ecifies the or"er in which
Page 21 of 28
the we# ser'ices will #e in'oke" It $ro'i"es a mechanism for reco'ering from faults It $ro'i"es consistency an"
relia#ility for .e# ser'ice a$$lications F*eymann, >ollerG
3P0*7.S is #ase" on D2* A #usiness $rocess, a"e&uately "escri#e" in 3P0*, is e+ecuta#le #y a 3P0* engine,
,ust like a $rocess mo"ele" in 3P2* is e+ecuta#le #y a 3P2* engine A $rocess "efine" in 3P0* can inclu"e .e#
ser'ices from $artners that "o not use 3P0*
Figure 19 is an e+am$le of 3P0* from *eymann an" >oller
1 <process name="ticketOrder">

2 <partners>
3 <partner name="customer"
4 serviceLinkType="agentLink"
5 myRole="agentService"/>
6 <partner name="airline"
7 serviceLinkType="buyerLink"
8 myRole="ticketRequester"
9 partnerRole="ticketService"/>
10 </partners>
11 <containers>
12 <container name="itinerary" messageType="itineraryMessage"/>
13 <container name="tickets" messageType="ticketsMessage"/>
14 </containers>
15 <flow>
16 <links>
17 <link name="order-to-airline"/>
18 <link name="airline-to-agent"/>
19 </links>
20 <receive partner="customer"
21 portType="itineraryPT"
22 operation="sendItinerary"
23 container="itinerary"
24 <source linkName"order-to-airline"/>
25 </receive>
26 <invoke partner="airline"
27 portType="ticketOrderPT"
28 operation="requestTickets"
29 inputContainer="itinerary"
30 <target linkName"order-to-airline"/>
31 <source linkName"airline-to-agent"/>
32 </invoke>
33 <receive partner="airline"
34 portType="itineraryPT"
35 operation="sendTickets"
36 container="tickets"
37 <target linkName"airline-to-agent"/>
38 </receive>
39 </flow>
40 </process>
Figure -5 - B,E% E/amle
Fhtt$H==www51B:i#mcom="e'elo$erworks=we#ser'ices=li#rary=ws5#$elw$=G
Page 22 of 28
3P0* i"entifies a num#er of im$ortant conce$ts (he first is Partners Partners are e+ternal .e# ser'ices that an
organi%ation inclu"es in its own #usiness $rocess In the e+am$le a#o'e, customer an" airline are $artners of
the tra'el agency (he ne+t conce$t is that of 8ontainer 8ontainers are .S/* "escri$tions of the content that is
$asse" #etween $artners Acti'ities are the actions or tasks $erforme" within the #usiness $rocess 3P0* s$ecifies
se'eral ty$es of acti'itiesH
Urecei'eV wait for a message from a $artner
U$ickV wait for one of se'eral messages from $artner@sA
Uin'okeV call a we# ser'ice asynchronously
UwaitV wait for a certain amount of time
Uem$tyV "o nothing
UterminateV en" the $rocess
UthrowV throw a fault
UassignV assign fiel"s from one container into another container
UflowV "efine sets of acti'ities connecte" #y links
Usco$eV grou$ acti'ities an" assign them common characteristics
Use&uenceV s$ecify an acti'ity e+ecution or"er
UswitchV #ranch #etween acti'ities #ase" on 'alues in containers
UwhileV loo$ until a s$ecifie" con"ition is true
(he final conce$t i"entifie" in 3P0* is the i"ea of fault han"lers Fault han"lers catch faults when they are
thrown #y other actions (hey are $rocess "escri$tions in their own right, s$ecifying the actions to take when
things "o not go as $lanne"
3P0* is a 'ery com$lete s$ecification In reality, it is a $rogramming language In or"er to e+ecute a $rogram
written in 3P0*, one nee"s a 3P0* engine, an inter$reter Ene such engine is 8horeoSer'er from E$enStorm
Software (here are others Future research shoul" look into the ca$a#ilities an" limitations of these $ro"ucts
e+,M" BP&&
e#D2* is much like 3P0*7.S e+ce$t that it is not "esigne" s$ecifically for .e# ser'ices as "efine" #y the .68
e#D2* is, as the name suggests #ase" on D2* (he 3usiness Process S$ecification Schema @3PSSA is #uilt on
to$ of a num#er of stan"ar"s $romulgate" #y e#D2*org .e will not go into the "etails of yet another D2*
#ase" we# choreogra$hy s$ecification Suffice to say, you coul" "o 'irtually the same things with e#D2* 3PSS
that you can "o with 3P0*
ntologies
-ntologies and Process Modeling
An ontology is the set of conce$ts @or entitiesA in a "omain an" their relation to each other (he ontology will
"ocument the tags or la#els for these conce$ts, more commonly calle" the names of things It can #e
"ifficult, if not im$ossi#le, to create a com$lete an" cohesi'e #usiness $rocess when the names of things are not
accurate (wo common mistakes are when @aA the same name is use" for "ifferent things, an" @#A the thing is
calle" #y two or more "ifferent names 0'en more "ifficult to "eal with is when two conce$ts are close #ut not
i"entical) in other wor"s, their #oun"aries o'erla$ without one #eing a com$lete su#set of the other A formal
ontology can mitigate or eliminate these $ro#lems when mo"eling a #usiness $rocess
Jowe'er, many #usiness $rocesses will s$an multi$le "omains of "iscourse an" it coul" #e im$ossi#le to "e'elo$
an o'erarching ontology that s$ans these "omains Entologies are normally "e'elo$e" for a single "omain It
might #e $ossi#le to enforce a single ontology for se'eral "omains, #ut this is rarely successful when humans are
in'ol'e" (here is greater chance of success when the $rocess agents are all machines Jowe'er, there is rarely a
#usiness $rocess that "oes not at some $oint ha'e an interface to a human (he sa'ing grace coul" #e where the
Page 26 of 28
human5machine interface incor$orates a translation mechanism from the ontology of the #usiness $rocess to the
ontology of the human 3ut of course, this woul" re&uire that the translation "e'ice somehow gain knowle"ge of
the actual ontology for the human
Another "ifficulty arises when one #usiness $rocess must interact with another #usiness $rocess 0ach #usiness
$rocess coul" ha'e its ontology incom$ati#le with the neigh#oring $rocess-s ontology In this case, there coul" #e
stan"ar"i%e" ontology translator or there coul" #e a mechanism that somehow "isco'ers the ontology "ifferences
an" a",usts to match these "ifferences It is not clear that there is technology yet a'aila#le to $erform these tricks
of ontology integration mentione" here (here a$$ears to #e $lenty of room for research in this fiel" on
ontologies an" #usiness $rocess engineering
(here are some who claim to ha'e such technology rea"y an" a'aila#le for use (he I/0E4 tool is a unifie"
enter$rise ontology s$ecifically "esigne" to su$$ort integrate" $lanning an" e+ecution of enter$rise $rocesses
F2a"ni 2BB1G .hile other ontologies ha'e focuse" on enter$rise analysis an" re5engineering, I/0E4 is focuse"
on integrating an" managing $lanning an" e+ecution within colla#orati'e "istri#ute" enter$rises (he I/0E4
$ro"uct consists ofH @aA a set of O#usiness- o#,ects that re$resent common entities within an enter$rise conte+t) @#A
relations that link these o#,ects in s$ecific ways to esta#lish #usiness configurations) an" @cA #usiness rules that
go'ern the #eha'ior of 'arious #usiness configurations Fi#i"G (his all soun"s goo", #ut it is not clear from their
$a$er how this uniform ontology is im$ose" on all $artici$ants in a #usiness $rocess, es$ecially where this
#usiness $rocess s$ans across multi$le colla#orati'e "istri#ute" enter$rises, all of whom may alrea"y ha'e their
own $re5e+isting $rocesses with their res$ecti'e ontologies @almost guarantee" to #e "ifferent from the startA
-ntological Engineering and E.Business
It a$$ears that classical systems engineering an" #usiness $rocess re5engineering, while necessary, are not
sufficient (he e5#usiness market must "escri#e an" aggregate the $ro"ucts, ser'ices, $rocesses, an" $ractices
within the in"ustry into which it is attem$ting to interme"iate itself 8S8 refers to this as the information
architecture, or ontology, of the net marketK Entological engineering is the thir" ca$a#ility nee"e" if successful
net markets are to #e reali%e"K D2* stan"ar"i%ation efforts which "o not allow the rigorous of knowle"ge
engineering are unlikely to stan" the test of time FSmith 2BBBG
(he $ro#lem accor"ing to Smith is how to achie'e meaningful communication among a "i'erse set of enter$rise
systems, each of which is largely autonomous in #oth o$eration an" "esignK Enly enter$rise5centric ontologies,
that ca$ture the e+$erience of a #usiness, #eyon" their a#ility to su$$ly a $ro"uct or ser'ice to s$ec, will emerge as
a key "ifferentiator Some 323 $latform 'en"ors are referring to this as a #usiness ma$ a$$arently unwilling to
use the more technical term ontology Fi#i"G
0'en though $u#lic ontologies will #e im$ortant, the most 'alua#le ontologies will ca$ture enter$rise $ri'ate
$rocesses an" core com$etenciesK (hese strategic ontologies will ca$ture #oth the enter$rise-s $ri'ate $rocesses
an" com$etencies an" the way in which the enter$rise has chosen to interact with their $artners in #usiness we#s
Fi#i"G <i'en all this, it is unclear how all this strategic ontology can #e hi""en from the rest of the worl" unless
the #usiness $artners form a close" grou$ If they "o form a close" grou$, then this woul" seem that it will greatly
inhi#it the e5#usiness "ri'en e+$ansion of the market$lace It woul" limit the num#er of $artners that can #e
fol"e" into the we# of glo#al, 'irtual enter$rises
(he 3P2* accommo"ates #oth $ri'ate an" $u#lic #usiness $rocess mo"els (he $ri'ate section is ke$t hi""en
from #usiness $artners to allow that com$any to maintain a strategic a"'antage Accor"ing to Smith, the strategic
ontology woul" #e incor$orate" within this $ri'ate section of the mo"el 3ut the $u#lic interface woul" still nee"
to use terminology an" conce$ts that coul" #e foreign to @or misun"erstoo" #yA $otential #usiness $artners that are
not $ri'y to the $ro$rietary $art of the ontology It is not clear how the ontology will #e share" at the $u#lic
interface since there a$$ears to #e no mechanism within 3P2* to "eclare which ontology is #eing use" (here
is not a means to make the internal ontology, either $artly or wholly, 'isi#le to the outsi"e worl" (his a$$ears to
#e a ma,or flaw in the 3P2* scheme
Perha$s the solution is for the 3P2* to ha'e a mechanism for incor$orating, or referencing, the s$ecific ontology
rele'ant to that e5#usiness using something like E.* (he .e# Entology *anguage E.* is a semantic marku$
language for $u#lishing an" sharing ontologies on the .orl" .i"e .e# E.* is a 'oca#ulary e+tension of >/F
Page 27 of 28
@the >esource /escri$tion FrameworkA an" is "eri'e" from the /A2*WEI* .e# Entology *anguage
Fhtt$H==wwww6org=(>=owl5ref=G
Lin!ing "#$usiness to perating Processes
Inowle"ge management has a key role to $lay in linking e5#usiness an" o$erating $rocesses FFahey 2BB1G
(he new #usiness lan"sca$e ushere" in #y e5#usiness has re'olutioni%e" #usiness o$erations #ut, to
"ate, has not integrate" well with internal knowle"ge management initiati'esK 1n"erstan"ing how
e5#usiness im$acts these core $rocesses an" the su# $rocesses within them, an" then le'eraging that
knowle"ge to enhance these $rocesses, is key to an organi%ation-s success in "eri'ing su$erior
market$lace results F(heyG highlight the central role knowle"ge management $lays in "iagnosing
an" managing e5#usiness5"ri'en changes in organi%ationsK (he new technologies at the heart of e5
#usiness o$en u$ myria" $ossi#ilities not ,ust to reconsi"er the re5engineering of e+isting $rocesses
#ut also to "esign, "e'elo$, an" "e$loy fun"amentally new ways of concei'ing an" e+ecuting #usiness
$rocesses Fi#i"G
0'en though this $a$er ne'er mentions 3P2*, it is clear that 3P2* can $lay a crucial role in fun"amental new
ways of concei'ing an" e+ecuting #usiness $rocesses It is har" to imagine how this can #e "one with
con'entional $rocess mo"eling tools an" techni&ues Accor"ing to their $a$er, e5#usiness is resha$ing e'ery
tra"itional #usiness $rocessH from "e'elo$ing new $ro"ucts an" managing customer relationshi$s to ac&uiring
human resources an" $rocuring raw materials an" com$onents 3y ena#ling ma,or new tasks to #e a""e" to
in"i'i"ual $rocesses, e5#usiness #roa"ens their sco$e, content, an" 'alue5generating ca$a#ility Fi#i"G
Furthermore, e5#usiness $ro'i"es
the electronic means to ena#le connections among an" #etween $rocesses to take $lace in
fun"amentally new ways an" at such s$ee"s that it literally o$ens u$ the a#ility to ra"ically reconfigure
each core o$erating $rocess, to create new su# $rocesses within each core o$erating $rocess, an" to
ena#le new mo"es of integration across the o$erating $rocessesK Fan" knowle"ge managementG
facilitates an" gui"es such thinking #y ser'ing as a means to "esigning, managing, an" learning from
these new forms of e5#usiness5"ri'en $rocesses Fi#i"G
Inowle"ge management can clearly $ro'i"e the know5how in enhancing o$erating $rocesses #y looking at how e5
#usiness changes the lan"sca$e of the #usiness an" "ri'es it towar"s o$erating in a worl" where the #oun"aries of
the #usiness e+ten" #eyon" the $hysical #oun"aries of a single com$any After transforming the o$erating
$rocesses through knowle"ge management, then the sharing of information, i"eas, an" $ers$ecti'es @knowle"ge
flowA will increase the o'erall knowle"ge of the 'irtual enter$rise which results in e'en #etter, enhance" learning
for the larger 'irtual enter$rise An" this in turn lea"s to e'en more im$ro'e" o$erating $rocesses Jence the
synergy #etween e5#usiness an" o$erating $rocesses will ser'e to im$ro'e each in turn (he synergy can #e
le'erage" #y #etter $rocess mo"eling which can #e reali%e" #y such tools as 3P2* an" 3P24
Process Modeling and %e$ Services
.e# ser'ices $ro'i"e the means to enhance the ca$a#ilities of enter$rises in efficiently ser'ing their customers
.e# ser'ices also facilitate the creation of e5#usiness $rocesses that s$an across se'eral #usinesses to create a larger
'irtual enter$rise .e# ser'ices eliminate the nee" for com$anies to "e'elo$ their own ca$a#ilities Furthermore,
we# ser'ices can #e share" #y all com$anies in the e5#usiness 'alue chain in the "e'elo$ment of a cross5#usiness,
en"5to5en" set of #usiness $rocesses .hen we# ser'ices are share" it increases the "egree of com$ati#ility
#etween similar $rocesses $erforme" #y the se$arate #usinesses that share interfaces u$ an" "own the 'alue chain
Ene reason that greater com$ati#ility is achie'e" is #ecause we# ser'ices com$onents @ser'ice a$$lication an"
clientsA use generally acce$te" stan"ar"i%e" APIs to communicate at each le'el of the $rogramming stack
F<ottschalk 2BB2G .hen "ealing with .e# ser'ices, it is often "esira#le to automatically com$ose .e# ser'ices
into a workflow, aggregating se'eral sim$ler ser'ices into a higher5le'el ser'ice Fi#i"G
Page 29 of 28
For most non5tri'ial #usiness $rocesses, it is necessary to use #usiness $rocess mo"eling techni&ues to $erform this
aggregation of sim$ler ser'ices into a larger workflow to ser'e the goals of the #usiness It is one thing to
com$ose a new $rocess, #ut it is another thing to com$ose an efficient and effective $rocess 0fficiency an"
effecti'eness are usually achie'e" through mo"eling an" simulation of "ifferent alternati'e a$$roaches to
"etermine the #est a$$roach that meets the goals an" o#,ecti'es of that #usiness It is also im$ortant to test out
se'eral "ifferent com$eting we# ser'ices to "etermine which ones to use in the #usiness $rocess 1sing 3P2* can
enhance the a#ility of testing we# ser'ices an" integrating them into a cohesi'e whole that accom$lishes what
might otherwise ha'e #een im$ossi#le #y using the tra"itional a$$roach of integrating a$$lications an" har"
co"ing the $rocess in the a$$lications an" their interfaces
0'en though we# ser'ices are #ecoming more rea"ily a'aila#le an" co'er a #roa" range of ser'ices, their
wi"es$rea" e+$loitation awaits "e'elo$ment an" acce$tance of higher5le'el stan"ar"s in such areas as security,
relia#le messaging, transaction su$$ort, an" workflow Fi#i"G (he use of #usiness $rocess mo"eling an"
simulation can somewhat mitigate the lack of stan"ar"s #y "oing rigorous testing of the $rocesses for issues such as
security, workflow, an" so on
*e+ &er/ices for Business Process Design
(here are se'eral initiati'es un"erway to allow the use of D2* $rotocol to "escri#e how we# ser'ices can #e
integrate" into #usiness $rocesses D*A4< is an D2*5#ase" technology $ro$ose" #y 2icrosoft as a way to use
we# ser'ices for #usiness $rocess "esign F(hatte 2BB1G Another initiati'e #y I32 is "e'elo$ing a we# ser'ices
flow language F*eymann 2BB1G
.e# ser'ices #ase" on the ser'ice5oriente" architecture framework $ro'i"e a suita#le technical
foun"ation for making #usiness $rocesses accessi#le within enter$rises an" across enter$rises 3ut to
a$$ro$riately su$$ort "ynamic #usiness $rocesses an" their management, more is nee"e", namely, the
a#ility to $rescri#e how .e# ser'ices are use" to im$lement acti'ities within a #usiness $rocess, how
#usiness $rocesses are re$resente" as .e# ser'ices, an" also which #usiness $artners $erform what
$arts of the actual #usiness $rocess F*eymann2BB2G
(he a$$roach a"'ocate" #y *eymann in'ol'es the "e'elo$ment of a flow mo"el which shows the or"er in which
o$erations at a ser'ice $ro'i"er are to #e in'oke" (he flow mo"el can #e #uilt using the .e# Ser'ices
8on'ersation *anguage @.S8*A or #y techni&ues "e'elo$e" #y the .orkflow 2anagement 8oalition @.f28A
(he theoretical un"er$inning of this a$$roach is roote" in Petri 4ets an" the $i5calculus *anguages closer to the
latter are D*A4< an" 3P2* Fi#i"G
*eymann "escri#es how we# ser'ices woul" #e em$loye" to "esign an" #uil" a #usiness $rocessH
(he flow mo"el "escri#es the flow of control an" information #etween re&uesting an" $erforming
o$erations of the .e# ser'ice an" can #e use" #y #usiness $artners to figure out how they can interact
with the gi'en ser'iceN#oth as ser'ice re&uestors an" ser'ice $ro'i"ersK 3oth woul" "efine
ser'ices that they contri#ute to the com$osite #usiness $rocess an" flow mo"els that "efine the
#eha'ior of those ser'icesK (he two interacting #usiness $rocesses are sai" to ha'e a $eer5to5$eer
structureKthe e#D2* 3usiness Process S$ecification Schema $ro'i"es formalism for "efining
$u#lic stan"ar"s for $eer5to5$eer colla#orations Fi#i"G
(he higher le'el $rocess will s$an two or more #usiness $artners an" is not necessarily owne" #y any of the
$arties in'ol'e" It merely "efines the rules for coo$eration of the $artners in a O'irtual enter$rise,- thus
choreogra$hing the colla#oration #etween the $artners of this 'irtual com$any 3ecause of this, it is necessary to
ha'e a stan"ar"i%e" a$$roach for "esigning an" "ocumenting the o'erarching $rocess (his stan"ar" coul" #e
such things as I32-s .e# Ser'ices Flow *anguage @.SF*A or the 3P2* from the 3usiness Process 2anagement
Initiati'e It is unclear at this time whether .SF* or 3P2* is the #etter a$$roach
*e+ &er/ices and Business Process Management
It is im$ortant that the 3usiness Process 2anagement @3P2A a$$roach incor$orates we# ser'ices as a key element
to #e manage" in the o'erall acti'ity of managing the $rocesses
Page 2: of 28
3usiness $rocess management @3P2A is all a#out transferring the results of #usiness $rocess re5
engineering "iscusse" a#o'e into $ro"uction 3P2 technology $ro'i"es not only the tools an"
infrastructure to "efine, simulate, an" analy%e #usiness $rocess mo"els, #ut also the tools to
im$lement #usiness $rocesses in such a way that the e+ecution of the resulting software artifacts can
#e manage" from a #usiness $rocess $ers$ecti'e
(he 3P2 infrastructure $ro'i"es the run5time en'ironment for $u#lic an" $ri'ate $rocess mo"elsK
It allows users to monitor the e+ecution of in"i'i"ual $rocesses, to analy%e the o'erall #eha'ior of a
set of #usiness $rocesses, to 'erify their successful $erformance, an" to $ro'i"e in$ut for $rocess
o$timi%ation It is im$ortant to note that $u#lic an" $ri'ate $rocess mo"els are only half of a
com$lete #usiness $rocess reali%ation) the other half are ser'ices that im$lement the $rocess ste$s an"
theses ser'ices must #e manage" together with the $rocess mo"els F*eymann 2BB2G
(he ser'ices mentione" a#o'e can often #e $u#licly5a'aila#le we# ser'ices an" these we# ser'ices must #e
manage" along with the $rocess mo"el "etails #y the 3P2 tools an" techni&ues Ene of the tools a'aila#le for
"oing this is I32-s .e#S$here J200 @Ja'a 2 Platform, 0nter$rise 0"itionA (his tool $ro'i"es the #asic facilities
for im$lementing #usiness com$onents an" the tooling to make those ser'ices a'aila#le as .e# ser'ices Fi#i"G
.e# ser'ices can #e use" to im$lement the acti'ities in a #usiness $rocess an" these #usiness $rocesses can #e
e+ternali%e" as we# ser'ices for others to use Jence, you can ha'e a truly hierarchical a$$roach to #uil"ing large,
com$le+ e5#usiness $rocesses that s$an many com$anies to form 'irtual enter$rises As time goes on, there will #e
more we# ser'ices that gi'e you the look an" feel of a whole #usiness without all the usual #loo", sweat, an"
tears
Conclusion
Process mo"eling has #een aroun" a 'ery long time Ene hun"re" years ago it was mainly use" for manufacturing
$rocess flows In the 1?:Bs it was use" for com$uter $rogramming In the 1?8Bs it starte" to #e use" for
"escri#ing a #usiness $rocess It really came on strong in the mi"51?8Bs when (otal Cuality 2anagement
#ecame a hot to$ic in the #usiness worl" (hen it got a shot in the arm when 2ichael Jammer an" James 8ham$y
$ro"uce" their #ook calle" "eengineering the #orporation$ A Manifesto for Business "evolution
An" then came the Internet re'olution an" the notion of 05#usiness an" 05commerce in the 1??Bs (his re'olution
in the way to think a#out creating #usinesses an" creating 'irtual enter$rises "eman"e" a new way of mo"eling
the ways of "oing #usinessNin other wor"s there came a#out a stronger nee" for #usiness $rocess mo"eling
(his has recently come to fruition with the recent $u#lication of the 3usiness Process 2o"eling *anguage an"
4otation @3P2* an" 3P24A #y the 3usiness Process 2anagement Initiati'e It has also come to fruition with the
3P0*7.S an" with e#D2* 3PSS .hich of these solutions is #etterT Are they intero$era#leT .ill they all
sur'i'eT All goo" &uestions for future research
%or!s Cited
3aker, Jeanne, an" Ismael <halimi Q3P2* 1B1H Im$lementing the 3P2* S$ecificationQ 3P2Iorg 2BB1 2 Fe#
2BB6 Uhtt$H==www#$miorg=#$mi5li#rary=A2:;6/01763P2*X1B1$"fV
3iemans, FP2, et al Q/ealing with the 8om$le+ity of 3usiness Systems ArchitectingQ Systems 0ngineering 72
@2BB1AH 1185166
3ock, 8onra", an" Jean5Jac&ues /u#ray Jome Page Uhtt$H==wwwe#$mlorg=V
Page 2; of 28
3P2Iorg an" Assaf Arkin 3usiness Process 2o"eling *anguage 6B Jan 2BB6
Uhtt$H==www#$miorg=#$mlX$ro$es$V
3P2Iorg, 3usiness Process 2o"eling 4otation 6B Jan 2BB6 Uhtt$H==www#$miorg=#$mn5s$eces$V
3P2Iorg, (he 3usiness Process 2anagement Intiati'e 3P2I 2 Fe# 2BB6 Uhtt$H==www#$miorg=V
3rowning, (yson > QProcess Integration 1sing the /esign Structure 2atri+Q Systems 0ngineering 96 @2BB2AH
18B51?6
/ale, 4ell, an" John *ewis Enline Stu"ent *earning 8enter 8om$uter Science Illuminate"
Uhtt$H==csilluminate",#$u#com="i"youknowXcha$tercfmTcha$terY1BV
/ata Flow /iagramming A$$lie" Information Sciences Uhtt$H==wwwaisintlcom=case="f"htmlV
/efense Ac&uisition 1ni'ersity Systems %ngineering &undamentals' /efense Ac&uisition 1ni'ersity Press,
/ecem#er 2BBB
Fagerstrom, 3,orn, an" *ars50rik Elsson QInowle"ge 2anagement in 8olla#orati'e Pro"uct /e'elo$mentQ
Systems 0ngineering 97 @2BB2AH 2;75289
Fahey, *, et al Q*inking e5#usiness an" o$erating $rocessesH (he role of knowle"ge managementQ I32 Systems
Journal 7B7 @2BB1AH 88?5?B;
Fe"eral <rants Pilot Architecture 1? 2ar 2BB6 Uhtt$H==n"uknowle"genet="ocs=architecture=architecture5
$ilot=<rantsXPilotXArchitecturehtmV
<ottschalk, I, et al QIntro"uction to .e# ser'ices architectureQ I32 Systems Journal 712 @2BB2AH 1;B51;;
Ja#erl, Ste$hen 3usiness Process /esci$tion *anguages
Uhtt$H==wwwcisunisae"uau=Zcissh=research=we#flow=#$"lhtmlV
Jatley, /erek, Peter Jruschka an" Imtia% Pir#hai Process for System Architecture and "equirements
%ngineering' /orset Jouse Pu#lishing, 2BBB
Jome Page Uhtt$H==wwwall$mcom=article$h$Tsi"Y786V
Jome Page Uhtt$H==wwwcisunisae"uau=Zcissh=research=we#flow=#$"lhtmlV
Jome Page Uhtt$H==wwwe#+mlorg=V
Jome Page Inowle"ge 3ase" Systems Inc Uhtt$H==wwwi"efcom="efaulthtmlV
*eymann, F, / >oller, an" 2 ( Schmi"t Q.e# ser'ices an" #usiness $rocess managementQ I32 Systems Journal
712 @2BB2AH 1?85211
*eymann, F .e# Ser'ices Flow *anguage, I32 8or$oration @2BB1A
*eymann, Frank, an" /ieter >oller Jome Page Aug 2BB2 3usiness Process in a .e# Ser'ices .orl"
Uhtt$H==www51B:i#mcom="e'elo$erworks=we#ser'ices=li#rary=ws5#$elw$=V
*in, .eiwen, 8arla 8 2a"ni, an" A%a" 2 2a"ni QI/0E4H An 0+tensi#le Entology for /esigning, Integrating,
an" 2anaging 8olla#orati'e /istri#ute" 0nter$risesQ Systems 0ngineering 71 @2BB1AH 69578
2ilner, >o#in #ommunicating and Mo!ile Systems$ The Pi #alculus' 8am#ri"ge 1ni'ersity Press, 1???
>ing, Jack /isco'ering the Architecture for Pro"uct D, I48ES0 Sym$osium 2BB1
Sangiorgi, /a'i"e an" /a'i" .alker The Pi-#alculus ( A Theory of Mo!ile Processes' 8am#ri"ge Press, 2BB1
Smith, Jowar" an" Peter Fingar Business Process Management$ The Third Wave' 2eghan5Iiffer Press, 2BB6
Smith, Jowar" an" Peter Fingar Q3usiness Process 2anagement SystemsH 0n'ironmental PolicyQ Internet .orl"
2ay 2BB2 2B Fe# 2BB6 Uhtt$H==www#$miorg=#$mi5li#rary=286B1093FBI.53P2S50P52ayX2BB2$"fV
Smith, Jowar", Peter Fingar, an" Ismael <halimi 3usiness Process 2anagementH (he (hir" .a'e @#ook re'iewA
2B Fe# 2BB6 Uhtt$H==www#$miorg=#$mi5li#rary=8/FB;082?23P256r"wa'e$"fV
(hatte, S D*A4<N.e# Ser'ices for 3usiness Process /esign, 2icrosoft @2BB1AG
1sing <antt 8harts (he <antt <rou$ Uhtt$H==2B717718?;B=in"e+htmV
ther Re&erences
Page 28 of 28
QIntegrating 3usiness ProcessesQ Forrester >esearch 2ar 1??? 2B Fe# 2BB6
Uhtt$H==wwwforrestercom=0>=*ogin=8lient=1,6217,B,BBhtmlT
refererY=0>=>esearch=>e$ort=B,1668,9:;?,FFhtmlV
3en"%, Johan, an" Jarol" . *awson QA 2o"el for /e$loying *ife58ycle Process Stan"ar"s in the 8hange
2anagement of 8om$le+ SystemsQ Systems 0ngineering 72 @2BB1AH 1B;511;
3utler, /a'i", /oug 4eal, an" Jowar" Smith Q(he e'olution of #usiness $rocessesQ #$miorg 7 Fe# 2BB6
Uhtt$H==www#$miorg=#$mi5li#rary=8203/13B3/Fortuna.2BB1B6B1$"fV
8hung, J M, M Juang, an" S Iumaran QA framework5#ase" a$$roach to #uil"ing $ri'ate tra"ing e+changesQ I32
Systems Journal 712 @2BB2AH 29652;1
8o"y, . F, et al Q(he integration of #usiness intelligence an" knowle"ge managementQ I32 Systems Journal
717 @2BB2AH :?;5;16
Fingar, Peter, an" Jowar" Smith QA 4ew Path (o 3usiness Process 2anagementQ E$timi%e Ect 2BB2 9 Fe#
2BB6 Uhtt$H==www#$miorg=#$mi5li#rary=9860;1/;98E$timi%e52ag53P26$"fV
<halimi, Ismael, Pyke Jon, an" Jowar" Smith QProcess PioneersH 3usiness Process 2anagementQ Infoconomy
2BB2 2B Fe# 2BB6 Uhtt$H==www#$miorg=#$mi5li#rary=68?91A8F3FI85ProcessPioneers$"fV
<ieskes, Jose F, an" Ilse *angen#erg Q*earning an" Im$ro'ement in Pro"uct Inno'ation ProcessesH 0na#ling
3eha'iorsQ Systems 0ngineering 72 @2BB1AH 1675177
I'ester, >o#, an" 8raig Schlenoff A ro#ust $rocess ontology for manufacturing systems integration ontologyorg
1 Fe# 2BB6 Uhtt$H==ontologyorg=main=$a$ers=$slhtmlV
*ea'er, Sharon, an" (e" Scha"ler Q3P2* 1BH A Ste$ (owar" Process Intero$era#ilityQ Forrester >esearch 11
July 2BB2 9 Fe# 2BB6 Uhtt$H==wwwforrestercom=0>=>esearch=3rief=0+cer$t=B,161;,197B7,FFhtmlV
Smith, Jowar" QA System IntegratorPs Pers$ecti'e on 3usiness Process 2anagement, .orkflow, an" 0AIQ
8om$uter Science 8or$oration June 2BB2 2B Fe# 2BB6 Uhtt$H==www#$miorg=#$mi5
li#rary=221B88:B8S85SIP5J142BB2$"fV
Smith, Jowar" Q2aking 3usiness Processes 2anagea#leQ .e# Ser'ices Journal June 2BB2 8 Fe# 2BB6
Uhtt$H==www#$miorg=#$mi5li#rary=/7B92:139.SJ53P2>5Jun2BB2$"fV
Sowa, J F, an" J A !achman Q0+ten"ing an" Formali%ing the Framework for Information Systems
ArchitectureQ I32 Systems Journal 616 @1??2AH 9?B5:1:
!achman, J A QA Framework For Information Systems ArchitectureQ I32 Systems Journal 682R6 @1???AH 7975
7;B