Methoden vergleichen
Prüfen Sie die ausgewählten Methoden nebeneinander; abweichende Zeilen sind hervorgehoben.
| Statische Code-Analyse× | Äquivalenzklassenbildung× | |
|---|---|---|
| Fachgebiet | Softwaretechnik | Softwaretechnik |
| Familie | Process / pipeline | Process / pipeline |
| Entstehungsjahr≠ | 2001 | 1979 |
| Urheber≠ | David Engler and William Pugh | Glenford Myers |
| Typ≠ | automated analysis | partitioning strategy |
| Wegweisende Quelle≠ | Chess, B., & West, J. (2007). Secure Programming with Static Analysis. Addison-Wesley Professional. link ↗ | Myers, G. J. (1979). The Art of Software Testing. John Wiley & Sons. link ↗ |
| Aliasnamen | static analysis, code inspection, automated review | equivalence partitioning, BVA, boundary value analysis |
| Verwandt | 4 | 4 |
| Zusammenfassung≠ | Static code analysis automatically examines source code without execution, detecting potential bugs, security vulnerabilities, code smells, and style violations. Pioneered by Engler and Pugh (2001), automated analysis tools scan codebases at scale, identifying defect patterns faster than manual review. Organizations integrate static analysis into continuous integration pipelines to prevent defects early. | Equivalence partitioning divides input domains into equivalence classes—sets of inputs expected to behave identically—then selects test cases from each class. Introduced by Myers (1979), this technique reduces test cases while maintaining effectiveness. Boundary value analysis (BVA) complements partitioning by testing values at partition boundaries where failures often occur. |
| ScholarGateDatensatz ↗ |
|
|