SEARCH · Engineering Papers

Results for “engineering software”

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 883 records · Page 49

All sources NASA NTRS DOE OSTI

NASA NTRS1983

Projecting manpower to attain quality

The resulting model is useful as a projection tool but must be validated in order to be used as an on-going software cost engineering tool. A procedure is developed to facilitate the tracking of model projections and actual data to allow the model to be tuned. Finally, since the model must be used in an environment of overlapping development activities on a progression of software elements in development and maintenance, a manpower allocation model is developed for use in a steady state development/maintenance environment. In these days of soaring software costs it becomes increasingly important to properly manage a software development project. One element of the management task is the projection and tracking of manpower required to perform the task. In addition, since the total cost of the task is directly related to the initial quality built into the software, it becomes a necessity to project the development manpower in a way to attain that quality. An approach to projecting and tracking manpower with quality in mind is described.

Rone, K. Y.↗

NASA NTRS2017

Advanced Software V&V for Civil Aviation and Autonomy

With the advances in high-computing platform (e.g., advanced graphical processing units or multi-core processors), computationally-intensive software techniques such as the ones used in artificial intelligence or formal methods have provided us with an opportunity to further increase safety in the aviation industry. Some of these techniques have facilitated building safety at design time, like in aircraft engines or software verification and validation, and others can introduce safety benefits during operations as long as we adapt our processes. In this talk, I will present how NASA is taking advantage of these new software techniques to build in safety at design time through advanced software verification and validation, which can be applied earlier and earlier in the design life cycle and thus help also reduce the cost of aviation assurance. I will then show how run-time techniques (such as runtime assurance or data analytics) offer us a chance to catch even more complex problems, even in the face of changing and unpredictable environments. These new techniques will be extremely useful as our aviation systems become more complex and more autonomous.

software assurance↗

NASA NTRS2013

Installation of TVC Actuators in a Two Axis Inertial Load Simulator Test Stand

This paper is about the installation of Space Shuttle Main Engines (SSME) actuators in the new Two Axis Inertial Load Simulator (ILS) at MSFC. The new test stand will support the core stage of the Space Launch System (SLS). Because of the unique geometry of the new test stand standard actuator installation procedures will not work. I have been asked to develop a design on how to install the actuators into the new test stand. After speaking with the engineers and technicians I have created a possible design solution. Using Pro Engineer design software and running my own stress calculations I have proven my design is feasible. I have learned how to calculate the stresses my design will see from this task. From the calculations I have learned I have over built the apparatus. I have also expanded my knowledge of Pro Engineer and was able to create a model of my idea.

Dziubanek, Adam↗

NASA NTRS2012

Logic Model Checking of Time-Periodic Real-Time Systems

In this paper we report on the work we performed to extend the logic model checker SPIN with built-in support for the verification of periodic, real-time embedded software systems, as commonly used in aircraft, automobiles, and spacecraft. We first extended the SPIN verification algorithms to model priority based scheduling policies. Next, we added a library to support the modeling of periodic tasks. This library was used in a recent application of the SPIN model checker to verify the engine control software of an automobile, to study the feasibility of software triggers for unintended acceleration events.

software analysis↗

NASA NTRS1985

Development of an Expert System for Representing Procedural Knowledge

A high level of automation is of paramount importance in most space operations. It is critical for unmanned missions and greatly increases the effectiveness of manned missions. However, although many functions can be automated by using advanced engineering techniques, others require complex reasoning, sensing, and manipulatory capabilities that go beyond this technology. Automation of fault diagnosis and malfunction handling is a case in point. The military have long been interested in this problem, and have developed automatic test equipment to aid in the maintenance of complex military hardware. These systems are all based on conventional software and engineering techniques. However, the effectiveness of such test equipment is severely limited. The equipment is inflexible and unresponsive to the skill level of the technicians using it. The diagnostic procedures cannot be matched to the exigencies of the current situation nor can they cope with reconfiguration or modification of the items under test. The diagnosis cannot be guided by useful advice from technicians and, when a fault cannot be isolated, no explanation is given as to the cause of failure. Because these systems perform a prescribed sequence of tests, they cannot utilize knowledge of a particular situation to focus attention on more likely trouble spots. Consequently, real-time performance is highly unsatisfactory. Furthermore, the cost of developing test software is substantial and time to maturation is excessive. Significant advances in artificial intelligence (AI) have recently led to the development of powerful and flexible reasoning systems, known as expert or knowledge-based systems. We have devised a powerful and theoretically sound scheme for representing and reasoning about procedural knowledge.

Georgeff, Michael P.↗

NASA NTRS1991

Technology readiness assessment of advanced space engine integrated controls and health monitoring

An evaluation is given for an integrated control and health-monitoring (ICHM) system that is designed to be used with hydrogen-oxygen rocket engines. The minimum required ICHM functions, system elements, technology readiness, and system cost are assessed for a system which permits the operation of H-O engines that are space-based, reusable, and descent-throttleable. Only the advanced sensors and some engine-dependent software are not found to be ready for applications to laboratory demonstration. Other systems related to the minimum functions are more developed, bringing the total system readiness to the conceptual design stage. Based on the evaluation of the H-O ICHM, it is estimated that the minimum system requirements for demonstration on an engine system testbed will require an investment of 30-45 million dollars over 6 years.

Millis, Marc G.↗

NASA NTRS2008

Cassini Information Management System in Distributed Operations Collaboration and Cassini Science Planning

Launched on October 15, 1997, the Cassini-Huygens spacecraft began its ambitious journey to the Saturnian system with a complex suite of 12 scientific instruments, and another 6 instruments aboard the European Space Agencies Huygens Probe. Over the next 6 1/2 years, Cassini would continue its relatively simplistic cruise phase operations, flying past Venus, Earth, and Jupiter. However, following Saturn Orbit Insertion (SOI), Cassini would become involved in a complex series of tasks that required detailed resource management, distributed operations collaboration, and a data base for capturing science objectives. Collectively, these needs were met through a web-based software tool designed to help with the Cassini uplink process and ultimately used to generate more robust sequences for spacecraft operations. In 2001, in conjunction with the Southwest Research Institute (SwRI) and later Venustar Software and Engineering Inc., the Cassini Information Management System (CIMS) was released which enabled the Cassini spacecraft and science planning teams to perform complex information management and team collaboration between scientists and engineers in 17 countries. Originally tailored to help manage the science planning uplink process, CIMS has been actively evolving since its inception to meet the changing and growing needs of the Cassini uplink team and effectively reduce mission risk through a series of resource management validation algorithms. These algorithms have been implemented in the web-based software tool to identify potential sequence conflicts early in the science planning process. CIMS mitigates these sequence conflicts through identification of timing incongruities, pointing inconsistencies, flight rule violations, data volume issues, and by assisting in Deep Space Network (DSN) coverage analysis. In preparation for extended mission operations, CIMS has also evolved further to assist in the planning and coordination of the dual playback redundancy of highvalue data from targets such as Titan and Enceladus. This paper will outline the critical role that CIMS has played for Cassini in the distributed ops paradigm throughout operations. This paper will also examine the evolution that CIMS has undergone in the face of new science discoveries and fluctuating operational needs. And finally, this paper will conclude with theoretical adaptation of CIMS for other projects and the potential savings in cost and risk reduction that could potentially be tapped into by future missions.

Equils, Douglas J.↗

NASA NTRS1997

Remote Sensing of Surficial Process Responses to Extreme Meteorological Events

Changes in the frequency and magnitude of extreme meteorological events are associated with changing environmental means. Such events are important in human affairs, and can also be investigated by orbital remote sensing. During the course of this project, we applied ERS-1, ERS-2, Radarsat, and an airborne sensor (AIRSAR-TOPSAR) to measure flood extents, flood water surface profiles, and flood depths. We established a World Wide Web site (the Dartmouth Flood Observatory) for publishing remote sensing-based maps of contemporary floods worldwide; this is also an online "active archive" that presently constitutes the only global compilation of extreme flood events. We prepared an article for EOS concerning SAR imaging of the Mississippi Valley flood; an article for the International Journal of Remote Sensing on measurement of a river flood wave using ERS-2, began work on an article (since completed and published) on the Flood Observatory for a Geoscience Information Society Proceedings volume, and presented lectures at several Geol. Soc. of America Natl. Meetings, an Assoc. of Amer. Geographers Natl. Meeting, and a Binghamton Geomorphology Symposium (all on SAR remote sensing of the Mississippi Valley flood). We expanded in-house modeling capabilities by installing the latest version of the Army Corps of Engineers RMA two-dimensional hydraulics software and BYU Engineering Graphics Lab's Surface Water Modeling System (finite elements based pre- and post-processors for RMA work) and also added watershed modeling software. We are presently comparing the results of the 2-d flow models with SAR image data. The grant also supported several important upgrades of pc-based remote sensing infrastructure at Dartmouth. During work on this grant, we collaborated with several workers at the U.S. Army Corps of Engineers, Remote Sensing/GIS laboratory (for flood inundation mapping and modeling; particularly of the Illinois River using the AIRSAR/TOPSAR/ERS-2 combined data), with Dr. Karen Prestegaard at the University of Maryland (geomorphological responses to the extreme 1993 flood along the Raccoon drainage in central Iowa), and with Mr Tim Scrom of the Albany National Weather Service River Forecast Center (initial planning for the use of Radarsat and ERS-2 for flood warning). The work thus initiated with this proposal is continuing.

Brakenridge, G. Robert↗

NASA NTRS1993

Research and Technology at the John F. Kennedy Space Center 1993

As the NASA Center responsible for assembly, checkout, servicing, launch, recovery, and operational support of Space Transportation System elements and payloads, the John F. Kennedy Space Center is placing increasing emphasis on its advanced technology development program. This program encompasses the efforts of the Engineering Development Directorate laboratories, most of the KSC operations contractors, academia, and selected commercial industries - all working in a team effort within their own areas of expertise. This edition of the Kennedy Space Center Research and Technology 1993 Annual Report covers efforts of all these contributors to the KSC advanced technology development program, as well as our technology transfer activities. Major areas of research include material science, advanced software, industrial engineering, nondestructive evaluation, life sciences, atmospheric sciences, environmental technology, robotics, and electronics and instrumentation.

Source record↗

NASA NTRS2001

Engineering Documentation and Data Control

Mississippi Space Services (MSS) the facility services contractor for NASA's John C. Stennis Space Center (SSC), is utilizing technology to improve engineering documentation and data control. Two identified improvement areas, labor intensive documentation research and outdated drafting standards, were targeted as top priority. MSS selected AutoManager(R) WorkFlow from Cyco software to manage engineering documentation. The software is currently installed on over 150 desctops. The outdated SSC drafting standard was written for pre-CADD drafting methods, in other words, board drafting. Implementation of COTS software solutions to manage engineering documentation and update the drafting standard resulted in significant increases in productivity by reducing the time spent searching for documents.

Matteson, Michael J.↗

NASA NTRS2016

SLS Flight Software Testing: Using a Modified Agile Software Testing Approach

NASA's Space Launch System (SLS) is an advanced launch vehicle for a new era of exploration beyond earth's orbit (BEO). The world's most powerful rocket, SLS, will launch crews of up to four astronauts in the agency's Orion spacecraft on missions to explore multiple deep-space destinations. Boeing is developing the SLS core stage, including the avionics that will control vehicle during flight. The core stage will be built at NASA's Michoud Assembly Facility (MAF) in New Orleans, LA using state-of-the-art manufacturing equipment. At the same time, the rocket's avionics computer software is being developed here at Marshall Space Flight Center in Huntsville, AL. At Marshall, the Flight and Ground Software division provides comprehensive engineering expertise for development of flight and ground software. Within that division, the Software Systems Engineering Branch's test and verification (T&V) team uses an agile test approach in testing and verification of software. The agile software test method opens the door for regular short sprint release cycles. The idea or basic premise behind the concept of agile software development and testing is that it is iterative and developed incrementally. Agile testing has an iterative development methodology where requirements and solutions evolve through collaboration between cross-functional teams. With testing and development done incrementally, this allows for increased features and enhanced value for releases. This value can be seen throughout the T&V team processes that are documented in various work instructions within the branch. The T&V team produces procedural test results at a higher rate, resolves issues found in software with designers at an earlier stage versus at a later release, and team members gain increased knowledge of the system architecture by interfacing with designers. SLS Flight Software teams want to continue uncovering better ways of developing software in an efficient and project beneficial manner. Through agile testing, there has been increased value through individuals and interactions over processes and tools, improved customer collaboration, and improved responsiveness to changes through controlled planning. The presentation will describe agile testing methodology as taken with the SLS FSW Test and Verification team at Marshall Space Flight Center.

Bolton, Albanie T.↗

NASA NTRS2019

Defining a Space Mission Architectural Framework: Guiding Robotic Space Mission Design and Development at NASA Goddard Spaceflight Center

Modern Systems Engineering activities for robotic science missions face increased complexity due to evolving measurement requirements, increased collaboration amongst stakeholders and increased collaboration between human and robotic systems. While NASA has employed standard process frameworks for project management and systems engineering for years, it has not yet established an architecture framework (AF) by which its mission systems are described. While an architecture framework is not a necessary component of an organization's operations, the value of a specified AF greatly enhances an organization's ability to define systems consistently and aid in communication across project and organizational boundaries. The current effort identifies an approach to establishing a Space Mission Architecture Framework (SMAF), an AF with roots in ISO 42010 (Systems and Software Engineering-Architecture Description), NASA Procedural Requirements (NPR) 7120.5 (NASA Space Flight Program and Project Management Requirements) and 7123.1B (NASA Systems Engineering Processes and Requirements). The heart of the AF lies in its viewpoints and work products, artifacts that represent a set of information from the viewpoint of a particular stakeholder. This effort articulates the needs, goals and objectives that the SMAF addresses, as well as the approach to creating the framework and establishing the various work products. A full set of work products, sufficient to satisfy the Mission System reporting requirements of NPR 7120/7123 at Key Decision Point (KDP) A is identified in this paper.

Architecture↗

NASA NTRS2012

ITOS to EDGE "Bridge" Software for Morpheus Lunar/Martian Vehicle

My project Involved Improving upon existing software and writing new software for the Project Morpheus Team. Specifically, I created and updated Integrated Test and Operations Systems (ITOS) user Interfaces for on-board Interaction with the vehicle during archive playback as well as live streaming data. These Interfaces are an integral part of the testing and operations for the Morpheus vehicle providing any and all information from the vehicle to evaluate instruments and insure coherence and control of the vehicle during Morpheus missions. I also created a "bridge" program for Interfacing "live" telemetry data with the Engineering DOUG Graphics Engine (EDGE) software for a graphical (standalone or VR dome) view of live Morpheus nights or archive replays, providing graphical representation of vehicle night and movement during subsequent tests and in real missions.

Hirsh, Robert↗

NASA NTRS2011

MicroShell Minimalist Shell for Xilinx Microprocessors

MicroShell is a lightweight shell environment for engineers and software developers working with embedded microprocessors in Xilinx FPGAs. (MicroShell has also been successfully ported to run on ARM Cortex-M1 microprocessors in Actel ProASIC3 FPGAs, but without project-integration support.) Micro Shell decreases the time spent performing initial tests of field-programmable gate array (FPGA) designs, simplifies running customizable one-time-only experiments, and provides a familiar-feeling command-line interface. The program comes with a collection of useful functions and enables the designer to add an unlimited number of custom commands, which are callable from the command-line. The commands are parameterizable (using the C-based command-line parameter idiom), so the designer can use one function to exercise hardware with different values. Also, since many hardware peripherals instantiated in FPGAs have reasonably simple register-mapped I/O interfaces, the engineer can edit and view hardware parameter settings at any time without stopping the processor. MicroShell comes with a set of support scripts that interface seamlessly with Xilinx's EDK tool. Adding an instance of MicroShell to a project is as simple as marking a check box in a library configuration dialog box and specifying a software project directory. The support scripts then examine the hardware design, build design-specific functions, conditionally include processor-specific functions, and complete the compilation process. For code-size constrained designs, most of the stock functionality can be excluded from the compiled library. When all of the configurable options are removed from the binary, MicroShell has an unoptimized memory footprint of about 4.8 kB and a size-optimized footprint of about 2.3 kB. Since MicroShell allows unfettered access to all processor-accessible memory locations, it is possible to perform live patching on a running system. This can be useful, for instance, if a bug is discovered in a routine but the system cannot be rebooted: Shell allows a skilled operator to directly edit the binary executable in memory. With some forethought, MicroShell code can be located in a different memory location from custom code, permitting the custom functionality to be overwritten at any time without stopping the controlling shell.

Werne, Thomas A.↗

NASA NTRS2004

OTIS 3.2 Software Released

Trajectory, mission, and vehicle engineers concern themselves with finding the best way for an object to get from one place to another. These engineers rely upon special software to assist them in this. For a number of years, many engineers have used the OTIS program for this assistance. With OTIS, an engineer can fully optimize trajectories for airplanes, launch vehicles like the space shuttle, interplanetary spacecraft, and orbital transfer vehicles. OTIS provides four modes of operation, with each mode providing successively stronger optimization capability. The most powerful mode uses a mathematical method called implicit integration to solve what engineers and mathematicians call the optimal control problem. OTIS 3.2, which was developed at the NASA Glenn Research Center, is the latest release of this industry workhorse and features new capabilities for parameter optimization and mission design. OTIS stands for Optimal Control by Implicit Simulation, and it is implicit integration that makes OTIS so powerful at solving trajectory optimization problems. Why is this so important? The optimization process not only determines how to get from point A to point B, but it can also determine how to do this with the least amount of propellant, with the lightest starting weight, or in the fastest time possible while avoiding certain obstacles along the way. There are numerous conditions that engineers can use to define optimal, or best. OTIS provides a framework for defining the starting and ending points of the trajectory (point A and point B), the constraints on the trajectory (requirements like "avoid these regions where obstacles occur"), and what is being optimized (e.g., minimize propellant). The implicit integration method can find solutions to very complicated problems when there is not a lot of information available about what the optimal trajectory might be. The method was first developed for solving two-point boundary value problems and was adapted for use in OTIS. Implicit integration usually allows OTIS to find solutions to problems much faster than programs that use explicit integration and parametric methods. Consequently, OTIS is best suited to solving very complicated and highly constrained problems.

Riehl, John P.↗

NASA NTRS2001

Requirements engineering and program synthesis: Mutually exclusive or synergistic?

There has often been a clash within the formal methods community between early life-cycle proponents such as the requirements engineering community and late life-cycle proponents such as the program synthesis community. This talk will first characterize these positions and their underlying assumptions, and then expose a common set of problems and approaches. The talk will then propose an integrated life-cycle framework, and expound on its potential benefits. Technical challenges to achieving this integrated life-cycle framework will be described, as well as some preliminary work towards that goal.

Program synthesis↗

NASA NTRS2014

Firing Room Remote Application Software Development

The Engineering and Technology Directorate (NE) at National Aeronautics and Space Administration (NASA) Kennedy Space Center (KSC) is designing a new command and control system for the checkout and launch of Space Launch System (SLS) and future rockets. The purposes of the semester long internship as a remote application software developer include the design, development, integration, and verification of the software and hardware in the firing rooms, in particular with the Mobile Launcher (ML) Launch Accessories subsystem. In addition, a Conversion Fusion project was created to show specific approved checkout and launch engineering data for public-friendly display purposes.

Pathways↗

NASA NTRS2002

Using a Formal Approach for Reverse Engineering and Design Recovery to Support Software Reuse

This document describes 3rd year accomplishments and summarizes overall project accomplishments. Included as attachments are all published papers from year three. Note that the budget for this project was discontinued after year two, but that a residual budget from year two allowed minimal continuance into year three. Accomplishments include initial investigations into log-file based reverse engineering, service-based software reuse, and a source to XML generator.

Gannod, Gerald C.↗