Question

How does the Lewis & Rieman design cycle compare to the three stage cycle (design, prototype, evaluate) described in lecture?

Answer 1

The Lewis & Rieman design cycle differs from the three-stage design cycle by explicitly incorporating an iterative or spiral design process that allows for continuous refinement of the design, while the three-stage cycle is more linear.

Step-by-step explanation:

The Lewis & Rieman design cycle and the three stage cycle (design, prototype, evaluate) are similar in that they include key steps intended to develop a product or system. However, the Lewis & Rieman cycle emphasizes a spiral design process, acknowledging the iterative nature of design. Projects often require multiple iterations of prototyping, testing, and refinement as their strengths and weaknesses emerge during evaluation. This cycle may involve going back to earlier stages to make necessary adjustments. The outcome is typically an improved final design, although this can consume more time and resources.

In contrast, the three-stage design cycle discussed in lectures is generally presented as more linear, directly moving from one stage to the next. While it may imply iteration, it does not inherently focus on a spiral of continuous improvement.

Evaluation is used to assess the quality of design, often leading to refinement of the design especially if it fails to meet certain criteria or constraints. The last step in the process, 'Communicate process and results', is vital as it ensures the outcomes and methodologies are shared with relevant stakeholders.

Answer 2

The cycles are very similar in that they both stress thinking about the product from the user's perspective, and basing the entire cycle upon this relationship. The cycles are structured a little differently; the Lewis & Rieman cycle wants the designer to create a rough design of the product, think about the design from the user's standpoint, then create a mock up, whereas the cycle described in class can jump right into the mock up after the designers understand the user's needs. The cycle from lecture doesn't say anything about iterations, which the L&R cycle does before the design is even completed. The L&R cycle talks about the life of the product after the design is completed, such as the designers keeping track of their product, and making changes toit as time goes on, while the cycle from class does not.