Group Project Proposal

Draft Due: Tuesday, February 19th before class.
Due: Friday, February, 22nd at 11:59PM

Assignment Overview

Your assignment is to extend and refine the existing one paragraph “elevator pitch” for your project into a longer, more comprehensive three to four page project proposal (images, figures, and tables are free and do not contribute to the page count). The appendix (required) and reference list (also required) do not contribute to the page count either. You will work on this assignment with your project team.

A Brief Timeline

On Thursday, February 14th, we will conduct in-class brainstorms. Specifically, we will break out into our teams and brainstorm/iterate on the original project pitches with a particular focus on who are the target users, how can interactive technology play a role in solving our proposed problem, and what particular aspects are you, as a team, going to solve this semester.

On Tuesday, February 19th, you must bring a draft (five print-outs) of your proposal into class. This proposal should be about ~75-80% completed to get full value out of our in-class exercises that day. You will exchange your draft with another team and receive feedback. Matt and I will go around and provide feedback as well. You must also post your draft to your team wiki before class begins.

On Friday, February 22nd, you will submit a final draft by posting it to your team wiki.

Project Proposal Sections

A successful project proposal will have, at the very least, the following seven labeled sections. Please email me or post to Piazza if there are questions or concerns about these sections.

Section 1: Title and Abstract

The title can be an updated form of the title from the “elevator pitch” and the abstract will simply be a refined version of your “elevator pitch.” Note, however, that the abstract must be no longer than six sentences. Roughly, your abstract should contain a motivating sentence about the problem and why it’s important, a sentence on past solutions along with their limitations, a sentence on your proposed solution and how it is unique from past approaches, a sentence on how you plan to evaluate the effectiveness of your proposed solution, and a sentence on who this will benefit and why. Your abstract must address each of the aforementioned points.

Section 2: Introduction

The introduction should clearly articulate the problem and why it is important. It should also include specific high-level goals for the project (i.e., what does a “win” look like for this project and what metrics are you going to use to know that you got there). You should be sure to describe how your proposed solution is novel or, at the very least, how it may extend existing solutions. The introduction should be two to three paragraphs.

Section 3: Background / Review of Past Work

This section should provide a background context on the problem (e.g., its history) as well as a review of past work. I expect at least eight specific references to either related commercial products or research papers. When relevant, you should include a figure of the related application, tool, product, or webpage with a numbered figure caption below. When referring to past work it’s important to include a description of the past work, why it’s relevant and significant to the proposal at hand, and how your proposed solution is different.

When citing past work, use the same numerical referencing paradigm that was introduced for the “Individual Project Brainstorming Assignment.” That is, each reference is assigned a unique number and referenced like this [id]. At the end of the proposal, the last section will be a “References” list that maps the unique id to the reference. See the example in the last assignment.

Note: If you are having trouble with this, post a question to Piazza or email me or Matt. It’s absolutely essential that you understand the current solutions within your problem space so that you (1) don’t reinvent the wheel; (2) can fully differentiate your solution; (3) can extend and build upon good ideas from past work and avoid the bad ideas from past work.

Section 4: Target Users

In this section, you should describe at least one group of target users, their needs, and why your proposed solution benefits them. A quality write-up will include a discussion of both target users and secondary users of the system. In fact, most, if not all, of the project proposals have more than one user group. Don’t believe me? Think about the IDEO shopping cart redesign. You may think that “shoppers” are the only users of the carts, but we know better. Shoppers may be the primary users—perhaps the most important users—but others include the employees who must clean and collect the carts from the parking lot, the mechanics who must fix the carts, and even the homeless who might want to use the cart for their own reasons. All of these user groups (with the exception of the last group) must be able to effectively use the cart or the cart design fails. Even further, the primary user group—shoppers—can be further categorized into subgroups: power shoppers, shoppers with children, shoppers with disabilities, shoppers in a hurry, very tall shoppers, etc.

Section 5: Scenario Walkthrough

Here the proposal should walk through a specific scenario where the application or service is used. It should highlight the problem that you are trying to solve, how the problem would currently be addressed, and how your application addresses the problem. Be sure to highlight the key features of your application or service. Feel free to include rough sketches here to help portray your point (these sketches are not required—if you do include them, treat them like a normal figure with a figure caption).

Section 6: References

A list of references formatted according to the ACM Style guide (link), Chicago Manual of Style guide (link), or the APA Style guide (link).

Section 7: Appendix

The appendix is a copy of the original elevator pitch (in its unmodified form) followed by a brief paragraph describing how the proposal has evolved since its initial composition.

Additional Requirements

You must include several visual elements that complement your submission; again, these elements will not count towards your total page count. Images, graphs, and tables should all be featured with captions that explain them. Remember to cite any sources used in your references. Please email me or post to Piazza if there are questions or concerns about this requirement.

Grading

You will be graded on how well you execute on each of the above seven sections. You will be additionally graded on creativity and writing quality across the entire proposal. Please follow the directions carefully. In the past, I've had students completely miss sections in their report. Finally, I will be factoring in peer review to help assess the quality of the work and the output from each team member. This proposal is worth 5% of your overall grade in the class.

Specifically, we will be using the following point tabulations:
  • 10 points | Section 1: Title and Abstract
  • 10 points | Section 2: Introduction
  • 15 points | Section 3: Background / Review of Past Work
  • 10 points | Section 4: Target Users
  • 10 points | Section 5: Scenario Walkthrough
  • 10 points | Section 6: References
  • 05 points | Section 7: Appendix
  • --------------------------------------------------------------------
  • 70 points

Here is an example from last term that received a good grade: SafePath. I expect everyone in the class to either meet or surpass this quality. There are certainly many things that could be improved even with this write-up.

Submission

You will not be emailing this submission. Instead, post it directly on the CMSC434 class wiki. Each team must make a wiki for their project. You will use this to post deliverables the rest of the semester. See Project Teams.

Common Mistakes

  • Including figures but without captions: Each figure should have a caption that looks like: "Figure X: <caption text>" where X is the figure number.
  • Not referencing figures in prose: Each figure must be referenced in your prose. If you have difficulty figuring out how to refer to the figure in your text, it's likely that the figure is tangential/irrelevant and can be removed.