DocumentationofProjects

When we do projects, it is important to have some goals at the beginning. Your goals help to keep you on track, and help to identify the things that you need to figure out or do. The documentation you create helps to prove that you did something and made something. Once your documentation is available, a person interested in it can look at it and see how you did it and what problems and successes you had. By creating the documentation, you can use the parts to create some other project, or you can put the project into use in the world.

Descriptions:

As you work on projects, you should create documentation of your actions. This documentation should include a description of the steps you have gone though. You should have photos of the project while it is in process.

Resources:

You should make a point of including the links to websites that were helpful for figuring out the project. You should make the links as useful as possible by creating a link to the actual page that held the information.

For example, a link to http://del.icio.us/ might be moderately useful, but a link to http://del.icio.us/search/?fr=del_icio_us&p=basicstamp&type=all would be more useful. To give a more specific result, show this, an example of how to use the basic stamp to measure wind speed: http://www.emesystems.com/OL2wind.htm#Annemometer

• Here are some questions that should give your documentation some form:**

1. What did you set out to do originally?
2. What did you do?
3. What did you have to do differently than you thought?
4. How would you approach this project differently, knowing what you do now?