Сравнение на методи
Прегледайте избраните методи един до друг; редовете с разлики са откроени.
| Проследяване на Agile Velocity× | Метрики за софтуерна сложност× | |
|---|---|---|
| Област | Софтуерно инженерство | Софтуерно инженерство |
| Семейство | Process / pipeline | Process / pipeline |
| Година на възникване≠ | 2002 | 1976 |
| Създател≠ | Ken Schwaber and Mike Cohn | Thomas J. McCabe |
| Тип≠ | measurement metric | quantitative measurement |
| Основополагащ източник≠ | Schwaber, K., & Beedle, M. (2002). Agile Software Development with Scrum. Prentice Hall. link ↗ | McCabe, T. J. (1976). A complexity measure. IEEE Transactions on Software Engineering, 2(4), 308–320. DOI ↗ |
| Други названия≠ | sprint velocity, team capacity planning, burndown analysis | code complexity analysis, complexity measurement |
| Свързани | 4 | 4 |
| Резюме≠ | Velocity tracking measures the amount of work (typically story points or tasks) a team completes in a sprint, enabling capacity planning, release forecasting, and identification of process improvements. Introduced in Scrum methodology by Schwaber (2002), velocity provides empirical data for realistic sprint planning and project timeline prediction. Teams use velocity trends to identify bottlenecks and validate process improvements. | 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. |
| ScholarGateНабор от данни ↗ |
|
|