विधियों की तुलना करें

	यूज़ केस पॉइंट अनुमान	तकनीकी ऋण मापन
क्षेत्र	सॉफ्टवेयर इंजीनियरिंग	सॉफ्टवेयर इंजीनियरिंग
परिवार	Process / pipeline	Process / pipeline
उद्भव वर्ष	1993	1992
प्रवर्तक	Gustav Karner	Ward Cunningham
प्रकार	quantitative estimation	quantitative assessment
मौलिक स्रोत	Karner, G. (1993). Resource estimation for objectory projects. Objective Systems SF, Inc.	Cunningham, W. (1992). The WyCash Portfolio Management System. OOPSLA 92 Experience Report.
उपनाम	UCP, use case sizing, effort estimation	debt metrics, code health scoring, maintenance burden assessment
संबंधित	4	4
सारांश	Use case point (UCP) estimation quantifies software development effort by analyzing use cases and environmental factors. Introduced by Karner (1993) for Objectory methodology, UCP provides structured approach to estimate labor hours from system requirements. Organizations use UCP to forecast project duration, allocate resources, and validate high-level project plans early in development.	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.