Search NASA⌕ Search

SEARCH · Search NASA

Results for “effort estimation”

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 19 records
All sourcesNASA NTRSDOE OSTI
NASA NTRS1995

Software Transition Project Retrospectives and the Application of SEL Effort Estimation Model and Boehm's COCOMO to Complex Software Transition Projects

The Multimission Image Processing Subsystem (MIPS) at the Jet Propulsion Laboratory (JPL) has managed transitions of application software sets from one operating system and hardware platform to multiple operating systems and hardware platforms. As a part of these transitions, cost estimates were generated from the personal experience of in-house developers and managers to calculate the total effort required for such projects. Productivity measures have been collected for two such transitions, one very large and the other relatively small in terms of source lines of code. These estimates used a cost estimation model similar to the Software Engineering Laboratory (SEL) Effort Estimation Model. Experience in transitioning software within JPL MIPS have uncovered a high incidence of interface complexity. Interfaces, both internal and external to individual software applications, have contributed to software transition project complexity, and thus to scheduling difficulties and larger than anticipated design work on software to be ported.

SEL Boehm COCOMO↗
NASA NTRS1974

A survey of AFFDL parameter estimation efforts and future plans

An overview is presented of the applications of parameter estimation methods to the following areas of interest at the Air Force Flight Dynamics Laboratory (AFFDL): (1) conventional stability and control parameter estimation of rigid aircraft; (2) extension to elastic aircraft; (3) extension to stall/spin aerodynamics of rigid aircraft with a nonlinear model; (4) application to the pilot model identification; and (5) correlation of wind tunnel, drop model and flight test data. Only well-documented algorithms are used with modification to the model as required for the specific application. The genesis of each problem and other background information are discussed which enumerate the algorithms and explain how this information is used to improve existing operational aircraft characteristics as well as specify design criteria for future USAF aerospace vehicles.

Eckholdt, D. C.↗
NASA NTRS2014

Technology Estimating 2: A Process to Determine the Cost and Schedule of Space Technology Research and Development

As a leader in space technology research and development, NASA is continuing in the development of the Technology Estimating process, initiated in 2012, for estimating the cost and schedule of low maturity technology research and development, where the Technology Readiness Level is less than TRL 6. NASA' s Technology Roadmap areas consist of 14 technology areas. The focus of this continuing Technology Estimating effort included four Technology Areas (TA): TA3 Space Power and Energy Storage, TA4 Robotics, TA8 Instruments, and TA12 Materials, to confine the research to the most abundant data pool. This research report continues the development of technology estimating efforts completed during 2013-2014, and addresses the refinement of parameters selected and recommended for use in the estimating process, where the parameters developed are applicable to Cost Estimating Relationships (CERs) used in the parametric cost estimating analysis. This research addresses the architecture for administration of the Technology Cost and Scheduling Estimating tool, the parameters suggested for computer software adjunct to any technology area, and the identification of gaps in the Technology Estimating process.

Cole, Stuart K.↗
NASA NTRS2008

Estimating Software-Development Costs With Greater Accuracy

COCOMOST is a computer program for use in estimating software development costs. The goal in the development of COCOMOST was to increase estimation accuracy in three ways: (1) develop a set of sensitivity software tools that return not only estimates of costs but also the estimation error; (2) using the sensitivity software tools, precisely define the quantities of data needed to adequately tune cost estimation models; and (3) build a repository of software-cost-estimation information that NASA managers can retrieve to improve the estimates of costs of developing software for their project. COCOMOST implements a methodology, called '2cee', in which a unique combination of well-known pre-existing data-mining and software-development- effort-estimation techniques are used to increase the accuracy of estimates. COCOMOST utilizes multiple models to analyze historical data pertaining to software-development projects and performs an exhaustive data-mining search over the space of model parameters to improve the performances of effort-estimation models. Thus, it is possible to both calibrate and generate estimates at the same time. COCOMOST is written in the C language for execution in the UNIX operating system.

Baker, Dan↗
NASA NTRS2002

Using Pilots to Assess the Value and Approach of CMMI Implementation

At Goddard Space Flight Center (GSFC), we have chosen to use Capability Maturity Model Integrated (CMMI) to guide our process improvement program. Projects at GSFC consist of complex systems of software and hardware that control satellites, operate ground systems, run instruments, manage databases and data and support scientific research. It is a challenge to launch a process improvement program that encompasses our diverse systems, yet is manageable in terms of cost effectiveness. In order to establish the best approach for improvement, our process improvement effort was divided into three phases: 1) Pilot projects; 2) Staged implementation; and 3) Sustainment and continual improvement. During Phase 1 the focus of the activities was on a baselining process, using pre-appraisals in order to get a baseline for making a better cost and effort estimate for the improvement effort. Pilot pre-appraisals were conducted from different perspectives so different approaches for process implementation could be evaluated. Phase 1 also concentrated on establishing an improvement infrastructure and training of the improvement teams. At the time of this paper, three pilot appraisals have been completed. Our initial appraisal was performed in a flight software area, considering the flight software organization as the organization. The second appraisal was done from a project perspective, focusing on systems engineering and acquisition, and using the organization as GSFC. The final appraisal was in a ground support software area, again using GSFC as the organization. This paper will present our initial approach, lessons learned from all three pilots and the changes in our approach based on the lessons learned.

Godfrey, Sara↗
NASA NTRS2006

Software Development Cost Estimation Executive Summary

Identify simple fully validated cost models that provide estimation uncertainty with cost estimate. Based on COCOMO variable set. Use machine learning techniques to determine: a) Minimum number of cost drivers required for NASA domain based cost models; b) Minimum number of data records required and c) Estimation Uncertainty. Build a repository of software cost estimation information. Coordinating tool development and data collection with: a) Tasks funded by PA&E Cost Analysis; b) IV&V Effort Estimation Task and c) NASA SEPG activities.

data mining↗
NASA NTRS1988

Logistics support of space facilities

The logistic support of space facilities is described, with special attention given to the problem of sizing the inventory of ready spares kept at the space facility. Where possible, data from the Space Shuttle Orbiter is extrapolated to provide numerical estimates for space facilities. Attention is also given to repair effort estimation and long duration missions.

Lewis, William C.↗
NASA NTRS2015

NASA Software Cost Estimation Model: An Analogy Based Estimation Model

The cost estimation of software development activities is increasingly critical for large scale integrated projects such as those at DOD and NASA especially as the software systems become larger and more complex. As an example MSL (Mars Scientific Laboratory) developed at the Jet Propulsion Laboratory launched with over 2 million lines of code making it the largest robotic spacecraft ever flown (Based on the size of the software). Software development activities are also notorious for their cost growth, with NASA flight software averaging over 50% cost growth. All across the agency, estimators and analysts are increasingly being tasked to develop reliable cost estimates in support of program planning and execution. While there has been extensive work on improving parametric methods there is very little focus on the use of models based on analogy and clustering algorithms. In this paper we summarize our findings on effort/cost model estimation and model development based on ten years of software effort estimation research using data mining and machine learning methods to develop estimation models based on analogy and clustering. The NASA Software Cost Model performance is evaluated by comparing it to COCOMO II, linear regression, and K-­ nearest neighbor prediction model performance on the same data set.

Hihn, Jairus↗
NASA NTRS1984

An approach to software cost estimation

A general procedure for software cost estimation in any environment is outlined. The basic concepts of work and effort estimation are explained, some popular resource estimation models are reviewed, and the accuracy of source estimates is discussed. A software cost prediction procedure based on the experiences of the Software Engineering Laboratory in the flight dynamics area and incorporating management expertise, cost models, and historical data is described. The sources of information and relevant parameters available during each phase of the software life cycle are identified. The methodology suggested incorporates these elements into a customized management tool for software cost prediction. Detailed guidelines for estimation in the flight dynamics environment developed using this methodology are presented.

Mcgarry, F.↗
NASA NTRS2016

Visual Odometry for Autonomous Deep-Space Navigation Project

Autonomous rendezvous and docking (AR&D) is a critical need for manned spaceflight, especially in deep space where communication delays essentially leave crews on their own for critical operations like docking. Previously developed AR&D sensors have been large, heavy, power-hungry, and may still require further development (e.g. Flash LiDAR). Other approaches to vision-based navigation are not computationally efficient enough to operate quickly on slower, flight-like computers. The key technical challenge for visual odometry is to adapt it from the current terrestrial applications it was designed for to function in the harsh lighting conditions of space. This effort leveraged Draper Laboratory’s considerable prior development and expertise, benefitting both parties. The algorithm Draper has created is unique from other pose estimation efforts as it has a comparatively small computational footprint (suitable for use onboard a spacecraft, unlike alternatives) and potentially offers accuracy and precision needed for docking. This presents a solution to the AR&D problem that only requires a camera, which is much smaller, lighter, and requires far less power than competing AR&D sensors. We have demonstrated the algorithm’s performance and ability to process ‘flight-like’ imagery formats with a ‘flight-like’ trajectory, positioning ourselves to easily process flight data from the upcoming ‘ISS Selfie’ activity and then compare the algorithm’s quantified performance to the simulated imagery. This will bring visual odometry beyond TRL 5, proving its readiness to be demonstrated as part of an integrated system.Once beyond TRL 5, visual odometry will be poised to be demonstrated as part of a system in an in-space demo where relative pose is critical, like Orion AR&D, ISS robotic operations, asteroid proximity operations, and more.

Robinson, Shane↗
NASA NTRS2016

Visual Odometry for Autonomous Deep-Space Navigation Project

Autonomous rendezvous and docking (AR&D) is a critical need for manned spaceflight, especially in deep space where communication delays essentially leave crews on their own for critical operations like docking. Previously developed AR&D sensors have been large, heavy, power-hungry, and may still require further development (e.g. Flash LiDAR). Other approaches to vision-based navigation are not computationally efficient enough to operate quickly on slower, flight-like computers. The key technical challenge for visual odometry is to adapt it from the current terrestrial applications it was designed for to function in the harsh lighting conditions of space. This effort leveraged Draper Laboratory's considerable prior development and expertise, benefitting both parties. The algorithm Draper has created is unique from other pose estimation efforts as it has a comparatively small computational footprint (suitable for use onboard a spacecraft, unlike alternatives) and potentially offers accuracy and precision needed for docking. This presents a solution to the AR&D problem that only requires a camera, which is much smaller, lighter, and requires far less power than competing AR&D sensors. We have demonstrated the algorithm's performance and ability to process 'flight-like' imagery formats with a 'flight-like' trajectory, positioning ourselves to easily process flight data from the upcoming 'ISS Selfie' activity and then compare the algorithm's quantified performance to the simulated imagery. This will bring visual odometry beyond TRL 5, proving its readiness to be demonstrated as part of an integrated system. Once beyond TRL 5, visual odometry will be poised to be demonstrated as part of a system in an in-space demo where relative pose is critical, like Orion AR&D, ISS robotic operations, asteroid proximity operations, and more.

Robinson, Shane↗
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↗
NASA NTRS2020

Pterodactyl: Thermal Protection System for Integrated Control Design of a Mechanically Deployed Entry Vehicle

The need for precision landing of high mass payloads on Mars and the return of sensitive samples from other planetary bodies to specific locations on Earth is driving the development of an innovative NASA technology referred to as the Deployable Entry Vehicle (DEV). A DEV has the potential to deliver an equivalent science payload with a stowed diameter 3 to 4 times smaller than a traditional rigid capsule configuration. However, the DEV design does not easily lend itself to traditional methods of directional control. The NASA Space Technology Mission Directorate (STMD)’s Pterodactyl project is currently investigating the effectiveness of three different Guidance and Control (G&C) systems – actuated flaps, Center of Gravity (CG) or mass movement, and Reaction Control System (RCS) – for use with a DEV using the Adaptable, Deployable, Entry, and Placement Technology (ADEPT) design. This paper details the Thermal Protection System (TPS) design and associated mass estimation efforts for each of the G&C systems. TPS is needed for the nose cap of the DEV and the flaps of the actuated flap control system. The development of a TPS selection, sizing, and mass estimation method designed to deal with the varying requirements for the G&C options throughout the trajectory is presented. The paper discusses the methods used to i) obtain heating environments throughout the trajectory with respect to the chosen control system and resulting geometry; ii) determine a suitable TPS material; iii) produce TPS thickness estimations; and, iv) determine the final TPS mass estimation based on TPS thickness, vehicle control system, vehicle structure, and vehicle payload.

Hays, Zane B.↗
NASA NTRS2006

Verification and Validation in NASA-CUIP LOX/methane Injector Research Efforts

The NASA-CUIP program is supporting experimental and modeling/computational research efforts investigating wall heat flux characteristics of LOX/methane single-element injectors. A Verification and Validation (V&V) task has begun with the objective of quantifying the degree of accuracy of the models for wall heat flux distributions at specific sets of conditions. The V&V approach used is that being drafted as a standard by the ASME Performance Test Codes Committee, PTC 61: Verification and Validation in Computational Fluid Dynamics and Heat Transfer. The approach is based on well-established concepts from experimental uncertainty analysis. Initially the V&V and uncertainty estimation efforts will use data obtained previously in the same facility using oxygen/hydrogen in single-element injector testing. In this paper the V&V process, experimental facility, and computer code are described, and approaches to estimating the associated uncertainties are discussed.

Coleman, Hugh W.↗
NASA NTRS1992

High-speed Civil Transport Aircraft Emissions

Estimates are given for the emissions from a proposed high speed civil transport (HSCT). This advanced technology supersonic aircraft would fly in the lower stratosphere at a speed of roughly Mach 1.6 to 3.2 (470 to 950 m/sec or 920 to 1850 knots). Because it would fly in the stratosphere at an altitude in the range of 15 to 23 km commensurate with its design speed, its exhaust effluents could perturb the chemical balance in the upper atmosphere. The first step in determining the nature and magnitude of any chemical changes in the atmosphere resulting from these proposed aircraft is to identify and quantify the chemically important species they emit. Relevant earlier work is summarized, dating back to the Climatic Impact Assessment Program of the early 1970s and current propulsion research efforts. Estimates are provided of the chemical composition of an HSCT's exhaust, and these emission indices are presented. Other aircraft emissions that are not due to combustion processes are also summarized; these emissions are found to be much smaller than the exhaust emissions. Future advances in propulsion technology, in experimental measurement techniques, and in understanding upper atmospheric chemistry may affect these estimates of the amounts of trace exhaust species or their relative importance.

Miake-Lye, Richard C.↗
NASA NTRS1994

Leveraging object-oriented development at Ames

This paper presents lessons learned by the Software Engineering Process Group (SEPG) from results of supporting two projects at NASA Ames using an Object Oriented Rapid Prototyping (OORP) approach supported by a full featured visual development environment. Supplemental lessons learned from a large project in progress and a requirements definition are also incorporated. The paper demonstrates how productivity gains can be made by leveraging the developer with a rich development environment, correct and early requirements definition using rapid prototyping, and earlier and better effort estimation and software sizing through object-oriented methods and metrics. Although the individual elements of OO methods, RP approach and OO metrics had been used on other separate projects, the reported projects were the first integrated usage supported by a rich development environment. Overall the approach used was twice as productive (measured by hours per OO Unit) as a C++ development.

Wenneson, Greg↗