Editing Software requirements specification (section)

==Requirement quality==
Requirements should strictly be about what is needed, independently of the system design, and not how the software should do it.<ref name=":1" /> Individual requirements shall hence be necessary, appropriate, and unambiguous. A set of requirements shall moreover be complete, consistent, feasible, and comprehensible. 

Following the idea of [[code smell]]s, the notion of ''requirements smell'' has been proposed to describe issues in requirements specification where the requirement is not necessarily wrong but could be problematic.<ref name="femmer17">{{cite journal|last1=Femmer|first1=Henning|last2=Méndez Fernández|first2=Daniel|last3=Wagner|first3=Stefan|last4=Eder|first4=Sebastian|title=Rapid quality assurance with Requirements Smells|journal=Journal of Systems and Software|date=2017|volume=123|pages=190–213|doi=10.1016/j.jss.2016.02.047|arxiv=1611.08847|s2cid=9602750}}</ref> Examples of requirements smells are ''subjective language'', ''ambiguous adverbs and adjectives'', ''superlatives'' and ''negative statements''.<ref name="femmer17"/> Comparative phrases, non-verifiable terms or terms implying totality should also be avoided.<ref name=":1" />