http://tc.eserver.org/authors/Oye,_Phil_and_John_Payne A bibliography of works by Oye, Phil and John Payne 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/Oye,_Phil_and_John_Payne 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.