![]() |
![]() |
![]() |
|
| 4.38 Elementary Method "Static Analysis" (STAT) |
4.38 Elementarmethode "Statische Analyse" (STAT)
1 Identification/Definition of the Method
2 Brief Characteristic of the Method
One of the objectives of the "Static Analysis" (STAT) is the identification of existing errors or respectively of error-prone situations. Another objective is to make quality measurable. Thus the method contributes its share to meet the basis requirement that it must be possible to prove quality.
Operational Sequence
The basic principle of the static analysis is that an object to be assessed which is structured according to a predefined formalism will be read. In this connection errors or error-prone situations are immediately detected or information is gained which allow deductions to errors or respectively error-prone situations after the read process has been completed.
Errors or error-prone situations might be:
Metrics are also quantified during the read process. The metrics offer a possibility to measure quality characteristics. However, it must also be evaluated if the measured values are meeting the requirements /ISO 9126, 1991/). An overview of all possible metrics can be found in /IEEE 982.2/.
3 Limits of the Methods Application
4 Specification of the Methods Allocation
| No. | Activity | Description |
|---|---|---|
| 4.1 | QA4.1 - Determination of Assessability | Method STAT is applied to determine the assessability of objects that are structured according to a predefined formalism. It only completely covers the determination of the assessability in combination with method REV - Review. However, after the realization of a static analysis the number of aspects to be taken into consideration during the review will be much less. |
| 4.2 | QA4.2 - Assessment of the Content of the Product |
Method STAT is applied to assess the following objects:
In case some of the contents of the object to be assessed are structured according to a predefined formalism, the application of method T is additionally required for the objects User Requirements, Technical Requirements, System Architecture, SW Architecture, and SW Design (Module/Database). If the reliability requirements are high, the application of method SIMU - Simulation Models is additionally required for the assessed objects User Requirements and Technical Requirements. |
5 Interfaces
6 Further Literature
7 Functional Tool Requirements
![]() |
![]() |
GDPA Online
Last Updated 01.Jan.2002
Updated by Webmaster
Last Revised 01.Jan.2002
Revised by Webmaster
![]() |