Please enable JavaScript.
Coggle requires JavaScript to display documents.
Evaluation (Efficient use of coding constructs (code is efficient if…
Evaluation
Fitness for Purpose
-
functional requirement and original purpose can be checked against the software to ensure it is fit for purpose
-
if software is not fir for purpose, previous stages may have to be revisited to find a solution and fix the problem
-
Usability
what is it?
-
Learnability - is the layout clear and consistent, can the user easily pick up how to use the interface
Memorability - hoe easy is it to start using the software again after a long period of time. does the user have to re-learn everything from before?
Efficiency - can the user carry out a task in as little steps as possible. are there unnecessary navigation links that could all be on one page? shortcut keys can be a way to improve efficiency
Error reporting/handling - easy access to help and tutorials should be available and any errors caused by the user should result in clear advice on how to fix the problem and proceed
Customisability - being able to customise the interface to suit the user. some users may need additional support due to disabilities such as text-to-speech. there will also be a range of experience in users (professional/ beginners)
Maintainability
how to improve it
using white space, clear comments, meaningful identifiers and indentation helps to make code more readable
-
what is it?
if a piece of software is maintainable, another programmer should be able to take it over easily, with no problem understanding it or working it
Robustness
-
when writing input validation, clear error messages should be included so that user can understand what they need to do to fix the problem
when using data within a range, programmers should alwasy test exceptional and extreme data as sometimes programs that are not robust may accept data just outside the bounderies