IAT 235 Lecture Notes - Lecture 6: Gestalt Psychology, Critical Path Method, Dont

34 views2 pages
Experience
Assignment Review:
Make sure you're doing your research. Researching what you want to show, as well as how to show it.
What tools best service that information?
Examples we discussed: bullet graph, spark lines (show vector, high points, low points, end point, margins)
How does tool map to information? How does it map to the criteria? What strategy?
Research tools, play with tools, bend tools
Design is always about innovating for context, consumer. Design right tool for the job.
Refine sketches more! Don't just submit because he said submit. Sketch sketch sketch sketch. Try a lot of
different types of things (horizontal exploration), keep going until you've exhausted all horizontal ideas, then
go back through and explore vertically (drill down on individual ideas)
Visual elements: formal properties: line, shape, colour, size, significance of each?
What does every single one of those things MEAN? If it doesn't have a meaning, throw it out. If it isn't
blatantly obvious, label it.
Have strategy for labeling, unified. Labels another type of information to design.
Organization methods and Gestalt Principles
Good information design draws you in to something as stupid as the potato life cycle!
Other tools:
Pert Sequence Diagram (critical sequence), the steps that CANNOT be left out, alternate paths, indexing
system. Can just show info, but indexing system allows you to discuss it, commit it to memory
Gantt Planning - common in project management, list of dependencies, waterfall, shows causality, shows
simultaneous events, can show critical path and margins
Process diagrams - set of steps, if order, show it
Documenting process
For project: how do people move through physical space? How negotiate through it? How do they imagine
and determine next step?
Qualitative Data
Quantitative (interval, numerical data, data is measured and statistical) vs Qualitative (nominal/ordinal,
descriptive, word/explanations data, data observed)
Shows differences, is descriptive, shows quality of experience, described in words rather than numbers,
something we experience, not capture
Data structures: chronology, spatial (proximity rather than cm, think personal space), hierarchy,
relationships/networks, collections, narrative (story, sequence, process)
Flowcharts: UML
Terminator, process, data(file), manual input, decision - grammar of flow charts! Don't always need to use
standard lexicon, but make it OBVIOUS
Change of lexical key = a change in type. Ex, using all rects means everything is same type
Unlock document

This preview shows half of the first page of the document.
Unlock all 2 pages and 3 million more documents.

Already have an account? Log in

Document Summary

Researching what you want to show, as well as how to show it. Examples we discussed: bullet graph, spark lines (show vector, high points, low points, end point, margins) Design is always about innovating for context, consumer. Try a lot of different types of things (horizontal exploration), keep going until you"ve exhausted all horizontal ideas, then go back through and explore vertically (drill down on individual ideas) If it doesn"t have a meaning, throw it out. Good information design draws you in to something as stupid as the potato life cycle! Pert sequence diagram (critical sequence), the steps that cannot be left out, alternate paths, indexing system. Can just show info, but indexing system allows you to discuss it, commit it to memory. Gantt planning - common in project management, list of dependencies, waterfall, shows causality, shows simultaneous events, can show critical path and margins. Process diagrams - set of steps, if order, show it.

Get access

Grade+
$10 USD/m
Billed $120 USD annually
Homework Help
Class Notes
Textbook Notes
40 Verified Answers
Study Guides
Booster Classes
Class+
$8 USD/m
Billed $96 USD annually
Homework Help
Class Notes
Textbook Notes
30 Verified Answers
Study Guides
Booster Classes