Succeeding with Componentbased Architectures

1
Succeeding with Component-based Architectures

• Industry Advisory Council
• Enterprise Architecture SIG
• Draft

2
Introduction

• John WeilerExecutive Director Interoperability
  Clearinghouse
• john_at_ICHnet.org,
• 703.768.0400

• John ButlerArchitect DirectorUnisys Corporation
• John.Butler_at_unisys.com
• 703.556.5011
• Dave MayoVice PresidentEverware, Inc.
• david_at_everware.com
• 703.246.0000 x.103

3
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
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
New IT Solution ParadigmCustom Development gives
way to Application Assembly
Y e s t e r d a y Design, Code Test
Services Oriented Architecture dictates Component-
Based SDLC process

• 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

Software Components Off the Shelf Products
T o d a y Architect, Acquire, Integrate

• 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

7
Component-Based Architecture Concepts
8
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
Federal Enterprise Architecture (FEA)
Performance Reference Model (PRM)

• Government-wide Performance Measures Outcomes
• Line of Business-Specific Performance Measures
  Outcomes

Business Reference Model (BRM)

• Lines of Business
• Agencies, Customers, Partners

Business-Driven Approach
Service Component Reference Model (SRM)

• Capabilities and Functionality
• Services and Access Channels

Data Reference Model (DRM)

• Business-focused data standardization
• Cross-Agency Information exchanges

Technical Reference Model (TRM)

• IT Services
• Standards

10
CBA Driven by BRM and Implements SRM
11
Implementation Challenges
12
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
Current EA and Solution Development Life-cycle
Processes Ineffective
EA Lifecycle
Traditional SDLC

• 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

14
No Consistent COTS Evaluation Acquisition
Process

• No common EA language to communicate business
  need to technology.

• Current documentation methods do not result in
  action oriented solution blueprints.

• No clear mapping of business drivers to standards
  or COTS solution offerings. Gap Risk!

• No body of knowledge from which PM can evaluate
  competing COTS offerings.

CIOs Feel...
Overwhelmed by offerings? Ill-equipped to
evaluate? Out paced by market? Interoperable? Over
hyped?

• No mechanisms for assessing risks, composability
  or interoperability of COTS solution

15
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
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
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
Common Components Enable Cross-agency
Interoperability Information Sharing
Access Channel
Agency C
Agency B
Agency A
Bureau
Citizen
Dept.
Business Segment 1
Business Segment 2
Office
Office
Business Segment 3
Business Segment 4
Gov. Analyst
Business Community
20
Agile Organizations Require Adaptable
Architectures
1980s and earlier
1990s

• Organization Focus
• Mainframe centric
• Monolithic
• Internal use

• Business Process Focus
• Client/Server
• Monolithic
• Business-to-business via EDI -file transfer

• Virtual organizations
• Distributed Functions
• Service oriented
• Componentized
• E-commerce
• Real-time

21
Enablers and Critical Success Factors
22
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
Business Process Driven Integration Business
Process Leadership
Conceptual and Strategic Interface Alignment
Technical Interface Development
24
OMBs New SDLC Incorporates CBA in an Iterative
Process
? Performance Measures, Objectives, Outcomes
(PRM) ? Business Objectives (BRM) ? Funding,
Partnering Strategies
Strategy
Understanding the Business
? Identify Best Practices, technology Enablers,
and Components ? Existing Stake Holders, Business
Processes, and Workflows ? Existing Delivery and
Access Channels (Portfolio)
Discovery
Knowing Whats Possible
? Must Have Functions, Features, and Info
Exchanges ? Short and Long-Term Requirements ?
Assessment of As-is state Gap analysis
Model the Business Define the Gaps
Requirements
? Define Component Relationships to BRM ? Wiring
Activity Diagrams, Component Arch, Data Arch ?
To-Be architecture blueprints
Develop the Blueprints
Architecture
? Define/Align Service Components ? Component
Common Criteria, SLA ? Select COTS based on
normalized EA vendor submissions.
Acquisition
Obtain Components
? Prototype Solution Architecture ? Verify ROI,
business fit ? Validate Sequencing Plan
Integration
Assemble the Components
Execution
? Deploy ? Manage ? re-Baseline
Execute Deploy
Iterative Development Value-Based Releases
Artifacts and Activities
25
Technologies to Support CBA are Here Today
J2EE Technical Architecture
Portals
Web Services
.Net Technical Architecture
EAI
Directory Services
26
Repository Sharing Managing Software Assets
Application Development Group
Specify
Find
Publish
Evaluate
Consume
User View
Publish
Agency Specific Catalog
Component Repository
Federal-Wide Catalog
Commercial Catalog
27
Recommendations
28
Recommendations for Transformation to CBA
Define SDLC FW
29
Phasing of Recommendations
30
Establish CBA Solution Center
CBA Solution Center
Component Integration Lab
Collaboration Forum
Process Center of Excellence

• 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

31
Update EA SDLC Processes

• Integrate CBA into Enterprise Architecture
  Solutions Development Framework

Initiation Ongoing
OMB Agency
32
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
Adopt Common Infrastructure

• Establish Technical Infrastructure (TRM), Acquire
  Appropriate Tools, Implement Component Repository

Initiation Ongoing
OMB Agency
34
Define Interoperability Standards

• Establish Policies, Procedures, Technology
  Options for Interoperability Information
  Sharing Across Agencies

Initiation Ongoing
OMB Agency
35
Update Policy Drive Organizational Change

• Organizational Change is Difficult Treat
  Transformation as Change Management Project

Initiation Ongoing
OMB Agency
36
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
Summary