DSDI120A 57160001-ACA DSDI 120A 数字输入模块

DSDI120A 57160001-ACA DSDI 120A 数字输入模块 

其职责范围的某些方面（过程、活动等）。
用于收集与项目目的和范围相关的信息的模板
体系结构描述、术语表和其他信息已经为
在DARS中注册该数据。
步骤2：确定架构的范围。范围定义了以下边界：
确定架构描述的深度和广度，并确定
架构的问题集，有助于定义其上下文，并定义所需的详细级别
建筑内容。尽管许多体系结构开发工作在其
方法，每项努力都是独特的，因为预期的结果或效果可能相当
不同的例如，系统开发工作通常首先关注流程
改变，然后专注于支持工作流程的自动化功能，或
活动。除了了解过程之外，这些“系统功能”的发现是
在决定如何继续开发或购买自动化支持时非常重要。
为描述服务的体系结构描述收集的信息类似于
为描述系统的体系结构描述收集的信息。描述
架构描述将收集关于订阅的附加信息，
目录服务、组织内的分销渠道和支持
系统/通信网络需求。
联合作战的体系结构描述开发也会出现类似情况。共同的
能力是指具有预期结果和预期执行能力的过程
日期。支持这些类型的开发的体系结构描述
能力通常需要重用军事部门已经建立的数据，并且
机构、分析和配置为新的或更新的流程，以提供所需的
能力。包括军事服务和/或机构响应所需的过程，
所需的自动化支持，以及所需结果和支持的明确定义
性能度量（度量）。这些类型的数据在模型中显示。
这一步的重要概念是明确为项目定义的工作范围
这实现了预期的结果。范围广泛或问题定义不明确可能会延迟
或者阻止成功。流程所有者主要负责确保：
范围界定是正确的，项目可以成功完成。
通过定义和描述要使用的数据，可以更好地确定范围的清晰度
在创建视图之前提出的架构描述
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中收集的数据类型，与建筑结构和深度有关
所需的细节。

DSDI120A 57160001-ACA DSDI 120A 数字输入模块 

some aspect of their area of responsibility (process, activity, etc.).
A template for collection of high-level information relating to the purpose and scope of the
Architectural Description, its glossary, and other information, has been developed for
registration of that data in DARS.
Step 2: Determine Scope of Architecture. The scope defines the boundaries that
establish the depth and breadth of the Architectural Description and establish the
architecture's problem set, helps define its context and defines the level of detail required for
the architectural content. While many architecture development efforts are similar in their
approach, each effort is also unique in that the desired results or effect may be quite
different. As an example, system development efforts generally focus first on process
change, and then concentrate on those automated functions supporting work processes or
activities. In addition to understanding the process, discovery of these 'system functions' is
important in deciding how to proceed with development or purchase of automation support.
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.