Quote:
Originally Posted by David Brinza
My oldest son, Matt, was a member of Team 16 (Bomb Squad). His role on the team was "compliance officer" and, basically, he verified the robot complied with the rules. I think this is a really good idea - the student can be the point-of-contact during inspections. A mentor can play the role of inspector while the student addresses the items. In this way the students and mentors being accountable to FIRST.
|
The BeachBots (mentioned above) have a student/mentor team that is responsible to see that ALL robot requirements are met. We write up a detailed requirements document every year and check off the items as they are accomplished. Many of these requirements are in the rule book, others are "homemade" the result of experience. Many of the requierments remain the same from year to year, others change due to the game.
An example of a homemade requirement is one that "all extendables shall be retractable". We learned this one the hard way. "The robot shall shoot balls at a speed greater than 4 ft/sec and less than 12 ft/sec" is an example of a game driven requirement from last year.
If it looks like we will not be able to meet a requirement, we develop a plan for either accomplishing it or doing without the effected subsystem, on rare occasions we might rewrite the requirement some time during build.
In any case, we develop the requirements document BEFORE we start building or even designing the robot. It is a lot easier to hit the target if you know where it is.