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 Exam ECBA 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:

Submit Cancel
Jacinta
1 months 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
7 days ago
C) prototyping
upvoted 0 times
...
Weldon
12 days 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
17 days ago
C) prototyping
upvoted 0 times
...
Aleta
23 days ago
A) interface analysis
upvoted 0 times
...
...
Tiffiny
2 months ago
Observation? Sounds more like something a user researcher would do. Prototyping is the clear choice here.
upvoted 0 times
...
Celia
2 months ago
Interface analysis? Sounds like something a UI designer would do, not a requirements engineer. Definitely prototyping.
upvoted 0 times
Dudley
25 days ago
Yeah, prototyping allows for quick feedback and adjustments.
upvoted 0 times
...
Paulina
28 days ago
I agree, prototyping is a great way to validate stakeholder needs.
upvoted 0 times
...
...
Jovita
2 months ago
Reverse engineering? That's for fixing old systems, not building new ones. I'm going with prototyping too.
upvoted 0 times
...
Shawnna
2 months 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
23 days ago
Reverse engineering may not be as effective for validating stakeholder needs.
upvoted 0 times
...
Silvana
25 days ago
Interface analysis can help identify requirements based on user interactions.
upvoted 0 times
...
Phuong
26 days ago
Observation can also be useful to understand stakeholder needs.
upvoted 0 times
...
Temeka
2 months ago
I agree, prototyping allows for quick feedback and adjustments.
upvoted 0 times
...
...
Dona
2 months ago
I'm not sure, but I think A) interface analysis could also be a valid option.
upvoted 0 times
...
Fletcher
2 months ago
I agree with Raymon, prototyping helps validate stakeholder needs.
upvoted 0 times
...
Raymon
2 months ago
I think the answer is C) prototyping.
upvoted 0 times
...

Save Cancel
a