REG NASA-LLIS-0590-1998 Lessons Learned Mars Pathfinder Flight Software Development Process (1997).pdf

1、Lessons Learned Entry: 0590Lesson Info:a71 Lesson Number: 0590a71 Lesson Date: 1998-06-04a71 Submitting Organization: JPLa71 Submitted by: G. Reeves/D. OberhettingerSubject: Mars Pathfinder Flight Software Development Process (1997) Abstract: Mars Pathfinder (MPF) flight software development departe

2、d from strict adherence to then existing institutional software standards in order to produce software that would contribute to lower operations cost and minimize the overall cost to the project. Innovations included early software planning, getting software and hardware together early, avoiding exc

3、essive use of CASE tools, and development of a “Flight-Like Test Set” for early unit and integration testingDescription of Driving Event: Beyond meeting mission requirements, the Mars Pathfinder (MPF) flight software development effort focused on producing software that would contribute to lower ope

4、rations cost and minimize the overall cost to the project. This cost consciousness necessitated the establishment of low cost software development processes compatible with short duration missions. These new processes did not require strict adherence to then existing institutional software standards

5、.Additional Keyword(s): System Architecture, Software Life Cycle, Rapid Prototyping, Concurrent EngineeringReference(s): Glenn Reeves, “Mars Pathfinder Flight Software Lessons Learned,“ April 28, 1997.Lesson(s) Learned: 1. Establish a software implementation plan early that outlines the basic strate

6、gy, including reviews, standards, processes, schedule, and deliverables.2. Get software and hardware together early in the development cycle, with hardware-software integration performed by the flight software team. Using the flight software team to identify Provided by IHSNot for ResaleNo reproduct

7、ion or networking permitted without license from IHS-,-,-integration problems is efficient, since it is the party responsible for fixing them.3. Make early, conscious, engineering decisions on the applicability of computer-aided software engineering (CASE) tools. Beyond basic software development pl

8、anning, their use can consume resources and prove counterproductive.4. Develop a “Flight-Like Test Set“ (FLTS) for early unit and integration testing. The MPF FLTS test set (shown below) was comprised of commercial hardware and simulation software assembled by the flight team members. Both the space

9、craft and FLTS used a standard VME bus and software architecture, thus avoiding any duplication of effort. refer to D descriptionD MPF Flight-Like Test Set (FLTS) 5. Provide the flight software team with a dedicated flight software testbed equipped with engineering model hardware. Such a testbed per

10、mits development and checkout of flight software in parallel with development of electronics and sensors.6. The MPF project avoided the overhead associated with strict adherence to documentation and coding standards since no inheritance by future projects was planned. However, project(s) inheriting

11、this software have since encountered problems due to limited documentation.Recommendation(s): See Lessons LearnedProvided by IHSNot for ResaleNo reproduction or networking permitted without license from IHS-,-,-Evidence of Recurrence Control Effectiveness: N/ADocuments Related to Lesson: N/AMission

12、Directorate(s): N/AAdditional Key Phrase(s): a71 Cryogenic Systemsa71 Industrial Operationsa71 Occupational Healtha71 Personal Protective EquipmentAdditional Info: Approval Info: a71 Approval Date: 1998-06-09a71 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-,-,-