OMG
Object Management Group — international standards consortium
The Object Management Group (OMG) is an international, member-driven standards consortium that develops specifications for modeling languages and middleware used in enterprise and systems software, most notably the Unified Modeling…
Definition
The Object Management Group (OMG) is an international, member-driven standards consortium that develops specifications for modeling languages and middleware used in enterprise and systems software, most notably the Unified Modeling Language (UML) and the Common Object Request Broker Architecture (CORBA). Its member companies collaborate through technical working groups to produce vendor-neutral specifications intended to keep software design notation and distributed-object communication portable across implementations.
Overview
Enterprise software development in the 1990s faced two related interoperability problems: object-oriented systems needed a shared visual notation for describing designs across teams and tools, and distributed applications needed a way for objects running on different machines, operating systems, and languages to invoke each other's methods without every vendor inventing an incompatible protocol. The OMG was formed as a nonprofit consortium specifically to solve problems like these through open, member-negotiated specifications rather than leaving them to whichever vendor's tools happened to dominate. The OMG's specification process runs through member-staffed technical committees that draft, revise, and vote on proposals, with a completed specification becoming an OMG standard once adopted by the membership. Its two most consequential outputs work at different layers: UML is a modeling notation, covering class diagrams, sequence diagrams, and state machines, used to describe the structure and behavior of a software system independent of any specific programming language or runtime, while CORBA is a middleware specification defining how objects on different machines and in different languages can invoke each other's methods through an Object Request Broker that handles the underlying network communication and language-bridging transparently to the calling code. Within the standards landscape, UML competes conceptually with lighter, less formal modeling notations and has been partly supplanted in casual use by simpler diagramming approaches, though it remains standard in formal systems-engineering and enterprise-architecture documentation. CORBA, by contrast, has been largely displaced in modern practice by simpler distributed-computing approaches such as REST APIs, gRPC, and message queues, which achieve similar cross-language interoperability with far less specification overhead and infrastructure; CORBA's heavyweight interface-definition-language-and-broker model was well suited to the constraints of 1990s enterprise systems but proved cumbersome relative to the web-era alternatives that followed. In practice today, UML diagrams still appear in software design documentation, architecture reviews, and academic coursework as a common vocabulary for describing object-oriented systems, even when the implementation itself is written in a language with no direct UML tooling. CORBA survives mainly in legacy enterprise, telecommunications, and defense systems built during its adoption peak, where the cost of migrating away from an entrenched middleware layer outweighs the benefit, though new systems rarely choose it. The OMG's standards illustrate a broader trade-off in formal, committee-driven specifications: the rigor that makes UML precise enough for regulated industries and CORBA robust enough for mission-critical distributed systems also makes both heavier to learn and apply than the more ad hoc, incrementally adopted alternatives that have captured mainstream use since, which is why the OMG's specifications remain more prominent in formal enterprise-architecture practice than in typical day-to-day software development.
Specification
- Developer and steward of the Unified Modeling Language specification
- Developer of the CORBA distributed-object middleware specification
- Member-driven technical committee process for drafting standards
- Vendor-neutral governance across competing enterprise software vendors
- Long-running standards body dating to the early object-oriented era
- Specifications used heavily in regulated and defense-industry systems
- Provides formal notation for software architecture documentation
- Maintains standards independent of any single vendor's tooling