Usability and Completeness
Last updated
Last updated
The area of usability and completeness is ultimately focused upon the ability of the notebook being able to provide enough detail that a reader could recreate the team’s implemented solution.
Looking over the provided documentation could a reader recreate and build the finalized robot, a particular subsystem, or program the solution to perform a desired task.
While there isn’t a specific task a team can accomplish to show proficiency in this area, it ultimately comes down to how well everything comes together.
Are design phases documented well?
Are there CAD diagrams, sketches, or other images with parts lists that show how a solution can be built?
Does the programming offer enough information to create a controllable solution?