SDCS-IOB-22 3BSE005177R1 I/O数字外部隔离模块PC控制板

SDCS-IOB-22 3BSE005177R1 I/O数字外部隔离模块PC控制板 

记录项目（PoR）是可以包含材料和非材料执行者的项目（见《FYDP项目结构手册》（DoD 7045.7-H）。
2.记录程序通过工作分解结构链接到PPBE
（WBS）（见DAS）描述与成本相关的执行者。
3.规划和编程*[1]过程通常通过
评估能力、执行者和与执行者相关的属性
（例如措施）。（例如，“差距和重叠分析”、能力演变等）。
DAS：
1.MIL-HDBK-881A*[2]和国防部5000.1，为以下方面提供基本指导：
DAS的规范、WBS、工作说明书（SOW）均要求
基本的执行者及其组成部分和类型的识别
元素。
2.获取过程通常涉及通过材料的表演者
获取系统或获取与执行者相关的流程。
3.获取过程还可以涉及服务的获取。
东南方：
1.活动分配给执行者（组织、人员、物资或
其组合）。能力或较低级别的衍生能力，
分配了度量、条件、约束和其他需求表达
不同层次的表演者具体化。分配从一个级别到另一个级别，如下所示：
结构设计分解或设计细化的一部分。
2.分配是建筑师和工程师所使用的术语，用于表示各种结构或层次结构中元素的有组织交叉关联（映射）
用户视图，不考虑建模约定或标准。分配的概念
需要适用于抽象系统规范的灵活性，而不是特定的
系统或软件设计的约束方法。系统建模者经常联想到
抽象的、初步的、有时是试探性的各种元素。分配
可以在设计早期使用，作为更详细、更严格规范的先驱
以及实现。当需求定义阶段让位给设计时
当阶段和实际组件变得可见时，区分
在分配给和分配给之间。
3.配置控制下的某些类型的执行者称为系统配置
项目（CI）。软件配置项被称为计算机软件
MIL-HDBK881A中的配置项（CSCI）或软件配置项（SCI）。硬件配置项可以遵循Mil-STD-196E分类法（中央，
（中心、系统、子系统、集合、组、单元）指导国防部的MIL-HDBK-881A
44
DM2-表演者
http://cio-nii.defense.gov/sites/dodaf20/performers.html[2011年3月3日下午3:43:02]
工作分解结构（WBS），仅按级别（如1、2、3等）定义软件
老年退休金计划：
1.确定谁将完成所需的任务（活动），其中
什么条件，采取什么措施
CPM：
1.执行者是投资组合中需要管理和优化的主要项目
转到页面顶部↑
隐私政策|网络政策124;联系人
45
DM2-资源流
http://cio-nii.defense.gov/sites/dodaf20/resource_flows.html[2011年3月3日下午3:43:08]
首页DoDAF-DM2工作组DoDAF期刊国防部元数据注册想法链接
DM2-DoDAF元模型
资源流动
资源流用于建模资源流-物资、信息（和数据），
地理空间范围、执行者或其任意组合。资源流动是关键
接口定义和互操作性保证中使用的建模技术
活动及其相关执行者（如系统和人员）之间的资源
流模型和相关分析技术揭示了如下行为：
资源之间的连通性。
资源流建模提供了一种明确的方法来描述
活动、系统、组织及其对整个企业的综合影响。
在资源之间流动的信息的内容（例如，接口定义）。
资源相对于一个资源的顺序或顺序行为（并行或串行）
另一个（例如，项目任务执行和关键路径）。
组织之间或内部的资源流的行为（例如，
信息流等）。
在资源的空间和/或时间存在期间的状态变化。
修改资源流的行为的规则（例如，
控制、决策等）。
定义资源流质量、约束、时间等的措施
（例如，服务质量（QoS）、性能度量、有效性度量等），
等等）。
协调资源流行为的控制流

SDCS-IOB-22 3BSE005177R1 I/O数字外部隔离模块PC控制板 

SDCS-IOB-22 3BSE005177R1 I/O数字外部隔离模块PC控制板 
 Programs of Record (PoR) are Projects that can contain both material and nonmaterial Performers (See FYDP Program Structure Handbook (DoD 7045.7-H).
2. Program of Record are linked to the PPBE through the Work Breakdown Structure
(WBS) (see DAS) depicting Performers related to cost.
3. The Planning and Programming*[1] process typically conducts analysis through the
evaluation of Capabilities, Performers and the attributes associated with Performers
(e.g. Measures). (e.g. "Gap and Overlap analysis", Capability evolution, etc.).
DAS:
1. MIL-HDBK-881A*[2] and DoD 5000.1, in providing fundamental guidance for
specifications, WBS, Statement of Works (SOWs) of the DAS, all require the
identification of the Performers and their component parts and types as fundamental
elements.
2. The acquisition process generally involves Performers either through the material
acquisition of systems or the acquisition of processes associated with performers.
3. The acquisition process can also involve the Acquisition of Services.
SE:
1. Activities are assigned to Performers (organizational, human, materiel, or some
combination thereof). Capabilities or lower-level derived capabilities,
measures,conditions, constraints and other expressions of requirements are assigned
to the various levels of Performer reification. Allocation occurs from level-to-level as
part of structural design decomposition or design refinement.
2. Allocation is the term used by architects and engineers to denote the organized crossassociation (mapping) of elements within the various structures or hierarchies of a
user view regardless of modeling convention or standard. The concept of allocation
requires flexibility suitable for abstract system specification, rather than a particular
constrained method of system or software design. System modelers often associate
various elements in abstract, preliminary, and sometimes tentative ways. Allocations
can be used early in the design as a precursor to more detailed rigorous specifications
and implementations. As the requirements definition stage gives way to the design
stage and actual components become visible, it becomes important to distinguish
between allocated to and assigned to.
3. Some types of performers under configuration control called system Configuration
Items (CIs). Software Configuration items are termed Computer Software
Configuration Items (CSCIs) or Software Configuration items (SCIs) in MIL-HDBK881A. Hardware Configuration items may follow the Mil-STD-196E taxonomy (Central,
Center, System, Subsystem, Set, Group, Unit.) MIL-HDBK-881A , which guides DoD
44
DM2 - Performers
http://cio-nii.defense.gov/sites/dodaf20/performers.html[3/3/2011 3:43:02 PM]
Work Breakdown Structures (WBS), defines software only by levels (e.g., 1, 2, 3, etc.)
Ops Planning:
1. Determines who is going to accomplish the required tasks (activities), where, under
what conditions, and to what measures
CPM:
1. Performers are the major items in the portfolio to be managed and optimized
Go to top of page ↑
Privacy Policy | Web Policy | Contacts
45
DM2 - Resource Flows
http://cio-nii.defense.gov/sites/dodaf20/resource_flows.html[3/3/2011 3:43:08 PM]
Home DoDAF-DM2 WG DoDAF Journal DoD Meta Data Registry IDEAS Links
DM2 - DoDAF Meta-Model
Resource Flows
Resource Flows are used to model the flow of Resources - Materiel, Information (and Data),
Geo-Spatial Extents, Performers, or any combination thereof. Resource Flows are key
modeling techniques used in the definition of Interfaces and assurance of Interoperability
between Activities and their associated Performers (e.g., Systems and Personnel.) Resource
Flow models and associated analysis techniques reveal behavior such as:
The connectivity between resources.
Resource Flow modeling provides an explicit means to describe the behavior of
activities, systems, organizations and their composite effects on the overall enterprise.
The content of the information flowing between resources (e.g., interface definition).
The order or sequential behavior (parallel or serial) of the resources in relation to one
another (e.g., project task execution and critical path).
The behavior of Resource Flow between or within organizations (e.g., work flow,
information flow, etc.).
The changes in state during the spatial and/or temporal existence of the resource.
The rules that modify the behavior of the Resource Flow (e.g., business rules,
controls, decisions, etc.).
The measures that define the quality, constraints, timing, etc. of the Resource Flow
(e.g., Quality of Service (QoS), measures of performance, measures of effectiveness,
etc.).
The flow of control orchestrating the behavior of the Resource Flow