The DOI matches its Crossref record.
Prototyping in industrial software projects-bridging the gap between theory and practice
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
Cites
Statistics
Verification
Claims the paper makes
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).”
From An empirically based model of software prototyping: a mapping study and a multi-case study (2023) · cites this paper as Lichter et al. 1994
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).”
From An empirically based model of software prototyping: a mapping study and a multi-case study (2023) · cites this paper as Lichter et al. 1994
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).”
From An empirically based model of software prototyping: a mapping study and a multi-case study (2023) · cites this paper as 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).”
From An empirically based model of software prototyping: a mapping study and a multi-case study (2023) · cites this paper as 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.”
From An empirically based model of software prototyping: a mapping study and a multi-case study (2023) · cites this paper as Lichter et al. 1994
Using a prototype in conditions similar to that of the final product increases the chance of uncovering new setting-specific requirements.
“Using a prototype in conditions similar to that of the final product increases the chance of uncovering new setting-specific requirements (Lichter et al. 1994).”
From An empirically based model of software prototyping: a mapping study and a multi-case study (2023) · cites this paper as Lichter et al. 1994
Previous research describes the impact of the physical environment.
“Previous research describes the impact of the physical environment (Lichter et al. 1994).”
From An empirically based model of software prototyping: a mapping study and a multi-case study (2023) · cites this paper as Lichter et al. 1994
There is a risk that prototypes can convey an inaccurate perception of development status and create unrealistic expectations.
“However, there is also a risk that prototypes can convey an inaccurate perception of development status and create unrealistic expectations (Lichter et al. 1994).”
From An empirically based model of software prototyping: a mapping study and a multi-case study (2023) · cites this paper as Lichter et al. 1994
Citations
Cites
No references could be resolved yet.
Research works printed but not linked: 26
- gordon, 1991, Rapid Prototyping and Software Quality Lessons from Industry
- grant, 1985, The downside of 4GLs, Datamation, 99
- 1992, Rapid software prototyping, Proc 25th Hawaii Int Conf Syst Sci, 470
- iggulden, 1986, Prototyping?State of the Art Report, 55
- 1992, Software prototyping, Info Technol People, 8
- kieback, 1992, Prototyping in industriellen Software-Projekten, Erfahrungen und Analysen Informatik-Spektrum, 15, 65
- 10.1080/07399018808962930 · DOI
- lantz, 1986, The Prototyping Methodology
- lipp, 1986, Prototyping?State of the Art Report, 129
- 10.1007/978-3-642-69796-8_10 · DOI
- 10.1145/800027.808439 · DOI
- bourke, 1986, Prototyping?State of the Art Report, 15
- carey, 1989, The prototyping conundrum, Datamation, 29
- budde, 1992, Prototyping?An Approach to Evolutionary System Development Heidelberg, 10.1007/978-3-642-76820-0 · DOI
- floyd, 1987, Computers and Democracy A Scandinavian Challenge
- floyd, 1984, Approaches to Prototyping, 105
- 10.1109/TSE.1984.5010238 · DOI
- goma, 1986, Prototyping?State of the Art Report, 41
- blum, 1986, Prototyping?State of the Art Report, 3
- meyer, 1988, Object-Oriented Software Construction
- rzevski, 1984, Approaches to Prototyping, 341
- 10.1145/1005959.1005963 · DOI
- tillmann, 1989, Prototyping for the right results, Datamation, 42
- 10.1080/07399018908960156 · DOI
- 10.1080/07399019108964983 · DOI
- 10.1093/comjnl/34.2.153 · DOI
Cited by
Sorted by citations
Benefits of and barriers to involving users in medical device technology development and evaluation
Shah, S. G. S., & Robinson, I. (2007) · International Journal of Technology Assessment in Health Care · doi:10.1017/s0266462307051677 · Cited by 299
Shah, S. G. S., Robinson, I., & AlShawi, S. (2009) · International Journal of Technology Assessment in Health Care · doi:10.1017/s0266462309990328 · Cited by 237
An empirically based model of software prototyping: a mapping study and a multi-case study
Bjarnason, E., Lang, F., & Mjöberg, A. (2023) · Empirical Software Engineering · doi:10.1007/s10664-023-10331-w · Cited by 75
Metadata
- Authors
- Lichter, H., Schneider-Hufschmidt, M., & Zullighoven, H.
- Affiliations
- University of Stuttgart (DE)
- ORCID
- Lichter, H.
- 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