Results for “reuse” — Page 2

NASA NTRS1989

SSFP approach to software reuse

This talk began by presenting the Space Station Freedom Program (SSFP) definitions of software commonality and software reuse. Software commonality is the use of identical, interchangeable, functionally compatible, or similar software items to satisfy different sets of functionally similar requirements. The Software Support Environment (SSE) and the Data Management System (DMS) of onboard computing facilities are examples of SSFP common software. Software reuse is the use of identical, compatible, or similar software items in either modified or unmodified form to satisfy development activities at any point in the software life cycle; in other words, taking an existing item and applying it to another development activity. Software commonality has been mandated in several critical areas (such as the SSE and DMS) and a policy directive is under review. A software reuse study group was established in May 1988 to gather background information (see Level 2 Software Reuse Study that follows by Scott Herman). The SSFP Program Definition and Requirements Document contains requirements for SSE support in the area of software reuse. The SSE is a collection of tools and rules, and provides the common environment to be used for the life cycle management of all SSFP operational software.

Snyder, Peg↗

NASA NTRS1993

A NASA-wide approach toward cost-effective, high-quality software through reuse

NASA Langley Research Center sponsored the second Workshop on NASA Research in Software Reuse on May 5-6, 1992 at the Research Triangle Park, North Carolina. The workshop was hosted by the Research Triangle Institute. Participants came from the three NASA centers, four NASA contractor companies, two research institutes and the Air Force's Rome Laboratory. The purpose of the workshop was to exchange information on software reuse tool development, particularly with respect to tool needs, requirements, and effectiveness. The participants presented the software reuse activities and tools being developed and used by their individual centers and programs. These programs address a wide range of reuse issues. The group also developed a mission and goals for software reuse within NASA. This publication summarizes the presentations and the issues discussed during the workshop.

Scheper, Charlotte O.↗

NASA NTRS1997

Reuse of a Formal Model for Requirements Validation

This paper reports experience from how a project engaged in the process of requirements analysis for evolutionary builds can reuse the formally specified design model produced for a similar, earlier project in the same domain. Two levels of reuse are described here. First, a formally specified generic design model was generated on one project to systematically capture the design commonality in a set of software monitors on board a spacecraft. These monitors periodically check for faults and invoke recovery software when needed. The paper summarizes the use of the design model to validate the software design of the various monitors on that first project. Secondly, the paper describes how the formal design model created for the first project was reused on a second, subsequent project. The model was reused to validate the evolutionary requirements for the second project's software monitors, which were being developed in a series of builds. Some mismatches due to the very different architectures on the two projects suggested changes to make the model more generic. In addition, several advantages to the reuse of the first project's formal model on the second project are reported.

Lutz, Robyn R.↗

NASA NTRS2011

Tools to Support the Reuse of Software Assets for the NASA Earth Science Decadal Survey Missions

The NASA Earth Science Data Systems (ESDS) Software Reuse Working Group (SRWG) is chartered with the investigation, production, and dissemination of information related to the reuse of NASA Earth science software assets. One major current objective is to engage the NASA decadal missions in areas relevant to software reuse. In this paper we report on the current status of these activities. First, we provide some background on the SRWG in general and then discuss the group s flagship recommendation, the NASA Reuse Readiness Levels (RRLs). We continue by describing areas in which mission software may be reused in the context of NASA decadal missions. We conclude the paper with pointers to future directions.

Mattmann, Chris A.↗

NASA NTRS1989

Software Reuse Issues

NASA Langley Research Center sponsored a Workshop on NASA Research in Software Reuse on November 17-18, 1988 in Melbourne, Florida, hosted by Software Productivity Solutions, Inc. Participants came from four NASA centers and headquarters, eight NASA contractor companies, and three research institutes. Presentations were made on software reuse research at the four NASA centers; on Eli, the reusable software synthesis system designed and currently under development by SPS; on Space Station Freedom plans for reuse; and on other reuse research projects. This publication summarizes the presentations made and the issues discussed during the workshop.

Voigt, Susan J.↗

NASA NTRS1989

Prototype software reuse environment at Goddard Space Flight Center

The Goddard Space Flight Center (GSFC) work is organized into four phases and includes participation by a contractor, CTA, Inc. The first phase was an automation study, which began with a comprehensive survey of software development automation technologies. Eight technical areas were analyzed for goals, current capabilities, and obstacles. The study documented current software development practice in GSFC Mission Operations and Data Systems Directorate, and presented short- and long-term recommendations that included focus on reuse and object-oriented development. The second phase, which has been completed, developed a prototype reuse environment with tools supporting object-oriented requirements analysis and design. This phase addressed the operational concept of software reuse, i.e., it attempted to understand how software can be reused. This environment has two semantic networks: object and keywords, and includes automated search, interactive browsing and a graphical display of database contents. Phase 3 was a domain analysis of Payload Operations Control Center (POCC) software. The goal in this phase was to create an initial repository of reusable components and techniques. Seven existing Operations Control Centers at GSFC were studied, but the domain analysis proved to be very slow. A lesson learned from this was that senior people who understand the environment and the functionality of the area are needed to perform successful domain analyses.

Truszkowski, Walt↗

NASA NTRS1991

Support for comprehensive reuse

Reuse of products, processes, and other knowledge will be the key to enable the software industry to achieve the dramatic improvement in productivity and quality required to satisfy the anticipated growing demands. Although experience shows that certain kinds of reuse can be successful, general success has been elusive. A software life-cycle technology which allows comprehensive reuse of all kinds of software-related experience could provide the means to achieving the desired order-of-magnitude improvements. A comprehensive framework of models, model-based characterization schemes, and support mechanisms for better understanding, evaluating, planning, and supporting all aspects of reuse are introduced.

Basili, V. R.↗

NASA NTRS1993

Software reuse in spacecraft planning and scheduling systems

The use of a software toolkit and development methodology that supports software reuse is described. The toolkit includes source-code-level library modules and stand-alone tools which support such tasks as data reformatting and report generation, simple relational database applications, user interfaces, tactical planning, strategic planning and documentation. The current toolkit is written in C and supports applications that run on IBM-PC's under DOS and UNlX-based workstations under OpenLook and Motif. The toolkit is fully integrated for building scheduling systems that reuse AI knowledge base technology. A typical scheduling scenario and three examples of applications that utilize the reuse toolkit will be briefly described. In addition to the tools themselves, a description of the software evolution and reuse methodology that was used is presented.

Mclean, David↗

NASA NTRS1994

Domain analysis for the reuse of software development experiences

We need to be able to learn from past experiences so we can improve our software processes and products. The Experience Factory is an organizational structure designed to support and encourage the effective reuse of software experiences. This structure consists of two organizations which separates project development concerns from organizational concerns of experience packaging and learning. The experience factory provides the processes and support for analyzing, packaging, and improving the organization's stored experience. The project organization is structured to reuse this stored experience in its development efforts. However, a number of questions arise: What past experiences are relevant? Can they all be used (reused) on our current project? How do we take advantage of what has been learned in other parts of the organization? How do we take advantage of experience in the world-at-large? Can someone else's best practices be used in our organization with confidence? This paper describes approaches to help answer these questions. We propose both quantitative and qualitative approaches for effectively reusing software development experiences.

Basili, V. R.↗

NASA NTRS1994

Application Reuse Library for Software, Requirements, and Guidelines

Better designs are needed for expert systems and other operations automation software, for more reliable, usable and effective human support. A prototype computer-aided Application Reuse Library shows feasibility of supporting concurrent development and improvement of advanced software by users, analysts, software developers, and human-computer interaction experts. Such a library expedites development of quality software, by providing working, documented examples, which support understanding, modification and reuse of requirements as well as code. It explicitly documents and implicitly embodies design guidelines, standards and conventions. The Application Reuse Library provides application modules with Demo-and-Tester elements. Developers and users can evaluate applicability of a library module and test modifications, by running it interactively. Sub-modules provide application code and displays and controls. The library supports software modification and reuse, by providing alternative versions of application and display functionality. Information about human support and display requirements is provided, so that modifications will conform to guidelines. The library supports entry of new application modules from developers throughout an organization. Example library modules include a timer, some buttons and special fonts, and a real-time data interface program. The library prototype is implemented in the object-oriented G2 environment for developing real-time expert systems.

Malin, Jane T.↗

NASA NTRS2000

Practical Considerations of Waste Heat Reuse for a Mars Mission Advanced Life Support System

Energy conservation is a key issue in design optimization of Advanced Life Support Systems (ALSS) for long-term space missions. By considering designs for conservation at the system level, energy saving opportunities arise that would otherwise go unnoticed. This paper builds on a steady-state investigation of system-level waste heat reuse in an ALSS with a low degree of crop growth for a Mars mission. In past studies, such a system has been defined in terms of technology types, hot and cold stream identification and stream energy content. The maximum steady-state potential for power and cooling savings within the system was computed via the Pinch Method. In this paper, several practical issues are considered for achieving a pragmatic estimate of total system savings in terms of equivalent system mass (ESM), rather than savings solely in terms of power and cooling. In this paper, more realistic ESM savings are computed by considering heat transfer inefficiencies during material transfer. An estimate of the steady-state mass, volume and crewtime requirements associated with heat exchange equipment is made by considering heat exchange equipment material type and configuration, stream flow characteristics and associated energy losses during the heat exchange process. Also, previously estimated power and cooling savings are adjusted to reflect the impact of such energy losses. This paper goes one step further than the traditional Pinch Method of considering waste heat reuse in heat exchangers to include ESM savings that occur with direct reuse of a stream. For example, rather than exchanging heat between crop growth lamp cooling air and air going to a clothes dryer, air used to cool crop lamps might be reused directly for clothes drying purposes. When thermodynamically feasible, such an approach may increase ESM savings by minimizing the mass, volume and crewtime requirements associated with stream routing equipment.

Levri, Julie↗

NASA NTRS2010

Progress Towards a NASA Earth Science Reuse Enablement System (RES)

A Reuse Enablement System (RES) allows developers of Earth science software to contribute software for reuse by others and.for users to find, select, and obtain software for reuse in their own systems. This paper describes work that the X4S,4 Earth Science Data Systems (ESDS) Software Reuse Working Group has completed to date in the development of an RES for NASA.

Marshall, James J.↗

NASA NTRSDate not supplied

Core Stage TVC Systems Engineering Challenges in Reusing Heritage Hardware

The Space Launch System (SLS) Core Stage (CS) Thrust Vector Control (TVC) system is comprised of 8 mechanical feedback Shuttle heritage Type III TVC actuators and four RS-25 engines, each attached to a Shuttle heritage gimbal block/bearing. Two actuators are used to move each engine in two planes perpendicular to one another (i.e., pitch and yaw). The TVC system design leverages hardware from the Space Shuttle program as well as new hardware designed specifically for the Core Stage. The Space Shuttle heritage hardware directly reused on SLS includes the Orbiter TVC hydraulic servo-actuators (with two slight design modifications), the Orbiter hydraulic circulation pumps, the Orbiter gimbal block/bearing, and the Solid Rocket Booster hydraulic pumps. The Core Auxiliary Power Unit (CAPU) is derived from the Orbiter Auxiliary Power Unit (APU). The Orbiter and Solid Rocket Booster APU turbines are powered by hot gas produced by catalyzed hydrazine decomposition. On the SLS Core Stage, the CAPU turbine is spun using cold gas tapped-off from the RS-25 to CS liquid hydrogen autogenous pressurization line. While direct reuse or slight modification of existing hardware may seem to be a triple-win for a program in cost, schedule, and technical risk mitigation, those benefits can only be realized when its degree of application in a new system is carefully and thoughtfully managed. The heritage hardware reuse should be prescribed within the heritage design capability and reuse environments must lie within the envelope of heritage qualification testing. Despite the significant test and flight experience of the Shuttle heritage hardware components, successful integration with the newly designed CS TVC components and incorporation into the stage design proved to be a challenge which required re-qualification of the heritage hardware as well as thorough integrated testing to support flight certification. Examples of the challenges that were overcome include: re-qualifying heritage hardware to survive new shock and vibration environments, certifying performance of extensively modified heritage hardware, regenerating design insight due to lack of available heritage vendor data, showing compliance to modern structural design standards, translation of heritage requirements for analog avionics to modern digital avionics, and interfacing heritage mechanical hardware with newly designed avionics. This paper is the second installment in a seven-paper series surveying the design, engineering, test validation, and flight performance of the Core Stage Thrust Vector Control system. This paper will discuss several engineering challenges encountered during the development process for SLS CS TVC and how they were successfully overcome to reach flight readiness.

Thrust Vector Control↗

NASA NTRSDate not supplied

Space Launch System: Core Stage Thrust Vector Control Systems Engineering Challenges in Reusing Heritage Hardware

The Space Launch System (SLS) Core Stage (CS) Thrust Vector Control (TVC) system is comprised of 8 mechanical feedback Shuttle heritage Type III TVC actuators and four RS-25 engines, each attached to a Shuttle heritage gimbal block/bearing. Two actuators are used to move each engine in two planes perpendicular to one another (i.e., pitch and yaw). The TVC system design leverages hardware from the Space Shuttle program as well as new hardware designed specifically for the Core Stage. The Space Shuttle heritage hardware directly reused on SLS includes the Orbiter TVC hydraulic servo-actuators (with two slight design modifications), the Orbiter hydraulic circulation pumps, the Orbiter gimbal block/bearing, and the Solid Rocket Booster hydraulic pumps. The Core Auxiliary Power Unit (CAPU) is derived from the Orbiter Auxiliary Power Unit (APU). The Orbiter and Solid Rocket Booster APU turbines are powered by hot gas produced by catalyzed hydrazine decomposition. On the SLS Core Stage, the CAPU turbine is spun using cold gas tapped-off from the RS-25 to CS liquid hydrogen autogenous pressurization line. While direct reuse or slight modification of existing hardware may seem to be a triple-win for a program in cost, schedule, and technical risk mitigation, those benefits can only be realized when its degree of application in a new system is carefully and thoughtfully managed. The heritage hardware reuse should be prescribed within the heritage design capability and reuse environments must lie within the envelope of heritage qualification testing. Despite the significant test and flight experience of the Shuttle heritage hardware components, successful integration with the newly designed CS TVC components and incorporation into the stage design proved to be a challenge which required re-qualification of the heritage hardware as well as thorough integrated testing to support flight certification. Examples of the challenges that were overcome include: re-qualifying heritage hardware to survive new shock and vibration environments, certifying performance of extensively modified heritage hardware, regenerating design insight due to lack of available heritage vendor data, showing compliance to modern structural design standards, translation of heritage requirements for analog avionics to modern digital avionics, and interfacing heritage mechanical hardware with newly designed avionics. This paper is the second installment in a seven-paper series surveying the design, engineering, test validation, and flight performance of the Core Stage Thrust Vector Control system. This paper will discuss several engineering challenges encountered during the development process for SLS CS TVC and how they were successfully overcome to reach flight readiness.

Thrust Vector Control↗

NASA NTRS1975

Processing of combined domestic bath and laundry waste waters for reuse as commode flushing water

An experimental investigation of processes and system configurations for reclaiming combined bath and laundry waste waters for reuse as commode flush water was conducted. A 90-min recycle flow was effective in removing particulates and in improving other physical characteristics to the extent that the filtered water was subjectively acceptable for reuse. The addition of a charcoal filter resulted in noticeable improvements in color, turbidity, and suds elimination. Heating and chlorination of the waste waters were investigated for reducing total organism counts and eliminating coliform organisms. A temperature of 335.9 K (145 F) for 30 min and chlorine concentrations of 20 mg/l in the collection tank followed by 10 mg/l in the storage tank were determined to be adequate for this purpose. Water volume relationships and energy-use rates for the waste water reuse systems are also discussed.

Hypes, W. D.↗

NASA NTRS1983

Four-dimensional modulation and coding: An alternate to frequency-reuse

Four dimensional modulation as a means of improving communication efficiency on the band-limited Gaussian channel, with the four dimensions of signal space constituted by phase orthogonal carriers (cos omega sub c t and sin omega sub c t) simultaneously on space orthogonal electromagnetic waves are discussed. "Frequency reuse' techniques use such polarization orthogonality to reuse the same frequency slot, but the modulation is not treated as four dimensional, rather a product of two-d modulations, e.g., QPSK. It is well known that, higher dimensionality signalling affords possible improvements in the power bandwidth sense. Four-D modulations based upon subsets of lattice-packings in four-D, which afford simplification of encoding and decoding are described. Sets of up to 1024 signals are constructed in four-D, providing a (Nyquist) spectral efficiency of up to 10 bps/Hz. Energy gains over the reuse technique are in the one to three dB range t equal bandwidth.

Wilson, S. G.↗

NASA NTRS1984

Four-dimensional modulation and coding - An alternate to frequency-reuse

Four dimensional modulation as a means of improving communication efficiency on the band-limited Gaussian channel, with the four dimensions of signal space constituted by phase orthogonal carriers (cos omega sub c t and sin omega sub c t) simultaneously on space orthogonal electromagnetic waves are discussed. 'Frequency reuse' techniques use such polarization orthogonality to reuse the same frequency slot, but the modulation is not treated as four dimensional, rather a product of two-D modulations, e.g., QPSK. It is well known that, higher dimensionality signalling affords possible improvements in the power bandwidth sense. Four-D modulations based upon subsets of lattice-packings in four-D, which afford simplification of encoding and decoding are described. Sets of up to 1024 signals are constructed in four-D, providing a (Nyquist) spectral efficiency of up to 10 bps/Hz. Energy gains over the reuse technique are in the one to three dB range t equal bandwidth.

Wilson, S. G.↗

NASA NTRS1986

Certification of Ada parts for reuse

One of the claims made by proponents of Ada is that Ada software is highly reusable. The fact that specifications are compiled and accessible would make reusability seem easily achievable. However, specifications give only a limited amount of information about a package; moreover, a specification cannot help determine whether a package worked, or how well it worked. This problem has led to the concept of certifying Ada parts for reuse; that is, determining the worthiness of a part as a reusable component. Issues that are critical to reuse are addressed: the characterization of part performance, design for reuse, and correct utilization of parts. Current areas of study beneficial in the development of a certification process are then addressed.

Hansen, Gregory A.↗