Quote Originally Posted by JGrapes
I'd also add that the intent of not re-inventing the wheel and not repeating common, well-understood requirements goes to requirements patterns.
I think a Req. Analyst can add value by recognizing a possible solution to the requirements being gathered and letting the stakeholders know. Maybe they are already aware of it and are giving specific requirements because they want something different, or maybe they want to see if something different is better ("innovation"), or maybe they simply didn't realize the most common solution...