Search NASA⌕ Search

SEARCH · Search NASA

Results for “Team 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.

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

At least 271 records · Page 15

Biomaterials Out of Thin Air: In Situ, On-Demand Printing of Advanced Biocomposites: A New Materials Design and Production Technique Using 3D-Printed Arrays of Bioengineered Cells

We have completed the proof of concept described in our Phase I proposal, a two-material array of nonstructural proteins. We created an implementation of each step in our technology concept and demonstrated its critical functionality. The biological chassis and printing hardware we created as part of this work can be re-used for future work by inserting a material coding region upstream of the fluorescent tag. Overall, we showed that our technology concept is sound. The mission benefit analyses, as described in our Phase I proposal, are complete and contained in this report. These calculations show that our technology can save hundreds of kilograms of upmass for a potential planetary human habit construction mission: the mass per habitat module can be reduced by approximately one third if the biomaterials are manufactured on Earth and included in the mission upmass, and the full 240 kg per module can be saved if the materials are derived entirely from in situ resources. Mass savings between these two extremes is expected for an actual mission, depending on the level of in situ resource extraction technology. We have shown that continued advancement of this technology concept for use in a space mission environment is justified. Our survey of future development pathways proved extremely informative in light of the lessons learned from our proof of concept work and mission scenario analyses. For example, we were able for the first time to distinguish between the levels of functionality provided by production of structural proteins, other polymers such as polysaccharides, and true organic-inorganic composites such as bone and mineralized shell. This new information represents a significant advance in formulating specific applications, and key enabling technologies, for our proposed concept. We surveyed potential collaborations with other projects and synergies with enabling technologies that are developing. We have received requests for collaboration from other institutions, including labs at Stanford University and Drexel University. We have also received visits from industry, including Organovo, a tissue engineering company, and Autodesk, a major 3D and materials design software company. Finally, we have been in touch with the team behind the 2013 NIAC Phase ll 'Super Ball Bot-Structures for Planetary Landing and Exploration' and are planning to develop our biomaterial printing technology with the goal of enabling tensegrity-based rovers such as theirs to use lighter, more robust materials. A smooth transition from TRL 2 to TRL 3 assumes that the implementations of the technology concept which demonstrate critical functionality are also pathways for future development; while this is the case for most hardware or software projects, the multidisciplinary nature of our project, particularly the biological aspect of it, means that this is not always true. For example, as part of this work we showed that although there are large number of known genetic parts that correspond to non-structural materials, this is not true for sequences for structural organic proteins, let alone biominerals. These realizations allowed us to further subdivide our concept into more detailed development areas, some of which are clearly established at TRL 3, others of which were newly identified sub-technologies moved from TRL 1 to TRL 2. Similarly, although a single feasibility /benefit analysis is sufficient for advancement from TRL 2 to TRL 3, not all potential benefits to a technology concept as broad in scope as ours are apparent at TRL 2. Both our future pathways survey and our proof of concept work highlighted that the true mass savings potential of our technology concept cannot be quantified without modification of existing materials modelling tools to take into account the possibility of positional materials properties customization. Therefore, we have simultaneously both advanced one potential set of applications of our technology concept from TRL 2 to TRL 3 and also identified a previously unknown set of applications and advanced it from TRL 1 to TRL 2. Overall, we have moved the original formulation of our concept forward from TRL 2 to TRL 3, and the expanded formulation of it presented in this document has been advanced from a combination of TRL 1 and early 1RL 2 to an overall late TRL 2. We have also identified the key areas necessary for both short-term and long-term advancement, and made recommendations for specific future work in the most promising directions. With future work on a 1-2 year timeframe to continue advancement to overall TRL 3, we will be well positioned to begin work on a specific space mission technology insertion path.

Biology↗

Apparel Manufacture

Marshall Space Flight Center teamed with the University of Alabama in Huntsville (UAH) in 1989 on a program involving development of advanced simulation software. Concurrently, the State of Alabama chartered UAH to conduct a technology advancement program in support of the state's apparel manufacturers. In 1992, under contract to Marshall, UAH developed an apparel-specific software package that allows manufacturers to design and analyze modules without making an actual investment -- it functions on ordinary PC equipment. By 1995, Marshall had responded to requests for the package from more than 400 companies in 36 states; some of which reported savings up to $2 million. The National Garment Company of Missouri, for example, uses the system to design and balance a modular line before committing to expensive hardware; for setting up sewing lines; and for determining the composition of a new team.

Source record↗

RAPIDS2: A SciDAC Institute for Computer Science, Data, and Artificial Intelligence (University of Delaware)

This report summarizes the activities, technical accomplishments, and outcomes of the RAPIDS2 Institute project at the University of Delaware (UD). The RAPIDS2 Institute was a large multi-institution project with the objective of assisting SciDAC and Office of Science application teams in the use of DOE supercomputing resources to achieve scientific breakthroughs. The UD team contributed to this effort through work on formal software verification. This thrust aims to reduce software developer time and effort, especially regarding debugging and testing, and to increase confidence in the correctness of the results computed by the software.

97 MATHEMATICS AND COMPUTING↗

HRMA calibration handbook: EKC gravity compensated XRCF models

This document, consisting of hardcopy printout of explanatory text, figures, and tables, represents one incarnation of the AXAF high resolution mirror assembly (HRMA) Calibration Handbook. However, as we have envisioned it, the handbook also consists of electronic versions of this hardcopy printout (in the form of postscript files), the individual scripts which produced the various figures and the associated input data, the model raytrace files, and all scripts, parameter files, and input data necessary to generate the raytraces. These data are all available electronically as either ASCII or FITS files. The handbook is intended to be a living document and will be updated as new information and/or fabrication data on the HRMA are obtained, or when the need for additional results are indicated. The SAO Mission Support Team (MST) is developing a high fidelity HRMA model, consisting of analytical and numerical calculations, computer software, and databases of fundamental physical constants, laboratory measurements, configuration data, finite element models, AXAF assembly data, and so on. This model serves as the basis for the simulations presented in the handbook. The 'core' of the model is the raytrace package OSAC, which we have substantially modified and now refer to as SAOsac. One major structural modification to the software has been to utilize the UNIX binary pipe data transport mechanism for passing rays between program modules. This change has made it possible to simulate rays which are distributed randomly over the entrance aperture of the telescope. It has also resulted in a highly efficient system for tracing large numbers of rays. In one application to date (the analysis of VETA-I ring focus data) we have employed 2 x 10(exp 7) rays, a substantial improvement over the limit of 1 x 10(exp 4) rays in the original OSAC module. A second major modification is the manner in which SAOsac incorporates low spatial frequency surface errors into the geometric raytrace. The original OSAC included the ability to use Legendre-Fourier polynomials to describe deviations from the basic optical prescription. To this we have added bicubic splines to address a deficiency in the handling of the sharper deformations in the areas of mirror support pads. SAO has developed software (TRANS-FIT) to translate the most common finite element analysis models into these forms for incorporation into the raytrace program.

Tananbaum, H. D.↗

Finite Element Analysis and Test Correlation of a 10-Meter Inflation-Deployed Solar Sail

Under the direction of the NASA In-Space Propulsion Technology Office, the team of L Garde, NASA Jet Propulsion Laboratory, Ball Aerospace, and NASA Langley Research Center has been developing a scalable solar sail configuration to address NASA's future space propulsion needs. Prior to a flight experiment of a full-scale solar sail, a comprehensive phased test plan is currently being implemented to advance the technology readiness level of the solar sail design. These tests consist of solar sail component, subsystem, and sub-scale system ground tests that simulate the vacuum and thermal conditions of the space environment. Recently, two solar sail test articles, a 7.4-m beam assembly subsystem test article and a 10-m four-quadrant solar sail system test article, were tested in vacuum conditions with a gravity-offload system to mitigate the effects of gravity. This paper presents the structural analyses simulating the ground tests and the correlation of the analyses with the test results. For programmatic risk reduction, a two-prong analysis approach was undertaken in which two separate teams independently developed computational models of the solar sail test articles using the finite element analysis software packages: NEiNastran and ABAQUS. This paper compares the pre-test and post-test analysis predictions from both software packages with the test data including load-deflection curves from static load tests, and vibration frequencies and mode shapes from vibration tests. The analysis predictions were in reasonable agreement with the test data. Factors that precluded better correlation of the analyses and the tests were uncertainties in the material properties, test conditions, and modeling assumptions used in the analyses.

Sleight, David W.↗

Structural Analysis of an Inflation-Deployed Solar Sail With Experimental Validation

Under the direction of the NASA In-Space Propulsion Technology Office, the team of L Garde, NASA Jet Propulsion Laboratory, Ball Aerospace, and NASA Langley Research Center has been developing a scalable solar sail configuration to address NASA s future space propulsion needs. Prior to a flight experiment of a full-scale solar sail, a comprehensive phased test plan is currently being implemented to advance the technology readiness level of the solar sail design. These tests consist of solar sail component, subsystem, and sub-scale system ground tests that simulate the vacuum and thermal conditions of the space environment. Recently, two solar sail test articles, a 7.4-m beam assembly subsystem test article and a 10-m four-quadrant solar sail system test article, were tested in vacuum conditions with a gravity-offload system to mitigate the effects of gravity. This paper presents the structural analyses simulating the ground tests and the correlation of the analyses with the test results. For programmatic risk reduction, a two-prong analysis approach was undertaken in which two separate teams independently developed computational models of the solar sail test articles using the finite element analysis software packages: NEiNastran and ABAQUS. This paper compares the pre-test and post-test analysis predictions from both software packages with the test data including load-deflection curves from static load tests, and vibration frequencies and mode shapes from structural dynamics tests. The analysis predictions were in reasonable agreement with the test data. Factors that precluded better correlation of the analyses and the tests were uncertainties in the material properties, test conditions, and modeling assumptions used in the analyses.

Sleight, David W.↗

Fully Employing Software Inspections Data

Software inspections provide a proven approach to quality assurance for software products of all kinds, including requirements, design, code, test plans, among others. Common to all inspections is the aim of finding and fixing defects as early as possible, and thereby providing cost savings by minimizing the amount of rework necessary later in the lifecycle. Measurement data, such as the number and type of found defects and the effort spent by the inspection team, provide not only direct feedback about the software product to the project team but are also valuable for process improvement activities. In this paper, we discuss NASA's use of software inspections and the rich set of data that has resulted. In particular, we present results from analysis of inspection data that illustrate the benefits of fully utilizing that data for process improvement at several levels. Examining such data across multiple inspections or projects allows team members to monitor and trigger cross project improvements. Such improvements may focus on the software development processes of the whole organization as well as improvements to the applied inspection process itself.

Shull, Forrest↗

Big Software for SmallSats: Adapting cFS to CubeSat Missions

Expanding capabilities and mission objectives for SmallSats and CubeSats is driving the need for reliable, reusable, and robust flight software. While missions are becoming more complicated and the scientific goals more ambitious, the level of acceptable risk has decreased. Design challenges are further compounded by budget and schedule constraints that have not kept pace. NASA's Core Flight Software System (cFS) is an open source solution which enables teams to build flagship satellite level flight software within a CubeSat schedule and budget. NASA originally developed cFS to reduce mission and schedule risk for flagship satellite missions by increasing code reuse and reliability. The Lunar Reconnaissance Orbiter, which launched in 2009, was the first of a growing list of Class B rated missions to use cFS.

Flight Software↗

Clinical Decision Support For Exploration Space Flight: Software Augmentation To Enhance Progressively Earth-Independent Medical Operations

This panel identifies the challenges of supporting medical events in deep space using integrated systems software to augment existing capabilities during increasingly Earth-independent missions where an asynchronous communication environment becomes routine. An interdisciplinary team of software designers, physicians, human factors engineers, and computational modelers applied their respective expertise to develop a roadmap for supporting the crew making medical decisions in more autonomous fashion with time-delayed ground support. The first presentation describes predictive modeling implemented to assist medical system design and address risk reduction using robust clinical decision support software. The second presentation details how operational and environmental challenges guide assumptions and, in turn, by what means requirements for medical decision-making in deep space are derived. The third presentation describes and defines the skills and capabilities an exploration spaceflight medical officer will need to perform effectively during extended-duration spaceflight missions. The fourth presentation covers the potential models and function of the software element for supporting clinical decisions. The final presentation covers how these elements may work together with ground support to provide comprehensive care despite deep space travel's extreme challenges and limitations.

Dana Levin↗

Conducting Feasibility Studies in a Virtual World: Lessons Learned and Emerging Best Practices from the NASA DEVELOP Program

In response to new workplace realities, the NASA DEVELOP National Program pivoted from co-locating students, emerging professionals, and science advisors to bringing together virtual teams from across the United States. In its spring 2020 term, rapidly evolving circumstances required an ad-hoc roll-out of a virtual approach to complete the spring projects. Based on the experience from the spring term and a few weeks of planning, DEVELOP then conducted a fully virtual summer term with features such as 1) online collaboration tools, 2) virtual machines for analysis, and 3) streamed training offerings, including DEVELOP’s first ever program-wide Software Carpentry workshop. This full term of bringing together remote actors to select, build, and manage teams brought many challenges. Summer feedback has influenced planning for the fall 2020 term and process improvement is ongoing. This presentation will highlight lessons learned throughout this period of rapid change. Feedback from spring and summer terms and the Software Carpentry workshop will be summarized. Beyond participant impacts, there will also be discussion of effects on project results and partner experience. Final takeaways will focus on best practices that have been distilled for virtually-conducted feasibility studies.

NASA DEVELOP↗

Using the cFS Command and Data Dictionary (CCDD) to Automate Software Development on Habulous

Final paper is attached. The NASA developed Core Flight System (cFS) is a reusable software architecture that has been used on multiple spaceflight missions. By using this framework, missions are able to reuse code from other missions, as well as leverage deployment onto similar computer architectures (i.e. not "reinvent the wheel" on each new mission). The success in the cFS concept can be seen in the large number of projects using cFS at FSW-2018. The Habulous project is an Earth-based testbed, used for hardware and software that may one day be used on a future space habitat unit, with many participating groups from various NASA centers and aerospace organizations around the country. The distributed nature of the various teams mean that defining (and following) an interface definition is critical on the project. Additionally, since various groups use various types of computer hardware (32/64-bit, big/little endian, Linux/VxWorks/Windows) many additional complications exist in interfacing all the various components into a final integrated system. cFS is used on the majority the flight software (FSW) in running in Habulous. But some subsystems have elected to not use cFS, and use a software bridge (called SBN_lib) to interact with the other cFS nodes in Habulous. In order to most efficiently develop the FSW, a central database is used to define and store each message sent by cFS. A Command and Data Dictionary (CDD) is something nearly universal on spacecraft, but as a team we worked to develop the CDD before the SW development was complete, and not treat it like "as built" documentation. To manage the CDD, the cFS Command and Data Dictionary (CCDD) tool was chosen (available from NASA as open source software). The CCDD tool has successfully been used to automate/autocode a large amount of software used on Habulous, as we are hoping to use it to define even more items in the future (time-triggered Ethernet (TTE) network maps, CPU scheduling). Additionally, Habulous has been exploring the use of cFS on wildly heterogeneous CPUs, and how to coordinate all those various machines using/extending the software bus – network (SBN) application in cFS, as well as TTE to coordinate message passing between various synchronized machines. The major topics to be covered in the presentation are: (1) Updating to the CCSDS_v2 extended headers (and using CPU# as subsystem ID). (2) Managing all the message identification numbers for each cFS message sent/received on any of the various CPUs. (3) Using the CCDD information to automatically generate the C-header files that define the structure for all software bus (SB) commands/telemetry messages. (4) Using the CCDD to automatically generate XML Telemetry and Command Exchange (XTCE) files, which streams display production/integration/testing in a web based display architecture (5) Extending/customizing SBN to pass messages among computers on multiple networks. (6) Using "Protobetter" inside SBN to manage different endian-ness/architectures. (7) Using SBN_lib to allow non-cFS node to communicate with cFS nodes. (8) Developing TTE network and schedule tables for all the various CPUs to use.

Hirsh, Robert L.↗

NASA PC software evaluation project

The USL NASA PC software evaluation project is intended to provide a structured framework for facilitating the development of quality NASA PC software products. The project will assist NASA PC development staff to understand the characteristics and functions of NASA PC software products. Based on the results of the project teams' evaluations and recommendations, users can judge the reliability, usability, acceptability, maintainability and customizability of all the PC software products. The objective here is to provide initial, high-level specifications and guidelines for NASA PC software evaluation. The primary tasks to be addressed in this project are as follows: to gain a strong understanding of what software evaluation entails and how to organize a structured software evaluation process; to define a structured methodology for conducting the software evaluation process; to develop a set of PC software evaluation criteria and evaluation rating scales; and to conduct PC software evaluations in accordance with the identified methodology. Communication Packages, Network System Software, Graphics Support Software, Environment Management Software, General Utilities. This report represents one of the 72 attachment reports to the University of Southwestern Louisiana's Final Report on NASA Grant NGT-19-010-900. Accordingly, appropriate care should be taken in using this report out of context of the full Final Report.

Dominick, Wayne D.↗

Transforming Our SMEX Organization by Way of Innovation, Standardization, and Automation

NASA's Small Explorer (SMEX) Flight Operations Team (FOT) is currently tackling the challenge of supporting ground operations for several satellites that have surpassed their designed lifetime and have a dwindling budget. At Goddard Space Flight Center (GSFC), these missions are presently being reengineered into a fleet-oriented ground system. When complete, this ground system will provide command and control of four SMEX missions, and will demonstrate fleet automation and control concepts as a pathfinder for additional mission integrations. A goal of this reengineering effort is to demonstrate new ground-system technologies that show promise of supporting longer mission lifecycles and simplifying component integration. In pursuit of this goal, the SMEX organization has had to examine standardization, innovation, and automation. A core technology being demonstrated in this effort is the GSFC Mission Services Evolution Center (GMSEC) architecture. The GMSEC architecture focuses on providing standard interfaces for ground system applications to promote application interoperability. Building around commercial Message Oriented Middleware and providing a common messaging standard allows GMSEC to provide the capabilities necessary to support integration of new software components into existing missions and increase the level of interaction within the system. For SMS, GMSEC has become the technology platform to transform flight operations with the innovation and automation necessary to reduce operational costs. The automation technologies supported in SMEX are built upon capabilities provided by the GMSEC architecture that allows the FOT to further reduce the involvement of the console, operator. Initially, SMEX is automating only routine operations, such as safety and health monitoring, basic commanding, and system recovery. The operational concepts being developed here will reduce the need for staffed passes and are a necessity for future fleet management. As this project continues to evolve, additional innovations beyond GMSEC and automation have, and will continue to be developed. The team developed techniques for migrating ground systems of existing on-orbit assets. The tools necessary to monitor and control software failures were integrated and tailored for operational environments. All this was done with a focus of extending fleet operations to mission beyond SMU. The result of this work is the foundation for a broader fleet-capable ground system that will include several missions supported by the Space Science Mission Operations Project.

Madden, Maureen↗

Workforce for the Future Development of Space Access Vehicles

The development of advanced vehicles that will travel between planetary surfaces with atmospheres and space requires the availability of experimental and computational capabilities that accomplish the research leading to new technologies and the development, test, and evaluation (RDT&E) of new flight systems. The United States is at risk of not having the required RDT&E workforce – qualified and in sufficient numbers – in place and ready to meet the future market’s commercial and defense needs. Systemic challenges include uncertain Federal budgets that limit and interrupt government research and development, the projectized nature of new space access systems that drive boom/bust cycles, an aging aerospace workforce (compounded by a mid-age demographic gap), limited to declining investment in sustaining and advancing experimental and computational tools infrastructure, lack of standards for sharing (and leveraging) data, dramatically changing technologies, changing social norms, and potentially large increases in commercial market needs. Flight systems have mission-based trajectories to and from space and designers must ensure risk is properly assessed across the entire trajectory. Thus, physics questions must be answered at each stage of flight, which requires a suite of experimental and computational tools. The RDT&E workforce utilizing these tools include subject matter experts from the producers, interested in acquiring data and information on the product, and from the capabilities being utilized, interested in addressing the product customer’s needs (providing robust data collection techniques, data quality, timeliness – available when needed, efficient with cost management, and teaming on data analysis). This requires a range of skills – in addition to aerospace, other engineers, and software developers, a highly trained and certified craft and technician workforce is critical to future success. This paper will present a human resources construct that addresses the system of needs for people – including, but more than just technical skills and an application of that construct in the hypersonic Test and Evaluation (T&E) community. This is part of a larger AIAA effort to document challenges and associated best practices for the aerospace RDT&E workforce.

Steven C Dunn↗

DADiSP processing guide

A guide for DADiSP software, intended for use by the Lambda Point Experiment (LPE) Team during and after the United States Microgravity Payload (USMP)-1 mission, is presented. DADiSP is a Data Analysis and Display Software developed and marketed by DSP Development Corporation, Cambridge, Massachusetts. This guide is intended to be used in addition to the DADiSP Worksheet User Manual and Reference Manual which are supplied by the company with the software. Technical support for DADiSP is available from DSP at (617) 577-1133. Access to DADiSP on Acceleration Characterization and Analysis Project (ACAP) EGSE is being provided to the LPE team during USMP-1 for off-line processing of SAMS data.

Rogers, Melissa J. B.↗

The Development of Two Science Investigator-led Processing Systems (SIPS) for NASA's Earth Observation System (EOS)

In 2001, NASA Goddard Space Flight Center's Laboratory for Terrestrial Physics started the construction of a science Investigator-led Processing System (SIPS) for processing data from the Ozone Monitoring Instrument (OMI) which will launch on the Aura platform in mid 2004. The Ozone Monitoring Instrument (OMI) is a contribution of the Netherlands Agency for Aerospace Programs (NIVR) in collaboration with the Finnish Meteorological Institute (FMI) to the Earth Observing System (EOS) Aura mission. It will continue the Total Ozone Monitoring System (TOMS) record for total ozone and other atmospheric parameters related to ozone chemistry and climate. OMI measurements will be highly synergistic with the other instruments on the EOS Aura platform. The LTP previously developed the Moderate Resolution Imaging Spectrometer (MODIS) Data Processing System (MODAPS), which has been in full operations since the launches of the Terra and Aqua spacecrafts in December, 1999 and May, 2002 respectively. During that time, it has continually evolved to better support the needs of the MODIS team. We now run multiple instances of the system managing faster than real time reprocessings of the data as well as continuing forward processing. The new OMI Data Processing System (OMIDAPS) was adapted from the MODAPS. It will ingest raw data from the satellite ground station and process it to produce calibrated, geolocated higher level data products. These data products will be transmitted to the Goddard Distributed Active Archive Center (GDAAC) instance of the Earth Observing System (EOS) Data and Information System (EOSDIS) for long term archive and distribution to the public. The OMIDAPS will also provide data distribution to the OMI Science Team for quality assessment, algorithm improvement, calibration, etc. We have taken advantage of lessons learned from the MODIS experience and software already developed for MODIS. We made some changes in the hardware system organization, database and software to adapt the system for OMI. We replaced the fundamental database system, Sybase, with an Open Source RDBMS called PostgreSQL, and based the entire OMIDAPS on a cluster of Linux based commodity computers rather than the large SGI servers that MODAPS uses. Rather than relying on a central I/O server host, the new system distributes its data archive among multiple server hosts in the cluster. OMI is also customizing the graphical user interfaces and reporting structure to more closely meet the needs of the OMI Science Team. Prior to 2003, simulated OMI data and the science algorithms were not ready for production testing. We initially constructed a prototype system and tested using a 25 year dataset of Total Ozone Mapping Spectrometer (TOMS) and Solar Backscatter Ultraviolet Instrument (SBUV) data. This prototype system provided a platform to support the adaptation of the algorithms for OMI, and provided reprocessing of the historical data aiding in its analysis. In a recent reanalysis of the TOMS data, the OMIDAPS processed 108,000 full orbits of data through 4 processing steps per orbit, producing about 800,000 files (400 GiB) of level 2 and greater data files. More recently we have installed two instances of the OMIDAPS for integration and testing of OM1 science processes as they get delivered from the Science Team. A Test instance of the OMIDAPS has also supported a series of "Interface Confidence Tests" (ICTs) and End-to-End Ground System tests to ensure the launch readiness of the system. This paper will discuss the high-level hardware, software, and database organization of the OMIDAPS and how it builds on the MODAPS heritage system. It will also provide an overview of the testing and implementation of the production OMIDAPS.

Tilmes, Curt↗

A recent Cleanroom success story: The Redwing project

Redwing is the largest completed Cleanroom software engineering project in IBM, both in terms of lines of code and project staffing. The product provides a decision-support facility that utilizes artificial intelligence (AI) technology for predicting and preventing complex operating problems in an MVS environment. The project used the Cleanroom process for development and realized a defect rate of 2.6 errors/KLOC, measured from first execution. This represents the total amount of errors that were found in testing and installation at three field test sites. Development productivity was 486 LOC/PM, which included all development labor expended in design specification through completion of incremental testing. In short, the Redwing team produced a complex systems software product with an extraordinarily low error rate, while maintaining high productivity. All of this was accomplished by a project team using Cleanroom for the first time. An 'introductory implementation' of Cleanroom was defined and used on Redwing. This paper describes the quality and productivity results, the Redwing project, and how Cleanroom was implemented.

Hausler, Philip A.↗

Long Term Manipulations of Intact Microbial Mat Communities in a Greenhouse Collaboratory: Simulating Earth's Present and Past Field Environments

Photosynthetic microbial mat communities were obtained from marine hypersaline saltern ponds, maintained in a greenhouse facility, and examined for the effects of salinity variations. Because these microbial mats are considered to be useful analogs of equivalent ancient marine communities, they offer insights about evolutionary events during the greater than 3 billion year time interval wherein mats co-evolved with Earth's geosphere and atmosphere. Although photosynthetic mats can be highly dynamic and exhibit extremely high activity, the mats in the present study have been maintained for more than one year with relatively minor changes. The major groups of microorganisms, as assayed using microscopic, genetic, and biomarker methodologies, are essentially the same as those in the original field samples. Field and greenhouse mats were similar with respect to rates of exchange of oxygen and dissolved inorganic carbon across the mat-water interface, both during the day and at night. Field and greenhouse mats exhibited similar rates of efflux of methane and hydrogen. Manipulations of salinity in the water overlying the mats produced changes in the community that strongly resemble those observed in the field. A collaboratory testbed and an array of automated features are being developed to support remote scientific experimentation with the assistance of intelligent software agents. This facility will permit teams of investigators to explore ancient environmental conditions that are rare or absent today but might have influenced the early evolution of these photosynthetic ecosystems.

Bebout, Brad↗