Att hantera sömmar i interaktiva system
Sammanfattning: The purpose of this paper is to examine how seams in an interactive system should be managed. Seamsin this study refer to the boundaries that arise when users move between for example differentsoftware, products or positioning systems. These seams are a cornerstone of the relatively unexploredarea called seamful design, which is based on that users can avail highlighted seams through activeparticipation in the use of a system. To analyze this area, seamful design is applied to the developmentof an interface of a smoothie vending machine. This smoothie machine thus provides the analyzedinteractive system, which the research questions are applied to as well as answered by. The researchquestions are infused by seams and seamful design. More specifically, this paper questions how, whenand why these seams should be made visible or hidden. Another question stresses if the visualizationof seams can be applied to a smoothie machine and create distinct advantages in this system. To accomplish this, the project was divided in three separate phases. The first phase consisted ofexamining the conditions, environment and design of the service and the product. The second phaseconsisted of an iterative creation of concept proposals and usage of related methods. The third andfinal phase involved performing user tests, evaluating the interface and drawing conclusions about theformulated research questions. The project results are visualized partly by the final interface that was generated, and partly by theresults of the performed user tests during the third phase, which later came to form the basis for theconclusions that arose. The results included the understanding that the visualization of seams have thepotential to increase the task success rate, but at the same time may entail the risk of extending thetime it takes to perform a task. This was distinguished from the result of the test where the user wasgiven the task to place a cup in the machine. In one case, the seam was highlighted, while it was hiddenin the other. An additional result was that users expressed that seams could entail an advantage whenthe system was used repeatedly, while they in situations where they only used the system once, arguedthat it was beneficial to hide the seam because of lack of interest of the additional information. The conclusions based on this result, included both guidelines of how, when and why it is appropriateto highlight or hide seams, and also the finding that that seamful design has potential to be applied toa smoothie machine with clear benefits. The first of these guidelines implies that seams should behidden in systems which focus on performance and efficiency, as there is a risk that the usage time isprolonged when the seam is highlighted. Another guideline states that seams should be hidden whenmanipulation of the system could entail a serious risk, due to that users in most cases create a deeperunderstanding of the underlying technology when the seams are highlighted. On the contrary, insystems where possible manipulation entails no significant risk, seams may be highlighted to facilitatean individual use of the system. Furthermore, it is advantageous to highlight seams when a repeateduse of the system occurs, because of the fact that many users expressed that they pay greater attentionto seams when they have acquired some familiarity with the interface. Finally, perhaps the mostimportant aspect when a seam is about to be highlighted, is to make sure that the user physically canact and respond to the additional information that comes with the seam.
HÄR KAN DU HÄMTA UPPSATSEN I FULLTEXT. (följ länken till nästa sida)