In this class you will:
• Learn to work in collaborative teams
• Learn to develop a system that can be applied to large scale, multi-media projects
• Learn to work with prototyping techniques
• Become familiar with fabrication/production techniques
• Gain experience with exhibition installation
.
Learning Outcome
Working with collaborators and addressing established constraints and conditions for the different aspects (“spaces”) of the show, design and complete one aspect of the End of Year show by opening date and de-install immediately following the closing of the show.
Week-by-Week Schedule (in the rough!)
Week 01: 2/07/2012: Determine exhibition goals, audiences, and contexts (spaces).
Week 02: 2/14/2012: Determine conceptual and formal system
2/21/2012: Begin studies for application to different media. Week 03: Review studies and set design directions to be developed; determine different conditions for each media and different types of work)
Week 04: 2/28/2012: Design Development
Week 05: 3/06/2012: Design Development
Week 06: 3/13/2012: Design Development
Week 07: 3/20/2012: Prototyping. Publicity begins.
3/26/2012: Spring Break
Week 08: 4/03/2012: Prototyping
Week 09: 4/10/2012: Fabrication
Week 10: 4/17/2012: Fabrication
Week 11: 4/24/2012: Fabrication
Week 12: 5/01/2012: Gathering work, materials, fabricating components
Week 13: 5/08/2012: Install show
Week 14: 5/15/2012: Install show
Assignments
Weekly, each team will have different tasks to complete.
Class Methodology
Through weekly meetings the class will work towards the development of all exhibition “spaces” — including the curating, exhibition design, exhibition graphics, website, and publicity and wayfinding. Teams will be responsible for each aspect of the show but will work as a class to ensure the show’s success as a whole. In these meetings we will discuss, evaluate, and prototype towards design and fabrication/realization/production.
documentation needs to show in order for me to know that you have achieved these goals:
Your fantasy project shows that you have ideas about and understand ways you might collaborate with another discipline
Your project documentation shows that you understand what another discipline does
Your documentation shows that you also know how to tell the story of what another discipline does.