What does a "bad" requirement often lack?

• A. Specificity and clarity
• B. Meeting user expectations
• C. Compliance with coding standards
• D. Documentation

Answer: (A)

A "bad" requirement often lacks specificity and clarity, which is crucial for ensuring that all stakeholders have a shared understanding of what is needed. When requirements are vague or open to interpretation, it can lead to confusion among the development team about what the end goal is. This can result in various inefficiencies, such as rework, miscommunication, and ultimately products that don't meet the intended purpose or user needs.

Specificity ensures that every team member knows exactly what features or functionalities need to be implemented, while clarity helps in communicating these requirements effectively across teams. When both these elements are missing, the likelihood of project failure increases significantly as developers might build functionalities based on their assumptions rather than clear guidelines, leading to discrepancies between what is built and what was expected.

The other options, while important in their own right, do not directly capture the essence of a "bad" requirement compared to specificity and clarity. For example, meeting user expectations may not necessarily stem from poorly defined requirements, and compliance with coding standards and documentation, while critical, pertain more to the implementation phase rather than the initial requirement gathering phase.