PM152 3BSE003643R1 模拟量输入输出DCS模块 ABB
PM152 3BSE003643R1 模拟量输入输出DCS模块 ABB
PM152 3BSE003643R1 模拟量输入输出DCS模块 ABB
PM152 3BSE003643R1 模拟量输入输出DCS模块 ABB
核心流程中的使用
位置数据用于描述表演者的表演位置。位置概念
在DoDAF V1.0和1.5中支持系统节点。在DoDAF2.0中,它被推广并
更***地定义。所有核心中各种类型位置的使用示例
过程包括:
a、 设施位置允许描述某些系统或组织所处的位置
特定的设施。请注意,设施的功能由活动决定
由设施内的表演者执行;也就是说,设施本身不是
表演者
b、 安装位置允许描述操作或使用
安装
c、 区域位置用于描述执行人员和活动的执行情况
某些地区。
d、 点位置可用于说明表演者何时位于特***;
e、 例如纬度和经度。当位置不是那么具体时,
并且可以使用其他几何形状。
e、 行(一组行)允许描述位于、旁边或内部的表演者
包围线。这条线可以用数学描述,这样它就可以***
轨道,例如,某些卫星在某个轨道上。
f、 体积,例如,某些系统覆盖某一体积;e、 例如防空系统。
g、 地址(位置名称)允许描述某物的位置
使用地址方案;e、 例如,URL地址方案允许查找
互联网协议(IP),然后是服务器上的文件。
演示
位置通常以图形图的形式在架构中表示,但表格和
根据“适用性”应用,可使用其他表示。许多
实例、位置结合中使用的典型模型和视图进行描述
架构描述。
转到页面顶部↑
隐私政策|网络政策124;联系人
87
DM2-谱系
http://cio-nii.defense.gov/sites/dodaf20/pedigree.html[2011年3月3日下午3:43:56]
首页DoDAF-DM2工作组DoDAF期刊***部元数据注册想法链接
DM2数据组
纯种
谱系数据组表示资源的工作流。它描述了这些活动
用于产生资源,例如一条信息。特别重要的
架构描述,是架构描述的产物
信息(体系结构描述是信息类型,因为信息描述
一些事物和架构描述描述了架构。)各方面
可使用谱系数据组描述生产工作流程,包括:
a、 资源生产过程中消耗了哪些资源
b、 哪些表演者表演了这部作品
c、 哪些规则约束了生产活动
d、 应用于生产和消耗的资源的度量(度量)是什么
e、 生产发生在哪里
数据组描述
包括谱系的数据的DoDAF元模型如下图所示。
DoDAF谱系元模型
(点击图片放大)
出身背景
建筑发展
元模型
概念的
必然的
表演者
资源流动
信息和数据
规则
目标
能力
服务
项目
物化
组织结构
措施
位置
纯种
PES
思想基金会
本体论
观点和模型
展示技巧
配置管理
概述
缩略语列表和词汇表
术语
网站地图
档案
***部
88
DM2-谱系
http://cio-nii.defense.gov/sites/dodaf20/pedigree.html[2011年3月3日下午3:43:56]
核心流程中的使用
谱系用于证明架构描述选择的基本原理。许多
系统工程和需求分析过程
保持可追溯性信息。
演示
谱系信息通常以可追溯性矩阵、表格或缩进文本形式呈现。
有时呈现反向可追溯性信息。,
需求),然后满足它的体系结构工件被列出
PM152 3BSE003643R1 模拟量输入输出DCS模块 ABB
PM152 3BSE003643R1 模拟量输入输出DCS模块 ABB
Usage in Core Processes
Data for Locations are used to describe where Performers perform. The Location concept
supported the system node in DoDAF V1.0 and V1.5. In DoDAF V2.0, it is generalized and
more precisely defined. Examples of the uses of the various types of Locations in all the core
processes are:
a. Facility Locations allow description that certain systems or organizations are located at
a specific facility. Note that the function of the Facility is determined by the Activities
performed by the Performers located at the Facility; that is, the Facility itself is not a
Performer.
b. Installation Locations allow descriptions of certain organizations that operate or use an
installation.
c. Region Locations are used to describe what Performers and Activities are performed in
certain regions.
d. A Point Location can be used to state when a Performer is located at a specific Point;
e.g., latitude and longitude. When the location is not that specific, Regions, Countries,
and other geometric shapes can be used.
e. Line (set of lines) allows description of Performers located on, beside, or within some
enclosing lines. The line could be described mathematically so that it could specify an
orbit, e.g., that certain satellites are in some orbit.
f. Volume, e.g., that some systems cover a certain volume; e.g., an air defense system.
g. Addresses (names for locations) allow descriptions of where something is located
using the address scheme; e.g., the URL address scheme allows for looking up the
internet protocol (IP) and then the files on the server.
Presentation
Location is typically represented in architecture in pictorial diagrams, however tabular and
other representations may be used depending on the "Fit-for-Purpose" application. In many
instances, locations are depicted in conjunction with typical models and view used in
architectural descriptions.
Go to top of page ↑
Privacy Policy | Web Policy | Contacts
87
DM2 - Pedigree
http://cio-nii.defense.gov/sites/dodaf20/pedigree.html[3/3/2011 3:43:56 PM]
Home DoDAF-DM2 WG DoDAF Journal DoD Meta Data Registry IDEAS Links
DM2 Data Groups
Pedigree
The pedigree data group represents the workflow for a Resource. It describes the Activities
used to produce a Resource, e.g., a piece of Information. Of particularly high importance for
architectural descriptions, is the production of architecture description
information. (Architecture descriptions are types of Information since Information describes
some Thing and architecture descriptions describe the architecture.) All aspects of the
production workflow are describable with the Pedigree data group including:
a. What Resources were consumed in the production of the Resource
b. What Performers performed the production
c. What Rules constrained the production activity
d. What metrics (Measures) applied to the production and the Resources consumed
e. Where did the production occur
Data Group Description
The DoDAF Meta Model for the data comprising Pedigree is shown in the figure below.
DoDAF Meta Model for Pedigree
(Click image to enlarge)
Background
Architecture Development
Meta-Model
Conceptual
Logical
Performers
Resource Flows
Information and Data
Rules
Goals
Capability
Services
Project
Reification
Organizational Structure
Measures
Locations
Pedigree
PES
IDEAS Foundation
Ontology
Viewpoints & Models
Presentation Techniques
Configuration Management
Overview
Acronyms List and Glossary
of Terms
Site Map
Archives
Department of Defense
88
DM2 - Pedigree
http://cio-nii.defense.gov/sites/dodaf20/pedigree.html[3/3/2011 3:43:56 PM]
Usage in Core Processes
Pedigree is used to demonstrate the rationale for architecture description choices. In many
systems engineering and requirements analysis processes, it is the means by which
traceability information is maintained.
Presentation
Pedigree information is usually presented in traceability matrices, tables, or indented text.
Sometime reverse-traceability information is presented, wherein the source (e.g.,
requirement) is listed and then the architectural artifacts that satisfy it are sho