EGovernment Architectures

1

• E-Government Architectures
• Solution Architecture Development Life Cycle
  (SDLC) for E-Government Initiatives
• Architecture Roadmap and E-Gov Documents

Federal Enterprise Architecture Program
Management Office (FEAPMO) Solutions Architect
Working Group (SAWG) December 13, 2002 Revision
11
2
Table of Contents

• Goals and Objectives
• SDLC Roadmap, Activities, and Documents
• SDLC Timeline
• Appendix A Templates

3
The FEAPMO SDLC supports the architecting,
development and implementation of E-Gov
Initiatives
Goals and Objectives

• To compliment existing (agency) SDLC
  methodologies
• To provide a common framework supporting the
  architecting, development and implementation of
  cross-agency E-Gov initiatives
• To increase the speed of transforming E-Gov
  requirements into tangible solutions that provide
  rapid return on investment (ROI)
• To provide a process to enable Component-Based
  Architectures and the reuse of solution
  architectures
• To provide agencies with a solution road-map that
  outlines the entire solution development
  lifecycle, activities, documents, deliverables,
  and templates for justifying and managing IT
  investments
• To create a framework focused on performance and
  measurable outcomes

4
The SDLC provides agencies with a common
framework to iteratively answer todays hardest
E-Gov questions
Typical Cycle of E-Gov Questions
Has anyone else solved this problem already?
What are we going to deliver?
How will I buy it
Subsequent Releases
What we know (prior to validation)
How much will it cost?
How are we going to deliver it COTS vs GOTS?
When are we going to deliver it?
What we dont know (after validation)
5
The SDLC consists of parallel strategic,
business and implementation efforts that
continually measure and evolve the initiatives
value
Conceptual
SDLC - Overview
Strategic Planning

• IT Capital Planning
• Enterprise Architecture Alignment (FEA and Agency
  Specific)
• Definition of Agency Strategic, Business, and
  Performance Objectives

What are we going to deliver?
Business Modeling

• Develop Vision, Performance Measures, Outcomes of
  Initiative
• Establish Partnerships, Initiative Goals and
  Objectives
• Create Business Documents (Business Model,
  Solution Architecture)

Shared/Evolving Vision
Iterative Release of Initiative
How much will it cost?
How are we going to deliver it?
Implementation and Delivery

• Define Products (Portal, Content Management)
• Iteratively Implement Products
• Validate with Stakeholders, Measure Outcomes

When are we going to deliver it?
Iterative Product Releases
Value is captured and measured in iterative
implementations Business strategy evolves based
on lessons learned and customer
feedback Performance is measured
6
To support the iterative implementation of an
E-Gov initiative, multiple activities, documents,
and deliverables were defined

• Knowing what the problem is
• Defining baseline and target performance measures
• Define partners, funding strategies, linkages to
  the FEA

Strategic Planning
Knowing Whats Wrong

• Stakeholder and partner expectations captures
• Define target business requirements and processes
• Solution Architecture (working draft)

Defining the Path
Business Modeling

• Understanding what components / capabilities can
  be leveraged
• Define business components, operations, workflow,
  process
• Solution Architecture (draft)

Finding the Components
Discovery

• Short, mid, and long term requirements defined
• System, functional, data, and interface
  requirements defined
• Component selection criterion established

Requirements
Model the Gaps
Iterations

• Define technical and data architectures
• Align to Agency / FEA
• System, Security and Final Solution Architectures

Develop the Blueprints
Architecture
Implementation (assembling the solution)
Iterations

• Acquisition / purchase of components or services
• Risk, Security, CM, Testing and Project Plans
• Technical Implementation Plan

Management
Create the Plans

• Component Integration / Development
• Testing and Validation
• User Acceptance Testing

Implementation
Assemble the Components

• Change Management Committee
• Validate with customer
• Measure performance, evolve strategy

Execute Deploy
Execution
Documents and Activities
7
The SDLC will accelerate (and validate)
investment return while providing a framework to
support evolving E-Gov requirements
Illustrative
SDLC - Iterative/Value-Based Implementations
Short Term
Mid Term
Long Term
300
Release 5
Release 4
What we dont now
Release 3
Initiative Capabilities
Release 2
Business Requirements
100
Changing Business Requirements
Integration of 2 Business Partners
Release 1
What we do know
Release of Portal
0
Baseline
Implementation Timeline
Validation with the Business and Users
8
Table of Contents

• Goals and Objectives
• SDLC Roadmap, Activities, and Documents
• SDLC Timeline
• Appendix A Templates

9
To support the iterative implementation of an
E-Gov initiative, multiple activities, documents,
and deliverables were defined
Conceptual
SDLC - Activities and Deliverables
Strategic Planning (defining the objective,
alignment to architecture)
1
Business Modeling (setting the vision, business
model, business /solution architecture)
2
Performance Objectives
Validation and Outcomes
9
Implementation and Delivery (selecting and
implementing a product)
Discovery
Requirements
Implementation
Execution
Management
Architecture
Input Strategic and Business Objectives
Output Product / Capability
3
7
8
4
6
5
- Activities
Documents/Deliverables -
10
Develop the business and performance strategy to
support the implementation of the initiative, or
initiative component
20,000 Foot
Strategic Planning (defining the objective,
alignment to architecture)
1
Activities
Artifacts/Deliverables

• Define Performance Gaps, Measures, Objectives,
  and Outcomes
• Define Architecture Alignment (Agency, FEA /
  Reference Models)
• Capture Stakeholder Expectations
• Distribute Questionnaires, Customer Surveys to
  Baseline Performance

• Business Performance Assessment
• Problem Statement
• Baseline Performance Assessment
• Define Target / Outcome Performance
• Managing Partner Document
• Managing and Associate Partners
• Business Line Owner
• Partnering Agreements
• Funding Strategy
• Agency / FEA Alignment Document (PRM)
• Establish Compliance / Regulatory Team

Critical Success Factors

• Knowing what the problem is
• Defining baseline and target performance measures
• Define partners and funding strategy
• Establish linkages to agency and FEA

11
Establish a starting point to build vision and
momentum, define target business requirements,
processes and solution architecture
10,000 Foot
Business Modeling (setting the vision, business
model, business / solution architecture)
2
Activities
Artifacts/Deliverables

• Engage Partners and Stakeholders
• Capture Stakeholder Problems / Expectations
• Define Business Patterns Amongst Partners
• Identify Short, Mid, and Long-term Objectives
• Identify Domain / Industry Best Practices
• Create Target Business Process / Business Flow/
  Business Model
• Connection of IT and Business Dots (Solution
  Architecture)

• Establish Compliance / Regulatory Team
• Vision / Charter Document
• Business Requirements and Process Document
  (Target)
• Program Management Plan (PMP)
• Agency / FEA Alignment Document (BRM)
• Solution Architecture (working draft)
• Partners/Value-Chain, Processes
• Technology / Infrastructure
• Access and Delivery Channels
• Business / Performance Objectives
• Mock-ups / Visualizations

Critical Success Factors

• Capture stakeholders and partners expectations
• Define target business requirements and processes
• Establish team to manage compliance and
  regulatory issues
• Define working draft Solution Architecture

12
Identify existing processes, workflow,
components, and capabilities that can be leveraged
Implementation and Delivery (selecting and
implementing a product)
5,000 Foot
Discovery
Requirements
Management
Implementation
Execution
Architecture
3
Activities
Artifacts/Deliverables

• Capture Cross-Agency / Industry Assets
• Define Existing Processes and Workflow
• Define Processes and Workflow That Needs to be
  Leveraged, Replaced, or Created
• Research Existing Standards, Technology, and
  Service Components (Industry, FEA-SRM / TRM)
• Define New Business Modules and Supporting
  Components

• Discovery Assessment
• Industry Capabilities
• Existing / New Components
• Product Specifications, Performance Metrics
• Business Component and Operations Document
• Selected Components
• Process, Workflow
• Use Cases, UML, Activity Diagrams
• Agency / FEA Alignment Document (SRM, TRM)
• Solution Architecture (draft)

Critical Success Factors

• Understanding of what components / capabilities
  can be leveraged
• Define business components and their operation,
  workflow, and process
• Create draft solution architecture

13
Establish short, mid, and long-term
requirements, define critical success factors,
achieve stakeholder buy-in
Implementation Delivery (selecting and
implementing a product)
2,500 Foot
Discovery
Requirements
Management
Implementation
Execution
Architecture
4
Activities
Artifacts/Deliverables

• Cross-Agency Functionality Matrix (must haves)
• Define Legislative, Compliance Requirements
• Security and Authentication
• Privacy and Legal, Section 508, IATO/ATO
• Define / Review Technical Considerations
• XML Enabled, Web Services, Access / Privilege
  Models
• Define Functional, System, Interface and Data
  Requirements
• Establish process for managing Conflicts of
  Interest

• System Requirements (Target)
• Security, Infrastructure
• Hosting, Compliance
• Technical Considerations
• Data and Information Requirements
• Functional Requirements
• Short, Mid, and Long-Term
• Service / Component Interface Requirements
• Web Service, API, Code, etc
• Interoperability, Integration
• Establish Selection Criterion for Components

Critical Success Factors

• Define short, mid, and long term requirements
• Establish system, functional, data, and interface
  requirements
• Establish component selection criterion

14
Create Solution Architecture / Blueprints
Implementation Delivery (selecting and
implementing a product)
1,000 Foot
Discovery
Requirements
Management
Implementation
Execution
Architecture
5
Activities
Artifacts/Deliverables

• Select Components that Will Be Leveraged
• Create Wiring, Linkages, Activity Diagrams
• Create System Architecture
• Create Data and Information Architecture
• Document Component Interaction, Assembly, Legacy
  Interfaces
• Finalize Solution Architecture Blueprints

• Data and Information Architecture
• Interoperability, Exchange, Archive, Record
• System Architecture
• Network, Infrastructure, Legacy Integration
• Scale, Disaster Recovery, Backup
• Security Architecture
• Solution Architecture (Final)
• Components, Blueprints
• Linkages, Interfaces, and Locations
• Wiring Diagrams, Platforms
• Agency / FEA Alignment Document (TRM, DRM)

Critical Success Factors

• Define Technical and Data Architecture, Align to
  Agency / FEA
• Create System and Security Architecture
• Create Final Solution Architecture / Blueprints

15
Source the necessary solution components,
establish agreements between agencies and vendors
in architecture / support terms
Implementation Delivery (selecting and
implementing a product)
500 Foot
Discovery
Requirements
Management
Implementation
Execution
Architecture
6
Activities
Artifacts/Deliverables

• Create Component Sourcing Strategy
• Purchase / Leverage Service Components
• Define Configuration Management and Associated
  Management Plans
• Create stakeholder Technical Implementation Plan
  to Guide the Implementation of the Initiative /
  Product

• Component Acquisition and Sourcing Plan
• Buy, Borrow, Build, Leverage, Lease
• Component Service Level Agreements
• Configuration Management Plan
• Risk Management Plan
• Security Plan
• Concept of Operations
• Testing Plan, Project Plan
• Technical Implementation Plan (TIP)

Critical Success Factors

• Clear understanding of component and capabilities
  to support implementation / integration
• Acquire/ purchase components or services
• Create risk, security, configuration, testing,
  and project plans
• Create technical implementation plan

16
Implement and test the initiative and/or product
Implementation Delivery (selecting and
implementing a product)
100 Foot
Discovery
Requirements
Management
Implementation
Execution
Architecture
7
Activities
Artifacts/Deliverables

• Assembly / Integration of Components
• Development and Testing
• Support and Maintenance
• User Acceptance Test

• Development / Integration
• Software Development Methodology / Plan
• Branding Guidelines, Design Document
• Data Dictionary
• Hardware and Software Requirements
• User Guides, Administration Guide
• Testing and Validation
• Unit Test, Test Scenarios
• Load, Penetration, and Security Testing
• Release (Version x.0)
• User Acceptance Test (UAT)

Critical Success Factors

• Component Integration / Development
• Testing and Validation
• User Acceptance Testing Customer Approval

17
Launch and support the solution, validate
performance measures, business requirements, and
outcomes with stakeholders
Implementation Delivery (selecting and
implementing a product)
On the ground
Discovery
Requirements
Management
Implementation
Execution
Architecture
8
Activities
Artifacts/Deliverables

• Establish Committee to Manage the Change and
  Updates to the Initiative
• Validate the Business Functions, Processes, and
  Requirements
• Measure Performance Outcomes
• Query Customers for Satisfaction
• Identify Next Round of Changes and/or
  Modifications

• Establish Change Management Committee (CMC)
• Capture Customer Feedback
• Prioritization
• Software / Component Control
• Stakeholder and Business Requirement Validation
  Document
• Performance Outcome Document
• Customer Satisfaction Report / Survey
• Version x.0 (1) Change Recommendations
• Business and Performance Driven

Critical Success Factors

• Established processes (i.e., CMM) to capture and
  prioritize the advancement of the initiative
• Validate initiative / product with customer
• Measure performance, identify change
  recommendations

18
The outcome of Execution assists in driving the
next phase of implementation and/or the selection
of products or components
Strategic Planning (defining the objective,
alignment to architecture)
Execution
9
Business Modeling (setting the vision, business
model, business /solution architecture)
Activities
Artifacts/Deliverables

• Updated Strategic Objectives
• Updated Business Objectives
• Updated Performance Objectives

• Evolve Business Strategy and Performance
  Objectives
• Re-Assess Market / Industry Capabilities
• Expand Value-Chain and Partners
• Define Next Round of Strategic, Business, and
  Performance Objectives

Critical Success Factors

• Evolution of Strategy and Objectives moving
  away from the big-bang approach (i.e., ERP)
• Analysis of market / industry capabilities are
  there new components and/or solutions available?
• Definition of next phase of the initiative or
  product

19
Table of Contents

• Goals and Objectives
• SDLC Roadmap, Activities, and Documents
• SDLC Timeline
• Appendix A Templates

20
The SDLC emphasizes the development of short,
mid, and long-term objectives that support
evolving business strategies
SDLC
Iterative Releases
Iterative Releases
Conceptual
Short Term (0-120 day)
Mid Term (120-180 days)
Long Term (180 days)
Citizen
Citizen
Citizen
Business Partners
Business Partner
Business Consolidation
Integration of Business Partners
Portal Launch
Business Consolidation

• Establish starting point
• Focus on 80 solution
• Query / validate citizen requirements
• Define next phase / release

• Partner integration into Portal
• Reuse of components and services
• Expansion of portal functionality that benefits
  multiple partners

• Integrated Business Processes
• Straight-thru processing
• Web Service Enabled
• Allocation of workforce
• Fast services to citizens

Objectives
21
Example Timeline Launch of Portal (Short Term)
Problem Statement (Business Case i.e. not enough
electronic transactions)
Strategic Objective (Outcome i.e. get more
customers online)
Define Base Metrics (i.e. currently 25 usage)
Align to FEA Performance Reference Model
Define Target Metrics (i.e. targeting 75 usage)
Strategic Planning
Charter Document (Description)
Baseline Business Architecture (i.e. what
existing processes support agency sub-functions)
Target Business Architecture (i.e. what new
processes will support agency sub-functions)
Align to FEA Business Reference Model, and Data
and Information Reference Model)
Functional Requirements Document (including Use
Cases)
Project Management Plan (i.e. Schedule, Budget)
Business Modeling
1 month
2 months
3 months
4 months
0 months
22
Example Timeline Launch of Portal (Short Term)
Define Components (SRM Elements)
Align to FEA Service Component Reference Model
Technology / Component Leverage Model (COTS/GOTS
systems aligned to FEA)
TRM / SRM Metrics Model (i.e. interoperability,
cost, maturity)
COTS/GOTS recommendation model (i.e. best
practices, industry alignment, FEA alignment)
Strategic Planning (completed)
Discovery
System Requirements Document (i.e. security,
infrastructure, compliance)
TRM / SRM Metrics aligned to PRM (i.e. selection
criteria model for COTS/GOTS)
Target System Requirements Document (i.e.
security, infrastructure, compliance)
Baseline System Requirements Document (i.e.
security, infrastructure, compliance)
System Discrepancy Document (i.e. Gap Analysis)
Business Modeling (completed)
Requirements
Align to FEA Technical Reference Model
System Architecture Document (i.e. security,
infrastructure, network)
Short list of potential systems
TRM Technical Requirements Document for COTS/GOTS
TRM Performance Metrics for COTS/GOTS
Software Module/Interface Document (i.e.
software module interfaces to Business
Functions/Processes)
Architecture
1 month
2 months
3 months
4 months
0 months
23
Example Timeline Launch of Portal (Short Term)
Management
COTS / GOTS Usage Agreement Document
Update Project Plan
Technical Implementation Plan (i.e. hosting,
maintenance, launch)
Strategic Planning (completed)
Discovery (completed)
Testing Plan (i.e. human resources, timelines,
technical resources)
Configuration / Change Management Plan (i.e
versioning, feedback)
Risk Management Plan
Business Modeling (completed)
Proof Of Concept (i.e. Technical Feasibility)
Requirements (completed)
User Acceptance Testing (i.e. Functional
Test,Proof of Concept)
Architecture (completed)
Pilot Development (i.e. Business Logic,
Presentation, Unit Testing)
User Acceptance Testing (i.e. Functional
Test, Pilot)
Implementation
Load Testing
Compliance Testing
1 month
2 months
3 months
4 months
0 months
24
Example Timeline Launch of Portal (Short Term)
Update Strategic and Performance Objectives
Iterative Development Methodology
Update Business and Performance Objectives
Update Requirements, Technology / Components,
Leverage Model,
Strategic Planning (completed)
Discovery (completed)
Management (completed)
Implementation (completed)
Business Modeling (completed)
Requirements (completed)
Release 1.0
Architecture (completed)
Update Functional Requirements (i.e. User
Feedback, Prioritization)
Measure Performance (ongoing)
Execution
1 month
2 months
3 months
4 months
0 months
25
Table of Contents

• Goals and Objectives
• SDLC Roadmap, Activities, and Documents
• SDLC Timeline
• Appendix A Templates