A Study on Safety of Airborne Software and Considerations during Development

항공용 소프트웨어 안전성 및 개발시 주의사항에 대한 고찰

  • 이백준 (한국항공우주연구원 SBAS사업단) ;
  • 최종연 (한국항공우주연구원 SBAS사업단) ;
  • 남기욱 (한국항공우주연구원 SBAS사업단)
  • Received : 2016.05.09
  • Accepted : 2016.06.15
  • Published : 2016.06.30


It is recognized that safety is a key point of technical competency. Its adoption is widely spread in development of products and it is essentially necessary in aerospace industry because airborne system and equipment are used complex high-technology and implemented systematic performance using software. This study reviews system safety assessment, development assurance level, airborne software, RTCA DO-178 process, and considerations & pitfalls in software development.


Supported by : 국토교통부


  1. Baeckjun Yi, Seung-kyem Kim, "Software Consideration in Airborne System Design and Certification", Aerospace Engineering and Technology, Vol.3 No.2, 2004, pp.177-182
  2. SAE, ARP 4754A "Certification Considerations for Highly Integrated or Complex Aircraft Systems", 2010
  3. SAE, ARP 4761 "Guidelines and Methods for Conducting the Safety Assessment Process on Civil Airborne Systems and Equipment", 1996
  4. Baeckjun Yi, "A Study on Aircraft System Safety Assessment and Airborne Software Development Assurance Level", 2014 SASE Fall Conference, 2014
  5. RTCA, DO-178C "Software Considerations in Airborne Systems and Equipment Certification", 2011
  6. Baeckjun Yi, Youngkwon Jin, "Airborne Software Approval and Common DO-178B Pitfalls", 2011 SASE Fall Conference, 2011
  7. Vance Hilderman, "DO-178B to 178C: Avoiding the Unlucky 13 Mistakes", Atego HighRely, 2011, pp.26-40