5pf - Honeywelll Challenge Group - Period 7

=
STEM Teacher Leadership Program (STLP)

Honeywell Student STEM Challenge
Project Overview
Your names and grades: Brian Young (10th),Farrell Edwards (10th), Arielle Brayboy (10th), Brooklyn Givens
(10th), Parrish Gilbert (10th)
Your project’s title: Tik Tok Alert
Your teacher’s name: Mrs. Mathieu Your school: Arabia Mountain
Your project summary: Our honeywell project design is a cover lever designed for children and handicap persons. A sensor
is to be located in a kids or handicap family member’s bedroom. The notifier is to be placed in a guardian or caregiver’s room.
In partnership with Honeywell and the GA Tech Center for Education Integrating Science, Mathematics & Computing
(CEISMC)
https://www.ceismc.gatech.edu/community/stlp
=
When in danger, a child or handicap person can lift the cover to emit a sound that will notify the guardian or caregiver of
distress. Our inputs for our project include LEDs, alligator clips, active Buzzer. Along with sensors, such as radio wireless
communication LIght sensor. The outputs of our project include Sound and light emitting from the alarm notifier to signal an
emergency. Our design properly sends signals to the corresponding microbit in an orderly fashion.
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.
(CEISMC)
=
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?
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
Need: There is always a need to enhance first response technology. Some technology is to complicated or not easy accessible for
handicapped individuals. The WheelWire will help handicapped individuals in a wheelchair get emergency help at a quick and easy
accessible rate.
Audience: The product is directed towards people with either physical or mental disabilities. Considering, these handicaps make
it harder for people to escape in a quickly. We are creating a product that allows them to be easily found and alerted to dangers,
such as fires and carbon monoxide in the air.
Constraints or Specifications: (Number each below)

1. Deadline Nov. 14
2. Maximum cost $30
3. Efficiency of workers
(CEISMC)
=
Problem Statement: Children and the disabled can’t get the help that they need in a timely manner. This will make it easier for
individuals in need of extra assistance to get quick help when an emergency has happened. We are creating a product that can be
easily found and used to alert parents or guardians of pending dangers . We have up $30 and up until Nov. 14 to accomplish our
goal.
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.
(CEISMC)
=
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.
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
1) Attach a sensor(microbit) to wheelchair that alerts the consumer of rapidly increasing

temperature and the presence of smoke, so they are able to quickly get out of disastrous
situations.
2 3 3 2 10
2) Program that allows the wheelchair to move to the closest exit in the case of an
emergency.
1 2 2 2 7
(CEISMC)
=
3) A sensor that sends a message to a notifier to alert a user of a pending emergency.
3 3 3 2 11

Get Feedback
Suggestions made: New ideas given:
● Lauryn- Give it the ability to be mounted ● Lauryn- use a button

● Keslyn- add a sensor for nearby objects
(CEISMC)
=
Concerns raised: Those with special needs may need extra Things others liked:
assistance in harmful situations
● Lauryns- gives attention to those that are disabled.
● Lauryn- the sensor could go off when there's no emergency ● Briana- help people quickly get out of disastrous
● Keslyn- the sensor not detecting the danger in time situations.
● Keslyns- helps people in need during emergencies
● Lauryn- the uniqueness of the light sensor
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:

A budget lever designed for children and handicap persons. A sensor is to be located in a kids or handicap family member’s bedroom.
The other is to be placed in a guardian or caregiver’s room. When in danger, a child or handicap person can pull this lever to emit a
sound that will notify the guardian or caregiver of distress.
(CEISMC)
=
What inputs/sensors are there?

● LEDs
● Alligator clips
● Active Buzzer
-Sensors
● Radio wireless communication
● LIght sensor
What outputs are there?

● Sound and light emitting from the alarm notifier to signal an emergency.
(CEISMC)
=
What processing will your project do?

The light sensor will send a signal to the alarm notifier to alert a guardian or family member of ones distress.
Will it store any data, and if so, what?

Our device will store distress signals in the form of a frowny face.
Will the data be transmitted to another device, and if so, how?

Our data will be transmitted to another device by radio communications.
Prototype (continued)
(CEISMC)
=
Diagram/picture/explanation of your prototype:
(CEISMC)
=
(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.
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.
(CEISMC)
=
Testing & Redesign

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

We had a small child and their parent/guardian participate in this test. The alarm sensor was positioned in the room of a small
child. We had the child act as if they were in distress and directed them to lift the cover . When the cover was pulled, data from
this device was sent to the notifier, in the guardians room, to alert them of an emergency.
What were the results? (Report your actual data as possible. Attach additional pages if needed.)
The messages were sent to the alarm notifier each time , however the flashing LEDs showed the wrong pattern a few times due
to the alligator clip shifting.
How well did your prototype meet the needed specifications/constraints?

The prototype met the needed specifications/constraints.
(CEISMC)
=
Things my design is doing well: Changes I need to make:

The design properly sends signals to the corresponding microbit in One thing we could change to make our project better is
an orderly fashion. to add a louder melody to alarm to ensure it is
detectable.
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
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:
(CEISMC)
=
● 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 design meets the constraints/specifications by
What inputs/sensors are there?

● LEDs
● Alligator clips
● Active Buzzer
-Sensors
● Radio wireless communication
● LIght sensor
What outputs are there?

Sound and light emitting from the alarm notifier to signal an emergency.
(CEISMC)
=
What processing does your design do?

The light sensor will send a signal to the alarm notifier to alert a guardian or family member of ones distress.
Does it store any data, and if so, what?

Our device will store distress signals in the form of a phrase “HELP” and a frowny face.
Is the data be transmitted to another device, and if so, how?

Our data will be transmitted to another device by radio communications.
Final Product (continued)
Diagram/picture/explanation of your final product:
(CEISMC)
=
Materials & Supplies
(CEISMC)
=
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.
(CEISMC)
=
Total Supply Cost: $7.43
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)
=
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.
Mr. Roberts provided our group with a “Super Kit for Arduino” which the active buzzer, an essential part of our project came from.
(CEISMC)
=
Team Member Contributions
Please explain the different roles and divisions of tasks amongst your team members here.
The initial brainstorming involved all members of the group. Farrell created the rich picture . Parrish was in charge of doing the
“Define the Problem “ section and the sketch for the prototype. Brooklyn assisted Arielle with the gathering of materials,
“Brainstorm & Evaluate Solutions: Decision Matrix”, and the Prototype Guide. Arielle programmed and built the product, along with
completing the Testing and Redesigning Guide. Brian assisted with the concept and filming for the video advertisement.
(CEISMC)
=
(CEISMC)

5pf - Honeywelll Challenge Group - Period 7

Încărcat de

Informații document

Titlu original

Drepturi de autor

Formate disponibile

Partajați acest document

Partajați sau inserați document

Opțiuni de partajare

Vi se pare util acest document?

Este necorespunzător acest conținut?

Drepturi de autor:

Formate disponibile

5pf - Honeywelll Challenge Group - Period 7

Încărcat de

Drepturi de autor:

Formate disponibile

=

STEM Teacher Leadership Program (STLP)

Your project’s title: Tik Tok Alert

Your teacher’s name: Mrs. Mathieu Your school: Arabia Mountain

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

1) Attach a sensor(microbit) to wheelchair that alerts the consumer of rapidly increasing

3) A sensor that sends a message to a notifier to alert a user of a pending emergency.

Brainstorm & Evaluate Solutions

Suggestions made: New ideas given:

● Lauryn- Give it the ability to be mounted ● Lauryn- use a button

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?

Diagram/picture/explanation of your prototype:

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: $7.43

Team Member Contributions

S-ar putea să vă placă și