In the beginning, they might represent initial concepts without much need for form or finesse. Different Prototypes for Different Levels of Complexityĭifferent Prototypes for Different Levels of Complexity Icon: EUROCONTROL © (All rights reserved)įor our purpose, prototypes can take many forms and evolve together with the design solution they represent. This leads to workarounds and training issues. Most often, this takes so long that there is no room for substantial changes even when they are necessary. After the requirements phase, a demonstrator or alpha version is programmed. Even though ATM systems are mostly software, the same thing happens in ANSPs. The project is bound to specific decisions. They are expensive to produce and thus hard to change or even reject. There, prototypes are almost ready for production and thus almost the final “thing”. They are somewhat different from a prototype in a typical industrial setting. We call these early and intermediate design solutions prototypes. Dead ends can also be identified early and the development can take another direction without severe loss of time and budget. Any mistake can be fixed before it becomes too entangled with other aspects of the product. This way, complexity can be increased in a controlled fashion. That means features and functionality should be introduced gradually during multiple cycles. Instead, the iterative approach should be fully embraced. Under realistic circumstances, this is never the case during the first iteration. Experts and users alike can evaluate the product to determine whether and to what degree the requirements are fulfilled.
![principle prototype tool principle prototype tool](https://miro.medium.com/max/1200/1*RWFZ8f9GzcWpjYs71sqbdw.png)
One key feature of iterative user-centred design is that each cycle yields a product: the design solution. When finished, the context of use is very well known, but changes come at high-cost.Įvaluate as early as possible with the help of prototypes, which range from pen & paper to beta versions to overcome this dilemma. Principle 5: Prototyping Icon: EUROCONTROL © (All rights reserved)ĭesign projects start with limitless possibilities but little knowledge about the context of use. Evaluate as early as possible with the help of prototypes.