© 2005-2006 The ATHENA Consortium.
AP5 – Principles of Model-Driven
Interoperability
Learn about model-driven interoperability, metamodelling, UML profiles and domain-specific languages (DSLs), and method engineering.
2© 2005-2006 The ATHENA Consortium.
Course description
• This course focuses on principles and processes of how to apply model-driven development approaches to solving software interoperability problems.
• The course teaches how to develop metamodels using MOF technology, and how to build your own UML profiles and domain-specific languages (DSLs).
• The course aims to provide guidelines on practical and correct use of these technologies in the development of interoperable software systems, using examples of how to apply metamodelling and UML profiles.
• The course also focuses on method engineering for MDA.
3© 2005-2006 The ATHENA Consortium.
Course objective
• This course aims to be a method engineering course that will teach the students how to develop and/or configure their own model-driven development methodologies and tools for software interoperability.
• Participants will gain an understanding of the use of metamodelling, UML profiles and domain-specific languages (DSLs) in a software engineering development and integration process.
4© 2005-2006 The ATHENA Consortium.
MDI training trackNo Topic Presenter
A
P
4
4-1 Interoperability & Model-Driven Architecture (MDA) <Person>, <Company>, <Country>
A
P
5
5-1 ATHENA Model-Driven Interoperability (MDI) Framework <Person>, <Company>, <Country>
5-2 Metamodelling• Eclipse Modeling Framework (EMF) Tutorial / Exercise
<Person>, <Company>, <Country>
5-3 UML Profiles and Domain-Specific Languages (DSLs)• Eclipse Graphical Modeling Framework (GMF) Tutorial / Exercise
<Person>, <Company>, <Country>
5-4 Method Engineering• Eclipse Process Framework (EPF) Tutorial / Exercise
<Person>, <Company>, <Country>
A
P
6
5-1 Model Mappings and Transformations• ATL Tutorial (optional)• MOFScript Tutorial (optional)
<Person>, <Company>, <Country>
5-2 Model-Driven Development with PIM4SOA <Person>, <Company>, <Country>
5-3 From PIM4SOA to Web Services• PIM4SOA to XSD ATL Tutorial / Exercise
<Person>, <Company>, <Country>
5-4 From PIM4SOA to Agents <Person>, <Company>, <Country>
5-5 From PIM4SOA to Peer-2-Peer (P2P) <Person>, <Company>, <Country>
5© 2005-2006 The ATHENA Consortium.
MDI website
http://www.modelbased.net/mdi
© 2005-2006 The ATHENA Consortium.
5-1. ATHENA Model-Driven
Interoperability (MDI) Framework
<Presenter>
<Company>, <Country>
<E-mail>
7© 2005-2006 The ATHENA Consortium.
Outline
• Requirements of the framework• Specification of the framework
– Conceptual integration– Technical integration– Applicative integration
• Realisation of the framework– Methodology and guidelines– Tools and services
• References
8© 2005-2006 The ATHENA Consortium.
Requirements of the framework
9© 2005-2006 The ATHENA Consortium.
Motivation
• We believe that there is a need for an interoperability framework that provides guidance on how MDD should be applied to address interoperability.
• The interoperability framework integrates principles of model-driven, service-oriented and adaptive software architectures:
– Model-driven architectures focus on design-time aspects of system engineering. Model-driven development methodologies describe how to develop and utilise (visual) models as an active aid in the analysis, specification, design and implementation phases of an ICT system.
– Service-oriented architecture (SOA) specifies systems composed of services offered by various service providers, which provides the basis for supporting new business models, such as “virtual organisations”.
– Adaptive software architectures focus on run-time aspects of system engineering. Agent and P2P technologies enrich an ICT system with dynamic and adaptive qualities.
10© 2005-2006 The ATHENA Consortium.
Service-oriented architectures
• Service provider: A service provider is the party that provides software applications for specific needs as services. Service providers publish, unpublish and update their services so that they are available on the Internet.
• Service requester: A requester is the party that has a need that can be fulfilled by a service available on the Internet. A requester could be a human user accessing the service through a desktop or a wireless browser; it could be an application program; or it could be another service. A requester finds the required services via a service broker and binds to services via the service provider.
• Service broker: A service broker provides a searchable repository of service descriptions where service providers publish their services and service requesters find services and obtain binding information for these services. Examples of service brokers are UDDI (Universal Description, Discovery, and Integration) and XMethods. In many cases the role of the service broker is not explicitly needed. Services can be discovered by marketing channels or by referrals.
InvokeBind
Service Provider
Service Broker
Service Requester
PublishUnpublishUpdate
Discover
11© 2005-2006 The ATHENA Consortium.
Adaptive business architectures
• Globalisation and mass customisation are business trends that have created a situation where business processes that used to be managed by a single enterprise are now distributed and need to be planned and enacted across multiple partners.
• This leads to highly distributed architectures of business systems with amplified complexity and increased need for collaboration among the participating organizations.
• At the same time, organizations are in increasing need of solutions to allow them to cope flexibly with constantly changing environments.
12© 2005-2006 The ATHENA Consortium.
Service-Oriented Architectures
AgentArchitectures
P2PArchitectures
Web ServiceArchitectures
Model-Driven InteroperabilityArchitectures (“Design-time”) Adaptive Interoperability
Architectures (“Run-time”)
PlatformIndependentModel
PlatformSpecificModels
Model-Drivenand AdaptiveInteroperabilityConcepts
“Interoperability Enhanced” Service-Oriented Architectures
Part I
Component &Message-OrientedArchitectures
BusinessProcess ExecutionArchitectures
Part II
Part III
ModelTransformations
TechnologyMappings
MDA and adaptive architectures
14© 2005-2006 The ATHENA Consortium.
Specification of the framework
15© 2005-2006 The ATHENA Consortium.
MDI framework (1)
VisionEnterprises are able to flexibly develop and execute interoperable applications based on model-driven development approaches to service-oriented and adaptive software solutions.
Conceptual Integration• Concepts• Metamodels• Languages• Model relationships
Technical Integration• Development environments• Execution environments
Applicative Integration• Methodologies• Standards• Domain models
Integrates principles of• Model-driven development• Service-oriented architectures• Adaptive architectures
Three main integration areas• Conceptual integration• Technical integration• Applicative integration
16© 2005-2006 The ATHENA Consortium.
MDI framework (2)
• The interoperability framework itself is structured according to three main integration areas defined in ATHENA:
• For each of these three areas a reference model to describe and support the application of model-driven development of software systems is specified.
1. Conceptual integration focuses on concepts, meta-models, languages and model relationships to systemise software model interoperability.
2. Technical integration focuses on the software development and execution environments.
3. Applicative integration focuses on methodologies, standards and domain models. It provides us with guidelines, principles and patterns that can be used to solve software interoperability issues.
Conceptual Integration
Technical Integration
Applicative Integration
Computational System A
Enterprise System A(MDD Abstraction)
Execution Platform A
Ontologies
Model-DrivenArchitecture (MDA)&Architecture-DrivenModernisation (ADM)
Platform IndependentModel (PIM)
Computational IndependentModel (CIM)
Architecture-DrivenModernisation (ADM)
SemanticAnnotation
SemanticAnnotation
Model-DrivenArchitecture (MDA)
Platform SpecificModel (PSM)
SemanticAnnotation
Computational System B
Enterprise System B(MDD Abstraction)
Execution Platform B
Ontologies
Model-DrivenArchitecture (MDA)&Architecture-DrivenModernisation (ADM)
Platform IndependentModel (PIM)
Computational IndependentModel (CIM)
Architecture-DrivenModernisation (ADM)
SemanticAnnotation
SemanticAnnotation
Model-DrivenArchitecture (MDA)
Platform SpecificModel (PSM)
SemanticAnnotation
Horizontal Integration
Vert
ical In
teg
rati
on
ReferenceOntology
MT
MT
MT
MT Model Transformation
MT
MT Model Transformation
MI
MI
InteroperabilityPatterns
Model Interoperability
Computational System A
Enterprise System A(MDD Abstraction)
Execution Platform A
Ontologies
Model-DrivenArchitecture (MDA)&Architecture-DrivenModernisation (ADM)
Platform IndependentModel (PIM)
Computational IndependentModel (CIM)
Architecture-DrivenModernisation (ADM)
SemanticAnnotation
SemanticAnnotation
Model-DrivenArchitecture (MDA)
Platform SpecificModel (PSM)
SemanticAnnotation
Computational System B
Enterprise System B(MDD Abstraction)
Execution Platform B
Ontologies
Model-DrivenArchitecture (MDA)&Architecture-DrivenModernisation (ADM)
Platform IndependentModel (PIM)
Computational IndependentModel (CIM)
Architecture-DrivenModernisation (ADM)
SemanticAnnotation
SemanticAnnotation
Model-DrivenArchitecture (MDA)
Platform SpecificModel (PSM)
SemanticAnnotation
Horizontal Integration
Vert
ical In
teg
rati
on
ReferenceOntology
MT
MT
MT
MT Model Transformation
MT
MT Model Transformation
MI
MI
InteroperabilityPatterns
Model Interoperability
Software System Software System
Service Bus
Enterprise A(Technical World)
Enterprise B(Technical World)
Business
BusinessTransactions
BusinessProcesses
BusinessCollaborations
Users
BusinessTasks
VerticalIntegration
Business
BusinessTransactions
BusinessProcesses
BusinessCollaborations
Users
BusinessTasks
VerticalIntegration
Infrastructure ServicesInfrastructure Services
Registry/Repository
ModelMgmt.
ServiceMgmt.
Exec.Mgmt.
DataMgmt.
Serv
ice B
us
Serv
ice B
us
User
Inte
rface S
erv
ices
User
Serv
ices
Bu
sin
ess S
erv
ices
Reso
urc
e S
erv
ices
User
Inte
rface S
erv
ices
User
Serv
ices
Bu
sin
ess S
erv
ices
Reso
urc
e S
erv
ices
ICT Infrastructure
So
ftware S
ystem
En
terprise A
rchitec
ture A
(Mo
de
l Wo
rld)
So
ftwa
reM
od
el
Sp
ecification
Mo
dels
Bu
sin
ess
Co
nte
xt
Bu
siness
En
terprise A
(Te
ch
nic
al W
orld
)
Bu
sine
ssT
ransa
ction
s
Bu
sine
ssP
roce
sses
Bu
sine
ssC
olla
bo
ratio
ns
Mo
de
ls o
f Se
rvic
e, In
form
atio
nP
roc
es
s a
nd
No
n-F
un
ctio
na
l As
pe
cts
En
terp
rise
Mo
de
l
Bu
siness
Mo
dels
Realisatio
nM
od
els
Users
Bu
sine
ssT
asks
Ve
rtica
lIn
teg
ratio
n
Co
mp
utatio
nal S
ystem A
En
terprise S
ystem A
(MD
D A
bs
trac
tion
)
Execution P
latform A
On
tolo
gie
s
Mo
del-D
rivenA
rchite
cture (M
DA
)&A
rchite
cture-D
rivenM
od
ernisatio
n (A
DM
)
Pla
tform
Ind
epe
nd
en
tM
od
el (P
IM)
Co
mp
uta
tion
al In
de
pe
nd
en
tM
od
el (C
IM)
Arch
itectu
re-Driven
Mo
dern
isation
(AD
M)
Sem
antic
An
no
tation
Sem
antic
An
no
tation
Mo
del-D
rivenA
rchite
cture (M
DA
)
Pla
tform
Sp
ecific
Mo
de
l (PS
M)
Sem
antic
An
no
tation
MT
MT
MT
Mo
de
l Tra
ns
form
atio
n
User Interface Services
User Services
Business Services
Resource Services
Service Bus
MT
MT M
TM
T
MT
Mo
de
ls o
f oth
er E
nte
rpris
e A
sp
ec
ts
17© 2005-2006 The ATHENA Consortium.
Conceptual integration – Overview
• Developed from a MDD point of view focusing on the enterprise applications and software system.
• A Computation independent model (CIM) corresponds to a view defined by a computation independent viewpoint. It describes the business context and business requirements for the software system(s).
• A platform independent model (PIM) corresponds to a view defined by a platform independent viewpoint. It describes software specifications independent of execution platforms.
• A platform specific model (PSM) corresponds to a view defined by a platform specific viewpoint. It describes the realisation of software systems.
18© 2005-2006 The ATHENA Consortium.
Computational System B
Enterprise System B(MDD Abstraction)
Execution Platform B
Ontologies
Model-DrivenArchitecture (MDA)&Architecture-DrivenModernisation (ADM)
Platform IndependentModel (PIM)
Computational IndependentModel (CIM)
Architecture-DrivenModernisation (ADM)
SemanticAnnotation
SemanticAnnotation
Model-DrivenArchitecture (MDA)
Platform SpecificModel (PSM)
SemanticAnnotation
MT
MT Model Transformation
MT
Computational System A
Enterprise System A(MDD Abstraction)
Execution Platform A
Ontologies
Model-DrivenArchitecture (MDA)&Architecture-DrivenModernisation (ADM)
Platform IndependentModel (PIM)
Computational IndependentModel (CIM)
Architecture-DrivenModernisation (ADM)
SemanticAnnotation
SemanticAnnotation
Model-DrivenArchitecture (MDA)
Platform SpecificModel (PSM)
SemanticAnnotation
MT
MT
MT Model Transformation
Service
Aspects
Information
Aspects
ProcessAspects
Non-
Functional
Aspects
Horizontal Integration
V
erti
cal
In
teg
rati
on
ReferenceOntology
MI
MI
InteroperabilityPatterns
Model Interoperability
Conceptual integration: Reference model
19© 2005-2006 The ATHENA Consortium.
Conceptual integration: System aspects
• We have identified four categories of system aspects where specific software interoperability issues can be addressed. These four aspects can be addressed at all three CIM, PIM and PSM levels.
• Service aspects: Services are an abstraction and an encapsulation of the functionality provided by an autonomous entity,.
• Information aspects: Information aspects are related to the messages or structures exchanged, processed and stored by software systems or software components.
• Process aspects: Processes describe sequencing of work in terms of actions, control flows, information flows, interactions, protocols, etc.
• Non-functional aspects: Extra-functional qualities that can be applied to services, information and processes.
• We have been studying the following metamodels.
• CIM level– Business Process Definition Metamodel
(BPDM)– Software Process Engineering Metamodel
(SPEM)– POP* (being defined within ATHENA)
• PIM level– EDOC – UML Profile for Enterprise Distributed
Object Computing Specification– QoS – UML Profile for Modelling Quality of
Services and Fault Tolerance Characteristics and Mechanisms
• PSM level– Web Services– Web Services Business Process Execution
Language (WSBPEL)– Agents Architectures– Peer2Peer Architectures
20© 2005-2006 The ATHENA Consortium.
System aspects and integration dimensions
Integration dimensions• System abstraction• Generality• Viewpoint• Composition• Time• Model abstraction
System aspects• Information• Service• Process• Non-functional
Model abstraction
M0 M1 M2 M3
Time
State
Evolution
Composition
(Virtual)Enterprise
Service
Component
Object
System abstraction
Code
PSM
PIM
CIM
Generality
System, Product
Product-line, Framework, Pattern
Viewpoint
Realisation Viewpoint
Specification Viewpoint
Business Viewpoint
Enterprise Viewpoint
Service
Aspects
Information
Aspects
ProcessAspects
Non-
Functio
nal
Aspects
21© 2005-2006 The ATHENA Consortium.
Technical integration – Overview
• Developed from a service-oriented point of view where a software system provides a set of services required by the businesses and users of the enterprise.
• The architecture of the enterprise applications and software systems can be described according to a 4-tier reference architecture where each tier provides different software services required by the enterprise.
• The software system itself is coupled to a service bus that provides the necessary communication infrastructure.
• Infrastructure services such as composition, mediation, matchmaking and transformation that enables interoperability between software systems should be provided.
– Model repository for managing models of various kinds.– Service registry for managing naming, directory and location of services– Execution repository for managing information and state needed in the execution
of software services and processes– Data repository for managing results and traces of the executions.
22© 2005-2006 The ATHENA Consortium.
Software System
Enterprise B(Technical World)
Business
BusinessTransactions
BusinessProcesses
BusinessCollaborations
Users
BusinessTasks
VerticalIntegration
Ser
vice
Bu
sSoftware System
Enterprise A(Technical World)
Business
BusinessTransactions
BusinessProcesses
BusinessCollaborations
Users
BusinessTasks
VerticalIntegration
Ser
vice
Bu
s
Technical integration: Reference model
Service Bus
Infrastructure Services
Registry/Repository
ModelMgmt.
ServiceMgmt.
Exec.Mgmt.
DataMgmt.
ICT Infrastructure
Use
r In
terf
ace
Ser
vice
s
Use
r S
ervi
ces
Bu
sin
ess
Ser
vice
s
Res
ou
rce
Ser
vice
s
Use
r In
terf
ace
Ser
vice
s
Use
r S
ervi
ces
Bu
sin
ess
Ser
vice
s
Res
ou
rce
Ser
vice
s
23© 2005-2006 The ATHENA Consortium.
Legend
Service
Inter-servicecommunication
Use
r S
erv
ice
Do
ma
inB
usi
nes
s S
ervi
ceD
om
ain
LS
Resource AdapterRALA Local Adapter
Local Storage Database
ResourceServiceTier
BusinessServiceTier
UserServiceTier
UserInterfaceTier
LS
RARA
LA
Service Bus(Middleware Services)
Technical integration: 4-tier reference architecture
24© 2005-2006 The ATHENA Consortium.
Service Wrappers / Interoperability Management
Evaluation & Negotiation of Available Functionality(using – “Enhanced Registry” & “Broker/Negotiator”)
Execution Environment
Service Interconnection Bus
Company B
Company A RepositoryRepository
Existing Enterprise Applications
According to the model-driven development models (ideally starting on the CIM level) are transformed and refined until they are eventually directly executed at the PSM level in a concrete execution environment.
Service Wrappers: Provides a standardised way of accessing and using services. A first version of the service wrapper will be based on Web service technology.
Evaluation & Negotiation: evaluate and negotiate incoming service requests, make use of underlying infrastructure services, and direct requests to the appropriate service deployed on an execution platform.
Execution Environment: Concrete platform that is able to execute PSM models, e.g. BPEL, Agent, or Composed Service models.
Service Interconnection Bus: provides middleware services for integrating the various execution platforms.
Operational vision on interoperability
25© 2005-2006 The ATHENA Consortium.
ATHENA integrated execution infrastructure
RegistryRepository
Service Wrappers (Enterprise A)
Evaluation & Negotiation of Available Functionality
Enhanced Service Interconnection Bus
Cross-org.
Intra-org.
Existing Enterprise Applications
PublicInfrastructure Services
Service Wrappers(Enterprise X)
Service Wrappers(Enterprise Y)
InternalInfrastructure Services
Process Execution Platform(BPEL)
Goal-orientedAdaptive ExecutionPlatform(Agents)
Goal-orientedAdaptive ExecutionPlatform(Agents)
ActiveModel Platform(AKMii)
ActiveModel Platform(AKMii)
Legend
Message-OrientedPlatform(MQSeries)
Message-OrientedPlatform(MQSeries)
Server-side Component Platform(.NET, J2EE)
Server-side Component Platform(.NET, J2EE)
ComposedWebServicePlatform(WebServices)
UML Model
Business Process/Agent
Active (Business) Model
Web/Server Component
Middleware Process/Agent
Middleware Component
Adaptive Distributed Resource Mgt Platform (P2P)
ModelExecutionPlatform(UML VM)
ModelExecutionPlatform(UML VM)
26© 2005-2006 The ATHENA Consortium.
Applicative integration – Overview
• Developed based on work related to enterprise architecture frameworks and software architecture frameworks.
• Enterprise and software models can be related in a holistic view, regardless of modelling language formalisms, by the use of meta-models.
• The MDD methodology needs to follow a structured approach where interoperability requirements from business operations in a networked enterprise drive the development of software solutions.
• An enterprise model describes a set of enterprise aspects, which includes descriptions of the business operations of the business models.
• Software models describe how software systems are used to support the businesses of an enterprise.
• All these models should include descriptions of the four system aspects identified in the reference model for conceptual integration.
27© 2005-2006 The ATHENA Consortium.
Computational System A
Enterprise System A(MDD Abstraction)
Execution Platform A
Ontologies
Model-DrivenArchitecture (MDA)&Architecture-DrivenModernisation (ADM)
Platform IndependentModel (PIM)
Computational IndependentModel (CIM)
Architecture-DrivenModernisation (ADM)
SemanticAnnotation
SemanticAnnotation
Model-DrivenArchitecture (MDA)
Platform SpecificModel (PSM)
SemanticAnnotation
MT
MT
MT Model Transformation Software System
Business
Enterprise A(Physical World)
BusinessTransactions
BusinessProcesses
BusinessCollaborations
Users
BusinessTasks
VerticalIntegration
Use
r In
terf
ace
Ser
vice
s
Use
r S
ervi
ces
Bu
sin
ess
Ser
vice
s
Res
ou
rce
Ser
vice
s
Ser
vice
Bu
s
Applicative integration: Reference model
Enterprise Architecture A(Model World)
SoftwareModel
SpecificationModels
BusinessContext
Models of Service, InformationProcess and Non-Functional Aspects
EnterpriseModel
BusinessModels
RealisationModels
MT
MT
MTMT
MT
Models of other Enterprise Aspects
28© 2005-2006 The ATHENA Consortium.
BusinessAnalyst
Bu
sin
ess
Vie
w
ARCADE data
FOFAS bør kunne oppdatere ARCADE
: COP
Actual and planned
draft TASKORG : Frequency requirements
verified list : Frequencies
From Div 6, FO/I, KA mobile avd, LV
final TASKORG : Frequency requirements
temp verified list : Frequencies
Receive ARCADE data
Generate Frequency list
Receive frequency requirements from lower level
Receive COP
Establish/maintain frequency pool
temporary list : Frequencies
Verify security level
Distribute Frequency list
Verify Frequency list
new operationnew campaign
list : Frequencies
new operationDistribute temporary
Frequency list
new campaign
Joint LevelLower Echelon UnitCOPdistributorARCADE system
e.g. BusinessProcess Model
SystemArchitect
Sp
ecif
icat
ion
Vie
w
Deployed Unit #1
InformationService #1Command Center
iProcess
InformationService #2
Deployed Unit #2
iNotification iPublishNotificationService
ProcessingService
Ethernet
Satelite
Radio
InformationInformation
e.g. Service &Interface Model
SoftwareDeveloper
cryptoKeys
Frequencies
Subnet
- nettId- nettType- name- frequency- frequencyChangeTime- newFrequency- frequencyFMprai- frequencyDigPray- areaCode- KVTid- KVTchangeTime
Main frequencies
- emitterType- frequency- emissionType- area(polygon, circle)- class of station(mobile, point-point, ground-air)
Frequency requirements
- emitterType- emissoinType- area- class of station[mobile, point-point, ground-air]- timerange- usage[send, receive,...]- securityLabel[(NATO) unclassified, restricted, confidential, secret]
Decoding list
Telephone DirectoryAddressee
SOICOP
op1
op2e.g.Interaction
&Data
Model
Rea
lisat
ion
Vie
w
NetworkedEnterprise
SoftwareSystem
Legend
BusinessViewpoint
SpecificationViewpoint
RealisationViewpoint
Applicative integration: Three basic viewpoints
29© 2005-2006 The ATHENA Consortium.
Virtual Enterprise
BusinessAnalyst
Business View(e.g. Business Process Models)
ARCADE data
FOFAS bør kunne oppdatere ARCADE
: COP
Actual and planned
draft TASKORG : Frequency requirements
verified list : Frequencies
From Div 6, FO/I, KA mobile avd, LV
final TASKORG : Frequency requirements
temp verified list : Frequencies
Receive ARCADE data
Generate Frequency list
Receive frequency requirements from lower level
Receive COP
Establish/maintain frequency pool
temporary list : Frequencies
Verify security level
Distribute Frequency list
Verify Frequency list
new operationnew campaign
list : Frequencies
new operationDistribute temporary
Frequency list
new campaign
Joint LevelLower Echelon UnitCOPdistributorARCADE system
ProductDeveloper
Product View(e.g. Product structure models)
SoftwareDeveloper
Extending the basic viewpoints
cryptoKeys
Frequencies
Subnet
- nettId- nettType- name- frequency- frequencyChangeTime- newFrequency- frequencyFMprai- frequencyDigPray- areaCode- KVTid- KVTchangeTime
Main frequencies
- emitterType- frequency- emissionType- area(polygon, circle)- class of station(mobile, point-point, ground-air)
Frequency requirements
- emitterType- emissoinType- area- class of station[mobile, point-point, ground-air]- timerange- usage[send, receive,...]- securityLabel[(NATO) unclassified, restricted, confidential, secret]
Decoding list
Telephone DirectoryAddressee
SOICOP
Component View(e.g. Design & Implementation Models)
op1
op2
SystemArchitect
System View(e.g. System Interface Models)
Deployed Unit #1
InformationService #1Command Center
iProcess
InformationService #2
Deployed Unit #2
iNotification iPublishNotificationService
ProcessingService
Ethernet
Satelite
Radio
InformationInformation
Rea
lisat
ion
View
poin
t
(Pla
tform
Spe
cific
)
Specification V
iewpoint
(Platform
Independent)
Con
text
Vie
wpo
int
(Com
puta
tion
Inde
pend
ent)
Product Viewpoint
30© 2005-2006 The ATHENA Consortium.
Realisation of the framework
31© 2005-2006 The ATHENA Consortium.
MD
I m
eth
od
en
gin
eeri
ng
fra
mew
ork
ATHENA Model-Driven Interoperability(MDI) Framework
ATHENA Development and Integration Methodology for SOA
A6
SINTEF
ATHENA MDI ToolsA5 & A6
Enterprise Modelling
Web ServiceModelling
AgentModelling
Service Integration Modelling
PIM4SOA Modelling
Interoperability
Metamodelling
Language Engineering
Model Transformations
Method Engineering
Provides guidelines and
existing method chunks for creating or
customizing your own
development andintegration
methodologies
ATHENA Development and Integration Methodology for SOA
SINTEF
Enterprise Modelling
Web ServiceModelling
AgentModelling
Service Integration Modelling
PIM4SOA Modelling
ATHENA Service-Oriented Interoperability (SOI) Methodology
A5
Enterprise Modelling
Web ServiceModelling
AgentModelling
Service Integration Modelling
PIM4SOA Modelling
Specific Metamodels (both Business Domains and Technology Domains)
Specific DSLs and UML Profiles
Specific Model Transformations
ATHENA MDI ToolsA5 & A6
Specific Metamodels (both Business Domains and Technology Domains)
Specific DSLs and UML Profiles
Specific Model Transformations
ATHENA MDI ToolsA5 & A6
Specific Metamodels (both Business Domains and Technology Domains)
Specific DSLs and UML Profiles
Specific Model Transformations
Tool-supportedmethodology
Reusable MDI Assets
• Method chunks• Tools and services
• Models and metamodels• Model transformations• DSLs and UML profiles
• Reference examples
Provides guidelines and existing assets for creating or customizing your own MDI
tools
32© 2005-2006 The ATHENA Consortium.
ATHENA MDI Framework
ATHENA Model-Driven Interoperability (MDI) Framework
MDA & Interoperability
Metamodelling
UML Profiles & DSLs
Model Transformations
Method Engineering
Reusable MDI Assets
• Method chunks• Tools and services
• Models and metamodels• Model transformations• DSLs and UML profiles
• Reference examples
33© 2005-2006 The ATHENA Consortium.
References
34© 2005-2006 The ATHENA Consortium.
References
[ATHENA] ATHENA, "ATHENA Public Web Site", ATHENA Integrated Project (IST-507849). http://www.athena-ip.org/
[ATHENA A6 2005] ATHENA A6, "D.A6.1: Specification of a Basic Architecture Reference Model", ATHENA IP, Deliverable D.A6.1, 2005.
[ATHENA A6 2006] ATHENA A6, "D.A6.2: Enhanced Registry/Repository Infrastructure", ATHENA IP, Deliverable D.A6.2, 2006.
[ATHENA A6 2006] ATHENA A6, "D.A6.3: Model-driven and Adaptable Interoperability Framework", ATHENA IP, Deliverable D.A6.3, 2006.
[ATHENA A6 2006] ATHENA A6, "D.A6.4: Model-driven and Adaptable Interoperability Infrastructure", ATHENA IP, Deliverable D.A6.4, 2006.
[Elvesæter, et al. 2005] B. Elvesæter, A. Hahn, A.-J. Berre, and T. Neple, "Towards an Interoperability Framework for Model-Driven Development of Software Systems", in Proc. of the 1st International Conference on Interoperability of Enterprise Software and Applications (INTEROP-ESA 2005), Geneva, Switzerland, 2005.
35© 2005-2006 The ATHENA Consortium.
This course has been developed under the funding of the EC with the support of the EC ATHENA-IP Project.
Disclaimer and Copyright Notice: Permission is granted without fee for personal or educational (non-profit) use, previous notification is needed. For notification purposes, please, address to the ATHENA Training Programme Chair at [email protected]. In other cases please, contact at the same e-mail address for use conditions. Some of the figures presented in this course are freely inspired by others reported in referenced works/sources. For such figures copyright and all rights therein are maintained by the original authors or by other copyright holders. It is understood that all persons copying these figures will adhere to the terms and constraints invoked by each copyright holder.