INFO2222 Computing 2 Usability and Security - Project: Usability Part
INFO2222 Project: Usability Part
1 Usability Project Description
Due 19th of May 2024 at 11:59 PM AEST This assignment is worth 15% of your final grade.
Extend the basic E2E secure messaging app to be a website support system for undergraduate School of Computer Science University of Sydney students to share experiences and seek the necessary help (if needed) for their academic studies. It should also have a knowledge repository where students can share reading or learning materials that they found useful to understand challenging computing concepts.
You already have an account and messaging service that allows pair-wise communication among students and to specific academic/administrative staff who they add as friends. New additional requirements are as below:
Basic Functionality Requirements:
|
15 marks |
1. Messaging and friends list enhancements
|
|
5 marks |
3. User account permissions system – student and staff accounts, with different types of staff accounts: academics, administrative staff and admin user. The role should be displayed in the user’s profile and on any posts they make, viewable to all. |
|
30 marks |
4. Knowledge repository
|
5 marks 5. One specific user function – depending on your user investigation
Additional Criteria:
User investigation – PACT analysis Navigation design – Card sorting exercise
|
8 marks |
Low-fidelity prototype testing |
|
7 marks |
Incremental development plan and outline of evaluations conducted
|
10 marks
Demonstration and overall website design and usability rating
Total: 100 marks
2 Recommended Activities
Step 1: User Investigation.
During this phase, you are to investigate a chosen user group to determine what they need from your website. To make things easier, you can concern yourself with only a single type of user:
-
Students – this can range from any students starting just starting their program of studies to final year students. It can also include students transferring into a computing program from other USyd schools; OR
-
Alumni – graduates who are willing to give back to their alma mater and to guide their juniors; OR
-
SCS/administrative staff – this can include program managers, academic advisors and adminis- trative staff responsible for the running of program operations that affects students’ academic performance.
Perform a PACT analysis for your chosen group. You will likely still find that your selected group is too large and complex but your analysis should help you identify what you know about your target group and what you need to find out during your investigation to narrow your group down to a single persona.
Expected outputs:
-
Outline of the user investigation process (surveys/interviews, how many?) that your group has
used to narrow down your target user.
-
Research materials used to collect data about your target group
-
A persona document outlining your target persona
-
Based on your findings above, gather content (collection of documents or articles) relevant to
the interests of your target persona. Ensure you cite all sources and quote where you have copied text verbatim. This content will be used in the example posts made to showcase your knowledgebase’s functionality.
Step 2: Navigation design.
Your design plan will need to include the user actions stated in the core requirements in addition to actions discovered specifically for your own target user group (user specific functions). Conduct a card sorting session with some of your target user group and use your results to create the navigation map (site map) of your website.
Expected outputs:
-
Outline of card sorting session along with all materials that were used.
-
Information architecture of your website
Step 3: Design-Evaluate – Low Fidelity or High Fidelity Prototype (paper or digital):
Based on the information architecture that you have from the previous phase, brainstorm and create sketches of your website. Create a prototype of the best design and perform a guerrilla test with target users using this prototype. Each of your team members should take part in the guerrilla test, and there should be at least one participant outside of your team.
Expected outputs:
-
A prioritized list of features – these do not need to all be developed in the actual web
application, but are more like a ‘wish list’ of things that would enhance the usability and user experience. It is expected that there would not be enough time to actually develop all of them in this assignment project.
-
Outline steps taken to determine the ‘best’ design to be developed
-
Paper or digital prototype – wireframe diagrams
-
Mini-report that outlines how the guerrilla test was conducted, raw results, materials used and
findings of the test.
Step 4: Design-Evaluate (Initial Implementation of Prototype)
Focus on converting your (improved) prototype (paper or digital) to the real web server. Do this incrementally and perform evaluations (e.g., think aloud test) to ensure that you are on the right track.
It is recommended that you create a github repository to track changes to your codebase. Share it with your tutor and include the link in your report.
Expected outputs:
• Incremental development plan (two iterations at least)
o Assume each iteration lasts for 2 weeks, eg. iteration #1: weeks 9-10, iteration #2: weeks 11-12. The project is due at the beginning of week 13.
o Which features were completed in the first iteration? What was the result of the user testing after the first iteration? Which features were prioritised for the second iteration?
-
Outline of evaluations conducted
-
Demonstration of the functionalities mentioned at the beginning: admin roles, the user specific
function etc.
-
Any thoughts and self-evaluation about how the team worked together and each member’s
contribution to the development process.
Your output in Step 4 does not need to be perfect, we care more about your improvements over each iteration and the evaluations conducted to improve usability.
Step 5: Final report
-
It is a collection of all the previous outputs in a neat format.
-
If one person did not contribute to the project, please state this and inform your tutor
-
Your final submission should consist of two files: a pdf file containing the report and a zip file
containing your code and other artifacts.
Submission deadline: The report for this component (usability part) and corresponding code is dueon Sunday midnight of W12.
3 Demonstration
You are required to give a demonstration during class after you’ve submitted. During the demonstration, you will show the functionality working, including usability features you have implemented and explain how they work. Your tutor may ask you questions about the sections of code you wrote and to explain how a particular feature is accomplished in the code. Failure to attend for the demonstration will result in a deduction of 20 marks.
4 Group Member Contribution Adjustment
Marks may be adjusted among group members based on each’s contribution. Each group member will give a confidential rating of the other’s contribution percentage to inform the teacher’s assessment of their participation in the project work. There will be surveys conducted for this purpose.
At the end of the project, marks may be adjusted as follows:
Group Mark = X points based on criteria
Bonus Mark = (Actual Contribution/50 - 1) * 20%
Penalty = (Actual Contribution/50 - 1) * 100%
Penalty Reduction = ((50 - Reported Contribution) / (50 - Actual Contribution)) * 25%
If Bonus Mark > 0:
Student receives X * (1 + Bonus Mark)
Else If Penalty > 0:
Student receives X * (1 – Penalty * (Penalty Reduction))
Else:
Student receives X
Mark cannot exceed 100% regardless of bonus marks. For example:
-
If Student A and Student B both contribute 50% each, then there is no adjustment and they both receive the same mark X/100.
-
If Student A contributed 75% effort and Student B only 25%, then Student A receives +10% bonus to account for the extra work they may have had to do, and Student B receives -50% penalty because they did half the work they should have done. Student A’s mark is 1.1*X and student B’s mark is 0.5*X
o If Student B reported their contribution honestly (25% or less) then they receive a reduction in their penalty of up to 25% - so instead of -50%, they would get -37.5%.
o If Student B reported their contribution dishonestly (50% or more) then they would receive the full -50% penalty.
o If Student B reported their contribution less than 50% but greater than 25%, then they would receive a reduction in their penalty linearly scaled in this range – so if they reported 40%, then they get (10/25)*25% = 10% reduction in their penalty, so they receive -45% penalty instead of -50%.
-
If Student A contributed 100% and Student B contributed 0%, then Student A receives +20% bonus, and Student B receives -100%.
-
If Student A contributed 80% and Student B contributed 20%, then Student A receives +12% bonus and Student B receives -60%.
-
If Student A contributed 55% and Student B contributed 45%, then student A receives +2% bonus mark and Student B receives -10% penalty (if student B reported their contribution as 45% or less, they only receive -7.5% penalty).
The actual contribution percentage will be determined based on a range of factors including:
-
The demonstration during class
-
Responses to confidential progressive weekly surveys and final survey (reported contribution)
-
Division of tasks explained in the group report
-
Additional evidence provided by group members
