Use-case Analysis step 1: Create a use-case realization.
用例分析第一步：建立一个用例实现。
A use-case realization may require work on each of these layers.
用例实现可能需要在这些层之上的工作。
Use-case realization team session to discuss and design the use-case realizations.
用例实现的团队会议讨论和设计用例实现。
Therefore, a formal a design model may not be the best output artifact for a use-case realization session.
因此，正式的设计模式也许不是用例实现会议的最好的输出工件。
It has several other work products as optional inputs, such as use-case realization, analysis class, glossary, and so on.
它也包括了可选择输入的一些其他工作产品，像用例实现，分析类，术语表等等。
As output work products, the task defines a use-case realization as well as the analysis model comprising analysis classes.
作为工作产品的输出，任务定义了一个用例实现和分析模型组成的一个分析类。
Interaction diagrams are informal documents used to communicate design ideas that come up during the use-case realization team sessions.
交互图是用于交流在用例实现团队会议中出现的设计思想的非正式文档。
Figure 2: Use-case realization team sessions should include the system architect and developers responsible for implementing the use case.
图2：用例实现的团队会议应该包括系统架构师和负责实现用例的开发人员。
The goal of a use-case realization is to produce a well-structured object-oriented design for implementing behavior defined in the use case.
用例实现的目标是生成用于实现用例中定义的行为的良构的面向对象的设计。
Depending on the severity of the design issues, the system architect might even want to hold another meeting to revisit the whole use-case realization in context.
根据设计问题的严重性，系统架构师甚至可能想要召开另一个会议，以在环境中重温整个用例实现。
These are to be expected; only the experience a team acquires over time as it conducts use-case realization sessions can minimize or even eliminate these problems.
这些是可能发生的，只有随着时间的过去，团队在进行用例实现会议时所获得的经验可以最小化，或者甚至消除这些问题。
Use-case realization sessions should produce a main output artifact; software development processes often suggest a design model composed of interaction and design class diagrams.
用例实现会议应该生成主要的输出工件，软件开发过程常常提出由交互和设计类图组成的设计模型。
Whether it is necessary to code responsibilities in other layers will be driven mainly by the system's architectural style and design decisions made during the use-case realization session.
是否有必要在其他层中对职责编码主要取决于在用例实现会议中做出的系统架构风格和设计的决策。
In other words, if the directions in the SAD together with the actual Use-Case Specification are sufficient for the developer to build the code of the use case, the Use-Case Realization is empty.
换句话说，如果SAD中的指示，连同实际的用例规格说明对开发人员来说足够构建用例的代码，那么用例实现就是空的。
However, even if one person is capable of doing every part of the design and implementation for a use case on a small project, it is imperative that creating the use-case realization be a team effort.
然而，即使一个人能够完成小项目中一个用例的设计和实现的每一个部分，生成用例实现也必须是一个团队的工作。
Use Case Storyboards provide an additional way of describing the realization of a Use Case.
用例情节串联模板提供了另外一种描述用例实现的方式。
In fact, every message that enters into the worker can be thought to become the realization of a System Use Case implementing the worker's functionality.
实际上，每个进入操作者的消息可以被认为是实现操作者功能的系统用例的实现。
Software elements can use UML and use case realization, an approach very similar to MDSD, but applied at the software design level, to create the technical design of the software.
软件元素能够使用UML和用例实现(一种同MDSD非常类似的方法，但是被应用于软件设计层级上)，创建软件的技术设计。
In analysis, our use case realization contains only analysis classes and objects, which may populate various UML diagrams such as class diagrams and interaction diagrams.
在分析阶段，我们的用例实现只包括分析类及分析对象，它们能组装成不同的UML图如类图和交互图。
In this context, the business use case realization can also be considered the definition of a Scenario.
在这种情况下，业务用例实现也可以视为场景的定义。
As that model is refined it may describe the nature of the use case realization, identifying components and services used to implement the use case.
由于模型经过了优化，因此可能会描述用例实现的本性，对用于实现用例的组件和服务进行标识。
Identifying and naming a use case realization provides traceability from the interactions diagrams and textual commentary back to the use case.
确认并命名一个用例实现保证了交互图和文本注释回到用例的可追踪性。
This is done through the business use case realization, which then becomes the means to create a link between the process, the business use cases and, indirectly, also the business goals.
这通过业务用例实现来完成，之后将成为创建流程、业务用例，间接地，还有业务目标之间关联的方法。
The relationship can be derived from the model by following the formal traces starting from a business goal, to the business use case realization, to the use case, and finally to the User Goal.
该关系可以源自于模型，通过从业务目标开始，到业务用例实现，到用例，并且最终到用户目标的形式化的追溯。
Realization is a formal term in use case modeling that indicates the relationship between a specification of something and its various implementations.
所谓的实现是用例建模中的一个规范化术语，它指示了规格与各种执行之间的关系。
Before we get into a formal definition of a realization, let's step back and ask, "What really is a use case?"
在我们给出用例实现的定义之前，回过头来看一下，到底什么是用例？
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工件进行形式化。
Figure 4 shows the basic flow of interactions among the participants in the Create Job Template use case realization.
图4表示了CreateJobTemplate用例实现中参与者之间的基本交互流程。
Use Case Design step 1: Create use case realization for each use case
用例设计第1步：为每个用例创建用例实现
Figure 3 shows the Participants class diagram for the Create Job Template use case realization.
图3显示了CreateJobTemplate用例实现中的参与者(Participants)类图。
应用推荐