Evaluating a solution
User requirements should form the criteria for a structured evaluation. Focus on the extent to which the user requirements were met (fully, partially, not met) would form the basis of a reflective evaluation.
| Question | Agree | Neither agree or disagree | Disagree |
| Did the product/website contain the information that you wanted? | ✔ | ||
| Were navigation tools provided through menus and icons readily available? | ✔ | ||
| Was it easy it to share or print or save items in the product/site? | ✔ | ||
| Video and sound added value to the product? | ✔ |
| Question | Did the product/website contain the information that you wanted? |
|---|---|
| Agree | |
| Neither agree or disagree | |
| Disagree | ✔ |
| Question | Were navigation tools provided through menus and icons readily available? |
|---|---|
| Agree | |
| Neither agree or disagree | ✔ |
| Disagree |
| Question | Was it easy it to share or print or save items in the product/site? |
|---|---|
| Agree | ✔ |
| Neither agree or disagree | |
| Disagree |
| Question | Video and sound added value to the product? |
|---|---|
| Agree | ✔ |
| Neither agree or disagree | |
| Disagree |
Your software solutions should be evaluated in terms of performance. Performance includes:
Functionality
Does the database/website perform the functions required? For example, searching for data, placing an order, posting a blog or viewing a video.
Ease of use
How easy is the website to use? Is there built-in help? Is the user interface intuitive?
Robustness
How does the website handle problems? Robust software works well with different hardware and software without crashing.
