Medien Wiki - User contributions [en]

IFD:Nutzerstudien WiSe1314/Gruppe Anmeldung endpresentation

2014-03-14T15:37:52Z

Kede7290:

==Course Aims==

During the course "Nutzerstudien" we focused on the smartphone app "ChatSecure" by interrelating the security of chat apps.
We wanted to find out about the importance of security in chat apps for students at our age. Further we were interested in general expectations they have from chat apps and what their problems/wishes are.
For that purpose we tested the app "ChatSecure" with our target group, accomplished usability tests and so developed a varied design to improve the process of creating an account and of signing in.

==Progress of work==

'''1. Interviews and target group'''
For that reason we started to interview a few people from our social environment as our target group. So we focused on students at the age of 20 - 30. We reached this test persons personally so we met them to conduct the interviews directly.

'''2. Analyse and Assessment'''
After that we analysed the results by summing up, comparing and strucuring them.

'''3. Prototypes and scenarios'''
Then we began to create prototypes. These prototypes also passed through usability tests to further improve the design.
For that prototypes we constructed scenarios which had to be accomplished by the test users.

'''4. Improving Design by Iteration'''
We further improved our design by iteration (five steps) to get our final design.

<span style="color:#598193">Ich denke, dass ''Progress of work'' und ''Course aims'' eine gute und einfache Einleitung sind. </span>

<span style="color:#ee9966">Sounds like a straightforward, useful, and doable plan.</span>

=='''Data gathering: Interviews'''==

table of interview partner:

{| class="wikitable"
|-
! Number
! Age class
! Course of studies
|-
| 1
| <20
| Arts
|-
| 2
| <20
| Arts
|-
| 3
| 20-25
| Science/Engineering
|-
| 4
| 25-30
| Science/Engineering
|-
| 5
| <20
| Fine Arts/Design
|-
| 6
| <20
| Fine Arts/Design
|-
| 7
| <20
| Fine Arts/Design
|}

Reasons for choosing those people:

We wanted to figure out the differences between the students of Arts, Fine Arts/Design and Science/Engineering. So we chose people from our social environment. Because we are students from different courses of studies (Arts, Fine Arts/Design and Science/Engineering) we had the chance to interview these types of students.

Form of accessibility:

From the start we were agreed that we want to reach our target group personally by meeting them at the university (fellow students/friends) or at home (homemates). We wanted to talk to them privately to get detailed information and to observe their chat behaviour.

<span style="color:#ee9966">In person interviews can give you a lot of focused time and information, and can be quite valuable. Did you consider any other less focused methods of gathering information? Like a survey via facebook, etc. Having a more neutral method of getting information from people might give you things that would not be mentioned in an interview.</span>

Central questions:
* What chat apps/programs do you use and for what purposes (one-on-one interviews or group discussions, image, video and link transfer)?
* Where do you see advantages and disadvantages of your favorite chat program?
* How important authentication is for you?
* How should a trustable profile be? What information are important?
* In what situations you prefer the phone or an E-Mail before chatting?
* What are requirements for you to use a new app with guaranteed security?
* How often do you use them and how important they are for you?
* How important is security for you while chatting with people?
* What measures do you probably adopt to be safe?
* What functions and design features do you find most important for a chat app?
<span style="color:#598193">''Kleine Anmerkung für zukünftige Projekte: Fragen "what are the requirements…" und "how often…" sind schwierig gut zu beantworten und ihr erfahrt dadurch vermutlich wenig über die Gründe für das Nutzerverhalten. "Advantages… Disadvantages" und "which measures" sind gut. Fragt nicht nach generellem, sondern nach "wie machst du…" "was machst du…", "warum hilft… wenn du…" – Dinge, die mit Aktionen zu tun haben, und, noch besser, beobachtet werden können.</span>

<span style="color:#ee9966">This is a good range of questions that sounds likely to bring out some of the harder issues of the interface, like finding the threshold where people will give up some security because the interface is too difficult to use. Like the comment above, some of the questions might be too vague without follow-up information. Perhaps there needs to be a couple more targeted questions about examples of when the user gave up on security because of usability issues.</span>

==Observation==

After that we did a usability test with ChatSecure to find out how other users deal with the app.

We wanted to find out if the register and login process is intuitive for the user or not. So we got to know about user's handling with apps and their expectations. We hoped to get suggestions and ideas for a better log in process based on the user's behavior.)

* What observations during the interviews did we make?

The tester was asked to say what she/he was thinking and doing while testing the prototype, which problems she/he had and how they could be solved.
With that method and the video it was possible to find and analyse the issues the tester had.

[https://www.youtube.com/watch?v=zdeTEaDdvy4&feature=youtu.be Usability test]
<br><br><br>

<span style="color:#ee9966">Nice video! Good format. Its definitely very useful for watching how a user navigates the app. The user seemed to feel comfortable enough to react naturally during the process, which is quite important. It would be useful to have a higher resolution video to see the details of what is on the screen. It would be nice to see more of these from other users.</span>

* What is noticeable during that usability test?

During the test we found out...
* ...how the proband approached to the test,
* ...how long it took her/him to understand the system and structure of the app,
* ...which problems appeared
* ...and where the problems appeared.

Results:
We evaluated the usability tests and made a heuristic analysis for creating a new account and the login-progress.
<span style="color:#598193">Der Abschnitt zu Observation zeigt eine gute Strukturierung, da bin ich sehr gespannt auf die Ergebnisse dieser Tests. leider steht unter "What is noticeable during that usability test?" nur welcher Art die Ergebnisse sind ("which problems appeared") und nicht was die Ergebnisse selber sind ("Problems: The ''foo'' irritates users, because it looks like the ''bar'' they already know from ''qux'') Auch die Heuristische Analyse, die ihr gemacht habt, hat eine kurze Hinleitung und deutliche Erwähnung verdient!</span>

[http://www.uni-weimar.de/medien/wiki/IFD:Nutzerstudien_WiSe1314/HeuristicAnalysisAnmeldung heuristic analysis]

<span style="color:#ee9966">The heuristic analysis provides a thorough overview of the issues discovered in the user testing. It would be interesting to see links to specific quotes and actions of users in the testing in relation to the points in the analysis. Then if I want to understand a specific problem better, I find the quotes, or reference in the video (you can link to specific times in a youtube video, for example).</span>

=='''Data Analysis & Main Results'''==

To analyze the data we got, we wrote down the interviews and focused on concisely statements that were important for our task. So we picked out some theses independent from each other and created a kind of digital pin board. There we collected the most important information and tried to arrange the notes into groups. So we got a good summary of our interview results and a much better basis for the designs and improvements.

[[File:Nutzerstudien-Authentifizierung.jpg| 600 px]]

* App Requirements
** It is of prime importance that the app has to be easily accessible. So it has to be widespread to make the user downloading it.
** The app should be for free.
** For the user it’s important to be up-to-date and flexible with messages. So he/she prefers an app for chatting.

* Visual Design
** Complexity takes a lot of time, so you need a simple, intuitive, neatly arranged design, which looks uniform on all gadgets.

* Interface & Functions
**It is handy for the user to have an interface, where you can see who is online at the moment and when a contact was online the last time.
** The app should contain a function to let the user know if the chat partner read the messages because it faciliate the communication.
** The user wants to send out photos/videos.
** The user likes to express its emotion with a lot of smileys.
** The function "writes..." is not necessary.

* Security
** It would be useful to have a password for the app.
** To feel safe, the user desires to have a security warranty.
** It is important that apps are immune from viruses. That means that the app should be save. Our probands talked about some safety gaps they experienced on social platforms and other chat providers they used (e.g. private messages that were published on the public profile, spam mails, ...).
** Important information, link, photos, videos, … are often sent by E-Mail.
** Distrust towards apps results e.g. from missing knowledge about safety and smart phone-apps.
** People use safety-options of social networks (e.g. Facebook) but don’t know, if they really work.

* Authenticity
** If you want a trustworthy profile you have to find a good balance between too much and too little information.
** (To much) Personalized advertising makes the user feel insecure.
** A “real” profile picture is soothing for the user.
** Authenticity doesn't loom large for students personally.

<span style="color:#ee9966">Some sections here are a good collection of overarching ideas for making good software. Other sections here are a couple of specific points, like wanting to see when a user is online. Each section should have a couple overarching ideas, with some important, specific points. For example, what specific things are required to provide an "up-to-date and flexible" messaging experience. What general rules did you learn about security?</span>

==Research and problem solutions==

'''What specific problem we want to solve'''

We want to solve some problems with the login-process we had as we first used the app and make it easier to use.
It's hard and circular to login with one of your accounts, because there are too many steps until you are finally logged in. Moreover the buttons are difficult to find on the interface.
Therefore we want to create a new login-process.

'''Plans – how we want to solve the problem(s)'''

--> Using the method: other application's test:
<span style="color:#598193">Ich freue mich, das ihr hier zusätzliche Methoden (Konkurrenzanalyse) angewandt habt. Das zeigt, dass ihr euch eigene Gedanken macht und eigene Lösungen sucht!</span>

First we start to analyse the login process at other applications.
We found out that WhatsApp is the most widespread app to chat for our target group, second one is the Facebook messanger.

1. WhatsApp

This application doesn't contain a login process. You only have to choose the app to be online and you directly see all of your conversations. It is quite easy and intuitive.

<span style="color:#ee9966">WhatsApp is a good example of sacrificing security and privacy to make it easy to use. WhatsApp definitely provides a simple login, but no app has been able to simplify the login that much without creating serious security and privacy concerns. For example, the WhatsApp login and password are generated based on data from the phone which can leak out. The user cannot even change the password once its leaked. Anyone with that username/password can then read and write messages using that account from anywhere on the internet: http://blog.philippheckel.com/2013/07/05/how-to-sniff-the-whatsapp-password-from-your-android-phone-or-iphone/ </span>

2. Facebook Messenger

This application functions nearly the same way as WhatsApp, so you don't need a password to sign in.

<span style="color:#ee9966">Facebook is a much better example to work with since it does require a password, and it is a password that the user sets and can change.</span>

Our conclusion:

Both applications manage without a password. That's quite intuitive but it isn't quite save. While doing our interviews we experienced that it would be convenient to have a password to have a safety warranty (e.g. in case of losing the smartphone).

<span style="color:#ee9966">One thing that both WhatsApp and Facebook have in common is that they both make the app and they also run the service that the app uses. This is the difficult part of ChatSecure: it is just the app, someone else is providing the service. The advantage is that anyone can provide the service (companies, student groups, universities, individuals, etc.) This means the user can choose a service provider that they trust the most, but that makes the login procedure a lot more complicated. One idea that works well in this kind of situation is having "sensible defaults". That means that the app will choose a specific service by default, and the user can just choose a username and password. Then if the user wants more choice, then can expand a hidden section that contains all of the options. <br /><br />

Another approach is to ask the user a question before setting up the account. Something like "how concerned are you about the security and privacy of this account?" Then based on the answer to that question, ChatSecure would choose the defaults for the user (things like which service, whether to use Tor or not, etc. Then the user could optionally change those defaults.</span>

==First design considerations and ideas==

After the intervies, the observations while usability tests and the comparision with other apps, we could draw the first design conclusion and ideas:

1. We want the process of creating an account and signing in as inutitve as possible (comparable with WhatsApp and Facebook Messenger)
2. We want the app as safe as possible (safer than WhatsApp and Facebook Messenger)

first changings/development ideas:
* additional button for entering a password (if it isn't saved)
* reduce redundant buttons
* clarify inconclusive and obscure functions/buttons

==Prototypes==

'''Version 1'''
<br>
Our first prototype for the login process contains the additional password entering button if it isn't saved. (at the beginning you can choose if you want to save the password for further use or not)
It occurs when you want to switch from offline to online as an extra field.

[[File:Prototyp Anmeldeprozess.jpg|600px]]
<br>
[[File:nutzerstudien_version1_1.JPG|200px]]
[[File:nutzerstudien_version1_2.JPG|200px]]
<br>
<br>
'''Version 2'''

<br>
Our next steps for our prototypes were to thought about a clear arrangement of the contact online/contact offline menu.
In our usability tests we found out, that the design is very confusing and the tester couldn't really find out wich contact was online and who not.
<br>Moreover we separated the symbol of the own status and the symbol of the contact's status, so there's no more confusion.
Now it's clear what your own status is and what's the status of your contacts.
<br>We also added a yellow star on the right side next to the contact's name. That's optional for every contact and a way to fix your favourite contacts on top of the list.

<br>
[[File:nutzerstudien_version2_1.JPG|200px]]
[[File:nutzerstudien_version2_2.JPG|200px]]
[[File:nutzerstudien_version2_3.JPG|200px]]
[[File:nutzerstudien_version2_4.JPG|200px]]
[[File:nutzerstudien_version2_5.JPG|200px]]
<br>
<br>
'''Version 3'''
<br>
For the next iteration we focused on improving the progress of creating an account.
At this juncture we considered that it is very important that the user could follow all of his actions and understands the results.
We also wanted a clear and visible design to show the system status.
<br>We added info buttons near interface-Elements that were misunderstood in our tests. So the user can get fast help without serching for it very long. We think this is a solution helping new users and not annoying user with a bigger knowledge. (images 5,6,7)

[[File:nutzerstudien_version3_1.JPG|200px]]
[[File:nutzerstudien_version3_2.JPG|200px]]
[[File:nutzerstudien_version3_3.JPG|200px]]
[[File:nutzerstudien_version3_4.JPG|200px]]
[[File:nutzerstudien_version3_5.JPG|200px]]
[[File:nutzerstudien_version3_6.JPG|200px]]
[[File:nutzerstudien_version3_7.JPG|200px]]
[[File:nutzerstudien_version3_8.JPG|200px]]
[[File:nutzerstudien_version3_9.JPG|200px]]
[[File:nutzerstudien_version3_10.JPG|200px]]

<br>Furthermore we improved the design for the list of contacts once more and clearly seperated "online" and "offline" from each other in order to prevent mistakes and confusion. This two lists are know reachable with a kind of "tabs". (images 11, 13,14)
<br>
<span style="color:#598193">Bezug zu Bildern herstellen (wie in der Mail angemerkt)</span>

[[File:nutzerstudien_version3_11.JPG|200px]]
[[File:nutzerstudien_version3_12.JPG|200px]]
[[File:nutzerstudien_version3_13.JPG|200px]]
[[File:nutzerstudien_version3_14.JPG|200px]]
<br>
<br>
'''Version 4 - final version'''
<br>
In the last and final version we used an old idea from the first prototype and grided the password-request in the progess of creating an account. (image 5)
<br>Moreover we added all error messages, that appeared in the tests to give feedback to the user in every of this situations and to let her/him decide by her-/himself how to react. (images 6,7 and 10)
<br>
<br>
[[File:nutzerstudien_version3_1.JPG|200px]]
[[File:nutzerstudien_version3_2.JPG|200px]]
[[File:nutzerstudien_version3_3.JPG|200px]]
[[File:nutzerstudien_version3_4.JPG|200px]]
[[File:nutzerstudien_version4_1.JPG|200px]]
[[File:nutzerstudien_version4_2.JPG|200px]]
[[File:nutzerstudien_version4_3.JPG|200px]]
[[File:nutzerstudien_version3_11.JPG|200px]]
[[File:nutzerstudien_version3_12.JPG|200px]]
[[File:nutzerstudien_version4_4.JPG|200px]]
[[File:nutzerstudien_version3_13.JPG|200px]]
[[File:nutzerstudien_version3_14.JPG|200px]]

==Our results==
<span style="color:#598193">Überblick am Schluss: Sehr gut. Wie in der Mail angemerkt, wäre hier ein guter Platz für eine Zusammenfassung der Änderungen, sozusagen ein Design-Fazit.</span>

FINAL DESIGN RESULTS/UPDATES FOR CHATSECURE:

1. additional password entering button

[[File:nutzerstudien_version4_1.JPG|200px]]

2. advice if password is wrong - error message

[[File:nutzerstudien_version4_2.JPG|200px]]

3. generelly error messages in case of no connection/wrong enters

[[File:nutzerstudien_version4_3.JPG|200px]]
[[File:nutzerstudien_version4_4.JPG|200px]]

4. new contact order with several colours - two different design ideas

[[File:nutzerstudien_version3_11.JPG|200px]]
[[File:nutzerstudien_version3_13.JPG|200px]]
[[File:nutzerstudien_version3_14.JPG|200px]]

5. yellow stars for most important contacts

[[File:nutzerstudien_version3_11.JPG|200px]]
[[File:nutzerstudien_version3_13.JPG|200px]]

6. info buttons to improve the user understanding

[[File:nutzerstudien_version3_4.JPG|200px]]
[[File:nutzerstudien_version3_7.JPG|200px]]

Problems we had:

The first user experiences by ourselves with the app "ChatSecure" passed dragging because of difficulties with the process of creating an account. We lost too much time by trying to test the app. It was a huge problem that the app didn't worked with IOS.

What did work well:

Our teamwork worked all time. On the one hand inside the course but especially inside our working group because we regulary organised meetings and were always in contact via messaging about the actual state of affairs.

Furthermore we were well prepared before interviewing so that we could implement that while talking to our target group.

Generally we got sufficient background knowledge for our process of work during the course. So we optained step by step our final design.

IFD:Nutzerstudien WiSe1314

2014-03-13T18:07:55Z

Kede7290: /* End-Term-Presentation */

=Werkmodul Nutzerstudien/Sicherheit und Benutzbarkeit=
jeden Donnerstag, 13:30 bis 16:45, Marienstraße 7 B - Seminarraum 102 (siehe auch: Die Veranstaltung im [http://www.uni-weimar.de/qisserver/rds?state=verpublish&status=init&vmfile=no&publishid=21968&moduleCall=webInfo&publishConfFile=webInfo&publishSubDir=veranstaltung Vorlesungsverzeichnis])


===Aktuelles===
* Ein Teil der Aufgaben werden im Medienwiki (auf dieser Website also) bearbeitet werden. Bitte informiert euch wie ihr euch [https://www.youtube.com/watch?v=3oJF0G25q9Q Anmelden], [https://www.youtube.com/watch?v=PVBOAyd_1Zw Editieren], [https://www.youtube.com/watch?v=hLoOpqCyos0 Formatieren] und [https://www.youtube.com/watch?v=P42Une7fC_g Unterseiten anlegen] könnt (Videos dazu in den Links).

==Beschreibung==
[[File:Messaging_CC2BY_FlickrUser-Håkan_Dahlström.jpg|thumb|right|300px|wer liest mit? ([http://flickr.com/photos/dahlstroms/8041061787/sizes/k/in/photostream/ Bild: Dahlström], [https://creativecommons.org/licenses/by/2.0/ CC-BY])]]
[[File:6930835797 2db7044d34 b.jpg|thumb||right|200px|Interviewen]]
[[File:ExploreChallenge CC-BY-2 FlickrUserServicedesignberlin.jpg|thumb|right|200px|Analysieren]]
''Warum ist eine App nützlich und nutzbar, eine andere nicht?''
''Wie kann ich herrausfinden was meine Nutzer brauchen?''

Im Werkmodul Nutzerstudien werden wir Design und die Funktionen von Apps zur sicheren Kommunikation entwickeln und verbessern.

Wir werden:
* Durch unsere Gespräche und Beobachtungen mehr über Nutzer lernen
* Lernen, welche psychologischen Prinzipien bestimmen, ob etwas leicht oder schwierig zu benutzen ist und damit Designen.
* Wir werden unsere Designs ausprobieren lassen und so Verbesserungsmöglichkeiten erkennen und neue Ideen bekommen.



Um zu lernen, wie wir diese Methoden in der Praxis anwenden, haben wir eine Praxiskooperation mit dem [https://guardianproject.info/ Guardian Project]. Wir haben die Aufgabe, sichere Kommunikation über mobile Apps zu verbessern. Mitarbeiter des Projektes werden uns beraten und Feedback für eure Ideen geben.

Kommunikation, die nicht einfach abgehört oder Personen zugeordnet werden kann, ist für Bürgerrechtler und Journalisten essentiell, wird aber auch von Personen verwendet, die ihre Rechte im Netz nicht geschützt sehen.

Leider ist die Nutzung solcher Methoden nicht einfach. Sicherheitsexperte Bruce Schneier z.B. [http://www.theguardian.com/world/2013/sep/05/nsa-how-to-remain-secure-surveillance gibt Tips], sieht diese Tips aber kritisch, denn: ''»My five tips [for more security] suck. They are not things the average person can use. […] Basically, the average user is screwed.«'' (aus einem [http://www.technologyreview.com/news/519336/bruce-schneier-nsa-spying-is-making-us-less-safe/ Interview mit dem MIT Technology Review]) Zwar wird oft auf [https://en.wikipedia.org/wiki/Rtfm »Nutzererziehung«] verwiesen. Das Argument entschuldigt auch die unbenutzbarsten Lösungen – und selbst erfahrene [http://www.gaudior.net/alma/johnny.pdf Nutzer scheitern] z.B. an Verschlüsselungsprogrammen. Besser wären Lösungen, die praktisch, gut benutzbar und sicher sind. Wir wollen zu solchen Lösungen beitragen.

==Häufige Fragen==

'''Muss ich Programmieren können?''' Nein.

'''Ist das hier alles theoretisch?''' Nein, der Kurs ist nicht theoretisch, im Gegenteil, wir werden die gelehrten Methoden anwenden und sie nutzen, um eine anwendbare, praktische Lösung für Probleme zu schaffen.

'''Ist das wissenschaftlich?''' Jein. Es ist [http://de.wikipedia.org/wiki/Naturwissenschaft wissenschaftlich] in dem Sinne, das die Gestaltung auf (eigenen) Erkenntnissen beruht, die wir auch [http://de.wikipedia.org/wiki/Kritischer_Rationalismus kritisch hinterfragen]. Nicht wissenschaftlich ist, das wir konkrete Probleme lösen, anstatt ein allgemeines Modell zu erstellen. (Vergleiche "Wie verhindere ich, das es umfällt?" mit "warum fallen Dinge nach unten?")

==Voraussetzungen==
* Bereitschaft zu eigener Forschung und Weiterentwicklung von Ideen. Mit einem Konzept, dessen Umsetzung für euch schon absolut feststeht, wird der Kurs freud- wie erkenntnislos.

* Texte auf Englisch lesen, denn es gibt wenig Literatur zu dem Gebiet auf deutsch. Wir lesen nicht viel, und ich wähle keine Texte aus, die den Leser mit [http://dev.null.org/postmodern/ nebulös-abstrakten] Begriffen beeindrucken. Aber es ist hilfreich, sich damit zu beschäftigen was andere bisher herausgefunden haben.

==Bewertung==
* Dokumentation (im Wiki, dabei an die Struktur des Arbeitsbuches halten)
* Vortrag
* Anwesenheit (regelm., max 3x fehlen)

==Anmelden==
Mail an ''jan.dittrich ÄT uni-weimar.de'' mit
* Name, Vorname
* Matrikelnummer
* Studiengang
* Kurzer Text der erklärt, warum ihr Teilnehmen möchtet.

==Vortragsthemen| ''student presentations''==
''Mögliche Vortragsthemen. Bitte nutzt die bereitgestellten Quellen, und macht dann eine eigene Recherche. Bereitet das Thema auf, macht es [http://dilbert.com/strips/comic/2010-01-18/ anschaulich] und nicht einfach nur eine Nacherzählung der Quellen (oder der Stichpunkte auf den Slides).''

'''Vortragsdauer: 15-20min'''
* 7.11 Attacks based on Psychology, [http://www.cl.cam.ac.uk/~rja14/book.html Security Engineering, Chapter 2.2] (Lisa Guth)
* 14.11 Personas: About Face 3, ISBN 0470084111, (page 75-81, 97-106)
* 21.11 'Service Blueprinting, [http://knowledge.wpcarey.asu.edu/article.cfm?articleid=1546 intro], [[wikipedia:Service blueprint|Wikipedia]], [http://www.flickr.com/photos/brandonschauer/3363169836/ template]
* 28.11 Security and Usability: The Case of passwords: [http://www.nngroup.com/articles/security-and-human-factors/ Norman/Nielsen on Sign-On-Usability], [http://www.cl.cam.ac.uk/~rja14/book.html Security Engineering, Chapter 2.4], [https://xkcd.com/936/ xkcd on password strength] (Anna Krieger)
* 05.12 "Intuitivität" [http://www.asktog.com/papers/raskinintuit.html Intuitive = Familiar], [http://www.uie.com/articles/design_intuitive/ The Intuition Gap] (Michèle Eike)
*12.12. Kein Vortrag
*19.12. Prototyping-Tools: [http://pencil.evolus.vn/ Pencil], [http://jquery.com/ jQuery] (Anja Rathgeber)
* 19.12. Parallel Prototyping: [http://www.sigchi.org/chi95/proceedings/shortppr/so_bdy.htm 1995], [http://aaalab.stanford.edu/papers/Parallel_Prototyping_2010.pdf 2010]
* 9.1 Knowledge in the Head, Knowledge in the World. In "The Design of Everyday Things" ("Alltägliche Dinge"), Donald Norman, ISBN 0465067107 (Psychologischer Fokus) (Susanne Pötzsch)
* 16.1. [http://www.gaudior.net/alma/johnny.pdf Why Johnny can't encrypt] a classic Security/HCI paper. (Benjamin Burse)
* 23.1. Paper: [http://technology.open.ac.uk/design/cross/documents/DesignerlyWaysofKnowing.pdf Designerly Ways of knowing]





==Zeitplan==
* '''24.10''': Einführung | ''Introduction''
* '''31.10''' : ''Feiertag''
* '''7.11''': Security
* '''14.11''' : Nutzerforschung: Beobachten und Fragen stellen | ''User Research: Observing and Asking Questions''
* '''21.11''': Datenanalyse, Szenarioerstellung | ''Analyse Data, Create Scenarios''
* '''28.11''': Idenentwicklung | ''Idea Development''
* '''5.12.: Prototyping
[…]
* '''12.12''': 1st Feedback round
[…]

==='''Gruppe Anmeldung'''===
* '''16.01''': heuristische Analyse und Schwachpunkte herausarbeiten <br>
Treffen um den PaperMockUp gestalten <br>
Prototyp in den nächsten zwei Wochen testen (evtl. mehrere Iterationsschritte)
* '''23.01''': Feedback | vorläufige Ergebnisse zusammentragen
* '''30.01''': Verbesserungen vornehmen <br>
Treffen um Wiki-Seite zu aktualisieren <br>
* bis vorlesungsfreie Zeit => Feedback

==='''Gruppe Sicherheit'''===
* '''16.01.:''' Heuristische Analyse fertigstellen und Schwachpunkte der App finden
* '''23.01.:''' Prototypen verbessern (je nach Zeit: für Hoch- und Querformat) und Klickdummy anfertigen
* '''30.01.:''' Fertiggestellten Klickdummy testen
* '''06.02:''' Tests auswerten; Anfangen für die Dokumentation zu sammeln





== Presentation and Documentation of Works==

===First use self observation===
[[/firstUseChatSecure]]

===Mid-Term-Presentations and Mentor Comments===
*[[/Gruppe Anmeldung]]
*[[/Sicherheit (security)]]

===End-Term-Presentation===
*[[/Gruppe Anmeldung endpresentation]]
*[[/Sicherheit endpresentation (security)]]

===Heuristic Analysis===
* Aktuelle [https://guardianproject.info/releases/ Versionen von ChatSecure]
* Wenn die nicht geht: die [https://guardianproject.info/releases/chatsecure-latest.apk stabile Version]

'''Team Anmeldung: [[/HeuristicAnalysisAnmeldung|view the summary]]'''
*[[/HeuristicAnalysisAnmeldung| summary]]
*[[/HeuristicAnalysisAnmeldung Person1]] (Aufgaben: Anmelden, Account erstellen, Einstellungen ("Settings"))
*[[/HeuristicAnalysisAnmeldung Person2]] (Aufgaben: Anmelden, Account erstellen, Einstellungen ("Settings"))
*[[/HeuristicAnalysisAnmeldung Person3]] (Aufgaben: Anmelden, Account erstellen, Einstellungen ("Settings"))

'''Team Sicherheit [[/HeuristicAnalysisSecurity|view the summary]] '''
*[[/HeuristicAnalysisSecurity|summary]]
*[[/HeuristicAnalysisSecurity Person4]] (Aufgaben: Neuen Kontakt hinzufügen, Nachricht verschicken auf den Wegen: Unsicher, Verschlüsselt, Authentifiziert)
*[[/HeuristicAnalysisSecurity Person5]] (Aufgaben: Neuen Kontakt hinzufügen, Nachricht verschicken auf den Wegen: Unsicher, Verschlüsselt, Authentifiziert)
*[[/HeuristicAnalysisSecurity Person6]] (Aufgaben: Neuen Kontakt hinzufügen, Nachricht verschicken auf den Wegen: Unsicher, Verschlüsselt, Authentifiziert)

''Die Analyse sollte am spätestens am 16.1. fertig sein''

{{IFD Nutzerstudien HeuristischeEvaluationAnweisungen}}

Für Material siehe Abschnitt [[#Heuristische Analyse|Materialien/Heuristische Analyse]] auf dieser Seite

===Endabgabe===
====Termine====
* Bis zum Vorlesungszeitende (7.2.) sollen die Entwürfe und Forschungen fertiggestellt sein.
* Bis zum Mi, 5.März 2014 ist die Dokumentation für den Lehrenden und die Designs und Erklärungen für den Projektpartner fertigzustellen. Auf diese Version gibt es Feedback (ca. am 10.), die fertige, darauf hin verbesserte und entgültige Version ist ca. eine Woche später, am 16. März abzugeben.

====Anforderungen====
* '''Gruppe oder/und einzeln?''' Dokumentation für den Lehrenden und die Designs und Erklärungen werden ''pro Gruppe'' erstellt. Wichtige Infos oder Erfahrungen (e.g. eine Person hatte diese und jene Probleme mit dem Interview und hat sich deshalb entschiedenen diese und jene Änderungen anm Vorgehen zu machen) sind mitzudokumentieren (u.U. anonym)
* '''Struktur/Inhalt:''' Die Dokumentation für den Lehrenden lehnt sich am besten an das [[IFD:Human-Centered-Design-Research - Workbook|Arbeitsbuch]] an. Möglicherweise sind nicht alle methodischen Vorschläge auf euer Projekt zutreffend, in diesem Fall kann es sinnvoll sein, die "Abweichung" zu erklären (''xyz'' ist nicht gut geeignet weil …, deshalb haben wir die methode ''xyz'' benutzt", um das und das zu machen)
* '''Format:'''Die Designs und Ergebnisse ''für den Projektpartner'' sind im Wiki zu veröffentlichen, die ''Doku an den Lehrenden'' im Wiki oder als PDF.
* '''Nachvollziehbarkeit:''' Die Designs und Ergebnisse für den Projektpartner sollen ermöglichen die ''Ideen in der Software umzusetzen'' und es soll klar werden wie und warum (oder warum nicht) die Entwürfe so entstanden sind (das Programmieren kosten natürlich auch Zeit, und niemand würde etwas "einfach so" einbauen; Zudem kann es sein das Abweichungen von euren Entwürfen nötig sind – dann sind die Begründungen und Daten wichtig, um etwas ähnliches umzusetzen)
* '''Anschaulich machen:''' Zu den Designs und Ergebnisse für den Projektpartner sollte gehören:
** Ein Text mit Screenshots und Entwurfsskizzen
** Ein Prototyp oder eine andere anschauliche Darstellungsform eures/eurer Entwurfes/Entwürfe

==Arbeits & Übungshilfen==
[[File:GuillocheGeldBitcoin.png|thumb|right|100px|"Geldscheinmuster" (zu Interviewbeispiel)]]
* [[IFD:Human-Centered-Design-Research_-_Workbook|"Workbook"]] in Begleitung zur Praktischen Arbeit als Dokumentation, Gedankenstütze und Reflektionsmöglichkeit
* [[Media:Interview IllustratorUse.mp3|Interview/Beobachtung]]: Thema: "Grafiken erstellen"; zum Ausprobieren von Auswertungsmethoden.
''Begriffe'':
Die erwähnten [https://de.wikipedia.org/wiki/Bitcoin "Bitcoins"] sind eine virtuelle Währung; "Offset" bedeutet soviel wie "Abstand".

Die Ergebnisse von Beobachtung und Fragen werden aufbereitet; [[Zusammenhänge Beispielinterview|Hier einige Zusammenhänge]], die sich aus der Audioaufnahme herrausarbeiten lasse.

===Folien===
* [http://webuser.uni-weimar.de/~fudo5114/talks/defineAndFindAudience.html define and find your audience]
* [http://webuser.uni-weimar.de/~fudo5114/talks/BeobachtenFragen.html Beobachten und Fragen]
* [http://webuser.uni-weimar.de/~fudo5114/talks/Datenanalyse.html Datenanalyse]
* [http://webuser.uni-weimar.de/~fudo5114/talks/VonAnalyseZuIdeen.html Szenarios und DesignStudio-Methode]
** [http://webuser.uni-weimar.de/~fudo5114/workshopapp/ Design Studio Webapp] (kam nicht im Kurs vor ist zum Selbernutzen der Methode aber praktischer als die Folien. Verbesserungsvorschläge willkommen)
* [http://webuser.uni-weimar.de/~fudo5114/talks/Minivortrag_Personas.html Personas erstellen]

==Links und Materialien==
===Security/Usability===
* [http://www.cl.cam.ac.uk/~rja14/book.html Security Engineering, Kapitel 2: Usability and Psychology]
* [https://www.cs.auckland.ac.nz/~pgut001/pubs/stupid.pdf Things that make us stupid] a talk on security (and UIs). Kudos if you get the norman reference.
* Security and Usability: Designing Secure Systems That People Can Use, Lorrie Faith Cranor, Simson Garfinkel et.al., O'Reilly Media, ISBN 0596008279
* [https://csclub.uwaterloo.ca/media/Off-the-Record%20Messaging:%20Useful%20Security%20and%20Privacy%20for%20IM.html Wie Off-The-Record funktioniert und warum]: Usability, Verbreitbarkeit, Effektivität, "Resilienz"/Fehlerresistenz (von [https://en.wikipedia.org/wiki/Ian_Goldberg Ian Goldberg])
* Usability: [http://jnd.org/dn.mss/when_security_gets_in_the_way.html »When Security gets in the Way«] (D. Norman)

===Kyptografie===
* [https://en.khanacademy.org/math/applied-math/cryptography/modern-crypt/v/the-fundamental-theorem-of-arithmetic-1 The intro to cryptography on Khan Academy] several 3-5min Videos. Easy.
* [http://www.mat-d.com/site/rsa-diffie-hellman-explained-in-3-minutes/ Diffie-Hellman-Key-Exchange] – ca. 2 DINA4 pages Text. How can you get a secret key without ever seeing each other or sending it?
* Zur Belohnung nach der Mathematik: [http://www.schneierfacts.com/ Bruce Schneier Facts]. Es hat keinen Bildungswert, ist aber lustig (wenn man ''sehr'' nerdigen Humor mag)

===Ausprobieren…===
* Mobile Applikationen testen, aber kein Telefon zur Hand? (Aber einen PC?): den [https://developer.android.com/sdk/index.html Android-Simulator] nutzen, der ein Android-System auf eurem Computer simuliert. ("SDK-Tools only" reicht aus). Schaut das [https://www.youtube.com/watch?v=4r3o2eBzyrs erklärende Video] an.
* https://guardianproject.info/apps/chatsecure/ ChatSecure]. ist die App, mit der wir u.A. arbeiten werden. Installieren über [https://play.google.com/store/apps/details?id=info.guardianproject.otr.app.im Android Store] oder direkt aus dem [https://guardianproject.info/releases/ChatSecure-v12.6.4-RC3.apk Repository]
* [http://www.pidgin.im/ Pidgin] kann mittels [https://otr.cypherpunks.ca/ OTR-Plugin] sicher mit ChatSecure (und vielen anderen Instant-Messangern) Nachrichten senden.
* man braucht natürlich mindestens einen XMPP-Account. Den kann man z.B. bei [http://einfachjabber.de/reg einfachjabber] oder [https://dukgo.com/blog/using-pidgin-with-xmpp-jabber dukgo] anlegen.

===Bücher Design===
* Interaction Design: Beyond Human-Computer Interaction – Preece, Rogers and Sharp, ISBN 978-0470665763 ''Interaktionsdesign-Bezug, darin aber sehr umfassender Überblick''

* Observing the User Experience: A Practitioner's Guide to User Research, Kuneavski, ISBN 978-1558609235

===Human Centered Design===

* Abläufe Analysieren: [http://mindthegap.blog.bau-ha.us/2013/08/from-research-to-requirements-user-need-tables/316/ User Need Tables] (Quellen sind dort verlinkt)
* Personas erstellen: About Face 3, Cooper et.al. (In der Bib)
* [[IFD:Course_Interaction_Design|Interaktionsdesign-Kurs]] Ein Script zu einem vorhergehenden, ähnlichen Werkmodul.
* [http://www.uxmatters.com/mt/archives/2011/10/research-guidelines-you-wont-find-in-a-textbook.php 3 Regeln für Nutzerforschung: Sich Anfreunden, nicht zum Fragen beantworten da sein, nichts "verkaufen"]
* [http://www.experientia.com/blog/ Putting People First-Blog] (u.A. Forschung, Gender, Bildung etc. im HCD. Keine hurra-wir-sind-toll-Artikel, sondern interessante Inhalte.)

===Mobile Apps===
[http://www.cs.uml.edu/~fredm/courses/91.308-fall05/palm/zenofpalm.pdf The Zen of Palm]. Gute Zusammenfassung.

===Heuristische Analyse===
Hinweis: Eine heuristische Analyse kann das Testen nur ergänzen, aber nicht ersetzen!
* [http://www.nngroup.com/articles/ten-usability-heuristics/ List of Heuristics]
* [http://www.nngroup.com/articles/how-to-conduct-a-heuristic-evaluation/ How to do a heuristic evaluation] (and statistics which number of evaluatiors are best and/or most efficient etc.)

===Software===
* [http://developer.nokia.com/Resources/Tools_and_downloads/Other/Flowella/ Nokia Flowella] für Durchklick-Prototypen
* [http://www.jQuery.com jQuery] für aufwändiger, interaktive Prototypen.

===Nützliches===
* Ein [http://en.wikipedia.org/wiki/Service_blueprint Service Blueprint] zum [http://www.flickr.com/photos/brandonschauer/3363169836/ Download]

* [http://m18.uni-weimar.de/mailman/listinfo/interaction Sign up] for our (inofficial) BU Interaction Design Mailinglist

===Meta===
...das Designen von Designlehre
* [http://www.newyorker.com/reporting/2012/01/30/120130fa_fact_lehrer?currentPage=all Brainstorming: Eine Kritik] (vgl. mit der pro-Brainstorm-Kultur von e.g. Design Thinking)
* Parallel Prototyping:Eine empirische Studie von [http://aaalab.stanford.edu/papers/Parallel_Prototyping_2010.pdf 2010] und einer von [http://www.sigchi.org/chi95/proceedings/shortppr/so_bdy.htm 1995], deren Ergebnisse sehr für paralelles Prototyping sprechen.
* Das Iteration sinnvoll ist, ist auch nix neues, aber auch hier eine [http://www.itu.dk/people/jeppeh/specialeartikler/The%20Efficacy%20of%20Prototyping%20Under%20Time%20Constraints.pdf Studie] dazu
* Gruppen, die sich nach bestehenden Freundschaften zusammenfinden, sind für designerische Gruppenarbeiten [http://www.stanford.edu/~roypea/RoyPDF%20folder/A154_CSCL09_Maldonado_Klemmer_Pea.pdf nicht gut geeignet]
* [http://hci.stanford.edu/publications/2011/PrototypingDynamics/PrototypingDynamics-CHI2011.pdf mehrere Designs erstellen und teilen] ist vorteilhaft. [http://hci.stanford.edu/publications/2012/RepeatedExamplesCogSci2012/RepeatedExamplesCogSci2012.pdf Früh mehrfach Beispiele zu teilen] verbessert Resultate.
* The Reflective Practitioner (D. Schön), ISBN 0465068782

IFD:Nutzerstudien WiSe1314/Gruppe Anmeldung endpresentation mentor

2014-03-13T18:01:50Z

Kede7290: Created page with "==Course Aims== During the course "Nutzerstudien" we focused on the smartphone app "ChatSecure" by interrelating the security of chat apps. We wanted to find out about the imp..."

==Course Aims==

During the course "Nutzerstudien" we focused on the smartphone app "ChatSecure" by interrelating the security of chat apps.
We wanted to find out about the importance of security in chat apps for students at our age. Further we were interessted in generelly expectations they have from chat apps and what their problems/whishes are.
For that purpose we tested the app "ChatSecure" with our target group, accomplished usability tests and so developed a varied design to improve the process of creating an account and of signing in.

==Progress of work==

'''1. Interviews and target group'''
For that reason we started to interview a few people from our social environment as our target group. So we focused on students at the age of 20 - 30. We reached this test persons personally so we met them to conduct the interviews directly.

'''2. Analyse and Assessment'''
After that we analysed the results by summing up, comparing and strucuring them.

'''3. Prototypes and scenarios'''
Then we began to create prototypes. These prototypes also passed through usability tests to further improve the design.
For that prototypes we constructed scenarios which had to be accomplished by the test users.

'''4. Improving Design by Iteration'''
We further improved our design by iteration (five steps) to get our final design.

<span style="color:#598193">Ich denke, dass ''Progress of work'' und ''Course aims'' eine gute und einfache Einleitung sind. </span>

=='''Data gathering: Interviews'''==

table of interview partner:

{| class="wikitable"
|-
! Number
! Age class
! Course of studies
|-
| 1
| <20
| Arts
|-
| 2
| <20
| Arts
|-
| 3
| 20-25
| Science/Engineering
|-
| 4
| 25-30
| Science/Engineering
|-
| 5
| <20
| Fine Arts/Design
|-
| 6
| <20
| Fine Arts/Design
|-
| 7
| <20
| Fine Arts/Design
|}

Reasons for choosing those people:

We wanted to figure out the differences between the students of Arts, Fine Arts/Design and Science/Engineering. So we chose people from our social environment. Because we are students from different courses of studies (Arts, Fine Arts/Design and Science/Engineering) we had the chance to interview these types of students.

Form of accessibility:

From the start we were agreed that we want to reach our target group personally by meeting them at the university (fellow students/friends) or at home (homemates). We wanted to talk to them privately to get detailed information and to observe their chat behaviour.

Central questions:
* What chat apps/programs do you use and for what purposes (one-on-one interviews or group discussions, image, video and link transfer)?
* Where do you see advantages and disadvantages of your favorite chat program?
* How important authentication is for you?
* How should a trustable profile be? What information are important?
* In what situations you prefer the phone or an E-Mail before chatting?
* What are requirements for you to use a new app with guaranteed security?
* How often do you use them and how important they are for you?
* How important is security for you while chatting with people?
* What measures do you probably adopt to be safe?
* What functions and design features do you find most important for a chat app?
<span style="color:#598193">''Kleine Anmerkung für zukünftige Projekte: Fragen "what are the requirements…" und "how often…" sind schwierig gut zu beantworten und ihr erfahrt dadurch vermutlich wenig über die Gründe für das Nutzerverhalten. "Advantages… Disadvantages" und "which measures" sind gut. Fragt nicht nach generellem, sondern nach "wie machst du…" "was machst du…", "warum hilft… wenn du…" – Dinge, die mit Aktionen zu tun haben, und, noch besser, beobachtet werden können.</span>

==Observation==

After that we did a usability test with ChatSecure to find out how other users deal with the app.

We wanted to find out if the register and login process is intuitive for the user or not. So we got to know about user's handling with apps and their expectations. We hoped to get suggestions and ideas for a better log in process based on the user's behavior.)

* What observations during the interviews did we make?

The tester was asked to say what she/he was thinking and doing while testing the prototype, which problems she/he had and how they could be solved.
With that method and the video it was possible to find and analyse the issues the tester had.

[https://www.youtube.com/watch?v=zdeTEaDdvy4&feature=youtu.be Usability test]
<br><br><br>

* What is noticeable during that usability test?

During the test we found out...
* ...how the proband approached to the test,
* ...how long it took her/him to understand the system and structure of the app,
* ...which problems appeared
* ...and where the problems appeared.

Results:
We evaluated the usability tests and made a heuristic analysis for creating a new account and the login-progress.
<span style="color:#598193">Der Abschnitt zu Observation zeigt eine gute Strukturierung, da bin ich sehr gespannt auf die Ergebnisse dieser Tests. leider steht unter "What is noticeable during that usability test?" nur welcher Art die Ergebnisse sind ("which problems appeared") und nicht was die Ergebnisse selber sind ("Problems: The ''foo'' irritates users, because it looks like the ''bar'' they already know from ''qux'') Auch die Heuristische Analyse, die ihr gemacht habt, hat eine kurze Hinleitung und deutliche Erwähnung verdient!</span>

[http://www.uni-weimar.de/medien/wiki/IFD:Nutzerstudien_WiSe1314/HeuristicAnalysisAnmeldung heuristic analysis]

=='''Data Analysis & Main Results'''==

To analyze the data we got, we wrote down the interviews and focused on concisely statements that were important for our task. So we picked out some theses independent from each other and created a kind of digital pin board. There we collected the most important information and tried to arrange the notes into groups. So we got a good summary of our interview results and a much better basis for the designs and improvements.

[[File:Nutzerstudien-Authentifizierung.jpg| 600 px]]

* App Requirements
** It is of prime importance that the app has to be easily accessible. So it has to be widespread to make the user downloading it.
** The app should be for free.
** For the user it’s important to be up-to-date and flexible with messages. So he/she prefers an app for chatting.

* Visual Design
** Complexity takes a lot of time, so you need a simple, intuitive, neatly arranged design, which looks uniform on all gadgets.

* Interface & Functions
**It is handy for the user to have an interface, where you can see who is online at the moment and when a contact was online the last time.
** The app should contain a function to let the user know if the chat partner read the messages because it faciliate the communication.
** The user wants to send out photos/videos.
** The user likes to express its emotion with a lot of smileys.
** The function "writes..." is not necassary.

* Security
** It would be useful to have a password for the app.
** To feel safe, the user desires to have a security warranty.
** It is important that apps are immune from viruses. That means that the app should be save. Our probands talked about some safety gaps they experienced on social platforms and other chat providers they used (e.g. private messages that were published on the public profile, spam mails, ...).
** Important information, link, photos, videos, … are often sent by E-Mail.
** Distrust towards apps results e.g. from missing knowledge about safety and smart phone-apps.
** People use safety-options of social networks (e.g. Facebook) but don’t know, if they really work.

* Authenticity
** If you want a trustworthy profile you have to find a good balance between too much and too little information.
** (To much) Personalized advertising makes the user feel insecure.
** A “real” profile picture is soothing for the user.
** Authenticity doesn't loom large for students personally.

==Research and problem solutions==

'''What specific problem we want to solve'''

We want to solve some problems with the login-process we had as we first used the app and make it easier to use.
It's hard and circular to login with one of your accounts, because there are too many steps until you are finally logged in. Moreover the buttons are difficult to find on the interface.
Therefore we want to create a new login-process.

'''Plans – how we want to solve the problem(s)'''

--> Using the method: other application's test:
<span style="color:#598193">Ich freue mich, das ihr hier zusätzliche Methoden (Konkurrenzanalyse) angewandt habt. Das zeigt, dass ihr euch eigene Gedanken macht und eigene Lösungen sucht!</span>

First we start to analyse the login process at other applications.
We found out that WhatsApp is the most widespread app to chat for our target group, second one is the Facebook messanger.

1. WhatsApp

This application doesn't contain a login process. You only have to choose the app to be online and you directly see all of your conversations. It is quite easy and intuitive.

2. Facebook Messenger

This application functions nearly the same way as WhatsApp, so you don't need a password to sign in.

Our conclusion:

Both applications manage without a password. That's quite intuitive but it isn't quite save. While doing our interviews we experienced that it would be convenient to have a password to have a safety warranty (e.g. in case of losing the smartphone).

==First design considerations and ideas==

After the intervies, the observations while usability tests and the comparision with other apps, we could draw the first design conclusion and ideas:

1. We want the process of creating an account and signing in as inutitve as possible (comparable with WhatsApp and Facebook Messenger)
2. We want the app as safe as possible (safer than WhatsApp and Facebook Messenger)

first changings/development ideas:
* additional button for entering a password (if it isn't saved)
* reduce redundant buttons
* clarify inconclusive and obscure functions/buttons

==Prototypes==

'''Version 1'''
<br>
Our first prototype for the login process contains the additional password entering button if it isn't saved. (at the beginning you can choose if you want to save the password for further use or not)
It occurs when you want to switch from offline to online as an extra field.

[[File:Prototyp Anmeldeprozess.jpg|600px]]
<br>
[[File:nutzerstudien_version1_1.JPG|200px]]
[[File:nutzerstudien_version1_2.JPG|200px]]
<br>
<br>
'''Version 2'''

<br>
In the next step for our prototype we thought about a clear arrangement of the contact online/contact offline menu. In our usability tests we found out, that the design is very confusing and the tester couldn't really find out wich contact was online and who not.
<br>Moreover we separated the symbol of the own status and the symbol of the contact's status, so there's no more confusion. Now it's clear what your own status is and what's the status of your contacts.
<br>We also added a star on the right side next to the contact's name. That's optional for every contact and a way to fix your favourite contacts on top of the list.

<br>
[[File:nutzerstudien_version2_1.JPG|200px]]
[[File:nutzerstudien_version2_2.JPG|200px]]
[[File:nutzerstudien_version2_3.JPG|200px]]
[[File:nutzerstudien_version2_4.JPG|200px]]
[[File:nutzerstudien_version2_5.JPG|200px]]
<br>
<br>
'''Version 3'''
<br>
For the next iteration we focused on improving the progress of creating an account.
At this juncture we found it very importent that the user could follow all of his actions and understands the results. We also wanted a clear and visible design to show the system status.
<br>We added info buttons near interface-Elements that were misunderstood in our tests. So the user can get fast help without serching for it very long. We think this is a solution helping new users and not annoying user with a bigger knowledge.
<br>Furthermore we improved the design for the list of contacts once more and clearly seperated "online" and "offline" from each other in order to prevent mistakes and confusion. This two lists are know reachable with a kind of "tabs".
<br>
<span style="color:#598193">Bezug zu Bildern herstellen (wie in der Mail angemerkt)</span>
[[File:nutzerstudien_version3_1.JPG|200px]]
[[File:nutzerstudien_version3_2.JPG|200px]]
[[File:nutzerstudien_version3_3.JPG|200px]]
[[File:nutzerstudien_version3_4.JPG|200px]]
[[File:nutzerstudien_version3_5.JPG|200px]]
[[File:nutzerstudien_version3_6.JPG|200px]]
[[File:nutzerstudien_version3_7.JPG|200px]]
[[File:nutzerstudien_version3_8.JPG|200px]]
[[File:nutzerstudien_version3_9.JPG|200px]]
[[File:nutzerstudien_version3_10.JPG|200px]]
[[File:nutzerstudien_version3_11.JPG|200px]]
[[File:nutzerstudien_version3_12.JPG|200px]]
[[File:nutzerstudien_version3_13.JPG|200px]]
[[File:nutzerstudien_version3_14.JPG|200px]]
<br>
<br>
'''Version 4 - final version'''
<br>
In the last and final version we used an old idea from the first prototype and grided the password-request in the progess of creating an account.
<br>Moreover we added all error messages, that appeared in the tests to give feedback to the user in every of this situations and to let her/him decide by her-/himself how to react.
<br>
<br>
[[File:nutzerstudien_version3_1.JPG|200px]]
[[File:nutzerstudien_version3_2.JPG|200px]]
[[File:nutzerstudien_version3_3.JPG|200px]]
[[File:nutzerstudien_version3_4.JPG|200px]]
[[File:nutzerstudien_version4_1.JPG|200px]]
[[File:nutzerstudien_version4_2.JPG|200px]]
[[File:nutzerstudien_version4_3.JPG|200px]]
[[File:nutzerstudien_version3_11.JPG|200px]]
[[File:nutzerstudien_version3_12.JPG|200px]]
[[File:nutzerstudien_version4_4.JPG|200px]]
[[File:nutzerstudien_version3_13.JPG|200px]]
[[File:nutzerstudien_version3_14.JPG|200px]]

==Our design conclusions==

Problems we had:

The first user experiences by ourselves with the app "ChatSecure" passed dragging because of difficulties with the process of creating an account. We lost too much time by trying to test the app. It was a huge problem that the app didn't worked with IOS.

IFD:Nutzerstudien WiSe1314

2014-03-13T18:00:24Z

Kede7290: /* End-Term-Presentation */

=Werkmodul Nutzerstudien/Sicherheit und Benutzbarkeit=
jeden Donnerstag, 13:30 bis 16:45, Marienstraße 7 B - Seminarraum 102 (siehe auch: Die Veranstaltung im [http://www.uni-weimar.de/qisserver/rds?state=verpublish&status=init&vmfile=no&publishid=21968&moduleCall=webInfo&publishConfFile=webInfo&publishSubDir=veranstaltung Vorlesungsverzeichnis])


===Aktuelles===
* Ein Teil der Aufgaben werden im Medienwiki (auf dieser Website also) bearbeitet werden. Bitte informiert euch wie ihr euch [https://www.youtube.com/watch?v=3oJF0G25q9Q Anmelden], [https://www.youtube.com/watch?v=PVBOAyd_1Zw Editieren], [https://www.youtube.com/watch?v=hLoOpqCyos0 Formatieren] und [https://www.youtube.com/watch?v=P42Une7fC_g Unterseiten anlegen] könnt (Videos dazu in den Links).

==Beschreibung==
[[File:Messaging_CC2BY_FlickrUser-Håkan_Dahlström.jpg|thumb|right|300px|wer liest mit? ([http://flickr.com/photos/dahlstroms/8041061787/sizes/k/in/photostream/ Bild: Dahlström], [https://creativecommons.org/licenses/by/2.0/ CC-BY])]]
[[File:6930835797 2db7044d34 b.jpg|thumb||right|200px|Interviewen]]
[[File:ExploreChallenge CC-BY-2 FlickrUserServicedesignberlin.jpg|thumb|right|200px|Analysieren]]
''Warum ist eine App nützlich und nutzbar, eine andere nicht?''
''Wie kann ich herrausfinden was meine Nutzer brauchen?''

Im Werkmodul Nutzerstudien werden wir Design und die Funktionen von Apps zur sicheren Kommunikation entwickeln und verbessern.

Wir werden:
* Durch unsere Gespräche und Beobachtungen mehr über Nutzer lernen
* Lernen, welche psychologischen Prinzipien bestimmen, ob etwas leicht oder schwierig zu benutzen ist und damit Designen.
* Wir werden unsere Designs ausprobieren lassen und so Verbesserungsmöglichkeiten erkennen und neue Ideen bekommen.



Um zu lernen, wie wir diese Methoden in der Praxis anwenden, haben wir eine Praxiskooperation mit dem [https://guardianproject.info/ Guardian Project]. Wir haben die Aufgabe, sichere Kommunikation über mobile Apps zu verbessern. Mitarbeiter des Projektes werden uns beraten und Feedback für eure Ideen geben.

Kommunikation, die nicht einfach abgehört oder Personen zugeordnet werden kann, ist für Bürgerrechtler und Journalisten essentiell, wird aber auch von Personen verwendet, die ihre Rechte im Netz nicht geschützt sehen.

Leider ist die Nutzung solcher Methoden nicht einfach. Sicherheitsexperte Bruce Schneier z.B. [http://www.theguardian.com/world/2013/sep/05/nsa-how-to-remain-secure-surveillance gibt Tips], sieht diese Tips aber kritisch, denn: ''»My five tips [for more security] suck. They are not things the average person can use. […] Basically, the average user is screwed.«'' (aus einem [http://www.technologyreview.com/news/519336/bruce-schneier-nsa-spying-is-making-us-less-safe/ Interview mit dem MIT Technology Review]) Zwar wird oft auf [https://en.wikipedia.org/wiki/Rtfm »Nutzererziehung«] verwiesen. Das Argument entschuldigt auch die unbenutzbarsten Lösungen – und selbst erfahrene [http://www.gaudior.net/alma/johnny.pdf Nutzer scheitern] z.B. an Verschlüsselungsprogrammen. Besser wären Lösungen, die praktisch, gut benutzbar und sicher sind. Wir wollen zu solchen Lösungen beitragen.

==Häufige Fragen==

'''Muss ich Programmieren können?''' Nein.

'''Ist das hier alles theoretisch?''' Nein, der Kurs ist nicht theoretisch, im Gegenteil, wir werden die gelehrten Methoden anwenden und sie nutzen, um eine anwendbare, praktische Lösung für Probleme zu schaffen.

'''Ist das wissenschaftlich?''' Jein. Es ist [http://de.wikipedia.org/wiki/Naturwissenschaft wissenschaftlich] in dem Sinne, das die Gestaltung auf (eigenen) Erkenntnissen beruht, die wir auch [http://de.wikipedia.org/wiki/Kritischer_Rationalismus kritisch hinterfragen]. Nicht wissenschaftlich ist, das wir konkrete Probleme lösen, anstatt ein allgemeines Modell zu erstellen. (Vergleiche "Wie verhindere ich, das es umfällt?" mit "warum fallen Dinge nach unten?")

==Voraussetzungen==
* Bereitschaft zu eigener Forschung und Weiterentwicklung von Ideen. Mit einem Konzept, dessen Umsetzung für euch schon absolut feststeht, wird der Kurs freud- wie erkenntnislos.

* Texte auf Englisch lesen, denn es gibt wenig Literatur zu dem Gebiet auf deutsch. Wir lesen nicht viel, und ich wähle keine Texte aus, die den Leser mit [http://dev.null.org/postmodern/ nebulös-abstrakten] Begriffen beeindrucken. Aber es ist hilfreich, sich damit zu beschäftigen was andere bisher herausgefunden haben.

==Bewertung==
* Dokumentation (im Wiki, dabei an die Struktur des Arbeitsbuches halten)
* Vortrag
* Anwesenheit (regelm., max 3x fehlen)

==Anmelden==
Mail an ''jan.dittrich ÄT uni-weimar.de'' mit
* Name, Vorname
* Matrikelnummer
* Studiengang
* Kurzer Text der erklärt, warum ihr Teilnehmen möchtet.

==Vortragsthemen| ''student presentations''==
''Mögliche Vortragsthemen. Bitte nutzt die bereitgestellten Quellen, und macht dann eine eigene Recherche. Bereitet das Thema auf, macht es [http://dilbert.com/strips/comic/2010-01-18/ anschaulich] und nicht einfach nur eine Nacherzählung der Quellen (oder der Stichpunkte auf den Slides).''

'''Vortragsdauer: 15-20min'''
* 7.11 Attacks based on Psychology, [http://www.cl.cam.ac.uk/~rja14/book.html Security Engineering, Chapter 2.2] (Lisa Guth)
* 14.11 Personas: About Face 3, ISBN 0470084111, (page 75-81, 97-106)
* 21.11 'Service Blueprinting, [http://knowledge.wpcarey.asu.edu/article.cfm?articleid=1546 intro], [[wikipedia:Service blueprint|Wikipedia]], [http://www.flickr.com/photos/brandonschauer/3363169836/ template]
* 28.11 Security and Usability: The Case of passwords: [http://www.nngroup.com/articles/security-and-human-factors/ Norman/Nielsen on Sign-On-Usability], [http://www.cl.cam.ac.uk/~rja14/book.html Security Engineering, Chapter 2.4], [https://xkcd.com/936/ xkcd on password strength] (Anna Krieger)
* 05.12 "Intuitivität" [http://www.asktog.com/papers/raskinintuit.html Intuitive = Familiar], [http://www.uie.com/articles/design_intuitive/ The Intuition Gap] (Michèle Eike)
*12.12. Kein Vortrag
*19.12. Prototyping-Tools: [http://pencil.evolus.vn/ Pencil], [http://jquery.com/ jQuery] (Anja Rathgeber)
* 19.12. Parallel Prototyping: [http://www.sigchi.org/chi95/proceedings/shortppr/so_bdy.htm 1995], [http://aaalab.stanford.edu/papers/Parallel_Prototyping_2010.pdf 2010]
* 9.1 Knowledge in the Head, Knowledge in the World. In "The Design of Everyday Things" ("Alltägliche Dinge"), Donald Norman, ISBN 0465067107 (Psychologischer Fokus) (Susanne Pötzsch)
* 16.1. [http://www.gaudior.net/alma/johnny.pdf Why Johnny can't encrypt] a classic Security/HCI paper. (Benjamin Burse)
* 23.1. Paper: [http://technology.open.ac.uk/design/cross/documents/DesignerlyWaysofKnowing.pdf Designerly Ways of knowing]





==Zeitplan==
* '''24.10''': Einführung | ''Introduction''
* '''31.10''' : ''Feiertag''
* '''7.11''': Security
* '''14.11''' : Nutzerforschung: Beobachten und Fragen stellen | ''User Research: Observing and Asking Questions''
* '''21.11''': Datenanalyse, Szenarioerstellung | ''Analyse Data, Create Scenarios''
* '''28.11''': Idenentwicklung | ''Idea Development''
* '''5.12.: Prototyping
[…]
* '''12.12''': 1st Feedback round
[…]

==='''Gruppe Anmeldung'''===
* '''16.01''': heuristische Analyse und Schwachpunkte herausarbeiten <br>
Treffen um den PaperMockUp gestalten <br>
Prototyp in den nächsten zwei Wochen testen (evtl. mehrere Iterationsschritte)
* '''23.01''': Feedback | vorläufige Ergebnisse zusammentragen
* '''30.01''': Verbesserungen vornehmen <br>
Treffen um Wiki-Seite zu aktualisieren <br>
* bis vorlesungsfreie Zeit => Feedback

==='''Gruppe Sicherheit'''===
* '''16.01.:''' Heuristische Analyse fertigstellen und Schwachpunkte der App finden
* '''23.01.:''' Prototypen verbessern (je nach Zeit: für Hoch- und Querformat) und Klickdummy anfertigen
* '''30.01.:''' Fertiggestellten Klickdummy testen
* '''06.02:''' Tests auswerten; Anfangen für die Dokumentation zu sammeln





== Presentation and Documentation of Works==

===First use self observation===
[[/firstUseChatSecure]]

===Mid-Term-Presentations and Mentor Comments===
*[[/Gruppe Anmeldung]]
*[[/Sicherheit (security)]]

===End-Term-Presentation===
*[[/Gruppe Anmeldung endpresentation]]
*[[/Gruppe Anmeldung endpresentation mentor]]
*[[/Sicherheit endpresentation (security)]]

===Heuristic Analysis===
* Aktuelle [https://guardianproject.info/releases/ Versionen von ChatSecure]
* Wenn die nicht geht: die [https://guardianproject.info/releases/chatsecure-latest.apk stabile Version]

'''Team Anmeldung: [[/HeuristicAnalysisAnmeldung|view the summary]]'''
*[[/HeuristicAnalysisAnmeldung| summary]]
*[[/HeuristicAnalysisAnmeldung Person1]] (Aufgaben: Anmelden, Account erstellen, Einstellungen ("Settings"))
*[[/HeuristicAnalysisAnmeldung Person2]] (Aufgaben: Anmelden, Account erstellen, Einstellungen ("Settings"))
*[[/HeuristicAnalysisAnmeldung Person3]] (Aufgaben: Anmelden, Account erstellen, Einstellungen ("Settings"))

'''Team Sicherheit [[/HeuristicAnalysisSecurity|view the summary]] '''
*[[/HeuristicAnalysisSecurity|summary]]
*[[/HeuristicAnalysisSecurity Person4]] (Aufgaben: Neuen Kontakt hinzufügen, Nachricht verschicken auf den Wegen: Unsicher, Verschlüsselt, Authentifiziert)
*[[/HeuristicAnalysisSecurity Person5]] (Aufgaben: Neuen Kontakt hinzufügen, Nachricht verschicken auf den Wegen: Unsicher, Verschlüsselt, Authentifiziert)
*[[/HeuristicAnalysisSecurity Person6]] (Aufgaben: Neuen Kontakt hinzufügen, Nachricht verschicken auf den Wegen: Unsicher, Verschlüsselt, Authentifiziert)

''Die Analyse sollte am spätestens am 16.1. fertig sein''

{{IFD Nutzerstudien HeuristischeEvaluationAnweisungen}}

Für Material siehe Abschnitt [[#Heuristische Analyse|Materialien/Heuristische Analyse]] auf dieser Seite

===Endabgabe===
====Termine====
* Bis zum Vorlesungszeitende (7.2.) sollen die Entwürfe und Forschungen fertiggestellt sein.
* Bis zum Mi, 5.März 2014 ist die Dokumentation für den Lehrenden und die Designs und Erklärungen für den Projektpartner fertigzustellen. Auf diese Version gibt es Feedback (ca. am 10.), die fertige, darauf hin verbesserte und entgültige Version ist ca. eine Woche später, am 16. März abzugeben.

====Anforderungen====
* '''Gruppe oder/und einzeln?''' Dokumentation für den Lehrenden und die Designs und Erklärungen werden ''pro Gruppe'' erstellt. Wichtige Infos oder Erfahrungen (e.g. eine Person hatte diese und jene Probleme mit dem Interview und hat sich deshalb entschiedenen diese und jene Änderungen anm Vorgehen zu machen) sind mitzudokumentieren (u.U. anonym)
* '''Struktur/Inhalt:''' Die Dokumentation für den Lehrenden lehnt sich am besten an das [[IFD:Human-Centered-Design-Research - Workbook|Arbeitsbuch]] an. Möglicherweise sind nicht alle methodischen Vorschläge auf euer Projekt zutreffend, in diesem Fall kann es sinnvoll sein, die "Abweichung" zu erklären (''xyz'' ist nicht gut geeignet weil …, deshalb haben wir die methode ''xyz'' benutzt", um das und das zu machen)
* '''Format:'''Die Designs und Ergebnisse ''für den Projektpartner'' sind im Wiki zu veröffentlichen, die ''Doku an den Lehrenden'' im Wiki oder als PDF.
* '''Nachvollziehbarkeit:''' Die Designs und Ergebnisse für den Projektpartner sollen ermöglichen die ''Ideen in der Software umzusetzen'' und es soll klar werden wie und warum (oder warum nicht) die Entwürfe so entstanden sind (das Programmieren kosten natürlich auch Zeit, und niemand würde etwas "einfach so" einbauen; Zudem kann es sein das Abweichungen von euren Entwürfen nötig sind – dann sind die Begründungen und Daten wichtig, um etwas ähnliches umzusetzen)
* '''Anschaulich machen:''' Zu den Designs und Ergebnisse für den Projektpartner sollte gehören:
** Ein Text mit Screenshots und Entwurfsskizzen
** Ein Prototyp oder eine andere anschauliche Darstellungsform eures/eurer Entwurfes/Entwürfe

==Arbeits & Übungshilfen==
[[File:GuillocheGeldBitcoin.png|thumb|right|100px|"Geldscheinmuster" (zu Interviewbeispiel)]]
* [[IFD:Human-Centered-Design-Research_-_Workbook|"Workbook"]] in Begleitung zur Praktischen Arbeit als Dokumentation, Gedankenstütze und Reflektionsmöglichkeit
* [[Media:Interview IllustratorUse.mp3|Interview/Beobachtung]]: Thema: "Grafiken erstellen"; zum Ausprobieren von Auswertungsmethoden.
''Begriffe'':
Die erwähnten [https://de.wikipedia.org/wiki/Bitcoin "Bitcoins"] sind eine virtuelle Währung; "Offset" bedeutet soviel wie "Abstand".

Die Ergebnisse von Beobachtung und Fragen werden aufbereitet; [[Zusammenhänge Beispielinterview|Hier einige Zusammenhänge]], die sich aus der Audioaufnahme herrausarbeiten lasse.

===Folien===
* [http://webuser.uni-weimar.de/~fudo5114/talks/defineAndFindAudience.html define and find your audience]
* [http://webuser.uni-weimar.de/~fudo5114/talks/BeobachtenFragen.html Beobachten und Fragen]
* [http://webuser.uni-weimar.de/~fudo5114/talks/Datenanalyse.html Datenanalyse]
* [http://webuser.uni-weimar.de/~fudo5114/talks/VonAnalyseZuIdeen.html Szenarios und DesignStudio-Methode]
** [http://webuser.uni-weimar.de/~fudo5114/workshopapp/ Design Studio Webapp] (kam nicht im Kurs vor ist zum Selbernutzen der Methode aber praktischer als die Folien. Verbesserungsvorschläge willkommen)
* [http://webuser.uni-weimar.de/~fudo5114/talks/Minivortrag_Personas.html Personas erstellen]

==Links und Materialien==
===Security/Usability===
* [http://www.cl.cam.ac.uk/~rja14/book.html Security Engineering, Kapitel 2: Usability and Psychology]
* [https://www.cs.auckland.ac.nz/~pgut001/pubs/stupid.pdf Things that make us stupid] a talk on security (and UIs). Kudos if you get the norman reference.
* Security and Usability: Designing Secure Systems That People Can Use, Lorrie Faith Cranor, Simson Garfinkel et.al., O'Reilly Media, ISBN 0596008279
* [https://csclub.uwaterloo.ca/media/Off-the-Record%20Messaging:%20Useful%20Security%20and%20Privacy%20for%20IM.html Wie Off-The-Record funktioniert und warum]: Usability, Verbreitbarkeit, Effektivität, "Resilienz"/Fehlerresistenz (von [https://en.wikipedia.org/wiki/Ian_Goldberg Ian Goldberg])
* Usability: [http://jnd.org/dn.mss/when_security_gets_in_the_way.html »When Security gets in the Way«] (D. Norman)

===Kyptografie===
* [https://en.khanacademy.org/math/applied-math/cryptography/modern-crypt/v/the-fundamental-theorem-of-arithmetic-1 The intro to cryptography on Khan Academy] several 3-5min Videos. Easy.
* [http://www.mat-d.com/site/rsa-diffie-hellman-explained-in-3-minutes/ Diffie-Hellman-Key-Exchange] – ca. 2 DINA4 pages Text. How can you get a secret key without ever seeing each other or sending it?
* Zur Belohnung nach der Mathematik: [http://www.schneierfacts.com/ Bruce Schneier Facts]. Es hat keinen Bildungswert, ist aber lustig (wenn man ''sehr'' nerdigen Humor mag)

===Ausprobieren…===
* Mobile Applikationen testen, aber kein Telefon zur Hand? (Aber einen PC?): den [https://developer.android.com/sdk/index.html Android-Simulator] nutzen, der ein Android-System auf eurem Computer simuliert. ("SDK-Tools only" reicht aus). Schaut das [https://www.youtube.com/watch?v=4r3o2eBzyrs erklärende Video] an.
* https://guardianproject.info/apps/chatsecure/ ChatSecure]. ist die App, mit der wir u.A. arbeiten werden. Installieren über [https://play.google.com/store/apps/details?id=info.guardianproject.otr.app.im Android Store] oder direkt aus dem [https://guardianproject.info/releases/ChatSecure-v12.6.4-RC3.apk Repository]
* [http://www.pidgin.im/ Pidgin] kann mittels [https://otr.cypherpunks.ca/ OTR-Plugin] sicher mit ChatSecure (und vielen anderen Instant-Messangern) Nachrichten senden.
* man braucht natürlich mindestens einen XMPP-Account. Den kann man z.B. bei [http://einfachjabber.de/reg einfachjabber] oder [https://dukgo.com/blog/using-pidgin-with-xmpp-jabber dukgo] anlegen.

===Bücher Design===
* Interaction Design: Beyond Human-Computer Interaction – Preece, Rogers and Sharp, ISBN 978-0470665763 ''Interaktionsdesign-Bezug, darin aber sehr umfassender Überblick''

* Observing the User Experience: A Practitioner's Guide to User Research, Kuneavski, ISBN 978-1558609235

===Human Centered Design===

* Abläufe Analysieren: [http://mindthegap.blog.bau-ha.us/2013/08/from-research-to-requirements-user-need-tables/316/ User Need Tables] (Quellen sind dort verlinkt)
* Personas erstellen: About Face 3, Cooper et.al. (In der Bib)
* [[IFD:Course_Interaction_Design|Interaktionsdesign-Kurs]] Ein Script zu einem vorhergehenden, ähnlichen Werkmodul.
* [http://www.uxmatters.com/mt/archives/2011/10/research-guidelines-you-wont-find-in-a-textbook.php 3 Regeln für Nutzerforschung: Sich Anfreunden, nicht zum Fragen beantworten da sein, nichts "verkaufen"]
* [http://www.experientia.com/blog/ Putting People First-Blog] (u.A. Forschung, Gender, Bildung etc. im HCD. Keine hurra-wir-sind-toll-Artikel, sondern interessante Inhalte.)

===Mobile Apps===
[http://www.cs.uml.edu/~fredm/courses/91.308-fall05/palm/zenofpalm.pdf The Zen of Palm]. Gute Zusammenfassung.

===Heuristische Analyse===
Hinweis: Eine heuristische Analyse kann das Testen nur ergänzen, aber nicht ersetzen!
* [http://www.nngroup.com/articles/ten-usability-heuristics/ List of Heuristics]
* [http://www.nngroup.com/articles/how-to-conduct-a-heuristic-evaluation/ How to do a heuristic evaluation] (and statistics which number of evaluatiors are best and/or most efficient etc.)

===Software===
* [http://developer.nokia.com/Resources/Tools_and_downloads/Other/Flowella/ Nokia Flowella] für Durchklick-Prototypen
* [http://www.jQuery.com jQuery] für aufwändiger, interaktive Prototypen.

===Nützliches===
* Ein [http://en.wikipedia.org/wiki/Service_blueprint Service Blueprint] zum [http://www.flickr.com/photos/brandonschauer/3363169836/ Download]

* [http://m18.uni-weimar.de/mailman/listinfo/interaction Sign up] for our (inofficial) BU Interaction Design Mailinglist

===Meta===
...das Designen von Designlehre
* [http://www.newyorker.com/reporting/2012/01/30/120130fa_fact_lehrer?currentPage=all Brainstorming: Eine Kritik] (vgl. mit der pro-Brainstorm-Kultur von e.g. Design Thinking)
* Parallel Prototyping:Eine empirische Studie von [http://aaalab.stanford.edu/papers/Parallel_Prototyping_2010.pdf 2010] und einer von [http://www.sigchi.org/chi95/proceedings/shortppr/so_bdy.htm 1995], deren Ergebnisse sehr für paralelles Prototyping sprechen.
* Das Iteration sinnvoll ist, ist auch nix neues, aber auch hier eine [http://www.itu.dk/people/jeppeh/specialeartikler/The%20Efficacy%20of%20Prototyping%20Under%20Time%20Constraints.pdf Studie] dazu
* Gruppen, die sich nach bestehenden Freundschaften zusammenfinden, sind für designerische Gruppenarbeiten [http://www.stanford.edu/~roypea/RoyPDF%20folder/A154_CSCL09_Maldonado_Klemmer_Pea.pdf nicht gut geeignet]
* [http://hci.stanford.edu/publications/2011/PrototypingDynamics/PrototypingDynamics-CHI2011.pdf mehrere Designs erstellen und teilen] ist vorteilhaft. [http://hci.stanford.edu/publications/2012/RepeatedExamplesCogSci2012/RepeatedExamplesCogSci2012.pdf Früh mehrfach Beispiele zu teilen] verbessert Resultate.
* The Reflective Practitioner (D. Schön), ISBN 0465068782

IFD:Nutzerstudien WiSe1314/Gruppe Anmeldung endpresentation

2014-03-02T20:45:16Z

Kede7290:

IFD:Nutzerstudien WiSe1314/Gruppe Anmeldung endpresentation

2014-03-02T20:26:33Z

Kede7290:

IFD:Nutzerstudien WiSe1314/Gruppe Anmeldung endpresentation

2014-03-02T20:00:26Z

Kede7290:

IFD:Nutzerstudien WiSe1314/Gruppe Anmeldung endpresentation

2014-03-02T19:09:01Z

Kede7290:

IFD:Nutzerstudien WiSe1314/Gruppe Anmeldung endpresentation

2014-01-30T15:11:29Z

Kede7290:

==Course Aims==

During the course "Nutzerstudien" we wanted to know how important security is for students at our age, what they expect from chat apps and what their problems/whishes are.
For that purpose we tested the app "ChatSecure" and tried to improve the design based on usability tests.

Our main focus premised on the process of creating an account and of signing in.

==Progress of work==

'''1. Interviews and target group'''
For that reason we started to interview a few people from our social environment as our target group. So we focused on students at the age of 20 - 30. We reached this test persons personally so we met them to conduct the interviews directly.

'''2. Analyse and Assessment'''
After that we analysed the results (infinity diagramming) by summing up, comparing and strucuring them.

'''3. Prototypes and scenarios'''
Then we began to create prototypes. These prototypes also passed through usability tests to further improve the design.
For that prototypes we constructed scenarios which had to be accomplished by the test users.

'''4. Improving Design by Iteration'''
We further improved our design by iteration (five steps) to get our final design.

=='''Data gathering: Interviews'''==

table of interview partner:

{| class="wikitable"
|-
! Number
! Age class
! Course of studies
|-
| 1
| <20
| Arts
|-
| 2
| <20
| Arts
|-
| 3
| 20-25
| Science/Engineering
|-
| 4
| 25-30
| Science/Engineering
|-
| 5
| <20
| Fine Arts/Design
|-
| 6
| <20
| Fine Arts/Design
|-
| 7
| <20
| Fine Arts/Design
|}

Reasons for choosing these people:

We wanted to figure out the differences between the students of Arts, Fine Arts/Design and Science/Engineering. So we chose people from our social environment. Because we are students from different courses of studies (Arts, Fine Arts/Design and Science/Engineering) we had the chance to interview these types of students. Thereby we had a huge spectrum of users.

Central questions:
* What chat apps/programs do you use and for what purposes (one-on-one interviews or group discussions, image, video and link transfer)?
* Where do you see advantages and disadvantages of your favorite chat program?
* How important authentication is for you?
* How should a trustable profile be? What information are important?
* In what situations you prefer the phone or an E-Mail before chatting?
* What are requirements for you to use a new app with guaranteed security?
* How often do you use them and how important they are for you?
* How important is security for you while chatting with people?
* What measures do you probably adopt to be safe?
* What functions and design features do you find most important for a chat app?

==Observation==

After that we did a usability test with ChatSecure to find out how other users deal with the app.

We wanted to find out if the register and login process is intuitive for the user or not. So we got to know about user's handling with apps and their expectations. We hoped to get suggestions and ideas for a better log in process based on the user's behavior.)

* What observations during the interviews did we make?

-> here the video can be integrated!

* What is noticeable during that usability test?

-> results

=='''Data Analysis & Main Results'''==

[[File:Nutzerstudien-Authentifizierung.jpg| 600 px]]

* App Requirements
** accessibility is of prime importance, so the app have to be widespread to make the user downloading it.
** The app should be for free.
** For the user it’s important to be up-to-date and flexible with messages. So he/she prefers an app for chatting.

* Visual Design
** Complexity takes a lot of time, so you need a simple, intuitive, neatly arranged design, which looks uniform on all gadgets.

* Interface & Functions
**It is handy for the user to have an interface, where you can see who is online at the moment and when a contact was online the last time.
** The app should contain a function to let the user know if the chat partner read the messages because it faciliate the communication.
** The user wants to send out photos/videos.
** The user likes to express its emotion with a lot of smileys.
** The function "writes..." is not necassary.

* Security
** It would be useful to have a password for the app.
** To feel safe, the user desires to have a security warranty.
** It is important that apps are immune from viruses.
** Important information, link, photos, videos, … are often sent by E-Mail.
** Distrust towards apps results e.g. from missing knowledge about safety and smart phone-apps.
** People use safety-options of social networks (e.g. Facebook) but don’t know, if they really work.

* Authenticity
** If you want a trustworthy profile you have to find a good balance between too much and too little information.
** (To much) Personalized advertising makes the user feel insecure.
** A “real” profile picture is soothing for the user.
** Authenticity doesn't loom large for students personally.

==Research and problem solutions==

'''What specific problem we want to solve'''

We want to solve some problems with the login-process and make it easier to use.
It's hard and circular to login with one of your accounts, because there are too many steps until you are finally logged in. Moreover the buttons are difficult to find on the interface.
Therefore we want to create a new login-process.

'''Plans – how we want to solve the problem(s)'''

* Method 1: Other application's test

First we start to analyse the login process at other applications.
We found out that WhatsApp is the most widespread app to chat for our target group, second one is the Facebook messanger.

1. WhatsApp

This application doesn't contain a login process. You only have to choose the app to be online and you directly see all of your conversations. It is quite easy and intuitive.

2. Facebook Messenger

This application functions nearly the same way as WhatsApp, so you don't need a password to sign in.

Our conclusion:

Both applications manage without a password. That's quite intuitive but it isn't quite save. While doing our interviews we experienced that it would be convenient to have a password to have a safety warranty (e.g. in case of losing the smartphone)

==First design considerations and ideas==

We want ChatSecure as intuitive as WhatsApp and Facebook Messenger but we also want it to be staying save. So there have to be an additional button for entering a password and we want to reduce redundant buttons and clarify inconclusive and obscure functions/buttons.

==Prototypes==

Our first prototype for the login process contains the additional password entering button if it isn't saved. (at the beginning you can choose if you want to save the password for further use or not)
It occurs when you want to switch from offline to online as an extra field.

[[File:Prototyp Anmeldeprozess.jpg|600px]]

==Our conclusions==
* problems we had

* what we would do better next time

* our final design

IFD:Nutzerstudien WiSe1314/Gruppe Anmeldung endpresentation

2014-01-30T15:08:15Z

Kede7290:

=='''DOCUMENTATION'''==

In the following you can find a elaborated documentation of the work in the course "Nutzerstudien".

==Course Aims==

During the course "Nutzerstudien" we wanted to know how important security is for students at our age, what they expect from chat apps and what their problems/whishes are.
For that purpose we tested the app "ChatSecure" and tried to improve the design based on usability tests.

Our main focus premised on the process of creating an account and of signing in.

==Progress of work==

'''1. Interviews and target group'''
For that reason we started to interview a few people from our social environment as our target group. So we focused on students at the age of 20 - 30. We reached this test persons personally so we met them to conduct the interviews directly.

'''2. Analyse and Assessment'''
After that we analysed the results (infinity diagramming) by summing up, comparing and strucuring them.

'''3. Prototypes and scenarios'''
Then we began to create prototypes. These prototypes also passed through usability tests to further improve the design.
For that prototypes we constructed scenarios which had to be accomplished by the test users.

'''4. Improving Design by Iteration'''
We further improved our design by iteration (five steps) to get our final design.

=='''Data gathering: Interviews'''==

table of interview partner:

{| class="wikitable"
|-
! Number
! Age class
! Course of studies
|-
| 1
| <20
| Arts
|-
| 2
| <20
| Arts
|-
| 3
| 20-25
| Science/Engineering
|-
| 4
| 25-30
| Science/Engineering
|-
| 5
| <20
| Fine Arts/Design
|-
| 6
| <20
| Fine Arts/Design
|-
| 7
| <20
| Fine Arts/Design
|}

Reasons for choosing these people:

We wanted to figure out the differences between the students of Arts, Fine Arts/Design and Science/Engineering. So we chose people from our social environment. Because we are students from different courses of studies (Arts, Fine Arts/Design and Science/Engineering) we had the chance to interview these types of students. Thereby we had a huge spectrum of users.

Central questions:
* What chat apps/programs do you use and for what purposes (one-on-one interviews or group discussions, image, video and link transfer)?
* Where do you see advantages and disadvantages of your favorite chat program?
* How important authentication is for you?
* How should a trustable profile be? What information are important?
* In what situations you prefer the phone or an E-Mail before chatting?
* What are requirements for you to use a new app with guaranteed security?
* How often do you use them and how important they are for you?
* How important is security for you while chatting with people?
* What measures do you probably adopt to be safe?
* What functions and design features do you find most important for a chat app?

==Observation==

After that we did a usability test with ChatSecure to find out how other users deal with the app.

We wanted to find out if the register and login process is intuitive for the user or not. So we got to know about user's handling with apps and their expectations. We hoped to get suggestions and ideas for a better log in process based on the user's behavior.)

* What observations during the interviews did we make?

-> here the video can be integrated!

* What is noticeable during that usability test?

-> results

=='''Data Analysis & Main Results'''==

[[File:Nutzerstudien-Authentifizierung.jpg| 600 px]]

* App Requirements
** accessibility is of prime importance, so the app have to be widespread to make the user downloading it.
** The app should be for free.
** For the user it’s important to be up-to-date and flexible with messages. So he/she prefers an app for chatting.

* Visual Design
** Complexity takes a lot of time, so you need a simple, intuitive, neatly arranged design, which looks uniform on all gadgets.

* Interface & Functions
**It is handy for the user to have an interface, where you can see who is online at the moment and when a contact was online the last time.
** The app should contain a function to let the user know if the chat partner read the messages because it faciliate the communication.
** The user wants to send out photos/videos.
** The user likes to express its emotion with a lot of smileys.
** The function "writes..." is not necassary.

* Security
** It would be useful to have a password for the app.
** To feel safe, the user desires to have a security warranty.
** It is important that apps are immune from viruses.
** Important information, link, photos, videos, … are often sent by E-Mail.
** Distrust towards apps results e.g. from missing knowledge about safety and smart phone-apps.
** People use safety-options of social networks (e.g. Facebook) but don’t know, if they really work.

* Authenticity
** If you want a trustworthy profile you have to find a good balance between too much and too little information.
** (To much) Personalized advertising makes the user feel insecure.
** A “real” profile picture is soothing for the user.
** Authenticity doesn't loom large for students personally.

==Research and problem solutions==

'''What specific problem we want to solve'''

We want to solve some problems with the login-process and make it easier to use.
It's hard and circular to login with one of your accounts, because there are too many steps until you are finally logged in. Moreover the buttons are difficult to find on the interface.
Therefore we want to create a new login-process.

'''Plans – how we want to solve the problem(s)'''

* Method 1: Other application's test

First we start to analyse the login process at other applications.
We found out that WhatsApp is the most widespread app to chat for our target group, second one is the Facebook messanger.

1. WhatsApp

This application doesn't contain a login process. You only have to choose the app to be online and you directly see all of your conversations. It is quite easy and intuitive.

2. Facebook Messenger

This application functions nearly the same way as WhatsApp, so you don't need a password to sign in.

Our conclusion:

Both applications manage without a password. That's quite intuitive but it isn't quite save. While doing our interviews we experienced that it would be convenient to have a password to have a safety warranty (e.g. in case of losing the smartphone)

==First design considerations and ideas==

We want ChatSecure as intuitive as WhatsApp and Facebook Messenger but we also want it to be staying save. So there have to be an additional button for entering a password and we want to reduce redundant buttons and clarify inconclusive and obscure functions/buttons.

==Prototypes==

Our first prototype for the login process contains the additional password entering button if it isn't saved. (at the beginning you can choose if you want to save the password for further use or not)
It occurs when you want to switch from offline to online as an extra field.

[[File:Prototyp Anmeldeprozess.jpg|600px]]

==Our conclusions==
* problems we had

* what we would do better next time

* our final design

IFD:Nutzerstudien WiSe1314/Gruppe Anmeldung endpresentation

2014-01-30T15:04:48Z

Kede7290:

=='''DOCUMENTATION'''==

==Course Aims==

During the course "Nutzerstudien" we wanted to know how important security is for students at our age, what they expect from chat apps and what their problems/whishes are.
For that purpose we tested the app "ChatSecure" and tried to improve the design based on usability tests.

Our main focus premised on the process of creating an account and of signing in.

==Progress of work==

'''1. Interviews and target group'''
For that reason we started to interview a few people from our social environment as our target group. So we focused on students at the age of 20 - 30. We reached this test persons personally so we met them to conduct the interviews directly.

'''2. Analyse and Assessment'''
After that we analysed the results (infinity diagramming) by summing up, comparing and strucuring them.

'''3. Prototypes and scenarios'''
Then we began to create prototypes. These prototypes also passed through usability tests to further improve the design.
For that prototypes we constructed scenarios which had to be accomplished by the test users.

'''4. Improving Design by Iteration'''
We further improved our design by iteration (five steps) to get our final design.

=='''Data gathering: Interviews'''==

table of interview partner:

{| class="wikitable"
|-
! Number
! Age class
! Course of studies
|-
| 1
| <20
| Arts
|-
| 2
| <20
| Arts
|-
| 3
| 20-25
| Science/Engineering
|-
| 4
| 25-30
| Science/Engineering
|-
| 5
| <20
| Fine Arts/Design
|-
| 6
| <20
| Fine Arts/Design
|-
| 7
| <20
| Fine Arts/Design
|}

Reasons for choosing these people:

We wanted to figure out the differences between the students of Arts, Fine Arts/Design and Science/Engineering. So we chose people from our social environment. Because we are students from different courses of studies (Arts, Fine Arts/Design and Science/Engineering) we had the chance to interview these types of students. Thereby we had a huge spectrum of users.

Central questions:
* What chat apps/programs do you use and for what purposes (one-on-one interviews or group discussions, image, video and link transfer)?
* Where do you see advantages and disadvantages of your favorite chat program?
* How important authentication is for you?
* How should a trustable profile be? What information are important?
* In what situations you prefer the phone or an E-Mail before chatting?
* What are requirements for you to use a new app with guaranteed security?
* How often do you use them and how important they are for you?
* How important is security for you while chatting with people?
* What measures do you probably adopt to be safe?
* What functions and design features do you find most important for a chat app?

==Observation==

* What observations during the interviews did we make?

--> here the video can be integrated!

what is noticeable during these usability test?

(After that we did some usability tests of the app (ChatSecure) to find out how others deal with the login process. We wanted to find out if the register and login process is intuitive for the user or not. So we got to know about user's handling with apps and their expectations. We hoped to get suggestions and ideas for a better log in process based on the user's behavior.)

=='''Data Analysis & Main Results'''==

[[File:Nutzerstudien-Authentifizierung.jpg| 600 px]]

* App Requirements
** accessibility is of prime importance, so the app have to be widespread to make the user downloading it.
** The app should be for free.
** For the user it’s important to be up-to-date and flexible with messages. So he/she prefers an app for chatting.

* Visual Design
** Complexity takes a lot of time, so you need a simple, intuitive, neatly arranged design, which looks uniform on all gadgets.

* Interface & Functions
**It is handy for the user to have an interface, where you can see who is online at the moment and when a contact was online the last time.
** The app should contain a function to let the user know if the chat partner read the messages because it faciliate the communication.
** The user wants to send out photos/videos.
** The user likes to express its emotion with a lot of smileys.
** The function "writes..." is not necassary.

* Security
** It would be useful to have a password for the app.
** To feel safe, the user desires to have a security warranty.
** It is important that apps are immune from viruses.
** Important information, link, photos, videos, … are often sent by E-Mail.
** Distrust towards apps results e.g. from missing knowledge about safety and smart phone-apps.
** People use safety-options of social networks (e.g. Facebook) but don’t know, if they really work.

* Authenticity
** If you want a trustworthy profile you have to find a good balance between too much and too little information.
** (To much) Personalized advertising makes the user feel insecure.
** A “real” profile picture is soothing for the user.
** Authenticity doesn't loom large for students personally.

==Research and problem solutions==

'''What specific problem we want to solve'''

We want to solve some problems with the login-process and make it easier to use.
It's hard and circular to login with one of your accounts, because there are too many steps until you are finally logged in. Moreover the buttons are difficult to find on the interface.
Therefore we want to create a new login-process.

'''Plans – how we want to solve the problem(s)'''

* Method 1: Other application's test

First we start to analyse the login process at other applications.
We found out that WhatsApp is the most widespread app to chat for our target group, second one is the Facebook messanger.

1. WhatsApp

This application doesn't contain a login process. You only have to choose the app to be online and you directly see all of your conversations. It is quite easy and intuitive.

2. Facebook Messenger

This application functions nearly the same way as WhatsApp, so you don't need a password to sign in.

Our conclusion:

Both applications manage without a password. That's quite intuitive but it isn't quite save. While doing our interviews we experienced that it would be convenient to have a password to have a safety warranty (e.g. in case of losing the smartphone)

==First design considerations and ideas==

We want ChatSecure as intuitive as WhatsApp and Facebook Messenger but we also want it to be staying save. So there have to be an additional button for entering a password and we want to reduce redundant buttons and clarify inconclusive and obscure functions/buttons.

==Prototypes==

Our first prototype for the login process contains the additional password entering button if it isn't saved. (at the beginning you can choose if you want to save the password for further use or not)
It occurs when you want to switch from offline to online as an extra field.

[[File:Prototyp Anmeldeprozess.jpg|600px]]

==Our conclusions==
* problems we had

* what we would do better next time

* our final design

IFD:Nutzerstudien WiSe1314/Gruppe Anmeldung endpresentation

2014-01-30T14:41:42Z

Kede7290:

=='''DOCUMENTATION'''==

==Course Aims==

During the course "Nutzerstudien" we wanted to know how important security is for students at our age, what they expect from chat apps and what their problems/whishes are.
For that purpose we tested the app "ChatSecure" and tried to improve the design based on usability tests.

Our main focus premised on the process of creating an account and of signing in.

==Progress of work==

'''1. Interviews and target group'''
For that reason we started to interview a few people from our social environment as our target group. So we focused on students at the age of 20 - 30. We reached this test persons personally so we met them to conduct the interviews directly.

'''2. Analyse and Assessment'''
After that we analysed the results (infinity diagramming) by summing up, comparing and strucuring.

'''3. Prototypes and scenarios'''
Then we began to create prototypes. These prototypes also passed through usability tests to further improve the design.
For that prototypes we constructed scenarios which had to be accomplished by the test users.

'''4. Improving Design by Iteration'''
We further improved our design by iteration (five steps) to get our final design.

=='''Data gathering: Interviews/Target group'''==

interview partner:

{| class="wikitable"
|-
! Number
! Age class
! Course of studies
|-
| 1
| <20
| Arts
|-
| 2
| <20
| Arts
|-
| 3
| 20-25
| Science/Engineering
|-
| 4
| 25-30
| Science/Engineering
|-
| 5
| <20
| Fine Arts/Design
|-
| 6
| <20
| Fine Arts/Design
|-
| 7
| <20
| Fine Arts/Design
|}

Reasons for choosing these people:

We wanted to figure out the differences between the students of Arts, Fine Arts/Design and Science/Engineering. So we chose people from our social environment. Because we are students from different courses of studies (Arts, Fine Arts/Design and Science/Engineering) we had the chance to interview these types of students. Thereby we had a huge spectrum of users.

Central questions:
* What chat apps/programs do you use and for what purposes (one-on-one interviews or group discussions, image, video and link transfer)?
* Where do you see advantages and disadvantages of your favorite chat program?
* How important authentication is for you?
* How should a trustable profile be? What information are important?
* In what situations you prefer the phone or an E-Mail before chatting?
* What are requirements for you to use a new app with guaranteed security?
* How often do you use them and how important they are for you?
* How important is security for you while chatting with people?
* What measures do you probably adopt to be safe?
* What functions and design features do you find most important for a chat app?

==Observation==

Next week we want to make some usability tests of the app (ChatSecure) to find out how others deal with the login process. We want to find out if the log in process is intuitive for the user or not. So we get to know about user's handling with apps and their expectations. We hope to get suggestions and ideas for a better log in process based on the user's behavior.

=='''Data Analysis & Main Results'''==

[[File:Nutzerstudien-Authentifizierung.jpg| 600 px]]

* App Requirements
** accessibility is of prime importance, so the app have to be widespread to make the user downloading it.
** The app should be for free.
** For the user it’s important to be up-to-date and flexible with messages. So he/she prefers an app for chatting.

* Visual Design
** Complexity takes a lot of time, so you need a simple, intuitive, neatly arranged design, which looks uniform on all gadgets.

* Interface & Functions
**It is handy for the user to have an interface, where you can see who is online at the moment and when a contact was online the last time.
** The app should contain a function to let the user know if the chat partner read the messages because it faciliate the communication.
** The user wants to send out photos/videos.
** The user likes to express its emotion with a lot of smileys.
** The function "writes..." is not necassary.

* Security
** It would be useful to have a password for the app.
** To feel safe, the user desires to have a security warranty.
** It is important that apps are immune from viruses.
** Important information, link, photos, videos, … are often sent by E-Mail.
** Distrust towards apps results e.g. from missing knowledge about safety and smart phone-apps.
** People use safety-options of social networks (e.g. Facebook) but don’t know, if they really work.

* Authenticity
** If you want a trustworthy profile you have to find a good balance between too much and too little information.
** (To much) Personalized advertising makes the user feel insecure.
** A “real” profile picture is soothing for the user.
** Authenticity doesn't loom large for students personally.

==Research and problem solutions==

'''What specific problem we want to solve'''

We want to solve some problems with the login-process and make it easier to use.
It's hard and circular to login with one of your accounts, because there are too many steps until you are finally logged in. Moreover the buttons are difficult to find on the interface.
Therefore we want to create a new login-process.

'''Plans – how we want to solve the problem(s)'''

Method 1: Other application's test

First we start to analyse the login process at other applications.
We found out that WhatsApp is the most widespread app to chat for our target group, second one is the Facebook messanger.

1. WhatsApp

This application doesn't contain a login process. You only have to choose the app to be online and you directly see all of your conversations. It is quite easy and intuitive.

2. Facebook Messenger

This application functions nearly the same way as WhatsApp, so you don't need a password to sign in.

Our conclusion:

Both applications manage without a password. That's quite intuitive but it isn't quite save. While doing our interviews we experienced that it would be convenient to have a password to have a safety warranty (e.g. in case of losing the smartphone)

Solution:

We want it as intuitive as WhatsApp and Facebook Messenger but we also want it to be save. So there have to be an additional button for entering a password.

==First design considerations and ideas==
...
==Prototypes==

Our first prototype for the login process contains the additional password entering button if it isn't saved. (at the beginning you can choose if you want to save the password for further use or not)
It occurs when you want to switch from offline to online as an extra field.

[[File:Prototyp Anmeldeprozess.jpg|600px]]

==Our conclusions==
problems we had

what we would do better next time

our final design

IFD:Nutzerstudien WiSe1314/Gruppe Anmeldung endpresentation

2014-01-30T14:40:15Z

Kede7290:

=='''DOCUMENTATION'''==

==Course Aims==

During the course "Nutzerstudien" we wanted to know how important security is for students at our age, what they expect from chat apps and what their problems/whishes are.
For that purpose we tested the app "ChatSecure" and tried to improve the design based on usability tests.

Our main focus premised on the process of creating an account and of signing in.

==Progress of work==

'''1. Interviews and target group'''
For that reason we started to interview a few people from our social environment as our target group. So we focused on students at the age of 20 - 30. We reached this test persons personally so we met them to conduct the interviews directly.

'''2. Analyse and Assessment'''
After that we analysed the results (infinity diagramming) by summing up, comparing and strucuring.

'''3. Prototypes and scenarios'''
Then we began to create prototypes. These prototypes also passed through usability tests to further improve the design.
For that prototypes we constructed scenarios which had to be accomplished by the test users.

'''4. Improving Design by Iteration'''
We further improved our design by iteration (five steps) to get our final design.

=='''Data gathering: Interviews/Observation'''==

===Interviews===

Interview partner:

{| class="wikitable"
|-
! Number
! Age class
! Course of studies
|-
| 1
| <20
| Arts
|-
| 2
| <20
| Arts
|-
| 3
| 20-25
| Science/Engineering
|-
| 4
| 25-30
| Science/Engineering
|-
| 5
| <20
| Fine Arts/Design
|-
| 6
| <20
| Fine Arts/Design
|-
| 7
| <20
| Fine Arts/Design
|}

Reasons for choosing these people:

We wanted to figure out the differences between the students of Arts, Fine Arts/Design and Science/Engineering. So we chose people from our social environment. Because we are students from different courses of studies (Arts, Fine Arts/Design and Science/Engineering) we had the chance to interview these types of students. Thereby we had a huge spectrum of users.

Central questions:
* What chat apps/programs do you use and for what purposes (one-on-one interviews or group discussions, image, video and link transfer)?
* Where do you see advantages and disadvantages of your favorite chat program?
* How important authentication is for you?
* How should a trustable profile be? What information are important?
* In what situations you prefer the phone or an E-Mail before chatting?
* What are requirements for you to use a new app with guaranteed security?
* How often do you use them and how important they are for you?
* How important is security for you while chatting with people?
* What measures do you probably adopt to be safe?
* What functions and design features do you find most important for a chat app?

===Observation===

Next week we want to make some usability tests of the app (ChatSecure) to find out how others deal with the login process. We want to find out if the log in process is intuitive for the user or not. So we get to know about user's handling with apps and their expectations. We hope to get suggestions and ideas for a better log in process based on the user's behavior.

==='''Data Analysis & Main Results'''===

[[File:Nutzerstudien-Authentifizierung.jpg| 600 px]]

* App Requirements
** accessibility is of prime importance, so the app have to be widespread to make the user downloading it.
** The app should be for free.
** For the user it’s important to be up-to-date and flexible with messages. So he/she prefers an app for chatting.

* Visual Design
** Complexity takes a lot of time, so you need a simple, intuitive, neatly arranged design, which looks uniform on all gadgets.

* Interface & Functions
**It is handy for the user to have an interface, where you can see who is online at the moment and when a contact was online the last time.
** The app should contain a function to let the user know if the chat partner read the messages because it faciliate the communication.
** The user wants to send out photos/videos.
** The user likes to express its emotion with a lot of smileys.
** The function "writes..." is not necassary.

* Security
** It would be useful to have a password for the app.
** To feel safe, the user desires to have a security warranty.
** It is important that apps are immune from viruses.
** Important information, link, photos, videos, … are often sent by E-Mail.
** Distrust towards apps results e.g. from missing knowledge about safety and smart phone-apps.
** People use safety-options of social networks (e.g. Facebook) but don’t know, if they really work.

* Authenticity
** If you want a trustworthy profile you have to find a good balance between too much and too little information.
** (To much) Personalized advertising makes the user feel insecure.
** A “real” profile picture is soothing for the user.
** Authenticity doesn't loom large for students personally.

==Research and problem solutions==

'''What specific problem we want to solve'''

We want to solve some problems with the login-process and make it easier to use.
It's hard and circular to login with one of your accounts, because there are too many steps until you are finally logged in. Moreover the buttons are difficult to find on the interface.
Therefore we want to create a new login-process.

'''Plans – how we want to solve the problem(s)'''

Method 1: Other application's test

First we start to analyse the login process at other applications.
We found out that WhatsApp is the most widespread app to chat for our target group, second one is the Facebook messanger.

1. WhatsApp

This application doesn't contain a login process. You only have to choose the app to be online and you directly see all of your conversations. It is quite easy and intuitive.

2. Facebook Messenger

This application functions nearly the same way as WhatsApp, so you don't need a password to sign in.

Our conclusion:

Both applications manage without a password. That's quite intuitive but it isn't quite save. While doing our interviews we experienced that it would be convenient to have a password to have a safety warranty (e.g. in case of losing the smartphone)

Solution:

We want it as intuitive as WhatsApp and Facebook Messenger but we also want it to be save. So there have to be an additional button for entering a password.

==First design considerations and ideas==
...
==Prototypes==

Our first prototype for the login process contains the additional password entering button if it isn't saved. (at the beginning you can choose if you want to save the password for further use or not)
It occurs when you want to switch from offline to online as an extra field.

[[File:Prototyp Anmeldeprozess.jpg|600px]]

==Our conclusions==
problems we had

what we would do better next time

our final design

IFD:Nutzerstudien WiSe1314/Gruppe Anmeldung endpresentation

2014-01-30T14:37:31Z

Kede7290:

=='''DOCUMENTATION'''==

==Course Aims==

During the course "Nutzerstudien" we wanted to know how important security is for students at our age, what they expect from chat apps and what their problems/whishes are.
For that purpose we tested the app "ChatSecure" and tried to improve the design based on usability tests.

Our main focus premised on the process of creating an account and of signing in.

==Progress of work==

'''1. Interviews and target group'''
For that reason we started to interview a few people from our social environment as our target group. So we focused on students at the age of 20 - 30. We reached this test persons personally so we met them to conduct the interviews directly.

'''2. Analyse and Assessment'''
After that we analysed the results (infinity diagramming) by summing up, comparing and strucuring.

'''3. Prototypes and scenarios'''
Then we began to create prototypes. These prototypes also passed through usability tests to further improve the design.
For that prototypes we constructed scenarios which had to be accomplished by the test users.

'''4. Improving Design by Iteration'''
We further improved our design by iteration (five steps) to get our final design.

=='''Data gathering: Interviews/Observation'''==

===Interviews===

Interview partner:

{| class="wikitable"
|-
! Number
! Age class
! Course of studies
|-
| 1
| <20
| Arts
|-
| 2
| <20
| Arts
|-
| 3
| 20-25
| Science/Engineering
|-
| 4
| 25-30
| Science/Engineering
|-
| 5
| <20
| Fine Arts/Design
|-
| 6
| <20
| Fine Arts/Design
|-
| 7
| <20
| Fine Arts/Design
|}

Reasons for choosing these people:

We wanted to figure out the differences between the students of Arts, Fine Arts/Design and Science/Engineering. So we chose people from our social environment. Because we are students from different courses of studies (Arts, Fine Arts/Design and Science/Engineering) we had the chance to interview these types of students. Thereby we had a huge spectrum of users.

Central questions:
* What chat apps/programs do you use and for what purposes (one-on-one interviews or group discussions, image, video and link transfer)?
* Where do you see advantages and disadvantages of your favorite chat program?
* How important authentication is for you?
* How should a trustable profile be? What information are important?
* In what situations you prefer the phone or an E-Mail before chatting?
* What are requirements for you to use a new app with guaranteed security?
* How often do you use them and how important they are for you?
* How important is security for you while chatting with people?
* What measures do you probably adopt to be safe?
* What functions and design features do you find most important for a chat app?

===Observation===

Next week we want to make some usability tests of the app (ChatSecure) to find out how others deal with the login process. We want to find out if the log in process is intuitive for the user or not. So we get to know about user's handling with apps and their expectations. We hope to get suggestions and ideas for a better log in process based on the user's behavior.

==='''Data Analysis & Main Results'''===

[[File:Nutzerstudien-Authentifizierung.jpg| 600 px]]

* App Requirements
** accessibility is of prime importance, so the app have to be widespread to make the user downloading it.
** The app should be for free.
** For the user it’s important to be up-to-date and flexible with messages. So he/she prefers an app for chatting.

* Visual Design
** Complexity takes a lot of time, so you need a simple, intuitive, neatly arranged design, which looks uniform on all gadgets.

* Interface & Functions
**It is handy for the user to have an interface, where you can see who is online at the moment and when a contact was online the last time.
** The app should contain a function to let the user know if the chat partner read the messages because it faciliate the communication.
** The user wants to send out photos/videos.
** The user likes to express its emotion with a lot of smileys.
** The function "writes..." is not necassary.

* Security
** It would be useful to have a password for the app.
** To feel safe, the user desires to have a security warranty.
** It is important that apps are immune from viruses.
** Important information, link, photos, videos, … are often sent by E-Mail.
** Distrust towards apps results e.g. from missing knowledge about safety and smart phone-apps.
** People use safety-options of social networks (e.g. Facebook) but don’t know, if they really work.

* Authenticity
** If you want a trustworthy profile you have to find a good balance between too much and too little information.
** (To much) Personalized advertising makes the user feel insecure.
** A “real” profile picture is soothing for the user.
** Authenticity doesn't loom large for students personally.

==First design considerations and ideas==

'''What specific problem we want to solve'''

We want to solve some problems with the login-process and make it easier to use.
It's hard and circular to login with one of your accounts, because there are too many steps until you are finally logged in. Moreover the buttons are difficult to find on the interface.
Therefore we want to create a new login-process.

==Research and problem solutions==

'''Plans – how we want to solve the problem(s)'''

Method 1: Other application's test

First we start to analyse the login process at other applications.
We found out that WhatsApp is the most widespread app to chat for our target group, second one is the Facebook messanger.

1. WhatsApp

This application doesn't contain a login process. You only have to choose the app to be online and you directly see all of your conversations. It is quite easy and intuitive.

2. Facebook Messenger

This application functions nearly the same way as WhatsApp, so you don't need a password to sign in.

Our conclusion:

Both applications manage without a password. That's quite intuitive but it isn't quite save. While doing our interviews we experienced that it would be convenient to have a password to have a safety warranty (e.g. in case of losing the smartphone)

Solution:

We want it as intuitive as WhatsApp and Facebook Messenger but we also want it to be save. So there have to be an additional button for entering a password.

==Prototypes==

Our first prototype for the login process contains the additional password entering button if it isn't saved. (at the beginning you can choose if you want to save the password for further use or not)
It occurs when you want to switch from offline to online as an extra field.

[[File:Prototyp Anmeldeprozess.jpg|600px]]

==Our conclusions==
problems we had

what we would do better next time

our final design

IFD:Nutzerstudien WiSe1314/Gruppe Anmeldung endpresentation

2014-01-30T14:35:46Z

Kede7290:

=='''DOCUMENTATION'''==

==Course Aims==

During the course "Nutzerstudien" we wanted to know how important security is for students at our age, what they expect from chat apps and what their problems/whishes are.
For that purpose we tested the app "ChatSecure" and tried to improve the design based on usability tests.

Our main focus premised on the process of creating an account and of signing in.

==Progress of work==

'''Interviews and target group'''
For that reason we started to interview a few people from our social environment as our target group. So we focused on students at the age of 20 - 30. We reached this test persons personally so we met them to conduct the interviews directly.

'''Analyse and Assessment'''
After that we analysed the results (infinity diagramming) by summing up, comparing and strucuring.

'''Prototypes and scenarios'''
Then we began to create prototypes. These prototypes also passed through usability tests to further improve the design.
For that prototypes we constructed scenarios which had to be accomplished by the test users.

'''Improving Design by Iteration'''
We further improved our design by iteration (five steps) to get our final design.

=='''Data gathering: Interviews/Observation'''==

===Interviews===

Interview partner:

{| class="wikitable"
|-
! Number
! Age class
! Course of studies
|-
| 1
| <20
| Arts
|-
| 2
| <20
| Arts
|-
| 3
| 20-25
| Science/Engineering
|-
| 4
| 25-30
| Science/Engineering
|-
| 5
| <20
| Fine Arts/Design
|-
| 6
| <20
| Fine Arts/Design
|-
| 7
| <20
| Fine Arts/Design
|}

Reasons for choosing these people:

We wanted to figure out the differences between the students of Arts, Fine Arts/Design and Science/Engineering. So we chose people from our social environment. Because we are students from different courses of studies (Arts, Fine Arts/Design and Science/Engineering) we had the chance to interview these types of students. Thereby we had a huge spectrum of users.

Central questions:
* What chat apps/programs do you use and for what purposes (one-on-one interviews or group discussions, image, video and link transfer)?
* Where do you see advantages and disadvantages of your favorite chat program?
* How important authentication is for you?
* How should a trustable profile be? What information are important?
* In what situations you prefer the phone or an E-Mail before chatting?
* What are requirements for you to use a new app with guaranteed security?
* How often do you use them and how important they are for you?
* How important is security for you while chatting with people?
* What measures do you probably adopt to be safe?
* What functions and design features do you find most important for a chat app?

===Observation===

Next week we want to make some usability tests of the app (ChatSecure) to find out how others deal with the login process. We want to find out if the log in process is intuitive for the user or not. So we get to know about user's handling with apps and their expectations. We hope to get suggestions and ideas for a better log in process based on the user's behavior.

==='''Data Analysis & Main Results'''===

[[File:Nutzerstudien-Authentifizierung.jpg| 600 px]]

* App Requirements
** accessibility is of prime importance, so the app have to be widespread to make the user downloading it.
** The app should be for free.
** For the user it’s important to be up-to-date and flexible with messages. So he/she prefers an app for chatting.

* Visual Design
** Complexity takes a lot of time, so you need a simple, intuitive, neatly arranged design, which looks uniform on all gadgets.

* Interface & Functions
**It is handy for the user to have an interface, where you can see who is online at the moment and when a contact was online the last time.
** The app should contain a function to let the user know if the chat partner read the messages because it faciliate the communication.
** The user wants to send out photos/videos.
** The user likes to express its emotion with a lot of smileys.
** The function "writes..." is not necassary.

* Security
** It would be useful to have a password for the app.
** To feel safe, the user desires to have a security warranty.
** It is important that apps are immune from viruses.
** Important information, link, photos, videos, … are often sent by E-Mail.
** Distrust towards apps results e.g. from missing knowledge about safety and smart phone-apps.
** People use safety-options of social networks (e.g. Facebook) but don’t know, if they really work.

* Authenticity
** If you want a trustworthy profile you have to find a good balance between too much and too little information.
** (To much) Personalized advertising makes the user feel insecure.
** A “real” profile picture is soothing for the user.
** Authenticity doesn't loom large for students personally.

==First design considerations and ideas==

'''What specific problem we want to solve'''

We want to solve some problems with the login-process and make it easier to use.
It's hard and circular to login with one of your accounts, because there are too many steps until you are finally logged in. Moreover the buttons are difficult to find on the interface.
Therefore we want to create a new login-process.

==Research and problem solution==

'''Plans – how we want to solve the problem(s)'''

Method 1: Other application's test

First we start to analyse the login process at other applications.
We found out that WhatsApp is the most widespread app to chat for our target group, second one is the Facebook messanger.

1. WhatsApp

This application doesn't contain a login process. You only have to choose the app to be online and you directly see all of your conversations. It is quite easy and intuitive.

2. Facebook Messenger

This application functions nearly the same way as WhatsApp, so you don't need a password to sign in.

Our conclusion:

Both applications manage without a password. That's quite intuitive but it isn't quite save. While doing our interviews we experienced that it would be convenient to have a password to have a safety warranty (e.g. in case of losing the smartphone)

Solution:

We want it as intuitive as WhatsApp and Facebook Messenger but we also want it to be save. So there have to be an additional button for entering a password.

==Prototypes==

Our first prototype for the login process contains the additional password entering button if it isn't saved. (at the beginning you can choose if you want to save the password for further use or not)
It occurs when you want to switch from offline to online as an extra field.

[[File:Prototyp Anmeldeprozess.jpg|600px]]

==Our conclusions==
problems we had

what we would do better next time

our final design

IFD:Nutzerstudien WiSe1314/Gruppe Anmeldung endpresentation

2014-01-30T14:29:23Z

Kede7290:

'''DOCUMENTATION'''

==Course Aims==

During the course "Nutzerstudien" we wanted to know how important security is for students at our age, what they expect from chat apps and what their problems/whishes are.
For that purpose we tested the app "ChatSecure" and tried to improve the design based on usability tests.

Our main focus premised on the process of creating an account and of signing in. Our general process was:

'''Interviews and target group'''
For that reason we started to interview a few people from our social environment as our target group. So we focused on students at the age of 20 - 30. We reached this test persons personally so we met them to conduct the interviews directly.

'''Analyse and Assessment'''
After that we analysed the results (infinity diagramming) by summing up, comparing and strucuring.

'''Prototypes and scenarios'''
Then we began to create prototypes. These prototypes also passed through usability tests to further improve the design.
For that prototypes we constructed scenarios which had to be accomplished by the test users.

'''Improving Design by Iteration'''
We further improved our design by iteration (five steps) to get our final design.

'''Data gathering: Interviews/Observation'''

1. Interviews:

Interview partner:

{| class="wikitable"
|-
! Number
! Age class
! Course of studies
|-
| 1
| <20
| Arts
|-
| 2
| <20
| Arts
|-
| 3
| 20-25
| Science/Engineering
|-
| 4
| 25-30
| Science/Engineering
|-
| 5
| <20
| Fine Arts/Design
|-
| 6
| <20
| Fine Arts/Design
|-
| 7
| <20
| Fine Arts/Design
|}

Reasons for choosing these people:

We wanted to figure out the differences between the students of Arts, Fine Arts/Design and Science/Engineering. So we chose people from our social environment. Because we are students from different courses of studies (Arts, Fine Arts/Design and Science/Engineering) we had the chance to interview these types of students. Thereby we had a huge spectrum of users.

Central questions:
* What chat apps/programs do you use and for what purposes (one-on-one interviews or group discussions, image, video and link transfer)?
* Where do you see advantages and disadvantages of your favorite chat program?
* How important authentication is for you?
* How should a trustable profile be? What information are important?
* In what situations you prefer the phone or an E-Mail before chatting?
* What are requirements for you to use a new app with guaranteed security?
* How often do you use them and how important they are for you?
* How important is security for you while chatting with people?
* What measures do you probably adopt to be safe?
* What functions and design features do you find most important for a chat app?

2. Observation:

Next week we want to make some usability tests of the app (ChatSecure) to find out how others deal with the login process. We want to find out if the log in process is intuitive for the user or not. So we get to know about user's handling with apps and their expectations. We hope to get suggestions and ideas for a better log in process based on the user's behavior.

'''Data Analysis & Main Results'''

[[File:Nutzerstudien-Authentifizierung.jpg| 600 px]]

* App Requirements
** accessibility is of prime importance, so the app have to be widespread to make the user downloading it.
** The app should be for free.
** For the user it’s important to be up-to-date and flexible with messages. So he/she prefers an app for chatting.

* Visual Design
** Complexity takes a lot of time, so you need a simple, intuitive, neatly arranged design, which looks uniform on all gadgets.

* Interface & Functions
**It is handy for the user to have an interface, where you can see who is online at the moment and when a contact was online the last time.
** The app should contain a function to let the user know if the chat partner read the messages because it faciliate the communication.
** The user wants to send out photos/videos.
** The user likes to express its emotion with a lot of smileys.
** The function "writes..." is not necassary.

* Security
** It would be useful to have a password for the app.
** To feel safe, the user desires to have a security warranty.
** It is important that apps are immune from viruses.
** Important information, link, photos, videos, … are often sent by E-Mail.
** Distrust towards apps results e.g. from missing knowledge about safety and smart phone-apps.
** People use safety-options of social networks (e.g. Facebook) but don’t know, if they really work.

* Authenticity
** If you want a trustworthy profile you have to find a good balance between too much and too little information.
** (To much) Personalized advertising makes the user feel insecure.
** A “real” profile picture is soothing for the user.
** Authenticity doesn't loom large for students personally.

==First design considerations and ideas==

'''What specific problem we want to solve'''

We want to solve some problems with the login-process and make it easier to use.
It's hard and circular to login with one of your accounts, because there are too many steps until you are finally logged in. Moreover the buttons are difficult to find on the interface.
Therefore we want to create a new login-process.

'''Plans – how we want to solve the problem(s)'''

Method 1: Other application's test

First we start to analyse the login process at other applications.
We found out that WhatsApp is the most widespread app to chat for our target group, second one is the Facebook messanger.

1. WhatsApp

This application doesn't contain a login process. You only have to choose the app to be online and you directly see all of your conversations. It is quite easy and intuitive.

2. Facebook Messenger

This application functions nearly the same way as WhatsApp, so you don't need a password to sign in.

Our conclusion:

Both applications manage without a password. That's quite intuitive but it isn't quite save. While doing our interviews we experienced that it would be convenient to have a password to have a safety warranty (e.g. in case of losing the smartphone)

Solution:

We want it as intuitive as WhatsApp and Facebook Messenger but we also want it to be save. So there have to be an additional button for entering a password.

==Prototypes==

Our first prototype for the login process contains the additional password entering button if it isn't saved. (at the beginning you can choose if you want to save the password for further use or not)
It occurs when you want to switch from offline to online as an extra field.

[[File:Prototyp Anmeldeprozess.jpg|600px]]

==Our conclusions==
problems we had
what we would do better next time
our final design

IFD:Nutzerstudien WiSe1314/Gruppe Anmeldung endpresentation

2014-01-30T14:27:21Z

Kede7290: Created page with "'''DOCUMENTATION''' '''Course Aims''' During the course "Nutzerstudien" we wanted to know how important security is for students at our age, what they expect from chat apps ..."

'''DOCUMENTATION'''

'''Course Aims'''

During the course "Nutzerstudien" we wanted to know how important security is for students at our age, what they expect from chat apps and what their problems/whishes are.
For that purpose we tested the app "ChatSecure" and tried to improve the design based on usability tests.

Our main focus premised on the process of creating an account and of signing in. Our general process was:

'''Interviews and target group'''
For that reason we started to interview a few people from our social environment as our target group. So we focused on students at the age of 20 - 30. We reached this test persons personally so we met them to conduct the interviews directly.

'''Analyse and Assessment'''
After that we analysed the results (infinity diagramming) by summing up, comparing and strucuring.

'''Prototypes and scenarios'''
Then we began to create prototypes. These prototypes also passed through usability tests to further improve the design.
For that prototypes we constructed scenarios which had to be accomplished by the test users.

'''Improving Design by Iteration'''
We further improved our design by iteration (five steps) to get our final design.

'''Data gathering: Interviews/Observation'''

1. Interviews:

Interview partner:

{| class="wikitable"
|-
! Number
! Age class
! Course of studies
|-
| 1
| <20
| Arts
|-
| 2
| <20
| Arts
|-
| 3
| 20-25
| Science/Engineering
|-
| 4
| 25-30
| Science/Engineering
|-
| 5
| <20
| Fine Arts/Design
|-
| 6
| <20
| Fine Arts/Design
|-
| 7
| <20
| Fine Arts/Design
|}

Reasons for choosing these people:

We wanted to figure out the differences between the students of Arts, Fine Arts/Design and Science/Engineering. So we chose people from our social environment. Because we are students from different courses of studies (Arts, Fine Arts/Design and Science/Engineering) we had the chance to interview these types of students. Thereby we had a huge spectrum of users.

Central questions:
* What chat apps/programs do you use and for what purposes (one-on-one interviews or group discussions, image, video and link transfer)?
* Where do you see advantages and disadvantages of your favorite chat program?
* How important authentication is for you?
* How should a trustable profile be? What information are important?
* In what situations you prefer the phone or an E-Mail before chatting?
* What are requirements for you to use a new app with guaranteed security?
* How often do you use them and how important they are for you?
* How important is security for you while chatting with people?
* What measures do you probably adopt to be safe?
* What functions and design features do you find most important for a chat app?

2. Observation:

Next week we want to make some usability tests of the app (ChatSecure) to find out how others deal with the login process. We want to find out if the log in process is intuitive for the user or not. So we get to know about user's handling with apps and their expectations. We hope to get suggestions and ideas for a better log in process based on the user's behavior.
<div style="color:darkgreen">Great idea. It is not easy though to see why for an outsider. You could fix it by explaining first, why and how you canged to the topic "login" and because of this it could not be part of the interview process one or two weeks ago.</div>--[[User:JanD|JanD]] 19:58, 13 December 2013 (CET)
<div style="color:blue">I tried to explain what we want to achieve with the usability tests. Ok? [M.E.]</div>
<div style="color:brown">I think this is an area that definitely needs analysis from a usability perspective, and having feedback from people who have limited experience with ChatSecure will be quite helpful. Having a few different setup scenarios to test with would be very useful since the login is quite different depending on what kind of account, etc. For example, using the same Google account as the phone should be quite simple. Using a Facebook acocunt should be a little more work, but straightforward. Using any account with Tor/Orbot would be trickier. And perhaps the hardest will be setting up an account on a server like jabber.ccc.de</div>--[[User:Hans|Hans]] 21:17, 18 December 2013 (CET)

'''Data Analysis & Main Results'''

[[File:Nutzerstudien-Authentifizierung.jpg| 600 px]]

* App Requirements
** accessibility is of prime importance, so the app have to be widespread to make the user downloading it.
** The app should be for free.
** For the user it’s important to be up-to-date and flexible with messages. So he/she prefers an app for chatting.

* Visual Design
** Complexity takes a lot of time, so you need a simple, intuitive, neatly arranged design, which looks uniform on all gadgets.

* Interface & Functions
**It is handy for the user to have an interface, where you can see who is online at the moment and when a contact was online the last time.
** The app should contain a function to let the user know if the chat partner read the messages because it faciliate the communication.
** The user wants to send out photos/videos.
** The user likes to express its emotion with a lot of smileys.
** The function "writes..." is not necassary. <div style="color:brown">not quite sure what this is, could you elaborate on it?</div>--[[User:Hans|Hans]] 21:35, 18 December 2013 (CET)

* Security
** It would be useful to have a password for the app.
** To feel safe, the user desires to have a security warranty.
** It is important that apps are immune from viruses.
** Important information, link, photos, videos, … are often sent by E-Mail.
** Distrust towards apps results e.g. from missing knowledge about safety and smart phone-apps.
** People use safety-options of social networks (e.g. Facebook) but don’t know, if they really work.

* Authenticity
** If you want a trustworthy profile you have to find a good balance between too much and too little information.
** (To much) Personalized advertising makes the user feel insecure.
** A “real” profile picture is soothing for the user.
** Authenticity doesn't loom large for students personally.

<div style="color:darkgreen">There are lots of "the user wants". It would be easier for outsiders to understand, if you could explain ''why'' the user wants this ('''if''' you know that. Naturally, my request is not asking for inventing explanations! If you only know that users ''want'' but not ''why'' you could make it subject of further research)</div>--[[User:JanD|JanD]] 19:58, 13 December 2013 (CET)

<div style="color:blue">I tried to phrase and explain some points in another way. Is it ok? [M.E.]</div>
<div style="color:brown">Definitely some interesting results here, it sounds like people are interested in security and are trying to figure out ways to increase their own security. It would be quite valuable to explore ideas of how people represent their concerns, and how they aim to increase their own security. About Authenticity, its a hard concept in computers. I think most computer users don't understand that its easy to fake messages. My guess is that people are concerned about it, but don't really understand the technical issues so they assume things they receive are what they seem to be. A parallel test on this topic could be very illuminating, like showing users how to generate fake emails, messages, etc. to make them appear they are coming from someone they trust. Also, I'm not quite sure what the point of view of all of these bullet points are. Are they from the person running the tests, or are the things that the users in the tests communicated? My guess is that they are all summaries of things communicated from the users.</div>--[[User:Hans|Hans]] 21:35, 18 December 2013 (CET)

==First design considerations and ideas==

'''What specific problem we want to solve'''

We want to solve some problems with the login-process and make it easier to use.
It's hard and circular to login with one of your accounts, because there are too many steps until you are finally logged in. Moreover the buttons are difficult to find on the interface.
Therefore we want to create a new login-process.

<div style="color:darkgreen">Nice proposal. Are you really talking about the log-in or about setting up a new (Jabber) account? Because in my experience it is not easy to set it up, but once you have your account working and data saved, it behaves very well. But please prove me wrong if that is a singular experience</div>--[[User:JanD|JanD]] 19:58, 13 December 2013 (CET)

<div style="color:blue">We really focus on the sign up process. There is the problem that you don't get an advice to enter the password but it is nessacary. The process is very inconvenient, it needs to many steps till you can start to chat so that we want to create an easier way. [M.E.]</div>

<div style="color:brown">I think this is important work since the process is currently confusing, but also complicated so its not easy to fix the usability issues. But its also not such a huge task, so you should be able to get solid results in the time you have in this class.</div>--[[User:Hans|Hans]] 21:35, 18 December 2013 (CET)

'''Plans – how we want to solve the problem(s)'''

Method 1: Other application's test

First we start to analyse the login process at other applications.
We found out that WhatsApp is the most widespread app to chat for our target group, second one is the Facebook messanger.

1. WhatsApp

This application doesn't contain a login process. You only have to choose the app to be online and you directly see all of your conversations. It is quite easy and intuitive.

2. Facebook Messenger

This application functions nearly the same way as WhatsApp, so you don't need a password to sign in.

Our conclusion:

Both applications manage without a password. That's quite intuitive but it isn't quite save. While doing our interviews we experienced that it would be convenient to have a password to have a safety warranty (e.g. in case of losing the smartphone)

Solution:

We want it as intuitive as WhatsApp and Facebook Messenger but we also want it to be save. So there have to be an additional button for entering a password.

==Prototypes==

Our first prototype for the login process contains the additional password entering button if it isn't saved. (at the beginning you can choose if you want to save the password for further use or not)
It occurs when you want to switch from offline to online as an extra field.

[[File:Prototyp Anmeldeprozess.jpg|600px]]

<div style="color:brown">The difficult part here is that there is no known way of making a secure, private connection without some kind of login process. WhatsApp's uses an automatically generated password that it is not hard for a malicious user to generate, getting full access to the whole account. So its security is very poor, but its usability is great. As far as I know, Facebook does require a login, but it just handles it well and it only happens once really. Facebook is probably a better example here. It probably makes the most sense to compare the Facebook mobile app's first time setup/login procedure with ChatSecure's Facebook login procedure. Then additionally, it would be great to see a comparison of other apps like ChatSecure that allow users to use a wide variety of accounts (Xabber, Beem, etc.) </div>--[[User:Hans|Hans]] 21:35, 18 December 2013 (CET)

==Our conclusions==
problems we had
what we would do better next time
our final design

IFD:Nutzerstudien WiSe1314

2014-01-30T14:25:33Z

Kede7290: /* Presentation and Documentation of Works */

=Werkmodul Nutzerstudien/Sicherheit und Benutzbarkeit=
jeden Donnerstag, 13:30 bis 16:45, Marienstraße 7 B - Seminarraum 102 (siehe auch: Die Veranstaltung im [http://www.uni-weimar.de/qisserver/rds?state=verpublish&status=init&vmfile=no&publishid=21968&moduleCall=webInfo&publishConfFile=webInfo&publishSubDir=veranstaltung Vorlesungsverzeichnis])


===Aktuelles===
* Ein Teil der Aufgaben werden im Medienwiki (auf dieser Website also) bearbeitet werden. Bitte informiert euch wie ihr euch [https://www.youtube.com/watch?v=3oJF0G25q9Q Anmelden], [https://www.youtube.com/watch?v=PVBOAyd_1Zw Editieren], [https://www.youtube.com/watch?v=hLoOpqCyos0 Formatieren] und [https://www.youtube.com/watch?v=P42Une7fC_g Unterseiten anlegen] könnt (Videos dazu in den Links).

==Beschreibung==
[[File:Messaging_CC2BY_FlickrUser-Håkan_Dahlström.jpg|thumb|right|300px|wer liest mit? ([http://flickr.com/photos/dahlstroms/8041061787/sizes/k/in/photostream/ Bild: Dahlström], [https://creativecommons.org/licenses/by/2.0/ CC-BY])]]
[[File:6930835797 2db7044d34 b.jpg|thumb||right|200px|Interviewen]]
[[File:ExploreChallenge CC-BY-2 FlickrUserServicedesignberlin.jpg|thumb|right|200px|Analysieren]]
''Warum ist eine App nützlich und nutzbar, eine andere nicht?''
''Wie kann ich herrausfinden was meine Nutzer brauchen?''

Im Werkmodul Nutzerstudien werden wir Design und die Funktionen von Apps zur sicheren Kommunikation entwickeln und verbessern.

Wir werden:
* Durch unsere Gespräche und Beobachtungen mehr über Nutzer lernen
* Lernen, welche psychologischen Prinzipien bestimmen, ob etwas leicht oder schwierig zu benutzen ist und damit Designen.
* Wir werden unsere Designs ausprobieren lassen und so Verbesserungsmöglichkeiten erkennen und neue Ideen bekommen.



Um zu lernen, wie wir diese Methoden in der Praxis anwenden, haben wir eine Praxiskooperation mit dem [https://guardianproject.info/ Guardian Project]. Wir haben die Aufgabe, sichere Kommunikation über mobile Apps zu verbessern. Mitarbeiter des Projektes werden uns beraten und Feedback für eure Ideen geben.

Kommunikation, die nicht einfach abgehört oder Personen zugeordnet werden kann, ist für Bürgerrechtler und Journalisten essentiell, wird aber auch von Personen verwendet, die ihre Rechte im Netz nicht geschützt sehen.

Leider ist die Nutzung solcher Methoden nicht einfach. Sicherheitsexperte Bruce Schneier z.B. [http://www.theguardian.com/world/2013/sep/05/nsa-how-to-remain-secure-surveillance gibt Tips], sieht diese Tips aber kritisch, denn: ''»My five tips [for more security] suck. They are not things the average person can use. […] Basically, the average user is screwed.«'' (aus einem [http://www.technologyreview.com/news/519336/bruce-schneier-nsa-spying-is-making-us-less-safe/ Interview mit dem MIT Technology Review]) Zwar wird oft auf [https://en.wikipedia.org/wiki/Rtfm »Nutzererziehung«] verwiesen. Das Argument entschuldigt auch die unbenutzbarsten Lösungen – und selbst erfahrene [http://www.gaudior.net/alma/johnny.pdf Nutzer scheitern] z.B. an Verschlüsselungsprogrammen. Besser wären Lösungen, die praktisch, gut benutzbar und sicher sind. Wir wollen zu solchen Lösungen beitragen.

==Häufige Fragen==

'''Muss ich Programmieren können?''' Nein.

'''Ist das hier alles theoretisch?''' Nein, der Kurs ist nicht theoretisch, im Gegenteil, wir werden die gelehrten Methoden anwenden und sie nutzen, um eine anwendbare, praktische Lösung für Probleme zu schaffen.

'''Ist das wissenschaftlich?''' Jein. Es ist [http://de.wikipedia.org/wiki/Naturwissenschaft wissenschaftlich] in dem Sinne, das die Gestaltung auf (eigenen) Erkenntnissen beruht, die wir auch [http://de.wikipedia.org/wiki/Kritischer_Rationalismus kritisch hinterfragen]. Nicht wissenschaftlich ist, das wir konkrete Probleme lösen, anstatt ein allgemeines Modell zu erstellen. (Vergleiche "Wie verhindere ich, das es umfällt?" mit "warum fallen Dinge nach unten?")

==Voraussetzungen==
* Bereitschaft zu eigener Forschung und Weiterentwicklung von Ideen. Mit einem Konzept, dessen Umsetzung für euch schon absolut feststeht, wird der Kurs freud- wie erkenntnislos.

* Texte auf Englisch lesen, denn es gibt wenig Literatur zu dem Gebiet auf deutsch. Wir lesen nicht viel, und ich wähle keine Texte aus, die den Leser mit [http://dev.null.org/postmodern/ nebulös-abstrakten] Begriffen beeindrucken. Aber es ist hilfreich, sich damit zu beschäftigen was andere bisher herausgefunden haben.

==Bewertung==
* Dokumentation (im Wiki, dabei an die Struktur des Arbeitsbuches halten)
* Vortrag
* Anwesenheit (regelm., max 3x fehlen)

==Anmelden==
Mail an ''jan.dittrich ÄT uni-weimar.de'' mit
* Name, Vorname
* Matrikelnummer
* Studiengang
* Kurzer Text der erklärt, warum ihr Teilnehmen möchtet.

==Vortragsthemen| ''student presentations''==
''Mögliche Vortragsthemen. Bitte nutzt die bereitgestellten Quellen, und macht dann eine eigene Recherche. Bereitet das Thema auf, macht es [http://dilbert.com/strips/comic/2010-01-18/ anschaulich] und nicht einfach nur eine Nacherzählung der Quellen (oder der Stichpunkte auf den Slides).''

'''Vortragsdauer: 15-20min'''
* 7.11 Attacks based on Psychology, [http://www.cl.cam.ac.uk/~rja14/book.html Security Engineering, Chapter 2.2] (Lisa Guth)
* 14.11 Personas: About Face 3, ISBN 0470084111, (page 75-81, 97-106)
* 21.11 'Service Blueprinting, [http://knowledge.wpcarey.asu.edu/article.cfm?articleid=1546 intro], [[wikipedia:Service blueprint|Wikipedia]], [http://www.flickr.com/photos/brandonschauer/3363169836/ template]
* 28.11 Security and Usability: The Case of passwords: [http://www.nngroup.com/articles/security-and-human-factors/ Norman/Nielsen on Sign-On-Usability], [http://www.cl.cam.ac.uk/~rja14/book.html Security Engineering, Chapter 2.4], [https://xkcd.com/936/ xkcd on password strength] (Anna Krieger)
* 05.12 "Intuitivität" [http://www.asktog.com/papers/raskinintuit.html Intuitive = Familiar], [http://www.uie.com/articles/design_intuitive/ The Intuition Gap] (Michèle Eike)
*12.12. Kein Vortrag
*19.12. Prototyping-Tools: [http://pencil.evolus.vn/ Pencil], [http://jquery.com/ jQuery] (Anja Rathgeber)
* 19.12. Parallel Prototyping: [http://www.sigchi.org/chi95/proceedings/shortppr/so_bdy.htm 1995], [http://aaalab.stanford.edu/papers/Parallel_Prototyping_2010.pdf 2010]
* 9.1 Knowledge in the Head, Knowledge in the World. In "The Design of Everyday Things" ("Alltägliche Dinge"), Donald Norman, ISBN 0465067107 (Psychologischer Fokus) (Susanne Pötzsch)
* 16.1. [http://www.gaudior.net/alma/johnny.pdf Why Johnny can't encrypt] a classic Security/HCI paper. (Benjamin Burse)
* 23.1. Paper: [http://technology.open.ac.uk/design/cross/documents/DesignerlyWaysofKnowing.pdf Designerly Ways of knowing]





==Zeitplan==
* '''24.10''': Einführung | ''Introduction''
* '''31.10''' : ''Feiertag''
* '''7.11''': Security
* '''14.11''' : Nutzerforschung: Beobachten und Fragen stellen | ''User Research: Observing and Asking Questions''
* '''21.11''': Datenanalyse, Szenarioerstellung | ''Analyse Data, Create Scenarios''
* '''28.11''': Idenentwicklung | ''Idea Development''
* '''5.12.: Prototyping
[…]
* '''12.12''': 1st Feedback round
[…]

==='''Gruppe Anmeldung'''===
* '''16.01''': heuristische Analyse und Schwachpunkte herausarbeiten <br>
Treffen um den PaperMockUp gestalten <br>
Prototyp in den nächsten zwei Wochen testen (evtl. mehrere Iterationsschritte)
* '''23.01''': Feedback | vorläufige Ergebnisse zusammentragen
* '''30.01''': Verbesserungen vornehmen <br>
Treffen um Wiki-Seite zu aktualisieren <br>
* bis vorlesungsfreie Zeit => Feedback

==='''Gruppe Sicherheit'''===
* '''16.01.:''' Heuristische Analyse fertigstellen und Schwachpunkte der App finden
* '''23.01.:''' Prototypen verbessern (je nach Zeit: für Hoch- und Querformat) und Klickdummy anfertigen
* '''30.01.:''' Fertiggestellten Klickdummy testen
* '''06.02:''' Tests auswerten; Anfangen für die Dokumentation zu sammeln





== Presentation and Documentation of Works==

===First use self observation===
[[/firstUseChatSecure]]

===Mid-Term-Presentations and Mentor Comments===
*[[/Gruppe Anmeldung]]
*[[/Sicherheit (security)]]

===End-Term-Presentation===
*[[/Gruppe_Anmeldung_endpresentation]]
*[[/Sicherheit_endpresentation (security)]]

===Heuristic Analysis===
* Aktuelle [https://guardianproject.info/releases/ Versionen von ChatSecure]
* Wenn die nicht geht: die [https://guardianproject.info/releases/chatsecure-latest.apk stabile Version]

'''Team Anmeldung: [[/HeuristicAnalysisAnmeldung|view the summary]]'''
*[[/HeuristicAnalysisAnmeldung| summary]]
*[[/HeuristicAnalysisAnmeldung_Person1]] (Aufgaben: Anmelden, Account erstellen, Einstellungen ("Settings"))
*[[/HeuristicAnalysisAnmeldung_Person2]] (Aufgaben: Anmelden, Account erstellen, Einstellungen ("Settings"))
*[[/HeuristicAnalysisAnmeldung_Person3]] (Aufgaben: Anmelden, Account erstellen, Einstellungen ("Settings"))

'''Team Sicherheit [[/HeuristicAnalysisSecurity|view the summary]] '''
*[[/HeuristicAnalysisSecurity|summary]]
*[[/HeuristicAnalysisSecurity_Person4]] (Aufgaben: Neuen Kontakt hinzufügen, Nachricht verschicken auf den Wegen: Unsicher, Verschlüsselt, Authentifiziert)
*[[/HeuristicAnalysisSecurity_Person5]] (Aufgaben: Neuen Kontakt hinzufügen, Nachricht verschicken auf den Wegen: Unsicher, Verschlüsselt, Authentifiziert)
*[[/HeuristicAnalysisSecurity_Person6]] (Aufgaben: Neuen Kontakt hinzufügen, Nachricht verschicken auf den Wegen: Unsicher, Verschlüsselt, Authentifiziert)

''Die Analyse sollte am spätestens am 16.1. fertig sein''

{{IFD_Nutzerstudien_HeuristischeEvaluationAnweisungen}}

Für Material siehe Abschnitt [[#Heuristische Analyse|Materialien/Heuristische Analyse]] auf dieser Seite

===Endabgabe===
====Termine====
* Bis zum Vorlesungszeitende (7.2.) sollen die Entwürfe und Forschungen fertiggestellt sein.
* Bis zum Mi, 5.März 2014 ist die Dokumentation für den Lehrenden und die Designs und Erklärungen für den Projektpartner fertigzustellen. Auf diese Version gibt es Feedback, die fertige, darauf hin verbesserte und entgültige Version ist eine Woche später, am 12. März abzugeben.

====Anforderungen====
* '''Gruppe oder/und einzeln?''' Dokumentation für den Lehrenden und die Designs und Erklärungen werden ''pro Gruppe'' erstellt. Wichtige Infos oder Erfahrungen (e.g. eine Person hatte diese und jene Probleme mit dem Interview und hat sich deshalb entschiedenen diese und jene Änderungen anm Vorgehen zu machen) sind mitzudokumentieren (u.U. anonym)
* '''Struktur/Inhalt:''' Die Dokumentation für den Lehrenden lehnt sich am besten an das [[IFD:Human-Centered-Design-Research_-_Workbook|Arbeitsbuch]] an. Möglicherweise sind nicht alle methodischen Vorschläge auf euer Projekt zutreffend, in diesem Fall kann es sinnvoll sein, die "Abweichung" zu erklären (''xyz'' ist nicht gut geeignet weil …, deshalb haben wir die methode ''xyz'' benutzt", um das und das zu machen)
* '''Format:'''Die Designs und Ergebnisse ''für den Projektpartner'' sind im Wiki zu veröffentlichen, die ''Doku an den Lehrenden'' im Wiki oder als PDF.
* '''Nachvollziehbarkeit:''' Die Designs und Ergebnisse für den Projektpartner sollen ermöglichen die ''Ideen in der Software umzusetzen'' und es soll klar werden wie und warum (oder warum nicht) die Entwürfe so entstanden sind (das Programmieren kosten natürlich auch Zeit, und niemand würde etwas "einfach so" einbauen; Zudem kann es sein das Abweichungen von euren Entwürfen nötig sind – dann sind die Begründungen und Daten wichtig, um etwas ähnliches umzusetzen)
* '''Anschaulich machen:''' Zu den Designs und Ergebnisse für den Projektpartner sollte gehören:
** Ein Text mit Screenshots und Entwurfsskizzen
** Ein Prototyp oder eine andere anschauliche Darstellungsform eures/eurer Entwurfes/Entwürfe

==Arbeits & Übungshilfen==
[[File:GuillocheGeldBitcoin.png|thumb|right|100px|"Geldscheinmuster" (zu Interviewbeispiel)]]
* [[IFD:Human-Centered-Design-Research_-_Workbook|"Workbook"]] in Begleitung zur Praktischen Arbeit als Dokumentation, Gedankenstütze und Reflektionsmöglichkeit
* [[Media:Interview IllustratorUse.mp3|Interview/Beobachtung]]: Thema: "Grafiken erstellen"; zum Ausprobieren von Auswertungsmethoden.
''Begriffe'':
Die erwähnten [https://de.wikipedia.org/wiki/Bitcoin "Bitcoins"] sind eine virtuelle Währung; "Offset" bedeutet soviel wie "Abstand".

Die Ergebnisse von Beobachtung und Fragen werden aufbereitet; [[Zusammenhänge Beispielinterview|Hier einige Zusammenhänge]], die sich aus der Audioaufnahme herrausarbeiten lasse.

===Folien===
* [http://webuser.uni-weimar.de/~fudo5114/talks/defineAndFindAudience.html define and find your audience]
* [http://webuser.uni-weimar.de/~fudo5114/talks/BeobachtenFragen.html Beobachten und Fragen]
* [http://webuser.uni-weimar.de/~fudo5114/talks/Datenanalyse.html Datenanalyse]
* [http://webuser.uni-weimar.de/~fudo5114/talks/VonAnalyseZuIdeen.html Szenarios und DesignStudio-Methode]
** [http://webuser.uni-weimar.de/~fudo5114/workshopapp/ Design Studio Webapp] (kam nicht im Kurs vor ist zum Selbernutzen der Methode aber praktischer als die Folien. Verbesserungsvorschläge willkommen)
* [http://webuser.uni-weimar.de/~fudo5114/talks/Minivortrag_Personas.html Personas erstellen]

==Links und Materialien==
===Security/Usability===
* [http://www.cl.cam.ac.uk/~rja14/book.html Security Engineering, Kapitel 2: Usability and Psychology]
* Security and Usability: Designing Secure Systems That People Can Use, Lorrie Faith Cranor, Simson Garfinkel et.al., O'Reilly Media, ISBN 0596008279
* [https://csclub.uwaterloo.ca/media/Off-the-Record%20Messaging:%20Useful%20Security%20and%20Privacy%20for%20IM.html Wie Off-The-Record funktioniert und warum]: Usability, Verbreitbarkeit, Effektivität, "Resilienz"/Fehlerresistenz (von [https://en.wikipedia.org/wiki/Ian_Goldberg Ian Goldberg])
* Usability: [http://jnd.org/dn.mss/when_security_gets_in_the_way.html »When Security gets in the Way«] (D. Norman)

===Kyptografie===
* [https://en.khanacademy.org/math/applied-math/cryptography/modern-crypt/v/the-fundamental-theorem-of-arithmetic-1 The intro to cryptography on Khan Academy] several 3-5min Videos. Easy.
* [http://www.mat-d.com/site/rsa-diffie-hellman-explained-in-3-minutes/ Diffie-Hellman-Key-Exchange] – ca. 2 DINA4 pages Text. How can you get a secret key without ever seeing each other or sending it?
* Zur Belohnung nach der Mathematik: [http://www.schneierfacts.com/ Bruce Schneier Facts]. Es hat keinen Bildungswert, ist aber lustig (wenn man ''sehr'' nerdigen Humor mag)

===Ausprobieren…===
* Mobile Applikationen testen, aber kein Telefon zur Hand? (Aber einen PC?): den [https://developer.android.com/sdk/index.html Android-Simulator] nutzen, der ein Android-System auf eurem Computer simuliert. ("SDK-Tools only" reicht aus). Schaut das [https://www.youtube.com/watch?v=4r3o2eBzyrs erklärende Video] an.
* https://guardianproject.info/apps/chatsecure/ ChatSecure]. ist die App, mit der wir u.A. arbeiten werden. Installieren über [https://play.google.com/store/apps/details?id=info.guardianproject.otr.app.im Android Store] oder direkt aus dem [https://guardianproject.info/releases/ChatSecure-v12.6.4-RC3.apk Repository]
* [http://www.pidgin.im/ Pidgin] kann mittels [https://otr.cypherpunks.ca/ OTR-Plugin] sicher mit ChatSecure (und vielen anderen Instant-Messangern) Nachrichten senden.
* man braucht natürlich mindestens einen XMPP-Account. Den kann man z.B. bei [http://einfachjabber.de/reg einfachjabber] oder [https://dukgo.com/blog/using-pidgin-with-xmpp-jabber dukgo] anlegen.

===Bücher Design===
* Interaction Design: Beyond Human-Computer Interaction – Preece, Rogers and Sharp, ISBN 978-0470665763 ''Interaktionsdesign-Bezug, darin aber sehr umfassender Überblick''

* Observing the User Experience: A Practitioner's Guide to User Research, Kuneavski, ISBN 978-1558609235

===Human Centered Design===

* Abläufe Analysieren: [http://mindthegap.blog.bau-ha.us/2013/08/from-research-to-requirements-user-need-tables/316/ User Need Tables] (Quellen sind dort verlinkt)
* Personas erstellen: About Face 3, Cooper et.al. (In der Bib)
* [[IFD:Course_Interaction_Design|Interaktionsdesign-Kurs]] Ein Script zu einem vorhergehenden, ähnlichen Werkmodul.
* [http://www.uxmatters.com/mt/archives/2011/10/research-guidelines-you-wont-find-in-a-textbook.php 3 Regeln für Nutzerforschung: Sich Anfreunden, nicht zum Fragen beantworten da sein, nichts "verkaufen"]
* [http://www.experientia.com/blog/ Putting People First-Blog] (u.A. Forschung, Gender, Bildung etc. im HCD. Keine hurra-wir-sind-toll-Artikel, sondern interessante Inhalte.)

===Mobile Apps===
[http://www.cs.uml.edu/~fredm/courses/91.308-fall05/palm/zenofpalm.pdf The Zen of Palm]. Gute Zusammenfassung.

===Heuristische Analyse===
Hinweis: Eine heuristische Analyse kann das Testen nur ergänzen, aber nicht ersetzen!
* [http://www.nngroup.com/articles/ten-usability-heuristics/ List of Heuristics]
* [http://www.nngroup.com/articles/how-to-conduct-a-heuristic-evaluation/ How to do a heuristic evaluation] (and statistics which number of evaluatiors are best and/or most efficient etc.)

===Software===
* [http://developer.nokia.com/Resources/Tools_and_downloads/Other/Flowella/ Nokia Flowella] für Durchklick-Prototypen
* [http://www.jQuery.com jQuery] für aufwändiger, interaktive Prototypen.

===Nützliches===
* Ein [http://en.wikipedia.org/wiki/Service_blueprint Service Blueprint] zum [http://www.flickr.com/photos/brandonschauer/3363169836/ Download]

* [http://m18.uni-weimar.de/mailman/listinfo/interaction Sign up] for our (inofficial) BU Interaction Design Mailinglist

===Meta===
...das Designen von Designlehre
* [http://www.newyorker.com/reporting/2012/01/30/120130fa_fact_lehrer?currentPage=all Brainstorming: Eine Kritik] (vgl. mit der pro-Brainstorm-Kultur von e.g. Design Thinking)
* Parallel Prototyping:Eine empirische Studie von [http://aaalab.stanford.edu/papers/Parallel_Prototyping_2010.pdf 2010] und einer von [http://www.sigchi.org/chi95/proceedings/shortppr/so_bdy.htm 1995], deren Ergebnisse sehr für paralelles Prototyping sprechen.
* Das Iteration sinnvoll ist, ist auch nix neues, aber auch hier eine [http://www.itu.dk/people/jeppeh/specialeartikler/The%20Efficacy%20of%20Prototyping%20Under%20Time%20Constraints.pdf Studie] dazu
* Gruppen, die sich nach bestehenden Freundschaften zusammenfinden, sind für designerische Gruppenarbeiten [http://www.stanford.edu/~roypea/RoyPDF%20folder/A154_CSCL09_Maldonado_Klemmer_Pea.pdf nicht gut geeignet]
* [http://hci.stanford.edu/publications/2011/PrototypingDynamics/PrototypingDynamics-CHI2011.pdf mehrere Designs erstellen und teilen] ist vorteilhaft. [http://hci.stanford.edu/publications/2012/RepeatedExamplesCogSci2012/RepeatedExamplesCogSci2012.pdf Früh mehrfach Beispiele zu teilen] verbessert Resultate.
* The Reflective Practitioner (D. Schön), ISBN 0465068782

IFD:Nutzerstudien WiSe1314

2014-01-30T14:23:27Z

Kede7290: /* Presentation and Documentation of Works */

=Werkmodul Nutzerstudien/Sicherheit und Benutzbarkeit=
jeden Donnerstag, 13:30 bis 16:45, Marienstraße 7 B - Seminarraum 102 (siehe auch: Die Veranstaltung im [http://www.uni-weimar.de/qisserver/rds?state=verpublish&status=init&vmfile=no&publishid=21968&moduleCall=webInfo&publishConfFile=webInfo&publishSubDir=veranstaltung Vorlesungsverzeichnis])


===Aktuelles===
* Ein Teil der Aufgaben werden im Medienwiki (auf dieser Website also) bearbeitet werden. Bitte informiert euch wie ihr euch [https://www.youtube.com/watch?v=3oJF0G25q9Q Anmelden], [https://www.youtube.com/watch?v=PVBOAyd_1Zw Editieren], [https://www.youtube.com/watch?v=hLoOpqCyos0 Formatieren] und [https://www.youtube.com/watch?v=P42Une7fC_g Unterseiten anlegen] könnt (Videos dazu in den Links).

==Beschreibung==
[[File:Messaging_CC2BY_FlickrUser-Håkan_Dahlström.jpg|thumb|right|300px|wer liest mit? ([http://flickr.com/photos/dahlstroms/8041061787/sizes/k/in/photostream/ Bild: Dahlström], [https://creativecommons.org/licenses/by/2.0/ CC-BY])]]
[[File:6930835797 2db7044d34 b.jpg|thumb||right|200px|Interviewen]]
[[File:ExploreChallenge CC-BY-2 FlickrUserServicedesignberlin.jpg|thumb|right|200px|Analysieren]]
''Warum ist eine App nützlich und nutzbar, eine andere nicht?''
''Wie kann ich herrausfinden was meine Nutzer brauchen?''

Im Werkmodul Nutzerstudien werden wir Design und die Funktionen von Apps zur sicheren Kommunikation entwickeln und verbessern.

Wir werden:
* Durch unsere Gespräche und Beobachtungen mehr über Nutzer lernen
* Lernen, welche psychologischen Prinzipien bestimmen, ob etwas leicht oder schwierig zu benutzen ist und damit Designen.
* Wir werden unsere Designs ausprobieren lassen und so Verbesserungsmöglichkeiten erkennen und neue Ideen bekommen.



Um zu lernen, wie wir diese Methoden in der Praxis anwenden, haben wir eine Praxiskooperation mit dem [https://guardianproject.info/ Guardian Project]. Wir haben die Aufgabe, sichere Kommunikation über mobile Apps zu verbessern. Mitarbeiter des Projektes werden uns beraten und Feedback für eure Ideen geben.

Kommunikation, die nicht einfach abgehört oder Personen zugeordnet werden kann, ist für Bürgerrechtler und Journalisten essentiell, wird aber auch von Personen verwendet, die ihre Rechte im Netz nicht geschützt sehen.

Leider ist die Nutzung solcher Methoden nicht einfach. Sicherheitsexperte Bruce Schneier z.B. [http://www.theguardian.com/world/2013/sep/05/nsa-how-to-remain-secure-surveillance gibt Tips], sieht diese Tips aber kritisch, denn: ''»My five tips [for more security] suck. They are not things the average person can use. […] Basically, the average user is screwed.«'' (aus einem [http://www.technologyreview.com/news/519336/bruce-schneier-nsa-spying-is-making-us-less-safe/ Interview mit dem MIT Technology Review]) Zwar wird oft auf [https://en.wikipedia.org/wiki/Rtfm »Nutzererziehung«] verwiesen. Das Argument entschuldigt auch die unbenutzbarsten Lösungen – und selbst erfahrene [http://www.gaudior.net/alma/johnny.pdf Nutzer scheitern] z.B. an Verschlüsselungsprogrammen. Besser wären Lösungen, die praktisch, gut benutzbar und sicher sind. Wir wollen zu solchen Lösungen beitragen.

==Häufige Fragen==

'''Muss ich Programmieren können?''' Nein.

'''Ist das hier alles theoretisch?''' Nein, der Kurs ist nicht theoretisch, im Gegenteil, wir werden die gelehrten Methoden anwenden und sie nutzen, um eine anwendbare, praktische Lösung für Probleme zu schaffen.

'''Ist das wissenschaftlich?''' Jein. Es ist [http://de.wikipedia.org/wiki/Naturwissenschaft wissenschaftlich] in dem Sinne, das die Gestaltung auf (eigenen) Erkenntnissen beruht, die wir auch [http://de.wikipedia.org/wiki/Kritischer_Rationalismus kritisch hinterfragen]. Nicht wissenschaftlich ist, das wir konkrete Probleme lösen, anstatt ein allgemeines Modell zu erstellen. (Vergleiche "Wie verhindere ich, das es umfällt?" mit "warum fallen Dinge nach unten?")

==Voraussetzungen==
* Bereitschaft zu eigener Forschung und Weiterentwicklung von Ideen. Mit einem Konzept, dessen Umsetzung für euch schon absolut feststeht, wird der Kurs freud- wie erkenntnislos.

* Texte auf Englisch lesen, denn es gibt wenig Literatur zu dem Gebiet auf deutsch. Wir lesen nicht viel, und ich wähle keine Texte aus, die den Leser mit [http://dev.null.org/postmodern/ nebulös-abstrakten] Begriffen beeindrucken. Aber es ist hilfreich, sich damit zu beschäftigen was andere bisher herausgefunden haben.

==Bewertung==
* Dokumentation (im Wiki, dabei an die Struktur des Arbeitsbuches halten)
* Vortrag
* Anwesenheit (regelm., max 3x fehlen)

==Anmelden==
Mail an ''jan.dittrich ÄT uni-weimar.de'' mit
* Name, Vorname
* Matrikelnummer
* Studiengang
* Kurzer Text der erklärt, warum ihr Teilnehmen möchtet.

==Vortragsthemen| ''student presentations''==
''Mögliche Vortragsthemen. Bitte nutzt die bereitgestellten Quellen, und macht dann eine eigene Recherche. Bereitet das Thema auf, macht es [http://dilbert.com/strips/comic/2010-01-18/ anschaulich] und nicht einfach nur eine Nacherzählung der Quellen (oder der Stichpunkte auf den Slides).''

'''Vortragsdauer: 15-20min'''
* 7.11 Attacks based on Psychology, [http://www.cl.cam.ac.uk/~rja14/book.html Security Engineering, Chapter 2.2] (Lisa Guth)
* 14.11 Personas: About Face 3, ISBN 0470084111, (page 75-81, 97-106)
* 21.11 'Service Blueprinting, [http://knowledge.wpcarey.asu.edu/article.cfm?articleid=1546 intro], [[wikipedia:Service blueprint|Wikipedia]], [http://www.flickr.com/photos/brandonschauer/3363169836/ template]
* 28.11 Security and Usability: The Case of passwords: [http://www.nngroup.com/articles/security-and-human-factors/ Norman/Nielsen on Sign-On-Usability], [http://www.cl.cam.ac.uk/~rja14/book.html Security Engineering, Chapter 2.4], [https://xkcd.com/936/ xkcd on password strength] (Anna Krieger)
* 05.12 "Intuitivität" [http://www.asktog.com/papers/raskinintuit.html Intuitive = Familiar], [http://www.uie.com/articles/design_intuitive/ The Intuition Gap] (Michèle Eike)
*12.12. Kein Vortrag
*19.12. Prototyping-Tools: [http://pencil.evolus.vn/ Pencil], [http://jquery.com/ jQuery] (Anja Rathgeber)
* 19.12. Parallel Prototyping: [http://www.sigchi.org/chi95/proceedings/shortppr/so_bdy.htm 1995], [http://aaalab.stanford.edu/papers/Parallel_Prototyping_2010.pdf 2010]
* 9.1 Knowledge in the Head, Knowledge in the World. In "The Design of Everyday Things" ("Alltägliche Dinge"), Donald Norman, ISBN 0465067107 (Psychologischer Fokus) (Susanne Pötzsch)
* 16.1. [http://www.gaudior.net/alma/johnny.pdf Why Johnny can't encrypt] a classic Security/HCI paper. (Benjamin Burse)
* 23.1. Paper: [http://technology.open.ac.uk/design/cross/documents/DesignerlyWaysofKnowing.pdf Designerly Ways of knowing]





==Zeitplan==
* '''24.10''': Einführung | ''Introduction''
* '''31.10''' : ''Feiertag''
* '''7.11''': Security
* '''14.11''' : Nutzerforschung: Beobachten und Fragen stellen | ''User Research: Observing and Asking Questions''
* '''21.11''': Datenanalyse, Szenarioerstellung | ''Analyse Data, Create Scenarios''
* '''28.11''': Idenentwicklung | ''Idea Development''
* '''5.12.: Prototyping
[…]
* '''12.12''': 1st Feedback round
[…]

==='''Gruppe Anmeldung'''===
* '''16.01''': heuristische Analyse und Schwachpunkte herausarbeiten <br>
Treffen um den PaperMockUp gestalten <br>
Prototyp in den nächsten zwei Wochen testen (evtl. mehrere Iterationsschritte)
* '''23.01''': Feedback | vorläufige Ergebnisse zusammentragen
* '''30.01''': Verbesserungen vornehmen <br>
Treffen um Wiki-Seite zu aktualisieren <br>
* bis vorlesungsfreie Zeit => Feedback

==='''Gruppe Sicherheit'''===
* '''16.01.:''' Heuristische Analyse fertigstellen und Schwachpunkte der App finden
* '''23.01.:''' Prototypen verbessern (je nach Zeit: für Hoch- und Querformat) und Klickdummy anfertigen
* '''30.01.:''' Fertiggestellten Klickdummy testen
* '''06.02:''' Tests auswerten; Anfangen für die Dokumentation zu sammeln





== Presentation and Documentation of Works==

===First use self observation===
[[/firstUseChatSecure]]

===Mid-Term-Presentations and Mentor Comments===
*[[/Gruppe Anmeldung]]
*[[/Sicherheit (security)]]

===End-Term-Presentation===
*[[/Gruppe Anmeldung]]
*[[/Sicherheit (security)]]

===Heuristic Analysis===
* Aktuelle [https://guardianproject.info/releases/ Versionen von ChatSecure]
* Wenn die nicht geht: die [https://guardianproject.info/releases/chatsecure-latest.apk stabile Version]

'''Team Anmeldung: [[/HeuristicAnalysisAnmeldung|view the summary]]'''
*[[/HeuristicAnalysisAnmeldung| summary]]
*[[/HeuristicAnalysisAnmeldung_Person1]] (Aufgaben: Anmelden, Account erstellen, Einstellungen ("Settings"))
*[[/HeuristicAnalysisAnmeldung_Person2]] (Aufgaben: Anmelden, Account erstellen, Einstellungen ("Settings"))
*[[/HeuristicAnalysisAnmeldung_Person3]] (Aufgaben: Anmelden, Account erstellen, Einstellungen ("Settings"))

'''Team Sicherheit [[/HeuristicAnalysisSecurity|view the summary]] '''
*[[/HeuristicAnalysisSecurity|summary]]
*[[/HeuristicAnalysisSecurity_Person4]] (Aufgaben: Neuen Kontakt hinzufügen, Nachricht verschicken auf den Wegen: Unsicher, Verschlüsselt, Authentifiziert)
*[[/HeuristicAnalysisSecurity_Person5]] (Aufgaben: Neuen Kontakt hinzufügen, Nachricht verschicken auf den Wegen: Unsicher, Verschlüsselt, Authentifiziert)
*[[/HeuristicAnalysisSecurity_Person6]] (Aufgaben: Neuen Kontakt hinzufügen, Nachricht verschicken auf den Wegen: Unsicher, Verschlüsselt, Authentifiziert)

''Die Analyse sollte am spätestens am 16.1. fertig sein''

{{IFD_Nutzerstudien_HeuristischeEvaluationAnweisungen}}

Für Material siehe Abschnitt [[#Heuristische Analyse|Materialien/Heuristische Analyse]] auf dieser Seite

===Endabgabe===
====Termine====
* Bis zum Vorlesungszeitende (7.2.) sollen die Entwürfe und Forschungen fertiggestellt sein.
* Bis zum Mi, 5.März 2014 ist die Dokumentation für den Lehrenden und die Designs und Erklärungen für den Projektpartner fertigzustellen. Auf diese Version gibt es Feedback, die fertige, darauf hin verbesserte und entgültige Version ist eine Woche später, am 12. März abzugeben.

====Anforderungen====
* '''Gruppe oder/und einzeln?''' Dokumentation für den Lehrenden und die Designs und Erklärungen werden ''pro Gruppe'' erstellt. Wichtige Infos oder Erfahrungen (e.g. eine Person hatte diese und jene Probleme mit dem Interview und hat sich deshalb entschiedenen diese und jene Änderungen anm Vorgehen zu machen) sind mitzudokumentieren (u.U. anonym)
* '''Struktur/Inhalt:''' Die Dokumentation für den Lehrenden lehnt sich am besten an das [[IFD:Human-Centered-Design-Research_-_Workbook|Arbeitsbuch]] an. Möglicherweise sind nicht alle methodischen Vorschläge auf euer Projekt zutreffend, in diesem Fall kann es sinnvoll sein, die "Abweichung" zu erklären (''xyz'' ist nicht gut geeignet weil …, deshalb haben wir die methode ''xyz'' benutzt", um das und das zu machen)
* '''Format:'''Die Designs und Ergebnisse ''für den Projektpartner'' sind im Wiki zu veröffentlichen, die ''Doku an den Lehrenden'' im Wiki oder als PDF.
* '''Nachvollziehbarkeit:''' Die Designs und Ergebnisse für den Projektpartner sollen ermöglichen die ''Ideen in der Software umzusetzen'' und es soll klar werden wie und warum (oder warum nicht) die Entwürfe so entstanden sind (das Programmieren kosten natürlich auch Zeit, und niemand würde etwas "einfach so" einbauen; Zudem kann es sein das Abweichungen von euren Entwürfen nötig sind – dann sind die Begründungen und Daten wichtig, um etwas ähnliches umzusetzen)
* '''Anschaulich machen:''' Zu den Designs und Ergebnisse für den Projektpartner sollte gehören:
** Ein Text mit Screenshots und Entwurfsskizzen
** Ein Prototyp oder eine andere anschauliche Darstellungsform eures/eurer Entwurfes/Entwürfe

==Arbeits & Übungshilfen==
[[File:GuillocheGeldBitcoin.png|thumb|right|100px|"Geldscheinmuster" (zu Interviewbeispiel)]]
* [[IFD:Human-Centered-Design-Research_-_Workbook|"Workbook"]] in Begleitung zur Praktischen Arbeit als Dokumentation, Gedankenstütze und Reflektionsmöglichkeit
* [[Media:Interview IllustratorUse.mp3|Interview/Beobachtung]]: Thema: "Grafiken erstellen"; zum Ausprobieren von Auswertungsmethoden.
''Begriffe'':
Die erwähnten [https://de.wikipedia.org/wiki/Bitcoin "Bitcoins"] sind eine virtuelle Währung; "Offset" bedeutet soviel wie "Abstand".

Die Ergebnisse von Beobachtung und Fragen werden aufbereitet; [[Zusammenhänge Beispielinterview|Hier einige Zusammenhänge]], die sich aus der Audioaufnahme herrausarbeiten lasse.

===Folien===
* [http://webuser.uni-weimar.de/~fudo5114/talks/defineAndFindAudience.html define and find your audience]
* [http://webuser.uni-weimar.de/~fudo5114/talks/BeobachtenFragen.html Beobachten und Fragen]
* [http://webuser.uni-weimar.de/~fudo5114/talks/Datenanalyse.html Datenanalyse]
* [http://webuser.uni-weimar.de/~fudo5114/talks/VonAnalyseZuIdeen.html Szenarios und DesignStudio-Methode]
** [http://webuser.uni-weimar.de/~fudo5114/workshopapp/ Design Studio Webapp] (kam nicht im Kurs vor ist zum Selbernutzen der Methode aber praktischer als die Folien. Verbesserungsvorschläge willkommen)
* [http://webuser.uni-weimar.de/~fudo5114/talks/Minivortrag_Personas.html Personas erstellen]

==Links und Materialien==
===Security/Usability===
* [http://www.cl.cam.ac.uk/~rja14/book.html Security Engineering, Kapitel 2: Usability and Psychology]
* Security and Usability: Designing Secure Systems That People Can Use, Lorrie Faith Cranor, Simson Garfinkel et.al., O'Reilly Media, ISBN 0596008279
* [https://csclub.uwaterloo.ca/media/Off-the-Record%20Messaging:%20Useful%20Security%20and%20Privacy%20for%20IM.html Wie Off-The-Record funktioniert und warum]: Usability, Verbreitbarkeit, Effektivität, "Resilienz"/Fehlerresistenz (von [https://en.wikipedia.org/wiki/Ian_Goldberg Ian Goldberg])
* Usability: [http://jnd.org/dn.mss/when_security_gets_in_the_way.html »When Security gets in the Way«] (D. Norman)

===Kyptografie===
* [https://en.khanacademy.org/math/applied-math/cryptography/modern-crypt/v/the-fundamental-theorem-of-arithmetic-1 The intro to cryptography on Khan Academy] several 3-5min Videos. Easy.
* [http://www.mat-d.com/site/rsa-diffie-hellman-explained-in-3-minutes/ Diffie-Hellman-Key-Exchange] – ca. 2 DINA4 pages Text. How can you get a secret key without ever seeing each other or sending it?
* Zur Belohnung nach der Mathematik: [http://www.schneierfacts.com/ Bruce Schneier Facts]. Es hat keinen Bildungswert, ist aber lustig (wenn man ''sehr'' nerdigen Humor mag)

===Ausprobieren…===
* Mobile Applikationen testen, aber kein Telefon zur Hand? (Aber einen PC?): den [https://developer.android.com/sdk/index.html Android-Simulator] nutzen, der ein Android-System auf eurem Computer simuliert. ("SDK-Tools only" reicht aus). Schaut das [https://www.youtube.com/watch?v=4r3o2eBzyrs erklärende Video] an.
* https://guardianproject.info/apps/chatsecure/ ChatSecure]. ist die App, mit der wir u.A. arbeiten werden. Installieren über [https://play.google.com/store/apps/details?id=info.guardianproject.otr.app.im Android Store] oder direkt aus dem [https://guardianproject.info/releases/ChatSecure-v12.6.4-RC3.apk Repository]
* [http://www.pidgin.im/ Pidgin] kann mittels [https://otr.cypherpunks.ca/ OTR-Plugin] sicher mit ChatSecure (und vielen anderen Instant-Messangern) Nachrichten senden.
* man braucht natürlich mindestens einen XMPP-Account. Den kann man z.B. bei [http://einfachjabber.de/reg einfachjabber] oder [https://dukgo.com/blog/using-pidgin-with-xmpp-jabber dukgo] anlegen.

===Bücher Design===
* Interaction Design: Beyond Human-Computer Interaction – Preece, Rogers and Sharp, ISBN 978-0470665763 ''Interaktionsdesign-Bezug, darin aber sehr umfassender Überblick''

* Observing the User Experience: A Practitioner's Guide to User Research, Kuneavski, ISBN 978-1558609235

===Human Centered Design===

* Abläufe Analysieren: [http://mindthegap.blog.bau-ha.us/2013/08/from-research-to-requirements-user-need-tables/316/ User Need Tables] (Quellen sind dort verlinkt)
* Personas erstellen: About Face 3, Cooper et.al. (In der Bib)
* [[IFD:Course_Interaction_Design|Interaktionsdesign-Kurs]] Ein Script zu einem vorhergehenden, ähnlichen Werkmodul.
* [http://www.uxmatters.com/mt/archives/2011/10/research-guidelines-you-wont-find-in-a-textbook.php 3 Regeln für Nutzerforschung: Sich Anfreunden, nicht zum Fragen beantworten da sein, nichts "verkaufen"]
* [http://www.experientia.com/blog/ Putting People First-Blog] (u.A. Forschung, Gender, Bildung etc. im HCD. Keine hurra-wir-sind-toll-Artikel, sondern interessante Inhalte.)

===Mobile Apps===
[http://www.cs.uml.edu/~fredm/courses/91.308-fall05/palm/zenofpalm.pdf The Zen of Palm]. Gute Zusammenfassung.

===Heuristische Analyse===
Hinweis: Eine heuristische Analyse kann das Testen nur ergänzen, aber nicht ersetzen!
* [http://www.nngroup.com/articles/ten-usability-heuristics/ List of Heuristics]
* [http://www.nngroup.com/articles/how-to-conduct-a-heuristic-evaluation/ How to do a heuristic evaluation] (and statistics which number of evaluatiors are best and/or most efficient etc.)

===Software===
* [http://developer.nokia.com/Resources/Tools_and_downloads/Other/Flowella/ Nokia Flowella] für Durchklick-Prototypen
* [http://www.jQuery.com jQuery] für aufwändiger, interaktive Prototypen.

===Nützliches===
* Ein [http://en.wikipedia.org/wiki/Service_blueprint Service Blueprint] zum [http://www.flickr.com/photos/brandonschauer/3363169836/ Download]

* [http://m18.uni-weimar.de/mailman/listinfo/interaction Sign up] for our (inofficial) BU Interaction Design Mailinglist

===Meta===
...das Designen von Designlehre
* [http://www.newyorker.com/reporting/2012/01/30/120130fa_fact_lehrer?currentPage=all Brainstorming: Eine Kritik] (vgl. mit der pro-Brainstorm-Kultur von e.g. Design Thinking)
* Parallel Prototyping:Eine empirische Studie von [http://aaalab.stanford.edu/papers/Parallel_Prototyping_2010.pdf 2010] und einer von [http://www.sigchi.org/chi95/proceedings/shortppr/so_bdy.htm 1995], deren Ergebnisse sehr für paralelles Prototyping sprechen.
* Das Iteration sinnvoll ist, ist auch nix neues, aber auch hier eine [http://www.itu.dk/people/jeppeh/specialeartikler/The%20Efficacy%20of%20Prototyping%20Under%20Time%20Constraints.pdf Studie] dazu
* Gruppen, die sich nach bestehenden Freundschaften zusammenfinden, sind für designerische Gruppenarbeiten [http://www.stanford.edu/~roypea/RoyPDF%20folder/A154_CSCL09_Maldonado_Klemmer_Pea.pdf nicht gut geeignet]
* [http://hci.stanford.edu/publications/2011/PrototypingDynamics/PrototypingDynamics-CHI2011.pdf mehrere Designs erstellen und teilen] ist vorteilhaft. [http://hci.stanford.edu/publications/2012/RepeatedExamplesCogSci2012/RepeatedExamplesCogSci2012.pdf Früh mehrfach Beispiele zu teilen] verbessert Resultate.
* The Reflective Practitioner (D. Schön), ISBN 0465068782

IFD:Nutzerstudien WiSe1314/Gruppe Anmeldung

2014-01-30T14:15:45Z

Kede7290:

IFD:Nutzerstudien WiSe1314/Gruppe Anmeldung

2014-01-30T14:06:20Z

Kede7290:

'''DOCUMENTATION'''

'''Course Aims'''

During the course "Nutzerstudien" we wanted to know how important security is for students at our age, what they expect from chat apps and what their problems/whishes are.
For that purpose we tested the app "ChatSecure" and tried to improve the design based on usability tests.

Our main focus premised on the process of creating an account and of signing in.

'''Interviews and target group'''
For that reason we started to interview a few people from our social environment as our target group. So we focused on students at the age of 20 - 30. We reached this test persons personally so we met them to conduct the interviews directly.

'''Analyse and Assessment'''
After that we analysed the results (infinity diagramming) by summing up, comparing and strucuring.

'''Prototypes and scenarios'''
Then we began to create prototypes. These prototypes also passed through usability tests to further improve the design.
For that prototypes we constructed scenarios which had to be accomplished by the test users.

'''Improving Design by Iteration'''
We further improved our design by iteration (five steps) to get our final design.

'''Data gathering: Interviews/Observation'''

1. Interviews:

Interview partner:

{| class="wikitable"
|-
! Number
! Age class
! Course of studies
|-
| 1
| <20
| Arts
|-
| 2
| <20
| Arts
|-
| 3
| 20-25
| Science/Engineering
|-
| 4
| 25-30
| Science/Engineering
|-
| 5
| <20
| Fine Arts/Design
|-
| 6
| <20
| Fine Arts/Design
|-
| 7
| <20
| Fine Arts/Design
|}

Reasons for choosing these people:

We wanted to figure out the differences between the students of Arts, Fine Arts/Design and Science/Engineering. So we chose people from our social environment. Because we are students from different courses of studies (Arts, Fine Arts/Design and Science/Engineering) we had the chance to interview these types of students. Thereby we had a huge spectrum of users.

Central questions:
* What chat apps/programs do you use and for what purposes (one-on-one interviews or group discussions, image, video and link transfer)?
* Where do you see advantages and disadvantages of your favorite chat program?
* How important authentication is for you?
* How should a trustable profile be? What information are important?
* In what situations you prefer the phone or an E-Mail before chatting?
* What are requirements for you to use a new app with guaranteed security?
* How often do you use them and how important they are for you?
* How important is security for you while chatting with people?
* What measures do you probably adopt to be safe?
* What functions and design features do you find most important for a chat app?

2. Observation:

Next week we want to make some usability tests of the app (ChatSecure) to find out how others deal with the login process. We want to find out if the log in process is intuitive for the user or not. So we get to know about user's handling with apps and their expectations. We hope to get suggestions and ideas for a better log in process based on the user's behavior.
<div style="color:darkgreen">Great idea. It is not easy though to see why for an outsider. You could fix it by explaining first, why and how you canged to the topic "login" and because of this it could not be part of the interview process one or two weeks ago.</div>--[[User:JanD|JanD]] 19:58, 13 December 2013 (CET)
<div style="color:blue">I tried to explain what we want to achieve with the usability tests. Ok? [M.E.]</div>
<div style="color:brown">I think this is an area that definitely needs analysis from a usability perspective, and having feedback from people who have limited experience with ChatSecure will be quite helpful. Having a few different setup scenarios to test with would be very useful since the login is quite different depending on what kind of account, etc. For example, using the same Google account as the phone should be quite simple. Using a Facebook acocunt should be a little more work, but straightforward. Using any account with Tor/Orbot would be trickier. And perhaps the hardest will be setting up an account on a server like jabber.ccc.de</div>--[[User:Hans|Hans]] 21:17, 18 December 2013 (CET)

'''Data Analysis & Main Results'''

[[File:Nutzerstudien-Authentifizierung.jpg| 600 px]]

* App Requirements
** accessibility is of prime importance, so the app have to be widespread to make the user downloading it.
** The app should be for free.
** For the user it’s important to be up-to-date and flexible with messages. So he/she prefers an app for chatting.

* Visual Design
** Complexity takes a lot of time, so you need a simple, intuitive, neatly arranged design, which looks uniform on all gadgets.

* Interface & Functions
**It is handy for the user to have an interface, where you can see who is online at the moment and when a contact was online the last time.
** The app should contain a function to let the user know if the chat partner read the messages because it faciliate the communication.
** The user wants to send out photos/videos.
** The user likes to express its emotion with a lot of smileys.
** The function "writes..." is not necassary. <div style="color:brown">not quite sure what this is, could you elaborate on it?</div>--[[User:Hans|Hans]] 21:35, 18 December 2013 (CET)

* Security
** It would be useful to have a password for the app.
** To feel safe, the user desires to have a security warranty.
** It is important that apps are immune from viruses.
** Important information, link, photos, videos, … are often sent by E-Mail.
** Distrust towards apps results e.g. from missing knowledge about safety and smart phone-apps.
** People use safety-options of social networks (e.g. Facebook) but don’t know, if they really work.

* Authenticity
** If you want a trustworthy profile you have to find a good balance between too much and too little information.
** (To much) Personalized advertising makes the user feel insecure.
** A “real” profile picture is soothing for the user.
** Authenticity doesn't loom large for students personally.

<div style="color:darkgreen">There are lots of "the user wants". It would be easier for outsiders to understand, if you could explain ''why'' the user wants this ('''if''' you know that. Naturally, my request is not asking for inventing explanations! If you only know that users ''want'' but not ''why'' you could make it subject of further research)</div>--[[User:JanD|JanD]] 19:58, 13 December 2013 (CET)

<div style="color:blue">I tried to phrase and explain some points in another way. Is it ok? [M.E.]</div>
<div style="color:brown">Definitely some interesting results here, it sounds like people are interested in security and are trying to figure out ways to increase their own security. It would be quite valuable to explore ideas of how people represent their concerns, and how they aim to increase their own security. About Authenticity, its a hard concept in computers. I think most computer users don't understand that its easy to fake messages. My guess is that people are concerned about it, but don't really understand the technical issues so they assume things they receive are what they seem to be. A parallel test on this topic could be very illuminating, like showing users how to generate fake emails, messages, etc. to make them appear they are coming from someone they trust. Also, I'm not quite sure what the point of view of all of these bullet points are. Are they from the person running the tests, or are the things that the users in the tests communicated? My guess is that they are all summaries of things communicated from the users.</div>--[[User:Hans|Hans]] 21:35, 18 December 2013 (CET)

==First design considerations and ideas==

'''What specific problem we want to solve'''

We want to solve some problems with the login-process and make it easier to use.
It's hard and circular to login with one of your accounts, because there are too many steps until you are finally logged in. Moreover the buttons are difficult to find on the interface.
Therefore we want to create a new login-process.

<div style="color:darkgreen">Nice proposal. Are you really talking about the log-in or about setting up a new (Jabber) account? Because in my experience it is not easy to set it up, but once you have your account working and data saved, it behaves very well. But please prove me wrong if that is a singular experience</div>--[[User:JanD|JanD]] 19:58, 13 December 2013 (CET)

<div style="color:blue">We really focus on the sign up process. There is the problem that you don't get an advice to enter the password but it is nessacary. The process is very inconvenient, it needs to many steps till you can start to chat so that we want to create an easier way. [M.E.]</div>

<div style="color:brown">I think this is important work since the process is currently confusing, but also complicated so its not easy to fix the usability issues. But its also not such a huge task, so you should be able to get solid results in the time you have in this class.</div>--[[User:Hans|Hans]] 21:35, 18 December 2013 (CET)

'''Plans – how we want to solve the problem(s)'''

Method 1: Other application's test

First we start to analyse the login process at other applications.
We found out that WhatsApp is the most widespread app to chat for our target group, second one is the Facebook messanger.

1. WhatsApp

This application doesn't contain a login process. You only have to choose the app to be online and you directly see all of your conversations. It is quite easy and intuitive.

2. Facebook Messenger

This application functions nearly the same way as WhatsApp, so you don't need a password to sign in.

Our conclusion:

Both applications manage without a password. That's quite intuitive but it isn't quite save. While doing our interviews we experienced that it would be convenient to have a password to have a safety warranty (e.g. in case of losing the smartphone)

Solution:

We want it as intuitive as WhatsApp and Facebook Messenger but we also want it to be save. So there have to be an additional button for entering a password.

==Prototypes==

Our first prototype for the login process contains the additional password entering button if it isn't saved. (at the beginning you can choose if you want to save the password for further use or not)
It occurs when you want to switch from offline to online as an extra field.

[[File:Prototyp Anmeldeprozess.jpg|600px]]

<div style="color:brown">The difficult part here is that there is no known way of making a secure, private connection without some kind of login process. WhatsApp's uses an automatically generated password that it is not hard for a malicious user to generate, getting full access to the whole account. So its security is very poor, but its usability is great. As far as I know, Facebook does require a login, but it just handles it well and it only happens once really. Facebook is probably a better example here. It probably makes the most sense to compare the Facebook mobile app's first time setup/login procedure with ChatSecure's Facebook login procedure. Then additionally, it would be great to see a comparison of other apps like ChatSecure that allow users to use a wide variety of accounts (Xabber, Beem, etc.) </div>--[[User:Hans|Hans]] 21:35, 18 December 2013 (CET)

==Our conclusions==
problems we had
what we would do better next time
our final design

IFD:Nutzerstudien WiSe1314/Gruppe Anmeldung

2014-01-30T11:24:32Z

Kede7290:

'''[[Documentation]]'''

'''Course Aims'''

During the course "Nutzerstudien" we wanted to know how important security is for students at our age, what they expect from chat apps and what their problems/whishes are.
For that purpose we tested the app "ChatSecure" and tried to improve the design based on usability tests.

Our main focus premised on the process of creating an account and of signing in.
For that reason we started to interview a few people from our social environment. After that we analysed the results (infinity diagramming) and began to create prototypes. These prototypes also passed through usability tests to further improve the design.
For that prototypes we constructed scenarios which had to be accomplished by the test users. So we further improved our design by iteration to get our final design.

'''Data gathering: Interviews/Observation'''

1. Interviews:

Interview partner:

{| class="wikitable"
|-
! Number
! Age class
! Course of studies
|-
| 1
| <20
| Arts
|-
| 2
| <20
| Arts
|-
| 3
| 20-25
| Science/Engineering
|-
| 4
| 25-30
| Science/Engineering
|-
| 5
| <20
| Fine Arts/Design
|-
| 6
| <20
| Fine Arts/Design
|-
| 7
| <20
| Fine Arts/Design
|}

Reasons for choosing these people:

We wanted to figure out the differences between the students of Arts, Fine Arts/Design and Science/Engineering. So we chose people from our social environment. Because we are students from different courses of studies (Arts, Fine Arts/Design and Science/Engineering) we had the chance to interview these types of students. Thereby we had a huge spectrum of users.

Central questions:
* What chat apps/programs do you use and for what purposes (one-on-one interviews or group discussions, image, video and link transfer)?
* Where do you see advantages and disadvantages of your favorite chat program?
* How important authentication is for you?
* How should a trustable profile be? What information are important?
* In what situations you prefer the phone or an E-Mail before chatting?
* What are requirements for you to use a new app with guaranteed security?
* How often do you use them and how important they are for you?
* How important is security for you while chatting with people?
* What measures do you probably adopt to be safe?
* What functions and design features do you find most important for a chat app?

2. Observation:

Next week we want to make some usability tests of the app (ChatSecure) to find out how others deal with the login process. We want to find out if the log in process is intuitive for the user or not. So we get to know about user's handling with apps and their expectations. We hope to get suggestions and ideas for a better log in process based on the user's behavior.
<div style="color:darkgreen">Great idea. It is not easy though to see why for an outsider. You could fix it by explaining first, why and how you canged to the topic "login" and because of this it could not be part of the interview process one or two weeks ago.</div>--[[User:JanD|JanD]] 19:58, 13 December 2013 (CET)
<div style="color:blue">I tried to explain what we want to achieve with the usability tests. Ok? [M.E.]</div>
<div style="color:brown">I think this is an area that definitely needs analysis from a usability perspective, and having feedback from people who have limited experience with ChatSecure will be quite helpful. Having a few different setup scenarios to test with would be very useful since the login is quite different depending on what kind of account, etc. For example, using the same Google account as the phone should be quite simple. Using a Facebook acocunt should be a little more work, but straightforward. Using any account with Tor/Orbot would be trickier. And perhaps the hardest will be setting up an account on a server like jabber.ccc.de</div>--[[User:Hans|Hans]] 21:17, 18 December 2013 (CET)

'''Data Analysis & Main Results'''

[[File:Nutzerstudien-Authentifizierung.jpg| 600 px]]

* App Requirements
** accessibility is of prime importance, so the app have to be widespread to make the user downloading it.
** The app should be for free.
** For the user it’s important to be up-to-date and flexible with messages. So he/she prefers an app for chatting.

* Visual Design
** Complexity takes a lot of time, so you need a simple, intuitive, neatly arranged design, which looks uniform on all gadgets.

* Interface & Functions
**It is handy for the user to have an interface, where you can see who is online at the moment and when a contact was online the last time.
** The app should contain a function to let the user know if the chat partner read the messages because it faciliate the communication.
** The user wants to send out photos/videos.
** The user likes to express its emotion with a lot of smileys.
** The function "writes..." is not necassary. <div style="color:brown">not quite sure what this is, could you elaborate on it?</div>--[[User:Hans|Hans]] 21:35, 18 December 2013 (CET)

* Security
** It would be useful to have a password for the app.
** To feel safe, the user desires to have a security warranty.
** It is important that apps are immune from viruses.
** Important information, link, photos, videos, … are often sent by E-Mail.
** Distrust towards apps results e.g. from missing knowledge about safety and smart phone-apps.
** People use safety-options of social networks (e.g. Facebook) but don’t know, if they really work.

* Authenticity
** If you want a trustworthy profile you have to find a good balance between too much and too little information.
** (To much) Personalized advertising makes the user feel insecure.
** A “real” profile picture is soothing for the user.
** Authenticity doesn't loom large for students personally.

<div style="color:darkgreen">There are lots of "the user wants". It would be easier for outsiders to understand, if you could explain ''why'' the user wants this ('''if''' you know that. Naturally, my request is not asking for inventing explanations! If you only know that users ''want'' but not ''why'' you could make it subject of further research)</div>--[[User:JanD|JanD]] 19:58, 13 December 2013 (CET)

<div style="color:blue">I tried to phrase and explain some points in another way. Is it ok? [M.E.]</div>
<div style="color:brown">Definitely some interesting results here, it sounds like people are interested in security and are trying to figure out ways to increase their own security. It would be quite valuable to explore ideas of how people represent their concerns, and how they aim to increase their own security. About Authenticity, its a hard concept in computers. I think most computer users don't understand that its easy to fake messages. My guess is that people are concerned about it, but don't really understand the technical issues so they assume things they receive are what they seem to be. A parallel test on this topic could be very illuminating, like showing users how to generate fake emails, messages, etc. to make them appear they are coming from someone they trust. Also, I'm not quite sure what the point of view of all of these bullet points are. Are they from the person running the tests, or are the things that the users in the tests communicated? My guess is that they are all summaries of things communicated from the users.</div>--[[User:Hans|Hans]] 21:35, 18 December 2013 (CET)

==First design considerations and ideas==

'''What specific problem we want to solve'''

We want to solve some problems with the login-process and make it easier to use.
It's hard and circular to login with one of your accounts, because there are too many steps until you are finally logged in. Moreover the buttons are difficult to find on the interface.
Therefore we want to create a new login-process.

<div style="color:darkgreen">Nice proposal. Are you really talking about the log-in or about setting up a new (Jabber) account? Because in my experience it is not easy to set it up, but once you have your account working and data saved, it behaves very well. But please prove me wrong if that is a singular experience</div>--[[User:JanD|JanD]] 19:58, 13 December 2013 (CET)

<div style="color:blue">We really focus on the sign up process. There is the problem that you don't get an advice to enter the password but it is nessacary. The process is very inconvenient, it needs to many steps till you can start to chat so that we want to create an easier way. [M.E.]</div>

<div style="color:brown">I think this is important work since the process is currently confusing, but also complicated so its not easy to fix the usability issues. But its also not such a huge task, so you should be able to get solid results in the time you have in this class.</div>--[[User:Hans|Hans]] 21:35, 18 December 2013 (CET)

'''Plans – how we want to solve the problem(s)'''

Method 1: Other application's test

First we start to analyse the login process at other applications.
We found out that WhatsApp is the most widespread app to chat for our target group, second one is the Facebook messanger.

1. WhatsApp

This application doesn't contain a login process. You only have to choose the app to be online and you directly see all of your conversations. It is quite easy and intuitive.

2. Facebook Messenger

This application functions nearly the same way as WhatsApp, so you don't need a password to sign in.

Our conclusion:

Both applications manage without a password. That's quite intuitive but it isn't quite save. While doing our interviews we experienced that it would be convenient to have a password to have a safety warranty (e.g. in case of losing the smartphone)

Solution:

We want it as intuitive as WhatsApp and Facebook Messenger but we also want it to be save. So there have to be an additional button for entering a password.

==Prototypes==
[[File:Prototyp Anmeldeprozess.jpg|600px]]

Our first prototype for the login process contains the additional password entering button.

<div style="color:brown">The difficult part here is that there is no known way of making a secure, private connection without some kind of login process. WhatsApp's uses an automatically generated password that it is not hard for a malicious user to generate, getting full access to the whole account. So its security is very poor, but its usability is great. As far as I know, Facebook does require a login, but it just handles it well and it only happens once really. Facebook is probably a better example here. It probably makes the most sense to compare the Facebook mobile app's first time setup/login procedure with ChatSecure's Facebook login procedure. Then additionally, it would be great to see a comparison of other apps like ChatSecure that allow users to use a wide variety of accounts (Xabber, Beem, etc.) </div>--[[User:Hans|Hans]] 21:35, 18 December 2013 (CET)

IFD:Nutzerstudien WiSe1314/Gruppe Anmeldung

2014-01-30T10:36:54Z

Kede7290:

[['''Documentation''']]

'''Course Aims'''

During the course "Nutzerstudien" we wanted to know how important security is for students at our age, what they expect from chat apps and what their problems/whishes are.
For that purpose we tested the app "ChatSecure" and tried to improve the design based on usability tests.

Our main focus premised on the process of creating an account and of signing in.
For that reason we started to interview a few people from our social environment. After that we analysed the results (infinity diagramming) and began to create prototypes. These prototypes also passed through usability tests to further improve the design.

'''Data gathering: Interviews/Observation'''

1. Interviews:

Interview partner:

{| class="wikitable"
|-
! Number
! Age class
! Course of studies
|-
| 1
| <20
| Arts
|-
| 2
| <20
| Arts
|-
| 3
| 20-25
| Science/Engineering
|-
| 4
| 25-30
| Science/Engineering
|-
| 5
| <20
| Fine Arts/Design
|-
| 6
| <20
| Fine Arts/Design
|-
| 7
| <20
| Fine Arts/Design
|}

Reasons for choosing these people:

We wanted to figure out the differences between the students of Arts, Fine Arts/Design and Science/Engineering. So we chose people from our social environment. Because we are students from different courses of studies (Arts, Fine Arts/Design and Science/Engineering) we had the chance to interview these types of students. Thereby we had a huge spectrum of users.

Central questions:
* What chat apps/programs do you use and for what purposes (one-on-one interviews or group discussions, image, video and link transfer)?
* Where do you see advantages and disadvantages of your favorite chat program?
* How important authentication is for you?
* How should a trustable profile be? What information are important?
* In what situations you prefer the phone or an E-Mail before chatting?
* What are requirements for you to use a new app with guaranteed security?
* How often do you use them and how important they are for you?
* How important is security for you while chatting with people?
* What measures do you probably adopt to be safe?
* What functions and design features do you find most important for a chat app?

2. Observation:

Next week we want to make some usability tests of the app (ChatSecure) to find out how others deal with the login process. We want to find out if the log in process is intuitive for the user or not. So we get to know about user's handling with apps and their expectations. We hope to get suggestions and ideas for a better log in process based on the user's behavior.
<div style="color:darkgreen">Great idea. It is not easy though to see why for an outsider. You could fix it by explaining first, why and how you canged to the topic "login" and because of this it could not be part of the interview process one or two weeks ago.</div>--[[User:JanD|JanD]] 19:58, 13 December 2013 (CET)
<div style="color:blue">I tried to explain what we want to achieve with the usability tests. Ok? [M.E.]</div>
<div style="color:brown">I think this is an area that definitely needs analysis from a usability perspective, and having feedback from people who have limited experience with ChatSecure will be quite helpful. Having a few different setup scenarios to test with would be very useful since the login is quite different depending on what kind of account, etc. For example, using the same Google account as the phone should be quite simple. Using a Facebook acocunt should be a little more work, but straightforward. Using any account with Tor/Orbot would be trickier. And perhaps the hardest will be setting up an account on a server like jabber.ccc.de</div>--[[User:Hans|Hans]] 21:17, 18 December 2013 (CET)

'''Data Analysis & Main Results'''

[[File:Nutzerstudien-Authentifizierung.jpg| 600 px]]

* App Requirements
** accessibility is of prime importance, so the app have to be widespread to make the user downloading it.
** The app should be for free.
** For the user it’s important to be up-to-date and flexible with messages. So he/she prefers an app for chatting.

* Visual Design
** Complexity takes a lot of time, so you need a simple, intuitive, neatly arranged design, which looks uniform on all gadgets.

* Interface & Functions
**It is handy for the user to have an interface, where you can see who is online at the moment and when a contact was online the last time.
** The app should contain a function to let the user know if the chat partner read the messages because it faciliate the communication.
** The user wants to send out photos/videos.
** The user likes to express its emotion with a lot of smileys.
** The function "writes..." is not necassary. <div style="color:brown">not quite sure what this is, could you elaborate on it?</div>--[[User:Hans|Hans]] 21:35, 18 December 2013 (CET)

* Security
** It would be useful to have a password for the app.
** To feel safe, the user desires to have a security warranty.
** It is important that apps are immune from viruses.
** Important information, link, photos, videos, … are often sent by E-Mail.
** Distrust towards apps results e.g. from missing knowledge about safety and smart phone-apps.
** People use safety-options of social networks (e.g. Facebook) but don’t know, if they really work.

* Authenticity
** If you want a trustworthy profile you have to find a good balance between too much and too little information.
** (To much) Personalized advertising makes the user feel insecure.
** A “real” profile picture is soothing for the user.
** Authenticity doesn't loom large for students personally.

<div style="color:darkgreen">There are lots of "the user wants". It would be easier for outsiders to understand, if you could explain ''why'' the user wants this ('''if''' you know that. Naturally, my request is not asking for inventing explanations! If you only know that users ''want'' but not ''why'' you could make it subject of further research)</div>--[[User:JanD|JanD]] 19:58, 13 December 2013 (CET)

<div style="color:blue">I tried to phrase and explain some points in another way. Is it ok? [M.E.]</div>
<div style="color:brown">Definitely some interesting results here, it sounds like people are interested in security and are trying to figure out ways to increase their own security. It would be quite valuable to explore ideas of how people represent their concerns, and how they aim to increase their own security. About Authenticity, its a hard concept in computers. I think most computer users don't understand that its easy to fake messages. My guess is that people are concerned about it, but don't really understand the technical issues so they assume things they receive are what they seem to be. A parallel test on this topic could be very illuminating, like showing users how to generate fake emails, messages, etc. to make them appear they are coming from someone they trust. Also, I'm not quite sure what the point of view of all of these bullet points are. Are they from the person running the tests, or are the things that the users in the tests communicated? My guess is that they are all summaries of things communicated from the users.</div>--[[User:Hans|Hans]] 21:35, 18 December 2013 (CET)

'''What specific problem we want to solve'''

We want to solve some problems with the login-process and make it easier to use.
It's hard and circular to login with one of your accounts, because there are too many steps until you are finally logged in. Moreover the buttons are difficult to find on the interface.
Therefore we want to create a new login-process.

<div style="color:darkgreen">Nice proposal. Are you really talking about the log-in or about setting up a new (Jabber) account? Because in my experience it is not easy to set it up, but once you have your account working and data saved, it behaves very well. But please prove me wrong if that is a singular experience</div>--[[User:JanD|JanD]] 19:58, 13 December 2013 (CET)

<div style="color:blue">We really focus on the sign up process. There is the problem that you don't get an advice to enter the password but it is nessacary. The process is very inconvenient, it needs to many steps till you can start to chat so that we want to create an easier way. [M.E.]</div>

<div style="color:brown">I think this is important work since the process is currently confusing, but also complicated so its not easy to fix the usability issues. But its also not such a huge task, so you should be able to get solid results in the time you have in this class.</div>--[[User:Hans|Hans]] 21:35, 18 December 2013 (CET)

'''Plans – how we want to solve the problem(s)'''

Method 1: Other application's test

First we start to analyse the login process at other applications.
We found out that WhatsApp is the most widespread app to chat for our target group, second one is the Facebook messanger.

1. WhatsApp

This application doesn't contain a login process. You only have to choose the app to be online and you directly see all of your conversations. It is quite easy and intuitive.

2. Facebook Messenger

This application functions nearly the same way as WhatsApp, so you don't need a password to sign in.

Our conclusion:

Both applications manage without a password. That's quite intuitive but it isn't quite save. While doing our interviews we experienced that it would be convenient to have a password to have a safety warranty (e.g. in case of losing the smartphone)

Solution:

We want it as intuitive as WhatsApp and Facebook Messenger but we also want it to be save. So there have to be an additional button for entering a password.

[[File:Prototyp Anmeldeprozess.jpg|600px]]

Our first prototype for the login process.

<div style="color:brown">The difficult part here is that there is no known way of making a secure, private connection without some kind of login process. WhatsApp's uses an automatically generated password that it is not hard for a malicious user to generate, getting full access to the whole account. So its security is very poor, but its usability is great. As far as I know, Facebook does require a login, but it just handles it well and it only happens once really. Facebook is probably a better example here. It probably makes the most sense to compare the Facebook mobile app's first time setup/login procedure with ChatSecure's Facebook login procedure. Then additionally, it would be great to see a comparison of other apps like ChatSecure that allow users to use a wide variety of accounts (Xabber, Beem, etc.) </div>--[[User:Hans|Hans]] 21:35, 18 December 2013 (CET)

File:Nutzerstudien Heuristic1.pdf

2014-01-23T15:00:21Z

Kede7290: uploaded a new version of "File:Nutzerstudien Heuristic1.pdf"

== Summary ==

== Copyright status: ==

== Source: ==

File:Problem passwordentering.jpg

2014-01-23T13:53:58Z

Kede7290:

== Summary ==

== Copyright status: ==

== Source: ==

IFD:Nutzerstudien WiSe1314/HeuristicAnalysisAnmeldung

2014-01-23T13:37:46Z

Kede7290:

== Visibility of system status ==
* New Account

** While creating an account the app keeps the user informed about what is to do. There are several input fields which have to be filled. If all fields are filled up, the user gets into the main page of ChatSecure where he/she sees a box with the account.
** Unfortunately there is no special information that the creation was successful.
[[File:new_account.jpg | 200px]]

* Log In
** On the start page the user finds his created account and the information if it is on or off. So the app always shows if the user is signed in or not.

** Usually the user pushes the button of the account to start to chat. Then you get in your inside page with your friendlist. But you can’t go online without entering your password (if you didn’t save the password) Than you get this information:
[[File:problem_passwordentering.jpg | 200px]]
** What misses at the beginning is the request to enter the password if it isn’t saved.
** There is no visible button to enter the password on the main page. When the user found out that it is the tool button where he/she can enter the password, then the app shows “application accomplished” and then the status “online” at the main page.
** When the user is finally online, he/she gets into the chat page and there is a button with “online” so that the user knows his/her status.

[[File:login_visability.jpg | 800px]]

* Settings

** There are visible boxes to fill with ticks so that the user always knows which option he/she uses or not.
[[File:settings.jpg | 200px]]

== Match between system and the real world==

* New Account

** The process of creating an account only consists of simple words that the user has to fill in (user name, password). But there are two fields/ buttons where I personally didn’t hear yet. Firstly I didn’t know what to choose as a domain and secondly I don’t know what “Verbinden über Tor (Benötigt Orbot app) means. Maybe that should be explained more to the user.

[[File:new_account_complication.jpg | 200px]]

* Log In

** The words “on” and “off” are clear to the user, it is also simple to find out that the user have to shove the button to change the status.
As already shown it isn’t intuitive for the user to enter the password with the help of the tool button at the right side.

* Settings

** All options are clear or they are explained but it would be better to keep one language and not to have an English heading and a German explanation.

[[File:settings_language.jpg | 200px]]

== User control and freedom==

* There are two possibilities to close the app but if you use the first, the program is closed and you get the information “ChatSecure stopped”. That is an error because it shows that the app didn’t react correctly. (no screenshot possible)

== Consistency and standards ==

* New Account

** The app uses standard words that other apps uses too, like user name, password etc.

* Log In

** Maybe first the user doesn’t notice the difference between “on”/”off” and “online”/”offline”.

** Unlike others, who have a slide bar to log in, I have to click on a checkmark. Since I have never logged in that way I needed some time to figure out that this is the log-in-button.

* Settings

** The settings largely follow platform conventions, like e.g. vibrate, audio.

== Error prevention ==

* I didn’t notice any error prevention while creating an account, signing in or at the settings.

== Recognition rather than recall==

* New Account

** At the main page there is a plus button to create a new account or to use an existing one. The user has to remember that but it is quite intuitive. For other actions the user doesn’t have to remember something from another part.

* Log In

** The user has to remember that he/she has to enter the password at the tool button at the right side. There is no instruction for it.

[[File:login_complication.jpg | 200px]]

* Settings

** There are two possible options to find the settings. Either the user pushes the left button at the smartphone (e.g. Samsung Galaxy S2) or he/she goes throw the lock and chooses “settings”. The second one is more intuitive for the user.
For the first possibility there is no advice that the settings are at that place but it isn’t necessary because there is the second one.

== Flexibility and efficiency of use==

* couldn’t find out differences for novice users and experts.

== Aesthetic and minimalist design==

* New Account

** There are no irrelevant buttons and a clear, simple design.

* Log In

** The design is simple but there are redundant steps to log in (first shove at “on”, than enter the password, than push on the account etc.) It would be enough to have one action to sign in so that it is more comfortable.

* Settings

** The design of the settings are well listed and clear. There is only one button for each option.

== Help users recognize, diagnose, and recover from errors==

* There was one error message that occurs after closing the program normally. It asked if you want to send the problem to the developers.

== Help and documentation ==

* couldn’t find a option for help or documentation so it would be necessary to add it.

IFD:Nutzerstudien WiSe1314/HeuristicAnalysisAnmeldung Person3

2014-01-23T13:09:36Z

Kede7290:

Aufgaben:
* Anmelden
* Account erstellen
* Einstellungen ("Settings")
{{IFD_Nutzerstudien_HeuristischeEvaluationAnweisungen}}

== Visibility of system status ==

*Create new account:
**The created account is visible and thus it's sure that the account was successfully created.
**But after I created a new account and agreed to the certificate the system crashed.

[[File:report_chat_secure.JPG | 200px]]

[[File:syytem_crash_chat_secure.jpeg | 200px]]

*Login:
**When the system is about to login a little loading bar could be usefull to show the status of the login-progress. But thus the login-progress is quite fast, the missing loading bar is no problem.


== Match between system and the real world==

Some terms where difficult for me to understand.
*Create new account:
**I don't know what "Tor" is. Maybe there could be some help and more information in the app.

[[File:tor_chat_secure.JPG | 200px]]

== User control and freedom==

I need the app-extern "back" button to get out of the settings. Everywhere else in the app there are functions that allow me to switch back or find an exit. But in my opinion it's not a big problem. Just a litte flaw of the app.


== Consistency and standards ==

All in all the app is easy to understand. The "moves" you have to make to use the app are quite familiar and like on every other smartphone.
There are just two things, that seemed to be a problem for me.
*Settings:
**I don't understand what the "Fingerpringt"-button is supposed to be used to.

**Also the "Panic"-button could confuse the user.

[[File:settings_chat_secure.JPG | 200px]]

It also would be more helpful to use one language (German or English) consequent in the whole app, than to mix up both languages. It also would help the app to appear more serious.

[[File:language_chat_secure.JPG | 200px]]

The last thing I recognized, is that I have to encrypt my chat to send a file. But if I'm allowed to chat without encryption, why can't I send a picture without encrypt my chat?

[[File:bilder_senden_chat_secure.JPG | 200px]]

== Error prevention ==

There were no errors in the app. Just the system crash when I created my account (see "visibly of system status").
But in the whole app I can't find any help- or support-page. Maybe it would be usefull to create such a page to give quick help to the user.

== Recognition rather than recall==

I didn't noticed any difficulties.

== Flexibility and efficiency of use==

I think that the offered providers don't sound very confidental to uninformed users because of the unfamiliar names. There should be some more information about the providers.
<--! What do you mean with providers and what has it to do with flexibility and efficiency? Maybe you should explain it more precisely for outside people.-->

[[File:nutzerstudien_anmedlung_create_jabberanbieter.png | 200 px]]

For the "first use"-user the account settings are a little bit hard to understand. But I think this results out of missing knowledge in the domains internet and programming. For the user, who is a little more comfortable with this topics it should be no problem.

In all other aspects I don't see any differences for beginners and advanced users.

== Aesthetic and minimalist design==

The design is quite modern and organized.
It would only be nice to use one language instead of mixing German and English.
<--! Was it your intent to state it twice?-->

== Help users recognize, diagnose, and recover from errors==

The only bug/error that happend to me was the system crash, when I created my account.

== Help and documentation ==

It would be very useful to have an short help- or support-page to give quick help to the user.

IFD:Nutzerstudien WiSe1314/HeuristicAnalysisAnmeldung

2014-01-23T12:42:10Z

Kede7290:

== Visibility of system status ==
* New Account

** While creating an account the app keeps the user informed about what is to do. There are several input fields which have to be filled. If all fields are filled up, the user gets into the main page of ChatSecure where he/she sees a box with the account.
** Unfortunately there is no special information that the creation was successful.
[[File:new_account.jpg | 200px]]

* Log In
** On the start page the user finds his created account and the information if it is on or off. So the app always shows if the user is signed in or not.

** Usually the user pushes the button of the account to start to chat. What misses is the request to enter the password. If he/she didn’t do that, it isn’t possible to chat.
** There is no visible button to enter the password on the main page. When the user found out that it is the tool button where he/she can enter the password, then the app shows “application accomplished” and then the status “online” at the main page.
** When the user is finally online, he/she gets into the chat page and there is a button with “online” so that the user knows his/her status.

[[File:login_visability.jpg | 800px]]

* Settings

** There are visible boxes to fill with ticks so that the user always knows which option he/she uses or not.
[[File:settings.jpg | 200px]]

== Match between system and the real world==

* New Account

** The process of creating an account only consists of simple words that the user has to fill in (user name, password). But there are two fields/ buttons where I personally didn’t hear yet. Firstly I didn’t know what to choose as a domain and secondly I don’t know what “Verbinden über Tor (Benötigt Orbot app) means. Maybe that should be explained more to the user.

[[File:new_account_complication.jpg | 200px]]

* Log In

** The words “on” and “off” are clear to the user, it is also simple to find out that the user have to shove the button to change the status.
As already shown it isn’t intuitive for the user to enter the password with the help of the tool button at the right side.

* Settings

** All options are clear or they are explained but it would be better to keep one language and not to have an English heading and a German explanation.

[[File:settings_language.jpg | 200px]]

== User control and freedom==

* There are two possibilities to close the app but if you use the first, the program is closed and you get the information “ChatSecure stopped”. That is an error because it shows that the app didn’t react correctly. (no screenshot possible)

== Consistency and standards ==

* New Account

** The app uses standard words that other apps uses too, like user name, password etc.

* Log In

** Maybe first the user doesn’t notice the difference between “on”/”off” and “online”/”offline”.

** Unlike others, who have a slide bar to log in, I have to click on a checkmark. Since I have never logged in that way I needed some time to figure out that this is the log-in-button.

* Settings

** The settings largely follow platform conventions, like e.g. vibrate, audio.

== Error prevention ==

* I didn’t notice any error prevention while creating an account, signing in or at the settings.

== Recognition rather than recall==

* New Account

** At the main page there is a plus button to create a new account or to use an existing one. The user has to remember that but it is quite intuitive. For other actions the user doesn’t have to remember something from another part.

* Log In

** The user has to remember that he/she has to enter the password at the tool button at the right side. There is no instruction for it.

[[File:login_complication.jpg | 200px]]

* Settings

** There are two possible options to find the settings. Either the user pushes the left button at the smartphone (e.g. Samsung Galaxy S2) or he/she goes throw the lock and chooses “settings”. The second one is more intuitive for the user.
For the first possibility there is no advice that the settings are at that place but it isn’t necessary because there is the second one.

== Flexibility and efficiency of use==

* couldn’t find out differences for novice users and experts.

== Aesthetic and minimalist design==

* New Account

** There are no irrelevant buttons and a clear, simple design.

* Log In

** The design is simple but there are redundant steps to log in (first shove at “on”, than enter the password, than push on the account etc.) It would be enough to have one action to sign in so that it is more comfortable.

* Settings

** The design of the settings are well listed and clear. There is only one button for each option.

== Help users recognize, diagnose, and recover from errors==

* There was one error message that occurs after closing the program normally. It asked if you want to send the problem to the developers.

== Help and documentation ==

* couldn’t find a option for help or documentation so it would be necessary to add it.

IFD:Nutzerstudien WiSe1314/HeuristicAnalysisAnmeldung

2014-01-23T12:41:52Z

Kede7290:

== Visibility of system status ==
* New Account

** While creating an account the app keeps the user informed about what is to do. There are several input fields which have to be filled. If all fields are filled up, the user gets into the main page of ChatSecure where he/she sees a box with the account.
** Unfortunately there is no special information that the creation was successful.
[[File:new_account.jpg | 200px]]

* Log In
** On the start page the user finds his created account and the information if it is on or off. So the app always shows if the user is signed in or not.

** Usually the user pushes the button of the account to start to chat. What misses is the request to enter the password. If he/she didn’t do that, it isn’t possible to chat.
** There is no visible button to enter the password on the main page. When the user found out that it is the tool button where he/she can enter the password, then the app shows “application accomplished” and then the status “online” at the main page.
** When the user is finally online, he/she gets into the chat page and there is a button with “online” so that the user knows his/her status.

[[File:login_visability.jpg | 400px]]

* Settings

** There are visible boxes to fill with ticks so that the user always knows which option he/she uses or not.
[[File:settings.jpg | 200px]]

== Match between system and the real world==

* New Account

** The process of creating an account only consists of simple words that the user has to fill in (user name, password). But there are two fields/ buttons where I personally didn’t hear yet. Firstly I didn’t know what to choose as a domain and secondly I don’t know what “Verbinden über Tor (Benötigt Orbot app) means. Maybe that should be explained more to the user.

[[File:new_account_complication.jpg | 200px]]

* Log In

** The words “on” and “off” are clear to the user, it is also simple to find out that the user have to shove the button to change the status.
As already shown it isn’t intuitive for the user to enter the password with the help of the tool button at the right side.

* Settings

** All options are clear or they are explained but it would be better to keep one language and not to have an English heading and a German explanation.

[[File:settings_language.jpg | 200px]]

== User control and freedom==

* There are two possibilities to close the app but if you use the first, the program is closed and you get the information “ChatSecure stopped”. That is an error because it shows that the app didn’t react correctly. (no screenshot possible)

== Consistency and standards ==

* New Account

** The app uses standard words that other apps uses too, like user name, password etc.

* Log In

** Maybe first the user doesn’t notice the difference between “on”/”off” and “online”/”offline”.

** Unlike others, who have a slide bar to log in, I have to click on a checkmark. Since I have never logged in that way I needed some time to figure out that this is the log-in-button.

* Settings

** The settings largely follow platform conventions, like e.g. vibrate, audio.

== Error prevention ==

* I didn’t notice any error prevention while creating an account, signing in or at the settings.

== Recognition rather than recall==

* New Account

** At the main page there is a plus button to create a new account or to use an existing one. The user has to remember that but it is quite intuitive. For other actions the user doesn’t have to remember something from another part.

* Log In

** The user has to remember that he/she has to enter the password at the tool button at the right side. There is no instruction for it.

[[File:login_complication.jpg | 200px]]

* Settings

** There are two possible options to find the settings. Either the user pushes the left button at the smartphone (e.g. Samsung Galaxy S2) or he/she goes throw the lock and chooses “settings”. The second one is more intuitive for the user.
For the first possibility there is no advice that the settings are at that place but it isn’t necessary because there is the second one.

== Flexibility and efficiency of use==

* couldn’t find out differences for novice users and experts.

== Aesthetic and minimalist design==

* New Account

** There are no irrelevant buttons and a clear, simple design.

* Log In

** The design is simple but there are redundant steps to log in (first shove at “on”, than enter the password, than push on the account etc.) It would be enough to have one action to sign in so that it is more comfortable.

* Settings

** The design of the settings are well listed and clear. There is only one button for each option.

== Help users recognize, diagnose, and recover from errors==

* There was one error message that occurs after closing the program normally. It asked if you want to send the problem to the developers.

== Help and documentation ==

* couldn’t find a option for help or documentation so it would be necessary to add it.

IFD:Nutzerstudien WiSe1314/HeuristicAnalysisAnmeldung

2014-01-23T12:41:28Z

Kede7290:

== Visibility of system status ==
* New Account

** While creating an account the app keeps the user informed about what is to do. There are several input fields which have to be filled. If all fields are filled up, the user gets into the main page of ChatSecure where he/she sees a box with the account.
** Unfortunately there is no special information that the creation was successful.
[[File:new_account.jpg | 200px]]

* Log In
** On the start page the user finds his created account and the information if it is on or off. So the app always shows if the user is signed in or not.

** Usually the user pushes the button of the account to start to chat. What misses is the request to enter the password. If he/she didn’t do that, it isn’t possible to chat.
** There is no visible button to enter the password on the main page. When the user found out that it is the tool button where he/she can enter the password, then the app shows “application accomplished” and then the status “online” at the main page.
** When the user is finally online, he/she gets into the chat page and there is a button with “online” so that the user knows his/her status.

[[File:login_visability.jpg | 200px]]

* Settings

** There are visible boxes to fill with ticks so that the user always knows which option he/she uses or not.
[[File:settings.jpg | 200px]]

== Match between system and the real world==

* New Account

** The process of creating an account only consists of simple words that the user has to fill in (user name, password). But there are two fields/ buttons where I personally didn’t hear yet. Firstly I didn’t know what to choose as a domain and secondly I don’t know what “Verbinden über Tor (Benötigt Orbot app) means. Maybe that should be explained more to the user.

[[File:new_account_complication.jpg | 200px]]

* Log In

** The words “on” and “off” are clear to the user, it is also simple to find out that the user have to shove the button to change the status.
As already shown it isn’t intuitive for the user to enter the password with the help of the tool button at the right side.

* Settings

** All options are clear or they are explained but it would be better to keep one language and not to have an English heading and a German explanation.

[[File:settings_language.jpg | 200px]]

== User control and freedom==

* There are two possibilities to close the app but if you use the first, the program is closed and you get the information “ChatSecure stopped”. That is an error because it shows that the app didn’t react correctly. (no screenshot possible)

== Consistency and standards ==

* New Account

** The app uses standard words that other apps uses too, like user name, password etc.

* Log In

** Maybe first the user doesn’t notice the difference between “on”/”off” and “online”/”offline”.

** Unlike others, who have a slide bar to log in, I have to click on a checkmark. Since I have never logged in that way I needed some time to figure out that this is the log-in-button.

* Settings

** The settings largely follow platform conventions, like e.g. vibrate, audio.

== Error prevention ==

* I didn’t notice any error prevention while creating an account, signing in or at the settings.

== Recognition rather than recall==

* New Account

** At the main page there is a plus button to create a new account or to use an existing one. The user has to remember that but it is quite intuitive. For other actions the user doesn’t have to remember something from another part.

* Log In

** The user has to remember that he/she has to enter the password at the tool button at the right side. There is no instruction for it.

[[File:login_complication.jpg | 200px]]

* Settings

** There are two possible options to find the settings. Either the user pushes the left button at the smartphone (e.g. Samsung Galaxy S2) or he/she goes throw the lock and chooses “settings”. The second one is more intuitive for the user.
For the first possibility there is no advice that the settings are at that place but it isn’t necessary because there is the second one.

== Flexibility and efficiency of use==

* couldn’t find out differences for novice users and experts.

== Aesthetic and minimalist design==

* New Account

** There are no irrelevant buttons and a clear, simple design.

* Log In

** The design is simple but there are redundant steps to log in (first shove at “on”, than enter the password, than push on the account etc.) It would be enough to have one action to sign in so that it is more comfortable.

* Settings

** The design of the settings are well listed and clear. There is only one button for each option.

== Help users recognize, diagnose, and recover from errors==

* There was one error message that occurs after closing the program normally. It asked if you want to send the problem to the developers.

== Help and documentation ==

* couldn’t find a option for help or documentation so it would be necessary to add it.

File:Login complication.jpg

2014-01-20T17:35:36Z

Kede7290:

== Summary ==

== Copyright status: ==

== Source: ==

File:Settings language.jpg

2014-01-20T17:35:10Z

Kede7290:

== Summary ==

== Copyright status: ==

== Source: ==

File:New account complication.jpg

2014-01-20T17:34:18Z

Kede7290:

== Summary ==

== Copyright status: ==

== Source: ==

File:Settings.jpg

2014-01-20T17:33:50Z

Kede7290:

== Summary ==

== Copyright status: ==

== Source: ==

File:Login visability.jpg

2014-01-20T17:33:27Z

Kede7290:

== Summary ==

== Copyright status: ==

== Source: ==

File:New account.jpg

2014-01-20T17:32:40Z

Kede7290:

== Summary ==

== Copyright status: ==

== Source: ==

IFD:Nutzerstudien WiSe1314/HeuristicAnalysisAnmeldung

2014-01-20T17:30:39Z

Kede7290:

== Visibility of system status ==
* New Account

** While creating an account the app keeps the user informed about what is to do. There are several input fields which have to be filled. If all fields are filled up, the user gets into the main page of ChatSecure where he/she sees a box with the account.
** Unfortunately there is no special information that the creation was successful.
[[File:new_account.jpg]]

* Log In
** On the start page the user finds his created account and the information if it is on or off. So the app always shows if the user is signed in or not.

** Usually the user pushes the button of the account to start to chat. What misses is the request to enter the password. If he/she didn’t do that, it isn’t possible to chat.
** There is no visible button to enter the password on the main page. When the user found out that it is the tool button where he/she can enter the password, then the app shows “application accomplished” and then the status “online” at the main page.
** When the user is finally online, he/she gets into the chat page and there is a button with “online” so that the user knows his/her status.

[[File:login_visability.jpg]]

* Settings

** There are visible boxes to fill with ticks so that the user always knows which option he/she uses or not.
[[File:settings.jpg]]

== Match between system and the real world==

* New Account

** The process of creating an account only consists of simple words that the user has to fill in (user name, password). But there are two fields/ buttons where I personally didn’t hear yet. Firstly I didn’t know what to choose as a domain and secondly I don’t know what “Verbinden über Tor (Benötigt Orbot app) means. Maybe that should be explained more to the user.

[[File:new_account_complication.jpg]]

* Log In

** The words “on” and “off” are clear to the user, it is also simple to find out that the user have to shove the button to change the status.
As already shown it isn’t intuitive for the user to enter the password with the help of the tool button at the right side.

* Settings

** All options are clear or they are explained but it would be better to keep one language and not to have an English heading and a German explanation.

[[File:settings_language.jpg]]

== User control and freedom==

* There are two possibilities to close the app but if you use the first, the program is closed and you get the information “ChatSecure stopped”. That is an error because it shows that the app didn’t react correctly. (no screenshot possible)

== Consistency and standards ==

* New Account

** The app uses standard words that other apps uses too, like user name, password etc.

* Log In

** Maybe first the user doesn’t notice the difference between “on”/”off” and “online”/”offline”.

* Settings

** The settings largely follow platform conventions, like e.g. vibrate, audio.

== Error prevention ==

* I didn’t notice any error prevention while creating an account, signing in or at the settings.

== Recognition rather than recall==

* New Account

** At the main page there is a plus button to create a new account or to use an existing one. The user has to remember that but it is quite intuitive. For other actions the user doesn’t have to remember something from another part.

* Log In

** The user has to remember that he/she has to enter the password at the tool button at the right side. There is no instruction for it.

[[File:login_complication.jpg]]

* Settings

** There are two possible options to find the settings. Either the user pushes the left button at the smartphone (e.g. Samsung Galaxy S2) or he/she goes throw the lock and chooses “settings”. The second one is more intuitive for the user.
For the first possibility there is no advice that the settings are at that place but it isn’t necessary because there is the second one.

== Flexibility and efficiency of use==

* couldn’t find out differences for novice users and experts.

== Aesthetic and minimalist design==

* New Account

** There are no irrelevant buttons and a clear, simple design.

* Log In

** The design is simple but there are redundant steps to log in (first shove at “on”, than enter the password, than push on the account etc.) It would be enough to have one action to sign in so that it is more comfortable.

* Settings

** The design of the settings are well listed and clear. There is only one button for each option.

== Help users recognize, diagnose, and recover from errors==

* There was one error message that occurs after closing the program normally. It asked if you want to send the problem to the developers.

== Help and documentation ==

* couldn’t find a option for help or documentation so it would be necessary to add it.

File:Nutzerstudien Heuristic1.pdf

2014-01-13T21:03:18Z

Kede7290:

== Summary ==

== Copyright status: ==

== Source: ==

IFD:Nutzerstudien WiSe1314/HeuristicAnalysisAnmeldung Person1

2014-01-09T14:47:40Z

Kede7290:

Aufgaben:
* Anmelden
* Account erstellen
* Einstellungen ("Settings")
{{IFD_Nutzerstudien_HeuristischeEvaluationAnweisungen}}

[[File:Nutzerstudien_Heuristic1.pdf]]

IFD:Nutzerstudien WiSe1314/Gruppe Anmeldung

2013-12-17T21:20:44Z

Kede7290:

'''Aims of data gathering'''

During the course "Nutzerstudien" we wanted to know how important security is for students at our age, what they expect from chat apps and what their problems/whishes are. Main focus was also the question of authenticity.
For that reason we started to interview a few people from our social environment.

'''Data gathering: Interviews/Observation'''

1. Interviews:

Interview partner:

{| class="wikitable"
|-
! Number
! Age class
! Course of studies
|-
| 1
| <20
| Arts
|-
| 2
| <20
| Arts
|-
| 3
| 20-25
| Science/Engineering
|-
| 4
| 25-30
| Science/Engineering
|-
| 5
| <20
| Fine Arts/Design
|-
| 6
| <20
| Fine Arts/Design
|-
| 7
| <20
| Fine Arts/Design
|}

Reasons for choosing these people:

We wanted to figure out the differences between the students of Arts, Fine Arts/Design and Science/Engineering. So we chose people from our social environment. Because we are students from different courses of studies (Arts, Fine Arts/Design and Science/Engineering) we had the chance to interview these types of students. Thereby we had a huge spectrum of users.

Central questions:
* What chat apps/programs do you use and for what purposes (one-on-one interviews or group discussions, image, video and link transfer)?
* Where do you see advantages and disadvantages of your favorite chat program?
* How important authentication is for you?
* How should a trustable profile be? What information are important?
* In what situations you prefer the phone or an E-Mail before chatting?
* What are requirements for you to use a new app with guaranteed security?
* How often do you use them and how important they are for you?
* How important is security for you while chatting with people?
* What measures do you probably adopt to be safe?
* What functions and design features do you find most important for a chat app?

2. Observation:

Next week we want to make some usability tests of the app (ChatSecure) to find out how others deal with the login process. We want to find out if the log in process is intuitive for the user or not. So we get to know about user's handling with apps and their expectations. We hope to get suggestions and ideas for a better log in process based on the user's behavior.
<div style="color:darkgreen">Great idea. It is not easy though to see why for an outsider. You could fix it by explaining first, why and how you canged to the topic "login" and because of this it could not be part of the interview process one or two weeks ago.</div>--[[User:JanD|JanD]] 19:58, 13 December 2013 (CET)
<div style="color:blue">I tried to explain what we want to achieve with the usability tests. Ok? [M.E.]</div>

'''Data Analysis & Main Results'''

* App Requirements
** accessibility is of prime importance, so the app have to be widespread to make the user downloading it.
** The app should be for free.
** For the user it’s important to be up-to-date and flexible with messages. So he/she prefers an app for chatting.

* Visual Design
** Complexity takes a lot of time, so you need a simple, intuitive, neatly arranged design, which looks uniform on all gadgets.

* Interface & Functions
**It is handy for the user to have an interface, where you can see who is online at the moment and when a contact was online the last time.
** The app should contain a function to let the user know if the chat partner read the messages because it faciliate the communication.
** The user wants to send out photos/videos.
** The user likes to express its emotion with a lot of smileys.
** The function "writes..." is not necassary.

* Security
** It would be useful to have a password for the app.
** To feel save, the user desires to have a security warranty.
** It is important that apps are immune from viruses.
** Important information, link, photos, videos, … are often sent by E-Mail.
** Distrust towards apps results e.g. from missing knowledge about safety and smart phone-apps.
** People use safety-options of social networks (e.g. Facebook) but don’t know, if they really work.

* Authenticity
** If you want a trustworthy profile you have to find a good balance between too much and too little information.
** (To much) Personalized advertising makes the user feel insecure.
** A “real” profile picture is soothing for the user.
** Authenticity doesn't loom large for students personally.

<div style="color:darkgreen">There are lots of "the user wants". It would be easier for outsiders to understand, if you could explain ''why'' the user wants this ('''if''' you know that. Naturally, my request is not asking for inventing explanations! If you only know that users ''want'' but not ''why'' you could make it subject of further research)</div>--[[User:JanD|JanD]] 19:58, 13 December 2013 (CET)

<div style="color:blue">I tried to phrase and explain some points in another way. Is it ok? [M.E.]</div>

'''What specifc problem we want to solve'''

We want to solve some problems with the login-process and make it easier to use.
It's hard and circular to login with one of your accounts, because there are too many steps until you are finally logged in. Moreover the buttons are difficult to find on the interface.
Therefore we want to create a new login-process.

<div style="color:darkgreen">Nice proposal. Are you really talking about the log-in or about setting up a new (Jabber) account? Because in my experience it is not easy to set it up, but once you have your account working and data saved, it behaves very well. But please prove me wrong if that is a singular experience</div>--[[User:JanD|JanD]] 19:58, 13 December 2013 (CET)

<div style="color:blue">We really focus on the sign up process. There is the problem that you don't get an advice to enter the password but it is nessacary. The process is very inconvenient, it needs to many steps till you can start to chat so that we want to create an easier way. [M.E.]</div>

'''Plans – how we want to solve the problem(s)'''

Method 1: Other application's test

First we start to analyse the login process at other applications.
We found out that WhatsApp is the most widespread app to chat for our target group, second one is the Facebook messanger.

1. WhatsApp

This application doesn't contain a login process. You only have to choose the app to be online and you directly see all of your conversations. It is quite easy and intuitive.

2. Facebook Messenger

This application functions nearly the same way as WhatsApp, so you don't need a password to sign in.

Our conclusion:

Both applications manage without a password. That's quite intuitive but it isn't quite save. While doing our interviews we experienced that it would be convenient to have a password to have a safety warranty (e.g. in case of losing the smartphone)

Solution:

We want it as intuitive as WhatsApp and Facebook Messenger but we also want it to be save. So there have to be an additional button for entering a password.

[[File:Prototyp Anmeldeprozess.jpg|600px]]

Our first prototype for the login process.

IFD:Nutzerstudien WiSe1314/Gruppe Anmeldung

2013-12-17T21:20:12Z

Kede7290:

'''Aims of data gathering'''

During the course "Nutzerstudien" we wanted to know how important security is for students at our age, what they expect from chat apps and what their problems/whishes are. Main focus was also the question of authenticity.
For that reason we started to interview a few people from our social environment.

'''Data gathering: Interviews/Observation'''

1. Interviews:

Interview partner:

{| class="wikitable"
|-
! Number
! Age class
! Course of studies
|-
| 1
| <20
| Arts
|-
| 2
| <20
| Arts
|-
| 3
| 20-25
| Science/Engineering
|-
| 4
| 25-30
| Science/Engineering
|-
| 5
| <20
| Fine Arts/Design
|-
| 6
| <20
| Fine Arts/Design
|-
| 7
| <20
| Fine Arts/Design
|}

Reasons for choosing these people:

We wanted to figure out the differences between the students of Arts, Fine Arts/Design and Science/Engineering. So we chose people from our social environment. Because we are students from different courses of studies (Arts, Fine Arts/Design and Science/Engineering) we had the chance to interview these types of students. Thereby we had a huge spectrum of users.

Central questions:
* What chat apps/programs do you use and for what purposes (one-on-one interviews or group discussions, image, video and link transfer)?
* Where do you see advantages and disadvantages of your favorite chat program?
* How important authentication is for you?
* How should a trustable profile be? What information are important?
* In what situations you prefer the phone or an E-Mail before chatting?
* What are requirements for you to use a new app with guaranteed security?
* How often do you use them and how important they are for you?
* How important is security for you while chatting with people?
* What measures do you probably adopt to be safe?
* What functions and design features do you find most important for a chat app?

2. Observation:

Next week we want to make some usability tests of the app (ChatSecure) to find out how others deal with the login process. We want to find out if the log in process is intuitive for the user or not. So we get to know about user's handling with apps and their expectations. We hope to get suggestions and ideas for a better log in process based on the user's behavior.
<div style="color:darkgreen">Great idea. It is not easy though to see why for an outsider. You could fix it by explaining first, why and how you canged to the topic "login" and because of this it could not be part of the interview process one or two weeks ago.</div>--[[User:JanD|JanD]] 19:58, 13 December 2013 (CET)
<div style="color:blue">I tried to explain what we want to achieve with the usability tests. Ok? [M.E.]</div>

'''Data Analysis & Main Results'''

* App Requirements
** accessibility is of prime importance, so the app have to be widespread to make the user downloading it.
** The app should be for free.
** For the user it’s important to be up-to-date and flexible with messages. So he/she prefers an app for chatting.

* Visual Design
** Complexity takes a lot of time, so you need a simple, intuitive, neatly arranged design, which looks uniform on all gadgets.

* Interface & Functions
**It is handy for the user to have an interface, where you can see who is online at the moment and when a contact was online the last time.
** The app should contain a function to let the user know if the chat partner read the messages because it faciliate the communication.
** The user wants to send out photos/videos.
** The user likes to express its emotion with a lot of smileys.
** The function "writes..." is not necassary.

* Security
** It would be useful to have a password for the app.
** To feel save, the user desires to have a security warranty.
** It is important that apps are immune from viruses.
** Important information, link, photos, videos, … are often sent by E-Mail.
** Distrust towards apps results e.g. from missing knowledge about safety and smart phone-apps.
** People use safety-options of social networks (e.g. Facebook) but don’t know, if they really work.

* Authenticity
** If you want a trustworthy profile you have to find a good balance between too much and too little information.
** (To much) Personalized advertising makes the user feel insecure.
** A “real” profile picture is soothing for the user.
** Authenticity doesn't loom large for students personally.

<div style="color:darkgreen">There are lots of "the user wants". It would be easier for outsiders to understand, if you could explain ''why'' the user wants this ('''if''' you know that. Naturally, my request is not asking for inventing explanations! If you only know that users ''want'' but not ''why'' you could make it subject of further research)</div>--[[User:JanD|JanD]] 19:58, 13 December 2013 (CET)

<div style="color:blue">I tried to phrase and explain some points in another way. Is it ok? [M.E.]</div>

'''What specifc problem we want to solve'''

We want to solve some problems with the login-process and make it easier to use.
It's hard and circular to login with one of your accounts, because there are too many steps until you are finally logged in. Moreover the buttons are difficult to find on the interface.
Therefore we want to create a new login-process.

<div style="color:darkgreen">Nice proposal. Are you really talking about the log-in or about setting up a new (Jabber) account? Because in my experience it is not easy to set it up, but once you have your account working and data saved, it behaves very well. But please prove me wrong if that is a singular experience</div>--[[User:JanD|JanD]] 19:58, 13 December 2013 (CET)

<div style="color:blue">We really focus on the sign up process. There is the problem that you don't get an advice to enter the password but it is nessacary. The process is very inconvenient, it needs to many steps till you can start to chat so that we want to create an easier way. [M.E.]</div>

'''Plans – how we want to solve the problem(s)'''

Method 1: Other application's test

First we start to analyse the login process at other applications.
We found out that WhatsApp is the most widespread app to chat for our target group, second one is the Facebook messanger.

1. WhatsApp
This application doesn't contain a login process. You only have to choose the app to be online and you directly see all of your conversations. It is quite easy and intuitive.

2. Facebook Messenger
This application functions nearly the same way as WhatsApp, so you don't need a password to sign in.

Our conclusion:

Both applications manage without a password. That's quite intuitive but it isn't quite save. While doing our interviews we experienced that it would be convenient to have a password to have a safety warranty (e.g. in case of losing the smartphone)

Solution:

We want it as intuitive as WhatsApp and Facebook Messenger but we also want it to be save. So there have to be an additional button for entering a password.

[[File:Prototyp Anmeldeprozess.jpg|600px]]

Our first prototype for the login process.

IFD:Nutzerstudien WiSe1314/Gruppe Anmeldung

2013-12-12T15:15:04Z

Kede7290:

IFD:Nutzerstudien WiSe1314/Gruppe Anmeldung

2013-12-12T14:48:02Z

Kede7290:

IFD:Nutzerstudien WiSe1314/Gruppe Anmeldung

2013-12-12T14:26:43Z

Kede7290:

IFD:Nutzerstudien WiSe1314/Gruppe Anmeldung

2013-12-12T11:12:55Z

Kede7290:

'''Aims of data gathering'''

''Michèle:''

We wanted to know how important security is for students at our age, what they expect from chat apps and what their problems/whishes are. Main focus was also the question of authenticity.
For that reason we started to interview a few people from our social environment.

''Susanne:''

In my interviews I asked about the chat habits and especially focused on how important authenticity is for them and how authenticity is mediated.

''Lisa:''

I talked to two people (Students of Computer Science an Media) and asked them about their daily chat behavior and the aspect of authentication.

'''Data gathering: Interviews/Observation'''

''Michèle:''

Interviews: I interviewed two female students of media sciene, both 19 years old.
I focused on security of chat apps and asked about their attitude towards this topic.
The central questions were:
* How important is security for you while chatting with people?
* What measures do you probably adopt to be safe?
* What functions and design features do you find most important for a chat app?

Observation:

Parallel to that task we examined the app "chat secure" and noticed some problems of handling. We started to think about how we can improve the login because it is too inconvenient.

''Susanne:''

I interviewed 3 girls (students of Media-Arts/Media-Design) in the age of 19.
The main questions were:
* What chat apps/programs do you use?
* How often do you use them and how important they are for you?
* Where do you see advantages and disadvantages of your favorite chat program?
* How important authentication is for you?
* How should a trustable profile be? What information are important?
* In what situations you prefer the phone or an E-Mail before chatting?
* What are requirements for you to use a new app with guaranteed security?

''Lisa:''

First I ask about the chatprogramms my interview partner use in their daily life an what is important for them to use them. Which aspects are important for the design.
Afterward they should specify which chatprogramm they use for one-on-one interviews and which for group discussion.
The next big topic was security. I asked them if they had thought about it. And what they did for their security.
The last topic was how they imagine authentication.

'''Data Analysis & Main Results'''

''Michèle:''

* The user wants to know if the chat partner read the messages.
* The user wants a simple, intuitive, neatly arranged design, which looks uniform on all gadgets.
* It would be useful to have a password for the app.
* The user wants to send out photos/videos.
* The user wants to use a lot of smileys.
* The function "writes..." is not necassary.
* The user wants to use an app/program which is used by a lot of people.
* The app should be for free.
* The user wants to have a security warranty.
* Authenticity doesn't loom large for students personally.
* It is important that apps are immune from viruses.

''Susanne:''

* The user wants an interface, where you can see who is online at the moment and when a contact was online the last time.
* (To much) Personalized advertising makes the user feel insecure.
* A “real” profile picture is soothing for the user.
* If you want a trustworthy profile you have to find a good balance between too much and too little information.
* It’s more comfortably to chat than to phone with somebody.
* For the user it’s important to be up-to-date and flexible with messages. So he/she prefers an app for chatting.
* Because of misunderstandings in chat, some users prefer a phone call for personal discussions.
* Some other users prefer the phone because think the chat-partner reads the message too late.
* Important information, link, photos, videos, … are often sent by E-Mail.
* Distrust towards apps results e.g. from missing knowledge about safety and smart phone-apps.
* People use safety-options of social networks (e.g. Facebook) but don’t know, if they really work.

'''What specifc problem we want to solve'''

''Lisa, Susanne, Michèle:''

[...]

'''Plans – how we want to solve the problem(s)'''

This thursday (12.12.13) we want to speak about what problem we want to solve.

'''[[Images]]'''

[[File:Prototyp Anmeldeprozess.jpg|600px]]

Our first prototype for the login process

IFD:Nutzerstudien WiSe1314/Gruppe Anmeldung

2013-12-12T11:11:06Z

Kede7290:

File:Prototyp Anmeldeprozess.jpg

2013-12-12T10:59:34Z

Kede7290:

== Summary ==

== Copyright status: ==

== Licensing ==
{{self|c}}
== Source: ==

IFD:Nutzerstudien WiSe1314/Gruppe Anmeldung

2013-12-12T10:23:52Z

Kede7290:

'''Aims of data gathering'''

''Michèle:''

We wanted to know how important security is for students at our age, what they expect from chat apps and what their problems/whishes are. Main focus was also the question of authenticity.
For that reason we started to interview a few people from our social environment.

''Susanne:''

In my interviews I asked about the chat habits and especially focused on how important authenticity is for them and how authenticity is mediated.

''Lisa:''

I talked to two people (Students of Computer Science an Media) and asked them about their daily chat behavior and the aspect of authentication.

'''Data gathering: Interviews/Observation'''

''Michèle:''

Interviews: I interviewed two female students of media sciene, both 19 years old.
I focused on security of chat apps and asked about their attitude towards this topic.
The central questions were:
* How important is security for you while chatting with people?
* What measures do you probably adopt to be safe?
* What functions and design features do you find most important for a chat app?

Observation:

Parallel to that task we examined the app "chat secure" and noticed some problems of handling. We started to think about how we can improve the login because it is too inconvenient.

''Susanne:''

I interviewed 3 girls (students of Media-Arts/Media-Design) in the age of 19.
The main questions were:
* What chat apps/programms do you use?
* How often do you use them and how important they are for you?
* Where do you see advantges and disadvantages of your favourite chat programm?

''Lisa:''

First I ask about the chatprogramms my interview partner use in their daily life an what is important for them to use them. Which aspects are important for the design.
Afterward they should specify which chatprogramm they use for one-on-one interviews and which for group discussion.
The next big topic was security. I asked them if they had thought about it. And what they did for their security.
The last topic was how they imagine authentication.

'''Data Analysis & Main Results'''

''Michèle:''

* The user wants to know if the chat partner read the messages.
* The user wants a simple, intuitive, neatly arranged design, which looks uniform on all gadgets.
* It would be useful to have a password for the app.
* The user wants to send out photos/videos.
* The user wants to use a lot of smileys.
* The function "writes..." is not necassary.
* The user wants to use an app/program which is used by a lot of people.
* The app should be for free.
* The user wants to have a security warranty.
* Authenticity doesn't loom large for students personally.
* It is important that apps are immune from viruses.

''Susanne:''

* The user wants an interface, where you can see who is online at the moment and when a contact was online the last time.
* (To much) Personalized advertising makes the user feel insecure.
* A “real” profile picture is soothing for the user.
* If you want a trustworthy profile you have to find a good balance between too much and too little information.
* It’s more comfortably to chat than to phone with somebody.
* For the user it’s important to be up-to-date and flexible with messages. So he/she prefers an app for chatting.
* Because of misunderstandings in chat, some users prefer a phone call for personal discussions.
* Some other users prefer the phone because think the chat-partner reads the message too late.
* Important information, link, photos, videos, … are often sent by E-Mail.
* Distrust towards apps results e.g. from missing knowledge about safety and smart phone-apps.
* People use safety-options of social networks (e.g. Facebook) but don’t know, if they really work.

'''What specifc problem we want to solve'''

''Lisa, Susanne, Michèle:''

das sollten wir noch klären, ob es im Bereich Authentizität ein Problem gibt, bzw. ob das für unsere Zielgruppe überhaupt von Interesse ist...?

'''Plans – how we want to solve the problem(s)'''

This thursday (12.12.13) we want to speak about what problem we want to solve.

IFD:Nutzerstudien WiSe1314/Gruppe Anmeldung

2013-12-11T13:18:48Z

Kede7290:

'''Aims of data gathering'''

'''[[Michèle:]]'''
We wanted to know how important security is for students at our age, what they expect from chat apps and what their problems/whishes are. Main focus was also the question of authenticity.
For that reason we started to interview a few people from our social environment.

'''[[Data gathering: Interviews/Observation]]'''
'''[[Michèle:]]'''
Interviews: I interviewed two female students of media sciene, both 19 years old.
I focused on security of chat apps and asked about their attitude towards this topic.
'''The central questions were:'''
How important is security for you while chatting with people?
What measures do you probably adopt to be safe?
What functions and design features do you find most important for a chat app?
Observation:
Parallel to that task we examined the app "chat secure" and noticed some problems of handling. We started to think about how we can improve the login because it is too inconvenient.

'''[[Data analysis:]]'''
'''[[Lisa, Susanne, Michèle:]] '''
was schreiben wir hier hin? -> Google Drive

'''[[Main Results Data Analysis]]'''
'''[[Michèle:]]'''
I found out that in general security is an important topic for students who chat, but authenticity is not an issue, students at our age think about. They can handle the term, but the function of to authenticating is not useful for them.

'''[[What specifc problem we want to solve]]'''
'''[[Lisa, Susanne, Michèle:]]'''
das sollten wir noch klären, ob es im Bereich Authentizität ein Problem gibt, bzw. ob das für unsere Zielgruppe überhaupt von Interesse ist...?

'''[[Plans – how we want to solve the problem(s)]]'''
'''[[Michèle:]]'''
Next week we want to speak about what problem we want to solve
'''[[Images:]]'''

IFD:Nutzerstudien WiSe1314/Gruppe Anmeldung

2013-12-11T13:11:15Z

Kede7290:

'''Aims of data gathering'''

'''[[Michèle:]]'''
We wanted to know how important security is for students at our age, what they expect from chat apps and what their problems/whishes are. Main focus was also the question of authenticity.
For that reason we started to interview a few people from our social environment.

'''[[Data gathering: Interviews/Observation]]'''
'''[[Michèle:]]'''
I interviewed two female students of media sciene, both 19 years old.
I focused on security of chat apps and asked about their attitude towards this topic.
'''The central questions were:'''
How important is security for you while chatting with people?
What measures do you probably adopt to be safe?
What functions and design features do you find most important for a chat app?

'''[[Data analysis:]]'''
'''[[Lisa, Susanne, Michèle:]] '''
was schreiben wir hier hin? -> Google Drive

'''[[Main Results Data Analysis]]'''
'''[[Michèle:]]'''
I found out that in general security is an important topic for students who chat, but authenticity is not an issue, students at our age think about. They can handle the term, but the function of to authenticating is not useful for them.

'''[[What specifc problem we want to solve]]'''
'''[[Lisa, Susanne, Michèle:]]'''
das sollten wir noch klären, ob es im Bereich Authentizität ein Problem gibt, bzw. ob das für unsere Zielgruppe überhaupt von Interesse ist...?

'''[[Plans – how we want to solve the problem(s)]]'''
'''[[Images:]]'''