 | | | |
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.
View all 2240 works published by STC Proceedings |
Creating a User Experience Specification
http://www.stc.org/ConfProceed/2004/PDFs/0062.pdf
Oye, Phil and John Payne
STC Proceedings
2004
Abstract: 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.
|
|
| |
There are 19 readers currently online: 0 registered users and 19 guests. Register.