200 likes | 300 Views
http://www.shape-project.eu/. SHAPE Project ~ Overview and 1 st Year Results ~. @ Collaboration Meeting for FP6 & FP7 Projects Brussels, 10 & 11 June 2009. Dumitru Roman STI / University of Innsbruck, Austria dumitru.roman@sti2.at. Outline. Project overview Objectives Approach
E N D
http://www.shape-project.eu/ SHAPE Project ~ Overview and 1st Year Results ~ @ Collaboration Meeting for FP6 & FP7 Projects Brussels, 10 & 11 June 2009 Dumitru Roman STI / University of Innsbruck, Austria dumitru.roman@sti2.at
Outline • Project overview • Objectives • Approach • Consortium • Technical solution overview • Metamodels: SoaML and ShaML extensions • Reference matrix • Tool suite • Methodology • Scenarios • Next steps
Outline • Project overview • Objectives • Approach • Consortium • Technical solution overview • Metamodels: SoaML and ShaML extensions • Reference matrix • Tool suite • Methodology • Scenarios • Next steps
SHAPE motivation & objectives Motivation: Lack of comprehensive methodological approaches supporting all phases of a service-oriented system engineering process In an integrated and efficient manner Involving all stakeholders throughout the process Core objectives: Integrated, tool-supported MDE framework for SOA engineering Extensionsto conventional SOA (SHA) Various technology platforms (conventional WS, Agents, SWS, P2P, Grid) Service Variability (configuration and extensions) Standardization via OMG Evaluationin industrial applications (StatoilHydro, Saarstahl)
An MDE approach Metamodels for all aspects relevant for SOA / SHA development Tools for model-driven development by end-users Model Transformations for automated model generation Methodology for guided engineering support
Outline • Project overview • Objectives • Approach • Consortium • Technical solution overview • Metamodels: SoaML and ShaML extensions • Reference matrix • Tool suite • Methodology • Scenarios • Next steps
SoaML Find the latest document at: http://www.omg.org/cgi-bin/doc?ad/08-11-01.pdf Revised submission per November 10th, 2008 See also: www.soaml.org
SoaML goals Intuitive and complete support for modeling services in UML Support for bi-directional asynchronous services between multiple parties Support for Services Architectures where parties provide and use multiple services. Support for services defined to contain other services Easily mapped to and made part of a business process specification Compatibility with UML, BPDM and BPMN for business processes Direct mapping to web services Top-down, bottom up or meet-in-the-middle modeling Design by contract or dynamic adaptation of services To specify and relate the service capability and its contract No changes to UML
ShaML extensions • ShaML – extension of SoaML modelling that aims to capture additional concepts for semantically enabled heterogeneous service oriented architectures • Currently defined for flexible business models and service variability
Reference matrix • The underlying organization scheme for the technologies developed in the project, providing the overall integration view
Tool suite • Business modelling tools • SoaML/ShaML Editor • Variability • Semantics • Adaptativeness • Methodology tool • Adaptation to project needs • Transformations Current integration architecture:
Outline • Project overview • Objectives • Approach • Consortium • Technical solution overview • Metamodels: SoaML and ShaML extensions • Reference matrix • Tool suite • Methodology • Scenarios • Next steps
Next steps • Focus on the extensions for ShaML • Focus on incremental use and evolution of the SHAPE methodology and tools for the two SHAPE pilots • Finalisation of SoaML through FTF work – and related dissemination