industry news
Subscribe Now

LDRA Tool Suite—First to Provide Requirements to Object-Code Traceabilit

San Bruno, CA, May 2, 2011. LDRA, the leader in standards compliance, automated software verification, source code analysis and test tools, has developed another first—requirements-to-object–code traceability. In the safety-critical domain, devices required to meet the most critical levels of certification must verify software traceability from requirements through design to code at both source- and object-code levels.By providing the most comprehensive traceability, LDRA ensures that verification problems found at the object-code level can be quickly and easily traced to the originating source code and requirements levels.

Evidence that all lines of software have been fully tested at the source- and object-code levels is becoming more important for a number of industries. DO-178C, the new avionics software standard, will soon mandate this for the most critical software, and medical and automotive industries are recognizing that this verification process is equally valuable in their environments. Discrepancies caused by compiler interpretation or program optimization can lead to code verification passing at the source level, but failing at the assembler object-code level.  

Tracing the object code—also referred to as assembler code—back to the originating high-level source code is a tedious, time-consuming challenge without requirements-to-object–code traceability. LDRA pioneered requirements-to-object–code traceability to reduce the time and risk for companies developing embedded software that must meet the highest levels of safety standards. 

In the past, many companies needing to meet stringent certification requirements verified their object code using in-house tools. However, with the adoption of more complex architectures, engineering teams no longer have in-house expertise on the modern architectures, nor can they afford to develop and maintain complex object-level verification tools for project-specific implementations. LDRA equips developers with the ability to review code instruction by instruction, while eliminating the cost of developing and maintaining tools in-house.

“In the medical community where 510k filings take 18 months or longer to be processed for compliance with the Medical Devices Act, there’s an understandable desire to develop, test and file for compliance as soon as possible,” commented Dr. Jerry Krasner, Principal Analyst of Embedded Market Forecasters. “Software verification tools, particularly those that automate requirements traceability to object code, provide an additional level of confidence that code has been thoroughly executed, tested against requirements and verified. Far too often, verification is a bottleneck for process completion.”

“Software whose failure can result in the loss of life quite understandably demands a more stringent level of verification,” confirmed Ian Hennell, LDRA Operations Director. “In the past, such rigor has caused companies to lose control of project budgets and deadlines. Automated traceability minimizes that risk through much improved transparency, speed of debug, test pass/fail verification, and automated documentation. It makes project management much simpler by providing the ability to pinpoint on demand what needs to be done and where any remaining problems lie.” 

The importance of software verification tools is underlined in “The use of requirements management and software verification tools as part of a comprehensive medical devices development strategy,” a paper by Dr. Jerry Krasner of Embedded Market Forecasters. Copies of the paper are available on LDRA’s Web site at and in LDRA’s booth (#838) at the Embedded Systems Conference (ESC), being held May 2–5, 2011 at the McEnery Convention Center in San Jose, CA.

About LDRA 

For more than 35 years, LDRA has developed and driven the market for software that automates code analysis and software testing for safety-, mission-, security- and business-critical markets. Working with clients to achieve early error identification and full compliance with industry standards, LDRA traces requirements through static and dynamic analysis to unit testing and verification for a wide variety of hardware and software platforms. Boasting a worldwide presence, LDRA is headquartered in the UK with subsidiaries in the United States and an extensive distributor network. For more information on the LDRA tool suite, please visit:

Leave a Reply

featured blogs
Jul 24, 2021
Many modern humans have 2% Neanderthal DNA in our genomes. The combination of these DNA snippets is like having the ghost of a Neanderthal in our midst....
Jul 23, 2021
The Team RF "μWaveRiders" blog series is a showcase for Cadence AWR RF products. Monthly topics will vary between Cadence AWR Design Environment release highlights, feature videos, Cadence... [[ Click on the title to access the full blog on the Cadence Community...
Jul 23, 2021
Synopsys co-CEO Aart de Geus explains how AI has become an important chip design tool as semiconductor companies continue to innovate in the SysMoore Era. The post Entering the SysMoore Era: Synopsys Co-CEO Aart de Geus on the Need for AI-Designed Chips appeared first on Fro...
Jul 9, 2021
Do you have questions about using the Linux OS with FPGAs? Intel is holding another 'Ask an Expert' session and the topic is 'Using Linux with Intel® SoC FPGAs.' Come and ask our experts about the various Linux OS options available to use with the integrated Arm Cortex proc...

featured video

Adopt a Shift-left Methodology to Accelerate Your Product Development Process

Sponsored by Cadence Design Systems

Validate your most sophisticated SoC designs before silicon and stay on schedule. Balance your workload between simulation, emulation and prototyping for complete system validation. You need the right tool for the right job. Emulation meets prototyping -- Cadence Palladium and Protium Dynamic Duo for IP/SoC verification, hardware and software regressions, and early software development.

More information about Emulation and Prototyping

featured paper

Configure the backup voltage in a reversible buck/boost regulator

Sponsored by Maxim Integrated

This application note looks at a reference circuit design using Maxim’s MAX38888, which provides a supercapacitor-based power backup in the absence of the system rail by discharging its stored charge. The backup voltage provided by the regulator from the super cap is 12.5% less than the system rail when the system rail is removed. This note explains how to maintain the backup voltage within 5% of the minimum SYS charge voltage.

Click to read more

featured chalk talk

IEC 62368-1 Overvoltage Requirements

Sponsored by Mouser Electronics and Littelfuse

Over-voltage protection is an often neglected and misunderstood part of system design. But often, otherwise well-engineered devices are brought down by over-voltage events. In this episode of Chalk Talk, Amelia Dalton chats with Todd Phillips of Littelfuse about the new IEC 623689-1 standard, what tests are included in the standard, and how the standard allows for greater safety and design flexibility.

Click here for more information about Littelfuse IEC 62368-1 Products