http://tc.eserver.org/dir/Design/User-Experience/Specifications A listing of the most recently indexed works about Design and User Experience and Specifications in the field of technical communication. en-us Copyright (c) 2005-08 by the EServer. All rights reserved. tclib-editorial@eserver.org (TC Library Editorial Board) webmaster@eserver.org (Geoffrey Sauer) http://tc.eserver.org/images/newlogo.gif http://tc.eserver.org/dir/Design/User-Experience/Specifications http://tc.eserver.org/35178.html http://tc.eserver.org/35178.html The role of the interaction designer is to specify the interface’s behaviors and elements, so that engineers know what to build and how the product should operate. This documentation is commonly known as a UI specification or UI spec. There are several applications for authoring a UI spec, with wikis being a relatively new tool. However, designers should be aware of a wiki’s benefits and drawbacks for documentation, since UI specs uniquely reflect a project and its context. The documentation needs are often based on the size of the project, launch date, team dynamics, audience, technology, and the product development process. The development process usually plays a major role in how teams interact and how work is completed or delivered, thus, there is a direct relationship between the UI spec and the process the team is using. http://tc.eserver.org/29762.html http://tc.eserver.org/29762.html Creating any system of sufficient complexity requires a diverse team and a dizzying amount of documentation. While these documents do a great job of conveying components of the system, they do not provide an integrated view. This is because each covers different aspects of the system, written by a different author for a different audience. This paper proposes that project teams should create a user experience specification, a document that shows what the system looks like, how it behaves, and how it works. This specification needs to describe the system for all team members, at a useful level of detail, in a form that encourages team members to read it and inviting enough to get them to participate in the design, as well as allow developers to build from.