PPD517A3011 3BHE051476R3011 工业驱动器专用电源

PPD517A3011 3BHE051476R3011 工业驱动器专用电源 

标准（规则）通常约束活动。其中一些限制可能：
也适用于表演者执行活动。
d、 执行者可以具有与活动的执行相关联的度量（例如。，
目标跟踪精度。）它还可能具有与执行者相关联的度量
总体（如操作条件）
e、 表演者在特定位置或区域、区域或
装置、场地或设施。执行者的位置、类型、要求/能力
通过在特定条件下执行的活动捕获/表达
（例如，必须能够在沙漠条件下执行机动。）
f、 由系统执行的活动可以被称为系统或服务功能（即。，
由系统执行的活动和/或过程）。系统或服务功能
（活动）分配给硬件、软件、固件或人员（当
人被认为是系统的组成部分）。
g、 在典型应用中，活动由动词表示，执行者是
由名词表示。这将“如何”与“谁”区分开来。典型地
对执行者的规范过程分配可以在不同的细节级别上进行
这取决于设计成熟度或设计约束的预期程度。
h、 表演者在详细架构中的许多地方和阶段都有代表。它
应该注意，纯需求体系结构描述可能不会显示
分配或执行者。这可留待设计过程的后期阶段进行。
此外，并非所有架构建模标准都明确规定了分配。对于
例如，系统建模语言（SysML）对UML建模的扩展
标准已添加此功能。
执行者的DoDAF元模型
（点击放大）
43
DM2-表演者
http://cio-nii.defense.gov/sites/dodaf20/performers.html[2011年3月3日下午3:43:02]
核心流程中的使用
执行者数据的使用方式如下：
JCIDS：
1.人型流程通常称为战术、技术和程序（TTP）
在国防部。程序是分配的活动和/或过程集，其中策略和
技术通常由受规则、理论和程序影响的程序组成，
教育和培训期间通过技能发展获得的范例等
过程
2.纯需求架构描述可能不显示分配或执行者。
这可留待设计过程的后期阶段进行。
PPBE：
1.记录项目（PoR）是可以包含材料和非材料执行者的项目（见《FYDP项目结构手册》（DoD 7045.7-H）。
2.记录程序通过工作分解结构链接到PPBE
（WBS）（见DAS）描述与成本相关的执行者。
3.规划和编程*[1]过程通常通过
评估能力、执行者和与执行者相关的属性
（例如措施）。（例如，“差距和重叠分析”、能力演变等）

PPD517A3011 3BHE051476R3011 工业驱动器专用电源 

PPD517A3011 3BHE051476R3011 工业驱动器专用电源 

. A standard (Rule) constrains an Activity in general. Some of those constraints might
also apply to the performance of the Activity by a Performer.
d. A Performer may have Measures associated with the performance of an Activity (e.g.,
target tracking accuracy.) It may also have Measures associated with the Performer
overall (e.g., operational condition.)
e. Performers perform at Locations that can be specific positions or areas, regions, or
installations, sites, or facilities. Location type requirements/capabilities of a Performer
are captured/expressed via the Activities that are performed under certain Conditions
(e.g., must be able to perform Maneuver under Desert Conditions.)
f. Activities performed by a System can be called system or service functions (i.e.,
activities and/or processes performed by a system). System or service functions
(activities) are allocated to hardware, software, firmware or personnel (when the
person is considered integral to the system).
g. In typical uses, the Activities are represented by verbs and Performers are
represented by nouns. This distinguishes the how from the who. In a typical
specification process allocation to performers can take place at varying levels of detail
depending on the design maturity or the intended degree of design constraint.
h. Performers are represented in many places and stages in the detailed architecture. It
should be noted that a pure Requirements Architectural Description may not show
allocations or performer. This may be left to later stages of the design process.
Further, not all architecture modeling standards explicitly provide for allocation. For
example, the Systems Modeling Language (SysML) extensions to the UML modeling
standard have added this feature.
DoDAF Meta Model for Performers
(Click to enlarge)
43
DM2 - Performers
http://cio-nii.defense.gov/sites/dodaf20/performers.html[3/3/2011 3:43:02 PM]
Usage in Core Processes
Data for Performer are used in the following ways:
JCIDS:
1. Person Type processes are typically termed Tactics, Techniques and Procedures (TTP)
in DoD. Procedures are allocated sets of activities and/or processes, where Tactics and
Techniques, typically, are made up of the procedures as influenced by rules, doctrine,
paradigms, etc. acquired through skill development during the education and training
process.
2. A pure Requirements Architectural Description may not show allocations or performer.
This may be left to later stages of the design process.
PPBE:
1. 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.)