PPT
Upcoming SlideShare
Loading in...5
×

Like this? Share it with your network

Share
  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Be the first to comment
    Be the first to like this
No Downloads

Views

Total Views
1,114
On Slideshare
1,114
From Embeds
0
Number of Embeds
0

Actions

Shares
Downloads
11
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
  • There will be two briefing books the first one addresses the more technical aspects and the second set of briefing address the more business-management aspects.
  • READ THROUGH THIS SLIDE AND USE WHITE BOARD TO DISCUSS THE THREE LEVEL FRA WE HAVE PROPOSED SOME CHANGES TO THE ORIGINAL BUSINESS ARCHITECTURE . . . (next slide)
  • READ THROUGH THIS SLIDE AND USE WHITE BOARD TO DISCUSS THE THREE LEVEL FRA WE HAVE PROPOSED SOME CHANGES TO THE ORIGINAL BUSINESS ARCHITECTURE . . . (next slide)

Transcript

  • 1. Leveraging XML Standards and Technologies Linked to Enterprise Architecture: Key to Government Transformation! John Dodd IAC Enterprise Architecture SIG- Co-chair Computer Sciences Corporation(CSC) [email_address] Linking IAC White Papers to XML Working Group “ XML Everywhere- A pervasive enabling technology”
  • 2. New Challenges Facing Agencies
    • Challenges
    • Focus on Business needs
    • Develop “Federated” Business Line
    • Architectures
    • Align with FEA Reference
    • Models with Industry Standards
    • Manage EAs across the Government- work with NASCIO, etc
    • Use of Emerging Open Standards
    • Goals
    • Provide “best-practices” and “thought leadership”on challenge problems
    • Support the Deployment and Outreach effort
    • Work with CIO Council and our government customers
  • 3. Agenda
    • IAC Role and Status
    • FEA Reference Model and New Approach
    • Enterprise Models- Linked to XML and Web Services
    • Focus on “Cross Government Information Sharing”- Business Line Architecture
    • Value and Leveraging XML: Challenges of Infusion
    • Recommendation for XML-based Technologies becoming “Mainstream” and Pervasive
  • 4. Context Setting
    • IAC Support for Challenge problems
    • FEA Reference Model: Made up of Reference Models acts as common “Target” Architecture and IAC recommends additions with strong focus on process/methodology elements with Strong Focus on “Applying”
      • www.feapmo.gov
    • XML, Web Services, other technologies linked to the Enterprise Architecture effort as part of an overall Technology Management initiative.
    • Leveraging XML Technology- Business Case- the Value and fitting within the FEA Mindset
    • Closing the Technical-Business Divide- “Common Conceptual Ground”- Goal Oriented- Beyond Neat to Useful and Useable!
  • 5. “ Emerging” Set of Common Goals
    • Business Goal Driven Framework
    • Transformation Framework: Models need Methods, New Thoughts, New Actions
    • Enterprise Model that links models together: Unified Enterprise Model
    • Leverage Inherent Features of Enabling Technologies: Use Mature and Be Ready for Emerging Technologies(eg. Web Services)
    • Human Actions and Role Changes integrated with Models
    • Implement Business Process Models and Federated Information Models with Model/Meta Data Approaches
    • Strong Open Standards Support and Involvement
    • Establish Cross-Government Interoperable Centric Concept of Information Supply Chain and Integration Points
    • Services-based Infrastructure(s): Everything a Service including Security Service Framework
    • Support for Reuse and other Tools needed for all Aspects
    Business Operational View Domain aspects of business transactions Technology Service View IT aspects of business transactions
  • 6. Overall Context Diagram: IAC Papers linked to FEA/RM and FEAF- IAC Business Line Channels Channel 1: XXX Channel : AAAA First gov Reference Models: EA Governance & Technology Management Human EA Element Security Service Framework Transition PLAN GEAF 1.0 Business Line Infostructure Forming BL Communities Information & Data Reference Model : Using Federated Approach Model: Usage
    • BRM in Conceptual –
    • Strategy Stage
    • Service Component Model
    • Interfaces,
    • Interoperability,
    • Integration :
    • TRM
    • Mgmt
    Technology Architecture Applications Architecture Information & Data Architecture Business Architecture Technology Architecture Applications Architecture Information & Data Architecture Business Architecture Framework RM to FEAF Compatibility Changes
    • Successful EA Activities:
    • Leveraging experience -- Facing new challenges
    Process Changes
    • Cross-cutting Security
    • Architecture
    Change PRM-Business Case -Value Management Goal Select  Plan Evaluate  
  • 7. Transformation= New (Thoughts + Models+ Process) with Value-Focused Actions that are Managed! Way of Thinking Way of Managing Way of Supporting Way of Modeling Way of Working Linked- Governance Common Services Linked- Implementations Way of Executing Actionable Steps Citizen-Centered, Business Lines, Cross-government, RM, etc Way of Focusing Value
  • 8. The FEA Business Reference Model (BRM), Version 1.0 Internal Operations / Infrastructure Human Resources, Financial Management Admin Supply Chain Management Human Resources, Financial Management Admin Supply Chain Management Inter-Agency Intra-Agency Support Delivery of Services Legislative Management Business Management of Information IT Management Planning and Resource Allocation Regulatory Management Controls and Oversight Public Affairs Internal Risk Management and Mitigation Federal Financial Assistance Web Services
    • Telephone
    • Voice
    • Interactive
    E-system to System Public/Private Partnerships Fax Kiosk Face to Face Mail Program Admin Compliance Services to Citizens Public Asset Management Marketable Asset Management Defense & Nat’l Security Ops Diplomacy & Foreign Relations Disaster Management Domestic Economy Education Energy Management Insurance Public Health Recreation & National Resources Social Services R&D & Science Regulated Activity Approval Consumer Safety Environmental Management Law Enforcement Legal Revenue Collection Trade (Import/Export) Transportation Workforce Management Program Admin Compliance Services to Citizens Public Asset Management Marketable Asset Management Defense & Nat’l Security Ops Diplomacy & Foreign Relations Disaster Management Domestic Economy Education Energy Management Insurance Public Health Recreation & National Resources Social Services R&D & Science Regulated Activity Approval Consumer Safety Environmental Management Law Enforcement Legal Revenue Collection Trade (Import/Export) Transportation Workforce Management Government- to-Citizen Access Channels Employee- to-Employee Access Channels Lines of Business Sub-Functions Internal Lines of Business (pictured on following pages) Business Areas Page Web Services
    • Telephone
    • Voice
    • Interactive
    E-system to System Public/Private Partnerships Fax Kiosk Face to Face Mail
  • 9. XML Standards and Web Services Alignment with FEAF and FEA RM’s Resource Management & Administration Data and Information Models XMI, CWM, MOF, XML Infoset, Xpath, Xlink, RDF, etc…. Standards Grants Technology Architecture Applications Architecture Information & Data Architecture Business Architecture S E C U R I T Y Evaluation & Research Enforcement Information Dissemination Resource Management & Administration Security Architecture/ Management Policy(SAML)  Standards Emerging Systems Technology- Grants TRM: Communication Access Channels : WSDL, SOAP, Channel Definition Formats, etc Business Process BPMS,ebXML/BPSS, BTP,UML/EDOC, UEML,WSDL XML Security & WS Component-Standards and use of Self-Describing Service Descriptions (WSDL, etc) Technology Architecture Applications Architecture Information & Data Architecture Business Architecture S E C U R I T Y Evaluation & Research Enforcement Information Dissemination
  • 10. Standards Mapped to the Reference Model…..Work with Standards Organizations to Meet e-Government and EA/BLA Needs Page BUSINESS NEEDS RESOURCE ALLOCATION DESIRED OUTCOMES Information Technology Other Capital Assets Workforce Human Capital Equipment, Fleet & Facilities Service Components, Technology & Data
    • Citizen Service
    • Mission Performance
    • Internal efficiency
    OUTCOMES Common measures across agencies and programs Programs tied to outcomes Business support and administrative opportunities Resource distribution The Business Reference Model (BRM)- Define Common BPM Models and Vocabulary- BPMN with Government Extensions Support Delivery of Services Internal Operations/Infrastructure Legislative Management Business Management of Information IT Management Planning and Resource Allocation Regulatory Management Controls and Oversight Public Affairs Internal Risk Management and Mitigation Federal Financial Assistance Human Resources Financial Management Admin Supply Chain Management Human Resources Financial Management Admin Supply Chain Management Inter - Agency Intra - Agency Program Admin Compliance Services to Citizens Public Asset Management Marketable Asset Management Defense & Nat’l Security Ops Diplomacy & Foreign Relations Disaster Management Domestic Economy Education Energy Management Insurance Public Health Recreation & National Resources Social Services R&D & Science Regulated Activity Approval Consumer Safety Environmental Management Law Enforcement Legal Revenue Collection Trade (Import/Export) Transportation Workforce Management Web Services/ XML Extensions Tracked by Leveraging Technology Working Groups Resource reference models: - Service Components - Facilities - Workforce, etc. The Performance Reference Model (PRM): XBRL Plus Performance Goal extension –Government Extension Needed! Web Services
    • Telephone
    • Voice
    • Interactive
    E-system to System Public/Private Partnerships Fax Kiosk Face to Face Mail Web Services
    • Telephone
    • Voice
    • Interactive
    E-system to System Public/Private Partnerships Fax Kiosk Face to Face Mail
  • 11. Recommend Technology Management Activities
    • Strategic Selection of Key Enabling Technologies
    • Business Case for Technology-What are the benefits- early adopters to “prove” it. Benefits and Value Propositions.
    • Technology for the Business Leaders
    • Technology Education.
    • Technology Roadmaps: Keeping Options Open
    • Maturity Maps- periodically updated.
    • Involvement in Open Standards efforts- OMG, OASIS, etc- Active Participation
    • Communities of Interest and sharing of Best practices.
    • Competency Centers such as “infostructure” Competency Center
    • Technology Readiness Timeline as part of Sequencing Plan- Open Architectures.
    • Enterprise Integration Solution Labs- test the interfaces and integration elements upfront with a continuous integration strategy.
    • Technology Management added to the EA Guidelines document
  • 12. Strategic Selection of Key Enabling Technologies Management Forces Technology Assessment- Current Architecture Technical Forces Strategic Technology Focus Strategic Paths of Change- Technology Tracking
    • Web Open Standards
    • Components and Frameworks
    • Interoperability Frameworks and Standards
    • Binding and Language Integration Standards
    • Transaction Management
    • Data Base Performance and Federation
    • Expressive Systems
    • Data Analysis and Reporting - Web Access
    • Business Process Integration Systems- Process Modeling, Rules
    • Security Integration
    • Collaboration and Distributive Dynamic Information Systems
    Technology Reviews and Infusion in Sequencing Plan
  • 13. TRM and XML: Web Services- Self Describing Components
  • 14. Self-Describing SOAP-based information Exchange Package- Key Part of Infostructure Extension File Xlinks- Xpaths-Xpointers or locators Schema/DTD’s Self Describing Base File Inner Envelope Outside Envelope VC “tagged” Information Package Header Information Package Audit Trail Information Directory- Meta Data Master Audit Log File Mapped to Business Process Standard Filing Elements (Canonical form) added During parts of BP/ Event processing /Annotations-Collaborative Comments can be added by peers Each element can be protected- “Locked” using policy & role-based enforcement management Lock , Signature,and Selective Encrypting Security Policy- Security Headers, Signatures, Encryption
  • 15. Leveraging Technology Work Groups should define Technology Roadmaps: Keeping Options Open
    • Mature:
    • J2EE
    • XML Technology Core
    • Document Management
    • Data Warehouse
    • Emerging:
    • XML Security
    • SOAP with Attachments
    • Xforms- Record Management
    • ebXML
    • BPMS- BPMN
    • UML 2.0- Model Driven
    • XML Integration Tools
    • KM Linked to BP
    • Incubating:
    • Government-Domain XML
      • Legal XML
      • Emergency Systems
    • Topic Maps
    • Semantic Web
    • XML Paths-Links
    • Web Services Security
    Timeline Current 6 Months-18 Months 12 months- 48 months Used at Workshop to Gather Opinions- Options- Focus on Value Mainstream- Acceptance by Pragmatist
  • 16. XML Maturity Mapping
  • 17. Technology Readiness Timeline Principles, Constraints, Assumptions … Design Standards
    • Justice Initiatives
    • IT Planning
    • JCN- II
    • JCON- IIA
    • Common Data Definition
    Emerging Standards J2EE/Connections JMS W3C/XML-Business Standards-ebXML, BPMS Java Meta API Now 2+ 1 Year
    • Incubating
    • New Security Concepts
    • Semantic Web
    • Dynamic Firewalls
    • LegalXML
    • J2EE Mgmt Spec
    FY 2003 FY 2004 FY 2005 Justice Initiatives
    • Early Pipeline: Technology
    • Dynamic Firewalls
    • Domain Services
    • Semantic Web-Searches
    • Recommendation Systems
    • Fault Tolerance
    • QOS
    • Legal XML
    • Ready: Technology Mature
    • Forms Management
    • Data Warehouse, Data Marts
    • Portals
    • EAI/Middleware
    • Content Management
    • Collaboration/KM
    • Business Rules
    • LDAP
    • XML Technical Core
    • J2EE
    • Near Ready: Technology
    • Data Integration
    • Web Services/Components
    • Business process with Workflow
    • Document Management/NARA
    • XML/SOAP
    • Government Mandates
    • President’s Mgmt Agenda
    • OMB-A130- EA
    • E-gov
    • GPEA - 2003
    • Clinger-Cohen
    • Section 508
    • GPRA
  • 18. Focus on Information Sharing: Interfaces, Interoperability and Integration
    • Business Line Architecture
    • Infostructure: “Information Interoperability Reference Model”
    • Exchange Packet formats and “Common Components” and Access and Connection Services
    • Work with NASCIO and Local organizations
    • OMG-OASIS Government Task Forces
    • Encourage “unified” Standards participation Government with Industry partners
    • Standards profile
    • Impact the Acquisition Process with Open Standard First
    • Process- a few ways and not- hundreds of ways
    • Taking action
  • 19. Business Service Framework:Federates Data and Links Business Services across Business Lines Business Line and “Zone” Resource Management: Federated-Business Communities Business Line Channels: Business Service-Data mapped & available a d e b f c g h / Business Service -Data Federation Data a d e Data b f Data c g h Zone A Zone B Zone C
  • 20. Common Infostructure- Process Emergence of Business Service Network Network as a Service Delivery Platform Business Line A Architecture Lead Agency X Support Agency y Context Business Line B Business Line C Integration Zone Integration Point Firewalls- enforcement points Common “Infostructure Framework”
  • 21. Cross-Government EA Management
  • 22. Next Steps
    • Add Side-bars to each of the paper linking XML and Web Services to the Topic Area
    • “ Section” on XML-based Information Exchanges, Metadata, XMI, Federated Security and Trust- “Infostructure” for BLA
    • Interested in External Reviewers- additional government and industry experts to review and refine papers
    • 3 more papers underway: Security and Privacy Service Framework, Web Services to EA with Action, Business Line Infostructure and Aligned Process with NASCIO along with other ideas to share on Governance-Technology Management
    • Support will shift to more Deployment and Outreach Support
    • Government Reviewers Needed and Industry Involvement Encouraged
      • Contact Davis Roberts &quot;Roberts, Davis&quot; <CAROLINE.DAVIS.ROBERTS@saic.com>