The IRIG 106 Programming Handbook presents a general overview of IRIG 106 conformance requirements. For the purposes of validation more detailed requirement are necessary. The logical and physical interfaces identified in the Programming Handbook are each assigned a numerical requirements section. For example, the “Media File Interface” is assigned requirements Section 10. The table below, adapted from the Programming Handbook, is a summary of physical and logical interfaces along with the assigned requirements section of each.
| LOGICAL INTERFACE REQUIREMENTS | ||
|---|---|---|
| Requirements Section | Ch 10 Section | Logical Interfaces |
| 1 | 10.5 | Media File Interface |
| 2 | 10.6 | Packetization & Data Format |
| 3 | 9, 10.6.7.2 | TMATS |
| PHYSICAL INTERFACES | ||
|---|---|---|
| Requirements Section | Ch 10 Section | Physical Interfaces |
| TBD | 10.3, 10.4.1 | Recorder Fibre Channel |
| TBD | 10.4.2 | Recorder IEEE 1394B |
| TBD | 10.4, 10.4.3 | Recorder Ethernet (on board) |
| TBD | 10.3.5, 10.3.6 | Removable Memory Media (RMM) |
| TBD | 10.3.2, 10.7.10 | Discrete Lines |
| TBD | 10.3.2 | RS-232 and 422 Full Duplex Communication |
| TBD | 10.3 | External Power Port |
Top level requirements may have subsections of requirements. For example, requirement Section 2 “Packetization & Data Format” will be composed of a general packet requirements subsection as well as subsections for each packet type. Requirement subsections are defined and numbered by appending a dot “.” to the parent section followed by a sequential subsection number.
Individual detailed requirements organized under the appropriate section and subsection. An individual requirement is identified by a section/subsection number, followed by a dash “-”, followed by a sequential requirement number. For example, the first requirement of the “Packetization & Data Format” section, “General Packet Requirements” subsection may be 2.1-1.