Automate Safety-Critical Standards Compliance for: DO-178B/C, IEC 62304, IEC 61508, ISO 26262, EN 50128 and IEC 60880 projects
If you are looking to bridge the gap between requirements and testing then look no further, LDRA has partnered with Visure to automate requirements engineering, software verification and compliance management.
The growing complexity of developing safety-critical systems encourages companies to review their current development environment and adopt new tools/processes capable of supporting and enforcing a compliance process. In this new landscape, implementing an efficient requirements-based testing process is critical to delivering high quality products on time and within budget.
What will I learn?
Verification Techniques that Improve Code Quality, Developer Productivity, and Enable Certification/Qualification
The conflicting demands for productivity and quality in safety- and security-critical software development environments have driven software development teams to look for automated solutions in the areas of requirements engineering, model-based design, code generation, and system/software verification. These technologies are key to ensuring productivity and quality in environments that enforce both overall safety- and security-related processes and compliance to standards such as DO-178B/C in aerospace, IEC 61508 in industrial applications, ISO 26262 in automotive, IEC 62304 for medical device software, and EN 50128 for rail transportation. To achieve the twin goals of productivity and quality, best practices in these environments have evolved to focus on bi-directional traceability from requirements through verification.
In this presentation, we will review verification criteria for both hand-written and automatically generated embedded code. We will discuss target verification tools, techniques, and services for languages ranging from C/C++, Java, Ada and Assembler that ensure embedded code matches the design and satisfies requirements, even in highly iterative or agile development environments. Integration with complementary tools such as MathWorks MATLAB/Simulink, Esterel SCADE and IBM Rational Rhapsody will be presented. We will also show how these tools and techniques can streamline the development process to enhance both developer productivity and the quality of the resultant code.
Model-Based Design & Verification for DO-178C Using Simulink and the LDRA Tool Suite
In this webinar learn how Model-Based Design and code verification technologies streamline flight software development for DO-178C, the FAA’s upcoming flight software certification standard. Simulink’s family of products enables simulation, code generation, and verification using models. The LDRA tool suite lets you assess code coverage and conduct low-level testing on target platforms, analyze software for standards conformance, and generate and manage artifacts for compliance. This webinar will introduce new integrations involving MathWorks and LDRA products that automate development and verification activities specified in DO-331, Model-Based Design supplement to DO-178C.
About the Presenters:
Shan Bhattacharya is a Business Development Manager for LDRA. He also manages the US Field Engineering team. He has worked for major defense system integrators as a software engineer, software lead and an IPT lead. As a Field Applications Engineer for over five years with LDRA he has deployed LDRA’s software solutions for a lot of major defense, commercial avionics, medical device, and automotive vendors to meet industry software certification.
Tom Erkkinen is an Embedded Applications Manager at MathWorks. He has more than 20 years embedded system experience including control system software development at Lockheed and NASA.
What You DON’T Know Can Hurt You:
What you NEED to know about MISRA C:2012
If you’re developing safety-critical applications, you can’t afford to take chances. But commercial pressures don’t go away just because you’re diligent. The latest version of the MISRA standard lets you take advantage of more C features while helping you mitigate risk for safety-critical automotive, medical, industrial or mil/aero applications.
Anyone developing software with the potential to put lives at risk has an obligation to take every reasonable step to ensure that the work is sound. Adhering to standards is one key step in that process, and MISRA is the internationally recognized foundation for best coding practices. But features of the language that are designed to increase application performance, developer productivity and implementation flexibility are often just the features that the standard disallows. MISRA C:2012 changes the game.
Following immediately on the heels of the new standard’s release, Chris Tapp, chairman of the MISRA C++ Committee, member of the MISRA C Working Group and one of the authors of MISRA C:2012, will tell you what you need to know:
Chris Tapp is a Field Applications Engineer at LDRA
Shan Bhattacharya is a Business Development Manager for LDRA
John Mchale - Editorial Director, OpenSystems Media
Focusing on Traceability in Software Development for Safe Medical Devices
The IEC 62304 standard was developed to address safety concerns triggered by the rising number of devices in the medical industry that use software. Checking each stage of software development to help create a functionally safe medical device is plain common sense, but the collation of evidence of compliance with the standard itself can be a real headache.
Traceability is key to the success of medical device approval, and yet too often it tends to be a background task. This webinar explains why making traceability the focal point of your development efforts from the beginning of development and throughout the project lifecycle can help ensure that the collation of evidence becomes second nature rather than a secondary overhead.
Join QNX Software Systems and LDRA for this web seminar as we offer insights using examples from our experience with safe systems, not only in the medical devices sector, but also in other fields.
Mark Pitchford, Field Applications Engineer, LDRA
Mark Pitchford has over 25 years' experience in software development for engineering applications. He has worked on many significant industrial and commercial projects in development and management, both in the UK and internationally including extended periods in Canada and Australia. For the past 10 years, he has specialised in software test and works throughout Europe and beyond as a Field Applications Engineer with LDRA.
Chris Ault, Product Manager, QNX Software Systems
Chris Ault is a product manager at QNX Software Systems, where he focuses on the medical and general embedded markets.
Prior to joining QNX, Chris worked in various roles, including software engineering, engineering management, product management, and technical sales, at AppZero, Ciena, Liquid Computing, Nortel, and Wind River Systems.
Achieving Road Vehicle Safety Certification using ISO 26262
Safety is one of the key issues facing automobile development in the future. Over the years automotive manufacturers have steadily introduced many active safety features such as ABS (anti-lock braking system), traction control, cruise control and passive safety features such airbags and seatbelts, etc. Today automotive development continues at a pace with the current development trend for increasing complexity, software content and mechatronic implementation, which brings with it increasing risks from systematic failures due to malfunctioning of software and hardware components. Software development processes focus on lifecycle traceability between the sub-phases of the software lifecycle and its compatibility with system and hardware lifecycles. ISO 26262 includes guidance to avoid these risks by providing feasible requirements and processes.
This webinar will focus on the Product Development phase i.e. Part 4 - System level and Part 6 - Software level of the ISO 26262 process. The focus will also be on achieving lifecycle traceability between sub-phases and the compatibility with system and hardware lifecycles by performing integration and system level verification. We will also focus on the Automotive Safety Integrity Levels (ASIL) which specifies the necessary safety measures for avoiding an unreasonable residual risk, with ASIL D representing the most stringent level. This will focus on how software verification and validation compliance with ISO 26262 standards can be achieved.
A Practitioner's Guide to Critical Software Certification
Covering technical methodologies and techniques for developing critical software in compliance with DO-178B/C, IEC 61508, CENELEC, ISO 26262 and FDA guidelines we will highlight the processes, procedures and tools used to achieve critical software certification.
Using practical examples, we remove the mystery and confusion surrounding embedded systems development, lifecycle traceability, verification, reporting and quality assurance. We pay special attention to requirements traceability, coding standards adherence, independent verification, testing and structural coverage analysis. Finally, we will discuss how these capabilities are used in achieving the next generation of certification.
Achieving Rail Safety Certification using EN 50128:2011
Safety is one of the key issues of railways applications. Railway safety is concerned with the protection of life and property through regulation, management and technology development of all forms of rail transportation. With involvement of modern technology, more and more electronics are added for building Interlocking system, signalling & train control systems, vital switch controller and anti collision systems (ACS). With the trend of increasing complexities, software content and mechatronic implementation, there are increasing risks from systematic failures due to malfunctioning of software and hardware components.
This webinar will focus on EN 50128:2011 for Railway applications — Communications, signalling and processing systems — Software for railway control and protection systems. Some key areas which are included are software design, implementation and testing for electrical/electronic/programmable electronic systems used in Railway applications. We will also focus on the Safety Integrity Levels, which specify the necessary safety measures for avoiding an unreasonable residual risk, with 4 representing the most stringent level.
LDRA, a pioneer and global leader in automating the verification and requirements traceability of standards objectives such as EN 50128:2011 will show how automated tools and techniques can assist in the certification process.
DO-178C/DO-331: Fast Track to Certification using Model-Based Design
The Impact of New Standards and Potential Pitfalls for Developing and Verifying Flight Code
The introduction of RTCA/DO-331 Model Based Development and Verification Supplement to DO-178C and DO-278A offers new opportunities to leverage the strengths of Model-Based Design under RTCA/DO-178C. The concept of simulation test cases for reuse and associated structural coverage analysis on Executable Object Code (EOC) to obtain test coverage credit allows for the painstaking work of model verification to help achieve EOC verification objectives.
This webinar explores the conditions under which model verification can be re-used to satisfy EOC verification objectives using Simulink and LDRA tool suite, and it also identifies areas which should be closely attended to in order to satisfy the regulatory requirements.
Achieving Road Vehicle Safety Certification using ISO 26262
- Jointly hosted by LDRA and Green Hills Software -
Safety is a key issue for road vehicle development. The automotive manufacturers and tier one suppliers are introducing more active safety features including collision avoidance, adaptive cruise control, pedestrian protection systems and integrating them with the passive safety features like airbags and seatbelts. These features are introducing additional complexity in software content and mechatronic implementation. As a consequence, there are increased risks of systematic failures due to malfunctioning of software and hardware components. V-model-based software development processes focus on traceability between the sub-phases of the software lifecycle and their compatibility with system and hardware lifecycles. The ISO 26262 automotive standard includes guidance to avoid these risks by providing feasible requirements and processes.
This webinar will concentrate on the Product Development phase, specifically Part 4 - System level and Part 6 - Software level of the ISO 26262 process. The focus will also be on achieving lifecycle traceability between sub-phases and the compatibility with system and hardware lifecycles by performing integration and system level verification. An emphasis will be placed on the Automotive Safety Integrity Levels (ASIL), which specify the necessary safety measures for avoiding an unreasonable residual risk, with ASIL D representing the most stringent level. This will focus on how software verification and validation compliance with ISO 26262 standards can be achieved, by looking at both the software architecture and the methods to achieve this goal more easily.
A Guide to Using Model-Based Design in Embedded Real-time Environments for Safety Critical Applications
This webinar will cover verification criteria and goals regarding the increasing portion of embedded code that has been directly derived from models. This has been driven in part due to high fidelity modeling tools and code generation tools like Simulink and Embedded Coder from MathWorks. These tools are extremely powerful in helping to show embedded code matches the model, even in cases in which the model and the application are rapidly changing. In safety critical environments, however, these tools in and of themselves are not adequate for system verification. They must be paired with embedded target-verification tools and matched with appropriate process standards.
LDRA with MathWorks support will discuss automating best practices to track code from the model to the target, ensuring that verification tasks such as code coverage are completed correctly. This is particularly important with process standards such as DO-178C, which require specific model elements to be connected to specific verification tasks and results. This traceability is critical to the certification of generated code.
Model-generated code has significantly lowered development costs and time to market. But, when it comes to safety-critical, certified systems, all code—manual and generated—must prove that it’s fulfilled system requirements and on-target testing. Using certification tools – such as the LDRA tool suite - can ensure traceability and track changes from requirements, to the model, code, verification tasks, and eventual certification of the system – saving time to market and eliminating a potential source of errors.
Developing safety critical software is difficult enough, but more and more often, developers are also now challenged with the task of developing the software so that it complies to industry standards such as DO-178B/C, IEC 61508, IEC 62304, ISO 26262 or even a company’s own internal standard. This is good news for the end users of the software, but what does it mean for the developers and how can they go about achieving this?
Many of these previously mentioned standards specify a number of ‘objectives’ or ‘requirements’ that need to be met. We will discuss these objectives and look at various ways in which they can be implemented and documented as well as also highlighting the processes, procedures and tools used to achieve critical software certification.
Using practical examples, we remove the mystery and confusion surrounding development, verification, configuration management and quality assurance. We pay special attention to requirements traceability, coding standards adherence, independence criteria, testing and structural coverage analysis. Finally, we discuss how these can assist in the next generation of certification.
The imminent adoption of DO-178C by major certification authorities presents a number of challenges for developers of certified avionics applications. Changes to the core documents, as well as understanding the corresponding supplements, can be a challenging task. And what are the best ways to ensure that your application development and verification process will lead to certification under the new standard in an efficient manner?
Join Bernard Dion, a DO-178C committee member, and Shan Bhattacharya as they explain changes coming with the adoption of DO-178C. Learn how to best tailor your development and verification process with model-based development and verification, and formal methods strategies, as well as discussing five techniques for achieving DO-178C compliance. Understand the new tool qualification requirements within DO-178C and how to best utilize tools for automatic code generation and testing on target to make sure that your safety critical avionics and defense applications are developed with the best possible approach.