Final Project Web Page Guidelines
Due at 8:00 AM Friday March 18 (finals week)
Email me a link to your site as well as a .zip file of your site, for archiving.
Instead of a printed final report, ME 333 uses web reports. With very
little more work than a written report, you can create a site that is
accessible to others and much more effective at communicating
your design.
You are free to design the web site as you like.
Content is more important than style, and your site must meet
the following guidelines.
- The site must have an "index.html" (or "index.htm") file for the
home page.
- There should be no spaces in any of the file names.
- The site must have at least one photo showing the whole project.
Other photos, which help demonstrate the functioning of the system,
are encouraged. We have a digital camera in the lab that can be used
during the final project review, or when the TA
is in the lab.
- The site should have an introductory page, with a picture of the
mechatronic system and a brief description of what it does.
- The site should have a "results and reflections" page which describes how well the
project worked and how it could have been improved.
- Give sufficient information on how the project was built that it
could be reproduced without excessive effort. You can break this down
into mechanical, electrical, and software subsections, or however you
want. You should include
- A list of parts and materials used, and where
possible, the vendor, part number, and price.
- Circuit diagrams for non-obvious circuits. These may be carefully
hand-drawn and scanned, but preferably generated using a drawing program.
Any drawing program is fine. (Currently only bench 1 is equipped with OrCad,
specifically for drawing circuit diagrams.)
- Drawings, or sufficiently clear pictures, of the mechanical systems with
brief supporting text descriptions.
- Pseudocode, flow charts, or other clear description of the working of
your control program. You may even wish to include
the actual code, though this isn't necessary.
- All files for the site must be in a single directory (no nested
sub-directories).