The analysis phase is based on the product’s development status. At early stages, in order to acquire an accurate elicitation of requirements and needs related to the product, we employ the usual analysis techniques (Requirements definition, focus groups, interviews and questionnaires). However, If an already existing product is to be revised, the analysis stage is preceded by a review of the products status quo, which is carried out using the standard set of (usability) testing procedures.
After all requirements have been defined in the analysis phase, they can be presented in the form of scenarios. Then, the basic structure of the interaction in terms of interaction and operating concepts is defined (conceptual design), which can be exemplified using storyboards. Through GUI (Graphical User Interface) design and the use of mock-ups or prototypes, even users with no programming skills are enabled to interact with the system in a very early stage.
An essential component of our iterative approach is the acquisition of evaluational data and opinions regarding the effectiveness, efficiency and satisfaction of users interacting with the system. We utilize evaluation methods at the end of each development step for every system component, as well as after the final completion of the product’s development.
Depending on the problem, different qualitative and/or quantitative (physiology) methods are employed – either testing (potential) users or experts in laboratory experiments (simulators), or performing field experiments (signage, road tests, traffic monitoring). The information acquired is then evaluated and processed by us.