Search NASA⌕ Search

SEARCH · Search NASA

Results for “reference language”

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.

At least 19 records

The preliminary SOL (Sizing and Optimization Language) reference manual

The Sizing and Optimization Language, SOL, a high-level special-purpose computer language has been developed to expedite application of numerical optimization to design problems and to make the process less error-prone. This document is a reference manual for those wishing to write SOL programs. SOL is presently available for DEC VAX/VMS systems. A SOL package is available which includes the SOL compiler and runtime library routines. An overview of SOL appears in NASA TM 100565.

Lucas, Stephen H.↗

UMP Reference Language - Examples

This document provides example language for referencing the use of Uniform Methods Project (UMP) protocols followed by examples of language that is currently in use, which helps the reader understand when and how the protocols are used and ensures consistent citation of relevant UMP protocols.

29 ENERGY PLANNING, POLICY, AND ECONOMY↗

Ada style guide (version 1.1)

Ada is a programming language of considerable expressive power. The Ada Language Reference Manual provides a thorough definition of the language. However, it does not offer sufficient guidance on the appropriate use of Ada's powerful features. For this reason, the Goddard Space Flight Center Ada User's Group has produced this style guide which addresses such program style issues. The guide covers three areas of Ada program style: the structural decomposition of a program; the coding and the use of specific Ada features; and the textural formatting of a program.

Seidewitz, Edwin V.↗

Ada (trademark) projects at NASA. Runtime environment issues and recommendations

Ada practitioners should use this document to discuss and establish common short term requirements for Ada runtime environments. The major current Ada runtime environment issues are identified through the analysis of some of the Ada efforts at NASA and other research centers. The runtime environment characteristics of major compilers are compared while alternate runtime implementations are reviewed. Modifications and extensions to the Ada Language Reference Manual to address some of these runtime issues are proposed. Three classes of projects focusing on the most critical runtime features of Ada are recommended, including a range of immediately feasible full scale Ada development projects. Also, a list of runtime features and procurement issues is proposed for consideration by the vendors, contractors and the government.

Roy, Daniel M.↗

Reference Interoperability Procurement Language

Achieving interoperability involves reaching agreement on common interfaces and promoting interoperability through performance specifications. Effective integration practices are a simple, effective, and direct way of addressing the challenge. By deciding on an integration approach with well-defined interfaces and selecting systems and devices that conform to that approach and choosing integrators that have experience implementing the chosen approach, many problems can be avoided. No integration effort is seamless but by specifying interoperability requirements during the procurement process typical problems from ad hoc approaches can be avoided or reduced. By continuing this approach to its conclusion at the end of the procurement process, these same interoperability requirements may lead themselves to specified performance criteria that can be used to measure interoperability during implementation. The contractual language may contain performance incentives and penalties tied to these requirements as appropriate.

29 ENERGY PLANNING, POLICY, AND ECONOMY↗

Advanced software techniques for data management systems. Volume 3: Programming language characteristics and comparison reference

A comparative evaluation was made of eight higher order languages of general interest in the aerospace field: PL/1; HAL; JOVIAL/J3; SPL/J6; CLASP; ALGOL 60; FORTRAN 4; and MAC360. A summary of the functional requirements for a language for general use in manned aerodynamic applications is presented. The evaluation supplies background material to be used in assessing the worth of each language for some particular application.

James, T. A.↗

Reference manual for a Requirements Specification Language (RSL), version 2.0

This report is a Reference Manual for a general-purpose Requirements Specification Language, RSL. The purpose of RSL is to specify precisely the external structure of a mechanized system and to define requirements that the system must meet. A system can be comprised of a mixture of hardware, software, and human processing elements. RSL is a hybrid of features found in several popular requirements specification languages and includes constructs for formal mathematical specification.

Fisher, Gene L.↗

Cybersecurity Considerations for State Procurement of Solar Assets

This tool provides an overview of existing procurement programs and example language that prioritizes cybersecurity language and references that can readily be applied to state solar cybersecurity practices . The tool also identifies sample language for procurement agreements, contracts, and grants which can serve as lower entry points for state officials interested in pursuing this subject matter more immediately. As this approach may be novel for many states, the information therein should be considered as a model only . The programs and example language included are not exhaustive and should be evaluated in accordance with state processes and policies .

14 SOLAR ENERGY↗

KB3D Reference Manual

This paper is a reference manual describing the implementation of the KB3D conflict detection and resolution algorithm. The algorithm has been implemented in the Java and C++ programming languages. The reference manual gives a short overview of the detection and resolution functions, the structural implementation of the program, inputs and outputs to the program, and describes how the program is used. Inputs to the program can be rectangular coordinates or geodesic coordinates. The reference manual also gives examples of conflict scenarios and the resolution outputs the program produces.

Munoz, Cesar↗

Assisted Authoring of Model-Based Systems Engineering Documents

In systems engineering practices system design and analysis have historically been performed using a document-centric approach where stakeholders produce a number of documents that represent their views on a system under development. Given the ad-hoc, disparate, and informal nature of natural language documents, these views become quickly inconsistent. Rigor in engineering work is also lost in the transition from model based engineering design and analysis to engineering documents. Once the documents are delivered, the engineering portion of the work is disconnected. In the Open Model Based Engineering Environment (OpenMBEE), Cross-References (aka transclusions) synthesize data for engineering when the information is not simply hyperlinked, but referenced in place in a document, upgrading a document-based process with model-based engineering technology. Those Cross-References are nowadays partially created manually, putting a burden on the engineer who is authoring the document.This paper presents an approach which can assist the engineer by providing machine-generated suggestions for Cross-References using language processing, graph analysis, and clustering technologies on model data managed by the OpenMBEE infrastructure.

Gomes, Ivan↗

Global wave energy resource classification system for regional energy planning and project development

Efforts to streamline and codify wave energy resource characterization and assessment for regional energy planning and wave energy converter (WEC) project development have motivated the recent development of resource classification systems. Given the unique interplay between WEC absorption and resource attributes, viz, available wave power frequency, directionality, and seasonality, various consensus resource classification metrics have been introduced. However, the main international standards body for the wave energy industry has not reached consensus on a wave energy resource classification system designed with clear goals to facilitate resource assessment, regional energy planning, project site selection, project feasibility studies, and selection of WEC concepts or archetypes that are most suitable for a given wave energy climate. In this work, a primary consideration of wave energy generation is the available energy that can be captured by WECs with different resonant frequency and directional bandwidths. Therefore, the proposed classification system considers combinations of three different wave power classifications: the total wave power, the frequency-constrained wave power, and the frequency-directionally constrained wave power. The dominant wave period bands containing the most wave power are sub-classification parameters that provide useful information for designing frequency and directionally constrained WECs. The bulk of the global wave energy resource is divided into just 22 resource classes representing distinct wave energy climates that could serve as a common language and reference framework for wave energy resource assessment if codified within international standards.

16 TIDAL AND WAVE POWER↗

Standardization of Smart Contracts for Energy Markets and Operation

This work presents a formal review of smart contracts, including definitions, technical requirements, and potential power and energy-related use cases. This includes in-depth discussions covering cybersecurity, legality and interoperability goals that must be taken into consideration by potential end-users. The paper presents a first attempt towards the standardization of smart contracts (SCs) within the field of power and energy as a work in progress activity under the IEEE Standards Association (IEEE SA) P2418.5 Working Group. This work also proposes a holistic, language-agnostic reference model that is intended to accelerate the adoption of Distributed Ledger Technology (DLT) by industry stakeholders by providing standardized processes. Finally, the paper discusses key takeaways that must continue to be developed to increase SC usage within the energy industry.

Blockchain, smart contracts, DLT↗

Review of Estelle and LOTOS with respect to critical computer applications

Man rated NASA space vehicles seem to represent a set of ultimate critical computer applications. These applications require a high degree of security, integrity, and safety. A variety of formal and/or precise modeling techniques are becoming available for the designer of critical systems. The design phase of the software engineering life cycle includes the modification of non-development components. A review of the Estelle and LOTOS formal description languages is presented. Details of the languages and a set of references are provided. The languages were used to formally describe some of the Open System Interconnect (OSI) protocols.

Bown, Rodney L.↗

Tools reference manual for a Requirements Specification Language (RSL), version 2.0

This report describes a general-purpose Requirements Specification Language, RSL. The purpose of RSL is to specify precisely the external structure of a mechanized system and to define requirements that the system must meet. A system can be comprised of a mixture of hardware, software, and human processing elements. RSL is a hybrid of features found in several popular requirements specification languages, such as SADT (Structured Analysis and Design Technique), PSL (Problem Statement Language), and RMF (Requirements Modeling Framework). While languages such as these have useful features for structuring a specification, they generally lack formality. To overcome the deficiencies of informal requirements languages, RSL has constructs for formal mathematical specification. These constructs are similar to those found in formal specification languages such as EHDM (Enhanced Hierarchical Development Methodology), Larch, and OBJ3.

Fisher, Gene L.↗

STAR (Simple Tool for Automated Reasoning): Tutorial guide and reference manual

STAR is an interactive, interpreted programming language for the development and operation of Artificial Intelligence application systems. The language is intended for use primarily in the development of software application systems which rely on a combination of symbolic processing, central to the vast majority of AI algorithms, with routines and data structures defined in compiled languages such as C, FORTRAN and PASCAL. References to routines and data structures defined in compiled languages are intermixed with symbolic structures in STAR, resulting in a hybrid operating environment in which symbolic and non-symbolic processing and organization of data may interact to a high degree within the execution of particular application systems. The STAR language was developed in the course of a project involving AI techniques in the interpretation of imaging spectrometer data and is derived in part from a previous language called CLIP. The interpreter for STAR is implemented as a program defined in the language C and has been made available for distribution in source code form through NASA's Computer Software Management and Information Center (COSMIC). Contained within this report are the STAR Tutorial Guide, which introduces the language in a step-by-step manner, and the STAR Reference Manual, which provides a detailed summary of the features of STAR.

Borchardt, G. C.↗

Towards a Methodology for Identifying Program Constraints During Requirements Analysis

Requirements analysis is the activity that involves determining the needs of the customer, identifying the services that the software system should provide and understanding the constraints on the solution. The result of this activity is a natural language document, typically referred to as the requirements definition document. Some of the problems that exist in defining requirements in large scale software projects includes synthesizing knowledge from various domain experts and communicating this information across multiple levels of personnel. One approach that addresses part of this problem is called context monitoring and involves identifying the properties of and relationships between objects that the system will manipulate. This paper examines several software development methodologies, discusses the support that each provide for eliciting such information from experts and specifying the information, and suggests refinements to these methodologies.

Romo, Lilly↗