IFD:Nutzerstudien WiSe1314/Sicherheit endpresentation (security) - Revision history

AnjaR: /* The interviews */

2014-03-19T22:16:22Z

The interviews

← Older revision		Revision as of 22:16, 19 March 2014
Line 133:		Line 133:

	<span style="color:#ee9966">Did he have specific concerns about the third party, or was he saying that that part of the app's interface was confusing?</span>		<span style="color:#ee9966">Did he have specific concerns about the third party, or was he saying that that part of the app's interface was confusing?</span>

			'''EDIT''': It's just circuitous to register on a third party. It had nothing to do with the interface.

Nioerd: /* Choosing Ideas and creating prototype */

2014-03-19T22:09:51Z

Choosing Ideas and creating prototype

← Older revision		Revision as of 22:09, 19 March 2014
Line 176:		Line 176:

	<span style="color:#598193">Warum habt ihr dieses Thema ("informing the user what is going on, if…") gewählt? Nutzerforschung? Vortest? Heuristik?</span>		<span style="color:#598193">Warum habt ihr dieses Thema ("informing the user what is going on, if…") gewählt? Nutzerforschung? Vortest? Heuristik?</span>
	<br>'''EDIT''': To improve our prototype, we did a heuristic analysis to search for specific problems in the chat. This analysis is divided in ten subitems. We had been going through them all and found some problems which we wanted to take care of. For time reasons though, we couldn’t involve them all.		<br>'''EDIT''': To improve our prototype, we did a [http://www.uni-weimar.de/medien/wiki/IFD:Nutzerstudien_WiSe1314/HeuristicAnalysisSecurity heuristic analysis] to search for specific problems in the chat. This analysis is divided in ten subitems. We had been going through them all and found some problems which we wanted to take care of. For time reasons though, we couldn’t involve them all.

	===Prototype 1===		===Prototype 1===

AnjaR: /* What we learned / conclusions: */

2014-03-19T22:04:14Z

What we learned / conclusions:

@@ Line 292: / Line 292: @@
 From our research, we got a lot of information about the requirements and the possible use of a chat application. The most important features people wanted to be part of such an application where group chat functionality, image transfer, smileys and an easy to use but appealing interface. People often want to plan parties in a chat, so the group function could be necessary and image transfer is also an important factor of communication for our interviewed students.
-For our prototypes, we concentrated to improve the interface. As shown in the prototypes before, we:
+For our prototypes, we concentrated to improve the interface. Here is a graphical summary of our proposals.
-[[File:pro.jpg | 900px]]
+[[File:Zusammenfassung prototyp.jpg | 900px]]

Xicu1652: /* The interviews */

2014-03-19T15:51:03Z

The interviews

← Older revision		Revision as of 15:51, 19 March 2014
Line 124:		Line 124:

	<span style="color:#ee9966">It would also be useful to find out how much she extra is willing to work to understand an app if it provides security.</span>		<span style="color:#ee9966">It would also be useful to find out how much she extra is willing to work to understand an app if it provides security.</span>


			'''EDIT''': I even asked both, 1 and 3, that question! Both didn't have any ideas, so I asked them if it would be okay to be asked a question in the app that she and her partner have set up before. It was an effort, both agreed it wouldn't bother them and they would use such a chat.

Xicu1652: /* Ideas */

2014-03-19T15:43:38Z

Ideas

← Older revision		Revision as of 15:43, 19 March 2014
Line 21:		Line 21:

	<span style="color:#ee9966">I like that you started with very quick and raw sketches! I think its important to generate lots of ideas in the beginning, so doing rough sketches is important. I would like to see more sketches with all sorts of ideas from small makeovers to radical new ideas. Its also possible to do quick user tests with very rough sketches.</span>		<span style="color:#ee9966">I like that you started with very quick and raw sketches! I think its important to generate lots of ideas in the beginning, so doing rough sketches is important. I would like to see more sketches with all sorts of ideas from small makeovers to radical new ideas. Its also possible to do quick user tests with very rough sketches.</span>
			'''EDIT''': Sorry, but we didn't make more sketches that time.

	==How we prepared for interviews / our questions==		==How we prepared for interviews / our questions==

Xicu1652: /* What we learned / conclusions: */

2014-03-16T15:21:11Z

What we learned / conclusions:

← Older revision		Revision as of 15:21, 16 March 2014
Line 294:		Line 294:
	[[File:pro.jpg \| 900px]]		[[File:pro.jpg \| 900px]]

	*b) inform the user, if the message is insecure, through an exclamation mark		*b) inform the user, if the message is insecure, through an exclamation mark and a slide-system
	and a slide-system

	[[File:nust_security_prototype.png \| 600px ]]		[[File:nust_security_prototype.png \| 600px ]]

Xicu1652: /* What we learned / conclusions: */

2014-03-16T15:19:42Z

What we learned / conclusions:

← Older revision		Revision as of 15:19, 16 March 2014
Line 290:		Line 290:
	From our research, we got a lot of information about the requirements and the possible use of a chat application. The most important features people wanted to be part of such an application where group chat functionality, image transfer, smileys and an easy to use but appealing interface. People often want to plan parties in a chat, so the group function could be necessary and image transfer is also an important factor of communication for our interviewed students.		From our research, we got a lot of information about the requirements and the possible use of a chat application. The most important features people wanted to be part of such an application where group chat functionality, image transfer, smileys and an easy to use but appealing interface. People often want to plan parties in a chat, so the group function could be necessary and image transfer is also an important factor of communication for our interviewed students.
	For our prototypes, we concentrated to improve the interface. As shown in the prototypes before, we:		For our prototypes, we concentrated to improve the interface. As shown in the prototypes before, we:
	*~~in prototype~~ a) added colors to button and bar		*a) added colors to button and bar
	*in b) inform the user, if the message is insecure, through an exclamation mark and a slide-system
	*in c) inform the user, if the message is insecure, through a pop-up		[[File:pro.jpg \| 900px]]
	*in d) changed the words "OTR" to "secure messaging", because users don't know what OTR meant and added a pop-up to inform the user what to do after sending a message fails three times in a row
	*in e) added the functions that secure messaging starts automatically.		*b) inform the user, if the message is insecure, through an exclamation mark
			and a slide-system

			[[File:nust_security_prototype.png \| 600px ]]

			*c) inform the user, if the message is insecure, through a pop-up

			[[File:impro2.jpg \| 300px]] [[File:pro2a.jpg \| 300px]]

			*d) changed the words "OTR" to "secure messaging", because users don't know what OTR meant and added a pop-up to inform the user what to do after sending a message fails three times in a row

			[[File:pro2b1.jpg \| 900px]]

			*e) added the functions that secure messaging starts automatically.

			[[File:prototyp_schalter.png \| 300px]][[File:nust_security_prototype_automatic.png \| 400px]]

Xicu1652: /* Aims of design */

2014-03-16T15:02:06Z

Aims of design

← Older revision		Revision as of 15:02, 16 March 2014
Line 5:		Line 5:

	<span style="color:#ee9966">Phrasing your goals as questions is a good way to guide the process. These are both quite valuable and relevant questions. I'm unclear who '''I''' is in the first question, the designer or the user.</span>		<span style="color:#ee9966">Phrasing your goals as questions is a good way to guide the process. These are both quite valuable and relevant questions. I'm unclear who '''I''' is in the first question, the designer or the user.</span>
			'''EDIT''': Thank you. I and We are the designer.

	==Ideas==		==Ideas==

Hans at 20:15, 14 March 2014

2014-03-14T20:15:01Z

← Older revision		Revision as of 20:15, 14 March 2014
Line 235:		Line 235:

	We tested it and our testperson went through it without problems.		We tested it and our testperson went through it without problems.

			<span style="color:#ee9966">This is a good balance of familiar interface experience and quick to use regularly. Its not as flashy as the swipe, but seems like it would not get too annoying if you saw it regularly.</span>


	===Prototype 2e)===		===Prototype 2e)===
Line 244:		Line 247:

	[[File:nust_security_prototype_automatic.png \| 400px]]		[[File:nust_security_prototype_automatic.png \| 400px]]


			<span style="color:#ee9966">You are right, starting the secure session is too complicated. The on/off switch would be a nice representation, but because of technical constraints, I don't think it would be workable. We tried it and it was confusing people. The problem is the on/off widget cannot represent anything but on or off, and it takes a while for the OTR session to start. So that leaves the on/off switch in a confusing state while OTR is starting. OTR is neither on nor off. We still don't have a great answer for this problem, but it seems that a button with an icon that changes is the best bet. Then we can represent multiple states.</span>

			<span style="color:#ee9966">Starting OTR automatically all the time would also make things easier, but that also has technical limitations. OTR works by sending text messages, and if someone is using a program that does not include OTR, they'll see those odd OTR messages. Its not a huge problem, but it does freak some people out.</span>



	==Presentation==		==Presentation==
Line 252:		Line 262:
	My topic had been ''security and usability of passwords''. It was really interesting to inform myself about that. The gap between easy understanding (usability) and security of password-protected websites was one theme. In my presentantion I explained that system builder to think out of the perspective of the user. <br>		My topic had been ''security and usability of passwords''. It was really interesting to inform myself about that. The gap between easy understanding (usability) and security of password-protected websites was one theme. In my presentantion I explained that system builder to think out of the perspective of the user. <br>
	However, what I liked the most in my research had been the studies about what passwords other people choose and how they choose them. I was quite surprised about how easy people's passwords can be encrypted and that hacker go social ways more than mathematical ones to crack them.		However, what I liked the most in my research had been the studies about what passwords other people choose and how they choose them. I was quite surprised about how easy people's passwords can be encrypted and that hacker go social ways more than mathematical ones to crack them.

			<span style="color:#ee9966">Its always surprising, but still, "social engineering" is still the main way people break into computer systems. Edward Snowden used a lot of social engineering techniques to get access to many of the documents that he leaked.</span>


	'''Student 2:'''		'''Student 2:'''

	My presentation was about prototyping. It was interesting, how many types of prototypes are existing. There are many ways to test new ideas. You have to choose, which type of prototyp is the best for your product.		My presentation was about prototyping. It was interesting, how many types of prototypes are existing. There are many ways to test new ideas. You have to choose, which type of prototyp is the best for your product.

			<span style="color:#ee9966">I find that rapid prototyping is essential to the process of making good user experiences. For most people, the design process works best when there are many iterations on the idea, so making more iterations as fast as possible means more ideas get explored.</span>


	'''Student 3:'''		'''Student 3:'''

	My talk was about designing interfaces for secure or security based systems. The main statement of these paper was, that the most of the classical rules of design does not meet the requirements of such an interface. The authors based their thesis upon user tests with the e-mail encryption tool pgp. It was also interesting to read how a test should be organised and which aspects of the test subjects should be kept in mind. All in all it was a very interesting topic for me and i could recommend this paper to everyone.		My talk was about designing interfaces for secure or security based systems. The main statement of these paper was, that the most of the classical rules of design does not meet the requirements of such an interface. The authors based their thesis upon user tests with the e-mail encryption tool pgp. It was also interesting to read how a test should be organised and which aspects of the test subjects should be kept in mind. All in all it was a very interesting topic for me and i could recommend this paper to everyone.

			<span style="color:#ee9966">Representing technical limitations to the user in a simple way will always be challenging. User testing has demonstrated itself to be a great method for finding out how well ideas and designs map to real experience.</span>


	==What we learned / conclusions:==		==What we learned / conclusions:==
Line 265:		Line 284:

	<span style="color:#598193">Ich habe mich sehr gefreut, eure Dokumentation zu lesen. Leider endet sie etwas abrupt. Es würde bei mir als Leser und vermutlich auch unseren Mentoren einen sehr guten letzten Eindruck hinterlassen, wenn hier noch eine Zusammenfassung der wichtigsten Erkenntnisse und Vorschläge zu lesen wäre; Sinnigerweise mit einer Übersicht in Bild- oder Grafikform (siehe Mail) </span>		<span style="color:#598193">Ich habe mich sehr gefreut, eure Dokumentation zu lesen. Leider endet sie etwas abrupt. Es würde bei mir als Leser und vermutlich auch unseren Mentoren einen sehr guten letzten Eindruck hinterlassen, wenn hier noch eine Zusammenfassung der wichtigsten Erkenntnisse und Vorschläge zu lesen wäre; Sinnigerweise mit einer Übersicht in Bild- oder Grafikform (siehe Mail) </span>

			<span style="color:#ee9966">I also want to see more. I think you had a lot of good design ideas, but there was not a lot of information outside that to back up the designs.</span>


Line 270:		Line 291:
	For our prototypes, we concentrated to improve the interface. As shown in the prototypes before, we:		For our prototypes, we concentrated to improve the interface. As shown in the prototypes before, we:
	*in prototype a) added colors to button and bar		*in prototype a) added colors to button and bar
	*in b) inform the user, if the message is ~~unsecure~~, through an exclamation mark and a slide-system		*in b) inform the user, if the message is insecure, through an exclamation mark and a slide-system
	*in c) inform the user, if the message is ~~unsecure~~, through a pop-up		*in c) inform the user, if the message is insecure, through a pop-up
	*in d) changed the words "OTR" to "secure messaging", because users don't know what OTR meant and added a pop-up to inform the user what to do after sending a message fails three times in a row		*in d) changed the words "OTR" to "secure messaging", because users don't know what OTR meant and added a pop-up to inform the user what to do after sending a message fails three times in a row
	*in e) added the functions that secure messaging starts automatically.		*in e) added the functions that secure messaging starts automatically.

Hans at 19:56, 14 March 2014

2014-03-14T19:56:16Z

← Older revision		Revision as of 19:56, 14 March 2014
Line 20:		Line 20:
	[[File:NuStu_prototyping.jpg \| 300px]] [[File:ideas.jpg \| 300px]]		[[File:NuStu_prototyping.jpg \| 300px]] [[File:ideas.jpg \| 300px]]

	<span style="color:#ee9966">I like that you started with very quick and raw sketches! I think its important to generate lots of ideas in the beginning, so doing rough sketches is important. I would like to see more sketches with all sorts of ideas from small makeovers to radical new ideas.</span>		<span style="color:#ee9966">I like that you started with very quick and raw sketches! I think its important to generate lots of ideas in the beginning, so doing rough sketches is important. I would like to see more sketches with all sorts of ideas from small makeovers to radical new ideas. Its also possible to do quick user tests with very rough sketches.</span>


Line 195:		Line 195:
	To make the user keep an eye on the current security level, we added colour to the send button. This means the button has the same colour as the bar with the names of the contacts.		To make the user keep an eye on the current security level, we added colour to the send button. This means the button has the same colour as the bar with the names of the contacts.

	'''EDIT''': So you know by clicking on the send button, whether the state is unsafe(red), safe(yellow) or safe and verified(green). You can also see the current status in the little lock above. But some test person told us, they ~~dont~~ look above by each sending of a message.		'''EDIT''': So you know by clicking on the send button, whether the state is unsafe(red), safe(yellow) or safe and verified(green). You can also see the current status in the little lock above. But some test person told us, they don't look above by each sending of a message.

	[[File:pro.jpg \| 900px]]		[[File:pro.jpg \| 900px]]

			<span style="color:#ee9966">Providing feedback where the user actually looks when working is key. Its not always easy to tell that in advance, that's where user testing comes in. So you got come valuable information in your test here. One idea related to the coloring to consider: the app is called ChatSecure, so people expect secure messaging. That expectation can be represented in the app, so when the messages are secure, the app looks like a "normal" Android messaging app. Then use the color to represent when things are not secure. That could make the non-secure states stand out more.</span>


	===Protoype 2b)===		===Protoype 2b)===
	A next question was how we could show that the message is not ~~encryped~~. This also included the problem how one could start encryption.		A next question was how we could show that the message is not encrypted. This also included the problem how one could start encryption.
	<span style="color:#598193">Warum habt ihr dieses Thema ("informing the user what is going on, if…") gewählt? Nutzerforschung? Vortest? Heuristik? Logische begründung, denn… (eure Erklärung)</span>		<span style="color:#598193">Warum habt ihr dieses Thema ("informing the user what is going on, if…") gewählt? Nutzerforschung? Vortest? Heuristik? Logische begründung, denn… (eure Erklärung)</span>

Line 210:		Line 213:

	We discussed this idea in the group and decided that this would not be easy to understand. So we gave up this idea.		We discussed this idea in the group and decided that this would not be easy to understand. So we gave up this idea.

			<span style="color:#ee9966">This would be a very valuable thing to have for people using ChatSecure in high risk situations, where it is important that they don't mistakenly send messages insecurely. An example is a journalist under surveillance from the state. But for many people, it would just annoy them. I wouldn't discard this idea so quickly, I think it could be made workable. And it would work a lot better than a popup once the user learns it.</span>


	===Protoype 2c)===		===Protoype 2c)===
	We added a pop up, which appears when the user tries to start an ~~unsecure~~ chat or to remind the user to verify himself and/or his contact person.		We added a pop up, which appears when the user tries to start an insecure chat or to remind the user to verify himself and/or his contact person.

	'''EDIT:''' The user have to choose, whether he will send the message unsafe or try a safe sending on another time. He also has the opportunity to save his response for all time. This can be changed in the settings.		'''EDIT:''' The user have to choose, whether he will send the message unsafe or try a safe sending on another time. He also has the opportunity to save his response for all time. This can be changed in the settings.