The EN 5012x series of functional safety standards (EN 50126, EN 50128, EN 50129) have become the dominant railway functional safety reference. Its requirements and processes are becoming increasingly familiar across the world. Take an in-depth look at how the key software development and verification process activities required by the standards, and how the automation offered by the LDRA tool suite can assist in proving compliance in a cost-effective manner.
Login or register to viewISO 26262 “Road vehicles – Functional safety” was updated in 2018 to address a sharp increase in the complexity and demand for automotive programmable electronic systems. Read an overview of the key software development and verification process activities required by the standards, and the role of automated tools.
Login or register to viewSoftware test tools have been traditionally designed with the expectation that the code under test is designed and developed following an ideal development process. Software Of Unknown Provenance (SOUP) – legacy or outsourced software and libraries – turns that ideal process on its head. Read how an integrated and automated tool suite can support a process to ensure that SOUP meets modern functional safety, security, and coding standards.
Login or register to viewCost effective software certification for automotive cybersecurity
Login or register to viewInsecure coding practices and undefined behaviours that can lead to exploitable vulnerabilities and unreliable applications. Read how the application of the CERT C coding standard can help to avoid them.
Login or register to viewWith recent advances in automation, software is no longer a bit-part contributor to electro-mechanical systems. It is now the underlying technology providing functional safety in many market segments. Take an in-depth look at why IEC 61508:2010 “Functional safety of electrical/electronic/programmable electronic safety-related systems” is widely accepted as a reference standard, and how an automated, integrated set of tools can help achieve compliance with it.
Login or register to viewISO 26262 “Road vehicles – Functional safety” was updated in 2018 in response to an explosion in automotive programmable electronic system complexity and the associated risks to public safety. Take an in-depth look at the key software development and verification process activities required by the standards, and how the automation offered by the LDRA tool suite can assist in proving compliance in a cost-effective manner.
Login or register to viewThe term “medical device” is broad ranging. Small wonder that medical device software now permeates a huge range of diagnostic and delivery systems, and applying its objectives to a specific set of circumstances can be challenging. Take an in-depth look at how an automated, integrated set of tools can help.
Login or register to viewHousehold appliances are becoming ever more smart, and the demand for new features is seemingly endless. In particular, connectivity that brings remote monitoring or control is now commonplace. Read an in-depth review of how its principles offer sound guidance in the establishment of a high quality software development process, and how the automation offered by the LDRA tool suite can assist in proving compliance in a cost-effective manner.
Login or register to viewRead how ASPICE promotes best practice processes for automotive software development. Understand how the Capability Maturity Model (CMM) helps describe the capacity of the behaviours, practices and processes of an organization to produce required outcomes. Learn how the LDRA tool suite underpins these principles through requirements traceability and automated verification and validation activities.
Login or register to viewMISRA C is a language subset of the C programming language (often referred to colloquially as a “coding standard”). Understand how the 2013 version of MISRA C:2012 differs from MISRA-C:2004.
Login or register to viewInsecure coding practices and undefined behaviours that can lead to exploitable vulnerabilities and unreliable applications. Gain an in-depth understanding of how automating the application of the CERT C coding standard can help to avoid those issues.
Login or register to viewOver the past few years, there has been a proliferation of automotive electrical and/or electronic (E/E/PE) systems such as adaptive driver assistance systems, anti-lock braking systems, steering and airbags.
Login or register to viewWhether working with the Adaptive or Classic Platform, compliance with functionality safety standards – typically ISO 26262 – is a separate but complementary issue. Take an in-depth look into the background of both platforms, and discover how an automated, integrated tool suite can support development in accordance with both AUTOSAR and ISO 26262 concurrently.
Login or register to viewThe AUTOSAR family of standards expanded in 2017 to embrace the new “Adaptive Platform,” with the existing development branch renamed “Classic Platform.” Take an in-depth look at how an automated, integrated set of tools can help ease the development path of AUTOSAR applications for both platforms.
Login or register to viewThe AUTOSAR family of standards expanded in 2017 to embrace the new “Adaptive Platform,” with the existing development branch renamed “Classic Platform.” Learn from this overview of how an automated, integrated set of tools can help ease the development path of AUTOSAR applications for both platforms.
Login or register to viewIEC 13849 is a functional safety standard that applies to control systems software. Learn of its relationship with EN 62061, IEC 61508, and IEC/ISO 17305, how it is applied, and how automated tools can help with compliance.
Login or register to viewMost of us are familiar with multicore processors and the benefits they have brought to our daily lives. They have been available in personal computers since the early 2000s [1], and NVIDIA was promoting their benefits in mobile devices as long ago as 2010 [2]. Multicore designs address the problem of processors hitting the ceiling of their physical limitations in terms of their clock speeds and how effectively they could be cooled and still maintain accuracy. By moving to extra cores on a single processor chip, manufacturers avoided problems with the clock speeds by effectively multiplying the amount of data that could be handled by the Central Processing Unit (CPU).
Login or register to viewThe guidance document DO-178 “Software Considerations in Airborne Systems and Equipment Certification”1 2 was first published in 1982, re-written in 1992 as DO-178B and updated in 2011 as DO-178C, to reflect the experience accrued to meet today’s aviation industry needs. LDRA has participated extensively on both the DO-178B3 and DO-178C4 committees over nearly two decades. Mike Hennell, LDRA’s CEO, was instrumental in the inclusion of several test measurement objectives in the standard, including those relating to structural coverage analysis. The LDRA tool suite® was itself a forerunner in automated verification for certification to both DO-178B, and to its companion standard, DO-2785 for ground-based systems.
Click to viewThe term “medical device” is broad ranging. Small wonder that medical device software now permeates a huge range of diagnostic and delivery systems, and applying its objectives to a specific set of circumstances can be challenging. Learn from this overview how an automated, integrated set of tools can help.
Login or register to viewEmerging technological trends promise productive, comfortable, and prosperous lifestyles across India. However, the rate of adoption of technologies including autonomous things, IoT, and AI is less promising due to a lack of competence in the development, validation and maintenance of complex intelligent systems. Take an in-depth look at the skill-and opportunity-related challenges associated with these emerging technologies, future job opportunities, and an objective view of the sectors that will always be in demand.
Login or register to viewThis document outlines the key software development and verification process activities of the standards, and uses LDRA’s tool suite to show how automation can assist in providing compliance in a cost effective manner
Login or register to viewAdherence to IEC 62443-4-1:2018 helps to enhance the security of software-dependant devices deployed in industrial automation control systems. Learn how it encourages a “shift left” approach to the application of security measures, and how the use of proven tools provides assurance, underpins confidence, and improves development process efficiency.
Login or register to viewMISRA C:2023 collates MISRA C:2012 and its addenda, including AMD4 with its attention to multithreading and atomic types in support of C11 and C18. This white paper explains these and other changes that keep the MISRA C Guidelines relevant to how embedded developers use the C language today.
Login or register to viewDO-178C covers the complete software lifecycle – planning, development and integral processes to ensure correctness and robustness in airborne application software. The breadth and depth of its guidance can be daunting for the experienced and newcomers alike. Learn from this overview how an automated, integrated set of tools can help.
Login or register to viewMISRA C is a language subset of the C programming language that is developed and maintained by the Motor Industry Software Reliability Association (MISRA). It is colloquially referred to as a “coding standard” – but never by MISRA themselves. Originally designed to promote the use of the C language in safety-critical embedded applications within the motor industry, the original version, MISRA C:19981, was released in 1998 to target C90.
Login or register to viewLike the automotive, medical device and process industries, the railway sector based their functional standard on the industry agnostic functional safety standard IEC 615085. The resulting EN 5012X series has become the dominant railway functional safety standard, and its requirements and processes are becoming increasingly familiar across the world. The international standards IEC 622786, IEC 627797, and IEC 622808 very largely mirror EN 50126, EN 50128 and EN 50129 respectively and can be considered to be identical in the context of this document.
Login or register to viewSoftware is almost infinitely malleable, and best practice in software development is constantly evolving. Standards and reference frameworks are necessary to provide points of reference. Without them, the coordination of the multitude of development organisations in the automotive ecosystem would be almost impossible
Login or register to viewAutomotive SPICE consists of a set of technical standards that collectively form a framework to measure the maturity of software development processes. ISO 26262 also promotes the development of high quality software but with the specific aim of ensuring that developments are adequately safe. Learn how the LDRA tool suite can underpin a development life cycle that is demonstrably compliant with both standards.
Login or register to viewSoftware is no longer a bit-part contributor to electro-mechanical systems. It is now the underlying technology providing functional safety in many market segments. Gain an overview of why IEC 61508:2010 “Functional safety of electrical/electronic/programmable electronic safety-related systems” is widely accepted as a reference standard, and how an automated, integrated set of tools can help achieve compliance with it.
Login or register to viewMISRA C is a language subset of the C programming language (often referred to colloquially as a “coding standard”). Understand how the 2013 version of MISRA C:2012 has since evolved through the publication and integration of amendments and the publication of supporting documents, including MISRA:Compliance.
Login or register to viewIt would be easy to get bogged down in the claims and counter-claims about whether Object Code Verification is useful in the context of DO-178C DAL A applications, or not. This DER’s perspective of Object Code Verification with respect to DO-178C Annex A Table A-7 Objective #9 may help to cut through the confusion.
Login or register to viewIt is inevitable that the control and data flow of object code will not be an exact mirror of the source code from which it was derived, and so proving that all source code paths can be exercised reliably does not prove the same thing of the object code. Learn why that gives rise to the potential for dangerous inconsistencies between developer intent and executable behaviour, and why Object Code Verification represents the best available technique for offsetting that potential – whatever the application.
Login or register to viewThe EN 5012x series of functional safety standards (EN 50126, EN 50128, EN 50129) have become the dominant railway functional safety reference. Its requirements and processes are becoming increasingly familiar across the world. Gain an introductory insight into how the key software development and verification process activities required by the standards, and how the automation offered by the LDRA tool suite can assist in proving compliance in a cost-effective manner.
Login or register to viewRTCA DO-278A (also known as EUROCAE ED-109A) “Guidelines for Communication, Navigation, Surveillance, and Air Traffic Management (CNS/ATM) Systems Software Integrity Assurance” is used in developing software associated with ground-based systems that are involved with aircraft operations
Login or register to viewToday’s complex software-based safety critical systems depend on software tools for automation and efficiency. “Tool qualification” is a generic term to describe a process designed to ensure that the risk of a tool error impacting the safety of a system is acceptably low – either because the errors are few, or because they cannot impact safety. Most functional safety standards define processes to achieve tool qualification by considering the application of the tool, and the environment in which it is deployed. The application considerations are designed to ensure that the tool is used in such a way that potential errors are either avoided or detected. The environmental perspective looks to ensure that the installed tool works as part of the broader tool chain to which it contributes, building confidence and trust in the tool and its use. All standards have a classification phase to establish the required confidence in the tool and a qualification phase that provides this level of confidence for some or all of its functionality. However, the classification and qualification methods differ in some details.
Click to viewToday’s complex software-based safety critical systems depend on software tools for automation and efficiency. “Tool qualification” is a generic term to describe a process designed to ensure that the risk of a tool error impacting the safety of a system is acceptably low – either because the errors are few, or because they cannot impact safety. Most functional safety standards define processes to achieve tool qualification by considering the application of the tool, and the environment in which it is deployed.
Login or register to viewDef Stan 00-055 specifies the requirements for achieving, assuring and managing the Design Integrity of Programmable Elements (PE) in compliant systems. Read how the LDRA tool suite supports the validation and verification of software to demonstrate compliance with the standard.
Login or register to viewSecurity has become a primary challenge in aerospace system development and certification. Increasingly the aviation network, as well as the aircraft, is connected to the internet (nose-to-tail) and other private networks. Learn how the the international guidelines DO-326A/ED-202A became the sole Acceptable Means of Compliance (AMC) for FAA and EASA cybersecurity airworthiness certification. Understand the security development and risk assessment process it defines. And learn of the role of structured consultancy in the standard’s application.
Login or register to viewThere are many different types of verification and validation activity required to ensure and demonstrate compliance with functional safety and cybersecurity standards. The reuse of test components throughout the development process can ensure efficient and complete testing, save time, and reduce costs. Learn how both the National Instruments test platform and the LDRA tool suite can help to achieve those aims.
Login or register to viewA chance to revisit a proposal for a revised approach to the derivation of IEC 61508 Safety Integrity Levels (SILs), based on reasoned principles.
Login or register to viewThe significance of Object Code Verification : An overview Verification and Validation practices championed by functional safety, security and coding standards ( including IEC 61508[1], ISO 26262 [2], IEC 622304[3], MISRA C [4] and C++ [5]. CWE [6]
Login or register to viewFor most ISO 26262 compliant applications the existence of a TUV certification is adequate evidence of the suitability of software test tools. However, for ASIL D applications (and optionally, for less demanding ASILs) the standard provides details of how tool qualification should be achieved in the context of a project tool chain . Learn how LDRA can help ease the path to the qualification of their tools for automotive applications.
Login or register to viewSeveral civil aviation standards including DO-178C require that software tools are qualified in the context of a project tool chain in accordance with the principles described in DO-330. Learn how LDRA can help ease the path to the qualification of their tools for civil aviation applications.
Login or register to viewISO 26262 requires any threats to functional safety to be adequately addressed, implicitly including those relating to security threats but it gives no explicit guidance relating to cybersecurity. Gain an overview of how SAE J3061, predecessor to ISO/SAE 21434, was introduced to address that deficiency.
Login or register to viewThere are many different elements to consider when seeking medical device approval. Read considered thoughts from both QNX and LDRA on how dynamic code analysis can support demonstrations of compliance with safety requirements, and the key capabilities to consider in the selection of dynamic analysis tools. Tables mapping development activities to the objectives of IEC 62304 are also presented in support of that selection process.
Login or register to viewThe RTCA/DO-331 “Model based Development and Verification Supplement” to DO-178C and DO-278A offers opportunities to leverage the strengths of model based development under DO-178C. Get a glimpse of the DER’s view of the conditions under which model verification can be used to partially satisfy EOC verification objectives, and the areas which should be closely attended to in order to satisfy the regulatory requirements.
Login or register to viewISO 13849 defines a machine control system as “[a] system which responds to input signals from parts of machine elements, operators, external control equipment or any combination of these and generates output signals causing the machine to behave in the intended manner.” Given the breadth of that definition, there’s no wonder that applying its objectives to a specific set of circumstances can be challenging. Learn about the development and verification process activities required by the standard, and the role of automated tools.
Login or register to viewTake an in-depth look at how DO-178C covers the complete software lifecycle – planning, development and integral processes to ensure correctness and robustness in airborne application software. The breadth and depth of its guidance can be daunting for the experienced and newcomers alike. Learn how an automated, integrated set of tools can help.
Click to viewIt’s hard to escape the headlines around Modular Open Systems Approach (MOSA), open standards, and individual initiatives such as those from The Open Group FACE™ Consortium, the creators of the FACE Technical Standard. In 2004, the United States government started a large effort to define and implement MOSA as a requirement within military systems with the definitive document titled MOSA Principles defined in OSD Open Systems Joint Task Force Program Manager’s Guide: A MOSA to Acquisition.
Login or register to viewEmail: info@ldra.com
EMEA: +44 (0)151 649 9300
USA: +1 (855) 855 5372
INDIA: +91 80 4080 8707