Effectiveness of a visualisation diagram

State 5 things that make a visualisation diagram effective.

• Can visual what it will look like layout wise and house style of he final product
• Adaptable
• Can get feedback (TA and client)
• Helps the graphic designer and coder
• Has annotations- connotations

How can visualisation diagrams be ineffective

• If annotations are not detailed enough or doesnt expand on connotations/ how it will appeal to the audience
• Structure isnt always clear, would need to be supported by a site map to clearly show structure
• Only shows what product looks like, not much info on how it is interactive especially for a website or app

Structure of evaluation question

• Introduction- state why the document is important in developing stages of making the product
• Effectiveness- Give 5 reasons why the document is effective/useful (support with examples from the brief)
• Ineffective- Give 2-3 reasons of how the document may not be effective/useful
• Conclusion- Overall, xyz is a effective document in development stages of making a xyz

LO4: Storyboards

1. The purpose of a storyboard is to show the Cinemtaographer, Editor and Director how it should look (frame the action,put the scenes together, controls the action) Represent the visuals to support the narrative
2. You would complete the script first because you need to know what the characters are saying so you can write the dailogue on the storyboard, script visualises the storyboard

1. Scene number
2. Timings per shot
3. Basic information about mise en scene (location INT/EXT charcters, action)
4. Camera shot types to be used
5. Camera movements and angles
6. Editing decisions (e.g cut to)
7. Information about use of sound (key dialogue/ SFX/ non diegteic music)
8. Camera types (DSLR, Sony prosumer)
9. Title graphics