SEDSAT-2 Design Review III
From SEDSWiki
The design review was conducted on 1st February 2009
Contents |
Current (active) members)
Who is in your team? Who is active on the team?
Timeframe for completion
A Gantt Chart is needed. It should include:
- All of the major sections of work you need to do.
- Each major section should be broken down into its component parts.
For example, the major sections of work might include: design, development, prototyping, testing (of prototype), construction (of launch version), pre-flight verification, documentation/post-launch support. Then drill-down into each major section, and define what next level of work will be, eg. for an ADCS subsystem, the "design" phase might include: attitude control-model design, attitude control hardware design and attitude determination hardware design. Drill down further into each part if you think it is appropriate. The lowest level tasks should have specific outcomes eg. "Develop PCB schematic" (where the outcome is a completed PCB schematic). Think about how much time will be required for each of the lowest level tasks - make an educated guess (it has been said that when an Engineer gives an educated guess for the amount of time to complete a project, it should be doubled to be realistic ;). It doesn't matter if the guess is wrong, the Gantt chart is a living document, update it as the design progresses.
Clarification
Design and Development are sometimes mixed together (sometimes this is unavoidable as they overlap) - it's up to you whether you combine them or not. For clarity, here are some possible definitions for "design" and "development":
- "Design" involves working out what your requirements are, eg. how much power must you generate, what is your ADCS pointing accuracy. What are your mass, power and size constraints? How much transmit power do you need? Then you need to work out how to implement something which meets these specifications. At the end of "Design", you should clearly know what your requirements are and have a proposal for a system to implement it.
- "Development" is when you actually do the coding, PCB schematic/layout, FPGA code, CAD models...
Current Design
What has been produced so far?
- Have your requirements been defined? If so, what are they?
- How will the completed system work? What technologies does it use? Are these technologies novel or have they been used before (where?)?
- Has the system been broken down into components? If so, what are they?
- Has development begun? What state? Code? Schematics? CAD models?
- Have prototypes been produced? What is their functionality? Does they perform as expected? Any issues?
- What next?
Interfaces
How does your design fit in with the rest of the system? There are numerous budgets and constraints. Do you have estimates for the attributes described below? Are your estimates significantly more/less than the budgeted amount (if so, say so and it may be possible to reallocate budgets).
- Mass - rough estimate?
- Dimensions - rough estimate?
- Operating Voltage/current: What is the power consumption of your system? Voltages and currents? What duty cycle (how often it's in high power state vs low power state)? What is the power consumption in the different states?
- Control Interface: What commands will CDH be able to give to your subsystem? What will these commands do? How do you plan to test your subsystem during integration?
- Data Interface: What data must be transferred from your subsystem to other systems? How is this data transfer achieved? Protocols? Bus specifications? Bus electrical requirements (logic standard, level shifter requirements etc...)
- Cad model or sketch of entire system: very useful to help people in the other teams understand exactly what your subsystem will do, and how it will do it.
- Thermal: Are there any thermal issues with your subsystem? How do you plan to dissipate thermal energy?
Financial Situation
What are the financial requirements of your subsystem, in order to fully achieve the plan set out in your Gantt chart? Money for parts, software, tools/facilities, component manufacture, flights etc...
Personnel Situation
Do you have enough people to complete the plan in your Gantt chart, in a reasonable amount of time? Are there any specific areas where you feel additional people/skills might be needed to work on parts of the design?
Summary
- Do you have a clear goal for your subsystem?
- Are you on track?
- Any issues?
