The Architecture-driven test development method uses different architectural viewpoints for system models: Requirements describe the required system functionality. In the logical view the system functional blocks are described without any information on actual physical or technical realization aspects. In the technical view the system architecture is described by its technical realization blocks. Technical aspects such as, for example, the collocation of different logical functions on the same hardware or the combined use of the same communication channel are modeled at this level. In the topological view, the locations for hardware installation, or wiring etc. will be modeled in the system architecture.

Initially ADT has been defined in the context of an automotive case study while using the PREEvision software. This developed test derivation method is useful to identify e.g. so-called PER-based tests, which consider sets of preconditions (P), events (E), and reactions (R). Basic PER validation tests are derived from the requirements available in the functional view of the system. Further tests can be derived due the inclusion of the other system layer information.

A set of algorithms to derive tests based on the system architecture has been defined in the case study. Examples of these algorithms have been implemented using the model query facilities and report writing facilities available in PREEVision to derive the test descriptions. The implementation allows different output formats, following either tool specific script the standardized test language TTCN-3.

http://www.fokus.fraunhofer.de/en/motion/projekte/laufende_projekte/D-MINT/ADT.html