succeeding with component-based architectures industry advisory council enterprise architecture sig...
TRANSCRIPT
Succeeding with Component-based Architectures
Industry Advisory CouncilEnterprise Architecture SIG
Draft
IAC Draft Material 2
Introduction
John ButlerArchitect DirectorUnisys [email protected]
Dave MayoVice PresidentEverware, [email protected] x.103
John WeilerExecutive Director Interoperability [email protected], 703.768.0400
IAC Draft Material 3
Presentation Outline
Current SituationComponent-Based Architecture: ContextImplementation ChallengesBusiness Drivers & BenefitsEnablers & Critical Success FactorsRecommendations for TransformationQuestions
IAC Draft Material 5
Current Issues in Federal IT
Many IT development projects fail or face significant cost overruns (72%)Current EA methods are tech centricDeployed legacy systems inflexibleCurrent EA efforts not oriented for cross agency interoperability/information sharing.Majority of IT budgets spent on maintaining legacy systemsFEAF, C4ISR and TEAF do not communicate business needs nor enable leverage of COTS solutions
IAC Draft Material 6
New IT Solution ParadigmCustom 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 dictatesComponent-Based
SDLC process
Softwar
e Co
mpo
nent
s
& O
ff the
She
lf Pr
oduc
ts
• 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
IAC Draft Material 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
IAC Draft Material 9
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
Busin
ess-D
riven A
ppro
ach
Performance Reference Model (PRM)
• Government-wide Performance Measures & Outcomes• Line of Business-Specific Performance Measures & Outcomes
Federal Enterprise Architecture (FEA)
IAC Draft Material 10
CBA: Driven by BRM and Implements SRM
BRMCBACBA Layer 1
CBA Layer M
BRMSRM Service Layer 1
Service Layer N
BRMBRMBusiness Lines
Sub-functions
Con
trib
uti
on
to F
ulfi
llmen
t
Fun
ctio
nal Tra
ceab
ility
IAC Draft Material 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 changeThe “Legacy Hurdle”Licensing issues are complex & confusing
IAC Draft Material 13
Current EA and Solution Development Life-cycle Processes Ineffective
Poor alignment of stakeholder viewsNo cross-agency or cross-application business process refactoringFocus on custom SW developmentNo consistency enforcement of EA artifacts (inter- and intra-agency)Does not produce actionable or comparable output
Typically waterfall – not iterativeProduces monolithic apps – not modularNo consistent COTS evaluation and acquisition processInhibits use of commercial best practices & SW artifactsFocus on custom SW development
EA Lifecycle Traditional SDLC
IAC Draft Material 14
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
IAC Draft Material 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.
IAC Draft Material 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
IAC Draft Material 18
Business Drivers & Benefits
Increased Adaptability & FlexibilityCapability Sharing = reduced redundancy Time to Market Lifecycle Cost Risk Mitigation
Consistent application of policy & guidanceInteroperability and Information SharingIT Value Chain and Business stakeholder alignment
IAC Draft Material 19
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
IAC Draft Material 20
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 Millennium3rd party service providers
ExtranetInternet
Customers
IAC Draft Material 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
IAC Draft Material 23
Conceptual and Strategic Interface Alignment
Technical Interface
Development
Business Process Driven Integration: Business Process Leadership
IAC Draft Material 24
OMB’s New SDLC Incorporates CBA in an Iterative Process
Artifacts and Activities
Performance Measures, Objectives, Outcomes (PRM) Business Objectives (BRM) Funding, Partnering Strategies
AcquisitionAcquisition
IntegrationIntegration
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 DevelopmentValue-Based Releases
Understanding theBusiness
Understanding theBusiness
Knowing What’s Possible
Knowing What’s Possible
Model the BusinessDefine the Gaps
Model the BusinessDefine the Gaps
Develop the“Blueprints”Develop the“Blueprints”
Obtain ComponentsObtain Components
Assemble theComponents
Assemble theComponents
ExecutionExecution Deploy Manage re-Baseline
Execute &Deploy
Execute &Deploy
DiscoveryDiscovery
RequirementsRequirements
StrategyStrategy
ArchitectureArchitecture
IAC Draft Material 25
Technologies to Support CBA are Here Today
J2EE Technical
Architecture
.Net Technical
ArchitectureEAI
Web Services
Portals
Directory Services
IAC Draft Material 26
Repository: Sharing & Managing Software Assets
Application Development Group
Commercial Catalog
Agency Specific Catalog
SpecifyBuild
Productize
Find
Evaluate Consume
Publish
Publish
Federal-Wide Catalog
User View
Com
ponen
t R
ep
os i
t or y
IAC Draft Material 28
Recommendations for Transformation to CBA
DiscoveryDiscovery
RequirementsRequirements
AcquisitionAcquisition
StrategyStrategy
ArchitectureArchitecture
IntegrationIntegration
ExecutionExecution
Update Policy &Drive Cultural Change
Reform COTSProcess
Define SDLC FW
Obtain Executive
Buy-In andSupport
Establish Management
Structure and Control
Define anArchitecture
Processand Approach
Develop Baseline Enterprise
ArchitectureDevelopTarget
Enterprise Architecture
Develop theSequencing Plan
Usethe
EnterpriseArchitecture
Maintain the Enterprise Architecture
Section 3.1
Section 3.2
Section 4
Section 5
Section 5
Section 5
Section 6
Section 7
Controland
Oversight
Controland
OversightUpdate EA Process
XML•Parse•Transform•Route•Manipulate
XML
DB
App
App
ServiceProvider
•SOAP•WSDL
•UDDI•ebXML
App
ServiceProvider
ServiceProvider
ServiceBroker
ServiceRequestor
ServiceRequestor Adopt
Common Infrastructure
Depart. A
Agency
Depart. C
Agency
Agency
Agency
Establish Solution Center
Interoperability
Define Interop. Standards
Initialization Ongoing Activities
Ongoing ActivitiesInitialization
OMB Process
Agency Processes
Ongoing ActivitiesInitializationOngoing ActivitiesInitialization
Ongoing ActivitiesInitialization
Phasing of Recommendations
IAC Draft Material 30
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
ComponentIntegration Lab
Collaboration Forum
Process Center of Excellence
IAC Draft Material 31
Update EA & SDLC Processes
Integrate CBA into Enterprise Architecture & Solutions Development Framework
Initiation Ongoing
OMB
Agency
IAC Draft Material 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
IAC Draft Material 33
Adopt Common Infrastructure
Establish Technical Infrastructure (TRM), Acquire Appropriate Tools, Implement Component Repository
Initiation Ongoing
OMB
Agency
IAC Draft Material 34
Define Interoperability Standards
Establish Policies, Procedures, Technology Options for Interoperability & Information Sharing Across Agencies
Establish Interoperability Standards: Technology & Semantics (TRM)
Repository Create Interoperability
Plan Template
Monitor Emerging Standards
Update TRM
Establish Runtime Platform (Based on TRM)
Adopt Interoperability Standards
Produce Interoperability Plan
Apply standards to new projects
Incorporate standards into major infrastructure programs
Initiation Ongoing
OMB
Agency
IAC Draft Material 35
Update Policy & Drive Organizational Change
Organizational Change is Difficult: Treat Transformation as Change Management Project
Define Outcomes & Targets for Agencies
Create Project Template for Organizational/Cultural Change
Define Evolution Phases to CBA Maturity
Monitor Agency Progress
Create & Implement Change Management Program
Establish Training & Awareness Program
Establish Incentive/ Reward Program
Generate Frequent, Incremental Successes to Maintain Momentum
Reward/Promote Those Who Successfully Implement the Change
Initiation Ongoing
OMB
Agency
IAC Draft Material 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