Transcript Title — Times New Roman 28pt, line spacing .85 Title 2

Making Architecture Come Alive:
Integrating EA with Solution Design and
Development
12th Annual Enterprise Architecture Conference
Washington Convention Center
Washington, DC
October 7, 2014
Agenda
Meet the Panel
Framing the Discussion:
• Aspiration vs. Reality: When EA becomes “DoA”
• Linking EA with Solution Delivery
IRS Case Study:
• EA as Change Driver
• Critical Success Factors
• EA in the System Development Lifecycle
Panel Discussion: Making Architecture Come Alive
Audience Q&A
1
Meet the Panel
Nitin Naik, Internal Revenue Service
Dr. Naik is an information systems
leader with extensive experience
in applying technology to business
problems, including the last 15
years in various senior IT
management positions. Presently, he serves as
Technical Director for Strategic Planning and
Technical Direction at the IRS, where he leads and
oversees the IT architecture, engineering and
innovation efforts for major programs.
Moderator
Adam Rubinson, Deloitte Consulting LLP
Mr. Rubinson, Deloitte’s Federal EA
Capability Leader, is a Certified
Enterprise Architect (TOGAF, FEAC,
Zachman). A former government
Deputy CTO, he has over 15 years
experience leading large-scale EA, solution
architecture, IT strategy, systems development,
and business transformation programs at the
federal, state, and local levels.
Randy Covert, Deloitte Consulting LLP
Mr. Covert is a Director in Deloitte’s
System Integration practice,
specializing in solution architecture,
design, development, and integration.
He has 29 years of experience in the IT industry,
and has worked with major government agencies
dealing with financial systems and tax and
revenue management functions, within the US
and globally.
2
EA Aspirations
Federal EA programs seek to proactively drive
business improvement, while achieving
efficiencies, across the enterprise.
EA Vision
Outcomes
Challenges
However, numerous challenges can make it
difficult to actually realize these goals.
3
EA Realities
Many Federal EA programs often find themselves:
•
Focusing mainly on compliance, reactive governance, and enforcement of IT standards.
•
Perceived as not fully relevant by, collaborative with, or actionable for large business
transformation programs that are managed by the lines of business.
•
Creating EAs that are “lost in translation” between enterprise architectures, project-level
designs, and implemented solutions.
•
Encountering portfolio and investment decisions that were not driven by the EA.
•
Lacking the in-house expertise to truly guide or manage detailed engineering and life cycle
activities that build and deliver real systems.
•
Unable to prevent large business transformation programs from failing to meet goals for
budget, schedule, quality, and expected mission value.
Lack of integration with
solution design and
development can mean
one’s EA is “DoA”
(Dead on Arrival)
4
Making Architecture Come Alive
Requires a proven approach integrating activities across the architecturedevelopment continuum.
1
Enterprise & Segment
Architecture Development
2
Preliminary phase where
enterprise business and IT
strategies establish the EA and
portfolio of transformation projects.
Define
Business
Vision & Value
Drivers
4
Define &
Assess
Capabilities
Portfolio
Organize, Validate
& Plan
Develop EA
Transformation
Models
Evaluation &
Optimization
Evaluate results of each
project implementation,
assess potential changes,
re-initiates cycle as needed.
Develops the Solution Architecture,
and develops the Program
Roadmap describing transition
states.
Document
Current
State
Develop
Solution
Architecture
Define Solution
Projects &
Transition
Roadmaps
Asses Results
& Conduct
Architecture
Change
Management
Solution Architecture
Development
Enabling
Disciplines
·
Organizational
Change z
·
Domain Expertise
·
Requirements &
Engineering
Align
During SDLC
Construction
& Transition
Align Design
Artifacts
During SDLC
Elaboration
Develop Program
Roadmap
Establish
Implementation
Governance
During SDLC
Inception
3
Design & Delivery
Governance
Bridges architecture to design,
and aligns with each phase of
the SDLC.
Addresses critical success factors across
all relevant life cycles
5
Copyright © 2013 Deloitte Development LLC. All rights reserved.
Making it Work
Case study: Internal Revenue Service (IRS)
6
EA as Change Driver
How the IRS central EA function coordinates solution architecture and designs
across large IT Programs.
Security
PMO
Privacy
Architect
Engineer
Develop
Test
Responsible
& Approve ELC
Consulted
& Approve ELC
Consulted from Proofof-Concept to Final
Code
Consulted for
Use Cases and
Performance
Engineering
Operations
Consulted and
Define Technical
Strategies
Promotes alignment and manages successful outcomes.
7
Critical Success Factors for EA at the IRS
To be successful, our approach:
• Focuses on the use of common standards, technical design patterns, and
common methods and governance tools to support project implementation
teams.
• Places responsibility for requirements and engineering into the same group that
develops and sustains the EA.
• Focuses on the identification of commonality of IT capabilities across lines of
business, and the promotion of common services to support those capabilities.
• Nurtures close collaboration between solution architects and SDLC engineers on
solution design with appropriate performance Service Level Agreements (SLAs).
• Thinks beyond our immediate project: Promotes enterprise approaches, ideas,
models, concepts, terminology, and re-usable design assets that inspire an
ecosystem of related transformation projects.
8
EA in the SDLC at the IRS
Major business programs require strong EA guidance. Examples include:
• Affordable Care Act
• Foreign Account Tax Compliance Act
• Information Returns Ecosystem
• Masterfile Data Management and Processing.
The IRS continues to leverage Solution Architecture and EA Architects to guide
and support SDLC implementation teams. The EA program:
• Is actively involved in the SDLC and not just in reviews and governance
• Brings industry best practices to bear.
• Translates business requirements and legislative mandates into re-useable IT
capabilities, design patterns and common services.
• Provides approach that includes development of common enterprise data
models, XML standards, web services standards, common services, design
patterns, technology standards and other technical strategies.
9
Panel Discussion
Making EA Come Alive
10
Audience Questions
11
Government Contact
Dr. Nitin Naik
Internal Revenue Service
[email protected]
12
Copyright © 2013 Deloitte Development LLC. All rights reserved.
Contact
Adam Rubinson
Fed Technology Strategy & Architecture
Deloitte Consulting LLP
+1 202 491 7005
[email protected]
13
Randy Covert
Fed Systems Integration
Deloitte Consulting LLP
+1 240 281 7641
[email protected]
Copyright © 2013 Deloitte Development LLC. All rights reserved.