用例建模有帮助吗？
i would like to design my program
alt text http://img405.imageshack.us/img405/331/helpq.jpg
what about relationships beetween use case?
this is my use case Is that correct??
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（2）
你的符号看起来是正确的，但正如尼尔和克里斯指出的那样，除此之外几乎没有什么可以判断的。这是帮助您组织想法、理解大粒度用例和涉及的参与者的良好开端。现在，您需要继续将大粒度用例分解为更有针对性、更细粒度的步骤。文本用例对此很有帮助。您可以查看 Alastair Cockburn 的编写有效用例了解更多信息。
一旦合理定义了步骤，您就可以进入活动图以更清楚地显示逻辑流程，然后进入序列图，在其中您将真正开始充实交互的细节。请注意，这不是一个严格的线性过程。您在创建每个工件时发现的事情可能需要您重新访问以前的图表。然而，随着您的继续，您的用例、类图和其他工件将演变成目标系统的更好表示。
Your notation looks correct, but as Neil and Chris point out, there is very little to judge beyond that. This is a good start in helping you organize your thoughts, understanding the large-grained use cases and involved actors. Now, you need to proceed to break down the large-grained use cases into more-focused, finer-grained steps. Textual use cases are good for this. You might check out Writing Effective Use Cases by Alastair Cockburn for more information.
Once you have your steps reasonable defined, you can then flow into Activity Diagrams to more clearly show the logical flow, then on to Sequence Diagrams where you will really begin to flesh out the details of interaction. Note that this is not a strict linear process. Things you discover as your create each artifact likely will require you to revisit previous diagrams. As you proceed, however, your Use Cases, Class Diagrams, and other artifacts will evolve into a better representation of your target system.
不，这只是一个用例图。每个气泡都可以分解为适当的用例，这些用例标识图中的参与者执行该用例所执行的步骤。
有关用例的更多信息，请查看此处：http://www.parlezuml.com/tutorials/usecases .htm
No, this is just a Use Case Diagram. Each of those bubbles can be broken out into proper use cases that identify the steps that the actors in the diagram perform to execute that use case.
For more about use cases, look here: http://www.parlezuml.com/tutorials/usecases.htm