Your SlideShare is downloading. ×
SemanitcCoreOsEra.ppt
SemanitcCoreOsEra.ppt
SemanitcCoreOsEra.ppt
SemanitcCoreOsEra.ppt
SemanitcCoreOsEra.ppt
SemanitcCoreOsEra.ppt
SemanitcCoreOsEra.ppt
SemanitcCoreOsEra.ppt
SemanitcCoreOsEra.ppt
SemanitcCoreOsEra.ppt
SemanitcCoreOsEra.ppt
SemanitcCoreOsEra.ppt
SemanitcCoreOsEra.ppt
SemanitcCoreOsEra.ppt
SemanitcCoreOsEra.ppt
SemanitcCoreOsEra.ppt
SemanitcCoreOsEra.ppt
SemanitcCoreOsEra.ppt
SemanitcCoreOsEra.ppt
SemanitcCoreOsEra.ppt
SemanitcCoreOsEra.ppt
SemanitcCoreOsEra.ppt
SemanitcCoreOsEra.ppt
SemanitcCoreOsEra.ppt
SemanitcCoreOsEra.ppt
SemanitcCoreOsEra.ppt
SemanitcCoreOsEra.ppt
SemanitcCoreOsEra.ppt
SemanitcCoreOsEra.ppt
SemanitcCoreOsEra.ppt
SemanitcCoreOsEra.ppt
SemanitcCoreOsEra.ppt
SemanitcCoreOsEra.ppt
SemanitcCoreOsEra.ppt
Upcoming SlideShare
Loading in...5
×

Thanks for flagging this SlideShare!

Oops! An error has occurred.

×
Saving this for later? Get the SlideShare app to save on your phone or tablet. Read anywhere, anytime – even offline.
Text the download link to your phone
Standard text messaging rates apply

SemanitcCoreOsEra.ppt

614

Published on

0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total Views
614
On Slideshare
0
From Embeds
0
Number of Embeds
0
Actions
Shares
0
Downloads
7
Comments
0
Likes
0
Embeds 0
No embeds

Report content
Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
No notes for slide
  • Cory
  • Tom or Cory
  • Transcript

    • 1. Open Source eGovernment Reference Architecture Semantic Core Cory Casanave, President Data Access Technologies, Inc. www.enterprisecomponent.com osera.modeldriven.org
    • 2. What is the Semantic Core?
      • The semantic core integrates the concepts of architecture as expressed in multiple languages such as UML, OWL, FEA, BPM, EDOC, XML, Requirements, Etc.
      • This provides for a unification of the intellectual capital used to specify
        • Organizations
        • Systems
        • Information
        • Interfaces
        • Processes
        • … Anything we architect
      • Making the organizations, processes and systems more agile and interoperable
    • 3. Driver: Interoperability
      • Interoperability of information and interfaces is a primary driver today. The cost and agility advantages are established, the issues known. We must enable a solution to these problems.
      • Semantic core provides a missing link for enabling interoperability, this is our driving requirement.
        • Adaptation of similar information and interfaces across organizations, processes, and systems.
      • Semantic Core combined with the capabilities of service oriented and model driven architectures provides a capability for wide scale, net centric interoperability.
    • 4. Caveat OsEra and the Semantic Core is work in progress, not a ready to use capability
    • 5. The Basics
      • Problems to be solved
        • Interoperability of organizations and technology
        • Collaboration
        • Architected business information and processes
        • Agile solutions based on the architectures
      • The Approach
        • Architecture models grounded in an open and extensible semantic framework
        • Model Driven Architecture to generate technology components
        • Service Oriented Architecture as the infrastructure
    • 6. “ Meta” Integration Problem Architectural Environment System Business or Technical Language UML Class Diagram Language Activity Diagram Language SAML Language EDOC Language ER Language WSDL Language Excel Language EJB Descriptor Class Diagram Language OWL Activites Web Service Specification Ontology Security Specification Database Schema EJB Ear Specification SOA Collaboration Requirements Too many ways to talk about the same thing, redundant and conflicting semantics. Key Uses Defines Artifact
    • 7. How this Effects Government
      • Contractors, using different and incompatible tools
      • Generate different architectures about the same things
      • That then need to be aligned – but are never maintained
      • Each project becomes an island, without reuse or interoperability
      • The resultant complexity is expensive, and anti-agile
    • 8. Adapting Systems with OsEra OsEra Semantic Core UML XML Provision Adapter Purchasing System Invoicing System Commerce Ontology Described in Described in J2EE Microsoft .NET Described in
    • 9. Integration Via Semantic Hubs Concepts We Specify Semantic Hub Reference Ontologies Common Concepts Monetary Trade Part Of Is Mapped Dis-Integrated Information Buy Purchase Mapping is not “ one-one” Ways To Specify Things Semantic Core Joint Behavior Part Of Describes Describes UML XML Describes Library of common concepts Can grow over time
    • 10. “ Views” of Integrated Information OsEra Semantic Core UML DoDAF BPMN Ontologies FEA Requirements EDOC XML SQL OWL E/R Models Security Provision Web Services Java/J2EE Workflow Documentation Components BPEL
    • 11. Semantic Components Semantic Core OWL Concepts XML Concepts UML Concepts Semantic Component Semantic Component Semantic Component Semantic Component Semantic Component Semantic Component Semantic Component Semantic Component Semantic Component Semantic Component Semantic Component Semantic Component Semantic Component Semantic Component Semantic Component Semantic Component Semantic Component
      • Library of component concepts
      • Growing based on need
      • Modular, not monolithic
      • A construction set for languages
      • A lattice of interoperable concepts
    • 12. Interoperability of Systems System A Shared Context System B System of Systems System C System D Shared Context Hub Context
    • 13. Importing Information External Artifacts OsEra Imported Source Model Provision Unified Model Provision Semantic Core Meta Ontology E.G. Business Process UML DoDAF
    • 14. Getting Value Out External Artifacts OsEra High Level (Business) Model Provision Provision Technology Model Derivative Systems Model Semantic Core Meta Ontology E.G. SOA or DoDAF E.G. Web Services E.G. Business Process
    • 15. Unifying Intellectual Capital Business Process (BPMN) System Architecture (UML) XML Vocabulary OsEra Process Model Component Model Document Model Order OR_ST_05 PO Reference Ontology Order Concept Unified Architecture Order Human/Automated Integration
    • 16. Ontological Grounding
      • Grounding our common concepts in Ontologies has multiple advantages
        • We can add “axioms” that help to more concretely define the concepts
        • Ontology tools can use this information to bridge like terms for the same concept or similar concepts
        • Other ontology aware components can assist architects in “grounding” their models
        • Adaptation components can help build “adapters” between different interfaces and information stores
        • Inconsistencies can be identified and resolve early
        • As ontologies advance, additional capabilities can be added
        • We can connect Ontological “hubs” – not requiring “one true solution”
    • 17. Example Workflow
    • 18. Some Semantic Core Concepts
      • Concepts, Symbols & Types
      • Roles and relations define logical connections between concepts
      • Context
      • Assertions about things and types of things
      • Process & activities
      • Purpose and objectives
      • Constraints & conditions
    • 19. Joining the “Stacks”
      • Modeling & Architecture “Stack”
        • UML
        • Model Driven Architecture
        • Meta Object Facility
        • Business Process
      • Semantic Web & Ontology “Stack”
        • RDF
        • OWL
      • Current Project – MOF to RDF
        • Makes ANY MOF compliant model (UML, EDOC, E/R, Etc) an OWL Ontology
        • Provides foundation for grounding models
        • Reduces the gaps between the camps
        • Allows models to be published as semantic web ontology resources
    • 20. OsEra Stack Enterprise Service Bus jBoss Application Server BPEL Processes Policy Web Services Semantic Web Architecture Publishing Provisioning Model Repository Tool Integration Semantics Core Transformations Model->Integrate UML EDOC Component-X UML System Architect FEA Inference Import/Export Runtime capabilities for deployment and integration of application components Import/Export external information and produce documentation and technical artifacts. Publish and Integrate enterprise intellectual capital on the web Manage models and information from diverse sources across projects and communities Architecture Modeling Process Information Rules Objectives Capture existing information and integrate with choice of tools Provide tools for the entire integrated life cycle Integrate diverse information into a coherent enterprise view FEA with real time metrics This is planned but not the current focus RDF & OWL Model Integration Eclipse Eclipse Environment Eclipse is an open source “IDE”
    • 21. Model to Integrate Using MDA and SOA from models to Solutions
    • 22. Simulated Model Driven Architecture Business Architecture Simulator Semantic Core Meta Model Enterprise Architecture Model (PIM) Live Process Simulation Refine/Iterate
    • 23. Automated Model Driven Architecture Business Architecture Framework & Infrastructure (E.G. -J2EE-WS) PSM Infrastructure Mapping (E.G. J2EE-WS) Mapping is tuned to the infrastructure Tools Produce & Integrate Enterprise Components Manual Coding Minimize and structure manual implementation C Technical Architecture Enterprise Architecture Model (CIM)
    • 24. SOA Architecture Modeling
      • Standards Based
        • OMG “Enterprise Collaboration Architecture”
          • http://www.omg.org/technology/documents/formal/edoc.htm
      • Models Collaborative Business Processes
      • Link between business and SOA
      • “ Drills down” to SOA interfaces
      • Provides the context for services
      • Populates part of the semantic core
    • 25. Collaborative Process Model Enterprise Role. A major area of functional responsibility within the discipline of financial management. Work Role. A role responsible for a specific functional area within an enterprise role, such as might be assigned to a single worker or supported by an IT system. Activity. A specification of a business function in carried out the context of a work role. Protocol. A defined conversation between two roles that may be extended over time. One role initiates and the other responds to the protocol, but information may flow both ways across the protocol. Information Flow. An individual flow of information across a protocol or into or out of an activity. Subactivity. A specification a subfunction within necessary to carry out an activity.
    • 26. Receivables Management Activities Related to Customer Orders Related to Receivables
    • 27. Information Model Example A term in the vocabulary represents a class of things to be described. Attributes specify descriptive information having simple types. Entities may be described as having a unique identity . A relation between terms is described by an association between classes. This means “zero or more” This means “one or more” This indicates a compositional (as opposed to referential) association. A class may be specialized into sub-classifications. This is a constraint that defines the sub-classification. An un-shaded class is further detailed on a different diagram.
    • 28. Enterprise Service Bus to Enable Target State
      • Services driven from the business model
      • Reusable Enterprise Services are independent & easily adapted and interconnected
        • Services communicate with each other like humans do with email
      • Information systems become a lattice of cooperating components providing services
      • SOA/Enterprise Service Bus using commercial standards
        • Industry best practice to avoid developing large monolithic applications
      One-GSA Business Model Funds Management Service Contracting Service Solution Provider Service Project Management Service Enterprise Services
    • 29. Example of XML provisioned from model
      • <CustomerOrderEstablishment>
      • <Inter-Work-RoleTransaction>
      • <inter-work-roleTransactionID> … </inter-work-roleTransactionID>
      • </Inter-Work-RoleTransaction>
      • <newOrder>
      • <orderingCustomer>
      • <customerID> … </customerID>
      • </orderingCustomer>
      • <controllingSalesInstrument>
      • <salesInstrumentId> … </salesInstrumentId>
      • </controllingSalesInstrument>
      • <customerOrderAmount> … </customerOrderAmount>
      • <lineItems>
      • </lineItems>
      • </newOrder>
      • </CustomerOrderEstablishment>
      Note; Don’t have to really read this!
    • 30.  
    • 31. The “Big Win”
      • Architectures developed using structured modeling tend to be islands
        • Bring these together into a coherent view of the problem domain – E.G. a true multi-view enterprise model
        • Embrace multiple structured modeling languages as well as integrate Ontologies
        • Use the semantic web stack to support integration of enterprises and their technology islands
        • Use MDA to make models executable
        • Ultimately, solve the interoperability and reuse problems
    • 32. Open Source Components
      • OsEra is building on and helping to create open source assets for use by the government
      • Integrating
        • Eclipse Integrated Development Environment
          • Tool framework - Eclipse
          • Repository – “EMF” Modeling framework
        • jBoss Application Server
          • Web services
          • BPEL Process Engine
        • J2EE Reference Edition, Web Services Toolkit
        • More…
    • 33. OsEra Opportunity
      • Open Source Initiative, this is work in progress!
      • Model to integrate platform
      • Business driven I.T.
      • Embraces current trends, EDOC, UML, MDA and Semantic Web
      • Applicable to any government agency
      • Helps achieve an architected enterprise
      • Substantial reduction in software Lifecycle cost
      • Reduce costs with increased effectiveness
      • Pilot already under way
      • We are looking for other sponsors for this work
      • How can we make this a government-wide “happening”?
    • 34. Resources
      • GSA OsEra Pages – www.osera.gov
      • DAT Osera Pages – osera.modeldriven.org
      • MDA – www.omg.org/mda
      • RDF Metadata Infrastructure - http://osera.modeldriven.org/documents/OsEraMetadata.pdf
      • Information & Interface Adaptation - http://osera.modeldriven.org/documents/InterfaceAdaptation.pdf
      • SOA - http://osera.modeldriven.org/industry/serviceoriented_architecture.htm
      • Email; cory-c (at)
      • Data Access Technolgies,: enterprisecomponent.com

    ×