Defining the business use case: Fishing reports.
定义业务用例：垂钓报告。
The domain model is useful, even if you do not produce business use case realizations.
域模型很有用，即使你不提出业务用例实现。
Another way to think of a business use case is that it documents a particular business workflow.
另一种思考业务用例的方式是，它记录了特定的业务流程。
In this context, the business use case realization can also be considered the definition of a Scenario.
在这种情况下，业务用例实现也可以视为场景的定义。
You can use this link to navigate between the business process and the business use case that it realizes.
你可以使用这种联系，以在业务流程和它所实现的业务用例之间进行切换。
Fetching strategy is a business level cross cutting concern and it changes based on the business use case.
抓取策略是个业务层的横切关注点，它会随着业务的变化而变化。
Decisions and guard conditions allow business analysts to show alternative paths in a business use case workflow.
决定和守卫条件允许业务分析师在业务用例流程中展示不同的路径。
Describe the Business Use Case Realizations in terms of Business Workers and the messages that they exchange.
定义关于业务操作者和他们所交换的信息的业务用例实现。
For manual tests, the test executor must typically enter data into the application to validate a business use case.
对于手工测试，测试执行者通常要向应用程序输入数据，来验证一个业务用例。
Here we use Aspect Oriented Programming for deciding which fetching strategy needs to used on business use case basis.
这里我们使用了面向方面的编程(Aspect Oriented Programming)以根据业务的不同使用不同的抓取策略。
By this we can use the same service and repository layer APIs to satisfy different business use case requirements.
这样我们就可以使用相同的Service和Repository层API来满足各种不同的业务规则了。
Requirements and business process are integrated in Rational Software Architect with the business use case UML diagram.
在Rational Software Architect中使用业务用例uml关系图集成的需求和业务流程。
Figure 10 shows how the Developing Schedule Definition business use case is realized in terms of three business workers.
图10显示了用三个业务操作者是如何实现开发进度定义(Developing Schedule Definition)业务用例的。
When an organization is complex and trying to automate significant functions, a business use case model can be invaluable.
当一个复杂的开发组织试图自动处理重要的功能时，业务用例模型是非常宝贵的。
The decision of injecting the above fetching strategy for the required business use case is placed in aspect as shown below.
由aspect将上述的抓取策略注入到相关的业务中，如下所示。
The way business use case realizations describe scenarios where users may interact with software systems is shown in Figure 4.
业务用例实现描述用户可能与软件系统交互所处的场景的方法如图4所示。
A similar algorithm is used here to map a business use case model onto another business use case model in a different context.
这里使用一个类似的算法，把一个业务用例模型映射到不同语境中的另一个业务用例模型。
The business modeling performed so far has identified a set of Business Workers who participate in business use case realizations.
所执行的业务建模到目前为止已经确定了一组参与业务用例实现的业务参与者。
Since UML's inception, Activity diagrams have identified and addressed the need for describing the workflow of a business use case.
从UML 出现之初开始，就一直使用活动关系图 (Activity diagram)来标识和处理描述业务用例的工作流的需求。
A business use case describes a business process, documented as a sequence of actions that provides observable value to a business actor.
一个业务用例描述了一个业务流程，记录了一系列动作的顺序，这些动作为业务操作者提供了显而易见的价值。
Figure 12 shows the integrated view of the business model, requirements, and a business use case UML diagram in Rational Software Architect.
图12显示了Rational Software Architect中的业务模型、需求和业务用例uml关系图的集成视图。
Figure 11 shows how the business workers of the Developing Schedule Definition business Use Case Realization cooperate to implement the activity.
图11显示了开发进度定义(Developing Schedule Definition)业务用例实现的业务操作者如何合作来实现活动。
Highlight the Business Use Case Realizations for each Business Use Case, and define how they link back to the Business Process Map activities.
为每个业务用例突出其业务用例实现，并且定义如何连接返回到业务流程图的活动。
We also linked the Purchase Order process to the Purchase Order process business use case to indicate the process realizes the use case (Figure 4).
我们还会将PurchaseOrderProcess与Purchase Order Process业务用例联系起来，以指示过程实现了用例(图4)。
This maintains the link between the service requirements contract, business processes, the business use case, and the business goals and objectives.
在这个过程中会一直保持服务需求契约、业务流程、业务用例及业务目标和目的之间的联系。
So a business use case should describe what the business does — namely, its interactions with its environment — to deliver value to its stakeholders.
所以，业务用例应该描述业务做了什么(也就是同其外部环境进行了那些互操作)，从而将价值传送给其涉众。
Link the Business Model to the System Model by means of dependencies between the System Use Case Realizations and the Business Use Case Realizations.
利用系统用例实现和业务用例实现间的依赖性将业务模型与系统模型连接起来。
As any new business use case might require a different fetching strategy and can be applied with out modifying the lower level service or repository API.
任何新的业务都可能需要不同的抓取策略，这样我们就无需修改底层服务或是Respository层的API就能应用新的抓取策略了。
During the third step, a business Analysis Model is developed wherein each business use case realization is formalized in terms of two major UML artifacts.
在第三个步骤中，将开发业务分析模型，在其中，每个业务用例实现根据两个主要的UML工件进行形式化。
Although there is no business use case for such an analysis engine, it provides a simple way to demonstrate how easy it is to create a UIMA analysis engine.
尽管没有针对这个分析引擎的业务用例，但它以一种简单的方式展示了创建UIMA分析引擎有多么容易。
应用推荐