Cited by 10Product Development and CustomizationManufacturing Process and OptimizationDesign Education and Practice

The DOI matches its Crossref record.

Prototype Experiments: Strategies and Trade-offs

Open access

Abstract

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

Crossref · 10.1016/j.procir.2017.01.049

Cites

Statistics

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

Verification

Claims the paper makes

We couldn’t retrieve this paper’s full text, 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 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.”
  • 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).”
  • 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).”
  • 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.”
  • 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. Smith RP, Tjandra P. Experimental observation of iteration in engineering design. Research in Engineering Design 1998;10:107-17. · DOI
  2. 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
  3. 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
  4. Harari O. Ten reasons why TQM doesn’t work. Management Review 1993;82:33.
  5. Elverum CW, Welo T, Tronvoll S. Prototyping in New Product Development: Strategy Considerations. Procedia CIRP 2016;50:117-22. · DOI
  6. Cooper RG, Kleinschmidt EJ. New product processes at leading industrial firms. Industrial Marketing Management 1991;20:137-47. · DOI
  7. 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.
  8. 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
  9. Sobek DK, Ward AC, Liker JK. Toyota's Principles of Set-Based Concurrent Engineering. Sloan Management Review 1999;40:67-83.
  10. 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
  11. Smith PG. Flexible product development: building agility for changing markets. John Wiley & Sons; 2007.
  12. 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.
  13. Simon HA. The sciences of the artificial. Cambridge, Mass.: MIT Press; 1969.
  14. 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
  15. Thomke SH. Managing experimentation in the design of new products. Management Science 1998;44:743-762. · DOI
  16. Ulrich KT, Eppinger SD. Product design and development. 5th ed. McGraw-Hill; 2012.
  17. Thomke SH. Simulation, learning and R&D performance: Evidence from automotive development. Research Policy 1998;27:55-74. · DOI · Paper page
  18. Tronvoll SA, Elverum CW, Welo T. Test Environments in Engineering Design: A conceptual study. DS 85-1: Proceedings of NordDesign 2016, Volume 1, 2016.
  19. Clark KB, Fujimoto T. Product Development Performance: Strategy, Organization, and Management in the World Auto Industry. Harvard Business Press; 1991.
  20. Studer R, Benjamins VR, Fensel D. Knowledge engineering: Principles and methods. Data & Knowledge Engineering 1998;25:161-97. · DOI
  21. 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
  22. Hill AV. The Encyclopedia of Operations Management: A Field Manual and Glossary of Operations Management Terms and Concepts. FT Press; 2012. · DOI
  23. 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
  24. 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
  25. 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
  26. Haaland KV, Walderhaug ØB. Master Thesis. Prototyping and testing of novel flood protection systems. 2016.

Cited by

Sorted by citations

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
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