OMG Meeting 00Feb 2005
MDA Tool component: Proposal for an OMG RFP
Philippe Desfray 00SOFTEAM
Philippe.desfray@Softeam.fr
OMG Meeting 00June 2005
Disseminating MDA technologies within organizations: what it requires
Define the model driven development approach adapted to your specific context Select the appropriate tools available on the market Customize and integrate them appropriately00/b> Requires high level skills and investments:
Expertise; Time to set up the solution Money00/b> Need to have on the shelf solutions that can be reused, combined and also adapted.
OMG Meeting 00June 2005
Define a development approach that takes benefit from the MDA technology
Define the Model Driven development methodology
Define the viewpoints that will need to be considered during the software development lifecycle Define the artifacts to be built during a software development lifecycle Define the process Define what will be supported by tools or handled manually for each of these viewpoints, for the process and the artifacts Ensure the adoption by each participant: evangelization, documentation, training, tooling 00/b>OMG Meeting 00June 2005
Tooling the Modeling languages that correspond to the dedicated viewpoints
Involves much more than metamodels 00/b>
Metamodel or profile definition Constraints implementation Notation definition and support Model transformations Dedicated tooling: audit, wizards, Usual tooling stuff: GUI, resources, Help on line Documentation 00/b>OMG Meeting 00June 2005
How do we package this?
OMG standards: QVT, UML2, MOF2, OCL, MOF2Text, standard metamodels, Standard profiles (SysML), DSLs, BPMN, XMI Tools: Objecteering, RSA, Together, Ilogix, 00 Adaptive, EMF Specific technologies: Java, VB, Jython, J, etc. Usage of RAS?OMG Meeting 00June 2005
MDA Tool Components: The One missing stone for MDA
An MDA Tool component is a deployable unit of packaging for the support of modeling languages with dedicated tools, services and resources. An MDA Tool Component contains all necessary material to customize an existing modeling environment in order to apply MDA to a specific domain or contextOMG Meeting 00June 2005
MDA Tool Component: Goal
Gluing MDA standards into one deployable artifact Standardizing the configuration of tools to support MDA approaches Allowing tool configuration interoperability and interchangeability Fostering an 芦 expertise 禄 market: MDA Tool Component = expertise component Tool independence: Capitalize knowledge within tool independent MDATCsOMG Meeting 00June 2005
Scope of the RFP
Define how to assemble MDA related artifacts into MDATCs Define an abstract architecture for loading and executing MDA Tool Components. (e.g. hosting tool, MDA Container, MDATC). Specify all the elements necessary for defining an MDATC that can be deployed, loaded and executed, and that contains features to customize the hosting tool Identify platform specific/independent elements of an MDA TC Define standard protocols and API between an MDATC and its environment (as defined by the abstract architecture) necessary to manage, load and run MDA Tool Components. This has to be formalized as a PIM. PSMs have to be defined for specific languages, Java being at least mandatory.OMG Meeting 00June 2005
Related initiatives
The MODELWARE IST European research project dedicated to MDA (ModelBus, model transformation techniques, MDATC, tool orchestration, methodologies) MDATC architecture prototype implemented on top of a commercial tool (Objecteering), centered on Profiles MDATC prototype, implemented as an open source effort, on top of EMF, metamodel centric The Eclipse/ MDDi project dedicated to integrate modeling tools, languages and methodologies in the Eclipse framework to create fully customizable MDD environmentsOMG Meeting 00June 2005
MDATC Draft RFP Version 0.9
Thank you to the numerous reviewers, and the large amount of feedbacks Has been first published in April 2005, 11 mandatory requirements 4 optional requirements To be presented for adoption next OMG meeting Work group address: 'mdac@omg.org'
