Use Case Driven OOAD

╰半橙微兮° 2021-12-16 15:03 219阅读 0赞

The fact that we’ve been able to teach this process, with only minimal changes, over an entire decade, with it remaining useful and relevant today, is made possible because our process is based on finding the answers to some fundamentally important questions about a system. These questions include the following:

  • Who are the users of the system (the actors), and what are they trying to do?
  • What are the “real world” (problem domain) objects and the associations among them?
  • What objects are needed for each use case?
  • How do the objects collaborating within each use case interact?
  • How will we handle real-time control issues?
  • How are we really going to build this system on a nuts-and-bolts level?

转载于:https://www.cnblogs.com/kapok/archive/2005/10/27/262948.html

发表评论

表情:
评论列表 (有 0 条评论,219人围观)

还没有评论,来说两句吧...

相关阅读

    相关 Use Case 和User Story

    Use Case(用例)和User Story(用户故事)他们之间究竟有什么联系和区别,还是他们本身就是一个物种的两种不同叫法而已,究竟哪个好或是哪个不好,这些问题的讨论见诸

    相关 Java面试之 OOAD & UML

    1、UML 是什么?常用的几种图?【基础】 答:UML 是标准建模语言;常用图包括:用例图,静态图(包括类图、对象图和包图),行为图,交互图(顺序图,合作图),实现图。

    相关 Use Case框图

    Use Case 框图用于显示系统功能(或称为使用案例)与提供或接收系统信息的人或系统(或称为角色)之间的相互关系,也即该框图需显示从用户角度出发对系统提出的要求。所以它可供用