IIWII Robotics
  • VEX Engineering Notebooks
    • Overview
    • Notebooking Best Practices
    • Understanding the Engineering Notebook Rubric
      • Engineering Notebook Scoring
      • Engineering Design Process Categories
        • Identify the Problem
        • Brainstorm, Diagram, or Prototype Solutions
        • Select Best Solution and Plan
        • Build and Program the Solution
        • Test Solution
        • Repeat Design Process
      • Additional Categories
        • Innovation/Originality
        • Usability and Completeness
        • Record of Team and Project Management
          • Time Management
          • Team Management
          • Resource Management
        • Notebook Format
    • Parts of a Notebook (Sections)
      • Cover Page
      • Team Overview / Introduction
      • Table of Contents (TOC)
      • Engineering Design Process (EDP)
      • Engineering Notebook Format
      • Game Overview / Analysis
      • Design Brief
      • Notebook Entries
        • General Entry
        • Team Meeting
        • Time Management
        • Resource Management
        • EDP Entries
          • Identify the Problem
          • Research
          • Brainstorm / Evaluation
          • Build / Program
          • Test
          • Repeat Design Process
      • Competition Writeup
      • Innovate Submission
      • Appendix
        • References
    • Engineering Notebook Resources
  • Interview
    • Overview
Powered by GitBook
On this page
  • Build Entry Examples
  • Programming Entry Examples
  1. VEX Engineering Notebooks
  2. Parts of a Notebook (Sections)
  3. Notebook Entries
  4. EDP Entries

Build / Program

PreviousBrainstorm / EvaluationNextTest

Last updated 10 months ago

Within the Build / Program entries the below items is a short list of what could be considered as mentioned below. When documenting the build process it can be good to lay out all the components required and ensure there is a build or parts list identified to make it easier to go back and recreate a project. Having photos of a solution is also helpful as changes are being made they can be compared to previous or future iterations. Not to mention sometimes a change may be made that doesn’t quite work and it makes sense to revert back to a previous design implementation.

Build

  • Build Process

  • CAD

  • Diagrams / Drawing / Sketches

  • Images / Photos of subsystem, inventory used to build a solution, or complete robot

Program

  • Program Pseudocode

  • Actual Code

  • Maps~Path

Build Entry Examples

Programming Entry Examples

Concept Pseudocode Map Entry vs.Established Pseudocode+Path Map+Functional Code

Additional Coding Entry Examples