Critique
Introduction
In this assessment piece we want you to evaluate a particular User Centred Design practice or theory (as presented in an
academic article) and assess its importance or relevance to software development practice. This is an independent research
project.
Topics

Chose ONE of the following articles for your critique:
Dray, S.M., 2014, ‘Questioning Assumptions: UX Research That Really Matters’, interactions, 21(2), pp. 82-5.
Dow, S., 2011, ‘How prototyping practices affect design results’, interactions, 18(3), pp. 54-9.
Bias, R.G., Kortum, P., Sauro, J. & Gillan, D., 2013, ‘Clothing the Naked Emperor: The Unfulfilled Promise of the
Science of Usability’, interactions, 20(6), pp. 72-7.
You will need to download your chosen reference from the ACM Digital Library database. You can access the references via
the library website.
Learning Objectives
In this report you must show evidence of the following Learning Objectives:
1. Critique current issues in User Centred Design and their implications for software development practice.
You will also be assessed according to:
• your analysis and research skills,
• your writing skills.
Resources
Interactions Magazine (where the articles are published)
Swinburne Library Human-Computer Interaction Reference Guide (in particular Databases/ACM Digital Library)
UNSW Academic Support website has some excellent advice about how to write a critical review and writing for academia in
general. Also see Monash Universities Learning Support website for more assistance with academic writing.
Swinburne Library guide to how to do referencing
COS70004 Usability
Swinburne University of Technology
Critique- 1
…continues next page
Table 1: Specifications
Specifications

Details
% of Unit10%
Number of Marks10
Number of PeopleThis is an INDIVIDUAL report.
DeliverablesWritten critique
AudienceThe audience for this report is a manager who wants you to assess the value of a User
Centered Design practice or theory (as presented in an academic article).
Length1,500-2,000 words (not including tables, figures, references or appendices)
Submission
Instructions
Submit report to Blackboard on Turnitin
FeedbackFeedback will be provided as per detailed on Blackboard or via swin email. Feedback
should be interpreted in relation to marking criteria.
Suggested Assessment Structure
This is a suggested format for this assessment piece. Variations are acceptable as long as your critique broadly addresses
the issues identified below.
Title Page
The title page contains:
• Title of paper critiqued and journal publication information
• The date the report due.
• The unit name.
• Tutorial day and time.
• Name of student and ID number
• Number of words (not including tables, figures, references or appendices)
Introduction
Summarise the main points of the article (i.e., the article/research paper, not your critique).
COS70004 Usability
Swinburne University of Technology
Critique- 2
Significance
Issues to consider in this section:
What is the purpose of the article?
Is the problem clearly stated?
Is the problem important?
Argument and use of evidence
Issues to consider in this section:
What claims are made?
What evidence is used to support their claims?
How effective is the evidence?

Implications
Issues to consider in this section:
What are the implications of the article for the software development community?
What are the implications of the article to you?
How has this article changed your views?
How could you see applying these ideas to your work practice, or the work practice of your organization?
Conclusions
Summarise your critique
References
A detailed list of material referenced in the text of the assessment. Failure to appropriately reference material from previously
published sources such as the web or journal articles etc (i.e., plagiarism) will result in a FAIL grade. The list of references
must be presented using approved referencing style such as Harvard or APS (see Blackboard/Assessment/ Guide to
Referencing). Include (appropriately referenced) web pages (include data accessed). Include references for any images
used. It should be clear whether you created an image or downloaded it from another source. For example this document
referenced Courage and Baxter (2005), which using APS style, would be referenced as:
Courage, C. & Baxter, K. (2005). Understanding your users: A practical guide to user requirements, methods, tools and
techniques. San Francisco, CA: Morgan-Kaufmann.
* Note: Plagiarism is the submission of work that is not your own for which you claim credit. Work in which plagiarism is
evident will be given an overall fail grade. Please see Avoiding Plagiarism (http://www.swinburne.edu.au/plagiarism).
COS70004 Usability

ScholarMatic: Explanation & Answer

Your ready answer from a verified tutor is just a click away for as little as $14.99

---

  

Click Order Now to get 100% Original Answer Customized to your instructions!