Design Principles

From Open Source Ecology
Jump to: navigation, search

Design Checklist for Collaborative Development on Constrained Timelines

To design artifacts in any mechatronic design, here are general best practices for any design, including OSE designs. OSE designs have extra requirements in the form of OSE Specifications, but the ones below are generic. These apply specifically to design sprints where a number of collaborators gather for a limited time frame, such as during STEAM Camps.

  1. When doing collaborative design in a constrained time frame, prioritize development of the complete Minimum Viable Product (MVP) over rapid iteration (Test-Driven Design) of individual components.
  2. Test individual components before doing a complete CAD design. Note that normally, CAD is generated at the same time. If there are not enough people, delay the CAD.
  3. Know how to reconcile 1 and 2 above.
  4. When doing collaborative design on a Window of Opportunity Approach, prioritize rapid iteration over fine-tuning - ie, quick-and-dirty rather than detailed-and-procedurally-correct.
  5. Understand the distinction between the rapid, iterative design phase for rapid prototyping and 'final' design phase that is at or near product release. Do not put excessive detail/refinement into a design at the iterative phase. In other words, do not spend time perfecting designs that don't work.
  6. Any design that has not been prototyped and evaluated should not be considered a working design. Prior to prototyping, designs should be considered 'nonworking' or a-working - to emphasize that we don't know enough yet to base further design on this design. Get to a prototype as quickly as possible before refining a nonworking design.
  7. Distinguish when it is more appropriate to do CAD design vs physical prototyping (3D printing or other prototyping).
  8. When CAD designing iterative modifications of existing parts on a constrained time frame, use existing CAD parts and combine them rather than redesigning them from scratch to make them 'better'.
  9. Use minimum extent of structure possible to perform a desired task. To get additional strength, first consider Intensive Scalability, and second, Extensive Scalability.
  10. Use the minimum number of fasteners to perform a desired task. Ideally, design for using only one. For fastener strength, see Clamp Force. Minimum number of fasteners can contribute to Robustification.
  11. If the part count for performing a task is greater than 1 - seek ways to bring the number back to 1
  12. Keep cost minimum by minimum use of material, without reducing performance. Robustification
  13. Keep build time down by using simple procedures. This is part of Robustification
  14. Reduce skill level requirements for building something, while not reducing performance. This is part of Robustification.
  15. Seek ways for a single part or assembly to serve multiple functions, without complicating the build procedure.