The IA Framework - Information Assurance Architecture - page 33

table 2.2 iA 2 principles (Continued)

IA 2 Principle Definition

Results oriented Establish and maintain focus on the end product,

service, or deliverable to keep the architectural
process focused on results.

Scalability Able to accommodate single systems or large, complex

solutions; that is, if it can work for 1 or 2, it can work
for 100 or 200.

Traceability Link business requirements to services to mechanics

to vendors to products to implementation best
practices to operations; formal recording of the IA 2
line of sight.

C&A, COOP); enterprise architecture's current state and desired state, plus tran-
sition states; business process architecture; and technical process architecture. See
appendix F for an example of the NIST compliance documents for information
and information technology security.
To achieve a well-rounded perspective on business drivers, good business prac-
tice is the complement to compliance requirements. Compliance requirements
describe the minimum (do at least this much to adhere to laws, regulations, etc.).
Good business practice requires additional activity to meet business objectives.

2.9 Aligning iA with elCM

he ELCM applies across the enterprise for business functions, workflows, and
services as well as technology. Each of these has a conception, a design, an imple-
mentation, an operation, and an ending. The specifics of architectural drivers,
architectural views, IA core principles, and compliance requirements will vary
according to the current phase of the ELCM. For example, the ELCM design and
development phases find the IA 2 systems and applications development view more
prevalent than during the operations phase.
Figure 2.4 shows a taxonomic alignment between the ELCM and IA. A taxo-
nomic alignment is not a direct one-to-one relationship; rather, it is a many-to-
many relationship, where any one phase in the ELCM may align with any aspect
of IA. IA 2 views assist to guide IA considerations. Each ELCM phase may have
different IA considerations that are entirely situation dependent. The differences in
IA considerations are what categories and elements of IA to consider (breadth of

See glossary for an expansion and explanation of acronyms.
ELCM is a more abstract but similar view of solutions life cycle management, systems life cycle
management (SLCM), or system development life cycle (SDLC).