Notes regarding the project proposal

The proposal describes the project's context, goals, deliverables and schedule. It has two main goals:

• Provide a characterization of the project motivation and outcomes to an external reader, namely the teaching staff.
• Serve as a first plan for the project scheduling and development.

The project proposal should include:

• A description of the project's context, with enough detail for a reader to understand the project motivation.
• The project's goals and deliverables
  • It should describe the deliverables format (e.g. software library available as a Nuget package or a Maven package, deployed web application, mobile application available on an app store).
• The project's detailed functionality
  • Divided into mandatory and optional functionality
  • If the project includes a user interface, then the use of user stories is recommended.
• A sketch for the project components/architecture (e.g. mobile application, application server, database) without too much emphasis on the chosen technologies.
• A description of related work or products.
• A weekly plan for the 20 weeks, including the relevant milestones: proposal, progress report, intermediate presentations, beta version and final version.
• An identification of the project's challenges and risks.
• The project logistics requirements (e.g. software and hardware requirements, access to external systems and APIs).