The guidance for this requirement applies to software Classes A though E (see SWE-020). Inventory information for software Classes F through H are captured separately and maintained by the NASA Chief Information Officer.
Periodically the OCE (Office of the Chief Engineer) issues a request to the Centers with instructions for an update to the inventory of software projects under its purview. When these instructions are completed, the resulting submission provides the information necessary to complete the data collection for the software inventory for projects containing Class A, B, C, D, and E software. The OCE typically reviews the Center submissions for consistency and reliability. The OCE may augment the Center submissions with comments on Center inputs from Mission Directorates, support offices, and other Centers, if appropriate. Execution of the software inventory process results in a prioritized list of projects based on the criticality of software under development or maintenance.
There is a minimal set of data collected for Class D and Class E software. Since projects containing exclusively Classes F, G, and H software are inventoried separately under the direction of the Chief Information Officer, they are not required to report under the OCE request.
The OCE software inventory is officially maintained in SIMS. Access to this password protected site is controlled by the OCE.
The OCE requires that a "Designated Point of Contact" (DPC) be named at each Center for the inventory activities. The DPC (or a designee) will be responsible for accessing the Software Inventory Management System (SIMS) and entering the Center's updated data into the system, or in the case of a new project, creating a new entry in the SIMS tool. The Center S&MA personnel will also have access to SIMS to enable the updating of the S&MA information for their Center's projects. All data must be reviewed and prioritized at the Center (based on the criticality and risk inherent in the project) by the appropriate Center personnel. The review must include participation by the representatives of the local S&MA office.
Detailed instructions for completing the software inventory survey are contained in the annual call letter for the inventory from the OCE. Entries for the software inventory include:
- Project information.
- Software title(s).
- Whether the software in development is safety critical.
- The size in KSLOC (Thousand Software Lines of Code)s
- Whether it is using the NASA IV&V facility services.
- The current software classification.
- Dates of major milestone reviews.
- The percentage of new or reused code.
- The software quality assurance effort on the project.
- Indications of primary and secondary languages being used.
- Contact information.
- Other identifying data.
The instructions counsel the DPC (designated point of contact) to include facility software as part of the Center's data inputs.
One particular instruction of note states that if a project contains software of multiple classes, the data requirements are to be based on the highest class.
In addition to the OCE review of the Center's submission, the OCE may review the Center software inventory at its periodic software surveys at the Center. See the reference to the OCE survey worksheet in the section of this guidance for an indication of how the information from the software inventory may be reviewed.