SWEN303 (2022) Assignment Two - Design

Due: 22nd April 2022

Assignment Two focuses on the first design for the system you selected in the AssignmentOne. Using the lessons you learnt from the first assignment about the requirements and users of a system, you now need to create a first wireframe design of the interface for / experience of using the system. You are expected to create a first draft of the design. The design is a living document that will be used in the second half of the trimester to build a prototype and test the prototype of the system. The idea is to have pairs create these draft designs and then merge 3 groups ( 6 individuals) to form a larger group that will evaluate the designs and select the best bits of each design to prototype and test.

You will create a design for the system you selected in Assignment 1, see TopicAreas

The design of the interface can be scanned drawings, digitally created click-through experiences in tools such as Balsamiq, Adobe XD or Figma. We are technologically agnostic and do not care which tool you use. The marking criteria are based on clarity of design, alignment with the identified users and their needs/use cases.

Due dates, contribution to course marks, submission requirements are in the Course Outline.


Your report should conform to the SWEN303 Written Assignment Rules. Organise your report into 4 Parts.
  • Part 1, An updated introduction to the project from Assignment 1. No more than 2 pages and will describe the background for the system and references to similar systems or situations.
  • Part 2, Updates assignment 1 to describe the personas (with 1 page per persona) and system requirements from the users perspective. These will be scenarios of use / use case analysis / User journeys. There should be no more than 5 pages of scenarios.
  • Part 3 The designs for the new interface including visualisation and description of main components, this is 5-8 pages per member of your group. This has an optional video presentation.
  • Part 4, Reflection on the pros and cons of your design, what you choose to emphasise and what you learnt during the creation of the design for the system.

Part 1: Introduction(<2 page)

Update of the description of the system that you are working with: * Describe existing solutions if there are any * Explain the business objectives for creating something a solution * Explain the importance of the system

Part 2: Personas and Requirements(<8 page)

Overview (1 page)

Give an updated one-page overview of your model: the personas, scenarios/tasks/essential use cases, and the relationships between them. The overview may be textual, a diagram (e.g. a use-case diagram) or a combination. Diagrams may be hand-drawn and scanned, or produced using a drawing tool. Your overview should include all the most important personas and scenarios/task use cases. Indicate (e.g. in bold) which personas and scenarios you have chosen to focus on in the rest of your report.

Personas (2 pages per group member, 1 page per persona)

Update the personas from the first assignment. If you have updated any of the personas significantly please indicate this so that we can evaluate the update as part of the work done for this assignment. For each persona: * give them a name * describe the persona, their goals, etc * you may incorporate structured persona attributes or facets (C&L, GenderMag) * you should include one or more pictures

You should present the personas in order of importance. Your marks may be affected if a persona is clearly not in the right place.

Scenarios (3-5 pages, 1 to 4 per page)

Update the scenarios you think are the most important to the design process, and that together give a good coverage of the requirements for the system,

For each scenario: * give it a name * show which persona(s) are involved in that scenario * give a description(narrative or use case steps) for the scenario.

You may choose to use either long style scenarios (as in Cooper 4) or short style scenarios (essential use cases as in Constantine & Lockwood, C&L ). All of your scenarios should be in the same style. If you use long form scenarios you may fit only one or two per page: short form scenarios may fit three or four per page. Do not break scenarios across page boundaries.

Again, You should present the scenarios in order of importance, and your marks may be affected if a task etc is clearly not in the right place

You will include at least 2 User Journey Maps. These combine the usecase scenario into a map that includes the entry and exit of the use case.

Part 3: Design ( <8 page per member)

This is the main contribution for this assignment. The presentation of the designs will be visual with descriptions where needed. The design must include the visual components related to what the user first encounters when using the system. The main activity of the user must be shown within the layout suggestions. The design should include colour selection and can refer to other products and solutions that have a similar "look and feel".

The exact layout is up to you, but these design proposals will form the basis for the development of the project after the mid-trimester break.

You are allowed to submit a video of the paper prototype in action. This should be a simple video with a voice over showing how the parts of the interface overlap. A video is a compulsory part of the final project submission, so this could be used as practice for that submission.

Part 4: Reflection ( <2 page per member)

As part of the design process you have to make compromises and prioritise parts of the system. In this section describe the pros and cons of the design you have proposed. What have you learnt about the problem by proposing a solution? Reflect on any changes you made to the personas or tasks based on creating these initial design documents.

Working in pairs

This project may be carried out individually, or in pairs. Individual or pair reports will be assessed to the same standards but with pairs expected to create more design content. As a pair submits one joint report it must be clear which design elements and reflection are attributed to each participant. Students will be expected to be able to discuss the designs they create when larger groups are created for the project.

You can change pairs from Assignment 1 or create a new pair from individuals. However, you will need to explain the contributions clearly in the reflection section. Each member of the pair must submit the same report file before the deadline, and must indicate their pair when they submit. If you have problems with working on your pairs you should contact a course tutor in the first instance. Confidential issues may be raised directly with the Course Coordinator (Craig Anslow).

Assessment Criteria

There are three main components that are graded about the design:
  • Updates from the work in Assignment 1 (10%)
  • Coverage (30%)
  • Quality (40%)
  • Reflection (20%)

We will be using a rubric for this assignment, see Ass2Rubric.

The assessment will consider both presentation and content. The presentation will be based on how easy it is to read, correct spelling, grammar, punctuation, clear diagrams, and so on.

The remaining content will be assessed according to its clarity, consistency, relevance, critical engagement and your demonstrated understanding of the material in the course. We will not mark you down because you missed a detail that covers a fairly minor situation, but we will if the missing detail is important to the strength of your argument.

Gitlab is optional for this assignment (compulsory for the final project). However, students can use gitlab to document their process during the development of this assignment. Documenting work will make it easier to show who was responsible for which tasks. If you are submitting a link to git repo make sure you give @craig @johntara @fishercait @zamanfais at least reporter level access.


Please submit your assignment into the Assignment 2 SWEN 303 submission system.