The benefits of bottom-up design

Abstract

An inconsistency is examined in generic top-down design methods and standards employed in the implementation of reliable software. Many design approaches adopt top-down ordering when defining the structure, interfaces, and processing of a system. However, strict adherence to a top-down sequencing does not permit accurate description of a system's error handling functions. The design of the system response to errors is becoming critical as the reliability requirements of systems increase. How top-down methods such as object oriented design and structured design do not adequately address the issues of error handling is described, and it is suggested using a bottom-up substep within these methods to eliminate the problem