Requirements on Participants

Requirements on Participants

The following information outlines the responsibilities of the subsystem design teams. Since this project will be a learning experience for all parties involved, and since all of us will need information from other teams to do a good job, significant attention to communication between universities and teams is of the utmost importance. Design progress will be monitored through weekly reports, tele and video conferences, conferences, and design reports.

  1. Teleconferences will take place to communicate ideas, questions, and design information between the subsystem teams and the system integration team. Additional conferences can be set up on an as needed basis.

  2. Weekly progress reports shall be submitted on the World Wide Web at the end of each week, using the design page progress report form. These forms will communicate the work that has been accomplished during the current week, and work that will be accomplished in the next week. The progress reports are of extreme importance, and will be used to communicate that the project is progressing smoothly.

  3. The Conceptual Design Review (CDR) Report is a mid-fall-semester report to provide a overview of the Conceptual Design of the subsystem, which will be examined in full detail through the remainder of the semester. The conceptual design report should include a minimum of 5 to 10 pages of single spaced text, not including tables, diagrams, cover pages, etc. A copy of this document will be sent to the system integration group in electronic form via the provided ftp account.

  4. Design Report I is a fall end-of-semester report which provides all necessary information to detailed preliminary design of the subsystem. This design report will be written in a detailed format (to be provided), and will be used in the second phase of this project. This report will include a minimum of 50 pages and include trade studies, detailed designs, diagrams, tables, integration tables, final mass estimates, volume, power, operational constraints, program outlines, where to go from here, etc. The report should show that design specifications and interfaces have been met. You will provide hard copies of this document for all teams (12 copies). One electronic copy of this shall be sent to the system integration group at the end of the fall semester.

  5. Design Review I (DR I) Design Review I will be held via audio/video conferencing at the end of the fall semester. Each subsystem design will be presented by the responsible subsystem design team. The presentation should be based on the Preliminary Design Report. The presentation should be approximately 20 minutes in length. Hard copies of the presentation must be provided to all design teams prior to the audio/video conference

  6. Design Report II is a spring mid-semester report (Date TBD) which will provide a overview to the second major design iteration of the subsystem begun in the fall semester, which will be examined in full detail through the remainder of the spring semester. This design report should include a minimum of 40 pages of single spaced text, not including tables, diagrams, cover pages, etc. A copy of this document will be sent to the system integration group in electronic form via the provided ftp account.

  7. Design Review II (DR II) Design Review II will be held via audio/video conferencing near the middle of the spring semester. Each subsystem design will be presented by the responsible subsystem design team. The presentation should be based on the Design Report II. The presentation should be approximately 20 minutes in length. Hard copies of the presentation must be provided to all design teams prior to the audio/video conference

  8. The Detailed Subsystem Design Report is a end-semester, end-project report which provides all necessary information to detailed preliminary design of the subsystem. This design report will be written in a detailed format (to be provided), and will be used in the second phase of this project. This report will include a minimum of 85 pages and include trade studies, detailed designs, diagrams, tables, integration tables, final mass estimates, volume, power, operational constraints, program outlines, where to go from here, etc. The report should indicate how design specifications and interfaces have been met. You will provide hard copies of this document for all teams (12) at the Design Conference. One electronic copy of this shall be delivered to the system integration group at the Design Conference. This report will be correlated with the other subsystem reports to form the proposal which will be sent to NASA.

  9. Detailed Design Conference Presentations will be held (site TBD) at the end of the spring semester. Each final subsystem design will be presented at this conference by at least one member of the responsible subsystem design team. The presentation should be based on the Detailed Subsystem Design Report . The presentation should be approximately 20 minutes in length.

Responsibilities may be added or modified throughout the course of this project if they are deemed necessary and reasonable by the instructor group and/or the project's PIs to ensure timely completion of this project .


Buttons

Wednesday, 31-Dec-1969 18:00:00 CST
CSR/TSGC Team Web