Iterative Design

The main point of my work in this current unit is to look at design as an iterative process, meaning that when designing we should be constantly testing and re-evaluating our work based on the requirements of the brief and reactions to the work. The iterative process encourages constant refinement and improvement to designs before they are released to make sure they engage properly with the audience and convey the intended message.

The earliest method of design was widely known as the Waterfall Model. It is the incremental progress in steps, a linear approach to design. The process was very popular due to its simplicity and ease of implementation with timeframes and deadlines. In practice the Waterfall Model doesn’t work too well as often clients don’t know their requirements straight away, which can delay the design process and the rest of the step. Clients may also change their requirements during the design process or once the project has been finalised and the model doesn’t allow them to go back easily, but rather have to start again at the top of the waterfall.

Iterative design is a more cyclical process that was developed in response to the weaknesses of the Waterfall Model. The model keeps the same steps ofrequirements gathering, design and implementation etc. but carries them out in a more flexible manner keeping analysis in mind in each step. In each iteration of the cycle most of the development processes are used making it a very effective process. Each iteration has a defined set of objectives and produced a partial working implementation of the finally system. Each successive iteration builds upon the work of previous iterations, continually evolving and refining until a finish product is made.


UPDATE: The iterative design process is something that I will be, and have been using as I progress towards the final product in this project. There is a process of development and constant improvement as I edge ever closer to creating a final, finished product. Each step along the way I set myself a goal of what I want to achieve (e.g. work out how to capture and display faces, improve performance, etc.) and I complete each goal as I progress. At the end of each stage of improvement there is a bit of user testing. The testing would involve me experimenting with my updated code, seeing if I’ve fixed the previous problem or made the appropriate adjustments and then considering what the next stage could be. Occasionally I get 3rd party feedback from other people on the course to see if they have any suggestions on future improvements as these people are representative of the end user (be it a little more informed as they’re also doing the same project) and have an idea of what they’d expect from a face swapping interactive display.


Leave a Reply

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s

%d bloggers like this: