As part of the exercise, students will:
You are to imagine a scenario that could exist in 10 years time. This should include a vision for an ecosystem of interacting connected products.
Students will work in collaborative groups and asked to prepare the following:
A vision: a conceptual introduction to how they envision the future ecosystem working and the kinds of connected solutions that will enhance the quality of experience for it’s end users. This should be realized as a short 2-3 minute video.
Working prototypes: prepare at three working prototypes from their vision. Each prototype will be demo’ed during the final class.
Presentation of outcomes: Present their design scenario and prototypes in a 5 minute final presentation
Demo Session: Provide a live-demonstration of the ecosystem working and the connected experience you have designed.
Process documentation: Maintain a record and illustrate their work process, rationale and design decisions.
Outcome documentation: Prepare written documentation of the solution (goal, vision, design process, prototyped solutions, viability of the solutions, next steps, reflection on success, etc.)
Process and Milestones There are three major steps to this assignment. Each of them is explored in separate documents.
Familiarize - get to know the domain we’re designing for in a rapid research exploration across users, precedents and objects.
Defamiliarize - find unusual approaches to explore this familiar design space, brainstorm possible connected scenarios, and propose a visionary scenario.
Visionary Proposal - develop a statement of intent for your future focused scenario and a lightweight description of your connected ecosystem
Prototype and Present - implement a working prototype, fast! implement connections between those prototypes, faster!
The team is expected to self organized. However, it is highly recommended to coordinate as follows:
Reuse This isn’t a race to the finish. This is a collaborative exploration.
Feel free to Share, reuse, revisit past projects as needed.
You are welcome to use the code, ideas, outcomes from any previous project even if it is not your own; but you must acknowledge it.
Final Documentation: Final documentation should be added to the relevant pool on the Gallery. It is recommended that you create one project for each prototype developed, as well as, one project which explains the overall vision and links to each of the prototype’s documentation.
You should provide a clear and concise description of your project, your process, and the outcomes. It should be quick to get an overview of the project. Ideally, your description of the outcomes should be repeatable too i.e. anyone in the class can replicate it easily from the information provided.
Using Online Material: It is perfectly fine to use examples, code, tutorials, and things you find on the web to help you realize your project. That’s part of the open-source mentality that surrounds much of Making, Arduino and microcontrollers. However, you cannot just copy and paste these solutions. In your documentation you must acknowledge where you got this content from. Include a link to any tutorials, guides, or code that are part of your final solution.