Your project proposal should be two to three pages of hardcopy, turned in at the start of class. If your proposal is more than a page, you must staple the pages together. It is sort of amazing to me that I need to make this requirement explicit, but I've gotten a lot of loose papers turned in.
You may work by yourself for the project, or you may have a partner. However, the maximum group size is two.
Please clearly explain the following. You can cut and paste these questions with your responses, if you want.
- Give your app a title.
- List contact email(s).
- What sort of app are you building? What will be the major
subsystems? What will be the major challenges?
- Sketch the major user interface elements (i.e., actually draw
them and include the drawing in your proposal. Focus on elements
that are likely to be difficult.
- Include a week-by-week schedule.
- List the APIs you will be using.
- Include a short functional specification for a deliverable that
you will demo to the TA. The date your demo is due is listed on the
course syllabus as a the project deliverable. The purpose of the
deliverable is to help us ensure that you are on the right track.
- Include a short discussion of other apps that have similar
features and the sources of inspiration for your design.
- Remember that we are looking at two things. First is the
technical breadth of your app, what APIs does it use, how complex
is it, how functional, how well tested. The second is the usability
of your app. Can we reinitialize the app without quitting? Can you
demo all of the functionality easily? In general, usability is less
technically demanding, so it is a good idea to polish it, regardless
of the technical scope of your app.
You will do a final explanation and demo for the instructor, TA, and
possibly fellow students
toward the end of the semester. That will also be posted on the