Test strategy derivation must always be performed but literature on the subject is minimal
at best, other than a traditional discussion of the merits of top-down versus bottom- up
with regards to integration. In the increasing complex systems found in today’s
businesses, both off- line and on the web, an efficient and effective test strategy must be a
goal that is reached for a system to be comprehensively and accurately tested. Simply
“banging on the box” or “flailing at the machine” will not do the job.
This paper will define what a test strategy is and what it must cover. It will review the
necessary sources and foundations for a test strategy, i.e. system requirement
specifications and system architecture documents, and discuss how the test strategy can
possibly be obtained in tandem with them. The paper will cover the critical dependencies
of a test strategy and explore the leverage points that may be found among them. In
particular the integration strategy and build documentation will be analyzed for their
relationship to a successful test strategy. Test documentation will be then be reviewed to
show where and how this information is best noted and preserved.