Wiki source code of Prototyping test
Version 7.2 by Sarantis Dimitriadis on 2022/06/02 09:11
Hide last authors
author | version | line-number | content |
---|---|---|---|
![]() |
7.2 | 1 | (% class="western" lang="en-GB" style="text-align:justify" %) |
2 | (% lang="en-US" %)**Description:** Prototyping test is a low cost and quick process in which a product or service with limited functionality and interaction is tested with real end-users. An interactive prototype product or service must be available so real end-users or experts can experience it. This prototype test can be, for instance, an interactive mock-up of a web service, which interface looks like a real thing. One can navigate through different screens and see simulated content. Also, the service prototype can consist of role-playing exercise to simulate service encounters. The main aim is to collect feedback on (%%)a 'close to real' user experience(% lang="en-US" %) as possible, but at a lower cost. Different methods such as interviews, surveys and observations can be used. | ||
![]() |
1.1 | 3 | |
![]() |
7.2 | 4 | (% class="western" lang="en-GB" style="text-align:justify" %) |
5 | (% lang="en-US" style="line-height:106%" %)**R&D service category-ies: **(% style="line-height:106%" %)Testing and validation | ||
![]() |
1.1 | 6 | |
![]() |
7.2 | 7 | (% class="western" lang="en-GB" style="text-align:justify" %) |
8 | (% lang="en-US" style="line-height:106%" %)**Key **(% style="line-height:106%" %)**characteristics**(% lang="en-US" %)** in Living Lab context:** | ||
![]() |
1.1 | 9 | |
![]() |
7.2 | 10 | * (% lang="en-US" style="line-height:106%" %)From rapid prototyping to the MVP |
11 | * (% lang="en-US" style="line-height:106%" %)IT solutions/Physical and cognitive exercises | ||
![]() |
1.1 | 12 | |
![]() |
7.2 | 13 | (% class="western" lang="en-GB" style="text-align:justify" %) |
![]() |
1.1 | 14 | **Objectives:** |
15 | |||
![]() |
7.2 | 16 | * Similar to proof-of-concept but testing higher fidelity solution, |
17 | * Identify improvement suggestions and usability test, | ||
18 | * Provides development recommendations based on user/patient/customer experience and needs, | ||
19 | * Identify key measures to investigate in follow-up tests | ||
![]() |
1.1 | 20 | |
![]() |
7.2 | 21 | (% class="western" lang="en-GB" style="text-align:justify" %) |
22 | **Methods: **Survey, observation, demo-session, interview, Wizard of Oz, usability tests, role playing | ||
![]() |
1.1 | 23 | |
![]() |
7.2 | 24 | (% class="western" lang="en-GB" style="text-align:justify" %) |
25 | **Tools: **Paper prototype,** **wireframes,** **interactive** **mockups, scaled down prototypes, visual dummies close to final (visual UI),** **video recording, usability questionnaires, eye tracking |