×

Stage 1: Project Proposal

Description:

In this initial stage, we focused on identifying a real-world problem related to food waste and brainstorming potential solutions. After thorough research and discussions, we proposed the idea of FreezApp, an application designed to help users manage their frozen food inventory effectively.

The proposal included defining the app's core features, target audience, and the overall user experience we aimed to create. We also outlined our project timeline and milestones to ensure a structured development process.

Date: 22 September 2025

Authors:

• Piotr Ratajczak
• Alicja Kowalska
• Paweł Spychała
• Dawid Józwik

Click to see a report

×

Stage 2: User and task analysis

Description:

In this stage, you should examine and understand the problem space. Who are the main users of the system? What tasks users want to perform with the system? What functionalities should be made available by the system? How is the work environment?

This stage should include:

• User analysis: Identify the characteristics of the target user population. Multiple user classes may exist, identify each one of them.
• Task analysis: Determine the tasks that should be allowed by your system and analyse their characteristics. You should find and analyse 3-6 high-level tasks. Each of these high-level tasks should have a goal and subtasks.
• Scenario design: Create 3 different scenarios (a concrete example of tasks performed in a hypothetical interface) that include the tasks considered in the task analysis.

Date: 13 October 2025

Authors:

• Piotr Ratajczak
• Alicja Kowalska
• Paweł Spychała
• Dawid Józwik

Click to see a report

×

Stage 3: 1st Prototype

Description:

We developed and evaluated the first prototype of our system. It was a throw-away prototype, which we ensured could handle at least three scenarios described in the task analysis. Our colleagues and Professor tested the prototype during the lab class.

This stage should include:

• Sketches: Your first approach to the design to show how your interface would look at key points of the interaction.
• Prototype photos: Photos of the relevant pieces of your prototypes (also take photos in the testing day)
• Storyboards: Sequence of fixed screens showing the interaction to perform a relevant task.
• Briefing: The briefing provided to the users.
• Scenarios: Scenario descriptions provided to the users.
• Observation: Usability problems found during the tests and possible solutions. Describe user comments without identifying them.

Date: 3 November 2025

Authors:

• Piotr Ratajczak
• Alicja Kowalska
• Paweł Spychała
• Dawid Józwik

Click to see a report

×

Stage 4: Functional prototype

In this stage, according to the results obtained during the first prototype user tests, you are going to develop a functional prototype.

Objective:

Develop a functional prototype of an interactive system.

Description:

According to the results you got from the first prototype user tests in stage 3, you should create a new prototype running on the appropriate platform (web, mobile). This prototype should be:

• High fidelity in look: explore the graphic design of your final application. Make choices about screen layout, colours, fonts, alignment, icons...
• High fidelity in feel: the prototype should behave as the real system. It is supposed to run on the appropriate platform (web, mobile).
• Medium fidelity in breath: support, at least, the scenarios and tasks tested in stage 3.
• Low fidelity in depth: don’t need to put much work on the backend.

Your prototype does not need to be functionally complete, but should be complete enough to give a convincing impression to candidate users. This prototype will be distributed to another group of students from your practical class, so they will do a heuristic evaluation of your prototype and produce an evaluation report during the next project stage.

You can use any appropriate tool to develop your prototype (html, React native, ...).

Report:

The report must include:

• URL for your prototype: make your prototype available for downloading (or use in case of a website) and include the corresponding URL in the report.
• Startup instructions: Specify the platform and software requirements to run your prototype. Give brief instructions for starting it up.
• “Briefing”: the “briefing” you gave to the users in stage 3, describing your application (with the necessary adjustments).
• Scenarios: developed during stage 3 to help evaluators understand and evaluate your application.
• URL of your project: So evaluators have access to your project history, which will help them to understand your application.
• Also describe which parts of your prototype are incomplete, so evaluators know what is supposed to work and what is not.
• …don’t forget to describe your application and to identify the tools you used to develop it.

Date: 24 November 2025

Authors:

• Piotr Ratajczak
• Alicja Kowalska
• Paweł Spychała
• Dawid Józwik

Click to see a report

×

Stage 5: Heuristic evaluation

In this stage, each group is going to evaluate the interactive system interface developed by another group of colleagues. A project will be assigned to each group (in class) to evaluate and produce an evaluation report.

Objective:

Do the heuristic evaluation of an interactive system interface.

Description and report

You should run the project of your colleagues that have been assigned to you and perform a heuristic evaluation, producing the corresponding evaluation report.

For each detected problem, the evaluation report should include:

• Problem title
• The violated heuristics
• Problem description: brief description of the problem
• Severity rate
• Suggestions to solve the problem
• Location of the problem: in case of need, print screens and sign the interface elements that should be modified

The report should also include the date you received the project for evaluation and the date you delivered the evaluation report to your colleagues.

The evaluation report should be sent by e-mail to your colleagues (in reply to their message with the prototype to evaluate) with “cc” to tir@fct.unl.pt.

Date: 30 November 2025

Authors:

• Piotr Ratajczak
• Alicja Kowalska
• Paweł Spychała
• Dawid Józwik

Click to see a report