Upload
zubin67
View
606
Download
0
Tags:
Embed Size (px)
DESCRIPTION
Citation preview
Copyright © 2006Data Access Technologies, Inc.
Slide 1
Open Source eGovernment Reference Architecture
Cory Casanave, PresidentData Access Technologies, Inc.www.enterprisecomponent.com
osera.modeldriven.org
Copyright © 2006Data Access Technologies, Inc.
Slide 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
Copyright © 2006Data Access Technologies, Inc.
Slide 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.
Copyright © 2006Data Access Technologies, Inc.
Slide 4
Caveat
OsEra and the Semantic Core is work in progress, not a ready to
use capability
Copyright © 2006Data Access Technologies, Inc.
Slide 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
Copyright © 2006Data Access Technologies, Inc.
Slide 6
“Meta” Integration Problem
ArchitecturalEnvironment
SystemBusiness orTechnical
LanguageUML Class
Diagram
LanguageActivityDiagram
LanguageSAML
LanguageEDOC
LanguageER
LanguageWSDL
LanguageExcel
LanguageEJB Descriptor
ClassDiagram
LanguageOWL
Activites
Web ServiceSpecification
Ontology
SecuritySpecification
DatabaseSchema
EJB EarSpecification
SOACollaboration
Requirements
Key
Uses
Defines
Artifact
Too many ways to talk about the same thing, redundant and conflicting semantics.
Copyright © 2006Data Access Technologies, Inc.
Slide 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
Copyright © 2006Data Access Technologies, Inc.
Slide 8
Adapting Systems with OsEra
OsEra
Semantic Core
UML XML
Provision
Adapter
PurchasingSystem
InvoicingSystemCommerce
Ontology
Described in Described in
J2EE Microsoft .NET
Described in
Copyright © 2006Data Access Technologies, Inc.
Slide 9
Integration Via Semantic Hubs
ConceptsWeSpecify
SemanticHub
ReferenceOntologies
CommonConcepts
MonetaryTrade
Part Of
IsMapped
Dis-IntegratedInformation
Buy
Purchase
WaysTo SpecifyThings
SemanticCore
JointBehavior Part Of
De
scribe
s
De
scribe
s
UML
XML
De
scribe
s
Library of common conceptsCan grow over time
Mappingis not
“one-one”
Copyright © 2006Data Access Technologies, Inc.
Slide 10
“Views” of Integrated Information
OsEra
Semantic Core
UML
DoDAF
BPMN
Ontologies
FEA
Requirements
EDOC XML
SQLOWLProvision
Web Services
Java/J2EE
WorkflowDocumentation
Components BPEL
E/R Models Security
Copyright © 2006Data Access Technologies, Inc.
Slide 11
Semantic Core
OWL Concepts
XML Concepts
UML Concepts
Semantic Components
SemanticComponent
SemanticComponent
SemanticComponentSemantic
ComponentSemanticComponent
SemanticComponent
SemanticComponent
SemanticComponent
SemanticComponentSemantic
Component
SemanticComponent
SemanticComponentSemantic
ComponentSemanticComponent
SemanticComponentSemantic
Component
SemanticComponent
•Library of component concepts
•Growing based on need
•Modular, not monolithic
•A construction set for languages
•A lattice of interoperable concepts
Copyright © 2006Data Access Technologies, Inc.
Slide 12
System A
Interoperability of Systems
SharedContext
System B
System C
System D
SharedContext
HubContext
System of Systems
Copyright © 2006Data Access Technologies, Inc.
Slide 13
Importing Information
ExternalArtifacts
OsEra
Imported SourceModel
Provision
UnifiedModel
Provision
Semantic CoreMeta OntologyE.G.
Business ProcessUML
DoDAF
Copyright © 2006Data Access Technologies, Inc.
Slide 14
Getting Value Out
ExternalArtifacts
OsEra
High Level(Business) Model
Provision
Provision
Technology Model
Derivative Systems Model
Semantic CoreMeta Ontology
E.G.SOA orDoDAF
E.G.Web Services
E.G.Business Process
Copyright © 2006Data Access Technologies, Inc.
Slide 15
Unifying Intellectual CapitalBusinessProcess(BPMN)
SystemArchitecture
(UML)
XMLVocabulary
OsEra
ProcessModel
ComponentModel
DocumentModel
Order OR_ST_05PO
Reference OntologyOrder Concept Unified
Architecture
Order
Human/AutomatedIntegration
Copyright © 2006Data Access Technologies, Inc.
Slide 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”
Copyright © 2006Data Access Technologies, Inc.
Slide 17
Example Workflow
Use tools tocompare/adapt grounded specs
Import new or Legacy Specand instances
Make New ConceptRelate to existing Concepts
For each term, Relateto reference Ontologies
Validate with Instances Make new termfor existing Concept
Generate AdapterImplementations
Extend/CorrectAdaptationCorrect?
GroundingComplete
Term Exists
Concept Exists
no
Yes
Yes
yes
no
Copyright © 2006Data Access Technologies, Inc.
Slide 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
Copyright © 2006Data Access Technologies, Inc.
Slide 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
Copyright © 2006Data Access Technologies, Inc.
Slide 20
OsEra Stack
Enterprise Service BusjBoss
ApplicationServer
jBossApplication
Server
BPELProcesses
BPELProcesses
PolicyPolicyWeb
ServicesWeb
Services
Semantic WebArchitecturePublishing
ArchitecturePublishing
Provisioning
Model Repository
Tool Integration
SemanticsCore
SemanticsCore
TransformationsTransformations
Model->IntegrateModel->Integrate
UMLUML
EDOCEDOC
Component-XComponent-X
UMLUML
SystemArchitectSystem
Architect
FEAFEA
InferenceInference
Import/ExportImport/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
ProcessProcess
InformationInformation
RulesRules
ObjectivesObjectives
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 & OWLRDF & OWL
ModelIntegrationModel
Integration
EclipseEclipse
EclipseEnvironment
Eclipse is an open source
“IDE”
Copyright © 2006Data Access Technologies, Inc.
Slide 21
Model to Integrate
Using MDA and SOA
from models
to Solutions
Copyright © 2006Data Access Technologies, Inc.
Slide 22
BusinessArchitecture
SimulatedModel Driven Architecture
SimulatorSimulator
EnterpriseEnterpriseArchitecture Architecture
ModelModel(PIM)(PIM)
Live Process Simulation
Refine/Iterate
Semantic CoreMeta Model
Copyright © 2006Data Access Technologies, Inc.
Slide 23
BusinessArchitecture
AutomatedModel Driven Architecture
Framework &Framework &InfrastructureInfrastructure
(E.G. -J2EE-WS)(E.G. -J2EE-WS)PSMPSM
InfrastructureInfrastructureMappingMapping
(E.G. J2EE-WS)(E.G. J2EE-WS)
Mapping is tunedMapping is tunedto the infrastructureto the infrastructure
ToolsToolsProduce &Produce &IntegrateIntegrate
EnterpriseEnterpriseComponentsComponents
Enterprise Enterprise Architecture Architecture Model (CIM)Model (CIM)
Minimize and structuremanual implementation
C
TechnicalArchitecture
Copyright © 2006Data Access Technologies, Inc.
Slide 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
Copyright © 2006Data Access Technologies, Inc.
Slide 25
Collaborative Process ModelEnterprise Role. A major area of functional responsibility within the discipline of financial management.
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.
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.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.
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.
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.Subactivity. A specification a subfunction within necessary to carry out an activity.
Copyright © 2006Data Access Technologies, Inc.
Slide 26
Receivables Management ActivitiesRelated to Customer Orders
Related to Receivables
Copyright © 2006Data Access Technologies, Inc.
Slide 27
Information Model ExampleA term in the vocabulary represents a class of things to be described.
A term in the vocabulary represents a class of things to be described.
Attributes specify descriptive information having simple types.
Attributes specify descriptive information having simple types.
Entities may be described as having a unique identity.
Entities may be described as having a unique identity.
A relation between terms is described by an association between classes.
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.
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.
Copyright © 2006Data Access Technologies, Inc.
Slide 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
FundsManagementService
Contracting Service
Solution ProviderService
ProjectManagementService
Enter
prise
Ser
vices
Copyright © 2006Data Access Technologies, Inc.
Slide 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!
Copyright © 2006Data Access Technologies, Inc.
Slide 30
Copyright © 2006Data Access Technologies, Inc.
Slide 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
Copyright © 2006Data Access Technologies, Inc.
Slide 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…
Copyright © 2006Data Access Technologies, Inc.
Slide 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”?
Copyright © 2006Data Access Technologies, Inc.
Slide 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