MAS – Grading Style
Web Design
|
CATEGORY
|
10
|
8
|
6
|
4
|
|
Project Goal
|
Project has a clearly understood goal and provides user with expectations based on said goal.
|
Project goal is understood but user has somewhat unclear expectations of the project.
|
Project goal is somewhat clear to the user, but provides no payoff expectation to user (why would I benefit from this?)
|
Project does not appear to have a goal.
|
|
Story/Aesthetic
|
Story and Aesthetic are consistent and inform the user in a way that promotes the project goal.
|
Story and Aesthetic are mostly clear but one or two elements interfere with an understanding of the goal.
|
Story and aesthetic are inconsistent but some elements still support the story or goal
|
There is no consistency in the story or aesthetic.
|
|
Navigation Titles
|
Navigation provides consistent and understandable direction across all sections. Verb/Adverb and plurals all agree
|
Navigation is consistent but not overly understandable. Navigation may include some abstract instructions.
|
Navigation is inconsistent across sections but provides somewhat expected results.
|
Navigation is inconsistent and provides no clear direction to user.
|
|
Written Word
|
Project writing respects the viewe’rs time and informs/supports section content
|
Project writing respects the viewer’s time and usually informs/supports the section content
|
Project writing rambles but is relevant to section content
|
Project writing does not provide useful information and is irrelevant to the sections
|
|
Spelling and Grammar
|
There are no errors in spelling, punctuation or grammar.
|
There are 1-3 errors in spelling, punctuation or grammar.
|
There are 4-5 errors in spelling, punctuation or grammar.
|
There are more than 5 errors in spelling, punctuation or grammar.
|
|
Imagery
|
Imagery style and presentation match across all sections of the
project. Style and presentation support project goal and story |
Imagery style and presentation mostly match with a few elements that don’t appear to belong.
|
Imagery style and presentation don’t match but is still provide relevance within their respective sections.
|
Imagery and style do not match and interfere with the goal of the site. (Most imagery serves no purpose)
|
|
Usability:Navigation
|
Navigation is clear and understandable providing the user a clear sense of what to expect after a selection
|
Navigation is clear and understandable but provides one or two actions the user does not expect
|
Navigation is mostly clear and provides a few unexpected actions.
|
Navigation is unclear and hinders the use of the project.
|
|
Usability: Buttons
|
Buttons are easily understood and provide feedback showing their existence including rollovers and hand pointer.
|
Most buttons are easily understood as buttons and all but 1 or 2 buttons have action indicators such as a rollover state
|
Buttons do not have clear action stats but visual appearance or location still inform the user that they are actionable.
|
Buttons do not work or are hard/impossible to locate. Buttons do not
appear to be buttons and user has no understanding of how to proceed. |
|
Usability: Path
|
Project contains a clear and consistent path. User is able to
understand his/her location in the path based on navigation, visuals and instructional text (For example user is able to understand how to navigate home and that he/she is not currently at the project home) |
Project contains a clear and consistent path but user may not always
understand where they are in relation to another section. |
project path is jumbled (no sense to order) but user is able to navigate and receive content.
|
user cannot navigate the project
|
|
Project Requirements
|
Project meets original requirements set forth and project beginning.
Project is provided in digital format and includes all source files. |
Project meets 80% of original requirements. Project is provided in
digital format and includes all source files. |
project meets 50% or less of the original requirements or does not
include all source file |
Project does not meet any of the original requirements or is missing all files required to publish/evaluate project
|
|
Production: buttons
|
All buttons produce expected result when clicked. Button code does not produce any errors.
|
All but 1 or 2 buttons produce expected result when clicked. Button code does not produce any errors.
|
3 or more buttons do not appear to work or errors are produced when buttons are clicked.
|
Buttons do not work. Project is not functional.
|
|
Production: Publish
|
No errors occur when moving through the pages(javascript warnings are ok but there must be no errors).
|
Code does produce expected result, though there are a few javascript errors/warnings.
|
Some pages have errors but the navigation still works
|
Many errors occur or code errors hamper ability to use the pages.
|
|
Production: code
|
Code is used where needed to accomplish a specific goal. Project does not contain orphaned or irrelvant.
|
Some duplicate or irrelivant code but nothing that creates an error.
|
Large amounts of duplicate code or orphaned code which is not complete.
Code may create some errors but does not hamper functionality |
Duplicate or orphaned code breaks functionality.
|
Flash 1
|
CATEGORY
|
10
|
8
|
6
|
4
|
|
Project Goal
|
Project has a clearly understood goal and provides user with expectations based on said goal.
|
Project goal is understood but user has somewhat unclear expectations of the project.
|
Project goal is somewhat clear to the user, but provides no payoff expectation to user (why would I benefit from this?)
|
Project does not appear to have a goal.
|
|
Story/Aesthetic
|
Story and Aesthetic are consistent and inform the user in a way that promotes the project goal.
|
Story and Aesthetic are mostly clear but one or two elements interfere with an understanding of the goal.
|
Story and aesthetic are inconsistent but some elements still support the story or goal
|
There is no consistency in the story or aesthetic.
|
|
Navigation Titles
|
Navigation provides consistent and understandable direction across all sections. Verb/Adverb and plurals all agree
|
Navigation is consistent but not overly understandable. Navigation may include some abstract instructions.
|
Navigation is inconsistent across sections but provides somewhat expected results.
|
Navigation is inconsistent and provides no clear direction to user.
|
|
Written Word
|
Project writing respects the viewe’rs time and informs/supports section content
|
Project writing respects the viewer’s time and usually informs/supports the section content
|
Project writing rambles but is relevant to section content
|
Project writing does not provide useful information and is irrelevant to the sections
|
|
Spelling and Grammar
|
There are no errors in spelling, punctuation or grammar.
|
There are 1-3 errors in spelling, punctuation or grammar.
|
There are 4-5 errors in spelling, punctuation or grammar.
|
There are more than 5 errors in spelling, punctuation or grammar.
|
|
Imagery
|
Imagery style and presentation match across all sections of the
project. Style and presentation support project goal and story |
Imagery style and presentation mostly match with a few elements that don’t appear to belong.
|
Imagery style and presentation don’t match but is still provide relevance within their respective sections.
|
Imagery and style do not match and interfere with the goal of the site. (Most imagery serves no purpose)
|
|
Usability:Navigation
|
Navigation is clear and understandable providing the user a clear sense of what to expect after a selection
|
Navigation is clear and understandable but provides one or two actions the user does not expect
|
Navigation is mostly clear and provides a few unexpected actions.
|
Navigation is unclear and hinders the use of the project.
|
|
Usability: Buttons
|
Buttons are easily understood and provide feedback showing their existence including rollovers and hand pointer.
|
Most buttons are easily understood as buttons and all but 1 or 2 buttons have action indicators such as a rollover state
|
Buttons do not have clear action stats but visual appearance or location still inform the user that they are actionable.
|
Buttons do not work or are hard/impossible to locate. Buttons do not
appear to be buttons and user has no understanding of how to proceed. |
|
Usability: Path
|
Project contains a clear and consistent path. User is able to
understand his/her location in the path based on navigation, visuals and instructional text (For example user is able to understand how to navigate home and that he/she is not currently at the project home) |
Project contains a clear and consistent path but user may not always
understand where they are in relation to another section. |
project path is jumbled (no sense to order) but user is able to navigate and receive content.
|
user cannot navigate the project
|
|
Project Requirements
|
Project meets original requirements set forth and project beginning.
Project is provided in digital format and includes all source files (.fla, fonts) |
Project meets 80% of original requirements. Project is provided in
digital format and includes all source files (.fla, fonts) |
project meets 50% or less of the original requirements or does not
include all source file (missing .fla, missing fonts required for publish, etc) |
Project does not meet any of the original requirements or is missing all files required to publish/evaluate project
|
|
Production: buttons
|
All buttons produce expected result when clicked. Button code does not produce any errors.
|
All but 1 or 2 buttons produce expected result when clicked. Button code does not produce any errors.
|
3 or more buttons do not appear to work or errors are produced when buttons are clicked.
|
Buttons do not work. Project can not have any interaction.
|
|
Production: Publish
|
No errors occur when project is published to a swf. Code produces expected result (stop, play, etc)
|
Code does not produce expected result, but no errors occur when published.
|
Code produces errors on publish, but the errors do not hamper use of the project
|
Many code errors occur or code errors hamper ability to publish/use a project
|
|
Production: code
|
Code is used where needed to accomplish a specific goal. Project does not contain orphaned or duplicate code
|
Some duplicate code but nothing that creates and error
|
Large amounts of duplicate code or orphaned code which is not complete.
Code may create some errors but does not hamper publish or use of project |
duplicate or orphaned code breaks publish and project cannot be used.
|
|
Production: Timeline
|
Timeline does not contain extra content that is not accessible in final
published version. Excess layers and frames have been removed. (excess is any frame/layer that doesn’t serve a purpose. IE empty frames without script or a label) |
Timeline may contain extra layers or frames but no extra content that cannot be accessed in the final published version.
|
Timeline contains excess content that is inaccessible in the final published version.
|
Timeline and content are a mess. Timeline contains large amounts of
excess or duplicate content that is inaccessible in the published version and excess layers and empty frames |