Software Engineering: Prototype (Definitions)

"A preliminary type, form, or instance of a product or product component that serves as a model for later stages or for the final, complete version of the product. This model (e.g., physical, electronic, digital, analytical) can be used for the following (and other) purposes: assessing the feasibility of a new or unfamiliar technology; assessing or mitigating technical risk; validating requirements; demonstrating critical features; qualifying a product; qualifying a process; characterizing performance or product features; elucidating physical principles; quality. The ability of a set of inherent characteristics of a product, product component, or process to fulfill requirements of customers." (Sandy Shrum et al, "CMMI®: Guidelines for Process Integration and Product Improvement", 2003)

"Software program, hardware assembly, or mockup built to assess feasibility or risks, validate requirements, demonstrate critical features, quantify (measure) performance, or evaluate alternative designs." (Richard D Stutzke, "Estimating Software-Intensive Systems: Projects, Products, and Processes", 2005)

"A simulation of the product using either software prototyping tools, low-fidelity whiteboards, or paper mock-ups. The prototype is intended to make iteasier for stakeholders to understand and describe their requirements." (Suzanne Robertson & James Robertson, "Mastering the Requirements Process" 2nd Ed., 2006)

"A validated build of a system produced at the end of an iteration microcycle." (Bruce P Douglass, "Real-Time Agility", 2009)

"1.An artifact in iterative development. A prototype may be disposable or the base for further incremental development. 2.Verb. To create a test artifact for the sole purpose of determining whether the design is feasible or will be successful given environmental restraints." (DAMA International, "The DAMA Dictionary of Data Management", 2011)

"An early sample or model built to test a concept or process or to act as a thing to be replicated or learned from. In Requirements Engineering prototypes can be used for requirements elicitation and validation." (IQBBA, "Standard glossary of terms used in Software Engineering", 2011)

"A method of obtaining early feedback on requirements by providing a working model of the expected product before actually building it. " (For Dummies, "PMP Certification All-in-One For Dummies" 2nd Ed., 2013)

"A simulation, usually automated, of the computer system to be implemented." (James Robertson et al, "Complete Systems Analysis: The Workbook, the Textbook, the Answers", 2013)

"A mockup of some or all of the application to let the developers and customers study an aspect of the system. Typically a software prototype is a program that mimics part of the application you want to build." (Rod Stephens, "Beginning Software Engineering", 2015)

"The first model of a product. In software, it’s the incomplete product used for testing and validation before final development." (Pamela Schure & Brian Lawley, "Product Management For Dummies", 2017)