SQA Tasks, Goals, Attributes, and Metrics
https://www.computersprofessor.com/2017/09/sqa-tasks-goals-attributes-and-metrics.html
Goals, Attributes, and Metrics:
Requirement quality : The correctness,
completeness, and consistency of the requirements model will have a strong
influence on the quality of all work products that follow. SQA must ensure that
the software team has properly reviewed the requirements model to achieve a
high level of quality.
Design quality : Every element of the design model
should be assessed y the software team to ensure that it exhibits high quality
and that the design itself conforms to requirements.
Code quality : Source code and related work products
must conform to local coding standards and exhibit characteristics that will
facilitate maintainability.
Quality control effectiveness : A software team
should apply limited resources in a way that has the highest likelihood of
achieving a high–quality result. SQA analyzes the allocation of resources for
reviews and testing to assess whether they are being allocated in the most
effective manner.
Software quality goals, attributes, and
metrics
|
Goal
|
Attribute
|
Metric
|
|
Requirement quality
|
Ambigully
|
Number of ambiguous
modifiers (e.., many, large, human–friendly)
|
|
|
Completeness
|
Number of TBA, TBD
|
|
|
Understandability
|
Number of
sections/subsections
|
|
|
Volatility
|
Number of changes per
requirement Time (by activity) when change is requested
|
|
|
Traceability
|
Number of requirements not
traceable to design/code
|
|
|
Model clarity
|
Number of UML models
Number of descriptive
pages per model
Number of UML errors
|
|
Design quality
|
Architectural integrity
Component completeness
Interface complexity
Patterns
|
Existence of architectural
model
Number of components that
trace to architectural model
Complexity of procedural
design
Average number of pick to
get to a typical function or content
Layout appropriateness
Number of patterns used
|
|
Code quality
|
Complexity
Maintainability
Understandability
Reusability
Documentation
|
Cyclomatic complexity
Design factors (Chapter 8)
Percent internal comments
Variable naming
conventions
Percent reused components
Readability index
|
|
QC effectiveness
|
Resource allocation
Completion rate
Review effectiveness
Testing effectiveness
|
Staff hour percentage per
activity
Actual vs. budgeted
completion time
See review metrics
Number of errors found and
criticality
Effort required to correct
an error
Origin of error
|
