Search NASA⌕ Search

SEARCH · Search NASA

Results for “software 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 127 records · Page 7
All sourcesNASA NTRSDOE OSTI
NASA NTRS1984

Standardization in software conversion of (ROM) estimating

Technical problems and their solutions comprise by far the majority of work involved in space simulation engineering. Fixed price contracts with schedule award fees are becoming more and more prevalent. Accurate estimation of these jobs is critical to maintain costs within limits and to predict realistic contract schedule dates. Computerized estimating may hold the answer to these new problems, though up to now computerized estimating has been complex, expensive, and geared to the business world, not to technical people. The objective of this effort was to provide a simple program on a desk top computer capable of providing a Rough Order of Magnitude (ROM) estimate in a short time. This program is not intended to provide a highly detailed breakdown of costs to a customer, but to provide a number which can be used as a rough estimate on short notice. With more debugging and fine tuning, a more detailed estimate can be made.

Roat, G. H.↗
NASA NTRS2019

Airborne Radar for sUAS Sense and Avoid

A primary challenge for the safe integration of small UAS operations into the National Airspace System (NAS) is traffic deconfliction, both from manned and unmanned aircraft. The UAS Traffic Management (UTM) project being conducted at the National Aeronautics and Space Administration (NASA) considers a layered approach to separation provision, ranging from segregation of operations through airspace volumes (geofences) to autonomous sense and avoid (SAA) technologies for higher risk, densely occupied airspace. Cooperative SAA systems, such as Automatic Dependent Surveillance-Broadcast (ADS-B) and/or vehicle-to-vehicle communication systems provide significant additional risk mitigation but they fail to adequately mitigate collision risks for non-cooperative (non-transponder equipped) airborne aircraft. The RAAVIN (Radar on Autonomous Aircraft to Verify ICAROUS Navigation) flight test being conducted by NASA and the Mid-Atlantic Aviation Partnership (MAAP) was designed to investigate the applicability and performance of a prototype, commercially available sUAS radar to detect and track non-cooperative airborne traffic, both manned and unmanned. The radar selected for this research was a Frequency Modulated Continuous Wave (FMCW) radar with 120 degree azimuth and 80 degree elevation field of view operating at 24.55GHz center frequency with a 200 MHz bandwidth. The radar transmits 2 watts of power thru a Metamaterial Electronically Scanning Array antenna in horizontal polarization. When the radar is transmitting, personnel must be at least 1 meter away from the active array to limit nonionizing radiation exposure. The radar physical dimensions are 18.7cm by 12.1cm by 4.1cm and it weighs less than 820 grams making it well suited for installation on small UASs. The onboard, SAA capability, known as ICAROUS, (Independent Configurable Architecture for Reliable Operations of Unmanned Systems), developed by NASA to support sUAS operations, will provide autonomous guidance using the traffic radar tracks from the onboard radar. The RAAVIN set of studies will be conducted in three phases. The first phase included outdoor, ground-based radar evaluations performed at the Virginia Tech’s Kentland Farm testing range in Blacksburg, VA. The test was designed to measure how well the radar could detect and track a small UAS flying in the radar’s field of view. The radar was used to monitor 5 test flights consisting of outbound, inbound and crossing routes at different ranges and altitudes. The UAS flown during the ground test was the Inspire 2, a quad copter weighing less than 4250 grams (10 pounds) at maximum payload. The radar was set up to scan and track targets over its full azimuthal field of view from 0 to 40 degrees in elevation. The radar was configured to eliminate tracks generated from any targets located beyond 2000 meters from the radar and moving at velocities under 1.45 meters per second. For subsequent phases of the study the radar will be integrated with a sUAS platform to evaluate its performance in flight for SAA applications ranging from sUAS to manned GA aircraft detections and tracking. Preliminary data analysis from the first outdoor ground tests showed the radar performed well at tracking the vehicle as it flew outbound and repeatedly maintained a track out to 1000 meters (maximum 1387 meters) until the vehicle slowed to a stop to reverse direction to fly inbound. As the Inspire flew inbound tracks from beyond 800 meters, a reacquisition time delay was consistently observed between when the Inspire exceeds a speed of 1.45 meters per second and when the radar indicated an inbound target was present and maintained its track. The time delay varied between 6 seconds to over 37 seconds for the inbound flights examined, and typically resulted in about a 200 meter closure distance before the Inspire track was maintained. The radar performed well at both acquiring and tracking the vehicle as it flew crossing routes out past 400 meters across the azimuthal field of view. The radar and ICAROUS software will be integrated and flown on a BFD-1400-SE8-E UAS during the next phase of the RAAVIN project. The main goal at the conclusion of this effort is to determine if this radar technology can reliably support minimum requirements for SAA applications of sUAS. In particular, the study will measure the range of vehicle detections, lateral and vertical angular errors, false and missed/late detections, and estimated distance at closest point of approach after an avoidance maneuver is executed. This last metric is directly impacted by sensor performance and indicates its suitability for the task.

Szatkowski, George N.↗
NASA NTRS1977

Stochastic models for software project management

A method for determining the number and characteristics of milestones to be achieved during a development project is presented in order that effective monitors of progress can be provided. Projections of progress data lead to estimates of the completion with determinable accuracy, but accuracy imposes a requirement that the number of milestones be inversely proportional to the estimate-error variance, and that the milestones themselves be defined in such a way that each represents approximately the same level of effort to complete.

Tausworthe, R. C.↗
NASA NTRS1991

Autonomous reconfigurable GPS/INS navigation and pointing system for rendezvous and docking

This paper describes the results of an integrated navigation and pointing system software development effort sponsored by the NASA MSFC through a SBIR Phase 2 Program. The integrated Global Positioning System (GPS)/Inertial Navigation System (INS) implements an autonomous navigation filter that is reconfigurable in real-time to accommodate mission contingencies. An onboard expert system monitors the spacecraft status and reconfigures the navigation filter accordingly, to optimize the system performance. The navigation filter is a multi-mode Kalman filter to estimate the spacecraft position, velocity, and attitude. Three different GPS-based attitude determination techniques, namely, velocity vector matching, attitude vector matching, and interferometric processing, are implemented to encompass different mission contingencies. The integrated GPS/INS navigation filter will use any of these techniques depending on the mission phase and the state of the sensors. The first technique, velocity vector matching, uses the GPS velocity measurement to estimate the INS velocity errors and exploits the correlation between INS velocity and attitude errors to estimate the attitude. The second technique, attitude vector matching, uses INS gyro measurements and GPS carrier phase (integrated Doppler) measurements during a spacecraft rotation maneuver to determine the attitude. Both of these techniques require only one GPS antenna onboard to determine the spacecraft attitude. The third technique, interferometric processing, requires use of multiple GPS antennae. In order to determine 3-axis body attitude, three GPS antennae (2 no-coplanor baselines) are required.

Upadhyay, Triveni N.↗
NASA NTRS1985

Software productivity improvement through software engineering technology

It has been estimated that NASA expends anywhere from 6 to 10 percent of its annual budget on the acquisition, implementation and maintenance of computer software. Although researchers have produced numerous software engineering approaches over the past 5-10 years; each claiming to be more effective than the other, there is very limited quantitative information verifying the measurable impact htat any of these technologies may have in a production environment. At NASA/GSFC, an extended research effort aimed at identifying and measuring software techniques that favorably impact productivity of software development, has been active over the past 8 years. Specific, measurable, software development technologies have been applied and measured in a production environment. Resulting software development approaches have been shown to be effective in both improving quality as well as productivity in this one environment.

Mcgarry, F. E.↗
NASA NTRS2002

Algorithms for Autonomous GPS Orbit Determination and Formation Flying: Investigation of Initialization Approaches and Orbit Determination for HEO

This report summarizes the efforts to date in processing GPS measurements in High Earth Orbit (HEO) applications by the Colorado Center for Astrodynamics Research (CCAR). Two specific projects were conducted; initialization of the orbit propagation software, GEODE, using nominal orbital elements for the IMEX orbit, and processing of actual and simulated GPS data from the AMSAT satellite using a Doppler-only batch filter. CCAR has investigated a number of approaches for initialization of the GEODE orbit estimator with little a priori information. This document describes a batch solution approach that uses pseudorange or Doppler measurements collected over an orbital arc to compute an epoch state estimate. The algorithm is based on limited orbital element knowledge from which a coarse estimate of satellite position and velocity can be determined and used to initialize GEODE. This algorithm assumes knowledge of nominal orbital elements, (a, e, i, omega, omega) and uses a search on time of perigee passage (tau(sub p)) to estimate the host satellite position within the orbit and the approximate receiver clock bias. Results of the method are shown for a simulation including large orbital uncertainties and measurement errors. In addition, CCAR has attempted to process GPS data from the AMSAT satellite to obtain an initial estimation of the orbit. Limited GPS data have been received to date, with few satellites tracked and no computed point solutions. Unknown variables in the received data have made computations of a precise orbit using the recovered pseudorange difficult. This document describes the Doppler-only batch approach used to compute the AMSAT orbit. Both actual flight data from AMSAT, and simulated data generated using the Satellite Tool Kit and Goddard Space Flight Center's Flight Simulator, were processed. Results for each case and conclusion are presented.

Axelrad, Penina↗
NASA NTRS2004

Refining the W1 and SE1 Facilities

The Engine Research Building (ERB) houses more than 60 test rigs that study all aspects of engine development. By working with Mary Gibson in the SE1 and W1A Turbine Facilities, I became aware of her responsibilities and better acquainted with the inner workings of the ERB. The SE1 Supersonic/Subsonic Wind Tunnel Facility contains 2 small wind tunnels. The first tunnel uses an atmospheric inlet, while the second uses treated 40-psig air. Both of the tunnels are capable of subsonic and supersonic operation. An auxiliary air supply and exhaust piping providing both test sections with suction, blowing, and crossfire capabilities. The current configuration of SE1 consists of a curved diffuser that studies the blockage along the endwalls. The W1A Low Speed Compressor Facility provides insight for the complex flow phenomena within its 4-stage axial compressor, sand the data obtained from W 1A is used to develop advanced models for fluid dynamic assessment. W1A is based off of a low speed research compressor developed by GE in the 1950's. This compressor has a removable casing treatment under rotor 1, which allows for various tip treatment studies. The increased size and low speed allows instrumentation to be located in the compressor s complex flow paths. Air enters the facility through a filtered roof vent, conditioned for temperature and turbulence, and then passed through the compressor W1A is described as a dynamic facility with many projects taking place simultaneously. This current environment makes it challenging to follow the various affairs that are taking place within the area. During my first 4 weeks at the NASA Glenn Research Center, I have assisted Mary Gibson in multiple tasks such as facility documents, record keeping, maintenance and upgrades. The facility has lube systems for its gearbox and compressor. These systems are critical in the successful operation of the facility. I was assigned the task of creating a facility estimate list, which included the filters and strainers required for the compressor. For my remaining time spent here, we expect to complete a facility parts listing and a virtual project summary so that W1A and SE1 will become ergonomic facilities that will make it easier for people to observe the capabilities and history of the area and the employees that operate. Bolstering our efforts in achieving these goal are the online technical tutorials, software such as Microsoft Excel. Macromedia Flash MX Macromedia Dreamweaver MX, Photoshop 6.0 and the assistance of several NASA employees.

Chambers, Rodney D.↗
NASA NTRS1985

Multi-crop area estimation and mapping on a microprocessor/mainframe network

The data processing system is outlined for a 1985 test aimed at determining the performance characteristics of area estimation and mapping procedures connected with the California Cooperative Remote Sensing Project. The project is a joint effort of the USDA Statistical Reporting Service-Remote Sensing Branch, the California Department of Water Resources, NASA-Ames Research Center, and the University of California Remote Sensing Research Program. One objective of the program was to study performance when data processing is done on a microprocessor/mainframe network under operational conditions. The 1985 test covered the hardware, software, and network specifications and the integration of these three components. Plans for the year - including planned completion of PEDITOR software, testing of software on MIDAS, and accomplishment of data processing on the MIDAS-VAX-CRAY network - are discussed briefly.

Sheffner, E.↗
NASA NTRS2009

An Analysis of Rocket Propulsion Testing Costs

The primary mission at NASA Stennis Space Center (SSC) is rocket propulsion testing. Such testing is generally performed within two arenas: (1) Production testing for certification and acceptance, and (2) Developmental testing for prototype or experimental purposes. The customer base consists of NASA programs, DOD programs, and commercial programs. Resources in place to perform on-site testing include both civil servants and contractor personnel, hardware and software including data acquisition and control, and 6 test stands with a total of 14 test positions/cells. For several business reasons there is the need to augment understanding of the test costs for all the various types of test campaigns. Historical propulsion test data was evaluated and analyzed in many different ways with the intent to find any correlation or statistics that could help produce more reliable and accurate cost estimates and projections. The analytical efforts included timeline trends, statistical curve fitting, average cost per test, cost per test second, test cost timeline, and test cost envelopes. Further, the analytical effort includes examining the test cost from the perspective of thrust level and test article characteristics. Some of the analytical approaches did not produce evidence strong enough for further analysis. Some other analytical approaches yield promising results and are candidates for further development and focused study. Information was organized for into its elements: a Project Profile, Test Cost Timeline, and Cost Envelope. The Project Profile is a snap shot of the project life cycle on a timeline fashion, which includes various statistical analyses. The Test Cost Timeline shows the cumulative average test cost, for each project, at each month where there was test activity. The Test Cost Envelope shows a range of cost for a given number of test(s). The supporting information upon which this study was performed came from diverse sources and thus it was necessary to build several intermediate databases in order to understand, validate, and manipulate data. These intermediate databases (validated historical account of schedule, test activity, and cost) by themselves are of great value and utility. For example, for the Project Profile, we were able to merged schedule, cost, and test activity. This kind of historical account conveys important information about sequence of events, lead time, and opportunities for improvement in future propulsion test projects. The Product Requirement Document (PRD) file is a collection of data extracted from each project PRD (technical characteristics, test requirements, and projection of cost, schedule, and test activity). This information could help expedite the development of future PRD (or equivalent document) on similar projects, and could also, when compared to the actual results, help improve projections around cost and schedule. Also, this file can be sorted by the parameter of interest to perform a visual review of potential common themes or trends. The process of searching, collecting, and validating propulsion test data encountered a lot of difficulties which then led to a set of recommendations for improvement in order to facilitate future data gathering and analysis.

Ramirez-Pagan, Carmen P.↗
NASA NTRS2003

Applying Model-Based Reasoning to the FDIR of the Command and Data Handling Subsystem of the International Space Station

All of the International Space Station (ISS) systems which require computer control depend upon the hardware and software of the Command and Data Handling System (C&DH) system, currently a network of over 30 386-class computers called Multiplexor/Dimultiplexors (MDMs)[18]. The Caution and Warning System (C&W)[7], a set of software tasks that runs on the MDMs, is responsible for detecting, classifying, and reporting errors in all ISS subsystems including the C&DH. Fault Detection, Isolation and Recovery (FDIR) of these errors is typically handled with a combination of automatic and human effort. We are developing an Advanced Diagnostic System (ADS) to augment the C&W system with decision support tools to aid in root cause analysis as well as resolve differing human and machine C&DH state estimates. These tools which draw from sources in model-based reasoning[ 16,291, will improve the speed and accuracy of flight controllers by reducing the uncertainty in C&DH state estimation, allowing for a more complete assessment of risk. We have run tests with ISS telemetry and focus on those C&W events which relate to the C&DH system itself. This paper describes our initial results and subsequent plans.

Robinson, Peter↗
NASA NTRS1995

Enhancements to the SSME transfer function modeling code

This report details the results of a one year effort by Ohio University to apply the transfer function modeling and analysis tools developed under NASA Grant NAG8-167 (Irwin, 1992), (Bartholomew, 1992) to attempt the generation of Space Shuttle Main Engine High Pressure Turbopump transfer functions from time domain data. In addition, new enhancements to the transfer function modeling codes which enhance the code functionality are presented, along with some ideas for improved modeling methods and future work. Section 2 contains a review of the analytical background used to generate transfer functions with the SSME transfer function modeling software. Section 2.1 presents the 'ratio method' developed for obtaining models of systems that are subject to single unmeasured excitation sources and have two or more measured output signals. Since most of the models developed during the investigation use the Eigensystem Realization Algorithm (ERA) for model generation, Section 2.2 presents an introduction of ERA, and Section 2.3 describes how it can be used to model spectral quantities. Section 2.4 details the Residue Identification Algorithm (RID) including the use of Constrained Least Squares (CLS) and Total Least Squares (TLS). Most of this information can be found in the report (and is repeated for convenience). Section 3 chronicles the effort of applying the SSME transfer function modeling codes to the a51p394.dat and a51p1294.dat time data files to generate transfer functions from the unmeasured input to the 129.4 degree sensor output. Included are transfer function modeling attempts using five methods. The first method is a direct application of the SSME codes to the data files and the second method uses the underlying trends in the spectral density estimates to form transfer function models with less clustering of poles and zeros than the models obtained by the direct method. In the third approach, the time data is low pass filtered prior to the modeling process in an effort to filter out high frequency characteristics. The fourth method removes the presumed system excitation and its harmonics in order to investigate the effects of the excitation on the modeling process. The fifth method is an attempt to apply constrained RID to obtain better transfer functions through more accurate modeling over certain frequency ranges. Section 4 presents some new C main files which were created to round out the functionality of the existing SSME transfer function modeling code. It is now possible to go from time data to transfer function models using only the C codes; it is not necessary to rely on external software. The new C main files and instructions for their use are included. Section 5 presents current and future enhancements to the XPLOT graphics program which was delivered with the initial software. Several new features which have been added to the program are detailed in the first part of this section. The remainder of Section 5 then lists some possible features which may be added in the future. Section 6 contains the conclusion section of this report. Section 6.1 is an overview of the work including a summary and observations relating to finding transfer functions with the SSME code. Section 6.2 contains information relating to future work on the project.

Irwin, R. Dennis↗
NASA NTRS1993

Space Life Support Engineering Program

This report covers the second year of research relating to the development of closed-loop long-term life support systems. Emphasis was directed toward concentrating on the development of dynamic simulation techniques and software and on performing a thermodynamic systems analysis in an effort to begin optimizing the system needed for water purification. Four appendices are attached. The first covers the ASPEN modeling of the closed loop Environmental Control Life Support System (ECLSS) and its thermodynamic analysis. The second is a report on the dynamic model development for water regulation in humans. The third regards the development of an interactive computer-based model for determining exercise limitations. The fourth attachment is an estimate of the second law thermodynamic efficiency of the various units comprising an ECLSS.

Seagrave, Richard C.↗
NASA NTRS1995

Generalized Support Software: Domain Analysis and Implementation

For the past five years, the Flight Dynamics Division (FDD) at NASA's Goddard Space Flight Center has been carrying out a detailed domain analysis effort and is now beginning to implement Generalized Support Software (GSS) based on this analysis. GSS is part of the larger Flight Dynamics Distributed System (FDDS), and is designed to run under the FDDS User Interface / Executive (UIX). The FDD is transitioning from a mainframe based environment to systems running on engineering workstations. The GSS will be a library of highly reusable components that may be configured within the standard FDDS architecture to quickly produce low-cost satellite ground support systems. The estimates for the first release is that this library will contain approximately 200,000 lines of code. The main driver for developing generalized software is development cost and schedule improvement. The goal is to ultimately have at least 80 percent of all software required for a spacecraft mission (within the domain supported by the GSS) to be configured from the generalized components.

Stark, Mike↗
NASA NTRS2015

Digital Astronaut Project Biomechanical Models: Biomechanical Modeling of Squat, Single-Leg Squat and Heel Raise Exercises on the Hybrid Ultimate Lifting Kit (HULK)

The NASA Digital Astronaut Project (DAP) implements well-vetted computational models to predict and assess spaceflight health and performance risks, and to enhance countermeasure development. The DAP Musculoskeletal Modeling effort is developing computational models to inform exercise countermeasure development and to predict physical performance capabilities after a length of time in space. For example, integrated exercise device-biomechanical models can determine localized loading, which will be used as input to muscle and bone adaptation models to estimate the effectiveness of the exercise countermeasure. In addition, simulations of mission tasks can be used to estimate the astronaut's ability to perform the task after exposure to microgravity and after using various exercise countermeasures. The software package OpenSim (Stanford University, Palo Alto, CA) (Ref. 1) is being used to create the DAP biomechanical models and its built-in muscle model is the starting point for the DAP muscle model. During Exploration missions, such as those to asteroids and Mars, astronauts will be exposed to reduced gravity for extended periods. Therefore, the crew must have access to exercise countermeasures that can maintain their musculoskeletal and aerobic health. Exploration vehicles may have very limited volume and power available to accommodate such capabilities, even more so than the International Space Station (ISS). The exercise devices flown on Exploration missions must be designed to provide sufficient load during the performance of various resistance and aerobic/anaerobic exercises while meeting potential additional requirements of limited mass, volume and power. Given that it is not practical to manufacture and test (ground, analog and/or flight) all candidate devices, nor is it always possible to obtain data such as localized muscle and bone loading empirically, computational modeling can estimate the localized loading during various exercise modalities performed on a given device to help formulate exercise prescriptions and other operational considerations. With this in mind, NASA's Digital Astronaut Project (DAP) is supporting the Advanced Exercise Concepts (AEC) Project, Exercise Physiology and Countermeasures (ExPC) laboratory and NSBRI-funded researchers by developing and implementing well-validated computational models of exercises with advanced exercise device concepts. This report focuses specifically on lower-body resistance exercises performed with the Hybrid Ultimate Lifting Kit (HULK) device as a deliverable to the AEC Project.

health↗
NASA NTRS2002

Studies of Dust Emission as Measured by DIRBE and IRAS

The main activity supported by this grant was to make the dust reddening map more useful for optical and microwave astronomy, and to increase our understanding of interstellar dust in general. We completed all the major objectives of the proposal, and we are eagerly awaiting the launch of Space Infrared Telescope Facility (SIRTF) so that we can check one of our most controversial conclusions. According to the ADS abstract service, the above paper has been cited 895 times. A number of authors have claimed the SFD98 dust maps are miscalibrated, but recent work suggests that the calibration is correct. The primary goal of this ADP grant was to determine the microwave / sum-mm spectrum of interstellar dust emission by cross-correlating the Far Infrared Absolute Spectrophotometer (FIRAS) spectra with a model based on the SFD98 dust map. Because of temperature variation, large (factor of two) variations are observed in submillimeter / 100 micron ratio, so a careful accounting of dust temperature data, based on Diffuse Infrared Background Experiment (DIRBE) 100 and 240 micron channels, was required. Even this improvement was unable to reduce the chi(sup 2) per degree of freedom below 30. Further study revealed that a two-component model, with the two components having different (but reasonable) optical properties, achieved a decrease in chi(sup 2) to less than 2, five times better than the next best fit in the literature. The resulting model uses density and temperature estimates based on DIRBE data, with only four global parameters fit using the FIRAS data. This dramatic reduction in chi(sup 2) using only four fit parameters may indicate that the model is physically correct, but in any case, it is an acceptable phenomenological model. We have released the appropriate data and software on our website (http://astro.berkeley.edu/dust) to allow users to compute the interstellar dust emission between from 100-3000 GHz (or 100 micron 3 mm) with approx. 15% precision. The paper describing these efforts appeared in ApJ 524, 867. This paper has to date been cited 24 times.

Davis, Marc↗
NASA NTRS2007

The Business Case for Automated Software Engineering

Adoption of advanced automated SE (ASE) tools would be more favored if a business case could be made that these tools are more valuable than alternate methods. In theory, software prediction models can be used to make that case. In practice, this is complicated by the 'local tuning' problem. Normally. predictors for software effort and defects and threat use local data to tune their predictions. Such local tuning data is often unavailable. This paper shows that assessing the relative merits of different SE methods need not require precise local tunings. STAR 1 is a simulated annealer plus a Bayesian post-processor that explores the space of possible local tunings within software prediction models. STAR 1 ranks project decisions by their effects on effort and defects and threats. In experiments with NASA systems. STARI found one project where ASE were essential for minimizing effort/ defect/ threats; and another project were ASE tools were merely optional.

model evaluation↗
NASA NTRS2010

Model for Simulating a Spiral Software-Development Process

A discrete-event simulation model, and a computer program that implements the model, have been developed as means of analyzing a spiral software-development process. This model can be tailored to specific development environments for use by software project managers in making quantitative cases for deciding among different software-development processes, courses of action, and cost estimates. A spiral process can be contrasted with a waterfall process, which is a traditional process that consists of a sequence of activities that include analysis of requirements, design, coding, testing, and support. A spiral process is an iterative process that can be regarded as a repeating modified waterfall process. Each iteration includes assessment of risk, analysis of requirements, design, coding, testing, delivery, and evaluation. A key difference between a spiral and a waterfall process is that a spiral process can accommodate changes in requirements at each iteration, whereas in a waterfall process, requirements are considered to be fixed from the beginning and, therefore, a waterfall process is not flexible enough for some projects, especially those in which requirements are not known at the beginning or may change during development. For a given project, a spiral process may cost more and take more time than does a waterfall process, but may better satisfy a customer's expectations and needs. Models for simulating various waterfall processes have been developed previously, but until now, there have been no models for simulating spiral processes. The present spiral-process-simulating model and the software that implements it were developed by extending a discrete-event simulation process model of the IEEE 12207 Software Development Process, which was built using commercially available software known as the Process Analysis Tradeoff Tool (PATT). Typical inputs to PATT models include industry-average values of product size (expressed as number of lines of code), productivity (number of lines of code per hour), and number of defects per source line of code. The user provides the number of resources, the overall percent of effort that should be allocated to each process step, and the number of desired staff members for each step. The output of PATT includes the size of the product, a measure of effort, a measure of rework effort, the duration of the entire process, and the numbers of injected, detected, and corrected defects as well as a number of other interesting features. In the development of the present model, steps were added to the IEEE 12207 waterfall process, and this model and its implementing software were made to run repeatedly through the sequence of steps, each repetition representing an iteration in a spiral process. Because the IEEE 12207 model is founded on a waterfall paradigm, it enables direct comparison of spiral and waterfall processes. The model can be used throughout a software-development project to analyze the project as more information becomes available. For instance, data from early iterations can be used as inputs to the model, and the model can be used to estimate the time and cost of carrying the project to completion.

Mizell, Carolyn↗
NASA NTRS1990

AdaNET research plan

The mission of the AdaNET research effort is to determine how to increase the availability of reusable Ada components and associated software engineering technology to both private and Federal sectors. The effort is structured to define the requirements for transfer of Federally developed software technology, study feasible approaches to meeting the requirements, and to gain experience in applying various technologies and practices. The overall approach to the development of the AdaNET System Specification is presented. A work breakdown structure is presented with each research activity described in detail. The deliverables for each work area are summarized. The overall organization and responsibilities for each research area are described. The schedule and necessary resources are presented for each research activity. The estimated cost is summarized for each activity. The project plan is fully described in the Super Project Expert data file contained on the floppy disk attached to the back cover of this plan.

Mcbride, John G.↗