Skip to main content
SpringerLink
Log in

Is ripple effect intuitive? A pilot study

  • Original Paper
  • Published:
Innovations in Systems and Software Engineering Aims and scope Submit manuscript

Abstract

The computation of ripple effect is based on the effect that a change to a single variable will have on the rest of a program; it determines the scope of the change and provides a measure of the program’s complexity. The original algorithm used to compute ripple effect has been reformulated mainly to provide clarity in the operations involved. The reformulation involved some approximation which was shown not to affect the measures produced. The reformulated, approximated algorithm has been implemented as the software tool: Ripple Effect and Stability Tool (REST). This paper uses a software development project as a case study to look at the relationship between the approximated ripple effect and a programmer’s intuitive idea of ripple effect. Four versions of a mutation testing software tool were written in C over a period of several months. After the completion of each version the programmer was asked to detail his predicted/intuitive ripple effect for each module of code. The predictions are compared with the approximated ripple effect measures for each module and some surprising conclusions drawn.

This is a preview of subscription content, log in via an institution to check access.

Access this article

Log in via an institution

Price excludes VAT (USA)
Tax calculation will be finalised during checkout.

Instant access to the full article PDF.

Institutional subscriptions

Similar content being viewed by others

References

  1. AlSharif M, Bond WP, Al-Otaiby T (2004) Assessing the complexity of software architecture. In: Proceedings of the 42nd annual Southeast regional conference. ACM Press, New York, pp 98–103. DOI http://doi.acm.org/10.1145/986537.986562

  2. Bainbridge JR (1993) A probablistic method for software product measurement. Ph.D. thesis, SCISM, South Bank University, London, p 149

    Google Scholar 

  3. Bainbridge JR, Whitty RW (2000) An empirical investigation into fault coupling in finite functions. Final report to the EPSRC on Grant gr/K85025

  4. Baker A, Bieman J, Fenton N, Gustavson D, Melton A, Whitty R (1990) A philosophy for software measurement. J Syst Softw 12(3):277–281

    Article  Google Scholar 

  5. Basili VR, Hutchens DH (1983b) An empirical study of a syntactic complexity family. IEEE Trans Softw Eng 9(6):664–672

    Article  Google Scholar 

  6. Black SE (2001a) Automating ripple effect measurement. In: 5th world multi-conference on systemics, cybernetics and informatics

  7. Black SE (2001b) Computation of ripple effects for software. Ph.D. thesis, School of Computing, Information Systems and Mathematics, South Bank University, London, p 124

    Google Scholar 

  8. Black SE (2001c) Computing ripple effect for software maintenance. Softw Maint Res Pract 13(4)

  9. Bowen JB (1978) Are current approaches sufficient for measuring software quality? In: Proceedings of the software quality assurance workshop, pp 148–155

  10. Fenton N, Pfleeger SL (1996) Software metrics: a rigorous and practical approach. Chapman and Hall, London

    Google Scholar 

  11. Glass RL (2002) Sorting out software complexity. Commun ACM 45(11):19–21, DOI http://doi.acm.org/10.1145/ 581571.581584

    Article  Google Scholar 

  12. Halstead MH (1977) Elements of software science. Elsevier, New York

    MATH  Google Scholar 

  13. Haney FM (1972) Module connection analysis-a tool for scheduling of software debugging activities. In: Proceedings of the fall joint computer conference, pp 173–179

  14. McCabe TJ (1976) A complexity measure. IEEE Trans Softw Eng 2(4):308–320

    Article  MathSciNet  Google Scholar 

  15. Myers GJ (1980) A model of program stability. Van Nostrand Reinhold, New York, pp 137–155

    Google Scholar 

  16. Park E Robert (1992) Software size measurement: a framework for counting source statements. Software Engineering Institute

  17. Shepperd M (1993) Software engineering metrics volume I: measures and validations. McGraw-Hill, London

    Google Scholar 

  18. Soong NL (1977) A program stability measure. In: Proceedings of the 1977 annual ACM conference, pp 163–173

  19. Yau SS, Collofello JS (1980) Some stability measures for software maintenance. IEEE Trans Softw Eng SE 6(6):545–552

    Article  Google Scholar 

  20. Yau SS, Collofello JS (1985) Design stability measures for software maintenance. IEEE Trans Softw Eng SE 11(9):849–856

    Article  Google Scholar 

  21. Yau SS, Collofello JS, McGregor TM (1978) Ripple effect analysis of software maintenance. In: Proceedings of COMPSAC ’78, pp 60–65

Download references

Author information

Authors and Affiliations

  1. Centre for Systems and Software Engineering, Faculty of Business, Computing and Information Management, London South Bank University, 103 Borough Road, London, SE1 0AA, UK

    Sue Black

Authors
  1. Sue Black
    View author publications

    You can also search for this author in PubMed Google Scholar

Corresponding author

Correspondence to Sue Black.

Rights and permissions

Reprints and permissions

About this article

Cite this article

Black, S. Is ripple effect intuitive? A pilot study. Innovations Syst Softw Eng 2, 88–98 (2006). https://doi.org/10.1007/s11334-006-0004-x

Download citation

  • Received:

  • Accepted:

  • Published:

  • Issue Date:

  • DOI: https://doi.org/10.1007/s11334-006-0004-x

Keywords

Search

Navigation