| Author(s) | Collection number | Pages | Download abstract | Download full text |
|---|---|---|---|---|
| Трач О. Р., Трішин Ф. А. | № 2 (71) | 94-106 |
|
|
Understanding and ensuring the quality of software (SW) specifications (QS) is a critical preventive measure that determines the reliability and validity of subsequent product quality metrics. This study synthesizes current data, confirming that the quality of the final SW is a direct function of the quality of the input specifications. Historical data shows that incomplete and changing requirements are the dominant causes of project failure, shifting the strategic focus from code metrics to requirements metrics as the primary risk factor.
An analysis of key standards such as ISO 25010 (SQuaRE) and IEEE 1061 demonstrates industry and academic consensus on the need for systematic measurement of requirements attributes such as completeness, consistency, and unambiguity. Among these attributes, ambiguity has the largest share of defect subtypes, highlighting its critical impact on interpretation and implementation.
It has been found that the Goal/Question/Metric (GQM) methodology applied to requirements management (RM) practices in the CMMI model provides a structured framework for empirical validation of these metrics. The central practical indicator of specification quality is the Requirements Stability Ratio, whose high value directly correlates with unproductive rework and low functionality scalability.
The report also discusses the contradictions in the application of formal methods, which, although they eliminate ambiguity, can increase complexity and lead to “bugs in the specification itself,” which can account for up to 60% of all input defects. Significant limitations are associated with natural language quantification (NLP), including problems of lexical and contextual ambiguity, as well as dependence on the quality of training data.
However, the integration of large language models (LLMs) opens up promising avenues for automated defect detection and tracing, reducing post-release defects by up to 40% through early automated validation. The conclusions drawn emphasize a strategic shift in focus to requirements metrics as a key lever for increasing Return on Investment (ROI) in software development.
Keywords: software specification, requirements attributes, quality metrics, requirements metrics, software quality standards, development cost-effectiveness.
doi: 10.32403/1998-6912-2025-2-71-82-93