Ten common misconceptions about how to use use cases, a technique for specifying requirements. Written by Andreas Hägglund, a consultant with more than 10 years of experience working with use cases and systems development. Feel free to use the presentation if you give credit to the Author and to Systemvaruhuset. Company webpage: http://www.systemvaruhuset.se Personal blog: http://www.systemvaruhuset.net

1. Does Everyone has the same view
on Use Cases as you do?

2. Ever met someone that completely
misunderstood Use Cases?

3. ”No they don't”
&
”I have!”

4. This is my top 10-list of
misconceptions!

5. 1. Use cases are not agile1. Use cases are not agile

6. 1. Use cases are not agile1. Use cases are not agile
NOT TRUE!!!

7. Use cases are as agile as you are!Use cases are as agile as you are!

8. 2. Use cases require user interactions2. Use cases require user interactions

9. 2. Use cases require user interactions2. Use cases require user interactions
NOT TRUE!!!

10. Use cases are valid for all processesUse cases are valid for all processes

11. 3. Use cases are the only
requirements document

12. 3. Use cases are the only
requirements document
NOT TRUE!!!

13. Supplement with other documentsSupplement with other documents
as you needas you need

14. Supplement with other documentsSupplement with other documents
as you needas you need
GenericGeneric
requirementsrequirements

15. Supplement with other documentsSupplement with other documents
as you needas you need
GenericGeneric
requirementsrequirements
BusinessBusiness
rulesrules

16. Supplement with other documentsSupplement with other documents
as you needas you need
GenericGeneric
requirementsrequirements
BusinessBusiness
rulesrules
GlossaryGlossary

17. Supplement with other documentsSupplement with other documents
as you needas you need
GenericGeneric
requirementsrequirements
BusinessBusiness
rulesrules
GlossaryGlossary
LegalLegal
requirementsrequirements

18. and many many moreand many many more
(at least in some cases)(at least in some cases)

19. 4. Use cases are text based4. Use cases are text based

20. 4. Use cases are text based4. Use cases are text based
NOT TRUE!!!

21. You can use textYou can use text
or what ever drawings you likeor what ever drawings you like

22. 5. The main flow must not be more5. The main flow must not be more
than 7 stepsthan 7 steps

23. 5. The main flow must not be more5. The main flow must not be more
than 7 stepsthan 7 steps
NOT TRUE!!!

24. There can be as many stepsThere can be as many steps
as you like it to beas you like it to be

25. 6. If you're doing RUP you must do6. If you're doing RUP you must do
use casesuse cases

26. 6. If you're doing RUP you must do6. If you're doing RUP you must do
use casesuse cases
NOT TRUE!!!

27. RUP offers a varietyRUP offers a variety
of non-compulsary techniquesof non-compulsary techniques

28. 7. If you do use cases, you do RUP7. If you do use cases, you do RUP

29. 7. If you do use cases, you do RUP7. If you do use cases, you do RUP
NOT TRUE!!!

30. 7. If you do use cases, you do RUP7. If you do use cases, you do RUP
NOT TRUE!!!

31. You're free to do use casesYou're free to do use cases
whenever you feel like itwhenever you feel like it

32. 8. Use cases makes dialogue needless8. Use cases makes dialogue needless

33. 8. Use cases makes dialogue needless8. Use cases makes dialogue needless
NOT TRUE!!!

34. Use cases are the basis for conversationsUse cases are the basis for conversations

35. 9. A use case is faulty if it is not9. A use case is faulty if it is not
specified according to the UMLspecified according to the UML

36. 9. A use case is faulty if it is not9. A use case is faulty if it is not
specified according to the UMLspecified according to the UML
NOT TRUE!!!

37. A correct use case is understoodA correct use case is understood
by the client, the developers and the testersby the client, the developers and the testers

38. 10. Use cases are not suited for non10. Use cases are not suited for non
functional requirementsfunctional requirements

39. 10. Use cases are not suited for non10. Use cases are not suited for non
functional requirementsfunctional requirements
NOT TRUE!!!

40. Use cases are suitable for all requirementsUse cases are suitable for all requirements
linked to a specific processlinked to a specific process

41. 10 Misconceptions about use cases
By Andreas Hägglund
http://www.linkedin.com/in/andreashagglund
Corporate site: http://www.systemvaruhuset.se/
Personal site: http://www.systemvaruhuset.se/
10 Misconceptions about Use Cases © Andreas Hägglund, Systemvaruhuset May 22, 2013