The Agile software development model is driven by "learning by doing" and rejects Big Design Up Front (BDUF) for that reason. User-Centered Design (UCD) on the other hand requires a more holistic view to be able to create a usable user interface and in the end create a good user experience. Finding a balance between the incremental development and the need for a more comprehensive view of the user interface is therefore the key to usability in Agile software development. The objective of this master thesis was to construct a framework on how to combine UCD and Agile development in general, and specifically for the web based tool, called Alo, at the IS/IT department of Com Hem AB, Sweden. The results of this thesis was that the process of integrating User-Centered Design in Agile software development first of all needs a familiar starting point for both usability experts and developers. This can be achieved with what Desirée Sy describes as “Cycle Zero”, to let usability experts perform initial research ahead of implementation. Designing one sprint ahead should later converge to a more synchronized process where requirements and sketches of the interface are put together, with the help of developers, just in time for the implementation. This does not only prevents waste in the form of documentation and miscommunication associated with hand-offs, but also makes the implementation more purposeful and fun for developers.Secondly, build prototypes early in the process to create a holistic vision of the finished product and to test concepts in usability tests early. Thirdly, create shared understanding (within the development team as well as with outside stakeholders) of user needs by involving the entire team in usability testing. Critical to the success of all the above is that all outside stakeholders understands the Agile process and respects that the team is a self-organizing unit that solves problems within a set of given boundaries, rather than a code factory that feeds on specification documents.

Idag är det många företag som misslyckas med sina implementeringsprojekt av affärssystem och många forskare anser att det beror på bristande användarinvolvering. Implementeringsprojekt av affärssystem blir allt vanligare i små företag, men effekten blir dock stor om ett mindre företag misslyckas med sitt projekt. Små företags misslyckanden är oftast relaterade till finansiella och humanitära kritiska framgångsfaktorer.   Ett affärssystem kan ge ett företag en rad olika fördelar och möjligheter. Men för att ett företag ska uppnå dem krävs ett lyckat implementeringsprojekt samt att användarna omgående efter driftstart kan använda affärssystemet. Därför måste företagsledare under projektet se till en rad olika kritiska framgångsfaktorer som är relaterade till användarinvolvering. För att kunna hantera användarrelaterade kritiska framgångsfaktorer och de problem som de kan orsaka finns det angreppssätt till stöd. Ett angreppssätt vars syfte är att stödja användarinvolvering och hantera användarrelaterade problem är Participatory design (PD) och dess metod User centered design (UCD). PD och UCD bygger på att involvera användarna tidigt och ständigt under ett implementeringsprojekt och det i form av bland annat testning och utbildning. Användarinvolvering är därmed en viktig faktor vid implementeringsprojekt av affärssystem.   Syftet med studien är att göra företagsledare medvetna om vilka användarrelaterade kritiska framgångsfaktorer och problem som kan påverka ett implementeringsprojekt och dess utfall. Vi anger ett antal åtgärder, baserade på användarinvolvering, som ska stödja företagsledare att bättre och effektivare kunna förutse och hantera användarrelaterade problem vid implementeringsprojekt.   Vi har med stöd av en kvalitativ undersökning och en empirisk studie påvisat sambandet mellan områdena affärssystem, affärssystemets implementeringsprocess, användarrelaterade kritiska framgångsfaktorer och användarinvolvering. Vi har konstruerat en egen modell och tabell, 4-A Modellen och 4-A Tabellen, som illustrerar hur de olika områdena relaterar och stödjer varandra under ett affärssystems implementeringsprojekt. Vårt bidrag är ett dokument vars syfte är att stödja företagsledare vid planering innan och under ett implementeringsprojekt, främst när det gäller projektets användarinvolvering. Dokumentet ska göra företagsledare medvetna om vad bristande användarinvolvering kan leda till, samt när och hur användare bör involveras under ett implementeringsprojekt. / Today many businesses fail in their enterprise recourse planning (ERP) implementation projects and many scientists believe it is due to lack of user involvement. ERP implementation projects are becoming more common in small businesses, but the effect will be large if a small business fails in their ERP implementation projects. Small businesses failures are usually related to financial and humanitarian critical success factors.   An ERP system can give a business a number of advantages and opportunities. But it requires a successful implementation project to achieve them and also that user immediately after start-up can use the ERP. Therefore, the manager during the implementation project needs to ensure a range of critical success factors that are related to user involvement. There are a number of approaches to manage user-related critical success factors and the problems they cause. An approach which aims to support user involvement and manage user-related problems is Participatory Design (PD) and its method User centered design (UCD). PD and UCD are based on involving the users early and continuously during the ERP implementation process and that in the form of testing and training. User Involvement is therefore an important factor in ERP implementation projects.   The aim of the study is to make managers more aware of the user-related critical success factors and issues that can affect an ERP implementation projects outcome. We foresee a number of measures, based on user involvement, which will support managers to better and more efficient anticipate and manage user-related problems in ERP implementation projects.   Supported by a qualitative and an empirical study, we have demonstrated the relationship between the areas ERP, ERP implementation process, user-related critical success factors and user involvement. We have constructed our own model and table, the 4-A Model and the 4-A Table, that illustrates how the different areas influences and support each other in an ERP implementation project. Our contribution is a document whose purpose is to support managers when planning a project’s user involvement, before and during an ERP implementation project. The document will make manager aware of what the lack of user involvement can lead to, but also when and how the users should involve in an ERP implementation project.

(in English): The diploma thesis deals with the use of design methods among Czech UX designers in the design of web and mobile applications. The aim of this work is to find out and critically describe how Czech UX designers use design methods in practice. The thesis analyse the design process of website, web and mobile applications, its various stages and procedures. The theoretical part of the thesis introduces the basic terminology of the User Experience field and current research in the field, with emphasis on relevant terms and processes that occur in design practice. This part of the thesis is based on data obtained in the practical part, according to which popular approaches, frameworks, processes and methodologies of the UX field will be identified and described on the basis of professional literature. In the research part, qualitative research will be carried out in the form of semi-structured interviews with Czech User Experience designers, focused on the identification of methods, procedures and principles and ways of their usage. At the end of the thesis, the obtained data will be evaluated and it will be identified whether Czech designers in their practice adhere to academic approaches, or what existing and theoretically described methodologies and procedures their design process...

Preem verkar inom drivmedelsbranschen som styrs av en mycket hög omsättning med förhållandevis små marginaler. Det är därför viktig med en väl fungerande lagerkontroll. Det man idag är ute efter är en ökad precision i lageruppföljningen och därmed behövs ett nytt systemstöd till detta. Jag fick i min roll hos Preem uppgiften att titta närmre på GUI och processerna bakom. Det resulterade i denna rapport med ett framtaget förslag på användargränssnittet till det nya systemet och dess affärsprocesser som är kopplat till detta. Arbetet fokuserar på hur de två framställs i förhållande till varandra och vilka metoder som används för att konstruera dessa. Arbetet inkluderar illustrationer av as-is och to-be processmodeller enligt BPMN specifikation, wireframes och en sitemap. Denna rapport visar ett förslag på ett sammanfört system och ett intuitivare GUI med nya processer bakom, för just Preem, och hur balansgången går mellan att skapa affärsprocesser och ett grafiskt användargränssnitt ur varandra, beroende av vilka som är involverade i projektet. / Preem is a Swedish company that operates in the oil industry, which is controlled by very high sales and with relatively small margins. It’s therefore essential with a well working stock control. Today they are looking for a better way of monitoring the stock with a higher precision and therefore they need a new system for that. My role at Preem was to take a closer look at the GUI and the processes behind that. It resulted in this thesis that includes the user interface for the new system and the business processes that are linked to this. The work will focus on how these two methods are produced in relation to each other, and the methods that are used to construct them. The thesis includes illustrations of as-is and to-be process models of the BPMN specification, wireframes and a sitemap. This report shows a proposal of an integrating system and an intuitive GUI with new processes, at Preem, and how the balance is between creating business processes and a graphical user interface out of each other, depending on the people who are involved in the project.

Résumé : L’informatique diffuse est le passage du paradigme informatique vers l’informatique partout. L’émergence couvre principalement l’informatique mobile et distribuée, les réseaux de capteurs, l’interaction homme-machine et l’intelligence artificielle sous l’égide de l’informatique diffuse. Des efforts considérables ont été mis sur les recherches dans ce domaine, mais il n’existe pas de normes ou des méthodologies communément acceptées pour évaluer ces systèmes et de définir des nouvelles orientations de recherche dans le futur. Cette thèse s’attaque au problème d’évaluation des systèmes informatiques ubiquitaires. La question de recherche notamment le quoi et comment évaluer n’a pas encore été résolue. Dans l’objectif de trouver une réponse à cette question et d’élaborer un cadre général d’évaluation, nous avons procédé comme suit. Pour répondre à la première partie de la question, “Quoi évaluer”, nous avons tout d’abord classè les systèmes en se basant sur certains critères, et nous avons défini ensuite les principaux paramètres pour évaluer ces systèmes. Pour ce faire, nous avons étudié différents aspects de l’informatique diffuse et nous les avons classés en onze différents aspects d’évaluation. Pour chaque aspect, nous avons identifiè les principaux paramètres qui peuvent être caractérisés et mesurés. Cette taxonomie n’est pas assez exhaustive, mais elle reflète le schéma de classification le mieux adaptè pour des évaluations effectives. Cependant, pour que l’évaluation soit la plus complète possible, nous avons jugé nécessaire d’incorporer l’utilisateur dans le processus d’évaluation. À cet effet, nous avons proposè un modèle d’évaluation qui prend en compte les besoins de l’utilisateur, le contexte dans lequel la technologie sera utilisée, et l’environnement d’exploitation dans lequel le système va être déployé. Le modèle proposè constitue une première étape vers le développement des directives et standards d’évaluation qui peuvent être utilisés peuvent être utilisées pendant les évaluations formatives et sommatives. Une autre question complémentaire à l’évaluation des performances est la validation fonctionnelle d’un système en cours d’exécution, qui confirme que le système est conforme aux exigences fonctionnelles et ne contient pas de failles. Pour répondre à la deuxième partie de la question à savoir “comment évaluer”, nous avons adoptè les techniques formelles de vérification et de validation. Comme le champ d’application du projet est très large, nous sommes concentrés sur l’évaluation au premier stade de la conception afin de vérifier et de valider l’exactitude fonctionnelle de la conception de systèmes. Pour la preuve de concept, nous avons appliqué deux méthodes, dans la première méthode, nous avons étudié les approches de vérification automatique et nous avons choisi la technique la plus connue qu’est le “model checking” pour vérifier les exigences fonctionnelles d’un système de gestion des médicaments basé sur le contexte pour des personnes âgées dans une maison Intelligente. Cette approche est complémentaire aux tests et à l’évaluation et permet aux concepteurs de vérifier le comportement de leurs systèmes par rapport aux exigences fonctionnelles avant le développement du prototype de système. Certaines propriétés de base, telles que la disponibilité ou la vivacité, l’interblocage, la comparaison des spécifications et implémentations et l’analyse d’accessibilité, sont également vérifiées à ce stade. Dans la deuxième méthode, nous avons étudié les approches de vérification d’exécution et nous avons adoptè la technique de conception par le contrat pour modéliser et vérifier la sémantique et exigences de l’interopérabilité des services dans les environnements intelligents. L’avantage de cette approche réside dans la vérification automatique en temps réel de l’interopérabilité des services dans les environnements intelligents. // Abstract : Summary performance evaluations. The proposed model is a step towards forming standard evaluation guidelines that can be used during formative and summative evaluations. A complementary issue to performance evaluation is functional correctness of a running system, which confirms that the system fulfills its functional requirements and does not contain any flaws. To address the second part of the question that is “ how to evaluate ”, we have adopted the well-known formal verification and validation techniques. As the scope of the project is very big, the focus of this thesis is on early design stage evaluation to verify and validate the functional correctness of the systems design. For the proof-of-concept, we applied two methods: In the first method, we studied automatic verification approaches and used a well-known model checking approach to model and verify the functional requirements of a context aware medication management system for the elderly in a Smart House. This approach is complementary to testing and evaluation, it allows designers to verify their system behavior against its functional requirements before developing the system prototype. Some basic properties like the availability or liveliness, deadlock checking, matching of specification and implementation, and reachability analysis are verified. In the second method, we studied the runtime verification approaches and used design by contract technique to model and verify the semantic and pragmatic service interoperability requirements in smart environments. The analysis of this technique and results are presented. The benefit of the approach is automatic verification of services interoperability in smart environments on the fly.

Denna rapport redogör för det praktiska examensarbete som har inneburit en redesign av Birnas Trafikskolas webbplats. Webbplatsen var i behov av en ny design, struktur och innehåll. I detta arbete har designprocessen utförts utifrån ett användarcentrerat perspektiv baserat på design thinking. Arbetsprocessen har bestått av research kring användarna, prototyparbete, framtagande av en grafisk profil och genomförande av användartester. Utvecklingen av den nya webbplatsen har skett via CMS-verktyget Joomla samt med användning av HTML och CSS-kod. Resultatet av detta examensarbete presenteras i form av en webbplats med ny grafisk design och innehåll. / This report describes the practical thesis that entailed the redesign of Birnas driving school’s website. The website was in need of a new design, structure and content. In this work, the design process was carried out with a user-centered approach based on design thinking. The work process has consisted of user research, prototyping, the developement of a graphic profile, and user testing. The developement of the new site has been made through the content management system Joomla and the use of HTML and CSS code. The result of this thesis is presented in the form of a website with new graphic design and content.

Recommender systems such as Amazon, offer uses recommendations, or suggestions of items to try or buy. We propose a novel classification of reasons for including explanations in recommender systems. Our focus is on the aim of effectiveness, or decision support, and we contrast it with other metrics such as satisfaction and persuasion. In user studies, we found that people varied in the features they found important, and composed a short list of features in two domains (movies and cameras). We then built a natural language explanation testbed system, considering these features as well as the limitations of using commercial data. This testbed was used in a series of experiments to test whether personalization of explanations affects effectiveness, persuasion and satisfaction. We chose a simple form of personalization which considers likely constraints of a recommender system (e.g. limited meta-data related to the user) as well as brevity. In these experiments we found that: 1. Explanations help participants to make decisions compared to recommendations without explanations, we saw as a significant decrease in opt-outs in item ratings – participants were more likely to be able to give an initial rating for an item if they were given an explanation, and the likelihood of receiving a rating increased for feature-based explanations compared to a baseline. 2. Contrary to our initial hypothesis, our method of personalization could damage effectiveness for both movies and cameras which are domains that differ with regard to two dimensions which we found affected perceived effectiveness: cost (low vs. high), and valuation type (subjective vs. objective). 3. Participants were more satisfied with feature-based than baseline explanations. If the personalization is perceived as relevant to them, then personalized feature-based explanations were preferred over non-personalized. 4. Satisfaction with explanation was also reflected in the proportion of opt-outs. The opt-out rate for the explanations was highest in the baseline for all experiments. This was the case despite the different types of explanation baselines used in the two domains.

In today’s society there is a growing awareness of where food is produced and there is a trend to use locally grown produce in restaurants. One way for restaurants to differentiate themselves is to grow the produce inside the restaurant. This thesis has the aim on identifying the problems and user needs for an indoor cultivation solution and developing a new indoor cultivation product that solves the identified problems and meet the user needs. To achieve this aim, a usercentered design approach was utilised and the following three research questions were answered: How can the needs of the user be translated into a product specification for indoor cultivation in restaurants? What are the functionality, usability, and construction requirements for an indoor cultivation product in a restaurant? What product concept can be designed to grow classic herbs in restaurants based on the needs of the user? To identify the needs interviews were performed with the users. The needs were then translated, together with the company’s needs, into a product specification. This was done in two steps, identifying the metrics and setting values. Some of the most important requirements are that a hydroponic system is used, that the product is easy to clean and is moveable. The product development process was iterative and included different ideation, development and evaluation methods. The users were involved in some of the evaluation methods to give input on the final design. Their opinion, together with evaluations based on the product specification, were used when choosing the final concept Lärad. Lärad uses a circulating hydroponic system and have three separate growing containers each containing 16 plants. The growing containers can be pulled out to enable easy access of the plants. Both the water system and the LED grow lights, that replaces natural sunlight, are controlled automatically to minimise the users’ involvement. To test the concept, to see how well the product specification is fulfilled, both a CAD model and a functional prototype were created. The results from the tests were, even at the concept stage, that 97% of all the tested requirements were fulfilled which shows that the concept is suitable for indoor cultivation in a restaurant environment. Some further work that includes refining the design and optimising for production will be needed to launch the product.

I Sverige uppskattas 800 000 personer leva med astma. I landet pågår ett digitaliseringsarbete för att via e-tjänster göra vården mer tillgänglig för patienter. E-tjänster avsedda för astmavård har uppvisat svårigheter att främja kommunikation mellan patient och vårdgivare. E-tjänster har inte ansetts kunna ersätta den personliga kontakt som ett möte mellan patient och vårdpersonal erbjuder. Bristande kontakt med vården kan leda till att gradvis försämring av astmasymtom inte upptäcks. Det kan också leda till en avsaknad av upplevt socialt stöd hos patienten, vilket kan leda till sämre mental hälsa. För att undersöka hur e-tjänster för astmavård kan designas för att, genom individanpassad information, främja och upprätthålla kommunikationen mellan patient och vårdgivare, till stöd för god vård och patienthälsa, har en studie uppdelad i tre steg genomförts. Denna studie inleddes med en litteratursökning, följdes av en intervjustudie med öppna intervjuer och avslutades i en konceptdriven designprocess. Intervjuerna analyserades mot tidigare teorier och användes tillsammans med dessa som grund för att skapa ett designkoncept tänkt att främja och upprätthålla kommunikation mellan patient och vårdgivare i astmavården. Designkonceptet, “Astmaportalen”, togs iterativt fram genom en konceptdriven designmetod vilken involverade astmavårdpersonal, astmapatienter samt informatikstuderande. Konceptet manifesterades i form av en digital prototyp. Utvärderingar med astmavårdpersonal, astmapatienter och informatikstuderande visade att designkonceptet skulle kunna utgöra ett användbart bidrag till en symbios av vårdmöten på plats och digitala lösningar. / In Sweden, 800,000 persons are estimated to live with asthma. There is an ongoing digitization work in the country, to make healthcare more accessible to patients through the use of e-services. E-services intended for asthma care have shown difficulties in promoting communication between patients and the caregiver. E-services have not been considered able to replace the personal contact that a healthcare meeting between the patient and the caregiver offers. Lack of contact with the healthcare can lead to gradual deterioration of asthma symptoms not being detected. It can also lead to a patient-perceived lack of social support, which can lead to poorer mental health for the patient. To explore how e-services for asthma care can be designed in order to, through individualized information, promote and maintain communication between patient and the healthcare provider, in support of good care and patient health, a study divided into three steps has been carried out. The study began with a literature search, was followed by an interview study with open interviews and ended in a concept-driven design process. The interviews were analyzed against previous theories and used together with these as the basis for creating a design concept intended to promote and maintain communication between the patient and the caregiver in asthma care. The design concept, "Astmaportalen” (“The Asthma Portal"), was iteratively created through a concept-driven design method which involved asthma care personnel, asthma patients and informatics students. The concept was manifested in the form of a digital prototype. Evaluations with asthma care personnel and asthma patients demonstrated that the design concept could make a useful contribution to a symbiosis of healthcare meetings on site and digital solutions.

The increasing reliance of people on computers for daily tasks has resulted in a vast number of digital documents. Search engines were once luxury tools for quickly scanning a set of documents but are now quickly becoming the only practical way to navigate through this sea of information. Traditionally, search engine results are based upon a mathematical formula of document relevance to a search phrase. Often, however, what a user deems to be relevant and what a search engine computes as relevant are not the same. User feedback regarding the utility of a search result can be collected in order to refine query results. Additionally, user feedback can be used to identify queries that lack high quality search results. A content author can then further develop existing content or create new content to improve those search results. The most straightforward way of collecting user feedback is to add a graphical user interface component to the search interface that asks the user how much he or she liked the search result. However, if the feedback mechanism requires the user to provide feedback before he or she can progress further with his or her search, the user may become annoyed and provide incorrect feedback values out of spite. Conversely, if the feedback mechanism does not require the user to provide feedback at all then the overall amount of collected feedback will be diminished as many users will not expend the effort required to give feedback. This research focused on the collection of explicit user feedback in both mandatory (a user must give feedback) and voluntary (a user may give feedback) scenarios. The collected data was used to train a set of decision tree classifiers that provided user satisfaction values as a function of implicit user behavior and a set of search terms. The results of our study indicate that a more accurate classifier can be built from explicit data collected in a voluntary scenario. Given a limited search domain, the classification accuracy can be further improved.