01-1 modeling enterprise collaboration
TRANSCRIPT
8/3/2019 01-1 Modeling Enterprise Collaboration
http://slidepdf.com/reader/full/01-1-modeling-enterprise-collaboration 1/66
EDOC-ECA Class 21 April 2002
1Copyright © 2001-2002, Data Access Technologies, Inc.
Model ing Ent erpr ise
Col laborat ion
A tutorial on applying Model Driven Architectureusing the OMG Enterprise Collaboration
Architecture with UML
Enterprise
Collaboration
Architecture
In t roduc t ions
Cory [email protected]
Primary author of “CCA” in EDOC
8/3/2019 01-1 Modeling Enterprise Collaboration
http://slidepdf.com/reader/full/01-1-modeling-enterprise-collaboration 2/66
EDOC-ECA Class 21 April 2002
2Copyright © 2001-2002, Data Access Technologies, Inc.
Copyright © 2000-2002, Data Access Technologies, Inc.
What is t he Ent erpr ise
Col labora t ion Arch i t ec t ure?
❚ ECA is a “profile of UML”, a way to use UML for aspecific purpose - it is an OMG standard❙ That purpose is modeling enterprise systems .
❚ You can also think of this as a “modeling framework” forenterprise computing
❚ ECA is part of the “Model Driven Architecture” (MDA)initiative of the OMG❙ Using precise modeling techniques as part of the development
lifecycle to speed development and provide technology
independence❚ ECA has been adopted by the OMG as part of the EDOC
RFP.
The Agi le Ent erpr ise
Has a compe t i t i ve
advantage in it s capab i l it y
t o embrac e c o l labora t ion
and change
8/3/2019 01-1 Modeling Enterprise Collaboration
http://slidepdf.com/reader/full/01-1-modeling-enterprise-collaboration 3/66
EDOC-ECA Class 21 April 2002
3Copyright © 2001-2002, Data Access Technologies, Inc.
Copyright © 2000-2002, Data Access Technologies, Inc.
In tegrat ing Enterpr ises, People &
Sys tems - Wor ldw ide
Integrat ing Enterpr ises, People &
Sys tems - Wor ldw ide
Using InternetTechnologies
Enabling e
Copyright © 2000-2002, Data Access Technologies, Inc.
In tegrat ing Enterpr ises, People &Sys tems - Wor ldw ideIntegrat ing Enterpr ises, People &Sys tems - Wor ldw ide
❚ Business Requirements
❙ Virtual Enterprises
❙ Enterprise Integration (EAI)
❙ Supply-chain automation (B2B)
❙ Customer Integration (B2B)❙ Web deployment (B2C)
❙ Internet Marketplace (B2C)
❚ Collaboration and Integration
8/3/2019 01-1 Modeling Enterprise Collaboration
http://slidepdf.com/reader/full/01-1-modeling-enterprise-collaboration 4/66
EDOC-ECA Class 21 April 2002
4Copyright © 2001-2002, Data Access Technologies, Inc.
Copyright © 2000-2002, Data Access Technologies, Inc.
The dynam ic real i t y
❚ The information system must facilitate;
❙ Rapid realization of business goals
❙ Integration of independent processes and systems
❙ Multiple and Changing
❘ business requirements
❘ business processes
❘ technologies
❘ standards
❘ enterprise boundaries
❘ partners
Copyright © 2000-2002, Data Access Technologies, Inc.
Tec hnology St ew
❚ Web services
❚ .NET
❚ C’
❚ XML
❚ EAI❚ Active Web pages
❚ EJB
❚ Java Beans
❚ Java
❚ Corba
❚ MQ-Series
❚ C++
❚ SQL
❚ Cobol
❚ IMS❚ CICS
❚ ...
Technology is transient, but we
must embrace and adapt to it to
provide meet current requirements
8/3/2019 01-1 Modeling Enterprise Collaboration
http://slidepdf.com/reader/full/01-1-modeling-enterprise-collaboration 5/66
EDOC-ECA Class 21 April 2002
5Copyright © 2001-2002, Data Access Technologies, Inc.
Copyright © 2000-2002, Data Access Technologies, Inc.
Problems t o be so lved
❚ Integration Nightmare
❚ Infrastructure, Version & Vendor lock-in
❚ Complex, divergent and manualdevelopment and deployment processes
❚Typical solutions require buy-in (Lock-in) to expensive, pervasive and proprietary infrastructure
Copyright © 2000-2002, Data Access Technologies, Inc.
Goals
❚ A scalable and robust enterprise architecture
❚ Loosely coupled enterprise components
❚ Enable rapid provisioning of business solutions❙ Simple, reproducible processes supporting reuse
❚ Technology & vendor independence
❚ Enable the integration and collaboration of multiple;❙ Business units (internal and external)
❙ Customers
❙ Suppliers
❙ Systems
❙ Technologies
8/3/2019 01-1 Modeling Enterprise Collaboration
http://slidepdf.com/reader/full/01-1-modeling-enterprise-collaboration 6/66
EDOC-ECA Class 21 April 2002
6Copyright © 2001-2002, Data Access Technologies, Inc.
Copyright © 2000-2002, Data Access Technologies, Inc.
Model Driven
Development
Solut ion Tr iad
Service Based
Architecture
Standards
Tooling & Infrastructure
Development Process
Components
WebServicesCorba
OMGECA
J2EE.NET
Copyright © 2000-2002, Data Access Technologies, Inc.
The new c ent e r
❚ The strategic core of you systems must be thebusiness its self
❚ Only technology independent business focusedmodels will survive the transience of technology
and lock-in❚ These models can become part of your source
code , driving enterprise applications
❚ Enabler: Model Driven Architecture (MDA) withEDOC-ECA
Extreme Modeling Extreme Modeling
8/3/2019 01-1 Modeling Enterprise Collaboration
http://slidepdf.com/reader/full/01-1-modeling-enterprise-collaboration 7/66
EDOC-ECA Class 21 April 2002
7Copyright © 2001-2002, Data Access Technologies, Inc.
Copyright © 2000-2002, Data Access Technologies, Inc.
Business & Techno logy
Coupl ing
“Open B2B”
Ad-hoc business
“Community B2B” -
Business Partners &
Independent Divisions
Integration within a
managed domain
Integration or
production
of an application
Internet
Computing
Model
ebXML
Soap Events &
Messaging
JMS
MQ-Series
Synchronous
Transactional
RPC
Corba
EJB
SharedData
SQL
IMS-DB
Collaborative
Components
EDOC
Model
(UML)
Traditional
EDI
Copyright © 2000-2002, Data Access Technologies, Inc.
Col laborat ive Vs. Managedbusiness proc esses
❚ The enterprise collaboration architecture isintended for collaborative business processes
❙ People, departments, systems and enterprisesworking together within a defined process
❚ Contrast with the managed business process❙ A central authority directs the activities of others
❚ Both have their place
❙ Collaborative - B2B, EAI
❙ Managed - Fine-grain business processes - factories
8/3/2019 01-1 Modeling Enterprise Collaboration
http://slidepdf.com/reader/full/01-1-modeling-enterprise-collaboration 8/66
EDOC-ECA Class 21 April 2002
8Copyright © 2001-2002, Data Access Technologies, Inc.
Copyright © 2000-2002, Data Access Technologies, Inc.
Col laborat ive Business Proc esses
Independent actors
working within a
defined process
No central
authority
Copyright © 2000-2002, Data Access Technologies, Inc.
Managed Business Proc esses
Someone or something
keeps track of everything
8/3/2019 01-1 Modeling Enterprise Collaboration
http://slidepdf.com/reader/full/01-1-modeling-enterprise-collaboration 9/66
EDOC-ECA Class 21 April 2002
9Copyright © 2001-2002, Data Access Technologies, Inc.
Copyright © 2000-2002, Data Access Technologies, Inc.
Col laborat ion is K ey
❚ Collaboration is a key differentiation and key cost center(Healthcare Example)❙ Customer Collaboration
❙ Claim processing
❙ Disputes
❙ Physician Collaboration
❙ Payer Collaboration
❙ Hospital Collaboration
❙ Broker Collaboration
❙ Government Collaboration❙ Employee Collaboration
❙ Others...
The system
integrates multiple
collaborations
Copyright © 2000-2002, Data Access Technologies, Inc.
AutomatedModel Dr iven Arc h i t ec t ure
ProfileProfile
(E.G. EDOC)(E.G. EDOC)
Framework &Framework &
InfrastructureInfrastructure(E.G.(E.G. ebXMLebXML))
InfrastructureInfrastructure
MappingMapping
(E.G.(E.G. ebXMLebXML))
Mapping is tunedMapping is tuned
to the infrastructureto the infrastructure
ToolsTools
Produce &Produce &
IntegrateIntegrate
EnterpriseEnterprise
ComponentsComponents
Business FocusedBusiness Focused
Model (UML)Model (UML)
Minimize and structure
manual implementation
C
8/3/2019 01-1 Modeling Enterprise Collaboration
http://slidepdf.com/reader/full/01-1-modeling-enterprise-collaboration 10/66
EDOC-ECA Class 21 April 2002
10Copyright © 2001-2002, Data Access Technologies, Inc.
Copyright © 2000-2002, Data Access Technologies, Inc.
EDOC St ruc t ure
ECAEntities Process
Events
Platform Specific ModelsPlatform Specific Models
RelationshipsCCA
Integration -
viewpoints
etc
FCMFCM
ebXMLebXML
Patterns
Platform Independent ModelsPlatform Independent ModelsPlatform Independent ModelsTechnologymappings
EJBEJBCORBACORBA COMCOMMOMMOM
Enterpr ise Arch i t ec t ure
How t o s li ce and d i ce
8/3/2019 01-1 Modeling Enterprise Collaboration
http://slidepdf.com/reader/full/01-1-modeling-enterprise-collaboration 11/66
EDOC-ECA Class 21 April 2002
11Copyright © 2001-2002, Data Access Technologies, Inc.
Copyright © 2000-2002, Data Access Technologies, Inc.
Loose Coupl ing
❚ Loose coupling is the ability for independentparts of systems to be built and evolveindependently
❚ Tightly coupled systems
❙ Prevent change (the next legacy system)
❙ Cause lock-in
❙ Become unmanageable
❙ Prevent reuse
❚ Quality architecture is essential for loosecoupling
Copyright © 2000-2002, Data Access Technologies, Inc.
Arch i t ec t ure Goa ls
❚ Create a system from loosely coupled “enterprisecomponents” that can evolve independently
❚ Provide well defined interfaces and interaction pointsbetween these enterprise components
❚ Make each enterprise component a reusable asset thatcan serve many business processes
❚ Build the information system as a community of interacting enterprise components
❚ Utilize open standards such as XML, EJB and Corba tointegrate the enterprise components
8/3/2019 01-1 Modeling Enterprise Collaboration
http://slidepdf.com/reader/full/01-1-modeling-enterprise-collaboration 12/66
EDOC-ECA Class 21 April 2002
12Copyright © 2001-2002, Data Access Technologies, Inc.
Copyright © 2000-2002, Data Access Technologies, Inc.
Ent erpr ise Com ponent s
❚ EnterpriseComponents must beindependent
❚ While being able tointeroperate witheach other
❚ Making theinformation system alattice of cooperatingcomponents
OpenStandards
O p e n S t a n d a r d s
O p e n
S t a
n d a r d
s
Copyright © 2000-2002, Data Access Technologies, Inc.
Poor Monol i t h icA rch i tec tu rePoor Monol i t h icA rch i tec tu re
Traditional datasources
SQL DBMS &
Client/Server
BadThing
All business rules, data rules,application logic, technology and userinterface code are contained here
The data goes here
MonolithicApplications
MonolithicApplicationsHTTP
Web
Browser
Making a monolithic webapplication doesn’t help!
8/3/2019 01-1 Modeling Enterprise Collaboration
http://slidepdf.com/reader/full/01-1-modeling-enterprise-collaboration 13/66
EDOC-ECA Class 21 April 2002
13Copyright © 2001-2002, Data Access Technologies, Inc.
Copyright © 2000-2002, Data Access Technologies, Inc.
HTTP Web ServerApplications
Ent erpr ise Arc h i tec t ureEnt erpr ise Arc h i tec t ure
SQL DBMS,Client/Server
& LegacyApplications
ClientApplications
Business and datarules go here
User interface andapplication logic gohere
The datagoes here
EAI Applications &B2B E-Commerce
WebBrowser
Standard Middlewareconnects applicationsto components &components tocomponents
XMLCorbaEJB
DCOMMQ
Supply Chain
EnterpriseComponents
Copyright © 2000-2002, Data Access Technologies, Inc.
“ Wrapping” Legac yAppl icat ions and Dat a“ Wrapping” Legac yAppl icat ions and Dat a
❚ Enterprise Components are defined in terms of their external contract; implementation may useexisting applications
❙ Can “call” existing application
❙ Can read and write legacy DBMS❙ Can use “screen scraper” (Last resort)
❚ Legacy applications can appear as enterprisecomponents but may not be implemented ascomponents
8/3/2019 01-1 Modeling Enterprise Collaboration
http://slidepdf.com/reader/full/01-1-modeling-enterprise-collaboration 14/66
EDOC-ECA Class 21 April 2002
14Copyright © 2001-2002, Data Access Technologies, Inc.
Copyright © 2000-2002, Data Access Technologies, Inc.
Legacy “ Wrapping”Legacy “ Wrapping”
Wrapping allows existing programsWrapping allows existing programs
and data to work with and workand data to work with and work
as enterprise componentsas enterprise components
Ad a p t e r s
Copyright © 2000-2002, Data Access Technologies, Inc.
What the infrastructure
vendors would
have you do
Tec hnology Independenc e
Business
Logic
Component
ebXmlBusiness
Logic
Component
.NETBusiness
Logic
Component
RosetaNetBusiness
Logic
Component
Ejb
Adapters
EJB
Business
Logic
Component
ebXml
BizTalk
Rosetanet
Adapters
CICS
EJB
MQ
Corba
8/3/2019 01-1 Modeling Enterprise Collaboration
http://slidepdf.com/reader/full/01-1-modeling-enterprise-collaboration 15/66
EDOC-ECA Class 21 April 2002
15Copyright © 2001-2002, Data Access Technologies, Inc.
Copyright © 2000-2002, Data Access Technologies, Inc.
Typic a l Requi rem ent
B2B
Buyer
Web
Service Seller
Buyer
Web PageHTML Seller
Redundant
Work!
Copyright © 2000-2002, Data Access Technologies, Inc.
B2B
Buyer
Mult i -t ie r im p lem enta t ion
Buyer
Web PageHTML
Buyer
Proxy
Web
ServiceSeller
Could have
multiple
implementations
using different
technologies
Could have
multiple
implementations
using different
technologies
8/3/2019 01-1 Modeling Enterprise Collaboration
http://slidepdf.com/reader/full/01-1-modeling-enterprise-collaboration 16/66
EDOC-ECA Class 21 April 2002
16Copyright © 2001-2002, Data Access Technologies, Inc.
Copyright © 2000-2002, Data Access Technologies, Inc.
Legacy
Seller
Applications
Event Cloud
B2B
Buyer
Mult i -t ie r im p lem enta t ion
Buyer
Web PageHTML
Buyer
Proxy
Web
Service Seller
EventEvent
Implementing sellerusing events
Model Driven Architectures
In t egrat ing and
Aut om at ing Design To
execu t i on
8/3/2019 01-1 Modeling Enterprise Collaboration
http://slidepdf.com/reader/full/01-1-modeling-enterprise-collaboration 17/66
EDOC-ECA Class 21 April 2002
17Copyright © 2001-2002, Data Access Technologies, Inc.
Copyright © 2000-2002, Data Access Technologies, Inc.
MDA Overview
❚ Modeling has evolved
❙ Its not just pictures anymore
❚ Use high level UML models made precise withprofiles
❚ With technology specific mappings
❚ Define and produce substantial parts of the
executable system
Copyright © 2000-2002, Data Access Technologies, Inc.
Models and m apping
map
Platform-specificartifacts (IDL/DTD)
PlatformIndependent
Model
Versionedrepository
BusinessModel
•UML/CORBA•UML/EJB•XML
•OAG•SOAP•ebXml•RosettaNet
•Legacy
Management
Over Time
8/3/2019 01-1 Modeling Enterprise Collaboration
http://slidepdf.com/reader/full/01-1-modeling-enterprise-collaboration 18/66
EDOC-ECA Class 21 April 2002
18Copyright © 2001-2002, Data Access Technologies, Inc.
Copyright © 2000-2002, Data Access Technologies, Inc.
Ways t o m ap
❚ Generate code and other artifacts❙ Usually required to adapt to legacy
❙ Emulates the manual process
❚ Assemble and configure existing generic andspecific components❙ Both efficient and dynamic
❚ Interpret or otherwise “animate” the high-level
model❙ High level & dynamic but may have performance
issues
Copyright © 2000-2002, Data Access Technologies, Inc.
Ex ample Genera ted Ar t i fac t s
Implementation Artifacts (EJB Examples)
Java Source
Class Objects
Stubs, Skeletons,Helpers, Holders,
Interfaces
Jars,Wars,Ears
BeanInfo,Editors..
Business ObjectImplementation
Logic
Homes,Managers,
Primary Keys
SQL
Descriptors
Documentation
M0/M1 XMI/DTD
Serialization,Persistence
Management
Artifact generation involves multiple tools•EJB Container provider;Deployment tools;Packagers;•java development tools(IDE);persistence provider;…Typical 10-20 per PIM Classifier0-20% manual override
8/3/2019 01-1 Modeling Enterprise Collaboration
http://slidepdf.com/reader/full/01-1-modeling-enterprise-collaboration 19/66
EDOC-ECA Class 21 April 2002
19Copyright © 2001-2002, Data Access Technologies, Inc.
Copyright © 2000-2002, Data Access Technologies, Inc.
PIM
Reverse Enginee r ing
modelnavigation
process
disposition
algorithms
Production ruleengine
Native artifacts
•Native meta-model is platform-specific
•XML DTD/Schema; java introspection; SQL tables; legacy model; etc.
•Map navigates the native meta-model, populates PIM
•Limited semantic recovery
•Information and middleware models work best
Copyright © 2000-2002, Data Access Technologies, Inc.
MDA and Com ponent s
PlatformIndependent
Model
BusinessModel
Assemble &
Execute Components
Enabled but not required
8/3/2019 01-1 Modeling Enterprise Collaboration
http://slidepdf.com/reader/full/01-1-modeling-enterprise-collaboration 20/66
EDOC-ECA Class 21 April 2002
20Copyright © 2001-2002, Data Access Technologies, Inc.
Copyright © 2000-2002, Data Access Technologies, Inc.
What c an w e au tom ate?
Model
Mappings
Technology Infrastructure
Process & Data Integrationrules
ProgrammerInternal business logicLegacy integration30% to 5%
EnterpriseCollaboration
Sum m ary of MDA benef i t s
❚ Isolates domain specifications from platform details❙ Reduces complexity
❙ Preserves domain model semantics
❙ Increases stability and lifetime
❙ Generates to platform/legacy of choice
❚ Decreased development time❙ fast iterative development
❙ separation between the engineering and business requirements
❚ Increased quality.
❚ Builds on industry directionsDomainDomain
SpecificationsSpecifications
MDAMDA
UsersUsers
8/3/2019 01-1 Modeling Enterprise Collaboration
http://slidepdf.com/reader/full/01-1-modeling-enterprise-collaboration 21/66
EDOC-ECA Class 21 April 2002
21Copyright © 2001-2002, Data Access Technologies, Inc.
Col laborat ions and Roles
Portions copied with permission of Trygve
Reenskaug - Taskon
(http://www.ifi.uio.no/~trygver)
OORAM
Conceptual Foundation
Copyright © 2000-2002, Data Access Technologies, Inc.
His tory
OORAM
Object Oriented
Role Analysis
UML
Collaborations
Enterprise
Collaboration
Architecture
Influence
8/3/2019 01-1 Modeling Enterprise Collaboration
http://slidepdf.com/reader/full/01-1-modeling-enterprise-collaboration 22/66
EDOC-ECA Class 21 April 2002
22Copyright © 2001-2002, Data Access Technologies, Inc.
Copyright © 2000-2002, Data Access Technologies, Inc.
The Connec t ed Ent erpr iseConten t and Comm unic a t ion
Aerial
Photos
Digital
Map
CensusData
HouseDrawings
PoliceRecords
Police
DispatcherRole
Copyright © 2000-2002, Data Access Technologies, Inc.
Mul t ip le ro les in a co l laborat ion
8/3/2019 01-1 Modeling Enterprise Collaboration
http://slidepdf.com/reader/full/01-1-modeling-enterprise-collaboration 23/66
EDOC-ECA Class 21 April 2002
23Copyright © 2001-2002, Data Access Technologies, Inc.
Copyright © 2000-2002, Data Access Technologies, Inc.
Implementation
Net
Hardware
Operating
System
Framework,
Middleware
& Container
Roles t o Syst em s
Interaction Path
Component in Role
Interaction (With Information)
Role
Collaboration
Copyright © 2000-2002, Data Access Technologies, Inc.
Travel Expense Example
1: travelPermissionReques 2: travelPermission
3: expenseReport
4: authorizedExpenseReport
5: paymentRequest
Peter(Technical author)
Bill(Dispatcher)
Joyce
(Sales clerk)
Douglas(Marketing manager)
Kim(Methodologist)
Elsie
(Programmer)
Eve(Software Manager)
Bill(Bookkeeper)
Joe
(Paymaster)
Adam(Chief Accountant)
Ruth(President)
John(Cashier)
Ann(Customer consultant)
8/3/2019 01-1 Modeling Enterprise Collaboration
http://slidepdf.com/reader/full/01-1-modeling-enterprise-collaboration 24/66
EDOC-ECA Class 21 April 2002
24Copyright © 2001-2002, Data Access Technologies, Inc.
Copyright © 2000-2002, Data Access Technologies, Inc.
Peter(Technical author)
Bill(Dispatcher)
Joyce(Sales clerk)
Douglas(Marketing manager)
Kim(Methodologist)
Elsie(Programmer)
Eve(Software Manager)
Bill(Bookkeeper)
Joe(Paymaster)
Adam(Chief Accountant)
Ruth(President)
John(Cashier)
Ann(Customer consultant)
DiagramTravel Expense Model
/ Paymaster
/ BookKeeper/ Traveler
/ Authorizer
Objects --> ClassifierRoles
Copyright © 2000-2002, Data Access Technologies, Inc.
Col laborat ion Diagram
Traveler Authorizer Book
Keeper
Paymaster
8/3/2019 01-1 Modeling Enterprise Collaboration
http://slidepdf.com/reader/full/01-1-modeling-enterprise-collaboration 25/66
EDOC-ECA Class 21 April 2002
25Copyright © 2001-2002, Data Access Technologies, Inc.
Copyright © 2000-2002, Data Access Technologies, Inc.
Travel Perm ission Dec is ionTravel Expense System
Traveler Peter Period week 11 Planned cost USD 2000.-
Purpose Attend TOOLS Europe 2001
Current plan for Peter
activity 1activity 2activity 3
week 10 11 12 13 14 15
Budget + commitments
Item Budget Committed
Travel 10,000 4,000
RejectPermit
Copyright © 2000-2002, Data Access Technologies, Inc.
Synthes is - Component splay several ro les
ProjectManager ProjectParticipant
ProjectParticipantProjectManager
Jane
8/3/2019 01-1 Modeling Enterprise Collaboration
http://slidepdf.com/reader/full/01-1-modeling-enterprise-collaboration 26/66
EDOC-ECA Class 21 April 2002
26Copyright © 2001-2002, Data Access Technologies, Inc.
Copyright © 2000-2002, Data Access Technologies, Inc.
Disc ussion Point
❚ What are other ways of representing businesssemantics?
❚ What role do these play?
❙ Business Processes
❙ Information Models (DBMS)
❙ Events
❙ Workflow
❙ Internet
❚ What is used internally?
St andards for Global
In ternet Comput ing
EDOCEDOCEDOC
SOAP
WSDL
XML
XML-Schema
.NET BPML
XLANG
8/3/2019 01-1 Modeling Enterprise Collaboration
http://slidepdf.com/reader/full/01-1-modeling-enterprise-collaboration 27/66
EDOC-ECA Class 21 April 2002
27Copyright © 2001-2002, Data Access Technologies, Inc.
Copyright © 2000-2002, Data Access Technologies, Inc.
XML St andards
❚ XML Schema & DTD
❙ Description and packaging of data
❚ WSDL
❙ Specification a services, operations and flowsavailable via that service
❚ Soap
❙ Basic messaging and packaging
❙ Extensions for Soap-RPC with WSDL
❙ May be extended to support collaborative messaging
Copyright © 2000-2002, Data Access Technologies, Inc.
Vision
❚ EDOC (a UML Profile)❙ Provide an architecture for open collaborative computing
❙ Simplify the development of component based distributedsystems by means of a modeling framework, based on UML 1.4
❙ Provide a platform independent, recursive collaboration basedmodeling approach supporting multiple technologies.
❙ Embrace Model Driven Architectures (MDA) – Provide designand infrastructure models and mapping
❚ ebXML❙ Creating a single global electronic market
❘ Includes process specification, transport and repositories
❘ Collaboration Oriented
8/3/2019 01-1 Modeling Enterprise Collaboration
http://slidepdf.com/reader/full/01-1-modeling-enterprise-collaboration 28/66
EDOC-ECA Class 21 April 2002
28Copyright © 2001-2002, Data Access Technologies, Inc.
Copyright © 2000-2002, Data Access Technologies, Inc.
J SR 159
❚ Java Process Components
❚ Uses ECA (CCA) as the baselinecomponent model
❚ Asynchronous document exchange
❚ Component composition
❚ A J2EE technology mapping for ECA
❚ Will make J2EE an excellent integrationand web services platform
Copyright © 2000-2002, Data Access Technologies, Inc.
ebXML & EDOC
Transport
Distribution
Repository
Runtime
Enterprise
Integration
Components
Information
Model
MDA
Collaboration
Process Model
ebXML EDOC
8/3/2019 01-1 Modeling Enterprise Collaboration
http://slidepdf.com/reader/full/01-1-modeling-enterprise-collaboration 29/66
EDOC-ECA Class 21 April 2002
29Copyright © 2001-2002, Data Access Technologies, Inc.
Copyright © 2000-2002, Data Access Technologies, Inc.
ECA as t he norm al form
EDOC-ECA
Web Services(WSDL)
ebXML(BPSS)
J2EE(Java RMI)
.NET
MOM(MQ-Series)
The standard way to modeland tool for multiple
technologies
MDAMappings
Copyright © 2000-2002, Data Access Technologies, Inc.
Sum m ary of po int s t hus far
❚ We must enable the emerging Internet Computing Model
❙ Loosely coupled roles exchanging documents based on a contract of collaboration
❚ Web need interoperability at two levels❙ Messaging for the data
❙ Metadata for the contract of collaboration, stored in repositories
❚ This model of collaborating roles is recursive, extending into theenterprise, into managed domains and into applications❙ Inside the enterprise we want to include resources entities, business
events and business processes
❚ Supporting the open domain has some required parts and can beaugmented with a “treasure chest” of tools and infrastructure
❚ Between EDOC & ebXML we are covering B2B and intra enterprise
8/3/2019 01-1 Modeling Enterprise Collaboration
http://slidepdf.com/reader/full/01-1-modeling-enterprise-collaboration 30/66
EDOC-ECA Class 21 April 2002
30Copyright © 2001-2002, Data Access Technologies, Inc.
Bac k t o EDOC
How t o rea l i ze g lobal
co l labora t ions
EDOC Com ponent
Col labora t ion Arch i t ec t ure
The mode l o f
co l labora t i vew o r k
8/3/2019 01-1 Modeling Enterprise Collaboration
http://slidepdf.com/reader/full/01-1-modeling-enterprise-collaboration 31/66
8/3/2019 01-1 Modeling Enterprise Collaboration
http://slidepdf.com/reader/full/01-1-modeling-enterprise-collaboration 32/66
EDOC-ECA Class 21 April 2002
32Copyright © 2001-2002, Data Access Technologies, Inc.
Copyright © 2000-2002, Data Access Technologies, Inc.
Part s of a CCA
Spec i f i ca t ion
❚ Structure of process components and protocols
❙ Process components, ports, protocols and documents
❘ Class Diagram or CCA Notation
❚ Composition of process components
❙ How components are used to specify components
❘ Collaboration diagram or CCA Notation
❚ Choreography
❙ Ordering of flows and protocols in and betweenprocess components
❘ Activity Diagram
Copyright © 2000-2002, Data Access Technologies, Inc.
The Com m uni ty Proc ess
❚ Identify a “community process”, the roles andinteractions in a collaboration
Buyer Seller
BuySell CommunityProcess
Buy Sell
Shipper
ShipDelivery
ShipDelivery
Protocol
8/3/2019 01-1 Modeling Enterprise Collaboration
http://slidepdf.com/reader/full/01-1-modeling-enterprise-collaboration 33/66
EDOC-ECA Class 21 April 2002
33Copyright © 2001-2002, Data Access Technologies, Inc.
Copyright © 2000-2002, Data Access Technologies, Inc.
Protocol OrderBT
OrderDenied
OrderConfirmationOrder
responderRoleSeller
initiatorRoleBuyer
Protoco ls
<<initiates>> Order
<<responds>> OrderDenied <<responds>> OrderConfirmation
Failure Success
Copyright © 2000-2002, Data Access Technologies, Inc.
Composi t ion
8/3/2019 01-1 Modeling Enterprise Collaboration
http://slidepdf.com/reader/full/01-1-modeling-enterprise-collaboration 34/66
EDOC-ECA Class 21 April 2002
34Copyright © 2001-2002, Data Access Technologies, Inc.
ECA Ent i t y Prof i le
The mode l o f t h ings
Data Inside a “shared domain”
Copyright © 2000-2002, Data Access Technologies, Inc.
Adding Ent i t ies
❚ Entities are added to manageentity data
❚ Entity Roles are managers thatprovides a view of the sameidentity in another context
❚ The Entities have ports formanaging and accessing theentities
❚ Non-entities which are ownedby (aggregate into) an entityare managed by the entity
+Street : String+City : String+State : String+Zip : String
«EntityData»Addtress
+Cust
1
+Adr
1..*
+Name : String+Balance : Decimal = 0+AccountNo : long
«EntityData»Account
+AccountNo : String
«Key»AccountKey
-.
1
-.
1
+Name : String-CompanyId : String
«EntityData»Company
+CompanyId : String
«Key»CompanyKey
-.
1
-.
1
.Manages
<<Entity>>CompanyManager
Manage
<<EntityRole>>AccountManager
Manage
-Manages1
-.1
8/3/2019 01-1 Modeling Enterprise Collaboration
http://slidepdf.com/reader/full/01-1-modeling-enterprise-collaboration 35/66
EDOC-ECA Class 21 April 2002
35Copyright © 2001-2002, Data Access Technologies, Inc.
ECA Business Event s
The mode l of w hen…
Loosely coupled integration within
the enterprise and with “aligned”business partners
Copyright © 2000-2002, Data Access Technologies, Inc.
Business
Process
Business
Entity
Business
Rules
Business
Events
Business
Actions
Business
Process
Business
Entity
Business
Rules
Business
Events
Business
Actions
Event Based Business Processes
Event
Notification
8/3/2019 01-1 Modeling Enterprise Collaboration
http://slidepdf.com/reader/full/01-1-modeling-enterprise-collaboration 36/66
EDOC-ECA Class 21 April 2002
36Copyright © 2001-2002, Data Access Technologies, Inc.
Copyright © 2000-2002, Data Access Technologies, Inc.
App
Business
Process
Business
Entity
Business
Rules
Business
Events
Business
Actions
App
Business
Process
Business
Entity
Business
Rules
Business
Events
Business
Actions
App
Business
Process
Business
Entity
Business
Rules
Business
Events
Business
Actions
App
Business
Process
Business
Entity
Business
Rules
Business
Events
Business
Actions
Point to point Event Notification
Event
Notifications
Copyright © 2000-2002, Data Access Technologies, Inc.
App
Business
Process
Business
Entity
Business
Rules
Business
Events
Business
Actions
App
Business
Process
Business
Entity
Business
Rules
Business
Events
Business
Actions
App
Business
Process
Business
Entity
Business
Rules
Business
Events
Business
Actions
App
Business
Process
Business
Entity
Business
Rules
Business
Events
Business
Actions
Pub/Sub
Pub/Sub Event Notification
8/3/2019 01-1 Modeling Enterprise Collaboration
http://slidepdf.com/reader/full/01-1-modeling-enterprise-collaboration 37/66
EDOC-ECA Class 21 April 2002
37Copyright © 2001-2002, Data Access Technologies, Inc.
Copyright © 2000-2002, Data Access Technologies, Inc.
Event Ex am ple
Copyright © 2000-2002, Data Access Technologies, Inc.
Event s or Serv ic es
❚ Services - conversation between knownparties
❙ Good supply chain model
❚ Events - Actions based on notification of events
❙ Parties do not know about each other!
❙ More loosely coupled
❙ Works best inside a managed domain(enterprise)
8/3/2019 01-1 Modeling Enterprise Collaboration
http://slidepdf.com/reader/full/01-1-modeling-enterprise-collaboration 38/66
8/3/2019 01-1 Modeling Enterprise Collaboration
http://slidepdf.com/reader/full/01-1-modeling-enterprise-collaboration 39/66
EDOC-ECA Class 21 April 2002
39Copyright © 2001-2002, Data Access Technologies, Inc.
Copyright © 2000-2002, Data Access Technologies, Inc.
Com m uni t y Proc ess (CCA)
CCA Notation
Copyright © 2000-2002, Data Access Technologies, Inc.
Protoco l
rder
<<CompositeData>>
OrderConfirmation
<<CompositeData>>
SendOrder
(from Buy SellProtocol)
<<FlowPort>>Get Confirmation
(from BuySellProtocol)
<<FlowPort>>
BuySellProtocol<<Protocol>><<responds>> <<initiates>>
OrderDenied
<<CompositeData>>etDenied
(from BuySellProtocol)
<<FlowPort>>
<<initiates>>
Class diagram for buy/sell protocol
UML Class Diagram
8/3/2019 01-1 Modeling Enterprise Collaboration
http://slidepdf.com/reader/full/01-1-modeling-enterprise-collaboration 40/66
EDOC-ECA Class 21 April 2002
40Copyright © 2001-2002, Data Access Technologies, Inc.
Copyright © 2000-2002, Data Access Technologies, Inc.
Prot oc ol (CCA)
Copyright © 2000-2002, Data Access Technologies, Inc.
Def ine Doc um ent s
8/3/2019 01-1 Modeling Enterprise Collaboration
http://slidepdf.com/reader/full/01-1-modeling-enterprise-collaboration 41/66
EDOC-ECA Class 21 April 2002
41Copyright © 2001-2002, Data Access Technologies, Inc.
Copyright © 2000-2002, Data Access Technologies, Inc.
Prot oc ol Choreography
SendOrder
GetConfirmation GetDenied
<<Success>> <<BusinessFailure>>
When
Internal Logic
Copyright © 2000-2002, Data Access Technologies, Inc.
EDOC Ex erc ise -Communi ty
❚ Part one
❙ Pick a collaboration from the first exercise
❙ Model it with EDOC notation as a communityprocess
❚ Identify an interaction
❙ Specify the documents of the interaction
❘ What are some of the major elements?
❙ Specify any choreography
8/3/2019 01-1 Modeling Enterprise Collaboration
http://slidepdf.com/reader/full/01-1-modeling-enterprise-collaboration 42/66
EDOC-ECA Class 21 April 2002
42Copyright © 2001-2002, Data Access Technologies, Inc.
Copyright © 2000-2002, Data Access Technologies, Inc.
Val idat ion Com ponent
CustService
checkCustomer()
checkCredit()
<<Interface>>
CheckCustomer
(from OrderValidation)
<<ProtocolPort>>
checkOrder
(from OrderValidation)
<<FlowPort>>
acceptOrder
(from CheckCustomer)
<<FlowPort>>
Order
(from BuySell)
<<CompositeData>>
OrderValidation
<<ProcessComponent>>
OrderDenied
<<CompositeData>>
reject
(from OrderValidation)
<<FlowPort>>
<<initiates>>
<<responds>>
<<initiates>>
<<initiates>>
Order Validation
Component
UML Class Diagram
Copyright © 2000-2002, Data Access Technologies, Inc.
Val idat ion Com ponent(CCA)
8/3/2019 01-1 Modeling Enterprise Collaboration
http://slidepdf.com/reader/full/01-1-modeling-enterprise-collaboration 43/66
EDOC-ECA Class 21 April 2002
43Copyright © 2001-2002, Data Access Technologies, Inc.
Copyright © 2000-2002, Data Access Technologies, Inc.
Choreography
checkOrder
rejectacceptOrder
CheckCustomer
success failure
Order ValidationChoreography
When
Internal Logic
Copyright © 2000-2002, Data Access Technologies, Inc.
Com posi t ion (UMLCol laborat ion)
Seller : Sells
Validate : OrderValidation
: c heckOrder
: reject
:
acceptOrder
: CheckCustomer
Process : OrderProcessing
: doOrder
: ProcessedOrder
CustBean :
CustomerComponent
: SendOrder
: GetDenied
:GetConfirmation
: EnqStatus
Seller Composition
1: checkCustomer(order : Order)
8/3/2019 01-1 Modeling Enterprise Collaboration
http://slidepdf.com/reader/full/01-1-modeling-enterprise-collaboration 44/66
EDOC-ECA Class 21 April 2002
44Copyright © 2001-2002, Data Access Technologies, Inc.
Copyright © 2000-2002, Data Access Technologies, Inc.
Com posi t ion (CCA)
Copyright © 2000-2002, Data Access Technologies, Inc.
Sam ple In form at ion Model
+Street : String+City : String
+State : String+Zip : String
«EntityData»Addtress
+Cust
1
+Adr
1..*
+Name : String
+Balance : Decimal = 0
+AccountNo : long
«EntityData»
Account
+InvNum : Integer+Total : Decimal
«EntityData»Invoice
-Act1
-Invoices*
+Quantity : float-Price : Currency
«EntityData»LineItem +PartId : String
+Description : String
+QtyInStock : float(idl)
«EntityData»
Part
-Env
1
-Items
*
-Items
*
-Part
1+InvNum : Integer
«Key»InvoiceKey
-.
1
-.
1
+PartId : String
«Key»PartKey
-. 1
-. *
+AccountNo : String
«Key»AccountKey
-.
1
-.
1
+Name : String-CompanyId : String
«EntityData»Company
+CompanyId : String
«Key»
CompanyKey
-.
1
-.
1
8/3/2019 01-1 Modeling Enterprise Collaboration
http://slidepdf.com/reader/full/01-1-modeling-enterprise-collaboration 45/66
EDOC-ECA Class 21 April 2002
45Copyright © 2001-2002, Data Access Technologies, Inc.
Copyright © 2000-2002, Data Access Technologies, Inc.
Adding Ent i t ies
❚ Entities are added tomanage entity data
❚ Entity Roles aremanagers thatprovides a view of thesame identity inanother context
❚ The Entities haveports for managingand accessing theentities
+Street : String+City : String+State : String+Zip : String
«EntityData»Addtress
+Cust
1
+Adr
1..*
+Name : String+Balance : Decimal = 0+AccountNo : long
«EntityData»Account
+AccountNo : String
«Key»AccountKey
-.
1
-.
1
+Name : String-CompanyId : String
«EntityData»Company
+CompanyId : String
«Key»CompanyKey
-.
1
-.
1
.
Manages
<<Entity>>CompanyManager
Manage
<<EntityRole>>AccountManager
Manage
-Manages1
-.1
Model ing Event s
What t o do w hen someth ing
happens
8/3/2019 01-1 Modeling Enterprise Collaboration
http://slidepdf.com/reader/full/01-1-modeling-enterprise-collaboration 46/66
EDOC-ECA Class 21 April 2002
46Copyright © 2001-2002, Data Access Technologies, Inc.
Copyright © 2000-2002, Data Access Technologies, Inc.
Business
Process
BusinessEntity
BusinessRules
Business
Events
Business
Actions
Business
Services
Event Based Business
Processes
Copyright © 2000-2002, Data Access Technologies, Inc.
Business
Process
Business
Entity
Business
Rules
Business
Events
Business
Actions
Business
Events
Business
Process
Business
Entity
Business
Rules
Business
Actions
Event
Notification
Event Based BusinessProcesses
8/3/2019 01-1 Modeling Enterprise Collaboration
http://slidepdf.com/reader/full/01-1-modeling-enterprise-collaboration 47/66
EDOC-ECA Class 21 April 2002
47Copyright © 2001-2002, Data Access Technologies, Inc.
Copyright © 2000-2002, Data Access Technologies, Inc.
Event Ex am ple
Does ECA m ap w el l t o
WSDL?
An approach t o the
mapp ing
8/3/2019 01-1 Modeling Enterprise Collaboration
http://slidepdf.com/reader/full/01-1-modeling-enterprise-collaboration 48/66
EDOC-ECA Class 21 April 2002
48Copyright © 2001-2002, Data Access Technologies, Inc.
Copyright © 2000-2002, Data Access Technologies, Inc.
ECA/WSDL m apping
❚ ECA works well as a modeling framework forWSDL
❚ How major concepts could map
❙ WSDL Port <-> ECA Port
❙ WSDL Operation <-> ECA Flow port (one way) orOperation (Two way)
❙ WSDL Service <-> ECA Component
❙ WSDL Port type <-> ECA Protocol
❙ WSDL Message <-> ECA Document type
Copyright © 2000-2002, Data Access Technologies, Inc.
WSDL/ECA Dif fe renc es
❚ WSDL Adds
❙ Technology binding and endpoints
❚ ECA adds
❙ Choreography, nested conversations, two-way protocols, nested components.
8/3/2019 01-1 Modeling Enterprise Collaboration
http://slidepdf.com/reader/full/01-1-modeling-enterprise-collaboration 49/66
EDOC-ECA Class 21 April 2002
49Copyright © 2001-2002, Data Access Technologies, Inc.
The WSEC RFP
Web Serv ic es for Ent erpr ise
Col laborat ion
This RFP has not yet been issued
Copyright © 2000-2002, Data Access Technologies, Inc.
Sol ic i t s proposals for
❚ A Mapping from EDOC-Enterprise Collaboration
Architecture to WSDL 1.1 with attachments and a SOAP
binding.
❚ A Mapping from WSDL 1.1 with a Soap binding to the
EDOC-Enterprise Collaboration Architecture.
❚ Any required extensions to the EDOC-Enterprise
Collaboration Architecture to represent WSDL semantics.
8/3/2019 01-1 Modeling Enterprise Collaboration
http://slidepdf.com/reader/full/01-1-modeling-enterprise-collaboration 50/66
EDOC-ECA Class 21 April 2002
50Copyright © 2001-2002, Data Access Technologies, Inc.
ECA Met hodology
A s imp le m et hodology fo r
c rea t ing c o l labora t i ve
bueiness proc esses
Copyright © 2000-2002, Data Access Technologies, Inc.
Basic St eps
❚ Identify roles and organize roles into collaborations
❚ Define collaboration documents
❚ Create basic business transactions
❚ Organize into protocols and events
❚ Use protocols to define ports on roles
❚ Drill-down into role detail
❚ Implement roles
❚ Configure implementations for deployment withtechnology specifics
❚ Deploy
8/3/2019 01-1 Modeling Enterprise Collaboration
http://slidepdf.com/reader/full/01-1-modeling-enterprise-collaboration 51/66
EDOC-ECA Class 21 April 2002
51Copyright © 2001-2002, Data Access Technologies, Inc.
Copyright © 2000-2002, Data Access Technologies, Inc.
Ident i fy ing ro les and
col laborat ions
Copyright © 2000-2002, Data Access Technologies, Inc.
Ident i fy Docum ents
8/3/2019 01-1 Modeling Enterprise Collaboration
http://slidepdf.com/reader/full/01-1-modeling-enterprise-collaboration 52/66
EDOC-ECA Class 21 April 2002
52Copyright © 2001-2002, Data Access Technologies, Inc.
Copyright © 2000-2002, Data Access Technologies, Inc.
Dist inguish protoc o ls and
events
Copyright © 2000-2002, Data Access Technologies, Inc.
Creat e BusinessTransact ions
8/3/2019 01-1 Modeling Enterprise Collaboration
http://slidepdf.com/reader/full/01-1-modeling-enterprise-collaboration 53/66
EDOC-ECA Class 21 April 2002
53Copyright © 2001-2002, Data Access Technologies, Inc.
Copyright © 2000-2002, Data Access Technologies, Inc.
Organize in t o prot oc o ls
Copyright © 2000-2002, Data Access Technologies, Inc.
Add por ts t o c omplet ec omm uni ty proc ess
8/3/2019 01-1 Modeling Enterprise Collaboration
http://slidepdf.com/reader/full/01-1-modeling-enterprise-collaboration 54/66
EDOC-ECA Class 21 April 2002
54Copyright © 2001-2002, Data Access Technologies, Inc.
Copyright © 2000-2002, Data Access Technologies, Inc.
Dri l l -down
Copyright © 2000-2002, Data Access Technologies, Inc.
Add implement a t ion
❚ As component compositions
❚ In a programming language
❚ By using an external service
8/3/2019 01-1 Modeling Enterprise Collaboration
http://slidepdf.com/reader/full/01-1-modeling-enterprise-collaboration 55/66
EDOC-ECA Class 21 April 2002
55Copyright © 2001-2002, Data Access Technologies, Inc.
Copyright © 2000-2002, Data Access Technologies, Inc.
Add tec hnology spec i f i cs
for deploym ent
Copyright © 2000-2002, Data Access Technologies, Inc.
Com plete process
❚ Implemented roles are deployed
❚ Completing the process
8/3/2019 01-1 Modeling Enterprise Collaboration
http://slidepdf.com/reader/full/01-1-modeling-enterprise-collaboration 56/66
EDOC-ECA Class 21 April 2002
56Copyright © 2001-2002, Data Access Technologies, Inc.
Vision
Bui ld ing and adapt ing
sys tem s fo r c o l labora t ion ,
reuse and c hange
Copyright © 2000-2002, Data Access Technologies, Inc.
Loosely c oupled ent erpr isea rch i tec tu re
OpenStandards
O p e n S t a n d a r d s
O p e n
S t a
n d a r d
s❚ Independententerprisecomponents
❚ Representing
business concepts❚ Link via open
standards
8/3/2019 01-1 Modeling Enterprise Collaboration
http://slidepdf.com/reader/full/01-1-modeling-enterprise-collaboration 57/66
EDOC-ECA Class 21 April 2002
57Copyright © 2001-2002, Data Access Technologies, Inc.
Copyright © 2000-2002, Data Access Technologies, Inc.
Business Com ponent
Marke tp lace
❚ The business component marketplace is projected to bea 10b market in 5 years
❚ Consider the value of XML components that wrappopular legacy
❚ New application functionality built from components
❚ Components for integration and transformation
❚ XML and web services makes an excellent basis for suchcomponents
❚ Technology components, such as for repositories andDBMS
❚ Marketplace my be inside the enterprise or commercial
Copyright © 2000-2002, Data Access Technologies, Inc.
OMG Model Dr iven Arc hi t ec t ure (MDA)
❚ High level – platformindependent models
❚ Technology Models
❚ Mapping
❙ Custom
❙ Standard
❚ Standard Modelsproduce technologyspecific standardsartifacts
8/3/2019 01-1 Modeling Enterprise Collaboration
http://slidepdf.com/reader/full/01-1-modeling-enterprise-collaboration 58/66
EDOC-ECA Class 21 April 2002
58Copyright © 2001-2002, Data Access Technologies, Inc.
Copyright © 2000-2002, Data Access Technologies, Inc.
Autom at ed MDA
ProfileProfile
(E.G. EDOC)(E.G. EDOC)
Framework &Framework &
InfrastructureInfrastructure(E.G. XML)(E.G. XML)
InfrastructureInfrastructure
MappingMapping
(E.G. XML)(E.G. XML)
Mapping is tunedMapping is tuned
to the infrastructureto the infrastructure
ToolsTools
Produce &Produce &
IntegrateIntegrate
EnterpriseEnterprise
ComponentsComponents
UMLUML
DesignDesign
Copyright © 2000-2002, Data Access Technologies, Inc.
Tec hnology Independenc e
Adapters
EJB
Business
Logic
Component
ebXml
BizTalk
Rosetanet
Adapters
CICS
EJB
MQ
Corba
8/3/2019 01-1 Modeling Enterprise Collaboration
http://slidepdf.com/reader/full/01-1-modeling-enterprise-collaboration 59/66
EDOC-ECA Class 21 April 2002
59Copyright © 2001-2002, Data Access Technologies, Inc.
Copyright © 2000-2002, Data Access Technologies, Inc.
High level t oo l ing &
in f ras t ruc ture
❚ MUST BE SIMPLE!
❙ We must be able to create better applications faster
❙ We must separate the technology and businessconcerns, enable the user
❚ Tooling + Infrastructure
❙ Executable models are source code
❙ Tooling must be technology aware
❙ Infrastructure must support tooling, not manualtechniques
❚ Model based component architectures
Copyright © 2000-2002, Data Access Technologies, Inc.
High level t oo l ing &in f ras t ruc ture
❚ MUST BE SIMPLE!
❙ We must be able to create better applications faster
❙ We must separate the technology and businessconcerns, enable the user
❚ Tooling + Infrastructure❙ Executable models are source code
❙ aTooling must be technology aware
❙ Infrastructure must support tooling
❚ Model based component architectures
Executable Models
8/3/2019 01-1 Modeling Enterprise Collaboration
http://slidepdf.com/reader/full/01-1-modeling-enterprise-collaboration 60/66
EDOC-ECA Class 21 April 2002
60Copyright © 2001-2002, Data Access Technologies, Inc.
Copyright © 2000-2002, Data Access Technologies, Inc.
I t era t ive Developm ent
Build Build Build Build BuildRelease
Build Deploy
BusinessModelDesign
Infrastructure
Development
Automation
Copyright © 2000-2002, Data Access Technologies, Inc.
Net e ffec t
❚ Using these open standards and automatedtechniques we can;
❙ Achieve the strategic advantage of an open andflexible enterprise
❙ Produce and/or integrate these systems FASTER andCHEAPER than could be done with legacy techniques
❙ Provide a lasting asset that will outlive thetechnology of the day
8/3/2019 01-1 Modeling Enterprise Collaboration
http://slidepdf.com/reader/full/01-1-modeling-enterprise-collaboration 61/66
EDOC-ECA Class 21 April 2002
61Copyright © 2001-2002, Data Access Technologies, Inc.
Copyright © 2000-2002, Data Access Technologies, Inc.
Adva nc ed EDOC
ECAEntities Process
Events
Platform Specific ModelsPlatform Specific Models
RelationshipsCCA
Integration -
viewpoints
etc
FCMFCM
ebXMLebXML
Patterns
Platform Independent ModelsPlatform Independent ModelsPlatform Independent ModelsTechnologymappings
EJBEJBCORBACORBA COMCOMMOMMOM
Business Proc ess Prof i le
how t h ings a re coo rdinat ed
8/3/2019 01-1 Modeling Enterprise Collaboration
http://slidepdf.com/reader/full/01-1-modeling-enterprise-collaboration 62/66
EDOC-ECA Class 21 April 2002
62Copyright © 2001-2002, Data Access Technologies, Inc.
Copyright © 2000-2002, Data Access Technologies, Inc.
Business Proc esses
❚ Specialize CCA
❚ Activity-centric view of a Process
❚ Express
❙ Complex temporal and data dependencies betweenbusiness activities
❙ Iteration of activities
❙ Alternative required Inputs and Outputs of activities
❙ Roles related to performers, artifacts and responsibleparties for activities
Relat ionships Prof i le
Usefu l assoc ia t ions and
dependencies
8/3/2019 01-1 Modeling Enterprise Collaboration
http://slidepdf.com/reader/full/01-1-modeling-enterprise-collaboration 63/66
EDOC-ECA Class 21 April 2002
63Copyright © 2001-2002, Data Access Technologies, Inc.
Copyright © 2000-2002, Data Access Technologies, Inc.
Relat ionships Prof i le
❚ Enables non-binary aggregations
❚ Defines useful association and dependency stereotypes
partA partB
aggregate <<Aggregation>>
<<Packet>>
<<Assembly>>
<<Subordination>>
<<List>> <<List>>
or
or
Pat t erns Prof i le
reus ing
parameter iseddes igns
8/3/2019 01-1 Modeling Enterprise Collaboration
http://slidepdf.com/reader/full/01-1-modeling-enterprise-collaboration 64/66
EDOC-ECA Class 21 April 2002
64Copyright © 2001-2002, Data Access Technologies, Inc.
Copyright © 2000-2002, Data Access Technologies, Inc.
Pat t erns Prof i le
! Profiles UML Parameterized Collaborations! Based on Business Function Object Patterns
(BFOP)
– Multi-Layer
– Based on Catalysis Approach
! Adds stereotypes for
– Named Patterns
–
Inheritance – Composition
– Pattern Binding with renaming
Copyright © 2000-2002, Data Access Technologies, Inc.
Plat form Speci f ic Modell ing
❚ EJB, FCM, MOF
❚ Technology mappings from EDOC to DistributedComponent and Message Flow Platform Specific Models
❙ EDOC to J2EE/EJB mapping
❙ EDOC to CORBA/CCM mapping
❙ EDOC Business Process to FCM mapping
❙ EDOC Business Process to CORBA mapping
8/3/2019 01-1 Modeling Enterprise Collaboration
http://slidepdf.com/reader/full/01-1-modeling-enterprise-collaboration 65/66
EDOC-ECA Class 21 April 2002
65Copyright © 2001-2002, Data Access Technologies, Inc.
Copyright © 2000-2002, Data Access Technologies, Inc.
ECA as t he norm al form
EDOC-ECA
Web Services(WSDL)
ebXML(BPSS)
J2EE(Java RMI)
.NET
MOM(MQ-Series)
The standard way to modeland tool for multiple
technologies
MDAMappings
Copyright © 2000-2002, Data Access Technologies, Inc.
Discussion
❚ How much are we using these kinds of concepts today?
❚ What would be the advantages to going
in this direction?❚ What are the barriers;
❙ Technical?
❙ Political?
❚ What would be a good first step?
8/3/2019 01-1 Modeling Enterprise Collaboration
http://slidepdf.com/reader/full/01-1-modeling-enterprise-collaboration 66/66
EDOC-ECA Class 21 April 2002
Copyright © 2000-2002, Data Access Technologies, Inc.
Contact
Cory Casanave
Data Access Technologies
www.enterprise-component.com
(305) 234-7077