The document discusses Model Driven Architecture (MDA), an approach developed by the Object Management Group (OMG) that uses models to manage complexity in software development. MDA aims to improve productivity by making applications more portable, interoperable, and able to evolve independently of platforms. It promotes modeling software at a platform-independent level and then mapping models to specific platforms. The document provides an overview of MDA and examples of how it has been applied to areas like application integration, metadata integration, and data warehousing. It also outlines some ongoing MDA work related to topics like enterprise application integration and model transformations.
Unified Modeling Language (UML) is a modeling language, used for design. Designed based on OMG Standard, Object this helps to express and design documents, software. This is particularly useful for OO design. Here is a brief tutorial that talks about UML usage.
Model-driven Software Engineering in practice: Chapter 3 - MDSE Use casesJordi Cabot
Slides for the mdse-book.com chapter 3: MDSE Use cases
Complete set of slides now available:
Chapter 1 - http://www.slideshare.net/mbrambil/modeldriven-software-engineering-in-practice-chapter-1-introduction
Chapter 2 - http://www.slideshare.net/mbrambil/modeldriven-software-engineering-in-practice-chapter-2-mdse-principles
Chapter 3 - http://www.slideshare.net/jcabot/model-driven-software-engineering-in-practice-chapter-3-mdse-use-cases
Chapter 4 - http://www.slideshare.net/jcabot/modeldriven-software-engineering-in-practice-chapter-4
Chapter 5 - https://www.slideshare.net/mbrambil/modeldriven-software-engineering-in-practice-chapter-5-integration-of-modeldriven-in-development-processes
Chapter 6 - http://www.slideshare.net/jcabot/mdse-bookslideschapter6
Chapter 7 - http://www.slideshare.net/mbrambil/model-driven-software-engineering-in-practice-book-chapter-7-developing-your-own-modeling-language
Chapter 8 - http://www.slideshare.net/jcabot/modeldriven-software-engineering-in-practice-chapter-8-modeltomodel-transformations
Chapter 9 - https://www.slideshare.net/mbrambil/model-driven-software-engineering-in-practice-book-chapter-9-model-to-text-transformations-and-code-generation
Chapter 10 - http://www.slideshare.net/jcabot/mdse-bookslideschapter10managingmodels
This book discusses how approaches based on modeling can improve the daily practice of software professionals. This is known as Model-Driven Software Engineering (MDSE) or, simply, Model-Driven Engineering (MDE).
MDSE practices have proved to increase efficiency and effectiveness in software development. MDSE adoption in the software industry is foreseen to grow exponentially in the near future, e.g., due to the convergence of software development and business analysis.
This book is an agile and flexible tool to introduce you to the MDE and MDSE world, thus allowing you to quickly understand its basic principles and techniques and to choose the right set of MDE instruments for your needs so that you can start to benefit from MDE right away.
The first part discusses the foundations of MDSE in terms of basic concepts (i.e., models and transformations), driving principles, application scenarios and current standards, like the wellknown MDA initiative proposed by OMG (Object Management Group) as well as the practices on how to integrate MDE in existing development processes.
The second part deals with the technical aspects of MDSE, spanning from the basics on when and how to build a domain-specific modeling language, to the description of Model-to-Text and Model-to-Model transformations, and the tools that support the management of MDE projects.
The book covers introductory and technical topics, spanning definitions and orientation in the MD* world, metamodeling, domain specific languages, model transformations, reverse engineering, OMG's MDA, UML, OCL, ATL, QVT, MOF, Eclipse, EMF, GMF, TCS, xText.
http://www.mdse-book.com
Unified Modeling Language (UML) is a modeling language, used for design. Designed based on OMG Standard, Object this helps to express and design documents, software. This is particularly useful for OO design. Here is a brief tutorial that talks about UML usage.
Model-driven Software Engineering in practice: Chapter 3 - MDSE Use casesJordi Cabot
Slides for the mdse-book.com chapter 3: MDSE Use cases
Complete set of slides now available:
Chapter 1 - http://www.slideshare.net/mbrambil/modeldriven-software-engineering-in-practice-chapter-1-introduction
Chapter 2 - http://www.slideshare.net/mbrambil/modeldriven-software-engineering-in-practice-chapter-2-mdse-principles
Chapter 3 - http://www.slideshare.net/jcabot/model-driven-software-engineering-in-practice-chapter-3-mdse-use-cases
Chapter 4 - http://www.slideshare.net/jcabot/modeldriven-software-engineering-in-practice-chapter-4
Chapter 5 - https://www.slideshare.net/mbrambil/modeldriven-software-engineering-in-practice-chapter-5-integration-of-modeldriven-in-development-processes
Chapter 6 - http://www.slideshare.net/jcabot/mdse-bookslideschapter6
Chapter 7 - http://www.slideshare.net/mbrambil/model-driven-software-engineering-in-practice-book-chapter-7-developing-your-own-modeling-language
Chapter 8 - http://www.slideshare.net/jcabot/modeldriven-software-engineering-in-practice-chapter-8-modeltomodel-transformations
Chapter 9 - https://www.slideshare.net/mbrambil/model-driven-software-engineering-in-practice-book-chapter-9-model-to-text-transformations-and-code-generation
Chapter 10 - http://www.slideshare.net/jcabot/mdse-bookslideschapter10managingmodels
This book discusses how approaches based on modeling can improve the daily practice of software professionals. This is known as Model-Driven Software Engineering (MDSE) or, simply, Model-Driven Engineering (MDE).
MDSE practices have proved to increase efficiency and effectiveness in software development. MDSE adoption in the software industry is foreseen to grow exponentially in the near future, e.g., due to the convergence of software development and business analysis.
This book is an agile and flexible tool to introduce you to the MDE and MDSE world, thus allowing you to quickly understand its basic principles and techniques and to choose the right set of MDE instruments for your needs so that you can start to benefit from MDE right away.
The first part discusses the foundations of MDSE in terms of basic concepts (i.e., models and transformations), driving principles, application scenarios and current standards, like the wellknown MDA initiative proposed by OMG (Object Management Group) as well as the practices on how to integrate MDE in existing development processes.
The second part deals with the technical aspects of MDSE, spanning from the basics on when and how to build a domain-specific modeling language, to the description of Model-to-Text and Model-to-Model transformations, and the tools that support the management of MDE projects.
The book covers introductory and technical topics, spanning definitions and orientation in the MD* world, metamodeling, domain specific languages, model transformations, reverse engineering, OMG's MDA, UML, OCL, ATL, QVT, MOF, Eclipse, EMF, GMF, TCS, xText.
http://www.mdse-book.com
This presentation discusses the following topics:
What is XML?
Syntax of XML Document
DTD (Document Type Definition)
XML Schema
XML Query Language
XML Databases
Oracle JDBC
Model-Driven Software Engineering in Practice - Chapter 4 - Model-Driven Arch...Jordi Cabot
Slides for the mdse-book.com chapter 4: MODEL DRIVEN ARCHITECTURE (MDA)
Complete set of slides now available:
Chapter 1 - http://www.slideshare.net/mbrambil/modeldriven-software-engineering-in-practice-chapter-1-introduction
Chapter 2 - http://www.slideshare.net/mbrambil/modeldriven-software-engineering-in-practice-chapter-2-mdse-principles
Chapter 3 - http://www.slideshare.net/jcabot/model-driven-software-engineering-in-practice-chapter-3-mdse-use-cases
Chapter 4 - http://www.slideshare.net/jcabot/modeldriven-software-engineering-in-practice-chapter-4
Chapter 5 - https://www.slideshare.net/mbrambil/modeldriven-software-engineering-in-practice-chapter-5-integration-of-modeldriven-in-development-processes
Chapter 6 - http://www.slideshare.net/jcabot/mdse-bookslideschapter6
Chapter 7 - http://www.slideshare.net/mbrambil/model-driven-software-engineering-in-practice-book-chapter-7-developing-your-own-modeling-language
Chapter 8 - http://www.slideshare.net/jcabot/modeldriven-software-engineering-in-practice-chapter-8-modeltomodel-transformations
Chapter 9 - https://www.slideshare.net/mbrambil/model-driven-software-engineering-in-practice-book-chapter-9-model-to-text-transformations-and-code-generation
Chapter 10 - http://www.slideshare.net/jcabot/mdse-bookslideschapter10managingmodels
This book discusses how approaches based on modeling can improve the daily practice of software professionals. This is known as Model-Driven Software Engineering (MDSE) or, simply, Model-Driven Engineering (MDE).
MDSE practices have proved to increase efficiency and effectiveness in software development. MDSE adoption in the software industry is foreseen to grow exponentially in the near future, e.g., due to the convergence of software development and business analysis.
This book is an agile and flexible tool to introduce you to the MDE and MDSE world, thus allowing you to quickly understand its basic principles and techniques and to choose the right set of MDE instruments for your needs so that you can start to benefit from MDE right away.
The first part discusses the foundations of MDSE in terms of basic concepts (i.e., models and transformations), driving principles, application scenarios and current standards, like the wellknown MDA initiative proposed by OMG (Object Management Group) as well as the practices on how to integrate MDE in existing development processes.
The second part deals with the technical aspects of MDSE, spanning from the basics on when and how to build a domain-specific modeling language, to the description of Model-to-Text and Model-to-Model transformations, and the tools that support the management of MDE projects.
The book covers introductory and technical topics, spanning definitions and orientation in the MD* world, metamodeling, domain specific languages, model transformations, reverse engineering, OMG's MDA, UML, OCL, ATL, QVT, MOF, Eclipse, EMF, GMF, TCS, xText.
http://www.mdse-book.com
Java Applet
Applet is a special type of program that is embedded in the webpage to generate the dynamic content. It runs inside the browser and works at client side.
Advantage of Applet
There are many advantages of applet. They are as follows:
It works at client side so less response time.
Secured
It can be executed by browsers running under many plateforms, including Linux, Windows, Mac Os etc.
Drawback of Applet
Plugin is required at client browser to execute applet.
J2EE Web Tier Structure and Framework MVC. This presentation includes J2EE web tier framework design. model-View-controller(MVC) is briefly described in the slides.Model View controller separates the development of an application modules in three main categories: one for the application model with its data representation and business logic, the second for views that provide data presentation and user input, the third for a controller to dispatch requests and control flow.
Welcome to my series of articles on Unified Modeling Language. This is "Session 7 – Deployment Diagram" of the series. Please view my other documents where I have covered each UML diagram with examples
This presentation discusses the following topics:
What is XML?
Syntax of XML Document
DTD (Document Type Definition)
XML Schema
XML Query Language
XML Databases
Oracle JDBC
Model-Driven Software Engineering in Practice - Chapter 4 - Model-Driven Arch...Jordi Cabot
Slides for the mdse-book.com chapter 4: MODEL DRIVEN ARCHITECTURE (MDA)
Complete set of slides now available:
Chapter 1 - http://www.slideshare.net/mbrambil/modeldriven-software-engineering-in-practice-chapter-1-introduction
Chapter 2 - http://www.slideshare.net/mbrambil/modeldriven-software-engineering-in-practice-chapter-2-mdse-principles
Chapter 3 - http://www.slideshare.net/jcabot/model-driven-software-engineering-in-practice-chapter-3-mdse-use-cases
Chapter 4 - http://www.slideshare.net/jcabot/modeldriven-software-engineering-in-practice-chapter-4
Chapter 5 - https://www.slideshare.net/mbrambil/modeldriven-software-engineering-in-practice-chapter-5-integration-of-modeldriven-in-development-processes
Chapter 6 - http://www.slideshare.net/jcabot/mdse-bookslideschapter6
Chapter 7 - http://www.slideshare.net/mbrambil/model-driven-software-engineering-in-practice-book-chapter-7-developing-your-own-modeling-language
Chapter 8 - http://www.slideshare.net/jcabot/modeldriven-software-engineering-in-practice-chapter-8-modeltomodel-transformations
Chapter 9 - https://www.slideshare.net/mbrambil/model-driven-software-engineering-in-practice-book-chapter-9-model-to-text-transformations-and-code-generation
Chapter 10 - http://www.slideshare.net/jcabot/mdse-bookslideschapter10managingmodels
This book discusses how approaches based on modeling can improve the daily practice of software professionals. This is known as Model-Driven Software Engineering (MDSE) or, simply, Model-Driven Engineering (MDE).
MDSE practices have proved to increase efficiency and effectiveness in software development. MDSE adoption in the software industry is foreseen to grow exponentially in the near future, e.g., due to the convergence of software development and business analysis.
This book is an agile and flexible tool to introduce you to the MDE and MDSE world, thus allowing you to quickly understand its basic principles and techniques and to choose the right set of MDE instruments for your needs so that you can start to benefit from MDE right away.
The first part discusses the foundations of MDSE in terms of basic concepts (i.e., models and transformations), driving principles, application scenarios and current standards, like the wellknown MDA initiative proposed by OMG (Object Management Group) as well as the practices on how to integrate MDE in existing development processes.
The second part deals with the technical aspects of MDSE, spanning from the basics on when and how to build a domain-specific modeling language, to the description of Model-to-Text and Model-to-Model transformations, and the tools that support the management of MDE projects.
The book covers introductory and technical topics, spanning definitions and orientation in the MD* world, metamodeling, domain specific languages, model transformations, reverse engineering, OMG's MDA, UML, OCL, ATL, QVT, MOF, Eclipse, EMF, GMF, TCS, xText.
http://www.mdse-book.com
Java Applet
Applet is a special type of program that is embedded in the webpage to generate the dynamic content. It runs inside the browser and works at client side.
Advantage of Applet
There are many advantages of applet. They are as follows:
It works at client side so less response time.
Secured
It can be executed by browsers running under many plateforms, including Linux, Windows, Mac Os etc.
Drawback of Applet
Plugin is required at client browser to execute applet.
J2EE Web Tier Structure and Framework MVC. This presentation includes J2EE web tier framework design. model-View-controller(MVC) is briefly described in the slides.Model View controller separates the development of an application modules in three main categories: one for the application model with its data representation and business logic, the second for views that provide data presentation and user input, the third for a controller to dispatch requests and control flow.
Welcome to my series of articles on Unified Modeling Language. This is "Session 7 – Deployment Diagram" of the series. Please view my other documents where I have covered each UML diagram with examples
Model-Driven Software Engineering in Practice - Chapter 2 - MDSE PrinciplesMarco Brambilla
Slides for the mdse-book.com chapter 2: Model-driven Software Engineering Principles.
Complete set of slides now available:
Chapter 1 - http://www.slideshare.net/mbrambil/modeldriven-software-engineering-in-practice-chapter-1-introduction
Chapter 2 - http://www.slideshare.net/mbrambil/modeldriven-software-engineering-in-practice-chapter-2-mdse-principles
Chapter 3 - http://www.slideshare.net/jcabot/model-driven-software-engineering-in-practice-chapter-3-mdse-use-cases
Chapter 4 - http://www.slideshare.net/jcabot/modeldriven-software-engineering-in-practice-chapter-4
Chapter 5 - https://www.slideshare.net/mbrambil/modeldriven-software-engineering-in-practice-chapter-5-integration-of-modeldriven-in-development-processes
Chapter 6 - http://www.slideshare.net/jcabot/mdse-bookslideschapter6
Chapter 7 - http://www.slideshare.net/mbrambil/model-driven-software-engineering-in-practice-book-chapter-7-developing-your-own-modeling-language
Chapter 8 - http://www.slideshare.net/jcabot/modeldriven-software-engineering-in-practice-chapter-8-modeltomodel-transformations
Chapter 9 - https://www.slideshare.net/mbrambil/model-driven-software-engineering-in-practice-book-chapter-9-model-to-text-transformations-and-code-generation
Chapter 10 - http://www.slideshare.net/jcabot/mdse-bookslideschapter10managingmodels
This book discusses how approaches based on modeling can improve the daily practice of software professionals. This is known as Model-Driven Software Engineering (MDSE) or, simply, Model-Driven Engineering (MDE).
MDSE practices have proved to increase efficiency and effectiveness in software development. MDSE adoption in the software industry is foreseen to grow exponentially in the near future, e.g., due to the convergence of software development and business analysis.
This book is an agile and flexible tool to introduce you to the MDE and MDSE world, thus allowing you to quickly understand its basic principles and techniques and to choose the right set of MDE instruments for your needs so that you can start to benefit from MDE right away.
The first part discusses the foundations of MDSE in terms of basic concepts (i.e., models and transformations), driving principles, application scenarios and current standards, like the wellknown MDA initiative proposed by OMG (Object Management Group) as well as the practices on how to integrate MDE in existing development processes.
The second part deals with the technical aspects of MDSE, spanning from the basics on when and how to build a domain-specific modeling language, to the description of Model-to-Text and Model-to-Model transformations, and the tools that support the management of MDE projects.
The book covers introductory and technical topics, spanning definitions and orientation in the MD* world, metamodeling, domain specific languages, model transformations, reverse engineering, OMG's MDA, UML, OCL, ATL, QVT, MOF, Eclipse, EMF, GMF, TCS, xText.
http://www.mdse-book.com
Layer between OS and distributed applications,Hides complexity and heterogeneity of distributed system ,Bridges gap between low-level OS communications and programming language abstractions,Provides common programming abstraction and infrastructure for distributed applications.
Middleware and Middleware in distributed applicationRishikese MR
The seminar discuss about the common middleware concept and middleware in distributed applications .Also we discuss about 4 different types of middleware. MOM( Message oriented Middleware), ORB (object request broker), TP Monitors, Request procedure calls RPC.
The slide also gives the advantages and disadvantages of each.
Standard Issue: Preparing for the Future of Data ManagementInside Analysis
The Briefing Room with Robin Bloor and Jaspersoft
Slides from the Live Webcast on Sept. 18, 2012
As change continues to sweep across the data management industry, many organizations are looking for ways to prepare their systems and personnel for an unpredictable future. Forces such as Big Data and Cloud Computing are creating new opportunities and significant challenges for a world filled with legacy systems. Information architectures are fundamentally changing, and that's good news for companies that can take advantage of recent innovations.
Check out this episode of The Briefing Room to learn from veteran Analyst Robin Bloor, who will explain why the Information Oriented Architecture provides a stable roadmap for companies looking to harness a new era of corporate computing. He'll be briefed by Mike Boyarski of Jaspersoft, who will tout his company's history of integrating with highly diverse information systems. He'll also discuss Jaspersoft's standards-based, Cloud-ready architecture, and how it enables organizations to embed powerful Business Intelligence capabilities into their existing systems.
http://www.insideanalysis.com
Oracle Middleware and Hardware Complete SolutionFumiko Yamashita
I put together a slide deck which explains the benefit of Oracle Middleware & Hardware offerings together as a complete solution. I hope you'll find it useful....
Enterprise Integration Patterns Revisited (again) for the Era of Big Data, In...Kai Wähner
In 2015, I had two talks about Enterprise Integration Patterns at OOP 2015 in Munich, Germany and at JavaDay 2015 in Kiev, Ukraine. I reused a talk from 2013 and updated it with current trends to show how important Enterprise Integration Patterns (EIP) are everywhere today and in the upcoming years.
Similar to Model Driven Architecture (MDA): Motivations, Status & Future (20)
Dev Dives: Train smarter, not harder – active learning and UiPath LLMs for do...UiPathCommunity
💥 Speed, accuracy, and scaling – discover the superpowers of GenAI in action with UiPath Document Understanding and Communications Mining™:
See how to accelerate model training and optimize model performance with active learning
Learn about the latest enhancements to out-of-the-box document processing – with little to no training required
Get an exclusive demo of the new family of UiPath LLMs – GenAI models specialized for processing different types of documents and messages
This is a hands-on session specifically designed for automation developers and AI enthusiasts seeking to enhance their knowledge in leveraging the latest intelligent document processing capabilities offered by UiPath.
Speakers:
👨🏫 Andras Palfi, Senior Product Manager, UiPath
👩🏫 Lenka Dulovicova, Product Program Manager, UiPath
UiPath Test Automation using UiPath Test Suite series, part 4DianaGray10
Welcome to UiPath Test Automation using UiPath Test Suite series part 4. In this session, we will cover Test Manager overview along with SAP heatmap.
The UiPath Test Manager overview with SAP heatmap webinar offers a concise yet comprehensive exploration of the role of a Test Manager within SAP environments, coupled with the utilization of heatmaps for effective testing strategies.
Participants will gain insights into the responsibilities, challenges, and best practices associated with test management in SAP projects. Additionally, the webinar delves into the significance of heatmaps as a visual aid for identifying testing priorities, areas of risk, and resource allocation within SAP landscapes. Through this session, attendees can expect to enhance their understanding of test management principles while learning practical approaches to optimize testing processes in SAP environments using heatmap visualization techniques
What will you get from this session?
1. Insights into SAP testing best practices
2. Heatmap utilization for testing
3. Optimization of testing processes
4. Demo
Topics covered:
Execution from the test manager
Orchestrator execution result
Defect reporting
SAP heatmap example with demo
Speaker:
Deepak Rai, Automation Practice Lead, Boundaryless Group and UiPath MVP
Securing your Kubernetes cluster_ a step-by-step guide to success !KatiaHIMEUR1
Today, after several years of existence, an extremely active community and an ultra-dynamic ecosystem, Kubernetes has established itself as the de facto standard in container orchestration. Thanks to a wide range of managed services, it has never been so easy to set up a ready-to-use Kubernetes cluster.
However, this ease of use means that the subject of security in Kubernetes is often left for later, or even neglected. This exposes companies to significant risks.
In this talk, I'll show you step-by-step how to secure your Kubernetes cluster for greater peace of mind and reliability.
UiPath Test Automation using UiPath Test Suite series, part 3DianaGray10
Welcome to UiPath Test Automation using UiPath Test Suite series part 3. In this session, we will cover desktop automation along with UI automation.
Topics covered:
UI automation Introduction,
UI automation Sample
Desktop automation flow
Pradeep Chinnala, Senior Consultant Automation Developer @WonderBotz and UiPath MVP
Deepak Rai, Automation Practice Lead, Boundaryless Group and UiPath MVP
Software Delivery At the Speed of AI: Inflectra Invests In AI-Powered QualityInflectra
In this insightful webinar, Inflectra explores how artificial intelligence (AI) is transforming software development and testing. Discover how AI-powered tools are revolutionizing every stage of the software development lifecycle (SDLC), from design and prototyping to testing, deployment, and monitoring.
Learn about:
• The Future of Testing: How AI is shifting testing towards verification, analysis, and higher-level skills, while reducing repetitive tasks.
• Test Automation: How AI-powered test case generation, optimization, and self-healing tests are making testing more efficient and effective.
• Visual Testing: Explore the emerging capabilities of AI in visual testing and how it's set to revolutionize UI verification.
• Inflectra's AI Solutions: See demonstrations of Inflectra's cutting-edge AI tools like the ChatGPT plugin and Azure Open AI platform, designed to streamline your testing process.
Whether you're a developer, tester, or QA professional, this webinar will give you valuable insights into how AI is shaping the future of software delivery.
LF Energy Webinar: Electrical Grid Modelling and Simulation Through PowSyBl -...DanBrown980551
Do you want to learn how to model and simulate an electrical network from scratch in under an hour?
Then welcome to this PowSyBl workshop, hosted by Rte, the French Transmission System Operator (TSO)!
During the webinar, you will discover the PowSyBl ecosystem as well as handle and study an electrical network through an interactive Python notebook.
PowSyBl is an open source project hosted by LF Energy, which offers a comprehensive set of features for electrical grid modelling and simulation. Among other advanced features, PowSyBl provides:
- A fully editable and extendable library for grid component modelling;
- Visualization tools to display your network;
- Grid simulation tools, such as power flows, security analyses (with or without remedial actions) and sensitivity analyses;
The framework is mostly written in Java, with a Python binding so that Python developers can access PowSyBl functionalities as well.
What you will learn during the webinar:
- For beginners: discover PowSyBl's functionalities through a quick general presentation and the notebook, without needing any expert coding skills;
- For advanced developers: master the skills to efficiently apply PowSyBl functionalities to your real-world scenarios.
Key Trends Shaping the Future of Infrastructure.pdfCheryl Hung
Keynote at DIGIT West Expo, Glasgow on 29 May 2024.
Cheryl Hung, ochery.com
Sr Director, Infrastructure Ecosystem, Arm.
The key trends across hardware, cloud and open-source; exploring how these areas are likely to mature and develop over the short and long-term, and then considering how organisations can position themselves to adapt and thrive.
Smart TV Buyer Insights Survey 2024 by 91mobiles.pdf91mobiles
91mobiles recently conducted a Smart TV Buyer Insights Survey in which we asked over 3,000 respondents about the TV they own, aspects they look at on a new TV, and their TV buying preferences.
Elevating Tactical DDD Patterns Through Object CalisthenicsDorra BARTAGUIZ
After immersing yourself in the blue book and its red counterpart, attending DDD-focused conferences, and applying tactical patterns, you're left with a crucial question: How do I ensure my design is effective? Tactical patterns within Domain-Driven Design (DDD) serve as guiding principles for creating clear and manageable domain models. However, achieving success with these patterns requires additional guidance. Interestingly, we've observed that a set of constraints initially designed for training purposes remarkably aligns with effective pattern implementation, offering a more ‘mechanical’ approach. Let's explore together how Object Calisthenics can elevate the design of your tactical DDD patterns, offering concrete help for those venturing into DDD for the first time!
FIDO Alliance Osaka Seminar: Passkeys and the Road Ahead.pdf
Model Driven Architecture (MDA): Motivations, Status & Future
1. Model Driven Architecture (MDA):
Motivations, Status & Future
September 4-7, 2001, Seattle, WA
Sridhar Iyengar
Unisys Fellow
OMG Architecture Board, MDA Evangelist
sridhar.iyengar2@unisys.com
Copyright 2001, UNISYS Corporation Slide 1
2. Presentation Overview
s Introduction - The integration problem
s Motivation for MDA
– Investment Protection of Intellectual and IT Assets
– Managing Technology Innovation and Churn
• Mapping to J2EE
• Mapping to .Net {Web Services - Initial target}
• Mapping to Transition (legacy architecture)
s OMG Model Driven Architecture (MDA) Overview
s MDA Status : What is in the pipeline?
– UML2, Action Semantics, UML Profile for EDOC
– XMI for XML Schemas, CWM Web Services...
s Future of MDA
Copyright 2001, UNISYS Corporation Slide 2
3. s Global services and technology company
– 2000 Revenues : $6.9 Billion
– www.unisys.com
s Focus on Enterprise Class E-Business Solutions and
Servers around the world
– Integrated Solutions for Financial, Telcom, Publishing and Government
markets
– Windows 2000 DataCenter focus (ES7000) and ClearPath Servers
s Actively using several
– OMG MDA Technologies : UML, XMI, MOF, CWM and MDA
– Java Technologies : J2EE, JMI, UML4EJB...
– Microsoft Technologies : Win2K, COM+, .Net platform and tools
– W3C Technologies : XML Suite of standards
s Member of OMG, W3C, UDDI Consortium, OASIS...
Copyright 2001, UNISYS Corporation Slide 3
4. ‘Muddleware’ Architect’s Dilemma
Architect (XML!)
Warehouse
DataMarts Unisys
Builder
SQL/Server LINC,
Oracle Apps DMSII
Middleware (Tuxedo, TIP, DCOM, IIOP, RMI, EJB, COM+, SOAP…)
Information Models/Schemas (MOF, XML, UML, CWM, SPE, BODs, ….)
Warehouse SAP Microsoft BEA
NCR Siebel BI Ware .NET Servers Weblogic
Teradata House SQL Server
Distributed, Heterogeneous, Client/Server !
Multiple Clients, Servers, Tools, Apps, O/S, File systems,
Databases, Repositories, Data Models, Object Models...
Copyright 2001, UNISYS Corporation Slide 4
5. The Technology Salad Bar
(A small subset!)
Capability J2EE COM+ CORBA/OMA Web Services OMG MDA .Net
Network Layer TCP/IP TCP/IP TCP/IP TCP/IP TCP/IP TCP/IP
Web Protocol HTTP HTTP HTTP HTTP HTTP HTTP
Interface Definition Java Microsoft IDL CORBA IDL WSDL IDL/XMI/WSDL WSDL
Meta Language XML XML XML/XMI XML MOF/XML XML
RPC Mechanism RMI DCOM IIOP SOAP; XMLP SOAP; IIOP SOAP
Registry/Repository JNDI; LDAP LDAP; ADSI I/F Repository UDDI MOF;UDDI UDDI
Process Flow Proprietary Proprietary Proprietary ebXML; WSFL UML XLANG
Modeling Language UML UML UML UML UML UML
Copyright 2001, UNISYS Corporation Slide 5
6. Solving the Integration Problem
What is needed?
s Short Answer is XML and HTTP!
s Slightly longer answer is SOAP, WSDL, UDDI
s Even longer answer is SOAP, WSDL, UDDI, WSFL, ebXML,
XAML, ACML, PIPs…
s The real answer is
– Things are a lot messier
– We need to think and build software like engineers and architects
– All these acronyms are great, but where is the process, methodology
and architecture!
– We need to integrate the systems we have with the newer technologies
– We need to rethink ‘Integration Platform’ & ‘Systems Integration
Platform’!
– etc.
Copyright 2001, UNISYS Corporation Slide 6
7. Solving the Integration Problem
What is needed?
s Methodology for building, evolving and integrating software across the life
cycle
s A mechanism for cataloging, indexing and searching enterprise assets
(metadata and data, internal and external)
s A flexible service based distributed component architecture that spans the
enterprise
s A set of shared standard vocabularies (information models) and notation
(meaning and context of data usage)
s A metadata driven approach to automate integration between islands of
information
s A set of open modeling, metadata and distributed computing standards
s Infrastructure products and applications that address these concerns; The
domain expertise needed to use these products and apply it to a customers
situation ---> Unisys Global Industries Technology Roadmap
Copyright 2001, UNISYS Corporation Slide 7
8. The Enterprise Application Life Cycle
Architecture Centric, Business driven,
Complex Life Cycle, Many Tools Manage
Discovery and
Transformation Component
s
Modeling Add Component
Build /Wrap Assemble Configure
Architecture, Business Runtimes
Components & Test &Deploy
Object, Data… Logic (EJB, COM+)
Components Components
Models, Metadata, Mappings, Middleware
Business
Requirem Rigorous Acquired
ents
Components
Modeling
Rapid
And do this with quality in a distributed environment
Copyright 2001, UNISYS Corporation Slide 8
9. Unisys ‘GITA’ Development
Framework (The case for MDA!)
WebGain WebLogic
Rational Rational Rational
RequisitePro Rose VS.NET .NET Svr ClearCase
Business,
Business, Visual
Visual .NET
.NET
.NET or J2EE
.NET or J2EE
Component
Component IDE
IDE or
or Component
Component
Generation &
Generation &
and Data
and Data & Legacy
& Legacy J2EE
J2EE Management
Management
Wrapping Deployment
Deployment
Modeling
Modeling Wrapping Framework
Framework
XMI
XML
XML
.NET Metadata, Models,
.NET MOF UML
MOF UML Components,
J2EE /XMI
/XMI CWM code...
Traceability J2EE CWM
VCS
VCS
Links &
Transformations
Developer
ClearCase
Portal
The Key is Forward & Backward Traceability ––From Components to Requirements
The Key is Forward & Backward Traceability From Components to Requirements
and Business Vision
and Business Vision
GITA : :Unisys Global Industries Technology Architecture
GITA Copyright 2001, UNISYS Corporation
Unisys Global Industries Technology Architecture Slide 9
10. An Overview of OMG Model Driven
Architecture
A vision that uses and integrates the 4M’s - Models,
Metadata, Mapping and Middleware of software.
MDA allows developers and users to productively design,
build, integrate and manage applications throughout the
lifecycle irrespective of hardware or middleware platform
11. OMG History
s 800+ Vendors and End User members
s 1989 OMA Vision & Architecture
s 1991 CORBA 1.0
s 1995 CORBA 2.0 IIOP - CORBA Interoperability
s 1997 UML and MOF adopted, Domain specs
begin to be adopted
s 1999 XMI (XML Metadata Interchange) adopted
s 2000 CWM, XML/Value, EAI, EDOC, XMI for
XML Schema, Additional domain specs begin
s 2001 UML for EDOC, EAI, UML 2.0, MOF 2.0
s 2001 OMG reinvents itself using MDA
Copyright 2001, UNISYS Corporation Slide 11
12. OMG Analysis & Design
Platform Task Force Premise
s The use of Modeling and Metadata enabled
architectures allows us to manage the complexity of
software development, application integration and
data warehouse management
s Modeling and Metadata standards are necessary for
interchange of software artifacts and interoperability
between tools, applications, middleware and data
stores across platforms
The unification of the original OMG vision of
OMA for distributed object interoperability
with this ADTF premise gave birth to MDA
Copyright 2001, UNISYS Corporation Slide 12
13. Solution for Managing Complexity :
MDA: Model Driven Architecture
s An eclectic integration of best practices in
Modeling , Middleware, Metadata, Internet
and Software Architecture
s Model Driven (UML, MOF, CWM…)
– Platform Independent Models (PIM)
– Platform Specific Models (PSM)
– Mappings : PIM <==> PSM
– Applies across the software life cycle
s Key Benefits
– Improved Productivity for Architects,
Designers, Developers and Administrators
– Lower cost of Application Development
and Management
– Enhanced Portability and Interoperability
– Business Models and Technologies evolve
at own pace on platform(s) of choice
Copyright 2001, UNISYS Corporation Slide 13
14. Mapping Platform Independent
Models to Specific Platforms
PIM
Software PSM
Infrastructure E J2EE
4J2E
UM ML
L U
.J2EE
.NET
PIM to PSM UM
L.
UML Transformation Ne
t
Model
PIM
PSM
HealthCare Business
.Net
Application (CIAS)
Copyright 2001, UNISYS Corporation Slide 14
15. OMG MDA - Details
Community & Enterprise Knowledge Portals A
P
L
A
T
HealthCare Financial Manufacturing Insurance... F
O
R
M
E-Business E-Business A
E-Business G
Application Intelligence, N
Application O
Development E.I. Portals S
Integration T
I
C
Mappings to Platforms S
P
Information Models, Metadata Formats E
C
I
Middleware Platforms F
I
C
Copyright 2001, UNISYS Corporation Slide 15
16. OMG MDA - Specific
Models/Work in Progress
Community & Enterprise Knowledge Portals (KM) A
P
L
A
T
HealthCare Financial Manufacturing Insurance... F
O
R
M
E-Business E-Business
E-Business A
Application Intelligence, G
Application N
Development E.I. Portals O
(CWM)
Integration S
(UML, SPEM T
(UML4EAI) I
UML4EDOC) C
Mappings to Platforms (UML4EDOC, UML4EJB, UML.NET*) S
P
Information Models, Metadata (UML, MOF, XMI, XML...) E
C
I
Middleware Platforms (.NET, CORBA, J2EE, SOAP…) F
I
C
* Opportunity Copyright 2001, UNISYS Corporation Slide 16
17. OMG Model Driven Architecture
MDA for Enterprise Integration
UML EDOC Vertical Industry
Applications
UML4EDOC*(PSM)
Model & Design (PIM) UML4EAI*(PSM)
1
200 Business
19 Components
97
Model Driven
Integration for App Integration
Model Driven
0 20
00
App Development
2 01
CORBA EJB
MetaData
Management
UML4CORBA(PSM) UML4EJB* (PSM) Business Process
Integration
PIM : Platform Independent Model
PSM : Platform Specific Model *Coming
Copyright 2001, UNISYS Corporation Slide 17
18. Early examples of MDA
s OMG has been using MDA principles for about 3 years in
several specifications
s Metadata and Object Interchange/Integration
– UML and MOF for modeling, MOF and XMI for metadata integration
– MOF is a subset of UML (Class diagrams) used to model metadata
s Application Development
– UML for modeling, XMI and IDL for tool integration and interchange
– UML profile CORBA : UML for modeling, IDL for Integration
s Data Warehousing
– UML and CWM for Modeling, XMI and IDL for Warehouse
integration
s Application Integration
– UML profile for Enterprise Application Integration (UML4EAI),
Distributed Object Computing (EDOC)
Copyright 2001, UNISYS Corporation Slide 18
19. OMG Model Driven Architecture
MDA for Metadata Integration
Vertical Industry
UML XMI Specifications
Model & Design (PIM) MOF2XML (PSM)
9
199 DTD, Document Data Warehousing
19
97 Schema (XMI 2.0)
B2B Application
Framework Metadata for Integration
(PIM)
Model Driven
7 20
99
App Development
1 01
JMI
MetaData
IDL Management
MOF2IDL (PSM) MOF2Java(PSM)
And So On
PIM : Platform Independent Model
PSM : Platform Specific Model *Opportunity UML2C#
Copyright 2001, UNISYS Corporation Slide 19
20. Transform UML models to DTD
XMI 1.1 : ad/99-10-02, ad/99-10-03
XML UML CWM Travel
Syntax and Encoding X UML
Models UML
Models UML
Documents
M XML Streams (Models)
(Many - based on each metamodel DTD)
MOF
Metadata Definitions
I Validate
& Management MOF UML CWM Travel
DTD DTD DTD
PIM TO
DTD, XML DTD (MetaModels)
UML XML (1 per metamodel used for validation)
Model
Analysis & Design
PSM
Copyright 2001, UNISYS Corporation Slide 20
21. Design-driven XMI for a car
Objects and Designs
Model in XMI
Auto
<Class> Model Interchange
<Name>Auto</Name>
</Class>
Color Door XMI DTD, Schema
<element name=quot;Autoquot; />
<!ELEMENT Auto (Color*, Door*)>
XMI Document
<Auto> Instance Interchange
<Color>red</Color>
<Door>2</Door>
</Auto>
Copyright 2001, UNISYS Corporation Slide 21
22. Transform Models to Schemas
XMI 2.0 OMG Document : ad/01-06-12,13
XML
Syntax and Encoding
X UML
UML
Models
CWM
UML
Models
Travel
UML
Documents
M XML Streams (Models)
(Many - based on each metamodel Schema)
MOF I Validate
Metadata Definitions
& Management 2.0 UML CWM Travel
PIM MOF2 XSD XSD XSD
UML XSD XML Schema(MetaModels)
(1 per metamodel used for validation)
Model
Analysis & Design
PSM
Copyright 2001, UNISYS Corporation Slide 22
23. XMI Production of XML
Schemas : OMG Vote next week
s Bi-directional mappings from UML/MOF to XML
Documents and XML Schema
s Formal metamodels for XML Schema and XML
s Reverse engineering of XML DTDs to assist
transformation to schemas and UML
s Integrate the Analysis and Design of XML
applications to be better integrated with the web
services platform
s Accelerates tool integration and new methods for
modeling web services
Copyright 2001, UNISYS Corporation Slide 23
24. Transform Models to Java
JMI 1.0 Draft : http://jcp.org/jsr/detail/40.jsp.
Java
Syntax and Encoding
J UML
UML
Models
CWM
UML
Models
Travel
UML
Objects
M Java Model Servers
(Many - based on each metamodel Schema)
MOF I Validate
Metadata Definitions
& Management 1.0 UML CWM Travel
PIM MOF2 JAR JAR JAR
Java Java Packages
UML (1 per metamodel used for validation)
Model
Analysis & Design
PSM
Copyright 2001, UNISYS Corporation Slide 24
25. Quick Lessons Learned
s Platforms and protocols come and go
– Some become ubiquitous over time; most don’t
s Just in the pace of 2 years DTD mania has become XML
Schema mania! { YML and ZML are next!)
s We used MDA to map UML/MOF to IDL and XML DTDs
s We used MDA to map UML/MOF to XML Schema
s We used MDA to map UML/MOF to EJB/Java respectively
s We even reverse mapped XML DTD and Documents to UML
s So design your models in UML and transform to DTD, XML
Schema, Java, C#, IDL.. Etc.
s Use well defined, standard design patterns to save time
Copyright 2001, UNISYS Corporation Slide 25
27. Integrating MDA and
Web Services Architecture
We finally apply the MDA principles - Modeling the
Web Services Architecture (and its components) so we
can formally define web service models with rich
semantics (remember the ‘semantic web’) so we can
manage the full application life cycle for .NET
applications.
P.S : We do the same for the next ‘fad’ or ‘real platform’
28. How to apply MDA principles to
Web Services
s Of course we start by modeling the various parts of
the web services architecture
s The key components of the architecture to model are
– XML itself
– UDDI
– WSDL
– Transformations from UML/MOF to these technologies
s These models of models are called ‘Metamodels’ in
OMG parlance
s Having these metamodels and transformation models
assists semantic integration of applications and data
Copyright 2001, UNISYS Corporation Slide 28
29. Mapping Platform Independent
Models to Specific Platforms
PIM PSM
Service Registry OMA - IR
Model BA
OR
UM L 4C
L UM PSM
OMA
DL WSA - WSDL
WSA 4W
S
PIM to PSM UML
UML Transformation UM
Model L4
UD
DI
PIM
Service Definition PSM
WSA: Web Services Architecture
Model OMA: Object Management Architecture WSA - UDDI
IR: Interface Repository
Copyright 2001, UNISYS Corporation Slide 29
30. Metamodels of XML and XML
Schema itself
s XML and XML Schema Model
– Defined in the OMG XML Production for XML Schemas
proposal
– OMG Document # : ad/01-06-12,13
– A complete MOF model using UML notation of XML and
XML Schema is available
– Forward and reverse mappings from UML/MOF to XML
and XML Schema have been specified
s Goal is to over time unify multiple schema models
such as XML Schema, XMI, RDF etc using MOF
s See also UML profile for XML at xmlmodeling.com
Copyright 2001, UNISYS Corporation Slide 30
31. Fragment of XML Schema
Model
Copyright 2001, UNISYS Corporation Slide 31
32. Metamodel of UDDI
s Formally defining a metamodel for UDDI will make
it more easy to integrate the structure and semantics
of other directories and registries
s An alternative approach is to define a generic
interface (JAXR - Java API for XML Registries) -
but this is not likely to capture the richer semantics in
models
s Models of UDDI are being developed at IBM, Unisys
and Microsoft (among other vendors)
Copyright 2001, UNISYS Corporation Slide 32
33. Metamodel of UDDI - Subset
BusinessContact
0.. *
BusinessEntity BusinessService BusinessTemplate
0..*
0..1
IdentifierBag
0..1
This is only a subset of the
UDDI metamodel. A complete
model will be in an upcoming
OMG Proposal.
TModel OverviewDocument
See xmlmodeling.com for a
Copyright 2001, UNISYS Corporation Slide 33
34. Metamodel of WSDL
s Formally defining a metamodel for WSDL will make
it more easy to integrate the structure and semantics
of other interface definition languages (IDL, Java…)
s A formal model (MOF metamodel) of WSDL is
being defined by IBM and Unisys for an OMG
submission
– The CWM Web Services RFP - so that it becomes easier to
integrate analytical web services with the rest of the
database/data warehouse integration infrastrcucture
s This model can be integrated with additional
metamodels of Java and IDL that have already
proposed in OMG specifications
Copyright 2001, UNISYS Corporation Slide 34
35. WSDL Metamodel Fragment
WSDLElement 0..1 Documentation
u nd ef in ed : boo lean text : St ring
+eDocumentation
Exten si b leElem ent
Import
+eImports 0..*
Types
+e Type s
0..1
0..* Message
+eMessages
Defini tio n
+ePortTypes PortType
0..*
+eBindings
Bin din g
0..*
Metamodel : Courtesy IBM +eServices
Service
0..*
Copyright 2001, UNISYS Corporation Slide 35
36. How do we use these metamodels
of WSDL, UDDI and XML!
s Within the OMG suite of metamodels, UML is the
most well known and used to integrate application
development and deployment tools
s CWM - Common Warehouse Metamodel is more
recent, but is a landmark model that addresses the
integration requirement of various types of databases
(network, relational, XML, multidimensional etc,)
s The OMG is now in the process of integrating these
suite of metamodels and the information they
represent into the world of web services.
s A quick peek at CWM will show us the way!
Copyright 2001, UNISYS Corporation Slide 36
37. OMG Common Warehouse
Metamodel (CWM)
s Scope
– Data Warehouse lifecycle metadata interchange and
management
s Initial submission : IBM, Unisys, NCR, Hyperion,
Oracle, Genesis, UBS, Dimension EDI...
– Metamodel - Single logical & physical!
– Generated XML DTDs
– Generated MOF - IDL mappings
– Generated XML document
s Approved by OMG Board in June 2000
s Endorsed by Meta Data Coalition in October 2000
s CWM 1.1 Revision is being now worked on
Copyright 2001, UNISYS Corporation Slide 37
38. CWM Package Architecture
Modular Design org.omg
ObjectModel
CWM
– Minimum dependencies Foundation
<<metamodel>> DataTypes
• Cross package services provided <<metamodel>> TypeMapping
by links to UML <<metamodel>> KeysIndexes
<<metamodel>> Expressions
– Avoid subpackages <<metamodel>> BusinessInformation
<<metamodel>> SoftwareDeployment
Resource
– Reduced complexity, improved <<metamodel>> Relational
understanding <<metamodel>> Record
<<metamodel>> Multidimensional
<<metamodel>> XML
– Use only the packages you Analysis
need <<metamodel>> Transformation
<<metamodel>> Olap
<<metamodel>> BusinessNomenclature
<<metamodel>> DataMining
<<metamodel>> InformationVisualization
Management
<<metamodel>> WarehouseProcess
<<metamodel>> WarehouseOperation
CWMX
Copyright 2001, UNISYS Corporation Slide 38
39. MDA for Data Warehouse
Integration using CWM
Copyright 2001, UNISYS Corporation Slide 39
40. What next for CWM : CWM Web
Services
s CWM is now being used by IBM, Unisys, Hyperion,
Oracle, and many others for integrating enterprise
data, metadata and content
s However this interchange even though it uses XML
(CWM is XMI compliant and uses XML for its
interchange) has the following problems
– The interchange patterns are too fine grained
– The interchange patterns need to be formalized between
the integration partners
– The interchange protocol does not support web services
s To address these needs OMG is standardizing ‘CWM
for Web Services’
Copyright 2001, UNISYS Corporation Slide 40
41. CWM Web Services RFP
s Requires Integration of
– CWM Metamodel
– XMI - The XML DTDs and Schemas that conform to
CWM
– WSDL
– SOAP
– UDDI
s A key principle of OMG MDA is define formal
models (platform independent and platform specific)
of these technologies and their transformations
s The suite of metamodels and transformations being
proposed will integrate MDA and Web Services
Copyright 2001, UNISYS Corporation Slide 41
42. CWM Web Services RFP -
A Potential Solution
s The specific interchange patterns model will be
specified using UML and MOF and this metadata
interchanged using XMI
s Mappings from UML/MOF to WSDL and UDDI will
make it possible to
– Design web services applications and components using
UML
– Manage all related metadata using MOF/XMI and XML
– Automatically publish the interfaces/service definitions in
CORBA IR, UDDI registry and JNDI/LDAP servers!
– Maintain traceability across the life cycle (try this today!)
Please note that the final adopted proposal may be different - Too early to tell!
Copyright 2001, UNISYS Corporation Slide 42
43. MDA meets Web Services bringing
some order to the web services Chaos!
PIM PSM
Service Registry .NET -ADSI
Model N ET
UM OF.
M PSM
UML
L
OMA OF.LD
AP DIR - LDAP
M
UML 1.4 WSA UML4W
App Design PIM to PSM SDL
PSM
Transformation
UML
UM WSA - WSDL
Model L4
ML
U
UD
DI
PIM
Service Definition PSM
WSA: Web Services Architecture
Model OMA: Object Management Architecture WSA - UDDI
ADSI: Active Directory Services Interface
Copyright 2001, UNISYS Corporation Slide 43
44. OMG MDA : What is Coming?
Submissions EJB Java UML Profile for
UML2
EDOC...
UML Profile UML Profile Action
for EJB - JSR 26 JMI - JSR-40
for EAI Semantics
CORBA Med
Evaluating XMI MOF
UML Life Sciences
WSDL EC
EAI EC
EAI
XML
CCM
CWM CCM
UML CWM
UML
Electronic
UDDI Commerce
MOF 2.0 WorkFlow Etc.
CIAS SPEM
Standards MOF UML CCM IDL CWM
UML4CORBA
Copyright 2001, UNISYS Corporation Slide 44
45. What about UML 2.0?
s Massive industry interest (30+ LOIs)
s ‘Gang of 17’ proposal
– Unisys/IBM/Rational/Oracle/Telelogic et al [Show model?]
s Kinetium/Adaptive et al proposal
s 4 others
s Expect
– A radical restructuring of UML/MOF kernel
– Better support for component architectures
– Much better extensibility
– Delays and some surprises!
– Much better next generation tools!
s MOF 2.0 coming on the heels
s UML/MOF/XMI/JMI will power the MDA platform
Copyright 2001, UNISYS Corporation Slide 45
46. Concluding Thoughts
s Ensuring a unified model and metadata driven architecture
is key to solving the heterogeneous integration problem
– Use models and metadata to enable transformation
– Use MDA principles through out the life cycle
– OMG MDA is the realization of this vision
s Most customers have and will continue to have
components/services and information/data from multiple
sources and formats that need integration
s Integration problem continues to be complex and
challenging
– Use MDA principles to abstract complex models, map these
models to platforms and interchange artifacts across life cycle
s Mapping MDA to .NET and J2EE frameworks will make
the developers and systems integrators work easier
– We handle the next platform even more easily!
Copyright 2001, UNISYS Corporation Slide 46
47. For More Information
s OMG : www.omg.org, www.omg.org/cwm
s MDA : www.omg.org/mda
s Unisys : www.unisys.com
s UML : www.omg.org/uml, www.rational.com
s CWM : www.cwmforum.org, www.omg.org/uml
s W3C : www.w3c.org
s DSTC : www.dstc.edu.au
s Sridhar : sridhar.iyengar2@unisys.com
s UML RTF : uml-rtf@omg.org
s MOF RTF : mof-rtf@omg.org
s XMI RTF : xmi-rtf@omg.org
s CWM RTF : cwm-rtf@omg.org
s JMI : http://java.sun.com/aboutJava/communityprocess/jsr
Copyright 2001, UNISYS Corporation Slide 47