Project 2-Evaluation Guidelines

The following are guidelines that will be used in evaluating the Project.

REVIEWER: You will be reviewing every other student's Project 2 tutorial except your own.
To do this you will use the shared google document. For say the Student with the last name Smith you will
go to the tab named "Smith-Reviews for the Smith Tutorial" and you will see that everyone in the class
except Smith will have a row, go to the row with your name on it and fill in the numbers and the last column has
a narrative explanation of your review of Smith's tutorial. DO NOT EDIT ANY OF THE OTHER rows on the Smith Tutorial. Then move on to review the next student's work by going to the correct tab.


INVITATION to SHARED GOOGLE DOC: You must have recieved an invitation to edit this document via email.

URGENT: you must keep a backup copy of your review of each student's tutorial. Sometimes people incorrectly edit the fields and we need to recover your information.

You will evaluate the following and the due dates are given below:

1. Project 2 "Proposal" - 15 points - Instructor Reviewed.
2. Project 2 "Tutorial" - 105 points
   • 85 points = tutorial
   • 20 points = you did good review of ALL of your fellow student's Project 2 tutorial (ALL of them except you don't review yourself).

 

Evaluation (85 Points) - PEER Reviewed

Section	Contents you should have (sometimes the negative values can total more than the section total ---this is correct as it represents possible points to take off. However, the minimum you can get in any seciton is 0 points.
1) Format: Implemented as tutorial done in HTML on topic of choice. To produce the web pages, you can use any web authoring tool you wish --- I personally use Adobe Dreamweaver (and you can get a free trial version to do this). I highly recommend that you use a web authoring tool. This is what professionals due.   1Points: 0 to 10	Even 1 HTML link that does not work in tutorial take ( -3 points) Has Navigation bar/feature that makes sense and can easily navigate around tutorial (5 points) Consistent look and feel, designed for good readability and text size and format is well readable (5 points)
2) Mixed-Media: You must have a minimum of 5 pictures or diagrams illustrating the concept you are discussing. As appropriate include video or audio also. If you borrow images, you must reference in the legend where you retrieved them from. Points: 0 to 10	Minimum of 5 pictures or diagrams (2 points each)
3) Organization: The tutorial should be organized. It SHOULD not look like a long paper. You should have a nice intro with an easy navigation scheme present throughout the site's pages. YOU MUST HAVE A NAVIGATION BAR either across the top or vertically down the left and must be present on ALL web pages in your html tutorial. Points: 0 to 10	Good Intro(2.5points) Have multiple pages --not one long page. (2.5 points ) Navigation bar must appear at the top or vertically down the left on ALL web pages in your html (2.5 points ) Creation of navigation bar links and the corresponding section makes sense --a good way to break up the tutorial into sections. (2.5 points )
4) Originality: Your writing should be original. You can NOT paraphrase large blocks of text. If you need to paraphrase smaller items, you need to refer to the article in which the text comes from and surround the text with quotes. You should keep to a bare minimum the number of times you paraphrase others words. I DO NOT WANT TO SEE LARGE AMOUNTS OF COPYING ......NOR DO I WANT TO SEE YOU JUST LINKING OFF TO OTHER PAGES AND NOT EXPLAINING IN YOUR OWN WORDS Points: 0 to 10	Work is original at least 90% of the writing with minimum paraphrasing(10 points ) -20 points if you do not have at least 90% of the writing as original
5)Length: Someone should be able to go through your tutorial on their own within 30 minutes. Points: 0 to 5	Length to go through tutorial is approximately 30 minutes (get 5 points) Length to go through tutorial is approximately 20 minutes (get 3.5 points) Length to go through tutorial is approximately 10 minutes (get 1.5 points) Length to go through tutorial is less than 10 minutes (get 0 points)
6)Level of Detail: I expect that you will delve into your topic at a sufficient level of detail for the audience to be able to understand how things are implemented or created and with possible reference to your article(s) (that you quote) be able to recreate or build the system(s) described. For example: If you are discussing a topic that involves the development of software or algorithms, you should present a minimum of one algorithm or piece of code on the topic. You should discuss how the algorithm works and if there are alternatives compare them to others, summarizing with what you think (and others may think) are superior algorithms (and why). Also, give the user an idea when you might apply one technique over another. If you are discussing a topic that is theoretical, you should discuss the various options, limitations and conditions under which the theory is applicable. Discuss applications of the theory and how it improves operations. Contrast and compare the theory with other theories/techniques that may accomplish the same or similar goals. Points: 0 to 20	You could create simple samples or recreate basic system using this tutorial (get 20 points) You need 10% help from other sites to create simple samples or recreate basic system using this tutorial (get 18 points) You need 20% help from other sites to create simple samples or recreate basic system using this tutorial (get 16 points) You need 30% help from other sites to create simple samples or recreate basic system using this tutorial (get 14 points) You need 40% help from other sites to create simple samples or recreate basic system using this tutorial (get 12 points) You need 50% help from other sites to create simple samples or recreate basic system using this tutorial (get 10 points) You need 60% help from other sites to create simple samples or recreate basic system using this tutorial (get 8 points) You need 70% help from other sites to create simple samples or recreate basic system using this tutorial (get 6 points) You need 80% help from other sites to create simple samples or recreate basic system using this tutorial (get 4 points) You need more than 80% help from other sites to create simple samples or recreate basic system using this tutorial (get 0 points)
7)Annotated Bibliography: You are required to have links in your tutorial to an annotated bibliography. You must have a minimum of TWO reference (please note different pages on the same web-site do NOT count). Throughout your on-line tutorial, each time you wish to quote a reference, it should be represented by a number that is hyper-text linked to the annotated bibliography. In this bibliography page, you will have listed in order of appearance (hence the numbers) your references each followed by an annotation of the contents of the reference. Specifically, you must include not only the title, author, date, source, but also, a sysnopsis, and a reliability rating. For example, for the second reference you would have: [2] "Java is Great", Lynne Grewe, PC Weekly, May, 1996., p.g. 21-33. synopsis: this is a journal article that discusses the benefits Java brings to the programming world and contrasts it with other high-level languages. reliablity: L. Grewe is an independent researcher and professor. PC Weekly is an popular computer industry magazine that publishes technical articles, mainly to a non-research but, technical audience.   Points: 0 to 10	no references (get 0 points) references with No synopsis and reliability (-5 points) DO NOT adequately cite ALL your references in the body of the tutorial -5 points.....example In [2] the authors discuss the fact that Java is the most popular language in China for Web Programming.
8)****NEW*** Presentation Review (separating it from other 1-7 more explicitly) this is to review the in-person presentation and live demonstration (of example/system) Points: 0 to 10	professional/clear speaking (up to 2.5 points) good presentation material (large font --easier to read then rest of tutorial matieral) (up to 2.5 points) live demo of an example (if theortical --go through sceanrio analysis) (up to 5 points)

Peer Review Accomplished (20 points) - Instructor assigned

alternative to the guidelines below the instructor may simply choose to pro-rate the number of points by the percentage of reviews finished.

Awarded Points	Criteria
20 points (A)	reviews are complete and done very well reviewer showed problems in code reviewer evaluated each piece given in rubric above reviewer made comments on how the application could be improved reviewer especially highlighted how Google App Engine datastore is used
17 points (mid B)	reviewer missed problems in more than 10% of tutorials
16 points (low B)	reviewer did between 75% to 100% of the necessary (all other students) reviews
14 points (low C)	reviewer did between 50% to 75% of the necessary (all other students) reviews
12 points (low D)	reviewer did between 35% to 50% of the necessary (all other students) reviews
10 points (F)	reviewer did at least 2 reviews and less than 35% of the necessary (all other students) reviews.
8 points (F)	revewer did only 1 review
0 points (F)	no reviews done