Week 9

Date 11/2

• Topic: Capstone design project

Pre-class:

• • • Watch the video “What is a Capstone Project?”
    • Why Capstone design project?

 In-class:

• Arduino Project Research

  • Pre-class activity in Week 8
  • In group, share what you researched on Arduino projects in the pre-class. Each member should present three projects. List the project name below.
  • Random grouping: Random Group Generator
    • Group 1: Richard, Lowman, Micheal, Ronaldo
      • https://docs.google.com/document/d/1iVFdiMRYxHVBx4cOtwqR2XoFwIE1gTACtVZ2GwiU-tc/edit?usp=sharing
    • Group 2: Alex, Dennis, Islam, Saralynn
      • https://docs.google.com/document/d/1lAbeXuQ7GywjjEfwDAv_gR-lC58CHFkL_DGu6eiaVwo/edit
    • Group 3: Jhorvi, Victor, Esau, Raul
      • https://docs.google.com/document/d/1un_8tmkM1nTvTMlUKLmAFiHvjRplUlwfrCOccj6j2oo/edit?usp=sharing
  • Select three project in the group, and analyze using the Input-Process-Output model.
    • Input: How does the project collect input? Which sensor(s) does the project use?
    • Process: How do the input date process? Write pseudo codes for the project.
    • Output: How does Arduino react to the input?

• Capstone Project.

  • Discuss below topics.
    • What is capstone project?
  • Team building
    • Grouping, Randomizing: Random Team Generator
    • Team Building Game, Aliens have landed
      • This team game needs a bit of your imagination
      • Scenario: aliens have finally landed on Earth near your home. They don’t speak English. So, each team must pick or draw three symbols or pictures to best describe your team.
      • Time: 10 minutes. Digitize the symbols by taking pictures or downloading images on your computer.
  • Capstone Project Brief

  • Download (DOCX, 21KB)

  • Report Format for Capstone Design
    • Cover Page: Title, Team members and number, Course Name, Date
    • Table of Contents
    • Abstract
    • Introduction
    • Problem Formulation
    • Impact of the Project
    • Ideations
    • Design Strategy (Include options considered, ones selected, and alternatives for risk reduction)
    • Division of tasks among team members
    • Time line showing dependencies and major testable milestones
    • Cost (Show total cost and cost to project in separate columns if different, eg. because of borrowed or donated items)
    • Conclusion
    • Appendices (eg. catalog copies, spec sheets, etc.)
    • References
  • Your milestones
    • Problem Identification: Due Nov 15 (Fri)
    • Solution Exploration: Due Nov 22 (Fri)
    • Final Submission: Due Dec 7 (Mon)
    • Final Presentation: Dec 14 (Mon)
  • Define the problem
    • Brainstorming (Rules as Suggested by Osborn, 1953))
      • 1. Go for Quantity: Come up with as many ideas as possible.
      • 2. Avoid Criticism: Verbal and nonverbal criticisms should be suspended until the evaluation process begins (after brainstorming).
      • 3. Welcome Unusual Idea: The crazier the better; you never know where the train of thought might take you.
      • 4. Combine and Improve: The idea that “1+1=3” means that combinations of ideas can lead to new and better ones.
    •  Questions
      • What is the problem or need?
      • Who has the problem or need?
      • Why is it important to solve?
    • Mind Mapping
      • Mind mapping refers to a technique that designers and engineers use to express and generate ideas. All that mind mapping really is, however, is a way to get all of the ideas in your head down onto paper. There is no right or wrong way to mind map. It is simply a visual representation of the thoughts in your head, and it often looks like organized chaos.
  • Research techniques
    • Case studies: in-depth investigations of a single individual, a group, or event. There is no right or wrong method but there are some basic roles of developing case studies.
    • Interviews: conduct interviews with experts in the field on a specific topic. There is are general guidelines for conducting research interview
    • Product Analysis: find a product that has the similar functions for your problem. Analyze if the product needs any improvements.