Documenting Projects

Your Assessment Rubric is the key to your success in this class. Every part of the rubric report explains and documents your work over an entire week. It is important that you document all your work, since this is the primary method upon which your score is based. You must prove that you have completed the work and steps described by including supporting documentation or examples of your work.

Here’s some helpful tips on writing the Rubric Report:

  • You must use this guide with the actual rubric. The rubric will explain what is expected in each section. This guide is just to help with the organization of the material the rubric asks for.
  • Remember to be detailed in your rubric report so that I will not have any question of whether or not you applied yourself to the project.
  • This document is a guide, as are the examples. You should follow the format of this document, not the exact words of the examples.

YOUR REPORT MUST BE SAVED IN YOUR PERSONAL NETWORK FOLDER
WITH THE FOLLOWING FILENAME FORMAT:
reportX-X .html

(For example, the filename for your report on project 1.2would be “report1-2 .html”)

Brief and Specifications:

This section of the report is the core of your entire project. It describes exactly what the purpose of the project was including detailed specifications. “I was supposed to make a video.” Is not detailed… You must include how long the video should be, what it was supposed to be about, how many transitions and titles were required, etc. These Briefs should be very detailed. Include every specification that your project must meet. This section should be no more than two sentences.

EXAMPLE: “The goal of this project was to design and produce a ___________ that met the following specifications: a. _______________, b.______________, c.________________.”

Research:

This section of the report includes details about what you had to learn and where you gathered the information necessary to successfully complete the project. Include some of the main concepts and vocabulary you learned, detail the sources you used for research, and list other things that you learned that made it possible to successfully complete this project. Be sure to include the information you had to gather to complete the project. “Following directions,” “working hard,” and “cooperating” are not concepts you had to learn to complete the project. They are possibly strategies you employed to complete the project, but are not concepts. I want you to use specific concepts related to the project. Things like making a link on a web page, using layers in a graphics program, animating using timelines in a 3D program, coordinates and multiple views in 3D and CAD programs, commands in programming, etc. are all examples of concepts. They are project related, project specific ideas that are critical to the task.

EXAMPLE: “In this project I used (name of resource) and (name of resource) to gather information about (name of subject studied). One of the main concepts I had to learn was (name concept) because (reason why concept was important). Another important concept I had to understand was (name of concept). This concept was important to understand because (reason it was important). Without learning these concepts, I would not have been able to finish my project successfully because (why these concepts helped you finish your project)

Ideation:

Ideation means to generate new ideas. This section is the area where you will demonstrate that you thought about different ways to solve the problem stated in the Brief and Specifications. This means that you should BRAINSTORM different approaches to solving the problem stated in the design brief. For a bridge or dragster, it would be different sketches of what your bridge or car could look like. For a web page, it would be different topics for the site and sketches of different page layouts. For robotics it might be different ideas about what kind of robot you will build. For video and audio it would be different ideas for scripts and storyboards. Different projects will have different types of brainstorming work. In every project, you should come up with 5-10 solutions for the problem. Then narrow your solutions down to 3. It is important for you to demonstrate that you thought about your project before working on it. If you came up with only one solution and just ran with it, you did not think enough about possible better methods for attacking the problem. This paragraph should discuss your 3 best ideas. Include reasons why you chose the final solution as well as reasons why you rejected the other solutions.

EXAMPLE: “On the attached developmental sketches, you will see 3 ideas labeled “A”, “B”, and “C”. I chose not to use the concept labeled “A” because (explain why). I also chose against the concept labeled “C” because (explain why). I used concept “B” as my final design because (explain why).

Developmental Work:

In every project, there is developmental work. You should document here the work that had to be done originally to successfully complete the project. You cannot just start and complete a project without planning. The developmental work for your project is the planning stage. You must demonstrate that before working, you developed a plan. This means that you should have rough and final drafts of scripts and storyboards, sketches of page layouts and project designs, rough drafts of programming code, tutorial projects that demonstrate that you experimented with the tools before working on your final project, etc. Often this will be a short paragraph describing the type of work you did and a sentence saying that examples of this work are attached. Don’t throw away your rough drafts, you’ll need them for this section of the report. Sometimes your developmental work will not be a sketch, but experimenting with programming code, experimenting with tools, or measuring and evaluating methods of solving the problem. In cases like these, be sure to explain the developmental work you did. Many times you will just briefly explain what kind of developmental work you did (sketches, scripts, rough drafts, outlines, etc.), explain that the work is attached, and attach the work to the back of your rubric report.

EXAMPLE: “For this project I created rough sketches, full-size drawings, and final comps. (Describe the quality of your developmental work). All sketches and drawings have been scanned and are attached to this document.

Testing:

In this section of the report you will evaluate whether or not your project met the requirements stated in the Brief and Specifications. This section of the report is evaluation of your project only, not your performance. If your project was a bridge, did it meet all the rules regarding width, height, construction, etc.? If your project was a drawing, does it meet all the requirements including size, presentation, media, etc.? You must evaluate whether or not your project is completed as specifically stated in the design brief.

EXAMPLE: “My final prototype met all (or “3 out of 4”, or “half”, etc.) the specifications listed in the design brief. It meets the requirements for (list specifications and explain how it meets the specs.). It failed to meet the specifications for (list specs that were not met and how they were missed).

Evaluation:

In this section, you must evaluate your work and participation in the project. Evaluate yourself honestly. If you did just what you were supposed to do then say it was average. If you went above and beyond the requirements, then say that your work was above average. And if you didn’t really focus on the project and didn’t give it the attention to detail it deserves, then admit that it was below average. Once you have evaluated yourself, if you believe you did above average work, you should include detailed and specific examples of what you did that was above average. In any case, there should be detailed reasons for the success or failure of the project, examples of what you would do differently if you had to do it over, and honest self-criticism (self-evaluation).

EXAMPLE: “On this project I would rate my work as (average, superior, fair, poor, etc.). The reason I feel this way is (detailed reasons for your evaluation). If I were to do this project again, I would (what would you do differently to do better?).”

Solution:

This section is not in the report. It is the evaluation of your project itself. Was there attention to detail? Does the project show evidence of craftsmanship? Is the project made out of the proper materials? Does the project demonstrate an appropriate amount of time used or does it look “rushed?” The rubric is very clear here. Follow the rubric point scale for examples of what is required for higher scores in this area.

Presentation:

This section of the rubric is a grade on your report itself. Was your report adequate? Did you include the appropriate materials and components? Is it detailed? Does your report seem like it was done carefully with evidence of proper preparation?