You are on page 1of 1

Naresh Chauhan Software Testing, 2e

Low Level design (LLD) Verification Checklist

Y/N/NA(Y=Yes, Remarks/Comments
S.NO. Criteria N=No, NA=Not
Applicable)
1. Is HLD traceable to LLD?
2. Is high level and low level abstraction
consistent?
3. Is every sub-system detailed enough to be
operational?
4. Does pseudo-code of every sub-system
follow the guidelines and syntax rules of a
Program design language (PDL)?
5. Does algorithm of every sub-system
consistent with its defined functionality?
6. Does design notation for LLD support the
development of modular software?
7. Does the design notation for LLD support
the means for interface specification?
8. Is design notation able to represent local and
global data?
9. Is design notation able to modify the design
representation easily?
10. Is the logic in each algorithm clear, correct
and complete?
11. Has all the data been properly defined and
initialized?
12. Is all data defined used somewhere?
13. Is every detail of data available?
14. Is data used consistently throughout the
module and module interface?
15. Are any variables missing?
16. Have all interfaces been correctly considered
and implemented in LLD?
17. Does sub-system accept all data within the
allowable range?
18. Is Data converted according to correct
Format?
19. Has consideration given to the effects of
round-off or truncation?
20. Are all indices valid in the sub-system
pesudocode?
21. Is there any infinite loop in the sub-system
pesudocode?
22. Does design address arithmetic overflow and
underflow?
23. Physical data models of database if any
written clearly?

© Oxford University Press 2016. All rights reserved.

You might also like