Construct · 1 fields · 1 citations

requirements ambiguity: a standalone construct

One name. One construct. A landmark on the map.

● anchor · a standalone construct Nearest construct by meaning·not indexed

A single standalone construct; nearby constructs are located against it in the Collider. Tap a field for its definition, unit, and measures.

Software engineering

the property of a requirement having more than one reading, classified into lexical, syntactic, semantic and pragmatic kinds.

In software engineering, requirements ambiguity refers to the property of a requirement having more than one reading, classified into lexical, syntactic, semantic and pragmatic kinds. This meaning comes from Berry (2004) in Perspectives on Software Requirements.[1]

Unit
Recovery means
Measured by

Run it through the Collider, or take the citations with you.

See how requirements ambiguity sits against neighbouring constructs in the Collider, or export every reference on this page in one click.

Open in Collider Export BibTeX Report this entry

Nearby constructs

ambiguity5 fields · 6 citationsjingle · one word, five constructs property4 fields · 4 citationsjingle · one word, four constructs reading2 fields · 2 citationsjingle · one word, two constructs

References

Berry, D. M., & Kamsties, E. (2004). Ambiguity in Requirements Specification. In Perspectives on Software Requirements (pp. 7-44). Springer US. https://doi.org/10.1007/978-1-4615-0465-8_2

Cited on this page?

Confirm your construct, or correct us.

If your work is cited behind one of these entries, you know better than we do whether we captured the meaning right. Confirm it, suggest an edit, or dispute it, and your name goes on the entry as an author who has checked it, linked to your ORCID.

Claim your construct