简而言之，ABD工作流程可以被描绘在RUP阶段，就像图3中所示的那样，而且还可以应用于跨项目的边界处，图4反映了这一点。
To summarize, the ABD workflows can be mapped on to the RUP phases as shown in Figure 3, and are applicable across project boundaries, as shown in Figure 4.
通常情况下，这种方法增加了跨越被采用的开发过程中的的工作流程、阶段，以及迭代来产生文档的需求。
Usually, this imposes a need to generate documentation across workflows, phases, and iterations in the adopted development process.
实际上，在ASDI项目的第一阶段中，为了演示图形化的用户界面，在分析用户工作流程的过程中我们尝试使用了这两种方法。
We actually tried both of these approaches during Phase 1 of the ASDI project, in the context of analyzing the user workflow for an administration graphical user interface.
第二阶段将任务(及其他BPEL制品)连接到一起从而确定流程的工作流。
The second stage would be to connect the tasks (and other BPEL artifacts) together thereby determining the workflow of the process.
项目管理工作流程的结果是高级的项目计划，包括阶段目标，可发布的中间版本，角色，以及图6中表示的关键工作流的时间框。
The project management workstream results in a high-level project plan with milestones, deliverables, roles, and timeframes for the key workstreams represented in Figure 6.
图1：RUP的阶段和工作流程。
在政务工作流模型的基础上，还引入两阶段设计的思想，通过使用流程设计模式简化政务流程的设计。
Moreover, based on the proposed government workflow model, the concepts of workflow design pattern and two-phase design are presented to simplify the design of government workflow.
传统工作流管理方法存在的一个问题是：设计阶段工作通常由业务专家具体执行，并力求体现企业管理层改进当前业务流程的思想。
This is typically done by a business consultant and is driven by ideas of management on improving the business processes at hand.
工作流程执行阶段引擎核心服务是衍生自此抽象基底类别。
WorkflowCommitWorkBatchService created by the workflow runtime engine if no other WorkflowCommitWorkBatch service is added.
工作流程执行阶段引擎实作锁定语意，以限制存取储存在资料存放区中的工作流程执行个体状态。
The workflow runtime engine implements locking semantics to restrict access to a workflow instance state that is saved in a data store.
在需求分析阶段运用UML中的用例图分析了系统的主要用例，划分了功能模块并给出了系统中重要的工作流程。
It analyzes the system with the use case picture in UML during the course of requirement analysis and divides the function module and provides the important workflow in the system.
通过对现有工作流引擎的对比，采用基于JBPM实现工作流引擎的方案，并在JBPM基础上进行了扩展，增加了阶段和挂载流程的处理。
By contrast to existing workflow engine, we adopt the implementation plan of JBPM-based workflow engine, and extend and increase processing stages and mounting process based on JBPM.
通过在流程建模阶段扩展工作流管理联盟的工作流元模型相关定义，重点分析了动态路由和多版本流程迁移在流程运行阶段的调度实现。
It extended basic workflow definition that proposed by workflow management coalition in the process-modeling phase, and mainly introduced the runtime implementation of dynamic characteristics.
表示组态档内的区段，用来定义工作流程执行阶段引擎的设定。
Represents a section, within a configuration file, that defines Settings for the workflow run-time engine.
包含用于设定工作流程执行阶段引擎的类别。
Contains classes that are used to configure the workflow runtime engine.
表示必须加入至工作流程执行阶段引擎才能启动本机服务通讯的服务。
Represents a service that must be added to the workflow run-time engine for local services communications to be enabled.
您的服务可能需要保留一些剩馀功能以支援其他服务，直到工作流程执行阶段引擎叫用所有工作流程执行阶段引擎的停止方法为止。
Your service may need to retain some residual functionality to support other services until all the workflow runtime engine services have had their stop methods invoked by the workflow runtime engine.
工作流程执行阶段引擎会快取其追踪设定档。
当工作流程执行阶段引擎为追踪服务没有关联追踪设定档的工作流程类型要求设定档时，将传回这个新的预设设定档。
SqlTrackingService will return the default tracking profile to the workflow runtime engine for any workflow type for which it doesn't have a tracking profile associated in its database.
当工作流程执行阶段引擎为追踪服务没有关联追踪设定档的工作流程类型要求设定档时，将传回这个新的预设设定档。
SqlTrackingService will return the default tracking profile to the workflow runtime engine for any workflow type for which it doesn't have a tracking profile associated in its database.
应用推荐