Consider Language Differences When Conveying Requirements to Foreign Partners (1997) (Diagrams may be useful in requirements specifications).Document Structure Reference: IDD - Interface Design Description The MICD s should have had periodic verification for accuracy and compatibility. In part, this was due to independently prepared Mechanical Interface Control Drawings by the Government and the contractor. (While this lesson involves a hardware-related problem, it illustrates the need for accuracy in interface documentation.) Investigation showed that the main wiring harness was built in accordance with documentation that had not been updated after design changes were made. Lesson Number 0569 508: Problems occurred during the Mars Pathfinder spacecraft integration and test due to out-of-date or incomplete interface documentation. Lesson Number 0403 507: "When command sequences are stored on the spacecraft and intended to be exercised only in the event of abnormal spacecraft activity, the consequences should be considered of their being issued during the system test or the pre-launch phases." Document Structure Reference: STP - Software Test Plan Thrusters Fired on Launch Pad (1975) (Plan for safe exercise of command sequences).4: "Design flexibility of the flight computer and software is critical to the ability to uplink software patches for the correction of unexpected in-flight spacecraft anomalies." Document Structure Reference: SwDD - Software Design Description Lesson Number 0310 501: Design for Maintenance, Lesson Learned No. Mars Observer Inertial Reference Loss.The NASA Lesson Learned database contains the following lessons learned related to software project documentation: SASTATUS - Software Status Report is now in topic 8.16, tab 2, Software Status Report Contentsģ. SADESIGN is now in topic 8.16, tab 2, Software Design Analysis. SAANALYSIS is now in topic 8.16, tab 2, Software Requirements Analysis. SSP - Software Safety Plan is now in topic 8.16, Software Assurance Plan product, tab 3, Safety Plan Contents SAP - Software Assurance Plan is now in topic 8.16, tab 2, Software Assurance Plan Contents. The following products have already been moved and are located as follows: Note: Software Assurance items are being moved to the Software Assurance and Safety Topics. SRS - Software Requirements Specification.SDP-SMP - Software Development - Management Plan. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |