TINK - sketching product experiences of connected objects

Recommendations

Info

88 - TINK 5.3 Prototyping the user interface A second prototype was developed with the intention of running a user test to evaluate the user experience of TINK. The development of a fully functional prototype of the entire system goes beyond the scope of the project because it would require months of development. Instead this partial prototype focused just on the implementation of the edit view, and to left out the monitor view. Time constraints also made it impossible to integrate the work done for the first technology test in the second prototype. The prototype was therefore not functional, as it was unable to connect to physical “connected objects“ (Arduino YUN). What was functional on this prototype were the main elements of the interface (the edit view to sketch and edit the system diagram) as well as the back-end used to save users information and save projects. The developed prototype will therefore be able to: • Create a new project • Access the system diagram editor • Add entities to the diagram • Add building blocks to the entities • Connect building blocks with each other. The prototype developed won’t allow to: • Share the project • Access the map view and visualize the data • Edit the code • Use the different types of building block connectors • Upload a custom picture for the entities • Clone entities • Deploy the software • Get real time feedback • Access the building block library The prototype was built on top of the stack of JavaScript technology shown in Figure 38. The front-end was implemented using AngularJs, a framework that facilitates the development of dynamic web applications. Since in modern browsers it is possible to include SVG tags into web pages, it was decided to use the vector markup language to code the system diagram. This was mainly adopted to solve the problem of drawing arrows to connect one building block to another and be able to arrange elements freely in the page. The back-end, with the role of storing data, was built on top of SailsJs, a web framework aimed at the development of real-time web application. SailsJs is able to automatically generate the required API to interact with several types of databases. Moreover it
Testing - 89 natively supports SocketIO allowing an easy integration with the Arduino library. MongoDB was chosen for the project as it provides several advantages for data intensive types of applications. The generated APIs where used to connect front-end and back-end. Figure 43 shows the interface of the prototype developed, an example project representing a simplified version of the system diagram of the Goodnight Lamp 24 project was drawn for demonstration purposes . Figure 43. Screenshot of the prototype of TINK’s interface.
Page 1:
sketching product experiences of co
Page 5 and 6:
Introduction This paper is a summar
Page 7 and 8:
CHAPTER 4 67 CHAPTER 5 83 CHAPTER 6
Page 9 and 10:
Graduation Assignment - 9 CHAPTER 1
Page 11 and 12:
Graduation Assignment - 11 1.1 Sket
Page 13 and 14:
Graduation Assignment - 13 bad stru
Page 15 and 16:
Graduation Assignment - 15 fact ske
Page 17 and 18:
Graduation Assignment - 17 phase. A
Page 19 and 20:
Graduation Assignment - 19 1.2 Abou
Page 21 and 22:
Graduation Assignment - 21 Figure 7
Page 23 and 24:
Page 25 and 26:
Page 27 and 28:
Graduation Assignment - 27 not expe
Page 29 and 30:
CHAPTER 2 Market analysis In the be
Page 31 and 32:
Market analysis - 31 Devices The de
Page 33 and 34:
Market analysis - 33 1 #011231=#ff0
Page 35 and 36:
Market analysis - 35 2.2.2 - Object
Page 37 and 38:
Market analysis - 37 2.2.4 - remote
Page 39 and 40: Market analysis - 39 2.2.6 - Object
Page 41 and 42: Market analysis - 41 require more t
Page 43 and 44: Market analysis - 43 not require th
Page 45 and 46: Market analysis - 45 2.5.1 Hardware
Page 47 and 48: Market analysis - 47 SEVERAL NODES
Page 49 and 50: Market analysis - 49 THE EVENTS LIN
Page 51 and 52: Market analysis - 51 THE REMOTELY C
Page 53: Market analysis - 53
Page 56 and 57: 56 - TINK After having analyzed dif
Page 58 and 59: 58 - TINK Phase 3- Imagine if… Fi
Page 60 and 61: 60 - TINK Research results The reco
Page 62 and 63: 62 - TINK a step was missing: The d
Page 64 and 65: 64 - TINK 3.5 Program of requiremen
Page 67 and 68: CHAPTER 4 Final design Guided by th
Page 69 and 70: Final design - 69 private copy on a
Page 71 and 72: Final design - 71 Monitor Edit Ciao
Page 74: Building blocks Data To Track trigg
Page 77 and 78: Final design - 75 Visual feedback H
Page 79 and 80: Monitor Edit Ciao Lorenzo Final des
Page 81 and 82: Final design - 79 The lamp is now c
Page 83: Final design - 81 developed for sta
Page 86 and 87: 84 - TINK 5.1 Prototyping TINK The
Page 88 and 89: 86 - TINK 5.2 Connecting a coffee m
Page 92 and 93: 90 - TINK 5.4 User Test As describe
Page 94 and 95: 92 - TINK 5.4.3 User test results T
Page 96 and 97: 94 - TINK state in a single action.
Page 99 and 100: CHAPTER 6 Evaluation Here, the grad
Page 101 and 102: Evaluation - 99 With TINK however,
Page 103 and 104: Evaluation - 101 related to an enti
Page 105 and 106: Evaluation - 103 students talking a
Page 107 and 108: Evaluation - 105 should provide too
Page 109 and 110: Evaluation - 107 DESIGN After the r
Page 111 and 112: References - 109 }. Retrieved June
Page 113: References - 111
show all

TINK - sketching product experiences of connected objects

Create successful ePaper yourself

Delete template?

Save as template?