Abstract model of usage-centered design methods used tend to keep things simple, encourage the use of generic rather than specific concepts to think. Carried out repeatedly simplification and generalization can make the model generated from the model and interface design trend in its most essential core. Developers once again revise their previous work, simplify it to make it more versatile, and finally develop smaller, simpler system, while keeping system complexity and cost does not increase, it is possible to provide the user more value. Simplification and generalization is a link between the use of each model centered design process interrelated. The real goal is to design software systems to build better and more economical.
Usage-centered design software availability is committed to a set of coordinated activities. These activities can be generally thought of as building blocks used in the game, the game might be a metaphor Naduominuo domino these activities to be assembled in different ways to constitute a path from concept to finished software. Like dominoes, there are numerous logic requirements of certain components (i.e., some activity) assembled together in a particular order various possible order. In the waterfall model, the whole process is divided into a series of steps or phases of execution order. The usage-centered design is a concurrent engineering process, separate from each other and independent of the activities performed in parallel where possible. Concurrent engineering methods have been successfully applied in modern design, engineering, manufacturing and construction in many areas, in order to more quickly and efficiently produce a perfect product. Concurrent engineering while developing a variety of models, description and subsystems. When the result of the work is substantially independent of each other, their development can be carried out by an independent, concurrent activities; when the result of the work is substantially interrelated, it is necessary to coordinate the activities of concurrently active communication by means of some form of . Usage-centered design activities has its own focus and purpose. The line between activities is not always clear, which means that activities can be more or less overlap, and often performed in parallel.
Experienced designers may in fact be developed simultaneously in concurrent activity task model and content model, but should first focus on the nature and structure of the work, and then adjust the user interface according to operating conditions and constraints when it comes to design details, in order to get good design. It should be the task of the organization as a primary factor in determining the interface architecture, and the operating environment in the second place, the only way to get good results. Many user interface design methods are standard user interface or from the beginning of the style guide, or the first to develop such a standard, or in accordance with such a standard has been designed to start. What is not clear what to do or need to standardize the time, attempted to set standards for what is illogical. We should proceed to follow the appropriate standards and style guides from the understanding of the work and design requirements. In practice, some of the standard and style definitions may begin before a project has been in existence. The user interface standards and style guides must continue to exert influence on the design, but it also must review and modify itself according to the results of the modeling and design activities.
The ultimate goal of software development is to get a working system available, so the design and improvement activities must eventually lead to the construction and testing of the operation of the system. Users play an important role in the usage-centered design, the most central location and even though they are not in the design process. A number of activities on behalf of the user or users involved in the design process can take a hybrid approach, or let users and developers to work together, or allow users to review the work of developers and provide feedback. Therefore, this process should be characterized by user participation, rather than user-centric.