CSE 110 F23 Final Review || with Errorless Answers.
According to Chapter 1 in HFSD, which of the following is a failing of developing a program in
one big phase?
If a developer leaves the project in the middle, it leaves a big hole that's hard to fill
The developers don't get paid until it's all over.
The developers get tired and start to make silly mistakes
No vacations until it's done!
The developers don't get any feedback from the customer along the way correct answers The
developers don't get any feedback from the customer along the way
According to Chapter 1 of HFSD, which of the following are positive qualities of Iteration in
software development (check all that apply)?
The team gets comfortable with each other on the first iteration, making all the later ones easier.
By running the tests more frequently, you find more bugs.
By doing it over and over, you eventually get it right.
You can adapt on the fly to changing conditions.
You can write code a lot faster. correct answers You can adapt on the fly to changing conditions
According to Chapter 1 of HFSD, an Iteration is:
An internal release for testing and finding bugs.
Putting it out there in the real world for people to use to see how they like it.
A release to the customer to get feedback. correct answers A release to the customer to get
feedback
According to Chapter 1 of HFSD, which of the following are the major concerns of a customer
(check all that apply):
,How much will it cost?
Is this what I asked for?
Will this scale to a lot of users?
How long will it take?
Is it bug-free? correct answers How much will it cost?
Is this what I asked for?
How long will it take?
According to Chapter 1 of HFSD, which of the following is the customer going to give the
software development team for an iteration:
A: Stable requirements for an iteration's functionality
B: Adequate time and budget
Both A and B
Neither A nor B correct answers Neither A nor B
According to HFSD Ch2, when it comes to requirements gathering, assumptions are (check all
that apply):
A way of staying on schedule when encountering ambiguity
The list of things that the developers will take on ("assume") in implementing the requirement
Gaps in the developers' understanding
Exposed and discussed in the planning game
Something to discuss with the customer if you can't solve it yourselves
Risks correct answers Gaps in the developers' understanding
Exposed and discussed in the planning game
Something to discuss with the customer if you can't solve it yourselves
, Risks
According to HFSD Ch2, how many iterations of the planning game are required?
As many as required to remove as many assumptions possible.
One - take the average of the team's estimates
Two - need to narrow the spread before averaging correct answers As many as required to
remove as many assumptions possible
According to HFSD Ch2, who should be involved in gathering the information for the user
stories?
The customer
Pretty much anybody touched by the software
The customer and the developers correct answers Pretty much anybody touched by the software
According to HFSD Ch2, a user story is (check all that apply):
Detailed and relatively complete
A story about the user
A single thing that the system should do
A statement of a software requirement in the customer's language
Completable in 15 days or less
Concise (short) correct answers A single thing the system should do
A statement of a software requirement in the customer's language
Completable in 15 days or less
Concise (short)
According to Chapter 1 in HFSD, which of the following is a failing of developing a program in
one big phase?
If a developer leaves the project in the middle, it leaves a big hole that's hard to fill
The developers don't get paid until it's all over.
The developers get tired and start to make silly mistakes
No vacations until it's done!
The developers don't get any feedback from the customer along the way correct answers The
developers don't get any feedback from the customer along the way
According to Chapter 1 of HFSD, which of the following are positive qualities of Iteration in
software development (check all that apply)?
The team gets comfortable with each other on the first iteration, making all the later ones easier.
By running the tests more frequently, you find more bugs.
By doing it over and over, you eventually get it right.
You can adapt on the fly to changing conditions.
You can write code a lot faster. correct answers You can adapt on the fly to changing conditions
According to Chapter 1 of HFSD, an Iteration is:
An internal release for testing and finding bugs.
Putting it out there in the real world for people to use to see how they like it.
A release to the customer to get feedback. correct answers A release to the customer to get
feedback
According to Chapter 1 of HFSD, which of the following are the major concerns of a customer
(check all that apply):
,How much will it cost?
Is this what I asked for?
Will this scale to a lot of users?
How long will it take?
Is it bug-free? correct answers How much will it cost?
Is this what I asked for?
How long will it take?
According to Chapter 1 of HFSD, which of the following is the customer going to give the
software development team for an iteration:
A: Stable requirements for an iteration's functionality
B: Adequate time and budget
Both A and B
Neither A nor B correct answers Neither A nor B
According to HFSD Ch2, when it comes to requirements gathering, assumptions are (check all
that apply):
A way of staying on schedule when encountering ambiguity
The list of things that the developers will take on ("assume") in implementing the requirement
Gaps in the developers' understanding
Exposed and discussed in the planning game
Something to discuss with the customer if you can't solve it yourselves
Risks correct answers Gaps in the developers' understanding
Exposed and discussed in the planning game
Something to discuss with the customer if you can't solve it yourselves
, Risks
According to HFSD Ch2, how many iterations of the planning game are required?
As many as required to remove as many assumptions possible.
One - take the average of the team's estimates
Two - need to narrow the spread before averaging correct answers As many as required to
remove as many assumptions possible
According to HFSD Ch2, who should be involved in gathering the information for the user
stories?
The customer
Pretty much anybody touched by the software
The customer and the developers correct answers Pretty much anybody touched by the software
According to HFSD Ch2, a user story is (check all that apply):
Detailed and relatively complete
A story about the user
A single thing that the system should do
A statement of a software requirement in the customer's language
Completable in 15 days or less
Concise (short) correct answers A single thing the system should do
A statement of a software requirement in the customer's language
Completable in 15 days or less
Concise (short)
