Engineering Papers⌕ Search

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.

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

At least 721 records · Page 40

Propel: Tools and Methods for Practical Source Code Model Checking

The work reported here is an overview and snapshot of a project to develop practical model checking tools for in-the-loop verification of NASA s mission-critical, multithreaded programs in Java and C++. Our strategy is to develop and evaluate both a design concept that enables the application of model checking technology to C++ and Java, and a model checking toolset for C++ and Java. The design concept and the associated model checking toolset is called Propel. It builds upon the Java PathFinder (JPF) tool, an explicit state model checker for Java applications developed by the Automated Software Engineering group at NASA Ames Research Center. The design concept that we are developing is Design for Verification (D4V). This is an adaption of existing best design practices that has the desired side-effect of enhancing verifiability by improving modularity and decreasing accidental complexity. D4V, we believe, enhances the applicability of a variety of V&V approaches; we are developing the concept in the context of model checking. The model checking toolset, Propel, is based on extending JPF to handle C++. Our principal tasks in developing the toolset are to build a translator from C++ to Java, productize JPF, and evaluate the toolset in the context of D4V. Through all these tasks we are testing Propel capabilities on customer applications.

Mansouri-Samani, Massoud↗

Aspects, Wrappers and Events

This viewgraph presentation provides information on Object Infrastructure Framework (OIF), an Aspect-Oriented Programming (AOP) system. The presentation begins with an introduction to the difficulties and requirements of distributed computing, including functional and non-functional requirements (ilities). The architecture of Distributed Object Technology includes stubs, proxies for implementation objects, and skeletons, proxies for client applications. The key OIF ideas (injecting behavior, annotated communications, thread contexts, and pragma) are discussed. OIF is an AOP mechanism; AOP is centered on: 1) Separate expression of crosscutting concerns; 2) Mechanisms to weave the separate expressions into a unified system. AOP is software engineering technology for separately expressing systematic properties while nevertheless producing running systems that embody these properties.

Filman, Robert E.↗

Case for Deploying Complex Systems Utilizing Commodity Components

This viewgraph representation presents a study of the transition of computer networks and software engineering at the Huntsville Operations Support Center (HOSC) from a client/server UNIX based system to a client/server system based on commodity priced and open system components. Topics covered include: an overview of HOSC ground support systems, an analysis for changes to the existing ground support system, an analysis of options considered for the transition to a new system, and a consideration of goals for a new system.

Bryant, Barry S.↗

Alternative Metrics for Evaluating the Resilence of Advanced Life Support Systems

Ensuring the safety of the crew is a key performance requirement of a life support system. However, a number of conceptual and practical difficulties arise when devising metrics to concretely measure the ability of a life support system to maintain critical functions in the presence of anticipated and unanticipated faults. Resilience is a dynamic property of a life support system that depends on the complex interactions between faults, controls and system hardware. We review some of the approaches to understanding the robustness or resilience of complex systems being developed in diverse fields such as ecology, software engineering and cell biology and discuss their applicability to regenerative life support systems. We also consider how approaches to measuring resilience vary depending on system design choices such as the definition and choice of the nominal operating regime. Finally, we explore data collection and implementation issues such as the key differences between the instantaneous or conditional and average or overall measures of resilience. Extensive simulation of a hybrid computational model of a water revitalization subsystem (WRS) with probabilistic, component-level faults provides data about off-nominal behavior of the system. The data are used to consider alternative measures of resilience as predictors of the system's ability to recover from component-level faults.

Bell, Ann Maria↗

Using CMMI for Improvement at GSFC

This viewgraph presentation discusses the Capability Maturity Model Integrated (CMMI) is an integrated framework for maturity models and associated products that integrates the two key disciplines that are inseparable in a systems development activity: software engineering and systems engineering.

Godfrey, Sara H.↗

Software for Intelligent System Health Management (ISHM)

The slide presentation is a briefing in four areas: overview of health management paradigms; overview of the ARC-Houston Software Engineering Technology Workshop held on April 20-22, 2004; identified technologies relevant to technical themes of intelligent system health management; and the author's thoughts on these topics.

Trevino, Luis C.↗

Proceedings 3rd NASA/IEEE Workshop on Formal Approaches to Agent-Based Systems (FAABS-III)

These preceedings contain 18 papers and 4 poster presentation, covering topics such as: multi-agent systems, agent-based control, formalism, norms, as well as physical and biological models of agent-based systems. Some applications presented in the proceedings include systems analysis, software engineering, computer networks and robot control.

Hinchey, Michael↗

[Editorial on NASA and its Goals]

Innovations in Systems and Software Engineering: A NASA Journal will address research and development issues that will be important to NASA in attaining its exploration goals. The journal will report on prior research and contemplate how it may be practically applied in future missions. It will provide feedback to the community on issues of concern to NASA and on work that NASA and its collaborators are performing to address these issues. It will also provide a forum for researchers to highlight topics that either are, or should be, of interest to NASA. The selection of papers in this our inaugural issue includes some work that has been funded by NASA in the past, and which has already been directly applied to NASA projects and missions, as well as research in areas that NASA has interest in, although the work reported has not been funded by NASA.

Hinchey, Michael G.↗

Beyond the Prototype: The Design Evolution of a Deployed AI System

Our previous experiences with deployed intelligent control agents for NASA advanced life support systems (Schreckenghost et al., 2002) inspired us to develop the Distributed Collaboration and Interaction (DCI) system to help humans and mostly-autonomous software agents work together. We discovered many unaddressed needs for human interaction with control agents that operate continuously over months to years to monitor and perform process control for regenerative life support systems. These systems recover usable water or air from the waste products created by biological systems over time. Through the DCI project, we have addressed the needs for interaction between humans and autonomous control systems. This paper describes the software engineering aspects of our experiences, first, in designing and developing a prototype of the DCI system, and later, in adjusting the implementation to make the leap from initial prototype to a system ready to be applied under varying circumstances to meet different needs. The details in the paper focus primarily on the second stage of development. The DCI system is currently deployed, operating 24/7, to assist humans to interact with an advanced Water Recovery System (WRS). In addition, we have demonstrated an application of DCI to support ground personnel in mission support roles.

Martin, C.↗

A software defect detection methodology

This paper identifies baseline procedures for verifying software for individual, small team, and large team development efforts for mission-critical and non-mission-critical software.

software engineering software verification validat↗

Mission planning and execution within the mission data system

Not only has the number of launched spacecraft per year exploded over the past few years, but also spacecraft are getting progressively more complex, as flyby missions give way to remote orbiters, which in turn give way to rovers and other in situ explorers. To address the software issues in this expanding mission set, JPL started the Mission Data System (MDS) project, an effort to make flight software engineering more straightforward and less prone to error through the eplicit modeling of spacecraft state. This paper presents how MDS performs mission planning and execution in the context of explicitly managing spacecraft state.

MDS↗

A Generic Multibody Parachute Simulation Model

Flight simulation of dynamic atmospheric vehicles with parachute systems is a complex task that is not easily modeled in many simulation frameworks. In the past, the performance of vehicles with parachutes was analyzed by simulations dedicated to parachute operations and were generally not used for any other portion of the vehicle flight trajectory. This approach required multiple simulation resources to completely analyze the performance of the vehicle. Recently, improved software engineering practices and increased computational power have allowed a single simulation to model the entire flight profile of a vehicle employing a parachute.

Neuhaus, Jason Richard↗

Advances in Distributed Operations and Mission Activity Planning for Mars Surface Exploration

A centralized mission activity planning system for any long-term mission, such as the Mars Exploration Rover Mission (MER), is completely infeasible due to budget and geographic constraints. A distributed operations system is key to addressing these constraints; therefore, future system and software engineers must focus on the problem of how to provide a secure, reliable, and distributed mission activity planning system. We will explain how Maestro, the next generation mission activity planning system, with its heavy emphasis on portability and distributed operations has been able to meet these design challenges. MER has been an excellent proving ground for Maestro's new approach to distributed operations. The backend that has been developed for Maestro could benefit many future missions by reducing the cost of centralized operations system architecture.

Mars Exploration Rover (MER)↗

NASA's Software Safety Standard

NASA (National Aeronautics and Space Administration) relies more and more on software to control, monitor, and verify its safety critical systems, facilities and operations. Since the 1960's there has hardly been a spacecraft (manned or unmanned) launched that did not have a computer on board that provided vital command and control services. Despite this growing dependence on software control and monitoring, there has been no consistent application of software safety practices and methodology to NASA's projects with safety critical software. Led by the NASA Headquarters Office of Safety and Mission Assurance, the NASA Software Safety Standard (STD-18l9.13B) has recently undergone a significant update in an attempt to provide that consistency. This paper will discuss the key features of the new NASA Software Safety Standard. It will start with a brief history of the use and development of software in safety critical applications at NASA. It will then give a brief overview of the NASA Software Working Group and the approach it took to revise the software engineering process across the Agency.

Ramsay, Christopher M.↗

Electrical Conductivity in Textiles

Copper is the most widely used electrical conductor. Like most metals, though, it has several drawbacks: it is heavy, expensive, and can break. Fibers that conduct electricity could be the solutions to these problems, and they are of great interest to NASA. Conductive fibers provide lightweight alternatives to heavy copper wiring in a variety of settings, including aerospace, where weight is always a chief concern. This is an area where NASA is always seeking improved materials. The fibers are also more cost-effective than metals. Expenditure is another area where NASA is always looking to make improvements. In the case of electronics that are confined to small spaces and subject to severe stress, copper is prone to breaking and losing connection over time. Flexible conductive fibers eliminate that problem. They are more supple and stronger than brittle copper and, thus, find good use in these and similar situations. While clearly a much-needed material, electrically conductive fibers are not readily available. The cost of new technology development, with all the pitfalls of troubleshooting production and the years of testing, and without the guarantee of an immediate market, is often too much of a financial hazard for companies to risk. NASA, however, saw the need for electrical fibers in its many projects and sought out a high-tech textile company that was already experimenting in this field, Syscom Technology, Inc., of Columbus, Ohio. Syscom was founded in 1993 to provide computer software engineering services and basic materials research in the areas of high-performance polymer fibers and films. In 1999, Syscom decided to focus its business and technical efforts on development of high-strength, high-performance, and electrically conductive polymer fibers. The company developed AmberStrand, an electrically conductive, low-weight, strong-yet-flexible hybrid metal-polymer YARN.

Source record↗

Beyond the Prototype: The Design Evolution of a Deployed AI System

Our previous experiences with deployed intelligent control agents for NASA advanced life support systems (Schreckenghost et al., 2002) inspired us to develop the Distributed Collaboration and Interaction (DCI) system to help humans and mostly-autonomous software agents work together. We discovered many unaddressed needs for human interaction with control agents that operate continuously over months to years to monitor and perform process control for regenerative life support systems. These systems recover usable water or air from the waste products created by biological systems over time. Through the DCI project, we have addressed the needs for interaction between humans and autonomous control systems. This paper describes the software engineering aspects of our experiences, first, in designing and developing a prototype of the DCI system, and later, in adjusting the implementation to make the leap from initial prototype to a system ready to be applied under varying circumstances to meet different needs. The details in the paper focus primarily on the second stage of development. The DCI system is currently deployed, operating 24/7, to assist humans to interact with an advanced Water Recovery System (WRS). In addition, we have demonstrated an application of DCI to support ground personnel in mission support roles.

Martin, Cheryl↗