供应 DSAI151 57120001-DE DSAI 151 控制主板

供应 DSAI151 57120001-DE DSAI 151 控制主板 

为描述服务的体系结构描述收集的信息类似于
为描述系统的体系结构描述收集的信息。描述
架构描述将收集关于订阅的附加信息，
目录服务、组织内的分销渠道和支持
系统/通信网络需求。
联合作战的体系结构描述开发也会出现类似情况。共同的
能力是指具有预期结果和预期执行能力的过程
日期。支持这些类型的开发的体系结构描述
能力通常需要重用军事部门已经建立的数据，并且
机构、分析和配置为新的或更新的流程，以提供所需的
能力。包括军事服务和/或机构响应所需的过程，
所需的自动化支持，以及所需结果和支持的明确定义
性能度量（度量）。这些类型的数据在模型中显示。
这一步的重要概念是明确为项目定义的工作范围
这实现了预期的结果。范围广泛或问题定义不明确可能会延迟
或者阻止成功。流程所有者主要负责确保：
范围界定是正确的，项目可以成功完成。
通过定义和描述要使用的数据，可以更好地确定范围的清晰度
在创建视图之前提出的架构描述
12
DoDAF体系结构开发-6步流程
http://cio-nii.defense.gov/sites/dodaf20/arch_development.html[2011年3月3日下午3:33:54]
以对管理人员有用的格式提供所需数据。尽早确定所需数据，特别是
关于建筑描述本身的数据
体系结构描述和对COI现有数据的审查可以提供丰富的来源
确保体系结构描述在开发时与其他描述一致
现有架构描述。它还确保与任何数据共享的一致性
部门或单个COI内的要求，并符合DM2。
一个重要的考虑因素，从架构的这一步开始，以及随后的每一步
开发过程是持续收集和记录一致、协调的，
以及常用词汇。术语的收集应在整个体系结构中继续进行
这是一个发展过程。确定体系结构数据以帮助澄清适当的范围
在架构工作中，应消除词汇术语和定义的歧义，
协调并记录在“DoDAF V2.0”中记录的一致的AV-2过程中
DoDAF描述模型“微软项目计划”的架构开发过程。
分析不同架构描述中的词汇表，范围相似，可能
帮助澄清和确定适当的体系结构描述范围。具体例子
利用AV-2数据字典结构进行数据识别的方法见DoDAF
杂志
步骤3：确定支持架构开发所需的数据。必要的
确定每个数据实体和属性要捕获的详细程度
通过分析步骤中范围界定期间进行的审查过程
2.这包括执行过程所需的数据和其他数据
在当前流程中实施变更所需的数据（例如
记录架构描述工作的组织）。这些考虑确定：
步骤4中收集的数据类型，与建筑结构和深度有关
所需的细节。
要收集的体系结构数据内容的初始类型由确定的
体系结构描述的范围，并记录为属性、关联和概念
如DM2中所述。从DM2概念、关联和属性到
架构模型建议建筑师可以开发的相关架构视图（使用
相关体系结构技术）在更全面和一致的数据
收集步骤4。此步骤通常与步骤4一起完成，即自下而上
有组织的数据收集和体系结构描述开发方法
重复这两个步骤。随着初始数据内容的范围化，附加数据范围可能是
建议采用更全面的建筑视图内容
演示或决策目的。
这一步骤通常可以通过重用其他人以前收集的数据来简化，但是
与当前工作相关。访问适当的COI数据和其他架构
可通过DAR和DMR发现的信息可提供数据和其他信息

供应 DSAI151 57120001-DE DSAI 151 控制主板 

供应 DSAI151 57120001-DE DSAI 151 控制主板 

Information collected for Architectural Descriptions describing services is similar to
information collected for Architectural Descriptions describing systems. For describing
services, Architectural Description will collect additional information concerning subscriptions,
directory services, distribution channels within the organization, and supporting
systems/communications web requirements.
Similar situations occur with Architectural Description development for joint operations. Joint
capabilities are defined processes with expected results, and expected execution capability
dates. The Architectural Descriptions supporting the development of these types of
capabilities usually require the reuse of data already established by the military services and
agencies, analyzed, and configured into a new or updated process that provides the desired
capability. Included are the processes needed for military service and/or agency response,
needed automation support, and a clear definition of both desired result and supporting
performance measures (metrics). These types of data are presented in models.
The important concept for this step is the clarity of scope of effort defined for the project
that enables an expected result. Broad scoping or unclear definition of the problem can delay
or prevent success. The process owner has the primary responsibility for ensuring that the
scoping is correct, and that the project can be successfully completed.
Clarity of scope can better be determined by defining and describing the data to be used in
the proposed Architectural Description in advance of the creation of views that present
12
DoDAF Architecture Development - 6 Step Process
http://cio-nii.defense.gov/sites/dodaf20/arch_development.html[3/3/2011 3:33:54 PM]
desired data in a format useful to managers. Early identification of needed data, particularly
data about the Architectural Description itself, the subject-matter of the proposed
Architectural Description, and a review of existing data from COIs, can provide a rich source
for ensuring that Architectural Descriptions, when developed, are consistent with other
existing Architectural Descriptions. It also ensures conformance with any data-sharing
requirements within the Department or individual COIs, and conformant with the DM2.
An important consideration beginning with this and each subsequent step of the architecture
development process is the continual collection and recording of a consistent, harmonized,
and common vocabulary. The collection of terms should continue throughout the architecture
development process. As architectural data is identified to help clarify the appropriate scope
of the architecture effort, vocabulary terms and definitions should be disambiguated,
harmonized, and recorded in a consistent AV-2 process documented in the "DoDAF V2.0
Architecture Development Process for the DoDAF-described Models" Microsoft Project Plan.
Analysis of vocabularies across different Architectural Descriptions with similar scope may
help to clarify and determine appropriate Architectural Description scope. Specific examples
of data identification utilizing the AV-2 Data Dictionary construct are found in the DoDAF
Journal.
Step 3: Determine Data Required to Support Architecture Development. The required
level of detail to be captured for each of the data entities and attributes is determined
through the analysis of the process undergoing review conducted during the scoping in Step
2. This includes the data identified as needed for execution of the process, and other data
required to effect change in the current process, (e.g., administrative data required by the
organization to document the Architectural Description effort). These considerations establish
the type of data collected in Step 4, which relate to the architectural structure, and the depth
of detail required.
The initial type of architectural data content to be collected is determined by the established
scope of the Architectural Description, and recorded as attributes, associations, and concepts
as described in the DM2. A mapping from DM2 concepts, associations, and attributes to
architecture models suggests relevant architectural views the architect may develop (using
associated architecture techniques) during the more comprehensive and coherent data
collection of Step 4. This step is normally completed in conjunction with Step 4, a bottom-up
approach to organized data collection, and Architectural Description development typically
iterates over these two steps. As initial data content is scoped, additional data scope may be
suggested by the more comprehensive content of Architectural Views desired for
presentation or decision-making purposes.
This step can often be simplified through reuse of data previously collected by others, but
relevant to the current effort. Access to appropriate COI data and other architecture
information, discoverable via DARS and the DMR, can provide information on data and other
architectural views that may provide useful in a current effort.
Work is presently underway within the Department to ensure unif