Methoden vergelijken
Bekijk de geselecteerde methoden naast elkaar; rijen die verschillen zijn gemarkeerd.
| Software Complexiteitsmetrieken× | Model voor defectvoorspelling× | |
|---|---|---|
| Vakgebied | Software-engineering | Software-engineering |
| Familie | Process / pipeline | Process / pipeline |
| Jaar van ontstaan≠ | 1976 | 2005 |
| Grondlegger≠ | Thomas J. McCabe | Thomas Ostrand, Elaine Weyuker, Robert Bell |
| Type≠ | quantitative measurement | machine learning model |
| Oorspronkelijke bron≠ | McCabe, T. J. (1976). A complexity measure. IEEE Transactions on Software Engineering, 2(4), 308–320. DOI ↗ | Ostrand, T. J., Weyuker, E. J., & Bell, R. M. (2005). Predicting the location and number of faults in large software systems. IEEE Transactions on Software Engineering, 31(4), 340–355. DOI ↗ |
| Aliassen≠ | code complexity analysis, complexity measurement | fault prediction, bug prediction, defect classification |
| Verwant | 4 | 4 |
| Samenvatting≠ | Software complexity metrics quantify the structural and operational difficulty of code through numerical measurements. Introduced by Thomas McCabe in 1976, cyclomatic complexity became the foundational approach. These metrics assess maintainability, testability, and defect risk, enabling teams to identify problematic code regions and guide refactoring efforts. | Defect prediction models forecast the likelihood of software faults in code modules using statistical or machine learning approaches. Pioneered by Ostrand, Weyuker, and Bell (2005), these models correlate code metrics (complexity, churn, coupling) with historical defect data to identify high-risk components. Organizations use predictions to allocate testing resources, guide code review, and prioritize refactoring. |
| ScholarGateGegevensset ↗ |
|
|