Open Source e Government Reference Architecture Approach to

Open Source e. Government Reference Architecture Approach to Semantic Interoperability Cory Casanave, President Data Access Technologies, Inc. www. enterprisecomponent. com Copyright © 2006 Data Access Technologies, Inc.

Semantically grounded Executable Architectures • Os. Era Overview • What MDA brings – Executable Architectures providing Business Driven Interoperable Components • What the Semantic Web Brings –Interoperability between independent architectures January 2006 Copyright © 2006 Data Access Technologies, Inc. Page 2

Caveat Os. Era and the Semantic Core is work in progress, not a ready to use capability Copyright © 2006 Data Access Technologies, Inc.

Os. Era Stack Capture existing information and integrate with choice of tools Tool Integration Manage models and information from diverse sources across projects and communities Component-X System Architect Eclipse UML Architecture Modeling Objectives Information Process FEA Eclipse Environment Integrate diverse information into a coherent enterprise view EDOC UML This is planned but not the current focus Rules Model Repository FEA with real time metrics Eclipse is an open source “IDE” Provide tools for the entire integrated life cycle Semantics Core Import/Export external information and produce documentation and technical artifacts. Provisioning Transformations Import/Export Model->Integrate Runtime capabilities for deployment and integration of application components January 2006 Enterprise Service Bus BPEL Processes j. Boss Application Server Policy Web Services Semantic Web Architecture Publishing Inference Model Integration Publish and Integrate enterprise intellectual capital on the web RDF & OWL Copyright © 2006 Data Access Technologies, Inc. Page 4

Model to Integrate Using MDA and SOA from models to Solutions Copyright © 2006 Data Access Technologies, Inc.

Simulated Model Driven Architecture Enterprise Architecture Model (PIM) Business Architecture Semantic Core Meta Model January 2006 Refine/Iterate Live Process Simulation Simulator Copyright © 2006 Data Access Technologies, Inc. Page 6

Automated Model Driven Architecture Enterprise Architecture Model (CIM) Business Architecture Infrastructure Mapping (E. G. J 2 EE-WS) Tools Produce & Integrate Mapping is tuned to the infrastructure January 2006 Enterprise Components C Framework & Infrastructure (E. G. -J 2 EE-WS) PSM Copyright © 2006 Data Access Technologies, Inc. Minimize and structure manual implementation Technical Architecture Page 7

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 January 2006 Copyright © 2006 Data Access Technologies, Inc. Page 8

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. Subactivity. A specification a subfunction within necessary to carry out an activity. 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. January 2006 Copyright © 2006 Data Access Technologies, Inc. Information Flow. An individual flow of information across a protocol or into or out of an activity. Page 9

Example Work Roles Enterprise role (within the Financial Management discipline) Enterprise business service Inter-work role protocol Work Role January 2006 Copyright © 2006 Data Access Technologies, Inc. Page 10

Receivables Management Activities Related to Customer Orders Related to Receivables January 2006 Copyright © 2006 Data Access Technologies, Inc. Page 11

Information Model Example A term in the vocabulary represents a class of things to be described. Entities may be described as having a unique identity. A relation between terms is described by an association between classes. Attributes specify descriptive information having simple types. An un-shaded class is further detailed on a different diagram. This means “zero or more” A class may be specialized into sub-classifications. This indicates a compositional (as opposed to referential) association. This means “one or more” This is a constraint that defines the sub-classification. January 2006 Copyright © 2006 Data Access Technologies, Inc. Page 12

Enterprise Service Bus to Enable Target State • Services driven from the business model One-GSA Business Model • Reusable Enterprise Services are independent & easily adapted and interconnected – Services communicate with each other like humans do with email Project Management Service • 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 En te r pr ise Se rv ice s – Contracting Service January 2006 Copyright © 2006 Data Access Technologies, Inc. Solution Provider Service Funds Management Service Page 13

Platform Specific Model Platform Independent Model (PIM) Core Financial System Specification Platform Specific Model (PSM) Core Financial System Implementation Service Interfaces Web Services Enterprise Components Work Components Service Manager Components Behavioral Specifications Enterprise Information Systems System Components System Functions Data Model Message Specifications Data Manager Components Persistent Data Specifications Data Definition XML Schemas Data Base Schemas January 2006 Copyright © 2006 Data Access Technologies, Inc. Page 14

Example of XML provisioned from model Note; Don’t have to really read this! <Customer. Order. Establishment> <Inter-Work-Role. Transaction> <inter-work-role. Transaction. ID> … </Inter-Work-Role. Transaction> <new. Order> <ordering. Customer> <customer. ID> … </customer. ID> </ordering. Customer> <controlling. Sales. Instrument> <sales. Instrument. Id> … </sales. Instrument. Id> </controlling. Sales. Instrument> <customer. Order. Amount> … </customer. Order. Amount> … <line. Items> … January 2006 </line. Items> Copyright © 2006 Data Access Technologies, Inc. </new. Order> Page 15

Example Transaction Message XML Document <Customer. Order. Establishment > <customer. Order. Establishment > <new. Order> <customer. Order. ID> … </customer. Order. ID> <customer. Order. Amount> … </customer. Order. Amount> <ordering. Customer> <customer. ID> … </customer. ID> </customer> <party> <name> … </name> </party> </ordering. Customer> <controlling. Sales. Instrument > <sales. Instrument. ID> … </sales. Instrument. ID> </controlling. Sales. Instrument > … <line. Items> … </line. Items> </customer. Order> </new. Order> </customer. Order. Establishment > <business. Domain. Transaction > <transaction. ID> … </transaction. ID> </business. Domain. Transaction > </Customer. Order. Establishment > January 2006 Copyright © 2006 Data Access Technologies, Inc. Page 16

Example Web Services Definition <wsdl: port. Type name="Customer. Order. Establishment "> <wsdl: operation name="Customer. Order. Establishment "> <wsdl: input message="tns: Customer. Order. Establishment. Panoptic. Inheritance. Cluster “ name=" Customer. Order. Establishment "> </wsdl: input> The primary port type has operations corresponding </wsdl: operation> to the request flows in the protocol. </wsdl: port. Type> <wsdl: port. Type name="Customer. Order. Establishment. Callback "> <wsdl: operation name="Customer. Order. Established "> <wsdl: input message="tns: Customer. Order. Established. Panoptic. Inheritance. Cluster “ name=" Customer. Order. Established "> </wsdl: input> </wsdl: operation> <wsdl: operation name="Customer. Order. Establishment. Rejected "> <wsdl: input message="tns: Customer. Order. Establishment. Rejected. Inheritance “ name=" Customer. Order. Establishment. Rejected "> </wsdl: input> The callback port type has operations corresponding </wsdl: operation> to the response flows in the protocol. </wsdl: port. Type> January 2006 Copyright © 2006 Data Access Technologies, Inc. Page 17

What MDA Provides • Business-centric Enterprise Models of Collaborative Processes, Information and Rules • That are refined to produce SOA based component specifications – independent of middleware and implementation technologies • Enabling model-based acquisition, FEA support, simulation and execution • Facilitating Automated Development of Services and Implementations • Providing for interoperable components that integrate new and legacy capabilities • MDA provides an Architected Solution to interoperability January 2006 Copyright © 2006 Data Access Technologies, Inc. Page 18

Copyright © 2006 Data Access Technologies, Inc.

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 • Providing for the integration of independently developed architectures – Or the integration of intellectual capital January 2006 Copyright © 2006 Data Access Technologies, Inc. Page 20

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. January 2006 Copyright © 2006 Data Access Technologies, Inc. Page 21

The Basics • Problems to be solved – – – • Interoperability of organizations and technology Collaboration Architected business information and processes Agile solutions based on the architectures Fully integrated life-cycle approach supporting the FEA 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 January 2006 Copyright © 2006 Data Access Technologies, Inc. Page 22

“Meta” Integration Problem Too many ways to talk about the same thing, redundant and conflicting semantics. Language UML Class Diagram Language Activity Diagram Language WSDL Architectural Environment Class Diagram System Business or Technical Activites Web Service Specification Ontology Requirements Key Uses Defines Language OWL Language Excel Security Specification Language SAML Database Schema Language ER SOA Collaboration Language EDOC EJB Ear Specification Language EJB Descriptor Artifact January 2006 Copyright © 2006 Data Access Technologies, Inc. Page 23

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 January 2006 Copyright © 2006 Data Access Technologies, Inc. Page 24

Adapting Systems with Os. Era UML Described in XML Semantic Core Described in Purchasing System Commerce Ontology J 2 EE Invoicing System Microsoft. NET Provision Adapter January 2006 Copyright © 2006 Data Access Technologies, Inc. Page 25

Integration Via Semantic Hubs Dis-Integrated Information XML Monetary Trade Purchase Semantic Hub Part Of Semantic Core Part Of Reference Ontologies Describes Buy Mapping is not “one-one” January 2006 Joint Behavior Describes Concepts We Specify UML Common Concepts Describes Ways To Specify Things Is Mapped Library of common concepts Can grow over time Copyright © 2006 Data Access Technologies, Inc. Page 26

“Views” of Integrated Information Ontologies UML Do. DAF FEA Os. Era Requirements BPMN Semantic Core EDOC OWL XML SQL Provision E/R Models January 2006 Security Web Services Documentation Workflow Components Java/J 2 EE BPEL Copyright © 2006 Data Access Technologies, Inc. Page 27

Semantic Components Semantic Core UML Concepts OWL Concepts Semantic Component Semantic Component Semantic Component Semantic Component • Library of component concepts Semantic Component • Growing based on need Semantic Component XML Concepts • Modular, not monolithic • A construction set for languages • A lattice of interoperable concepts January 2006 Copyright © 2006 Data Access Technologies, Inc. Page 28

Interoperability of Systems System A System B System C Shared Context System D Hub Context System of Systems January 2006 Copyright © 2006 Data Access Technologies, Inc. Page 29

Unifying Intellectual Capital Business Process (BPMN) System Architecture (UML) XML Vocabulary Os. Era Process Model Component Model Order PO Document Model OR_ST_05 Human/Automated Integration Order Concept Reference Ontology Unified Architecture Order January 2006 Copyright © 2006 Data Access Technologies, Inc. Page 30

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” January 2006 Copyright © 2006 Data Access Technologies, Inc. Page 31

Example Workflow January 2006 Copyright © 2006 Data Access Technologies, Inc. Page 32

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 January 2006 Copyright © 2006 Data Access Technologies, Inc. Page 33

Summary • Semantic integration and interoperability requires – – – A Business driven approach Intellectual capital contained in semantically grounded models Provisioning to technology infrastructures Tooling and automation Standards – An approach for executing architected solutions – MDA – An approach to integrate architectures – Semantically Grounded Architectures & Semantic Core January 2006 Copyright © 2006 Data Access Technologies, Inc. Page 34

Resources • Os. Era – www. osera. modeldriven. org – www. osera. gov • Data Access Technologies, Inc – www. enterprisecomponent. com • Cory Casanave – Cory-c (at) enterprisecomponent. com • OMG Model Driven Architecture – www. omg. org/mda January 2006 Copyright © 2006 Data Access Technologies, Inc. Page 35