| LDRA MISRA C 1998 - HIS Mapping v2.2.2 Web |
|
| The LDRA tool suite is developed and certified to BS EN ISO 9001:2000. This comparison has used the MISRA-C:1998 and the HIS (Herstellerinitiative Software) standard (which is a subset of MISRA-C:1998). |
|
| |
|
| LDRA MISRA C++ 2008 Standard v2.1 Web |
|
| The LDRA tool suite is developed and certified to BS EN ISO 9001:2000. This comparison has used the MISRA-C++:2008 standard. |
|
| |
|
| Legacy code in the safety critical age v2.1 |
|
| Legacy code reuse might seem like a good idea, but what about when security and safety-critical risks are a factor? Legacy code is expected to function correctly, but structural testing provides a way to mitigate the unexpected. |
|
| |
|
| LDRA MISRA C 2004 v2.5.3 Web |
|
| The LDRA tool suite is developed and certified to BS EN ISO 9001:2000. This comparison has used the revised MISRA standard, MISRA-C:2004. |
|
| |
|
| LDRA JSF AV CPP Standard Compliance v2 3.2 Web |
|
| The LDRA tool suite is developed and certified to BS EN ISO 9001:2000. This comparison has used Doc. No. 2RDU00001 Rev C - Date: December 2005 by Lockheed Martin Corporation. |
|
| |
|
| LDRA High Integrity CPP v2.5.3 Web |
|
| The LDRA tool suite is developed and certified to BS EN ISO 9001:2000. This comparison has used the High Integrity C++ Coding Standard © - The Programming Research Group manual - Version 2.2 - Issued 18/5/04 by PRL. |
|
| |
|
| LDRA Tool Suite and TBreq v2.1.1 |
|
| The LDRA tool suite with TBreq provides a solution for software developers, testers, QA managers, architects, business modellers and project managers. Combining the new features of TBreq with LDRA’s leading-edge methodology, Zero Defect Software Development (ZDSD), the LDRA tool suite is the most feature rich and technically advanced product in the embedded software development market. |
|
| |
|
| The SIL Levels of IEC 61508 - A Revised Proposal v6 |
|
| The paper proposes a new scheme for safety integrity levels (SILs) based on reasoned principles. The scheme provides a mechanism for selecting appropriate verification and validation techniques for a given SIL and, in particular, suggests a replacement for the existing technique selection tables of the IEC 61508 standard. |
|
| |
|
| LDRA Tool Suite & DO-178B v2.3 |
|
| Working with the avionics industry to meet the challenges of achieving certification economically. LDRA has exceptional experience in this specialist area and the LDRA tool suite provides the most comprehensive source code analysis and testing facilities for assisting meet DO-178B software development and verification requirements. |
|
| |
|
| LDRA Tool Suite & Testing Automotive Software v2.1 |
|
| Modern motor vehicles make greater use of software than ever before. Much of this software is of a safety-critical or safety-related nature and, as such, must be designed, developed and tested to the highest possible standards most notable the MISRA C / MISRA-C:2004 standard. |
|
| |
|
| LDRA Tool Suite & Def Stan 00-55 v2.1 |
|
| It is a requirement that all safety-critical software supplied to the MOD must comply with the MOD standard Def Stan 00-55. LDRA have worked with the MOD to develop the LDRA tool suite to meet the challenges of achieving software certification. |
|
| |
|
| ZDSD_Manifesto_v2_1_2 |
|
| This white paper looks at Zero Defect Software Development (ZDSD) as a results-oriented process that emphasises the analysis, testing and reporting of the causality of defects. This process, which has evolved from LDRA’s commitment to safety-critical software development and verification, supplants the traditional approach of reacting to undesirable effects and treating symptoms while attempting to manage verification process using “trend analyses” or simply tracking the occurrences of defects. |
|
| |
|
| Testing Times for Real Time Software v2.1 |
|
| LDRA looks at ways to reduce the cost of testing and maintaining code. Testing and maintenance of code constitute 70% or more of the typical software lifecycle, but what strategies can be used to manage these costs? |
|
| |
|
| Lessons Learnt from Aerospace Software Development v2.1 |
|
| The aerospace industry has been at the forefront of software development for the past 30 years and the lessons learnt and approaches that aerospace companies have utilised bring proven methodologies and techniques that ensure good quality and high reliability. |
|
| |
|
| Unit Testing Embedded Systems on Railways v2.1 |
|
| The rail industry can learn from the aerospace business in using software development tools. A strategy for testing software is now seen as critical as software design and implementation. The challenges of testing Real-Time Embedded Systems is explained and how automated unit testing benefits the process. |
|
| |
|
| Development of Object Code Verification v2.1 |
|
| The increasing sophistication and safety-critical nature of many modern embedded control applications, mean that as non-avionics based suppliers adopt DO-178B then object code verification is one of the key elements that they have to sit up and take notice of. LDRA explains this area and provides information on Object Code Verification Solutions. |
|
| |
|
| Efficient testing ensures requirements traceability & verification v2.1 |
|
| Integrating requirements with automotive electronics hardware and software testing streamlines development and cuts costs. The need for requirements traceability and verification is typically imposed on automotive electronics suppliers as a contractual requirement. With increasing frequency, vendors are recognizing that requirements-based testing is an essential element of successful software development projects in general. |
|
| |
|
| Testing Software - The New Frontier v2.1 |
|
| As the designs created in the aerospace and defense industry have grown more sophisticated, the resulting systems have become quite complex. This complexity starts with the mission and permeates the system being built, including the control system that runs, executes, or guides it. As a result, software development has become ever more critical to the development process. |
|
| |
|