National Aeronautics and Space Administration

Glenn Research Center

Public Metadata Alt. Plan B

STRS Public Metadata Alternative (Plan B)

  • Enter the unique name:

    This name should be used in all other forms, paperwork, and email for identification.
    NASA only: This name should be the same as the name used in the New Technology Report (NTR).
    Non-NASA: Use the name from your release process.

  • Enter the version, if known:
  • Enter the your identification number (NTR#, LEW#, NPO#, etc.), if known:
  • Enter the item type submitted (Click on one of the example buttons provided to avoid typing: , , , , , ) If none of the above, please enter a one-word or two-word summary of type.
  • Item type submitted when Other selected above.
  • Short Description of the usage: (maximum of 80 characters)
  • Enter the functional description:

    NASA only: Most of the usage and functional description may be created from the NTR data's descriptive title (1), abstract (9), description of the problem (Section I), and purpose (Section II). The capabilities should include such items as: Frequency range(s), Modulation, Spreading, Functionality, Forward Error Correction/Encoding/Decoding, User Data Rates, Over-the-air Symbol Rates, Scrambling, and Data Formatting.

  • Enter the main capabilities of the item (Click on one of the example buttons provided to avoid typing:
  • Enter the main capabilities of the item when Other selected above.
  • Enter the target platform (Enter name of target system, OS, FPGAs, tools, and versions, etc.)
  • Enter the Software Classification:

    NASA only: The software classification is determined according to NPR 7150.2A, Appendix E, or NPR 7150.2B, Appendix D, Software Classifications.

  • Is the application developed for a safety-critical system?

    NASA only: For more information, Safety Critical software is defined in detail in NASA-STD-8739.8, Appendix A, The Software Assurance Classification Assessment.

  • Enter the deployment date (mm/dd/yyyy)

    Deployment date is when the item is first used in the target environment rather than a test environment. Leave blank, if this application has not been deployed.

    Date Format: MM slash DD slash YYYY
  • Enter the software architecture and version
  • Enter the software architecture and version when Other selected above.
  • Enter the release category

    NASA only: more detail in NPR 2210.1 in section A.2

  • Are there any export control restrictions (ITAR, SBU, EAR, etc.):

    The export control restrictions may include International Traffic in Arms Regulations (ITAR), Sensitive But Unclassified (SBU), Export Administration Regulations (EAR), etc.

  • Enter any contract restrictions:
  • Enter the availability of models (Choose: Yes, No)

    Models of interest are in files that may be used by a tool to perform simulations or generate code. The description of these models and the associated tools are required elsewhere but the availability of such models to speed up the reuse process is desirable for evaluation of reuse level of effort.

  • Enter the Technology Readiness Level (TRL):

    NASA only: more detail in NPR 7123.1B, Appendix E.

  • Enter a short (publicly viewable) TRL justification:

    This is usually an indication of mission and operational environment where tested and used.

  • Enter whether the target/operational environment is Space or Ground. Note that this is to support TRL above.
  • Compute Reuse Readiness Levels (RRL) :

    The Reuse Readiness Level (RRL) Assessment will be stored in the STRS Application Repository. For background information, see NASA's Earth Observing System Data and Information System (EOSDIS) web site. Specifically, NASA's Earth Science Data System Working Group (ESDSWG) has studied reuse. References:
    1. Reuse Readiness Levels as a Measure of Software Reusability
    2. Example

    Select one item for each RRL category below:

  • (1) Documentation
  • (2) Extensibility
  • (3) Intellectual Property Issues
  • (4) Modularity
  • (5) Packaging
  • (6) Portability
  • (7) Standards Compliance
  • (8) Support
  • (9) Verification and Testing
  • Enter your name in case there are any questions relating to the metadata.
  • Enter your email address in case there are any questions relating to the metadata. Except for the submitter's email address, the data will be publicly available.
  • Would you like to receive a copy of your Public Metadata as submitted?