Team Project

There are two basic options for this project; designing a new tool or doing a research-oriented policy report. If you have an idea for a team project that doesn't seem to fit either, please see me.

Teams should be 4-5 students. All teams need to submit a document which identifies the roll and responsibilities of each student in the team, and how they met those responsibilities.

All teams will give a 15-20 minute PowerPoint presentation about their project. For the tools, you will need to show what it will allow users to do, how it will allow them to do these things, and why your design makes sense. For the policy report, you will present your topic and its main issues, and focus on the key points of your policy proposal.




Designing a New Tool

In this assignment option you will work in teams of 4-5. Each team will have clearly-stated design goals. The following are some examples, but other options can be proposed.

  • Digital Camera of the Future: This camera will not just take pictures, but also be able to perform things such as automatic (and error-free) settings adjustments, post processing operations, and direct online publishing and archiving. What exact tasks should it support - that's one of the things you need to determine. In the end, you need to have a 3D paper and cardboard prototype, along with a user's manual.
  • Digital Editing Tool of the Future: This is a software challenge. Current tools tend to have multitudes of features and options which make use difficult. At the same time, many are missing the tools that people really want. You need to find out what people really wish they could do, and then prepare paper prototypes of the interface, and storyboards showing how your software would be used to meet those desires.
  • Photo Collections of the Future: This may be software, or a combination of software and hardware that people can use with their current digital cameras and available technology. You need to discover how people want to build collections and search collections and then prepare prototypes showing how your system will look and how it will be used both by people creating collections as well as those who are searching through collections (not necessarily collections they built).



For each team, the objective will be to:

  • Identify who the target users will be. You need to identify populations who are not currently happy with what is currently available.
  • Determine what tasks this user base will want to accomplish. You need to encourage your participants to think "big" - detailed task scenarios can help push the boundaries of current technologies.
  • Create low-fidelity prototypes to flesh out ideas. Do not limit yourself based on costs or current technologies - this is a paper prototype where the goal is to say what we should have.
  • Submit a written report / design portfolio to the Vice President of Development at your company detailing your work and results. This report/portfolio will contain things such as:
    • a list describing expected users of the system and their work contexts
    • a list of actual, representative tasks that people are expected to do
    • a prioritized list of system requirements
    • a low fidelity prototype
    • a task-centered walkthrough of the prototype

Some goals of this exercise are that you will gain experience in:

  • articulating good task descriptions
  • using task scenario descriptions to decide upon system requirements
  • brainstorming low fidelity prototypes based on the above
  • evaluating various design ideas and prototypes through task-centered walk-throughs




    Research-oriented Policy Report

    In this assignment option you will work in teams of 4-5. Each team will have a clearly-stated topic and will need to research the background and existing information on the topic, perform some type of original research (probably in the form of interviews), and write a report that provides an overview of the topic as well as The following are examples, but other proposals are welcomed.
    • License Plate Scanning Police are scanning license plates to do things such as determine whether to give parking tickets or locate stolen vehicles. How else is this information beign used? For how long is it being kept? What are the potential consequences of this technology and what policies should be put in place which would be consistent with existing laws regarding things such as search or privacy?
    • Cameraphone Usage Many cellphones have cameras built into them. What policies and laws exist regarding where these phones may and may not be taken or used to take photos. What new policies might be needed to address the prevalence of these devices?


    For each team, the objective will be to:

    • Identify the populations who are effected by the current technology and policies.
    • Determine what tasks are being performed using the technology and what new uses might be on the horizon or risk being on the horizon (you should think "big" and think about how the boundaries of current technologies and their uses might be pushed).
    • Create a policy statement that defines both acceptable uses as well as limits of use of the technology in the domain.
    • Submit a written report to a local politician or policy maker detailing your research and policy recommendations. This report will contain things such as:
      • a list describing how the technology is currently being used
      • a list of possible ways it could be used in the future
      • any worst-case scenarios of unintended uses
      • an overall policy statement designed to make sure the technology is only used as it was intended to or even make recommendations against the current uses

    Some goals of this exercise are that you will gain experience in:

  • identifying uses of technology that impact society
  • considering the ways technologies can be misused
  • talking to citizens about the use of technology
  • talking to officials regarding the use of technology
  • writing and supporting policy proposals




    Submitting

  • Send me your PowerPoint presentation at egolubUMD@gmail.com by December 5th at 8:00pm.
  • Be prepared to bring your reports and low fidelity prototypes to class on December 6th. Presentation schedule TBA.

    If you have any questions - please see me in office hours, or send me e-mail at egolubUMD@gmail.com












  • Web Accessibility