Which attribute is NOT a characteristic of a good requirements specification?

A good requirements specification is essential for successful systems engineering, and it typically embodies several key attributes. One of the fundamental characteristics of such specifications is that they should be unambiguous. This means that each requirement should be stated clearly so that it can be understood in only one way. Ambiguity can lead to different interpretations among stakeholders, which can result in confusion, misaligned expectations, and ultimately, project failure.

In contrast, requirements being implementation independent means that they should express what the system must do without describing how these functions will be delivered. Clear and concise is crucial because overly complex or verbose requirements can obscure their intent and render them less useful. Additionally, completeness ensures that all necessary requirements are included, covering all functional and non-functional aspects of the system.

Thus, the attribute “ambiguous” is the one that does not fit as a characteristic of a good requirements specification, since a well-formed specification should strive to eliminate ambiguity entirely to ensure clarity and effective communication among stakeholders.