1. What is Enterprise Architecture?
Enterprise Architecture (EA) is a blueprint for improving, reengineering, and integrating best practice capabilities into programmatic and system solutions for emerging business needs. More specifically, it is a framework which outlines processes, tools, techniques, and their relationships to determine current and future needs across the enterprise to meet tactical and strategic objectives.

2. HRM EA can: Help manage information technology (IT) investments;
Serve as a common lexicon of operational activities, capabilities, system functionality, and operational roles across the human resources community;
Provide an overarching framework for future HRM program development and enhancement;
Support alignment of IT with business objectives;
Support acquisition processes;
Foster interoperability among HRM, other federal agencies, and business partner systems;
Serve as a Capstone Architectural Framework for all HRM;
Serve as an enabler for conducting and documenting Continuous Process Improvements and Lean Six Sigma efforts across the HRM Core Business Mission.

3. Information Flow
Boundaryless Information Flow achieved through global interoperability in a secure, reliable and timely manner
“Boundaryless does not mean there are no boundaries – it means that boundaries are permeable to enable business.”

4. TOGAF - The Continuing Story
The Zachman Framework
Version /03
What?
Data
How?
Function
Where?
Network
Who?
People
When?
Time
Why?
Motivation
Planner’s Viewpoint
Contextual
Architecture principles
Validated principles
Approved statement of architecture work
Validated principles
Business functions
Correlation of organization
and function
Validated principles
Organization
structure
Business goals
and objectives
Business roles
Business principles goals & drivers
Refined Business principles goals & drivers
Scope
Owner’s Viewpoint
Conceptual
Target data architecture
Gap analysis results
Business architecture version 1
Data model managem’t
view
Business baseline version 1
Business processes
Business services
Enterprise
Models
Designer’s Viewpoint
Logical
Common application services view
Target application architecture
Applications information view
Application information view
Technology architecture version 0.3
Technology architecture version 0.2
Data security view
Applications interoperability view
Application interop. view
Data lifecycle view
Data dissemination view
Technical architecture version 1
Technical baseline version 1
Application user location view
Technical require-ments
Constraints on technology architecture
Technical require-ments
Systems
Models
Builder’s Viewpoint
Physical
Gap analysis results
Technology architecture version 0.4
Technology architecture version 0.1
Technology
Models
Sub-contractor’s Viewpoint
Out-of-context
Detailed
Representations
Functioning Enterprise
Actual
Systems
TOGAF - The Continuing Story
TA P12

5. Architecture Development Cycle (ADM Cycle)
The Open Group Architecture Forum(TOGAF)
Start with a foundation architecture
Follow the phases of the ADM
Results in
an organization-specific architecture
more reusable building block assets in the Enterprise Continuum
Each iteration becomes easier and has more reusable building blocks to use
Every phase is validated against and validates the current requirements of the business

7. The position of IT Architects
TOGAF - The Continuing Story
Version /03
The position of IT Architects
How do I know what I want, when I don’t know what you can do for me
We know solutions to every problem? What’s your problem?
TOGAF - The Continuing Story
TA P12