ah teaches interface design (P5: Introduction)

P5: Introduction (due July 31)

On this page:

Introduction
Instructions
Grading rubric
Final submission requirements (July 31)

This is old content

Andrew is not currently teaching IAT-334. This material is left online for reference only.

Introduction

This project has you introducing and explaining one piece of your interface design project that was your responsibility.

This project is completed individually.

P5: Introduction is worth 5% of your final grade.

Instructions

Please read the weekly instructions carefully.

For this project you will be creating a brief (max 300 word) write-up explaining one aspect of either P3 or P4 that you did as an individual. The intention is that this could be taken and placed in your portfolio once completed. What you will need to include is detailed below:

An introduction providing us with:
- The context of the problem you will be talking about.
- What part of the problem you dealt with individually (not as a team).
An analysis of what part of the problem you dealt with individually describing:
- What actions did you take.
- What decisions did you make.
- Why did you take these actions and make these decisions?
An explanation of what was the outcome of what you did including:
- Why was what you did successful or unsuccessful?
- What have you learned from what you have described?
Integrate artifacts — sketches, images, videos, etc — that help explain what you did. Ensure that the write-up directly mentions and comments on the artifacts.

Some common issues that come up in these kinds of documents:

Not being focused enough on one task and talking more broadly about the project 'at large'.
Providing artifacts that are not explained or discussed and just left for the reader to determine their purpose.
Talking only about what the team did and not providing details on what you individually did.
Describing actions that were taken without giving us an understanding of why.

Put together your write-up as a PDF or webpage.

Grading rubric

Your project will be graded on the following criteria:

	A	B	C	D/F
Use of supporting artifacts (1 points): 'Do I have to guess what is referred to?'	Uses artifacts — images, quotes, process samples, etc — in combination with the text that make the thinking very clear/evident.	Uses artifacts — images, quotes, process samples, etc — that illustrate the thinking with little explanation.	Uses artifacts — images, quotes, process samples, etc — that illustrate pieces of the project with no explanation.	Uses artifacts — images, quotes, process samples, etc — that are unclearly related to the thinking with little-to-no explanation.
Reasonably concise writing (1 points): 'Can I follow the thinking? Does it stay on topic?'	The writing presents a clear narrative from beginning to end of the document without extra, un-related materials.	Each section of the document presents a clear narrative without extra, un-related materials.	Each section of the document presents a clear narrative with some extra, un-related materials.	The document presents an unclear narrative with many extra, un-related materials.
Effective argumentation (1 points): 'Am I convinced? (by the approach)'	The document uses artifacts effectively in combination with written descriptions to make a strong explanation for why a particular direction or conclusion is appropriate.	The document uses written descriptions to make a strong case for why a particular direction or conclusion is appropriate.	The document uses written descriptions that do not make a strong case for why a particular direction or conclusion is appropriate due to gaps in explanation or description of the thinking.	The document uses written arguments that do not explain why a particular direction or conclusion is appropriate.
Audience (1 points): 'Would a hiring manager understand this?'	Document uses a language understandable by a lay — naive or new-to-the-topic — audience.	Document uses a language understandable by a professional or design audience.	Document uses a language understandable by a design audience.	Document uses a language not understandable by a design audience.
Polish (1 points): 'Would a professional read this?'	Document's design — layout, type, content, interaction (if used) — allows for easy reading. Document is proofread and edited with few errors. It consistently follows the rules of Standard English.		Document's design — layout, type, content, interaction (if used) — leads to some confusion when reading. Document is proofread and edited with few errors. It consistently follows the rules of Standard English.	Document's design — layout, type, content, interaction (if used) — leads to lots of confusion when reading. Document contains many errors that interfere with meaning. It generally does not follow the rules of Standard English.

Final submission requirements (July 31)

The final submission for P5 is a document that is designed for easy and concise understanding by a non-designer (i.e. hiring manager). The format (PDF or website) is of your choosing but should demonstrate a refined and well-designed document.

Your project submission is due to Canvas before your July 31 class.

Please make sure double-check all your submitted files and URLs to ensure they can be opened. We want to avoid late or problematic submission penalties whenever possible.