Jason Withrow - INP Instructional Website
INP 253: Project Grading Criteria
Use Case Content (15 points)
- Use cases are detailed, providing a careful walkthrough of the process, its alternate paths, and technical details.
- A sufficient amount of use cases are provided to address all aspects of the functionality.
- Use cases address and resolve the challenges presented by the assignment.
Prototype Content (15 points)
- Prototypes need to be medium to high fidelity.
- Digital wireframes or XHTML versions of the screens are two possibilities.
- Regardless of the medium chosen, the prototype needs to clearly convey how the application will work.
- Most importantly, the design needs to be elegant as well as usable and accessible. Many solutions provide an adequate user experience; to achieve full points in this section create a design that provides surpassing user experience.
Presentation (10 points)
- Project Grade Sheet (PDF, 8.7k) is filled out and stapled to the use case document as the first page.
- Digital wireframes (if created) should be in the flow of the document, as shown in the use case examples.
- If you created your prototypes in XHTML or another format upload those files to the student web server. Include the URL of the file(s) after the associated use case.
- Visual quality of the prototypes needs to be at a professional level.
- Each project will have a cover page, table of contents, and then the use cases. There is no executive summary because this is a document for the developers rather than the client.
- Make sure that the pages are stapled together, with a single staple in the upper left corner.
- Include your name on the cover page.
- Include a header that indicates the project name.
- Provide the page number in either the header or the footer.
- Font sizes are within a normal reading range, are consistent, and naturally progress from larger to smaller sizes in headings and subheadings, respectively.
- Single-spaced lines are used.
- Paragraph content is flush left.
- Content is free of typos and grammatical issues.
- Use cases are written in the third person.
- First person ("I", "We", "Our") and second person ("You", "Your") phrasing is avoided.
- Sentences flow well; awkward phrasing is avoided.
- Slang terms are avoided.
- The tone of the writing is professional and not conversational.
- Margins are acceptable and consistent.
- No other visual inconsistencies are present (such as inconsistent line spacing, inconsistent indentation, inconsistent text sizes for headings at a given level, inconsistent usage of fonts, etc.).
- Do not submit your project in a binder or slip-cover.