INFO2222: Computing 2 Usability and Security - Project: Usability Part - Support system for undergraduate
INFO2222 Project
1 Usability Part Description Expand the basic web based E2EE (secure messaging) to be a website of 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 shou ld 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 themselves and to specific academic/administrative staff. Besides the Login, Register, Messaging (view, send), Regular User role, your website should also have functionalities like following (to be assessed in last activity) • Data/Info hierarchy – how you organize user generated content • Admin Role - delete/mute user, delete a course guide • One specific user function – depending on your user investigation. In this part of the project, you are required to design the website with usability and accessibility in mind. A series of recommended activities will be provided in this document as a guide for your team’s action plan and discussion. It is advisable that you pace yourself and utilize the practical session to collec t feedback on your project from your tutors and peers through the mini -presentation session. Starting from Week 9, you can use the lab to do mini -presentation to collect feedback from both tutors and peers on pieces of work that have been produced. It is not necessary for presentation slides to be used. Hint : Think about the type of feedback that you would like to get and select the results and work to be presented. you will need to prepare a prototype of the website to conduct a usability test of your website to the tutor and peers in labs. During this presentation session, you will need to demonstrate a typical scenario in which your website will be used by your intended user(s) together with the core requirements. Submission deadline. The final report about the usability part (and corresponding code) will be due on Sunday 21st of May at 11:59pm .
1.1 Recommended Activities Step 1: User Investigation. During this phase, you are to investigate your chosen group to determine what they need from your website. To make things easier, your group can concern yourself with a single very specific 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. • Alumni – graduates who are willing to give back to their alma mater and to guide their juniors 2 • 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. Step 1: Expected output: — 10 points. • 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) relevant to the interest of your target persona. This should be in document form before you convert it to your website and must keep it up dated with any changes. Ensure you cite all sources and quote where you have copied text verbatim.
Step 2: Navigation design. There will hopefully be a lot of information from Step 1 in many potential categories. As well as this, your website will need to include the following ‘user’ actions stated in the core requirements in addition to actions specified specially for your own target user group. 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. Step 2: expected output. — 10 points. • Outline of card sorting session along with all materials that was used. • Information architecture of your website
Step 3: Design -Evaluate (Prototype (paper or digital) ). Based on the information architec - ture that you have from the previous phase, brainstorm and create sketches of your website. Create a prototype of the best design and perform guerrilla test with target use rs using this prototype. Each of your team member should take part in the guerrilla test, at least one participant is outside of your team. Step 3: expected output. — 10 points. • A prioritized list of additional features? • Outline steps taken to determine the ‘best’ design to be prototyped • Paper or digital prototype, • Mini -report that outline of how guerrilla test is conducted, actual raw results, materials used and findings of the test.
Step 4: Design -Evaluate (Hi -Fi 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. Step 4: expected output: — 70 points. • Incremental development plan (two iterations at least) • Outline of evaluations conducted 3 • Demonstrations of the functionalities mentioned at the beginning, admin roles, the user specific function etc. Remark 2 Your output in Step4 does not need to be perfect, we care more and the marking will focus on your improvements over each iteration.
Step 5: Final report • It is a collection of all the previous outputs in a neat format. • Your final submission should consist of two files: a pdf file containing the report and a zip file containing your code and other art ifacts.
