New Year Sale ! 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 1 Question 99 Discussion

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

What requirements are good candidates for reuse?

Show Suggested Answer Hide Answer
Suggested Answer: A

Requirements that are good candidates for reuse are those that are not tied to a specific tool, technology, or system. These requirements are generally applicable across various contexts and can be used in multiple projects without significant changes. They are typically high-level business requirements that describe what the business needs without prescribing how to achieve it. This makes them flexible and adaptable to different situations, which is essential for reuse.


by Kristel at Sep 19, 2024, 04:52 AM

Limited Time Offer

25%

Off

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

Contribute your Thoughts:

Submit Cancel
Devorah
2 months ago
I'd go for option A. Keeps things flexible and avoids the dreaded 'vendor lock-in'.
upvoted 0 times
...
Rosalyn
2 months ago
Ha! Requirements with department references? Might as well just name the company too. Good one!
upvoted 0 times
Arlen
1 months ago
C) Requirements at low levels of abstraction
upvoted 0 times
...
Michel
2 months ago
B) Requirements expressed in more detail
upvoted 0 times
...
Lino
2 months ago
A) Requirements without direct ties to a particular tool
upvoted 0 times
...
...
Isabella
2 months ago
Definitely not the ones with specific references to departments. That's way too specific and tied to a particular organization.
upvoted 0 times
Kate
2 months ago
C) Requirements at low levels of abstraction
upvoted 0 times
...
Albina
2 months ago
B) Requirements expressed in more detail
upvoted 0 times
...
Lawanda
2 months ago
A) Requirements without direct ties to a particular tool
upvoted 0 times
...
...
Delsie
3 months ago
I agree with Alexia. Requirements at a higher level of abstraction are more reusable. But I'd still want some detail, not just vague statements.
upvoted 0 times
Kimi
2 months ago
C) Requirements at low levels of abstraction
upvoted 0 times
...
Lindsey
2 months ago
B) Requirements expressed in more detail
upvoted 0 times
...
Eden
2 months ago
A) Requirements without direct ties to a particular tool
upvoted 0 times
...
...
Francine
3 months ago
I believe requirements expressed in more detail can also be good candidates for reuse, as they provide a clear understanding of what needs to be done.
upvoted 0 times
...
Alexia
3 months ago
A requirements without direct ties to a particular tool sounds like the way to go. That way, we can reuse it across different projects and tools.
upvoted 0 times
Paris
2 months ago
A) Requirements without direct ties to a particular tool sounds like the way to go. That way, we can reuse it across different projects and tools.
upvoted 0 times
...
Lauran
2 months ago
That makes sense. It would make it easier to reuse across different projects.
upvoted 0 times
...
Kandis
2 months ago
C) Requirements at low levels of abstraction
upvoted 0 times
...
Essie
2 months ago
B) Requirements expressed in more detail
upvoted 0 times
...
Jerry
3 months ago
A) Requirements without direct ties to a particular tool
upvoted 0 times
...
...
Melodie
3 months ago
I agree with Percy. Requirements at low levels of abstraction can also be good candidates for reuse.
upvoted 0 times
...
Percy
4 months ago
I think requirements without direct ties to a particular tool are good candidates for reuse.
upvoted 0 times
...

Save Cancel