A possible solution would be to generate test cases from implementation modules, which are more similar to the actual code.
Features correspond to selectable concepts of the system at different abstraction level: functional and non-functional requirements, environment and context restrictions, runtime components, implementation modules, etc.
Generate test cases from B implementation modules: since B implementations represent more closely the tested code, the ability to also generate test cases from them would reduce the abstraction gap and make the process of refinement of the test cases easier.
For simplicity of illustration, only the nearest-neighbor inhibitory connections are shown; in the computational implementation, each module inhibits all the subordinate modules in the hierarchy (e.g., 2 inhibits 3, 4, and 5).
In software, detailed design is the implementation of module internals, design of data structures and algorithms, and coding in a programming language.
Curricular modules were designed in the 2007 2008 academic year, and implementation of modules 1 and 2 began in Fall 2008.
It should also be kept in mind that the interveners that are involved in the practical implementation of modules may induce effects that are beyond the ones originally intended by the module's concept.
Hierarchical internetworks are more scalable because they allow growing internetwork in a gradual way with the implementation of modules.
However, the use of software such as ArcGIS (a complete, cloud based mapping platform) can automate these tasks easily through the implementation as modules, to obtain the features as the building footprint, height and shape.
