This HTML5 document contains 32 embedded RDF statements represented using HTML+Microdata notation.

The embedded RDF content will be recognized by any processor of HTML5 Microdata.

Namespace Prefixes

PrefixIRI
dctermshttp://purl.org/dc/terms/
dbohttp://dbpedia.org/ontology/
foafhttp://xmlns.com/foaf/0.1/
n11https://global.dbpedia.org/id/
dbthttp://dbpedia.org/resource/Template:
rdfshttp://www.w3.org/2000/01/rdf-schema#
n15https://www.faa.gov/documentLibrary/media/Advisory_Circular/
rdfhttp://www.w3.org/1999/02/22-rdf-syntax-ns#
owlhttp://www.w3.org/2002/07/owl#
wikipedia-enhttp://en.wikipedia.org/wiki/
dbchttp://dbpedia.org/resource/Category:
dbphttp://dbpedia.org/property/
provhttp://www.w3.org/ns/prov#
xsdhhttp://www.w3.org/2001/XMLSchema#
wikidatahttp://www.wikidata.org/entity/
dbrhttp://dbpedia.org/resource/

Statements

Subject Item
dbr:AC_00-69
rdfs:label
AC 00-69
rdfs:comment
The Advisory Circular AC 00-69, Best Practices for Airborne Software Development Assurance Using EUROCAE ED-12 and RTCA DO-178, initially issued in 2017, supports application of the active revisions of ED-12C/DO-178C and AC 20-115. The AC does not state FAA guidance, but rather provides information in the form of complementary "best practices".
dcterms:subject
dbc:RTCA_standards dbc:Software_requirements dbc:Computer_standards dbc:Avionics dbc:Safety
dbo:wikiPageID
65092839
dbo:wikiPageRevisionID
1071865654
dbo:wikiPageWikiLink
dbr:FAA_Order_8110.49 dbc:Software_requirements dbc:RTCA_standards dbr:Software_design_description dbr:Best_practice dbr:AC_20-115 dbr:Data_coupling dbr:Advisory_circular dbr:DO-178C dbc:Computer_standards dbc:Safety dbr:Runtime_error_detection dbr:Change_impact_analysis dbc:Avionics dbr:Control_coupling
dbo:wikiPageExternalLink
n15:AC_00-69.pdf
owl:sameAs
wikidata:Q104853009 n11:FN6EM
dbp:wikiPageUsesTemplate
dbt:Reflist
dbo:abstract
The Advisory Circular AC 00-69, Best Practices for Airborne Software Development Assurance Using EUROCAE ED-12 and RTCA DO-178, initially issued in 2017, supports application of the active revisions of ED-12C/DO-178C and AC 20-115. The AC does not state FAA guidance, but rather provides information in the form of complementary "best practices". * Notably, the guidance of regarding "Software Change Impact Analysis" was removed in Rev A of that notice in 2018. The best practices that AC 00-69 now describes for Software Change Impact Analysis are much reduced and less prescriptive than what was removed from 8110.49. * This AC clarifies that Data Coupling Analysis and Control Coupling Analysis are distinct activities and that both are required for satisfying objective A-7 (8) of ED-12C/DO-178C and ED-12B/DO-178B, adding that data and control coupling analyses rely upon detailed design specification of interfaces and dependencies between components. * The AC also recommends that error handling (how the software avoids, detects, and handles runtime error) should be defined in explicit, reviewed design specifications rather than implemented ad hoc in the source code.
prov:wasDerivedFrom
wikipedia-en:AC_00-69?oldid=1071865654&ns=0
dbo:wikiPageLength
3023
foaf:isPrimaryTopicOf
wikipedia-en:AC_00-69