click below
click below
Normal Size Small Size show me how
Graves Engineer Note
Graves VEX Robotics Engineering Notebook
| Question | Answer |
|---|---|
| How do you show Identifying the Problem in your notebook? | Clearly define and justify the -design goals, -criteria (how you know you succeed), and -constraints (restrictions) |
| How do you show Brainstorming and Research in your notebook? | Explore several different solutions with explanations, and citations from other sources |
| How do you show Selecting the Best Solution in your notebook? | Explain the “why” behind design decisions in each step of the design process |
| How do you show Build and Program the Solution in your notebook? | Include enough detail that the reader can: -follow the logic used by the team to develop their robot design, -recreate the robot design and program it from the documentation. |
| How do you show Original Testing of Designs in your notebook? | Record all the steps to test the solution, including test results. |
| How do you show Repeating the Design Process in your notebook? | Show: -setbacks that the team learned from, and -design alternatives that were considered but not pursued |
| How do you show Independent Inquiry in your notebook? | Note whether ideas come from: -the students on the team, or -if students found inspiration elsewhere. |
| How do you show Usability and Completeness in your notebook? | Record the entire design and development process with enough clarity and detail that the reader could recreate the project's history |
| How do you show Originality and Quality in your notebook? | Keep to relevant information AND -all content not original to the team is located in appendices (at the end of the notebook). |
| How do you show Organization and Readability in your notebook? | There is an overall organization to the document that makes it easy to reference, like: -color-coded entries, -tabs or other markers for key sections. |
| How do you demonstrate Recording of Team and Project Management in your notebook? | Provide team meeting notes including: -goals, -decisions, and -building/programming accomplishments. Design cycles (dates) are easily identified |