The DIANE+ Method Jean-Claude Tarby and Marie-France Barthet TRIGONE Laboratory, CUEEP Institute, Université Lille 1, F-59655 Villeneuve d'Ascq Cedex, France Phone: +33-20.43.32.62 – Fax: +33-20.43.32.79 E-mail: Jean-Claude.Tarby@univ-lille1.fr Laboratory for Information Science, Université Toulouse I, Place Anatole France, F-31042 Toulouse Cedex, France Phone: +33-61.63.36.03 – Fax: +33-61.63.37.98 E-mail: barthet@cict.fr Abstract The DIANE method has been created to solve malfunctions in the use of interac- tive software, leading to trouble in the information systems and difficulties in the user learning and memorisation. The DIANE method aims to integrate the user and his interaction capability into the current process of designing an interactive soft- ware. DIANE+ extends the DIANE method to make possible the automatic genera- tion of user interface. This extension concerns the model of dialogue control, and the integration of an OPAC object data model extending the PAC model. This work is based upon a key concept: the control sharing between man and machine. Our approach complements the object methods by integrating aspects relating to tasks and work stations, and concepts such as the user's level and activity. Keywords User interface design, task analysis, computer-aided generation, automatic contex- tual help, automatic user interface management. Introduction With actual UIMSs, user-friendly interfaces can be created with greater decisional latitude 1 , direct manipulation, prototyping facilities and code generation. These two last features can be executed from screen layouts or specifications of the applica- tion. On the other hand, UIMSs have a major default: they do not integrate ergo- nomics into the life cycle. These limitations occur at four distinct levels: 1. The user is not modelled in the application, so interactions are treated inde- pendently of him, and do not take into account his level of knowledge of the application (from beginner to expert); 2. UIMS do not have any specification method. They are used after specifications have been made; 1 The decisional latitude is the user’s freedom of action within the application.