Transcript CAF Presentation 12082004

An Overview of the Chief Architects Forum
Ira Grossman
National Oceanic and Atmospheric Administration
December 9, 2004
Department of the Treasury
Agenda
What is CAF?
Progress To Date
CAF 2005 Meeting Schedule
January 6, 2005 Meeting - EA Dictionary/Glossary
Conclusion
1
What is CAF?
The Chief Architects Forum serves as a formal
mechanism for the voice of the Chief Architect
Community to be heard by the AIC Leadership, CIO
Council, and OMB.
The Forum is comprised of Chief Architects from federal
government agencies.
Provides an opportunity for Chief Architects to get
together to share real world experiences and identify
specific issues to promote EA successes.
2
The Chief Architects Forum
The CAF meets quarterly and focuses on topics that are
relevant to advancing the practice of EA.
During the meetings, participants are facilitated in small
group breakout sessions on various EA topics.
A discussion summary of the meeting is prepared, which
includes analysis, and is disseminated to the CAF
community via the CAF list serve.
The summary is also sent to the AIC Leadership.
3
Progress To Date
2004 CAF Meeting Summaries
4
CY 2005 Meeting Schedule
January 6, 2005
– Participate in a breakout session to
begin collaboration among
Agencies to derive at a Strawman
common set of EA definitions that
can be used by all Federal
Enterprise Architecture
constituencies
– Create a forum for shared ideas and
feedback from each agency on its
EA and compare similarities among
agencies.
– Outcome: Working draft EA
Dictionary/Glossary (Version 1.0)
May 12, 2005
July 7, 2005
October 27, 2005
• All the meetings will be held at
NOAA in Silver Spring, Maryland
from 1- 4 pm.
• The meetings are Government only
- Chief architects and government
support staff.
• Industry participation is welcome
by CAF invitation only to
companies who are members of the
Industry Advisory Council.
January 6, 2005 Meeting: Objective and
Tentative Agenda
The objective of this meeting is to begin to develop a draft Dictionary/Glossary
of Enterprise Architecture Terms and Terminologies that the Government could
then refine and publish as a de jure standard to be used across the federal
government
EA Definition Session
January 6, 2005
A. Welcome Introduction – Ira Grossman (2 minutes)
B. Meeting Objectives – Michael Farber (5 minutes)
C. Presentation by Dick Burke, Chief Architect, OMB-FEAPMO (10
minutes)
D. Small Group Break out Sessions (60 minutes)-EA Glossary
E. Break (10 minutes)
F. Report Outs from Small Groups (30 minutes)
G. Group Discussion (60 minutes)
H. Concluding Remarks (3 minutes)
Draft EA Dictionary/Glossary
The Industry Advisory Council will prepare a strawman
draft EA Dictionary/Glossary to be introduced at the
CAF Meeting.
This dictionary will be used in small group break-outs
and will be refined and will serve as the basis for the
Draft Version 1.0 of the EA Dictionary/Glossary
The dictionary will contain an edited set of
terminologies and terms
The draft EA Dictionary/Glossary Version 1.0 will be
placed on the Wiki to give constituents an opportunity
to improve the definitions after the CAF meeting
7
EA Dictionary/Glossary Categories
Meta EA Definitions
Business Architecture Definitions
Data Architecture Definitions
Information Architecture Definitions
Application Architecture Definitions
Infrastructure Architecture Definitions
8
Meta Enterprise Architecture Definitions
–
Architecture
– Gap Analysis
–
Architecture Framework
– Information Technology
–
Baseline Architecture (As-Is
Architecture)
– IT Principle
–
Best Practice
–
– Linkage
Capability Maturity Model
–
– Methodology
Collaboration
–
– Migration Plan
Constituent
–
– Model
Elevator Speech
–
– Ontology
Enterprise
–
– Reference Model
Enterprise Architecture Capability
Maturity Model
– Relationship
–
Enterprise Architecture Model
–
Federal Enterprise Architecture
–
Federated Enterprise
–
Federation
–
Framework
– Line of Sight
– Repository
– Semantic Ontology
– Sequencing Plan
– Target Architecture (To-Be
Architecture)
Business Architecture Definitions
–
Action
– Milestone
–
Analysis
– Mission
–
Business
– Objective
–
Business Capability
– OMB Circular No. A-11 Section 300
–
Business Question
– Opportunity
–
Cause
– Performance Metric
–
Capital Planning and Investment Control
– Policy
–
Critical Success Factor
– Problem
–
Conclusion
– Program Management
–
Condition
– Project Management
–
Decision
– Recommendation
–
Earned Value Management
– Requirement
–
Exhibit 300
– Risk
–
Finding
– Rule
–
Goal
– Strategic Plan
–
Key Performance Indicator
– Strategic Requirement
–
Lines of Business
– Success Factor
–
Measure
– Vision
Data Architecture Definitions
– Association
– Information Exchange Package
– Business Context
– Meta Data
– Business Data Flow
– Query Class
– Data
– Resource Class
– Data Base
– Resource Description
– Data Class
– Security Context
– Data Dictionary
– Service Class
– Data Element
– Service Context
– Data Element Description
– Subject Area
– Data Object
– Subject Class
– Data Property
– Subject Context
– Data Property
– Super Type
– Data Representation
– Unique Identifiers
– Data Store
11
Information Architecture
– Attribute
– Information Object
– Exchange Class
– Information Process
– Exchange Payload
– Module
– Function
– Product
– Information
– Product Item
– Information Exchange
– Product Line
– Information Group
– Service
12
Applications Architecture
 Application
 Application Building Block
 Application Function
 Application Type
 Component
 Service
 Software
13
Infrastructure Architecture Definitions
– Application Environment
– Hardware
– Blade
– Handheld Computer
– Broadband
– High Performance Computing
– Cellular (Mobile) Phone
– Hub
– Computer
– Interface
– DBMS
– Internet
– Disk
– Internet Cloud
– Equipment
– Internet Protocol (IP)
– Ethernet
– Internet Two
– Gigabit
– Laptop Computer
– Local Area Network
14
Infrastructure Architecture Definitions
– Mainframe
– Service System
– Memory
– Specification
– Metropolitan Area Network
– Storage
– Middleware
– Switch
– Network
– Transmission Control Protocol,
(TCP)
– Network Router
– Operating System
– Peripheral Equipment
– Personal Digital Assistant
– POTS (Plain Old Telephone System)
– Protocol
– Server
– Technology Function
– Technology Item
– Telecommunications
– Voice Over IP
– Wide Area Network
– Wireless LAN
15
January 6, 2005 Meeting: Development and
Approval Process for EA Glossary
16
Conclusion
The CAF is an active body and its success is dependent on your participation.
Please feel free to contact the CAF Planning Team for further information about
upcoming meetings.
Chief Architects Forum (CAF) Planning Members:
Ira Grossman, Chief Architect
National Oceanic and Atmospheric Administration,
Department of Commerce
[email protected]
Mary McCaffery, Senior Advisor, Assistant
Administrator
Environmental Protection Agency
[email protected]
Stephen Lowe, Senior Enterprise Architect
Department of Housing and Urban Development
[email protected]
John Sullivan, Chief Architect,
Environmental Protection Agency
[email protected]
Roy Mabry, Governance Subcommittee Co-Chair,
Senior Enterprise Architect
Office of the Secretary of Defense, Department of
Defense
[email protected]
Susan Turnbull, Senior Program Advisor,
Office of Intergovernmental Solutions and
Office of Citizen Services and Communications
General Services Administration
[email protected]
Pat Heinig, Chief Enterprise Architect
Bureau of Industry and Security,
Department of Commerce
[email protected]
17
Background
18
The Chief Architects Forum
What is the purpose of CAF?
– To assist Chief Architects in improving the practice and usefulness of
architectures in their agencies and in the Federal Government at
large.
What is the philosophy of CAF?
– The belief that federal – wide EA success rests squarely on the
success of the individual and departments.
19
Planning for the CAF
The CAF planning team meets on a bi-monthly basis to
prepare for quarterly CAF Meetings.
20
January 6, 2005 Meeting: Action Steps
Preparation for Meeting
Discuss ideas with individual agency
Bring notes on important talking points for small groups
During Meeting
Meet in small groups to brainstorm
Take notes on terminology and share individual agencies’ perspectives
Select a representative to summarize group findings
Present findings to larger group
After Meeting
Take findings back to individual agency
Prepare agencies perspective on findings and prepare to participate in revision sessions
21