1. Architectural Ecosystem (AE) AB SIG SIG Formation 2009 Long Beach OMG Meeting Cory Casanave Model Driven Solutions Discussion: model-arch@omg.org

2. Initiatives Behind the AE SIG UML Futures UML Futures Identified the need for a strategic modeling infrastructure – one that takes the UML brand into new markets Identified the need for a strategic modeling infrastructure – one that takes the UML brand into new markets Business Architecture White Paper Business Architecture White Paper Identified the need for stronger links between viewpoints and in particular the link between business and technology viewpoints Identified the need for stronger links between viewpoints and in particular the link between business and technology viewpoints UPDM/DoDAF-2 UPDM/DoDAF-2 A primary goal of DoDAF-2 is the integration of the data behind multiple viewpoints addressing the full life-cycle of architecture. Has the need to integrate multiple OMG standards (meta models and profiles) A primary goal of DoDAF-2 is the integration of the data behind multiple viewpoints addressing the full life-cycle of architecture. Has the need to integrate multiple OMG standards (meta models and profiles) BPMN/UML Integration Issues BPMN/UML Integration Issues Fundamentally a language integration isue Fundamentally a language integration isue Information Meta Model (IMM) Information Meta Model (IMM) Currently defining a common framework for data languages Currently defining a common framework for data languages

3. Fragmented Architecture Domains

4. Unified Architectures

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

6. Semantically Federating Multiple Viewpoints and Standards

7. The OMG Meta-Muddle The OMG has created stovepipes, hard to integrate and understand The OMG has created stovepipes, hard to integrate and understand Since each stovepipe has to solve world hunger, each becomes big and complex or dies Since each stovepipe has to solve world hunger, each becomes big and complex or dies Consider using these together today: Consider using these together today: UML-2, BPMN-2, IMM, ODM, SBVR, SoaML, SysML, UPDM UML-2, BPMN-2, IMM, ODM, SBVR, SoaML, SysML, UPDM Profiles do not mix well with other profiles or with other meta models at all Profiles do not mix well with other profiles or with other meta models at all Mapping the stovepipes does not make an effective integrated environment! Mapping the stovepipes does not make an effective integrated environment! This meta-muddle is compromising the value of each standard and making OMG & modeling less relevant This meta-muddle is compromising the value of each standard and making OMG & modeling less relevant Move to leading the solution rather than causing the problem Move to leading the solution rather than causing the problem The leaders in architecture have a lousy architecture – how embarrassing! The leaders in architecture have a lousy architecture – how embarrassing! We need to FIX the Meta-Muddle Madness! We need to FIX the Meta-Muddle Madness!

8. Example - DoDAF-2 Vision

9. The Architectural Ecosystem Open Markets, Open World The technologies and standards that have been successful are those that provide a foundation for the marketplace to build on The technologies and standards that have been successful are those that provide a foundation for the marketplace to build on Visual Basic, Java, Eclipse, TCP/IP, Etc Visual Basic, Java, Eclipse, TCP/IP, Etc Why are people still building their modeling foundations on PowerPoint, Visio and Excel? Why are people still building their modeling foundations on PowerPoint, Visio and Excel? Because the foundation we have provided is not open – it is a “closed world” except for the restrictive capabilities of UML profiles. Because the foundation we have provided is not open – it is a “closed world” except for the restrictive capabilities of UML profiles. An Open Market / Open World approach to modeling has an inherently unlimited market and the potential to excite and embrace new users and new markets An Open Market / Open World approach to modeling has an inherently unlimited market and the potential to excite and embrace new users and new markets

10. High-Level Goals The set of architectural languages defined in the ecosystem should, together, create a complete architectural environment The set of architectural languages defined in the ecosystem should, together, create a complete architectural environment Advantages of unified tools – integrated Advantages of unified tools – integrated Without the coupling of monolithic tools Without the coupling of monolithic tools Full life-cycle Full life-cycle Integrating the same information about the same enterprise from multiple viewpoints Integrating the same information about the same enterprise from multiple viewpoints Well defined meaning Well defined meaning Flexible for extension and new viewpoints Flexible for extension and new viewpoints Models as data – repurpose, query, mash-up Models as data – repurpose, query, mash-up The goal of the architectural ecosystem is to figure out how to do this – to architect our architectures The goal of the architectural ecosystem is to figure out how to do this – to architect our architectures Identify real or perceived problems and find solutions Identify real or perceived problems and find solutions Take action – don’t become a never-ending discussion! Take action – don’t become a never-ending discussion!

11. Ecosystem IMM Family of Languages UML Class Diagrams Activity Diagrams Sequence Diagrams State Diagrams Interaction Diagrams Use Cases Motivations BPMN Business RulesOWL Value Chains SQL XML Schema Cobol SoaML SysML UPDM Java C#

12. Ecosystem IMM Family of Languages UML Class Diagrams Activity Diagrams Sequence Diagrams State Diagrams Interaction Diagrams Use Cases Motivations BPMN Business RulesOWL Value Chains SQL XML Schema Cobol SoaML SysML UPDM Java C#

13. The OMG Meta-Model & Model Resource We have an enormous resource – our current meta models and user models We have an enormous resource – our current meta models and user models A cross-section of required viewpoints – from business models to ADM A cross-section of required viewpoints – from business models to ADM (Reasonably) well defined concepts so that we can better understand their connections (Reasonably) well defined concepts so that we can better understand their connections Existing interchange formats so we can evaluate existing models and test any solution Existing interchange formats so we can evaluate existing models and test any solution Use this resource as a set of use cases and requirements for the Architectural Ecosystem Use this resource as a set of use cases and requirements for the Architectural Ecosystem

14. This is being done now Current Integrated Modeling Efforts Current Integrated Modeling Efforts DoDAF DM2 DoDAF DM2 FEA/FSAM FEA/FSAM Proprietary tool models Proprietary tool models BPDM & IMM BPDM & IMM Nasa NExIOM Nasa NExIOM (Proposed) Business Modeling Framework (Proposed) Business Modeling Framework Unified Process Model (NIST) Unified Process Model (NIST) Model Driven Solutions “EKB” Model Driven Solutions “EKB” Others…. Others…. A major problem and multiple non integrated solutions – sounds like standards time!

15. Architecture Ecosystem and UML The key to the future of UML is not “UML” it is the architectural ecosystem The key to the future of UML is not “UML” it is the architectural ecosystem UML needs to be a part of the AE and to play a role in this ecosystem UML needs to be a part of the AE and to play a role in this ecosystem UML should not stop while UML is in progress, continue to incrementally evolve UML UML should not stop while UML is in progress, continue to incrementally evolve UML The expertise and market position of UML and other tool vendors should be part of the solution. OMG seems like the right place to do this The expertise and market position of UML and other tool vendors should be part of the solution. OMG seems like the right place to do this UML offers a rich set of modeling concepts to integrate, but the answer can’t be “UML Centric” or “OO Centric” or “I.T. Centric” – languages defined in the AE can be “Centric” but the AE should not have a dominant decomposition. UML offers a rich set of modeling concepts to integrate, but the answer can’t be “UML Centric” or “OO Centric” or “I.T. Centric” – languages defined in the AE can be “Centric” but the AE should not have a dominant decomposition. Initially UML would live in parallel to AE as a mapping, later UML may be natively based on AE – this minimizes market impact on UML-2 Initially UML would live in parallel to AE as a mapping, later UML may be natively based on AE – this minimizes market impact on UML-2 As the AE would not be defining a “new language”, it would not address some UML superstructure issues – this should come after AE or, if small, be done incrementally, extending UML-2 As the AE would not be defining a “new language”, it would not address some UML superstructure issues – this should come after AE or, if small, be done incrementally, extending UML-2

16. UML/BPMN Integration Poll They remain separate standards 3 BPMN is a UML profile with notation 6 Create is a unified model encompassing both 13 Semantic models with UML and BPMN viewpoints 9 BPMN replaces UML activity diagrams 4 BPMN grows to make UML not required 0 BPMN and UML are separate models, mapped with QVT 2 There are ways to make links between them 3

17. Potential Solution Scenarios Improved meta modeling infrastructure Improved meta modeling infrastructure Having specific intent is to support a family of languages Having specific intent is to support a family of languages Better ways to precisely define languages Better ways to precisely define languages Better mapping between them Better mapping between them Decoupling of structure, semantics and representations Decoupling of structure, semantics and representations Grounding of languages in common semantics Grounding of languages in common semantics Formal semantics Formal semantics Improved sharing and/or linking between languages Improved sharing and/or linking between languages Shared concepts Shared concepts Bridge models Bridge models Interchange of all aspects of architectures (diagrams, viewpoints, context, etc) Interchange of all aspects of architectures (diagrams, viewpoints, context, etc) Better process for reuse, sharing and linking Better process for reuse, sharing and linking

18. Didn’t we try this? Or, why did the UML-Infrastructure Fail? Or, why did the UML-Infrastructure Fail? Meta-modeling infrastructure issues Meta-modeling infrastructure issues The late and questionable introduction of package merge as the sharing mechanism The late and questionable introduction of package merge as the sharing mechanism No federation mechanism No federation mechanism No viewpoint mechanism No viewpoint mechanism The now obvious lack of multiple classification The now obvious lack of multiple classification Structural, not semantic meta model Structural, not semantic meta model Informality of approach Informality of approach Project Issues Project Issues Driving the infrastructure solely from the needs of UML-2 & “OO” instead of embracing a family of languages approach Driving the infrastructure solely from the needs of UML-2 & “OO” instead of embracing a family of languages approach Trying to change the infrastructure and superstructure at the same time Trying to change the infrastructure and superstructure at the same time Political goals of putting every possible viewpoint and methodology into UML Political goals of putting every possible viewpoint and methodology into UML Team dynamics and leadership Team dynamics and leadership

19. Work Plan User Stories User Stories Solution Scenarios Solution Scenarios Work virtual – use mail list and wiki Work virtual – use mail list and wiki Face-face, probably on Sunday prior to OMG meetings Face-face, probably on Sunday prior to OMG meetings Weekly or biweekly meetings Weekly or biweekly meetings Target initial deliverables for 3 rd meeting 2010 Target initial deliverables for 3 rd meeting 2010 Focus on deliverables and action, not endless discussion Focus on deliverables and action, not endless discussion

20. Notes on Initial Thoughts Better infrastructure retired to support breadth of UPDM Better infrastructure retired to support breadth of UPDM Need for viewpoints and loose coupling Need for viewpoints and loose coupling Standards such as time ontology already need to be represented in 3 separate languages Standards such as time ontology already need to be represented in 3 separate languages Look for sweet spot between extremes of monolithic models and anarchy Look for sweet spot between extremes of monolithic models and anarchy DoD has several drivers – architectures should work together, IT Standards and Acquisition. DoD has several drivers – architectures should work together, IT Standards and Acquisition. There is some interesting work along this lines in SBVR There is some interesting work along this lines in SBVR Interest in exploiting RDF-LOD for both technical and community reasons Interest in exploiting RDF-LOD for both technical and community reasons Separation of concerns between defining and connecting languages logically and the various technical infrastructures to support them (MDA applied to MDA) Separation of concerns between defining and connecting languages logically and the various technical infrastructures to support them (MDA applied to MDA) Need paper outlining vision and straw-man approach Need paper outlining vision and straw-man approach

21. Why an AB SIG? Concerns are cross cutting and should not be driven from any one viewpoint Concerns are cross cutting and should not be driven from any one viewpoint ADTF – MOF, UML, Etc ADTF – MOF, UML, Etc BMI – BPMN, Business Meta Models BMI – BPMN, Business Meta Models Business Architecture Business Architecture Domain specific meta models Domain specific meta models This is essentially an architectural pursuit This is essentially an architectural pursuit AB seems like the right place AB seems like the right place May define architecture process or policy May define architecture process or policy May champion RFPs in multiple task forces May champion RFPs in multiple task forces

22. Architecture Ecosystem Mission Statement

23. Mission Statement Introduction 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.

24. Problem Statement OMG languages can be defined using the MOF meta model and models based on OMG standards can be exchanged and serialized using the MOF standards. In this way the MOF provides a common platform for exchanging and, in some cases managing, model information. Despite the MOF capabilities, languages and UML profiles are excessively stove piped and not easily integrated. Information in models is not easily accessible over the internet which makes it difficult to query, federate and links across models from different authorities and those in different languages. The semantics of language elements is not well grounded or formalized. Real and perceived issues with the MOF as well as OMG process have contributed to these problems.

25. What The AE SIG Will Do Through the OMG processes, recommend improvements, changes and/or additions to the OMG modeling infrastructure to better support these requirements. This includes but is not limited to improvements in the way languages are modeled and integrated. The SIG will facilitate improving support for viewpoints, support for formal methods[1], support for federating independently conceived models and support for model data as open internet accessible data. Through the OMG processes, recommend improvements, changes and/or additions to the OMG modeling infrastructure to better support these requirements. This includes but is not limited to improvements in the way languages are modeled and integrated. The SIG will facilitate improving support for viewpoints, support for formal methods[1], support for federating independently conceived models and support for model data as open internet accessible data.[1] Evaluate reasons for problems and perceived problems with the OMG modeling standards and infrastructure. Evaluate the business case for addressing any such problems. Evaluate reasons for problems and perceived problems with the OMG modeling standards and infrastructure. Evaluate the business case for addressing any such problems. Identify use cases, scenarios and examples to act as a guide for evaluating approaches to solving real and perceived problems. Identify use cases, scenarios and examples to act as a guide for evaluating approaches to solving real and perceived problems. Recommend the guiding principles, technologies, best practices and policies for recognizing and leveraging the commonalities between different languages and viewpoints. This may include managing dictionaries, models, mappings or ontologies of these concepts. These recommendations will specifically address the strategic modeling architecture requirements identified as part of the UML Futures RFI as well as the needs identified in the Business Architecture White Paper. Recommend the guiding principles, technologies, best practices and policies for recognizing and leveraging the commonalities between different languages and viewpoints. This may include managing dictionaries, models, mappings or ontologies of these concepts. These recommendations will specifically address the strategic modeling architecture requirements identified as part of the UML Futures RFI as well as the needs identified in the Business Architecture White Paper. Analyze existing and proposed architectural concepts in various standards and domains for commonality, synergy and differences and leverage that commonality and synergy for better federation based on the best practices approach identified above. Analyze existing and proposed architectural concepts in various standards and domains for commonality, synergy and differences and leverage that commonality and synergy for better federation based on the best practices approach identified above.

26. Desired Result The resulting capability envisioned by the AE-SIG is that architectural viewpoints (also known as domain specific languages or DSLs) will be better integrated and consistent, enable more flexible extension and integration with other information, and therefore provide greater value. In addition these architectural viewpoints will be available as web-accessible data such that architectures can be used and federated across organizational and domain boundaries. This will enable architectures and architectural efforts to more directly address modern enterprise needs for data sharing, service use and reuse, business process integration, openness and collaboration on multiple levels.