MENU
The requirements elicitation technique used to iteratively validate the needs of stakeholders that interact with the application is:
32 comments · newest first
RO
Ronald
11 months ago
I think prototyping is the best choice here!
LI
Lindsey
11 months ago
Interface analysis is also a good method, though.
DE
Deeanna
12 months ago
Wait, can prototyping really capture all stakeholder needs?
KA
Karrie
12 months ago
Totally agree, prototyping allows for real-time feedback.
MU
Muriel
1 year ago
Prototyping is super effective for validating needs!
NA
Nana
1 year ago
I practiced a similar question, and I think prototyping was emphasized as a key technique for validating needs.
MA
Mable
1 year ago
I feel like observation could be relevant, but it doesn't seem as interactive as the others.
NO
Novella
1 year ago
I'm not entirely sure, but I remember something about interface analysis being used for gathering requirements too.
RE
Regenia
1 year ago
I think prototyping might be the right answer since it allows for iterative feedback from stakeholders.
MA
Mauricio
1 year ago
Prototyping seems like the most logical choice here. It allows you to get feedback from stakeholders and refine the application based on their needs.
AN
Annmarie
1 year ago
I'm a bit confused by the wording here. Let me think through each option and see if I can eliminate the ones that don't fit the description.
LI
Lisbeth
1 year ago
Ah, I know this one! Iterative validation of stakeholder needs is all about prototyping. That's the way to go.
BE
Berry
1 year ago
Hmm, I'm not entirely sure about this one. The options seem similar, but I'll try to recall the differences between them and make my best guess.
RO
Rosalind
1 year ago
This looks like a straightforward requirements elicitation question. I'll carefully read through the options and think about which technique is best for iteratively validating stakeholder needs.
JA
Jacinta
2 years ago
Prototyping is the way to go, but I hope it doesn't turn into a never-ending cycle of changes and feedback loops!
KA
Kaycee
1 year ago
C) prototyping
WE
Weldon
1 year ago
I agree, prototyping can be a great way to validate stakeholder needs, but it's important to manage the feedback effectively.
GE
Gerardo
1 year ago
C) prototyping
AL
Aleta
1 year ago
A) interface analysis
TI
Tiffiny
2 years ago
Observation? Sounds more like something a user researcher would do. Prototyping is the clear choice here.
CE
Celia
2 years ago
Interface analysis? Sounds like something a UI designer would do, not a requirements engineer. Definitely prototyping.
DU
Dudley
1 year ago
Yeah, prototyping allows for quick feedback and adjustments.
PA
Paulina
1 year ago
I agree, prototyping is a great way to validate stakeholder needs.
JO
Jovita
2 years ago
Reverse engineering? That's for fixing old systems, not building new ones. I'm going with prototyping too.
SH
Shawnna
2 years ago
Hmm, I think prototyping is the way to go. It lets you get feedback from stakeholders and refine the requirements iteratively.
GL
Glory
1 year ago
Reverse engineering may not be as effective for validating stakeholder needs.
SI
Silvana
1 year ago
Interface analysis can help identify requirements based on user interactions.
PH
Phuong
1 year ago
Observation can also be useful to understand stakeholder needs.
TE
Temeka
2 years ago
I agree, prototyping allows for quick feedback and adjustments.
DO
Dona
2 years ago
I'm not sure, but I think A) interface analysis could also be a valid option.
FL
Fletcher
2 years ago
I agree with Raymon, prototyping helps validate stakeholder needs.
RA
Raymon
2 years ago
I think the answer is C) prototyping.