MakerRepo Administrators, MakerRepo Staff
795
edits
Changes
Jump to navigation
Jump to search
Line 15:
Line 15: + + + + + Line 68:
Line 73: + + + + +
Professional development/Design thinking/Design for manufacturing (view source)
Revision as of 20:33, 5 April 2021
, 20:33, 5 April 2021no edit summary
#Always practice soldering, it is a skill that takes time to master.
#Always practice soldering, it is a skill that takes time to master.
#Your time is also valuable. Spend a few dollars if it will save your many hours of frustration.
#Your time is also valuable. Spend a few dollars if it will save your many hours of frustration.
== Prototype planning ==
The first step when thinking about prototyping is deciding which technical specification(s) or metric(s) you want to evaluate. You can then use the specs to come up with an <u>objective</u> for your prototype and a <u>testing plan</u>. This objective, or reason, for the prototype will be a justification for making it, for example a high priority metric needs to be validated. The testing plan will include ways to evaluate the metric(s) and how the results will be collected. You can then develop and build a prototype that will be able to perform the outlined tests and give appropriate results.
Remember that a prototype is not regular everyday work on a project, it is a targeted way of obtaining and evaluating test results. This may mean that a prototype will not be used in the final product.
==Prototype 1==
==Prototype 1==
#Always think about the right fastening/adhesive for your material, hot glue is never an appropriate fastening or sealing method.
#Always think about the right fastening/adhesive for your material, hot glue is never an appropriate fastening or sealing method.
#Always solder electronic circuits with wire and protoboard. No breadboards or jumper cables here!
#Always solder electronic circuits with wire and protoboard. No breadboards or jumper cables here!
== Prototype testing and results ==
Once your prototype is made then you can test it. Remember that the whole purpose for creating the prototype is to test and get measurable results to evaluate a metric(s). The results should be as objective as possible and collected with a clear procedure that is repeatable. This procedure should be documented so that multiple teammates could carry it out and achieve the same results. This is especially true when conducting interviews for user feedback.
Remember that debugging part of the project is not considered testing. The tests should be a clear reflection of the metrics outlined earlier in the design process.
''Have fun!''
''Have fun!''