DSMB127 57360001-HG/2 DSMB 127 多路控制主板

DSMB127 57360001-HG/2 DSMB 127 多路控制主板 

DSMB127 57360001-HG/2 DS在任何层建立架构工作的范围在确定
体系结构边界（预期用途和用途），以及建立数据
分析和管理决策所需的类别。范围还定义了
关键参与者的投入、建议和共识是成功构建和
实施变更（即内部和外部利益相关者）。重要的是，范围
确定工作的目标和目的，与边界和
15
DoDAF体系结构开发-6步流程
http://cio-nii.defense.gov/sites/dodaf20/arch_development.html[2011年3月3日下午3:33:54]
利益相关者；因为目标和目的定义了架构创建的目的
以及架构的级别。确定工作范围也决定了水平
数据收集和信息呈现的复杂性。
体系结构开发还需要了解外部需求，这些需求可能：
对建筑创作的影响。为内部机构目的开发的架构仍然
需要可映射并与更别的体系结构保持一致，并可映射到
国防部EA。对于某些架构开发，必须考虑数据收集
以及满足其他外部要求的图形表示，如向上
报告和提交架构数据和模型，以供项目审查、资助
由于所提议的解决方案的敏感性或美元价值。
本网站包含指令要求的特定视图的数据收集指南，
法规或其他监管指南（即，附件53或附件300提交文件；OMB
分系统架构审查或互操作性要求）。
体系结构范围界定必须有助于与决策过程保持一致，并支持决策过程
终的任务结果和目标如下图所示。建筑的
通过将原始数据组织成有用信息创建的数据和支持视图，以及
收集到有用的观点中，应使领域专家、项目经理和
决策者利用架构定位、识别和解析定义，
属性、事实、约束、推论和问题，包括体系结构内部和跨体系结构
冗余、冲突、缺失和/或过时的边界。DoDAF V2.0提供
灵活地开发适合用途的视图（用户开发视图）和来自
DoDAF描述了大化各级决策能力的模型。这个
下图显示了架构的开发如何支持管理决策
过程在本例中，该示例显示了架构如何在分析中使用
可以促进确定和/或验证任务结果的能力。
分析还揭示了变化的影响和影响（“如果发生了什么情况”）
重新定义、重新部署、删除、移动、延迟、加速或不再提供资金。有
支持分析的体系结构开发的严格流程将产生质量
结果，不容易被误解，因此对决策具有很高的价值
制造商和任务成果。MB 127 多路控制主板 

DSMB127 57360001-HG/2 DSMB 127 多路控制主板 

Establishing a scope for an architecture effort at any tier is similarly critical in determining
the architecture boundaries (Purpose and Use expected), along with establishing the data
categories needed for analysis and management decision-making. Scope also defines the
key players whose input, advice, and consensus is needed to successfully architect and
implement change (i.e., Stakeholders, both internal and external). Importantly, scope also
determines the goals and objectives of the effort, consistent with both boundaries and
15
DoDAF Architecture Development - 6 Step Process
http://cio-nii.defense.gov/sites/dodaf20/arch_development.html[3/3/2011 3:33:54 PM]
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.