Springe direkt zu Inhalt

Bastian van de Wetering:

Entwicklung einer Usability-Lösung zur Korrektur fehlerhafter Daten bei mobilen Visitenkartenscannern

Requirements

  • Swift
Academic Advisor
Discipline
User-Centered-Design
Degree
Bachelor of Science (B.Sc.)

Contents

Context

Business card scanners can be classified as business management software and serve the purpose of increasing the productivity of the user. A classic field of application are so-called sales fairs, in which sales staff hold many customer meetings one after the other, between which they have to create a new contact with the corresponding customer note in the system - often under time pressure. If this process is poorly solved, the loss of time adds up to a significant cost factor when repeated use is made. The usability of the application thus has a direct influence on the productivity of the user.

Smartphones are a special case. These are often used both privately and professionally, with the result that expectations regarding hedonic quality, especially aesthetics, are higher than, for example, at the work PC. In addition, the business card scanners available in the App or Playstore are exposed to a special competitive situation, since the purpose of use is very homogeneous, and these are therefore very easy to compare with each other.

If the used business card scanner causes stress or even frustration due to complicated operation, the user will look for an alternative in the medium term. At the same time, a bad user experience leads to bad ratings on the portals, which in turn are decisive for the success of an application.

Problem

Business card scanners use OCR technology to read the contact data and assign it to the contact form. Errors occur during readout and assignment. For example, vertical hyphens are often used on business cards, which are incorrectly interpreted as "1" or small "L" during conversion. Address supplements, name titles or job titles are also often incorrectly assigned or not assigned at all.

In order to handle errors, the editing function provided by the operating system is usually used for the common business card scanners. In order to enter the editing mode, the user presses the position to be corrected a little longer until a cursor appears, with whose help he can edit the position again. If the text is very small, it is difficult to find the correct position immediately. A double click on the word to be corrected works a bit better. This marks the whole text block and instead of a simple cursor two cursors appear, which are provided with a pinhead, with whose help these can be moved.

Most business card scanners display the corresponding business card section enlarged in editing mode, so the user can compare with the original when correcting.

Until today, the author only knows one application that deals with the problem of incorrectly assigned fields. The Android application Business Card Reader for HubSpot CRM displays an exchange symbol behind each field of the contact form. If a contact element has been incorrectly assigned, the user can tap the symbol to open a selection of the remaining contact fields and select the correct element. Other applications do not explicitly handle the case of incorrectly assigned fields. Fields that have been changed must be completely rewritten using the normal editing mode.

Objectives

In the course of this work a module shall be developed which solves the correction process of business card scanners with regard to usability better than established applications. For this purpose, two control elements or features will be developed which deal with the problem of swapped assignment and incorrect contact data.

Drag&Drop Feature - To correct incorrectly assigned contact elements in a user-friendly way, it should be possible in the module to be developed to drag and drop the contact elements to the correct position. The contact elements are visually highlighted to suggest to the user that the elements are mobile. If such an element is dragged into a contact field and released, the contact field ensures that the element is integrated into existing elements.

Edit Feature - in edit mode, the element is greatly enlarged and displayed in a scrabble-like letter grid, so that the user hits the area that is to be corrected better with his finger.

Procedure

The procedure will be based on the user-centered design process, i.e. it will be carried out iteratively and by involving a test user group.

At the beginning of the first iteration, a test group has to be put together to be used for evaluation. The test group itself should reflect the user group of business card scanners as far as possible.

There will be at least one iteration in which the concept is planned and implemented. The evaluation after the development may result in further iterations.

The project created for the work will not contain an independent scanner.

Both features can be integrated into the project separately from each other, which makes it possible to have them evaluated in isolation by the test users.

  • Module 1 - the form gets neither of the two features. The user can only make corrections using the editing function provided by the operating system.
  • Module 2 - the user gets the edit feature to correct erroneous data.
  • Module 3 - the user gets the Drag&Drop feature to correct erroneous data.
  • Module 4 - the user gets the Edit and Drag&Drop features to correct erroneous data.

References

M. Ecker. Usability und Usability Engineering zur Gestaltung von Lernsystemen. Technische Berichte. Pädagogische Hochschule Weingarten, 2016.

Kathrin Figl. Isonorm 9241/10 und isometrics: Usability-fragebögen im vergleich. In Hartmut Wandke, Saskia Kain, and Doreen Struve, editors, Mensch & Computer, pages 143–152. Oldenbourg Verlag, 2009.

DIN Deutsches Institut für Normung (Berlin). Ergonomie der Mensch- System-Interaktion: Teil 210: Prozess zur Gestaltung gebrauchstauglicher interaktiver Systeme (ISO 9241-210:2010) : Deutsche Fassung EN ISO 9241- 210:2010 : part 2010: Human-centred design for interactive systems (ISO 9241-210:2010). Deutsche Norm. DIN Deutsches Institut fu ̈r Normung, 2010.

John D. Gould and Clayton Lewis. Designing for usability: Key principles and what designers think. Commun. ACM, 28(3):300–311, March 1985.

Susanne Hanst. Agil und kundenorientiert? arbeiten bei autoscout24. In Henning Brau, Andreas Lehmann, Kostanija Petrovic, and Matthias C. Schro- eder, editors, Tagungsband UP12, pages 268–273, Stuttgart, 2012. German UPA e.V.

Marc Hassenzahl, Michael Burmester, and Franz Koller. Attrakdiff: Ein fragebogen zur messung wahrgenommener hedonischer und pragmatischer qualität. In Gerd Szwillus and Jürgen Ziegler, editors, Mensch & Computer 2003: Interaktion in Bewegung, pages 187–196, Stuttgart, 2003. B. G. Teubner.

Marc Hassenzahl, Axel Platz, Michael Burmester, and Katrin Lehner. Hedonic and ergonomic quality aspects determine a software’s appeal. CHI ’00: Proceedings of the SIGCHI conference on Human factors in computing systems, April 2000.

Apple Inc. The Swift Programming Language (Swift 4) - Swift is a fantastic way to write software, whether it’s for phones, desktops, servers, or anything else that runs code. Wattanakarn Vladimirova, 2017.

Bettina Laugwitz, Martin , and Theo Held. Konstruktion eines fragebogens zur messung der user experience von softwareprodukten. In Andreas M. Hei- necke and Hansjürgen Paul, editors, Mensch und Computer 2006: Mensch und Computer im Strukturwandel, pages 125–134, Mu ̈nchen, 2006. Olden- bourg Verlag.

Donald A. Norman. The Design of Everyday Things. Basic Books, Inc., New York, NY, USA, 2002.

Dennis Pagano and Walid Maalej. User feedback in the appstore: An empirical study. In RE, pages 125–134. IEEE Computer Society, 2013.

Martin Schrepp, Theo Held, and Bettina Laugwitz. Hedonische aspekte be- triebswirtschaftlicher software. In Reinhard Keil-Slawik, Harald Selke, and Gerd Szwillus, editors, Mensch & Computer 2004: Allgegenwärtige Interaktion, pages 127–136, München, 2004. Oldenbourg Verlag.

International Organization For Standardization. ISO 9241-11 - Ergonomic Requirements for Office Work with Visual Display Terminals (VDTs): Part 11: Guidance on Usability. Freuburg i.B., 1998.