1. Succeeding with Component-based Architectures Industry Advisory Council Enterprise Architecture SIG Draft

2. IAC Draft Material2 Introduction John Butler Architect Director Unisys Corporation John.Butler@unisys.com 703.556.5011 Dave Mayo Vice President Everware, Inc. david@everware.com 703.246.0000 x.103 John Weiler Executive Director Interoperability Clearinghouse john@ICHnet.org, 703.768.0400

3. IAC Draft Material3 Presentation Outline Current Situation Component-Based Architecture: Context Implementation Challenges Business Drivers & Benefits Enablers & Critical Success Factors Recommendations for Transformation Questions

4. Current Situation

5. IAC Draft Material5 Current Issues in Federal IT Many IT development projects fail or face significant cost overruns (72%) Current EA methods are tech centric Deployed legacy systems inflexible Current EA efforts not oriented for cross agency interoperability/information sharing. Majority of IT budgets spent on maintaining legacy systems FEAF, C4ISR and TEAF do not communicate business needs nor enable leverage of COTS solutions

6. IAC Draft Material6 New IT Solution Paradigm Custom Development gives way to Application Assembly Y e s t e r d a y Design, Code & Test Focus on Component Assembly & Integration Model, Evaluate, & Acquire Timeframes are 12-24 weeks! Reliance on industry standards Rate of change is high and accelerating Increased Agility & Adaptability of Enterprise Systems T o d a y Architect, Acquire, Integrate Services Oriented Architecture dictates Component-Based 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 data model & structured methods

7. Component-Based Architecture: Concepts

8. IAC Draft Material8 Component-Based Architecture: Concepts CBA Approach to structuring enterprise solutions that increases modularity and adaptability Focus on component assembly Origins in OO and CBD Fits within Federal Framework of Reference Models Facilitates alignment of business and technology CSF for OMB FEAPMO Services Oriented Architecture Way of thinking about systems as set of modular services: business, data, infrastructure

9. IAC Draft Material9 Business Reference Model (BRM) Lines of Business Agencies, Customers, Partners Service Component Reference Model (SRM) Capabilities and Functionality Services and Access Channels Technical Reference Model (TRM) IT Services Standards Data Reference Model (DRM) Business-focused data standardization Cross-Agency Information exchanges Business-Driven Approach Performance Reference Model (PRM) Government-wide Performance Measures & Outcomes Line of Business-Specific Performance Measures & Outcomes Federal Enterprise Architecture (FEA)

10. IAC Draft Material10 CBA: Driven by BRM and Implements SRM BRM CBA Layer 1 CBA Layer M BRM SRM Service Layer 1 Service Layer N BRM Business Lines Sub-functions Contribution to Fulfillment Functional Traceability

11. Implementation Challenges

12. IAC Draft Material12 Implementation Challenges Current EA, SDLC & funding processes are not attuned to CBA, and encourage monolithic stove pipes. No consistent COTS evaluation & acquisition process Bureaucracy & culture protect against change The “Legacy Hurdle” Licensing issues are complex & confusing

13. IAC Draft Material13 Current EA and Solution Development Life-cycle Processes Ineffective Poor alignment of stakeholder views No cross-agency or cross- application business process refactoring Focus on custom SW development No consistency enforcement of EA artifacts (inter- and intra-agency) Does not produce actionable or comparable output Typically waterfall – not iterative Produces monolithic apps – not modular No consistent COTS evaluation and acquisition process Inhibits use of commercial best practices & SW artifacts Focus on custom SW development EA Lifecycle Traditional SDLC

14. IAC Draft Material14 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”. No Consistent COTS Evaluation & Acquisition Process

15. IAC Draft Material15 Culture is hard to change "Nothing is more difficult than to introduce a new order. Because the innovator has for enemies all those who have done well under the old conditions and lukewarm defenders in those who may do well under the new." Nicolai Machiavelli, 1513 A.D.

16. IAC Draft Material16 The “Legacy Hurdle” Legacy systems typically: Monolithic – Difficult to modify Closed – Difficult to interface with Ties up available resources Most of IT staff and funds devoted to application maintenance All or nothing legacy replacement Difficult to carve out functionality for incremental replacement

17. Business Drivers & Benefits

18. IAC Draft Material18 Business Drivers & Benefits Increased Adaptability & Flexibility Capability Sharing = reduced redundancy Time to Market Lifecycle Cost Risk Mitigation Consistent application of policy & guidance Interoperability and Information Sharing IT Value Chain and Business stakeholder alignment

19. IAC Draft Material19 Common Components Enable Cross-agency Interoperability & Information Sharing Agency A Agency B Access Channel Agency C Office Bureau Office Business Community Citizen Dept. Business Segment 1 Business Segment 2 Business Segment 3 Business Segment 4 Gov. Analyst

20. IAC Draft Material20 Agile Organizations Require Adaptable Architectures 1980’s and earlier Organization Focus Mainframe centric Monolithic Internal use 1990’s Business Process Focus Client/Server Monolithic Business-to-business via EDI -file transfer Virtual organizations Distributed Functions Service oriented Componentized E-commerce Real-time New Millennium 3rd party service providers Extranet Internet Customers

21. Enablers and Critical Success Factors

22. IAC Draft Material22 Enablers and Critical Success Factors Enablers Technologies Exist to Enable CBA Commercial components available Standards & Best Practices Exist - Adopt them BRM is the starting point Critical Success Factors Business Driven EA Approach Revised Solution Development Lifecycle focused on COTS acquisition/integration Mechanism for Sharing and Managing Software Assets Is Key

23. IAC Draft Material23 Conceptual and Strategic Interface Alignment Technical Interface Development Business Process Driven Integration: Business Process Leadership

24. IAC Draft Material24 OMB’s New SDLC Incorporates CBA in an Iterative Process Artifacts and Activities  Performance Measures, Objectives, Outcomes (PRM)  Business Objectives (BRM)  Funding, Partnering Strategies Acquisition Integration  Identify Best Practices, technology Enablers, and Components  Existing Stake Holders, Business Processes, and Workflows  Existing Delivery and Access Channels (Portfolio)  Must Have Functions, Features, and Info Exchanges  Short and Long-Term Requirements  Assessment of As-is state: Gap analysis  Define/Align Service Components  Component Common Criteria, SLA  Select COTS based on normalized EA vendor submissions.  Define Component Relationships to BRM  Wiring & Activity Diagrams, Component Arch, Data Arch  To-Be architecture ‘ blueprints ’  Prototype Solution Architecture  Verify ROI, business fit  Validate Sequencing Plan Iterative Development Value-Based Releases Understanding the Business Understanding the Business Knowing What’s Possible Knowing What’s Possible Model the Business Define the Gaps Model the Business Define the Gaps Develop the “Blueprints” Develop the “Blueprints” Obtain Components Assemble the Components Assemble the Components Execution  Deploy  Manage  re-Baseline Execute & Deploy Execute & Deploy Discovery Requirements Strategy Architecture

25. IAC Draft Material25 Technologies to Support CBA are Here Today J2EE Technical Architecture.Net Technical Architecture EAI Web Services Portals Directory Services

26. IAC Draft Material26 Repository: Sharing & Managing Software Assets Application Development Group Commercial Catalog Agency Specific Catalog Specify Build Productize Find EvaluateConsume Publish Federal-Wide Catalog User View Component Repository

27. Recommendations

28. IAC Draft Material28 Recommendations for Transformation to CBA Update Policy & Drive Cultural Change Reform COTS Process Define SDLC FW Update EA Process Adopt Common Infrastructure Establish Solution Center Interoperability Define Interop. Standards

29. Phasing of Recommendations

30. IAC Draft Material30 Establish CBA Solution Center CBA Solution Center Mission: Foster Use of Common Services/Components Across Agencies Process Center of Excellence: CBA Best Practices, Business Process Patterns, Linkages to Reference Models Component Integration Lab: COTS/GOTS Evaluation, Common Components, Certification of Components Collaboration Forum: Build Consensus on Process & Data Factoring CBA Solution Center Component Integration Lab Collaboration Forum Process Center of Excellence

31. IAC Draft Material31 Update EA & SDLC Processes Integrate CBA into Enterprise Architecture & Solutions Development Framework Initiation Ongoing OMB Agency

32. IAC Draft Material32 Define Reference Model Linkages Agencies Need Assistance in Building Agency Services Architecture from SRM and BRM; also data structures (DRM) from the SRM Initiation Ongoing OMB Agency

33. IAC Draft Material33 Adopt Common Infrastructure Establish Technical Infrastructure (TRM), Acquire Appropriate Tools, Implement Component Repository Initiation Ongoing OMB Agency

34. IAC Draft Material34 Define Interoperability Standards Establish Policies, Procedures, Technology Options for Interoperability & Information Sharing Across Agencies Initiation Ongoing OMB Agency

35. IAC Draft Material35 Update Policy & Drive Organizational Change Organizational Change is Difficult: Treat Transformation as Change Management Project Initiation Ongoing OMB Agency

36. IAC Draft Material36 Reform COTS Process Establish Common Process for Evaluating & Acquiring COTS/GOTS; Mechanism for Development of Common Components; Certification Process & Repository Initiation Ongoing OMB Agency

37. IAC Draft Material37 Summary