A business use case will become a subsystem.
业务用例将变成一个子系统。
Defining the business use case: Fishing reports.
定义业务用例：垂钓报告。
Figure 1: Example of a business use case specification.
图1：一个业务用例规格的例子。
For example, a business process becomes a business use case.
例如，业务模型变为业务用例。
Typically our business use case knows what data is required.
典型情况下，我们的业务很清楚需要哪些数据。
This concept is captured in the Business Use Case Realizations.
此概念在业务用例实现中获得。
The flow of events, or workflow, is a key element of a business use case.
事件流、或者工作流程流，是业务用例的一个关键要素。
Now you have a well-structured and understandable business use case model.
现在你有一个结构良好并可以理解的业务用例模型。
In my experience, it is best to avoid these in your business use case model.
以我的经验，最好在你的业务用例模型中避免这些联系。
The terms business function and business use case can be used interchangeably.
术语业务功能和业务用例的使用可以互换。
In RUP terms, we rebuild the Business Use Case and its Business Analysis Model.
在RUP的术语中，我们重新构建业务用例及其业务分析模型。
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 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 11 shows how the business workers of the Developing Schedule Definition business Use Case Realization cooperate to implement the activity.
图11显示了开发进度定义(Developing Schedule Definition)业务用例实现的业务操作者如何合作来实现活动。
应用推荐