SEARCH · Search NASA

Results for “Software development”

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.

SourceResearch connectionFrom yearThrough year

Quote a phrase for an exact phrase match. Source license links do not imply unrestricted reuse.

At least 847 records · Page 47

All sources NASA NTRS DOE OSTI

NASA NTRS2017

Description of the GMAO OSSE for Weather Analysis Software Package: Version 3

The Global Modeling and Assimilation Office (GMAO) at the NASA Goddard Space Flight Center has developed software and products for conducting observing system simulation experiments (OSSEs) for weather analysis applications. Such applications include estimations of potential effects of new observing instruments or data assimilation techniques on improving weather analysis and forecasts. The GMAO software creates simulated observations from nature run (NR) data sets and adds simulated errors to those observations. The algorithms employed are much more sophisticated, adding a much greater degree of realism, compared with OSSE systems currently available elsewhere. The algorithms employed, software designs, and validation procedures are described in this document. Instructions for using the software are also provided.

OSSE↗

NASA NTRS1989

Improving A Remote Manipulator

Set of three reports describes work on Protoflight Manipulator Assembly (PFMA). "Performance Characteristics of Protoflight Manipulator Assembly" presents parameters of PFMA after refurbishment of operating components. "End Effector and Task Board Development for the Protoflight Manipulator Assembly" describes special tools and adaptations allowing PFMA to be used for servicing equipment. "Modular Software Development for the Protoflight Manipulator Assembly" documents interface and control software for PFMA.

Haslam, John W., Jr.↗

NASA NTRS2016

Marshall Space Flight Center Telescience Resource Kit

Telescience Resource Kit (TReK) is a suite of software applications that can be used to monitor and control assets in space or on the ground. The Telescience Resource Kit was originally developed for the International Space Station program. Since then it has been used to support a variety of NASA programs and projects including the WB-57 Ascent Vehicle Experiment (WAVE) project, the Fast Affordable Science and Technology Satellite (FASTSAT) project, and the Constellation Program. The Payloads Operations Center (POC), also known as the Payload Operations Integration Center (POIC), provides the capability for payload users to operate their payloads at their home sites. In this environment, TReK provides local ground support system services and an interface to utilize remote services provided by the POC. TReK provides ground system services for local and remote payload user sites including International Partner sites, Telescience Support Centers, and U.S. Investigator sites in over 40 locations worldwide. General Capabilities: Support for various data interfaces such as User Datagram Protocol, Transmission Control Protocol, and Serial interfaces. Data Services - retrieve, process, record, playback, forward, and display data (ground based data or telemetry data). Command - create, modify, send, and track commands. Command Management - Configure one TReK system to serve as a command server/filter for other TReK systems. Database - databases are used to store telemetry and command definition information. Application Programming Interface (API) - ANSI C interface compatible with commercial products such as Visual C++, Visual Basic, LabVIEW, Borland C++, etc. The TReK API provides a bridge for users to develop software to access and extend TReK services. Environments - development, test, simulations, training, and flight. Includes standalone training simulators.

Wade, Gina↗

NASA NTRS2006

New Challenges in Model Checking

In the last 25 years, the notion of performing software verification with logic model checking techniques has evolved from intellectual curiosity to accepted technology with significant potential for broad practical application. In this paper we look back at the main steps in this evolution and illustrate how the challenges have changed over the years, as we sharpened our theories and tools. Next we discuss a typical challenge in software verification that we face today - and that perhaps we can look back on in another 25 years as having inspired the next logical step towards a broader integration of model checking into the software development process.

software verification↗

NASA NTRS1988

Evolving impact of Ada on a production software environment

Many aspects of software development with Ada have evolved as our Ada development environment has matured and personnel have become more experienced in the use of Ada. The Software Engineering Laboratory (SEL) has seen differences in the areas of cost, reliability, reuse, size, and use of Ada features. A first Ada project can be expected to cost about 30 percent more than an equivalent FORTRAN project. However, the SEL has observed significant improvements over time as a development environment progresses to second and third uses of Ada. The reliability of Ada projects is initially similar to what is expected in a mature FORTRAN environment. However, with time, one can expect to gain improvements as experience with the language increases. Reuse is one of the most promising aspects of Ada. The proportion of reusable Ada software on our Ada projects exceeds the proportion of reusable FORTRAN software on our FORTRAN projects. This result was noted fairly early in our Ada projects, and experience shows an increasing trend over time.

Mcgarry, F.↗

NASA NTRS1974

Multiple IMU system development, volume 1

A redundant gimballed inertial system is described. System requirements and mechanization methods are defined and hardware and software development is described. Failure detection and isolation algorithms are presented and technology achievements described. Application of the system as a test tool for shuttle avionics concepts is outlined.

Landey, M.↗

NASA NTRS1978

SEASAT A satellite scatterometer

The analyses performed in the early period of the program which formed the basis of the sensor design is reviewed, along with the sensor design. The test program is outlined, listing all tests performed and the environmental exposure (simulated) for each, as applicable. Ground support equipment designed and built for assembly integration and field testing is described. The software developed during the program and the algorithms/flow diagrams which formed the bases for the software are summarized.

Bianchi, R.↗

NASA NTRS1984

Nasa-wide Standard Administrative Systems

Factors to be considered in developing agency-wide standard administrative systems for NASA include uniformity of hardware and software; centralization vs. decentralization; risk exposure; and models for software development.

Schneck, P.↗

NASA NTRS1990

Information System Life-Cycle And Documentation Standards (SMAP DIDS)

Although not computer program, SMAP DIDS written to provide systematic, NASA-wide structure for documenting information system development projects. Each DID (data item description) outlines document required for top-quality software development. When combined with management, assurance, and life cycle standards, Standards protect all parties who participate in design and operation of new information system.

Source record↗

NASA NTRS1989

A comparison of software for the modeling and control of flexible systems

A researcher proposes a cooperative effort among specialists who use or develop software for simulating and analyzing the control of flexible aerospace systems. A comparison of existing software for modeling control systems and flexible structures, applied to several example problems would be quite valuable. The comparison would indicate computational efficiency and capabilities with respect to handling nonlinearities and graphical output. Because of the diversity of applications of such software, the researcher believes that the proposed cooperative effort can transcend projects involving specific applications. Comparisons of software capability and efficiency can be made and gaps can be identified. In this way the results of the cooperative effort can provide guidance for individual projects. Several charts which outline the objectives and approach of the proposed cooperative effort are given here.

Taylor, Lawrence W., Jr.↗

NASA NTRS1990

Improving software quality - The use of formal inspections at the Jet Propulsion Laboratory

The introduction of software formal inspections (Fagan Inspections) at JPL for finding and fixing defects early in the software development life cycle are reviewed. It is estimated that, by the year 2000, some software efforts will rise to as much as 80 percent of the total. Software problems are especially important at NASA as critical flight software must be error-free. It is shown that formal inspections are particularly effective at finding and removing defects having to do with clarity, correctness, consistency, and completeness. A very significant discovery was that code audits were not as effective at finding defects as code inspections.

Bush, Marilyn↗

NASA NTRS1994

An instrument to measure the charge, and energy spectrum (20-1000 GeV/a) of the cosmic ray species oxygen to iron

BUGS-4 (Bristol University Gas Scintillator-4) made its maiden engineering flight from Fort Summer (NM) on the 29th of September 1993. The instrument was consumed by fire after striking a power line during landing following 24 hours at float. The analysis of the telemetered data from this sophisticated instrument is a demanding task. Early analysis was compromised by electronic artifacts. Unravelling these problems has been difficult and time consuming, especially as the flight hardware was burned beyond salvage, but is is an essential preliminary to analysis. During this report period we have concentrated on a small sub-set of data (the first 30,000 events; 90 minutes at float), and developed software algorithms to correct systematic errors. Using these corrected events we have begun to develop the analysis algorithms. Although the analysis is preliminary, and restricted to the first 30,000 events, the results are encouraging, and suggest the design concepts are well matched to this application. Further work will refine the analysis, and allow quantitative evaluation of the concepts employed in BUGS-4 for applicability to future instruments. We believe this work will justify fabrication of a new instrument employing techniques deployed on BUGS-4.

Gregory, J. C.↗

NASA NTRS1997

The Development of a User Inclusion Strategy for CLCS Display Design

This report summarizes a ten week effort to evaluate the software development process in the Checkout and Launch Control System (CLCS) for the presence of user inclusion in the design operation. A background is presented that highlights the value of achieving usability through user inclusion, progress-to-date is described, and future work is suggested so that a user inclusive design environment can be accomplished.

Jacko, Julie A.↗

NASA NTRS1989

General-Purpose Electronic System Tests Aircraft

Versatile digital equipment supports research, development, and maintenance. Extended aircraft interrogation and display system is general-purpose assembly of digital electronic equipment on ground for testing of digital electronic systems on advanced aircraft. Many advanced features, including multiple 16-bit microprocessors, pipeline data-flow architecture, advanced operating system, and resident software-development tools. Basic collection of software includes program for handling many types of data and for displays in various formats. User easily extends basic software library. Hardware and software interfaces to subsystems provided by user designed for flexibility in configuration to meet user's requirements.

Glover, Richard D.↗

NASA NTRS2015

Software Innovation in a Mission Critical Environment

Operating in mission-critical environments requires trusted solutions, and the preference for "tried and true" approaches presents a potential barrier to infusing innovation into mission-critical systems. This presentation explores opportunities to overcome this barrier in the software domain. It outlines specific areas of innovation in software development achieved by the Johnson Space Center (JSC) Engineering Directorate in support of NASA's major human spaceflight programs, including International Space Station, Multi-Purpose Crew Vehicle (Orion), and Commercial Crew Programs. Software engineering teams at JSC work with hardware developers, mission planners, and system operators to integrate flight vehicles, habitats, robotics, and other spacecraft elements for genuinely mission critical applications. The innovations described, including the use of NASA Core Flight Software and its associated software tool chain, can lead to software that is more affordable, more reliable, better modelled, more flexible, more easily maintained, better tested, and enabling of automation.

Fredrickson, Steven↗

NASA NTRS1994

Lessons learned in deploying software estimation technology and tools

Developing a software product involves estimating various project parameters. This is typically done in the planning stages of the project when there is much uncertainty and very little information. Coming up with accurate estimates of effort, cost, schedule, and reliability is a critical problem faced by all software project managers. The use of estimation models and commercially available tools in conjunction with the best bottom-up estimates of software-development experts enhances the ability of a product development group to derive reasonable estimates of important project parameters. This paper describes the experience of the IBM Software Solutions (SWS) Toronto Laboratory in selecting software estimation models and tools and deploying their use to the laboratory's product development groups. It introduces the SLIM and COSTAR products, the software estimation tools selected for deployment to the product areas, and discusses the rationale for their selection. The paper also describes the mechanisms used for technology injection and tool deployment, and concludes with a discussion of important lessons learned in the technology and tool insertion process.

Panlilio-Yap, Nikki↗

NASA NTRS1996

An Object-Oriented Approach to Writing Computational Electromagnetics Codes

Presently, most computer software development in the Computational Electromagnetics (CEM) community employs the structured programming paradigm, particularly using the Fortran language. Other segments of the software community began switching to an Object-Oriented Programming (OOP) paradigm in recent years to help ease design and development of highly complex codes. This paper examines design of a time-domain numerical analysis CEM code using the OOP paradigm, comparing OOP code and structured programming code in terms of software maintenance, portability, flexibility, and speed.

Zimmerman, Martin↗

NASA NTRS1985

Plasma and magnetospheric research

Research and development in plasmas and magnetospheric environments is reported. Topics discussed include: analysis and techniques of software development; data analysis and modeling; spacecraft sheath effects; laboratory plasma flow studies; instrument development.

Comfort, R. H.↗