2.1 Interface Documentation
The IRD, ICD, and IR are closely related and each has a specific purpose. The Integrated Product Team (IPT) or program office is typically responsible for developing IRDs, ICDs, and IRs. IRDs identify the interface requirements between two subsystems, between a subsystem and a "user" (where the "user" can be viewed as a variable that can be filled with multiple subsystems), or between a facility and a subsystem. The requirements in an IRD are often traced to or derived from requirements in a system-level specification or system requirements document. ICDs describe the formal agreement that documents how the interface requirements between two subsystems, between a subsystem and a "user" (where the "user" can be viewed as a variable that can be filled with multiple subsystems), or between a facility and a subsystem are implemented; the as-built configuration. The design characteristics in an ICD trace to and are derived from the interface requirements in an IRD.
Replaced/Superseded by document(s)
|File||MIME type||Size (KB)||Language||Download|
|FAA STD- Preparation of Interface Documentation.pdf||application/pdf||1.04 MB||English||DOWNLOAD!|
This standard establishes the format and minimum content of Interface Requirements Documents (IRD), Interface Control Documents (ICD), and Interface Revisions (IRs) used by the Federal Aviation Administration (FAA).
The purpose of this standard is to provide a set of instructions for the preparation of IRDs, ICDs, and IRs. This standard is applicable to all programs responsible for acquiring, upgrading, or developing NAS subsystems.
1.2 Order of Precedence
In the event of a conflict between the text of this document and the references cited herein, the text of this document takes precedence. Nothing in this document, however, supersedes applicable laws and regulations unless a specific exemption has been obtained.