A configuration management program should focus on ensuring designs are traceable to capability needs, developmental changes are controlled and documented, interfaces are well-defined and understood, and ________________.

A configuration management program should focus on ensuring designs are traceable to capability needs, developmental changes are controlled and documented, interfaces are well-defined and understood, and ________________.

• A. All product documentation is consistent with its supporting information
• B. All product documentation is stored in a central repository
• C. All product documentation is printed and hard bound
• D. All product documentation is anonymized

Answer: (A)

Documentation integrity and alignment between product documentation and its supporting information is essential in configuration management. When designs trace back to capability needs, and developmental changes are controlled and documented, the documentation must reflect the same basis. If documentation diverges from the supporting information, you lose a reliable baseline, making it hard to verify changes, understand interfaces, or reproduce configurations. Ensuring that all product documentation is consistent with its supporting information keeps the configuration coherent, auditable, and easier to manage through changes. Storing everything in a central repository helps with accessibility, but it doesn’t by itself guarantee that the documentation stays aligned with the evidence and assumptions that supported the design. Printing and hard binding isn’t a requirement for effective CM, and anonymizing documentation would remove accountability and traceability.

Documentation integrity and alignment between product documentation and its supporting information is essential in configuration management. When designs trace back to capability needs, and developmental changes are controlled and documented, the documentation must reflect the same basis. If documentation diverges from the supporting information, you lose a reliable baseline, making it hard to verify changes, understand interfaces, or reproduce configurations. Ensuring that all product documentation is consistent with its supporting information keeps the configuration coherent, auditable, and easier to manage through changes.

Storing everything in a central repository helps with accessibility, but it doesn’t by itself guarantee that the documentation stays aligned with the evidence and assumptions that supported the design. Printing and hard binding isn’t a requirement for effective CM, and anonymizing documentation would remove accountability and traceability.