Search results

Overviews the history of prototyping. Illustrates trends which have supported the emergence of it. Comments on methods which are in line with prototyping. Suggests future areas of research and development. Explores the integration of prototyping into systems development which incorporates pre‐existing software.

Explains and defines prototyping in terms of its character, actors and types. Examines four aspects: its use in the software development process, its goals, horizontal and vertical and the relationship between prototype and application system. Clarifies the distinction between breadboard and prototype.

Why are we publishing this special issue on prototyping? Hasn't the subject received enough attention already, prototyping having become little more than a hackneyed buzzword? I don't think so. On the contrary, I feel we have reached a good time to summarize the ideas behind this concept, and the experience gained with the practice.

Presents five case studies of industrial software projects specifically involving prototyping. Designates projects ranging from 240 person‐years to two person‐years involving large industrial corporations to small/medium software manufacturers. Analyses the benefits and limitations of prototyping. Concludes that prototyping is conducive to the quality of the product and the development process, particularly when used in conjunction with an evolutionary development strategy and when all parties are aware of the benefits and limitations.

Compares experimental (eg. prototyping) and analytical (eg. specifying) approaches in systems design. Derives ′The Principle of Limited Reduction′. Defines this as: “Relying on an analytical mode of operation to reduce complexity introduces new sources of uncertainty requiring experimental countermeasures; relying on an experimental mode of operation to reduce complexity introduces new sources of uncertainty requiring analytical countermeasures”. Concludes that a mixed approach is best, but warns that this is as yet (1992) hypothetical.

The guest editor's editorial speaks for itself in introducing the scope of this special issue on prototyping. As a general overview of the contribution, from a farther perspective than the authors—all system developers or prototyping practitioners—I submit the following brief comments.