Here is a good general outline for your proposal document:
- Introduction and background.
- Brief summary of your
project: what problem does it solve, who will use it?
- Features.
- This is where you get into the nitty-gritty of
what your app will do. Be specific here. What pages will
there be? How will users interact with your app? In
addition, think about what your app won't do. What would
you implement if you had time? What features are out of
scope?
- Technology stack.
- How will you implement
the features you talked about in the previous sections?
What languages/libraries/frameworks will you use? Will you
use any third-party APIs? What tools will you use to
collaborate with your team members? How and why did you
decide to use these technologies?
- Timeline.
- ?Who will
focus on what parts of you project? When will you
implement features? How will you collaborate and
communicate outside of classes?
The goal of the proposal is mainly for you and your team
members to have clear vision of what you'll be working on for the rest
of the quarter and how you'll create it.
1–2 pages is a reasonable length.
See the USENIX templates in Resources
for written reports and oral presentations for
good formats.