Description

LIST OF INCLUDED SOFTWARES IN SUITE :

Software	What it does
LDRA Testbed	Core static + dynamic analysis engine
TBvision	View violations, metrics, and coverage on source
TBrun	Unit / integration / system tests
TBmanager	Requirements traceability and compliance tasks
LDRArules	Standalone coding-standards checker
LDRAcover	Standalone coverage tool
LDRAunit	Standalone unit-test tool
LDRAlite	Light standards-checking plugin
TBmisra	MISRA / AUTOSAR / JSF++ etc.
TBsecure	CERT / CWE security rules
TBsafe	Extra high-integrity analysis (e.g. MC/DC)
TBhis	HIS quality metrics
TBexclude	Suppress / justify rule violations
TBextreme / TBextremePLUS	Auto-generate test vectors
TBjustify	Document coverage justifications
TBobjectbox	Object-code verification
DDFC	Dynamic data-flow coverage
TBwcet	Worst-case execution time
TBexec	Execution timing / multicore overlap
TBpublish	Certification / quality reports
TBevolve	Compare violations across versions
LDRAvault	Web dashboard for team results
TBbuildimport	Import existing build projects
FCP	FACE conformance package
TIP	TBmanager links to ALM tools
TCC	Compiler / toolchain adapters
TLP	Target (on-hardware) licenses
TQSP	Tool-qualification evidence packs

---

🛡️ LDRA Tool Suite 10.6.0 with Testbed

LDRA Tool Suite 10.6.0 is the current release of LDRA’s professional platform for safety- and security-critical embedded software. The heart of the suite is LDRA Testbed — the static and dynamic analysis engine that feeds TBvision, TBrun, TBmanager and the timing tools. Use it when you must prove that C, C++, Ada or Java code meets coding standards, has measured structural coverage (including MC/DC), is unit- and integration-tested, and still meets timing limits on real hardware.

Version 10.6.0 is aimed at projects that must produce audit-ready evidence for DO-178C, DO-326B / DO-356A, ISO 26262, ISO/SAE 21434, IEC 61508, IEC 62304, IEC 62443-4-1, EN 50128 / EN 50716, EN 60880 and IEC 62138.

✨ What’s new in LDRA 10.6.0

🎯 Hybrid trace + instrumentation coverage

The flagship change in 10.6.0 is hybrid structural coverage. You can now collect coverage from hardware trace through TASKING winIDEA and BlueBox probes, then import it into LDRA reports next to classic instrumentation coverage.

• ✅ Trace path: no source change, very low runtime overhead
• ✅ Instrumentation path: deep metrics including MC/DC
• ✅ Coverage smoothing merges both sources into one evidence set
• ✅ Built for DO-178C DAL A/B, ISO 26262 ASIL C/D and IEC 61508 SIL 3/4

That combination is the practical answer to “instrumentation changes timing” versus “trace alone cannot prove MC/DC.”

⏱️ TBexec — execution timing for multicore

TBexec is new in the Worst-Case Execution Time package. It records actual test-run timing and turns it into evidence you can show an auditor.

• 📊 Interactive scheduling and function-timing diagrams
• 📞 Call times, call stacks and function overlaps
• 🔗 Timing-coupling / interference views for multicore (MCP)
• 🧩 Works with TBwcet for measured WCET under stress
• 📋 Supports A(M)C 20-193 style multicore objectives in TBmanager
• ⚙️ RTOS-independent: bare metal or any RTOS

🧰 Day-to-day workflow upgrades

• 🧩 Global Stubs — load stub behaviour from external templates when TBrun builds harnesses. Large regression suites stay maintainable.
• 📁 TBreports path repair — if reports moved after generation, pick the new folder once; every linked source path is resolved.
• ⚡ Energy standards pack — EN 60880 and IEC 62138 objectives now sit in TBmanager via the Energy Productivity Package.

🔁 Carried forward from 10.5.x

• 📝 TBjustify inside TBrun for white-box coverage justifications
• 📈 TBexec regression timing reports
• 🔎 LDRAvault search across projects, components and uploads
• ▶️ Import TBrun sequences into LDRAvault
• 🏗️ Multi-node CI/CD analysis with centralised results
• 📦 Build Import fixes for creating LDRA projects from real compile lines

🚀 Product highlights

🧠 LDRA Testbed — the analysis engine

Testbed is not a thin wrapper around Clang or a commercial parser. It uses LDRA’s own engine so new rules and coverage methods can be added without waiting on a third-party frontend. It drives:

• 📜 Coding-standard enforcement
• 📉 Quality metrics (complexity, knots, HIS and more)
• 🔀 Data-flow and control-flow analysis
• 🔗 Data coupling and control coupling
• 🧪 Dynamic coverage collection on host or target

👁️ TBvision

See violations and coverage on the original source. Switch between rule sets, jump from a finding to the line, and review quality metrics without exporting a spreadsheet first.

🧪 TBrun / LDRAunit

Automatic harness and stub generation for unit, module, integration and subsystem tests. Run on the host, a simulator or the physical target. Pair with TBextreme / TBextremePLUS for generated vectors: requirements-based, boundary, equivalence, robustness and fuzz-style presets.

🗺️ TBmanager

Bidirectional traceability from standard objectives and system requirements down to code, tests and results. Integration Packages (TIP) connect Microsoft Office, IBM DOORS / DNG, Jama, Polarion, Jira, ReqIF and other ALM tools.

☁️ LDRAvault

Web dashboard that aggregates reviews, coverage and unit-test results across users and sites. Snapshots, heat maps and trend graphs support multi-team and CI/CD programmes.

📦 Typical add-on modules

• 📘 TBmisra — MISRA C/C++, AUTOSAR C++, JSF++ AV, HIC++
• 🔐 TBsecure — CERT C/C++/Java and CWE
• 🛡️ TBsafe — extra high-integrity analysis for DAL A / SIL 3–4 class work
• 🚫 TBexclude — controlled suppression of selected violations
• 📤 TBpublish — configurable certification report packs
• 🧬 TBevolve — compare rule violations across code versions
• 🧱 TBobjectbox — source-to-object verification
• 🌊 DDFC — Dynamic Data Flow Coverage
• ✈️ FACE Conformance Package (FCP)
• 🎛️ TCC / TLP — compiler and target adapters
• 📑 TQSP — Tool Qualification Support Packages (DO-330 style evidence)

💻 System requirements

Confirm the exact matrix on your license and Tool Chain Configuration. Public baselines for current LDRA 10.x / 10.6.0 deployments:

🖥️ Host workstation

• 🪟 Windows 11, 10, 8 or 7 — 64-bit strongly recommended
• 🐧 Linux: RHEL / CentOS, Ubuntu, SUSE / openSUSE
• 🍎 macOS (host analysis; target packs vary)
• ⚙️ Multi-core x86-64 CPU
• 🧠 16 GB RAM recommended for large systems (8 GB is a practical floor)
• 💾 SSD for projects, instrumentation output and report trees

🔑 License server

• 🪟 64-bit Windows 7–11 or Windows Server 2008 / 2012 / 2016 / 2019 / 2022
• 🐧 64-bit Ubuntu or RHEL
• 📦 FlexNet Publisher / FlexLM 11.19.2 or later (11.19.6 utilities are the current download)
• ⛔ Windows XP and Server 2003 cannot host current FlexLM utilities
• 📄 Licenses are version-specific. 10.6.0 needs a 10.6-compatible CTL file. An older CTL will not unlock this build.

💻 Languages and toolchains

• Languages: C, C++, Java, Ada 95
• IDEs / compilers commonly used with TCC packs: TASKING, Green Hills MULTI / INTEGRITY, Wind River Diab / VxWorks, IAR, Keil, TI Code Composer Studio, GNU, Cosmic, HighTec, Microchip MPLAB, QNX, Lauterbach TRACE32, winIDEA, MathWorks Simulink and others
• Targets: 8-bit through 64-bit MCUs and SoCs, including multicore devices used in avionics and automotive

🐛 Fixes and stability notes

10.6.0 was published as a certification-facing feature release. The public TASKING note does not list individual bug IDs; those sit in the licensed PDF release notes. What is documented for shoppers:

• 🔧 More reliable merge of trace coverage into existing LDRA coverage results and reports
• 🔧 Less stub-management drift on long-lived TBrun suites (Global Stubs)
• 🔧 Report viewers no longer “go blind” when source or report folders are relocated
• 🔧 10.5.x Build Import corrections remain in the 10.6 line
• 🔧 TBjustify no longer lives as a disconnected extra step for many white-box flows
• 🔧 LDRAvault search and sequence import reduce “which snapshot is this?” errors on multi-user programmes

⚠️ Before a formal tool-qualification or SOI audit, install the exact service pack named in your vendor portal and keep the TQSP revision aligned with the build number shown in Help → About.

🧩 What’s included vs what is licensed

The suite is modular. A typical “Testbed” seat is the analysis engine plus the modules on the license file — not every name in the catalogue. Standalone siblings map as follows:

• LDRArules → TBvision rules checking
• LDRAcover → coverage-focused TBvision
• LDRAunit → TBrun-only unit test
• LDRAlite → light rules plugin

Productivity Packages bundle the common set for Aerospace & Defense, Automotive, Medical, Industrial/Energy or Rail so you do not have to pick every add-on by hand.

🏆 Interesting facts

• 🏛️ LDRA began as Liverpool Data Research Associates. Researchers there defined LCSAJ (Linear Code Sequence and Jump) coverage — still a distinctive Testbed metric.
• ✈️ LDRA Testbed was among the first commercial tools used to support FAA DO-178B airborne software certification, on both airborne and ground systems.
• 🔬 Independent process studies cited by LDRA historically reported large drops in escaped defects and shorter test cycles when Testbed was applied early — the same reason the engine is still the suite’s foundation 40+ years on.
• 🤝 In 2025 TASKING acquired LDRA. Release 10.6.0 (June 2026) is the first major suite drop that treats TASKING winIDEA / BlueBox hardware trace as a first-class coverage source beside Testbed instrumentation.
• 🧪 TBexec exists because multicore interference is no longer a lab curiosity: published LDRA/DEVCOM work measured mean execution-time inflation up to about 40% from timing coupling. 10.6.0 is the release that productises that measurement path.

✅ Who should choose 10.6.0

Buy this version if you verify firmware for aircraft, vehicles, industrial controllers, medical devices, rail signalling or energy systems and need one vendor chain for:

• 🔍 static analysis and MISRA / CERT / CWE compliance
• 🧪 automated unit and integration test
• 📈 statement, branch and MC/DC coverage — now with optional hardware trace
• 🗺️ requirements-to-test traceability
• ⏱️ multicore timing and WCET evidence
• 📁 certification reports and tool-qualification support

Need only rules checking or only unit test? Ask for LDRArules, LDRAcover or LDRAunit instead of a full suite seat.

---

⭐⭐⭐⭐⭐ — Verification lead, aerospace / automotive

LDRA Tool Suite 10.6.0 with Testbed is the tool we actually use to close DO-178C and ISO 26262 evidence, not a demo. Static analysis, MISRA/CERT, MC/DC coverage, TBrun unit tests and TBmanager traceability sit in one chain. Hybrid trace + instrumentation coverage and TBexec timing in 10.6 cut target-test overhead on multicore boards. Steep licence and setup cost, but audit packages come out complete. For safety-critical C/C++ this is still the benchmark.