Legacy Code의 DO-178C 인증 준수를 위한 모델 기반 소프트웨어 개발 연구
A Study on Model-Based Software Development for Compliance with DO-178C Certification of Legacy Code
0
조회
0
다운로드
0
인용
0
참고문헌
키워드
초록
This paper addresses key considerations when converting Legacy Code into a Model-Based Design (MBD) structure, highlighting advantages such as market growth, ease of maintenance, and improved development quality. For aerospace control software, compliance with DO-178C, an international standard for airworthiness certification, is critical, especially to meet Design Assurance Level A (DAL-A), the highest level of safety assurance. In this context, the study analyzes differences between Simulink, a widely adopted MBD tool, and SCADE, a tool specifically optimized for DO-178C certification. The primary contribution of this paper is the introduction of five practical methodologies for converting Legacy Code into an MBD-compatible structure. These methodologies consider key factors such as automation level, cost, and certification compatibility, and are intended to provide clear guidance for developers to select the most suitable approach according to their tool expertise, development environment, and testing conditions. Through these methodologies, this study aims to simplify the complex task of achieving DO-178C DAL-A compliance, improving software reusability and flexibility, and reducing overall development time for safety-critical aerospace applications.
Abstract
This paper addresses key considerations when converting Legacy Code into a Model-Based Design (MBD) structure, highlighting advantages such as market growth, ease of maintenance, and improved development quality. For aerospace control software, compliance with DO-178C, an international standard for airworthiness certification, is critical, especially to meet Design Assurance Level A (DAL-A), the highest level of safety assurance. In this context, the study analyzes differences between Simulink, a widely adopted MBD tool, and SCADE, a tool specifically optimized for DO-178C certification. The primary contribution of this paper is the introduction of five practical methodologies for converting Legacy Code into an MBD-compatible structure. These methodologies consider key factors such as automation level, cost, and certification compatibility, and are intended to provide clear guidance for developers to select the most suitable approach according to their tool expertise, development environment, and testing conditions. Through these methodologies, this study aims to simplify the complex task of achieving DO-178C DAL-A compliance, improving software reusability and flexibility, and reducing overall development time for safety-critical aerospace applications.