Ensure that all quality factors are considered including
both those that are developer-oriented as well as those that
are user-oriented.
Almost all quality factors will be relevant for large,
complex, business-critical applications.
It is important to annotate the cells to:
Deal with situations where a quality factor has
different levels of importance when applied to different
parts of the application (or component).
Provide a rationale for critically-important quality
factors.
Typically, the more important a quality factor is, the
more expensive it will be to obtain it. Thus, typical
projects cannot afford to rate all quality factors as
critical.
Ensure that the distribution of importance levels to
quality factors is balanced. It is highly unlikely that all
quality requirements are critical, that all are equally
important, or that all are unimportant.
Columns are provided for each level of importance because
this makes it easier for stakeholders to determine if the
allocation of importance levels to quality factors is
balanced.
The more important general quality is, the more likely
that most of the quality factors will be given high levels of
importance.
There is typically no need to maintain the quality grids
once their information has been incorporated into the quality
requirements section of the
system requirements specification.
Quality girds are typically developed incrementally,
iteratively, and in parallel with other requirements work
products.
