10. Why OMG and Why MARS?
◀ Previous | Top | Next ▶
Why OMG?
-
Model Driven Architecture provides the foundation for separating platform-independent and platform-specific concerns
-
OMG modeling languages support precise architectural and information models
-
Existing OMG specifications address interfaces, middleware, distributed Systems, Data exchange, and Semantics
-
Domain Task Forces contribute operational requirements and real-world use cases
-
The OMG RFP process supports competing or joint proposals and consensus-based adoption
-
An OMG specification can provide a common foundation across industries and implementation technologies
Why MARS?
-
SIP-RA addresses distributed processing, middleware, interfaces, and information exchange
-
Federation requires architectural relationships among independently governed Systems
-
Platform independence is central to the proposed Reference Architecture
-
MARS members bring experience with APIs, protocols, distributed services, and interoperability
-
MARS can coordinate the RFP while drawing on expertise from other OMG groups
Cross-OMG Participation
-
Architecture Board for architectural consistency and specification quality
-
ADTF for MDA, UML, SysML v2, metamodeling, and model transformation
-
Domain Task Forces for representative missions, constraints, and use cases
-
Ontology and semantics communities for governed meaning and semantic mappings
-
Security communities for trust, Policy, jurisdictional, and cross-domain concerns
MARS provides the technical center of gravity, while successful adoption requires participation across OMG.
◀ Previous | Top | Next ▶
| 13 September 2026 | Page: 10 |
© 2026 Dido Solutions, Inc. and Jackrabbit Consulting, Inc.