OMG Homepage MDA Homepage CORBA Homepage MOF Homepage UML Homepage CWM Homepage XMI Homepage DDS Homepage OMG MARTE BPMN Homepage SysML Homepage banner

|Request For Comments Form | Technology Process FAQ | Request for Information FAQ |

Current OMG Technology Adoption Processes Under Way
Last updated: Saturday, 19-Apr-2014 18:01:12 EDT

Specifications which have been approved by the OMG membership are available to everyone, but only OMG members have access to specifications under development. This page lists OMG Request processes for technology submissions which are open to both members and the general public for comment or response. For more information on the OMG technology adoption process, please see the Process Technology FAQ.

Please note that the actual Request documents are freely available; simply click on the document number below to get the document in several different formats. However, the internal mechanics of the OMG process are available only to members by clicking on the process name.

A catalog of our published specifications is available here. If you're interested in learning more about the OMG and the benefits of becoming a member, please contact our Business Development staff.

Pending Requests for Comments:

FIBO Business Entities RFC
FIBO BE ODM XMI Files (document finance/2013-11-05)
FIBO BE OWL Files (document finance/2013-11-03)
FIBO BE UML XMI Files (document finance/2013-11-04)
FIBO BE VOM Model Files (ancillary) (document finance/2013-11-06)
FIBO Business Entities specification RFC (document finance/2013-11-01)
FIBO Business Entities specification RFC - cover letter (document finance/2013-11-12)
FIBO-BE Inventory File (document finance/2013-11-02)

Financial Instrument Global Identifier RFC
FIGI ODM XMI (document finance/2014-03-04)
FIGI RFC cover letter (document finance/2014-02-06)
FIGI RFC machine-readable files: OWL specification for the main semantic model (document finance/2014-03-03)
FIGI UML XMI (document finance/2014-03-05)
FIGI ancillary VOM file (document finance/2014-03-06)
FIGI revised inventory file (document finance/2014-03-08)
OWL specification of the pricing sources referenced in the semantic model for FIGI (document finance/2014-02-05)
OWL specification of the security types referenced in the semantic model for FIGI (document finance/2014-02-04)
Updated Financial Instrument Global Identifier RFC (document finance/2014-03-07)

Implementation Patterns Metamodel for Software Systems RFC
APML XMI (document admtf/2014-02-05)
IPMMS RFC Inventory file (document admtf/2014-03-04)
IPMMS RFC cover letter (document admtf/2014-02-02)
PHORML XMI (document admtf/2014-02-04)
Updated IPMMS XMI (document admtf/2014-03-03)
Updated Implementation Patterns Metamodel for Software Systems (IPMSS) RFC (clean) (document admtf/2014-03-01)

Pending Requests for Information:

Contract Information Exchange Model Request For Information (document bmi/2013-03-06)
Providing standardized Contract Information Exchange Model (CIEM) facilitates the acquisition of goods and services through the open, exchange of contractual information between offerors and bidders during the transparent negotiation process. The dynamic, rapid, agile and flexible requirements of Cloud Computing make it an excellent usage scenario for CIEM. However, the acquisition process is far larger than cloud services. The CIEM is intended to support the larger process. The CIEM is also intended to support third party, automated or semi-automated brokers in a transparent, repeatable, non-reputable, enforceable, auditable acquisition process. The CIEM may include taxonomies, ontologies, rules, and data structures required to capture the kind of agreement, scope of work to be performed and the terms and conditions associated with the scope of work. The purpose of this RFI is to identify existing whole or partial standards applicable to CIEM, identify gaps between the standards and to solicit proposals for filling the gaps.

Data Distribution Service - Enterprise Edge (DDS-EE) RFI (document mars/2013-09-14)
An enterprise represents the entirety of an organization and includes things such as activities, organization, strategy and marketing. An Information Technology (IT) Enterprise represents the entirety of the IT resources used to support the enterprise. Originally, the IT resources used to support the enterprise were disparate, independent, loosely federated, confederated or isolated elements. However, recently the trend is to define enterprise architectures that provide a strategy for integrating the IT resources together into a more unified, systematic and consolidated system. The original focuses of these architectural activities were on the needs of the enterprise's primary or core business and IT resources. However, discontinuities occur within the enterprise as a consequence of: " Growth and absorption of other independently developed enterprise domains " Expansion outward from the core business area towards non-core business areas hereafter referred to as Edge Domains " Divestiture of some core business areas from the enterprise Technically, discontinuities persist within the enterprise because of differences in the: " Convergence of various service models, e.g., client-server, request-reply, publish-subscribe, activity based computing, or event driven architecture " Non-real-time versus real-time Quality of Service (QoS), e.g., operational deadlines for event delivery measured in milliseconds or microseconds " Logical boundaries such as security boundaries, political boundaries, e.g., intranet versus internet, classified versus non-classified, International Traffic in Arms Regulations (ITAR), data sovereignty, and privacy issues " Physical boundaries or constraints such as network connectivity or speed, e.g. Disconnected, Intermittent, Limited (DIL), baseband versus broadband Modern enterprise architectures are typically developed using Service Oriented Architecture (SOA) precepts, which sometimes include Enterprise Service Busses (ESBs). Within that context, the ESB may translate and mediate information between service models and provides an abstraction of services. Characteristically, Enterprise Architectures are: " Large scale, diverse systems built up from individual systems, such as Systems of Systems (SoS) " Based upon the client-server pattern " Developed and maintained over long periods of time " Comprised of many moving parts or elements developed by different independent teams with often competing or opposing goals using the technology du jour. Enterprise Domains represent the entirety of the business functionality. In contrast, edge Domains are narrowly focused on specific goals or technologies (e.g., air traffic control, wind turbines, unmanned vehicles, medical devices). Typical implementations are more tightly integrated, often time sensitive and created in smaller timeframes using an event or publish-subscribe model leveraging specialized messaging systems (e.g., AMQP, CORBA, DDS, Distrix, IBM MQ, MQTT, or MSMQ). Although these architectural generalizations are stereotypic in nature, they represent the notional behaviors for these architectures. It is possible for enterprise architectures to use the event or publish-subscribe model or for the edge architectures to use the server-client or request-reply models. However, the various behaviors create barriers when trying to " Expand the enterprise architectures towards the edge of the enterprise " Expand the edge architectures to cover the requirements of the enterprise at large to help incorporate the edge functionality into the fabric of the Enterprise Domain. " Federation or merging of edge systems into existing enterprise architectures.

Hardware Abstraction Layer for Robots RFI (document robotics/2013-06-06)
This RFI is the first step towards standardization of the application programming interface to access hardware devices such as motors and sensors. Currently, porting existing software to different systems, including device drivers in the development of embedded systems, requires considerable effort. For example, turning on an LED or operating a motor on different hardware may require many days because the application program interfaces to control sensors and motors are uniquely defined by the device manufacturers. It is necessary to unify these interfaces. A Hardware Abstraction Layer is an open platform to standardize the specifications of the software implementation of robotics and control systems. A Hardware Abstraction Layer provides the base portion of a software platform for robotics and control systems, and aims to enable applications to run on different hardware. This increases the portability and reusability of the software, resulting in improved quality, lower costs and improved productivity. It is expected to improve convenience for users and developers.

Pending Requests for Proposals:

Agent Metamodel and Profile (AMP) RFP (document ad/2008-09-05)
This Request for Proposal solicits submissions for an Agent Metamodel and Profile (AMP). Essentially, the AMP RFP requests a metamodel and profile for extending UML with capabilities applicable to agents and agent-based software. Submissions developed in response to this RFP will achieve the following: Clarify semantics concerned with modeling agents. Establish Agent modeling best practices utilizing OMG technologies. Develop a MOF-compliant agent metamodel to be used either standalone or via extending the existing UML metamodel with agent modeling capabilities. Enable agent model interchange between tools via XMI. Optionally facilitate modeling of Peer-to-Peer, Grid and Cloud computing, and other technologies in terms of a collection of Agents. It is expected that responses to this RFP will make good use of agent modeling capabilities already supported by the OMG.

Application Programming Interfaces (API) to Knowledge Bases (KB) RFP (document ad/2010-06-09)
The intent of this RFP is to request proposals for Application Programming Interfaces (API) to Knowledge Bases (KB). According to Wikipedia ([WIK-KB]), “a knowledge base is a special kind of database for knowledge management, providing the means for the computerized collection, organization, and retrieval of knowledge”. This RFP targets mainly the basic administration services as well as the retrieval and the modification of knowledge in a KB designed specifically for use with knowledge representation languages supported by OMG standards, including but not limited to those supported by the Ontology Definition Metamodel (ODM - Proposals are sought that create a common set of APIs and interfaces for accessing namespaces and IRIs (internationalized uniform resource identifiers), documents, and other common infrastructure, some of which is modeled, for example, in the ODM RDFWeb package of the RDF metamodel, regardless of the target representation language, for knowledge representation languages that can be serialized in XML. The primary target is for accessing such KBs in the context of a tool, such as a parser, ontology editor, inference engine, or other applications where a uniform set of APIs and related services is desirable. APIs and service interfaces supporting basic queries, such as those that can be represented in SPARQL, are also desired. While this API shall be independent from the way the KB was populated and how the KB is designed and organized, the resultant API(s) and services shall be designed to complement and work in concert with ODM. It is understood that this effort may necessitate modifications to the ODM, including collaboration with ODM revisions underway to support OWL 2. This RFP solicits proposals for the following: API to retrieve raw information from a KB (resources, properties…); API to modify raw information in a KB; API to query knowledge in a KB (i.e., through reasoning); API to create instances: API to administrate the KB: add, import or remove ontology

Archetype Modeling Language (AML) (A UML Profile for Modeling Archetypes) RFP (document health/2012-07-01)
The objective of this RFP is to provide a standard for modeling Archetype Models (AMs) using UML, to support the representation of Clinical Information Modeling Initiative (CIMI) artifacts in UML. Archetypes are Platform Independent Models (PIMs), which are developed as a set of constraints on a specific Reference Model (RM). This RFP solicits proposals for an UML Profile, to be known as the "Archetype Modeling Language" (AML). The AML Profile will be developed as an aggregation of three sub-profiles, which together meet the requirements of archetype modeling. The three sub-profiles of the AML Profile will include: - Reference Model Profile (RMP): This profile will enable the specification of reference models, upon which archetypes can be based. - Constraint Model Profile (CMP): This profile will support the specification of constraints on a given reference model, to enable the development of archetypes, including Clinical Information Models (CIMs). - A Terminology Binding Profile (TBP): This profile will support the binding of information models to terminology, with optional support for binding to CTS2. Terminology bindings will include:
1. Value Bindings: Linkage of the data model to value domains, which restrict the valid value of an attribute to a set of values that corresponds to a set of meanings recorded in an external terminology;
2. Semantic Bindings: Defining the meaning of model elements, using concepts in an external terminology; and
3. Constraint Bindings: Specifying constraints on the information model, using concepts and relationships defined in an external terminology. This set of three UML sub-profiles (which together constitute the AML) will enable the specification of CIMI clinical model content (using the CIMI Reference Model), and the generation of CIMI clinical model artefacts, such as the Archetype Definition Language (ADL). While the transformation of AML models to an instance of the Archetype Object Model v1.5 (AOM-1.5) is optional, this transformation must be possible. The Archetype Definition Language (ADL) is a serialization of the Archetype Object Model.

DDS Security RFP (document mars/2010-12-37)
The Data Distribution Service for Real-Time Systems (DDS) is the Object Management Group (OMG) standard for data-centric publish subscribe. The objective of this RFP is to define the set of Extensions to DDS required to provide Information Assurance for systems built using DDS.

Dependability Assurance Framework For Safety-Sensitive Consumer Devices RFP (document sysa/2013-03-20)
The term "Safety-Sensitive Consumer device" (SSCD) refers to a category of industrial products used by consumer users, including automobiles, service robots, medical devices and clinical systems, and smart houses. Unlike traditional industrial machinery, such consumer devices must be dependable because they are used in diverse, open and dynamic environments where the need for safety, reliability and even availability of such devices is no longer an option but a requirement. The challenge is to develop a solution that satisfies this dependability requirement in cost-efficient way, preserving the affordable prices of SSCDs for the mass-market. A Dependability Assurance Framework (DAF) extends engineering approaches with additional viewpoints describing the assurance case, conceptual model for describing properties and process models. This would allow us to justify given properties throughout engineering processes by using explicit argumentation and evidence. The objective of this RFP is to produce a specification for building justifiably dependable SSCDs by specifying: 1. One or more Dependability Conceptual Models (DCMs) defining the factors of dependability, 2. One or more templates to be used to construct Dependability Assurance Cases (DACs) for SSCDs, and 3. One or more Dependability Process Models (DPMs) that define rapid and iterative processes for engineering dependable SSCDs. The response is expected to include generic customizable templates for DAC, as well as generic models for DCM and DPM, all supported by specific examples.

Event Metamodel and Profile (EMP) RFP (document ad/2008-09-15)
This Request for Proposal solicits submissions for an Event Metamodel and Profile (EMP). Essentially, the EMP RFP requests a metamodel and profile for extending UML with capabilities applicable to the sensing and interpretation of events, such as monitoring, filtering, aggregation, and correlation. Submissions developed in response to this RFP will achieve the following: Clarify semantics concerned with modeling events. Establish Event modeling best practices utilizing OMG technologies. Develop a MOF-compliant event metamodel to be used either standalone or via extending the existing UML metamodel with event modeling capabilities. Enable event model interchange between tools via XMI. It is expected that responses to this RFP will make good use of event modeling capabilities already supported by the OMG

Finite State Machine Component for RTC (FSM4RTC) RFP (document robotics/2013-06-11)
The Robotic Technology Components (RTC) is an Object Management Group (OMG) specification for the component model and certain important infrastructure services applicable to the domain of robotic software development. In robotic software development, Finite State Machines (FSMs) are frequently used (even within a single system) in various styles and users want to reuse them. Moreover communication between RTC components and between state machines is done using some data structures through well-defined input/output ports in order to communicate state information. Although the RTC provides the specification of FSM components, it does not provide data models and methods/operations to be used in the FSM components in order to send events with parameters to components, get current states, send/receive the notification of state transitions and the definition of FSM. These features are usually required to simply interface an FSM with external tools for monitoring purposes. This RFP solicits proposals for an extension to the RTC specification as a solution to these problems. This extension will make the FSM component of RTC more applicable to real robotic software development.

IEF Reference Architecture RFP (document mars/2014-03-17)
The Information Exchange Framework (IEF) is an OMG initiative to develop a family of specifications for policy-driven, data-centric information sharing and safeguarding (ISS) services. These services target the automation of key policy decision and enforcement points to enable responsible information sharing across a broad range of business and operational scenarios. This Request for Proposal (RFP) seeks submissions for an overall reference architecture, reference model, and supporting materials for the IEF. The IEF Reference Architecture (RA) will be used to steer the overall IEF effort and broaden general understanding of domain requirements. The domain focus of the IEF RA includes interagency information sharing, often challenged by rapid, unpredictable changes in operational contexts (e.g., threat, risk, roles & responsibilities, scale, scope, and severity), e.g.: 1. Military (coalition and Civilian-Military) operations; 2. National Security; 3. Public Safety; 4. Crisis Management; 5. Border Security; 6. Emergency Management; and 7. Humanitarian Assistance. The IEF is focused on these environments because they require higher degrees of flexibility, agility and adaptability: often more than traditional solutions can satisfy. This RFP solicits proposals for a reference architecture for the IEF comprising: o A Platform Independent Model (PIM) for the IEF; o At least one Platform Specific Model, associating PIM elements to applicable standards; and o Operating concept and use cases for the IEF.

Information Management Metamodel (IMM) RFP (document ab/2005-12-02)
This RFP solicits proposals for a standard metamodel to address the needs of Information Management. This includes the scope of the existing Common Warehouse Metamodel (CWM) standard but is extended to cover the following areas: · MOF2 Metamodel for Information Management (IMM) · UML2 Profile for Relational Data Modeling, with a mapping to the IMM metamodel and SQL DDL · UML2 Profile for Logical (Entity Relationship) Data Modeling, with a mapping to the IMM metamodel · UML2 Profile for XML Data Modeling, with a mapping to the IMM metamodel and XML Schema · UML2 Profile for Record Modeling, with a mapping to the IMM metamodel and COBOL Copybooks · A standardized ‘Information Engineering’ data modeling notation with a mapping to the IMM metamodel

MOF to RDF Structural Mapping in Support of Linked Open Data RFP (document ad/2009-12-09)
RDF and Linked Open Data (LOD) have become important technologies for exposing, managing, analyzing, linking and federating data and metadata. This set of RDF based technologies, sometimes known as the “Semantic Web” or “Web 3.0”, are emerging as the lingua franca of data on the web. Major initiatives such as the President’s open government initiative are moving to the use of RDF & Linked Open Data as the foundation for publishing all government data and metadata in support of transparency. OMG & MOF based models should be a part of the LOD and Web 3.0 data cloud. The objective of this RFP is to define a structural mapping between OMG-MOF models and RDF to provide for better integration of MDA and LOD, to enable the ability to apply LOD capabilities to MOF compliant models and to make the information available in MOF compliant models available as LOD web resources. Any MOF based model should be able to become a LOD resource.

Metamodel Extension Facility RFP (document ad/2011-06-22)
This RFP solicits proposals for a Facility for extending and integrating metamodels that will complement and may eventually replace the current UML Profiles capability. The new Facility will be: o Able to replicate all of the semantic capabilities of the current profile mechanism; o Applicable to any metamodel or well-formed metamodel subset, not just UML; o Defined in a technically sound manner; o Able to define new diagram mappings; o Integrated with OMG platform technologies.

OCL 2.5 RFP (document ad/2014-03-05)
Despite some limitations, OCL has proved useful in fleshing out the details of a variety of OMG specifications. However users regularly report a steep learning curve and poor useability. This RFP solicits proposals for the following: resolution of OCL misalignments with UML normative UML-aligned metamodels for OCL editorial revision of the OCL specification to align with its metamodels no incompatible changes to the OCL Concrete Syntax language improved useability

Ontology, Model and Specification Integration and Interoperability (OntoIOp) RFP (document ad/2013-12-02)
This RFP solicits proposals for the following: A specification for an abstract metalanguage with an associated metamodel targeted at cross-language interoperability among a class of concrete languages used to record logical expressions found in ontologies, models and specifications. A list of concrete languages and translations to be recognized and correctly processed by implementations of this specification. A description of constraints and conformance criteria for additional concrete languages and translations between concrete languages that are not explicitly supported, but nonetheless have equivalent uses that could be recognized and correctly processed by implementations

Precise Semantics of UML Composite Structures RFP (document ad/2011-12-07)
The objective of this RFP is to solicit specifications containing more precise semantics for UML composite structures and their extensions (e.g., profiles) to enable execution, model checking, and reduce ambiguities in UML models. By semantics, we mean the underlying meaning of models, that is, the constraints that models place on the structure and runtime behavior of the specified system. In support of this objective, the RFP solicits proposals for the precise specification of the semantics for all the metaclasses supporting the ability of classifiers to have both an internal structure (comprising a network of linked parts) and an external structure (consisting of one or more ports). The specification should cover both structural semantics (e.g. the runtime manifestations of connectors, ports, and parts) and behavioral semantics (e.g. life-cycles of composite objects and their constituents, the nature and characteristics of flows through ports and connectors). Proposals shall build on the precise semantics of fUML, which specifies the execution semantics of a computationally complete and compact subset of UML 2 to support execution of activities.

RIA Dynamic Component Model RFP (document mars/2013-03-28)
The Rich Internet Application (RIA) domain provides client-side functionalities like visualization, user interactions, and device control for internet-based distributed applications. Usually, a RIA Application is rendered with a RIA runtime engine (referred to as a RIA Platform), which behaves like a typical application or native component. In an Enterprise business application, master data like product codes or basic data like order information are retrieved and/or referenced frequently by all subsequent applications. To increase the reusability of applications, front-end RIA Applications should be componentized as server-side/back-end distributed business components such as EJB, OSGi, and CCM. Moreover, this RIA componentization should be done under no-compilation (XML and JavaScript) and runtime deployment environment (no pre-installation, e.g., HTML) conditions so that a RIA Application can be treated as a RIA Component by another RIA application. This RFP solicits proposals for the following: o A standard RIA Dynamic Component Model (RDCM) which defines the services necessary to dynamically construct a RIA Application using RIA Components specific to a single, homogenous RIA Platform. The goal is a specification defining a format for declaring interfaces for exposing properties and methods within the RIA Application, as well as, how to use interfaces at development time and/or runtime in a RIA Platform. Submissions developed in response to this RFP should address the following: o A Vocabulary defining a RIA Component interface. This vocabulary defines the terminology used in the RIA development community including event information, property, method, and event handler. o A Platform Independent Model (PIM) of the component model which maps the preceding vocabulary including: o Mechanisms for the dynamic deployment of RIA Components, consisting of interface descriptions (IDL) and implementations (RIA Application source code). o Mechanisms for dynamically instantiating implementations and dynamically binding interfaces while executing a RIA Application. o Mechanisms for calling interfaces and exchanging data including dynamically declared custom data types. o Platform Specific Models (PSM) implementing the preceding PIM for specific deployment platforms, including JavaScript. The RDCM RFP does not apply to: o Presentation issues (layout and look & feel) of a RIA Application. o Specifications addressing bi-dimensional and tri-dimensional computer based graphics. o Instantiations of RIA runtime engines based on an OS application or native component. o Data exchanged between RIA runtime engines. o Server-side/back-end web applications.

Remote Procedure Calls (RPC) over Data Distribution Service (DDS) RFP (document mars/2012-06-29)
The Data Distribution Service for Real-Time Systems (DDS) is an Object Management Group (OMG) specification for real-time and data-centric publish/subscribe. The DDS standard has been widely adopted and applied across application domains including Aerospace and Defense, Transportation, SCADA, and Financial. In many of these domains, DDS is often the only middleware technology used to build complex and large-scale distributed systems. In these systems, DDS is used to represent and share distributed state, to distribute event, and to execute commands. Although DDS provides first class support for distributed state and event, it makes it a bit cumbersome to express commands, or put it in another way, it does not provide first class support for synchronous two way interactions, thus leading users to implement their own ad hoc solution over DDS. This RFP calls for a systematic solution to this problem by means of a Remote Procedure Calls (RPC) extension to the DDS specification. This extension will allow commands to be naturally represented as remote method invocations.

Records Management Services Version 2 RFP (document gov/2009-12-05)
The OMG adopted the Records Management Services specification (Beta-1: in June 2009. Provision for specifying context dependent Attribute Profiles was established, but specific instances were not. Additionally, no fine grained compliance points were defined. Compliant implementations are constrained to implement the specification in toto. This RFP solicits proposals for the following: · The provision of one or more Attribute Profiles minimally supporting DoD 5015.02 compliant Records Management Environments. · The addition of compliance points to subset service operations and profile attribution as it is affected by the subsetting. This will allow RMS to be provisioned on a scale that suits the business needs of diverse organizations.

Semantic Information Modeling for Federation (SIMF) RFP (document ad/2011-12-10)
The SIMF RFP asks for submissions for a standard that addresses the federation of information across different representations, levels of abstraction, communities, organizations, viewpoints, and authorities. Federation, in this context, means using independently conceived information sets together for purposes beyond those for which the individual information sets were originally defined. The purpose of SIMF is to help federate information across different authorities, vocabularies and formats. Current conceptual and logical information modeling approaches tend to be focused on a particular information modeling problem, using a particular technical approach. Examples of such technical approaches include object modeling, DBMS modeling and exchange schema modeling. SIMF seeks to address the problem of information federation by specifying standards for conceptual domain modeling, logical information modeling and model bridging relationships. SIMF submissions will define, adopt and/or adapt languages to express the conceptual domain models, logical information models and model bridging relationships needed to achieve this federation. Many if not all of these capabilities can be achieved with expert application of multiple standards and technologies. SIMF is intended to unify and tailor these capabilities, providing a standard for tools that reduce the barrier to entry and overhead required to achieve federated information.

UML Profile for GRA (GRA-UML) RFP (document gov/2013-09-20)
The objective of this RFP is to provide a standard for modeling Global Information Sharing Initiative (Global) Reference Architecture (GRA) artifacts (Services Specification Packages - SSPs) with UML. (Please see Appendix A for the glossary of terms). This RFP solicits proposals for the following which together shall comprise "GRA-UML": o Build on the success of NIEM-UML (focused on data only) and leverage GRA to extend the development of an IEPD to a full services specification. o UML profiles for modeling GRA SSPs: a profile that will enable the development of Platform Independent Models for GRA SSPs, and a second profile that provides the parameters required to transform the Platform Independent Models for GRA SSP to GRA conformant SSPs (the Platform Specific Model) o A transformation from UML models that conform to the GRA profiles (described above) to GRA-conformant SSP artifacts o Optionally, a transformation from a GRA-conformant SSP to a UML model that conforms to the profile(s)

UML Profile for NIEM 3 (NIEM-UML) RFP (document gov/2014-03-01)
This Request for Proposal (RFP) solicits proposals related to developing the next major revision of the OMG Unified Modeling Language (UML) Profile for the National Information Exchange Model (NIEM) Specification, which is commonly referred to as NIEM-UML. The revision addresses alignment to the newest version of NIEM, i.e. NIEM Version 3. Specifically, it addresses changes to the NIEM content model and the technical architecture. NIEM-UML allows modelers and developers to produce NIEM model packages conforming to the NIEM Naming and Design Rules (NDR) and the Model Package Description (MPD) Specification. The profile was created to broaden NIEM adoption by facilitating the separation of concerns between community business needs and XML Schema specific technology implementations. The OMG adopted the UML Profile for NIEM (based on NIEM Version 2.1) in December 2013. The profile has been successfully implemented in both commercial and open source development platforms. Due to the extensive changes to NIEM between Versions 2.1 and 3, revisions are outside the scope of a Revision Task Force (RTF). This RFP for a major revision solicits proposals for the following: o UML profiles for modeling NIEM MPDs; a logical profile that will enable the development of Platform Independent Models for NIEM content and a second profile that models MPD metadata and provides the parameters required to transform the logical model to NIEM-conformant XML schema and MPD specifications (the Platform Specific Model). o A transformation from UML models that conform to the NIEM profiles (described above) to NIEM-conformant MPD artifacts. o Optionally, a transformation from a NIEM-conformant XML schema set (as defined by the NIEM NDR) to a UML model that conforms to the profile(s). o A UML representation of the NIEM controlled vocabularies (reference namespaces) from which MPDs are constructed. This UML representation must conform to the profiles mentioned in the first bullet point.

UML Testing Profile V2 (UTP2) RFP (document ad/2013-12-08)
This RFP solicits proposals for the following: a UML Testing Profile as a successor specification of the UML Testing Profile 1.2 a UML Testing Profile that is applicable to a variety of domains and methodologies a UML Testing Profile enables the specification of test cases for different quality attributes and on different level of abstractions a UML Testing Profile that allows for test generation and the precise specification of test coverage

UPDM 3.0 RFP (document c4i/2013-09-11)
Architecture frameworks continue to evolve. A NATO Architecture Capability Team (Architecture CaT) meeting on Sept. 10-11, 2012 committed to moving to a single world-wide Architecture Framework. Consequently, a new architecture framework profile supporting a unified nations' framework is needed. This RFP solicits proposals for the following: An architecture framework UML profile that reuses SysML V1.3, where appropriate, that evolves from legacy architectural frameworks including but not limited to the Ministry of Defence Exchange Mechanism [MODEM], DoDAF 2.x Metamodel (known as [DM2]), and the International Defence Enterprise Architecture Specification [IDEAS]. The proposed architecture framework profile shall enable the development of an integrated Architecture Description (AD).

Unified Component Model for Distributed, Real-Time and Embedded Systems RFP (document mars/2013-09-10)
The objective of this RFP is to solicit proposals for a new component model called the “Unified Component Model” targeting Distributed, Real-Time and Embedded (DRTE) Systems. A component model defines a set of standards for component implementation, naming, interoperability, customization, composition, evolution, and deployment [COMP]. The UCM will be a simple, lightweight, middleware-agnostic, and flexible component model. The UCM will allow many different interaction models, including publish-subscribe and request-reply.

Current Specification Revision Processes (available to members only:

2nd Dynamic Deployment and Configuration for RTC (DDC4RTC) 1.0 FTF
Abstract Syntax Tree Metamodel 1.0 (ASTM) RTF
Action Language for fUML 1.1 (ALF) RTF
Application Instrumentation 1.0 FTF
CTS2 XML to JSON Transformation Rules 1.0 FTF
Common Terminology Services 2 (CTS2) 1.3 Revision Task Force
DDS Security 1.0 FTF
DDS-PSM-Cxx v1.1 RTF
DDS-PSM-Java v1.1 RTF
Data Distribution Service 1.4 RTF
DateTime Vocabulary (DTV) 1.1 RTF
Decision Model and Notation 1.0 FTF
Diagram Definition 1.1 RTF
Diagram Definition 1.2 RTF
EXPRESS Metamodel 1.1 RTF
Essence 1.0 FTF
Essence 1.1 RTF
Extensible and WebEnabled DDS FTF
FIBO Business Entities 1.0 FTF
FIBO Foundations 1.0 FTF
Ground Equipment Monitoring Service 1.4 RTF
IDL to C++11 1.2 RTF
Information Exchange Packaging Policy Vocabulary (IEPPV) FTF
MOF 2 Core 2.5 RTF
Ontology Definition Metamodel (ODM) 1.2 RTF
Precise Semantics of UML Composite Structures 1.0 FTF
Records Management Services V1.1 (RMS) RTF
Requirements Interchange Format V1.2 (ReqIF) RTF
Robotic Interaction Service Framework 1.1 RTF
Ruby CORBA Language Mapping 1.3 (RCLM) RTF
SoaML 1.1 RTF
Structured Metrics Metamodel 1.1 RTF
SysML 1.5 RTF
TelcoML 1.1 RTF
TestIF 1.0 FTF 2
UML Profile for BPMN Processes 1.1 RTF
VSIPL_1.5_and VSIPL++_1.3_RTF
Vector Image Signal Processing Specifications 1.6 RTF
XML Telemetric & Command Exchange Format 1.2 (XTCE) RTF
XTCE US Government Satellite Conformance Profile 1.0 (XUSP) FTF
fUML 1.2 RTF
Copyright © 1997-2014 Object Management Group, Inc. All Rights Reserved. For questions about the WEBSITE , please contact
For TECHNICAL questions, please contact
This site is best viewed with Mozilla Firefox or Internet
Explorer versions 6.0 or later or any browser capable of viewing JavaScript and CSS 2.0. The site is using
DHTML JavaScript Menu By