An integrated rapid prototyping methodology for command and control systems: experience and insight

Tamanaha, D.Y.

doi:10.1109/hicss.1989.48016

Cited by 2 publications

(6 citation statements)

References 2 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…Ford and Marlin state that prototyping "allows early assessment of the efficiency of techniques [FM82]. Overall, seven cases (from six sources) cite improvement in design quality [Hek87,CB85,FM82,Bar89,A8,Kie91], while five sources observe deterioration [BGS84,CB85,Tam82,A9,A10]. Among evolutionary prototyping cases, an equal number reported better and worse design quality.…”

Section: Effect On Design Qualitymentioning

confidence: 99%

“…Code which is transferred to the final product must satisfy the checklist. Quality can also be improved by limiting the scope of the prototype to a particular subset (often the user interface) [Ala84,Tam82,Tae91,Bar89], and by including a design phase with each iteration of the prototype [Hek87]. Another option is to completely discard the prototype.…”

Section: Inferior Design Qualitymentioning

confidence: 99%

“…Of 34 cases, six can be considered substantial (at least 100,000 lines of source code) [AB90,Hek87,Tam82,Mar90,Kie91,A9], and another nine are medium-sized [Gom83, BJK + 89, CB85, A1, A4, Zel80, GCG + 89, Bar89]. We used the descriptions given in the case study reports to distinguish between medium and small projects.…”

Section: Can Prototyping Be Used For Developing Large Systems?mentioning

confidence: 99%

“…Connell and Brice [CB85] describe a project which failed partly because temporary student programmers were thrown into a rapid prototyping environment. Other sources [A7,Tam82,Ala84,A10] state that experienced (or at least thoroughly trained) engineers are required for successful use of rapid prototyping. Alavi describes a successful small-scale project which utilized entry-level programmers, but then concludes without explanation that "Prerequisites to successful prototyping include ... motivated and knowledgeable users and designers" [Ala84].…”

Section: Does Rapid Prototyping Require Experienced Programmers?mentioning

confidence: 99%

“…Only seven authors insist that prototypes be discarded. Six of the case studies [AB90,Hek87,Tam82,Mar90,Kie91,A9] represent successful keep-it prototyping on substantial software projects. On small projects, several sources suggest that keep-it prototyping is essential.…”

Section: Should the Prototype Be Kept Or Thrown Away?mentioning

confidence: 99%

See 4 more Smart Citations

Reported effects of rapid prototyping on industrial software quality

Gordon

Bieman

1993

Software Qual J

View full text Add to dashboard Cite

Empirical data is required to determine the effect of rapid prototyping on software quality. We examine 34 published and unpublished case studies of the use of rapid prototyping in "real world" software development. We identify common observations, unique events, and opinions. We develop guidelines to help software developers use rapid prototyping to maximize product quality and avoid common pitfalls.

show abstract