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
  1. VEX Engineering Notebooks
  2. Understanding the Engineering Notebook Rubric
  3. Engineering Design Process Categories

Select Best Solution and Plan

PreviousBrainstorm, Diagram, or Prototype SolutionsNextBuild and Program the Solution

Last updated 1 year ago

This section takes advantage of the work that was completed in the last section. Whether a decision matrix, pro/con list, or other brainstorming solution was used to come up with ideas it is not time to select the best solution for implementation and explain why it was chosen.

In some cases just because a solution appears to be the best based on a decision matrix a team may opt to pick a lower scored solution based potentially on team voting or some other decision process.

By providing reasoning behind why a solution was selected, the reader can better understand the approach the team is trying to take. In some cases, such as with prototypes, testing of the device may provide results that may not have been expected by a team. By explaining this and how it affects the overall decision to implement, the team may be able to augment their testing section.