Limitations are aspects of the solution either not done or done poorly.
‘Limitation’ means slightly different things at different points in the process. In Analysis (AO 2.2), limitation refers to features and functionality intentionally discounted. They may be discounted because they are less important than other features or because there isn’t sufficient evidence to justify their inclusion.
In Evaluation (AO 3.3), limitation retains the above meaning and expands to include issues with the coded solution. Such issues may include:
- poor performance;
- poor robustness;
- unintended behaviour (i.e., bugs);
- features that were previously excluded but, in hindsight, are necessary; and
- features that seemed a good idea at the time but are in some way unsatisfactory.