...
- The current tracks allow for rolling stock to travel at up to 160mph
- The maximum rolling stack length is 12 x 23.9m
- The maximum tonnage of the tracks predefined by the rail standards authority
- The tracks, clips and bolts are of a specific tensile strength
- The switching circuitry operates at the specific capacity
Target state for tracks
- The current tracks allow for rolling stock to travel at up to 220mph
- Rolling stock will tilt at high speed through bends
- The maximum rolling stack length is 12 x 23.9m
- The maximum tonnage of the tracks predefined by the rail standards authority
- The tracks, clips and bolts are of a specific tensile strength to cope with the higher speed rolling stock
- The switching circuitry operates at the specific capacity
In order to ensure that the new rolling stock can transit across the new tracks each element must be verified as being able to carry the rolling stock at the new desired speed. In other words each element (component) making up the track system must be separately unit tested to verify their individual quality. Once the components have been assembled into a complete track system, a series of integration/system level tests must be executed to verify that the rolling stock can actually get to their destinations within a specified set of requirements. So from a software perspective unit level testing using tools like JUnit verifies the quality of the components in a system, and tools like fitnesse verify that the system is built according my requirements, in other words you have built what I asked for (more of an end to end testing strategy).