Abstract
Abstract:
There has been much discussion on the relative merits of the specification-driven approach to software development versus the prototyping approach. An experiment has been conducted to give some basis for comparison of the two approaches. Seven software teams developed the same application software product. Three used the prototyping approach, four the specifying approach. Results indicate that prototyping required less effort and less code for equivalent performance. Prototyped products were easier to learn and use but rated lower on functionality and robustness. Specified products were easier to integrate.