An Introduction to Safety Critical Systems

An Introduction to Safety Critical Systems

An Introduction to Safety Critical Systems

This paper provides an introduction to the development of software for safety-critical systems. It aims to serve as a tutorial for developers who are new to the development of software for safety critical systems, discussing the issues involved, introducing some of the techniques available to developers, and providing an overview of how QA Systems’ tools can be used to assist with the development of software for safety-critical systems.

A safety-critical system is a system where human safety is dependent upon the correct operation of the system. The emphasis of this paper is on the software element of safety-critical systems, which for convenience, is often referred to as safety-critical software. However, safety must always be considered with respect to the whole system, including software, computer hardware, other electronic and electrical hardware, mechanical hardware, and operators or users, not just the software element.

To access this resource please fill in the form:

By submitting your information, you will gain access to this resource and receive periodic relevant event invitations, as well as information on the latest valuable embedded software testing resources from our experts. You can opt out at any time. See our privacy policy.

Cantata Testing C++

Cantata Testing C++

Cantata provides a full and unique suite of testing capabilities for the efficient unit and integration testing of C and C++. This feature brief highlights the capabilities specifically useful for testing C++ code.

To access this resource please fill in the form:

By submitting your information, you will gain access to this resource and receive periodic relevant event invitations, as well as information on the latest valuable embedded software testing resources from our experts. You can opt out at any time. See our privacy policy.

Organisational Approaches to Unit Testing

Organisational Approaches to Unit Testing

This paper describes three organisational approaches for unit testing: top down, bottom up and isolation. The organizational approach is a key element yo unit test strategy and planning; selection of an inappropriate approach can have a significant impact on the cost of unit testing and software maintenance. A unit test strategy based on isolation testing is recommended.

To access this resource please fill in the form:

By submitting your information, you will gain access to this resource and receive periodic relevant event invitations, as well as information on the latest valuable embedded software testing resources from our experts. You can opt out at any time. See our privacy policy.

Cantata Team Reporting Feature Brief

Cantata Team Reporting

This Feature Brief highlights the optional Add-on for Cantata, Cantata Team Reporting. It enables teams to work more effectively together by providing a web interface for teams to share tests avoiding the need to replicate tests over multiple work spaces.

To access this resource please fill in the form:

By submitting your information, you will gain access to this resource and receive periodic relevant event invitations, as well as information on the latest valuable embedded software testing resources from our experts. You can opt out at any time. See our privacy policy.

Dr. Keil’s comprehensive testing for administration module

Dr. Keil’s comprehensive testing for administration module

This case study centers on Dr. Keil Informationstechnik GmbH & Co KG and a prominent telecom equipment supplier aiming to enhance their administration module reliability within stringent downtime limits while utilizing Cantata as the primary testing tool. Cantata facilitated testing at various levels, from unit to cluster testing, including GUI, database, and client-server interactions. The tool’s flexibility and comprehensive testing capabilities proved invaluable in meeting the client’s reliability objectives.

View Fullscreen
LEARN MORE
CANTATA DATASHEET
START TRIAL

Designing Unit Test Cases

Designing Unit Test Cases

Producing a test specification, including the design of test cases, is the level of test design which has the highest degree of creative input. Furthermore, unit test specifications will usually be produced by a large number of staff with a wide range of experience, not just a few experts. This paper provides a general process for developing unit test specifications and describes some specific design techniques for designing unit test cases. It serves as a tutorial for developers who are new to formal testing of software, and as a reminder of some finer points for experienced software testers.

To access this resource please fill in the form:

By submitting your information, you will gain access to this resource and receive periodic relevant event invitations, as well as information on the latest valuable embedded software testing resources from our experts. You can opt out at any time. See our privacy policy.

Automotive Sector Brief

Automotive Sector Brief

In this sector brief, we highlight the ISO 26262 software standard, which is used in the verification and validation of vehicle-based software. We also discuss how Cantata and AdaTEST 95 support project certification.

To access this resource please fill in the form:

By submitting your information, you will gain access to this resource and receive periodic relevant event invitations, as well as information on the latest valuable embedded software testing resources from our experts. You can opt out at any time. See our privacy policy.

Meggitt’s reliable software for Airbus and Rolls Royce

Meggitt’s reliable software for Airbus and Rolls Royce

Meggitt’s two significant projects were the Engine Interface and Power Monitoring (EIPM) unit for the Airbus A380 aircraft, and the Engine Monitoring Unit (EMU) for the Rolls Royce Trent 900 engine. These projects necessitated robustly tested software to comply with the rigorous safety requirements of the civil avionics industry-standard DO-178B.

View Fullscreen
LEARN MORE
CANTATA DATASHEET
START TRIAL

Which Code Coverage Metrics to Use

Which Code Coverage Metrics to Use

This paper provides a discussion of structural test coverage metrics, looking at the practicality of their use for real software developments. It concludes that some metrics are unsuitable for real use, and recommends suitable combinations of structural coverage metrics for testing a range of integrity levels. It should be remembered that structural coverage based on control flow analysis is only a good starting point for thorough testing, and that other criteria for designing tests based on data flow and required functionality should be included in an effective testing strategy. It evaluates: statement coverage, decision coverage, LCSAJ coverage, path coverage, condition operand coverage, condition operator coverage and Boolean operand effectiveness coverage.

To access this resource please fill in the form:

By submitting your information, you will gain access to this resource and receive periodic relevant event invitations, as well as information on the latest valuable embedded software testing resources from our experts. You can opt out at any time. See our privacy policy.