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 145 records · Page 8

Thermostructural tailoring of fiber composite structures

A significant area of interest in design of complex structures involves the study of multidisciplined problems. The coordination of several different intricate areas of study to obtain a particular design of a structure is a new and pressing area of research. In the past, each discipline would perform its task consecutively using the appropriate inputs from the other disciplines. This process usually required several time-consuming iterations to obtain a satisfactory design. The alternative pursued here is combining various participating disciplines and specified design requirements into a formal structural computer code. The main focus of this research is to develop a multidiscipline structural tailoring method for select composite structures and to demonstrate its application to specific areas. The development of an integrated computer program involves the coupling of three independent computer programs using an excutive module. This module will be the foundation for integrating a structural optimizer, a composites analyzer and a thermal analyzer. With the completion of the executive module, the first step was taken toward the evolution of multidiscipline software in the field of composite mechanics. Through the use of an array of cases involving a variety of objective functions/constraints and thermal-mechanical load conditions, it became evident that simple composite structures can be designed to a combined loads environment.

Acquaviva, Thomas H.↗

A verification logic representation of indeterministic signal states

The integration of modern CAD tools with formal verification environments require translation from hardware description language to verification logic. A signal representation including both unknown state and a degree of strength indeterminacy is essential for the correct modeling of many VLSI circuit designs. A higher-order logic theory of indeterministic logic signals is presented.

Gambles, J. W.↗

Configuration Management of an Optimization Application in a Research Environment

Multidisciplinary design optimization (MDO) research aims to increase interdisciplinary communication and reduce design cycle time by combining system analyses (simulations) with design space search and decision making. The High Performance Computing and Communication Program's current High Speed Civil Transport application, HSCT4.0, at NASA Langley Research Center involves a highly complex analysis process with high-fidelity analyses that are more realistic than previous efforts at the Center. The multidisciplinary processes have been integrated to form a distributed application by using the Java language and Common Object Request Broker Architecture (CORBA) software techniques. HSCT4.0 is a research project in which both the application problem and the implementation strategy have evolved as the MDO and integration issues became better understood. Whereas earlier versions of the application and integrated system were developed with a simple, manual software configuration management (SCM) process, it was evident that this larger project required a more formal SCM procedure. This report briefly describes the HSCT4.0 analysis and its CORBA implementation and then discusses some SCM concepts and their application to this project. In anticipation that SCM will prove beneficial for other large research projects, the report concludes with some lessons learned in overcoming SCM implementation problems for HSCT4.0.

Townsend, James C.↗

Experiment Document for 01-E077 Microgravity Investigation of Crew Reactions in 0-G (MICRO-G)

The Experiment Document (ED) serves the following purposes: a) It provides a vehicle for Principal Investigators (PIS) to formally specify the requirements for performing their experiments. b) It provides a technical Statement of Work (SOW). c) It provides experiment investigators and hardware developers with a convenient source of information about Human Life Sciences (HLS) requirements for the development and/or integration of flight experiment projects. d) It is the primary source of experiment specifications for the HLS Research Program Office (RPO). Inputs from this document will be placed into a controlled database that will be used to generate other documents.

Newman, Dava J.↗

Minnowbrook I: 1993 Workshop on End-Stage Boundary Layer Transition

This volume contains materials presented at the Minnowbrook I-1993 Workshop on End-Stage Boundary Layer Transition, held at the Syracuse University Minnowbrook Conference Center, New York, from August 15 to 18, 1993. This volume was previously published as a Syracuse University report edited by John E. LaGraff. The workshop organizers were John E. LaGraff (Syracuse University), Terry V. Jones (Oxford University), and J. Paul Gostelow (University of Technology, Sydney). The workshop focused on physical understanding of the late stages of transition from laminar to turbulent flows, with the specific goal of contributing to improving engineering design of turbomachinery and wing airfoils. The workshop participants included academic researchers from the United States and abroad, and representatives from the gas-turbine industry and U.S. government laboratories. To improve interaction and discussions among the participants, no formal papers were required. The physical mechanisms discussed were related to natural and bypass transition, wake-induced transition, effects of freestream turbulence, turbulent spots, hairpin vortices, nonlinear instabilities and breakdown, instability wave interactions, intermittency, turbulence, numerical simulation and modeling of transition, heat transfer in boundary-layer transition, transition in separated flows, laminarization, transition in turbomachinery compressors and turbines, hypersonic boundary-layer transition, and other related topics. This volume contains abstracts and copies of the viewgraphs presented, organized according to the workshop sessions. The workshop summary and the plenary discussion transcript clearly outline future research needs.

LaGraff, John E.↗

Compositional Verification of a Communication Protocol for a Remotely Operated Vehicle

This paper presents the specification and verification in the Prototype Verification System (PVS) of a protocol intended to facilitate communication in an experimental remotely operated vehicle used by NASA researchers. The protocol is defined as a stack-layered com- position of simpler protocols. It can be seen as the vertical composition of protocol layers, where each layer performs input and output message processing, and the horizontal composition of different processes concurrently inhabiting the same layer, where each process satisfies a distinct requirement. It is formally proven that the protocol components satisfy certain delivery guarantees. Compositional techniques are used to prove these guarantees also hold in the composed system. Although the protocol itself is not novel, the methodology employed in its verification extends existing techniques by automating the tedious and usually cumbersome part of the proof, thereby making the iterative design process of protocols feasible.

Goodloe, Alwyn E.↗

Data Automata in Scala

The field of runtime verification has during the last decade seen a multitude of systems for monitoring event sequences (traces) emitted by a running system. The objective is to ensure correctness of a system by checking its execution traces against formal specifications representing requirements. A special challenge is data parameterized events, where monitors have to keep track of the combination of control states as well as data constraints, relating events and the data they carry across time points. This poses a challenge wrt. efficiency of monitors, as well as expressiveness of logics. Data automata is a form of automata where states are parameterized with data, supporting monitoring of data parameterized events. We describe the full details of a very simple API in the Scala programming language, an internal DSL (Domain-Specific Language), implementing data automata. The small implementation suggests a design pattern. Data automata allow transition conditions to refer to other states than the source state, and allow target states of transitions to be inlined, offering a temporal logic flavored notation. An embedding of a logic in a high-level language like Scala in addition allows monitors to be programmed using all of Scala's language constructs, offering the full flexibility of a programming language. The framework is demonstrated on an XML processing scenario previously addressed in related work.

runtime verification↗

Feature-Guided Analysis of Neural Networks

Applying standard software engineering practices to neural networks is challenging due to the lack of high-level abstractions describing a neural network’s behavior. To address this challenge, we propose to extract high-level task-specific features from the neural network internal representation, based on monitoring the neural network activations.The extracted feature representations can serve as a link to high-level requirements and can be leveraged to enable fundamental software engineering activities, such as automated testing, debugging, requirements analysis, and formal verification, leading to better engineering of neural networks. Using two case studies, we present initial empirical evidence demonstrating the feasibility of our ideas.

Features↗

Software Formal Inspections Guidebook

The Software Formal Inspections Guidebook is designed to support the inspection process of software developed by and for NASA. This document provides information on how to implement a recommended and proven method for conducting formal inspections of NASA software. This Guidebook is a companion document to NASA Standard 2202-93, Software Formal Inspections Standard, approved April 1993, which provides the rules, procedures, and specific requirements for conducting software formal inspections. Application of the Formal Inspections Standard is optional to NASA program or project management. In cases where program or project management decide to use the formal inspections method, this Guidebook provides additional information on how to establish and implement the process. The goal of the formal inspections process as documented in the above-mentioned Standard and this Guidebook is to provide a framework and model for an inspection process that will enable the detection and elimination of defects as early as possible in the software life cycle. An ancillary aspect of the formal inspection process incorporates the collection and analysis of inspection data to effect continual improvement in the inspection process and the quality of the software subjected to the process.

Source record↗

The Ten Lockheed Martin Cyber-Physical Challenges: Formalized, Analyzed, and Explained

Capturing and analyzing requirements of Cyber-Physical Systems (CPS) can be challenging, since CPS models typically involve time-varying and real-valued variables, physical system dynamics, or even adaptive behavior. MATLAB/Simulinkis a development and simulation framework that is widely used in industry to capture such systems. In this paper, we report on the application of NASA Ames tools to perform end-to-end analysis of the Ten Lockheed Martin Challenge Problems (LMCPS). LMCPS is a set of industrial Simulink model benchmarks and natural language requirements developed by domain experts. Our framework, which integrates the tools FRET and COCOSIM, is used to: 1) elicit, explain, and formalize the semantics of the given natural language requirements; 2) generate verification code and monitors that can be automatically attached to the Simulink models; 3) perform verification by using SMT-based model checkers. FRET and COCOSIM are open source, and can be used by other researchers and practitioners to replicate our case study. We provide a categorization of recurring patterns in the formalization of the requirements and discuss the strengths and weaknesses of our automated verification approach.

Anastasia Mavridou↗

Software Safety Risk in Legacy Safety-Critical Computer Systems

Safety-critical computer systems must be engineered to meet system and software safety requirements. For legacy safety-critical computer systems, software safety requirements may not have been formally specified during development. When process-oriented software safety requirements are levied on a legacy system after the fact, where software development artifacts don't exist or are incomplete, the question becomes 'how can this be done?' The risks associated with only meeting certain software safety requirements in a legacy safety-critical computer system must be addressed should such systems be selected as candidates for reuse. This paper proposes a method for ascertaining formally, a software safety risk assessment, that provides measurements for software safety for legacy systems which may or may not have a suite of software engineering documentation that is now normally required. It relies upon the NASA Software Safety Standard, risk assessment methods based upon the Taxonomy-Based Questionnaire, and the application of reverse engineering CASE tools to produce original design documents for legacy systems.

Hill, Janice↗

The MINERVA Software Development Process

This paper presents a software development process for safety-critical software components of cyber-physical systems. The process is called MINERVA, which stands for Mirrored Implementation Numerically Evaluated against Rigorously Verified Algorithms. The process relies on formal methods for rigorously validating code against its requirements. The software development process uses: (1) a formal specification language for describing the algorithms and their functional requirements, (2) an interactive theorem prover for formally verifying the correctness of the algorithms, (3) test cases that stress the code, and (4) numerical evaluation on these test cases of both the algorithm specifications and their implementations in code. The MINERVA process is illustrated in this paper with an application to geo-containment algorithms for unmanned aircraft systems. These algorithms ensure that the position of an aircraft never leaves a predetermined polygon region and provide recovery maneuvers when the region is inadvertently exited.

Narkawicz, Anthony↗

Unmanned Aircraft Systems in the National Airspace System: A Formal Methods Perspective

As the technological and operational capabilities of unmanned aircraft systems (UAS) have grown, so too have international efforts to integrate UAS into civil airspace. However, one of the major concerns that must be addressed in realizing this integration is that of safety. For example, UAS lack an on-board pilot to comply with the legal requirement that pilots see and avoid other aircraft. This requirement has motivated the development of a detect and avoid (DAA) capability for UAS that provides situational awareness and maneuver guidance to UAS operators to aid them in avoiding and remaining well clear of other aircraft in the airspace. The NASA Langley Research Center Formal Methods group has played a fundamental role in the development of this capability. This article gives a selected survey of the formal methods work conducted in support of the development of a DAA concept for UAS. This work includes specification of low-level and high-level functional requirements, formal verification of algorithms, and rigorous validation of software implementations.

Munoz, Cesar A.↗

Formal Methods in Air Traffic Management: The Case of Unmanned Aircraft Systems

As the technological and operational capabilities of unmanned aircraft systems (UAS) continue to grow, so too does the need to introduce these systems into civil airspace. Unmanned Aircraft Systems Integration in the National Airspace System is a NASA research project that addresses the integration of civil UAS into non-segregated airspace operations. One of the major challenges of this integration is the lack of an onboard pilot to comply with the legal requirement that pilots see and avoid other aircraft. The need to provide an equivalent to this requirement for UAS has motivated the development of a detect and avoid (DAA) capability to provide the appropriate situational awareness and maneuver guidance in avoiding and remaining well clear of traffic aircraft. Formal methods has played a fundamental role in the development of this capability. This talk reports on the formal methods work conducted under NASA's Safe Autonomous System Operations project in support of the development of DAA for UAS. This work includes specification of low-level and high-level functional requirements, formal verification of algorithms, and rigorous validation of software implementations. The talk also discusses technical challenges in formal methods research in the context of the development and safety analysis of advanced air traffic management concepts.

Munoz, Cesar A.↗

Enabling Affordable Communications for the Burgeoning Deep Space Cubesat Fleet

The low costs of development and launch, coupled with new propulsive technologies, have made CubeSats increasingly popular for use in science investigations beyond geosynchronous orbit. As this deep space CubeSat fleet grows in size, the challenge of trying to provide affordable communications for it grows commensurately. The mass, power, and volume constraints inherent to CubeSats limit the antenna size and transmit power that they can use to close the deep space link. As a consequence, CubeSats need to rely more heavily on ground antennas that are characterized by large aperture, low noise temperatures, and relatively high-power transmitters. Such antennas are not in great abundance, nor are they inexpensive to build. For this reason, NASA’s Deep Space Network has been advocating a three-pronged approach to meeting anticipated CubeSat demand: development of simultaneous, shared-beam multi-spacecraft communications capabilities, development of large-antenna cross-support arrangements with other agencies and universities, and development of less uplink-intensive navigation techniques. This paper focuses on the pursuit of simultaneous, shared-beam multi-spacecraft communications capabilities. While the Multiple Spacecraft per Antenna (MSPA) technique has existed for over a decade, it has generally been limited to supporting downlink for just two in-beam spacecraft at a time. This limitation has largely been a function of the number and cost of available receivers. A relatively new technique that potentially overcomes this limitation is Opportunistic MSPA (OMSPA). Instead of relying on additional receivers, OMSPA makes use of a digital recorder at each ground station that is capable of capturing the intermediate frequency (IF) signals from every spacecraft in the antenna beam within the frequency bands of interest. When CubeSat projects see one or more opportunities for their CubeSat(s) to intercept the traditionally scheduled antenna beam of a “host” spacecraft, they can arrange for the CubeSat(s) to transmit open loop during those opportunities. Via a secure Internet site, the CubeSat mission operators can then retrieve the time- and frequency-relevant portions of the digital recording for subsequent demodulation and decoding, or subscribe to a service that does it for them. This “opportunistic” use of a host spacecraft’s ground antenna beam potentially enables CubeSat projects to make use of large ground antennas for downlink without having to compete with bigger, better-funded missions for antenna time in the formal scheduling process. In so doing, it also potentially enables CubeSat projects to avoid the aperture fees associated with formally scheduled downlink time - fees that factor into the “bottom-line” of competitively-bid NASA missions and that actually get charged to non-NASA missions. Taking advantage of these potential OMSPA benefits, however, will require CubeSat projects to pursue mission designs that ensure at least periodic in-beam operations relative to a “host” spacecraft. In the case of a constellation of CubeSats with inter-spacecraft distances that do not extend outside of the beam-width of the desired ground antenna at the given range, one CubeSat can serve as the “host” and have a formally scheduled downlink while the rest of the CubeSats can downlink essentially for “free” via OMSPA. Deep space CubeSats, of course, will need uplink in addition to downlink. Beyond commanding, this need is driven by the use of two-way ranging and Doppler for navigation. While OMSPA may not directly facilitate uplink, it does have the potential to free up antennas for those spacecraft that periodically require formally scheduled links for commanding and two-way radio metrics. NASA is also exploring the physical feasibility of an in-beam, simultaneous multi-spacecraft uplink technique. As with OMSPA, if successful, it will require little new equipment, further enabling affordable deep space CubeSat communications.

Abraham, Douglas S.↗

Implementing Software Safety in the NASA Environment

Until recently, NASA did not consider allowing computers total control of flight systems. Human operators, via hardware, have constituted the ultimate safety control. In an attempt to reduce costs, NASA has come to rely more and more heavily on computers and software to control space missions. (For example. software is now planned to control most of the operational functions of the International Space Station.) Thus the need for systematic software safety programs has become crucial for mission success. Concurrent engineering principles dictate that safety should be designed into software up front, not tested into the software after the fact. 'Cost of Quality' studies have statistics and metrics to prove the value of building quality and safety into the development cycle. Unfortunately, most software engineers are not familiar with designing for safety, and most safety engineers are not software experts. Software written to specifications which have not been safety analyzed is a major source of computer related accidents. Safer software is achieved step by step throughout the system and software life cycle. It is a process that includes requirements definition, hazard analyses, formal software inspections, safety analyses, testing, and maintenance. The greatest emphasis is placed on clearly and completely defining system and software requirements, including safety and reliability requirements. Unfortunately, development and review of requirements are the weakest link in the process. While some of the more academic methods, e.g. mathematical models, may help bring about safer software, this paper proposes the use of currently approved software methodologies, and sound software and assurance practices to show how, to a large degree, safety can be designed into software from the start. NASA's approach today is to first conduct a preliminary system hazard analysis (PHA) during the concept and planning phase of a project. This determines the overall hazard potential of the system to be built. Shortly thereafter, as the system requirements are being defined, the second iteration of hazard analyses takes place, the systems hazard analysis (SHA). During the systems requirements phase, decisions are made as to what functions of the system will be the responsibility of software. This is the most critical time to affect the safety of the software. From this point, software safety analyses as well as software engineering practices are the main focus for assuring safe software. While many of the steps proposed in this paper seem like just sound engineering practices, they are the best technical and most cost effective means to assure safe software within a safe system.

Wetherholt, Martha S.↗