Practices
  Home arrow Practices arrow Page 3 - Creating and Using Storyboards
Dev Shed Forums  
Administration  
AJAX  
Apache  
BrainDump  
DHTML  
Flash  
Java  
JavaScript  
Multimedia  
MySQL  
Oracle  
Perl  
PHP  
Practices  
Python  
Reviews  
Security  
Smartphone Development  
Style-Sheets  
Web Services  
XML  
Zend  
Zope  
Mobile Linux  
App Generation ROI  
IBM® developerWorks  
Forums Sitemap  
E-Commerce Hosting  
Linux Web Hosting  
Managed Hosting  
Small Business Hosting  
VPS Hosting  
Weekly Newsletter

 
Developer Updates  
Free Website Content 
 RSS  Articles
 RSS  Forums
 RSS  All Feeds
Write For Us Get Paid  
Request Media Kit
Contact Us  
Site Map  
Privacy Policy  
Support  
 USERNAME
 
 PASSWORD
 
 
  >>> SIGN UP!  
  Lost Password? 
PRACTICES

Creating and Using Storyboards
By: Tony Leonard
  • Search For More Articles!
  • Disclaimer
  • Author Terms
  • Rating: starstarstarstarstar / 146
    2004-11-15


    Table of Contents:
  • Creating and Using Storyboards
  • What is a Storyboard?
  • Storyboards as Documentation
  • Basic Form
  • Question and Feedback Form
  • How do I Create Storyboards?
  • Automated Storyboard Tools

  • Rate this Article: Poor Best 
      ADD THIS ARTICLE TO:
      error-file:tidyout.log Del.ici.ous error-file:tidyout.log Digg
      error-file:tidyout.log Blink error-file:tidyout.log Simpy
      error-file:tidyout.log Google error-file:tidyout.log Spurl
      error-file:tidyout.log Y! MyWeb error-file:tidyout.log Furl
    Email Me Similar Content When Posted
    Add Developer Shed Article Feed To Your Site
    Email Article To Friend
    Print Version Of Article
    PDF Version Of Article

     
     
    ADVERTISEMENT


    Creating and Using Storyboards - Storyboards as Documentation
    ( Page 3 of 7 )

    In addition to communicating information, storyboards are also the documentation for what you build. If you need to fix, change, or re-do something, you need the storyboards to figure out what was done. I know this is common sense, but when you’re in the throes of production, it’s easy to let things slip. Besides, you designed it, right?  You should be able to tell someone what was done. That may be true for up to a month after the project is over, but not much longer. And what happens if you leave that department, or go to work for another company, or just throw up your hands in disgust and leave the working world for a tropical island? What then?

    For example, I’m working on a project now where I have to take a finished project and reverse engineer it to reproduce it in another authoring tool. There are no storyboards available from the last time it was built.  There’s no list of graphics or interactions or navigation branches. I have to look at the tool screen by screen and make notes about what the screen does. Fortunately, this isn’t a complicated project, but you can imagine that I would have been able to quote a lower cost if the storyboards were available.

    What Makes Up a Good Storyboard?

    For the projects I’ve done, I’ve developed a list of things that made storyboards good for each project. Some of these things worked better than others, depending on the team and the content and the project as a whole. The message here is that what follows worked for some projects, and in fact may work for you, but is by no means an exhaustive list. You should use these elements as guidelines and think through what you may or may not need.

    I use at least seven different “storyboard” forms. They include a basic form, question form, video script, audio script, animation form, and glossary list. I’ll briefly describe each of these and what’s on them.



     
     
    >>> More Practices Articles          >>> More By Tony Leonard
     

       

    PRACTICES ARTICLES

    - More Techniques for Finding Things
    - Finding Things
    - Finishing the System`s Outlines
    - The System in So Many Words
    - Basic Data Types and Calculations
    - What`s the Address? Pointers
    - Design with ArgoUML
    - Pragmatic Guidelines: Diagrams That Work
    - Five-Step UML: OOAD for Short Attention Span...
    - Five-Step UML: OOAD for Short Attention Span...
    - Introducing UML: Object-Oriented Analysis an...
    - Class and Object Diagrams
    - Class Relationships
    - Classes
    - Basic Ideas





    © 2003-2009 by Developer Shed. All rights reserved. DS Cluster 6 Hosted by Hostway
    Stay green...Green IT