REG NASA-LLIS-0608-1999 Lessons Learned Consider Language Differences When Conveying Requirements to Foreign Partners (1997).pdf

《REG NASA-LLIS-0608-1999 Lessons Learned Consider Language Differences When Conveying Requirements to Foreign Partners (1997).pdf》由会员分享，可在线阅读，更多相关《REG NASA-LLIS-0608-1999 Lessons Learned Consider Language Differences When Conveying Requirements to Foreign Partners (1997).pdf（3页珍藏版）》请在麦多课文档分享上搜索。

1、Lessons Learned Entry: 0608Lesson Info:a71 Lesson Number: 0608a71 Lesson Date: 1999-01-21a71 Submitting Organization: JPLa71 Submitted by: J. Wirth/ D. OberhettingerSubject: Consider Language Differences When Conveying Requirements to Foreign Partners (1997) Abstract: When communications are phrased

2、 ambiguously, foreign partners who use English as a second language may misinterpret requirements. In the case of the Huygens probe, a requirement specifying the memory location of probe science data confused the European Space Agency. The use of a diagram would have helped. Hence, when working with

3、 foreign partners, document requirements in terms that describe the intent very clearly.Description of Driving Event: The Huygens probe was the European Space Agencys (ESAs) contribution to the joint NASA/ESA Cassini/Huygens mission, and it represented the first medium-sized mission of ESAs long-ter

4、m space science program. This venture required a high degree of collaboration between NASA and ESAs industrial partners in 14 European countries where 10 different languages are spoken. Provided by IHSNot for ResaleNo reproduction or networking permitted without license from IHS-,-,-refer to D descr

5、iptionD ESA Industrial Partners for the Huygens Probe Control of subsystem interfaces always requires effective interaction between engineers. The complexity of the Cassini/Huygens interfaces increased the need for clear and unambiguous communication.Since most Europeans use English as a second lang

6、uage, requirements that are clear to JPL engineers may be misinterpreted by foreign partners. When the wording is vague, a requirement or specification may be interpreted many ways. For example, a requirement called for two copies of probe science data to be stored in each of two memory partitions o

7、n the dual solid state recorders. Read correctly, this requirement called for a total of eight storage locations, but the lack of a diagram illustrating these assignments confused ESA.Additional Keyword(s): Interpretation, Interface Control, Configuration Management, Joint Venture, International Par

8、tnersReference(s):1. Cassini Spacecraft Assembly, Test, and Launch Operations (ATLO) Final Report, Volume I, JPL Document D-15701, May 15, 1998, page 155.Lesson(s) Learned: It is especially important when working with foreign partners to document requirements in terms that describe the intent very c

9、learly; include graphics where possible.Recommendation(s): Provided by IHSNot for ResaleNo reproduction or networking permitted without license from IHS-,-,-See lesson(s) learned.Evidence of Recurrence Control Effectiveness: N/ADocuments Related to Lesson: N/AMission Directorate(s): N/AAdditional Ke

10、y Phrase(s): a71 Administration/Organizationa71 Configuration Managementa71 External RelationsAdditional Info: Approval Info: a71 Approval Date: 1999-01-26a71 Approval Name: Carol Dumaina71 Approval Organization: 125-204a71 Approval Phone Number: 818-354-8242Provided by IHSNot for ResaleNo reproduction or networking permitted without license from IHS-,-,-