LDRA Articles





07 December 2011 - Cut the cost of code development with tracability tools
The requirements-driven development mantra and all that it encompasses has been documented and discussed thoroughly for almost two decades, in the pursuit of building better and more reliable applications. This mantra has been the underlying motivation behind software processes, certifying authorities, and industry standards focused on realizing requirements-driven development in its utopian form.

EE Times

www.eetimes.com
10 November 2011 - Zertifizierung industrieller Systeme gemäß IEC 61508
Wir erleben es leider täglich: Software gehört zu den fehleranfälligsten Produkten unserer digitalen Welt. Das müsste nicht so sein. Denn die Norm IEC 61508 beschreibt, wie man Software nach bestimmten Qualitäts- und Sicherheitsstandards entwickelt. Um den Standard einzuhalten, muss die Entwicklung strengen Vorgaben folgen. Selbst wenn eine Zertifizierung nicht notwendig ist - das Vorgehensmodell eignet sich für jede qualitativ hochwertige Software.

elektroniknet.de

www.elektroniknet.de
09 November 2011 - Certification of medical devices for developers to simplify the IEC 62304-compatible steps
Now, with advanced medical equipment is more than ever to help health care professionals to easily and accurately make a diagnosis. However, their dependence on the equipment to ensure equipment also led to concerns about safety and quality.

ECCN.com

www.eccn.com
07 November 2011 - DO-178C Enhances Safety-Critical Avionics Software Development
Since its introduction in 1992, DO-178B has become the defacto standard for certifying all new aviation software. Subsequently, however, avionics software complexity has increased dramatically, software development technology has improved by leaps and bounds, and DO-178B has lagged behind.

Electronic Design

electronicdesign.com
02 November 2011 - Are You Covered?
LDRA issued a press release sometime back on their work with the Mathworks; I addressed the overall topic at the time, but there was something else that caught my eye. In the press release was the statement, “The LDRA tool suite provides full code coverage whether statement, branch or decision, linear code sequence and jump (LCSAJ), or modified condition/decision coverage (MC/DC) of code created from Simulink models and hand-written code.”

EE Journal

www.eejournal.com
27 October 2011 - Make Sense of Software of Unknown Pedigree (SOUP)
Software test tools have been traditionally designed with the expectation that the code has been (or is being) designed and developed following an ideal development process which adheres to a best practise approach. Such an approach implies the existence of clearly defined requirements, an adherence to corporate or international coding standards, a well-controlled development process, and a coherent test regime.

ECN

www.ecnmag.com
25 October 2011 - Unit testing: why bother?
Unit test has been around almost as long as software development itself. It just makes sense to take each application building block, build it in isolation, and execute it with test data to make sure that it does just what it should do without any confusing input from the remainder of the application.

Embedded Insights

www.embeddedinsights.com
04 October 2011 - LDRA Tool Suite Integrating Traceability Requirements
Bill Wong of Electronic Design magazine talks with Chris Murray at LDRA about their LDRA tool suite which is unique in its integration of requirements traceability with static and dynamic analysis.

Engineering TV

www.engineeringtv.com
13 September 2011 - CWE: what developers of connected embedded systems need to know
A lot has been written about the potential risks that could exist if insecure software is used within military, infrastructure or medical systems, and it is easy to understand why they need to be secure.

EE Times

www.eetimes.com
13 July 2011 - How can we increase the commercial viability of advanced technology vehicles?
Automotive companies increasingly automate tasks, such as distance detection, crash avoidance, and anti-skid steering, that inch the high-end automotive toward avionics fly-by-wire capabilities. For the avionics community to achieve its comparatively gold-star safety record, avionics OEMs ensure their software systems meet stringent DO-178B standards.

ECN

www.ecnmag.com
13 July 2011 - Brainstorm: Automotive Electronics
Automotive companies increasingly automate tasks, such as distance detection, crash avoidance, and anti-skid steering, that inch the high-end automotive toward avionics fly-by-wire capabilities. For the avionics community to achieve its comparatively gold-star safety record, avionics OEMs ensure their software systems meet stringent DO-178B standards. Developers must prove that each and every line of code can be bidirectionally traced from requirement through the pass/fail of specific tests. No line of code can remain that does not rise from a requirement, has not been tested, and is not proven to do what it was intended to do.

ecnmag.com

www.ecnmag.com
12 July 2011 - Tracing requirements through to verification: How to improve current practices to meet ISO/DIS 26262
Recent quality concerns are driving the automotive industry to start looking seriously at ways to improve quality software development. One of the key defects in automotive quality stems from the increased use of electronic systems that affect the cars’ safety. Because of this, automotive companies are looking to standards such as the ISO/DIS 26262 (ISO 26262) to help them comply with the specific needs of the electrical, electronic and programmable electronic (E/E/PE) systems of road vehicles.

Automotive Electronic News

www.johndayautomotivelectronics.com
05 June 2011 - Not complying with IEC 62304 for software design could be detrimental on many levels
Medical devices have become increasingly sophisticated, now employing software-controlled applications whose failure to function correctly could result in death or serious injury. Despite this increased complexity, medical software standards continue to reflect only the rigor of low-risk applications.

EE Times

www.eetimes.com
31 May 2011 - Easing the IEC 62304 Compliance Journey for Developers to Certify Medical Devices
By adopting the quality software processes of IEC 62304, companies are better able to develop a safe product, avoid expensive recalls, and ensure that the same development process underpins the maintenance and upgrade process.

MEDS

www.medsmagazine.com
25 March 2011 - Not complying with IEC 62304 for software design could be detrimental on many levels
Medical devices have become increasingly sophisticated, now employing software-controlled applications whose failure to function correctly could result in death or serious injury. Despite this increased complexity, medical software standards continue to reflect only the rigor of low-risk applications. Notably, many of the medical device faults stem from product upgrades.

Medical Electronics Design

www.medicalelectronicsdesign.com
16 March 2011 - Zertifizierung von Medizingeräten – Eine Hilfe auf dem Weg zur Konformität mit der IEC 62304 für Softwareentwickler
Medizingeräte werden immer komplizierter; jetzt sind softwaregesteuerte Anwendungen ein integraler Bestandteil von ihnen, deren Ausfall zu Todesfällen oder schweren Personenschäden führen könnte. Trotz dieser erhöhten Komplexität reflektieren die Normen für medizinische Software nur die Vorschriften für risikoarme Anwendungen.

European Medical Device Technology

www.emdt.co.uk
01 March 2011 - Think static analysis cures all ills? Think again.
Static code analysis has been around as long as software itself, but you'd swear from current tradeshows that it was just invented. Here's how to choose the right code-analysis tools for your project.

EE Times

www.eetimes.com
01 February 2011 - Safety- and security-critical avionics software
As the complexity, requirements, and criticality of avionics software grow, innovative tools are increasingly necessary to test, verify, and secure military and aerospace systems.

Military & Aerospace Electronics

www.militaryaerospace.com
18 January 2011 - Simplifying IEC 62304 Compliance for Developers
Medical devices have become increasingly sophisticated, often employing software-controlled applications whose failure to function correctly could result in death or serious injury to the patient treated by them. Despite this increased danger, medical software standards continue to reflect only the rigour of low-risk applications.

European Medical Device Technology

www.emdt.co.uk
15 November 2010 - Code Analysis Discussion With LDRA
Static and dynamic code analysis can improve application performance, safety and reliability by identifying problems early in the development cycle if the proper tools and procedures are used from the start. Dr. Mike Hennell, founder of LDRA, spoke with me about the various aspects of these types of tools.

Electronic Design

http://electronicdesign.com
04 November 2010 - Gap analysis forges the links from requirements to verification
With recent quality concerns, the automotive industry has started looking seriously at ways to improve software development. The increased use of electronic systems that affect the car’s safety has driven automotive companies to look at standards such as ISO/DIS 26262 to help them comply with the specific needs of the electrical, electronic, and programmable electronic (E/E/PE) vehicle systems.

EE Times

http://www.eetimes.com
01 November 2010 - An accumulation of stuff - Lifecycle stuff
On another front, the folks at LDRA gave me an indepth demo of their products at the recent Embedded Systems Conference in Boston. I've been following LDRA for some time, both because of their interesting products and since they have some really smart people. I find it hard to describe the Tool Suite as it's composed of a great number of individual components that can work together or alone (and they can be purchased individually).

EE Times

http://www.eetimes.com
28 October 2010 - LDRA tool suite delivers ISO 26262 compliance for automakers
LDRA tool suite now supports the current implementation of ISO/DIS 26262, a functional safety standard for road vehicles. The LDRA tool suite automatically checks compliance to the ISO 26262 standard through all stages of the software development lifecycle.

EE Times

http://eetimes.com
28 September 2010 - Closing the back door - directives & standards
Following CERT C programming guidelines can increase system security. The last decade has seen a significant increase in the numbers and types of wireless systems. While these technologies allow for the easy connection of mobile platforms to peripherals, local networks and the internet, the connections are over the air and can be intercepted and altered, making them a potential source of security breaches.

New Electronics

http://www.newelectronics.co.uk
17 September 2010 - Securing Connected Systems
The adoption of networking in embedded systems is widespread and includes everything from domestic audio/video systems to SCADA (supervisory control and data acquisition) systems. Because of this, these systems need to be hardened so that they are impervious to attack without relying on the user “doing the right thing” to protect them.

ECN

http://www.ecnmag.com
02 September 2010 - DO-178C nears finish line, with credit for modern tools and technologies
After five years, RTCA and EUROCAE, the U.S. and European avionics standards organizations, are nearing the finish line in updating DO-178B, the bible for developers of safety-critical software. A cast of 1,000-plus people have observed or participated in the process and about 100 people show up at every meeting, according to one member of RTCA Special Committee 205 (SC-205). The industry expects the final package -- DO-178C -- to be released in the first quarter of 2011 and be mandated six to nine months after ratification.

Avionics Intelligence

http://www.militaryaerospace.com
01 September 2010 - Software development optimised through unit testing
Unit test has been around almost as long as software development itself. It just makes sense to take each application building block, build it in isolation, and execute it with test data to make sure that it does just what it should do without any confusing input from the remainder of the application.

Boards & Solutions

http://ece-news.stc-d.de
17 August 2010 - Achieving Zero Defect Software Development
Zero Defect Software Development (ZDSD) is a results-oriented process that emphasizes the analysis, testing and reporting of the causality of defects. This process, which has evolved from the commitment to providing “five-nines” (99.999%) reliability for mission-critical applications, supplants the traditional approach of reacting to undesirable effects and treating symptoms while attempting to manage verification processes using “trend analyses” or simply tracking the occurrences of defects.

ECN

http://www.ecnmag.com
August 2010 - DO-178C: Improved certification for cost-effective avionics systems
With the geometric growth in software size and complexity, avionics manufacturers are losing control of project schedules and budgets. Consequently, the Radio Technical Commission for Aeronautics (RTCA) hopes to address software development challenges through DO-178C – a new standard that embraces contemporary technologies and methodologies necessary to achieve these aims.

VME & Critical Systems

http://www.vmecritical.com
01 August 2010 - DO-178C nears finish line, with credit for modern tools and technologies
After five years, RTCA and EUROCAE, the U.S. and European avionics standards organizations, are nearing the finish line in updating DO-178B, the bible for developers of safety-critical software. A cast of 1,000-plus people have observed or participated in the process and about 100 people show up at every meeting, according to one member of RTCA Special Committee 205 (SC-205). The industry expects the final package -- DO-178C -- to be released in the first quarter of 2011 and be mandated six to nine months after ratification.

Military & Aerospace

http://www.militaryaerospace.com
01 July 2010 - Ensuring Software Quality in Embedded Medical Devices
In medical devices, increasing complexity and market pressure bring additional risk and cost associated with defects. Attention to quality standards as well as the use of fundamental tools and practices can be applied to help meet these standards and mitigate the risk.

RTC Magazine

http://rtcmagazine.com
July 2010 - Medical Device Software: Why Has It Gone Code Red?
The typical medical device software engineering process often suffers from gaps in repeatability. These gaps present enormous legal and financial risks to suppliers as well as health and safety risks to patients. The use of application lifecycle management within a project can effectively mitigate these risks.

RTC

http://rtcmagazine.com
03 June 2010 - DO-178B certification challenges for real-time Java applications
Every software engineer working on avionics systems has to deal with certifying their code to the Federal Aviation Administration's DO-178B safety certification standard. The process is required for any aircraft that flies in civilian airspace and can be quite costly.

Avionics Intelligence

http://www.militaryaerospace.com
May 2010 - Bullet-proofing your software design
Applying secure programming standards and methodology can reduce vulnerabilities in software.

Embedded Systems Design / Embedded.com

http://www.embedded.com
06 April 2010 - How to use new unit testing tools & techniques to improve software quality
Unit test tools have long provided commercial benefit for the team developing the highest integrity applications. Now these tools can also streamline the efforts of their peers working in less critical environments " even those charged with the ongoing development of undocumented legacy code.

Embedded.com

http://www.embedded.com
05 April 2010 - Mission-critical design may be the future for the SoC world
Toyota’s recent travails have stimulated discussion lately about the risks of having unsupervised software in control of a system that can do harm. The Toyota issue was whether engine-control software could cause unintended acceleration. But similar questions have been asked about other automotive systems such as ABS, and about medical systems ranging from radiation-therapy equipment to implanted pacemaker/defibrillators to robotic surgeons. There has even been angst about a computer-driven securities trading system running amok, as has apparently already happened a few times.

EDN

http://www.edn.com
11 March 2010 - Invest in requirements management to reduce defects and improve quality
Requirements are the foundation of every project. A weak foundation results in high numbers of defects, unforeseen remedial work, spiralling costs and missed deadlines. Investment in requirements management, equal to that made for design and coding, is necessary to secure a firm foundation on which to construct a successful project whether you’re motivated by DO-178B or not.

The Mil Aero Command Post

http://community.milaero.com
01 March 2010 - Making Sense Out of SOUP (Software of Unknown Pedigree)
Software test tools have been traditionally designed with the expectation that the code has been (or is being) designed and developed following a best practice development process. Legacy code turns the ideal process on its head. Although such code is a valuable asset, it is likely to have been developed on an experimental, ad hoc basis by a series of “gurus” — experts who prided themselves on getting things done and in knowing the application itself, but not necessarily expert at complying with modern development thinking and bored with providing complete documentation. That doesn’t sit well with the requirements of standards such as DO-178B.

Embedded Technology

http://www.embeddedtechmag.com
26 February 2010 - Static analysis aids code portability
Code reuse is often a major consideration within new projects, both in terms of making use of legacy code from preceding projects and as a foundation for those that will follow. Static analysis can be used to ensure that legacy code does not become a source of issues within a project and to guarantee that any code produced during its development will not afflict any projects that draw on it as a code base.

Embedded Computing Design

http://embedded-computing.com
23 February 2010 - Requirements Driven Development - Too Challenging To Be Worth It?
Requirements-driven development and testing in its ideal form has long been considered too challenging by industries who are not forced to follow stringent verification standards. After all, if no one mandates you to drive your development and testing process by a requirements traceability matrix (RTM), then adjusting your entire design and development process in the face of ever-looming deadlines and budget constraints appears not to make business sense. There’s no time for such luxuries—or so it seems.

Electronic Design

http://electronicdesign.com
12 February 2010 - Security-Critical Software Development Process and Tools
Security now dominates the forefront of industries as varied as defense, finance, and energy, and transportation. Software developed for these markets must ensure that it meets new levels of assurance.

ECN

http://www.ecnmag.com
February 2010 - Advanced development in avionics and the software verification
Will the new DO-178C provide the guidance necessary to facilitate the acceptance of advanced technologies covered by its supplements? The answer is, yes. This article explains why.

Embedded Know How

http://www.embedded-know-how.com
01 February 2010 - Integrating the LDRA tool suite and IAR Embedded Workbench for Safe, Cost-Effective and Efficient Software Development
LDRA has a comprehensive set of embedded software development tools that facilitate and enhance the capabilities provided by IAR Embedded Workbench® and allow you to create devices that can be used in safety- and mission-critical applications as well as increase quality and reliability by enforcing software development practices and processes.

IAR Systems

http://www.iar.com
31 January 2010 - Defects lurk in requirements: Reduce project costs with disciplined requirements engineering
Developing and integrating medium- to large-scale military and aerospace systems are daunting tasks. The systems unite various disciplines, subject-matter experts, customers, support personnel and managers over long development lifecycles. Breaking down an initial vision from an operational concept to a polished and robust fielded product takes disciplined execution, technical ingenuity and tenacity.

The Mil-Aero Command Post

http://community.mae.pennnet.com
03 November 2009 - Going For Golden - Tracing Requirements with LDRA's TBreq
Let’s say you’re new to a company, or you’re proposing a new product. Engineering and manufacturing will demand a requirements document. And an environment analysis (remember SWOT?) And a competitive analysis. And a business/ROI analysis. And a marketing plan. And a sales plan. Make that a forecast. For five years, accurate to 10% or else you’ll get called on the carpet. The article will explain more about the approached you can take.

Embedded Technology Journal

http://www.embeddedtechjournal.com
19 October 2009 - Security and C language: fix it, don't nix it
Critics who claim that the decades-old C programming language is inherently insecure; no so, argues E&T - as with any other software environment, programmers just have to ensure that they use security tools to fix vulnerabilities.

IET - The Knowledge Network

http://kn.theiet.org
15 October 2009 - Upgrade to DO-178B certification -- DO-178C - to address modern avionics software trends
Avionics software designers are quite familiar with the DO-178B certification process for flight software from the Federal Aviation Administration (FAA) and the European Aviation Safety Agency (EASA). However, current technology trends in software code development are requiring new verification and certification approaches, so industry and government experts are building a new certification called DO-178C to address these concerns.

Avionics Intelligence

http://avi.pennnet.com
02 October 2009 - Brainstorm: Medical Electronics
Software quality in medical applications is undergoing a transformation. In the past, some testing was done, but rigorous testing and changes only occurred if something went seriously wrong. Recent steps by lawmakers are pushing the medical industry to take a more preventative stance by threatening to heavily fine or imprison CEOs of companies not doing due diligence. Software quality is one of the areas coming under greater scrutiny. It won’t be long until a medical certification process of software is in place.

ECNMag.com

http://ecnmag.com
29 September 2009 - Software Fault Management for Medical Devices
To implement fault management and fault reduction, medical device companies need to look at a variety of different methodologies focused on at least two levels: fault reduction throughout the development lifecycle and fault handling at application runtime. During the software development lifecycle, requirements traceability, static analysis, dynamic analysis, and testing strategies can all contribute significantly to software quality and fault reduction when applied at the proper stage in the development process. Once faults have been minimized using proven techniques during development, fault handling at run-time can protect safety-critical software from unforeseen events that can creep up during the operation of complex software applications.

Ecnmag.com

http://www.ecnmag.com
14 September 2009 - Using the MISRA C++ language subset in your application
This article will demonstrate how the MISRA C++ language subset mitigates the insecurities within the C++ language in an efficient, cost-effective manner. The advantages and disadvantages of subsets will be discussed and guidance given to show how some basic up front work ensures its successful deployment within a project.

embedded.com

http://www.embedded.com
10 September 2009 - Making Sense of Software of Unknown Pedigree
Software test tools have been traditionally designed with the expectation that the code has been (or is being) designed and developed following an ideal development process which adheres to a best practice approach. Such an approach implies the existence of clearly defined requirements, an adherence to corporate or international coding standards, a well-controlled development process, and a coherent test regime. The article will discuss and provide techniques how to overcome these challenges.

Dr Dobbs

http://www.ddj.com
11 August 2009 - Automating Compliance to MISRA C/C++ Standards
Thanks to their inherent flexibility and potential for portability across a wide range of hardware, C and C++ have become the languages of choice for the development of real-time embedded applications within the automotive industry. C and C++ have most of the features a software development team could wish for, and in the right hands they can be used to write well laid out, structured, and expressive code. In the wrong hands, this flexibility can lead to perverse and extremely hard to understand code.

John Day's Automotive Electronics News

http://johndayautomotivelectronics.com
07 August 2009 - Wireless Security and CERT C
A set of programming standards is designed to prevent the kinds of errors that can result in security breaches. When combined with automatic tools that can test code for compliance, firmware in wireless networked devices can be made more secure.

RTC Magazine

http://www.rtcmagazine.com
July 2009 - Legacy enhancement: Nightmare or dream?
It can be a real nightmare when a customer wants a new solution based upon legacy software for which the original developers left no clear indication of design criteria. But finding the proper analysis methodologies and tool suites can help developers get a good night's rest.

Military Embedded Systems

http://www.mil-embedded.com
June 2009 - DO-178C will arrive, then drive safety-critical software
Safety is imperative to keeping the skies friendly, and DO-178B has been keeping avionics systems engineers on the straight and narrow for years. However, as our recent interview with LDRA technical evangelist Bill StClair reveals, DO-178B’s soon-to-be-released progeny, DO-178C, will shape the safety-critical software market for companies such as the “RTOS agnostic” LDRA and others.

VME and Critical Systems

http://www.vmecritical.com
May 2009 - Software richtig verifizieren und validieren
Wenn Firmen versuchen, Prozesse zu verbessern und Softwaredefekte zu reduzieren, dann bildet ein Standard wie CMMI eine gute Grundlage, um dafür geeignete Methoden und Werkzeuge zu integrieren. Die Kategorie »CMMI Engineering Process« hebt die Anforderungsverwaltung als einen Bereich hervor, der die Implementierung, die Verifizierung und Validierung maßgeblich beeinflusst. Mit der rechten Mischung aus Methoden und Werkzeugen sind Projektteams in der Lage, die Anforderungen zu erfüllen, ihre Effizienz zu erhöhen und somit eine höhere Qualität in ihrer ausgelieferten Softwarelösung sicherzustellen.

Elektoniknet

http://www.elektroniknet.de
May 2009 - Seaweed Systems adopts LDRA tool
Seaweed Systems is a supplier of High Performance OpenGL graphics drivers and devices to the Military and Aerospace industries for use in safety critical applications, such as flight deck instrumentation. LDRA assisted them in capturing the DO-178B Level A structural coverage data across the entire Seaweed Systems software while executing their automated test suite and Seaweed has full support for any OS using LDRA.

Military & Aerospace Electronics

http://mae.pennnet.com
May 2009 - Emerging CERT C Offers Security Assurance for Networked Mil Systems
Security vulnerabilities are an increasing concern for “connected” systems like military software radios and other networked defense platforms. The emerging CERT C coding standard provides new levels of security assurance to such systems.

COTS Journal

http://www.cotsjournalonline.com
29 April 2009 - Requirements Management Reduces Software Defects and Improves Code Quality
Before I become a software consultant, I spent over 10 years in industry developing and testing software. Back then the "waterfall" process dominated software development with its distinct phases of analysis, design, code and test. More will be explained in the article.

Embedded.com

www.embedded.com
April 2009 - ENSCO employs LDRA tool suite for aerospace applications
ENSCO’s Innovative Systems Solutions (ISS) Division, is a leading provider of solutions for internet development, e-commerce, automated equipment and process controls and mission-critical sofware development and engineering. Due to the ease of use of the tool they can have a tester up and running within 3 – 10 days and the tools assisted with a 50% improvement in performance using the LDRA tool suite.

Military & Aerospace Electronics

http://mae.pennnet.com/
April 2009 - Neptec selects LDRA software for U.S. space shuttle project
Neptec is a leader in the design, development, and integration of mission-critical real-time software, harsh environment electronics and digital signal processing. They required a tool that had extensive and detailed reporting facilities for audit purposes and which was easy to use and configure through the graphical user interface.

Military & Aerospace Electronics

http://mae.pennnet.com
April 2009 - Is It Safe to Code?
The article which starts on p16 discussed "The CERT C Standard: Lessons In Etiquette and Protocol For Building Secure Applications From the Start."

Software Test & Performance

http://www.stpmag.com
March 2009 - Automatisierung der Einhaltung der MISRA C/C++ Standards
Genauso wie physikalische Komponenten einer statistischen Analyse zur Bestimmung der Ausfallzeit bedürfen, muss auch untersucht werden, inwieweit für Software eine Ausfallzeit tolerierbar ist. Der MISRA-C-Standard hat viel dazu beigetragen, Qualität in der Software-Entwicklung überprüfbar zu machen.

Elektronik Automotive

http://www.elektroniknet.de
March 2009 - Zero Defect Software Development
Zero Defect Software Development (ZDSD) is a results-oriented process that emphasizes the analysis, testing, and reporting of the causes of defects. It evolved from the commitment to providing “five-nines” (99.999%) reliability for mission critical applications. It supplants the traditional approach of reacting to undesirable effects and treating symptoms while trying to manage verification using trend analyses or simply tracking the occurrences of defects.

Advanced TCA Newsletter

http://www.atcanewsletter.com
March 2009 - Does your software warrant a safety standard?
If your application isn’t safety critical, you may still benefit from practicing software verification. The aerospace and automotive industries are well known for the rigorous software quality standards to which they must adhere, but developers of non-safety critical systems can also benefit from the type of standards employed within these industries. In addition to producing reliable software, development costs can be contained and requirements met more easily by observing a software quality process.

Embedded Systems Europe

http://www.esemagazine.com
February 2009 - Implications of adopting aerospace development and verification standards
Non-aerospace industries are increasingly obliged to undertake safety-critical and safety-related analysis and testing. Companies in these industries are consequently tending to look outside their own market sector for best-practice approaches, techniques, and standards. This article examines the challenges.

Boards & Solutions

http://www.embedded-control-europe.com
27 January 2009 - Ensuring Software Safety, Reliability & Security Using Automated Software Testing
Ensuring Software Safety, Reliability & Security Using Automated Software Testing Webinar

Electronic Design

http://electronicdesign.com
13 January 2009 - Big Brother?
Writing software is a tricky business, particularly if the code being produced is intended for application in a safety critical environment. In these applications, you don’t want the code to crash when it encounters unexpected conditions...

New Electronics

http://www.newelectronics.co.uk
02 January 2009 - Why Use Software Verification?
Developers of nonsafety critical systems can benefit from the type of rigorous standards employed within the aerospace and automotive industries.

Control Engineering

http://www.controleng.com
01 December 2008 - C and C++ Tools Reduce Code Errors
Tools find problems before you compile code. Programmers now have many tools that help reduce or eliminate problems. Unfortunately, they might not know these tools exist. In 1998, the UK's Motor Industry Software Reliability Association (MISRA) published their standard for the C language to promote 'safe C' in the UK automotive industry.

Ecnmag.com

http://www.ecnmag.com
01 December 2008 - MISRA C++ im eigenen Projekt einführen
Alle Programmiersprachen enthalten Aspekte, die unvollständig spezifiziert, mangelhaft festgelegt, oder so definiert sind, dass Compilerimplementierungen ein unterschiedliches Verhalten für so ein spezifisches Sprachkonstrukt zeigen. Jede dieser Unsicherheiten (Insecurities) kann zu einem unvorsehbaren Programmverhalten führen. C++ ist da keine Ausnahme. Dieser Beitrag zeigt wie die MISRA C++-Sprachuntermenge die inhärenten Unsicherheiten von C++ in effizienter, kosteneffektiver Weise abmildert und bietet Leitlinien für den erfolgreichen Einsatz in einem Projekt.

Elektronikpraxis

http://www.elektronikpraxis.vogel.de
November 2008 - Tools and Processes Round out the MILS Puzzle
Proper processes and tools must form part of the MILS puzzle. They’re needed to ensure rigorous static and dynamic analysis and verification needed to match specified security requirements and properties.

COTS Journal

http://www.cotsjournalonline.com
01 November 2008 - Adopting Aerospace Development and Verification Standards for Software
An ever-increasing reliance on software control has meant that many companies from non-aerospace business sectors (automotive, nuclear power, MRI scanners, financial systems) that do not have a traditional requirement for sophisticated software development processes now find themselves compelled to undertake safety-critical and safety-related analysis and testing.

Embedded Technology

http://www.embeddedtechmag.com
September 2008 - Why use Software Verification?
Developers of nonsafety critical systems also benefit from the type of rigorous standards employed within the aerospace and automotive industries. In addition to producing reliable software, costs can be contained and requirements met more easily by adhering to a software quality process.

Electronics Products and Technology

http://www.ept.ca
06 August 2008 - Does Harry Use Tools?
In England there is a phrase used to describe a significant sub-class of embedded engineers - "Fred in a shed." It is the guy who works for himself and carries out contract work for a range of different people.

Embedded Technology Journal

http://www.embeddedtechjournal.com
25 July 2008 - Gap Analysis Strengthens Link Between Requirements and Verification
Gap Analysis is a technique regularly used in business to ascertain the maturity of working processes and to identify areas for improvement. One area that is regularly flagged by gap analyses of software projects is the troubling field of requirements traceability, a key discipline for safety-critical projects.

COTS Journal

http://www.cotsjournalonline.com
July 2008 - Legacy code in the security-critical age
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.

Military Embedded

http://www.mil-embedded.com
July 2008 - Software Fault Management for Medical Devices
Because we now rely on medical devices so heavily and because the devices’ software is so critical to their operation, software fault management and the ability to reduce faults throughout the development lifecycle have become hot-button issues.

RTC Magazine

http://www.rtcmagazine.com
10 June 2008 - Shortening the Rope - LDRA Checks Cert C and MISRA C++
Once upon a time, a man was given a rope and was told that it would be useful for many things. That most anything could be done with that rope. And the man tried it out, found some things easy to do – tying a bow, for example – and some things hard – intricate cat’s cradle, for example.

Embedded Technology Journal

http://www.embeddedtechjournal.com
09 May 2008 - Embedded software applications challenge test limits
Technical evangelist Bill St. Clair discusses the development of embedded software for avionics and automotive applications.

Test and Measurement

http://www.tmworld.com
March 2008 - Wing Ice Protection System (WIPS) Tool Chain
The Wing Ice Protection System is being developed by Ultra Electronics Controls with Datel providing the software. The system provides electro-thermal ice protection to the leading slats of the Boeing 787 Dreamliner in response to pilot and automated ice detection triggers.

Ultra Datel Website

http://www.ultra-datel.com
March 2008 - Engine Ice Protection System (EIPS) Tool Chain
The Engine Ice Protection System is being developed by Ultra Electronics Controls with Datel providing the software. The ice protection system is a thermo-electronic controller replacing typical bleed air systems with a more efficient and controllable electronic controller.

Ultra Datel Website

http://www.ultra-datel.com
 

Back to Newsroom