c. Message Descriptions. Identify each message transmitted across the interface and specify the
assignment of data elements to each message. Provide cross references between data elements and
messages, as a two-way sorted list.
d. Interface Priority. Specify the relative priority of this interface and of each message transmitted
across it.
e. Communication Protocols. Identify the protocol for the interface by name and describe its technical
details in terms of the following:
1. Fragmentation and reassembly of messages
2. Message formatting
3. Error control and recovery procedures, including fault tolerance features
4. Synchronization, including connection establishment, maintenance, termination, and timing
5. Flow control, including sequencing, and buffer allocation
6. Data transfer rate, whether periodic or aperiodic, and minimum interval between transfers
7. Routing, addressing, and naming conventions
8. Transmission services, including priority and grade
9. Status, identification, notification, and other reporting features
10. Security, including encryption, user authentication, compartmentalization, and auditing
Defines standard
Replaced/Superseded by document(s)
Cancelled by
Amended by
| File | MIME type | Size (KB) | Language | Download | |
|---|---|---|---|---|---|
| NASA_DIDs.pdf | application/pdf | 187.16 KB | English | DOWNLOAD! |
Provides definitions
Cover images
Introduction
The purpose of the Concept is to provide an overview of the software. The Concept section should be
relatively brief. The Concept provides the context in which to read the Requirements section of the
Product Specification. All requirements should be traceable, in a general sense, to the functions or capabilities described in the Concept. However, the Requirements section (or document, if the section isrolled-out), is the governing specification for the product.