A Formal Approach to Network/Distributed Systems Complex Testing

Abstract

Abstract-Deployment of network/distributed systems sets high requirements for procedures, tools and approaches for the complex testing of these systems. This work provides a survey of testing activities with regard to these systems based on standards and actual practices for both software-based and distribution (network) aspects. On the basis of this survey, we determine formal testing procedures/processes which cover these aspects, but which are not contrary to both aspects. The next step, based on the analysis of the implementation phase of System Development Life Cycle, determines a formal model for these processes.

A Formal Model of Distributed Systems For Test Generation Missions

“…-System architecture layer (configuration details see [16] [22]. The requirements-coverage strategy application to the model covers:…”

“…The static analysis determined the characteristics of each layer based on the layer structure (or topology). It covers [22]:  individual components;  every interaction from the end-user requirements on functional, system, logical and physical architectural layers. The dynamic analysis (or fault injection simulation) provides a means for understanding how distributed systems behave in the presence of faults.…”

A Formal Approach to Distributed System Security Test Generation

“…Applying of the requirements-coverage test strategy [19] to the system model (see Fig.2.) provides the set of system objects that need to be protected.…”

“…The service architectural layer and the logical architectural layer are represented in [19] (they are not shown here because of the lack of space). [19] The security checklist generation process application to the example shows a surprisingly large number of tests required to fully cover even this very simple system -see Table 3. V. CONCLUSIONS When talking about the security testing of distributed systems, we face the great challenge of the dual nature of these systems.…”

“…Applying of the requirements-coverage test strategy [19] to the system model provides a set of system objects that need to be protected:  individual components;  individual components interaction from the end-user requirements on all architectural layers. Next, we partitioned the set of typical threats with regard to the model layered structure (see Table 1).…”