Английская Википедия:FAA Order 8110.105
Шаблон:Short description Шаблон:Infobox technology standard
FAA Order 8110.105A, Simple and Complex Electronic Hardware Approval Guidance, supplements RTCA DO-254() by explaining how FAA aircraft certification staff can use that document "when working on certification projects".[1] "The Order states specific topics of interest to the FAA that may go above and beyond content specific to DO-254."[1] This order is recommended as a reference for developers applying under DO-254() for certification of electronic hardware designs,[2] including those implemented in "custom micro-coded components" (ie., ASICs, PLDs, or FPGAs).
Clarification of application of DO-254 to simple electronic hardware
Custom micro-coded devices are typically presumed to be complex components that cannot be verified through testing alone and must be assured through formal design assurance processes such as those defined in DO-254. However, some applicants have proposed their specific applications as simple components, that is, those that can be verified through testing alone, thereby requiring much less effort to certify.[3] DO-254 had been considered too ambiguous on its application to simple hardware. This concern was the topic of the Certification Authorities Software Team's 2007 CAST-30 position paper, Simple Electronic Hardware and DO-254 and ED-80.
In particular, Order 8110.105 provides clarification of DO-254 guidance for "simple" electronic hardware. Such simple hardware does not require as rigorous design assurance as complex functions installed in custom micro-coded components.
General clarification of application of DO-254
Additionally, Order 8110.105 addresses some of the omissions and clarification needs identified by the Certification Authorities Software Team in their position paper, CAST-31, and as such informs electronic hardware developers of interests beyond those presently expressed in DO-254.[1]
Overview
Functioning electronic hardware systems and products certified through DO-254() processes range from replaceable electronic boxes, circuit boards within such enclosures, and any ASICs, PLDs, or FPGAs placed on such boards. These sorts of electronic hardware can be classified as simple or complex.[4] With respect to DO-254(), a device is classified as simple if comprehensive inspection or testing alone can demonstrate that it is reasonably free of design defects or errors and has deterministic behavior. A complex device, then, is one that cannot be assessed by comprehensive inspection or testing alone.[5][6][7]
For the purposes of aircraft type certification efforts, aircraft system components are designated as software or hardware. Software components are computer programs installed and operating on computers or microcontrollers and are usually subjected to the design assurance processes of RTCA DO-178() when installed in aircraft. DO-254() is applied to the certification of both simple and complex hardware components, particularly inclusive of both simple and complex custom micro-coded components. "A hardware item is considered simple if a comprehensive combination of deterministic tests and analyses can ensure correct functional performance under all foreseeable operating conditions with no anomalous behavior." All other hardware items are considered complex and, since complex hardware items cannot be completely validated by inspection and testing alone, design assurance methodology is required.[8] Advisory Circular 20-152 recognizes the guidance in DO-254 as a suitable means for demonstrating compliance for the use of complex custom micro-coded components within aircraft systems.[9] However, application of DO-254 to simple micro-coded components was not explicitly addressed by that circular.[10]
Initially, applicants and developers were concerned with the apparent ambiguity of DO-254's guidance on simple electronic hardware. That document is largely concerned with the objectives and activities of developing complex electronic hardware. However, it provides only one short paragraph suggesting that a simple hardware item should be configuration controlled and verified, but "extensive documentation is not needed". In response to the concern, CAST-30 Simple Electronic Hardware and RTCA Document DO-254 and EUROCAE Document ED-80 was completed in 2007 to provide clarification to the guidance in DO-254/ED-80 specifically for simple electronic hardware.[11][12] Following this, FAA Order 8110.105 was released in 2008 to supplement the guidance for both simple and complex electronic hardware,[1] and updated to Revision A in 2017. Three primary chapters are clarification of
- topics applicable to both simple and complex electronic hardware,
- topics applicable to complex electronic hardware alone, and
- topics applicable to simple electronic hardware alone.[13][14]
References
External links
- Шаблон:Cite web
- Regulations & Policies on the FAA website
- ↑ 1,0 1,1 1,2 1,3 Шаблон:Cite book
- ↑ Spitzer, Ferrell, and Ferrell, p. 14-17 " ... it behooves applicants and PLD developers to be familiar with the content and intent of the Order ...."
- ↑ Spitzer, Ferrell, and Ferrell, p. 14-2 "Classifying hardware as simple allows for a reduction in the hardware design assurance activities and documentation described within DO-254."
- ↑ Шаблон:Cite book
- ↑ Шаблон:Citation
- ↑ Шаблон:Cite book
- ↑ Шаблон:Cite book
- ↑ RTCA/DO-254 "Design Assurance Guidance For Airborne Electronic Hardware", Appendix C
- ↑ AC 20-152, FAA, Office AIR-100, 2005. "This AC recognizes the guidance in RTCA/DO-254 applies specifically to complex custom micro-coded components with hardware design assurance levels of A, B, and C, such as ASICs, PLDs, and FPGAs", Page 1.
- ↑ Шаблон:Cite journal
- ↑ Шаблон:Cite journal
- ↑ Шаблон:Citation CAST-30 is listed as relevant to 8110.105
- ↑ Шаблон:Cite journal
- ↑ Шаблон:Citation The table list these three subjects.
