DSCA180A 57520001-GY DSCA 180A 通信处理器

DSCA180A 57520001-GY DSCA 180A 通信处理器 

利益相关者；因为目标和目的定义了架构创建的目的
以及架构的级别。确定工作范围也决定了水平
数据收集和信息呈现的复杂性。
体系结构开发还需要了解外部需求，这些需求可能：
对建筑创作的影响。为内部机构目的开发的架构仍然
需要可映射并与更别的体系结构保持一致，并可映射到
国防部EA。对于某些架构开发，必须考虑数据收集
以及满足其他外部要求的图形表示，如向上
报告和提交架构数据和模型，以供项目审查、资助
由于所提议的解决方案的敏感性或美元价值。
本网站包含指令要求的特定视图的数据收集指南，
法规或其他监管指南（即，附件53或附件300提交文件；OMB
分系统架构审查或互操作性要求）。
体系结构范围界定必须有助于与决策过程保持一致，并支持决策过程
终的任务结果和目标如下图所示。建筑的
通过将原始数据组织成有用信息创建的数据和支持视图，以及
收集到有用的观点中，应使领域专家、项目经理和
决策者利用架构定位、识别和解析定义，
属性、事实、约束、推论和问题，包括体系结构内部和跨体系结构
冗余、冲突、缺失和/或过时的边界。DoDAF V2.0提供
灵活地开发适合用途的视图（用户开发视图）和来自
DoDAF描述了大化各级决策能力的模型。这个
下图显示了架构的开发如何支持管理决策
过程在本例中，该示例显示了架构如何在分析中使用
可以促进确定和/或验证任务结果的能力。
分析还揭示了变化的影响和影响（“如果发生了什么情况”）
重新定义、重新部署、删除、移动、延迟、加速或不再提供资金。有
支持分析的体系结构开发的严格流程将产生质量
结果，不容易被误解，因此对决策具有很高的价值
制造商和任务成果。
架构支持的任务成果
企业架构
“今天，之间令人鼓舞的联合是许多企业
系统具有相同的体系结构方法，尽管不是所有系统都在
同样的方式。类似的融合解决了各种技术、模式和
16
DoDAF体系结构开发-6步流程
http://cio-nii.defense.gov/sites/dodaf20/arch_development.html[2011年3月3日下午3:33:54]
独立于特定应用程序域的设计
有效生产响应、可扩展、灵活和统一的企业
应用程序。”
在国防部内部，企业体系结构（EA）多年来一直被视为提供
以产品为导向深入了解各种数据、计划和活动
通过利益共同体（COI）。DoDAF V2.0的以数据为中心的方法是
旨在促进COI数据的重用和共享。由于DoDAF提供了
概念、逻辑和PES，但未另行规定
产品组合、架构师和利益相关者可以自由创建他们的数据视图
好是满足他们的需要。
导言和概述
体系结构描述是描述当前和/或
组织的业务、使命和管理之间的理想关系
过程和支持基础设施。体系结构描述定义了以下策略：
管理变化，以及发展业务状态所需的过渡过程
或任务更有效，效果更好

DSCA180A 57520001-GY DSCA 180A 通信处理器 

DSCA180A 57520001-GY DSCA 180A 通信处理器 

stakeholders; since goals and objectives define both the purpose for architecture creation
and the level of the architecture. Establishing the scope of an effort also determines the level
of complexity for data collection and information presentation.
Architecture development also requires an understanding of external requirements that may
influence architecture creation. An architecture developed for an internal agency purpose still
needs to be mappable, and consistent with, higher level architectures, and mappable to the
DoD EA. For some architecture developments, consideration must be given in data collection
and graphical presentation to satisfaction of other external requirements, such as upward
reporting and submission of architectural data and models for program review, funding
approval, or budget review due to the sensitivity or dollar value of the proposed solution.
This site contains guidance on data collection for specific views required by instruction,
regulation, or other regulatory guidance (i.e., Exhibit 53, or Exhibit 300 submissions; OMB
Segment architecture reviews, or interoperability requirements).
Architecture scoping must facilitate alignment with, and support the decision-making process
and ultimately mission outcomes and objectives as shown in the figure below. Architectural
data and supporting views, created from organizing raw data into useful information, and
collected into a useful viewpoint, should enable domain experts, program managers, and
decision makers to utilize the architecture to locate, identify, and resolve definitions,
properties, facts, constraints, inferences, and issues, both within and across architectural
boundaries that are redundant, conflicting, missing, and/or obsolete. DoDAF V2.0 provides
the flexibility to develop both Fit-for-Purpose Views (User-developed Views) and views from
DoDAF-described Models to maximize the capability for decision-making at all levels. The
figure below shows how the development of architectures supports the management decision
process. In this case, the example shows how an architecture and the use of it in analysis
can facilitate the ability to determine and/or validate mission outcome.
Analysis also uncovers the effect and impact of change (“what if”) when something is
redefined, redeployed, deleted, moved, delayed, accelerated, or no longer funded. Having a
disciplined process for architecture development in support of analytics will produce quality
results, not be prone to misinterpretations, and therefore, be of high value to decision
makers and mission outcomes.
Mission Outcomes Supported by Architectures
Enterprise Architecture
“Today, the encouraging coalescence among leaders is that many enterprise
systems have the same architectural approach—although not all express it in the
same way. A similar convergence addresses the kinds of techniques, pattern, and
16
DoDAF Architecture Development - 6 Step Process
http://cio-nii.defense.gov/sites/dodaf20/arch_development.html[3/3/2011 3:33:54 PM]
designs that are independent of specific application domains, and that enable
effective production of responsive, scalable, flexible, and unifiable enterprise
applications.”
Within DoD, Enterprise Architecture (EA) has been seen for many years as providing
product-oriented insight into a wide range of data, programs, and activities, organized
through Communities of Interest (COI). The data-centric approach to DoDAF V2.0 is
designed to facilitate the reuse and sharing of COI data. Since DoDAF provides the
conceptual, logical, and PES but does not otherwise prescribe the configuration of the
product composition, architects and stakeholders are free to create their views of data that
best serve their needs.
Introduction and Overview
An Architectural Description is a strategic information asset that describes the current and/or
desired relationships between an organization’s business, mission and management
processes, and the supporting infrastructure. Architectural Descriptions define a strategy for
managing change, along with transitional processes needed to evolve the state of a business
or mission to one that is more efficient, effect