Purpose and Requirements

What's your why?

Purpose

This section explains why you are developing your proposed digital outcome. You wrote this in the design stage. 

Now you have completed your research and understand your users better, you should be able to be more specific and add more detail. 

Check out the "Understand" page to remind yourself about the purpose...

Who's It For?

You are developing this outcome for other people, known as your users or end users. So who will your outcome be for and why? 

Is it for you? Your peers? Your school? Your community? Your whaanau? 

Spend time thinking how they will benefit from what you are proposing. 

Requirements and Specifications

These are short, specific statements that are measurable — you should be able to tick them off. What does your digital technologies outcome need to have, be, or do in order to achieve its purpose?

Before starting this section, watch the video below to make sure you have a good understanding of requirements and specifications.

Requirements

Requirements are the important features or considerations that your project needs to include. 

• They are broad statements, no more than 6 to 8.

• You decide on these by using your end user, conventions, and components research. 

• You should start each requirement using IT MUST

• If you can't picture how you could actually make it, it's not a good requirement!!

Specifications

These provides detailed lists of how you plan to meet each requirement. It's breaking your requirements up into bite size chunks. 

They should:

• List the specific features you plan to use to achieve this requirement

• They should be clear, concise, and measurable

• Start each specification with IT WILL

• Use bullet points

Here are some examples to help you: