Project Proposal

Proposal Content

Team Composition

The preferred team size is four members. Teams of three or five are allowed with instructor permission only.

The proposal should include the names and majors of team members.

Project Alternatives

Each team must submit at least two project ideas (one primary and at least one backup). For each possible project, the following information should be included:

  • Project description
    • Give enough detail so the project scope and objectives are clear.
    • Identify and describe your project's client or customer, if you have one.
    • Focus on the necessity of the project and the problem it will solve. Avoid a solution looking for a problem.
    • Show that your proposed project complies with the ABET requirement that “Students must be prepared for engineering practice through the curriculum culminating in a major design experience based on the knowledge and skills acquired in earlier course work and incorporating appropriate engineering standards and multiple realistic constraints.”
    • Demonstrate that your proposed project has appropriate content for all your team members:
      • Any team with a CE member must have a project with significant hardware content.
      • Any team with an SE member must have a project with significant software content.
  • Project technologies and support facilities
    • Identify the technologies (hardware, software, other) you anticipate may be required for successful project completion.
    • Describe your familiarity with each of the key technologies, and what level of assistance you expect you'll need.
    • Support needed from MSOE EECS department - lab equipment, PC workstation.
    • Support needed from MSOE CCSD department - special server, access to MSOE active directory, etc.
    • Support needed for equipment fabrication (e.g., machine shop, Rapid Prototyping), testing, etc.
  • Preliminary development plan
    • Initial breakdown of overall project into incrementally delivered pieces
    • Description of functionality to be attempted in development cycles

It is important that your team give early and serious thought to your project alternatives, technologies, and potential development approach. If you don't, the result can be wasted time at the beginning of your course sequence, which can have a major negative effect on your team's success (and your senior design grades).

Optional information

Add your comments and suggestions regarding the senior design sequence. Be sure to include any questions about the courses, project, or process.

Submission

Submit this proposal no later than Monday of Week 9 (due date may differ by instructor) of spring quarter. Submit pdf format proposal here.

seniordesign/proposal.txt · Last modified: 2010/05/11 08:35 by taylor
 

This website is not owned or managed by the Milwaukee School of Engineering.

© 2003-2010 Dr. Christopher C. Taylor, et. al. • Office: L-343 • Phone: 277-7339 • npǝ˙ǝosɯ@ɹolʎɐʇ • -> RSS <-