Public Metadata Alt. Plan B STRS Public Metadata Alternative (Plan B) "*" indicates required fields SWL03_1_ApplicationName*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. SWL03_1_ApplicationVersionEnter the version, if known: SWL03_1_ApplicationIdentificationEnter the your identification number (NTR#, LEW#, NPO#, etc.), if known: SWL03_4_ItemType*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. ApplicationComponentDeviceOEServiceToolOtherSWL03_4_ItemTypeOtherItem type submitted when Other selected above. SWL03_3_Usage*Short Description of the usage: (maximum of 80 characters) SWL03_3_FunctionalDescription*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. SWL03_4_TransmitOrReceive*Enter the main capabilities of the item (Click on one of the example buttons provided to avoid typing: TransmitReceiveBothNetworkingCognitiveComputationOEFlight ControlTestOtherSWL03_4_TransmitOrReceiveOtherEnter the main capabilities of the item when Other selected above. SWL03_2_TargetPlatformEnter the target platform (Enter name of target system, OS, FPGAs, tools, and versions, etc.) SWL15_SWClassificationEnter 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.Not determined or N/AClass A: Human Rated Space Software SystemsClass B: Non-Human Space Rated Software Systems or Large Scale Aeronautics VehiclesClass C: Mission Support Software or Aeronautic Vehicles, or Major Engineering/Research Facility SoftwareClass D: Basic Science/Engineering Design and Research and Technology SoftwareClass E: Small Light Weight Design Concept and Research and Technology SoftwareClass F: General Purpose Computing Software (Multi-Center or Multi- Program/Project)Class G: General Purpose Computing Software (Single Center or Project)Class H: General Purpose Desktop SoftwareSWL16_SafetyCritical*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. Yes No SWL03_6_DeploymentDateEnter 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. MM slash DD slash YYYY SWL03_7_SWArchitectureAndVersion*Enter the software architecture and versionNoneSTRS v1.02NASA-STD-4009NASA-STD-4009ASTRXOMG STIOtherSWL03_7_SWArchitectureAndVersionOtherEnter the software architecture and version when Other selected above. SWL03_8_ReleaseCategoryEnter the release category NASA only: more detail in NPR 2210.1 in section A.2PUBLICOPENFOREIGNUSGPRBETAPROJECTDEVINTERAGENCYNASANONEVENDORTBDSWL03_9_ExportControlRestrictions*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. NONE ITAR SBU EAR Unknown SWL03_9_ReleaseRestrictions*Enter any contract restrictions: None Agreement Copyright Patent SWL03_11_AvailabilityOfModels*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. Yes No SWL03_14_TRL_LevelEnter the Technology Readiness Level (TRL): NASA only: more detail in NPR 7123.1B, Appendix E.1. Basic principles observed and reported.2. Technology concept and/or application formulated.3. Analytical and experimental critical function and/or characteristic proof-of-concept.4. Component/subsystem validation in laboratory environment.5. System/subsystem/component validation in relevant environment.6. System/subsystem model or prototyping demonstration in a relevant end-to-end environment.7. System prototyping demonstration in an operational environment (ground or space).8. Actual system completed and "mission qualified" through test and demonstration in an operational environment.9. Actual system "mission proven" through successful mission operations (ground or space).SWL03_15_TRL_JustificationEnter a short (publicly viewable) TRL justification: This is usually an indication of mission and operational environment where tested and used.SWL03_5_SpaceGround*Enter whether the target/operational environment is Space or Ground. Note that this is to support TRL above. Space Only Ground Only Both Space and Ground 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: Reuse Readiness Levels as a Measure of Software Reusability Example Select one item for each RRL category below: SWL03_12_RRL_Level_D(1) Documentation1. Little or no internal or external documentation available2. Partially to fully commented source code available3. Basic external documentation for sophisticated users available4. Reference manual available5. User manual available6. Tutorials available7. Interface guide available8. Extension guide and/or design/developers guide available9. Documentation on design, customization, testing, use, and reuse is availableSWL03_12_RRL_Level_E(2) Extensibility1. No ability to extend or modify program behavior2. Very difficult to extend the software system, even for application contexts similar to the original application domain3. Extending the software is difficult, even for application contexts similar to the original application domain4. Some extensibility is possible through configuration changes and/or moderate software modification5. Consideration for future extensibility designed into the system for a moderate range of application contexts; extensibility approach defined and at least partially documented6. Designed to allow extensibility across a moderate to broad range of application contexts, provides many points of extensibility, and a thorough and detailed extensibility plan exists7. Demonstrated to be extensible by an external development team in a similar context8. Demonstrated extensibility on an external program, clear approach for modifying and extending features across a broad range of application domains9. Demonstrated extensibility in multiple scenarios, provides specific documentation and features to build extensions which are used across a range of domains by multiple user groupsSWL03_12_RRL_Level_I(3) Intellectual Property Issues1. Product developers have been identified, but no rights have been determined.2. Developers are discussing rights that comply with their organizational policies.3. Rights agreements have been proposed to developers.4. Developers have negotiated on rights agreements.5. Agreement on ownership, limited reuse rights, and recommended citation.6. Developer list, recommended citation, and rights statements have been drafted.7. Developer list and limited rights statement included in product prototype.8. Recommended citation and intellectual property rights statement included in product.9. Statements describing unrestricted rights, recommended citation, and developers embedded into product.SWL03_12_RRL_Level_M(4) Modularity1. Not designed with modularity2. (Between)3. Modularity at major system or subsystem level only4. (Between)5. Partial segregation of generic and specific functionality6. (Between)7. Clear delineations of specific and reusable components8. (Between)9. All functions and data encapsulated into objects or accessible through web service interfacesSWL03_12_RRL_Level_O(5) Packaging1. Software or executable available only, no packaging2. (Between)3. Detailed installation instructions available4. (Between)5. Software is easily configurable for different contexts6. (Between)7. OS detect and auto-build for supported platforms8. (Between)9. Installation user interface providedSWL03_12_RRL_Level_P(6) Portability1. The software is not portable2. Some parts of the software may be portable3. The software is only portable with significant costs4. The software may be portable at a reasonable cost5. The software is moderately portable6. The software is portable7. The software is highly portable8. (Between)9. The software is completely portableSWL03_12_RRL_Level_S(7) Standards Compliance1. No standards compliance2. No standards compliance beyond best practices3. Some compliance with local standards and best practices4. Standards compliance, but incomplete and untested5. Standards compliance with some testing6. Verified standards compliance with proprietary standards7. Verified standards compliance with open standards8. Verified standards compliance with recognized standards9. Independently verified standards compliance with recognized standardsSWL03_12_RRL_Level_T(8) Support1. No support available2. Minimal support available3. Some support available4. Moderate systematic support is available5. Support provided by an informal user community6. Formal support available7. Organized/defined support by developer available8. Support available by the organization that developed the asset9. Large user community with well-defined support availableSWL03_12_RRL_Level_V(9) Verification and Testing1. No testing performed2. Software application formulated and unit testing performed3. Testing includes testing for error conditions and proof of handling of unknown input4. Software application demonstrated in a laboratory context5. Software application tested and validated in a laboratory context6. Software application demonstrated in a relevant context7. Software application tested and validated in a relevant context8. Software application "qualified" through test and demonstration (meets requirements) and successfully delivered9. Actual software application tested and validated through successful use of application outputContact NameEnter your name in case there are any questions relating to the metadata. First Last SWL03_ContactEmail*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. Enter Email Confirm Email SWL03_ContactSendCopy*Would you like to receive a copy of your Public Metadata as submitted? Yes No