Skip to main content
Unit outline_

INFO2222: Computing 2 Usability and Security

Semester 1, 2021 [Normal day] - Camperdown/Darlington, Sydney

This unit provides an integrated treatment of two critical topics for a computing professional: human computer interaction (HCI) and security. The techniques and core ideas of HCI will be studied with a particular focus on examples and case studies related to security. This unit builds the students' awareness of the deep challenges in creating computing systems that can meet people's needs for both HCI and security. It will develop basic skills to evaluate systems for their effectiveness in meeting people's needs within the contexts of their use, building knowledge of common mistakes in systems, and approaches to avoid those mistakes.

Unit details and rules

Academic unit Computer Science
Credit points 6
Prerequisites
? 
(INFO1103 OR INFO1105 OR INFO1905 OR INFO1113) AND (INFO1111 OR INFO1711 OR ENGG1111 OR ENGD1000 OF ENGG1805)
Corequisites
? 
None
Prohibitions
? 
None
Assumed knowledge
? 

None

Available to study abroad and exchange students

Yes

Teaching staff

Coordinator Sue Chng, sue.chng@sydney.edu.au
Lecturer(s) Sue Chng, sue.chng@sydney.edu.au
Alan Robertson, alan.robertson@sydney.edu.au
Type Description Weight Due Length
Final exam (Take-home short release) Type D final exam hurdle task Final Exam
Open-book computer exam.
50% Formal exam period 3 hours
Outcomes assessed: LO2 LO5 LO6 LO7 LO8 LO9 LO10 LO11 LO12 LO13
Assignment Logbook
Outputs created from independent study.
20% Please select a valid week from the list below Multiple components
Outcomes assessed: LO2 LO4 LO5 LO6 LO7 LO8 LO9 LO10 LO11 LO12 LO13
Assignment group assignment Project - Usability
Design report and system demonstration.
15% Week 06 4000 words/ 20 minutes
Outcomes assessed: LO1 LO3 LO4 LO5 LO6 LO7 LO8 LO9
Assignment group assignment Project - Security
Design report and system demonstration.
15% Week 13 4000 words/ 20 minutes
Outcomes assessed: LO1 LO3 LO10 LO11 LO12 LO13
hurdle task = hurdle task ?
group assignment = group assignment ?
Type D final exam = Type D final exam ?

Assessment summary

Project – Students work in a team to design and develop a ‘usable and secure’ website. Each student will be required to review their own performance and that of each team members using SparkPlus. SparkPlus evaluations are due on W4, W6 and W13. Individual marks for group assessments will be determined using these reviews, logbook submissions and tutorial participation. 

Logbook – Personal logbook to keep track of learning and project contributions. Entries must be dated and include a short paragraph (not more than 200 words) of your thoughts. Students are expected to maintain a Git repository of their entries and submit a copy of their logbook for formative assessment every fortnight starting from W2. Logbooks will be summatively assessed on Week 6 and Week 13.

Final Exam – Open book online exam that assesses all contents covered in the semester. Students must score at least 40% in the final exam to pass the unit (see Pass requirements).

Detailed information for each assessment can be found on Canvas.

Conditions for pass in this unit:

  • At least 40% in the progressive marks
  • At least 40% in the final exam
  • At least 50% total

Assessment criteria

The University awards common result grades, set out in the Coursework Policy 2014 (Schedule 1).

As a general guide, a high distinction indicates work of an exceptional standard, a distinction a very high standard, a credit a good standard, and a pass an acceptable standard.

Result name

Mark range

Description

High distinction

85 - 100

Awarded when you demonstrate the learning outcomes for the unit at an exceptional standard, as defined by grade descriptors or exemplars outlined by your faculty or school. 

Distinction

75 - 84

Awarded when you demonstrate the learning outcomes for the unit at a very high standard, as defined by grade descriptors or exemplars outlined by your faculty or school.

Credit

65 - 74

Awarded when you demonstrate the learning outcomes for the unit at a good standard, as defined by grade descriptors or exemplars outlined by your faculty or school.

Pass

50 - 64

Awarded when you demonstrate the learning outcomes for the unit at an acceptable standard, as defined by grade descriptors or exemplars outlined by your faculty or school.
Fail 0 - 49 When you don’t meet the learning outcomes of the unit to a satisfactory standard.

Minimum Pass Requirement:

It is a policy of the School of Computer Science that in order to pass this unit, a student must achieve at least 40% in the written examination. For subjects without a final exam, the 40% minimum requirement applies to the corresponding major assessment component specified by the lecturer. A student must also achieve an overall final mark of 50 or more. Any student not meeting these requirements may be given a maximum final mark of no more than 45 regardless of their average.

For more information see guide to grades.

Late submission

In accordance with University policy, these penalties apply when written work is submitted after 11:59pm on the due date:

  • Deduction of 5% of the maximum mark for each calendar day after the due date.
  • After ten calendar days late, a mark of zero will be awarded.

Academic integrity

The Current Student website  provides information on academic integrity and the resources available to all students. The University expects students and staff to act ethically and honestly and will treat all allegations of academic integrity breaches seriously.  

We use similarity detection software to detect potential instances of plagiarism or other forms of academic integrity breach. If such matches indicate evidence of plagiarism or other forms of academic integrity breaches, your teacher is required to report your work for further investigation.

You may only use artificial intelligence and writing assistance tools in assessment tasks if you are permitted to by your unit coordinator, and if you do use them, you must also acknowledge this in your work, either in a footnote or an acknowledgement section.

Studiosity is permitted for postgraduate units unless otherwise indicated by the unit coordinator. The use of this service must be acknowledged in your submission.

Simple extensions

If you encounter a problem submitting your work on time, you may be able to apply for an extension of five calendar days through a simple extension.  The application process will be different depending on the type of assessment and extensions cannot be granted for some assessment types like exams.

Special consideration

If exceptional circumstances mean you can’t complete an assessment, you need consideration for a longer period of time, or if you have essential commitments which impact your performance in an assessment, you may be eligible for special consideration or special arrangements.

Special consideration applications will not be affected by a simple extension application.

Using AI responsibly

Co-created with students, AI in Education includes lots of helpful examples of how students use generative AI tools to support their learning. It explains how generative AI works, the different tools available and how to use them responsibly and productively.

WK Topic Learning activity Learning outcomes
Week 01 Introduction and the usability context: introduction to the unit and to the challenges in enabling the use of system features by humans. Lecture and tutorial (4 hr) LO1 LO4 LO8
Week 02 Investigating users and their importance in understanding usability Lecture and tutorial (4 hr) LO1 LO4 LO8
Week 03 Usability in Design and Implementation: How to perform the processes of usability engineering in the context of software and system engineering Lecture and tutorial (4 hr) LO1 LO4 LO5 LO6
Week 04 1. Human factors - individual physiology, cognition and broader psychology. 2. Accessibility - legal and ethical requirement Lecture and tutorial (4 hr) LO1 LO3 LO4 LO5 LO7 LO9
Week 05 1. Handling human errors 2. Social and organization context Lecture and tutorial (4 hr) LO3 LO5 LO7 LO8
Week 06 Usability and security - a compromise? Security terminology, identification and authentication Lecture and tutorial (4 hr) LO1 LO2 LO3 LO10
Week 07 Web and database security Lecture and tutorial (4 hr) LO1 LO2 LO3 LO13
Week 08 Cryptography Lecture and tutorial (4 hr) LO1 LO2 LO3 LO13
Week 09 Network security Lecture and tutorial (4 hr) LO1 LO2 LO3 LO13
Week 10 Software and system security Lecture and tutorial (4 hr) LO1 LO2 LO3 LO12
Week 11 Physical and operational security Lecture and tutorial (4 hr) LO1 LO2 LO3 LO11 LO12 LO13
Week 12 Privacy, legal and ethical issues Lecture and tutorial (4 hr) LO1 LO2 LO3 LO11 LO12 LO13
Week 13 Review and revision Lecture and tutorial (4 hr) LO2 LO5 LO6 LO7 LO8 LO9 LO10 LO11 LO12

Attendance and class requirements

Each week, students must:

  • Perform own independent study by reviewing provided materials, reading the required sections of literature and completing weekly exercises in the tutorial sheet.
  • Be prepared (completed task/research/background reading) for all face-to-face sessions (online/physical) with teaching staff and group project members.
  • Attend and participate in all classes scheduled.

Tutorials will NOT be recorded. 

 

Study commitment

Typically, there is a minimum expectation of 1.5-2 hours of student effort per week per credit point for units of study offered over a full semester. For a 6 credit point unit, this equates to roughly 120-150 hours of student effort in total.

Learning outcomes are what students know, understand and are able to do on completion of a unit of study. They are aligned with the University's graduate qualities and are assessed as part of the curriculum.

At the completion of this unit, you should be able to:

  • LO1. work effectively in a team
  • LO2. understand the balance between risk, achieved security, and cost; experience with threat modelling and risk analysis as tools to choose this balance for a given system
  • LO3. produce written reports that evaluate a web site for usability and security
  • LO4. experience building a prototype interface, and learning aspects of it independently from provided resources
  • LO5. knowledge of design guidelines and how to apply them to design user interfaces
  • LO6. use iterative prototyping, with design and evaluation cycles, to explore a design space
  • LO7. demonstrate knowledge of a core set of cognitive, physiological, organisational, and other key human factors and their implications for interface design
  • LO8. demonstrate awareness of the major challenges for designing effective user interfaces, including factors associated with individual users, cultural and organisational contexts
  • LO9. evaluate interfaces, following a user-based technique
  • LO10. understand common security terminology in security literature
  • LO11. understand different ways in which security of computer systems can be compromised, e.g. physically, remotely, operationally (esp. social engineering); and relate specific attack scenarios to the major security goals such as authentication, integrity, secrecy, non-repudiation
  • LO12. understand the major challenges for security of programs, information, computers and networks, and ability to avoid most egregious (typical) flaws in designing and operating IT systems
  • LO13. demonstrate a high-level knowledge of common approaches to achieve security goals in computer systems (environment control, communications security and OS security, secure operational practices).

Graduate qualities

The graduate qualities are the qualities and skills that all University of Sydney graduates must demonstrate on successful completion of an award course. As a future Sydney graduate, the set of qualities have been designed to equip you for the contemporary world.

GQ1 Depth of disciplinary expertise

Deep disciplinary expertise is the ability to integrate and rigorously apply knowledge, understanding and skills of a recognised discipline defined by scholarly activity, as well as familiarity with evolving practice of the discipline.

GQ2 Critical thinking and problem solving

Critical thinking and problem solving are the questioning of ideas, evidence and assumptions in order to propose and evaluate hypotheses or alternative arguments before formulating a conclusion or a solution to an identified problem.

GQ3 Oral and written communication

Effective communication, in both oral and written form, is the clear exchange of meaning in a manner that is appropriate to audience and context.

GQ4 Information and digital literacy

Information and digital literacy is the ability to locate, interpret, evaluate, manage, adapt, integrate, create and convey information using appropriate resources, tools and strategies.

GQ5 Inventiveness

Generating novel ideas and solutions.

GQ6 Cultural competence

Cultural Competence is the ability to actively, ethically, respectfully, and successfully engage across and between cultures. In the Australian context, this includes and celebrates Aboriginal and Torres Strait Islander cultures, knowledge systems, and a mature understanding of contemporary issues.

GQ7 Interdisciplinary effectiveness

Interdisciplinary effectiveness is the integration and synthesis of multiple viewpoints and practices, working effectively across disciplinary boundaries.

GQ8 Integrated professional, ethical, and personal identity

An integrated professional, ethical and personal identity is understanding the interaction between one’s personal and professional selves in an ethical context.

GQ9 Influence

Engaging others in a process, idea or vision.

Outcome map

Learning outcomes Graduate qualities
GQ1 GQ2 GQ3 GQ4 GQ5 GQ6 GQ7 GQ8 GQ9

This section outlines changes made to this unit following staff and student reviews.

Changes were made to the assessment structure.

 

IMPORTANT: School policy relating to Academic Dishonesty and Plagiarism.

In assessing a piece of submitted work, the School of Computer Science may reproduce it entirely, may provide a copy to another member of faculty, and/or to an external plagiarism checking service or in-house computer program and may also maintain a copy of the assignment for future checking purposes and/or allow an external service to do so.


Computer programming assignments may be checked by specialist code similarity detection software. The Faculty of Engineering currently uses the MOSS similarity detection engine (see http://theory.stanford.edu/~aiken/moss/), or the similarity report available in ED (edstem.org). These programs work in a similar way to Turnitin in that they check for similarity against a database of previously submitted assignments and code available on the internet, but they have added functionality to detect cases of similarity of holistic code structure in cases such as global search and replace of variable names, reordering of lines, changing of comment lines, and the use of white space.

All written assignments submitted in this unit of study will be submitted to the similarity detecting software program known as Turnitin. Turnitin searches for matches between text in your written assessment task and text sourced from the Internet, published works and assignments that have previously been submitted to Turnitin for analysis.

There will always be some degree of text-matching when using Turnitin. Text-matching may occur in use of direct quotations, technical terms and phrases, or the listing of bibliographic material. This does not mean you will automatically be accused of academic dishonesty or plagiarism, although Turnitin reports may be used as evidence in academic dishonesty and plagiarism decision-making processes.

Disclaimer

The University reserves the right to amend units of study or no longer offer certain units, including where there are low enrolment numbers.

To help you understand common terms that we use at the University, we offer an online glossary.