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.
Industry automations depend on Electrical/Electronic/Programmable Electronic (E/E/PE) Systems and these systems have become more and more dependent on embedded software. The reliability and risk posed by these systems became important and led to the development of the IEC 61508 standard.
This webinar will focus on IEC 61508 – Part 3 –Software Requirements, Design, implementation and Testing for E/E/PE systems and IEC 61508 – Part 7 - Overview of Techniques and Measures for Software Safety as discussed in Part 3. We also focus on the Safety Integrity Levels (SIL1 – SIL4) which specifies the necessary safety measures for avoiding an unreasonable residual risk, with SIL4 representing the most stringent level. This will focus on how software validation compliance with IEC 61508 standards can be achieved.
IEC 61508-3:2010 applies to any software forming part of a safety-related system or used to develop a safety-related system. Compared to Edition 1 of the standard IEC 61508:2010 focuses of forward and backward traceability with respect to the requirement specification and the actual implementation. This new standard also stresses the importance of structural coverage like Statement, Branch /Decision and MC/DC (Modified Condition/Decision Coverage). We pay special attention towards these aspects of the software development lifecycle and how the impact on productivity can be minimised following the adoption of IEC 61508 software development standards.
LDRA, a pioneer and global leader in automated, requirements-based software verification, source code analysis, run time error prevention and test tools covering the full development lifecycle, will share their experiences in achieving successful compliance with IEC 61508 standard for industrial software.
Improving your software engineering process without breaking the budget or project timeline
Since medical devices increasingly employ sophisticated software, whose failure to function correctly could result in death or serious injury, both the United States and the European Union are taking action to ensure that medical devices comply with rigorous standards. For medical device developers, increased government scrutiny and new international standards create a compliance burden that challenges time-to-market goals and threatens to explode software development costs.
LDRA, a pioneer and international leader in automated, requirements-based software verification, source code analysis, run-time error prevention and test tools, invites you to a webinar that helps you meet the new medical standards through better process management-a solution that cuts costs while improving software quality.
Starting with a brief overview of new government standards such as IEC 62304, LDRA will show you how to manage your product development throughout the entire software development lifecycle. Using requirements traceability, you will learn how to trace your requirements through design, code analysis, testing, verification, and documentation to achieve the compliance your device needs for today's standards.
Safety is one of the key issues of future automobile development. Now a days automotive manufactures are introducing many active safety features like ABS (anti-lock braking system), traction control, cruise control and passive safety features like airbags and seatbelts etc. With the trend of increasing complexity, software content and mechatronic implementation, there are increasing risks from systematic failures due to malfunctioning of software and hardware components. V model based software development processes focuses 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.
The webinar will explain the purpose of object code verification, highlight the nature of problems it can expose, and discuss how the management of requirements and their traceability can be extended right through to object code verification. Through practical examples we will show how tools can be used to automate the whole of that process from requirements traceability right through to object code verification challenges. Specifically, we will follow the process of adding additional test cases to obtain 100% object code coverage and mapping those test cases to your high level requirements for traceability.