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.

SourceResearch connectionFrom yearThrough year

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

At least 163 records · Page 9

All sources NASA NTRS DOE OSTI

NASA NTRS1990

IDEF4 technical report, version 1.0

A language for the representation of object oriented software designs is described. IDEF4, a methodology for object-oriented design, is being developed as a design tool for software designers who use such object-oriented languages. Such languages include the Common LISP Object System, Flavors, C++, Smalltalk, Objective C, and others. Since effective usage of the object-oriented paradigm requires a different thought process than that used with conventional procedural or database languages, standard methodologies such as structure charts, data flow diagrams, and traditional data design models (hierarchical, relational, and network) are not sufficient. IDEF4 seeks to provide the necessary facilities to support the object-oriented design decision making process. Specifically, the two primary design goals of IDEF4 are: (1) to provide support for creating object oriented designs whose implementations will exhibit desirable life cycle qualities and reduce total implementation development time; and (2) to make it easy to evaluate object oriented code to determine whether or not the delivered product both conforms to the design and exhibits the desired life cycle qualities. The application of IDEF4 in the life cycle of a software development project is intended to be focused on those activities after a decision has been made to employ object oriented programming technology, but prior to detailed code specification.

Mayer, Richard J.↗

NASA NTRS1994

The Pacor 2 expert system: A case-based reasoning approach to troubleshooting

The Packet Processor 2 (Pacor 2) Data Capture Facility (DCF) acquires, captures, and performs level-zero processing of packet telemetry for spaceflight missions that adhere to communication services recommendations established by the Consultative Committee for Space Data Systems (CCSDS). A major goal of this project is to reduce life-cycle costs. One way to achieve this goal is to increase automation. Through automation, using expert systems, and other technologies, staffing requirements will remain static, which will enable the same number of analysts to support more missions. Analysts provide packet telemetry data evaluation and analysis services for all data received. Data that passes this evaluation is forwarded to the Data Distribution Facility (DDF) and released to scientists. Through troubleshooting, data that fails this evaluation is dumped and analyzed to determine if its quality can be improved before it is released. This paper describes a proof-of-concept prototype that troubleshoots data quality problems. The Pacor 2 expert system prototype uses the case-based reasoning (CBR) approach to development, an alternative to a rule-based approach. Because Pacor 2 is not operational, the prototype has been developed using cases that describe existing troubleshooting experience from currently operating missions. Through CBR, this experience will be available to analysts when Pacor 2 becomes operational. As Pacor 2 unique experience is gained, analysts will update the case base. In essence, analysts are training the system as they learn. Once the system has learned the cases most likely to recur, it can serve as an aide to inexperienced analysts, a refresher to experienced analysts for infrequently occurring problems, or a training tool for new analysts. The Expert System Development Methodology (ESDM) is being used to guide development.

Sary, Charisse↗

NASA NTRS2010

The ICARE Method

The ICARE method is a flexible, widely applicable method for systems engineers to solve problems and resolve issues in a complete and comprehensive manner. The method can be tailored by diverse users for direct application to their function (e.g. system integrators, design engineers, technical discipline leads, analysts, etc.). The clever acronym, ICARE, instills the attitude of accountability, safety, technical rigor and engagement in the problem resolution: Identify, Communicate, Assess, Report, Execute (ICARE). This method was developed through observation of Space Shuttle Propulsion Systems Engineering and Integration (PSE&I) office personnel approach in an attempt to succinctly describe the actions of an effective systems engineer. Additionally it evolved from an effort to make a broadly-defined checklist for a PSE&I worker to perform their responsibilities in an iterative and recursive manner. The National Aeronautics and Space Administration (NASA) Systems Engineering Handbook states, engineering of NASA systems requires a systematic and disciplined set of processes that are applied recursively and iteratively for the design, development, operation, maintenance, and closeout of systems throughout the life cycle of the programs and projects. ICARE is a method that can be applied within the boundaries and requirements of NASA s systems engineering set of processes to provide an elevated sense of duty and responsibility to crew and vehicle safety. The importance of a disciplined set of processes and a safety-conscious mindset increases with the complexity of the system. Moreover, the larger the system and the larger the workforce, the more important it is to encourage the usage of the ICARE method as widely as possible. According to the NASA Systems Engineering Handbook, elements of a system can include people, hardware, software, facilities, policies and documents; all things required to produce system-level results, qualities, properties, characteristics, functions, behavior and performance. The ICARE method can be used to improve all elements of a system and, consequently, the system-level functional, physical and operational performance. Even though ICARE was specifically designed for a systems engineer, any person whose job is to examine another person, product, or process can use the ICARE method to improve effectiveness, implementation, usefulness, value, capability, efficiency, integration, design, and/or marketability. This paper provides the details of the ICARE method, emphasizing the method s application to systems engineering. In addition, a sample of other, non-systems engineering applications are briefly discussed to demonstrate how ICARE can be tailored to a variety of diverse jobs (from project management to parenting).

Henke, Luke↗

NASA NTRS1991

Portable Common Execution Environment (PCEE) project review: Peer review

The purpose of the review was to conduct an independent, in-depth analysis of the PCEE project and to provide the results of said review. The review team was tasked with evaluating the potential contribution of the PCEE project to the improvement of the life cycle support of mission and safety critical (MASC) computing components for large, complex, non-stop, distributed systems similar to those planned for such NASA programs as the space station, lunar outpost, and manned missions to Mars. Some conclusions of the review team are as follow: The PCEE project was given high marks for its breath of vision on the overall problem with MASC software; Correlated with the sweeping vision, the Review Team is very skeptical that any research project can successfully attack such a broad range of problems; and several recommendations are made such as to identify the components of the broad solution envisioned, prioritizing them with respect to their impact and the likely ability of the PCEE or others to attack them successfully, and to rewrite its Concept Document differentiating the problem description, objectives, approach, and results so that the project vision becomes assessible to others.

Locke, C. Douglass↗

NASA NTRS2004

An Exploratory Study of Cost Engineering in Axiomatic Design: Creation of the Cost Model Based on an FR-DP Map

Large complex projects cost large sums of money throughout their life cycle for a variety of reasons and causes. For such large programs, the credible estimation of the project cost, a quick assessment of the cost of making changes, and the management of the project budget with effective cost reduction determine the viability of the project. Cost engineering that deals with these issues requires a rigorous method and systematic processes. This paper introduces a logical framework to a&e effective cost engineering. The framework is built upon Axiomatic Design process. The structure in the Axiomatic Design process provides a good foundation to closely tie engineering design and cost information together. The cost framework presented in this paper is a systematic link between the functional domain (FRs), physical domain (DPs), cost domain (CUs), and a task/process-based model. The FR-DP map relates a system s functional requirements to design solutions across all levels and branches of the decomposition hierarchy. DPs are mapped into CUs, which provides a means to estimate the cost of design solutions - DPs - from the cost of the physical entities in the system - CUs. The task/process model describes the iterative process ot-developing each of the CUs, and is used to estimate the cost of CUs. By linking the four domains, this framework provides a superior traceability from requirements to cost information.

Lee, Taesik↗

NASA NTRS2007

Adapting Project Management Practices to Research-Based Projects

From dealing with the inherent uncertainties in outcomes of scientific research to the lack of applicability of current NASA Procedural Requirements guidance documentation, research-based projects present challenges that require unique application of classical project management techniques. If additionally challenged by the creation of a new program transitioning from basic to applied research in a technical environment often unfamiliar with the cost and schedule constraints addressed by project management practices, such projects can find themselves struggling throughout their life cycles. Finally, supplying deliverables to a prime vehicle customer, also in the formative stage, adds further complexity to the development and management of research-based projects. The Biomedical Research and Countermeasures Projects Branch at NASA Johnson Space Center encompasses several diverse applied research-based or research-enabling projects within the newly-formed Human Research Program. This presentation will provide a brief overview of the organizational structure and environment in which these projects operate and how the projects coordinate to address and manage technical requirements. We will identify several of the challenges (cost, technical, schedule, and personnel) encountered by projects across the Branch, present case reports of actions taken and techniques implemented to deal with these challenges, and then close the session with an open forum discussion of remaining challenges and potential mitigations.

Bahr, P.↗

NASA NTRS1984

The dynamics of software development project management: An integrative systems dynamic perspective

Rather than continuing to focus on software development projects per se, the system dynamics modeling approach outlined is extended to investigate a broader set of issues pertaining to the software development organization. Rather than trace the life cycle(s) of one or more software projects, the focus is on the operations of a software development department as a continuous stream of software products are developed, placed into operation, and maintained. A number of research questions are ""ripe'' for investigating including: (1) the efficacy of different organizational structures in different software development environments, (2) personnel turnover, (3) impact of management approaches such as management by objectives, and (4) the organizational/environmental determinants of productivity.

Vandervelde, W. E.↗

NASA NTRS1977

A maintenance and operations cost model for DSN

A cost model for the DSN is developed which is useful in analyzing the 10-year Life Cycle Cost of the Bent Pipe Project. The philosophy behind the development and the use made of a computer data base are detailed; the applicability of this model to other projects is discussed.

Burt, R. W.↗

NASA NTRS1986

Programming support environment issues in the Byron programming environment

Issues are discussed which programming support environments need to address in order to successfully support software engineering. These concerns are divided into two categories. The first category, issues of how software development is supported by an environment, includes support of the full life cycle, methodology flexibility, and support of software reusability. The second category contains issues of how environments should operate, such as tool reusability and integration, user friendliness, networking, and use of a central data base. This discussion is followed by an examination of Byron, an Ada based programming support environment developed at Intermetrics, focusing on the solutions Byron offers to these problems, including the support provided for software reusability and the test and maintenance phases of the life cycle. The use of Byron in project development is described briefly, and some suggestions for future Byron tools and user written tools are presented.

Larsen, Matthew J.↗

NASA NTRS1995

A Validation of Object-Oriented Design Metrics

This paper presents the results of a study conducted at the University of Maryland in which we experimentally investigated the suite of Object-Oriented (00) design metrics introduced by [Chidamber and Kemerer, 1994]. In order to do this, we assessed these metrics as predictors of fault-prone classes. This study is complementary to [Lieand Henry, 1993] where the same suite of metrics had been used to assess frequencies of maintenance changes to classes. To perform our validation accurately, we collected data on the development of eight medium-sized information management systems based on identical requirements. All eight projects were developed using a sequential life cycle model, a well-known 00 analysis/design method and the C++ programming language. Based on experimental results, the advantages and drawbacks of these 00 metrics are discussed and suggestions for improvement are provided. Several of Chidamber and Kemerer's 00 metrics appear to be adequate to predict class fault-proneness during the early phases of the life-cycle. We also showed that they are, on our data set, better predictors than "traditional" code metrics, which can only be collected at a later phase of the software development processes.

Basili, Victor R.↗

NASA NTRS1997

A Validation of Object-Oriented Design Metrics as Quality Indicators

This paper presents the results of a study in which we empirically investigated the suits of object-oriented (00) design metrics introduced in another work. More specifically, our goal is to assess these metrics as predictors of fault-prone classes and, therefore, determine whether they can be used as early quality indicators. This study is complementary to the work described where the same suite of metrics had been used to assess frequencies of maintenance changes to classes. To perform our validation accurately, we collected data on the development of eight medium-sized information management systems based on identical requirements. All eight projects were developed using a sequential life cycle model, a well-known 00 analysis/design method and the C++ programming language. Based on empirical and quantitative analysis, the advantages and drawbacks of these 00 metrics are discussed. Several of Chidamber and Kamerer's 00 metrics appear to be useful to predict class fault-proneness during the early phases of the life-cycle. Also, on our data set, they are better predictors than 'traditional' code metrics, which can only be collected at a later phase of the software development processes.

Basili, Victor R.↗

NASA NTRS2009

Low Impact Docking System (LIDS)

Since 1996, NASA has been developing a docking system that will simplify operations and reduce risks associated with mating spacecraft. This effort has focused on developing and testing an original, reconfigurable, active, closed-loop, force-feedback controlled docking system using modern technologies. The primary objective of this effort has been to design a docking interface that is tunable to the unique performance requirements for all types of mating operations (i.e. docking and berthing, autonomous and piloted rendezvous, and in-space assembly of vehicles, modules and structures). The docking system must also support the transfer of crew, cargo, power, fluid, and data. As a result of the past 10 years of docking system advancement, the Low Impact Docking System or LIDS was developed. The current LIDS design incorporates the lessons learned and development experiences from both previous and existing docking systems. LIDS feasibility was established through multiple iterations of prototype hardware development and testing. Benefits of LIDS include safe, low impact mating operations, more effective and flexible mission implementation with an anytime/anywhere mating capability, system level redundancy, and a more affordable and sustainable mission architecture with reduced mission and life cycle costs. In 1996 the LIDS project, then known as the Advanced Docking Berthing System (ADBS) project, launched a four year developmental period. At the end of the four years, the team had built a prototype of the soft-capture hardware and verified the control system that will be used to control the soft-capture system. In 2001, the LIDS team was tasked to work with the X- 38 Crew Return Vehicle (CRV) project and build its first Engineering Development Unit (EDU).

LaBauve, Tobie E.↗

NASA NTRS2004

Integrated Risk Management Within NASA Programs/Projects

As NASA Project Risk Management activities continue to evolve, the need to successfully integrate risk management processes across the life cycle, between functional disciplines, stakeholders, various management policies, and within cost, schedule and performance requirements/constraints become more evident and important. Today's programs and projects are complex undertakings that include a myriad of processes, tools, techniques, management arrangements and other variables all of which must function together in order to achieve mission success. The perception and impact of risk may vary significantly among stakeholders and may influence decisions that may have unintended consequences on the project during a future phase of the life cycle. In these cases, risks may be unintentionally and/or arbitrarily transferred to others without the benefit of a comprehensive systemic risk assessment. Integrating risk across people, processes, and project requirements/constraints serves to enhance decisions, strengthen communication pathways, and reinforce the ability of the project team to identify and manage risks across the broad spectrum of project management responsibilities. The ability to identify risks in all areas of project management increases the likelihood a project will identify significant issues before they become problems and allows projects to make effective and efficient use of shrinking resources. By getting a total team integrated risk effort, applying a disciplined and rigorous process, along with understanding project requirements/constraints provides the opportunity for more effective risk management. Applying an integrated approach to risk management makes it possible to do a better job at balancing safety, cost, schedule, operational performance and other elements of risk. This paper will examine how people, processes, and project requirements/constraints can be integrated across the project lifecycle for better risk management and ultimately improve the chances for mission success.

Connley, Warren↗

NASA NTRS1992

The LiAl/FeS2 battery power source for the future

Advanced high power density rechargeable batteries are currently under development. These batteries have the potential of greatly increasing the power and energy densities available for space applications. Depending on whether the system is optimized for high power or high energy, values up to 150 Wh/kg and 2100 W/kg (including hardware) are projected. This is due to the fact that the system uses a high conductivity molten salt electrolyte. The electrolyte also serves as a separator layer with unlimited freeze thaw capabilities. Life of 1000 cycles and ten calendar years is projected. The electrochemistry consists of a lithium aluminum alloy negative electrode, iron disulfide positive electrode, and magnesium oxide powder immobilized molten salt electrolyte. Processed powders are cold compacted into circular discs which are assembled into bipolar cell hardware with peripheral ceramic salts. The culmination of the work will be a high energy battery of 40 kWh and a high power battery of 28 kWh.

Briscoe, J. Douglass↗

NASA NTRS2007

CanSat Competition: Contributing to the Development of NASA's Vision for Robotic Space Exploration

CanSat is an international student design-build-launch competition organized by the American Astronautical Society (AAS) and American Institute of Aeronautics and Astronautics (AIAA). The competition is also sponsored by the Naval Research Laboratory (NRL) and the National Aeronautics and Space Administration (NASA). The CanSat competition is designed for college, university and high school students wanting to participate in an applicable space-related competition. The objective of the CanSat competition is to complete space exploration missions by designing a specific system for a small sounding rocket payload which will follow and perform to a specific set of rules and guidelines for each year's competition. The competition encompasses a complete life-cycle of one year which includes all phases of design, integration, testing, judging and competition. The mission guidelines are based from space exploration missions and include bonus requirement options which teams may choose to participate in. The fundamental goal of the competition is to educate future engineers and scientists. This is accomplished by students applying systems engineering practices to a development project that incorporates an end-to-end life cycle, from requirements analysis, through preliminary design, integration and testing, an actual flight of the CanSat, and concluding with a post-mission debrief. This is done specifically with space related missions to bring a unique aspect of engineering and design to the competition. The competition has been progressing since its creation in 2005. The competition was originally meant to purely convey the engineering and design process to its participants, but through many experiences the competition has also undergone a learning experience with respect to systems engineering process and design. According

Berman, Joshua↗

NASA NTRS2016

Advanced Exploration Systems Atmosphere Resource Recovery and Environmental Monitoring

In September 2011, the Atmosphere Resource Recovery and Environmental Monitoring (ARREM) project was commissioned by NASA's Advanced Exploration Systems program to advance Atmosphere Revitalization Subsystem (ARS) and Environmental Monitoring Subsystem (EMS) technologies for enabling future crewed space exploration missions beyond low Earth orbit. The ARREM project's period of performance covered U.S. Government fiscal years 2012-2014. The ARREM project critically assessed the International Space Station (ISS) ARS and EMS architectures and process technologies as the foundation for an architecture suitable for deep space exploration vehicles. The project's technical content included technical tasks focused on improving the reliability and life cycle cost of ARS and EMS technologies as well as reducing future flight project developmental risk and design, development, test, and evaluation costs. Targeted technology development and maturation tasks, including key technical trade assessments, were accomplished and integrated ARS architectures were demonstrated. The ARREM project developed, demonstrated, and tested leading process technology candidates and subsystem architectures that met or exceeded key figures of merit, addressed capability gaps, and significantly improved the efficiency, safety, and reliability over the state-of-the-art ISS figures of merit. Promising EMS instruments were developed and functionally demonstrated in a simulated cabin environment. The project's technical approach and results are described and recommendations for continued development are provided.

Perry, J.↗

NASA NTRS2011

Qualification of Bonding Process of Temperature Sensors to Extreme Temperature Deep Space Missions

A process has been explored based on the state-of-the-art technology to bond the platinum resistance thermometer (PRT) on to potential aerospace material such as a flat aluminum surface and a flexible copper tube to simulate coaxial cable for the flight applications. Primarily, PRTs were inserted into a metal plated copper braid to avoid stresses on the sensor while attaching the sensor with braid to the base material for long duration deep space missions. Appropriate pretreatment has been implemented in this study to enhance the adhesion of the PRTs to the base material. NuSil product has been chosen in this research to attach PRT to the base materials. The resistance (approx.1.1 k(Omega)) of PRTs has been electrically monitored continuously during the qualification thermal cycling testing from -150 C to +120 C and -100 C to -35 C. The test hardware has been thermal cycled three times the mission life per JPL design principles for JUNO project. No PRT failures were observed during and after the PRT thermal cycling qualification test for extreme temperature environments. However, there were some failures associated with staking of the PRT pig tails as a result of thermal cycling qualification test.

Extreme temperatures↗

NASA NTRS2004

Comparing NASA and ESA Cost Estimating Methods for Human Missions to Mars

To compare working methodologies between the cost engineering functions in NASA Marshall Space Flight Center (MSFC) and ESA European Space Research and Technology Centre (ESTEC), as well as to set-up cost engineering capabilities for future manned Mars projects and other studies which involve similar subsystem technologies in MSFC and ESTEC, a demonstration cost estimate exercise was organized. This exercise was a direct way of enhancing not only cooperation between agencies but also both agencies commitment to credible cost analyses. Cost engineers in MSFC and ESTEC independently prepared life-cycle cost estimates for a reference human Mars project and subsequently compared the results and estimate methods in detail. As a non-sensitive, public domain reference case for human Mars projects, the Mars Direct concept was chosen. In this paper the results of the exercise are shown; the differences and similarities in estimate methodologies, philosophies, and databases between MSFC and ESTEC, as well as the estimate results for the Mars Direct concept. The most significant differences are explained and possible estimate improvements identified. In addition, the Mars Direct plan and the extensive cost breakdown structure jointly set-up by MSFC and ESTEC for this concept are presented. It was found that NASA applied estimate models mainly based on historic Apollo and Space Shuttle cost data, taking into account the changes in technology since then. ESA used models mostly based on European satellite and launcher cost data, taking into account the higher equipment and testing standards for human space flight. Most of NASA's and ESA s estimates for the Mars Direct case are comparable, but there are some important, consistent differences in the estimates for: 1) Large Structures and Thermal Control subsystems; 2) System Level Management, Engineering, Product Assurance and Assembly, Integration and Test/Verification activities; 3) Mission Control; 4) Space Agency Program Level activities.

Hunt, Charles D.↗