방법 비교
선택한 방법을 나란히 검토하세요. 서로 다른 행은 강조 표시됩니다.
| 아키텍처 스멜 탐지× | 소프트웨어 복잡도 측정 지표× | |
|---|---|---|
| 분야 | 소프트웨어공학 | 소프트웨어공학 |
| 계열 | Process / pipeline | Process / pipeline |
| 기원 연도≠ | 2009 | 1976 |
| 창시자≠ | Martin Fowler and García et al. | Thomas J. McCabe |
| 유형≠ | pattern-based analysis | quantitative measurement |
| 원전≠ | Fowler, M. (2018). Code smell. Martin Fowler's Website. link ↗ | McCabe, T. J. (1976). A complexity measure. IEEE Transactions on Software Engineering, 2(4), 308–320. DOI ↗ |
| 별칭≠ | design smell detection, architectural debt analysis, system quality assessment | code complexity analysis, complexity measurement |
| 관련 | 4 | 4 |
| 요약≠ | Architecture smells are recurring patterns in system structure that indicate potential design problems. Introduced by García et al. (2009), these patterns signal violations of architectural principles (modularity, independence, abstraction) at system scale. Detection combines code metrics, dependency analysis, and pattern recognition to identify smells early, guiding refactoring and architectural 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데이터셋 ↗ |
|
|