![]() in a file format that can at least be viewed by the project team members, better even annotated) close to what will actually be built later.Requirements for an optimal prototype can be derived from this insight: Prototypes musts be Change requests surface whenever you walk your project team through a design (no matter on which level of development you are right then). This is driven from the insight that changes get more expensive the later in the development process they are realized – and anyone who has worked in software development knows that changes are inevitable. Why bother? The aim of prototyping is to simulate the behavior of digital artifacts before any real development effort has had to be invested. ![]() Prototyping is, eventually, a central area of work for interaction designers, information architects and people with other roles in the software development process. This is a summary of my experiences with different tools for and approaches to prototyping.
0 Comments
Leave a Reply. |