Here are a few thoughts: Models are very different than patterns. Cognitively, a pattern is a recurring phenomenon, widely used and accepted for representation of common or similar visual/non-visual elements. A model on the other hand can be a set of rules and guidance that can help in the creation of a pattern or a group of patterns. Typically, the patterns become patterns only when they are in use by many users. Otherwise it is just another piece of code or interface. Also a model can be refined only when there is a proper flow of information from the usage of the patterns. So in effect each one feeds the other for mutual symbiotic growth, but are not the same.
For your query on design model, there are many process steps, but as a concise one, the only one that I had seen in the past was called the usability maturity model. The link is here: http://www.processforusability.co.uk/Usability_test/html/umm.html Hope this helps. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Posted from the new ixda.org http://www.ixda.org/discuss?post=43747 ________________________________________________________________ Welcome to the Interaction Design Association (IxDA)! To post to this list ....... [email protected] Unsubscribe ................ http://www.ixda.org/unsubscribe List Guidelines ............ http://www.ixda.org/guidelines List Help .................. http://www.ixda.org/help
