Upcoming SlideShare
Loading in...5

Like this? Share it with your network








Total Views
Views on SlideShare
Embed Views



0 Embeds 0

No embeds



Upload Details

Uploaded via as Microsoft PowerPoint

Usage Rights

© All Rights Reserved

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
Post Comment
Edit your comment

EKBIntro Presentation Transcript

  • 1. Enterprise Knowledge Base Integrated knowledge for and about the enterprise EKB Cory Casanave, President Model Driven Solutions Cory-c (at) ModelDriven.com July 2008
  • 2. EKB Goals
    • Management, Integration & Analysis of Enterprise Architectural, Systems, Metadata and Governance Information
      • Authored and managed by multiple authorities
      • Using different tools, models, diagrams, standards, paradigms and formats
      • Presented in user-friendly views appropriate to the role and task
      • Provisioned to tools & technologies for execution
      • Federated across the Enterprise, Government and Supply Chain
  • 3. Business Focused Architected Solutions Business Concerns Goals Policy Customers Costs Agility Technology Specification JMS, JEE, Web Services WSDL, BPEL, XML Schema Logical Systems Architecture Technology Services (t-SOA), Components, Process Execution Interfaces, Messages & Data Business Architecture Enterprise Services (e-SOA) Roles, Collaborations & Interactions Business Process & Information Refinement & Automation Line-Of-Sight Computation Independent Model Platform Independent Model Platform Specific Model MDA Terms
  • 4. Value derived from the architecture Component Acquisition Specification Technology Interfaces Test & Simulation OMB 300 FEA/FTF BRM SRM DRM TRM Business Driven Technology Facilitating Business Processes Adapters Components Data Deployment
  • 5. There is no one enterprise view!
    • What is King?
      • Information & Data
      • Services (SOA)
      • Process (BPM)
      • Finances
      • Rules
      • Goals
      • Governance
      • Systems Design
      • Organizational Structure
    Yes Every one, and more, are part of the Enterprise and Systems Architectures But none of them can stand alone A solution must integrate information, while providing the view of that information appropriate to each stakeholder
  • 6. The “Meta Muddle”
    • There are hundreds of “meta models”, tools, diagrams and exchange formats, all associated with our business architectures, solution architectures and systems implementations.
    • These are “stovepiped”, and not designed to work together.
    • Users struggle to keep different views of the same thing and related things coherent and consistent
    • The result is an error prone, expensive and ineffective process for managing our information assets and system implementations.
    • Business and systems goals and requirements are not integrated and thus not fully realized.
    • Information defined in a “foreign” format, tool or methodology is frequently lost, inconsistent or manually synchronized.
    • Each new standard or proprietary product is just another stovepipe.
    • Different contractors and technologies introduce more of the same, or proprietary ways to integrate information that attempt to lock the enterprise into a single vendor’s solution.
  • 7. EKB Approach
  • 8. Three layers of solution
    • Dynamic Configuration Management of Artifacts
      • Understand where all of your information artifacts are, where and who they came from and how they evolved over time (Based on Subversion and Provenance)
    • Structured Information & Metadata Management
      • Get all of your models, forms, requirements and other structured information into a common form that can be analyzed and federated (Based on the Shared Web)
    • Integration of Information through Shared Concepts
      • Understand how information in multiple forms, tools, standards and methodologies is related and mutually supportive (Based on Ontologies and standards from the OMG, W3C and Oasis)
  • 9. EKB High Level Architecture Enterprise Knowledge Base Configuration Mgmt Eclipse Tortoise Web-UI User Views Forms Browse Query File Get/Put Eclipse IDE Subversion Interface Artifact Repository Subversion Orbeon XForms Server Artifact / KB Integration XML “Rest” Interface Knowledge Base Sesame RDF KB Inference & Rules Transformation Eclipse EMF Adapter* Semantic Web Interface Shared Concepts Green = Existing Open Source
  • 10. Transformation Example ( BPMN/UML ) Enterprise Knowledge Base Configuration Mgmt Eclipse Tortoise Web-UI User Views Forms Browse Query File Get/Put Eclipse IDE Subversion Interface Artifact Repository Orbeon XForms Server Artifact / KB Integration XML “Rest” Interface Knowledge Base Sesame RDF KB Inference & Rules Transformation Eclipse EMF Interface* Semantic Web Interface BPMN Process Model BPMN Model UML Model UML Shared Concepts Subversion
  • 11. Enterprise Knowledge Integration Knowledge Base Process Models Information Models Services Models Rules Models Governance Models Integrated Enterprise Viewpoints Systems Architects And Developers Business Analysts And Stakeholders Software Artifacts And Execution {BPM, SOA, Rules, DBMS…}
  • 12. Shared Concept Libraries Integrate Architectures EKB OWL Concepts XML Concepts UML Concepts Shared Concept Shared Concept Shared Concept Shared Concept Shared Concept Shared Concept Shared Concept Shared Concept Shared Concept Shared Concept Shared Concept Shared Concept Shared Concept Shared Concept Shared Concept Shared Concept Shared Concept
    • Library of Concepts
    • Growing based on need
    • Modular, not monolithic
    • A construction set for languages
    • A lattice of interoperable concepts
  • 13. “ Views” of Integrated Information EKB Shared Concepts UML DoDAF BPMN Ontologies FEA Requirements EDOC XML SQL OWL E/R Models Security Projection Projection * Conceptual - Not all of these models are implemented! Provision Web Services Java/J2EE Workflow Documentation Legacy BPEL
  • 14. Managing Change & Provenance
    • Enterprise knowledge must be trusted and managed.
    • The source and authority of each fact in the knowledge base is traceable to the “speech act” of some individual at a particular time.
    Knowledge Base Data Asset Version Version Version Version Version Speech Act Speech Act Speech Act Speech Act Speech Act What is stated by a particular authority at a particular time with respect to a particular data resource A view of the data resource at a particular point in time informed by a authorized set of speech acts A managed set of information, I.E. “A process kodel” “ Head” version – is up to date
  • 15. Base Technologies & Standards
    • Eclipse with EMF (Eclipse Modeling Framework) and UML-2
    • RDF & OWL Using Sesame ( www.openrdf.org )
    • Subversion configuration management ( http://subversion.tigris.org/ )
    • Orbeon xForms ( http://www.orbeon.com/ )
    • Intalio BPMN ( http:// www.intalio.com / )
      • BPDM / BPMN-2 Support planned
    • Magicdraw UML
    • OMG - UML, MOF, XMI, EDOC, BPMN (BPDM & IMM Planned)
    • W3C “Semantic Web: - RDF, RDFS, OWL
    • Tomcat using REST
    • XML Stack (XSD, XSLT…)
  • 16. Licensing
    • The EKB is an open source project
      • https://sourceforge.net/projects/enterpisekb
      • Not announced yet
    • Licensed as “GPL”
      • Free for open source and internal use
      • Licensed for commercial use
    • Initially funded as part of a U.S. Government project of the G.S.A (osera.gov)
    • Planned as commercial open source under ModelDriven.org
  • 17. Status
    • The EKB is a prototype implementation aimed at Government requirements, but is not government specific
    • The prototype release is planned for the end of August, 2008
    • All of the functionality mentioned will demonstratable in this release, with the exception of a dynamic Eclipse-EMF API & Rule support. Model synchronization is not yet bi-directional.
    • Current model support includes: XSD, BPMN, UML (partial), EDOC & RDFS
    • Our goal is to create a pervasive and open knowledge management platform
    • Both commercial and open source tools will plug into this platform
    • Next stage is to plan and execute a production version
    • ModelDriven.org plans to develop to a commercial open source product with partners
  • 18. Opportunities
    • Enable better integration of architectural and governance information for our enterprise customers
    • Open and pervasive governance and metadata platform throughout the government and large organizations
    • Enabling communities and virtual organizations
    • SOA & BPM Governance
    • Better execution of architecture and implementation projects
    • Products and services that leverage and build on the core repository capabilities
    • Solve our own problems with multiple tools, standards and methodologies.
  • 19. EKB Demo
    • DRM (Data Reference Model) View
    • Configuration Management UI
    • SVN Integration / Artifact versions & Provenance
    • Model/Configuration management integration
    • Model Transformation (Not fully integrated yet)
  • 20. Support slides
  • 21. Integration Via Semantic Hubs Concepts We Specify Semantic Hub Reference Ontologies Shared Concepts Monetary Trade Part Of Is Mapped Dis-Integrated Information Buy Purchase Mapping is not “ one-one” Ways To Specify Things Shared Core Joint Behavior Part Of Describes Describes UML XML Describes Library of common concepts Can grow over time
  • 22. EKB Layers EKB (Enterprise Knowledge Base) Artifact Management / Configuration Management (Subversion) Asset Categorization, Provenance, Dependencies (OWL) Articles About Anything (RDF) Shared Concept Hubs (OWL Ontologies) FEA DRM BRM SRM SOA EDOC SOA-Pro Process BPMN UML Extended Knowledge Analysis Plug-ins Governance Business concepts XML Import/ Export View specific User Interface Mapping Facility Shared Metadata Concepts Asset Management Concepts Governance Ontology of Architecture Query Views Information ERD UML OWL Rules SBVR SWRL Technology Provisioning