Iterative design: Difference between revisions

{{refimprovemore citations needed|date=January 2011}}

'''Iterative design''' is a [[design]] methodology based on a cyclic process of [[prototyping]], [[Product testing|testing]], analyzing, and refining a product or process. Based on the results of testing the most recent [[iteration]] of a design, changes and refinements are made. This process is intended to ultimately improve the quality and functionality of a design. In iterative design, interaction with the designed system is used as a form of research for informing and evolving a project, as successive versions, or iterations of a design are implemented.

Iterative design is commonly used in the development of human computer interfaces. This allows designers to identify any usability issues that may arise in the user interface before it is put into wide use. Even the best usability experts cannot design perfect user interfaces in a single attempt, so a usability engineering lifecycle should be built around the concept of iteration.<ref>{{cite journal| title=Iterative User Interface Design | year = 1993 | author = Nielsen, J. | journal = IEEE Computer |volume=26 |issue=11 |pagepages=32–41| doi = 10.1109/2.241424 | s2cid = 17748574 }}</ref>

Iterative design is a way of confronting the reality of unpredictable user needs and behaviors that can lead to sweeping and fundamental changes in a design. User testing will often show that even carefully evaluated ideas will be inadequate when confronted with a user test. Thus, it is important that the flexibility of the iterative design’sdesign's implementation approach extends as far into the system as possible. Designers must further recognize that user testing results may suggest radical change that requires the designers to be prepared to completely abandon old ideas in favor of new ideas that are more equipped to suit user needs. Iterative design applies in many fields, from making knives to rockets. As an example consider the design of an [[electronic circuit]] that must perform a certain task, and must ultimately fit in a small space on a [[circuit board]]. It is useful to split these independent tasks into two smaller and simpler tasks, the functionality task, and the space and weight task. A [[breadboard]] is a useful way of implementing the electronic circuit on an interim basis, without having to worry about space and weight.

One approach to iterative design is to use the highest level of abstraction for developing an early generation product. The principle here is that rapid development may not produce efficient code, but obtaining feedback is more important thatthan technology optimization. Examples of this approach include use of non-functional code, object databases, or low code platforms - these allow quick testing of designs before issues of optimization are addressed.

When properly applied, iterative design will ensure a product or process is the best solution possible. When applied early in the development stage, significant cost savings are possible.<ref>{{citeCite journal |doi = 10.1145/42404.42408|title = Cost/Benefit Analysisanalysis for incorporating human factors in the software lifecycle | datejournal = AprilCommunications 1988of |the authorACM|volume = Marilyn31|issue Mantei;= Toby Teorey4|pages = 428–439|year journal= 1988|last1 = PublicationsMantei|first1 of= theMarilyn ACMM.|last2 = Teorey|volumefirst2 =31 Toby J.|issues2cid =4 2031965|pagesdoi-access =428–439 free}}</ref>

[[File:Marshmallow_Challenge.jpg|thumb|upright|Marshmallow challenge winning work.]]

The Marshmallow Challenge is an instructive design challenge. It involves the task of constructing the highest possible free-standing structure with a marshmallow on top. The structure must be completed within 18 minutes using only 20 sticks of spaghetti, one yard of tape, and one yard of string.<ref>{{cite web|url=http://www.marshmallowchallenge.com/Welcome.html |title=The Marshmallow Challenge |publisher=The Marshmallow Challenge |access-date= |accessdate=2010-08-10}}</ref><ref name="bpwrap1">{{cite web|url=http://www.bpwrap.com/2010/04/the-marshmallow-challenge/ |title=The Marshmallow Challenge |location=CA |publisher=BPWrap |date=2010-04-22 |accessdateaccess-date=2010-08-10}}</ref>

Observation and studies of participants show that kindergartners are regularly able to build higher structures, in comparison to groups of business school graduates. This is explained by the tendency for children to at once stick the marshmallow on top of a simple structure, test the prototype, and continue to improve upon it. Whereas, business school students tend to spend time vying for power, planning, and finally producing a structure to which the marshmallow is added.<ref>{{cite web|last=Jerz |first=Dennis G. |url=http://jerz.setonhill.edu/weblog/2010/05/the_marshmallow_challenge/ |title=The Marshmallow Challenge - Jerz's Literacy Weblog |publisher=Jerz.setonhill.edu |date=2010-05-10 |accessdateaccess-date=2010-08-10}}</ref> The challenge helps to build and develop prototyping, teamwork, [https://www.experientiallearning.org/the-marshmallow-challenge-a-facilitative-approach/ leadership and innovation skills] and is a popular [[Science, technology, engineering, and mathematics|STEM]] activity. The challenge was invented by Peter Skillman of [[Palm, Inc.]] and popularized by Tom Wujec of [[Autodesk]].<ref>{{cite web |last=Cameron |first=Chris |url=http://www.readwriteweb.com/start/2010/04/marshmallows-and-spaghetti-how-kindergartners-think-like-lean-startups.php |title=Marshmallows and Spaghetti: How Kindergartners Think Like Lean Startups |publisher=Readwriteweb.com |date=2010-04-23 |accessdateaccess-date=2010-08-10 |archive-url=https://web.archive.org/web/20100821031127/http://www.readwriteweb.com/start/2010/04/marshmallows-and-spaghetti-how-kindergartners-think-like-lean-startups.php |archive-date=2010-08-21 |url-status=dead }}</ref><ref>{{cite web|url=http://engineeringrevision.com/302/the-marshmallow-challenge/ |title=The Marshmallow Challenge |publisher=Engineeringrevision.com |date=2010-05-02 |accessdateaccess-date=2013-08-10}}</ref><ref>{{cite web|url=http://www.selfishprogramming.com/2010/04/28/the-marshmallow-challenge/ |title=The Marshmallow Challenge |publisher=Selfish Programming |access-date= |accessdate=2013-08-10}}</ref><ref>[http://www.ideasforideas.com/content/marshmallow-challenge] {{webarchive|url=https://web.archive.org/web/20110713002340/http://www.ideasforideas.com/content/marshmallow-challenge|date=July 13, 2011}}</ref><ref>{{cite web|url=https://www.ucalgary.ca/science/node/1578 |title=Marshmallow challenge &#124; Faculty of Science &#124; University of Calgary |publisher=Ucalgary.ca |date=2010-12-13 |accessdateaccess-date=2013-08-10}}</ref><ref>{{Citation|last=Original Design Challenge|title=Peter Skillman Marshmallow Design Challenge|date=2014-01-27|url=https://www.youtube.com/watch?v=1p5sBzMtB3Q |accessdatearchive-url=https://ghostarchive.org/varchive/youtube/20211213/1p5sBzMtB3Q| archive-date=2021-12-13 |url-status=live|access-date=2017-09-12}}{{cbignore}}</ref>

* Boehm, Barry W.( (May 1988) "A Spiral Model of Software Development and Enhancement," Computer, IEEE, pp.&nbsp;61–72.

* Gould, J.D. and Lewis, C. (1985). Designing for Usability: Key Principles and What Designers Think, Communications of the ACM, March, 28(3), 300-311300–311.

* {{cite web|last=Kruchten, |first=P. |title=From Waterfall to Iterative Development -– A Challenging Transition for Project Managers. The|type=White paper|publisher=Rational Edge,Software Corporation|year=2000. Retrieved from http|url=https://www-128sceweb.ibmuhcl.comedu/developerworkshelm/rationalRationalUnifiedProcess/librarypapers/contentpdf/RationalEdge/dec00/FromWaterfalltoIterativeDevelopmentDec00tp173a.pdf.|access-date=2019-08-17}} Addison Wesley Longman, 1999.