SOA Metamodel Sumission to Object Management Group
Everware-CBDI Announce Intent to Submit SOA Metamodel to Object Management Group
Supporting Industry Standardization Efforts to Clarify SOA
Fairfax, VA, USA. December 01, 2006.
Everware-CBDI Inc., the leading independent source of practices, consulting and education on Service Oriented Architecture (SOA), announced today that it intends to make a submission to the Object Management Group (OMG) in response to their UML Profile and Metamodel for Services (UPMS) RFP (Request for Proposal).
SOA is widely regarded as one of the most profound changes ever in enterprise computing, yet there is general confusion over basic concepts, architecture and practices. To address these issues Everware-CBDI has developed and published a comprehensive metamodel that defines SOA unambiguously leveraging current industry standards. A metamodel defines the rules for building business and software models and defines terminology in a consistent manner to eliminate confusion. The SOA metamodel provides essential precision for the specification of business services, and enables SOA automation and effective governance.
OMG is an open membership, international organization of information system vendors, software vendors, and end-user companies. Through its members, the OMG produces and maintains specifications for interoperable software. The OMG SOA Special Interest Group focuses on definition of methodology and models for SOA. Its UPMS RFP aims to address a part of the overall SOA metamodel by linking architectural, business and technology views of services.
David Sprott, Vice President of Everware-CBDI, said, "Our objective in developing a metamodel for SOA was to bring clarity and consistency to SOA practices. We welcome the OMG's initiatives in this important area and are pleased to contribute to the achievement of a standardized industry view."
Everware-CBDI is the leading independent provider of full-lifecycle, SOA-based research, education and consulting to businesses and governments. CBDI Forum is the Everware-CBDI research capability and portal providing members with independent guidance on best practice in SOA, including CBDI Service Architecture & EngineeringTM a repeatable process for enterprise SOA. CBDI Journal is a monthly subscription publication read by IT architects worldwide. Headquartered in Fairfax, Virginia, USA, the company has operations in North America and Europe. For more details see www.everware-cbdi.com and www.cbdiforum.com or call 1-888-383-7927 (US) and +353 28 38073 (Europe).
The introductory report on the Everware-CBDI SOA Metamodel is available at:
Editors may request the October CBDI Journal from contacts below.
Tel: +1 703-938-1242
Tel: +353 28 38073
OMG document: UML Profile and Metamodel for Services (UPMS). Request For Proposal. OMG Document, reference 'soa/2006-09-09'. Letters of Intent due: November 28, 2006. Submissions due: June 4, 2007 [source PDF soa/06-09-09, main reference page]
"Globalization and the Internet have resulted in the need to define more loosely coupled components executing in distributed heterogeneous environments. Service Oriented Architectures (SOA) represent an approach to Information Technology (IT) development that facilitates this loose coupling while at the same time providing sufficient qualities of services necessary for acceptable solutions. There are a number of existing and emerging/evolving runtime platforms resulting in a need to abstract their commonality and define standards for interoperability and information exchange. This Request for Proposal solicits submissions for a UML Metamodel and Profile for Service (UPMS). Essentially, the UPMS RFP requests a services metamodel and profile for extending UML with capabilities applicable to modeling services using an SOA. The profile will define extensions for modeling and integrating services within and across business enterprises. UPMS will include facilities for formal specification of service contracts that may be developed directly using the profile, or abstracted from business processes. It will also include facilities for indicating which of these contracts are fulfilled by modeled service providers..."
Submissions developed in response to this RFP are expected to achieve the following:
- A common vocabulary and metamodel to unify the diverse service definitions that exist in the industry.
- Clarify UML semantics concerned with services modeling and establish modeling best practices.
- Complement existing UML metamodel by defining an extension to UML to ensure complete and consistent service specifications and implementations.
- Integrate with and complement standards developed by other organizations such as W3C and OASIS to facilitate collaborations between service consumer and providers.
- Support a service contract describing the collaboration between participating service consumers and service providers using mechanisms that clearly separate service requirements and specification from realization.
- Enable traceability between contracts specifying services requirements, service specifications that fulfill those requirements and service providers that realize service specifications.
- Facilitate the adoption of Service Oriented Architectures through more abstract and platform independent services models to speed service development, decouple service design from evolving implementation, deployment and runtime technologies, and enable generation of platform specific artifacts.
- The ability to exchange services models between tools using XMI.
It is expected that responses to this RFP will make good use of SOA modeling capabilities already supported by UML. This may require clarifications of UML semantics, best practices that may be incorporated in constraints in UPMS, and possibly issues raised against UML with proposed resolutions.
The purpose of this RFP is to address Service Modeling, not methodologies for SOA. However, submissions are expected to demonstrate how service models relate to business process models on the one hand and existing Web Services standards (XSD, WSDL, BPEL, etc.) on the other in order to facilitate bridging the gap between business models and deployed services solutions.
Submissions developed in response to this RFP should avoid the following capabilities which are expected to be follow-on extensions of UPMS, addressed by separate RFPs, and/or handled by other standards organizations:
- Methodologies for service design. This RFP does not espouse or recommend any service or discovery methodology. Any references to methodologies serve only to enable understanding. What the RFP does specify is the content captured by any service methodology.
- Services governance or compliance.
- Service metrics, policy, security, trust, performance, or other Qualities of Services
- Wire protocols and/or message transfer encodings or marshalling.
- Message delivery reliability, transaction scopes, or other mechanisms for managing data integrity.
- Service brokering, publishing, discovery, service addressing, service registries, asset management.
- Service runtime configuration and deployment.
- Dynamic binding, service federation, mediation, service bus structure, or other service execution concerns.
- User experience or user interfaces.
These are concepts that are not currently addressed in UML or are concerned with qualities of service or service execution. The reason for excluding these capabilities is to limit the scope of this RFP in order to provide a foundation as quickly as possible which can be effectively extended to address these and other concerns as appropriate. Another motivation is to allow these concepts to stabilize in practice before attempting to standardize them, or allow them to be addressed by more appropriate standards bodies.
Adoption of a submission to this RFP will improve communication between modelers, including between business and software modelers, provide flexible selection of tools and execution environments, and promote the development of more specialized tools for the analysis and design of artifacts of emerging Service Oriented Architectures....