Thread: Kickoff day
View Single Post
  #19   Spotlight this post!  
Unread 07-12-2015, 17:35
GeeTwo's Avatar
GeeTwo GeeTwo is offline
Technical Director
AKA: Gus Michel II
FRC #3946 (Tiger Robotics)
Team Role: Mentor
 
Join Date: Jan 2014
Rookie Year: 2013
Location: Slidell, LA
Posts: 3,572
GeeTwo has a reputation beyond reputeGeeTwo has a reputation beyond reputeGeeTwo has a reputation beyond reputeGeeTwo has a reputation beyond reputeGeeTwo has a reputation beyond reputeGeeTwo has a reputation beyond reputeGeeTwo has a reputation beyond reputeGeeTwo has a reputation beyond reputeGeeTwo has a reputation beyond reputeGeeTwo has a reputation beyond reputeGeeTwo has a reputation beyond repute
Re: Kickoff day

Quote:
Originally Posted by TikiTech View Post
..
Design Labs[/b] – We have been using Stanford Design Thinking for many years in our design process ..
For more information on Stanford Design Thinking you can visit:
http://kealakeherobotics.org/student...sign-thinking/
The five steps of SDT are (from your web site):
  1. The first step is empathy; we see how others feel towards a specific item. Interviews are used to gain insight to human nature.
  2. The second step is to define. In this step, we use the information gathered from interviews to find the user’s real problem.
  3. Ideate, the third step in design thinking, is where the group finds solutions to the problem.
  4. The fourth step is to prototype. Once an idea is decided upon, groups work together using random materials to construct examples of their product and explain how their product works.
  5. Testing is the final step. Groups rebuild their prototypes and create a working product. Once built, testing begins. Testing identifies problems with the item, so the product can be modified to better suit the user.

With the requirements already specified in the form of rule books, what to you do for step 1 on the first round? The other steps correspond roughly to our planned engineering process; not quite how we think about it, but it makes sense.
Edit: Our mnemonic of the engineering cycle is DRIPPER:
  • Define the Problem
  • Research known solutions
  • Imagine possible solutions
  • Plans (blueprints and schedule)
  • Prototype/Build
  • Evaluate/Test
  • Repeat as necessary (meaning not always back to Define)

Looking this over makes me also wonder if and how you review known/previous solutions to similar problems in your process.
__________________

If you can't find time to do it right, how are you going to find time to do it over?
If you don't pass it on, it never happened.
Robots are great, but inspiration is the reason we're here.
Friends don't let friends use master links.

Last edited by GeeTwo : 07-12-2015 at 17:43.
Reply With Quote