1. Architecture Ecosystem SIG March 2010 Update Jacksonville FL

2. Fragmented Architecture Domains

3. Unified Architectures

4. Multiple Stakeholder Viewpoints Different stakeholders need different views of the same information

5. Semantically Federating Multiple Viewpoints and Standards

6. What it is and is NOT Provide the infrastructure and methodology to support an ecosystem of modeling languages Provide the infrastructure and methodology to support an ecosystem of modeling languages May include integrating and/or refactoring of how existing languages are expressed May include integrating and/or refactoring of how existing languages are expressed Provide a roadmap for OMG standards to provide and exploit the ecosystem to define and federate languages Provide a roadmap for OMG standards to provide and exploit the ecosystem to define and federate languages Not intended to create or change modeling languages Not intended to create or change modeling languages

7. AESIG – A Short History Created at Long beach meeting (last meeting) Created at Long beach meeting (last meeting) Created wiki and mailing list Created wiki and mailing list http://www.omgwiki.org/architecture- ecosystem/doku.php http://www.omgwiki.org/architecture- ecosystem/doku.php http://www.omgwiki.org/architecture- ecosystem/doku.php http://www.omgwiki.org/architecture- ecosystem/doku.php Nine virtual phone meetings (5 to 22 people) Nine virtual phone meetings (5 to 22 people) Initial phase has emphasized discussion and collecting viewpoints Initial phase has emphasized discussion and collecting viewpoints Moving to the phase of creating a roadmap Moving to the phase of creating a roadmap

8. Points of Agreement That we need to be able to create architectures that include information expressed in multiple modeling languages That we need to be able to create architectures that include information expressed in multiple modeling languages That what we are doing now is not providing this capability That what we are doing now is not providing this capability That there is substantial user and vendor requirement for a more federated architectural environment That there is substantial user and vendor requirement for a more federated architectural environment Separation of model and viewpoints Separation of model and viewpoints Layered with stronger semantics Layered with stronger semantics That we come up with needs to exploit and extend what we have now in standards such as UML, BPMN and UPDM That we come up with needs to exploit and extend what we have now in standards such as UML, BPMN and UPDM That UPDM is a good example of the kind of integrated framework we should be able to provide That UPDM is a good example of the kind of integrated framework we should be able to provide

9. Notional Architecture Modular & Layered Semantic Model Viewpoint-A Terminology, Structure & Notation Projection Grounding Viewpoint-B Terminology, Structure & Notation Viewpoint-C Terminology, Structure & Notation Grounding Projection Mapping

10. Notional Architecture Modular & Layered Semantic Model Viewpoint-A Terminology, Structure & Notation Projection Grounding Viewpoint-B Terminology, Structure & Notation Viewpoint-C Terminology, Structure & Notation Grounding Projection Architectural Information Linking, Federation, Integration & Mapping Mapping

11. Points of Contention What is the best way to model the semantic model, viewpoints and mappings? What is the best way to model the semantic model, viewpoints and mappings? How much we should commit to extending the MOF platform Vs exploiting other industry initiatives, such as RDF How much we should commit to extending the MOF platform Vs exploiting other industry initiatives, such as RDF Is MOF more PIM or PSM, should we have a MOF independent PIM? Is MOF more PIM or PSM, should we have a MOF independent PIM? How much should we use/exploit the semantic web technologies (RDF, OWL, Etc) How much should we use/exploit the semantic web technologies (RDF, OWL, Etc) How far to go with semantics and how to represent those semantics How far to go with semantics and how to represent those semantics Point-point Vs hub/spoke integration Point-point Vs hub/spoke integration Linking Vs. Mapping Linking Vs. Mapping

12. Wiki Summary Tour of Wiki Tour of Wiki Developing requirements Developing requirements Concepts and terminology Concepts and terminology Options and positions Options and positions Roadmap Roadmap

13. Roadmap Problem space and scope Problem space and scope Use cases and user stories Use cases and user stories Vision Vision Architecture Ecosystem Foundation Architecture Ecosystem Foundation Applying the architecture ecosystem to OMG specifications Applying the architecture ecosystem to OMG specifications Examples Examples Assessment Assessment Roadmap for future action – RFPs to issue Roadmap for future action – RFPs to issue

14. Problem space and scope How modeling languages are expressed How modeling languages are expressed How modeling languages are extended with new capabilities How modeling languages are extended with new capabilities How the same, or similar concepts, in different modeling languages are integrated How the same, or similar concepts, in different modeling languages are integrated How notations, diagrams, views and viewpoints are defined and mapped to modeling languages How notations, diagrams, views and viewpoints are defined and mapped to modeling languages How modeling languages are grounded semantically How modeling languages are grounded semantically How models expressed in these modeling languages may be managed, linked and interchanged using a variety of technical platforms How models expressed in these modeling languages may be managed, linked and interchanged using a variety of technical platforms How structured knowledge is supported at many levels and domains, including How structured knowledge is supported at many levels and domains, including

15. Languages Requiring Integration OSM and Business Architecture OSM and Business Architecture Combining modular capabilities (replacement of PackageMerge) Combining modular capabilities (replacement of PackageMerge) BPMN and SoaML integration BPMN and SoaML integration SoaML and QoS integration SoaML and QoS integration BMM and BPMN integration BMM and BPMN integration Specification of UPDM and integration with BMM and BPMN Specification of UPDM and integration with BMM and BPMN IMM IMM OWL and ERA integrated with UML OWL and ERA integrated with UML TOG SOA Ontology, SOA Reference Architecture and SoaML TOG SOA Ontology, SOA Reference Architecture and SoaML Fact Based Modeling (FBM) Fact Based Modeling (FBM)

16. Defining Architecture Ecosystem Foundation - AEF Language Definition Concepts Language Definition Concepts Extending a Modeling Language Extending a Modeling Language Integrating Modeling Languages Integrating Modeling Languages Defining Views and Viewpoints Defining Views and Viewpoints Semantic Grounding Semantic Grounding UML Profile for AEF UML Profile for AEF AEF Viewpoint AEF Viewpoint

17. Applying AEF to OMG Specifications Use AEF for M2 meta-model definition, extension and integration Use AEF for M2 meta-model definition, extension and integration Provide complete, end-to-end, executable scenarios Provide complete, end-to-end, executable scenarios Demonstrate, communicate and validate the AE SIG vision Demonstrate, communicate and validate the AE SIG vision Demonstrate how the vision addresses the Requirements Demonstrate how the vision addresses the RequirementsRequirements Show how meta-modelers would use the integrated solution Show how meta-modelers would use the integrated solution Possible examples: Possible examples: UML Capabilities UML Capabilities Business Architecture Business Architecture SOA Modeling SOA Modeling UPDM UPDM

18. Examples using Integrated Meta-models Verify the integrations defined in the previous sections for M1 models Verify the integrations defined in the previous sections for M1 models Demonstrate how end-users would create their own viewpoints Demonstrate how end-users would create their own viewpoints Demonstrate how end-users would extend the modeling language(s) for Demonstrate how end-users would extend the modeling language(s) for MDA markings MDA markings Some missing modeling capability, or Some missing modeling capability, or To integrate with information not covered in existing modeling languages To integrate with information not covered in existing modeling languages requirements motivating the models requirements motivating the models work items representing actions to be taken as a result of communicating modeling information work items representing actions to be taken as a result of communicating modeling information etc. etc.

19. Assessment Applicability of the solution to the problem Applicability of the solution to the problem QoS QoS Response to other requirements Response to other requirements Adjust requirements and solution proposal as needed Adjust requirements and solution proposal as needed Refine and iterate until some agreed upon workable solution evolves Refine and iterate until some agreed upon workable solution evolves

20. Roadmap Actions Architecture Ecosystem Foundation RFP – Architecture Ecosystem Foundation RFP – This includes the core concepts, their semantic grounding and mapping to both MOF and RDF/S This includes the core concepts, their semantic grounding and mapping to both MOF and RDF/S UML profile for expressing modeling languages using these concepts UML profile for expressing modeling languages using these concepts Populated library of concepts to the extent required for reflective definition Populated library of concepts to the extent required for reflective definition Language Integration RFP Language Integration RFP A defined set of modeling language integration issues A defined set of modeling language integration issues Any required extensions to the concept library Any required extensions to the concept library Mapping the concept library to the subject languages Mapping the concept library to the subject languages

21. Mission The mission of the Architecture Ecosystem SIG (AE SIG) is to work with OMG domain and platform task forces, other relevant OMG SIGs, external entities and related industry groups to facilitate the creation of a common architectural ecosystem. This ecosystem will support the creation, analysis, integration and exchange of information between modeling languages across different domains, viewpoints and from differing authorities. In particular the need for business and enterprise level architectural viewpoints must be better integrated with the technical viewpoints that define systems to address enterprise needs. The AE SIG will focus on the capability to define and integrate languages and models in various viewpoints and support other groups that will focus on the specific viewpoints required for their specific domains. The set of viewpoints, supporting models and supporting technologies will comprise the ecosystem. The mission of the Architecture Ecosystem SIG (AE SIG) is to work with OMG domain and platform task forces, other relevant OMG SIGs, external entities and related industry groups to facilitate the creation of a common architectural ecosystem. This ecosystem will support the creation, analysis, integration and exchange of information between modeling languages across different domains, viewpoints and from differing authorities. In particular the need for business and enterprise level architectural viewpoints must be better integrated with the technical viewpoints that define systems to address enterprise needs. The AE SIG will focus on the capability to define and integrate languages and models in various viewpoints and support other groups that will focus on the specific viewpoints required for their specific domains. The set of viewpoints, supporting models and supporting technologies will comprise the ecosystem.