Practitioners’ perceptions on requirements smells

Software specifications are usually written in natural language and may suffer from imprecision, ambiguity, and other quality issues, hereafter referred to as requirement smells. Requirement smells can hinder project development in many aspects, such as delays, reworks, and low customer satisfaction. From an industrial perspective, we want to focus our time and effort on identifying and preventing the requirement smells of high interest. We also want to identify the metrics to measure the effect of smells on a software project. We aim to characterise types of requirement smells in terms of frequency, severity, and effects. To the best of our knowledge, no previous study analysed how frequency, severity, or effects vary across types of smells. We interview ten experienced practitioners from different divisions of a large international company in the safety-critical domain called MBDA Italy Spa. Then we survey 58 people from the same company to support our findings and extend the analysis to metrics for measuring specific types of requirements smells effects. Our results show that the smell types perceived as most severe are Ambiguity and Unverifiability, while the most frequent are Ambiguity and Incompleteness. We also provide six Findings about requirements smells, such as that the effects of smells are expected to differ across smell types and stages of the project. our study suggests that measuring the effects of requirement smells may necessitate type-specific metrics. Our results contribute to a greater understanding of the importance of addressing requirement smells and provide actionable insights for improving requirement quality in industrial settings. Our results pave the way for future empirical investigations, such as mining project repositories, to measure the specific effect type and size of specific requirements’ smells. • Ambiguity and Unverifiability stand out as the most critical challenges in requirements engineering, significantly impacting software quality and project success. • This study reveals how requirement issues can cause project delays, costly rework, and diminished customer satisfaction, shedding light on their real-world consequences. • Through an innovative mix of practitioner interviews and broader surveys, we explored how different roles perceive and prioritize these issues, ensuring insights are both practical and actionable. • We introduced new metrics tailored to measure the impact of specific requirement issues, offering a pathway for teams to track and improve software project outcomes. • By engaging 58 professionals from a safety-critical industry, this research bridges the gap between theoretical knowledge and real-world application, paving the way for better requirement quality management.