Sizing the System : JPL Software Estimation Class for NASA
This presentation has two parts: (a) Sizing the System and (b) Case Study.
software size estimation↗
SEARCH · Search NASA
Results for “software size”
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.
Object-Oriented Software Metrics for Predicting Reusability and Estimating Size
As object-oriented software development methods come into more widespread use, basic questions of software quality assurance must be reconsidered. We will highlight efforts now underway at NASA's Jet Propulsion Laboratory to both assess the quality of software systems developed using object oriented technology and develop guidelines for future development of such systems. The current focus is on design and code reusability., and system size estimation. A number of metrics are proposed and two software systems measured and analyzed. The preliminary results reported here should be useful to software development and quality assurance personnel working in C++ implementation environment.
Sanderson, D. Peter↗
Enhancing the physical modeling capability of open-source MFIX-DEM software for handling particle size polydispersity: Implementation and validation
Multiphase flows are ubiquitous in many industrial processes. The inherent coupling of different phases poses many unique challenges in predicting and effectively controlling these processes. Hence, computational modeling and simulation offers a viable approach to overcome these challenges. Here in this study, we present recent development efforts for enhancing the physical modeling capabilities of an open-source computational modeling tool for real life industrial multiphase processes by enabling particle-size polydispersity and demonstrating with an associated validation study. The proposed implementation was performed in MFIX open-source framework due to its unique feature of tightly integrated computational fluid dynamics and discrete element method solvers for simulating coupled continuum fluid and granular flows. We have implemented the polydispersity feature in a minimally invasive way and provided means to allow easy specification of an arbitrary particle size distribution function, which also enables the user to easily handle an arbitrary number of solid phases, each possessing a distinct arbitrary particle-size distribution. To establish the credibility of improvements, we have carried out a preliminary verification and validation (V&V) study for the polydispersity feature by employing a hopper bin discharge problem, which is frequently encountered in industrial applications. Specifically, two types of micro-glass beads with distinct size distributions are used to fill the hopper in two possible packing arrangements, i.e., well-mixed and layered configurations, with varying mass (particle number) ratios. The experimentally obtained discharge dynamics (e.g., normalized discharge mass fraction for one of the phases versus the overall discharge mass fraction) for different systems is found to be in excellent agreement with the corresponding simulation results.
42 ENGINEERING↗
Developing a software tool for discovery, sizing and sales of thermal energy storage systems
Explore the source record for details and available documents.
25 ENERGY STORAGE↗
N-Set: A NASA Research Project
This slide presentation reviews the research project named N-Set. The goal of this project is to create a user friendly tool for estimating the cost and size of software development. Using the historical experience which NASA has desire is to create a tool that will give an early Rough Order Magnitude (ROM) estimate of the cost and size of a software development task without using the lines of code as a primary input value.
software cost estimating tool↗
Forecasting trends in NASA flight software development tools
The experience gained in the design and development of Shuttle flight and ground support embedded software systems along with projections of increasing role and size of software in the proposed Space Station and other future NASA projects provides the basis for forecasting substantial changes in the tools and methodologies by which embedded software systems are developed and acquired. Similar changes in software architectures and operator interfaces will lead to substantial changes in the approach and techniques involved in software test and system integration. Increasing commonality among different flight systems and between flight and supporting ground systems is projected, along with a more distributed approach to software acquisition in highly complex projects such as Space Station.
Garman, J. R.↗
Assessing Reliability of NDE Flaw Detection Using Smaller Number of Demonstration Data Points
The paper provides an engineering analysis approach for assessing reliability of NDE flaw detection using smaller number of demonstration data points. It explores dependence of probability of detection (POD), probability of false positive (POF), on contrast-to-noise ratio, and net decision threshold-to-noise ratio in a simulated data; and draws some generically applicable inferences to devise the approach. ASTM nondestructive evaluation standards provide requirements on signal-to-noise ratio and/or contrast-to-noise ratio in order to provide reliable flaw detection and limit false positive calls. POD analysis of inspection test data results in an estimated flaw size, denoted by 𝑎90/95. This flaw size has 90% POD and minimum 95% confidence. POF is also estimated in the analysis. POD demonstration requires specimens with flaws of known size. In many situations, it is very expensive to produce the large number of flaws required for the POD analysis. In some situations, only real flaws can truly represent the flaws for demonstration. Real flaws of correct size and location in part configuration specimen may be difficult to produce, if not impossible. Here, an engineering analysis approach is devised using simulation to assess reliability of NDE technique when a limited number of flaws are available for demonstration. In this simulation, a technique is considered reliable, if it provides flaw detectability size equal to or better than the theoretical 𝑎90𝑡ℎ used in simulation and also provides a POF less than or equal to a chosen value. The paper uses simulated signal response versus flaw size data to devise the approach. Linear correlation is used between the signal response data and flaw size. POD software mh1823 uses generalized linear model (GLM) in POD analysis after transforming the flaw size and signal response, if needed, using logarithm. Therefore, this approach is in agreement with the linear signal correlation used in mh1823. Using the POD analysis of data, generic conditions on contrast-to-noise ratio and net decision threshold-to-noise ratio are derived for reliable flaw detection. In order to assess technique reliability using the engineering approach, signal response-to-flaw size correlation about the flaw size of concern is needed. In addition, measurement of noise is also needed. If the technique meets the above requirements, assumption of linear signal-to-flaw size correlation and conditions on noise, then the technique can be assessed using this analysis as it fits the underlying POD model used here. The approach is conservative and is designed to provide a larger flaw size compared to the POD approach. Such NDE technique assessment approach, although, not as rigorous as POD, can be cost effective if the larger flaw size can be tolerated. Typically, this is a situation for all quality control NDE inspections. Here, an NDE technique needs to be reliable and 𝑎90/95 is not estimated, but the assessed flaw size is assumed to be larger than the unknown a90 due to conservative factors or margins. Applicability of the approach for assessing reliability of flaw detection in x-ray radiography and 2D imaging in general is also explored.
Koshti, Ajay M.↗
A controlled experiment on the impact of software structure on maintainability
The impact of software structure on maintainability aspects including comprehensibility, locality, modifiability, and reusability in a distributed system environment is studied in a controlled maintenance experiment involving six medium-size distributed software systems implemented in LADY (language for distributed systems) and six in an extended version of sequential PASCAL. For all maintenance aspects except reusability, the results were quantitatively given in terms of complexity metrics which could be automated. The results showed LADY to be better suited to the development of maintainable software than the extension of sequential PASCAL. The strong typing combined with high parametrization of units is suggested to improve the reusability of units in LADY.
Rombach, Dieter H.↗
SILIA: software implementation of a multi-channel, multi-frequency lock-in amplifier for spectroscopy and imaging applications
In this work, we describe a software implementation of a multi-channel, multi-frequency Lock-in Amplifier (SILIA) to extract modulated signals from noisy data distributed over multiple channels of arbitrary number and size. This software implementation emulates the functionality of a multi-channel, multi-frequency lock-in amplifier in a post-processing step following data acquisition. Unlike most traditional lock-in amplifiers, SILIA can work with any number of input channels and is especially useful to analyze data distributed over many channels. We demonstrate the versatility and performance for extracting weak signals in spectroscopy and fluorescence microscopy. We also discuss more general applications and exhibit a method to automatically estimate error from a lock-in result.
47 OTHER INSTRUMENTATION↗
Artificial intelligence and the space station software support environment
In a software system the size of the Space Station Software Support Environment (SSE), no one software development or implementation methodology is presently powerful enough to provide safe, reliable, maintainable, cost effective real time or near real time software. In an environment that must survive one of the most harsh and long life times, software must be produced that will perform as predicted, from the first time it is executed to the last. Many of the software challenges that will be faced will require strategies borrowed from Artificial Intelligence (AI). AI is the only development area mentioned as an example of a legitimate reason for a waiver from the overall requirement to use the Ada programming language for software development. The limits are defined of the applicability of the Ada language Ada Programming Support Environment (of which the SSE is a special case), and software engineering to AI solutions by describing a scenario that involves many facets of AI methodologies.
Marlowe, Gilbert↗
Measuring Thread Timing to Assess the Feasibility of Early-Bird Message Delivery Across Systems and Scales
Early-bird communication is a communication/computation overlap technique that leverages fine-grained communication to improve application run-time. Communication is divided such that each individual thread can initiate transmission of its portion of the data upon completion rather than waiting for a dedicated communication phase. The benefit of early-bird communication depends on the completion timing of the individual threads: On the one hand, if all threads are complete at nearly the same time, the overheads of sending multiple messages will accumulate, leading to performance that is worse than if a single message had been sent. On the other hand, if thread completions are spread out in time, those that complete earlier can send data while others continue working, leading to performance that is better than if a single message had been sent. The challenge is that the completion times are currently unknown and can vary based on application, problem size, system software, and underlying hardware. In this paper, we address this lacuna by measuring and evaluating the potential overlap afforded by early-bird communication for a selection of proxy applications. These measurements help us understand whether a given application could benefit from early-bird communication. Here, we present our technique for gathering this data and evaluate data collected from three proxy applications: MiniFE, MiniMD, and MiniQMC. Each application is run on three systems with distinct CPU architectures and strong scales across three run sizes. To characterize the behavior of these workloads, we study the trends of thread timings at both a macro level, across all threads across all runs of an application, and a micro level, that is, within a single process of a single run. We observe that our tested applications exhibit significantly different thread arrival distributions. The machine used had a significant impact, with the window of potential overlap varying by as much as an order of magnitude.
97 MATHEMATICS AND COMPUTING↗
ThermalNetwork [SWR-23-101]
ThermalNetwork is software to size distributed ground heat exchangers for district-connected ground-source heat pump systems. The intended audience includes Ground Source Heat Pump Designers.
Mitchell, Matt↗
Space Tug avionics definition study. Volume 1: Executive summary
A top down approach was used to identify, compile, and develop avionics functional requirements for all flight and ground operational phases. Such requirements as safety mission critical functions and criteria, minimum redundancy levels, software memory sizing, power for tug and payload, data transfer between payload, tug, shuttle, and ground were established. Those functional requirements that related to avionics support of a particular function were compiled together under that support function heading. This unique approach provided both organizational efficiency and traceability back to the applicable operational phase and event. Each functional requirement was then allocated to the appropriate subsystems and its particular characteristics were quantified.
Source record↗
Hybrid Wing Body Configuration System Studies
The objective of this study was to develop a hybrid wing body (HWB) sizing and analysis capability, apply that capability to estimate the fuel burn potential for an HWB concept, and identify associated technology requirements. An advanced tube with wings concept was also developed for comparison purposes. NASA s Flight Optimization System (FLOPS) conceptual aircraft sizing and synthesis software was modified to enable the sizing and analysis of HWB concepts. The noncircular pressurized centerbody of the HWB concept was modeled, and several options were created for defining the outboard wing sections. Weight and drag estimation routines were modified to accommodate the unique aspects of an HWB configuration. The resulting capability was then utilized to model a proprietary Boeing blended wing body (BWB) concept for comparison purposes. FLOPS predicted approximately a 15 percent greater drag, mainly caused by differences in compressibility drag estimation, and approximately a 5 percent greater takeoff gross weight, mainly caused by the additional fuel required, as compared with the Boeing data. Next, a 777-like reference vehicle was modeled in FLOPS and calibrated to published Boeing performance data; the same mission definition was used to size an HWB in FLOPS. Advanced airframe and propulsion technology assumptions were applied to the HWB to develop an estimate for potential fuel burn savings from such a concept. The same technology assumptions, where applicable, were then applied to an advanced tube-with-wings concept. The HWB concept had a 39 percent lower block fuel burn than the reference vehicle and a 12 percent lower block fuel burn than the advanced tube-with-wings configuration. However, this fuel burn advantage is partially derived from assuming the high-risk technology of embedded engines with boundary-layer-ingesting inlets. The HWB concept does have the potential for significantly reduced noise as a result of the shielding advantages that are inherent with an over-body engine installation.
Nickol, Craig L.↗
Functional description of the ISIS system
Development of software for avionic and aerospace applications (flight software) is influenced by a unique combination of factors which includes: (1) length of the life cycle of each project; (2) necessity for cooperation between the aerospace industry and NASA; (3) the need for flight software that is highly reliable; (4) the increasing complexity and size of flight software; and (5) the high quality of the programmers and the tightening of project budgets. The interactive software invocation system (ISIS) which is described is designed to overcome the problems created by this combination of factors.
Berman, W. J.↗
Object-oriented productivity metrics
Software productivity metrics are useful for sizing and costing proposed software and for measuring development productivity. Estimating and measuring source lines of code (SLOC) has proven to be a bad idea because it encourages writing more lines of code and using lower level languages. Function Point Analysis is an improved software metric system, but it is not compatible with newer rapid prototyping and object-oriented approaches to software development. A process is presented here for counting object-oriented effort points, based on a preliminary object-oriented analysis. It is proposed that this approach is compatible with object-oriented analysis, design, programming, and rapid prototyping. Statistics gathered on actual projects are presented to validate the approach.
Connell, John L.↗
A practical experience with independent verification and validation
One approach to reducing software cost and increasing reliability is the use of an independent verification and validation (IV & V) methodology. The Software Engineering Laboratory (SEL) applied the IV & V methodology to two medium-size flight dynamics software development projects. Then, to measure the effectiveness of the IV & V approach, the SEL compared these two projects with two similar past projects, using measures like productivity, reliability, and maintain ablilty. Results indicated that the use of the IV & V methodology did not help the overall process nor improve the product in these cases.
Page, Gerald↗