Software prototyping: Difference between revisions

Revision as of 22:26, 3 April 2021

Revision as of 23:16, 11 April 2021

Line 1:

{{shortShort description|Activity of creating prototypes of software applications}}

{{otherOther 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]].

Line 129:

Systems with little user interaction, such as [[batch processing]] or systems that mostly do calculations, benefit little from prototyping. Sometimes, the coding needed to perform the system functions may be too intensive and the potential gains that prototyping could provide are too small.{{Ref label|7|7}}

Prototyping is especially good for designing good [[human-computerhuman–computer interface]]s. "One of the most productive uses of rapid prototyping to date has been as a tool for iterative user requirements engineering and human-computerhuman–computer interface design."{{Ref label|8|8}}

===Dynamic systems development method===

Line 251:

# {{note|17}} from GE Research and Development. https://web.archive.org/web/20061013220422/http://www.crd.ge.com/esl/cgsp/fact_sheet/objorien/index.html

# {{note|18}} Dynamic Systems Development Method Consortium. https://web.archive.org/web/20060209072841/http://na.dsdm.org/

# {{note|19}} Alan Dix, Janet Finlay, Gregory D. Abowd, Russell Beale; Human-ComputerHuman–Computer Interaction, Thirdthird edition

==References==