System Design Requirements

[EricH]

A couple of design-drivers from my time on 330:

--Shall comply with all rules.
--Shall move. (It should be noted that the specific attributes of the motion were dependent on year.)
--All deployables shall be retractable.*


*There have been exceptions--generally, it's because there isn't a good retract method available AND the deployable doesn't get in the way when deployed.

[SenorZ]

Establish your capabilities first. Then design within them.

It is easy to get carried away with outsourced parts. Make sure you have the ability to build a robot in-house that will meed your minimum needs. Only then do you start calling your waterjet sponsor.

[GeeTwo]

Our technical requirements (how fast, how strong) derive from our functional requirement (score 6 boulders) which derive from the game rules. The only one that we could probably call up front is that the trickiest manipulator must weigh no more than 20-25 pounds, so that we can fit it and a few other neat things in our 40 pound withholding bag. Then, we can keep tweaking it up until competition.