• Share
  • Email
  • Embed
  • Like
  • Save
  • Private Content
Working Draft Enterprise Architecture Roadmap for Business ...

Working Draft Enterprise Architecture Roadmap for Business ...






Total Views
Views on SlideShare
Embed Views



0 Embeds 0

No embeds



Upload Details

Uploaded via as Microsoft PowerPoint

Usage Rights

© All Rights Reserved

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
Post Comment
Edit your comment
  • The FEA models are organized very much around Services but it is also business driven. The BRM describes business lines and the functions and sub-functions or segments that they comprise. These segments use services defined in the SRM that to support their mission. These services are often used by multiple business functions. CBA provides the mechanism for grouping and realizing these services in an effective manner. By driving the architecture in this manner, the CBA, like the FEA Models, is business driven and shows direct contribution of components to agency mission fulfillment.

Working Draft Enterprise Architecture Roadmap for Business ... Working Draft Enterprise Architecture Roadmap for Business ... Presentation Transcript

  • Enterprise Architecture Roadmap for Business Transformation Architecture Roadmap and eGov Artifacts An ICHnet.org perspective on getting from architectures to implementation reality John Weiler, CAO [email_address] SAWG Representative October 15, 2002 ICH Architecture Resource Center
  • Our mission to advance mechanisms that assure the successful implementation of enterprise technical solutions aligned to business drivers “ From Architectures …. to Implementation Reality”
  • The EA Challenge making sound COTS decisions based on business drivers Exert from EDS Business Case Analysis: “The leveraging of our efforts with other parties through the formulation of a non-profit consortium is the most cost effective and efficient way of achieving the goal of interoperability assurance among heterogeneous systems. This ICH capability will augment our capability and provide us much more information about products, standards, and viable enterprise solution sets than we could ever realize through our own internal efforts.”
  • The New IT Solution Paradigm Custom Development gives way to COTS Integration Y e s t e r d a y Design, Code, Test
    • Focus on COTS Integration & Component Assembly
    • Architect, Evaluate, & Integrate
    • Timeframes are 12-24 weeks!
    • Interoperability not “knowable” in advance
    • Rate of change is high and accelerating
    T o d a y Model, Validate, Integrate COTS Paradigm shift dictates EA driven SDLC process Software Components & Off the Shelf Products
    • Focus is Software Development
    • Code everything to spec
    • Timeframes 12-24 months
    • Complexity and rate of
    • change manageable (CMM)
    • Technology base Stable
    • Driven by IDEF, UML,
    • and antiquated EA methods
  • PMs lack the tools to make sound COTS acquisition decisions! CIOs Feel... Overwhelmed by offerings? Ill-equipped to evaluate? Out paced by market? Interoperable? Over hyped?
    • No body of knowledge from which PM can evaluate competing COTS offerings.
    • No common EA language to communicate business need to technology.
    • No mechanisms for assessing risks, composability or interoperability of COTS solution
    • No clear mapping of business drivers to standards or COTS solution offerings. Gap = Risk!
    • Current documentation methods do not result in action oriented solution “blueprints”.
  • ICH Architecture Assurance: Model Align Validate Integrate
    • Architecture Driven
    • Begin with Business Drivers
    • Mission Aligned
    • Imbedded Metric
    • Interoperable
    • Normative
    • Non Prescriptive
    • Action Oriented
    • Acquisition Ready
    • Risk Adverse
    ICH Common Criteria
  • ICH Architecture Alignment BRM CBA Application Layer 1 Infrastructure Layer M BRM SRM Appl Service Components Layer 1 Infrastructure Service Components Layer N BRM BRM Business Lines Sub-functions Contribution to Fulfillment Functional Traceability
  • ICH Architecture Collaboratory Linking the IT Value Chain “ ... the concept of the Interoperability Clearinghouse is sound and vital. Its developing role as an honest broker of all interoperability technologies, no matter what the source, is especially needed. Such efforts should be supported by any organization that wants to stop putting all of its money into maintaining archaic software and obtuse data formats, and instead start focusing on bottom-line issues of productivity and cost-effective use of information technology.” Assessment by Leading FFRDC, 2000
  • ICH Architecture Resource Center (ARC) EA Collaboratory for the IT Value chain
    • Establishment of “building codes” for COTS e-solution frameworks using architecture templates
    • Modeling re-usable solution models by industry; finance, e-gov, mfg, healthcare.... based on implementation successes
    • Shared COTS Solutions vetting results reduces redundant research
    • e-Directory of interconnecting products, integration services documents “what works” and “what works with what”
    • Architecture Methods, Mentoring, Training, Research, and IV&V to transform the EA process
    • Unbiased Collaboratory promotes information sharing between standards groups, vendors, integrators and enterprise users. Give a little, get a lot!
  • Architecture Assurance Method Aligning & vetting the inputs & outputs Dave Connelly, President and CEO of the Open Applications Group , says, "We are looking forward to the contributions of the Interoperability Clearinghouse as a partner in our efforts to dramatically improve software integration for customers Internet eCommerce and other projects."
  • COTS Assessment Framework compliance with OMB guidance Architecture Roles Validation Points Respond to Business Change Investment Process /Architecture Project Assessment Framework 1 Assess Business Alignment 2 Assess Business Case Proposal Assess Technology Compliance Target IT App.Port / Infra. Initiatives Aligned per IT Strategy Alignment Scorecard (SELECT) Develop Business Case Compliance Assessment 5 Assess Waiver/ Exception Request Enterprise Design Patterns Acceptable Alignment Acceptable Compliance Unacceptable Conformance Unacceptable Alignment Unacceptable Compliance Proposed Concept Report TRM Standards 4 Evaluate Architecture Compliance IRB Report Audit Reports (EVALUATE) Evaluation Disapproved 3 (SELECT) Project Initialization (CONTROL) • Define • Build • Implement • Operate
  • ICH Architecture Assurance Method aligns SDLC views Business drivers, Standards, COTS Specs & Integration Needs Product Mfg. Integrator IT Standards Drivers
    • Standards Profile
    • Two Phase Commit
    • Relational Constructs
    • Row Level Locking
    • Referential Integrity
    • ODBC Interface
    • SQL Interface
    • IDL Interface
    • Vetted Product Spec-
    • Two Phase Commit
    • Relational Constructs
    • Row Level Locking
    • Referential Integrity
    • ODBC Interface
    • SQL Interface
    • JDBC Interface
    • Triggers
    • OLE DB Interface
    • Multiphase converter
    Solution Profile Scale, Industry Solution Suite Product A Product B v6.1 Product C v2 Platform S BRM Biz Process Infrastructure Needs Bus. Drivers External Influences Policy Strategic Plans Legacy Integration As-is EA
    • Normalized Lexicon
    • Distributed Org
    • Mobile Force
    • non-fixed locations
    • secure communications
    • concurrent updates
    • complex data types
    • unstructured data
    • central data collection
    • Open Systems
    Solution Architecture Stake Holders ICH AAM
  • Strength of Evidence = Risk Metrics Due diligence on features/functions reduces risk 85% Evidence Sources Strength of Evidence 50% 25% Bi-directional vendor claim Functional/ conformance testing Implementation successes Integration testing Risk 75% $ & time
  • ICH Method: The Benefit Sharing results reduces time, cost, and risks ICH Confidence Level Resources (cost & time) Trade Studies Testing Alone Traditional approach ICH advantage High Low Risk Delta Cost/time Delta
  • COTS Repository Cornerstone of Portfolio Mgt “ propagation of intellectual capital that can assist in E-Government transformation” FEAPMO.gov OFFICE OF THE SECRETARY OF DEFENSE, DEPUTY CIO: "Since the value of the ICH to our programs increases rapidly through results sharing, we encourage the defense community and IT industry to participate directly in the public service initiative in terms of sponsorship and lessons learned"
  • Example: OnLine Documents
  • Example 2: Technology Area Criteria Selection
  • Example 2: Technology Area Criteria Management
  • Example 2: Technology Area Viewing
  • Shared COTS Research: Eliminating Redundant Study efforts saves $$$$
  • Validation Process Flows “ As one of the leading advocates of open systems and interoperability, the OMG believes that the Interoperability Clearinghouse initiative will help users realize the benefits from our combined efforts”. OMG, Bill Hoffman, President
  • ISV Product Entry Workflow Workflow engine validates vendor entries Product Data Sheet Composite Features Add New Features New Product/ Standard Profiles Technology Class Profile Documented Features Select Existing Features Establish XML URL Links Create UML Template Conformance Templates Work Flow Manager. Standards Directory Product Directory Standard Specification Validate New Features COTS Validation
  • Functional Validation Process Vendor Statements Work Flow Manager. Stds Conform. Statement Interop. Statement Functional Statement Conformance Testing Functional Testing Interoperability Testing Testing Results Attach to Product Profile Vendor Concurs 60 Days Pass? Yes No Vendor Correction No Yes Update Product Directory Send to 3rd Parties 3rd Party Product Statement Send Message to Subscribers Interop Validation
  • Interoperability Validation Process Industry validates Vendor Interworking Statements Select Products Tested Show Current Product Connections & Functions Confirm Connections Existing Links ? Create new Connection & Component Vendor Interop. Submissions Confirm Product Functions Determine Level of Effort & Interop. Create Product C4ISR Attrib. Update IC
  • Results from the ICH Process: Interoperable Web-Based Solution Architectures Test Env. (Mercury Intl.) NT 4.0 WS Application Libs (C, DLL, MFC) Security Service (PKI X.509) IDL Stub RMI Runtime Win 32 Subsystem | NT Device Drivers J2EE Web Services EJB Comms (TCP/IP) SSL IDE Runtime (Javascript, PB, C++, JDK) Java JITC Directory Svrs. X.500, or DNS, DHCP J2EE /Web Services Systems Management Server (Patrol) Certificate Validation Win 32 Subsystem - NT Device Drivers Comms (TCP/IP)/ SSL CDS Service Backup Network Mgt. (Open View) Apha or Pentium- Pro NT 4.0 Server Application Client Systems Server Alpha, Pentium Pro NT 4.0 Server Application & System Runtime Modules Security Service (PKI Certificate) Directory Svrs. X.500, DNS, DHCP, LDAP (v1.22) CDS EJB Server (or CORBA Server) TP Mntr. (Encina++) Win 32 Subsystem - NT Device Drivers Comms (TCP/IP) SSL Time Servicer JDBC API Client (Connection Client) Compilers (Java JITC) Application Server or A P I EJB Module RDBMS Server SQL Proxy Server (Connection Server) HP, Sun, or IBM Unix or Alpha NT 40 Server Posix Subsystem (Native or NT), Drivers Comms (TCP/IP) SSL ebXML Server Database Server JDBC Driver OCI/INET XA Lib. (Encina) RDBMS API (ODBC or JDBC) ebXML API HP, Sun, or IBM Unix or Alpha NT 40 Server Posix Subsystem (Native or NT), Drivers Comms (TCP/IP) SSL Web Services WEB Server ODBC Driver (Intersolve) OCI/INET RMI/ IIOP MFI/ Gateway Browser, Native GUI
  • Case Studies Applied Architectonics “ The ICH repository data and analysis methodologies was very helpful in supporting a quick turn around for [Information Assurance] section of COTS security products. Highly detailed ICH technology domain and product evaluation data comprised over 60% of this urgently needed [architecture] report”. GCPR, Program Manager, Northrop Grumman/PRC
    • Applied ICH Architecture Immersion Program
      • Developed architecture validation criteria to GCPR Program Office
      • Developed product selection guidelines for Prime Contractor
      • Applied ICH Architecture Assurance Method
    • Outcomes
      • Enabled award based on unambiguous design specs
      • Augmented UML/MDA to address legacy and COTS capabilities
      • Ensured viability of chosen technologies
        • Met HIPPA requirements
        • Met security requirements
        • Provided integration framework for web infrastructure
      • Assured implementation success
    Case Study: World Largest Healthcare Project Challenge: develop enterprise architecture for patient record integration
    • Applied ICH Solutions Validation Program
      • Performed architecture baseline assessment
      • Provided guidance and selection support for Web-app server, VPN, portal, last-mile wireless connectivity
    • Outcomes
      • Validated requirements against marketplace offerings
      • Improved confidence in technology decisions
        • Delayed VPN implementation
        • Purchased Web application server, database, and media products
        • Deployed system without a hitch
      • Significantly reduced time/cost to implementation
    Case Study: World Largest Media Company Challenge: Select enterprise web infrastructure to integrate stovepipe applications
  • Case Study: World Largest Intelligence Agency
    • Applied Architecture Validation Program
      • Developed common criteria for emerging portal market
      • Evaluated selection of Enterprise Portal for pilot project
      • Developed impact analysis on enterprise architecture
      • Maintained view of evolving marketplace
    • Outcomes
      • Enhanced and normalized portal selection criteria
      • Identified key features/functional areas for testing
      • Applied commercial best practices for successful production rollout
        • Improved understanding and alignment of technology to problem domain
    Challenge: means of integrating diverse communities via the web
  • Conclusion: The ICH Method is; Industry Developed, Government Approved, Business Driven, Standards-based, Collaborative COTS Selection Process ………...on GSA Schedule! “ ... to help the 24 Presidential Priority E-Gov Initiatives and Federal Agencies with activities surrounding the technical and solution design of their e-Gov initiatives. ” Mark Forman
  • www.ICHnet.org 703 768 0400 [email_address] Need Help?