Almost half of a software maintainer's time is spent trying to understand programs. This means that software maintenance cost prediction depends on software understandability. We have proposed ripple complexity as a means to predict program understandability. This paper describes an experiment to prove the usefulness of ripple complexity. The result of this experiment has shown that ripple complexity is more closely related to program understandability than lines of source code, cyclomatic complexity and function point analysis.< <ETX xmlns:mml="http://www.w3.org/1998/Math/MathML" xmlns:xlink="http://www.w3.org/1999/xlink">></ETX>
No takes yet. Share an insight, caveat, or question.
Hirota et al. (2002) studied this question.
Synapse has enriched 3 closely related papers on similar clinical questions. Consider them for comparative context: