Editing Software prototyping (section)

{{Short description|Activity of creating prototypes of software applications}}
{{Other uses|Prototype-based programming}} 
{{Software development process}}
'''Software prototyping''' is the activity of creating [[prototype]]s of software applications, i.e., incomplete versions of the [[Software|software program]] being developed. It is an activity that can occur in [[Software development process|software development]] and is comparable to [[prototyping]] as known from other fields, such as [[mechanical engineering]] or [[manufacturing]].

A prototype typically simulates only a few aspects of, and may be completely different from, the final product. 

Prototyping has several benefits: the software designer and implementer can get valuable feedback from the users early in the project. The client and the contractor can compare if the software made matches the [[Program specification|software specification]], according to which the software program is built. It also allows the software engineer some insight into the accuracy of initial project estimates and whether the deadlines and [[Milestone (project management)|milestone]]s proposed can be successfully met. The degree of completeness and the techniques used in prototyping have been in development and debate since its proposal in the early 1970s.<ref>Todd Grimm: The Human Condition: A Justification for Rapid Prototyping. Time Compression Technologies, vol. 3 no. 3. Accelerated Technologies, Inc. May 1998 . Page 1. [http://www.tagrimm.com/publications/art-human-1998.html]</ref>