4.2: Scope
Define the Scope of the Architecture Other Information:
It is critically important that EA development be approached in a top-down, incremental manner, consistent with the hierarchical
architectural views that are the building blocks of proven EA frameworks, including the ones discussed later in this guide.
In doing so, it is equally important that the scope of the higher level business views of the EA span the entire enterprise
or agency. By developing this enterprise-wide understanding of business processes and rules, and information needs, flows,
and locations, the agency will be positioned to make good decisions about whether the enterprise, and thus the EA, can be
appropriately compartmentalized. Without doing so, scoping decisions about the EA run the risk of promoting "stove-piped"
operations and systems environments, and ultimately sub-optimizing enterprise performance and accountability. Other considerations
relevant to defining the scope of the EA include, but are not limited to: • Relevance of activities, functions, organizations,
timeframes, etc. • Enterprise scope (intra-and inter-Agency domains) • Operational scenarios, situations, and geographical
areas to be considered • Projected economic benefits • Projected business and technical risk areas • Projected availability
and capabilities of specific technologies during the target timeframe (applies to target architecture only). Defining the
scope leads the planners to project management factors that will contribute to these determinations, including the resources
available for building the architecture as well as the resources and level of expertise available for analysis and design
tasks.
Indicator(s):
|
