Construct · 1 fields · 1 citations

non-functional requirements: a standalone construct

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

● anchor · a standalone construct Nearest construct by meaning·not indexed
non-functionalrequirements1 CONSTRUCTNon-functionalGLINZ · SOFTWARE ENGINEERING

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

Software engineering

requirements about system qualities and constraints rather than functions, with a proposed classification of their kinds.

In software engineering, non-functional requirements refers to requirements about system qualities and constraints rather than functions, with a proposed classification of their kinds. This meaning comes from Glinz (2007) in 15th IEEE International Requirements Engineering Conference (RE 2007).[1]

Unit
Recovery means
Measured by

Next

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

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

Open in ColliderExport BibTeXReport this entry

Nearby constructs

requirements engineering1 fields · 1 citationsanchor · a standalone construct

References

  1. Glinz, M. (2007). On Non-Functional Requirements. 15th IEEE International Requirements Engineering Conference (RE 2007). https://doi.org/10.1109/re.2007.45

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