PDR/CDR expectations

[Brian T Sanders]

Hello team,

Here is some more to consider for the CDR on Friday 2/20.  We will meet Friday at 3pm for our full PDR/CDR with presentation.  Which team wants to start at 3pm?

Here is a CDR package from a few years ago.  Take a look at the CDR presentation specifically for some ideas.  This was done by a larger team and they needed to go more in depth for the design, and your teams are on a much compressed schedule.  Look through their design and get ideas of what design aspects should be covered but don’t get too carried away with scope and the complexity of this design.

https://drive.google.com/a/colorado.edu/file/d/0B6nuS4-reQ5-WkRhR1NOeUN5NG8/view?usp=sharing

Please be sure to cover the following:

*Estimate People hours reemitting per system and a grand total 

*Risk chart (severity and probability - see the CDR presentation at the above link)

*Logic Flow diagram for software showing navigation.  This is typically the first step in pseudo code.

*Testing plan - Show/list how you are going to test the individual units (like motors) and then how you are going to test the full integrated system and where you are going to test (hint, inside at first then where outside).

We will meet here on Friday at 3pm for the first team CDR and will hope to conclude by 4pm, 4:30 if we need to go long. 

B

Brian Sanders
Deputy Director
Colorado Space Grant Consortium
spacegrant.colorado.edu
Office: 303-492-5451
Mobile: 303-258-6339