Embed Size (px)
Citation preview
ICT
INF5120Modellbasert systemutvikling
�F15 – Oppsummering av kurset�Pensum�Eksamens-eksempler 2000-2006�Eksamen 2007
Forelesning 14.05.2007
Arne-Jørgen Berre
ICT
INF5120 - Forelesninger - 2007
AJB: Arne-Jørgen Berre, AJB: Arne-Jørgen Berre, BRE: Brian ElvesæterBRE: Brian Elvesæter GKOGKO: : Gøran K. Olsen Gøran K. Olsen
� MDSU (Bok 1 – part 1 og 2) – fra 22/1� 1 22-1: Introduction to MBSU, MDA, OO and modeling (M1-M5)� 2: Metamodeling and UML profiles, MDA technologies (Eclipse technologies) (M2, M4, M6)� 3: Language Engineering and DSL (M8)� 4: Model transformations with ATL and other technologies (M10, M11� 5: Code generation with MOFScript and other technologies (M9
� COMET – New development (Bok 1 part 3, Bok 2) – fra 26/2� 6 26-2: Method Engineering and Process – and COMET overview (M13)� 7: COMET EA and Business Modeling - Enterprise Modeling and Enterprise Architecture (EA) � 8: Requirements Engineering and Use cases – (and Agile methods and modeling), Patterns and aspects� 9: SOA Architectures and platforms (SOA) and COMET Architecture Modeling and PIM4SOA and UPMS� 10: PIM and Web Services teknologi (PSM) med WSDL/XML/BPEL
� MDI (Område 3) - fra 16/4� 11 16/4: Interoperability and MDI – AIF, EIF and EIM� 12: 23/4: Ontologies and Semantic web and Modeling � 13. 30/4: MDI – Model Driven Interoperability, PIM4SOA –> Agent transformations, AIM� 14. 7/5: Aspekt-orientert Programmering og Modellering� 15. 14/5 Course summary
ICT
F2: Outline
� Model-driven interoperability (MDI) framework
� MDA (revisited)
� Applied metamodelling
� Standards and technologies
� OMG MOF and metamodelling
� Eclipse Modeling Framework (EMF)
� Examples
� Metamodel for PIM4SOA
� Metamodel for Web services
� Metamodel for BDI agents
� Eclipse Modeling Framework (EMF) exercise
� References
ICT
F3: Outline
� Metamodelling (revisited)
� UML profiles
� Domain-specific languages (DSLs)
� Eclipse technologies� Eclipse Modeling Framework (EMF)
� Eclipse Graphical Modeling Framework (GMF)
� Example� Metamodels and UML profiles for SOA and Web services
� References
ICT
INF 5120 - Lecture #4 Model transformations with ATL and other
technologies
Gøran K. Olsen
SINTEF ICT
Cooperative and Trusted Systems
ICT
Model-to-Model Transformation idea
COM / DCOM
Java EJB
PIM2
C# .net XML SOAP
PIM.. 1..*
MT
A PIM can be transformed into
different PSM
Or transformed to a new PIM
ICT
Atlas Transformation Language (ATL)
� Will be used in INF 5120
� ATL is a hybrid language (a mix of declarative and imperative constructions) designed to express model transformations as described by the MDA approach.
� It is not QVT, but similar and with the corresponding functionality
� A transformation model in ATL is expressed as a set of transformation rules.
� The recommended style of programming is declarative.
� OCL is used to expression constraints on rules
� Guards (constraints) on the entry point for a rule
ICT
INF 5120 - Lecture #5 Code generation with MOFScript and other
technologies
Gøran K. Olsen
SINTEF ICT
Cooperative and Trusted Systems
ICT
MOFScript placed in the 4-layer architecture
MOFMOF
Source Source
MetamodelMetamodel
Source Source
modelmodel
MOFScript MOFScript
languagelanguage
MOFScript MOFScript
transformationtransformation
TargetTarget
texttext
MOFScript MOFScript
tool tool
engineengine
executed byexecuted by
inputinput
outputoutput
conforms toconforms to conforms toconforms to
conforms toconforms to
based onbased on
M1M1
M2M2
M3M3
conforms toconforms to
ICT
INF5120Lecture #6 (F6)26 February 2007
� Method engineering and process
� COMET overview
Based on material developed in the ATHENA (IST-507849), COMBINE (IST-1999-20839), INTEROP (IST-508011), and MODELWARE (IST-511731) research projects.
Brian Elvesæter, SINTEF ICT
ICT
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
ICT
EPF Concepts to Create Process Frameworks
Process FrameworkResponsible for creating and modifying work
products
Input or output of performing roles
Assigned to a role in a creation of modification
of a work product
Used to define processes, can relate to other activities to create
work flows
Complete process template for a specific
type of project
Express process knowledge for a key area
of interest
ICT
EPF Composer
� EPF Composer isa tool platform for process engineers,project leads, projectand program managerswho are responsiblefor mainteining and implementing processesfor development organizations or individual projects
� Aims to:� provide for development practitioners a knowledge base of intelectual
capital that allows them to browse, manage and deploy content.
� provide process engineering capabilities by supporting processe engineers and project managers in selecting, tailoring, and rapidly assembling processes for their concrete development process.
ICT
Tutorial:Overview of the COMET Methodology
Developed by:Brian Elvesæter, Arne-Jørgen Berre, Arnor Solberg
SINTEF ICT
ICT
ResourceServiceTier
BusinessServiceTier
UserServiceTier
UserInterfaceTier
LS
RARA
LA
Concepts & Artifacts
Processes
Actors Bu
sin
ess
do
main
Real worldModel world
Web Services
model
Web Servicesimplementationmodel
Web Services
profile
model
Business
model
Domain model
Risk
analysis
Product vision
& product desc.
Requirements
model
boundarySystemboundarymodel
Use caseScenario model
Otherrequirements
Prototype
BCE model
Service-Oriented Architecturemodel
Componentstructure model
Serviceinteractionmodel
Serviceinterfacemodel.
Tech
nic
al
do
main
CO
ME
T m
od
el
arc
hit
ec
ture
ICT
Phases - organisation along time
Iterations:
Requirements Model
Architecture Model
Platform specific Model
Elaboration Specification&ConstructionInception Transition
iter .#1
iter#2
iter#n
iter#n+1
iter#n+2
preliminaryiteration(s)
iter#m
iter#m+1
Business Model
Models
Supporting activitiesProject management
Work productmanagement
Review milestones:
Inc
ep
tio
n R
evie
w
Pro
du
ct
La
un
ch
Te
ch
nic
al
Au
dit
De
mo
ns
tra
tor
Ite
rati
on
Lau
nc
h
De
mo
/ D
eli
ve
ryB
eta
Te
st
La
un
ch
Ac
ce
pt
Me
eti
ng
De
mo
ns
tra
tor
Ite
rati
on
La
un
ch
Pro
toty
pe
Ite
rati
on
La
un
ch
Test
CO
ME
T p
roc
es
s a
rch
ite
ctu
re
ICT
Ex
ten
din
g C
OM
ET
fo
r S
OA
(1
)
Semantic
Space
Service-Oriented
Architecture Model
Web ServiceExecution Artefacts
AgentExecution Artefacts
BPELExecution Artefacts
P2PExecution Artefacts
Web ServiceSpecification Model
Agent SpecificationModel
BPEL SpecificationModel
P2P SpecificationModel
Model Transformation
UML Profile for Web Services
UML Profile for Agents
UML Profile for BPEL
UML Profile for P2P
Model Transformation
Architecture Specification
ATHENA Integrated
Execution Infrastructure
Registry
RepositoryService Wrappers (Enterprise A)
Evaluation & Negotiation of Avai lable Fun ctionality
Enh anced Service Interconnection Bus
Cross-org.
Intra-org.
Existing Enterprise Applications
PublicInfrastructure Services
Service Wrapp ers(Enterprise X)
Service Wrappers(Enterprise Y)
Inte rna lInfrastructure Services
Process Execution Platform(BPEL)
Goal-orientedAdaptive ExecutionPlatform(Agents)
Goal-orientedAdaptive ExecutionPlatform(Agents)
ActiveModel Platfo rm(AKMii)
ActiveModel Platfo rm(AKMii)
Legend
Message-OrientedPlatform(MQS erie s)
Message-OrientedPlatform(MQS erie s)
Server-s ide C omponent Platfo rm(.NET, J2 EE)
Server-s ide C omponent Platfo rm(.NET, J2 EE)
ComposedWebServicePlatform(WebSe rvice s)
Busine ss Process /Agent
Active (Bus ine ss) Mode l
Web/Server Com pone nt
Middlewa re P roce ss/Agent
Middlewa re Com ponent
Ad aptive D istributed R esource Mgt Platform (P 2P)
Deployment
UML Profile for SOA
• Information• Service• Process• QoS
Re
fere
nc
e O
nto
log
yannotated with
Model to Model Transformation
Model to Text
Transformation
OWLOntology
annotated
with
annotated
with
EnterpriseModel
UML Profile for POP*
• Process• Organisation• Product• …
Model to ModelTransformation
Business Requirements
Analysis
annotated with
ICT
Outline
� Motivation – Why systems development methodology?
� Method engineering
� MDD Process Framework (MDD PF) and Software Process Engineering Metamodel (SPEM)
� Eclipse Process Framework (EPF)
� COMET methodology
� References
ICT
F7: Enterprise Architecture and Enterprise Modeling
� Enterprise Architecture
� Systems Architecture
� Methodologies (e5, p111-140, SEI/CMM, Zachman)
� Architectural Frameworks (C4ISR-AF, RM-ODP, MAF, TOGAF/DODAF, ….
� Enterprise Unified Process
� Enterprise Modeling
� ATHENA POP*
� ArchiMate example
� Next: COMET Methodology
ICT
PIM-K
CIM-K
Ontologies Bus.Process Bus.Rules Goals NFA/Qualities Org
BPDM, SBVR,
EDOC,UPMS,
PIM4SOA, ODM
PSM-K
BPMN, POP*, ARIS,
ArchiMate,
GERAM, GRAI, Zachman,
UEML, B.Rules. ..
Technologies/Realisation-K
UML profiles and
metamodels for BPEL, WSDL, XML,
XPDL,
OWL-S, WSML, WSDL-S
Technology
Reliastion
Code
Information Process Services Rules NFA UI
Data Wflow/Comp Interfaces Rules NFA UI
XML, BPEL/XPDL, WSDL, SWRL, Security, AJAX
OWL, OWL-S/WSML WSDL-S, Induction, … QoS
Legacy and New systems/services, ERPs/ESAs
ICT
PIM-K
CIM-K
BPDM, SBVR,
EDOC,UPMS,
PIM4SOA, ODM
TR/QVT
PSM-K
TR/QVT
BPMN, POP*, ARIS,
ArchiMate,
GERAM, GRAI, Zachman,
UEML, B.Rules
BPEL, WSDL, XML, XPDL,
OWL-S, WSML, WSDL-S
TR/M2T ADM
ADM
ADM
UML profiles and
metamodels for BPEL, WSDL, XML,
XPDL,
OWL-S, WSML, WSDL-S
Code
PIM-K
CIM-K
TR/QVT
PSM-K
TR/QVT
BPEL, WSDL, XML, XPDL,
OWL-S, WSML, WSDL-S
TR/M2T ADM
ADM
ADM
Code
Semantic
Interoperability
Part 3: MDI
Model Driven
Interoperabtiliy
Organisational
Interoperability
Technical
Interoperability
ICT
F8: COMET Business Modelling
with WesternGeco Survey Booking
Reference Example
ICT
Platform specific
model
UMT Config model
Component implementationmodel
Bu
sin
ess D
om
ain
Syste
m D
om
ain
Model world Real world
Concepts& Artifacts
Processes
Actors
Business
model Goal Model
Architecturemodel
Requirementsmodel
Use case Scenario Model
Otherrequirements
Prototype
Visionfor change
Context statement
Risk analysis
Business Process & RoleModelWARM
Business Resource Model
PIM Data Types
Context Businessmodel Goal Model
Visionfor change
Context statement
Risk analysis
Business Process & RoleModel
Business Resource Model
0,1
0,1
System Boundary
*
**
*
Deployment
User Service
Tier
User Resource
Service TierLS
Legacy
Business
Service
Tier
Resource
Service
Tier
Presentation Tier
User Dialog Tier
Co
mp
on
en
t Infra
stru
ctu
re &
Wo
rkflo
w E
ng
ine (
Mic
row
ork
flow
)
User
Serv
ice
Do
main
Bu
sin
ess S
erv
ice
Do
main
User
Interface
Tier
RARA
LA
Workflow Service Domain
Component structureand internal design
Interface and interaction specification
Busines domain to system domainmapping
•Subsystem grouping and BCE
(Combine Ref Arch)•BM analysis
Work Element Analysis Model
BCE Model
ICT
F9: INF5120Modellbasert systemutvikling
� SOA architectures and platforms� COMET architecture modelling� PIM4SOA and UPMS
Forelesning 19.03.2007
Brian Elvesæter
ICT
F9: Outline
� SOA architecture and platforms� Service-oriented architecture (SOA)
� SOA reference models
� SOA platforms
� COMET architecture modelling
� PIM4SOA and UPMS
ICT
ICT
Architecture model template in RSM
ICT
Reference architecture analysis
� Recall the Reference Architecture with associated tiers and component types.
� Analyse the System Boundary part of the Use Case Model with regards to the Reference Architecture.� The System Boundary correspond to the boundaries
of the component of concern for the actual project, typically an Application Component.
� After the identification of this "main" component the next step is to analyze the System Boundary Model with respect to its set of use cases and actors.
� Divide the System Boundary Model into a set of subsystems.� Each subsystem will cover a collection of the System
Boundary use cases.
� The subsystems are non-exclusive, implying that a use case might be part of more than one subsystem.
� The result of this task is a functional decomposition of the main component, with reiterated versions of the use cases.
ICT
Application component (AC) structure
BookingEditor BookingViewer SubscriptionEditor
SubscriptionService
ISubscription
SubscriptionInfo
ISubscriptionInfo
EmailBrowser
BookingService
IBookingService
ActivityInfo
IActivityInfo
INotifyEmailServer
SMTP
POP
Survey Booking AC Subscription Management AC
Existing Email Service
ICT
Component model in RSM
ICT
PIM4SOAMetamodel
Web ServicesMetamodel
Agent Metamodel(AgentMM)
P2PMetamodel
GridMetamodel
PIM
PS
Ms
Symbols
Metamodel
Concept
Relationship
Correspondence
PIM4SOA → platform specific models
ICT
Metamodel for (software) services Metamodel for (automated software) processes
Metamodel for information Metamodel for quality of service (QoS)
PIM4SOA addresses four system aspects
Services are an abstraction and an encapsulation of the functionality provided by an autonomous entity. Service architectures are composed of functions provided by a system or a set of systems to achieve a shared goal.
Web Services Architecture as proposed by W3C (W3C 2004)UML Profile for Enterprise Distributed Object Computing (OMG 2002)
Information is related to the messages or structures exchanged, processed and stored by software systems or software components.
Structural constructs for class modelling in UML 2.0 (OMG 2003)UML Profile for Enterprise Distributed Object Computing (OMG 2002)
Processes describe sequencing of work in terms of actions, control flows, information flows, interactions, protocols, etc.
Business Process Definition Metamodel (BPDM) (IBM et al. 2004)UML Profile for Enterprise Distributed Object Computing (OMG 2002)
Extra-functional qualities that can be applied to services, information and processes.
UML Profile for Modeling Quality of Service and Fault Tolerance Characteristics and Mechanisms (OMG 2004)
ICT
PIM4SOA: Metamodel for (software) services
ICT
INF5120Modellbasert systemutvikling
� F10: Web Services XML Schema
WSDL
BPEL
Forelesning 26.03.2007
Roy Grønmo
ICT
Outline
� Web Services – Infrastructure and Architecture
� XML Introduction
� XML Schema
� Web Service Description Language (WSDL)
� Business Process Execution Language (BPEL)
ICT
XSD: UML profile for XSD
� UML representation of XML schema.
� Useful in a UML-centric development method if the modelling environment supports generation/import of XSD documents.
ICT
UML profile for WSDL
UML representation Text representation
ICT
UML profile for BPEL
ICT
PIM4SOA main mappings to BPEL
This defines a specific use of a PartnerLink, alongside what role we
are playing, and even the PortType being used. See links to the
WSDL transformation described below.
PartnerLink, Role(…) CollaborationUsePath
The CollaborationUses defined for the ServiceProvider tell us what
PartnerLinks we will need. See CollaborationUsePath.
PartnerLinkCollaborationUseRoleBinding
All messages sent and received must have appropriate variables
defined within the BPEL
VariableMessage
Interactions have a role to play both in determining collaboration type
(see Task (ii) above), and passing particular parts of messages
between tasks (data flow, a BPEL assign).
AssignInteraction, Pin
The structure of flows between Steps must be analysed to deduce the
applicable BPEL structure.
Sequence, Flow, (…)Flow
This might be a task requiring further implementation or human
interaction beyond the scope of the PIM4SOA.
EmptyTask (ii) (no collaboration use)
The type of communication with other service providers must be
deduced from parameters passed to or from the task in question.
Receive, Invoke, ReplyTask (i) (participating in collaboration)
ProcessServiceProviderProcess
NotesBPEL
equivalent
PIM4SOA element
ICT
F11: INF5120Modellbasert systemutvikling
� Interoperability� ATHENA Interoperability Framework (AIF)� European Interoperability Framework (EIF)
Forelesning 16.04.2007
Brian Elvesæter
ICT
Outline
� Interoperability� Interoperability scenarios
� ATHENA Interoperability Framework (AIF)� ATHENA Interoperability Profiles (AIPs)
� Application of the AIF
� Evaluation, conclusion and future work
� European Interoperability Framework (EIF)
ICT
ATHENA Interoperability Reference Architecture
Enterprise/Business
Processes
Services
Information/Data
Cross-OrganisationalBusiness Processes
Collaborative EnterpriseModelling
Flexible Execution and Composition of Services
InformationInteroperability
Mo
de
l-D
rive
n In
tero
pe
rab
ility
Sem
an
tics a
nd
On
tolo
gie
s
Enterprise/Business
Processes
Services
Information/Data
Provided Required
ICT
Interoperability framework
ICT
Baseline methodology
EIMM
Interoperabilityanalysis
Requirementssolutionmapping
Test definition
Implementation
Testing
IIAM
Implicit strategicbusiness
needsOptimized
co-operationmodel
Interoperabilitymaturity and
modelling approach
Requirements related to
business needs
Solution blueprint(generic solutions)
Solution instance(actual solutions)
Testprocedure
Solutionimplementation
ROI(impact)
Methodology overview(V-model view)
Formalized interoperability business needs
BIF
ICT
Enterprise/Business
Processes
Services
Information/Data
Cross-OrganisationalBusiness Processes
Collaborative EnterpriseModelling
Flexible Execution and Compof Services
InformationInteroperability
Mo
de
l-D
rive
n I
nte
rop
era
bili
ty
Sem
an
tics a
nd
On
tolo
gie
s
Enterprise/Business
Processes
Services
Information/Data
Provided Required
Organisational Interoperability
Semantic Interoperability
Technical Interoperablity
AIF EIF version 1
Harmonisation of AIF and EIF
Enterprise/Business
Processes
Services
Information/Data
Cross-OrganisationalBusiness Processes
Collaborative EnterpriseModelling
Flexible Execution and Compof Services
InformationInteroperability
Mo
de
l-D
rive
n I
nte
rop
era
bili
ty
Se
ma
ntics a
nd
On
tolo
gie
s
Enterprise/Business
Processes
Services
Information/Data
Provided Required
EIFversion 2AIF
ICT
Offentlig, Innbygger, Næringsliv A
Organisatoriskinteroperabilitet
Semantiskinteroperabilitet,InformasjonsInnhold med mening for:
Tekniskinteroperabilitet(Tekniskestandarder)
PresentasjonProsessTjenesteInformasjon/Data
PresentasjonProsessTjenesterDataAdm/MetadatSikkerhetTekn. sem/org
ArbeidsProsessMålOrganisasjonProduktBegrep
Offentlig, Innbygger, Næringsliv B
Organisatoriskinteroperabilitet
Semantiskinteroperabilitet,InformasjonsInnhold med mening for:
Tekniskinteroperabilitet(Tekniskestandarder)
PresentasjonProsessTjenesteInformasjon/Data
PresentasjonProsessTjenesterDataAdm/MetadatSikkerhetTekn. sem/org
ArbeidsProsessMålOrganisasjonProduktBegrep
Organisatorisk harmonisering,spesielt rundt prosess
Felles forståelse av mening/semantikk i innhold ved
bruk av teknologier forpresentasjon/prosess/tjeneste/data
Samvirkende teknologier
Organisatorisk interoperabilitet
Semantisk interoperabilitet
Teknisk interoperabilitet
Tekniskinterkonnektivitet
MellomvarePlattformLagring/Nettverk
Tekniskinterkonnektivitet
MellomvarePlattformLagring/Nettverk
Teknisk interkonnektivitet
Transport (HTTPS, FTP)Overføring (IP, IPv6)
Bit transport (WAN, WiFi, LAN)
Norwegian eGovernmentInteroperability Reference Model
ICT
F12: OWL Classes
OWLRestriction
RDFSCl ass
(from RDFS)
OWLClass
com plete : Boolean
deprecated : Boolean
0..*
+OWLdisjo intWi th
0..*0..*
+OWLequivalentClass
0..*
Individual
Enum eratedClass
1..*+OWLoneOf 1..*
In tersectio nClass Unio nCl ass
OWLClass
2..*+OWLintersectionOf 2..*
2..*
+OWLunionOf
2..*
Co mp lem e ntC lass
1
+OWLco m ple me ntOf
1
ICT
The Tree of Knowledge Technologies (Utvidet med basis fra Top Quadrant)
SAWSDL
EXPRESS
ISO 15926
CC
ICT
UML Ontology profile
ICT
Current MDA Architecture with Semantic annotations
CIM/EMmodels
PIMSystemmodels
PSMSystemmodels
System
ADM
QVT
QVT
MOF2Txt
ADM
ADM
Enterprisemodeling
expert
Systemmodeling
expert
Systemrealisationinstallation
expert
Ref.ontology
Semanticannotation
Semanticannotation
Semanticannotation
ICT
Current MDA Interoperability Architecture
CIM/EMmodels
PIMSystemmodels
PSMSystemmodels
System
Ref.ontology
Semanticannotation
Semanticannotation
Semanticannotation
CIM/EMmodels
PIMSystemmodels
PSMSystemmodels
System
Semanticannotation
Semanticannotation
Semanticannotation
Sem.mapping
Technicalmapping
Interoperabilityexecution
IF IF
ICT
Semantiske Teknologier
� Ontologier
� RDF og OWL
� Topic Maps, ISO 15926, UML og andre
� 2 papers:
� Semaphore model mapping (Semaphore paper)
� Sammenlikning av model mapping og bruk av ontologier (Semantic mapping: ontology-based vs. model-based approachAlternative or complementary approaches?)
ICT
Semantisk Interoperabilitet gjennomreferanse til felles ontologier
Service-orientertIT system
Virksomhet Virksomhet
Service-orientertIT system
Forretningsorientering
Brukerorientering
Semantisk orientering
Serviceorientert
IT
Informasjon*TjenesteProsess
Ontologier
Serviceorientert
IT
Modellorientering
Forretningsorientering
ICT
Run-time
Sem
Annot
Set
#2
InternetSem
Rec
Rules
#2
Local
Software
&
Data
SwApp#1
Local
Software
&
Data
SwApp#2
Sem
Annot
Set
#1
Sem
Rec
Rules
#1
ReferenceOntology
Semantic Annotation
Reconciliation
Design-time
ICT
Step 3 – Create mediator/transformation
ICT
SAWSDL - Semantic Annotations for WSDL and XML Schema
� W3C Working Draft 10 April 2007
� This specification defines a set of extension attributes for the Web Services Description Language and XML Schema definition language that allows description of additional semantics of WSDL components. The specification defines how such semantic annotation is accomplished using references to semantic models, e.g. ontologies
� 3 constructs: modelReference, liftingSchemaMapping, loweringSchemaMapping
ICT
A Web Service Composition Scenario with Ontology Reasoning
ICT
Semantic Annotations for WSDL and XML Schema
� W3C Working Draft 10 April 2007
� This specification defines a set of extension attributes for the Web Services Description Language and XML Schema definition language that allows description of additional semantics of WSDL components. The specification defines how such semantic annotation is accomplished using references to semantic models, e.g. ontologies. SAWSDL does not specify a language for representing the semantic models. Instead it provides mechanisms by which concepts from the semantic models, typically defined outside the WSDL document, can be referenced from within WSDL and XML Schema components using annotations.
ICT
Enterprise/Business
Processes
Services
Information/Data
Cross-OrganisationalBusiness Processes
Collaborative EnterpriseModelling
Flexible Execution and Compof Services
InformationInteroperability
Mo
de
l-D
rive
n I
nte
rop
era
bili
ty
Sem
an
tics a
nd
On
tolo
gie
s
Enterprise/Business
Processes
Services
Information/Data
Provided Required
Organisational Interoperability
Semantic Interoperability
Technical Interoperablity
AIF EIF version 1
Harmonisation of AIF and EIF
Enterprise/Business
Processes
Services
Information/Data
Cross-OrganisationalBusiness Processes
Collaborative EnterpriseModelling
Flexible Execution and Compof Services
InformationInteroperability
Mo
de
l-D
rive
n I
nte
rop
era
bili
ty
Se
ma
ntics a
nd
On
tolo
gie
s
Enterprise/Business
Processes
Services
Information/Data
Provided Required
EIFversion 2AIF
ICT
F13: Model-driven Development of Agent Systems:
A Platform-Independent Model for Agents to improve Interoperability between Platforms
Christian HahnMultiagent System Group
German Research Center for Artificial Intelligence (DFKI GmbH), Saarbrücken
Guest researcher, SINTEF, Oslo, as part of theINTEROP project
ICT
Platform-Independent Model for Agents (PIM4Agents)
Agent is the autonomous entity capable of acting in the environment
Behaviour describes the internal processes
Protocol describes interaction between agents/organisations
Message exchange is described in protocols
Cooperation between agents
Role: domain-specific & application-specific roles
ICT
F14
AOSD - Enhancing SoC AOSD :: Aspect Oriented Software DevelopmentSoC :: Separation of Concerns
ICT
Agenda
1. SoC mechanisms in software development
a. SoC – a definition
b. OO technology / Object “thinking”c. Enhancements to OO-technology
d. Agents and Services
e. Model-centric “thinking”
2. AOSD – Aspect-Oriented Software Developmenta. Motivation
b. Introduction
c. Aspectsd. Benefits
3. AOP - Examplea. AspectJ
� AOM – Aspect Oriented Modeling
a. AOM in general
b. AOMDF – Overviewc. AOMDF - Interactions
d. The Theme Approach
� Summarizing thoughts� Summarizing thoughts� Future
� References
ICT
4a. AOM in general� Fusing AO-concepts and Model Driven Engineering
� Leveraging the strengths of two great advancements in software development
� The Theme Approach
� Theme/Doc (analysis)
� Theme/UML (design)
� Partial tool support
� AOMDF (Aspect Oriented Model Driven Framework)
� Structural and behavioural AOM, extends UML
� Automated model compositions of Class diagrams and Sequence diagrams
� Tools support in near future
� Design only
� Many other approaches, but the one’s mentioned above are the most mature / complete. The Theme approach is the most known of them all.
ICT
4a. AOM in general (2)
� Reference Architecture for AOM:
ICT
Eksamen
� Case-basert oppgave (ref. tidligere eksamen), men der mer av de initielle modellene/metamodeller nå blir gitt i oppgaven (pga begrenset tid)
� Alle skriftlige hjelpemidler er tillatt
� Fredag 1. juni kl. 14:30 (3 timer)
ICT
Pensum litteratur
� F – Foiler fra alle forelesningene, F1 – F15
� Artikler: ”MDI - Model Driven Interoperability”, � ATHENA Interoperability Framework
� Semaphore
� Model Driven Ontology
� Aspects, AOM
ICT
Pensum litteratur� F – Foiler fra alle forelesningene, F1 – F14
� Bok: Model-Driven Software Development: Technology, Engineering, Management (Paperback) by Thomas Stahl, Markus Voelter, Krzysztof Czarnecki
� Handbook: ”COMET Methodology” , A.J. Berre & B. Elvesæter
� Papers: ”MDI - Model Driven Interoperability”, A.J. Berre & B. Elvesæter
� ATL - http://www.eclipse.org/gmt/atl/ og http://www.modelbased.net/
� MOFScript - see http://www.eclipse.org/gmt/mofscript/
ICT
Model-Driven Software Development
� Part I. – Introduction (1-5)
� Part II – Domain architectures (6-12)
� Part III – Processes and Engineering (13-17)
� Part IV – Management (18-20)
ICT
Model-Driven Software Development
� 1. Introduction
� 2. MDSD – Basic ideas and terminology
� 3. Case-study: A typical Web application
� 4. Concept Formation
� 5. Classfication
� 6. Metamodeling
� 7. MDSD-capable target architectures.
� 8. Building Domain Architectures
� 9. Code Generation Techniques
� 10. Model transformations with QVT
ICT
Model-Driven Software Development
� 11. MDSD Tools: Roles, architecture, selection criteria, and pointers
� 12. The MDA standard
� 13. MDSD Process building blocks and best practices
� 14. Testing
� 15. Versioning
� 16. Case study: Embedded component infrastructures
� 17. Case study: An Enterprise system
� 18. Decision support
� 19. Organisational aspects
� 20. Adoption strategies for MDSD
A. Model transformation code: QVT relations/mappings
