One of the goals of IP217 was to address the ambiguities and confusions in terminology that exist in some of the fundamental aspects of DO1-78B. Terms like High Level, Low Level and Derived Requirements have no single consistent and unambiguous definition in DO-178B. In fact they are often used in ways that convey multiple interpretations that are not always consistent. To address these weakness, IP217 proposed a number of definitions and concepts as first principles. In this section we will present and explain those definitions and concepts in order to lay a strong foundation for the rest of the material of the IP217 OpenDO project - including the formal Requirements/Design Information model on which IP217 is centered.
First Principle - Requirement Concept
It is IP217's point of view that many of the problems with terminology in DO-178C are the result of a lack of formal definition of the very concept of "requirement". IP217 provides a very fundamental, formal, and unambiguous definition that is both based on the intuitive understanding that "a requirement describes what and when but not how" and expressed in identifiable, objective concepts like input/output functional relationships and temporal/constraint relationships.
IP217 Definition of Requirement
First Principle - Design
IP217 Definition of Design
First Principle - Verification
IP217 Definition of Verification
Want to get involved?
Contactinfo @ open-do.org