Is establishing requirements simply writing a wish-list of features? Why or why not?
a) No, To ensure both parties, the users and development team are absolutely on the same page.
b) No, Establishing requirements is not simply writing a wish-list of features. Establishing requirements is an interactive process that evolves through a series of evaluations.
c) No, Aim to replace or update an established system.
d) No, Essential use cases represent abstractions from scenarios and try to avoid the assumptions of a use case