Date post: | 14-Dec-2015 |
Category: |
Documents |
Upload: | aileen-watkins |
View: | 218 times |
Download: | 0 times |
1 Architectural Ecosystem1
Architectural EcosystemOpen Source Project Proposal
Cory Casanave (cory-c at modeldriven.com)Sept. 2009 V0.50
Copyright © 2009, Data Access Technologies, Inc.
2 Architectural Ecosystem2
A Strategic Opportunity Today, modeling, architecture,
vocabularies and enterprise information are closed and siloed
There is an opportunity To help federate information for
and about the enterprise and enterprise systems
To enable architecture as an open and collaborative experience, tuned to the needs of stakeholders
To discover and reconcile concepts, entities and architectures throughout the enterprise and beyond.
To unify the knowledge in multiple tools, infrastructures and information resources
To enable the transformations, agility, efficiency, collaboration and automation we have been promising for years
3 Architectural Ecosystem3
The Architectural EcosystemOpen Markets, Open World 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 – all provide a foundation to build on,
not an end result – this has been key to their success.
Why are people still modeling their architectures in PowerPoint, Visio and Excel? Because the foundation we have provided is not open – it is a “closed world” Because modeling environments are inflexible and hard to use, unable to adapt
to stakeholder needs.
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
Lets create an Ecosystem for Architecture
4 Architectural Ecosystem4
The Architectural Ecosystem Idea What is the opportunity?
There is an opportunity for an architectural ecosystem that will solve major government and industry problems. The information contained in DoDAF, FEA, UML and other OMG and non-OMG standards, once federated, can be a springboard for and part of this ecosystem implemented as a pervasive open source capability
What do users want? Users want better ways to plan, design, discover, reconcile and realize their business and
technology objectives and to have open technologies and vocabularies that facilitate these objectives without artificial boundaries or complexities. They want enterprise knowledge on their terms.
What is the core idea? By integrating the full life-cycle of modeling using an open world, open market architectural
ecosystem based on “Linked Open Data” we can address crucial enterprise needs with a profitable business model
This ecosystem provides for federated semantic models with multiple views and viewpoints What about UML and other OMG standards as they are now?
UML, BPMN, UPDM and MOF are not designed for or sufficient as the foundation for the architectural ecosystem. However, they can be a major part of that ecosystem. UML and BPMN notations can be views in the ecosystem. UML is both too large and too small. Extensibility will enable simplicity.
Conclusion We can be the foundation of an architectural ecosystem that captures, communicates and
leverages knowledge for and about the enterprise and enterprise systems at many levels and from many viewpoints. We can choose to be a leader in forming that ecosystem or let it pass us by. This will create new business opportunities and address crucial user requirements
5 Architectural Ecosystem
Ecosystem supporting multiple viewpoints and standards
6 Architectural Ecosystem6
The ModelDriven.org Open Source Project
Our intent is to create a pervasive capability, doing so as open source has the best chance of success and provides stakeholders with a platform on which to build products and services Initiate a funded open source project to create the foundation for the
Architectural Ecosystem Charter a team of world-class experts to put the foundation in place Invite key industry, end user and government stakeholders to participate Sponsors contributes $25k/Month and one FTE First stage planned for one year Current baseline built on Java but other platforms can be supported as
well – can work with vendors to build other implementations 3-7 Sponsors to start
Try it out on: http://portal.modeldriven.org/project/EKB
7 Architectural Ecosystem7
What Will Be Developed? Model server based on Linked Open Data that federates information from multiple
sources (Builds on existing ModelDriven.org baseline) Core repository and server MOF/UML/BPMN model or meta model to Linked Open Data RDF transformation Semantic integration of models and meta models – use them together Support for views, viewpoints and projecting models to viewpoints Web user interfaces based on viewpoints Model transformation between languages and tools Hooks for capabilities such as discovery, analysis and reconciliation (Option) EMF API Support over RDF repository (Option) Executable model engine and action language
Models Ontology and UML profile for language integration and definition Ontology to support linking and federating languages and models as well as projecting
semantic models to viewpoints Hub vocabularies and ontologies of architecture integrating concepts of UML, BPMN,
Information Modeling, Business Motivation and others Standards
Support for MOF to RDF, future of UML and business architecture standards
8 Architectural Ecosystem8
Advantages of this approach
Expands marketplace, potentially integrating: Business modeling Process Modeling, Information Modeling, Service Modeling Enterprise Architecture Metrics Motivation & requirements Systems modeling OO modeling Ontologies MDA Others we have not thought of
Provides a foundation for a rich set of federated languages, tools and supporting capabilities
Will not destabilize current tools markets “waiting for UML 3” Puts in place a strategic capability we can all build on and leverage
9 Architectural Ecosystem
Detailed Sections
Key Opportunities Simple Example Business Structure Industry Business Case Team Users Business Case Standards and Technologies
10 Architectural Ecosystem10
Action Items
Consider your commitment to this effort Highly interested – provide letter of intent Interested – resolve questions and issues Not interested – please let us know
Requesting a one week turn-around for initial reactions
Refine business and project plan
This Presentation:http://lib.modeldriven.org/MDLibrary/trunk/Pub/Presentations/EcosystemOpenSourceProject.ppt
11 Architectural Ecosystem11
Key Opportunities
Also see http:www.GAINInitiative.net for more
12 Architectural Ecosystem12
Open Government
Provide a key enabling capability for open government Enable transparency, collaboration and participation by
publishing, integrating and collaboratively developing the nation’s architectures, including: Vocabularies, Business architectures, Services Architectures,
Enterprise Architectures, Information Architectures, Process Architectures, Business Rules, Systems of Systems Architectures, Implementation Architectures
Architectures available as linked open data on the internet and available on Data.gov
Provide a common foundation for industry, DoD, OMB and agency architectures to be collaborative and linked
13 Architectural Ecosystem13
Healthcare
Unified architecture for healthcare and records management
Common foundation for health and operational data Break the interoperability log jam Provide architectures that span technologies and
organizations Use architected technologies to reduce costs and
improve healthcare
14 Architectural Ecosystem14
Open Business Intelligence
The foundation of Business Intelligence is enterprise information
Most BI platforms depend on proprietary infrastructure and formats
Use the Ecosystem and Linked Open Data as the foundation for Open Business Intelligence and Data Warehousing
15 Architectural Ecosystem15
Enterprise Knowledge Base
Metadata about enterprise services, information, processes, rules, systems, policies, vocabularies and metrics is currently dis-integrated
The Enterprise Knowledge Base (EKB) can provide a federated repository of information from and about the enterprise, from a variety of sources
Each architecture can then be managed, linked, analyzed and utilized for purposes never originally intended
Stakeholder specific views make enterprise knowledge accessible Ease of creating information makes new enterprise knowledge
available Model transformation between languages, tools and viewpoints Can be an integrating framework under new and existing tools
16 Architectural Ecosystem16
Executable Models
Executable Models and simulation provide a direct path from architecture to a realized solution that directly supports business needs
Reducing development time and costs while improving agility Execution can be supported by viewpoints and execution engines
built on available technologies Existing efforts like Foundational UML, Action Language, Eclipse
and ModelPro provide a basis for Executable models Multiple execution platforms and technologies can be supported Execution capability will be integrated into the architectural
ecosystem once the foundation is in place
17 Architectural Ecosystem
Simple Examples
How linking architectures with each other and with external data
solves problems
18 Architectural Ecosystem
Different models may represent the same enterprise – even the same information
But there are usually
structural differences
How do we link these concepts?
19 Architectural Ecosystem
Two ways to say the same thing
UML uses an arrow to say that a branch is a rental organization unit
E/R Uses “Nesting” to say that a branch is a rental organization unit
How do we know these both say
the same thing?
How do we know these both say
the same thing?
20 Architectural Ecosystem
We want to ask this question
What city branches are in cities with a population of less than 1 million?Population information is in the U.S. census
data – accessible as linked open data
http://www.rdfabout.com/demo/census/Our DBMS
How do we link these data sets?
How do we know the concept “city” and “zip code” is
the same?
21 Architectural Ecosystem
Which impacts the business
process
Rules, Processes and Services Support Business Functions
Then we may want to add a business rule
The process may require
SOA services and components
All aspects of the same enterprise!
22 Architectural Ecosystem
The Ecosystem Helps By
Allowing us to understand that two model (or DBMS) elements may represent the same thing E.G. “Branch” is the same in both models Because we have a way to record that these represent the same real-world
concept To understand the where the semantics of the language overlap, or don’t
E.G. Two ways to say that a branch is a rental organization Because we can understand the shared concept of a subtype in both
architectural languages To connect diverse data sets
Our DBMS, Model and The U.S. Census Because both can leverage Linked Open Data and we can query across both
data sets Integrating Models, Data, Rules, Process, Services and Components
As data linked in the ecosystem
23 Architectural Ecosystem23
Business Structure
24 Architectural Ecosystem24
Business Structure Instituted as a funded project of ModelDriven.org ModelDriven.org is currently a division of Data Access Technologies but
would “spin off” into a not for profit Board of sponsors would direct the project effort All assets are produced as open source and donated to ModelDriven.org Project assets may move into other open source organization once
complete Any work done that is specific to a single participants needs is funded
separately Team members would be provided by sponsors & supporting companies
like Model Driven Solutions and Sandpiper Software Team is provided by supporting companies at loaded cost (no profit) to
project, at least 90% of funds go directly to development efforts
25 Architectural Ecosystem25
Resource Commitment
Each sponsor contributes $25k/Month into the effort, plus Each sponsor contributes one “FTE”, perhaps split between two
people (Other options can be considered if no FTE is available) Expected one year commitment, but a sponsor can cancel if project
is not meeting their business needs Some sponsors may want to do related development, perhaps using
an alternate technology stack. This would be supported by but not done by the core team – such development would require separate resources and funding
Project board could vote to raise the monthly commitment to accelerate results
26 Architectural Ecosystem26
Potential Sponsors DoD/OSD Computer Sciences Corporation IBM Hewlett Packard John Deere Lockheed Martin Microsoft Mitre NASA NIST NoMagic NTT Data Oracle SAIC SAP Unisys
Many of these organizations have already expressed interest based on preliminary information. Others may be invited as well.
27 Architectural Ecosystem27
GAIN Initiative
Existing initiative on ModelDriven.org Provides business case and community for the
ecosystem The ecosystem can be the implementation project
behind GAIN
http://www.GAINInitiative.net Note – this is still work in progress and there are issues we are
working on resolving. It should, however, give you a feel for the existing capabilities.
28 Architectural Ecosystem28
Working with Other Organizations
The Ecosystem effort is not intended to be an island, it will be part of and support other efforts Standards in OMG, W3C, Open Group, ISO and Oasis All or parts of the assets could be donated to or built in
collaboration with other open source efforts Eclipse JAZZ Apache Codeplex
Data.gov, DoDAF DM2 and UPDM Office of Management and Budget (FEA/FSAM) Others as appropriate
29 Architectural Ecosystem29
Industry Business Case
30 Architectural Ecosystem30
Industry Business Case Address crucial customer needs Influence and have early access to a strategic capability Be a leader in meeting user expectations with strategic modeling and architecture Provide products and services for knowledge management, architecture, governance,
planning, and automating development Reduce costs of developing, maintaining and integrating multiple overlapping tools
and repositories A community effort has a higher chance of success and lower cost Low risk and exposure – need not interfere with internal plans, politics, resources or
visible strategy Agile development of proof of concept justifies ongoing investment until it is product-
ready Provides a platform for multiple tools and infrastructure products – commercial add-
ons Integrate with product plans when ready
31 Architectural Ecosystem31
Team
We have the opportunity to bring together a world class team of known experts to achieve these goals
32 Architectural Ecosystem32
Strategic Team Resources Cory Casanave – Thought leader in architecture, meta modeling, open
source, standards and semantic integration– experienced tool developer who will lead the effort
Ed Seidewitz – World class architect and expert in UML, Executable UML, meta modeling, standards and development who will be the chief architect of the future modeling capability
Tom Digre – World class architect and developer focused on knowledge integration and provisioning who will lead the development of core capabilities
Jim Logan – World class modeler/architect, UML authority and Data/Information expert who will bring together diverse viewpoints into a common model
Elisa Kendall – World class Ontologist and tool developer who will provide the semantic integrity for the solution
Others…
33 Architectural Ecosystem33
Team Availability
These world class experts are available now and motivated to take on a challenge like this today, however, availability can not be guaranteed in the future without sponsorship. Other highly qualified potential team members are also available. Some of the above would be 50% (aprox) dedicated to the effort.
34 Architectural Ecosystem34
User Business Case
35 Architectural Ecosystem35
User Problems
Organizations are very frustrated They can’t easily share data, services or processes Their systems are not business driven or interoperable Their business processes are not even business driven They find it hard to collaborate, to integrate The are not agile, their technology holds them back They have rampant redundancy in capabilities They can’t plan a transition and make it happen Complexity at all levels (business and technology) Costs are out of control
They will and are paying billions to try and solve these problems – and failing, even with tool vendor support
This community currently claims modeling will solve these problems! Just look at what your web page says your tools will help with now!
Yet the problems continue, and continue to get worse
36 Architectural Ecosystem36
Architecture Models Are Trapped in Stovepipes
Information is unconnected, redundant and not easily usable outside its source
But, model “files” are not web assets and hard to connectStandards & Vocabularies overlap and are inconsistent
Architecture Models hold our Enterprise Architectures, business processes and services, technology models,
SOA architectures, data schema and more
37 Architectural Ecosystem37
Architectures Published into the Data Cloud
Visible and connected architectures have more value!
38 Architectural Ecosystem38
Goal: Linked Open Architectures
Federated Architectures Promote Collaboration and Shared ResourcesModels are part of an ecosystem, not islands
ServicesProcesses Data Policies
39 Architectural Ecosystem39
Architectural Ecosystem Context
Community of Stakeholders and Architects
Viewpoints
FederatedArchitectural
Knowledge Base
40 Architectural Ecosystem40
Standards and Technology
41 Architectural Ecosystem41
The Linked Open Data WorldThe Linked Open Data World
LOD as the architectural LOD as the architectural integration platformintegration platform
Architectures
42 Architectural Ecosystem42
Linked Open Data
AKA – “Semantic Web” or RDF/RDF-Schema Based on W3C RDF (Resource Description Framework) Provides an internet data model – federates data
globally Link, query, infer and repurpose information without
controlling it Getting support as the backbone for open government Inherently “Open World” and Federated A growing & vibrant community
43 Architectural Ecosystem43
ModelDriven.org Existing Baseline Prototype Enterprise Knowledge Base
Publishes any MOF (UML, BPMN, Etc) model or XML-Schema as Linked Open Data
Baseline “common concepts” for semantic integration Enterprise Knowledge Base (EKB) server
Uses RDF repository as distributed and federated model repository
Integration with existing tools (MagicDraw, Sparx) Model Transformation Model Browser (rudimentary)
ModelPro Automated MDA provisioning and transformation
44 Architectural Ecosystem44
The OMG Meta-Muddle
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 Consider using these together today:
UML-2, BPMN-2, IMM, ODM, SBVR, SoaML, SysML 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
Move to leading the solution rather than causing the problem The leaders in architecture have a lousy architecture – how embarrassing!
What the market doesn’t need: Another Stovepipe!
45 Architectural Ecosystem45
Architectural Ecosystem OMG-RFP
Create standards once the Ecosystem is “bootstrapped” and proven It is not a modeling language – it is the integration framework for
languages and a construction kit for new, federated, DSLs Existing languages represent viewpoints of an underlying model The ecosystem provides the underlying model and a way to make
projections to these language viewpoints (including diagram interchange) Semantic concepts are open, extensible and shared between language
structures Open Scope
Business, Enterprise, Systems, Implementation, Metrics, Security… As an open set of concepts that can be shared among languages, the
ultimate scope is open.
46 Architectural Ecosystem46
Conceptual Model
Architecture Ecosystem Framework
Library ofConcepts
CoreConcepts
UML-2
Class
Activity
State
Sequence
Use case
Composite Structure
Process
Services
Information
Rules
DoDAF
Projection& Mapping
More…FEA/FSAM
Motivation
Java/C#/C++
47 Architectural Ecosystem47
Desired Technical Features
Provides the basis for the Architectural Ecosystem Semantically grounded tight core – we know what things mean Projection & mapping – we can map to the viewpoints and structures people
understand Library of concepts – integrates common concepts into a growing library Extensible – allows others to build on the ecosystem Federated – multiple sources of information can be brought together All meta levels in one repository – a place for enterprise knowledge Separation of concerns (business and technical) – provides agility Modular & loosely coupled – not monolithic Provides for capabilities of “profiles” and meta models Actionable & Executable (where applicable) – brings architectures to life Collaborative – enables people, organizations and systems to work together Integrates core concepts of UML, BPMN, OWL, ISO-11179, SoaML, DoDAF
48 Architectural Ecosystem48
The Ecosystem and UML
A new architectural foundation was identified in the “Future Development of UML” process as a strategic priority
UML needs to be a part of the ecosystem and to play a major role UML should not stop while this is in progress, continue to incrementally
evolve UML The expertise and market position of UML 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 ecosystem can be “Centric” but the ecosystem should not have a dominant decomposition.
Initially UML would live in parallel to the ecosystem as a mapping, later UML may be natively based on the ecosystem models – this minimizes market impact on UML-2
Provides the basis for a future UML, BPMN, business modeling and integrated architectural suite
49 Architectural Ecosystem49
OM
G S
tand
ard
XM
I R
epre
sent
atio
n
Mapping Meta Levels & Ontologies
UML Models(I.E. CRR)
The World (Business & Technical Systems)
UML “Meta Model”
MOF “Meta Meta Model”
Uses Vocabulary
Uses Vocabulary
Models
Link
ed O
pen
RD
F R
epre
sent
atio
n
UML RDF Models(I.E. CRR)
UML “RDF Schema”
MOF “Meta RDF Schema”
Uses Vocabulary
Uses Vocabulary
Models
50 Architectural Ecosystem50
Hub Ontologies
Ontologies with well defined, modular and layered semantics provide the “glue” between existing languages and architectures
A foundation “Ontology of Architecture” federates concepts shared among existing architectural languages
Existing languages and architectures are then “grounded” in the hub ontologies, providing a “pivot point” for mutual understanding
Hubs are “projected” to viewpoints focused on the needs of stakeholders
Hub ontologies are inclusive, not exclusive – many hubs can be used together
Core concepts in the hub would be formally grounded in logic Logic can be based on OWL, Common Logic and Existing
Ontologies
51 Architectural Ecosystem51
Federating Models & Data with Hub Ontologies & Mapping (Bridge Ontologies)
The World (Business & Technical Systems)
BPMN RDF Models
BPMN “RDF Schema”
MOF “Meta RDF Schema”
Uses Vocabulary
Uses Vocabulary
Models
UMLRDF Models
UML “RDF Schema”
MOF “Meta RDF Schema”
Uses Vocabulary
Uses Vocabulary
Models
Federated ModelsFederated Data
Shared ConceptHub Ontology
Shared ConceptMeta Ontology
Uses Vocabulary
Models
Uses Vocabulary
52 Architectural Ecosystem52
Enterprise Knowledge Base
Configuration MgmtEclipseTortoise
Web-UIUser Views
FormsBrowseQuery
File Get/Put
Eclipse IDE
Sub
vers
ion
Inte
rfac
e Artifact Repository
UI Server
Model Transformation/IntegrationBPMN/UML Example
Artifact / KB Integration
XM
L “R
est”
In
terf
ace
Knowledge Base
RDF KB
Inference & Rules
Transformation
Eclipse EMF Interface* Semantic Web Interface
BPMN
ProcessModel
BPMNModel
UMLModel
UML
Shared Concepts
Subversion
53 Architectural Ecosystem53
Advantages of this approach Expands marketplace, potentially integrating:
Business modeling Process Modeling, Information Modeling, Service Modeling Enterprise Architecture Metrics Motivation & requirements Systems modeling OO modeling Ontologies MDA Others we have not thought of
Provides a foundation for a rich set of federated languages, tools and supporting capabilities
Will not destabilize current tools markets or development “waiting for UML 3” Puts in place a strategic capability we can all build on and leverage
54 Architectural Ecosystem54
Action Items
Consider your commitment to this effort Highly interested – provide letter of intent Interested – resolve questions and issues Not interested – please let us know
Requesting a one week turn-around for initial reactions
Refine business and project plan
This Presentation:http://lib.modeldriven.org/MDLibrary/trunk/Pub/Presentations/EcosystemOpenSourceProject.ppt