Skip to content

Latest commit

 

History

History
31 lines (17 loc) · 2.37 KB

uml-use-case.md

File metadata and controls

31 lines (17 loc) · 2.37 KB
title
UML / Use Case Diagram

UML / Use Case Diagram

  • Use case diagram - Wikipedia

    • A use case diagram at its simplest is a representation of a USER'S INTERACTION WITH THE SYSTEM that shows the relationship between the user and the different use cases in which THE USER IS INVOLVED.

      A use case diagram can IDENTIFY THE DIFFERENT TYPES OF USERS of a system and the different use cases and will often be accompanied by other types of diagrams as well. The use cases are represented by either circles or ellipses.

      Use case diagram 的目的是為了識別系統要滿足哪些 use case，而這些 use case 又涉及哪些類型的 user；覺得太簡單沒存在的必要? 下面提到是跟 stakeholder 溝通的 high-level view 就不會覺得怪了。

    Application

    • While a use case itself MIGHT DRILL INTO A LOT OF DETAIL about EVERY POSSIBILITY, a use-case diagram can help provide a HIGHER-LEVEL VIEW of the system.

      It has been said before that "Use case diagrams are the blueprints for your system". They provide the simplified and graphical representation of WHAT THE SYSTEM MUST ACTUALLY DO.

      確實 use case 可以展開很多細節 (各種變化的 scenario)，但這裡刻意提高視角 -- 忽略細節。

    • Due to their simplistic nature, use case diagrams can be a good communication tool FOR STAKEHOLDERS. The drawings attempt to mimic the real world and provide a view for the stakeholder to understand how the system is going to be designed.

      Siau and Lee conducted research to determine if there was a valid situation for use case diagrams at all or if they were UNNECESSARY. What was found was that the use case diagrams conveyed the intent of the system in a more simplified manner to stakeholders and that they were "interpreted more completely than class diagrams".

      The purpose of the use case diagrams is simply to provide the high level view of the system and CONVEY THE REQUIREMENTS IN LAYPEOPLE'S TERMS FOR THE STAKEHOLDERS. Additional diagrams and documentation can be used to provide a complete FUNCTIONAL and TECHNICAL view of the system.

      圖很簡單是刻意的，重點是要用 stakeholder 也看得懂的 term 來講，技術細節是其他 diagram 的事。

  • Use case - Wikipedia #ril