User Tools

Site Tools



This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
courses:2013_exp_prototyping_week38 [2013/09/12 01:43]
courses:2013_exp_prototyping_week38 [2013/09/17 04:47] (current)
Line 1: Line 1:
 +====Week 38: Improvisation Interfaces====
 +//​with:​[[http://​​web/​dqi-group/​bart-hengeveld/​|Bart Hengeveld]] and [[http://​​about/​|Mathias Funk]]//\\
 +Coming from the traditional craft of Designing for Appearance, we are currently moving through Designing for Interaction towards Designing for Systems. This means that we are not longer only designing from a one user-one technology paradigm but more and more from a multiple users-multiple technologies paradigm. Designing for this new situation is easier said than done. A profound difficulty is that we seemingly cannot simply transfer our ‘designing for interaction methods and tools’ to this new paradigm. This has several reasons. Firstly, the systems we are designing are essentially too large and our targeted user-groups too heterogeneous to simply choose an approach (e.g., bottom-up or top-down) and start designing. Moreover, as designing for systems is relatively uncharted territory, we even don’t know if these existing approaches apply or if we need an alternative hybrid approach. Secondly, the interaction with systems appears to be different than with interactive standalone products as systems are more focused on facilitating opportunities for behaviour rather than on disclosing functionalities.
 +To explore how we can design for systems this project proposes to learn lessons from fields with a longer tradition in facilitating behaviour and personalisation. One such field is that of improvised music. For example, in jazz music the rendition of a composition—which is in essence a musical design—is highly dependant on the size of the performing band, the people in the band bringing their individual musical backgrounds,​ heroes, styles, fortes and flaws, and even on the type of gig or venue. Nonetheless,​ as a system a jazz band functions really well; the whole is genuinely more than the sum of the parts.
 +Transferring this phenomenon to designing for systems, we may ask: can we design for such a setting, in which people can express themselves while being part of a self-directing,​ co-creating,​ musical organism? Or better: can we even go further? Can we design interactive musical instruments that are specifically aimed at ‘the whole’ rather than ‘the sum of the parts’? In other words, intelligent musical instruments that allow the musician control over someone else’s instrument or even the entire group?
 +This is what we will explore throughout the week.
 +====Week Overview====
 +10:00 - 12:00: Introductions,​ lectures.\\
 +13:00 - 17:30: First design exploration.\\
 +9:00 - 12:00: Technology morning.\\
 +13:00 - 17:30: Second design exploration:​ direction.
 +9:00 - 12:00: Design work and prototyping (part 1)
 +//keep afternoon free//\\
 +9:00 - 17:30: Design work and prototyping (part 2)
 +9:00 - 12:00: Final presentations & demonstrations. Jam session.
 +  * //​workspaces cleanup//\\
 +  * //​presentation//​\\
 +  * //​reflections and feedback//​\\
 +====Links and materials provided by teachers and students====
 +Code for the examples of Tuesday morning:
 +(these two archives contain Processing sketches)
 +[[https://​​u/​286741/​UMU/​|OOCSI Server]]
 +(this is the OOCSI server you can use to test your Processing sketches locally on your computer)
 +If you need help with these examples, ask Mathias.
 +You might want to read [[http://​​iasdr2013/​papers/​1161-3b.pdf|one of our papers]].
 +====Results of the week====
 +In the week you will get hands-on experience in the upcoming paradigm of systems design in industrial design, through various lectures and activities, resulting in a group music improvisation system.\\
courses/2013_exp_prototyping_week38.txt · Last modified: 2013/09/17 04:47 by funk