DAC86-16CH 5761379-3B 模拟输出模块PCB驱动板

DAC86-16CH 5761379-3B 模拟输出模块PCB驱动板 

DARS提供了更多具体的信息，以及检索所需数据的指南
通过发现过程。一旦发现注册数据，就可以对数据进行编目
并在集中的分类法中进行组织，便于确定新数据
是必需的。定义新数据，在DARS中注册，并将其纳入分类法
结构创建所需数据的完整定义列表。数据被安排上传
以允许后续分析和重用。发现元数据
（即，标识特定体系结构描述、其数据、视图和
使用）应在DARS中注册，以支持发现和
启用联合。架构师和数据管理人员应使用DoD EA业务参考
模型（DoD EA BRM）分类元素作为其注册工作的起点。
以后可能需要额外的发现元数据，如流程和服务，以及
应遵循相同的注册流程。
步骤5：进行分析以支持架构（Architecture）目标。建筑数据
分析确定遵守过程所有者要求的程度。这一步骤可能：
还应确定完成所需的其他流程步骤和数据收集要求
并更好地促进其预期用途。验证适用于
过程要求的指导原则、目标和目标，如
流程所有者与已发布的性能度量（度量）一起确定
在架构描述工作中取得了一定的成功。完成此步骤
编制架构描述，以供流程所有者批准。需要更改
从验证过程开始，导致架构过程的迭代（重复步骤3
根据需要通过5）。
步骤6：根据决策者的需要记录结果。后一步
在架构开发过程中，涉及基于以下内容创建架构视图：
基础数据的查询。向不同的受众展示体系结构数据需要：
将架构数据转化为决策者有意义的演示。这是
由步骤3中确定的数据要求和数据收集方法促进
在步骤4中使用。
DoDAF V2.0提供了模型和视图。DoDAF描述的模型是指：
启用数据已定义的架构师和开发团队，以及
描述与DM2一致。模型在填充
架构数据。这些模型包括之前在的早期版本中描述的模型
DoDAF，以及从MODAF、北约NAF和TOGAF合并的新模型
与国防部体系结构开发工作相关。
适用视图是架构师和开发团队可以使用的用户定义视图
创建：以通常使用的格式提供决策所需的信息
代理机构。这些视图的开发应与DM2一致，但可以采用格式
（例如，仪表盘、图表、图形表示）通常用于机构
简报和决策目的。架构描述开发工作可能导致
一种体系结构描述，是DoDAF描述的模型和适用视图的组合。
DoDAF不需要特定的模型或视图，但建议本地组织
可以利用DoDAF创建的数据的表示类型是管理的
14
DoDAF体系结构开发-6步流程
http://cio-nii.defense.gov/sites/dodaf20/arch_development.html[2011年3月3日下午3:33:54]
演示许多可用的体系结构工具支持创建视图
如本步骤所述。PES提供了数据共享的格式。
注意：DoDAF V2.0没有规定物理数据模型，将该任务留给
将在其
自己的软件产品。
范围界定体系结构“适合用途”
确定体系结构的范围对于确保其目的和用途是至关重要的
与具体项目目标一致。术语“适用于目的”用于
DoDAF来描述适当聚焦的架构（及其视图）（即。，
响应过程所有者的既定目标和目的，在决策过程中有用，并响应内部和外部利益相关者的关注。会议
预期目标是指直接支持客户需求或
改进正在经历的整个过程

DAC86-16CH 5761379-3B 模拟输出模块PCB驱动板 

DAC86-16CH 5761379-3B 模拟输出模块PCB驱动板 

DARS provides more information that is specific, and guidance on retrieving needed data
through a discovery process. Once registered data is discovered, the data can be cataloged
and organized within a focused taxonomy, facilitating a means to determine what new data
is required. New data is defined, registered in DARS, and incorporated into the taxonomy
structure to create a complete defined list of required data. The data is arranged for upload
to an automated repository to permit subsequent analysis and reuse. Discovery metadata
(i.e., the metadata that identifies a specific Architectural Description, its data, views, and
usage) should be registered in DARS as soon as it is available to support discovery and
enable federation. Architects and data managers should use the DoD EA Business Reference
Model (DoD EA BRM) taxonomy elements as the starting point for their registration efforts.
Additional discovery metadata, such as processes and services may be required later, and
should follow the same registration process.
Step 5: Conduct Analyses in Support of Architecture Objectives. Architectural data
analysis determines the level of adherence to process owner requirements. This step may
also identify additional process steps and data collection requirements needed to complete
the Architectural Description and better facilitate its intended use. Validation applies the
guiding principles, goals, and objectives to the process requirement, as defined by the
process owner, along with the published performance measures (metrics), to determine the
achieved level of success in the Architectural Description effort. Completion of this step
prepares the Architectural Description for approval by the process owner. Changes required
from the validation process, result in iteration of the architecture process (repeat steps 3
through 5 as necessary).
Step 6: Document Results in Accordance with Decision-Maker Needs. The final step
in the architecture development process involves creation of architectural views based on
queries of the underlying data. Presenting the architectural data to varied audiences requires
transforming the architectural data into meaningful presentations for decision-makers. This is
facilitated by the data requirements determined in Step 3, and the data collection methods
employed during Step 4.
DoDAF V2.0 provides for models and views. DoDAF-described Models are those models that
enable an architect and development team whose data has already been defined and
described consistent with the DM2. The models become views when they are populated with
architectural data. These models include those previously described in earlier versions of
DoDAF, along with new models incorporated from the MODAF, the NATO NAF, and TOGAF
that have relevance to DoD architecture development efforts.
Fit-for-Purpose Views are user-defined views that an architect and development team can
create to provide information necessary for decision-making in a format customarily used in
an agency. These views should be developed consistent with the DM2, but can be in formats
(e.g., dashboards, charts, graphical representations) that are normally used in an agency for
briefing and decision purposes. An Architectural Description development effort can result in
an Architectural Description that is a combination of DoDAF-described Models and Fit-forPurpose Views.
DoDAF does not require specific models or views, but suggests that local organizational
presentation types that can utilize DoDAF-created data are preferred for management
14
DoDAF Architecture Development - 6 Step Process
http://cio-nii.defense.gov/sites/dodaf20/arch_development.html[3/3/2011 3:33:54 PM]
presentation. A number of available architecture tools support the creation of views
described in this step. The PES provides the format for data sharing.
NOTE: DoDAF V2.0 does NOT prescribe a Physical Data Model, leaving that task to the
software developers who will implement the principles and practices of DoDAF in their
own software offerings.
Scoping Architectures to be "Fit-for-Purpose"
Establishing the scope of an architecture is critical to ensuring that its purpose and use are
consistent with specific project goals and objectives. The term “Fit-for-Purpose” is used in
DoDAF to describe an architecture (and its views) that is appropriately focused (i.e.,
responds to the stated goals and objectives of process owner, is useful in the decisionmaking process, and responds to internal and external stakeholder concerns. Meeting
intended objectives means those actions that either directly support customer needs or
improve the overall process undergoing