50000 lines of code to brew a coffee

We are used to agile software development. The tools and methods to thrive towards continuous delivery are mature. We can spin up environments in minutes, test our software automatically and deploy to production with a single click.

Connected devices bring a new layer of complexity to a project.

Hardware prototypes evolve in much longer cycles than the software. Automated testing becomes a challenge when user flows spread across multiple devices and involve human interaction. Environments for continuous integration suddenly move back from the cloud to real devices on our desks.

This talk is about the lessons learned from a real life project that builds a system around a connected consumer device. The goal is to highlight some of the challenges and our approaches to tackle them. There are patterns evolving that are a good guidance for other projects.

Transcript

1. 50 000 LINES OF CODE FOR A CUP OF COFFEE Philip Peter | Jan Riehn @jriehn 1
2. 50 000 LINES OF CODE TO BREW A COFFEE 2
3. 50 000 LINES OF CODE TO BREW A COFFEE 3 010101010011001110010101010110 011001101101010101100110011100 110101010111001110011101001100 111001101010101100110011100110 101010110011001110011010101011 001100111001101010101100110011 100110101010110011001110011101 010101010100110011100110101010 011001110011010101011001100111 101010101100110011100110101010 110011001110011010101011001100 111001101010101100110011100110 101010110011001110011010101011 001100110011010101011001100111 001101010101000
4. 50 000 LINES OF CODE TO BREW A COFFEE 4 New? New? New!
5. PROJECT OVERVIEW 5
6. PROJECT OVERVIEW 6
7. PROJECT OVERVIEW 7
8. PROJECT OVERVIEW 8 PRODUCT SYSTEM CONNECTED PRODUCT SMART PRODUCT PRODUCT
9. PROJECT OVERVIEW 9 BACKEND, WEBSITE, SHOP IOS, ANDROID, WATCH APP FIRMWARE MACHINE
10. PROJECT OVERVIEW 10 backend app machine
11. PROJECT OVERVIEW 11 backend app no machine
12. PROTOTYPING 12
13. PROTOTYPES 13 DUMMIES low fi hi fi clickable WALKING SKELETON Hello World! ALPHA core functions BETA real users RELEASE live!
14. PROTOTYPES 14 DUMMIES
15. PROTOTYPES 15 FAKE SERVICE
16. PROTOTYPES 16 FAKE MACHINE
17. PROTOTYPES 17 THE BOX
18. PROTOTYPES 18 FUNCTIONAL PROTOTYPE
19. PROTOTYPES 19 DUMMIES WALKING SKELETON ALPHA BETA RELEASE DUMMIES FAKE SERVICE FAKE MACHINE THE BOX FUNCTIONAL PROTOTYPE
20. PROTOTYPES 20 DUMMIES WALKING SKELETON ALPHA BETA RELEASE DUMMIES FAKE SERVICE FAKE MACHINE THE BOX FUNCTIONAL PROTOTYPE minutes hours weeks months
21. PROTOTYPES 21 DUMMIES WALKING SKELETON ALPHA BETA RELEASE DUMMIES FAKE SERVICE FAKE MACHINE THE BOX FUNCTIONAL PROTOTYPE FAKE SOFTWARE REAL SOFTWARE FAKE HARDWARE REAL HARDWARE
22. PROTOTYPES 22 DUMMIES WALKING SKELETON ALPHA BETA RELEASE DUMMIES FAKE SERVICE FAKE MACHINE THE BOX FUNCTIONAL PROTOTYPE define interfaces and data structures implement and test features
23. TESTING 23
24. TESTING 24
25. TESTING 25
26. TESTING 26 Problem 1: How do you test the integration with something that doesn’t exist?
27. TESTING 27 CONTRACT TEST FAKE CONTRACT TEST FAKE CONTRACT TEST
28. TESTING 28 Problem 2: How do you fake physical user interaction?
29. TESTING 29 TESTS
30. TESTING 30 user fake real
31. TESTING 31 user fake real
32. TESTING 32 automated testing guided manual testing user fake real
33. TESTING 33 Problem 3: Setting up scenarios for end-to-end tests
34. FAKE TESTING 34
35. TESTING 35 CONTRACT TESTS FAKE / GUIDED USER INTERACTION PARTIAL USER JOURNEYS
36. CONNECTIVITY 36
37. CONNECTIVITY AND USER FLOWS 37 CONNECTED DEVICES
38. CONNECTIVITY AND USER FLOWS 38 USER FLOWS ACROSS DEVICES 1 2 3 4 5 6 7
39. CONNECTIVITY AND USER FLOWS 39 STAND ALONE COFFEE MAKER
40. CONNECTIVITY AND USER FLOWS 40 PHONE AS REMOTE CONTROL
41. CONNECTIVITY AND USER FLOWS 41 CONNECTED PRODUCT SYSTEM
42. CONNECTIVITY AND USER FLOWS 42 EVERYTHING IS OFFLINE
43. SECURITY 43
44. SECURITY 44 … what if somebody … Do you know that you can …
45. SECURITY 45 http://www.microsoft.com/en-us/sdl/adopt/eop.aspx
46. SECURITY 46 scenario I: you break your own machine oh…
47. SECURITY 47 scenario II: you break somebody else’s machine oh… haha!
48. SECURITY 48 scenario III: you break ALL machines it doesn’t stop! haha! what happened?! I want coffee! oh…
49. SECURITY 49
50. MAKE TECHNOLOGY INVISIBLE 50
51. MAKE TECHNOLOGY INVISIBLE IOT = CONNECTED DEVICES CONNECTION IS KEY CONNECTION - I DON'T CARE
52. MAKE TECHNOLOGY INVISIBLE 52
53. MAKE TECHNOLOGY INVISIBLE 53
54. MAKE TECHNOLOGY INVISIBLE 54
55. MAKE TECHNOLOGY INVISIBLE 55
56. MAKE TECHNOLOGY INVISIBLE 56
57. MAKE TECHNOLOGY INVISIBLE 57
58. MAKE TECHNOLOGY INVISIBLE 58
59. WRAP UP 59 Build prototypes and fake hardware Test everything works smoothly together Get this stupid thing connected Avoid security disasters Try to hide technology from user 0 50 000
60. WRAP UP 60 time spent on … user facing features “the rest”
61. LESSONS LEARNED 61 resources matter, hardware is hard to change software has to be build around it 5 offline + complex user flows analyse more than you used to 4 don’t reinvent the wheel when getting things connected 3 automate more than you first think is possible 2 co-locate with the hardware people 1
62. WRAP UP 62 ?
63. THANK YOU! Philip Peter | Jan Riehn @jriehn 63