FDC86-UNIT1B 58173487B FDC86UNIT1B 驱动软盘模块

FDC86-UNIT1B 58173487B FDC86UNIT1B 驱动软盘模块 

以及常用词汇。术语的收集应在整个体系结构中继续进行
这是一个发展过程。确定体系结构数据以帮助澄清适当的范围
在架构工作中，应消除词汇术语和定义的歧义，
协调并记录在“DoDAF V2.0”中记录的一致的AV-2过程中
DoDAF描述模型“微软项目计划”的架构开发过程。
分析不同架构描述中的词汇表，范围相似，可能
帮助澄清和确定适当的体系结构描述范围。具体例子
利用AV-2数据字典结构进行数据识别的方法见DoDAF
杂志
步骤3：确定支持架构开发所需的数据。必要的
确定每个数据实体和属性要捕获的详细程度
通过分析步骤中范围界定期间进行的审查过程
2.这包括执行过程所需的数据和其他数据
在当前流程中实施变更所需的数据（例如
记录架构描述工作的组织）。这些考虑确定：
步骤4中收集的数据类型，与建筑结构和深度有关
所需的细节。
要收集的体系结构数据内容的初始类型由确定的
体系结构描述的范围，并记录为属性、关联和概念
如DM2中所述。从DM2概念、关联和属性到
架构模型建议建筑师可以开发的相关架构视图（使用
相关体系结构技术）在更全面和一致的数据
收集步骤4。此步骤通常与步骤4一起完成，即自下而上
有组织的数据收集和体系结构描述开发方法
重复这两个步骤。随着初始数据内容的范围化，附加数据范围可能是
建议采用更全面的建筑视图内容
演示或决策目的。
这一步骤通常可以通过重用其他人以前收集的数据来简化，但是
与当前工作相关。访问适当的COI数据和其他架构
可通过DAR和DMR发现的信息可提供数据和其他信息
可以在当前工作中提供有用的架构视图。
该部目前正在开展工作，以确保
架构建模中的相同语义内容称为架构建模原语。
架构建模原语（以下简称为原语）将成为标准
映射到DM2概念并应用于
建模技术。使用原语支持架构内容的收集
与PES合作，将有助于形成共识，并
建筑师之间关于建筑视图的沟通。作为基本概念
应用于更多建模技术，将在DoDAF期刊上更新
DoDAF后续版本中提供了详细信息。在业务中创建OV-6c时
过程建模符号（BPMN），可以使用原语符号。国防部已经创建
这个符号在DoDAF期刊上。视图的全部基本体，如
当前的BPMN原语将被架构工具供应商协调采用。
步骤4：收集、组织、关联和存储架构数据。建筑师通常
通过使用设计为使用视图的架构技术收集和组织数据
（例如，作为视图的活动、流程、组织和数据模型）用于表示和

FDC86-UNIT1B 58173487B FDC86UNIT1B 驱动软盘模块 

FDC86-UNIT1B 58173487B FDC86UNIT1B 驱动软盘模块 

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 uniform representation for the
same semantic content within architecture modeling, called Architecture Modeling Primitives.
The Architecture Modeling Primitives, hereafter referred to as Primitives, will be a standard
set of modeling elements, and associated symbols mapped to DM2 concepts and applied to
modeling techniques. Using the Primitives to support the collection of architecture content
and, in concert with the PES, will aid in generating common understanding and
communication among architects in regard to architectural views. As the Primitives concepts
are applied to more modeling techniques, they will be updated in the DoDAF Journal and
details provided in subsequent releases of DoDAF. When creating an OV-6c in Business
Process Modeling Notation (BPMN), the Primitives notation may be used. DoD has created
the notation and it is in the DoDAF Journal. The full range of Primitives for views, as with the
current BPMN Primitives, will be coordinated for adoption by architecture tool vendors.
Step 4: Collect, Organize, Correlate, and Store Architectural Data. Architects typically
collect and organize data through the use of architecture techniques designed to use views
(e.g., activity, process, organization, and data models as views) for presentation and