Value of Use Cases in AI: Insights from a Foundation Model Approach
Explore the source record for details and available documents.
Rahul Ramachandran↗
SEARCH · Search NASA
Results for “Use Cases”
Search indexed NASA NTRS and DOE OSTI research on propulsion, heat transfer, battery materials and energy systems. Follow report and document links to the original sources.
Quote a phrase for an exact phrase match. Source license links do not imply unrestricted reuse.
Language Model Applications to Scientific Tools: Exploring Use Cases in Data Visualization
Explore the source record for details and available documents.
Patrick Maynard↗
New Solid Propellant Additives: Evaluation for NASA Mission Use Cases
Researchers and small companies have been investigating and developing new solid rocket motor propellant ingredients with renewed vigor. Lithium-aluminum alloy is an ingredient of particular interest, but most of the advertisement about its benefits are focused on defense tactical rocket applications. This paper develops a framework to evaluate this and other propellants against standard aluminized composite propellant for mass-limited missions like many NASA in-space applications. It shows a way to estimate density’s effect with an exponent less than 1 depending on mission and technology parameters, and an algorithm for directly calculating delta-velocity or payload performance improvement.
Lithium-aluminum↗
Engineering Against Digital Risk in CIP Applications: Cyber-Informed Engineering Use Cases
Cyber-Informed Engineering (CIE) addresses the reality that cyber attacks on engineered systems can have consequences far beyond data loss or disruption of digital networks. When control systems are compromised, safety, reliability, and performance of the physical process itself may be threatened. This presentation discusses engineered controls of 7 categories and the CIE database of controls that provides clear examples and guidance for defining and applying engineered controls in CIE. It explains what engineered controls are, how they differ from information security measures, and how they are integrated into system design.
99 - GENERAL AND MISCELLANEOUS↗
Simulation budgeting for hybrid effective field theories
In this work, we forecast the number of, and requirements on, N-body simulations needed to train hybrid effective field theory (HEFT) emulators for a range of use cases, using a hybrid of HMcode and perturbation theory as a surrogate model. Our accuracy goals, determined with careful consideration of statistical and systematic uncertainties, are 1% accurate in the high-likelihood range of cosmological parameters, and 2% accurate over a broader parameter space volume for k < 1 h Mpc -1 and z < 3. Focusing in part on the 8-parameter w 0 w a CDM+ m ν cosmological model, we find that < 225 simulations are required to meet our error goals over our wide parameter space, including models with rapidly evolving dark energy, given our simulation and emulator recommendations. For a more restricted parameter space volume, as few as 80 simulations are sufficient. We additionally present simulation forecasts for example use cases, and make the code used in our analyses publicly available. These results offer practical guidance for efficient emulator design and simulation budgeting in future cosmological analyses.
cosmological parameters from LSS↗
Experimental Applications of Automatic Test Markup Language (ATML)
The authors describe challenging use-cases for Automatic Test Markup Language (ATML), and evaluate solutions. The first case uses ATML Test Results to deliver active features to support test procedure development and test flow, and bridging mixed software development environments. The second case examines adding attributes to Systems Modelling Language (SysML) to create a linkage for deriving information from a model to fill in an ATML document set. Both cases are outside the original concept of operations for ATML but are typical when integrating large heterogeneous systems with modular contributions from multiple disciplines.
Lansdowne, Chatwin A.↗
Sherlock Data Warehouse
This slide deck provides an overview of the data and resources available in the Sherlock Data Warehouse. Sherlock was developed and is currently maintained by the Aviation Systems Division at NASA Ames Research Center. Sherlock contains a valuable collection of flight, air traffic management, and weather data. But Sherlock is not just a data archive. Sherlock also includes tools and resources to access, download, and visualize data, as well as resources to process the data. This overview summarizes Sherlock data sources, demonstrates data analytics and visualization with MicroStrategy, illustrates disparate data integration using the ATM Knowledge graph, and presents a machine learning use case using the Big Data system.
data warehouse↗
Transitioning from Software Requirements Models to Design Models
The Scenario Creation and Simulation Process (SCASP) includes the following steps: 1) Write Requirements; 2) Write Use Cases; 3) Prioritize Use Cases; 4) Write Nominal Scenarios; 5) Identify Relationships; 6) Refine/Generalize Scenarios; 7) Transform to State Machines. SCASP provides thorough simulation of use cases before design/implementation, resulting in: 1) Reduced cost; 2) Fewer misunderstandings; 3) Reuse of executable form of use cases. SCASP gives systematic guidelines on how to 1) Separate concerns in use case descriptions; 2) Elicit non-nominal scenarios (alternatives, exceptions, concurrent scenarios, etc.); 3) Transform those scenarios automatically into a set of concurrent state machines; 4) Execute those state machines, i.e., scenario simulation.
Whittle, Jon↗
Object Oriented Modeling and Design
The Object Oriented Modeling and Design seminar is intended for software professionals and students, it covers the concepts and a language-independent graphical notation that can be used to analyze problem requirements, and design a solution to the problem. The seminar discusses the three kinds of object-oriented models class, state, and interaction. The class model represents the static structure of a system, the state model describes the aspects of a system that change over time as well as control behavior and the interaction model describes how objects collaborate to achieve overall results. Existing knowledge of object oriented programming may benefit the learning of modeling and good design. Specific expectations are: Create a class model, Read, recognize, and describe a class model, Describe association and link, Show abstract classes used with multiple inheritance, Explain metadata, reification and constraints, Group classes into a package, Read, recognize, and describe a state model, Explain states and transitions, Read, recognize, and describe interaction model, Explain Use cases and use case relationships, Show concurrency in activity diagram, Object interactions in sequence diagram.
Shaykhian, Gholam Ali↗
Quantum Key Distribution Applicability to Smart Grid Cybersecurity Systems
To meet the increasing demand for electricity and to have a more reliable and resilient electric grid against conventional and extreme events, grid modernization is more crucial now than ever before. This will require the development and deployment of devices that provide advanced communication capabilities. The overall efficiency, reliability, and resilience of the smart grid will be inextricably linked to the exchange of information between these devices. Unfortunately, the increased information flow will increase the potential attack surface and introduce new vulnerabilities. While a smarter grid will depend critically on information flow, these benefits will be accrued only if that information can be protected. Nowadays, information is secured in smart grids primarily through cryptography. However, with the increasing number of sophisticated attacks as well as the increasing computational power, the security of the “classical” cryptographic algorithms is threatened. Quantum information science offers solutions to this problem, specifically quantum key distribution (QKD), which provides a means for the generation and secure distribution of symmetric cryptographic keys. The security of QKD stems ultimately from the very nature of quantum physics. In this paper, we investigate the applicability of QKD to the various smart grid sectors and specific use cases. We have identified 18 smart grid use cases of interest for QKD suitability together with 7 QKD factors used for the assessment of the various use cases. For each use case, the impact to security of the loss of confidentiality, integrity, and/or availability is specified. In addition, the suitability of QKD is assessed for each use case with respect to multiple factors.
24 POWER TRANSMISSION AND DISTRIBUTION↗
BuildingSync® v.2.7.0 (released 9.11.2025) [SWR-18-28]
BuildingSync® is a building data exchange schema to better enable integration between software tools and building data workflows. The schema's original use case was focused on commercial building energy audits; however, several additional use cases have been realized including building energy modeling and more high-level generic building data exchange. Version 2.7.0 adds new elements for file attachment feature and FederalBuilding, and generalizes usage of Optional Elements (e.g. EquipmentCondition, EquipmentID) to all assets/systems. BuildingSync helps streamline the data exchange process, improving the value of the data, minimizing duplication of effort for subsequent building data collection efforts (including audits), and facilitating the achievement of greater energy efficiency. This in done in part by standardizing on (a) reporting audits in an electronic format, (b) tracking proposed, implemented, and discarded energy conservation measures, and (c) storing building characteristics (at multiple levels) for audits, benchmarking, and building energy analysis. BuildingSync has several documents and tools available to help users understand how to best leverage BuildingSync. The list below are only a subset of the resources available. If new resources are discovered, then feel free to create a new pull request with the additions. Generic BuildingSync information is available on the DOE website and the project website. BuildingSync Examples - These examples are kept up to date and show a wide range of implementations. Any new update to BuildingSync is required to pass validation on these example files. BuildingSync Use Case Validator allows for users to determine if their instance complies with a specific use case for BuildingSync by checking if the required elements are implemented in an uploaded instance. An API is also provided for automated integration into other tools. Also, the website contains an easy way to view the entirety of the schema and how elements relate to the Building Exchange Data Exchange Specification. The Validator is open sourced here Use Case TestSuite provides a Python package for easier generation of BuildingSync use cases. BuildingSync use cases depend on the generation of schematron documents, which is time-consuming and difficult to implement well. The TestSuite allows users to define a use case using a more palatable CSV template, which it then turns into a Schematron document. The source code is available here. BuildingSync to OpenStudio/EnergyPlus. The translator is open sourced here. This project will translate a Level 1 (and partial Level 2) ASHRAE Energy Audit to a fully defined OpenStudio and EnergyPlus model. This project is in early Beta testing and any feedback is welcome!
Long, Nicholas [National Renewable Energy Lab. (NR↗
Research Data Alliance: Understanding Big Data Analytics Applications in Earth Science
The Research Data Alliance (RDA) enables data to be shared across barriers through focused working groups and interest groups, formed of experts from around the world - from academia, industry and government. Its Big Data Analytics (BDA) interest groups seeks to develop community based recommendations on feasible data analytics approaches to address scientific community needs of utilizing large quantities of data. BDA seeks to analyze different scientific domain applications (e.g. earth science use cases) and their potential use of various big data analytics techniques. These techniques reach from hardware deployment models up to various different algorithms (e.g. machine learning algorithms such as support vector machines for classification). A systematic classification of feasible combinations of analysis algorithms, analytical tools, data and resource characteristics and scientific queries will be covered in these recommendations. This contribution will outline initial parts of such a classification and recommendations in the specific context of the field of Earth Sciences. Given lessons learned and experiences are based on a survey of use cases and also providing insights in a few use cases in detail.
Riedel, Morris↗
Third Sonic Boom Prediction Workshop Cases: Analysis Using the NASA PCBoom
This paper presents simulation results and analyses using the test cases provided for the Third Sonic Boom Prediction Workshop of the American Institute of Aeronautics and Astronautics. The simulation focuses on propagation to the ground of sonic boom generated by supersonic aircraft accounting for atmospheric effects. The simulation results use the NASA PCBoom propagation code that features the latest updates on the ray tube area and kinematic ray tracing algorithms to better predict waveforms and sonic boom carpet edges, respectively.
low boom↗
Sequence Diagrams & PFMEA Table - VGI [SWR-25-107]
As part of the VGI work under the National Charging Experience (ChargeX) Consortium, reliability analysis of communication interfaces for multiple SCM/VGI use-cases was performed using a Process Failure Modes and Analysis (PFMEA) style framework. This repository hosts all the relevant files for each of these use-cases which include: *A visual representation of their communication architecture: Image file (.png) *UML sequence diagram: Plant-UML source file (.puml). Visio file (.vsdx) and image file (.png) derived from the UML sourceX` *The PFMEA table: Excel file (.xlsx) These files are meant to serve as a starting point and can be adapted to company / organization specific SCM implementation.
Gadamsetty, Pranav [National Renewable Energy Labo↗
SMART NAS Test Bed Overview
These slides presents an overview of SMART NAS Test Bed. The test bed is envisioned to be connected to operational systems and to allow a new concept and technology to be evaluated in its realistic environment. Its role as an accelerator of concepts and technologies development, its use cases and use-case-driven development approach, and its state are presented.
rapid development↗
Establishing the Framework for e-VTOL Flight Mission Scenario Development for Urban Air Mobility Research using Cognitive Task Analysis
This paper focuses on applying specific protocol aspects of Cognitive Task Analysis (CTA) methods to formulate non-routine flight mission use-case scenarios in support of a potential research study at the National Aeronautics and Space Administration (NASA) Langley Research Center under the Air Traffic Management – eXploration (ATM-X) Urban Air Mobility (UAM) sub-project. The objective of use-case scenarios is to provide a hypothetical situation to elicit expert knowledge and feedback in a specific subject matter area. Use-case scenarios in the field of aviation, including UAM, can help to support the safe integration of these vehicles into the National Airspace System (NAS) through the examination of airspace procedures during non-routine events. Inherent in this type of research is the need to study in-flight non-routine scenarios that the UAM vehicle could encounter. Situations categorized as non-routine events are any events that occur outside of the original flight plan such as a mechanical malfunction or other in-flight emergency requiring special procedures, which can include diversions to a specified, or non-specified, emergency landing area. In specific instances, some non-routine events could be considered as “routine” during in-flight operations, such as the need to perform a go-around due to a balked landing. As the rate of technological expansion surrounding UAM grows rapidly in modern aviation, so does the need for research that focuses on the safe integration of these vehicles including research with a focus on the methods and development of airspace operational procedures. Research rooted in CTA methods provides a framework for developing use-case scenarios appropriate for environments where mental demands are substantial. Substantial mental demands exist while operating in the NAS for pilots, airline dispatchers, and air traffic controllers among many others. With the focus on UAM in mind, it is critical to frame a baseline use-case scenario using information as it pertains to current-day airspace operations. According to Dr. Robert R. Hoffman’s “Protocols for Cognitive Task Analysis,” one of the first steps to applying CTA methods to research is the concept of “bootstrapping” in which the researcher(s) familiarize themselves with the domain that is being studied. To formulate the non-routine flight mission use-case scenarios for the purpose of this potential NASA ATM-X UAM research study, and to inform the baseline use-case scenario, the practice of bootstrapping was utilized to acquire knowledge of current-day airspace procedures.
Heidi S Glaudel↗
The Use of UML for Software Requirements Expression and Management
It is common practice to write English-language "shall" statements to embody detailed software requirements in aerospace software applications. This paper explores the use of the UML language as a replacement for the English language for this purpose. Among the advantages offered by the Unified Modeling Language (UML) is a high degree of clarity and precision in the expression of domain concepts as well as architecture and design. Can this quality of UML be exploited for the definition of software requirements? While expressing logical behavior, interface characteristics, timeliness constraints, and other constraints on software using UML is commonly done and relatively straight-forward, achieving the additional aspects of the expression and management of software requirements that stakeholders expect, especially traceability, is far less so. These other characteristics, concerned with auditing and quality control, include the ability to trace a requirement to a parent requirement (which may well be an English "shall" statement), to trace a requirement to verification activities or scenarios which verify that requirement, and to trace a requirement to elements of the software design which implement that requirement. UML Use Cases, designed for capturing requirements, have not always been satisfactory. Some applications of them simply use the Use Case model element as a repository for English requirement statements. Other applications of Use Cases, in which Use Cases are incorporated into behavioral diagrams that successfully communicate the behaviors and constraints required of the software, do indeed take advantage of UML's clarity, but not in ways that support the traceability features mentioned above. Our approach uses the Stereotype construct of UML to precisely identify elements of UML constructs, especially behaviors such as State Machines and Activities, as requirements, and also to achieve the necessary mapping capabilities. We describe this approach in the context of a space-based software application currently under development at the Jet Propulsion Laboratory.
model-based engineering↗
Space Telecommunications Radio System Software Architecture Concepts and Analysis
The Space Telecommunications Radio System (STRS) project investigated various Software Defined Radio (SDR) architectures for Space. An STRS architecture has been selected that separates the STRS operating environment from its various waveforms and also abstracts any specialized hardware to limit its effect on the operating environment. The design supports software evolution where new functionality is incorporated into the radio. Radio hardware functionality has been moving from hardware based ASICs into firmware and software based processors such as FPGAs, DSPs and General Purpose Processors (GPPs). Use cases capture the requirements of a system by describing how the system should interact with the users or other systems (the actors) to achieve a specific goal. The Unified Modeling Language (UML) is used to illustrate the Use Cases in a variety of ways. The Top Level Use Case diagram shows groupings of the use cases and how the actors are involved. The state diagrams depict the various states that a system or object may be in and the transitions between those states. The sequence diagrams show the main flow of activity as described in the use cases.
Handler, Louis M.↗