The DOI matches its Crossref record.
Prototype Experiments: Strategies and Trade-offs
Open accessAbstract
Throughout the whole product development process, there is always a question on whether the proposed product is “up to its task”, and often it is up to the engineer or designer to answer these questions. In many cases, this calls for experiments in form of prototype testing, to explore, verify, and validate the product performance. This paper connects the overall approach of the development process, in form of point-based, set-based, and agile strategies, and connects them to what seems to be the fundamental tradeoff in prototype experiments, exemplified by real cases from an industrial-academic development project.
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 of the main purposes of prototyping is to validate requirements by testing a solution option with internal and/or external stakeholders for perspectives such as problem-solution fit, product-market fit, technical feasibility, and usability.
“One of the main purposes of prototyping is to validate requirements by testing a solution option with internal and/or external stakeholders (Ciriello et al. 2017;Tronvoll et al. 2017) for perspectives, such as problem-solution fit, product-market fit, technical feasibility, and usability.”
From An empirically based model of software prototyping: a mapping study and a multi-case study (2023) · cites this paper as Tronvoll et al. 2017
Proof-of-concept prototypes are built for technical feasibility and can be used to evaluate novel technical approaches.
“Proof-of-concept prototypes are built for this purpose (Tronvoll et al. 2017) and can be used to evaluate novel technical approaches (Fern and Donaldson 1989).”
From An empirically based model of software prototyping: a mapping study and a multi-case study (2023) · cites this paper as Tronvoll et al. 2017
The scope affects the cost of producing a prototype and the feedback that can be obtained.
“The scope affects the cost of producing a prototype and the feedback that can be obtained (Derboven et al. 2010;Lim et al. 2008;Liu and Khooshabeh 2003;McCurdy et al. 2006;Tronvoll et al. 2017).”
From An empirically based model of software prototyping: a mapping study and a multi-case study (2023) · cites this paper as Tronvoll et al. 2017
Tronvoll's flexible exploration strategy corresponds to a single exploration strategy where the solution options are based on best-guesses and on facilitating the change of quality requirements as the work progresses.
“Finally, Tronvoll's flexible exploration strategy corresponds to a single exploration strategy where the solution options are based on best-guesses and on facilitating the change of quality requirements as the work progresses.”
From An empirically based model of software prototyping: a mapping study and a multi-case study (2023) · cites this paper as Tronvoll et al. 2017
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 Tronvoll et al. 2017
We model the exploration strategy aspect using the three facets: single vs parallel exploration, iteration focus, and iteration size.
“We model this aspect using the three facets: single vs parallel exploration, iteration focus, and iteration size These facets are partly based on the four strategies identified by Tronvoll et al., namely point-based, parallel (or set-based solution arrays), optimisation (or performance set investigations), and flexible exploration (Tronvoll et al. 2017).”
From An empirically based model of software prototyping: a mapping study and a multi-case study (2023) · cites this paper as Tronvoll et al. 2017
Our facet of single exploration corresponds to Tronvoll's point-based strategy where resources are focused on one single solution path and where alternatives are considered before being cemented.
“Our facet of single exploration corresponds to Tronvoll's point-based strategy where resources are focused on one single solution path and where alternatives are considered before being cemented.”
From An empirically based model of software prototyping: a mapping study and a multi-case study (2023) · cites this paper as Tronvoll et al. 2017
Tronvoll's optimisation exploration uses parallel exploration with a focus on feature or product level, and with gradually decreasing iteration sizes.
“Tronvoll's optimisation exploration uses parallel exploration with a focus on feature or product level, and with gradually decreasing iteration sizes.”
From An empirically based model of software prototyping: a mapping study and a multi-case study (2023) · cites this paper as Tronvoll et al. 2017
With these four facets of prototype use the main uses of prototype identified in our literature review can be represented, namely internal prototype use without any user presentation, prototype demonstrations, scenario testing, and free testing.
“With these four facets of prototype use the main uses of prototype identified in our literature review can be represented, namely internal prototype use without any user presentation (Budde and Zullighoven 1990;Dow et al. 2011;Schneider 1996), prototype demonstrations (Bellomo et al. 2013;Heisler et al. 1989), scenario testing (Tronvoll et al. 2017), and free testing (Heisler et al. 1989;Tronvoll”
From An empirically based model of software prototyping: a mapping study and a multi-case study (2023) · cites this paper as Tronvoll et al. 2017
When iterating over multiple parallel prototyping instances, the length of the iterations may impact the extent and quality of the prototyped solution option and thus the prototyping effectiveness.
“When iterating over multiple parallel prototyping instances, the length of the iterations may impact the extent and quality of the prototyped solution option and thus the prototyping effectiveness (Tronvoll et al. 2017).”
From An empirically based model of software prototyping: a mapping study and a multi-case study (2023) · cites this paper as Tronvoll et al. 2017
In both prototyping in small optimising iterations and managing quality requirements, the outcome focuses on evaluating against a range of values, as opposed to a simple pass/fail, and the increased complexity of needing to consider influencing factors.
“In both cases, the outcome focuses on evaluating against a range of values, as opposed to a simple pass/fail, and the increased complexity of needing to considering influencing factors (Tronvoll et al. 2017).”
From An empirically based model of software prototyping: a mapping study and a multi-case study (2023) · cites this paper as Tronvoll et al. 2017
Previous research identifies four main strategies, namely point-based, parallel, optimisation and flexible exploration.
“Previous research identifies four main strategies, namely point-based, parallel, optimisation and flexible exploration (Tronvoll et al. 2017).”
From An empirically based model of software prototyping: a mapping study and a multi-case study (2023) · cites this paper as Tronvoll et al. 2017
Citations
Cites
No references could be resolved yet.
Research works printed but not linked: 26
- Smith RP, Tjandra P. Experimental observation of iteration in engineering design. Research in Engineering Design 1998;10:107-17. · DOI
- Dow SP, Klemmer SR. The Efficacy of Prototyping Under Time Constraints. In: Meinel C, Leifer L, Plattner H, editors. Design Thinking, Springer Berlin Heidelberg; 2011, p. 111-28. · DOI · Paper page
- Mohamed Zairi, Mohamed A. Youssef. Quality function deployment: a main pillar for successful total quality management and product development. International Journal of Quality & Reliability Management 1995;12:9-23. · DOI
- Harari O. Ten reasons why TQM doesn’t work. Management Review 1993;82:33.
- Elverum CW, Welo T, Tronvoll S. Prototyping in New Product Development: Strategy Considerations. Procedia CIRP 2016;50:117-22. · DOI
- Cooper RG, Kleinschmidt EJ. New product processes at leading industrial firms. Industrial Marketing Management 1991;20:137-47. · DOI
- Ward A, Liker JK, Cristiano JJ, Sobek DK. The second Toyota paradox: How delaying decisions can make better cars faster. Sloan Management Review 1995;36:43.
- Kennedy BM, Sobek DK, Kennedy MN. Reducing Rework by Applying Set-Based Practices Early in the Systems Engineering Process. Systems Engineering 2014;17:278-96. · DOI
- Sobek DK, Ward AC, Liker JK. Toyota's Principles of Set-Based Concurrent Engineering. Sloan Management Review 1999;40:67-83.
- Welo T. On the application of lean principles in Product Development: a commentary on models and practices. International Journal of Product Development 2011;13:316-43. · DOI
- Smith PG. Flexible product development: building agility for changing markets. John Wiley & Sons; 2007.
- Steinert M, Leifer LJ. “Finding One”s Way’: Re-Discovering a Hunter-Gatherer Model based on Wayfaring. International Journal of Engineering Education 2012;28:251.
- Simon HA. The sciences of the artificial. Cambridge, Mass.: MIT Press; 1969.
- Clark KB, Fujimoto T. Lead time in automobile product development explaining the Japanese advantage. Journal of Engineering and Technology Management 1989;6:25-58. · DOI
- Thomke SH. Managing experimentation in the design of new products. Management Science 1998;44:743-762. · DOI
- Ulrich KT, Eppinger SD. Product design and development. 5th ed. McGraw-Hill; 2012.
- Thomke SH. Simulation, learning and R&D performance: Evidence from automotive development. Research Policy 1998;27:55-74. · DOI · Paper page
- Tronvoll SA, Elverum CW, Welo T. Test Environments in Engineering Design: A conceptual study. DS 85-1: Proceedings of NordDesign 2016, Volume 1, 2016.
- Clark KB, Fujimoto T. Product Development Performance: Strategy, Organization, and Management in the World Auto Industry. Harvard Business Press; 1991.
- Studer R, Benjamins VR, Fensel D. Knowledge engineering: Principles and methods. Data & Knowledge Engineering 1998;25:161-97. · DOI
- Thomke S, Fujimoto T. The Effect of “Front-Loading” Problem-Solving on Product Development Performance. Journal of Product Innovation Management 2000;17:128-42. · DOI
- Hill AV. The Encyclopedia of Operations Management: A Field Manual and Glossary of Operations Management Terms and Concepts. FT Press; 2012. · DOI
- McCurdy M, Connors C, Pyrzak G, Kanefsky B, Vera A. Breaking the fidelity barrier: an examination of our current characterization of prototypes and an example of a mixed-fidelity success. Proceedings of the SIGCHI Conference, ACM; 2006, p. 1233-1242. · DOI · Paper page
- Floyd C. A Systematic Look at Prototyping. In: Budde R, Kuhlenkamp K, Mathiassen L, Züllighoven H, editors. Approaches to Prototyping, Springer Berlin Heidelberg; 1984, p. 1-18. · DOI
- Bjerkholt JT, Lindholm OG. An Innovative Semi-permanent Flood Protection Structure-Alternative to Sandbags and Supplements to Conventional Earth Embankments. Advances in Urban Flood Management 2007:461. · DOI
- Haaland KV, Walderhaug ØB. Master Thesis. Prototyping and testing of novel flood protection systems. 2016.
Cited by
Sorted by citations
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
- Tronvoll, S. A., Elverum, C. W., & Welo, T.
- Affiliations
- Norwegian University of Science and Technology (NO)
- Corresponding author
- Tronvoll, Sigmund A.
- Venue
- Procedia CIRP
- Publisher
- Elsevier BV
- Published
- 2017
- Volume
- 60
- Pages
- 554-559
- ISSN
- 2212-8271 (ISSN-L)
- OpenAlex
- W2612029344
- Cited by
- 10
- References
- 0
- Citations by year
- 2025: 1 · 2023: 2 · 2022: 1 · 2020: 1 · 2019: 4 · 2018: 1
- FWCI
- 2.61
- Type
- journal article
- Language
- en
- Open access
- diamond
- doi.org
- Licence
- Locations
- Procedia CIRP (publishedVersion, cc-by-nc-nd)
- NORA - Norwegian Open Research Archives (submittedVersion, cc-by-nc-nd)
- Topics
- Social Sciences › Business, Management and Accounting › Management of Technology and Innovation › Product Development and Customization
- Physical Sciences › Engineering › Industrial and Manufacturing Engineering › Manufacturing Process and Optimization
- Physical Sciences › Engineering › Mechanical Engineering › Design Education and Practice
- Keywords
- prototype testing, product development, set-based design, agile software development, trade-offs
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