%0 Conference Paper %1 loconsole05 %A Loconsole, A. %A Borstler, J. %B Asia-Pacific Software Engineering Conference %D 2005 %J APSEC '05 %K evolution requirements empirical %P 1--8 %T An industrial case study on requirements volatility measures %U http://ieeexplore.ieee.org/xpls/abs_all.jsp?arnumber=1607159 %X Requirements volatility is an important risk factor for software projects. Software measures can help in quantifying and predicting this risk. In this paper, we present an industrial case study that investigated measures of volatility for a medium size software project. The goal of the study was twofold: 1) to empirically validate a set of measures associated with the volatility of use case models (UCM); 2) to investigate the correlation between subjective and objective volatility. Measurement data was collected in retrospect for all use case models of the software project. In addition, we determined subjective volatility by interviewing stakeholders of the project. Our data analysis showed a high correlation between our measures of size of UCM and total number of changes, indicating that the measures of size of UCMs are good indicators of requirements volatility. No correlations was found between subjective and objective volatility. These results suggest that project managers at this company should measure their projects because of the risk to take wrong decisions based on their own and the developer's perceptions.

@inproceedings{loconsole05, abstract = {Requirements volatility is an important risk factor for software projects. Software measures can help in quantifying and predicting this risk. In this paper, we present an industrial case study that investigated measures of volatility for a medium size software project. The goal of the study was twofold: 1) to empirically validate a set of measures associated with the volatility of use case models (UCM); 2) to investigate the correlation between subjective and objective volatility. Measurement data was collected in retrospect for all use case models of the software project. In addition, we determined subjective volatility by interviewing stakeholders of the project. Our data analysis showed a high correlation between our measures of size of UCM and total number of changes, indicating that the measures of size of UCMs are good indicators of requirements volatility. No correlations was found between subjective and objective volatility. These results suggest that project managers at this company should measure their projects because of the risk to take wrong decisions based on their own and the developer's perceptions.}, added-at = {2006-09-04T19:16:16.000+0200}, author = {Loconsole, A. and Borstler, J.}, biburl = {https://www.bibsonomy.org/bibtex/271ca58f8aff5940338bde061310be087/neilernst}, booktitle = {Asia-Pacific Software Engineering Conference}, citeulike-article-id = {776813}, description = {citeulike sept 4}, interhash = {2debcdb02334711bf9d5a1494bd8f8f0}, intrahash = {71ca58f8aff5940338bde061310be087}, journal = {APSEC '05}, keywords = {evolution requirements empirical}, pages = {1--8}, priority = {0}, timestamp = {2006-09-04T19:16:16.000+0200}, title = {An industrial case study on requirements volatility measures}, url = {http://ieeexplore.ieee.org/xpls/abs_all.jsp?arnumber=1607159}, year = 2005 }