New change impact factor estimation in software development

Change in software is always an essential part of software development and maintenance. Estimating a proposed change's effect on the later phases of the development helps project managers and developers with decision-making and predicting future progress. During development, on some occasions, speedy solutions are necessary to meet project schedules. Such quick changes may lead to major quality flaws in the long term, even though they solve local problems in the short term. Controlled management of change is achieved by being able to estimate the impact of changes. In this paper, we propose a new change impact factor estimation and present the design of an experiment to measure these effects, describe its application, and show the measured results of the change impact.

New change impact factor estimation in software development

Change in software is always an essential part of software development and maintenance. Estimating a proposed change's effect on the later phases of the development helps project managers and developers with decision-making and predicting future progress. During development, on some occasions, speedy solutions are necessary to meet project schedules. Such quick changes may lead to major quality flaws in the long term, even though they solve local problems in the short term. Controlled management of change is achieved by being able to estimate the impact of changes. In this paper, we propose a new change impact factor estimation and present the design of an experiment to measure these effects, describe its application, and show the measured results of the change impact.

___

  • • Determine the quality of software via CIF; a high CIF indicates low quality or an immature software project.
  • Alpha values help to predict a change based on the average of how many other changes it
  • initiates. Consequently, this helps during: ◦ Decision making, ◦ Effort estimation, and ◦ Project scheduling.
  • J.W. Fawcett, M.K. Gungor, “Software development risk model. Applied to data from open-source Mozilla project”, 2005 International Conference on Software Engineering Research and Practice, Las Vegas, NV, USA, 2005.
  • J.W. Fawcett, M.K. Gungor, A.V. Iyer, “Analyzing static structure of large software systems based on data from open-source Mozilla project”, 2005 International Conference on Software Engineering Research and Practice, Las Vegas, NV, USA, 2005.
  • S.L. Pfleeger, S.A. Bohner, “A framework for software maintenance metrics”, IEEE Transactions on Software Engineering, pp. 320-327, 1990.
  • S. Bohner, R. Arnold, Software Change Impact Analysis, Los Alamitos, CA, USA, IEEE Computer Society Press, 1996.
  • S. Barros, T. Bodhuin, A. Escudie, J.P. Queille, J.F. Voidrot, “Supporting impact analysis: a semi-automated technique and associated tool”, Proceedings of the Conference on Software Maintenance, pp. 42-51, 1995.
  • M. Lee. Change Impact Analysis of Object-Oriented Software. PhD Dissertation, George Mason University, 1999.
  • M. Lee, A.J. Offutt, R.T. Alexander, “Algorithmic analysis of the impacts of changes to object-oriented software”, TOOLS-34 ’00, 2000.
  • J. Law. G. Rothermel, “Incremental dynamic impact analysis for evolving software systems”, Proceedings of the International Symposium on Software Reliability Engineering, pp. 430-441, 2003
  • S. Jungmayr, “Identifying test-critical dependencies”, Proceedings of the International Conference on Software Maintenance, IEEE, pp. 404-413, 2001.
  • B.G. Ryder, F. Tip, “Change impact analysis for object-oriented programs”, ACM Workshop on Program Analysis
  • for Software Tools and Engineering, Vol. 1, pp. 46-53, 2001.