Requirements Volatility in Software Architecture Design: An Exploratory Case Study

A research team from the University of Oulu, including Sanja Aaramaa, Sandun Dasanayake, and Markku Oivo, has published a significant study on the relationship between changing requirements and software architecture. Their paper, 'Requirements Volatility in Software Architecture Design: An Exploratory Case Study,' addresses a critical gap in software engineering research. While previous work focused primarily on project management impacts, this study specifically examines how volatile requirements affect the technical design of systems, finding they can lead directly to higher defect density during testing.

The researchers conducted 15 semi-structured interviews at a company providing software products to both business customers and consumers. Their investigation revealed that factors like requirements uncertainty and a dynamic business environment are primary drivers of volatility. This volatility poses substantial challenges to software architects, including scheduling difficulties and the accumulation of architectural technical debt—compromises in design that incur future costs.

The study's industrial relevance is high, as it not only identifies the problems but also discusses practical means to mitigate the factors causing volatility and address the resulting design challenges. For software architects and development teams, this research provides a framework for understanding and managing the inevitable changes in requirements, helping to prevent project delays and cost overruns that plague the industry.