P2: Project Proposal

P2: Project Proposal #

Deadline: Jan 31, 11:59pm Eastern Time

The proposal document should be a PDF document. Formatting requirements: page limit 4–6 pages (excluding acknowledgements and references); letter size; main text font size 11pt.

The document should include the following sections:

Introduction #

Introduce your project topic. Focus on answering the following questions:

  • What is your project?
  • Why is it interesting?
  • Why does this project make sense in a mobile form?

You can include figures (mockups / screenshots / hand drawings) to help describe your app.

Not sure what app to build? Take a look at the project videos from previous years to get some inspirations.

Project Requirements #

  • Define the functional requirements of your project. Use numbered points (e.g., 1, 1.1, 1.2, 1.2.1, etc.) to organize your requirements.
    • A typical app-level software system would have 5–10 functional requirements.
    • You can mark some functional requirements as “stretch goals” if you think they may be too ambitious; we will take into those into consideration when grading.
  • Describe at least 2 non-functional requirements that your app needs to support. Justify why these requirements are important for your app.
    • You can include more than 2 non-functional requirements, but only the first 2 will be considered when grading this report.
  • The list of requirements will be compared against what you actually implement in the project to determine the completeness scaling factor.
    • It is possible to revise the requirements during the project development, e.g., based on the prototypes and feedback from the course staff or peers. Those changes should be clearly documented (e.g., as a change log) and negotiated with the TA during the iteration demos.

Use Cases and Human Values #

  • Draw a use case diagram to illustrate how users interact with your app.
  • Provide at least 2 user scenarios to describe how a user would interact with your app and what the benefit to them would be.
    • For each user scenario, describe: a statement of the purpose of the scenario, the individual user/transaction being followed, assumptions about equipment/software, and the steps of the scenario.
    • You can refer back to your numbered functional/non-functional requirements and the use case diagram.
    • You can include more than 2 user scenarios, but only the first 2 will be considered when grading this report.
  • Describe at least 1 human value(s) that is addressed in your app (e.g., by certain design of some features, or explicitly excluding certain features).
    • You can include more than 1 human value, but only the first 1 will be considered when grading this report.

How to Submit #

Submit the PDF report on Learn. Your file should be named as p2-XX.pdf where XX is your team number.

Feedback #

We will provide feedback on your proposal via written comments on Learn, hopefully by Feb 07 (one week after submission). In addition to comments and suggestions, we will also provide an estimation of the utility and difficulty scaling factors based on what you claimed in the proposal.