Back

Sessions 15–16: Research & Design

Racquet Ball Launcher Project — Milestone 1 of 6

divider

The Racquet Ball Launcher Project

Sessions 15–27

What You're Actually Building

Not just "a launcher that goes far."

A team that can predict where their launcher will land — and prove it, live, on Field Test Day.

The Real Deliverable

Distance vs. your chosen variable (pull distance or angle).

The Real Deliverable

Your empirical calibration model is the project — not a working launcher by itself.

Field Test Day (Session 26)

You'll get 3 random target distances.

Using only your own model, in real time, you choose settings that land within margin.

Margin of Error

± 3 yards.

The Arc

SessionsPhase
15–16Research & Design
17–20Build (Iteration 1)
21–23Test & Calibrate
24–25Iterate & Re-calibrate
26Field Test Day
27Reflect & Defend

Your Launcher Uses Bungee Cords

Stretched elastic stores real energy — and releases it suddenly.

Bungee Safety

  • Never stand in the release path, ever — not "just to check something"
  • Inspect every cord for fraying or wear before each use
  • Anchor points get checked before every pull, not just the first one
  • Eye protection any time a cord is under tension
  • Release under control — never just let go at full stretch

Bungee Safety

This is the same hazard category from Session 5 — except this time it's not general shop tooling, it's the actual mechanism you're about to build with.

No team touches a bungee cord in this project until they're certified on this today.

Today: Choose Your Variable

Pull distance or launch angle — your team's choice, unless your instructor assigns it.

Whichever you pick is what your entire calibration model will be built around.

Today: Generate Concepts

Same technique as Session 3:

  1. Sketch 3 genuinely different concepts
  2. Score each in a decision matrix
  3. Choose — with reasons, not a vote

Due by End of Session 16

Design Packet:

  • Concept sketch + decision matrix
  • IV choice + written justification
  • Written test protocol

Why the Protocol Matters

A vague protocol now means a chaotic Test & Calibrate later.

Why the Protocol Matters

Name: what you're varying, how many trials per setting, and how the data becomes a model.

Watch Out For

  • "3 variations on one idea" instead of genuinely different concepts
  • Rushing to build before the protocol is real
  • Picking a variable without a stated reason

Next Up

Build begins (Sessions 17–20).

Bring your Design Packet — you'll be building straight from your concept sketch.

'F' → Fullscreen

divider

Build

Step 1: Bungee Safety Certification

Before anyone on your team touches a bungee cord, watch your instructor's demonstration and confirm you understand all five protocols:

  • Never stand in the release path
  • Inspect every cord for fraying or wear before each use
  • Check anchor points before every pull, not just the first
  • Eye protection any time a cord is under tension
  • Release under control — never just let go at full stretch

This is a hard gate: no team begins Build (Sessions 17–20) without every member certified.


Step 2: Choose Your Independent Variable

Pull distance or launch angle — confirm with your instructor whether this is your team's free choice this year. Whichever you pick, everything downstream (your test protocol, your calibration model, your field-day strategy) is built around it.


Step 3: Generate 3 Concepts + Decision Matrix

Using the exact technique from Session 3: sketch 3 genuinely different launcher concepts, then score them in a decision matrix (Cost / Feasibility / Time / Alignment with your chosen IV) before committing to one.


Step 4: Write Your Test Protocol

State, in writing, all three of these:

  • What you're varying (your IV) and across what range
  • How many trials you'll run per setting
  • How that data becomes a calibration model

You don't need the model yet — just a real plan for building one. A vague protocol will be sent back before Build begins.

divider

Checkpoint

Before Session 16 ends, confirm all of the following:

  • Every team member is certified on bungee cord safety
  • Three genuinely different concepts were sketched — not 3 variations on one idea
  • Your decision matrix has real scores and reasoning, not a pre-decided winner
  • Your IV is chosen and justified in writing
  • Your test protocol names what's varied, trial count, and how data becomes a model
divider

Reflection

Answer the following questions before submitting your work.

  1. Why does this project require a written test protocol before anyone builds anything, instead of just letting teams start building and figure out testing later?
  2. Of the five bungee safety protocols, which one do you think would be easiest to get careless about after a few weeks of routine building? Why?
  3. Session 3 taught you that your first idea is rarely your best one. Did that hold true here — did your team's chosen concept end up being the first one anyone sketched, or a later one?
divider

Submit

Submit your team's Design Packet (concept sketch, decision matrix, IV justification, test protocol) and your individual reflection.

Milestone Complete