Cited by 81Software Engineering Techniques and PracticesUsability and User Interface DesignAdvanced Software Engineering Methodologies

The DOI matches its Crossref record.

Prototyping in industrial software projects-bridging the gap between theory and practice

Lichter, H., Schneider-Hufschmidt, M., Zullighoven, H.·1994·IEEE Transactions on Software Engineering

Abstract

Prototyping, a method and technique frequently used in many engineering disciplines, has been adopted as a technique in software engineering to improve the calculation of new projects involving risks. However, there has so far been a lack of documented experience with the use of prototyping in industrial software production. The paper tries to close this gap. First, we introduce central prototyping concepts and terminology. We also present five industrial software projects in which explicit use was made of prototyping. Based on our analysis of these projects we present the resulting conclusions: prototyping means more than rapidly developing user interfaces; prototyping is a central part of a development strategy; prototyping means end user involvement; finding the right mixture of prototypes improves the development process.>

Overview

Integrity signals

Registry

Crossref · 10.1109/32.368126

Cites

Statistics

Recomputing p-values needs the paper’s full text.

Verification

Claims the paper makes

This paper’s full text isn’t openly available, so its claims and self-check weren’t run. The registry and citation checks still apply.

Claims other papers make about this one

Each is checked against this paper’s own text: does it say what the citing paper says it does?

  • One purpose of prototyping may be to evolve the prototype into a final product based on user feedback and priorities.

    “One purpose of prototyping may be to evolve the prototype into a final product based on user feedback and priorities (Budde and Zullighoven 1990;Lichter et al. 1994;Schneider 1996;Toffolon and Dakhli 2008).”
  • Breadboard prototypes are used to investigate technical aspects and to support system specification and coding.

    “Similarly, breadboard prototypes are used to investigate technical aspects, e.g. in circuit design, and to support system specification and coding (Budde and Zullighoven 1990;Ciriello et al. 2017;Lichter et al. 1994;Lim et al. 2008).”
  • A prototype built to demonstrate feasibility can also support project acquisition.

    “Furthermore, Lichter et al. found that a prototype built to demonstrate feasibility can also support project acquisition (Lichter et al. 1994).”
  • A prototype may convey an overly positive impression of the current status that can lead to unrealistic customer expectations and subsequent requests to evolve the prototype into the final system.

    “However, a prototype may convey an overly positive impression of the current status that can lead to unrealistic customer expectations and subsequent requests to evolve the prototype into the final system (Lichter et al. 1994).”
  • The usage environment for a prototype can affect the outcome both in the possible feedback and the representation of subjects in the review.

    “The usage environment for a prototype can affect the outcome (Grevet and Gilbert 2015;Lichter et al. 1994;Tronvoll et al. 2017) both in the possible feedback and the representation of subjects in the review.”

Citations

Cites

No references could be resolved yet.

Research works printed but not linked: 26

  1. gordon, 1991, Rapid Prototyping and Software Quality Lessons from Industry
  2. grant, 1985, The downside of 4GLs, Datamation, 99
  3. 1992, Rapid software prototyping, Proc 25th Hawaii Int Conf Syst Sci, 470
  4. iggulden, 1986, Prototyping?State of the Art Report, 55
  5. 1992, Software prototyping, Info Technol People, 8
  6. kieback, 1992, Prototyping in industriellen Software-Projekten, Erfahrungen und Analysen Informatik-Spektrum, 15, 65
  7. 10.1080/07399018808962930 · DOI
  8. lantz, 1986, The Prototyping Methodology
  9. lipp, 1986, Prototyping?State of the Art Report, 129
  10. 10.1007/978-3-642-69796-8_10 · DOI
  11. 10.1145/800027.808439 · DOI
  12. bourke, 1986, Prototyping?State of the Art Report, 15
  13. carey, 1989, The prototyping conundrum, Datamation, 29
  14. budde, 1992, Prototyping?An Approach to Evolutionary System Development Heidelberg, 10.1007/978-3-642-76820-0 · DOI
  15. floyd, 1987, Computers and Democracy A Scandinavian Challenge
  16. floyd, 1984, Approaches to Prototyping, 105
  17. 10.1109/TSE.1984.5010238 · DOI
  18. goma, 1986, Prototyping?State of the Art Report, 41
  19. blum, 1986, Prototyping?State of the Art Report, 3
  20. meyer, 1988, Object-Oriented Software Construction
  21. rzevski, 1984, Approaches to Prototyping, 341
  22. 10.1145/1005959.1005963 · DOI
  23. tillmann, 1989, Prototyping for the right results, Datamation, 42
  24. 10.1080/07399018908960156 · DOI
  25. 10.1080/07399019108964983 · DOI
  26. 10.1093/comjnl/34.2.153 · DOI

Cited by

Sorted by citations

Metadata

Authors
Lichter, H., Schneider-Hufschmidt, M., & Zullighoven, H.
Affiliations
University of Stuttgart (DE)
Venue
IEEE Transactions on Software Engineering
Published
1994
Volume
20
Issue
11
Pages
825-832
ISSN
0098-5589 (ISSN-L)
OpenAlex
W2161498631
Cited by
81
References
0
Citations by year
2026: 2 · 2025: 3 · 2024: 4 · 2023: 1 · 2022: 1 · 2021: 3 · 2020: 5 · 2019: 4 · 2018: 2 · 2017: 2 · 2016: 2 · 2015: 2 · 2014: 1 · 2013: 2 · 2012: 1
FWCI
4.36
Type
journal article
Language
en
Open access
closed
Locations
IEEE Transactions on Software Engineering (publishedVersion)
Topics
  • Physical Sciences › Computer Science › Information Systems › Software Engineering Techniques and Practices
  • Physical Sciences › Computer Science › Human-Computer Interaction › Usability and User Interface Design
  • Physical Sciences › Computer Science › Software › Advanced Software Engineering Methodologies
Keywords
prototype development, industrial software projects, software development strategy, end-user involvement, user interface development, theory-practice gap

About these checks

Registry, retraction, Cites and statistics results are computed, not judged, with one exception: a printed reference that no index lists is read once by a model before it counts as a citation error. Claims are extracted by a model and kept only when their quote appears verbatim in the text; each cited source is then checked, with a model’s help, for whether it says what the claim relies on. Those verdicts can be wrong — read the claim’s quote and the cited source before relying on one.

Statistics and arithmetic are recomputed, not judged.

Confidence bands are shown only for fields calibrated on our annotated test set. None is calibrated yet, so no band is shown.

What counts as a claim ›How we measure confidence ›How we check this ›

Are you an author, or do you see a problem with this page? Request a review