A proposal is a formal document that outlines a plan or idea for a project or initiative to solve a problem or offer an opportunity. They are also known a design brief.
In the real-world you would normally either be the person the proposal is for (stakeholder), or the person who carries it out (contractor). For your project, you'll be both!
For this project you are just creating a simple proposal. However, it's really important to make sure that you really think about each section when writing - what you create here sets you up for your whole Design AND Development work...
This section explains why you are developing your proposed digital outcome. You wrote this at the start.
Now you have completed your research and understand your users better, you should be able to be more specific and add more detail.
A typical purpose at Y12/13 would be 4 to 6 sentences.
Check out the "Understand" page again to remind yourself about the Purpose.
Before starting this section, watch the video above to make sure you have a good understanding of requirements and specifications.
Requirements are the important features or considerations that your project needs to include. In other words what it needs to do or be.
They are broad statements, no more than 6 to 8.
You decide on these by using your end user, conventions, and implications research.
You could start each requirement using IT MUST
This section provides detailed lists of how you plan to meet the requirements. They work as a really good checklist for your designs.
They should:
List the specific features you plan to use to achieve this requirement
They should be clear, concise, and measurable
You could start each specification with IT WILL
IMPORTANT: You may not yet know what the specifications for your project are - that is what the Design phase that comes next is all about.
At the end of each part of the design phase you will need to revisit your specifications and update them.