Paper

{
  "raw_xml": "<entry>\n    <id>http://arxiv.org/abs/2603.17648v1</id>\n    <title>Requirements Volatility in Software Architecture Design: An Exploratory Case Study</title>\n    <updated>2026-03-18T12:08:55Z</updated>\n    <link href='https://arxiv.org/abs/2603.17648v1' rel='alternate' type='text/html'/>\n    <link href='https://arxiv.org/pdf/2603.17648v1' rel='related' title='pdf' type='application/pdf'/>\n    <summary>Requirements volatility is a major issue in software (SW) development, causing problems such as project delays and cost overruns. Even though there is a considerable amount of research related to requirement volatility, the majority of it is inclined toward project management aspects. The relationship between SW architecture design and requirements volatility has not been researched widely, even though changing requirements may for example lead to higher defect density during testing. An exploratory case study was conducted to study how requirements volatility affects SW architecture design. Fifteen semi-structured, thematic interviews were conducted in the case company, which provides the selection of software products for business customers and consumers. The research revealed the factors, such as requirements uncertainty and dynamic business environment, causing requirements volatility in the case company. The study identified the challenges that requirements volatility posed to SW architecture design, including scheduling and architectural technical debt. In addition, this study discusses means of mitigating the factors that cause requirements volatility and addressing the challenges posed by requirements volatility. SW architects are strongly influenced by requirement volatility. Thus understanding the factors causing requirements volatility as well as means to mitigate the challenges has high industrial relevance.</summary>\n    <category scheme='http://arxiv.org/schemas/atom' term='cs.SE'/>\n    <published>2026-03-18T12:08:55Z</published>\n    <arxiv:comment>International Conference on Software and System Process 2017</arxiv:comment>\n    <arxiv:primary_category term='cs.SE'/>\n    <author>\n      <name>Sanja Aaramaa</name>\n    </author>\n    <author>\n      <name>Sandun Dasanayake</name>\n    </author>\n    <author>\n      <name>Markku Oivo</name>\n    </author>\n    <author>\n      <name>Jouni Markkula</name>\n    </author>\n    <author>\n      <name>Samuli Saukkonen</name>\n    </author>\n    <arxiv:doi>10.1145/3084100.3084105</arxiv:doi>\n    <link href='https://doi.org/10.1145/3084100.3084105' rel='related' title='doi'/>\n  </entry>"
}