Search

Avionic industry in Russian Federation faces difficulties in organizing the reliable instrumental support of development processes. State-wide active direction on digitalization of the economy doesn’t facilitate the issue solving. The choice of software tools is an important component of success while developing complex certifiable software such as aircraft onboard systems. The same situation could be observed in other industries as well. Nowadays the Russian IT-market provides a sufficient amount of different software that can cover the development lifecycle processes of complex certifiable software for avionics in a varying degree. This article analyses the current situation on Russian software market and the impact of import substitution policy of Russian Federation on software developers and consumers – industrial enterprises. Details of regulation document DO-178C for onboard software development are considered to show the importance of correct choice of project’s instrumental landscape. Certain types of specialized software tools for development processes automating are considered. Authors identified the basic groups of tool functionality that provide support for the development lifecycle of onboard software. The Russian and foreign PLM (Product Lifecycle Management) and PDM (Product Data Management) systems and other software were examined for compliance with the necessary functionality. For comparative analysis the method based on additive verification of software by criteria was proposed. Research results allowed authors to make a conclusion about current Russian software level in comparison with worldwide analogues. Also some prospects of Russian software further evolution have received justification based on results of this research. Recommendations for the directions of software development and completion are given. The analysis, presented in the article, can be useful for avionic and other industries enterprises which need to choose some software for support the development lifecycle processes in new and ongoing projects of complex systems development. Also specialists who are interested in the current state of Russian IT industry can find some valuable information in this article.

—General-Purpose GPU software is considered for use in avionics to satisfy the increased computational requirements of future systems. Therefore, it needs to be certified following the DO-178C guidance as all airborne software. In this work, we review the existing methods in the literature, we analyse their advantages and disadvantages, and we discuss how they can be combined to obtain certification with lower effort and cost. Our focus is restricted on application-level software, under the premise that successful completion of verification of avionics graphics GPU software products has been demonstrated, so their GPU compiler has been considered acceptable for these already DO-178C certified products, or existing qualified GPU compilers exist. Finally, we discuss upcoming solutions for certified general purpose GPU computing . This work was performed within the Airbus TANIAGPU Project ADS (E/200) in collaboration with the project partners Airbus Defence and Space, Madrid, Spain and CoreAVI, Canada. It was also partially supported by the European Space Agency (ESA) through the GPU4S (GPU for Space) activity, the Spanish Ministry of Economy and Competitiveness under grants PID2019-107255GB and FJCI-2017-34095 (Spanish State Research Agency / http://dx.doi.org/10.13039/501100011033) and the HiPEAC Network of Excellence.

Adaptive and Learning Agents (ALAs) bring computational intelligence to their Cyber Physical host systems to adapt to novel situations encountered in their complex operational environment. They do so by learning from their experience to improve their performance. RTCA DO-178C specifies a stringent certification process for airborne software which represents several challenges when applied to an ALA in regards of functional completeness, functional correctness, testability and adaptability. This research claims that it is possible to certify an Adaptive Learning Unmanned Aerial Vehicle (UAV) Agent designed as per a Cognitive Architecture with current DO-178C certification process when leveraging a qualified tool (DO-330), Model-Based Development and Verification (DO-331) and Formal Methods (DO-333). The research consists in developing, as a case study, an ALA embedded in a UAV aimed at neutralizing rogue UAVs in the vicinity of civil airports and test it in the field. This article is the plan to complete, by end 2022, a dissertation currently in its confirmation phase.

International audience; As the number of embedded systems has grown regularly over the past decades, the development and certification costs of safety-critical software has increased accordingly. For the aeronautics industry, certification activities are covered by DO-178C, which provides guidance for developing airborne software; and its companion document DO-330 covers the qualification of tools used for the development of such software. In this paper, we present ASTERIOS , a solution for the design, generation and execution of safety critical real-time applications; then we present the certification strategy we advocate for systems developed using our technology. This strategy relies on the use of an automated verification tool called ASTERIOS Checker , qualified in accordance with DO-330. This paper presents the technology behind the code generation engine of ASTERIOS and the verification activities automated by ASTERIOS Checker. It shows how the use of such an automated, qualified tool enables to benefit from design abstractions and relatively complex code generation engines while developing certified systems at the highest level of certification.

ARP 4754A (Guidelines for Development of Civil Aircraft and Systems) promotes modeling and simulation for aircraft systems integration, requirements validation and implementation verification. DO-331, the model-based development and verification supplement to DO-178C (Software Considerations in Airborne Systems and Equipment Certification) further endorses simulation for verification of Specification Models, Design Models and executable code. While both state that the quality of simulation should be assured, there is no particular guidance for its qualification. This paper investigates the application of IEEE Recommended Practice for Distributed Simulation Engineering and Execution Process (DSEEP) for the qualification of simulation as a tool for airborne systems engineerinng.

Avionics systems are relying more on software to control their behaviour. However, engineering such software is a complex task. Even more so due to their safety-critical nature. Aviation authorities require suppliers to provide appropriate safety assurance through the certification of compliance with DO-178C to a determined software design assurance level. Such a concern is leading the avionics software industry to consider and incorporate effective engineering methods that can support them in their certification endeavours. This paper presents a domain specific modelling language (DSML) providing a documentation infrastructure that enforces certification information mandated by DO-178C and its supplements according with the software's design assurance level. Focus is given to the conceptual model of DO-178C and its supplements, which lies behind the proposed DSML to support the features it delivers. The DSML was built and implemented as a UML profile. Three different use cases for the DSML are illustrated in an avionics case study.

As with many of the products and systems that pervade us, aircraft rely more and more on software for controlling the behaviour of their systems. In consequence, the field has seen increased work around more up-to-date, effective software engineering technologies for aiding avionics software providers in reducing software and development complexities and supporting them in their certification endeavours. However, there is a lack in the literature of reusable, comprehensive references about avionics software developments in conformance with DO-178C. Moreover, there is a need for a benchmark specification to support the evaluation of proposed engineering approaches in the field. This paper presents a software development case study of an avionics control software for a landing gear system. All the documentation for the software's requirements specification and design has been developed to conform with the DO-178C guideline and the applicable DO-331 and DO-332 supplements for model-based and object-oriented development, respectively. A requirements specification and design methodology is proposed and followed for the construction of the software in the case study. Furthermore, the paper discusses the observations, and challenges and issues experienced throughout the process.

This paper presents an approach for the formal modeling of certification processes using automatic reasoning in order to optimize the development process and to support business decision making while ensuring compliance with certification standards. The approach consists of combining formal models of the certification standard (what has to be satisfied), and models of the actual development process (how it is satisfied). A contract-based language is used to model the certification process. A SMT solver (Satisfiability Modulo Theories) is used to verify whether the certification is satisfied and to find optimization possibilities. The proposed approach is demonstrated using a case study to model a subset of the certification of a real aircraft cooling system certified under DO-178C. It is anticipated that modeling of the certification standards demonstrated in this case study would help meet the current challenge of creating new standards to certify new technologies.

Airborne systems are considered to compose a highly complex network of interconnected Cyber-Physical Systems (CPS). Following the ARP-4754A development guidelines, a series of multidisciplinary engineers have to decompose system, hardware and software requirements in order to validate their correctness. System intrinsic complexity though, imposed by CPS(s), constitutes the certification of airborne systems a difficult, time-consuming and often expensive task. In the same line, requirements traceability, validation and verification is considered to be a crucial part of certification processes for both hardware (DO-254) and software (DO-178C) components. In this paper we review challenges and solutions for software certification under the DO-178C standard using formal verification in line with new CPS analysis evolution. We describe current model-based design methodologies followed today in the aerospace domain and comment on new approaches and techniques that could accelerate the software certification processes with respect to CPS(s) requirements.

Complex products, such as an aircraft, require a large number of software projects developed in parallel. The development of airborne software, using the DO-178C, is a challenge and metrics can help the evaluation and adherence. This paper provides a summary of master thesis approved in the Brazilian Aeronautics Institute of Technology. The thesis proposes the creation of a set of metrics that evaluates the compliance with DO-178C objectives related to the development phase of the airborne software projects, monitoring delays in the certification schedule of the aircraft. These metrics were created using the PSM model (Software and Systems Measurement Practice) as guidance. Finally, a case study is performed using the metrics in an actual airborne software development.

The development and verification of safety-critical systems increasingly relies on the use of tools which automate/replace/ supplement complex verification and/or development tasks. The safety of such systems risks to be compromised, if the tools fail. To mitigate this risk, safety standards (e.g. DO-178C/DO330, IEC 61508) define prescriptive tool qualification processes. Compliance with these processes can be required for (re-)certification purposes. To enable reuse and thus reduce time and cost related to certification, cross-domain tool manufacturers need to understand what varies and what remains in common when transiting from one domain to another. To ease reuse, in this paper we focus on verification tools and model a cross-domain tool qualification process line. Finally, we discuss how reusable cross-domain process-based arguments can be obtained.

The RTCA has recently released DO-178C and DO-278A as new certification guidance for the production of airborne and ground-based air traffic management software, respectively. Additionally, RTCA special committee SC-205 has also produced, at the same time, five other companion documents. These documents are RTCA DO-248C, DO-330, DO-331, DO- 332, and DO-333. These supplements address frequently asked questions about software certification, provide guidance on tool qualification requirements, and illustrate the modifications recommended to DO-178C when using model-based software design, object oriented programming, and formal methods. The objective of this paper is to first explain the relationship of DO-178C to the former DO-178B in order to give those familiar with DO- 178B an indication of what has been changed and what has not been changed. With this background, the relationship of DO-178C and DO-278 to the new DO-278A document for ground-based software development is shown. Last, an overview of the new guidance contained in the tool qualification document and the three new supplements to DO-178C and DO-278A is presented. For those unfamiliar with DO-178B, this paper serves to provide an entry point to this new certification guidance for airborne and ground-based CNS/ATM software certification.

This paper describes initial work towards building an explicit assurance case for DO-178C / ED-12C. Two specific questions are explored: (1) What are some of the assumptions upon which the guidance in the document relies, and (2) What claims are made concerning test coverage analysis?

In the civil aviation certification the software has an unlike treatment due to its peculiarities and also for being a relatively new item. There is no specific software certification requirement in the FAR – FAR 33.28 is the only section that mentions the word software. The FAA recognizes the considerations presented in RTCA/DO-178B as an acceptable means for approval of software used in airborne systems for civil aviation. The CTA/IFI/CAvC, responsible for the type certification in Brazil, has been applying RTCA/DO-178B since it was issued. The purpose of this paper is to present the experience of CTA in applying DO-178B, focusing on those technical issues that were source of controversy among certification authorities and industries. This paper is relevant at present time as RTCA and EUROCAE have recently organized a Special Committee intending to issue DO-178C by the end of 2008.

The commercial avionics community's DO-178B software safety certification requirements document is being updated to take into account twenty years of experience, and the new version (DO-178C) is close to completion. This half-day tutorial covers the core of the DO-178C standard, including the new treatment of tool qualification, as well the supplements on Object-Oriented and Other Technologies, Model-Based Design, and Formal Methods.