10 misconceptions about use cases

Post on 28-Nov-2014

740 Views

Category:

Technology

2 Downloads

Preview:

Click to see full reader

DESCRIPTION

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

TRANSCRIPT

Does Everyone has the same view

on Use Cases as you do?

Ever met someone that completely

misunderstood Use Cases?

”No they don't”&

”I have!”

This is my top 10-list of

misconceptions!

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

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

NOT TRUE!!!

Use cases are as agile as you are!Use cases are as agile as you are!

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

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

NOT TRUE!!!

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

3. Use cases are the only requirements document

3. Use cases are the only requirements document

NOT TRUE!!!

Supplement with other documents Supplement with other documents as you needas you need

Supplement with other documents Supplement with other documents as you needas you need

Gen

eric

G

ener

ic

req

uir

em

ents

req

uir

em

ents

Supplement with other documents Supplement with other documents as you needas you need

Gen

eric

G

ener

ic

req

uir

em

ents

req

uir

em

ents

Bu

sin

ess

Bu

sin

ess

rule

sru

les

Supplement with other documents Supplement with other documents as you needas you need

Gen

eric

G

ener

ic

req

uir

em

ents

req

uir

em

ents

Bu

sin

ess

Bu

sin

ess

rule

sru

les

Glo

ssar

yG

loss

ary

Supplement with other documents Supplement with other documents as you needas you need

Gen

eric

G

ener

ic

req

uir

em

ents

req

uir

em

ents

Bu

sin

ess

Bu

sin

ess

rule

sru

les

Glo

ssar

yG

loss

ary

Leg

al

Leg

al

req

uir

emen

tsre

qu

irem

ents

and many many more and many many more (at least in some cases) (at least in some cases)

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

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

NOT TRUE!!!

You can use text You can use text or what ever drawings you likeor what ever drawings you like

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

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

NOT TRUE!!!

There can be as many steps There can be as many steps as you like it to beas you like it to be

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

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

NOT TRUE!!!

RUP offers a variety RUP offers a variety of non-compulsary techniquesof non-compulsary techniques

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

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

NOT TRUE!!!

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

NOT TRUE!!!

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

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

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

NOT TRUE!!!

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

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

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

NOT TRUE!!!

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

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

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

NOT TRUE!!!

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

10 Misconceptions about use cases

By Andreas Hägglundhttp://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

top related