扩展所有用例 [英] Extend all use-case
问题描述
我对uml有疑问，并扩展了用例的表示法。
如何扩展所有用例。
例如，如果我创建了一个连接断开的用例，该用例几乎扩展了所有用例，但我不想将所有用用例图上的符号连接起来，原因是很难理解的。我该怎么办？
I have a question about uml and extend notation of use-case. How I can extend all use case. For example if I created a connection down use case that extend almost all use case, but I don't want to connect all with the notation on the use case diagram cause is very orrible to see. How can I do?
推荐答案
首先：用例的重要性
建模用例图（用例建模）在软件分析中非常重要步骤，用例建模应由专业分析师执行：
First of all: the importance of Use Cases
Modeling Use Case Diagrams (Use Case Modeling) is SO important step in Software Analysis and Use Case Modeling should be performed by professional Analysts:
- 所有估计（时间，预算，资源等）均基于用例进行。
- 在某些用例驱动的方法中，所有后续步骤均基于用例。
- 等。
其次：了解用例建模陷阱。
在用例建模中，我们需要考虑一些与您的问题相关的陷阱：
Secondly: Knowing Use Case Modeling Traps.
In Use Case Modeling there are some traps that we need to conside related to your question:
- （陷阱＃ 1：用户不理解的使用情况。）（请参阅参考1 ）
- (Trap #1: Use cases that users don't understand.) (see reference 1)
用例是表示用户需求的一种方式，它描述了
用户需要如何使用该产品。用例
应该专注于用户需要借助
系统完成的任务，因此它们应与用户的业务流程相关。
您的用户应该能够阅读并查看用例，以发现
可能的问题，例如缺少替代流程或错误地处理了
的异常。如果用户无法与用例相关，则存在
问题。也许从技术角度，而不是从业务角度，他们写了太多的东西。
Use cases are a way to represent user requirements, which describe what the user needs to be able to do with the product. Use cases should focus on tasks a user needs to accomplish with the help of the system, so they should relate to the user's business processes. Your users should be able to read and review use cases to find possible problems, such as missing alternative flows or incorrectly handled exceptions. If users cannot relate to use cases, there's a problem. Perhaps they're written too much from a technical, rather than business, perspective.
- （陷阱4：描述特定的用户界面元素和操作）（请参阅参考1 ）
- (Trap #4: Describing specific user interface elements and actions) (see reference 1)
编写必要用例，以抽象级别描述
用户与系统之间的交互，而无需合并
用户界面的细节。用例描述不应包括
a屏幕设计，尽管简单的用户界面原型可能对
有价值，以利于用例探索。
Write "essential" use cases that describe the interactions between the user and the system at an abstract level, without incorporating user interface specifics. The use case description should not include a screen design, although simple user interface prototypes can be valuable to facilitate the use case exploration.
-
（2。对于每个用例都没有明确的业务目标）（请参阅参考2 ）
（6。也要指定用例（请参见参考2 ）
(6. Specifying use cases in too much detail) (see reference 2)
第三：用例建模位于方法的需求噬菌体中。
Thirdly: Use Case Modeling is in the Requirement phage of methodologies.
我们不应在用例中放入常见的实现方法。在方法的下一步中，其他图中处理的实现中的常用方法。 （也许在设计模型中）因此，如果我们将所有通用方法放在用例模型中，用例的数量将大量增加。 （并且我们在第一部分中提到的估计有误）
We should not put common implementation methods in Use Cases. Common methods in implementation handled by other diagrams in next steps of methodology. (maybe in Design Model) So, if we put all common methods in Use Case Model, the number of use cases increases a lot. (and our estimation as mentioned in first part goes wrong)
这篇关于扩展所有用例的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！
