Skip to main content

An Assessment of Space Shuttle Flight Software Development Processes (1993) / Chapter Skim
Currently Skimming:

3. The Space Shuttle Flight Software Development Process
Pages 39-50

The Chapter Skim interface presents what we've algorithmically identified as the most significant single chunk of text within every page in the chapter.
Select key terms on the right to highlight them within pages of the chapter.


From page 39...
... On the other hand, since the applications software is too large to fit into a computer at one time, it is divided up into separate functional overlays. The overlays are stored on Mass Memory Units and are loaded into the on-board computers as Hey are needed for each phase of flight (descent, orbit, and entry)
Read the entire page →
From page 40...
... data, initialization data, telemetry format data, and flight software patches (corrections In response to late change requests and discrepancy reports) to produce a final integrated mass memory load.
Read the entire page →
From page 44...
... 44 SPACE SNUTILE FLIGHT SOFTWARE DEVELOPMENT PROCESSES .. ~ ~ ~ CG into r~: ~ ~ , / to ~ ~ ~ I 3.
Read the entire page →
From page 45...
... WE SPACE Shrilly FLIGHT SOFTWARE DEVELOPMENT PROCESS ~ o& ~ U)
Read the entire page →
From page 46...
... SPACE SHUTTLE FLIGHT SOFTWARE DEVELOPMENT PROCESSES fit' Cal 3 'A a: o C)
Read the entire page →
From page 48...
... 48 SPACE SHUlTM FLIGHT SOFTWARE DEVELOPMENT iRoCESSES | ~ E ,:a :: ~ to I -- 3 = do .?
Read the entire page →
From page 49...
... The SSMEC is delivered to the Shuttle Program Office at JSC as a finished package, i.e., as government furnished equipment. · Me Flight Crew Operational Directorate (FCODJ at ISC assesses each change or discrepancy for flight safety and operational impacts using desktop review or simulators.
Read the entire page →
From page 50...
... Over IBM and RockweD/Downey personnel independently build PASS/BFS software loads and perform bit-level comparisons with the newly built Of load. ~ Me Systems Design Contractors, Rockwell, Lockheed, and Charles Stark Draper Labs, design tests and use the SAM to verify that both the PASS and BFS flight software loads are compatible with hardware interfaces, perform as designed, and conform to He mission requirements.
Read the entire page →

Key Terms

  • software development
  • space shuttle
  • main engine
  • shuttle main
  • engine controller

  • development contractors
  • shuttle program
  • shuttle avionics
  • mass memory
  • flight data

  • backup computer
  • control board
  • bfs software
  • software control
  • software patches

  • change requests
  • discrepancy reports
  • software module
  • module designs
  • software discrepancies

  • own internal
  • furnished equipment
  • perform verification
  • late change
  • approved flight

  • approved development
  • using government
  • install late
  • memory load
  • initializing data


    • This material may be derived from roughly machine-read images, and so is provided only to facilitate research.
    More information on Chapter Skim is available.