1.1 Standards1.2 OMG1.3 Distributed Object Management (DOM)1.5 Object ServicesPicture 4 Detailed view of the OMA1. 6 Conclusion1.7 ReferencesOMG Standards Presented By: Ilvana Mesic Date: October, 19991.1 StandardsStandard can be defined as just the approach taken by the ‘innovator’, the first successful seller in a new market segment. Why the standards are useful? For example in the software component market development they are useful to agree on common models, enabling interoperation in principle [2].They are also used for specific interface specifications, enabling effective composition. They can be used toagree on overall architectures to assign components their place in a larger picture of composition and interoperation [2].Today in the software component world there were two different approaches developing standards. The firstapproach is to build working markets first, followed by the formulation and publication of standards.The most prominent player following this approach is Microsoft (COM, OLE, Active X, COM+) [2]. Another player is Sun Microsystems (Java, Java Beans). Second approach was to build standards first and then to build the markets. The prime player in this arena is a huge international standardization organization: the Object Management Group (OMG)[2].1.2 OMGThe Object Management Group was founded in April 1989 by eleven companies, including 3Com Corporation, American Airlines, Canon, Inc., Data General, Hewlett-Packard, Phillips Telecommunications N.V., Sun Microsystems and Unisys Corporation [1]. In October 1989, the OMG began independent operations as a non-profit corporation. The consortium now includes over 800 members.The OMG is headquartered in Framingham, Massachusetts, USA with international marketing offices in the UK, Germany, Japan, Australia, Brazil[1]. 1.2.1 GoalThe OMG was formed to create a component-based software marketplace by introducing the standardizedobject software. The organization's charter includes the establishment of industry guidelines and detailed object management specifications to provide a common framework for application development [1].OMG is mainly active in two areas: object orientation and distributed systems[3]. Both fields are important for the development of the information processing in the future. The objects representing software components will be interacting in heterogeneous hardware and software environments, exchanging and offering services, and passing messages in order to execute programs, perform calculations, access data from databases and so on.. In order to realize this vision two significant goals must be reached:- interoperability – the ability of different pieces of software to collaborate in a heterogeneous and distributed hardware environment [3]- satisfactory integration of newly developed and existing legacy systems [3]OMG defines object management as software development that models the real world through representation of “objects” [1]. These objects are the encapsulation of the attributes, relationships and methods of software identifiable program components [1]. A key benefit of an object-oriented system is its ability to expand in functionality by extending existing components and adding new objects to the system. Object management results in faster application development, easier maintenance, enormous scalability andreusable software [1]. Originally, OMG efforts concentrated on solving one fundamental problem: how can distributed object-oriented systems implemented in different languages and running on different platforms interact [2]?The first years of OMG went into tracking basic “wiring” problems [2]. (problems in communication between code generated by two C++ compilers on the same platform or problems like differences between platforms ) The outcome was the Common Object Request Broker Architecture (CORBA) in its initial version, 1.1 released in 1991. Although OMG’s most famous standard is CORBA, its most resent standard is UML. OMG’s Unified Modeling Language is a standard notation for Analysis and Design modeling. UML is likely to become the most widely accepted and adopted software specification since ANSI COBOL.1.3 Distributed Object Management (DOM)Distributed Object Management is a concept that supports interoperability and integration in heterogeneous, locally autonomous and distributed systems in two ways:- The data structures and the functionality of such systems are represented as encapsulated objects, which communicate with each other by sending messages to well-defined interfaces [3].- Clear access to (server) objects is made possible for (client) applications [3].Distributed object management supports the following features:- integration of existing and separately developed aggregations of objects or data into heterogeneous database system [3];- integration of different types of data (for example, conventionally formatted data, audio data, images, and so on) [3];- the possibility of applying traditional database techniques (such as query processing, query optimization, transaction synchronization and recovery) to the integrated collection of data [3];- integration of resources at every desired level of granularity (for example objects representingan entire DBMS as opposed to objects representing circles or students) [3];- the capability to launch and control the “execution” of combinations of objects (at any network location), if necessary by means of moving objects to a desired location [3];- the capability to support collaboration between intelligent components [3];A distributed Object Management System (DOMS) comprises the following elements:- an arbitrary number of distributed nodes which run application programs, database system or simple objects [3]- a collection of clients, which can also be application programs, software tools or simple objects, and which issue requests that are served by the resources [3].Distributed objects managers are mediators between clients and resources [3]. The principle of distributed object management has shown on the picture 1.Picture 1. The principle of distributed object managementMiddleware layer is added to the ordinary client-server architecture, service providers inform this component about their available services. Clients get information about objects in the system that supply required services. There are two types of mediators: - trader mediator – it is it functioning strictly as a