Premium
On the Use of Attributes to Manage Requirements
Author(s) -
Wheatcraft Louis S.,
Ryan Michael J.,
Dick Jeremy
Publication year - 2016
Publication title -
systems engineering
Language(s) - English
Resource type - Journals
SCImago Journal Rank - 0.474
H-Index - 50
eISSN - 1520-6858
pISSN - 1098-1241
DOI - 10.1002/sys.21369
Subject(s) - requirements engineering , non functional requirement , requirements management , computer science , term (time) , requirements analysis , set (abstract data type) , requirement , functional requirement , risk analysis (engineering) , system requirements , requirements traceability , systems engineering , software engineering , engineering , software development , business , software , software construction , physics , quantum mechanics , programming language , operating system
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.