NASA ENGINEERING NETWORK
Follow this link to skip to the main content
+ Contact LLIS
Go
ABOUT NASALATEST NEWSMULTIMEDIAMISSIONSMyNASAWORK FOR NASA

+ NASA Home
FIND ENGINEERING RESOURCES BY
LLIS HOME
NASA CENTERS
MISSION DIRECTORATE
TOPICS
BY YEAR


Public Lessons Learned Entry: 1022

Lesson Info:

  • Lesson Number: 1022
  • Lesson Date: 1997-02-01
  • Submitting Organization: HQ
  • Submitted by: David M. Lengyel

Subject:

Computer Software/Software Safety Policy Requirements/Potential Inadequacies

Description of Driving Event:

Potential Inadequacy of NASA Agencywide Software Safety Policy Requirements

Lesson(s) Learned:

NASA has put considerable effort into the reorganization of its software activities and has made significant progress. It does not yet, however, have a comprehensive, clear set of roles and responsibilities for various groups within the Agency with respect to software development, safety, V&V, and software process development.

Recommendation(s):

NASA should ensure that there is a clear, universally well-understood, widely promulgated, and enforced NASA Policy Directive on the roles and responsibilities of its various organizations vis-à-vis software development and safety. Moreover, that Policy Directive should specify organizational roles and responsibilities solely on the basis of technical and administrative capability.

Evidence of Recurrence Control Effectiveness:

NASA agrees with the recommendation. The July 1996 (draft) program plan for the Fairmont (IV&V) Facility is the contract between Code Q and the Facility and will be updated for future funding and delegation of the software assurance program. NASA concurs that the draft plan now contains ambiguities but will be clarified in the next update.

The IV&V Facility's reporting structure will be finalized in the upcoming proposed Ames Research Center reorganization. It is anticipated that the IV&V Facility will be moved from under the direction of Code I at Ames and installed as the equivalent of a Directorate in the new ARC organization.

The IV&V Facility Business Plan currently defines the roles and responsibilities of the IV&V Facility. NASA Headquarters will establish and document at the policy level the roles in the Agency for all software, including embedded and flight system software. The policies document will explain how the roles and responsibilities of the Agencywide software efforts mentioned in the finding (e.g., CIO, COE-IT, IV&V Facility) fit together in a synergistic manner within the Agency.

The new NPD 2820 will define Agency policy for program/project utilization of the IV&V Facility. The Chief Information Officer, the Chief Engineer's Office, the Office of Safety and Mission Assurance, and the Software Working Group will be responsible for increasing Agency awareness of all the software-related resources, policies, and existing standards. The newly implemented Code Q process verification activity will validate Agency project managers' awareness of software assurance policy and procedures for compliance in software development efforts.

Documents Related to Lesson:

N/A

Mission Directorate(s):

  • Exploration Systems
  • Aeronautics Research

Additional Key Phrase(s):

  • Aerospace Safety Advisory Panel
  • Computers
  • Policy & Planning
  • Research & Development
  • Safety & Mission Assurance
  • Software
  • Test & Verification

Additional Info:

    Approval Info:

    • Approval Date: 2001-11-20
    • Approval Name: Bill Loewy
    • Approval Organization: QS
    • Approval Phone Number: 202-358-0528


    FirstGov - Your First Click to the US Government
    + 2004 Vision for Space Exploration
    + FY 2005 Budget Request
    + 2003 Strategic Plan
    + Freedom of Information Act
    + The President's Management Agenda
    + FY 2003 Agency Performance and Accountability Report
    + NASA Privacy Statement, Disclaimer,
    and Accessibility Certification

    + Freedom to Manage
    NASA
    Curator:Manson Yew
    NASA Official: Gregory Robinson
    + Contact LLIS