Mail Notifier

mailbanner

Physical Prototyping and Computing: HCDE 498

University of Washington

June 2014 – August 2014

This project was a quarter long project for HCDE 498 course. It was an individual prototyping project using the Arduino program and system. I created a computer that would signal a light when it sensed mail was placed inside the mailbox. I programed the system and assembled the hardware. I created additional pieces that were added by designing 3D models digitally and printing them with the MakerBot.

Check out my thoughts on this project’s process here at: http://jkumura.wordpress.com/

 

The Process

Week One & Two:

In week one and two of the quarter, we focused on learning on how to code and hard wire programs for the Arduino. To help familiarize ourselves with this type of prototyping, we were assigned to assemble and code a pre-existing model of a bike-computer, which calculated the speed of the bike, the current temperature, and time. Here are a few images of the hardware below. These first couple weeks also involved brainstorming for final project ideas, which was very difficult for me.

photo 1   photo 2   photo

 

Week Three:

After brainstorming, we submitted an initial project proposal and plan. This posed many problems for me because I was still unaware what my capabilities I had working with the Arduino. Additionally, being that this was the first time I did any physical prototyping, I was restricted by my limited knowledge of the different sensors and potential the Arduino has. I resorted in an idea, which solved a current and trivial issues I had with my apartment’s mailbox.

See this week’s deliverable here:       Project Proposal

 

Week Four – Eight:

This whole time was working on building our prototype. The weekly progress of the project during this period can be found in the blog link listed above.

 

Week Nine:

In the final week of the course, we wrapped up course, and I finished my prototype. We had a public showing of our prototypes during the last class where we were able to explain and present our creations.

Here is my final project report:     Final Report

And a video of it in action!

Comfort through Convenience

BusBanner

Foundations of Interaction Design: DESIGN 383

University of Washington

July 2014 – August 2014

This design project was a half of quarter long where the task was to create design solutions to the Seattle bus system.

We assembled into a group of three. We researched using observations, surveys, and interviews. From this research, our key findings from our research themed our project goal in our design process, which was to provide comfort to bus riders by creating convenient solutions. The design process continued with steps including: quick ideation and sketching, grouping and expanding of ideas,  storyboarding, wireframing, early designing., and presenting. The project was created in Adobe InDesign and Illustrator. (Note: this was this first experience our group members ever had in these platforms) My role was mostly designing. I created presentation template/layout in InDesign and the wireframes/ early designs in Illustrator.

PDF version of the presentation of project’s process is linked here.

Calendar Project

CalendarBanner

Foundations to Interactive Design: DESIGN 383

University of Washington

June 2014

This week long project involved me getting familiar with using Illustrator and InDesign for the first time. We brought a few images to class of calendar applications that we like. Our task from that class on was to create a new type of calendar that makes us visualize events in a different way. There were two iterations of this project.

The design process was broken down into steps: Inspiration/ Web Researching → Ideation →  Sketching → Digital Designing→  Critiques  →  Digital Designing Take 2 → Presenting

My first iteration can be viewed here – Calendar Project Design 1

My second iteration can be viewed here – Calendar Project Design 2

Project Management

PMBanner

Project Management: HCDE 303

University of Washington

April 2014 – June 2014

During this course in Spring Quarter, I had paired up with a partner where we went through a project management stimulation.

While I was the project manager in the stimulation, I created schedules using an Agile approach to prepare for whatever unexpected scenarios would come my way. The schedule expanded the course of 4 weeks, and I provided a day each week for a buffer incase anything went wrong, or if the team fell behind schedule, or to use as testing. Back-up plans and additional tasks were included in the schedule to prepare for the team being either ahead or behind schedule. The professor provided surprise scenarios along the process, which required constant updating and reorganizing of the schedule to still meet the end goal.

Tight communication was of great importance with the team, the instructor, and the audience. I exhibited great communication with my partner who represented the development team lead with frequent exchanges of messages via email and documents on a Google Drive. Weekly progress reports were also submitted to the instructor, which was a good way on reflecting on the process and putting it into written form. The project entailed two presentations: one to kick-off the project and another as a wrap-up and reflection, which involved engagement of my peers as an audience.

 

Documents of the Process

Initial Phase

 

First Phase

  • Given Scenario:

    The last project your company did was to create some financial reports for a local company. Unfortunately, that company got a visit from the IRS to have their books audited. When the IRS found out about your company’s work, they called up and said to freeze all the code (i.e. stop working on every project your company is currently involved in or else face criminal charges) until they can come in and review it. While your company didn’t do anything wrong, it took 3 days for your company’s accountants and lawyers to sort it all out and you could get back to work. Net project effect, each person on your dev team lost 3 days of project work.”

  • Task Schedule 2

 

Second Phase

 

Final Phase

  • Given Scenario:

    “This morning, you were met by the police when you showed up to the office. You saw your whole dev team standing outside under the watchful eye of several Sheriff’s deputies. The only thing that the police officer would say is that you’re not allowed inside until the detective arrives and you need to wait with your team. After what seems like an eternity, a plainclothes detective arrives and asks which one of you put the “inappropriate” pictures on the FabricLand website? You look at each other and shrug. It wasn’t anyone on your team. Apparently, the local police got a call from the authorities in England, who received a complaint from Mildred Maywether. Mildred claims she nearly died of a heart attack when she saw some “unspeakably pornographic” images on the FabricLand website. The British authorities called the web hosting company to take down the site, and then called the local police to confiscate your servers and laptops as evidence and for forensic analysis. What do you do?”

  • 2-Minute Wrap Up Presentation
  • Final Reflection

 

 

 

User Research

URBanner

Introduction to User Research: HCDE 313

University of Washington

January 2014 – March 2014

This course was all about learning to research the users before creating any solutions. The core research techniques learned were field observation, interviews, and surveys. These techniques were practiced in a sequence; each step’s results building off of the previous. I have done the first two portions individually, but teamed up with three other individuals for the surveying portion. However, all these steps lead up to an individual research report.

Documents

Field Observation – Field Observation Assignment

Interviews – Interview Assignment

Surveys – Group Survey Assignment

Final Report – Final Report

Twitter Word Cloud

Twitter Banner

Interactive Systems Design & Technology: HCDE 310

University of Washington

November 2013 – December 2013

Created an application that runs on Eclipse, using python which takes the Twitter’s main timeline API and prompts the user, using their own Twitter data, to create word clouds of the tweets containing the searched term.

 

Screen Shot 2014-02-16 at 9.53.19 PM