Week Learning Sessions Description

1 Introduction On-boarding
Introduction to the Course
2 An Overview of Provides an overview of the discipline of Enterprise Architecture
Enterprise (EA). The main concept of this chapter is that EA is a strategy
Architecture and business-driven activity that supports management planning
and decision-making by providing coordinated views of an entire
enterprise. These views encompass strategy, business, and
technology, which is different from technology-driven, systems-
level, or process-centric approaches. Implementing an EA
involves core elements, a management program, and a
framework-based documentation method.
3 The Structure and Discusses the need for enterprise architects to understand the role
Culture of of organizational structure and culture in developing an EA.
Enterprises Structure and culture are important to include in the EA in order
to accurately reflect the true nature of organizational goals,
processes, and informal structures which influence the current
and future views of the architecture. Understanding structure and
culture are also important in working with stakeholders to gain
their support and manage expectations for the development and
implementation of the EA program. Enterprises are types of
social organizations and as such, the concepts of organizational
theory presented in this chapter are applicable to the practice of
EA.
4 The Value and Discusses the value and risks associated with creating an
Risk of Creating enterprise-wide architecture. The main concepts of this chapter
an Enterprise are that EA represents a different way of looking at resources
Architecture across the enterprise, and that the significant cost of creating an
EA must be justified in terms of the value that it will bring to
users of EA products in their planning and decision-making
activities.
5 The Describes the EA implementation methodology (EA
Implementation methodology), which is a detailed procedure for establishing,
Methodology maintaining and using an EA framework and documentation
Chapter Overview approach. The EA methodology is the first step in coordinating
the EA documentation approach. The value of adopting an EA
methodology is that it reduces the risk of creating an ineffective
EA program and/or inaccurate EA documentation.
6 The Analysis and Defines and describes the purpose of the EA analysis and
Documentation documentation framework, provides examples of existing
Framework frameworks and discusses the EA3 Cube Framework which is a
generalized framework that is suitable for use in public and
private sector enterprises.
7 Components and Defines and describes EA components and artifacts within the
Artifacts context of an EA framework. Using the EA3 Framework as an
example, EA components are replaceable elements within the
 framework that come and go with changes in strategy, business
services, and new designs for resources involving information
flows, applications, networks and other infrastructure.
Descriptions are provided of example EA components at each
level of the framework. Appendix E gives examples of each
artifact.
8 Assessment Case Studies
9 Assessment MT Exam
10 Developing Covers the development of current views of the EA, within the
Current context of a documentation framework and implementation
Architecture methodology. The current architecture is actually a collection of
Views EA artifacts that document existing EA components throughout
the enterprise. Current EA views are important to an enterprise in
that they establish or verify what resources (including IT) are
being used in lines of business to support the achievement of
strategic goals. This becomes a reference baseline much like an
inventory that then supports planning and decision-making
regarding the future architecture.
11 Developing Covers the development of future views of the EA, within the
Future context of a documentation framework and implementation
Architecture methodology. The future views of the EA are important to the
Views enterprise because they capture one or more possible business
and technology operating scenarios, which supports planning and
decision-making. These future operating scenarios are based on
assumptions of capability and strategies for successful
performance in response to internal and external influences. The
creation of future view artifacts is accomplished by using the
planning assumptions in the scenarios and the same
documentation and modeling techniques as were used to develop
the current view artifacts. This allows future view artifacts to be
directly related to current view artifacts at each level of the
framework, so that potential and planned changes are evident,
and various types or combinations of changes can be modeled.
12 Developing an Discusses the development of an EA Management Plan, which is
Enterprise the document that describes how an enterprise will manage the
Architecture transition of its current processes and resources to those which
Management Plan will be needed in the future. This transition from the current EA
to the future EA is an ongoing activity, as new resources are
implemented and therefore become part of the current EA. The
purpose of configuration management and version control are
also discussed, along with the need to provide a sequence for
implementation projects.
13 The Role of Introduces the concepts of the capital planning and investment
Investment control (CPIC) process and its relationship to enterprise
Planning and architecture and project management. The four phases of the
Project CPIC process are described (plan, select, control, and evaluate).
 Management The chapter concludes with a discussion of how a significant part
of IT governance is implemented through the CPIC process.
14 The Role of Discusses the role of security and privacy as part of an EA
Security and program and architecture. Security is one of the vertical
Privacy “threads” that has an impact at all levels of the EA framework.
The enterprise’s Security and Privacy Program is described in
four basic parts: information security, personnel security,
operational security, and physical security. The chapter also
covers discusses the role of security and privacy as part of risk
management and the elements of an example Security and
Privacy Plan.
15 The Enterprise Describes the role of an on-line EA repository and support tools
Architecture in the EA program and the documentation of EA components.
Repository and The design and structure of an EA repository is discussed, and
Support Tools the relationship to an underlying EA documentation framework.
The example of the EA3 Cube Framework and the Living
EnterpriseTM repository design is used in this discussion.
Additionally, different types of EA documentation and support
tools are discussed in the context of developing EA component
documentation and populating the on-line EA repository.
16 Future Trends in Provides the author’s thoughts on future trends in the profession
Enterprise and practice of enterprise architecture, based on readings and
Architecture observations during work on EA projects. This is done to give
the reader a sense of the issues that are currently of interest to
enterprise architects and organizations considering EA programs.
These comments are also intended to help promote discussion in
each topic area as well as to encourage the adoption of a common
language for EA greater collaboration among those in the
profession.
17 Assessment Case Studies
18 Assessment Final Term Exam