/* Style Definitions */
table.MsoNormalTable
{mso-style-name:"Table Normal";
mso-tstyle-rowband-size:0;
mso-tstyle-colband-size:0;
mso-style-noshow:yes;
mso-style-priority:99;
mso-style-parent:"";
mso-padding-alt:0in 5.4pt 0in 5.4pt;
mso-para-margin:0in;
mso-para-margin-bottom:.0001pt;
mso-pagination:widow-orphan;
font-size:12.0pt;
font-family:Cambria;
mso-ascii-font-family:Cambria;
mso-ascii-theme-font:minor-latin;
mso-hansi-font-family:Cambria;
mso-hansi-theme-font:minor-latin;}
The United States Naval Academy (USNA) is an undergraduate-only institution whose mission is to educate future officers in the United States Navy and Marine Corps. The Naval Academy has participated in a number of project based learning efforts both in engineering classes (Design–Build–Fly) as well as in focused projects (e.g. SAE Formula-1 race car, Cockpit of the Future, and the Sailbot). We are currently participating in the Systems Engineering Research Center research topic “RT-19: Research on Building Education & Workforce Capacity in Systems Engineering” (RT-19) for the 2010–2011 academic year.
Research topic RT-19 is to develop Systems Engineering talent in the workforce through projects developing working solutions to real-world problems. USNA RT-19 participation includes sixteen students from four majors and three departments working on four independent senior-design capstone projects:
• Improving Surge Power Capabilities.
• Personnel Tracking.
• Portable Low-power Water Purification (interdisciplinary project).
• Portable Renewable Sea-based Power Generation, Storage, and Distribution (interdisciplinary project).
Each team is developing a functioning artifact that could be delivered to the RT-19 sponsor as a prototype implementation. The projects were conceived to solve a specific problem, designed to be viable within senior-design course limitations, and implemented by the students. They will be demonstrated as part of capstone presentations in April.
We have faced two challenges so far. The first challenge has been interdisciplinary project coordination in the presence of different senior-design sequences with different schedules, course content, and course requirements. The second challenge has been providing systems-engineering content without a common senior-design sequence for interdisciplinary project teams.
In this paper, we provide a full accounting of our experiences to date including accomplishments, lessons learned, and our plans to improve the senior-design process to support both well-defined as well as quick-reaction project opportunities.