4.1) Static Quality Assurance: Assessment and Measurement

Question 1

What is the difference between constructive quality management and static quality assurnace?

Answer 1

In contrast to constructive quality management, which specifies activities in a software process, static quality assurance measures examine and evaluate the results created in a software process.

Question 2

Please define static quality assurance.

Answer 2

Static quality assurance procedures are analytical procedures in which the test object is analyzed, assessed, and investigated within the scope of a review. The information obtained in the process is collected, condensed into metrics or key figures, if necessary, and, ultimately, evaluated.

Question 3

Please explain the difference between static and dynamic procedures.

A.K.A static and dynamic quality assurance

Answer 3

In contrast to dynamic procedures, the source code to be examined is not executed in static procedures. In principle, all static quality assurance procedures can be conducted without the use of software, i.e., only “with pen and paper”. However, the measurement and calculation of metrics, as well as static code analysis, are particularly well supported by tools. Static procedures can be used to examine all artifacts created in the software process, as well as activities for quality assurance.

Question 4

What activities can take place within static procedures?

Answer 4

• Examination of the business requirements: review techniques are used to examine documented requirements with regard to predefined quality criteria.
• Quality gates: with the help of checklists, the current situation in a software process is assessed and compliance with required attributes is evaluated.
• Examination of the technical specification: review techniques are used to examine the technical specification with regard to predefined quality criteria. Technical data schemas and data structures are also automatically analyzed and evaluated, if required.
• Evaluation of the planned architecture: review techniques and scenario-based architecture analysis are used to examine the suitability of the architecture description for meeting the requirements. Detailed technical designs of components and data structures can be automatically analyzed and evaluated, if required.
• Test case generation: the test cases generated are reviewed using review techniques to determine whether they can ensure the quality level defined for the current project.
• Component tests: although component tests are not static procedures, measures for static code analysis are carried out in the context of these tests. The program code created is automatically reviewed for compliance with required attributes and error probability analyses are performed.