Deal of The Day! Hurry Up, Grab the Special Discount - Save 25% - Ends In 00:00:00 Coupon code: SAVE25
Welcome to Pass4Success

- Free Preparation Discussions
Mail Us support@pass4success.com
Location US
Mob_nav_barsMENU

IIBA ECBA Exam - Topic 5 Question 104 Discussion

The requirements elicitation technique used to iteratively validate the needs of stakeholders that interact with the application is:
D) reverse engineering.
A) interface analysis
B) observation.
C) prototyping

IIBA ECBA Exam - Topic 5 Question 104 Discussion

Actual exam question for IIBA's ECBA exam
Question #: 104
Topic #: 5
[All ECBA Questions]

The requirements elicitation technique used to iteratively validate the needs of stakeholders that interact with the application is:

Show Suggested Answer Hide Answer
Suggested Answer: D

Confirming elicitation results is a critical step in the business analysis process. It ensures that the information gathered during elicitation is not only accurate but also aligns with other information. This confirmation process involves reviewing the elicited information to identify any discrepancies, errors, omissions, or conflicts.By doing so, business analysts can guarantee that the information used as input for further analysis and decision-making is reliable and consistent, which is essential for the success of any business initiative.Reference: The importance of confirming elicitation results for accuracy and consistency is highlighted in the BABOK Guide, which serves as a standard for the practice of business analysis12.


by Dominque at Jan 25, 2025, 03:45 PM

Limited Time Offer

25%

Off

Get Premium ECBA Questions as Interactive Web-Based Practice Test or PDF

Contribute your Thoughts:

0/2000 characters
Submit Cancel
Ronald
8 months ago
I think prototyping is the best choice here!
upvoted 0 times
...
Lindsey
8 months ago
Interface analysis is also a good method, though.
upvoted 0 times
...
Deeanna
9 months ago
Wait, can prototyping really capture all stakeholder needs?
upvoted 0 times
...
Karrie
9 months ago
Totally agree, prototyping allows for real-time feedback.
upvoted 0 times
...
Muriel
9 months ago
Prototyping is super effective for validating needs!
upvoted 0 times
...
Nana
9 months ago
I practiced a similar question, and I think prototyping was emphasized as a key technique for validating needs.
upvoted 0 times
...
Mable
10 months ago
I feel like observation could be relevant, but it doesn't seem as interactive as the others.
upvoted 0 times
...
Novella
10 months ago
I'm not entirely sure, but I remember something about interface analysis being used for gathering requirements too.
upvoted 0 times
...
Regenia
10 months ago
I think prototyping might be the right answer since it allows for iterative feedback from stakeholders.
upvoted 0 times
...
Mauricio
10 months 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.
upvoted 0 times
...
Annmarie
10 months 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.
upvoted 0 times
...
Lisbeth
10 months ago
Ah, I know this one! Iterative validation of stakeholder needs is all about prototyping. That's the way to go.
upvoted 0 times
...
Berry
10 months 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.
upvoted 0 times
...
Rosalind
10 months 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.
upvoted 0 times
...
Jacinta
1 year ago
Prototyping is the way to go, but I hope it doesn't turn into a never-ending cycle of changes and feedback loops!
upvoted 0 times
Kaycee
1 year ago
C) prototyping
upvoted 0 times
...
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.
upvoted 0 times
...
Gerardo
1 year ago
C) prototyping
upvoted 0 times
...
Aleta
1 year ago
A) interface analysis
upvoted 0 times
...
...
Tiffiny
1 year ago
Observation? Sounds more like something a user researcher would do. Prototyping is the clear choice here.
upvoted 0 times
...
Celia
1 year ago
Interface analysis? Sounds like something a UI designer would do, not a requirements engineer. Definitely prototyping.
upvoted 0 times
Dudley
1 year ago
Yeah, prototyping allows for quick feedback and adjustments.
upvoted 0 times
...
Paulina
1 year ago
I agree, prototyping is a great way to validate stakeholder needs.
upvoted 0 times
...
...
Jovita
1 year ago
Reverse engineering? That's for fixing old systems, not building new ones. I'm going with prototyping too.
upvoted 0 times
...
Shawnna
1 year ago
Hmm, I think prototyping is the way to go. It lets you get feedback from stakeholders and refine the requirements iteratively.
upvoted 0 times
Glory
1 year ago
Reverse engineering may not be as effective for validating stakeholder needs.
upvoted 0 times
...
Silvana
1 year ago
Interface analysis can help identify requirements based on user interactions.
upvoted 0 times
...
Phuong
1 year ago
Observation can also be useful to understand stakeholder needs.
upvoted 0 times
...
Temeka
1 year ago
I agree, prototyping allows for quick feedback and adjustments.
upvoted 0 times
...
...
Dona
1 year ago
I'm not sure, but I think A) interface analysis could also be a valid option.
upvoted 0 times
...
Fletcher
1 year ago
I agree with Raymon, prototyping helps validate stakeholder needs.
upvoted 0 times
...
Raymon
1 year ago
I think the answer is C) prototyping.
upvoted 0 times
...

Save Cancel