विधियों की तुलना करें
चुनी हुई विधियों की आमने-सामने समीक्षा करें; भिन्नता वाली पंक्तियाँ रेखांकित हैं।
| आर्किटेक्चर स्मेल डिटेक्शन× | तकनीकी ऋण मापन× | |
|---|---|---|
| क्षेत्र | सॉफ्टवेयर इंजीनियरिंग | सॉफ्टवेयर इंजीनियरिंग |
| परिवार | Process / pipeline | Process / pipeline |
| उद्भव वर्ष≠ | 2009 | 1992 |
| प्रवर्तक≠ | Martin Fowler and García et al. | Ward Cunningham |
| प्रकार≠ | pattern-based analysis | quantitative assessment |
| मौलिक स्रोत≠ | Fowler, M. (2018). Code smell. Martin Fowler's Website. link ↗ | Cunningham, W. (1992). The WyCash Portfolio Management System. OOPSLA 92 Experience Report. link ↗ |
| उपनाम | design smell detection, architectural debt analysis, system quality assessment | debt metrics, code health scoring, maintenance burden assessment |
| संबंधित | 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. | Technical debt represents accumulated shortcuts, deferred maintenance, and design compromises that incur future costs through slower development, higher defect rates, and deployment difficulty. Introduced by Ward Cunningham (1992), technical debt measurement quantifies these burdens using metrics like code complexity, duplication, test coverage gaps, and maintainability indices. Organizations use debt measurement to balance immediate delivery with long-term sustainability. |
| ScholarGateडेटासेट ↗ |
|
|