ABSTRACT
There are few examples of clear, coherent nonfunctional requirements that are realistic in both the technical and commercial senses. The main reason for this state of affairs is that the nonfunctional aspects receive insufficient attention. The same individuals who are responsible for the functional requirements frequently write them. These authors tend to have limited technical knowledge, as they usually come from a business analysis or application development background. The result is that the requirements are often vague, ambiguous, and lacking in basic sizing information, and the expectations are often technically unrealistic and financially unaffordable.
