Use case diagram explained

A use case diagram^[1] is a graphical depiction of a user's possible interactions with a system.A use case diagram shows various use cases and different types of users the system has and will often be accompanied by other types of diagrams as well. The use cases are represented by either circles or ellipses. The actors are often shown as stick figures.

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".^{[2] [3]}

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".^[4]

See also

• Agile software development
• Business case
• Fundamental modeling concepts
• Object Process Methodology
• SysML
• Unified Modeling Language
• User story

Bibliography

• Gemino, A., Parker, D.(2009) "Use case diagrams in support of use case modeling: Deriving understanding from the picture", Journal of Database Management, 20(1), 1-24.
• Jacobson, I., Christerson M., Jonsson P., Övergaard G., (1992). Object-Oriented Software Engineering - A Use Case Driven Approach, Addison-Wesley.
• Kawabata, R., Kasah, K. (2007). "Systems Analysis for Collaborative System by Use Case Diagram", Journal of Integrated Design & Process Science, 11(1), 13–27.
• Book: Brett D. McLaughlin. Gary Pollice. David West. Head First Object Oriented Analysis and Design. Shroff Publishers & Distributors Pvt Ltd. December 1, 2006. 978-8-184-04221-4.

Notes and References

1. Book: Use case. Unified Modeling Language 2.5.1. OMG Document Number formal/2017-12-05. December 2017. Object Management Group Standards Development Organization (OMG SDO). 639.
2. Book: Chapter 5. UML & Requirement Diagram (1. Use Case Diagram). Visual Paradigm User's Guide. May 11, 2018. Visual Paradigm Community Circle.
3. Book: Brett D. McLaughlin. Gary Pollice. David West. Head First Object Oriented Analysis and Design. Shroff Publishers & Distributors Pvt Ltd. December 1, 2006. 978-8-184-04221-4. 297.
4. Keng Siau. Lihyunn Lee. Are use case and class diagrams complementary in requirements analysis? An experimental study on use case and class diagrams in UML. Requirements Engineering. 9. 229–237. October 7, 2004. 10.1007/s00766-004-0203-7.