Normally each layer of a Product is tested against more and more detailed requirements and behaviors. But all in all, like shown above it’s always a new black box vs. interpreted Requirements, that are taken from above.
But this introduces risks, as these Layers may get lost in details and loose track of beeing focused on problem to be solved.
Or detailed requirements interpreted wrong.
All in all, just increasing requirements on left side and independently testing layers on right side will fail, and if it’s just because of the sheer amount of requirements that will quickly become non maintainable and not matching with the product.
Also solution side will become verry static and even the slightest change will need to adjust lots of Tests if testing is done from top to bottom.
Continue reading “Test Embedded Systems”