S

STEM Teacher Leadership Program (STLP)
Honeywell Student STEM Challenge
Project Overview
Your names and grades: Madison Williams, Caleal Truitt, Jamarcus Weaver, Namdi Nantambu, Charity Johnson
Your project’s title S.B.A.N.D. Device
Your teacher’s name: Mrs. Mathieu Your school: Arabia Mountain High School
Your project summary: (A short, ~5 sentence overview. To be completed AFTER you complete your project.)
The goal of the project is to aid those who experience disaster. Our project is going to be based on alerting home
In partnership with Honeywell and the GA Tech Center for Education Integrating Science, Mathematics & Computing
(CEISMC)
https://www.ceismc.gatech.edu/community/stlp
owners of natural disasters as well as burglars. The device that we are designing is similar to the alarm system Ring yet
it has a different purpose. The product is constructed to identify any types of natural disasters. This applies to
hurricanes, tornadoes, typhoons, etc. During this time, burglars are common as well. THe second serving purpose of
our product is to alert and scare burglars if they try to break into vacated homes. When the alert is triggered, a silent
alarm will be sent to the police as well as the owners of the home. THe sole purpose is to scare the burglar so that they
leave. If they do not, they would have been caught on camera already so they would hopefully still be caught.
Define the Problem

Guide
Before you even begin to work on your project, it’s important to first ask a few questions to guide your work. On the next page, you’ll
answer the following questions in order to develop a problem statement.
1. First, think about why there is a need for your project’s solution. What would happen if the problem wasn’t addressed? What
is the impact of the problem?
(CEISMC)
2. Second, think about the audience affected by the problem and your solution. Are there any particular traits of your audience
you should consider? Can your project’s solution be more inclusive by considering other audiences with different abilities or
challenges?
3. Third, think about if there are any particular constraints or specifications your solution must adhere to. These can be things
like size, timing, cost, or any other factor that puts a limit on possible solutions. Your constraints or specifications may be
given to you in a prompt, or they may be considerations or goals in your design that you want to follow yourself.
Finally, use your thoughts on all of the above to create a problem statement. A problem statement is a short (one to a few
sentences) description of the problem which includes the need, audience, and any constraints or specifications. A problem
statement is specific. For instance:
● “Build a better mousetrap” is not a sufficient problem statement. It addresses a challenge, but none of the items above.
● “John’s house is infested with mice that only eat oranges. Design a mousetrap that can trap mice with oranges using only
supplies from John’s house before his friends arrive this weekend.” is a much better problem statement as it addresses the
need, audience, and design constraints such as supplies and timing.
(CEISMC)
Define the Problem

NeedThere is a need for my problem’s solution because it can help people prepare their homes in order to
prevent damage. They would also be alerted of burglars if someone were to enter their home while they
were away.
Audience: The audience would be positively affected because if they were alerted of the disasters, they
could prepare their home. They could also catch potential burglars with the use of our device.
Constraints or Specifications: (Number each below)

● Multiple well hidden cameras
● As soon as an unidentified person enters the home, begin recording
● Make them battery operated in the event of a power outage
● Cost of the cameras with night vision to clearly depict faces
(CEISMC)
Problem Statement: The problem is that this device focuses to solve is preparation of homes regarding
natural disasters and possible burglaries during this time.
Brainstorm & Evaluate Solutions

Guide
Before you get too committed to one way of solving a problem, it’s important to consider alternatives and get feedback. In fields
like robotics, this may help you consider ways to reduce time and material costs. Even in computer science design, you might find
that one way of approaching the problem gets you the same result for less code!
Many designers review their brainstormed solutions by placing them on a chart to compare their pros and cons. These charts
often compare things like:
● Time and material costs
● How well the solution meets the problem’s constraints/specifications
● If there are any major unknowns or difficulties with this approach
● Safety
● If there is any particular skill required
● ...and any other items relevant to the project.
To make comparing these different concerns easier, often a “decision matrix” is used. A decision matrix is a chart in which each
approach is scored by how well the approach meets those concerns. The scores can then be tallied to see which approach won the
most points.
(CEISMC)
On the next page, you’ll be asked to make your own decision matrix. For each row, write a short description of each of your
brainstormed approaches and then put a score in each column using the following metric:
1 = Poor, 2 = Fair, 3 = Excellent
Tally up the scores in the last column to help you pick your approach (the higher the number the better). Duplicate the page as
needed if you have more ideas. Finally, use the “Get Feedback” page to share your best approach with others and note the results!
(CEISMC)

Decision Matrix
Short description of approach Quick to Little Meets Little Total

make Resource problem Technical Score
Cost constraints Difficulty (higher is better)
Example: Plexiglass city model that uses pressure sensors to detect “pedestrians” (marbles) that
move through its streets and use LED lights to direct walking traffic flow 2 1 3 2 8
4 4 4 4 16
1) Set up a camera system and trigger system both inside and outside of homes in order to
alert families when they are away of natural disasters on the way as well as
potential/real life burglars.
2 1 4 1 8
2) Set up storm trackers on the roof in order to alert families of natural disasters that are
on the way. Set up trip wires inside the house to trigger silent alarms and lights.
1 1 3 2 7
3) Set up motion sensors around the perimeter of the house.
(CEISMC)

Get Feedback
Suggestions made: New ideas given:

- Night vision cameras - Set up trip wires
- Loud speakers or something that will give off a - Set up motion sensors outside of home around
loud sound when triggered the perimeter
- Cameras that can depict the situation outside
as well as meters to determine the weather
situation(outside)
(CEISMC)
Concerns raised: Things others liked:

- Will the faces of criminals be visualized enough - Cameras present to catch others in the act
to catch them - Alert to scare burglars
- If a house destroyed, and/or another house is - Alert police as well as the home owners
robbed, will and how will the information be
recovered
Prototype
Guide
Before creating the final product, many designers (especially in engineering) build what is called a “prototype.” A prototype is an
early sample or model of the final product used to test or learn from before making the final product. Prototypes are used to help test
a solution before committing the time and materials needed for the final product. Prototypes often have the following characteristics
compared to the final product:
● Are simpler
● Made of cheaper materials
● Not decorated or as well-polished
● Easier to work with
● Sometimes smaller or reduced in capacity
(CEISMC)
For instance, in computer science this may be a simplified, shorthand version of a particular program that accomplishes most of the
program’s goals, but to a lesser extent. In engineering, this might be a smaller, more cheaply built version of a robot.
Now that you’ve decided on the intended solution to your problem, it’s time to make a prototype. Your prototype should help you
learn about the characteristics of your design solution and be testable.
On the next two pages, briefly describe the approach or solution you chose from the previous brainstorming steps and why you
chose it. Answer the planning questions about your prototype and then, in the “diagram/explanation” section, draw and label the main
components and capabilities of the prototype you will create. If your project consists mostly of code, you can draw a flow-chart of the
code’s logic. Be sure to write some short explanations of anything not obvious from the drawing!
Additional resource: Prototyping Toolkit

Attach an additional page if you need more space.
Prototype
(Remember: The total cost for all prototyping AND your final design should not exceed $30. Plan ahead!)
Chosen solution/approach and reasoning:

The solution in which we chose was the idea to set up cameras and sensors inside and outside of homes in
order to determine possible burglars and natural disasters. We chose this solution because it would be the
most effective in providing solutions to our problem(s).
What inputs/sensors are there?
(CEISMC)
The inputs will be the information, such as the faces and data that the sensors pick up.
What outputs are there?

The outputs will be the sounds and lights that the device gives off when the alarm is triggered; it is clear that an unidentified
person has entered the home and has not turned off the alarm system.
What processing will your project do?

The product will process pictures as well as weather conditions to determine the situation and successfully transmit the
information to homeowners.
Will it store any data, and if so, what?

The device will have to save weather conditions in order for families to determine common weather conditions of the area in
which they reside. It will also save faces that are picked up by cameras for they mar be burglars or witnesses if the house is
broken into.
Will the data be transmitted to another device, and if so, how?

The data will be transmitted to police departments. The police will receive a signal that will alert them of the situation. There will be an announcement
over their radios and they will report to the scene. The data will also be transmitted to the phones of families through their phones to alert them of
both situations. There will be an app specifically designed and linked to the cameras in which the family receives so that they will know what is going
on 24/7.
(CEISMC)
Prototype (continued)
Diagram/picture/explanation of your prototype.
This prototype is a diagram of what the device could possibly look like. It would need a camera in order to determine and
(CEISMC)
make out the faces of people within or who pass the home. The cameras could also be used to observe the outside conditions.
The device would also require light sensors in order to give off a light. This will alert the criminal that they have been found
out and they will hopefully leave. The battery pack will provide the cameras with a back-up source in case of a power outage.
The sensor will identify motion within the home or outside of the home. THere will also be an alert that will notify the
homeowners if the device is moved.
(CEISMC)
Light Camera Battery

sensor pack
Sensor
Alert if
moved
(CEISMC)
Testing & Redesign

Guide
Designing a solution is almost always an “iterative” process. An iterative process is one that repeats itself, ideally improving each
time, until reaching the desired goal. An important part of such a process is testing at each stage of the process to assess your
solution in relation to the goal. A product may be tested and redesigned many times before reaching its final version.
(CEISMC)
In robotics design, this might look something like:
1. Build a prototype
2. Test the prototype
3. Evaluate the data from the test to see if it meets the desired solution and constraints
4. Redesign an improved prototype
5. Repeat
In a pure programming project, the iterative process might be different versions of your program. Your first prototype program might
not be able to accomplish all of the design specifications, but after testing to verify working portions, you might create new versions
with further capabilities.
This process would continue until the prototype is ready to be considered the final product, either by tweaking the prototype or by
completing new builds.
So now that you have a prototype, it’s time to test it! Determine the best way to test your prototype against your problem’s intended
solution and constraints and fill out the next page with what you’ve learned. You can then duplicate the next page for any major
additional tests and redesigns. Ideally, all data and multiple trials should be recorded, but it’s up to you on how many iterations you
will go through here.
Testing & Redesign

Duplicate this page for any additional major tests & redesigns
How did you test your prototype?

We tested to observe if the circuit was complete by pushing down on our sensor and seeing if our device was fully functional.
(CEISMC)
What were the results? (Report your actual data as possible. Attach additional pages if needed.)
The circuit was complete and the light turned on
How well did your prototype meet the needed specifications/constraints?

Perfectly
Things my design is doing well: Changes I need to make:

Our design is working Add extra reinforcements to our design.
It completes its task to the fullest
All components are complete and functional
Final Product
Guide
Now that you’ve built your prototype, tested it, and redesigned it as needed, it’s time to communicate the solution you’ve made! On
the next two pages, first briefly describe how your final design meets the initial constraints or specifications set in the Define the
Problem step. Answer the questions about your final design and then use the next page to diagram and explain your project. If your
(CEISMC)
project is mostly coding, you can draw a flow chart of the code’s main logical components. Be sure to explain any items that are not
clear from the drawing.
Attach an additional page if you need more space.
There are a couple of remaining things to think of:
● You’ll need to list out your materials and supplies. With the exception of non-consumable items that your teacher lets you
use (such as robotics or electronics kits), your total supply cost must not exceed $30. Use the “Materials and Supplies” page
to list out what materials you had to buy, how much they cost, and attach pictures of your receipts.
● Did you use any code that you didn’t write yourself (such as code found online)? If so, use the “References” page to list
which parts of your code you found elsewhere and where you found them. The majority of your project should be original work
by your team.
● Did you use supplies or equipment from an industry, laboratory, or individual outside of your class? If so, use the
“References” page to note those supplies, where they came from, and provide some contact information for the individual
who worked with you on those items.
● Don’t forget to work on your video presentation for the Student STEM Challenge Competition!
● Additional resource: Storytelling Guide
(CEISMC)
Final Product
(Remember: The total cost for all prototyping AND your final design should not exceed $30!)
How does your final design meet your constraints/specifications? (If you run out of space, describe on your diagram below.)
Our final product met all of the necessary needs in order to fully operate.
What inputs/sensors are there?
What outputs are there?
What processing does your design do?

It processes images and weather conditions to alert owners about potential threats and/or natural disasters.
Does it store any data, and if so, what?

No it doesn’t store data
(CEISMC)
Is the data be transmitted to another device, and if so, how?

N/A
Final Product (continued)
Diagram/picture/explanation of your final product:
(CEISMC)
(CEISMC)
(CEISMC)
Materials & Supplies
You’ll need to list your materials and their cost. Don’t forget to attach receipts!
With the exception of non-consumable items that your teacher lets you use (such as robotics or electronics kits), your total supply cost must not exceed $30. Use
this page to list out what materials you had to buy, their total cost, and to attach pictures of your receipts as evidence. Feel free to add additional pages as needed.
Cardboard- Free
Batteries- $4
Markers- $1
Wire- $10
Tape- $3
Aluminum Foil- $6
(CEISMC)
Total Supply Cost:
References
Did you use any code that you didn’t write yourself (such as code found online)?
If so, use this box to list which parts of your code you found elsewhere and where you found them. The majority of your project should be original work by your
team. Use whichever format your teacher requires.
(CEISMC)
N/A
Did you use supplies or equipment from an industry, laboratory, or individual outside of your class?
If so, use this box to note those supplies, where they came from, and provide some contact information for the individual who worked with you on those items.
N/A
(CEISMC)
Team Member Contributions
Please explain the different roles and divisions of tasks amongst your team members here.
Madison - Connected components to help the product function. Made sure everyone in the group stayed on task at all times, and led the group in the right direction
Namdi - Provided with tools.
Jamarcus- Provided cardboard/ base for the model, as well as giving precise measurements
Caleal- Provided batteries, kept group on task, and completed pages on the document
Charity- Came up with idea, gave guidelines, and supported as much as she could within the given time period
(CEISMC)
(CEISMC)

S

Diunggah oleh

Informasi Dokumen

Judul Asli

Hak Cipta

Format Tersedia

Bagikan dokumen Ini

Bagikan atau Tanam Dokumen

Opsi Berbagi

Apakah menurut Anda dokumen ini bermanfaat?

Apakah konten ini tidak pantas?

Hak Cipta:

Format Tersedia

S

Diunggah oleh

Hak Cipta:

Format Tersedia

STEM Teacher Leadership Program (STLP)

Honeywell Student STEM Challenge

Your project’s title S.B.A.N.D. Device

Define the Problem

Define the Problem

Constraints or Specifications: (Number each below)

Brainstorm & Evaluate Solutions

1 = Poor, 2 = Fair, 3 = Excellent

Brainstorm & Evaluate Solutions

Short description of approach Quick to Little Meets Little Total

Brainstorm & Evaluate Solutions

Suggestions made: New ideas given:

Concerns raised: Things others liked:

Additional resource: Prototyping Toolkit

Chosen solution/approach and reasoning:

What inputs/sensors are there?

What outputs are there?

What processing will your project do?

Will it store any data, and if so, what?

Will the data be transmitted to another device, and if so, how?

Light Camera Battery

Testing & Redesign

In robotics design, this might look something like:

Testing & Redesign

How did you test your prototype?

How well did your prototype meet the needed specifications/constraints?

Things my design is doing well: Changes I need to make:

Attach an additional page if you need more space.

There are a couple of remaining things to think of:

What inputs/sensors are there?

What outputs are there?

What processing does your design do?

Does it store any data, and if so, what?

Is the data be transmitted to another device, and if so, how?

Final Product (continued)

Diagram/picture/explanation of your final product:

Materials & Supplies

Total Supply Cost:

Team Member Contributions

Anda mungkin juga menyukai