AeroE 462                  AEROSPACE  DESIGN II                  Spring,1997

COURSE REQUIREMENTS
GENERAL
Group projects are run concurrently by separate groups of students. These may generally be selected from some combination of
1 Aircraft Design
2. Spacecraft Design
3. Engine Design
4. Other, depending upon student interest

All projects must include a complete problem specification and analysis. Projects are specified in the form of a Request for Proposal (RFP), a Company Directive or a detailed problem statement. The RFP may be class generated, instructor generated or an AIAA or Industry competition. If the problem is class generated, a conceptual design stage is required. The Engineering Methodology of AeroE 461 is to be followed generally.
The class will be organized and responsibilities assigned in the fashion of a Preliminary Design Team. Communications will follow the chain-of-command: V-P, Chief Engineer, Team Leaders. The V-P (instructor) will make or OK the initial organizational structure and appointments and will make subsequent team assignments in cooperation with the Chief Engineer. If problems in the organization arise (e.g.,personal conflicts), it is the responsibility of the team leaders to report them early so that changes may be made if necessary.
Grades in the course will be based primarily on assessments made by each student and these will be determined by considering the position held by the student in the organizational structure.
Assessments are to be submitted by the individuals directly to the instructor at two separate times; before mid-term and before the end of dead week. Assessments must also be made when a team is disbanded.
Activity summaries are to be submitted to each team leader at a time the latter specifies.
Grades for the Chief Engineer will be determined also by the instructor's assessment of his/her leadership qualities, record of meetings, scheduling etc.
A semester-end final report and presentation are required at the time scheduled by the Chief Engineer during dead week (normally Tuesday).
TEAM LEADER RESPONSIBILITIES
Team Leaders will

schedule regular team meetings
prepare and continually update a schedule and submit it to the Chief Engineer
submit a written weekly status report to the Chief Engineer which includes actual and perceived present and future problems
arrange for completion of assessments by individual team members
submit assessments of other Team Leaders and of the Chief Engineer to the instructor
call for, verify and submit activity summaries, with comments to Chief Engineer at a time the latter specifies CHIEF ENGINEER RESPONSIBILITIES
The Chief Engineer will
assign and dissolve teams as required with notification to V-P (team members are selected from lists of specialists determined by student interests at the beginning of class)
schedule a weekly meeting between him/herself, Team Leaders and V-P
prepare and continually update the project schedule and submit it to the V-P for discussion at or before the weekly meeting
submit a weekly status report to the V-P
attach the team reports to the status report
report problems, etc. verbally to the V-P
arrange for completion of assessments by her/his Team Leaders on each other and on the Chief Engineer
prepare and submit assessments of his/her Team Leaders to V-P
review, comment on, and submit activity summaries to the instructor by end of dead week