Chapter 1 Flashcards

1
Q

A thing that is needed or wanted; something that is compulsory; a necessary condition

A

Requirement

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

Requirements are the ____

A

What

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

What is the first truth about requirements engineering?

A

Requirements are not really about requirements

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

Requirements focus on understanding a ____ problem and providing a ____ for it

A

Business, Solution

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

What is the art of requirements?

A

To discover the real problem

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

What is the second truth about requirements engineering?

A

Software must be optimally valuable for its owner

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

Who is the owner?

A

Funds the development or the purchase of the software
Pays for the disruption to his/her business
Is buying a benefit

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

T/F The owner is also the end-user

A

F

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

The product must provide a benefit that is in proportion to the cost of the product

A

Optimal value

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

What is the third truth about requirements engineering?

A

You have to know the real need to build the right software

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

Estimated __ percent of errors originate from the requirements activity; eliminate errors early to avoid developing the wrong product

A

60

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

What is the fourth truth about requirements engineering?

A

There is a difference between building SW and solving a business problem

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

T/F Start with the problem to be solved, not a perceived solution

A

T

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

T/F If the team starts with the interface to be developed, that’s fine.

A

F, start with the business problem

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

What is the fifth truth about requirements engineering?

A

Requirements do not have to be written, but they have to become known to the builders

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

Is it a good idea to have unwritten requirements?

A

No, very little good comes from them

17
Q

What is the sixth truth about requirements engineering?

A

The customer/owner may not have the answers

18
Q

How can you earn the right to be there?

A

Do the research and ask the right questions

19
Q

What is the seventh truth about requirements engineering?

A

A requirements process is essential

20
Q

A set of tasks that achieve the intended result

A

Process

21
Q

What is the eighth truth about requirements engineering?

A

Iterative is good; skipping requirements discovery is not

22
Q

What is the ninth truth about requirements engineering?

A

No silver bullet

23
Q

What is the tenth truth about requirements engineering?

A

Requirements Must Be Measurable and Testable

24
Q

What is the eleventh truth about requirements engineering?

A

You might change the way a stakeholder thinks about his/her problem

25
Q

Something the product must do to support the owner’s business

A

Functional requirement

26
Q

The quantification of how well it must carry out its functionality

A

Non-functional requirement

27
Q

global requirements in the form of limitations or restrictions on the eventual design of the product

A

Constraints