Logout

1.2.9

Discuss the importance of iteration during the design process.

 

Teaching Note:

MYP Design cycle.

 

JSR Notes:

"Iteration" means to repeat. And so the point here is that you don't just go through the design cycle once. Rather, once you have a functional product, you then look at it and refine it, and in the process go through the entire design cycle again. And this repeats over and over again, whether it be a new major release of a software application, or a new iMac.

Importance of iteration:


The cycle that we go through with each major release of a product is, generally (for both hardware and software):

1) Planning, _______ Your dossier Stage A

2) Design, _______ Your dossier Stage B

3) Development _______ Your dossier Stage C

4) Installation (construction and/or programming)_______ Your dossier Stage Programming

5) Implementation _______ Your dossier handing it over to your user to try

6) Evaluation_______ Your dossier Stage E

(And this is cyclical - so right back to the planning for the next iteration of the product, making better and better and better. In fact the key word in the assessment statement, "iterate" implies that the design process is cyclical.)

 

Having to re-build and re-release anything like the iPhone 6 and "Bend-gate".

Think of all of the version of

 

The Example of Your Dossiers Getting Another "Iteration":

With the idea of your Dossiers possibly being taken on by another student (to be further developed), the students will not just program from where you left off. They will "go back to the drawing board" and go through the analysis, class diagrams and plans first, and then they will add to it and maybe even re-do whole classes or whole parts of the program.

Many of the reasons for the planning and the prototyping of the first iteration of the dossier would still be generally applicable the next time around, but (and this is a main point) they would be able to be slightly different and slightly refined because of the existence and use of the first program that you made. Though its actual use, in real life, many things unable to be seen or thought of before could then be taken into consideration.

 

IA Solution Connection and Considerations

 

Jaimie: Version controlling, GIT Hup

and great example of robot fine tuning and ramping up year after year with Vex team

Google always releases in Beta.....

Jose: Team DRIFT - even just changing the design because of lack of proper understanding of the rules and how the game points actaully worked out....

 

Iterative Design Process

The iterative system helps you find problems quickly because it makes it easy to try it again.

Once a design is completed, problems are noted that many test users had with it. These problems would be quickly fixed through an iteration which should be tested to make sure the "fixes" went through and problems that had occurred are solved. It also finds any new usability problems by the new changed design. Iterative design is specifically aimed to teach you through messing up repetitively until you get it right resulting in a more successful final product.

When applied early in the development stage, significant cost savings are possible.

Iterative testing enables an objective assessment of the project's status. Inconsistencies among requirements, designs, and implementations are detected early.

  get isb one

Iterative_development_model_V2.jpg