【COMPSCI5060】computer security
Code of Assessment Rules for Coursework Submission
Deadlines for the submission of coursework which is to be formally assessed will be published in course documentation, and work which is submitted later than the deadline will be subject to penalty asset out below.
The primary grade and secondary band awarded for coursework which is submitted after the published deadline will be calculated as follows:
(i) in respect of work submitted not more than five working days after the deadline
a. the work will be assessed in the usual way;
b. the primary grade and secondary band so determined will then be reduced by two secondary bands
for each working day (or part of a working day) the work was submitted late.
(ii) work submitted more than five working days after the deadline will be awarded Grade H.
Penalties for late submission of coursework will not be imposed if good cause is established for the late submission. You should submit documents supporting good cause via MyCampus.
Group Project Overview
The group project for Human Centred Security M requires a) proposing ideas for usable security and/or privacy protection mechanisms, b) implementing a prototype (can be a paper prototype or a computer prototype), c) evaluating the usability and/or security of the prototype in a user study, d) writing a report on the implementation and the evaluation of the results and d) preparing a video presentation that demonstrates the prototype, and summarizes the study procedure, the most important results, and the learned lessons. Detailed instructions for each part are explained below.
The group project is 30% of the final course grade. The expectation is that strong performance in the group project demonstrates the team’s ability to achieve the following Learning Outcomes:
• Examine a given context and design an appropriate security solution and be able to justify your choices (Intended Learning Outcome 2) .
• Identify causative effects of particular human behaviours in a security setting, explain how these can be influenced (Intended Learning Outcome 3) .
• Design and analyse the results of user studies to evaluate the usability and security of computing systems (Intended Learning Outcome 7) .
Evaluation: The aim here is to evaluate the usability and security of the concept you have implemented.
• Define a study design and study procedure. Think of the aspects of your implementation that need to be evaluated. What are the independent and dependent variables? And what are the conditions? What is the baseline condition? The teams should engage with literature and the “Research methods in Usable Security” lecture for inspiration on how to define the study design and study procedure.
• Evaluate all the features that you prototypedina user study with 6 or more participants.
• Focus on identifying the pros and cons of each experimental condition and collect general feedback about the idea.
• Remember that receiving negative feedback does not result in losing marks as long as you demonstrate that you’ve taken reasonable precautions in the implementation. For example, if you provide a convincing argument why a design decision was taken, but the evaluation results show that it resulted in less usability, then this is not regarded as a shortcoming of your work.
• Define tasks for the participants to make sure they try all the concepts, modes and viewsyou’ve implemented. Like reality, the tasks should tell the participants what they should achieve rather than how to achieve it. The ideal interface is usable and intuitive enough for users to figure out the how on their own.
• The teams are free to use qualitative evaluation measures (e.g., questionnaires, interviews, etc.), quantitative evaluation measures (e.g., usage logs, task completion accuracy, task completion time, etc.), or a combination of both, as long as the methods result in a rigorous evaluation of the implemented concepts.
See the Deliverables section below for details on what to submit by the deadline of this milestone.