Сравнение методов
Просматривайте выбранные методы рядом; строки с различиями подсвечены.
| Отслеживание скорости в Agile× | Анализ покрытия кода× | |
|---|---|---|
| Область | Программная инженерия | Программная инженерия |
| Семейство | Process / pipeline | Process / pipeline |
| Год появления≠ | 2002 | 1988 |
| Автор метода≠ | Ken Schwaber and Mike Cohn | Test Coverage Community |
| Тип≠ | measurement metric | measurement and analysis |
| Основополагающий источник≠ | Schwaber, K., & Beedle, M. (2002). Agile Software Development with Scrum. Prentice Hall. link ↗ | Zhu, H., Hall, P. A. V., & May, J. H. R. (1997). Software unit test coverage and adequacy. ACM Computing Surveys, 29(4), 366–427. DOI ↗ |
| Другие названия | sprint velocity, team capacity planning, burndown analysis | coverage metrics, test coverage, instrumentation-based 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. | Code coverage analysis measures the extent to which source code is executed by a test suite, quantifying which lines, branches, or paths are exercised. Tools instrument code to track execution, reporting coverage percentages and identifying untested regions. Coverage analysis guides test creation, detects dead code, and validates test adequacy in quality assurance processes. |
| ScholarGateНабор данных ↗ |
|
|