Search NASA⌕ Search

SEARCH · Search NASA

Results for “Project Life Cycle”

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
All sourcesNASA NTRSDOE OSTI
NASA NTRS2008

Guidance and Control Software Project Data - Volume 1: Planning Documents

The Guidance and Control Software (GCS) project was the last in a series of software reliability studies conducted at Langley Research Center between 1977 and 1994. The technical results of the GCS project were recorded after the experiment was completed. Some of the support documentation produced as part of the experiment, however, is serving an unexpected role far beyond its original project context. Some of the software used as part of the GCS project was developed to conform to the RTCA/DO-178B software standard, "Software Considerations in Airborne Systems and Equipment Certification," used in the civil aviation industry. That standard requires extensive documentation throughout the software development life cycle, including plans, software requirements, design and source code, verification cases and results, and configuration management and quality control data. The project documentation that includes this information is open for public scrutiny without the legal or safety implications associated with comparable data from an avionics manufacturer. This public availability has afforded an opportunity to use the GCS project documents for DO-178B training. This report provides a brief overview of the GCS project, describes the 4-volume set of documents and the role they are playing in training, and includes the planning documents from the GCS project. Volume 1 contains five appendices: A. Plan for Software Aspects of Certification for the Guidance and Control Software Project; B. Software Development Standards for the Guidance and Control Software Project; C. Software Verification Plan for the Guidance and Control Software Project; D. Software Configuration Management Plan for the Guidance and Control Software Project; and E. Software Quality Assurance Activities.

Hayhurst, Kelly J.↗
NASA NTRS2008

Guidance and Control Software Project Data - Volume 3: Verification Documents

The Guidance and Control Software (GCS) project was the last in a series of software reliability studies conducted at Langley Research Center between 1977 and 1994. The technical results of the GCS project were recorded after the experiment was completed. Some of the support documentation produced as part of the experiment, however, is serving an unexpected role far beyond its original project context. Some of the software used as part of the GCS project was developed to conform to the RTCA/DO-178B software standard, "Software Considerations in Airborne Systems and Equipment Certification," used in the civil aviation industry. That standard requires extensive documentation throughout the software development life cycle, including plans, software requirements, design and source code, verification cases and results, and configuration management and quality control data. The project documentation that includes this information is open for public scrutiny without the legal or safety implications associated with comparable data from an avionics manufacturer. This public availability has afforded an opportunity to use the GCS project documents for DO-178B training. This report provides a brief overview of the GCS project, describes the 4-volume set of documents and the role they are playing in training, and includes the verification documents from the GCS project. Volume 3 contains four appendices: A. Software Verification Cases and Procedures for the Guidance and Control Software Project; B. Software Verification Results for the Pluto Implementation of the Guidance and Control Software; C. Review Records for the Pluto Implementation of the Guidance and Control Software; and D. Test Results Logs for the Pluto Implementation of the Guidance and Control Software.

Hayhurst, Kelly J.↗
NASA NTRS2008

Guidance and Control Software Project Data - Volume 4: Configuration Management and Quality Assurance Documents

The Guidance and Control Software (GCS) project was the last in a series of software reliability studies conducted at Langley Research Center between 1977 and 1994. The technical results of the GCS project were recorded after the experiment was completed. Some of the support documentation produced as part of the experiment, however, is serving an unexpected role far beyond its original project context. Some of the software used as part of the GCS project was developed to conform to the RTCA/DO-178B software standard, "Software Considerations in Airborne Systems and Equipment Certification," used in the civil aviation industry. That standard requires extensive documentation throughout the software development life cycle, including plans, software requirements, design and source code, verification cases and results, and configuration management and quality control data. The project documentation that includes this information is open for public scrutiny without the legal or safety implications associated with comparable data from an avionics manufacturer. This public availability has afforded an opportunity to use the GCS project documents for DO-178B training. This report provides a brief overview of the GCS project, describes the 4-volume set of documents and the role they are playing in training, and includes configuration management and quality assurance documents from the GCS project. Volume 4 contains six appendices: A. Software Accomplishment Summary for the Guidance and Control Software Project; B. Software Configuration Index for the Guidance and Control Software Project; C. Configuration Management Records for the Guidance and Control Software Project; D. Software Quality Assurance Records for the Guidance and Control Software Project; E. Problem Report for the Pluto Implementation of the Guidance and Control Software Project; and F. Support Documentation Change Reports for the Guidance and Control Software Project.

Hayhurst, Kelly J.↗
DOE OSTI2026

Williston basin associated co 2 storage field laboratory

The Williston Basin Associated CO 2 Storage Field Laboratory (WBCFL), led by the Energy & Environmental Research Center (EERC) in partnership with Denbury (now ExxonMobil), was established to advance understanding of CO 2 enhanced oil recovery (EOR) and associated geologic CO 2 storage in the Williston Basin. The specific objective of the WBCFL was to conduct field and laboratory activities to inform decisionmakers regarding the 1) efficacy of associated storage in stacked geologic reservoirs during EOR operations; 2) CO 2 injectivity, oil production, and storage in residual oil zones (ROZs); 3) use of a novel CO 2 storage monitoring, verification, and accounting (MVA) technology (active seismoelectric [ASE] monitoring), and 4) life cycle and techno-economic factors for EOR development scenarios targeting ROZs. The project location was the Pennel Field in southeast Montana, which is part of the Cedar Creek Anticline (CCA) geologic structure within the Williston Basin.

02 PETROLEUM↗
NASA NTRS2008

XTCE and XML Database Evolution and Lessons from JWST, LandSat, and Constellation

The database organizations within three different NASA projects have advanced current practices by creating database synergy between the various spacecraft life cycle stakeholders and educating users in the benefits of the Consultative Committee for Space Data Systems (CCSDS) XML Telemetry and Command Exchange (XTCE) format. The combination of XML for managing program data and CCSDS XTCE for exchange is a robust approach that will meet all user requirements using Standards and Non proprietary tools. COTS tools for XTCEKML are very wide and varied. To combine together various low cost and free tools can be more expensive in the long run than choosing a more expensive COTS tool that meets all the needs. This was especially important when deploying in 32 remote sites with no need for licenses. A common mission XTCEKML format between dissimilar systems is possible and is not difficult. Command XMLKTCE is more complex than telemetry and the use of XTCEKML metadata to describe pages and scripts is needed due to the proprietary nature of most current ground systems. Other mission and science products such as spacecraft loads, science image catalogs, and mission operation procedures can all be described with XML as well to increase there flexibility as systems evolve and change. Figure 10 is an example of a spacecraft table load. The word is out and the XTCE community is growing, The f ~ sXt TCE user group was held in October and in addition to ESAESOC, SC02000, and CNES identified several systems based on XTCE. The second XTCE user group is scheduled for March 10, 2008 with LDMC and others joining. As the experience with XTCE grows and the user community receives the promised benefits of using XTCE and XML the interest is growing fast.

Gal-Edd, Jonathan↗
NASA NTRS2011

Circumstellar Environments of Luminous Infrared Stellar Objects in the Magellanic Clouds

Young stars are formed out of the interstellar medium (ISM) which is replenished by mass loss rates from evolved stars. Circumstellar matter around young and evolved stellar objects usually emits energy in the infrared (IR) wavelength range as the matter is heated by the central star. Surveys of the Magellanic Clouds with the Spitzer Space Telescope in the 3.6-160 micron range have previously been completed. These surveys have led to catalogs of infrared sources: which include HII regions, young stars, super giants, asymptotic giant branch (AGB) stars, post-asymptotic giant branch (post-AGB) stars, and planetary nebulae. The utility of such surveys can be improved upon by using Hubble Space Telescope (HST) data. HST provides higher angular resolution than Spitzer and has allowed for more detailed investigation of these luminous IR objects. This project used previously obtained HST archival data to examine luminous IR objects at optical wavelengths. This allows for the reclassification of stellar objects previously thought as one type of object or in a particular stage of their stellar evolution. An overall objective of this project included looking for extended nebulosity around evolved stars to better understand the life cycle of such objects and classify these nebulae by shape.

large Magellanic clouds↗
NASA NTRS2013

Development of Hybrid Product Breakdown Structure for NASA Ground Systems

The Product Breakdown Structure is traditionally a method of identification of the products of a project in a tree structure. It is a tool used to assess, plan, document, and display the equipment requirements for a project. It is part of a product based planning technique, and attempts to break down all components of a project in as much detail as possible, so that nothing is overlooked. The PBS for ground systems at the Kennedy Space Center is being developed to encompass the traditional requirements including the alignment of facility, systems, and components to the organizational hierarchy. The Ground Operations Product Breakdown Structure is a hybrid in nature in that some aspects of a work breakdown structure will be incorporated and merged with the Architecture Concept of Operations, Master Subsystem List, customer interface, and assigned management responsibility. The Ground Operations Product Breakdown Structure needs to be able to identify the flexibility of support differing customers (internal and external) usage of ground support equipment within the Kennedy Space Center launch and processing complex. The development of the Product Breakdown Structure is an iterative activity Initially documenting the organization hierarchy structure and relationships. The Product Breakdown Structure identifies the linkage between the customer program requirements, allocation of system resources, development of design goals, and identification logistics products. As the Product Breakdown Structure progresses the incorporation of the results of requirement planning for the customer occurs identifying facility needs and systems. The mature Product Breakdown Structure is baselined with a hierarchical drawing, the Product Breakdown Structure database, and an associated document identifying the verification of the data through the life cycle of the program/product line. This paper will document, demonstrate, and identify key aspects of the life cycle of a Hybrid Product Breakdown Structure. The purpose is to show how a project management and system engineering approach can be utilized for providing flexible customer service in an evolving manned space flight launch processing environment.

Monaghan, Mark W.↗
NASA NTRS2013

Development of Hybrid Product Breakdown Structure for NASA Ground Systems

The Product Breakdown Structure is traditionally a method of identification of the products of a project in a tree structure. It is a tool used to assess, plan, document, and display the equipment requirements for a project. It is part of a product based planning technique, and attempts to break down all components of a project in as much detail as possible, so that nothing is overlooked. The PBS for ground systems at the Kennedy Space Center is being developed to encompass the traditional requirements including the alignment of facility, systems, and components to the organizational hierarchy. The Ground Operations Product Breakdown Structure is a hybrid in nature in that some aspects of a work breakdown structure will be incorporated and merged with the Architecture Concept of Operations, Master Subsystem List, customer interface, and assigned management responsibility. The Ground Operations Product Breakdown Structure needs to be able to identify the flexibility of support differing customers (internal and external) usage of ground support equipment within the Kennedy Space Center launch and processing complex. The development of the Product Breakdown Structure is an iterative activity Initially documenting the organization hierarchy structure and relationships. The Product Breakdown Structure identifies the linkage between the customer program requirements, allocation of system resources, development of design goals, and identification logistics products. As the Product Breakdown Structure progresses the incorporation of the results of requirement planning for the customer occurs identifying facility needs and systems. The mature Product Breakdown Structure is baselined with a hierarchical drawing, the Product Breakdown Structure database, and an associated document identifying the verification of the data through the life cycle of the program/product line. This paper will document, demonstrate, and identify key aspects of the life cycle of a Hybrid Product Breakdown Structure. The purpose is to show how a project management and system engineering approach can be utilized for providing flexible customer service in an evolving manned space flight launch processing environment.

Monaghan, Mark W.↗
DOE OSTI2024

Scaleup and Site-Specific Engineering Design for Global Thermostat Direct Air Capture Technology

The overall goal of the project is completion of an initial design of a commercial-scale, Carbon Capture, Utilization, and Storage Direct Air Capture (CCUS-DAC) plant design at three different sites that captures a net of at least 100,000 tonnes per year (TPY) carbon dioxide (CO 2 ) from the atmosphere and considers compression and conditioning of the captured CO 2 for purpose of pipeline transportation to different geological formation sites for deep well injection and underground storage. In addition to the leading system consisting of a scaled-up Global Thermostat DAC unit, overall plant design includes a combined Heat and Power (CHP) unit integrated with a conventional liquid amine-based carbon capture system (90% capture) and compression facilities. These are considered balance of plant (BOP) systems and are required to provide low carbon-intensity steam and power to the DAC process. A second approach involving provision of DAC units modified to directly capture emissions from the CHP unit was initially assessed as an alternative and it was determined to be less mature than considered approach and not included in the scaled-up plant design efforts. Three geographically diverse continental United States locations were selected to better understand the effect of local/regional ambient conditions on scaled-up DAC system performance and project costs: Bucks, Alabama (hot wet climate), Odessa, Texas (dry hot climate), and Goose Creek, Illinois (mid continental climate). The team focused on initial engineering design activities, including the development of project design criteria, initiation of site-specific studies and investigations, completion of DAC system process and equipment design, and definition of balance of plant (BOP) engineering. The purpose of the activities were to develop Technoeconomic Analysis (TEA), Life-Cycle Analysis (LCA), and Environmental, Health, and Safety (EH&S) analysis, and Business Case Analysis (BCA) to validate that the project engineering and scale-up plans of the DAC systems, at each of the three distinct case studies considered, are technically, economically, and environmentally feasible for commercial-scale operation.

20 FOSSIL-FUELED POWER PLANTS↗
NASA NTRS2004

Software Quality Assurance Metrics

Software Quality Assurance (SQA) is a planned and systematic set of activities that ensures conformance of software life cycle processes and products conform to requirements, standards and procedures. In software development, software quality means meeting requirements and a degree of excellence and refinement of a project or product. Software Quality is a set of attributes of a software product by which its quality is described and evaluated. The set of attributes includes functionality, reliability, usability, efficiency, maintainability, and portability. Software Metrics help us understand the technical process that is used to develop a product. The process is measured to improve it and the product is measured to increase quality throughout the life cycle of software. Software Metrics are measurements of the quality of software. Software is measured to indicate the quality of the product, to assess the productivity of the people who produce the product, to assess the benefits derived from new software engineering methods and tools, to form a baseline for estimation, and to help justify requests for new tools or additional training. Any part of the software development can be measured. If Software Metrics are implemented in software development, it can save time, money, and allow the organization to identify the caused of defects which have the greatest effect on software development. The summer of 2004, I worked with Cynthia Calhoun and Frank Robinson in the Software Assurance/Risk Management department. My task was to research and collect, compile, and analyze SQA Metrics that have been used in other projects that are not currently being used by the SA team and report them to the Software Assurance team to see if any metrics can be implemented in their software assurance life cycle process.

McRae, Kalindra A.↗
NASA NTRS1993

Cost and schedule estimation study report

This report describes the analysis performed and the findings of a study of the software development cost and schedule estimation models used by the Flight Dynamics Division (FDD), Goddard Space Flight Center. The study analyzes typical FDD projects, focusing primarily on those developed since 1982. The study reconfirms the standard SEL effort estimation model that is based on size adjusted for reuse; however, guidelines for the productivity and growth parameters in the baseline effort model have been updated. The study also produced a schedule prediction model based on empirical data that varies depending on application type. Models for the distribution of effort and schedule by life-cycle phase are also presented. Finally, this report explains how to use these models to plan SEL projects.

Condon, Steve↗
DOE OSTI2024

Abstract for CRADA between National Energy Technology Laboratory and Carbon To Stone, Inc.

The National Energy Technology Laboratory (NETL) and Carbon To Stone (CTS), Inc. (Participant) will collaborate on a techno-economic assessment (TEA) and life cycle assessment (LCA) of CTS’s carbon dioxide removal (CDR) technology under an awarded project from the Department of Energy’s Direct Air Capture Pre-Commercialization Technology Prize. CTS has developed a technological platform that captures carbon dioxide (CO2) from air and mineralizes it into durable carbonates using alkaline industrial residues such as steel slag and mine tailings. In addition, CTS’s technology uses electrochemistry to recover value-added energy critical metals (ECMs) from these residues. NETL has expertise in CDR TEA and LCA development. The collaboration between CTS and NETL aims to quantify the performance, cost and lifecycle impacts of CTS’s technology and produce LCA and TEA models that can accelerate development and deployment of this technology.

54 ENVIRONMENTAL SCIENCES↗
NASA NTRS1989

Computer-aided software development process design

The authors describe an intelligent tool designed to aid managers of software development projects in planning, managing, and controlling the development process of medium- to large-scale software projects. Its purpose is to reduce uncertainties in the budget, personnel, and schedule planning of software development projects. It is based on dynamic model for the software development and maintenance life-cycle process. This dynamic process is composed of a number of time-varying, interacting developmental phases, each characterized by its intended functions and requirements. System dynamics is used as a modeling methodology. The resulting Software LIfe-Cycle Simulator (SLICS) and the hybrid expert simulation system of which it is a subsystem are described.

Lin, Chi Y.↗
NASA NTRS2010

Planning and Estimation of Operations Support Requirements

Life Cycle Cost (LCC) estimates during the proposal and early design phases, as well as project replans during the development phase, are heavily focused on hardware development schedules and costs. Operations (phase E) costs are typically small compared to the spacecraft development and test costs. This, combined with the long lead time for realizing operations costs, can lead to de-emphasizing estimation of operations support requirements during proposal, early design, and replan cost exercises. The Discovery and New Frontiers (D&NF) programs comprise small, cost-capped missions supporting scientific exploration of the solar system. Any LCC growth can directly impact the programs' ability to fund new missions, and even moderate yearly underestimates of the operations costs can present significant LCC impacts for deep space missions with long operational durations. The National Aeronautics and Space Administration (NASA) D&NF Program Office at Marshall Space Flight Center (MSFC) recently studied cost overruns and schedule delays for 5 missions. The goal was to identify the underlying causes for the overruns and delays, and to develop practical mitigations to assist the D&NF projects in identifying potential risks and controlling the associated impacts to proposed mission costs and schedules. The study found that 4 out of the 5 missions studied had significant overruns at or after launch due to underestimation of the complexity and supporting requirements for operations activities; the fifth mission had not launched at the time of the mission. The drivers behind these overruns include overly optimistic assumptions regarding the savings resulting from the use of heritage technology, late development of operations requirements, inadequate planning for sustaining engineering and the special requirements of long duration missions (e.g., knowledge retention and hardware/software refresh), and delayed completion of ground system development work. This paper updates the D&NF LCC study, looking at the operations (phase E) cost drivers in more detail and extending the study to include 2 additional missions and identifies areas for increased emphasis by project management in order to improve the fidelity of operations estimates.

Newhouse, Marilyn E.↗
NASA NTRS2023

Digital Engineering Design Center (DEDC): Modelling an ISRU System

The DEDC provides immersive project-based learning on digital engineering toolsets and processes supporting NASA’s digital transformation goals: - Digital Engineering uses authoritative sources of systems' data and models as a continuum across disciplines to support integrated digital approach life cycle activities from concept through disposal. - The digital environment provided includes the state-of-the-art digital engineering suite, Siemens Xcelerator. The pilot project is developing an end-to-end integrated model of an In-Situ Resource Utilization (ISRU) system for commodities production: - ISRU uses local resources to provide mission consumables to enable a sustainable Moon or Mars surface presence. - The final digital twin product will include a methanation reactor, condenser, and electrolyzer subsystem.

Digital Engineering Design Center↗
DOE OSTI2025

UBW (USLCI-Brightway2) [SWR-25-169]

Life cycle inventory (LCI) data are critical for robust life cycle assessment (LCA), yet many widely used datasets such as the U.S. Life Cycle Inventory (USLCI) are not natively compatible with advanced modeling frameworks like Brightway2. This work presents an automated pipeline to transform USLCI data into a fully functional Brightway2 project. The workflow performs systematic data cleaning, resolves duplicate process and exchange identifiers, and applies allocation to multi-output processes. Technosphere and biosphere flows are harmonized through unit conversions and a bridge mapping to the biosphere3 database, with comprehensive logging of missing flows and cutoff issues. The resulting Brightway2 database is validated using matrix diagnostics to ensure consistency of the technosphere, and is benchmarked via life cycle impact assessment (LCIA) methods such as ReCiPe and IPCC GWP. Outputs include reproducible CSV exports of corrected processes, elementary flows, characterization factors, and LCIA results, alongside backup utilities for project sharing. This pipeline lowers barriers for integrating USLCI data into open-source LCA workflows, enabling reproducible, validated LCA inventories within the Brightway 2 framework.

Ghosh, Tapajyoti [National Laboratory of the Rocki↗