Open Source egovernment Reference Architecture Cory Casanave, President www.enterprisecomponent.com Slide 1 What we will cover OsEra OsEra Overview Model to Integrate From business model to execution Synthesis of MDA, Semantic Web and FEA Slide 2, 1
Capture existing information and integrate with choice of tools Manage models and information from diverse sources across projects and communities FEA with real time metrics Tool Integration System Component-X Architect Eclipse OsEra Stack UML Model Repository FEA EDOC Semantics UML Core Architecture Modeling Objectives Process Information Rules Provide tools for the entire integrated life cycle This is planned but not the current focus Integrate diverse information into a coherent enterprise view Eclipse is an open source IDE Runtime capabilities for deployment and integration of application components Eclipse Environment Service Bus BPEL jboss Processes Application Server Policy Web Services Provisioning Transformations Import/Export Model->Integrate Semantic Web Architecture Publishing Inference Model Integration RDF & OWL Import/Export external information and produce documentation and technical artifacts. Publish and Integrate enterprise intellectual capital on the web Slide 3 GSA Sea Change Sea of change Get-it-right (Initiative for better acquisition) Merger of FTS/FSS (Major Internal Organizations) Restructuring to provide a unified face to the customer OMB and Congressional mandates and changes of mission Integrating and modernizing financial management Reduction of redundant processes and systems Implications Massive organizational change Massive system changes Retraining staff High cost of change Risky and hard to achieve Change combined with current costs and inefficiencies of redundant stovepipe systems is not practical Business As Usual is insufficient Slide 4, 2
Sea Change Enablers & Cost Reduction Value Chain Analysis Analyzing and restructuring business processes based on realized customer value Model Driven Executable Architecture Executable enterprise architecture to realize business goals with systems and workflow automation Business Service Oriented Architecture (SOA) An enterprise modernization strategy supporting business services, integration, reuse and common components across a system of systems integrated with SOA/ESB Service Bus (ESB) A technology platform to support the deployment and integration of SOA components. Semantic web with semantic core integration ontology Make architectures a web resource able to be interconnected and analyzed Integrate information into a coherent enterprise view Combined effect of architected, automated processes Slide 5 Standards Base OMG-MDA Specifications Distributed Object Computing (EDOC) Unified Modeling Language (UML) Meta Object Facility (MOF) XML Model Interchange (XMI) Query View Transform (QVT) Ontology Definition Metamodel (ODM) W3C Standards XML, XML Schema, Web Services Business Process Execution Language (BPEL) Ws-Security, Ws-Policy Resource Definition Framework (RDF) Web Ontology Language (OWL) Java Community J2EE set of standards Slide 6, 3
Simulated Model Driven Architecture Architecture Model (PIM) Business Architecture Refine/Iterate Live Process Simulation Semantic Core Meta Model Simulator Slide 7 Automated Model Driven Architecture Architecture Model (CIM) Infrastructure Mapping (E.G. J2EE-WS) Business Architecture Mapping is tuned to the infrastructure Tools Produce & Integrate Components C Framework & Infrastructure (E.G. -J2EE-WS) PSM Minimize and structure manual implementation Technical Architecture Slide 8, 4
Develop Provide Plan and Design and Deliver After Care Mission-Critical Value Chain MDA in the U.S. Government Model to Integrate From business needs to executing solutions Slide 9 egoverment MDA Process Computation Independent Model (CIM) Stakeholders Business Drivers As-Is Business Processes Business Context Value Chains Roles and Information Model Collaboration Platform Independent Model (PIM) Business Case As-Is Systems Service-Oriented Architecture Data Model Sequencing Plan EA Report Platform Specific Model (PSM) Open Source egov Reference Architecture <wsdl:porttype> </wsdl:porttype > Web Services Components Program Management and Risk Assessment/Mitigation Change Management, Configuration Management, and Communications Slide 10, 5
Value Chains Plan and Design Develop and Deliver Provide After Care Mission-Critical Value Chain Development of Government-wide Policy Marketing Acquisition Support Services Value Chains Financial Management Services I.T. Services Human Capital Services Shared Services Value Chains Slide 11 Disciplines Areas of Responsibility Financial Management Acquisition Solutions Property Management Policy Business Intelligence Human Resources Marketing Slide 12, 6
Collaborative Process Model 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. Information Flow. An individual flow of information across a protocol or into or out of an activity. Slide 13 Receivables Management Example Related to Customer Orders Related to Receivables Slide 14, 7
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. This means zero or more An un-shaded class is further detailed on a different diagram. 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. Slide 15 Business (CIM) view -Collaborating Roles with Processes Role Role Role Role Conversation Protocol Slide 16, 8
Upper PIM (system) View - Component Rotate to look At other aspects of the component Role Role Component People, organizations And/or enterprise components play roles in Business Processes. Slide 17 The Digital Assistant People, Organizations And systems play roles Components frequently help people play these roles People, organizations and systems components work together to realize roles Components are the peoples Automated assistant Role Role Component Business Process components help people and organizations play roles by automating and monitoring The business process From the system perspective. People and organizations become part of the implementation Of the role Slide 18, 9
People, Components & Organizations Collaborating Role Component Role Component Role Component Slide 19 Lower PIM View - Component Internals UI Client Tier Browser Component UI Server Tier Business Logic UI Framework Component [Web] Service DBMS Component Adaptation Data Managers [Web] Service Legacy Systems Containers Slide 20, 10
PIM: Service-Oriented Component Architecture Each Work Component in the PIM implements a Work Role from the CIM. Presentation Tier Application Tier Data Tier Service Managers implement as system services the business services defined in the CIM. Slide 21 Information Model Note; Not expecting anyone To really read this Business Transaction Business Entity Slide 22, 11
Note; Not expecting anyone To really read this Messaging Message Namesake Slide 23 Persistence Model Association indicates a reference to an entity persisted elsewhere. Slide 24, 12
Service Bus to Enable Target State Services driven from the business model Reusable 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/ Service Bus using commercial standards Industry best practice to avoid developing large monolithic applications Services Project Management Service One-GSA Business Model Solution Provider Service Contracting Service Funds Management Service Slide 25 Provisioning Model Slide 26, 13
Example of XML provisioned from model Note; Don t have to really read this either! <CustomerOrderEstablishment> <Inter-Work-RoleTransaction> <inter-work-roletransactionid> </inter-work </Inter-Work-RoleTransaction> <neworder> <orderingcustomer> <customerid> </customerid> </orderingcustomer> <controllingsalesinstrument> <salesinstrumentid> </salesinstrumentid </controllingsalesinstrument> <customerorderamount> </customerorderamoun <lineitems> </lineitems> </neworder> </CustomerOrderEstablishment> Slide 27 Service Bus * Complements of jboss Slide 28, 14
Many BPEL Processes support the CIM Slide 29 Slide 30, 15
Common Environment for Intellectual Capital Meta Object Facility Meta Models Value Chain Modeling UML Modeling Workflow Tools Business Modeling Collaboration Modeling MOF MDA Environment Models define the system Intellectual Capital Apl 1 CICS EJB.NET Cust Sys Integration of infrastructure Slide 31 Net Effect of MDA Clear path from needs to running technology Integrate business driven solutions with capital planning & the FEA Interoperable component architecture based on SOA Integrate legacy, COTS, GOTS and new development into a coherent solution Strategic evolution Reduced time, costs & risk Slide 32, 16
Integration of the Semantic Web with MDA And now a word from another community! Slide 33 Users meta integration problem Too many ways to talk about the same thing, redundant and conflicting semantics. Language UML Class Diagram Class Diagram System Definition Environment Security Specification Language SAML Language Activity Diagram Activites System Business or Technical Database Schema Language ER Language WSDL Web Service Specification Java classes Language Java Key Ontology Requirements EJB Ear Specification Uses Defines Artifact Language OWL Language Excel Language EJB Descriptor Slide 34, 17
MDA Modeling Needs Ontologies The semantic web infrastructure provides a great way to Publish models as web resources Query over models Analyze models and the intersection of multiple models Semantically ground models RDF/Ontology based models are more resilient to change without refactoring Ontologies are better able to connect models that were not designed together integrating and adapting architectures, processes, interfaces and information The open, distributed and federated meta object facility has yet to emerge as readily available and mainstream Semantic web infrastructure is picking up industry steam, tools and infrastructure are coming available Slide 35 Ontologies Need MDA Modeling A vast amount of information exists in these environments. Use of these paradigms represents mainstream best practice there are lots of practitioners The structured modeling tools are more mature and suited to specific problems. Model Driven Architecture has started to bind structured models with the software development process, providing even more leverage Doesn t require changing the runtime infrastructure as some Semantic Web Approaches are suggesting separation of technology concerns Ontologies can t ignore this wealth of knowledge, tools, expertise and industry momentum. Slide 36, 18
The Big Win Architectures developed using structured modeling tend to be islands Can we bring these together into a coherent view of the problem domain E.G. a true multi-view enterprise model? Can we embrace multiple structured modeling languages as well as integrate Ontologies? Can we use the semantic web stack to support integration of enterprises and their technology islands? Can we, ultimately, solve the interoperability and reuse problems? Slide 37 Example Slide 38, 19
Metadata Technology Layers Modeling/SW Layer Eclipse UI UML, Business Models, Schema, Java, Software MOF/ RDF Mapping Eclipse-EMF EMF Adapter Eclipse Code Generators SW Eng Tools RDF Metadata Infrastructure API Web Server Query Inference & Rules RDF/OWL Ontology Store Ontology Tools Metadata DBMS Ontology Layer Slide 39 OsEra Parts Eclipse UI Framework CVS XMI Merge Semantics Web Key Model Of Mapping Interaction DOORS Requirements View Tools Biz Req OWL/ODM Provisioning/QVT Provisioning Model Provisioning & QVT EMF & Semantic Web Repository & Supporting Framework Org Structure Vocabulary Ontology of Semantic Core Ontology of Domain BPEL FEA Domain Model Activities Sync Sync Sync Sync Sync Application Org Chart Organization View Tools SQL SQL PSM TopScape SKOS? Vocabulary View Tools BPEL PSM FEA View Tools EJB CX Semantic Core WSDL Eclipse Technology Plugins EJB PSM Activities View Tools WSDL PSM UML-2 Java-- EDOC/CX HTML Web UI DBMS jboss BPEL Pub/Sub SOAP Monitoring Slide 40 Sync Java-- PSM SOIP/ESB/SOA Deployment Package SOIP/ESB/SOA Runtime Framework Collaboration Components View Tools POPKIN Domain Repository HTMLPSM PSM Data/ Information View Tools Data Sync Abstract Syntax Domain Architecture Views Abstract Syntax Abstract Semantics Technology Views Meta Repository, 20
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 Slide 41 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 Opportunity for others to participate How can we make this a government-wide happening? Slide 42, 21