The Model Based Method relies upon the development of a set of mutual dependant models. All models are subject to the generic and iterative modelling phase of analysis, design, and evaluation. The consequence is that the design team can leave one perspective and switch to another at any time in the development cycle, since the modification of one model implicitly affects the other models. Thus, problems abandoned in one perspective can be solved implicitly from another perspective.
The method can be conceptually heavy for the developers. The main reason for this is the employment of multiple perspectives to the interactive system to be developed. Despite this, the development team appreciated the method because the models served as a concise communication medium. Both users, other experts, and members of the development team can discuss the various models and discover unnecessary, erroneous or lacking concepts at an early stage in the development cycle - even before prototypes are developed.
The budget of STOY is 500.000 ECU. Four people have been involved in the development team. The project is on schedule regarding both time and budget constraints. The system is when writing in phase 8.
The method is now being used by two other projects. The first project aims at making a navigational aid system for blind people. The second project designs and tests prototypes and existing information- and communication systems for truck drivers. Both projects share the navigation task, but the user and the domain are slightly different. Thus, the task and domain models in the former project were reused and slightly modified in the latter project because of a different user profile.
In a third project we are searching for an effective development method for multi-modal user interface systems. The method will be reviewed in this project.
Aamodt, A. ( 1991), A knowledge-intensive, integrated approach to problem solving and sustained learning, Ph.D. thesis, Norwegian University of Science and Technology, May 1991.
Hall, A. ( 1997), "Do interactive systems need specifications?", In: Design Specification and Verification of Interactive Systems '97, pp. 1-12, SpringerVerlag, June 1997.
Wielinga et al ( 1994), Expertise model definition document. ESPRIT Project P- 5248 /KADS-II/M2/UvA/026/5.0, University of Amsterdam, Free University of Brussels and Netherlands Energy Research Center ECN, June 1994.