Chapter 5 Flashcards

1
Q

What are the roles of the requirements engineer/business analyst

A

Investigate the work

Interview and understand stakeholders

Translate and communicate to developers

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

List some trawling techniques

A
Interviewing
Apprenticing
Scenarios
Mind mapping
Essence
Brainstorming
Personas
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
3
Q

What do you do at the start of trawling?

A

Business events to current work

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

What happens by the end of trawling?

A

The requirements for the future work will be defined

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

T/F Interviewing is a critical skill

A

T

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

What’s critical to getting the right answers?

A

Asking the right questions

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

What is useful during interviews as a graphical tool to verify information?

A

Quick and dirty process modeling

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

A series of 3-10 steps that describe the work done by the BUC

A

Scenario

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

What happens when everything goes well; the outcome is expected

A

Normal case

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

When unwanted things happen

A

Exception case

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

Allowable variation on the normal case

A

Alternative case

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

____ = Business results, not output

A

Outcome

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

Defines or constrains one aspect of your business that is intended to assert business structure or influence the behavior of your business

A

Business Rules

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

Pros of high fidelity prototypes

A

Great visualization
Easy to change
Appears to execute requirements
Good for discovering usability requirements

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

Cons of high fidelity prototypes

A

You can build a prototype that could never be implemented

Because the prototype is easy to change, the users may believe software changes are just as easy

Because the prototype can look so much like the end product, users may be dazzled by the “look and feel” and stop innovating

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

Which techniques are best?

A

The ones that you are most comfortable with

The ones that work best in the environment/culture