Grading+Rubrics

= Grading Rubrics =

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

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

Mobile Application Design Rubric (120 points)
 * Client Goals (24 points)
 * User Experience (28 points)
 * Visual Design (16 points)
 * Technical (28 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 Brief 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. ||
 * **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 (18 + 2 for creating document=20 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):

Mobile Application Design Rubric
Designer: Project:

Total Client Goals Points (24 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 brief. || Intended message fulfills some goals and objectives as outlined in project brief. || Intended message fulfills most goals and objectives as outlined in project brief. || Intended message fulfills all goals and objectives as outlined in project brief. ||
 * **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 brief. || The author has put information in the Web site but it does not fulfill the business objectives as outlined in the project brief. || The author has tried to make the content of this app fulfill the business objectives as outlined in the project brief. || The author has made an exceptional attempt to make the content of this app fulfill the business objectives as outlined in the project brief. ||
 * **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 brief. || The author has put information in the app but the organization of the information does not fulfill the business objectives as outlined in the project brief. || The author has tried to organize the content of this app to fulfill the business objectives as outlined in the project brief. || The author has made an exceptional attempt to organize the content of this app to fulfill the business objectives as outlined in the project brief. ||
 * **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 (28 points):

 * **User Experience** || **1 Points** || **2 Points** || **3 Points** || **4 Points** ||
 * **Message** || Intended message is missing. || There is little evidence that the intended message is 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 app but it is not written and presented for the target audience(s). || The author has tried to make the content of this app for the people for whom it is intended. || The author has made an exceptional attempt to make the content of this app for 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 app but it is not organized for the target audience(s). || The author has tried to organize the content of this app 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** || Navigation items do not clearly describe where the reader will end up. A user typically feels confused. || Some navigation items are labeled, allowing the reader to move from a view to related views. A user sometimes gets confused. || Many navigation items are labeled, allowing the reader to move from a view to related views. A user rarely gets confused. || All navigation items are clearly labeled and consistently placed allowing the reader to easily move from a view to related views, and take the reader where s/he expects to go. A user does not get confused. ||
 * **Spelling and Grammar** || There are more than 5 errors in spelling, punctuation or grammar in the final draft of the app. || There are 4-5 errors in spelling, punctuation or grammar in the final draft of the app. || There are 1-3 errors in spelling, punctuation or grammar in the final draft of the app. || There are no errors in spelling, punctuation or grammar in the final draft of the app. ||
 * **Sounds** || Music, audio clips and/or sounds were seemingly used randomly OR typically detracted from the overall app. || Music, audio clips and/or sounds are thoughtfully edited and used, but 1 or 2 detracted from the overall app. || 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. ||
 * **View Titles** || View titles are missing. || Some views have clear titles. || Many views have clear titles. || All views have clear titles. ||

Total Visual Design Points (16 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 Brief** || 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. ||
 * **Icons** || Icons seem randomly chosen, are of low quality, OR distract the reader. || Some icons are related to the theme/purpose of the app and enhance reader interest or understanding. || Many icons are related to the theme/purpose of the app and enhance reader interest or understanding. || Icons are related to the theme/purpose of the app 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 app, are of excellent quality and enhance reader interest or understanding. ||