SWEN 303 (2024) Assignment 1: Process and Users

CHANGE LOG

22.03.2024 Increased page limited from 2 to 3 pages
19.03.2024 Added information on referencing styles as a note.
29.02.2024 Release date.

Due: 23:59 Sunday 24 March 2024
How to submit: In the ECS submission system, submit your assignment as a PDF file called 303-a1-report-username.pdf.
Extensions: see notes on Slip Days and Extensions.

This individual assignment consists of two parts: Process Understanding and Reflecting on Users. You should produce a single PDF of no more than three A4 pages for this assessment. The expectation is that you appropriately reference material provided in class, as well as any additional material from other sources, in your report. The list of references included does not count towards the three page limit.

• NOTE: The VUW Library has advice on how to reference AI-generated content: https://libguides.victoria.ac.nz/referencing-citing/what-is-referencing#s-lg-box-wrapper-26260706
• NOTE: You can use standard IEEE format for references: https://www.canterbury.ac.nz/study/study-support-info/citations-and-referencing/ieee-style. There's no strict rule for referencing lecture slides (as long as it is clear) so you can use something like what is suggested here: https://libraryguides.vu.edu.au/apa-referencing/7CourseNotesPresentations

There is a general marking guide included below.

1. Process Understanding (50% of assignment mark)

Below are UX Engineering activities presented in a series of phases. Each phase consists of 2-4 activities (listed as bullet points beneath the name of each phase). The phases presented here are not necessarily in the correct order. Your task is to place the phases below in an order that you think would result in a meaningful UX Engineering Process. Justify your ordering:

• NOTE: You do not need to list all the activities when presenting your ordering - just the name of each phase. You DO need to refer to specific activities when justifying your ordering.

Implementation Phase

• Adopt agile development methodologies to enable quick adaptation to changing user needs.
• Regularly review and reassess project goals, adjusting the system as necessary based on user feedback and evolving requirements.
• Develop comprehensive training materials to ensure users and stakeholders understand the new system.

Designing for Human-Centeredness Phase

• Implement design thinking methodologies to ensure solutions are intuitive and user-friendly.
• Iterate on prototypes based on user feedback, ensuring the system aligns with user expectations.
• Implement design elements that consider different cultural backgrounds and preferences.

Understanding User Needs Phase

• Conduct surveys, interviews, and usability tests to understand user expectations and pain points.
• Identify key personas and user journeys to guide the design and improvement process.
• Arrange stakeholder workshops to gather insights on their expectations and requirements.
• Foster collaboration by involving both internal and external stakeholders in the decision-making process.

Continuous Improvement Phase

• Establish feedback loops to gather user insights continuously.
• Regularly review and analyze feedback to identify opportunities for improvement.

Collaboration and Communication Phase

• Foster collaboration by establishing cross-functional teams that bring together individuals with diverse skills and perspectives.
• Encourage open communication channels to facilitate the exchange of ideas and insights.
• Establish a user advocacy program to empower employees who champion user needs.

2. Reflecting on Users (50% of assignment mark)

Read through the following persona description and respond to the questions that follow:

Persona Description

• Name: Alex Singh
• Age: 32
• Occupation: Senior Software Engineer
• Location: New Zealand
• Background: Alex Singh is a driven and creative individual who has been working in the software industry for the past eight years. Originally from a small town, Alex moved to the city after university to pursue a career in software, drawn by the dynamic nature of the field and the opportunities it offers for creativity and innovation.
• Education: Alex holds a Bachelor of Engineering degree from a reputable university. Throughout university, Alex was involved in various extracurricular activities, including internships and part-time jobs, which provided practical experience and helped shape their career path.
• Career: After graduating, Alex started their career as a Junior Software Engineer at Software4U. Over the years, Alex demonstrated a strong work ethic, skill, and strategic thinking, which led to promotions and increased responsibilities. Currently, Alex holds the position of Senior Software Engineer at a medium-sized company, where they oversee a team of software developers and lead various projects.
• Interests: Outside of work, Alex enjoys staying active by participating in outdoor activities such as hiking, biking, and running. They are also an avid reader, with interests ranging from fiction to personal development. Alex values continuous learning and often attends industry conferences and workshops to stay updated with the latest trends and strategies in software engineering.
• Personality: Alex is known for being highly organized, detail-oriented, and goal-driven. They thrive in fast-paced environments and are always looking for ways to improve processes and achieve better results. Alex is also a team player who values collaboration and believes in the importance of fostering a positive work culture.
• Goals: Professionally, Alex aims to continue growing in their career and eventually take on a leadership role within the software industry. They are passionate about making a meaningful impact through their work and aspire to become a respected thought leader in the field.

In summary, Alex Singh is a dedicated and ambitious software professional who brings a blend of technical skill, strategic thinking, and leadership skills to their role. With a passion for continuous learning and a drive to succeed, Alex is poised to achieve great things in their career.

1. Imagine you are building an app that helps flatmates manage their expenses. Which details in the Alex Singh persona would inform the design of your app? Explain how they would affect the design?
2. What additional details would you need to know about the Alex Singh persona for it to be a more relevant representation of users of your app?
3. List all stakeholders relevant to your app that you would need personas for and explain why they are relevant?

Marking Guide

The assessment will consider both presentation and content. There are no explicit marks for presentation, however, if presentation is poor, then this could detract from the overall grade. Presentation will be assessed based on whether all parts of the assignment have been addressed, sentence and paragraph construction, spelling, punctuation, images are clear and easy to read.

Content	A range (A+, A, A-)	B range (B+, B, B-)	C range (C+, C, C-)	D/E
Process Understanding	Very clear what the ordering of phases should be. Excellent justification of the ordering of phases. Justification presents a coherent, logical process where activities inform the ones following. Justification refers to all the appropriate activities within phases.	Clear what the ordering of phases should be. Very good justification of the ordering of phases. Justification presents a coherent, logical process where activities build on the previous and inform the ones following. Justification refers to most of the appropriate activities within phases.	Somewhat clear what the ordering of phases should be. Good justification of the ordering of phases. Justification presents a somewhat coherent, logical process where activities build on the previous and inform the ones following. Justification refers to the some of the appropriate activities within phases.	Unclear what the ordering of phases should be. Poor justification of the ordering of phases. Justification does not present a coherent, logical process where activities build on the previous and inform the ones following. Justification refers to few/none of the appropriate activities within phases.
Reflecting on Users (design)	All relevant details of the persona are identified. Excellent explanation of the effects on the design. Concrete design examples are provided in a high level of detail.	All relevant details of the persona are identified. Very good explanation of the effects on the design. Concrete design examples are provided.	Most relevant details of the persona are identified. Good explanation of the effects on the design. Some concrete design examples are provided.	Few/no details of the persona are identified. Poor explanation of the effect the design. No concrete design examples are provided.
Reflecting on Users (additional details)	Additional details suggested are relevant. Excellent justifications provided.	Additional details suggested are relevant. Very good justifications provided.	Additional details suggested are relevant. Good justifications provided.	Additional details suggested are loosely relevant. Poor/no justifications provided.
Reflecting on Users (stakeholders)	Stakeholders suggested are relevant. Excellent justifications provided.	Stakeholders suggested are relevant. Very good justifications provided.	Stakeholders suggested are relevant. Good justifications provided.	Stakeholders suggested are somewhat relevant. Poor/no justifications provided.