At first glance it might appear that volume testing should be fairly high up
on the V model, especially if we take the above definition. Certainly it comes
under non-functional requirements testing and Performance testing.
Volume testing can (and should) be used in component testing. This would be
closely correlated with the code, so might at this level be connected to Dynamic
Analysis.
Volume testing will also be undertaken (normally) as part of the User
Acceptance test. Stress testing is closely related, as it seeks to find out how
the software will behave beyond its specified limits.
