I've recently experienced #3.

3. "The requirements make it clear what has to be done."
Translation: “Simply including certain features is more important than how those features are implemented.”

Development of requirements should be part of a customer-centered design process: it should be based on established user needs and followed by a design process that includes customers throughout. However, many cultures have become feature-focused, and they over-emphasize what needs to be done while paying little attention to how it is to be designed.

Companies with feature-focused cultures will tend to generate requirements in-house and base requirements on scanty, anecdotal, and/or antiquated customer information. They may also consider the requirements the measure by which finished products are evaluated, instead of balancing that view with external measures such as usability test results.

Read on here.

--Mark