# data[].attributes.body
The test is now done, thank you for participating. Do you have any feedback for us?

# data[].attributes.body
Observations on what went well and what did not go well (make notes if someone has trouble with a task)
Success rate (yes/no) per user per task
Feedback from user

# data[].attributes.body
We are creating an app to assist people in public transport, can you help us with testing it by doing some tasks? During the tasks it is important that you think out loud so we know what you are thinking.

# data[].attributes.body
What did you think of the branding and colors used in the app?

# data[].attributes.body
The tests will results in valuable qualitative and quantitative knowledge about how the app is used, what unexpected choices users make and if the requirements have been implemented well enough. An indication of if this has been done correctly is the success rate of each task. These results will be used to change the implementation in the look & feel prototype. These changes can then be tested again to see if the changes have their desired effect.

# data[].attributes.body
You want to know more about the trip between Apeldoorn and Deventer, where in the train is it the least busy?

# data[].attributes.body
You want to catch the train at 10:20,  what time will you arrive in Deventer?

# data[].attributes.body
Plan a trip from Apeldoorn to Zwolle, what is the reason that the train that departs at 9:50 was cancelled?

# data[].attributes.body
Go to the track malfunctions page and view all of the current track malfunctions in the Netherlands. What is the extra travel time between Hilversum and Baarn?

# data[].attributes.body
Go to the settings, and change the theme to dark mode.

# data[].attributes.headline
How the Look & Feel prototype will be tested

# data[].attributes.subject
How the Look & Feel prototype will be tested

# data[].attributes.body
The look & feel prototype will be used to test how effectively usable the visual implementation of the requirements is. This will be tested through usability testing by giving a group of 8 relevant users 5 tasks and observing how these tasks are performed. The user is asked beforehand to think out loud so insights into the user's mind are gained. Observations are made about what struggles the user has and what went well. Besides this, the success rate of every task across the usability testing procedure will be measured. After the test the user will be asked for tips and tops regarding the usability of the prototype. The questions will give the user a task (or a question with an implied task) that tests one or multiple of the requirements.

# data[].attributes.body
A summary of the feedback we received is listed below.

Overall they thought it is pretty nice that the app will check in and out for you.

According to them, this feature makes the transition easier and reduces the chance of things going wrong.

They were wondering how the app knows where to check in and out. That is not clear in the story.

They were a bit confused by the fact that she sees at the check-in / check-out poles that her app has already done it. That makes it a bit unclear and doesn't show how useful this feature is.

# data[].attributes.headline
Link to functional digital prototype (click image)

# data[].attributes.subject
Link to functional digital prototype (click image)

# data[].attributes.attachment_link.description
15 Screens, Last modified on May 28, 2020 09:59 GMT

# data[].attributes.body
We chose to include the requirements we did for multiple reasons, the most important ones (as decided by users) were included first, the rest were chosen based on how useful they would be to implement in the prototype, and how doable it would be to include the functionality (or a simulation of the functionality) in a Look & Feel prototype

# data[].attributes.headline
The app shall use polite language to the user

# data[].attributes.subject
The app shall use polite language to the user

# data[].attributes.headline
The app shall offer the choice to switch between Dutch and English

# data[].attributes.subject
The app shall offer the choice to switch between Dutch and English

# data[].attributes.headline
The app shall have unique branding (colors, fonts etc.)

# data[].attributes.subject
The app shall have unique branding (colors, fonts etc.)

# data[].attributes.headline
The app shall offer dark mode functionality

# data[].attributes.subject
The app shall offer dark mode functionality

# data[].attributes.headline
The app shall only display the necessary information, to plan your trip, on the home screen

# data[].attributes.subject
The app shall only display the necessary information, to plan your trip, on the home screen

# data[].attributes.headline
Users shall be able to purchase train tickets and subscriptions in the app

# data[].attributes.subject
Users shall be able to purchase train tickets and subscriptions in the app

# data[].attributes.headline
The app shall show the current physical location of the train

# data[].attributes.subject
The app shall show the current physical location of the train

# data[].attributes.headline
The app shall show what seats in the train are taken and not taken

# data[].attributes.subject
The app shall show what seats in the train are taken and not taken

# data[].attributes.headline
The app shall show any current track malfunctions in the country

# data[].attributes.subject
The app shall show any current track malfunctions in the country

# data[].attributes.headline
The app shall show on which platform the train departs and arrives

# data[].attributes.subject
The app shall show on which platform the train departs and arrives

# data[].attributes.body
We felt that choosing these two kinds of prototypes made the most sense, since we do not have the time to develop an actual application (or access to the third-party services needed to create it). This means that acquiring insights into how it should be developed is not necessary. Since the final product is an app it is much more useful to gain insight into how the app is used and how to make it more usable. This is what we aim to achieve using the Role & Look and Feel prototypes

# data[].attributes.body
The goal of an implementation prototype is to simulate and analyze how the development will be performed. They show what will be needed during development of the final product.

# data[].attributes.body
The goal of a look & feel prototype is getting feedback from users as soon as possible about the prototype’s look. The prototype shows how the product will look and how users will use and interact with it.

# data[].attributes.body
The goal of a role prototype is to quickly gain insight into the role a product will play in the user's life. A role prototype defines the functionality that a user can utilize.

# data[].attributes.body
The tool that is used to bring the prototype to life is Rapid Prototyping with a mock-up. This allows us to make our idea tangible and quickly receive feedback from our users. It is quick to change according to feedback and allows us to communicate about it with stakeholders. It is also very cost-effective since no actual application has to be developed. We didn't choose for a physical model because it is hard to test it due to Corona.

# data[].attributes.body
Below you can find the adjusted version of the storyboard according to the feedback of the users. The users thought this version of the storyboard was more logic and clear as suppose to the previous storyboard.

# data[].attributes.body
We asked the users what they think of the storyboard and what they would change about it. Specifically about switching between travel companies.
We let the group discuss the storyboard together. We observed the group and received feedback on it.

# data[].attributes.body
This tool will allow you to visualize the situation better and is more common for the users. This option scored the best as it was the most feasible and practical solution. The tool is also very easy to use and conveys the situation clearly. We didn't choose role playing because of the fact that Corona makes it impossible to meet with our design team in person.

# data[].attributes.body
We brainstormed about the feedback and that will lead to solutions on how to implement the feedback in the storyboard.

# data[].attributes.body
We tested the storyboard with a group interview. This interview took place on Skype. We chose this method because it will help us to learn quickly what is valuable to the community.

# data[].attributes.body
With Adobe XD it is possible to allow the user to navigate through the app. This gives the user a true-to-life experience of using the app. We decided to use Adobe XD because it makes it easy to give the prototype a consistent, professional look and it has better reviews than other options.

# data[].attributes.body
Adobe XD was chosen because the use of this application will enable us to create a good look and feel that looks similar to an eventual end product.

# data[].attributes.body
The purpose of the bulletin board is to provide insight into the prototype that has been designed, including the choices that have been made. A prototype is shown which presents the problem along with the solution.

# data[].attributes.body
We decided to create a storyboard about our ”The app allows users to switch between travel companies.” requirement, using this storyboard, we wanted to understand our users and their reactions in this situation better.

# data[].attributes.body
Our storyboard is shown below. We decided to use our persona. In this storyboard Larissa wants to switch between travel companies and she will do this with the app.