use cases Flashcards

1
Q

what are use cases often used for

A

to derive functional requirements

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
1
Q

what is the best way to discover requirements and what are some limitations

A

talking to stakeholders

they may express them in their own terms
the can change their minds
system developers may make assumptions

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
2
Q

what is a use case

A

a behavioural model of a system
also a standard part of uml

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
2
Q

what do use cases consist of

A

use case diagram and description

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
3
Q

what are some positives of use cases (4)

A

graphical
you describe sample scenarios which are easy to discuss with the user
easy way to communicate between different stakeholders
used to derive test cases

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
3
Q

how are use cases represented in the model

A

ovals

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
4
Q

what does the box in a use case model represent

A

system boundaries

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
4
Q

how is a use case written

A

a verb noun phrase that represents where the system would be used

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
5
Q

actor

A

a user system or device that interacts with the system

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
6
Q

use case description

A

a sequence of steps that identifies what you need to do to complete a use case

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
7
Q

primary actor

A

the actor that wants to achieve the use case

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
8
Q

secondary actor

A

interacts with the use case in order to help the primary actor complete it

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
9
Q

precondition

A

activities that must take place before the use case can start

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
10
Q

flow of events

A

user actions and system responses that take place under the regular execution of the use case

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
11
Q

alternate flows

A

you must complete another task before going back to the flow of events

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
12
Q

post conditions

A

the state of the system when the use case has been completed

13
Q

why do we not use control statements and what do we use instead

A

it can make our description too algorithmic so we use scenarios instead

14
Q

primary scenario

A

what we expect to be normal behaviour

15
Q

secondary scenarios

A

reveal useful information e.g. exceptions

16
Q

«include»

A

adds one use case’s behaviour into another when it is mandatory

17
Q

«extend»

A

adds optional/conditional behaviour to another use case

18
Q

exceptions

A

scenarios where the postcondition cannot be fulfilled

19
Q

alternatives

A

different ways to fulfil the post conditions

20
Q

what are the 4 levels of use case detail

A

cloud level
sea level
fish level
bottom-of-the-ocean level

21
cloud level
v high level summary - usually a business goal
22
sea level
user goal; single sitting and the user gets a result
23
fish level
include/extend goals
24
bottom-of-the-ocean level
too low!!
25
which levels are recommended for use cases
sea and fish level
26
what is "weird" about non-functional requirements in use cases
the don't appear explicitly in use cases instead you can use simple annotations to add them in e.g. nfr
27
how do we deal with making use cases for overly complex systems
we can break them down into subsystems and each one can interact with another as an actor
28
what is the main criteria for use case testing
there should be a test case for at least each flow in the use case