10 Team Goals for E ff ective Design Specifications Jack Moff e Manager Apps Development – GUI Inmedius, a Boeing Company @jackmoffe | jackmoffe@mac.com designaday.tumblr.com
Welcome message from author
This document is posted to help you gain knowledge. Please leave a comment to let me know what you think about it! Share it to your friends and learn new things together.
Transcript
10Team Goalsfor Effective Design Specifications
Jack Moffett Manager Apps Development – GUI
Inmedius, a Boeing Company
@jackmoffett | [email protected] designaday.tumblr.com
Poor documentation is a source of
unmet expectations
misunderstood requirements
incorrect implementation
unexpected complications
blown estimates
The cup that can only be half-full. by vrogy
CONSISTENCY
Repeating Lines - Project 50/50 (Week 23) by Jason Mrachina
CONSISTENCY
CONSISTENCY
We are all different by Paolo Braiuca
A foolish consistency is the hobgoblin of little minds.Ralph Waldo Emerson
Flexible Flamingo by Jeff S. PhotoArt at HDCanvas.ca
Flexibility
Flexible Flamingo by Jeff S. PhotoArt at HDCanvas.ca
Flexibility
Flexible Flamingo by Jeff S. PhotoArt at HDCanvas.ca
Flexibility
Flexible Flamingo by Jeff S. PhotoArt at HDCanvas.ca
Flexibility
Flexible Flamingo by Jeff S. PhotoArt at HDCanvas.ca
Flexibility
Flexible Flamingo by Jeff S. PhotoArt at HDCanvas.ca
Flexibility
Thoroughness
nested un-whole cube in red oak by Jared Tarbell
Thoroughness
nested un-whole cube in red oak by Jared Tarbell
Thoroughness
nested un-whole cube in red oak by Jared Tarbell
Thoroughness
nested un-whole cube in red oak by Jared Tarbell
Clarity
Clarity
• Proofread (or have someone else do it).
• Develop a common vocabulary.
• Refer to specific UI elements by name.
• When using names, give them consistent typographic treatment.
• Use images.
• Use the language of your readers.
Clarity
• Proofread (or have someone else do it).
• Develop a common vocabulary.
• Refer to specific UI elements by name.
• When using names, give them consistent typographic treatment.
• Use images.
• Use the language of your readers.
Design your document!
Clarity
• Proofread (or have someone else do it).
• Develop a common vocabulary.
• Refer to specific UI elements by name.
• When using names, give them consistent typographic treatment.
• Use images.
• Use the language of your readers.
Design your document!
The Eye by Augusto Serna
Visualitythe quality or state of being visual or visible
The Eye by Augusto Serna
Visualitythe quality or state of being visual or visible
OrganizationLooking for by ilConte
Shareability
Macro of two white straws by Horia Varlan
Shareability
Macro of two white straws by Horia Varlan
Locked Out by Chris Yarzab
inclusiveness
Locked Out by Chris Yarzab
inclusiveness
Developers
Testers
Product Management
Sales & Marketing
Customers
Users
ConclusionYou aren’t creating documentation for its own sake. There are problems your documentation is solving. There are needs being fulfilled.
ConclusionInstitute a process that ensures correctness prior to implementation, during testing, and beyond.
Iteratively evaluate and improve.
ConclusionResponsibly reduce your documentation.
The more you can show, the less you have to describe.
Design documentation for its target audience.
QuestionsConsistency
Flexibility Thoroughness
Correctness Conciseness
Clarity Visuality
Organization Shareability
Inclusiveness
Jack Moffett Manager Apps Development – GUI Inmedius, a Boeing Company
@jackmoffett | [email protected] designaday.tumblr.com
More
Related Documents
