|
|
|
|
|
|
|
HELP | |
|
  $44.99
TRADE PAPER, NEW
Ships in 1 to 3 days
This title in other formats:Communicating Design: Developing Web Site Documentation for Design and Planningby Dan Brown
Synopses & ReviewsPublisher Comments:Most discussion about Web design seems to focus on the creative process, yet turning concept into reality requires a strong set of deliverables — the documentation (concept model, site maps, usability reports, and more) that serves as the primary communication tool between designers and customers. Here at last is a guide devoted to just that topic. Combining quick tips for improving deliverables with in-depth discussions of presentation and risk mitigation techniques, author Dan Brown shows you how to make the documentation you're required to provide into the most efficient communications tool possible. He begins with an introductory section about deliverables and their place in the overall process, and then delves into to the different types of deliverables. From usability reports to project plans, content maps, flow charts, wireframes, site maps, and more, each chapter includes a contents checklist, presentation strategy, maintenance strategy, a description of the development process and the deliverable's impact on the project, and more. Book News Annotation:It's up to the designer to not only do it right but also to let the
client see what's being done, and to capture ideas, track progress,
and make sure everyone is singing from the same page. Consultant
Brown describes the ten basic deliverables as belonging to three
basic types, thereby making it much easier to sort out who gets what
and when. He works in layers with user needs documents (personas,
usability test plans and usability reports), strategy documents
(competitive analyses, concept models, and content inventory) and
finally with design documents (site maps, flow charts, wire frames
and screen designs) on top. The logic of Brown's ideas works well at
a practical as well as theoretical basis, because he shows why user
needs and strategy documents come first, before planners start
playing with all the cool software.
Annotation ©2006 Book News, Inc., Portland, OR (booknews.com) Book News Annotation:It's up to the designer to not only do it right but also to let the
client see what's being done, and to capture ideas, track progress,
and make sure everyone is singing from the same page. Consultant
Brown describes the ten basic deliverables as belonging to three
basic types, thereby making it much easier to sort out who gets what
and when. He works in layers with user needs documents (personas,
usability test plans and usability reports), strategy documents
(competitive analyses, concept models, and content inventory) and
finally with design documents (site maps, flow charts, wire frames
and screen designs) on top. The logic of Brown's ideas works well at
a practical as well as theoretical basis, because he shows why user
needs and strategy documents come first, before planners start
playing with all the cool software.
Annotation ©2006 Book News, Inc., Portland, OR (booknews.com) About the AuthorDan Brown has been practicing information architecture and user experience design since 1994. Through his consulting work in both public and private sectors, he has improved enterprise communications for both Federal and Fortune 500 clients, currently the Federal Communications Commission. Dan writes and speaks frequently on information architecture, and contributed to the inaugural issue of UX Matters, a new online magazine dedicated to user experience design. Dan is very active in the local Washington, DC information architecture community, and serves on the advisory board for the Information Architecture Institute. What Our Readers Are SayingAdd a comment for a chance to win!
Average customer rating based on 1 comment: | ||||||||||||||||||
|
| |||||||||||||||||||
|
|||||||||||||||||||
Don't Miss
