Applied Computing

Step 1. User Data (this step may not be applicable for all groups)

As part defining your Solution Requirements, you may have a particular person or group of people who may be a potential end-user of your solution.

To help establish what the needs of this potential end user/s, you may apply techniques (such as interviews and surveys) to collect data from these from them to help define your Solution Requirements.

The data you collect should then be used to help inform and guide the definition of functional and non-functional requirements for your solution.

Who to survey / interview?

• Any potential user for your innovative solution

• If your solution is meeting a problem / need, it should be someone who that problem / need applies to

• If your solution is meeting an identified opportunity, it should be someone who may be a potential user

You may choose which platform you wish to conduct your survey / interview.

• Ensure you obtain informed consent from your survey / interview participants

• Ensure you meet the privacy guidelines by de-identifying the survey / interview responses when submitted as part of your project.

Categories of non-functional requirements

Solution Requirements 

Determine the solution requirements, you should think about the following:

• What the solution must do

• What the solution might dothese are features that you might implement - if there is enough time and funds (if applicable) during development

• What the solution will not dothese are the features that you will not implement - they are outside the scope of your project or affected by constraints such as time or budget