REG NASA-LLIS-0593-1998 Lessons Learned Mars Pathfinder Avionics and Flight Software Architecture (1997).pdf

《REG NASA-LLIS-0593-1998 Lessons Learned Mars Pathfinder Avionics and Flight Software Architecture (1997).pdf》由会员分享，可在线阅读，更多相关《REG NASA-LLIS-0593-1998 Lessons Learned Mars Pathfinder Avionics and Flight Software Architecture (1997).pdf（3页珍藏版）》请在麦多课文档分享上搜索。

1、Lessons Learned Entry: 0593Lesson Info:a71 Lesson Number: 0593a71 Lesson Date: 1998-06-18a71 Submitting Organization: JPLa71 Submitted by: G. Reeves/D. OberhettingerSubject: Mars Pathfinder Avionics and Flight Software Architecture (1997) Abstract: The Mars Pathfinder (MPF) avionics and flight softw

2、are development effort focused on producing a software architecture that would contribute to lower operations cost and minimize the overall project cost. This lesson summarizes MPF success factors, including use of an extra powerful flight computer and a standardized backplane and bus.Description of

3、 Driving Event: The Mars Pathfinder (MPF) avionics and flight software development effort focused on producing a software architecture that would contribute to lower operations cost and minimize the overall project cost.Additional Keyword(s): Software Life Cycle, Life Cycle Cost, Concurrent Engineer

4、ingReference(s):1. Glenn Reeves, “Mars Pathfinder Flight Software Lessons Learned,“ April 28, 1997.2. “Mars Pathfinder Flight Software Development Process,“ JPL Lesson Learned No.10-105, June 4, 1998.Lesson(s) Learned: 1. Use of a powerful computer (20 MIPS) with large memory for margin management p

5、rovided flexibility in software development for MPF.2. Consider use of a commercial standard backplane (e.g., VME) and avionics standard bus (such as MIL-STD-1553) to allow the fast development of realistic test environments using Provided by IHSNot for ResaleNo reproduction or networking permitted

6、without license from IHS-,-,-commercial hardware and software.3. The early MPF risk assessments prompted the use of an essentially single string avionics design, which resulted in a great reduction in the complexity of the software.4. A multitasking execution model permits parallel development of se

7、parate modules and is supported by a variety of commercial products.5. Purchase a commercial operating system (kernel) rather than developing one in house.6. Select a mature flexible implementation language, with mature development tools, such as the C language.7. The MPF project combined the Comman

8、d Data Subsystem (CDS) and Attitude Control Subsystem (ACS) hardware and software functions in one processor. This greatly simplified hardware design, ground and flight software design, system implementation, and integration and test.8. Consider using software system analysts to directly produce fli

9、ght code, instead of just writing software specifications and handing them to a flight software team to code.Recommendation(s): See Lessons LearnedEvidence of Recurrence Control Effectiveness: N/ADocuments Related to Lesson: N/AMission Directorate(s): N/AAdditional Key Phrase(s): a71 Administration/

10、Organizationa71 Computersa71 Risk Management/Assessmenta71 SoftwareAdditional Info: Provided by IHSNot for ResaleNo reproduction or networking permitted without license from IHS-,-,-Approval Info: a71 Approval Date: 1998-06-25a71 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-,-,-