MENU
Which of the following requirements elicitation techniques is ineffective at defining the future requirements of a system?
Suggested Answer: D
Get Premium CBAF-001 Questions
as Interactive Web-Based Practice Test or PDF
Real Exam Format
Detailed Explanations
Instant Access
Get Your Practice Test
28 comments · newest first
LO
Loren
10 months ago
Wait, are we saying shadowing is ineffective? That seems off!
CA
Carman
10 months ago
Workshops can be hit or miss, but they usually gather good insights.
AL
Aliza
11 months ago
I think prototyping is super effective for future requirements!
LO
Lorrie
11 months ago
Scenario analysis is great for exploring future possibilities.
JA
Janine
11 months ago
Shadowing is often overlooked but really helps understand user needs.
DE
Denae
11 months ago
Scenario analysis seems like it could be useful, but I vaguely recall something about shadowing being less effective for future requirements.
RO
Rozella
11 months ago
I feel like prototyping is often used to clarify requirements, so that can't be the right answer either.
DE
Demetra
12 months ago
I'm a bit unsure, but I think shadowing might not really help in defining future requirements since it's more about observing current processes.
DI
Dianne
12 months ago
I remember we discussed that workshops are usually effective for gathering requirements, so I don't think it's A.
RI
Ricki
1 year ago
I think the key here is to focus on techniques that allow you to imagine and test out future scenarios, rather than just documenting existing processes. Based on that, I'd say prototyping is probably the most effective approach for defining future requirements.
ER
Erick
1 year ago
Shadowing seems like it would be the least effective technique for defining future requirements. It's more focused on observing current user behaviors and workflows, rather than exploring new possibilities for the future system.
BU
Buck
1 year ago
Hmm, I'm a bit unsure about this one. I know workshops and prototyping are both common requirements elicitation techniques, but I can't quite remember which one is less effective for future requirements. I'll have to think this through carefully.
RA
Ramonita
1 year ago
I'm pretty confident that prototyping is the most effective technique for defining future requirements. Workshops and scenario analysis are good for eliciting current needs, but prototyping lets you explore and test potential future features.
CH
Chi
1 year ago
What kind of crazy question is this? Everyone knows the best way to define future requirements is to consult a crystal ball and a tarot deck. Duh.
CI
Ciara
1 year ago
I'm gonna have to agree with Marshall on this one. Shadowing is just observing the present, not defining the future. That's like trying to drive while only looking in the rearview mirror.
LA
Lai
1 year ago
I think Marshall makes a good point about shadowing not defining the future requirements.
MA
Mari
1 year ago
Haha, I bet the answer is A. Workshops are like herding cats. Good luck getting anything useful out of that chaos.
MA
Marshall
1 year ago
I'm gonna have to go with D. Shadowing is just watching someone else do their job - how's that supposed to help us figure out what we need in the future?
MI
Ming
1 year ago
A) Workshops.
EU
Eulah
1 year ago
Hmm, I see your point. Maybe I should reconsider my answer.
DA
Daniel
1 year ago
I agree with Curtis, prototyping can be effective in defining requirements.
CU
Curtis
1 year ago
But prototyping helps visualize the future system.
EU
Eulah
1 year ago
I disagree, I believe it's D) Shadowing.
SU
Suzi
1 year ago
Definitely not B. Prototyping is super effective for defining future requirements. How else would we know what the users really want?
BE
Beckie
1 year ago
D) Shadowing.
LO
Louvenia
1 year ago
C) Scenario analysis.
WE
Wenona
1 year ago
A) Workshops.
CU
Curtis
1 year ago
I think the answer is B) Prototyping.