SecurE-Biz Conf 4-1-..
21
1 Using the SRM to Succeed with Component-Based Architectures Dave Mayo Vice President Everware [email protected] John Weiler Executive Director Interoperability Clearinghouse [email protected] April 1, 2003
description
Transcript of SecurE-Biz Conf 4-1-..
1
Using the SRM to Succeed with Component-Based Architectures
Dave MayoVice [email protected]
John WeilerExecutive Director Interoperability Clearinghouse
April 1, 2003
2
Agenda
• Current IT Issues• CBA: Concepts & Context• Business Drivers & Benefits• FEA Service/Component Reference Model• Enablers & Critical Success Factors• Recommendations for Transformation• Discussion
3
Current Issues in Federal IT
• Most IT development projects fail or never deploy• Many Federal EA methods are neither business aligned
nor actionable.• Legacy systems inflexible, stove-piped• Many systems not designed for interoperability• OMB seeks to establish a common EA framework• OMB has directed an Component Architecture
Approach
4
New IT Solution ParadigmCustom Development gives way to Application Assembly
Y e s t e r d a yDesign, 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 yArchitect, Acquire, Integrate
Services Oriented Architecture dictatesComponent-Based
SDLC process
Softw
are C
ompo
nent
s
& Off th
e 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
5
Component-Based Architecture: Concepts
• Services Oriented Architecture– Way of thinking about systems as set of modular
services: business, data, infrastructure• CBA
– Modular EA Process for Value Chain Alignment– Approach to structuring enterprise solutions– Focus on component assembly – Origins in OO and CBD– Fits within Federal Framework of Reference Models – Facilitates alignment of business with technology (via
SRM)– A CSF for OMB FEA-PMO, and FEAMS
6
Business Drivers & Benefits
• Increased Modularity, 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• Enables establishment of common EA terms and
specifications or “building codes”
7
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
Source: Butler Group
8
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):Reference Models
9
FEA Service Component Reference Model
Customer Services
Process Automation Services
Business Management Services
Digital Asset Services
Business Analytical Services
Back Office Services
Com
mon
Ser
vice
sCr
oss-
Cutti
ng S
ervi
ce A
reas
(i.e.
, Sea
rch,
Sec
urity
)
ServiceTypes
Service Layers
Components
PerformanceMeasures
BusinessProcess
Access and Delivery ChannelsConceptual
10
Services/Components Reference Model
• Identify & Classify Horizontal & Vertical Service Components
• Base of Common Terminology and Structure for Services & Components
• Source of Information for Enterprise Architects to Align Service Oriented Architectures
• Vehicle for Agencies to Collaborate on Service Definition and Development
• Mechanism for Agencies to Locate Candidate Components for Use/Reuse
11
Exploiting Service/Component Reference Model
SRM / FEAMS
Component Repository
IdentifyCollaboration
Partners
Consume Service
Component
AlignService
Definitions
RegisterService
Component
EnterpriseArchitect
ApplicationDesigner
CIO CouncilSAWG
Set UpClassification &
Mappings
12
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 1Business Segment 2Business Segment 3Business Segment 4
Gov. Analyst
13
CBA: Driven by BRM and Implements SRM
BRMCBA CBA Layer 1
CBA Layer M
BRMSRM Service Layer 1
Service Layer N
BRMBRM Business Lines
Sub-functions
Cont
ribut
ion
to F
ulfil
lmen
t
Func
tiona
l Tra
ceab
ility
14
Service Architecture Layering
BRMPlatform Components
Business Subdomain Components
Application Specific Components
Common Business Components
Infrastructure Components
Busin
ess
Infra
stru
ctur
e
15
Enablers and Critical Success Factors
• Enablers– Technologies Exist to Enable CBA– Commercial components available– Standards & Best Practices Exist - Adopt them– BRM/SRM are the starting point
• Critical Success Factors– Value Chain Driven EA Approach– Revised Solution Development Lifecycle focused on
COTS/GOTS acquisition & integration– IT Portfolio Management – Mechanism for sharing and reusing software assets and
components
16
IAC Recommendations for Transformation to CBA
Reform COTS Process
Update Policy &Drive Cultural Change
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 & SDLC
Processes
XML•Parse•Transform•Route•Manipulate
XML
DB
App
App
ServiceProvider
•SOAP•WSDL
•UDDI•ebXML
App
ServiceProvider
ServiceProvider
ServiceBroker
ServiceRequestor
ServiceRequestor
AdoptCommon Infrastructure
Depart. A
Agency
Depart. C
Agency
Agency
Agency
Establish Solution Center
Interoperability
Define Interop. Standards
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
Define Ref.Model Linkages
17
Application Development Group
Commercial Catalog
Agency Specific Catalog
SpecifyBuild
Productize
Find
Evaluate Consume
Publish
Publish
Federal-Wide Catalog
User View
Com
p one
nt R
e pos
it ory
Repository: Sharing & Managing Software Assets
18
OMB’s Draft SDLC needs to be vetted with industry 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 Stakeholders, 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 & Acquire GOTS/COTS Components
Define Component Relationships to BRM/SRM Wiring & Activity Diagrams, Component Arch, Data Arch To-Be architecture ‘blueprints’
Prototype Solution Architecture Verify ROI, business fit Conduct Integration Testing
Iterative DevelopmentValue-Based Releases
Understanding theBusiness
Knowing What’s Possible
Model the BusinessDefine the Gaps
Develop the“Blueprints”
Obtain Components
Assemble theComponents
Execution Deploy Manage re-Baseline
Execute &Deploy
Discovery
Requirements
Strategy
Architecture
John C. Butler
Why isn't acquire in with Acquisition?Doesn't acquisition include development if needed?Shouldn't Execution be Delivery or Deployment?
19
Establish CBA Solution Center
Foster Use of Common Services/Components Across Agencies
ProcessCOE
ComponentIntegration
Lab
CollaborationForum
CBASolutionCenter
ProcessCOE
ComponentIntegration
Lab
CollaborationForum
CBASolutionCenter
CBA Best Practices, Business Process Patterns, Linkages to Reference Models
Build Consensus on Process & Data Factoring
COTS/GOTS Evaluation, Common Components, Certification of
Components
20
Thank You.
21
Contact Information
For more information about IAC, go towww.iaconline.orgFor more information about the IAC EA SIG,
please contact Kay Cederoth at: [email protected] more information on each of the IAC EA SIG White Papers, go to: http://www.ichnet.org/IAC_EA.htm
