View Single Post
  #1   Spotlight this post!  
Unread 07-07-2015, 18:43
IKE's Avatar
IKE IKE is offline
Not so Custom User Title
AKA: Isaac Rife
no team (N/A)
Team Role: Mechanical
 
Join Date: Jan 2008
Rookie Year: 2003
Location: Michigan
Posts: 2,149
IKE has a reputation beyond reputeIKE has a reputation beyond reputeIKE has a reputation beyond reputeIKE has a reputation beyond reputeIKE has a reputation beyond reputeIKE has a reputation beyond reputeIKE has a reputation beyond reputeIKE has a reputation beyond reputeIKE has a reputation beyond reputeIKE has a reputation beyond reputeIKE has a reputation beyond repute
Design Documentation Best Practices

I am curious what sort of design documentation practices teams have? I have observed a few threads about CAD sharing, and code sharing, and about solving problems.... I am curious if any teams feel they ahve a really great documentation process that they would like to share on CD.

IE documentation of scoring analysis, strategy derivation, functional decomposition, Prototype results, architecture development/solution, design calculations (motor & gearbox selection), detailed design, design changes (and change processes), component and subassembly tests, integration, system testing, system tuning, practice, design changes due to seeing competitors, design changes due to stuff breaking, strategic shifts mid comp season.....

The closest I have observed were some teams that kept build blogs, which is definitely a type of design documentation. What others are out there that teams use? Any success or best practices worth sharing?