The object-oriented software development process is increasingly used for the construction of complex distributed systems. In this context, behavior models have long been recognized as the basis for systematic approaches to requirements capture, specification, design, simulation, code generation, testing, and verification. Two complementary approaches for modeling behavior have proven useful in practice: interaction-based modeling (e.g. UML sequence diagrams) and state-based modeling (e.g. UML statecharts). Building on formal V&V techniques, in this article we present a method and a tool for automated synthesis of test cases from scenarios and a state-based design model of the application, remaining entirely within the UML framework. The underlying "on the fly" test synthesis algorithms are based on the input/output labeled transition system formalism, which is particularly appropriate for modeling applications involving asynchronous communication. The method is eminently compatible with classical OO development processes since it can be used to synthesize test cases from the scenarios used in early development stages to model global interactions between actors and components, instead of these test cases being derived manually. We illustrate the system test synthesis process using an Air Traffic Control software example.

Abstract. The object-oriented software development process is increasingly used for the construction of both centralised and distributed systems. As yet, however, formal V&V techniques have not found much use in the objectoriented context, in spite of the fact that some are now mature enough to be exercised in real world applications. In this paper, we investigate the use of formal validation in a UML-based development process. We present a method and a tool for automated synthesis of test cases from generic test scenarios and a design model of the application, remaining entirely within the UML framework. The underlying "on the fly" test synthesis algorithms are based on the input/output labelled transition formalism, which is particularly appropriate for modelling applications which may involve asynchronous communication. We illustrate the system test synthesis process using an Air Traffic Control software case study.

Software product families (PF)

No abstract

No abstract