Military Embedded Systems

Company Directory

LDRA Technology

2540 King Arthur Blvd, Suite #228
Lewisville, TX 75056
[email protected]
https://ldra.com/
LDRA Technology
Articles related to LDRA Technology
Avionics

What's needed to ensure safety and security in UAV software - Story

July 31, 2013
UAVs are not like the remote control stunt plane you unwrapped on your 10th birthday. In their different guises they can be found in civil airspace or flying as integral players in military missions. That makes unmanned systems? safety and security very serious considerations. Accordingly, ISO 14508 and DO-178 could prove helpful in perpetuating safety and security for unmanned systems. Software tools that automate the processes required by these certification standards are easing the burden.
Avionics

Managing FAA DO-178B/C, 278A, and 254 with one system - Product

May 22, 2013
Certifying to FAA applications is an expensive, time-consuming process, but required for any software or hardware that is flight-critical on aircraft that travel through civil airspace. LDRA engineers in Wirral, United Kingdom, have found a way to make that process more manageable by creat...
Avionics

DO-178C, DO-278A, DO-254 Certification Management System developed by LDRA - News

April 25, 2013
SAN JOSE, CA. The LDRA Compliance Management System (LCMS), a resource for developing infrastructure that supports DO-178B/C, DO-278A, and DO-254 compliancy, has been released by LDRA. LCMS ensures certification readiness through a process that includes LDRA Certification Services (LCS) professionals support from development and production through the maintenance lifecycle.
Avionics

Code Quality: Dynamic & static analysis combined makes engineers & auditors happy - Blog

March 28, 2013
In the good old days, before writing software became “software engineering,” code development was a black art practiced by weird nerdy kids straight out of college. For them, coding was by no means a structured discipline. If you managed to get them to communicate, they might tell you that they were hacking code together and using ad hoc test data to see whether it did what it was supposed to do when they executed it.