The work of the OMG has been driven since 1990 by a clear architectural statement
that has not changed much since it was first designed. The Object Management
Architecture (OMA) provided the vision and roadmap for the problem that the OMG
has always addressed, the problem of integration. Having created the CORBA
interoperability standards, OMG has in the past used them almost exclusively when
creating standards for use in particular application domains. However, since 1997 the
scope of the organization has broadened significantly. In 1997 the OMG issued several
important specifications that are not CORBA based, including the Unified Modeling
Language™ (UML™) and the Meta Object Facility™ (MOF™), and later XML
Metadata Interchange™ (XMI™) and the Common Warehouse Metamodel™
(CWM™).
When the OMG was issuing only CORBA-oriented standards, the manner in which its
various standards fit together was quite well understood, and clearly mapped by the
OMA. The emergence of these new kinds of standards, and their potential use in
defining other standards, necessitates that we expand our vision of the OMG’s
architecture.
This paper is a statement by the OMG Architecture Board (AB) of how it sees the
relationships among these standards and how they can be used today in a coordinated
fashion. It discusses new standards work that would fill in some significant gaps we
have identified. It does not attempt to address all standardization activities of OMG. It
describes how the MDA approach helps in the creation, maintenance and evolution of
standards and dealing with associated problems. It is important to realize that the MDA
is a proposal to expand and not replace the old OMA, to give us a roadmap and vision
that will include and integrate all of the work done to date, and to point the way to
future integration standards.
An important aspect of some of the latest OMG standards is that they greatly advance
the art and science of modeling. We believe that
Did you find this white paper useful?
16 out of 29 users found this white paper useful
Related white papers
Introduction to the FileConnection API
This paper describes the FileConnection API. It also includes a brief description of the example MIDlet that is included in this package and additional details about the API implementation in...
2007 Comparative Assessment Methodology Process for BPEL
By following the BPEL standard, the choice of which BPEL engine to use should not affect interoperability of the orchestrated services or the reuse of the BPEL models or designs....
Setting Up and Using Bluetooth Hardware With Development Tools
The purpose of this paper is to describe how to set up the Bluetooth testing environment for the C++ emulators of Software Development Kits (SDK), such as the Series 60...
Building a Robust Linux Kernel Piggybacking the Linux Test Project
The Linux kernel is growing at a rapid rate and runs across many architectures and platforms; ensuring that the kernel is reliable, robust and stable is very critical. The Linux...
MSDN Webcast: Unit Testing for Mobile Devices (Level 300)
With Microsoft Visual Studio 2008, unit testing is now available for mobile device developers as well. The presenter of this webcast explores unit testing for devices. The attendee will learn...
Introduction to Dependency Injection With Microsoft Enterprise Library Unity Application Block
This webcast introduces the Microsoft Enterprise Library Unity Application Block - a lightweight, extensible dependency injection container with support for constructor, property, and method call injection. Dependency injection is a...
Taking Advantage of Microsoft Enterprise Library 4.0 for Visual Studio 2008
Microsoft Enterprise Library is a collection of reusable software components (application blocks) designed to assist software developers with common enterprise development challenges (such as logging, validation, exception handling, and many...
