Search NASA⌕ Search

SEARCH · Search NASA

Results for “developments”

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 397 records · Page 22
All sourcesNASA NTRSDOE OSTI
NASA NTRS1987

Development of a comprehensive software engineering environment

The generation of a set of tools for software lifecycle is a recurring theme in the software engineering literature. The development of such tools and their integration into a software development environment is a difficult task because of the magnitude (number of variables) and the complexity (combinatorics) of the software lifecycle process. An initial development of a global approach was initiated in 1982 as the Software Development Workbench (SDW). Continuing efforts focus on tool development, tool integration, human interfacing, data dictionaries, and testing algorithms. Current efforts are emphasizing natural language interfaces, expert system software development associates and distributed environments with Ada as the target language. The current implementation of the SDW is on a VAX-11/780. Other software development tools are being networked through engineering workstations.

Hartrum, Thomas C.↗
NASA NTRS1986

Solar Concentrator Advanced Development Program, Task 1

Solar dynamic power generation has been selected by NASA to provide power for the space station. Solar dynamic concentrator technology has been demonstrated for terrestrial applications but has not been developed for space applications. The object of the Solar Concentrator Advanced Development program is to develop the technology of solar concentrators which would be used on the space station. The first task of this program was to develop conceptual concentrator designs and perform trade-off studies and to develop a materials data base and perform material selection. Three unique concentrator concepts; Truss Hex, Spline Radial Panel and Domed Fresnel, were developed and evaluated against weighted trade criteria. The Truss Hex concept was recommended for the space station. Materials data base development demonstrated that several material systems are capable of withstanding extended periods of atomic oxygen exposure without undesirable performance degradation. Descriptions of the conceptual designs and materials test data are included.

Source record↗
NASA NTRS1990

Expert System Development Methodology (ESDM)

The Expert System Development Methodology (ESDM) provides an approach to developing expert system software. Because of the uncertainty associated with this process, an element of risk is involved. ESDM is designed to address the issue of risk and to acquire the information needed for this purpose in an evolutionary manner. ESDM presents a life cycle in which a prototype evolves through five stages of development. Each stage consists of five steps, leading to a prototype for that stage. Development may proceed to a conventional development methodology (CDM) at any time if enough has been learned about the problem to write requirements. ESDM produces requirements so that a product may be built with a CDM. ESDM is considered preliminary because is has not yet been applied to actual projects. It has been retrospectively evaluated by comparing the methods used in two ongoing expert system development projects that did not explicitly choose to use this methodology but which provided useful insights into actual expert system development practices and problems.

Sary, Charisse↗
NASA NTRS1991

Lessons learned in the development of the STOL intelligent tutoring system

Lessons learned during the development of the NASA Systems Test and Operations Language (STOL) Intelligent Tutoring System (ITS), being developed at NASA Goddard Space Flight Center are presented. The purpose of the intelligent tutor is to train STOL users by adapting tutoring based on inferred student strengths and weaknesses. This system has been under development for over one year and numerous lessons learned have emerged. These observations are presented in three sections, as follows. The first section addresses the methodology employed in the development of the STOL ITS and briefly presents the ITS architecture. The second presents lessons learned, in the areas of: intelligent tutor development; documentation and reporting; cost and schedule control; and tools and shells effectiveness. The third section presents recommendations which may be considered by other ITS developers, addressing: access, use and selection of subject matter experts; steps involved in ITS development; use of ITS interface design prototypes as part of knowledge engineering; and tools and shells effectiveness.

Seamster, Thomas↗
NASA NTRS1991

Cooperative research and development opportunities with the National Cancer Institute

The Office of Technology Development (OTD) of the National Cancer Institute (NCI) is responsible for negotiating Cooperative Research and Development Agreements (CRADAs), whereby the knowledge resulting from NCI investigators' government-sponsored research is developed in collaboration with universities and/or industry into new products of importance for the diagnosis and treatment of cancer and acquired immunodeficiency syndrome (AIDS). The NCI has recently executed a unique 'clinical trials' CRADA and is developing a model agreement based upon it for the development and commercialization of products for the diagnosis and treatment of cancer and AIDS. NCI drug screening, preclinical testing, clinical trials, and AIDS program capabilities form the basis for this new technology development/technology transfer vehicle. NCI's extensive drug screening program and 'designer foods' program serve as potential sources of investigational new drugs (INDs) and cancer preventatives. Collaborations between NCI and pharmaceutical companies having the facilities, experience, and expertise necessary to develop INDs into approved drugs available to the public are being encouraged where the companies have proprietary rights to INDs, or where NCI has proprietary rights to INDs and invites companies to respond to a collaborator announcement published in the Federal Register. The joint efforts of the NCI and the chosen collaborator are designed to generate the data necessary to obtain pharmaceutic regulatory approval from the Food and Drug Administration (FDA) to market the drugs developed, and thereby make them available to health care providers for the diagnosis and treatment of cancer and AIDS.

Sybert, Kathleen↗
NASA NTRS1992

Ground Systems Development Environment (GSDE) software configuration management

This report presents a review of the software configuration management (CM) plans developed for the Space Station Training Facility (SSTF) and the Space Station Control Center. The scope of the CM assessed in this report is the Systems Integration and Testing Phase of the Ground Systems development life cycle. This is the period following coding and unit test and preceding delivery to operational use. This report is one of a series from a study of the interfaces among the Ground Systems Development Environment (GSDE), the development systems for the SSTF and the SSCC, and the target systems for SSCC and SSTF. This is the last report in the series. The focus of this report is on the CM plans developed by the contractors for the Mission Systems Contract (MSC) and the Training Systems Contract (TSC). CM requirements are summarized and described in terms of operational software development. The software workflows proposed in the TSC and MSC plans are reviewed in this context, and evaluated against the CM requirements defined in earlier study reports. Recommendations are made to improve the effectiveness of CM while minimizing its impact on the developers.

Church, Victor E.↗
NASA NTRS1992

Development of 3D electromagnetic modeling tools for airborne vehicles

The main goal of this project is to develop methodologies for scattering by airborne composite vehicles. Although our primary focus continues to be the development of a general purpose code for analyzing the entire structure as a single unit, a number of other tasks are also pursued in parallel with this effort. These tasks are important in testing the overall approach and in developing suitable models for materials coatings, junctions and, more generally, in assessing the effectiveness of the various parts comprising the final code. Here, we briefly discuss our progress on the five different tasks which were pursued during this period. Our progress on each of these tasks is described in the detailed reports (listed at the end of this report) and the memoranda included. The first task described below is, of course, the core of this project and deals with the development of the overall code. Undoubtedly, it is the outcome of the research which was funded by NASA-Ames and the Navy over the past three years. During this year we developed the first finite element code for scattering by structures of arbitrary shape and composition. The code employs a new absorbing boundary condition which allows termination of the finite element mesh only 0.3 lambda from the outer surface of the target. This leads to a remarkable reduction of the mesh size and is a unique feature of the code. Other unique features of this code include capabilities to model resistive sheets, impedance sheets and anisotropic materials. This last capability is the latest feature of the code and is still under development. The code has been extensively validated for a number of composite geometries and some examples are given. The validation of the code is still in progress for anisotropic and larger non-metallic geometries and cavities. The developed finite element code is based on a Galerkin's formulation and employs edge-based tetrahedral elements for discretizing the dielectric sections and the region between the target and the outer mesh termination boundary (ATB). This boundary is placed in conformity with the target's outer surface, thus resulting in additional reduction of the unknown count.

Volakis, John L.↗
NASA NTRS1992

The development and technology transfer of software engineering technology at NASA. Johnson Space Center

The United State's big space projects of the next decades, such as Space Station and the Human Exploration Initiative, will need the development of many millions of lines of mission critical software. NASA-Johnson (JSC) is identifying and developing some of the Computer Aided Software Engineering (CASE) technology that NASA will need to build these future software systems. The goal is to improve the quality and the productivity of large software development projects. New trends are outlined in CASE technology and how the Software Technology Branch (STB) at JSC is endeavoring to provide some of these CASE solutions for NASA is described. Key software technology components include knowledge-based systems, software reusability, user interface technology, reengineering environments, management systems for the software development process, software cost models, repository technology, and open, integrated CASE environment frameworks. The paper presents the status and long-term expectations for CASE products. The STB's Reengineering Application Project (REAP), Advanced Software Development Workstation (ASDW) project, and software development cost model (COSTMODL) project are then discussed. Some of the general difficulties of technology transfer are introduced, and a process developed by STB for CASE technology insertion is described.

Pitman, C. L.↗
NASA NTRS1989

Space biology initiative program definition review. Trade study 2: Prototype utilization in the development of space biology hardware

The objective was to define the factors which space flight hardware developers and planners should consider when determining: (1) the number of hardware units required to support program; (2) design level of the units; and (3) most efficient means of utilization of the units. The analysis considered technology risk, maintainability, reliability, and safety design requirements for achieving the delivery of highest quality flight hardware. Relative cost impacts of the utilization of prototyping were identified. The development of Space Biology Initiative research hardware will involve intertwined hardware/software activities. Experience has shown that software development can be an expensive portion of a system design program. While software prototyping could imply the development of a significantly different end item, an operational system prototype must be considered to be a combination of software and hardware. Hundreds of factors were identified that could be considered in determining the quantity and types of prototypes that should be constructed. In developing the decision models, these factors were combined and reduced by approximately ten-to-one in order to develop a manageable structure based on the major determining factors. The Baseline SBI hardware list of Appendix D was examined and reviewed in detail; however, from the facts available it was impossible to identify the exact types and quantities of prototypes required for each of these items. Although the factors that must be considered could be enumerated for each of these pieces of equipment, the exact status and state of development of the equipment is variable and uncertain at this time.

Jackson, L. Neal↗
NASA NTRS1987

NASA Procurement Career Development Program

The NASA Procurement Career Development Program establishes an agency-wide framework for the management of career development activity in the procurement field. Within this framework, installations are encouraged to modify the various components to meet installation-specific mission and organization requirements. This program provides a systematic process for the assessment of and planning for the development, training, and education required to increase the employees' competence in the procurement work functions. It includes the agency-wide basic knowledge and skills by career field and level upon which individual and organizational development plans are developed. Also, it provides a system that is compatible with other human resource management and development systems, processes, and activities. The compatibility and linkage are important in fostering the dual responsibility of the individual and the organization in the career development process.

Source record↗
NASA NTRS1992

Insights into software development in Japan

The interdependence of the U.S.-Japanese economies makes it imperative that we in the United States understand how business and technology developments take place in Japan. We can gain insight into these developments in software engineering by studying the context in which Japanese software is developed, the practices that are used, the problems encountered, the setting surrounding these problems, and the resolution of these problems. Context includes the technological and sociological characteristics of the software development environment, the software processes applied, personnel involved in the development process, and the corporate and social culture surrounding the development. Presented in this paper is a summary of results of a study that addresses these issues. Data for this study was collected during a three month visit to Japan where the author interviewed 20 software managers representing nine companies involved in developing software in Japan. These data are compared to similar data from the United States in which 12 managers from five companies were interviewed.

Duvall, Lorraine M.↗
NASA NTRS1994

The analysis of rapidly developing fog at the Kennedy Space Center

This report documents fog precursors and fog climatology at Kennedy Space Center (KSC) Florida from 1986 to 1990. The major emphasis of this report focuses on rapidly developing fog events that would affect the less than 7-statute mile visibility rule for End-Of-Mission (EOM) Shuttle landing at KSC (Rule 4-64(A)). The Applied Meteorology Unit's (AMU's) work is to: develop a data base for study of fog associated weather conditions relating to violations of this landing constraint; develop forecast techniques or rules-of-thumb to determine whether or not current conditions are likely to result in an acceptable condition at landing; validate the forecast techniques; and transition techniques to operational use. As part of the analysis the fog events were categorized as either advection, pre-frontal or radiation. As a result of these analyses, the AMU developed a fog climatological data base, identified fog precursors and developed forecaster tools and decision trees. The fog climatological analysis indicates that during the fog season (October to April) there is a higher risk for a visibility violation at KSC during the early morning hours (0700 to 1200 UTC), while 95 percent of all fog events have dissipated by 1600 UTC. A high number of fog events are characterized by a westerly component to the surface wind at KSC (92 percent) and 83 percent of the fog events had fog develop west of KSC first (up to 2 hours). The AMU developed fog decision trees and forecaster tools that would help the forecaster identify fog precursors up to 12 hours in advance. Using the decision trees as process tools ensures the important meteorological data are not overlooked in the forecast process. With these tools and a better understanding of fog formation in the local KSC area, the Shuttle weather support forecaster should be able to give the Launch and Flight Directors a better KSC fog forecast with more confidence.

Wheeler, Mark M.↗
NASA NTRS1994

New Developments and Research Findings: NASA Hydrazine Arcjets

In 1984, the market for commercial geosynchronous communications satellites (comsats) was expanding and there was strong competition between spacecraft builders for market share. The propellant required for the north-south stationkeeping (NSSK) function was a major mission limiter, and the small chemical and resistojet systems then in use were at or near their physical limits. Thus, conditions were right for the development of a high performance NSSK system, and after an extensive survey of both propulsion technologies and the aerospace community, the NASA program chose hydrazine arcjets for development. A joint government/industry development program ensued which culminated in the acceptance of arcjet technology. NASA efforts included fundamental feasibility assessments, hardware development and verification, and multiple efforts aimed at the demonstration of critical operational characteristics of arcjet systems. Throughout the program, constant contact with the user community was maintained to determine system requirements. Both contracted and cooperative programs with industry were supported. First generation, kW-class arcjets are now operational for NSSK on the Telstar 401 satellite launched in December of 1993 and are baselined for use on multiple future satellite series (Intelsat 8, AsiaSat, Echostar). Arcjet development efforts are now focusing on the development of both high performance (600 s), 2 kW thrusters for application on next generation comsats and low power (Pe approximately 0.5 kW) for a variety of applications on power limited satellites. This paper presents a review of the NASA's role in the development of hydrazine arcjets with a focus on approaches, lessons learned, and the future.

Curren, Francis M.↗
NASA NTRS1994

SCOS 2: An object oriented software development approach

The Spacecraft Control and Operations System 2 (SCOS 2), is intended to provide the generic mission control system infrastructure for future ESA missions. It represents a bold step forward in order to take advantage of state-of-the-art technology and current practices in the area of software engineering. Key features include: (1) use of object oriented analysis and design techniques; (2) use of UNIX, C++ and a distributed architecture as the enabling implementation technology; (3) goal of re-use for development, maintenance and mission specific software implementation; and (4) introduction of the concept of a spacecraft control model. This paper touches upon some of the traditional beliefs surrounding Object Oriented development and describes their relevance to SCOS 2. It gives rationale for why particular approaches were adopted and others not, and describes the impact of these decisions. The development approach followed is discussed, highlighting the evolutionary nature of the overall process and the iterative nature of the various tasks carried out. The emphasis of this paper is on the process of the development with the following being covered: (1) the three phases of the SCOS 2 project - prototyping & analysis, design & implementation and configuration / delivery of mission specific systems; (2) the close cooperation and continual interaction with the users during the development; (3) the management approach - the split between client staff, industry and some of the required project management activities; (4) the lifecycle adopted being an enhancement of the ESA PSS-05 standard with SCOS 2 specific activities and approaches defined; and (5) an examination of some of the difficulties encountered and the solutions adopted. Finally, the lessons learned from the SCOS 2 experience are highlighted, identifying those issues to be used as feedback into future developments of this nature. This paper does not intend to describe the finished product and its operation, but focusing on the journey to arrive there, concentrating therefore on the process and not the products of the SCOS 2 software development.

Symonds, Martin↗
NASA NTRS1995

Development and analysis of SCR requirements tables for system scenarios

We describe the use of scenarios to develop and refine requirement tables for parts of the Earth Observing System Data and Information System (EOSDIS). The National Aeronautics and Space Administration (NASA) is developing EOSDIS as part of its Mission-To-Planet-Earth (MTPE) project to accept instrument/platform observation requests from end-user scientists, schedule and perform requested observations of the Earth from space, collect and process the observed data, and distribute data to scientists and archives. Current requirements for the system are managed with tools that allow developers to trace the relationships between requirements and other development artifacts, including other requirements. In addition, the user community (e.g., earth and atmospheric scientists), in conjunction with NASA, has generated scenarios describing the actions of EOSDIS subsystems in response to user requests and other system activities. As part of a research effort in verification and validation techniques, this paper describes our efforts to develop requirements tables from these scenarios for the EOSDIS Core System (ECS). The tables specify event-driven mode transitions based on techniques developed by the Naval Research Lab's (NRL) Software Cost Reduction (SCR) project. The SCR approach has proven effective in specifying requirements for large systems in an unambiguous, terse format that enhance identification of incomplete and inconsistent requirements. We describe development of SCR tables from user scenarios and identify the strengths and weaknesses of our approach in contrast to the requirements tracing approach. We also evaluate the capabilities of both approach to respond to the volatility of requirements in large, complex systems.

Callahan, John R.↗
NASA NTRS1994

Study of development and utilization of a multipurpose atmospheric corrosion sensor

There has been a critical need for analyzing various aspects of atmospheric corrosion and for the development of atmospheric corrosion microsensors. The project work has involved the following activities: (1) making of multielectrode corrosion monitors on dielectric substrates; (2) testing them in the laboratory for functional characteristics; (3) preparing a report on the state of the art of atmospheric corrosion sensor development around the world; and (4) corrosion testing of electrochemical changes of sensor specimens and related fog testing. The study included work on the subject of development and utilization of a multipurpose atmospheric corrosion sensor and this report is the annual report on work carried out on this research project. This has included studies on the development of sensors of two designs, stage 1 and stage 2, and with glass and alumina substrate, experimentation and development and characterization of the coating uniformity, aspects of corrosion monitoring, literature search on the corrosion sensors and their development. A state of the art report on atmospheric corrosion sensor development was prepared and submitted.

Diwan, Ravinder M.↗
NASA NTRS1995

Making intelligent systems team players. A guide to developing intelligent monitoring systems

This reference guide for developers of intelligent monitoring systems is based on lessons learned by developers of the DEcision Support SYstem (DESSY), an expert system that monitors Space Shuttle telemetry data in real time. DESSY makes inferences about commands, state transitions, and simple failures. It performs failure detection rather than in-depth failure diagnostics. A listing of rules from DESSY and cue cards from DESSY subsystems are included to give the development community a better understanding of the selected model system. The G-2 programming tool used in developing DESSY provides an object-oriented, rule-based environment, but many of the principles in use here can be applied to any type of monitoring intelligent system. The step-by-step instructions and examples given for each stage of development are in G-2, but can be used with other development tools. This guide first defines the authors' concept of real-time monitoring systems, then tells prospective developers how to determine system requirements, how to build the system through a combined design/development process, and how to solve problems involved in working with real-time data. It explains the relationships among operational prototyping, software evolution, and the user interface. It also explains methods of testing, verification, and validation. It includes suggestions for preparing reference documentation and training users.

Land, Sherry A.↗
NASA NTRS1994

Graviceptor development in jellyfish ephyrae in space and on Earth

Graviceptor (rhopalium) development in Aurelia aurita ephyrae which developed on Earth and in space during the nine-day NASA SLS-1 mission was compared. The space-developed ephyrae made graviceptors which were morphologically similar to those of their ground-based controls. Rhopalia of both groups developed statocysts with statoliths, ocelli, ciliated mechanoreceptor cells, and immature touch-plates with one type of hair cell. The number of rhopalia formed per arm of ephyrae of both groups revealed no significant differences. The number of statoliths formed per rhopalium was statistically higher in ephyrae which were induced to form in space with iodine than in L(Launch)+8h controls. Statolith numbers were not significantly different between Earth-formed control ephyrae and those formed from polyps induced on Earth and then sent into space 24h and 48h later. Statolith loss from rhopalia was significantly enhanced in the space-maintained ephyrae in artificial sea water (ASW) as compared to their controls. Ephyrae formed through thyroxine treatment and those maintained in thyroxine in space had statolith numbers comparable to thyroxine-treated controls. Pulsing abnormalitities seen in some space-developed ephyrae suggest that some space-formed ephyrae may have developed abnormal rhopalia because normal rhopalia development and function is necessary for normal pulsing.

Spangenberg, D. B.↗