Help:Capstone Design

Description of project design task. This, along with the picture, should engage the reader and communicate the goals of your project.



Background
Optional section used to explain the project further, or to mention (and link!) past projects.

Sponsors
Put your sponsor's logo and short description here. If you have several sponsors consider a custom table or the gallery template. Our wiki back-end, MediaWiki is currently version 1.21. When the back-end is upgraded to 1.22 the mode: packed-hover option will become available for the gallery template.

Team Members
In this section needs to include a picture of each member and their corresponding bios. Consider using level three headings for each member, or perhaps a two x n table.

Design Goals
Use bulleted/numbered lists as necessary. If the design goals change/clarify during initial interview, you should make note of that.

Design Specifications
More detailed (quantified) specifications of the design goals.

Background Research
Topics can include research on material, methods / devices, specialized equations, etc. Topics not covered by your education should be recorded here

Topic one
Make sure to [Help:General_Information#Resources|cite](See the note under Cheatsheet) your sources !!!

Interview with Joe Vandal, 9/9/99
Use bullets, lists and quotes as necessary

Concept Development
This section will document any work which contributes to the final design. This will include prioritizing design functionalities using a design matrix, preliminary testing of concepts, design/testing of prototypes. The below is only an example, the order/completeness may of course be modified as needed.

Consider including an initial system diagram (could be a sketch) which shows initial organization/understanding of subsystems.

Design matrix
Thought ME123 was going to be the last time you did this? Below is an implementation from the Band-Beesten_rolling_drum_set. The table can be organized from least to greatest by any column. Please not, wiki tables are not capable of handling equations like Excel, so you'll have to do this addition by hand.

Sub system one
Description of subsystem functionality (that someone outside of your discipline or unfamiliar with your project would understand

Could also use lists:
 * Foreseen challenges
 * challenge 1
 * challenge 2
 * Ideas, design specs, etc.
 * idea 1
 * idea 2

Proposed solutions
A table making use of the RowTemplate or ADRow templates may work well.

Testing
Descriptions/pictures/data would all work well here!

Below is one idea:

Conclusion
You can use this section to state rational if needed.