Document & Represent

Ajax_loader_tiny
  • The primary purpose of your Presentations  at NuVu is to describe the creative and technical journey you undertook in developing your project. In this post you will write what you are going to say, slide by slide, for your Final Post.   During your presentation you will not read from this script. It is here to help you frame your presentation and give insight to website visitors.

    Feel free to organize the post by slides in the presentation. The example below if for a build studio but the concept holds for a film/animation studio.

    Slide 1: Write out your title and tagline.
    Slide 2: Describe your Problem/Solution or Thesis
    Slide 3: SAY NOTHING!
    Slide 4: Explain your functional diagram - how is your your project used or function in the world.
    Slide(s) 5: Walk through each of the final images and describe the overall use/design of project.
    Slide(s) 6: Discuss how each precedent inspired/informed your design.
    Slide(s) 7: Discuss your initial sketches - how they arose from your brainstorming and how they informed the start of your design process.
    Slide(s) 8: Discuss each iteration - Briefly describe major design changes and how they effected the overall project arc and design.
    Slide(s) 9: Walk through the construction/electronics diagrams to describe the technical aspects of the final design fabrication and underlying structure or electronics functionality.
    Slide(s) 10: Discuss the final prototype, what was a success, and where your project might go from here.

    Your post will:

    • Introduce the general context of your project
    • Present the thesis or design problem and how you approached the solution
    • Using precedents, begin to tell the story of the genesis of your actual design.
    • Describe the overall design concept.
    • Delve deeply into the heart of the design process through a description of major design iterations.
    • Thoroughly describe the final design technically and functionally through the reference to your diagrams.
    • Walk through the final images, discussing how everything came together.
    • Discuss the conceptual and technical challenges you faced. These should be broad view issues, not hyper-specific technical issues.
    • Your vision for where your project can go.
  • The Final Post:

    This post showcases your final design through two parts:

    1. An Abstract that shows the final project a concise series of images and diagrams. Its purpose is to allow a viewer or visitor to understand the project in its entirety in a few brief minutes. It is mainly concerned with the What of your project but must contain an overview of the Why and your entire narrative arc. This part of your post will be used in your 2-3 minute NuVu community presentation and will likely be the portion reporters, colleges, and family will see first. 
    2. The Process which tells the comprehensive story of how your idea was born, developed, and manifested. The arc of the story should encompass the, How of your project in a compelling narrative. It showcases your design process including your brainstorming, each of your iterations, and your final prototype. It allows the viewer to delve deeply into your process. This post will be used in your review presentation at the end of the session. 

    The title of this post must be The name of your project..

    Slides:

    The Final post has 14-19 slides. Every slide MUST have a title. Captions are a good idea as well.

    ABSTRACT PORTION 

     

    Slides:

    The Process post has 111-15 slides. Every slide MUST have a title. Captions are a good idea as well. Please download the slide storyboard to lay this out.

    1. TITLE WITH TAGLINE (1 Slide): This is a TEXT ONLY slide that gives your project name and pithy blurb describing the project. Both the name and the tagline should draw a viewer in. Use the design template for this slide.

    Examples:

    • Night of NuVu - When Zombies Attack NuVu Prom, Horror Ensues
    • T is for Talent - A Day in the Life of an MBTA Busker
    • Seed to Soup - An Aminamed Fable of Food and Hope

    2. CONTEXT IMAGE: (1 slide) This is a single image that shows a clear precedent or evocative image. This image helps set up the why in a compelling way, sets the stage for your narrative, and will help frame the entire presentation. No Text.

    3. THESIS STATEMENT  (1 Slide) : This is a TEXT ONLY slide. In consultation with your coach you will create a Thesis Statement o. Use the design template for this slide. Use the design template for this slide.

    Thesis: Thesis statements are appropriate for a conceptual project with a nuanced or complex generative narrative. Your thesis states the Why and How clearly and succinctly in 1-3 sentences.

    • Examples:
      • The Cocoon:  A wearable sculpture that explores the concept of transformations and death. The Cocoon explores the spiritual journey beyond the human experience; what it means to be human, how wonder effects us, and the concept of what happens after death.
      • Body Accordion: A musical prosthetic that translates the wearer’s body movements into a dynamic multimedia performance. The Body Accordion converts flex sensor input to sound through Arduino, MaxMSP, and Ableton Live. 
      • Seed to Soup Animation: A whimsical animation about the slow food movement. Seed to Soup showcases a holistic method of cooking. From garden, to kitchen, to dinner table.
      • Antlers: A wearable sculpture inspired by antlers found in the deer and antelope family. "Antlers" explores the comparison between armor and attraction. 

    4. FINAL STILLS (3 Slides) - These slides should have still images of the final project. Choose a wide variety of images that show the project from different perspectives. 

    5. SHOW FILM OR ANIMATION - Pause in your presentation to do this. Video/Book/Etc is a separate post.

    6. PRECEDENTS (1 Slide minimum -2 Slides maximum) - Stills or GIFS. Precedents are any projects that inspired you creatively or gave you technical guidance. No Text.

    • 1 Slide - Conceptual Precedent
    • 1 Slide - Technical Precedent

    7. INITIAL STORYBOARD (1 slide):  A scan of your original storyboard. If your original is illegible or hard to understand, you should create a cleaner version. Preferably in marker pen.Make sure the storyboard is in the right orientation. You can include 2 boards on 1 slide. No Text.

    8. PRODUCTION DECISIONS (1 slide minimum, 2 slides maximum): These slides show the changes you made after your initial edits. These should NOT include screenshot of your editing software. You can choose stills, a sketch of camera angles, or other representations of decisions you made. The caption should clearly explain the decisions and their ramifications. No Text.

    9. ANALYSIS: (2 slides minimum, 3 slides maximum): The next part of the process post retrospectively express and explain your idea and process. They should include:

    • Final Storyboard :  A storyboard of the final cut of the film. Work in a graphics software and maintain a high production value. ALL film and animation projects should have this analysis.
    • Technical Analysis: A diagram showing your technical workflow. This should not be a screenshot of your editing software. ALL film and animation projects should have this analysis.
    • Character/Scene Development: If appropriate, include asset development (such as character or scene) sketches (primarily for animation studios.)

    10. FINAL IMAGE: (1 slides) The last slide should have representative still images of the final project. 

  • You should already have written this post! 
    This post should be copied from the final revision in the Writing tab of your project. Feel free to use your own style or voice in The Brief.

    Title the post "Brief".

    The Brief should have a strong narrative that ties together the Why, How and What of your project through clear, cogent writing. Tell the story of how your idea was born, developed, and manifest. 

    Create 1 post titled “The Brief” with text that includes the following 2 items:

    1. A 1-2 sentence project description for your transcript. This will serve as the basis of the Project Description that appears in your transcript. This description should not include the name of the project and should be written in the third person. On Thursday you and your teammates will add this under project settings.
      examples:
       Night Light Blankie: A child's sensory blanket that provides comfort and privacy in the high stress environment of the hospital using weight, textures, and light. The blanket transforms into a mini light up fort over a child’s head.
      Cocoon is a shroud that explores human spirituality and the concept of life after death through the use of repetitive religious iconography. Composed of over 300 pieces of laser cut balsa wood lined with space tape, the icons are arranged using a mathematical strange attractor.
    2. A 1-2 paragraph brief for your project based on the description below. This text will be edited by the NuVu writing coach. You will have the opportunity to revise this text before the final presentation. The primary purpose of The Brief is to explain, entice, and convince the reader that your project is amazing and important. Imagine your project on display in the Museum of Modern Art. The Brief is hanging on the wall next to your work. In 1-2 paragraphs, a viewer should understand what your project is, why it exists, and how you made it. More importantly, the viewer should be interested and care. You will draw them into your project through a compelling narrative.

      Things to think about:
      • The what is a clear statement of the thesis or problem+solution.
      • The why explains how your project changes the world. It is the reason your project exists – what social issue is it engaging, who is your project helping, how does the project change the world, and what important social, intellectual, or technical questions does it raise? The scope of the why can vary widely.
      • The how briefly explains what technical prowess, innovative methods, or cool materials you used in your solution.
      • Think of the reader - it is good to imagine that a college admissions officer AND a potential employer in the field of your design should both be able to understand and be excited by the project based on your writing.
      • Write in the Third person in an explanatory fashion. Resist using I, WE, OUR and focus on describing the work.

        Here is an example from Penelope the Pain-O-Monster:

        Pediatricians and other doctors find it challenging to collect accurate self reported information from children about their level of pain due to lack of communication skills, fear, anxiety, and discomfort. Traditional 1-10 pain scales do not fully address these issues, often leading to uncomfortable children and inaccurate symptom information. Penelope the Pain-O-Monster is a cute plush toy that uses integrated pressure sensors to allow children to express their source and level of pain through play.    

        Our previous project, The EmoOwl, helped children with autism to express themselves by translating motion into color. As we sought to expand our children’s health menagerie, we thought about making a different stuffed animal to help kids in hospitals. We quickly realized that the pain charts that patients used to express their pain could be made more interactive and easier for a child to use. We read that playing with stuffed animals can take the children’s mind off the pain so we created an additional “Fun” mode to distraction from pain and anxiety. The handcrafted stuffed animal uses force sensors in different body parts that light up from blue to red depending on how hard they are pushed to show the child’s pain level. It is our hope that Penelope will help sick children feel safer while providing more useful information to care providers. We anticipate that Penelope and the EmOwl will soon have many more friends to help improve healthcare for kids.
  • The Final Post:

    This post showcases your final design through two parts:

    1. An Abstract that shows the final project a concise series of images and diagrams. Its purpose is to allow a viewer or visitor to understand the project in its entirety in a few brief minutes. It is mainly concerned with the What of your project but must contain an overview of the Why and your entire narrative arc. This part of your post will be used in your 2-3 minute NuVu community presentation and will likely be the portion reporters, colleges, and family will see first. 
    2. The Process which tells the comprehensive story of how your idea was born, developed, and manifested. The arc of the story should encompass the, How of your project in a compelling narrative. It showcases your design process including your brainstorming, each of your iterations, and your final prototype. It allows the viewer to delve deeply into your process. This post will be used in your review presentation at the end of the session. 

    The title of this post must be The name of your project. 

    Slides:

    The Final post has 15-20 slides. Every slide MUST have a title. Captions are a good idea as well.

    ABSTRACT PORTION
    I this section you are showing the main concept and design of the project. The abstract is an overview meant to excite the viewer. You should not plan to describe the entire project in this section.

    1. TITLE WITH TAGLINE (1 Slide): This slides shows a crisp, clear final image and the title of your project. with a pithy blurb describing the project. The image, name, and tagline should draw a viewer in. 

    Examples:

    • The Fruit - A line following, light tracking robot
    • Segmented Vehicle - A vehicle that conforms to the landscape
    • Cacoon - Wearable sculpture exploring the concept of transformation and death

    2. CONTEXT IMAGE: (1 slide) This is a single image that shows a clear precedent or evocative image. This image helps set up the why in a compelling way, sets the stage for your narrative, and will help frame the entire presentation. The caption of this slide (set with the Edit Captions button when editing your post) should be the text of the Thesis Statement/Problem & Solution. You will read these while presenting this slide. No Text on the slide.

    3. THESIS STATEMENT / PROBLEM & SOLUTION SLIDE (1 Slide) : This is a TEXT ONLY slide for visitors to your portfolio. In consultation with your coach you will either create a Thesis Statement or state the Problem/Solution. You will skip past this slide in the presentation as you will have read the content in the Context Image.

    Problem/Solution: This works best for a project with a clear problem that leads to a describable physical solution.

    This slide answers the questions:

    • What is the problem I am trying to Solve? This is likely different for each project in a studio. Be clear and use the problem to set up the narrative for your presentation.
      • Example: The Problem: Design a vehicle for a mountainous world with difficult terrain to traverse.
    • How did I solve it?. This is your 1 sentence project description with an optional additional 1-2 sentences. 
      • Example: The Solution: A segmented vehicle with a universal joint system that handles mountainous terrain by conforming to the landscape.

    Thesis: Thesis statements are appropriate for a conceptual project with a nuanced or complex generative narrative. Your thesis states the Why and How clearly and succinctly in 1-3 sentences.

    • Examples:
      • The Cocoon:  A wearable sculpture that explores the concept of transformations and death. The Cocoon explores the spiritual journey beyond the human experience; what it means to be human, how wonder effects us, and the concept of what happens after death.
      • Body Accordion: A musical prosthetic that translates the wearer’s body movements into a dynamic multimedia performance. The Body Accordion converts flex sensor input to sound through Arduino, MaxMSP, and Ableton Live. 
      • Seed to Soup Animation: A whimsical animation about the slow food movement. Seed to Soup showcases a holistic method of cooking. From garden, to kitchen, to dinner table.
      • Antlers: A wearable sculpture inspired by antlers found in the deer and antelope family. "Antlers" explores the comparison between armor and attraction. 

    4. FUNCTIONAL DIAGRAM: A diagram showing some aspect of the functionality. These can include:

    • How one uses or interacts with the project
    • The overall behavior of the project over time
    • For a complex interactive project, this can be a clear diagram of the software behavior\

    5. FINAL IMAGE: (3 slides) The last slides should have an image of the final project. These images should be taken in the photo booth, cropped, and adjusted for contrast, brightness, etc. You can also use an image In-Use. Consider using a GIF to show how the project works. You will NOT describe the whole project here, simply show the completed project before going onto the Process. 

    PROCESS PORTION

    6. PRECEDENT SLIDES (2 slides minimum, 3 slides maximum):  Precedents are any projects that inspired you creatively or gave you technical guidance. No Text.

    • 1 Slide - Conceptual Precedent
    • 1 Slide - Technical Precedent
    • 1 Slide - Additional Precedent

    7. INITIAL SKETCHES/CONCEPT DIAGRAM (1 slide minimum, 2 slides maximum): These slides show your initial, generative ideas in sketch form. You can think of this as a sketch of the big idea, it is the chief organizing thought or decision behind the design presented in the form of a basic sketch or diagram. If you do not have a clear concept sketch it is fine to make one after the fact. These should clean, clear drawings. No Text.

    8. ITERATIONS: (3 slides minimum, 5 slides maximum): The next part of the process post are the iterations you documented in your daily posts. Explain your design decisions and how your project changed at each step.

    • For build studios, choose 3-5 representative iterations of your project with 1 slides per iteration. The images should show clear, major design changes. 
    • For digital or graphics studios, have a slide for each important design decision. Generally it is best to avoid screen shots. These could include:
      • A storyboard slide
      • A slide with multiple images showing graphical character development.
      • Stylistic explorations

    9. DIAGRAMS: (1 slides minimum) Diagrams of the final project.

    Build studios will need at least 1-2 additional diagrams:

    • Construction Diagram:  A diagram offering insight on how the project is put together
      • Ideally, this will be an exploded axonometric
      • At minimum this can be a labeled disassembled photo  
    • Electronics Diagram: A circuit schematic showing project inputs, outputs, and architecture.

    Digital studios should have a diagram of the storyboard and flow of the project.

    10. ADDITIONAL FINAL IMAGES: (3 slides minimum, 5 slides maximum) Additional final images showing the culmination of your process. You should include:

    • 2-3 Images in the Booth. Make sure they are cropped, adjusted, and look great.
    • 1-2 Images in Use

     

  • Your portfolio tab is the part of your project viewable to the world. This is where you will present your work to your coaches and peers for both the in-depth reviews and the NuVu community presentations. This is also what family, friends, colleges, the media, and everyone outside of NuVu will see. It is the record of your work and must stand alone, telling a compelling story of your project.

    Portfolio pages have 3-4 posts in this order:

    1. The Final Post: This post's privacy is set to Everyone. This post showcases your final design through two parts:
      1. An Abstract that shows the final project a concise series of images and diagrams. Its purpose is to allow a viewer or visitor to understand the project in its entirety in a few brief minutes. It is mainly concerned with the What of your project but must contain an overview of the Why and your entire narrative arc. This part of your post will be used in your 2-3 minute NuVu community presentation and will likely be the portion reporters, colleges, and family will see first. 
      2. The process which tells the comprehensive story of how your idea was born, developed, and manifested. The arc of the story should encompass the, How of your project in a compelling narrative. It showcases your design process including your brainstorming, each of your iterations, and your final prototype. It allows the viewer to delve deeply into your process. This post will be used in your review presentation at the end of the session. 
    2. Optional Video: This post's privacy is set to Everyone. A video showing the interactive functionality of your project. The title of this post will be Video.
    3. The Brief: These posts' privacy are set to Everyone.Each Student in the group will post their FINAL revised Brief writing assignment in the Portfolio Tab and title it "Brief".
    4. Presentation Script: This post's privacy is set to School. Each group will post their script for there presentation. This post will be used to prepare for and practice your presentation. This post should be titled "Presentation Script" and should not be made public.

     

    After reading this post and completing your Portfolio Tab, you must make sure you have done the following:

  • The Project Description is  1-2 sentence project description that appears in your transcript. 

    It should be:

    1-2 Sentences (written in the third person) that clearly and objectively identifies the project and its use. Do NOT include the name of the project in the description. This should be your clearest, best and most concise writing as it will be seen by colleges, your parents, and your home school. Eventually, it will also appear under the project title for all the world to see.

    Samples:

    • A portable heated IV for extreme climate situation and/or high altitude climbers suffering from hypothermia or dehydration.
    • A sculptural device that helps users practice the slow movement associated with Tai Chi by incorporating speed sensors into lit wooden dodecahedrons and leading the practitioner through a formal sequence.    

    To edit the Description:

    • Click on the gear next to your Project Name
    • Scroll down to "Description for Transcript"
    • Enter the description
    • Click "Save"
  • Our world is mountainous with difficult terrain to traverse. The ‘Segmented Mountain Climber’ is able to deftly maneuver up and down the steep mountainsides, and over their sharp peaks. Its Whegs, half wheel half legs, are able to climb over both small rocks and large boulders. It can also quickly reverse, turn and is able to continue movement even if flipped upside down. 

    Our original idea was a mountainous world with difficult terrain to traverse. We started by brainstorming many different models that could help climb mountains. We decided on a segmented car which could work best in a mountainous situation by conforming to the landscape. It’s called ‘Segmented Mountain Climber’.

         During the first few days, we thought of various shapes for the vehicle, drawing inspiration from existing creations including roller coasters, snakes and trains. Then we brainstormed various designs for the wheels, including tank treads, legs, many small wheels, and large powered wheels.

         In order to better visualize the connections and turning of the segments, we made our first prototype of the large-wheeled model. In essence, it was just a trio of cardboard boxes tied together with string, with an axle and pair of wheels through each segment. However, some clear problems came up: the connection was not sturdy enough, and the wheels failed to rotate. We discussed at length how to incorporate the right wheels and connectors into our design. We started looking at other possible wheel choices, and then we settled on wegs. A weg is essentially a spoked wheel with the rim removed. Deriving its name from the words "wheel" and "leg," it could use circular motion, but with legs. Compared to traditional wheels, they could climb over obstructions and had superior grip. We also decided to replace the strings. At first, we had considered ball joints by virtue of their versatility, however we chose to nix the ball joints in favor of universal joints, because they could be better incorporated into the segments. Universal joints are basically two axles intersecting at a point, offering flexibility in two dimensions. Furthermore, the ability to transfer torque is exclusive to universal joints, so they could prevent any one segment from falling over. 

        Taking these considerations into account, we replaced the string and wheels on our prototype with universal joints and wegs. Upon finishing, we realized that the wegs in the prototype had the right structure but would not rotate because of the material (cardboard), the number of legs (4), and the structure of the foot. We decided that a 6-legged wooden weg would work better, and we redesigned the shape of the foot to include rubber that could provide traction. Another problem was the turning, we considered models such as rack-and-pinion, which was too delicate and complicated, and exploiting right-and-left rotation differences, which wouldn't work as well in a multi-car design such as ours. We decided on using a servo to rotate the first compartment relative to the others, turning the rest in due course. We didn't know, however, how we could incorporate the servo into the overall design. We decided that the joints would be included into the design of the car segments, and the servo would be attached to the foremost universal joint via a 3D-printed attachment. Unfortunately, a problem inherent to servos was the elimination of one of the two axes of rotation; as a result, the first and second compartments would always stay firm on uneven ground.

    Finally, after considering all these issues, we crafted the final product, learning from our previous errors. We used wood, which is much sturdier than cardboard; we used wegs, capable of scaling obstacles, and we used a servo to turn and manipulate the vehicle. We connected the motors and servo to an Arduino controlled by a remote. Overall, we had many separate design challenges; in the end, however, all the components came together to form a polished final product.

  • next