Abstract
Previous work on structural software reliability modelling should be
extended to account for data flow in software. A way forward is
explained by contrasting two extremely simple examples of software
structure. In addition to improving software reliability estimates,
development of such an approach is important because it has the
potential to provide guidelines for testable software and it would
provide a formal meaning for the notion of coupling between software
components.
Users
Please
log in to take part in the discussion (add own reviews or comments).