%0 Journal Article %1 stark99 %A Stark, George E. %A Oman, Paul %A Skillicorn, Alan %A Ameele, Alan %D 1999 %J Journal of Software Maintenance: Research and Practice %K maintenance software requirements empirical %N 5 %P 293--309 %T An examination of the effects of requirements changes on software maintenance releases %U http://dx.doi.org/10.1002/(SICI)1096-908X(199909/10)11:5<293::AID-SMR198>3.0.CO;2-R %V 11 %X Requirements are the foundation of the software release process. They provide the basis for estimating costs and schedules, as well as developing design and testing specifications. When requirements have been agreed on by both clients and maintenance management, then adding to, deleting from, or modifying those existing requirements during the execution of the software maintenance process impacts the maintenance cost, schedule, and quality of the resulting product. The basic problem is not the changing in itself, but rather the inadequate approaches for dealing with changes in a way that minimizes and communicates the impact to all stakeholders.Using data collected from one organization on 44 software releases spanning seven products, this paper presents two quantitative techniques for dealing with requirements change in a maintenance environment. First, exploratory data analysis helps one to understand the sources, frequency, and types of changes being made. Second, a regression model helps managers communicate the cost and schedule effects of changing requirements to clients and other release stakeholders. These two techniques can help an organization provide a focus for management action during the software maintenance process

@article{stark99, abstract = {Requirements are the foundation of the software release process. They provide the basis for estimating costs and schedules, as well as developing design and testing specifications. When requirements have been agreed on by both clients and maintenance management, then adding to, deleting from, or modifying those existing requirements during the execution of the software maintenance process impacts the maintenance cost, schedule, and quality of the resulting product. The basic problem is not the changing in itself, but rather the inadequate approaches for dealing with changes in a way that minimizes and communicates the impact to all stakeholders.Using data collected from one organization on 44 software releases spanning seven products, this paper presents two quantitative techniques for dealing with requirements change in a maintenance environment. First, exploratory data analysis helps one to understand the sources, frequency, and types of changes being made. Second, a regression model helps managers communicate the cost and schedule effects of changing requirements to clients and other release stakeholders. These two techniques can help an organization provide a focus for management action during the software maintenance process}, added-at = {2006-09-19T02:18:18.000+0200}, author = {Stark, George E. and Oman, Paul and Skillicorn, Alan and Ameele, Alan}, biburl = {https://www.bibsonomy.org/bibtex/239b4867017baf37174c7f5d74c88ab12/neilernst}, citeulike-article-id = {776812}, interhash = {2ffd2ae972e32b90e9c8b43a78429063}, intrahash = {39b4867017baf37174c7f5d74c88ab12}, journal = {Journal of Software Maintenance: Research and Practice}, keywords = {maintenance software requirements empirical}, number = 5, pages = {293--309}, timestamp = {2006-09-19T02:18:18.000+0200}, title = {An examination of the effects of requirements changes on software maintenance releases}, url = {http://dx.doi.org/10.1002/(SICI)1096-908X(199909/10)11:5<293::AID-SMR198>3.0.CO;2-R}, volume = 11, year = 1999 }