LDSYN-101 3BHE005555R0101 模拟量智能输入输出卡

LDSYN-101 3BHE005555R0101 模拟量智能输入输出卡 

项目初始阶段或活动期间的正式需求收集过程
分析或事件分析。在这种情况下，收集业务规则与
确定流程工作流的更大发现过程。项目，如
启动支持新的或更改的业务操作的新系统或服务
可能会为需要员工的组织带来一套新的业务规则
以新的方式概念化组织的宗旨。这种做法是巧合
业务规则收集容易产生不一致甚至冲突的数据
不同组织单位或同一组织单位内的业务规则
随着时间的推移。
DoDAF元模型提供了一组关于规则的清晰、简洁的数据，有助于
创建规则，并允许与需要类似规则的其他人共享这些规则
信息
规则不是一个过程-这两者虽然相关，但却非常不同。过程是
从现有事物（输入）产生新事物（输出）的转换，而规则
规定了用于确保输出符合预期的准确程序
执行该过程的每个实例。
数据组描述
包含规则的数据的DoDAF元模型如下图所示。
出身背景
建筑发展
元模型
概念的
必然的
表演者
资源流动
信息和数据
规则
目标
能力
服务
项目
物化
组织结构
措施
位置
纯种
PES
思想基金会
本体论
观点和模型
展示技巧
配置管理
概述
缩略语列表和词汇表
术语
网站地图
档案
国防部
57
DM2-规则
http://cio-nii.defense.gov/sites/dodaf20/rules.html[2011年3月3日下午3:43:16]
DoDAF规则元模型
（点击图片放大）
关于规则数据组，应注意以下事项：
a、 规则约束活动。例如，限速规则限制驾驶活动。
一些看似静态的规则具有限制可能活动的效果。对于
例如，安全围栏必须为10英尺高的规则限制了
建筑安全围栏。在某些条件下，该约束可能适用或变化。
例如，在恶劣天气条件下，速度限制可能较低。
b、 安全分类、安全标记、可发布性等是指南的类型。
类似地；规则是一种更强的指导形式。
c、 一个重要的约束类型是服务策略，它约束对能力的访问
表演者。
d、 根据定义，条令限制了军事行动。
核心流程中的使用
规则数据用于创建、记录和共享支持的所有类型的规则
运营活动和/或运营过程中能力的执行（复合
活动）。这些数据可以包括：
a、 定义必须交换或传递数据的事务的流程
执行指定的活动，如PPBE、CPM、JCIDS或DAS。
b、 定义访问网络中心内信息或服务的方法的规则
58
DM2-规则
http://cio-nii.defense.gov/sites/dodaf20/rules.html[2011年3月3日下午3:43:16]
环境，如Ops、PPBE、CPM或JCIDS。
c、 中必须执行的一系列操作中发生的步骤顺序
特定订单，如DAS、SE、PPBE或CPM。
d、 定义选项或未来行动分析的规则，如作战计划、JCIDS、PPBE
或CPM。
规则的数据在六个核心流程中以以下方式使用：
a、 JCIDS：
1） 对于作为DOTMLPF分析一部分的装备设施、安装和现场权衡
2） 用于详细说明互操作性要求。
3） 约束处理材料和非材料解决方案的需求。
4） 将条令和TT&P与材料和非材料解决方案相关联。
b、 PPBE：
1） 在规划和方案编制过程中，许多规则适用于成本效益
权衡、成本估算、项目结构和项目约束。
c、 DAS：
1） 在DA的技术和程序方面

LDSYN-101 3BHE005555R0101 模拟量智能输入输出卡 

LDSYN-101 3BHE005555R0101 模拟量智能输入输出卡 
formal requirement-gathering process during the initial stages of a Project or during activity
analysis, or event analysis. In this case, the collecting of the business rules is coincidental to
the larger discovery process of determining the workflow of a process. Projects such as the
launching of a new system or service that supports a new or changed business operation
might lead to a new body of business rules for an organization that would require employees
to conceptualize the purpose of the organization in a new way. This practice of coincidental
business rule gathering is vulnerable to the creation of inconsistent or even conflicting
business rules within different organizational units, or within the same organizational unit
over time.
The DoDAF Meta Model provides a set of clear, concise data about rules that facilitates the
creation of rules and enables the sharing of those rules with others requiring similar
information.
A rule is not a process - the two, while related, are very different. A process is a
transformation that produces new things (outputs) from existing things (inputs), while a rule
prescribes the exact procedures to be used to ensure that the output is as to be expected in
each instance that the process is executed.
Data Group Description
The DoDAF Meta Model for the data comprising Rules is shown in the figure below.
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
57
DM2 - Rules
http://cio-nii.defense.gov/sites/dodaf20/rules.html[3/3/2011 3:43:16 PM]
DoDAF Meta Model for Rules
(Click image to enlarge)
The following should be noted about the Rules Data Group:
a. A Rule constrains Activities. For example, a speed limit rule constrains driving activity.
Some seemingly static rules have the effect of limiting possible activities. For
example, a rule that security fences must be 10 feet high constrains the activity of
building security fences. This constraint may apply or vary under certain conditions.
For example, speed limits can be lower in poor weather conditions.
b. Security classification, security marking, releasability, etc. are types of Guidance.
Similarly; a Rule is a stronger form of Guidance.
c. An important Constraint type is a Service Policy that constrains access to capability
Performers.
d. Doctrine, by definition, constrains military action.
Usage in Core Processes
Rules data are used to create, document, and share rules of all types that support
operational activities and/or the execution of capabilities in operational processes (composite
activities). These data can include:
a. Processes that define transactions where data must be exchanged or passed to
execute a specified activity, such as PPBE, CPM, JCIDS, or DAS.
b. Rules that define methods of accessing information or services within the net-centric
58
DM2 - Rules
http://cio-nii.defense.gov/sites/dodaf20/rules.html[3/3/2011 3:43:16 PM]
environment, such as Ops, PPBE, CPM, or JCIDS.
c. The order of steps that occur in a series of actions that must be performed in a
specific order, such as DAS, SE, PPBE, or CPM.
d. Rules defining analysis of options or future actions, such as Ops Planning, JCIDS, PPBE
or CPM.
Data for Rules are used in the six core processes in the following ways:
a. JCIDS:
1) For Materiel Facility, Installation, and Site trade-offs as part of DOTMLPF analyses
2) For detailing Interoperability requirements.
3) In constraining requirements dealing with material and non-material solutions.
4) In relating Doctrine and TT&P to material and non-material solutions.
b. PPBE:
1) In the Planning and Programming process many rules are applied to cost-benefit
tradeoffs, cost estimation, program structure, and program constraints.
c. DAS:
1) In both technical and programmatic aspects of the DA