DO-178B
E732924
DO-178B is a widely used aviation industry standard that defines objectives and processes for developing and certifying safety-critical airborne software.
All labels observed (1)
| Label | Occurrences |
|---|---|
| DO-178B canonical | 1 |
How this entity was disambiguated
This entity first appeared as the object of triple T8413987 — resolving that mention is where its identity was fixed. The disambiguator weighed these candidate entities and picked the highlighted one (or “None”, minting a new entity). This is how homonymy is resolved: the same surface form can point to different entities.
Target entity: DO-178B Context triple: [Integrity, supportsStandard, DO-178B]
-
A.
ISO 26262
ISO 26262 is an international functional safety standard for electrical and electronic systems in production automobiles, defining requirements to ensure the safety of road vehicles throughout their lifecycle.
-
B.
ARINC 664
ARINC 664 is an aviation data network standard that defines Ethernet-based communication for aircraft systems, enabling reliable, deterministic, and interoperable avionics networking.
-
C.
IEEE 12207
IEEE 12207 is an international standard that defines processes, activities, and tasks for the life cycle management of software systems.
-
D.
ISO/IEC/IEEE 29148
ISO/IEC/IEEE 29148 is an international standard that defines best practices and processes for engineering and managing system and software requirements.
-
E.
ISO/IEC 16262
ISO/IEC 16262 is the international standard that formally defines the ECMAScript programming language, the basis for JavaScript and related implementations.
- F. None of above. chosen
- G. Unsure - the case is ambiguous/there is not enough information to decide.
Target entity: DO-178B Target entity description: DO-178B is a widely used aviation industry standard that defines objectives and processes for developing and certifying safety-critical airborne software.
-
A.
ISO 26262
ISO 26262 is an international functional safety standard for electrical and electronic systems in production automobiles, defining requirements to ensure the safety of road vehicles throughout their lifecycle.
-
B.
ARINC 664
ARINC 664 is an aviation data network standard that defines Ethernet-based communication for aircraft systems, enabling reliable, deterministic, and interoperable avionics networking.
-
C.
IEEE 12207
IEEE 12207 is an international standard that defines processes, activities, and tasks for the life cycle management of software systems.
-
D.
ISO/IEC/IEEE 29148
ISO/IEC/IEEE 29148 is an international standard that defines best practices and processes for engineering and managing system and software requirements.
-
E.
ISO/IEC 16262
ISO/IEC 16262 is the international standard that formally defines the ECMAScript programming language, the basis for JavaScript and related implementations.
- F. None of above. chosen
Statements (56)
| Predicate | Object |
|---|---|
| instanceOf |
RTCA standard
ⓘ
aviation software standard ⓘ safety-critical software standard ⓘ |
| appliesTo |
airborne equipment
ⓘ
airborne systems ⓘ safety-critical software ⓘ |
| coordinatedWith | EUROCAE ED-12B NERFINISHED ⓘ |
| defines |
configuration management objectives
ⓘ
guidance for certification liaison ⓘ objectives for safety-critical airborne software ⓘ processes for safety-critical airborne software ⓘ quality assurance objectives ⓘ software level assurance objectives ⓘ software life cycle data requirements ⓘ verification objectives ⓘ |
| domain | airborne software ⓘ |
| equivalentTo | ED-12B NERFINISHED ⓘ |
| focusesOn |
software certification for airborne systems
ⓘ
software development for airborne systems ⓘ |
| fullName | DO-178B: Software Considerations in Airborne Systems and Equipment Certification NERFINISHED ⓘ |
| hasConcept |
change control
ⓘ
configuration management process ⓘ design assurance level ⓘ development process ⓘ independence of verification ⓘ planning process ⓘ problem reporting ⓘ quality assurance process ⓘ requirements-based testing ⓘ software levels A through E ⓘ software life cycle processes ⓘ structural coverage analysis ⓘ traceability from requirements to code and tests ⓘ verification process ⓘ |
| hasSuccessor | DO-178C NERFINISHED ⓘ |
| hasVersion | DO-178A NERFINISHED ⓘ |
| industry | aviation ⓘ |
| objective |
to ensure acceptable safety of airborne software
ⓘ
to provide guidance for certification authorities and applicants ⓘ |
| publishedBy |
RTCA
NERFINISHED
ⓘ
RTCA Special Committee 167 NERFINISHED ⓘ |
| replaced | DO-178A NERFINISHED ⓘ |
| replacedBy | DO-178C NERFINISHED ⓘ |
| requires |
documented software requirements
ⓘ
evidence of verification activities ⓘ independent reviews and audits ⓘ traceability between requirements, design, code, and tests ⓘ |
| status | superseded by DO-178C in many new projects ⓘ |
| stillUsedIn |
legacy avionics programs
ⓘ
maintenance of certified airborne software ⓘ |
| usedBy |
aircraft manufacturers
ⓘ
avionics suppliers ⓘ certification authorities ⓘ software development organizations in aviation ⓘ |
| usedFor |
approval of software in civil aircraft
ⓘ
certification of airborne software ⓘ |
How these facts were elicited
The pipeline generated the facts above by prompting gpt-5.1 with this entity's name + description and the instruction below.
You are a knowledge base construction expert. Given a subject entity and a description of it, return factual statements that you know for the subject as a JSON list of dictionaries(triples), where keys must be "subject", "predicate" and "object". The number of facts may be very high, between 25 to 50 or more, for very popular subjects. For less popular subjects, the number of facts can be very low, like 5 or 10. # Requirements - If you don't know the subject at all, return an empty list. - If the subject is not a named entity, return an empty list. - Include at least one triple where predicate is "instanceOf". - Do not get too wordy. - Separate several objects into multiple triples with one object.
Subject: DO-178B Description of subject: DO-178B is a widely used aviation industry standard that defines objectives and processes for developing and certifying safety-critical airborne software.
Referenced by (1)
Full triples — surface form annotated when it differs from this entity's canonical label.