Nowadays, most of the research developed by industry and academy have led to several object-oriented methods highly adequate for the development of systems. But most of these methods do not include mechanisms (models) for: 1) Identify and specify user needs and requirements, 2) Test and Validate requirements with end-users before, during and after development. These considerations are specially important in interactive systems, where the user interaction is very high and user interface is a significant part of the system.
As a result of this weakness, interactive systems developed using such methods can meet all technical requirements, be very robust, and yet be unusable by the end-user. This problem explain a large part of the frequently-observed phenomenon whereby large numbers of change requests to modify the services of an application are made after its deployment.
As a solution to this problem we propose a method for integrating a user interface model, taking into account user needs and requirements, in the software life cycle. Besides, this approach to the development process ensures the quality of delivered applications from the point of view of the end user.'