Jump to content

Iterative design

From Wikipedia, the free encyclopedia

This is an old revision of this page, as edited by 77.251.87.254 (talk) at 11:32, 4 June 2018 (→Marshmallow Challenge: I moved the image to right below the header so that it doesn't break up the sentence.). The present address (URL) is a permanent link to this revision, which may differ significantly from the current revision.

Iterative design is a design methodology based on a cyclic process of prototyping, 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 process

The iterative design process may be applied throughout the new product development process. However, changes are easiest and less expensive to implement in the earliest stages of development. The first step in the iterative design process is to develop a prototype. The prototype should be evaluated by a focus group or a group not associated with the product in order to deliver non-biased opinions. Information from the focus group should be synthesized and incorporated into the next iteration of the design. The process should be repeated until user issues have been reduced to an acceptable level.

Application: Human computer interfaces

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.[1]

The typical steps of iterative design in user interfaces are as follows:

  1. Complete an initial interface design
  2. Present the design to several test users
  3. Note any problems had by the test user
  4. Refine interface to account for/fix the problems
  5. Repeat steps 2-4 until user interface problems are resolved

Iterative design in user interfaces can be implemented in many ways. One common method of using iterative design in computer software is software testing. While this includes testing the product for functionality outside of the user interface, important feedback on the interface can be gained from subject testing early versions of a program. This allows software companies to release a better quality product to the public, and prevents the need of product modification following its release.

Iterative design in online (website) interfaces is a more continual process, as website modification, after it has been released to the user, is far more viable than in software design. Often websites use their users as test subjects for interface design, making modifications based on recommendations from visitors to their sites.

Iterative design use

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

Once the circuit works, improvements or incremental changes may be applied to the breadboard to increase or improve functionality over the original design. When the design is finalized, one can set about designing a proper circuit board meeting the space and weight criteria. Compacting the circuit on the circuit board requires that the wires and components be juggled around without changing their electrical characteristics. This juggling follows simpler rules than the design of the circuit itself, and is often automated. As far as possible off the shelf components are used, but where necessary for space or performance reasons, custom made components may be developed.

Several instances of iterative design are as follows:

  • Wiki: A wiki is a natural repository for iterative design. The 'Page History' facility allows tracking back to prior versions. Modifications are mostly incremental, and leave substantial parts of the text unchanged.
  • Common law: The principle of legal precedent builds on past experience. This makes law a form of iterative design where there should be a clear audit trail of the development of legal thought.
  • Evolution: There is a parallel between iterative and the theory of natural Selection. Both involve a trial and error process in which the most suitable design advances to the next generation, while less suitable designs perish by the wayside. Subsequent versions of a product should also get progressively better as its producers learn what works and what doesn't in a process of refinement and continual improvement.

Fast prototyping tools

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

Benefits

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.[2]

Other benefits to iterative design include:

  1. Serious misunderstandings are made evident early in the lifecycle, when it's possible to react to them.
  2. It enables and encourages user feedback, so as to elicit the system's real requirements.
  3. Where the work is contracted, Iterative Design provides an incremental method for more effectively involving the client in the complexities that often surround the design process.
  4. The development team is forced to focus on those issues that are most critical to the project, and team members are shielded from those issues that distract and divert them from the project's real risks.
  5. Continual testing enables an objective assessment of the project's status.
  6. Inconsistencies among requirements, designs, and implementations are detected early.
  7. The workload of the team, especially the testing team, is spread out more evenly throughout the lifecycle.
  8. This approach enables the team to leverage lessons learned, and therefore to continually improve the process.
  9. Stakeholders in the project can be given concrete evidence of the project's status throughout the lifecycle.

Marshmallow Challenge

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.[3][4]

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.[5] The challenge was invented by Peter Skillman of Palm, Inc. and popularized by Tom Wujec of Autodesk.[6][7][8][9][10][11]

See also

References

  1. ^ Nielsen, J. (1993). "Iterative User Interface Design". IEEE Computer vol.26 no.11 pp 32-41.
  2. ^ Marilyn Mantei; Toby Teorey (April 1988). "Cost/Benefit Analysis for incorporating human factors in the software lifecycle". Publications of the ACM vol.31 no.4 pp 428-439.{{cite journal}}: CS1 maint: multiple names: authors list (link)
  3. ^ "The Marshmallow Challenge". The Marshmallow Challenge. Retrieved 2010-08-10.
  4. ^ "The Marshmallow Challenge". CA: BPWrap. 2010-04-22. Retrieved 2010-08-10.
  5. ^ Jerz, Dennis G. (2010-05-10). "The Marshmallow Challenge - Jerz's Literacy Weblog". Jerz.setonhill.edu. Retrieved 2010-08-10.
  6. ^ Cameron, Chris (2010-04-23). "Marshmallows and Spaghetti: How Kindergartners Think Like Lean Startups". Readwriteweb.com. Retrieved 2010-08-10.
  7. ^ "The Marshmallow Challenge". Engineeringrevision.com. 2010-05-02. Retrieved 2013-08-10.
  8. ^ "The Marshmallow Challenge". Selfish Programming. Retrieved 2013-08-10.
  9. ^ [1] Archived July 13, 2011, at the Wayback Machine
  10. ^ "Marshmallow challenge | Faculty of Science | University of Calgary". Ucalgary.ca. 2010-12-13. Retrieved 2013-08-10.
  11. ^ Original Design Challenge (2014-01-27), Peter Skillman Marshmallow Design Challenge, retrieved 2017-09-12
  • Boehm, Barry W.( May 1988) "A Spiral Model of Software Development and Enhancement," Computer, IEEE, pp. 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-311.
  • Kruchten, Philippe. The Rational Unified Process—An Introduction,
  • Kruchten, P. From Waterfall to Iterative Development - A Challenging Transition for Project Managers. The Rational Edge, 2000. Retrieved from http://www-128.ibm.com/developerworks/rational/library/content/RationalEdge/dec00/FromWaterfalltoIterativeDevelopmentDec00.pdf. Addison Wesley Longman, 1999.


Retrieved from "https://en.wikipedia.org/w/index.php?title=Iterative_design&oldid=844356792"