Search NASA⌕ Search

SEARCH · Search NASA

Results for “requirement formalization”

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 181 records · Page 10

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.↗

Generation of Requirements for Simulant Measurements

This document provides a formal, logical explanation of the parameters selected for the Figure of Merit algorithm used to evaluate lunar regolith simulant. The objectives, requirements, assumptions and analysis behind the parameters is provided. From NASA's objectives for lunar simulants a requirement is derived to verify and validate simulant performance versus lunar regolith. This requirement leads to a specification that comparative measurements be taken the same way on the regolith and the simulant. In turn this leads to a set of 9 criteria with which to evaluate comparative measurement. Many of the potential measurements of interest are not defensible under these criteria, for example many geotechnical properties of interest were not explicitly measured during Apollo and they can only be measured in situ on the Moon. A 2005 workshop identified 32 properties of major interest to users (Sibille Carpenter Schlagheck, and French, 2006). Virtually all of the properties are tightly constrained, though not predictable, if just four parameters are controlled. Three: composition, size and shape, are recognized as being definable at the particle level. The fourth, density, is a bulk property. In recent work a fifth parameter has been identified, which will need to be added to future releases of the Figure of Merit: spectroscopy.

Rickman, Doug↗

Moving formal methods into practice. Verifying the FTPP Scoreboard: Results, phase 1

This report documents the Phase 1 results of an effort aimed at formally verifying a key hardware component, called Scoreboard, of a Fault-Tolerant Parallel Processor (FTPP) being built at Charles Stark Draper Laboratory (CSDL). The Scoreboard is part of the FTPP virtual bus that guarantees reliable communication between processors in the presence of Byzantine faults in the system. The Scoreboard implements a piece of control logic that approves and validates a message before it can be transmitted. The goal of Phase 1 was to lay the foundation of the Scoreboard verification. A formal specification of the functional requirements and a high-level hardware design for the Scoreboard were developed. The hardware design was based on a preliminary Scoreboard design developed at CSDL. A main correctness theorem, from which the functional requirements can be established as corollaries, was proved for the Scoreboard design. The goal of Phase 2 is to verify the final detailed design of Scoreboard. This task is being conducted as part of a NASA-sponsored effort to explore integration of formal methods in the development cycle of current fault-tolerant architectures being built in the aerospace industry.

Srivas, Mandayam↗

Generation of Requirements for Simulant Measurements

This TM presents a formal, logical explanation of the parameters selected for the figure of merit (FoM) algorithm. The FoM algorithm is used to evaluate lunar regolith simulant. The objectives, requirements, assumptions, and analysis behind the parameters are provided. A requirement is derived to verify and validate simulant performance versus lunar regolith from NASA s objectives for lunar simulants. This requirement leads to a specification that comparative measurements be taken the same way on the regolith and the simulant. In turn, this leads to a set of nine criteria with which to evaluate comparative measurements. Many of the potential measurements of interest are not defensible under these criteria. For example, many geotechnical properties of interest were not explicitly measured during Apollo and they can only be measured in situ on the Moon. A 2005 workshop identified 32 properties of major interest to users. Virtually all of the properties are tightly constrained, though not predictable, if just four parameters are controlled. Three parameters (composition, size, and shape) are recognized as being definable at the particle level. The fourth parameter (density) is a bulk property. In recent work, a fifth parameter (spectroscopy) has been identified, which will need to be added to future releases of the FoM.

Rickman, D. L.↗

Using SCR methods to analyze requirements documentation

Software Cost Reduction (SCR) methods are being utilized to analyze and verify selected parts of NASA's EOS-DIS Core System (ECS) requirements documentation. SCR is being used as a spot-inspection tool. Through this formal and systematic approach of the SCR requirements methods, insights as to whether the requirements are internally inconsistent or incomplete as the scenarios of intended usage evolve in the OC (Operations Concept) documentation. Thus, by modelling the scenarios and requirements as mode charts using the SCR methods, we have been able to identify problems within and between the documents.

Callahan, John↗

Formal Methods for Verification and Validation of Partial Specifications: A Case Study

This paper describes our work exploring the suitability of formal specification methods for independent verification and validation (IV&V) of software specifications for large, safety critical systems. An IV&V contractor often has to perform rapid analysis on incomplete specifications, with no control over how those specifications are represented. Lightweight formal methods show significant promise in this context, as they offer a way of uncovering major errors, without the burden of full proofs of correctness. We describe a case study of the use of partial formal models for V&V of the requirements for Fault Detection Isolation and Recovery on the space station. We conclude that the insights gained from formalizing a specification are valuable, and it is the process of formalization, rather than the end product that is important. It was only necessary to build enough of the formal model to test the properties in which we were interested. Maintenance of fidelity between multiple representations of the same requirements (as they evolve) is still a problem, and deserves further study.

Easterbrook, Steve↗

Flight Guidance System Validation Using SPIN

To verify the requirements for the mode control logic of a Flight Guidance System (FGS) we applied SPIN, a widely used software package that supports the formal verification of distributed systems. These requirements, collectively called the FGS specification, were developed at Rockwell Avionics & Communications and expressed in terms of the Consortium Requirements Engineering (CoRE) method. The properties to be verified are the invariants formulated in the FGS specification, along with the standard properties of consistency and completeness. The project had two stages. First, the FGS specification and the properties to be verified were reformulated in PROMELA, the input language of SPIN. This involved a semantics issue, as some constructs of the FGS specification do not have well-defined semantics in CoRE. Then we attempted to verify the requirements' properties using the automatic model checking facilities of SPIN. Due to the large size of the state space of the FGS specification an exhaustive state space analysis with SPIN turned out to be impossible. So we used the supertrace model checking procedure of SPIN that provides for a partial analysis of the state space. During this process, we found some subtle errors in the FGS specification.

Naydich, Dimitri↗

Formal Methods in the Development of Highly Assured Software for Unmanned Aircraft Systems

In traditional software development methodologies, operational and functional requirements of systems are often specified in structured natural language notations. These restricted notations provide good documentation support, but only provide limited support for semantic analysis. These notations are generally not rich enough to unambiguously specify the requirements of safety-critical systems that, for example, involve complex numerical computations or that interact with the physical environment. Examples of these safety-critical systems are autonomous vehicles such as unmanned aircraft systems. This talk advocates the use of expressive formal logics, such as higher-order logic, to specify the operational and functional requirement of unmanned systems and to prove the correctness of these requirements. Semantic analysis of requirements written in higher-order logic is supported through the use of interactive theorem provers. Formal models serve as ideal reference implementations of functional requirements. Hence, formal logics enable software validation techniques where software implementations can be checked against functional requirements in a mechanical way. The Formal Methods group in the Safety-Critical Avionics Systems Branch at NASA Langley Research Center has conducted research on the development and application of formal verification techniques to safety-critical applications of interest to NASA for more than 30 years. This talk illustrates the use of formal methods in the development of highly-assured autonomous unmanned aircraft systems.

Formal Methods↗

Formal Methods Demonstration Project for Space Applications

Requirements and design specifications are a high priority candidate for better software engineering techniques. Most hazardous software safety errors found during system integration and test of two NASA spacecraft were the result of requirements discrepancies or interface specifications. The highest density of major defects found through the use of software inspections was during the requirements phase. This was seven times higher than the density of major defects found in code inspections. Requirements errors are between 10 and 100 times more costly to fix at later phases of the software lifecycle than at the requirements phase itself. One study found that early lifecycle errors are the most likely to lead to catastrophic failures.

critical↗

Conjunction Assessment and Deconfliction Paradigm for Co-Located Satellite Constellations With on-Spacecraft “Autonomous” Flight Dynamics Control

Satellite constellations that employ on-spacecraft flight dynamics and conjunction assessment (CA) approaches face particular challenges. First, they must arrange to obtain and upload to the constellation satellite close approach information, such as Conjunction Data Messages, so that their on-board systems will have the data they need to make informed CA decisions. Second, given current latencies in obtaining CA screening information, such systems often cannot obtain dedicated screenings of their proposed maneuvers before they are executed. Third, they usually cannot engage in real time with owner/operators (O/Os) with whom they may come into conjunction, relying instead on pre-arranged courses of action that may or may not fit a given situation well. Despite these difficulties, it is nonetheless possible, as operators such as SpaceX have demonstrated, to operate safely using on-board CA calculations, in the presence of a largely collaborative operating environment. The situation breaks down, however, when two constellations that operate with such a paradigm are placed in the same orbital region and will experience conjunctions with each other. Each may have a vague idea of where the other’s satellites are, or perhaps even a somewhat precise idea if they exchange O/O ephemerides, but neither will know the other’s more immediate maneuver intentions, especially for situations in which they are in a high-risk conjunction with each other and a mitigation maneuver is required. As there is no formalized way for these automated systems to ascertain each other’s intentions for this type of conjunction, it is quite possible that each spacecraft may choose a maneuver that results in the two objects’ colliding. An opportunity to develop a solution to this problem was presented by the NASA “Starling” project, a small experimental constellation developed to demonstrate autonomous satellite control and constellation reconfiguration and for which a launch was obtained that, serendipitously, will place this constellation close to the SpaceX Starlink constellation. Because the NASA constellation is experimental, an extended mission part of the mission has been negotiated to implement and test mechanisms for resolving the problem of co-located constellations with on-board flight dynamics control. For the last eighteen months, a consortium among NASA Ames (the Starling satellite providers), NASA CARA (the Agency organization responsible for conjunction assessment), Space X, and the Department of Commerce (in observer status) has met regularly to assemble a concept of operations for a robust solution to this problem and has developed a prototype ground node that will serve as a needed CA screening and information dispensary. The approach and methods, as well as the active employment of the developed ground node, will be tested both in simulation before actual use and then in actual spacecraft operations, which are anticipated to begin in January 2024. This paper will describe the co-located autonomously-controlled constellation problem and the developed solution in detail, outlining what ground node (i.e., government) infrastructure and features are required, what particular capabilities are needed by the constellations themselves in order to make use of this deconfliction paradigm, and the migration path forward to allow such a capability set to be incorporated by the Department of Commerce’s space traffic coordination system.

Conjunction Assessment↗

An assessment of the real-time application capabilities of the SIFT computer system

The real-time capabilities of the SIFT computer system, a highly reliable multicomputer architecture developed to support the flight controls of a relaxed static stability aircraft, are discussed. The SIFT computer system was designed to meet extremely high reliability requirements and to facilitate a formal proof of its correctness. Although SIFT represents a significant achievement in fault-tolerant system research it presents an unusual and restrictive interface to its users. The characteristics of the user interface and its impact on application system design are assessed.

Butler, R. W.↗

The implementation and use of Ada on distributed systems with high reliability requirements

A preliminary analysis of the Ada implementation of the Advanced Transport Operating System (ATOPS), an experimental computer control system developed at NASA Langley for a modified Boeing 737 aircraft, is presented. The criteria that was determined for the evaluation of this approach is described. A preliminary version of the requirements for the ATOPS is contained. This requirements specification is not a formal document, but rather a description of certain aspects of the ATOPS system at a level of detail that best suits the needs of the research. The survey of backward error recovery techniques is also presented.

Knight, J. C.↗

The 1990 Johnson Space Center bibliography of scientific and technical papers

Abstracts are presented of scientific and technical papers written and/or presented by L. B. Johnson Space Center (JSC) authors, including civil servants, contractors, and grantees, during the calendar year of 1990. Citations include conference and symposium presentations, papers published in proceedings or other collective works, seminars, and workshop results, NASA formal report series (including contractually required final reports), and articles published in professional journals.

Source record↗

Transition elements based on transfinite interpolation

In this study the transfinite interpolation methodology, a 'blending-function' method in particular, is utilized for the formulation of transition elements. The method offers a formal way of meeting continuity requirements in a transition element. Element shape functions are derived by blending the continuity requirements of individual boundary segments. The blending directions are naturally orthogonal in rectangular domains therefore interpolation of the boundaries over rectangular 2D and 3D elements can be performed with minimal effort. In triangular domains, however, the choice of blending directions and interpolants is not straightforward. For that reason, two interpolation techniques are proposed for blending of the boundaries of triangular domains. A series of transition elements of various classes compatible with elements of different orders and dimensions is developed and the full potential of the transfinite interpolation, as it applies to element formulation, is explored.

Odabas, Onur R.↗

The Transition from Spacecraft Development Ot Flight Operation: Human Factor Considerations

In the field of aeronautics and astronautics, a paradigm shift has been witnessed by those in academia, research and development, and private industry. Long development life cycles and the budgets to support such programs and projects has given way to aggressive task schedules and leaner resources to draw from all the while challenging assigned individuals to create and produce improved products of processes. however, this "faster, better, cheaper" concept cannot merely be applied to the design, development, and test of complex systems such as earth-orbiting of interplanetary robotic spacecraft. Full advantage is not possible without due consideration and application to mission operations planning and flight operations, Equally as important as the flight system, the mission operations system consisting of qualified personnel, ground hardware and software tools, and verified and validated operational processes, should also be regarded as a complex system requiring personnel to draw upon formal education, training, related experiences, and heuristic reasoning in engineering an effective and efficient system. Unquestionably, qualified personnel are the most important elements of a mission operations system. This paper examines the experiences of the Deep Space I Project, the first in a series of new technology in-flight validation missions sponsored by the United States National Aeronautics and Space Administration (NASA), specifically, in developing a subsystems analysis and technology validation team comprised of former spacecraft development personnel. Human factor considerations are investigated from initial concept/vision formulation; through operational process development; personnel test and training; to initial uplink product development and test support. Emphasis has been placed on challenges and applied or recommended solutions, so as to provide opportunities for future programs and projects to address and disposition potential issues and concerns as early as possible to reap the benefits associated with learning from other's past experiences.

Basilio, Ralph R.↗

Defining the Core Archive Data Standards of the International Planetary Data Alliance (IPDA)

A goal of the International Planetary Data Alliance (lPDA) is to develop a set of archive data standards that enable the sharing of scientific data across international agencies and missions. To help achieve this goal, the IPDA steering committee initiated a six month proj ect to write requirements for and draft an information model based on the Planetary Data System (PDS) archive data standards. The project had a special emphasis on data formats. A set of use case scenarios were first developed from which a set of requirements were derived for the IPDA archive data standards. The special emphasis on data formats was addressed by identifying data formats that have been used by PDS nodes and other agencies in the creation of successful data sets for the Planetary Data System (PDS). The dependency of the IPDA information model on the PDS archive standards required the compilation of a formal specification of the archive standards currently in use by the PDS. An ontology modelling tool was chosen to capture the information model from various sources including the Planetary Science Data Dictionary [I] and the PDS Standards Reference [2]. Exports of the modelling information from the tool database were used to produce the information model document using an object-oriented notation for presenting the model. The tool exports can also be used for software development and are directly accessible by semantic web applications.

ontology↗

Solutions Network Formulation Report. Aerosol Polarimetry Sensor Measurements of Diffuse-to-Global Irradiance Ratio for Improved Forecasting of Plant Productivity and Health

Studies have shown that vegetation is directly sensitive to changes in the diffuse-to-global irradiance ratio and that increased percentage of diffuse irradiation can accelerate photosynthesis. Therefore, measurements of diffuse versus global irradiance could be useful for monitoring crop productivity and overall vegetative health as they relate to the total amount of particulates in the air that result from natural disasters or anthropogenic (manmade) causes. While the components of solar irradiance are measured by satellite and surface sensors and calculated with atmospheric models, disagreement exists between the results, creating a need for more accurate and comprehensive retrievals of atmospheric aerosol parameters. Two satellite sensors--APS and VIIRS--show promise for retrieving aerosol properties at an unprecedented level of accuracy. APS is expected to be launched in December 2008. The planned launch date for VIIRS onboard NPP is September 2009. Identified partners include the USDA s ARS, North Carolina State University, Purdue Climate Change Research Center, and the Cooperative Institute for Research in the Atmosphere at Colorado State University. Although at present no formal DSSs (decision support systems) require accurate values of diffuse-to-global irradiance, this parameter is sufficiently important that models are being developed that will incorporate these measurements. This candidate solution is aligned with the Agricultural Efficiency and Air Quality National Applications.

Knowlton, Kelly↗

Dynamic Safety Cases for Through-Life Safety Assurance

We describe dynamic safety cases, a novel operationalization of the concept of through-life safety assurance, whose goal is to enable proactive safety management. Using an example from the aviation systems domain, we motivate our approach, its underlying principles, and a lifecycle. We then identify the key elements required to move towards a formalization of the associated framework.

Dynamic Safety Case↗