
doi: 10.1002/sys.21369
ABSTRACT There are many sources in systems engineering and requirements engineering that use the term “attribute,” but few define the term and fewer actually go into any detail regarding how the attributes might be applied to requirement statements. This paper addresses the inconsistent definition and use of the term as part of the systems engineering and requirements engineering processes. We discuss the importance of defining requirement attributes and offer a useful definition. We provide a possible list of attributes along with their meaning, in order to provide a useful set of attributes that organizations may include with requirement expressions to manage better their requirements. Finally, we discuss how attributes can be used to manage not only requirements and sets of requirements, but also the project.
| selected citations These citations are derived from selected sources. This is an alternative to the "Influence" indicator, which also reflects the overall/total impact of an article in the research community at large, based on the underlying citation network (diachronically). | 10 | |
| popularity This indicator reflects the "current" impact/attention (the "hype") of an article in the research community at large, based on the underlying citation network. | Top 10% | |
| influence This indicator reflects the overall/total impact of an article in the research community at large, based on the underlying citation network (diachronically). | Top 10% | |
| impulse This indicator reflects the initial momentum of an article directly after its publication, based on the underlying citation network. | Top 10% |
