Engineering PapersSearch

Engineering topics

Hayhurst, Kelly

Publications and source records attributed to Hayhurst, Kelly.

Certification

Objective 1: Provide regulators with a methodology for development of airworthiness requirements for certification of UAS. a) Rationale: a comprehensive methodology does not currently exist to support development of regulation for certification of UAS. Regulation is essential to enable routine access to the NAS. b) Approach: 1) assess existing approaches and classification schemes for deriving acceptable means of compliance to airworthiness requirements. 2) investigate a service-based approach to classification of UAS. 3) conduct comparative analysis of different methodologies. 4) work with FAA to determine best approach and conduct case study. 5) participate in regulatory/standards organizations developing safety and performance requirements for UAS. Objective 2: Provide regulators and industry with hazard and risk-related data to support criteria for UAS type design. a) Rationale: There is presently little UAS specific data (incident, accident, and reliability), especially in a civil context, to support risk assessment and development of standards and regulation. b) Approach: Identify gaps in existing data, provide measured data as needed, and formulate recommendations by: 1) evaluating UAS incident/accident data collection efforts and determining additional support necessary for regulation. 2) assessing UAS-specific hazards and risks. 3) evaluating need for reliability data for UAS-unique systems, components and subsystem, and determining additional measurement requirements. 4) developing guidance and best practices for UAS type design.

Hayhurst, Kelly

Guidance for Using Formal Methods in a Certification Context

This paper discusses some of the challenges to using formal methods in a certification context and describes the effort by the Formal Methods Subgroup of RTCA SC-205/EUROCAE WG-71 to propose guidance to make the use of formal methods a recognized approach. This guidance, expected to take the form of a Formal Methods Technical Supplement to DO-178C/ED-12C, is described, including the activities that are needed when using formal methods, new or modified objectives with respect to the core DO-178C/ED-12C document, and evidence needed for meeting those objectives.

Brown, Duncan

Mending the Gap, An Effort to Aid the Transfer of Formal Methods Technology

Formal methods can be applied to many of the development and verification activities required for civil avionics software. RTCA/DO-178B, Software Considerations in Airborne Systems and Equipment Certification, gives a brief description of using formal methods as an alternate method of compliance with the objectives of that standard. Despite this, the avionics industry at large has been hesitant to adopt formal methods, with few developers have actually used formal methods for certification credit. Why is this so, given the volume of evidence of the benefits of formal methods? This presentation will explore some of the challenges to using formal methods in a certification context and describe the effort by the Formal Methods Subgroup of RTCA SC-205/EUROCAE WG-71 to develop guidance to make the use of formal methods a recognized approach.

Hayhurst, Kelly