Grading+Rubrics

=Grading Rubrics=

The following rubrics are used by the instructor in the WDIM courses.

Research and Analysis Documentation Rubric (25 points) Presentation Rubric (25 points)

Project Contract Rubric (25 points) Individual Project Document Rubric (25 points)

Web Site Design Rubric (160 points)
 * Client Goals (32 points)
 * User Experience (32 points)
 * Visual Design (32 points)
 * Technical (40 points)
 * Project Archive (24 points)

= Research and Analysis Documentation Rubric = Presenter: Topic: Other feedback:
 * || **1 Point** || **2 Points** || **3 Points** || **4 Points** ||
 * **Quality of Information** || Information has little or nothing to do with the main topic. || Information clearly relates to the main topic. No details and/or examples are given. || Information clearly relates to the main topic. It provides 1-2 supporting details and/or examples. || Information clearly relates to the main topic. It includes several supporting details and/or examples. ||
 * **Sources** || Some sources are not accurately documented. || All sources (information and graphics) are accurately documented, but many are not in the desired format. || All sources (information and graphics) are accurately documented, but a few are not in the desired format. || All sources (information and graphics) are accurately documented in the desired format. ||
 * **Diagrams & Illustrations** || Diagrams and illustrations are not accurate OR do not add to the reader's understanding of the topic. || Diagrams and illustrations are neat and accurate and sometimes add to the reader's understanding of the topic. || Diagrams and illustrations are accurate and add to the reader's understanding of the topic. || Diagrams and illustrations are neat, accurate and add to the reader's understanding of the topic. ||
 * **Research Summary Documentation Materials** || Documentation materials demonstrate little or no thought regarding the audience. || Documentation materials are generic. || Documentation materials are crafted for the audience. || Documentation materials are crafted specifically for the audience and provide the intended user experience. ||
 * **Presentation Materials (when presenting research summary)** || Presentation materials demonstrate little or no thought regarding the audience. || Presentation materials are generic. || Presentation materials are crafted for the audience. || Presentation materials are crafted specifically for the audience and provide the intended user experience. ||
 * **Mechanics** || Many grammatical, spelling, or punctuation errors. || A few grammatical spelling, or punctuation errors. || Almost no grammatical, spelling or punctuation errors || No grammatical, spelling or punctuation errors. ||

Total Points (24 + 1 point for creating document=25 points):

= Presentation Rubric = Presenter__:__

Topic:


 * || **1 Point** || **2 Points** || **3 Points** || **4 Points** ||
 * **Organization** || Audience cannot understand presentation because there is no sequence of information. || Audience has difficulty following presentation because presenter jumps around. || Presenter presents information in logical sequence which audience can follow. || Presenter presents information in logical, interesting sequence which audience can follow. ||
 * **Subject Knowledge** || Presenter does not have grasp of information; presenter cannot answer questions about subject. || Presenter is uncomfortable with information and is able to answer only rudimentary questions. || Presenter is at ease with expected answers to all questions, but fails to elaborate. || Presenter demonstrates full knowledge (more than required) by answering all audience questions with explanations and elaboration. ||
 * **Graphics** || Presenter uses superfluous graphics or no graphics || Presenter occasionally uses graphics that rarely support text and presentation. || Presenter 's graphics relate to text and presentation. || Presenter 's graphics explain and reinforce screen text and presentation. ||
 * **Eye Contact** || Presenter reads all of report with no eye contact. || Presenter occasionally uses eye contact, but still reads most of report. || Presenter maintains eye contact most of the time but frequently returns to notes. || Presenter maintains eye contact with audience, seldom returning to notes. ||
 * **Elocution** || Presenter mumbles, incorrectly pronounces terms, and speaks too quietly for audience in the back of room to hear. || Presenter 's voice is low. Presenter incorrectly pronounces terms. Audience members have difficulty hearing presentation. || Presenter 's voice is clear. Presenter pronounces most words correctly. Most audience members can hear presentation. || Presenter uses a clear voice and correct, precise pronunciation of terms so that all audience members can hear presentation. ||
 * **Time Limit to Cover Content** || Presenter goes over time limit by more than 9 minutes. || Presenter goes over time limit by 6 minutes. || Presenter goes over time limit by 3 minutes. || Presenter finishes content within time limit. ||

Other feedback:

Total Points (24 + 1 point for getting up to speak=25 points):

= Project Contract Rubric = Author Name and Project:
 * **Project Contract** || **0 Points** || **1 Points** || **2 Points** || **3 Points** ||
 * **Project Background** || Information about project background is missing. || Project background contains some information but many team members may not understand why the project is being done. || Project background contains information but some team members may not understand why the project is being done. || Project background contains enough information for all project team members to understand why the project is being done. ||
 * **Project Goal Statement** || Project goal statement is missing. || Project goal statement is obscure. || Project goal is clear to only some team members. || Project goal is clear and concise so all project team members understand the intended outcome. ||
 * **Project Objectives and Requirements** || List of project objectives and requirements is missing. || Project objectives and requirements are obscure. || Project objectives and requirements are clear to only some team members. || Project objectives and requirements are clear and concise for all team members (and measurable). ||
 * **Target Audience(s)** || Description regarding the target audience(s) for the project is missing. || Description of target audience is obscure or describes something other than the target audience(s). || Description of target audience(s) is clear to only some team members. || Description of target audience(s) is clear and concise for all team members. ||
 * **Tone and Image Information** || Description regarding the tone and image for the project is missing. || Description of tone and image is obscure. || Description of tone and image is clear to only some team members. || Description of tone and image is clear and concise for all team members. ||
 * **List of Project Deliverables** || List of deliverables for the project is missing. || Key deliverables are missing. OR Key deliverables are listed but due date AND responsible person are missing. || Key deliverables are listed. Due dates OR responsible person is missing. || List of deliverables clearly defines deliverable, due date and person responsible for delivery. ||
 * **Change to Scope Information** || Policy for making changes to the scope of the project is missing. || Policy for making changes to the scope of the project is obscure. || Policy for making changes to the scope of the project leaves some room for interpretation. || Policy for making changes to the scope of the project is clear and concise. ||
 * **Language Subject to Lawsuit** || Project contract contains language guaranteeing the client financial gain that is difficult or impossible to measure that, if not met, could result in a lawsuit (Web site will increase business.) || Project contract contains some language that could inadvertently lead to a lawsuit. || Project contract contains very little language that could inadvertently lead to a lawsuit. || Project contract contains language that that minimizes the opportunity for a client to sue for breach of contract. ||

Total Project Contract Points (24 + 1 for creating document=25 points):

= Individual Project Document Rubric = Author Name and Project__:__


 * **Project Document** || **1 Points** || **2 Points** || **3 Points** || **4 Points** ||
 * **Message** || Intended message is missing or obscure. || Intended message is appropriate for some of the team project members. || Intended message is appropriate for most of the team project members. || Intended message is exceptionally crafted specifically for all team project members. ||
 * **Content Copy** || The author has provided only the minimum amount of information and has not transformed the information to make it more readable and understandable to the team project members. || The author has put information in the Web site but it is not written and presented for the team project members. || The author has tried to make the content in the document more readable and understandable to the team project members. || The author has made an exceptional attempt to make the content in the document more readable and understandable to the team project members. ||
 * **Documentation Organization** || The author has provided only the minimum amount of information and has not organized the information for the audience(s). || The author has put information in the documents but it is not organized for the audience(s). || The author has tried to organize the content of the documents for the people for whom it is intended. || The author has made an exceptional attempt to organize the content of the document(s) for the people for whom it is intended. ||
 * **Navigation through Document** || Sections of the document have not labels or misleading labels. A project member typically feels lost when trying to locate information in a document. || Some section labels of the document take the reader where s/he expects to go, but some labels are missing or are named in a way the project member does not expect. S/he sometimes gets lost when trying to find information in a document. || Sections of the documents are clearly labeled, allowing the reader to easily move from one section to another and take the reader where s/he expects to go. A project member rarely becomes lost when trying to locate information in a document. || Sections of the document are clearly labeled, consistently placed, allowing the reader to easily move from one section to another and take the reader where s/he expects to go. A project member does not become lost when trying to locate information in a document. ||
 * **Project Branding** || Document contains no branding for the project. It could belong to any project. || Document contains minimal branding. || The author has made an attempt to create and use an interesting brand for the document that conveys basic project information. || The author has made an exceptional attempt to create and use a professional and interesting “production-quality” brand for the document (and other documents). ||
 * **Spelling and Grammar** || There are more than 5 errors in spelling, punctuation or grammar. || There are 4-5 errors in spelling, punctuation or grammar. || There are 1-3 errors in spelling, punctuation or grammar. || There are no errors in spelling, punctuation or grammar. ||

Total Individual Project Document Points (24 + 1 for creating document=25 points):

= Web Site Design Rubric = Designer: Project:

Total Client Goals Points (32 points):

 * **Client Goals** || **1 Points** || **2 Points** || **3 Points** || **4 Points** ||
 * **Message** || Intended message is missing. || Intended message is obscure. || Intended message is present but not entirely clear. || Intended message is clear and concise. ||
 * **Message Matches Project Contract** || Intended message unrelated to goals and objectives as outlined in project contract. || Intended message fulfills some goals and objectives as outlined in project contract. || Intended message fulfills most goals and objectives as outlined in project contract. || Intended message fulfills all goals and objectives as outlined in project contract. ||
 * **SEO Keywords** || Few or no keywords are used in content copy and included on web pages. || Some keywords are used in content copy and included on web pages. || Many keywords are used in content copy and included on web pages. || Keywords are used in content copy AND included on each web page. ||
 * **SEO Description** || Few or no descriptions are included on web pages. || Some descriptions are included on web pages. || Many descriptions are included on web pages. || Description is included on each web page. ||
 * **Content Copy** || The author has provided only the minimum amount of information and has not transformed the information to fulfill the business objectives as outlined in the project contract. || The author has put information in the Web site but it does not fulfill the business objectives as outlined in the project contract. || The author has tried to make the content of this Web site fulfill the business objectives as outlined in the project contract. || The author has made an exceptional attempt to make the content of this Web site fulfill the business objectives as outlined in the project contract. ||
 * **Content Organization** || The author has provided only the minimum amount of information and has not organized the information to fulfill the business objectives as outlined in the project contract. || The author has put information in the Web site but the organization of the information does not fulfill the business objectives as outlined in the project contract. || The author has tried to organize the content of this Web site to fulfill the business objectives as outlined in the project contract. || The author has made an exceptional attempt to organize the content of this Web site to fulfill the business objectives as outlined in the project contract. ||
 * **Fulfills Project Goal** || The outcome does not fulfill the project goal. || The outcome somewhat fulfills the project goal. || The outcome mostly fulfills the project goal. || The outcome completely fulfills the project goal. ||
 * **Fulfills Objectives and Requirements** || The outcome does not fulfill the project objectives and requirements. || The outcome somewhat fulfills the project objectives and requirements. || The outcome mostly fulfills the project objectives and requirements. || The outcome completely fulfills the project objectives and requirements. ||

Total User Experience Points (32 points):

 * **User Experience** || **1 Points** || **2 Points** || **3 Points** || **4 Points** ||
 * **Message** || Intended message is missing. || Intended message is not appropriate for the target audience(s). || Intended message is appropriate for the target audience(s). || Intended message is exceptionally crafted specifically for the target audience(s). ||
 * **Content Copy** || The author has provided only the minimum amount of information and has not transformed the information to make it more interesting to the audience. || The author has put information in the Web site but it is not written and presented for the target audience(s). || The author has tried to make the content of this Web site interesting to the people for whom it is intended. || The author has made an exceptional attempt to make the content of this Web site interesting to the people for whom it is intended. ||
 * **Content Organization** || The author has provided only the minimum amount of information and has not organized the information for the audience. || The author has put information in the Web site but it is not organized for the target audience(s). || The author has tried to organize the content of this Web site for the people for whom it is intended. || The author has made an exceptional attempt to organize the content of this Web site for the people for whom it is intended. ||
 * **Navigation** || Some links do not take the reader to the sites described. A user typically feels lost. || Links for navigation take the reader where s/he expects to go, but some needed links seem to be missing. A user sometimes gets lost. || Links for navigation are clearly labeled, allowing the reader to easily move from a page to related pages, and internal links take the reader where s/he expects to go. A user rarely becomes lost. || Links for navigation are clearly labeled, consistently placed, allowing the reader to easily move from a page to related pages, and take the reader where s/he expects to go. A user does not become lost. ||
 * **Spelling and Grammar** || There are more than 5 errors in spelling, punctuation or grammar in the final draft of the Web site. || There are 4-5 errors in spelling, punctuation or grammar in the final draft of the Web site. || There are 1-3 errors in spelling, punctuation or grammar in the final draft of the Web site. || There are no errors in spelling, punctuation or grammar in the final draft of the Web site. ||
 * **Images (accessibility)** || The needs of visually impaired Internet users are ignored. || Most images used for navigation have an ALT tag that describes the image and where it links to so people who are visually impaired can use the Web site well. || All images used for navigation have an ALT tag that describes the image and where it links to so people who are visually impaired can use the Web site well. || All images, especially those that are used for navigation, have an ALT tag that describes the image and its link so people who are visually impaired can use the Web site well. ||
 * **Sounds** || Music, audio clips and/or sounds were seemingly used randomly OR typically detracted from the overall site. || Music, audio clips and/or sounds are thoughtfully edited and used, but 1 or 2 detracted from the overall site. || Music, audio clips and/or sounds are used only where they add to reader understanding of the content or to make the site more accessible to persons with visual handicaps || Music, audio clips and/or sounds are thoughtfully edited and used only where they add to reader understanding of the content or to make the site more accessible to persons with visual handicaps. ||
 * **Page Titles** || Page titles are missing. || Some pages have clear titles. || Many pages have clear titles. || All pages have clear titles. ||

Total Visual Design Points (32 points):

 * **Visual Design** || **1 Points** || **2 Points** || **3 Points** || **4 Points** ||
 * **Message** || Intended message is missing. || Intended message is obscure. || Intended message is present but not entirely clear. || Intended message is clear and concise. ||
 * **Message Matches Project Contract** || Intended message unrelated to goals and objectives as outlined in project contract. || Intended message fulfills some goals and objectives as outlined in project contract. || Intended message fulfills most goals and objectives as outlined in project contract. || Intended message fulfills all goals and objectives as outlined in project contract. ||
 * **Background** || Background detracts from the readability of the site. || Background is consistent across pages and does not detract from readability. || Background is attractive, consistent across pages, adds to the theme or purpose of the site, and does not detract from readability. || Background is exceptionally attractive, consistent across pages, adds to the theme or purpose of the site, and does not detract from readability. ||
 * **Layout** || The Web pages are cluttered looking or confusing. It is often difficult to locate important elements. || The Web pages have a usable layout. It is easy to locate most of the important elements. || The Web pages have an attractive and usable layout. It is easy to locate all important elements. || The Web site has an exceptionally attractive and usable layout. It is easy to locate all important elements. White space, graphic elements and/or alignment are used effectively to organize material. ||
 * **Fonts** || A wide variety of fonts, styles and point sizes is used. || The fonts are consistent and point size varies appropriately for headings and text. || The fonts are consistent, easy to read and point size varies appropriately for headings and text. || The fonts are consistent, easy to read and point size varies appropriately for headings and text. Use of font styles (italic, bold, underline) is used consistently and improves readability. ||
 * **Color Choices** || Colors of background, fonts, unvisited and visited links make the content hard to read or otherwise distract the reader. || Colors of background, fonts, unvisited and visited links do not detract from the content. || Colors of background, fonts, unvisited and visited links do not detract from the content, and are consistent across pages. || Colors of background, fonts, unvisited and visited links form a pleasing palette, do not detract from the content, and are consistent across pages. ||
 * **Icons** || Icons seem randomly chosen, are of low quality, OR distract the reader. || Some icons are related to the theme/purpose of the site and enhance reader interest or understanding. || Many icons are related to the theme/purpose of the site and enhance reader interest or understanding. || Icons are related to the theme/purpose of the site and enhance reader interest or understanding. ||
 * **Graphics** || Graphics seem randomly chosen, are of low quality, OR distract the reader. || Graphics are related to the theme/purpose of the site, and are of good quality. || Graphics are related to the theme/purpose of the site, are of good quality and enhance reader interest or understanding. || Graphics are related to the theme/purpose of the site, are thoughtfully cropped, are of high quality and enhance reader interest or understanding. ||

Total Technical Points (40 points):

 * **Technical** || **1 Points** || **2 Points** || **3 Points** || **4 Points** ||
 * **Validation HTML** || Few or no pages validate. || Some pages validate. || Most pages validate. || All pages validate. ||
 * **Validation CSS** || Little or no CSS validates. || Some CSS validates. || Most CSS validates. || All CSS validates. In the case where a design decision was made to use invalid markup, there is documentation. ||
 * **Compatibility** || This Web site has not been tested OR supports only one browser on one platform. || This Web site has been tested and shown to work on both Macs and PCs but supports only one browser. || This Web site has been tested and shown to work in relatively current versions of common browsers on Mac or PC. || This Web site has been tested and shown to work on both Macs and PCs and works in relatively current versions of common browsers. ||
 * **Interactive Elements Fail Gracefully** || There is no backup plan for interactive elements needed for the user to complete a task. || Some interactive elements will fail gracefully from a user’s point of view. || Most interactive elements will fail gracefully from a user’s point of view. || All interactive elements will fail gracefully from a user’s point of view. ||
 * **Organization of Markup/Scripting on Page** || There is little or no organization with the markup and scripting. || Markup and scripting is somewhat organized so others can identify and find sections. || Markup and scripting is mostly organized so others can identify and find sections. || Markup and scripting is clearly organized so others can identify and find sections. ||
 * **Commenting of Markup/Scripting** || Markup and scripting contain little or no comments. || Markup and scripting contains some comments so others can understand what is intended. || Markup and scripting contains many comments so others can understand what is intended. || Markup and scripting is clearly commented so others can understand what is intended. ||
 * **File and Folder Naming Conventions** || Web site files and folder names fail to relate to the project. || Web site files and folders follow a consistent naming convention. Some names fail to relate to the project. || Web site files and folders follow a consistent naming convention and clearly relate to the project. The home page is named something other than index.html. || Web site files and folders follow a consistent naming convention and clearly relate to the project. The home page is named index.html. ||
 * **Organization of Web Site Files and Folders** || Web site folder lacks organization. Multiple copies of assets are used. || Web site folder is organized. 3 or more copies of assets are used. || Web site folder is organized. 1-2 copies of assets are used. || Web site folder is clearly organized and optimized to include only one copy of reusable assets. ||
 * **Source Files in Web Site Folder** || 5 or more source files for web site elements are contained within the web site folder. || 3-4 source files for web site elements are contained within the web site folder. || 1-2 source files for web site elements are contained within the web site folder. || No source files for web site elements are contained within the web site folder. ||
 * **Web Site Ready for Deployment** || Final web site files and folders are mixed in with other project documents. || Final web files and folders are contained within one folder. Many old versions of files or other project documents are included. || Final web files and folders are contained within one folder. Some old versions of files or other project documents are included. || Final web site folder contains only the files needed for deployment to the web server. (e.g. old versions of pages, images, etc. have been cleaned out) ||

Total Project Archive Points (24 points):

 * **Project Documentation** || **1 Points** || **2 Points** || **3 Points** || **4 Points** ||
 * **Project Archive** || Few or no project files are contained in the project archive folder. || Some project files are contained in the project archive folder. || Many project files are contained in the project archive folder. || All project files are contained in the project archive folder. ||
 * **Naming Conventions** || Labeling of documents fails to follow the project team’s agreed-upon naming conventions. Project members must open documents to find the one they want. || Many project documents fail to follow the project team’s agreed-upon naming conventions. Project members must open many documents to find the one they want. || Some project documents fail to follow the project team’s agreed-upon naming conventions. Project members must open very few documents to find the one they want. || Documents are clearly labeled according to the project team’s agreed-upon naming conventions. Project members can easily find a document. ||
 * **File and Folder Organization** || Project files and folders lack organization. A project member typically feels lost when trying to find a document. || Project files and folders are somewhat organized according to the agreed-upon project archive structure. A project member often becomes lost when trying to locate a document. || Project files and folders are mostly organized according to the agreed-upon project archive structure. A project member sometimes becomes lost when trying to locate a document. || Project files and folders are clearly organized according to the agreed-upon project archive structure. A project member does not become lost when trying to locate a document. ||
 * **Branding of Project Files** || Files contain no branding for the project. || Some files contain branding for the project. || Most files contain branding for the project. || Files are consistently branded for the project. ||
 * **Versioning** || Information about a file’s version is missing from the filename or from within the document. || The latest version of the document can easily be determined from the filename and within the document for some project files. || The latest version of the document can easily be determined from the filename and within the document for most project files. || The latest version of the document can easily be determined from the filename and within the document for all project files. ||
 * **Readme File** || List of project documents by file name is missing. || Project readme file lists some project documents by file name. || Project readme file lists many project documents by file name. || Project readme file lists all project documents by file name. ||