Thesis Design Document
Spring 2002
Introduction
Ever had a stranger leave a group of friends and approach you with a camera? "Could your take our picture?"
I find this interaction interesting because it could not have happened before the advent of consumer photography equipment. It is an interaction that is a result of this technology entering our culture. (Self-timers help, but you need someplace to put the camera and the framing is a crap shoot.) What is the future of this interaction as cameras become even less expensive and more common?
In order to get in the picture we summon the courage to ask a stranger to take our photo and then hand them a (potentially expensive) piece of equipment containing some number of irreplaceable photographs. We put our trust in them and they usually comply.
But what if the camera itself was passed on to the person taking the photo? How would they react? How would the camera need to change in order to convey this new interaction?
The goal of my thesis is to create an edition of cameras which will travel from person to person until the camera runs out of film. The last person will drop the camera in the mail and I will have the film developed and make the photographs available on-line. These participants can then contribute a story about where they were when the photo was taken and what they thought of the experience.
Details
This is a living document and a work in progress. It will evolve as the project evolves.
Last Update: 05/01/02
Table of Contents
Design Document
Project Constraints
Functional Requirements
Non-Functional Requirements
User Scenario
Project Planning
View the Thesis Journal
Visit the Thesis show poster
In order to keep the project on track and keep the idea as clear as possible I'll be applying a design process that is loosely based on information architecture and software development processes. Not sure how it will work out with a project like this, but hey that's why I'm in graduate school.
Project Constraints - restrictions and limitations
that apply to the project.
The purpose of the project
To modify an otherwise familiar interaction such that the participants see it in a new way. To create an interaction based on a familiar situation that allows further interaction and perhaps makes the interaction more memorable or creative as a result.
Who is the audience, who are the users?
The cameras will be distributed to tourists who are assembled to have their picture taken in a public space. I will ask people who appear to be tourists to take my picture then I will give them the camera. At that point I have to rely on the participants to see it through.
Tourists have spare time to participate in such events and my distribute the camera to another location. They will most likely have access to the web and e-mail and will enjoy the opportunity to participate.
Who will see the results?
The participants and other visitors to the web site. Potentially I may have a show or produce a book depending on how the project progresses.
Requirements constraints
The project will be limited by the number of disposable cameras and cost of processing the film and the cost of postage. I have access to a film scanner and will scan the negatives myself. I do not plan on making prints in this first phase. If Kodak or another vendor of disposable cameras is willing to contribute then I can expand the scope of the project.
I also have access to an ISP who I believe will be willing to host the site during it's initial phase.
Assumptions
I assume that I will be able to create a package that will encourage people to return the cameras in a reasonable amount of time. It is difficult to predict how many cameras will be returned and in what condition. This will be tested in the prototype phase.
I am assuming that a majority of the participants will follow the instructions and return the cameras.
Prototype phase will be limited to 20 disposable cameras with flash.
All instructions and website will be in English.
Camera instructions will request that cameras stay in the United States.
The look and feel
Still thinking about this one. I will probably take a cue from the existing aesthetics in place at tourist locations and airports.
Usability
Cameras need to be common cameras, cards need to be durable and recognizable as part of the project and match the website. The participants should be able to find their photos with a minimum of confusion.
Performance
Cameras and modifications should be reliable and not interfere with the task of taking the photos.
The web site should be up 24/7 and provide quick access to compressed jpg images over a 56K connection.
Operations
The modified cameras should be able to withstand the usual treatment of a disposable camera. Camera should be easily distinguishable from other cameras the user may have.
Legal
Participants should be informed that their photos will be on the website and that by participating they agree to release their likeness according to the terms of the project. (Hmmm, I should run this past a lawyer.)
Project Issues
Open Issues as of 03/15/02
Contact Kodak
Buy first 10 cameras on EBay
Also see Prototype Phase/TimelineTasks
Risks
No cameras are returned
Photos are unusable for some reason
People refuse to participate
Participants lose/destroy cameras
Participant does not understand directions
Camera is damaged in shipping/lost in mail
Postage is invalid for some reason
Participant does not agree to release photograph rights
Participants may be impatient or be angry when the camera is not returned and they don't get to see their photograph. (Yeah, me too!)Costs
Initial cameras and processing
- Cameras $3-$4 each
Domain registration
User is visiting a popular tourist location and is asked to take the photo of another tourist who perhaps explains the project at this time.
User takes photo and keeps camera.
User approaches next person and the cycle continues until the last shot is reached.
User who takes last shot "unwraps" the camera in to a SASE(Self Addressed Stamped Envelope) and drops it in to a mailbox.
Project Plan/Timeline
Write instructions
- Brief description of the project
- Please use the camera and pass it on within 24 hours.
- Please keep the camera in the United States
Create first shot board (return instructions for lab)First build of website
- Register domain
- Set up e-mail accounts
- Register with search engines
- Create 1.0 site in EnglishBuy 10 cameras to test with
Modify cameras
- change form of camera to include cards
- shoot first shot, leave progressively less shots on each camera.
- Cameras 1,2 - 24 shots
- Cameras 3,4 - 15 shots
- Cameras 4,5 - 10 shots
- Cameras 6,7 - 8 shots
- Cameras 7,8 - 5 shots
- Cameras 9,10 - 3 shots
Assuming I get them all back I'll have approximately 130 photos. I hope to get 1/3 back in two weeks. This will also help to determine how many shots should be on each camera. More shots = more time causing participants to lose interest and more risk that the camera will disappear.
Provide SASE with Domestic Priority Postage
Ask Kodak and Fuji for camera/processing contributions
Visit the Empire State Building in New York and Fisherman's Wharf in San Francisco on a weekend and distribute cameras to English speaking tourists.
Once these steps are complete I will enter phase one. (April 1st)
Translate instructions in several languages with the help of other ITP students
Create 2.0 multilingual website for launch at end of Phase One.Obtain a large set of cameras
Provide SASE with International Priority Postage
Distribute cameras to cities in all seven continents
- Using ITP students as distributors I have at least 5 continents covered.
Opportunities for further development
(time permitting)
Digital cameras with GPS and wireless networking
A new camera released from the same location every day
Use a self sustaining solar wireless web camera which would record information for the life of the camera.
This design document is based on the one described in the book, "Mastering the Requirements Process" by Suzanne Robertson and James Robertson.