Static Testing - Software Testing: Testing Across the Entire Software Development Life Cycle - page 94

an investment of millions of dollars because the end users could not fi gure out how to
properly operate the software to do their routine business. Human nature being what
it is, the recipients of poor documentation and training do not say, “I will fi gure out
how to operate this software”; rather, they say, “this software doesn't do what I need
it to do, so I want the old system back.”

6.3 CANDIDATE DOCUMENTS FOR STATIC
TESTING

It is time to take a look at a reasonably representative list of software development
document candidates for static testing.

1. Software development manager's documents

(a) Software requirements
(b) Software project plans
Software developers' documents
(a) Use cases
(b) Software designs
(c) Software specifi cations
(d) Data fl ow diagrams
(e) Database and fi le designs
(f) Online operating environment specifi cations
(g) Batch operating environment specifi cations
(h) Interfaces
(i) Connectivity (network) specifi cations
(j) Security specifi cations
(k) Screen/window/page specifi cations
(l) Report specifi cations
(m) Code
Test er s' do cu ment at ion
(a) Test plans
(b) Test cases
(c) Test environment specifi cations
(d) Test data sources and preparation
(e) Test tool installation and operation
Administrator's documentation
(a) Installation guides
(b) Operation/administration guides
End users' documentation
(a) Users guides
(b) Help screens
(c) Training manuals

2.

3.

4.

5.