Advertisement

A Technique to Predict Software Change Propagation

  • Leilei YinEmail author
  • Yanchen Liu
  • Ziran Shen
  • Yijin Li
Conference paper
Part of the Advances in Intelligent Systems and Computing book series (AISC, volume 905)

Abstract

Software change can occur frequently and it is inevitable in the lifecycle of software development. It can cause tremendous impact on software engineering including cycle, cost, workload, etc. This work proposes an advanced technique to assess the software changeability on the class level. From the perspective of member variable and function, mutual relations between classes are introduced to record the change likelihood and impact. Change propagation model between classes is developed to transform the change impact and the total impact is calculated to analyse the class changeability. Based on the analysis results, class changes with high risk should be avoided and those with low change risk should be given priority in the software change process. Finally, a simplified software system is applied for the initial evaluation of the method.

Keywords

Class change Mutual relation Change propagation 

References

  1. 1.
    Ramzan, S., Ikram, N.: Making decision in requirement change management. In: International Conference on Information and Communication Technologies, pp. 309–312. IEEE (2005)Google Scholar
  2. 2.
    Leung, H.K.N., White, L.: A study of integration testing and software regression at the integration level. In: Proceedings of Conference on Software Maintenance, pp. 290–301. IEEE (1990)Google Scholar
  3. 3.
    Rothermel, G., Harrold, M.J.: Selecting regression tests for object-oriented software. In: Proceedings of International Conference on Software Maintenance, pp. 14–25. IEEE (1994)Google Scholar
  4. 4.
    Badri, L., Badri, M., St-Yves, D.: Supporting predictive change impact analysis: a control call graph based technique. In: Asia-Pacific Software Engineering Conference, pp. 167–175. IEEE Computer Society (2005)Google Scholar
  5. 5.
    Jang, Y.K., Chae, H.S., Yong, R.K., Bae, D.H.: Change impact analysis for a class hierarchy. In: Proceedings of Software Engineering Conference, Asia Pacific, pp. 304–311 (1998)Google Scholar
  6. 6.
    Tang, D., Xu, R., Tang, J., He, R.: Design structure matrix-based engineering change management for product development. Int. J. Internet Manuf. Serv. 1(3), 231–245 (2008)Google Scholar
  7. 7.
    Wang, Y.H., Wang, L.F., Zhang, S.K., Wang, Q.F.: Tracing approach of software requirement change. Acta Electron. Sin. 34(8), 1428–1432 (2006)Google Scholar
  8. 8.
    Wang, Y.H., Zhang, S.K., Liu, Y., Wang, Y.: Ripple-effect analysis of software architecture evolution based on reachability matrix. J. Softw. 15(8), 1107–1115 (2004)zbMATHGoogle Scholar

Copyright information

© Springer Nature Switzerland AG 2020

Authors and Affiliations

  1. 1.The 28th Research Institute of China Electronics Technology Group CorporationNanjingChina

Personalised recommendations