Information Technology Reference
In-Depth Information
−
Infrastructure
Technical
Physical
Intraorganizational (internal)
Interorganizational (external)
IA core principles
Confidentiality-integrity-availability (CIA)
Possession-authenticity-utility (PAU)
Privacy-authorized use-nonrepudiation (PAN)
Compliance requirements
Enterprise life cycle management (ELCM)
Supporting constructs
For example, IA operations framework
Compliance verification
Line of sight
n
n
−
−
n
−
−
−
n
n
−
n
n
n
The following sections elaborate the IA
2
F.
2.4 iA
2
Architectural Driers
The root motivation behind technology is business need. Business risk is a direct
outgrowth of business need, and is the root driver behind IA. The two macro-level
IA
2
architectural drivers are
business drivers
and
technical drivers
. Technical drivers
are distinct from business drivers; however, both find root in business need. Two
good architectural principles are
no business need, no technology
and
no business risk,
no IA
.
2.4.1
Business Drivers
Business drivers come out of mission statements, organizational strategies, and
compliance requirements; organizational policies convey business drivers to the
organization in everyday language. Enterprise architecture must align business
requirements with services and mechanisms that will fulfill those requirements.
IA
2
must align business risks with the IA services and IA mechanisms that mitigate
those risks.
Two of the many ways to characterize business drivers are in financial terms
and in terms of enterprise need. Chapter 12 contains additional details on the ROI
framework and the enterprise perspective of an IA
(EPIA) framework. These frame-
See glossary for definition of construct.
See Section 2.8 for an elaboration on compliance requirements.
