The requirements, as initially defined, do not accurately account for the
customers' real problems (an incorrectly stated
requirement may solve a non-problem).
Requirements are not properly prioritized. (There are
always more requirements than can be satisfied in a single release or
version of a software product.
Requirements are stated at an inappropriate level of
specification:
- Over-specification: embeds unnecessary design
constraints
- Under-specification: missing or incomplete
definition of requirements