Marking Outline for Assignment 2

 
 
Overall Marking
Over the entire assignment deduct marks for the following global
errors
 
The design should be 
1. Internally consistent (stuff from one section to next make sense)
2. Authentic and Honest (eg not reverse engineered, an attempt at
understanding the users and designing for them).  
3. A clearly auditable trail of decisions from one step to the
next.  Doesn’t necessarily need to be cross indexed but you can see
the decision flow from one section to the next.   If something is
changed later on should be clear why (and its ok to do this). 
4. Evidence of thought, empathy and application, taking the
assessment seriously,  not started late
Superficial components should fail as they show no evidence of
application of skills
 
 
 
 
Task 1. 
5%
Should target the outcome of this assignment
(eg stakeholders should be directly relevant to the two sub
systems). 
 
Should have a list of stakeholders and any notes regarding their
needs/wants on the system and how they may impact the design
and the usage of the final product.   
 
This will not be the same list as the personas later but there will be
a significant overlap.   I would expect more stakeholders on this list
and that will be refined down to the personas later by eliminating
non user stakeholders, and combining similar user stakeholders. 
 
A pass mark for this section should be a good well rounded list with
a reasonable set of stakeholders that is consistent with the
information they received.  
 
 
 
Task 2
10%
Mark this similar to assignment 1. 
The interview outline should try to get to understand the users of
the system 
Should ask the questions you need answered to build a good design 
Should try to fill in demographies of the user 
Eg what did you study 
What do you like 
what irritates you 
Questions should be deep and probing some open ended some close
ended questions. 
 
A pass mark for this section would be an interview plan that will
extract a reasonable amount of depth about the users. 
 
 
 
Task 3 
10%
Basic questions form Task 2 and answers that have been
generated.  Should be authentic and rich.   If the questions and
answers are superficial short and haven’t been thought of should fail
this section. 
 
A pass mark for this section would be reasonable length answers to
the questions form task 2 that shows the UX team what the users
are like. 
 
 
 
Task 4
15%
A fairly complete set of user stories that would handle the tasks that
the two subsystems should do.   We will discuss them in the
markers meeting.  Clearly this is where people who are not taking
the assignment seriously will do a few user stories and think they
covered everything they need.   A good solution to this will have
surprises of tasks that you might not have thought of as well.   
 
A pass in this would be the minimum system functionality
covered.   A great solution is secondary functions that might not be
obvious when you first look at the assignment. 
 
 
 
Task 5
10%
Using stakeholder list as a start the students should have broken
that down to the key list of roles of people using the system.   Then
a group of personas that represent the users of the system. 
 
A pass will have the minimum number of personas with some
demographic, etc.. information enough to fill in the blanks your
self.   A great solution will have a deep persona that really makes
you feel who the users is and how they will view the system. 
 
 
Task 6
5%
A table mapped between the user stories to the personas.   
 
A pass solution would just be the table.  A great solution is
annotations on the table showing where some user stories are
essentially the same and can be combined.  
 
 
Task 7
15%
A set of contextual storyboards.   They should avoid the design of
the interface and concentrate on the context of use.  In this
assignment imagine two ambos driving to a scene for
example.  Stress, traffic, speed etc… the storyboards should reflect
that. 
 
A pass solution would give a complete set of storyboards.   A great
solution really gets the detail of how they will use the product. 
 
 
Task 8 
10%
The structure of the system + look and feel 
 
A pass solution would be a chart for structure and some basic fonts,
colours etc.. A great solution is an aesthetic with a well designed
slick IA. 
 
 
Task 9 
5%
A backlog 
 
A pass solution would be a priority list of user stories.  A great
solution would be a well justified set of priority guides (eg a
justification of the ordering technique).
 
 
Task 10 
15%
An adobe XD set of designs that map back to the previous 9
tasks.  They should be the logical extension of all the stuff in the
previous sections. 
 
A pass solution will have a minimum number of screens and be
designed in accordance with the previous tasks.  (eg look and feel
IA etc..).   A great design will be a slick well laid out and placed
design.