/pdf/the-guide-to-the-software-engineering-body-of-knowledge-2py588n7u7.pdf

The Guide to the Software Engineering Body of Knowledge Reporting on the SWEBOK pr o ject, t he authors—who re pr e sent the pr o ject's editorial team—discuss the thr e e-phase plan to characterize a body of knowledge, a vital step toward developing softwar e engineering as a pr o fession.

data types Sorting and searching parallel and distributed algorithms 3. [AR] Computer Architecture

/pdf/guide-to-the-software-engineering-body-of-knowledge-4x9ajlpq2m.pdf

Guide to the Software Engineering Body of Knowledge

An orchestrated survey of methodologies for automated software test case generation

Model-based testing (MBT) relies on models of a system under test and/or its environment to derive test cases for the system. This paper discusses the process of MBT and defines a taxonomy that covers the key aspects of MBT approaches. It is intended to help with understanding the characteristics, similarities and differences of those approaches, and with classifying the approach used in a particular MBT tool. To illustrate the taxonomy, a description of how three different examples of MBT tools fit into the taxonomy is provided. Copyright © 2011 John Wiley & Sons, Ltd.

/pdf/a-taxonomy-of-model-based-testing-approaches-242q024wa8.pdf

A taxonomy of model-based testing approaches

Embeddedsystemsareofgrowingimportanceinindustry. Forexample,inatoday'svehicleahugenumberofembeddedandcommunicating systems can be found. Exhaustive testing of such systems is a requirement, because changes after deliveryand use are expensive and sometimes even impossible. In this paper we propose the use of qualitative models, which are anabstraction of quantitative physical models, for test case generation and test execution. In particular, we show how Simulinkmodels from which control programs are automatically extracted can be tested with respect to qualitative models. SinceSimulink models are heavily used in industry, the approach is of practical interest.Keywords: conformance testing, hybrid systems, qualitative reasoning, qrioconf, Garp3 1 Introduction In industry and especially in the automotive industry Simulink is often used to implementcontrol programs for various purposes. One reason is that those models can be directlyconverted into C code, which runs on the vehicle's electronic control units (ECUs). As aconsequence Simulink models have to be tested thoroughly. This holds in particular forsafety critical systems. In order to meet the safety and quality criteria of such modelsautomated test case generation and more specically model-based testing is of specicinterest but has hardly been explored. In order to ll this gap we present an approach thatmakes use of qualitative models for model-based test cases generation.Qualitative models represent basically cause-effect relationships and constraints onmodel variables. They can be seen as an abstraction of the usually implemented quan-titative differential equation models when using Simulink or other modeling languages.Hence, Simulink models are a renement of qualitative models. This is in contrast to theuse of other means for representing models in this domain like hybrid automata, whichshares basically the same abstraction level with Simulink models.Inordertoallowforusingqualitativemodelsformodel-basedtestingwehavetospecifythe equality relation between the specication and the implementation. For this purpose

Electronic Notes in Theoretical Computer Science

Formal specifications contain a great deal of information that can be exploited in the testing of an implementation, either for the generation of test-cases, for sequencing the tests, or as an oracle in verifying the tests. This papers presents automatic techniques for partition analysis in state-based specifications, specifically VDM. Test domains for individual operations are calculated by reduction of their mathematical description to a Disjunctive Normal Form. Following this, a partition analysis of the system state can be performed which permits the construction of a Finite State Automaton from the specification. This, in turn, can be used to sequence the required tests in a valid and sensible way. A tool has been developed based on the techniques applied to VDM, which has been used to develop the examples presented in the paper.

Automating the Generation and Sequencing of Test Cases from Model-Based Specifications

Making the most of formal specification through animation, testing and proof

This paper reports on the experience gained in the MaFMeth project, which undertook a formal development with tool support for several parts of the life cycle from requirements capture through to C code generation. We explore the hypotheses that formal methods enable the early detection of faults in design by examining the development process in the light of the stages at which faults were introduced and discovered.

/pdf/quantitative-analysis-of-an-application-of-formal-methods-3son243zra.pdf

Quantitative Analysis of an Application of Formal Methods

This paper reports on the experiences of IBM Hursley in using the Z notation and the B-Method [Abr95] [Abr93] in developing new function for IBM's CICS product [IBM94].

/pdf/applying-the-b-technologies-on-cics-3m6q17a8t7.pdf

Applying the B Technologies on CICS

This article describes the rigorous application of formal methods of software development to a system software development project within a conventional industrial software development environment. This project applied formal methods to a small part (one subsystem) of the development of a release of a system software product. The formal methods VDM and B were used to specify, design and implement the administration subsystem of a product that was otherwise developed along conventional lines. Support tools were used to assist with the use of both methods throughout the development lifecycle. Metrics for effort and quality were collected from the project and compared with historical metrics for similar projects to allow the impact of formal methods on cost and quality to be assessed. This article briefly outlines the product being developed and the subsystem to which formal methods were applied. The environment in which this development was performed and the particular approach used are described. The results of this industrial application of formal methods and the lessons learned by the project are discussed at some length.

Jeremy Dick

Papers

Automating the Generation and Sequencing of Test Cases from Model-Based Specifications

Making the most of formal specification through animation, testing and proof

Quantitative Analysis of an Application of Formal Methods

Applying the B Technologies on CICS

Lessons learned from rigorous system software development