The Usability Engineering Lifecycle: A Practitioner's Handbook for User Interface Design
By Deborah J. Mayhew
Chapter 14: Style Guide Development
Chapter 14: Style Guide Development
Purpose
The purpose of this task is to bring together in a single document all previous Requirements Analysis and user interface design work products relevant to a particular product. As you can see in the lifecycle chart at the beginning of this chapter, you actually start developing the contents of the product Style Guide earlier in the lifecycle than is implied by its placement in the order of the chapters in this book. However, this seemed like the best place to stop and describe it, as this is the point at which you would finally complete its contents.
It is useful and important to document the Usability Engineering Lifecycle work products along the way for several reasons:
?
Especially on projects with long development cycles, it is too easy to forget information and design decisions across time unless they are well documented. Also, documentation ensures that information is not lost and tasks don't have to be redone in the common event of staff turnover.
?
Especially on complex projects in which great volumes of requirements analysis information are gathered and many design decisions are made, it is too difficult for designers to keep all this information in mind. They need documentation to which they can constantly refer, making sure all requirements analysis data is actually applied to design, and all design decisions are actually implemented.
?
Especially on projects with large project teams and a lot of division of labor, documentation...
Copyright Morgan Kaufmann Publishers, Inc. 1999 under license agreement with Books24x7