Joint Force Quarterly. Issue 51, 4th Quarter, October 2008
2008-10-01
and Japanese forces to conduct operations in the event of a WMD attack, to include consequence management operations. Recent activities have...strategic challenges. As a supple- ment, we hosted regular professional devel- opment activities, such as Friday afternoon cinema presentations where a
Strategies for Resolving the Cyber Attribution Challenge
2013-05-01
grant- ing the United States extraterritoriality in the prosecution of US citizens engaged in child sex tourism .10 Furthermore, section 40 7202 of the...the Internet Gover - nance Forum. The United States has been active in venues such as the Organization for Economic Cooperation and Devel- opment in
2010-01-01
program because the bird allegedly was so slow that the new jets would kill it easily. Yet early jets were noto- rious fuel burners . How could the...Winged Defense: The Devel- opment and Possibilities of Modern Air Power— Eco - nomic and Military (New York: G. P. Putnam’s Sons, 1925), 169. 4
2006-01-24
peroxidase-conjugated goat anti-human IgG anti- body ( Kierkegaard and Perry, Gaithersburg, MD) was then added to detect bound antigen colorimetrically...Color devel- opment was stopped after a 30-min incubation by adding Per- oxidase Stop Solution ( Kierkegaard and Perry, Gaithersburg, MD). Optical
Preliminary Study for the Modeling of an Artificial Icing Cloud.
1983-08-01
C.E. and Schulz, R.J., "Analytical Study of Icing Simulation for Turbine Engines in Altitude Test Cells". Arnold Engineering Devel- opment Center...Dept. SAMSO-TR-79-31, May 1979. 7. Keenan, J.H. and Keyes, F.G., "Thermodynamic Properties of Steam", John Wiley and Sons, Inc., N.Y., i961. 8. Pelton
2009-01-01
its role in toxicology , Tox. Sci. 78 (2004) 185–188. [6] (a) B.H. Sorbo, Crystalline rhodanese. I. Purification and physicochemical exam- ination, Acta...the devel- opment of quantitative structure–activity relationships ( QSARs ). pKa-values of phenols and aromatic and aliphatic carboxylic acids, Chemosphere 19 (1989) 1595.
Modeling of Diffuse Photometric Signatures of Satellites for Space Object Identification.
1982-12-01
to provide the groundwork for devel- opment of a computer program which could serve as an aid to tactical space object identification and analysis ...I Photometric Analysis Capability at the ADIC. . . . . .. 2 Operational Limitations of the Photometric Data Analysis Module (PDA...7 PDAM Diffuse Analysis . . . . . . . . . . . . . . . . . 7 Real World SOI Requirements vs POAN Capabilities . . . . 16 Statement of the Problem
Operational Exercise Integration Recommendations for DoD Cyber Ranges
2015-08-05
be the precision and recall of a security information and event management (SIEM) system ’s notifications of unauthorized access to that directory...network traffic, port scanning Deplete Resources TCP flooding, memory leak exploitation Injection Cross-site scripting attacks, SQL injection Deceptive...requirements for personnel development; tactics, techniques, and procedures (TTPs) devel- opment; and mission rehearsals . While unique in their own
JPRS Report, Nuclear Developments
1989-06-28
the Industrial Devel- opment Corporation, the Department of Posts and Tele- communications , the weather bureau, the Department of Trade and...Industry, the SABC [South African Broad- casting Corporation] and the academic space research community had been appointed to keep up with space- related...wanted to launch its own space programme for communication , commercial, industrial and military purposes. JPRS-TND-89-013 28 June 1989 CHINA
Helicopter Transparent Enclosures. Volume 1. Design Handbook
1979-01-01
Armour Research Foundation, "Engineering Design Factors for Laminated Aircraft Windshields, Part 2," WADC-TR-53-99, Wright Air Devel- opment Center...77L~i- -- - -- References .. l,. Islir~ger, Armour Research Foundation, "Engineering Design Factors for Laminated Aircraft Windshields, Parts 1 ahd I...of having separate heating and forming devices, often used with acrylic, will rarely be feasible with polycarbonates. 29.7 Forming Methods Drape
Geokinetic Environment Investigations.
1981-03-31
geoceivers. Small DC solenoids had to be incorporated on each tiltmeter to overcome the Y tilt component stiction after geosensor azimuth slews... tiltmeter data during the sample period. Devel- opment of a LSI-11 executable multiple regression program was also initiated. Several runs of the ALS units...understanding of tilt and temperature data in- side the STM units, tilt and temperature data were collected at various locations on the tiltmeter and its
JPRS Report, Science & Technology, China
1992-09-24
Yuhong; YUHANG XUEBAO, No 3, Jul 92] 23 Improvement of Manufacturing Process and Analysis of Tensile Strength of SiC/Al Preform Wire [Wan Hong...centered on 600MW pressur- ized-water reactor nuclear power plants . Complete devel- opment of the 200MW nuclear low-temperature heat supply reactor...grain yields, substan- tially reduce the amounts of farm chemicals used; develop plant genetic atlas research, try to make major research
USSR Report, International Affairs
1986-10-07
the comprehensive utilization of coal and devel- opment of improved methods assuring a more effective use of low-quality coals, low- calory lignites...promising trend of the joint activity in this sphere. Thus, cyclone furnaces for burning low-quality fuel and fuel wastes save up to 10-20 per cent of...structure of the developing countries should be refined and made concrete and we should move from studying particular classes and strata to a comprehensive
Emerging Issues from New Product Development in Food Manufacturing Industries.
1981-08-19
where price competition can be avoided by increasing emphasis on new product development and by experimenting with product characteristics and images...stress price compe- tition rather than emphasize new product devel- opment and further extend the availability of economy-oriented food products ...is based not on costs and price , but on new product development. 33/, 34/ 13 Economic theory predicts that forces that act to concentrate economic
McMurdo Consolidated Airfields Study: Phase I, Basis of Design
2013-01-01
contents of this report are not to be used for advertising , publication, or promotional purposes. Citation of trade names does not constitute an official...interplay of aircraft movement, maintenance, and environmental conditions may allow devel- opment of successful working strategies to maintain runway...Buenos Aires, Argentina, 9−12 August. Bonin, J. H and E. O. Teichmann. 1949. Investigation of solar energy for ice melting. Armour Research
1990-08-24
solve global problems. 4. It is a fact of history that Stalinism, totalitarian "command socialism," has strongly affected the devel- opment of the...parties are concerned, there we must differentiate. The People’s Party and the Socialist Party paid for the fact that in the past they were de facto...subordinated to the CPCZ, and not just politically. The Social Democratic Party, which was banned for 40 years, on the other hand paid for the fact
Rethinking Twenty-First Century Acquisition: Emerging Trends for Efficiency Ends
1997-01-01
improve the quality of their services. However, dispari- ties in current accounting methods and rules between the two sectors make evalu- ating costs ...are facilitated by the grow- ing use of ABC methods in the account - ing community. These methods tie the to- tal costs of production or services more...Acquisition program man- agers can learn by studying recent devel- opments in the private sector accounting community. Knowledge of relevant total costs and
Summary of Dynamic Analyses of Selected NSS Buildings.
1980-07-01
AREA & WORK UNIT NUMBERS SRI International! Menlo Park, California 94025 FEMA Work Unit 1151D 12. REPORT DATE 13. NO. OF PAGES 11. CONTROLLING OFFICE...ADDRESS (if deff. I’Om Controlling Office) , 1-,7 77 15a. DECLASSIFICATION /DOWNGRADING SCHEDULE 16. DISTRIBUTION STATEMENT (of this report) Approved for... control the final dynamic failure mechanism when there is adequate anchorage to assure full devel- * opment of the tensile membrane mode. The "/s" case
Quantitative Uncertainty Assessment and Numerical Simulation of Micro-Fluid Systems
2005-04-01
flow at Sandia, that was supported by the Laboratory Directed Research and Devel- opment program, and by the Dept. of Energy , Office of Basic Energy ...finite energy . 6 θ is used to denote the random nature of the corresponding quantity. Being symmetrical and positive definite, REE has all its...Laboratory Directed Research and Development Program at Sandia National Laboratories, funded by the U.S. Department of Energy . Support was also provided
2010-06-01
stained using methodology described by Hansel [24]. Semi-quantitative scoring of eosinophilia [25] was as follows: no cells, O; few scattered cells or...with local exam findings of nasal discharge, hyperemia. and/or edema. Exploratory analyses of nasal cytology showed pre-vaccination nasal eosinophilia ...et al. Global burden of Shigella infections: implications for vaccine devel- opment and implementation of control strategies. Bull World Health Organ
Studies in Intelligence. Volume 51, Number 2, 2007
2007-01-01
in the United States, the routine interactions of trade and transnational business and finance , and the exchange of hun- dreds of thousands of...he sought cordial relations with the United States in order to obtain financing for major devel- opment projects, notably the Aswan High Dam. He...expert on Middle East affairs and knowl- edgeable in international finance . Hoover did not share Dulles’s neg- ative view of Nasser and played a key
CACDA Jiffy War Game Technical Manual. Part 1: Methodology
1977-03-01
Systems Analysis Office (Mr Tyburski) Fort Monmout’.h, NJ 07703 Commander 1* USAISD ATTN: ATISE-TD-TS-CD (LT Boyer) Fort Deven , MASS 01433 Commander 2...Developments Activity Fort Leavenworth, Kansas 66027 CACDA JIFFY WAR GAME TECHNICAL MANUAL Part 1: Methodology by Timothy J. Bailey and Gerald A. Martin ACN...ComrbatDevelopments Activity (CACDA), Fort Leavenworth,i-Xsas," for scenario devel- opment and force structure evaluation. The Jiffy Game computer
The Navy Supply Corps Newsletter, March-April 2000
2000-04-01
Logistics Overhaul Team, Jackson- ville, Fla., November 1996 through Janu- ary 2000. Navy and Marine Corps Commendation Medal SHCS (SW) Rolando C...Storekeeper in USS Boone (FFG 28), No- vember 1998 to April 1999. SH1 Andeluvia U. Garcia , USN, (Gold Star in lieu of Fourth Award), Ship’s Store Spe...University, San Francisco, Calif. His previous duty stations include Naval Support Facility, Diego Garcia ; Commander Naval Special Warfare Devel- opment
An Arab NATO in the Making Middle Eastern Military Cooperation Since 2011
2016-09-01
with a focus on strategy and security. In addition to monitoring post -conflict devel- opments in Iraq, Lebanon, and Libya, she researches Arab...non-Arab states such as Iran, Turkey, or post -conflict Israel. Announced at the 2010 Sirte Summit, the League’s Arab Neighbor- hood Policy has failed...preceding de- cade. For example, Saudi Arabia had increased its air 14 force to 305 fighter jets—and currently has a de facto monopoly on Airborne
JPRS Report, Soviet Union, Sociological Studies, No. 6, November-December 1987
1988-08-02
of long- standing, urgently needed changes in society . The con- cept of "uniformity"—a unified view of the world and understanding of social good ...which significantly transformed the social sphere of society already existed on their territory before the arrival of Soviet Power. That is where the... society have become stronger. At the same time, however, uniformity of paths of social devel- opment, of which a great deal has been written and is
2014-12-24
scenarios. The USACEHR has been conducting research and devel- opment efforts on the incorporation of various ENMs into Army materiel, ranging from food ...materiel characteristics, and (3) apply the algorithm and associated risk ranking tool to prioritize additional assessments based on the human health risk...online correspondence to confirm, edit, and supplement the inventory with additional information (See Section 1 in Supplementary Information (SI) for
1990-10-25
Compatibility Sub- Group Steering Committee Sub- Group Chairman Wiley I. Robinson Air Force Systems Command Study Group Chairmen Electrical Interface Joe...on the surface of the body organized into groups defining the corners of a series of four -sided surface panel elements which represent a faceted...Structures Technology. In the Aeroanalysis Group , Dr. Cunningham has conducted many studies leading to devel- opments in the area of analytically
Report on Research at AFGL, January 1979-December 1980.
1982-04-01
Labora- tory. It covers a two-year interval. Although written primarily for Air Force and DOD managers of research and development it is intended to...also includes an introductory chap- ter on AFGL management and logistic activities related to the reporling period. DD IJAN73 1473 EDITIONO I NOV 6S IS...the Air Force Cambridge Research Laboratories (AFCRL). Written primarily for Air Force and DOD managers of research and devel- opment, it shows how
2000-07-01
acceptance is not as simple a matter as it may first appear. Several points must be kept in mind. (1) Risk is a fundamental reality . (2) Risk...1) Proper preparation of an SSPP requires coming to grips with the hard realities of program execution. It involves the exami- nation and...Interfaces. (32:48) Since the conduct of a system safety program will eventually touch on virtually every other element of a system devel- opment program, a
Is a Turretless Tank a Viable Option for the United States Army
1990-06-01
The available pool of service age manpower will decline. The societal trend to smaller, later families and the demographics of the post baby boom...current age of U.S tank devel- opment, began in 1963 and continues to the present. It began with an abortive attempt to jointly design a tank with...Intensity Conflict: The U. S. Expierence ," Armor. The Magazine of Mobile Warfare, XCVII (July-August 1988): 9-15. Nitkowski, Steven R. ILT. "The Return
Optical Pattern Recognition for Missile Guidance.
1982-11-15
directed to novel pattern recognition algo- rithms (that allow pattern recognition and object classification in the face of various geometrical and...I wats EF5 = 50) p.j/t’ni 2 (for btith image pat tern recognitio itas a preproicessing oiperatiton. Ini devices). TIhe rt’ad light intensity (0.33t mW...electrodes on its large faces . This Priz light modulator and the motivation for its devel- SLM is known as the Prom (Pockels real-time optical opment. In Sec
2010-04-01
to be 700 km. The scale of devel- opment is therefore within the fast -growing, smaller wavenumber portion of the large cyclone growth regime...the baroclinic conversion term CA increases about half as fast as it does in the corresponding moist experiment. In the moist case, CA reaches its...conversion of mean-state APE to eddy APE is slower, so the occlusion process is delayed and the system con- tinues deepening, although not as fast as in the
NASA Astrophysics Data System (ADS)
Tyralis, Hristos; Karakatsanis, Georgios; Tzouka, Katerina; Mamassis, Nikos
2015-04-01
The Greek electricity system is examined for the period 2002-2014. The demand load data are analysed at various time scales (hourly, daily, seasonal and annual) and they are related to the mean daily temperature and the gross domestic product (GDP) of Greece for the same time period. The prediction of energy demand, a product of the Greek Independent Power Transmission Operator, is also compared with the demand load. Interesting results about the change of the electricity demand scheme after the year 2010 are derived. This change is related to the decrease of the GDP, during the period 2010-2014. The results of the analysis will be used in the development of an energy forecasting system which will be a part of a framework for optimal planning of a large-scale hybrid renewable energy system in which hydropower plays the dominant role. Acknowledgement: This research was funded by the Greek General Secretariat for Research and Technology through the research project Combined REnewable Systems for Sustainable ENergy DevelOpment (CRESSENDO; grant number 5145)
Cost Estimation Techniques for C3I System Software.
1984-07-01
opment manmonth have been determined for maxi, midi , and mini .1 type computers. Small to median size timeshared developments used 0.2 to 1.5 hours...development schedule 1.23 1.00 1.10 2.1.3 Detailed Model The final codification of the COCOMO regressions was the development of separate effort...regardless of the software structure level being estimated: D8VC -- the expected development computer (maxi. midi . mini, micro) MODE -- the expected
DOE Office of Scientific and Technical Information (OSTI.GOV)
Li, Lianwei; Cai, Zhengxu; Wu, Qinghe
Developing high efficient photocatalyts for splitting water into oxygen and hydrogen is one of the biggest chemical challenges in solar energy utilization. In this paper, we report our effort in rationally designing conjugated porous polymer (CPP) photocatalysts for photocatalytic hydrogen production (PHP) from water. A series of CPP photocatalysts with different chromophore components and bipyridyl (bpy) contents were synthesized and found to evolve hydrogen photocatalytically from water. The PHP activity of bpy-containing CPPs can be greatly enhanced due to the improved light absorption, better wettability, higher crystallinity and the improved charge separation process. Moreover, the CPP photocatalyst made of strongmore » and fully conjugated donor chromo-phore DBD shows the highest hydrogen production rate ~ 33 μmol/h. The results indicate that copolymerization between a strong donor and weak acceptor is a useful strategy for the devel-opment of efficient photocatalysts. This study clarifies that the residual palladium in the CPP networks plays a key role for the catalytic performance. The PHP activity of CPP photocatalyst can be further enhanced to 164 μmol/h with an apparent quantum yield of 1.8% at 350 nm by loading 2 wt% of extra platinum cocat-alyst.« less
Space Weather Model Testing And Validation At The Community Coordinated Modeling Center
NASA Astrophysics Data System (ADS)
Hesse, M.; Kuznetsova, M.; Rastaetter, L.; Falasca, A.; Keller, K.; Reitan, P.
The Community Coordinated Modeling Center (CCMC) is a multi-agency partner- ship aimed at the creation of next generation space weather models. The goal of the CCMC is to undertake the research and developmental work necessary to substantially increase the present-day modeling capability for space weather purposes, and to pro- vide models for transition to the rapid prototyping centers at the space weather forecast centers. This goal requires close collaborations with and substantial involvement of the research community. The physical regions to be addressed by CCMC-related activities range from the solar atmosphere to the Earth's upper atmosphere. The CCMC is an integral part of NASA's Living With aStar initiative, of the National Space Weather Program Implementation Plan, and of the Department of Defense Space Weather Tran- sition Plan. CCMC includes a facility at NASA Goddard Space Flight Center, as well as distributed computing facilities provided by the Air Force. CCMC also provides, to the research community, access to state-of-the-art space research models. In this paper we will provide updates on CCMC status, on current plans, research and devel- opment accomplishments and goals, and on the model testing and validation process undertaken as part of the CCMC mandate.
Debris flow hazards mitigation--Mechanics, prediction, and assessment
Chen, C.-L.; Major, J.J.
2007-01-01
These proceedings contain papers presented at the Fourth International Conference on Debris-Flow Hazards Mitigation: Mechanics, Prediction, and Assessment held in Chengdu, China, September 10-13, 2007. The papers cover a wide range of topics on debris-flow science and engineering, including the factors triggering debris flows, geomorphic effects, mechanics of debris flows (e.g., rheology, fluvial mechanisms, erosion and deposition processes), numerical modeling, various debris-flow experiments, landslide-induced debris flows, assessment of debris-flow hazards and risk, field observations and measurements, monitoring and alert systems, structural and non-structural countermeasures against debris-flow hazards and case studies. The papers reflect the latest devel-opments and advances in debris-flow research. Several studies discuss the development and appli-cation of Geographic Information System (GIS) and Remote Sensing (RS) technologies in debris-flow hazard/risk assessment. Timely topics presented in a few papers also include the development of new or innovative techniques for debris-flow monitoring and alert systems, especially an infra-sound acoustic sensor for detecting debris flows. Many case studies illustrate a wide variety of debris-flow hazards and related phenomena as well as their hazardous effects on human activities and settlements.
A Vision for Co-optimized T&D System Interaction with Renewables and Demand Response
DOE Office of Scientific and Technical Information (OSTI.GOV)
Anderson, C. Lindsay; Zéphyr, Luckny; Liu, Jialin
The evolution of the power system to the reliable, effi- cient and sustainable system of the future will involve development of both demand- and supply-side technology and operations. The use of demand response to counterbalance the intermittency of re- newable generation brings the consumer into the spotlight. Though individual consumers are interconnected at the low-voltage distri- bution system, these resources are typically modeled as variables at the transmission network level. In this paper, a vision for co- optimized interaction of distribution systems, or microgrids, with the high-voltage transmission system is described. In this frame- work, microgrids encompass consumers, distributed renewablesmore » and storage. The energy management system of the microgrid can also sell (buy) excess (necessary) energy from the transmission system. Preliminary work explores price mechanisms to manage the microgrid and its interactions with the transmission system. Wholesale market operations are addressed through the devel- opment of scalable stochastic optimization methods that provide the ability to co-optimize interactions between the transmission and distribution systems. Modeling challenges of the co-optimization are addressed via solution methods for large-scale stochastic op- timization, including decomposition and stochastic dual dynamic programming.« less
Basic Techniques in Environmental Simulation.
1982-07-01
the devel- ’I or oper is liable for all necessary changes in the model or its supporting computer software . After the 90-day warranty expires, the user...processing unit, that part of a computer which accom- plishes arithmetic and logical operations DCFLOS Dynamic cloud -free line-of-sight, a simulation... Software Development ......... 12 1.7.7 Operational Environment, Interfaces, and Constraints. . 12 1.7.8 Effectiveness Evaluation, Value Analysis, and
1993-05-01
limitation of the software package would not allow DATE/I’ME FREQUENCY (kHz) the program to run over 2359 to 0001 UT. This was 18.1 19.0 21.4 24.0...Capability (LWPC), software package devel- oped at NOSC (FERGUSON et al 1989) and adapted by us to the Macintosh personal computer. We find that this... software works very well. Our investigations are to I evaluate and devise geophysical models to be used with . LWPC in assessing VLF communications and
Reconnaissance of the hydrothermal resources of Utah
Rush, F. Eugene
1983-01-01
Geologic factors in the Basin and Range province in Utah are more favorable for the occurrence of geothermal resources than in other areas on the Colorado Plateaus or in the Middle Rocky Mountains. These geologic factors are principally crustal extension and crustal thinning during the last 17 million years. Basalts as young as 10,000 years have been mapped in the area. High-silica volcanic and intrusive rocks of Quaternary age can be used to locate hydrothermal convection systems. Drilling for hot, high-silica, buried rock bodies is most promising in the areas of recent volcanic activity. Southwestern Utah has more geothermal potential than other parts of the Basin and Range province in Utah. The Roosevelt Hot Springs area, the Cove Fort-Sulphurdale area, and the area to the north as far as 60 kilometers from them probably have the best potential for geothermal development for generation of electricity. Other areas with estimated reservoir temperatures greater than 150°C are Thermo, Monroe, Red Hill (in the Monroe-Joseph Known Geothermal Resource Area), Joseph Hot Springs, and the Newcastle area. The rates of heat and water discharge are high at Crater, Meadow, and Hatton Hot Springs, but estimated reservoir temperatures there are less than 150°C. Additional exploration is needed to define the potential in three additional areas in the Escalante Desert.
1984-10-01
functions", Numer . Math., Engineering , Massachusetts Institute of Technology, 1980. (see 10, 177-183, 1967. also MIT Al Lab Technical Report 597, 1980...and steady growth. We have augmented our hardware and distance. In related work, we have explored the use of software base (Vax plus Grinnel, running...capabilities will be the body of software currently ac- 8. COMPUTING ENVIRONMENT FOR cumulated in the testbed and other programs now being devel- IU
2014-09-30
software devel- oped with this project support. S1 Cork School 2013: I. UPPEcore Simulator design and usage, Simulation examples II. Nonlinear pulse...pulse propagation 08/28/13 — 08/02/13, University College Cork , Ireland S2 ACMS MURI School 2012: Computational Methods for Nonlinear PDEs describing
CrossTalk. The Journal of Defense Software Engineering. Volume 17, Number 8, August 2004
2004-08-01
with refined flour and sugars, updated their resumes, and dreamed of better times. Then one day a lone devel- oper from a neighboring province rode into...over the little blue stone by his keyboard while all of the customers in the room beamed their concept of an ideal system at him via mental telepathy
Neurobehavioural Effects of Hypergravity Exposure in CD-1 Mice
NASA Astrophysics Data System (ADS)
Santucci, Daniela; Francia, Nadia; Aloe, Luigi; Enrico, Alleva
The effects of spaceflight on the nervous system physiology could have important implications for the prolonged stay outside Earth's gravitational field. In this view, both ground-based and space research using animal models represent useful tools to investigate the impact of gravity (hypergravity, microgravity and weightlessness) on the nervous system and behaviour. Data coming from these studies, besides acquisition of knowledge relevant for spaceflights and pro-longed permanence of both humans and animals in space, could provide insight into basic bio-logical phenomena underlying the plasticity of the nervous system and its adaptive responses to a changing environment. Most ground experiments employing animal models use the paradigm of hypergravity exposure with the expectation that behavioural and physiological reactions to this environment might help to explain reactions to the microgravity challenge faced by or-biting animals. An overview of ground-based experiments set up to investigate the effects of changes of gravitational environment on the neurobehavioural responses of CD-1 mouse will be reported, and will illustrate the short-, medium-and long-term behavioural and neurobiological consequences of hypergravity exposure both at adulthood and during early and late postnatal development. Moreover, since mother-pup interaction is critical for the survival and the devel-opment of neonatal rodents, especially in an extreme environment such as that of space, we characterized, exploiting ethological methods, changes in maternal behaviour of CD-1 outbred mouse dams exposed to mild hypergravity. The results of these experiments will be discussed.
Calibration strategies for a groundwater model in a highly dynamic alpine floodplain
Foglia, L.; Burlando, P.; Hill, Mary C.; Mehl, S.
2004-01-01
Most surface flows to the 20-km-long Maggia Valley in Southern Switzerland are impounded and the valley is being investigated to determine environmental flow requirements. The aim of the investigation is the devel-opment of a modelling framework that simulates the dynamics of the ground-water, hydrologic, and ecologic systems. Because of the multi-scale nature of the modelling framework, large-scale models are first developed to provide the boundary conditions for more detailed models of reaches that are of eco-logical importance. We describe here the initial (large-scale) groundwa-ter/surface water model and its calibration in relation to initial and boundary conditions. A MODFLOW-2000 model was constructed to simulate the inter-action of groundwater and surface water and was developed parsimoniously to avoid modelling artefacts and parameter inconsistencies. Model calibration includes two steady-state conditions, with and without recharge to the aquifer from the adjoining hillslopes. Parameters are defined to represent areal re-charge, hydraulic conductivity of the aquifer (up to 5 classes), and streambed hydraulic conductivity. Model performance was investigated following two system representation. The first representation assumed unknown flow input at the northern end of the groundwater domain and unknown lateral inflow. The second representation used simulations of the lateral flow obtained by means of a raster-based, physically oriented and continuous in time rainfall-runoff (R-R) model. Results based on these two representations are compared and discussed.
Montaje Experimental de Optica Adaptiva con Tecnología FPGA
NASA Astrophysics Data System (ADS)
Rodriguez Brizuela, F.; Verasay, J. P.; Recabarren, P.
An experimental platform based on FPGA devices, dedicated to implement active and adaptive optic software in HDL has been developed. The devel- oped assembly is the first of a series of works focused on this important area of instrumental astronomy. The exposed development is part of a Final Project of Electronic Engineering of the National University of Cordoba. FULL TEXT IN SPANISH
Gusev, E A; Chemodanov, D V; Sungurov, V A; Neverovsky, E A; Grebenchikov, O A; Likhvantsev, V V
2017-09-01
Despite the use of modern methods of prevention, at least 10% of patients operated on for ophthalmic indications not develop corneal erosion as the indirect complication of general anesthesia. To reduce the number of ophthalmic complications of general anesthesia by prophylactic use of new mito- chondria-targeted antioxidants - Vizomitin (eye drops). 70 patients, which was supposed to perform the average duration of operations under general anesthesia were randomized into 3 groups depending on the method specific (pharmacological) prevention of corneal erosions: (1) control (specic (pharmacological) prevention was not carried out), (2), using preparation "natural tear, and (3) "Vizomitin" preparation. Postoperative biomicroscopy was performed to assess the condition of the cornea, tear film stability was measured and the height of the tear meniscus. When using eye drops "Vizomitin" value is an indicator of stability of the tear film on the 3rd day after the operation more than in the control group of patients by 51% (p = 0.012) and patients groups, natural tear by 57% (p = 0.013). Surgical interventions performed under general anesthesia, leading to an increase in the number ofpatients with decreased tear meniscus height index of the control group with 4 to 7 patients (p = 0.30) in the group of natural tear from 3 to 11 patients (p = 0.008) . In the group with drug "Vizomitin" the number of such patients is reduced from 7 to 1 (p = 0.018). In the surgical procedures under general anesthesia eye drops "Vizomitin" effectively prevents the devel- opment of corneal erosion.
CrossTalk: The Journal of Defense Software Engineering. Volume 20, Number 9, September 2007
2007-09-01
underlying application framework, e.g., Java Enter- prise Edition or .NET. This increases the risk that consumer Web services not based on the same...weaknesses and vulnera- bilities that are targeted by attackers and malicious code. For example, Apache Axis 2 enables a Java devel- oper to simply...load his/her Java objects into the Axis SOAP engine. At runtime, it is the SOAP engine that determines which incoming SOAP request messages should be
NASA Astrophysics Data System (ADS)
Narciso, Steven J.
2011-08-01
An emerging test and measurement standard called AXIe, AdvancedTCA extensions for Instrumentation, is expected to find wide acceptance within the Physics community as it offers many benefits to applications including shock, plasma, particle and nuclear physics. It is expected that many COTS (commercial off-the-shelf) signal conditioning, acquisition and processing modules will become available from a range of different suppliers. AXIe uses AdvancedTCA® as its basis, but then levers test and measurement industry standards such as PXI, IVI, and LXI to facilitate cooperation and plug-and-play interoperability between COTS instrument suppliers. AXIe's large board footprint and power allows high density in a 19" rack, enabling the development of high-performance signal conditioning, analog-to-digital conversion, and data processing, while offering channel count scalability inherent in modular systems. Synchronization between modules is flexible and provided by two triggering structures: a parallel trigger bus, and radially-distributed, time-matched point-to-point trigger lines. Inter-module communication is also provided with an adjacent module local bus allowing data transfer to 600 Gbits/s in each direction, for example between a front-end digitizer and DSP. AXIe allows embedding high performance computing and a range of COTS AdvancedTCA® computer blades are currently available that provide low cost alternatives to the development of custom signal processing modules. The availability of both LAN and PCI Express allow interconnection between modules, as well as industry-standard high-performance data paths to external host computer systems. AXIe delivers a powerful environment for custom module devel opment. As in the case of VXIbus and PXI before it, commercial development kits are expected to be available. This paper will give an overview of the architectural elements of AXIe 1.0, the compatibility model with AdvancedTCA, and signal acquisition performance of many of the AXIe structures.
Entropy, pumped-storage and energy system finance
NASA Astrophysics Data System (ADS)
Karakatsanis, Georgios
2015-04-01
Pumped-storage holds a key role for integrating renewable energy units with non-renewable fuel plants into large-scale energy systems of electricity output. An emerging issue is the development of financial engineering models with physical basis to systematically fund energy system efficiency improvements across its operation. A fundamental physically-based economic concept is the Scarcity Rent; which concerns the pricing of a natural resource's scarcity. Specifically, the scarcity rent comprises a fraction of a depleting resource's full price and accumulates to fund its more efficient future use. In an integrated energy system, scarcity rents derive from various resources and can be deposited to a pooled fund to finance the energy system's overall efficiency increase; allowing it to benefit from economies of scale. With pumped-storage incorporated to the system, water upgrades to a hub resource, in which the scarcity rents of all connected energy sources are denominated to. However, as available water for electricity generation or storage is also limited, a scarcity rent upon it is also imposed. It is suggested that scarcity rent generation is reducible to three (3) main factors, incorporating uncertainty: (1) water's natural renewability, (2) the energy system's intermittent components and (3) base-load prediction deviations from actual loads. For that purpose, the concept of entropy is used in order to measure the energy system's overall uncertainty; hence pumped-storage intensity requirements and generated water scarcity rents. Keywords: pumped-storage, integration, energy systems, financial engineering, physical basis, Scarcity Rent, pooled fund, economies of scale, hub resource, uncertainty, entropy Acknowledgement: This research was funded by the Greek General Secretariat for Research and Technology through the research project Combined REnewable Systems for Sustainable ENergy DevelOpment (CRESSENDO; grant number 5145)
Estimation of ICBM (Intercontinental Ballistic Missile) Performance Parameters
1985-12-01
Formulation . . . . . 42 Staging Event Detection . . . . . . 43 Staging Estimator for Two State System . 46 * Staging Time and Vehicle Parameter...6 4. Land Based Sensor Coordinate System . . . . 10 5. Radar Site Geometry . . . . . . . . . 1 6. Observation Geometry . . . . . . . . . 12 7...Ve dm mi + dmi+d Figure 3. Rocket Thrust of fuel, the equation of motion of the rocket can be devel--S oped. This is a closed system of particles
ggCyto: Next Generation Open-Source Visualization Software for Cytometry.
Van, Phu; Jiang, Wenxin; Gottardo, Raphael; Finak, Greg
2018-06-01
Open source software for computational cytometry has gained in popularity over the past few years. Efforts such as FlowCAP, the Lyoplate and Euroflow projects have highlighted the importance of efforts to standardize both experimental and computational aspects of cytometry data analysis. The R/BioConductor platform hosts the largest collection of open source cytometry software covering all aspects of data analysis and providing infrastructure to represent and analyze cytometry data with all relevant experimental, gating, and cell population annotations enabling fully reproducible data analysis. Data visualization frameworks to support this infrastructure have lagged behind. ggCyto is a new open-source BioConductor software package for cytometry data visualization built on ggplot2 that enables ggplot-like functionality with the core BioConductor flow cytometry data structures. Amongst its features are the ability to transform data and axes on-the-fly using cytometry-specific transformations, plot faceting by experimental meta-data variables, and partial matching of channel, marker and cell populations names to the contents of the BioConductor cytometry data structures. We demonstrate the salient features of the package using publicly available cytometry data with complete reproducible examples in a supplementary material vignette. https://bioconductor.org/packages/devel/bioc/html/ggcyto.html. gfinak@fredhutch.org. Supplementary data are available at Bioinformatics online and at http://rglab.org/ggcyto/.
Safer bridge railings, volume 1 summary report.
DOT National Transportation Integrated Search
1984-06-01
This study consisted of strength analyses of five in-service bridge railing systems, thirty full-scale vehicle crash tests on those railing systems and on a load measuring wall, the development of recommended design guidelines and deve1opment of reco...
Polinyk, S I; Rybchenko, L A; Klimyk, B T
2017-12-01
The objective of this work was to identify and compare the polymorphism of the rs3803662 polymorphism of the TOX3/LOC643714 gene in breast cancer patients who have undergone ionizing radiation due to the Chornobyl accident and in patients without ionizing radiation (IR) in the history. The determination of the rs3803662 polymorphism of the TOX3/LOC643714 gene was per formed by polymerase chain reaction (PCR) in 83 patients with breast cancer: 42 subjects who were exposed to ion izing radiation due to the Chornobyl accident, 41 people without ionizing radiation in history and 17 controls in Ukraine without cancer pathology. In order to compare the obtained data on spontaneous and radiation associated breast cancer and to calculate the differences in the frequencies of alleles and the risk of oncopathology, data from literature on control groups of the populations of the Russian Federation, Sweden, and the United Kingdom were used. Comparing with the literature data and the group of exposed subjects, the homozygous carriers of the minor alleles of the TOX3/LOC643714 ТТ gene revealed an increased risk of developing breast cancer: OR = 2.89, p = 0.02 (CI 95% 1.17 7,16). In subjects without the influence of IR in history, the carrier of homozygous minor axis of the gene TOX3/LOC643714 ТТ is also associated with the risk of breast cancer: OR = 3.83, p = 0.0002 (CI 95% 0.82-14.14). In the homozygous carriers of the minor alleles of the TOX3 / LOC643714 gene exposed to IR, there was no increase in the risk of developing breast cancer (OR = 0.65, p = 0.46, CI 95% 0.21-2.04) compared with the con trol group of Ukrainian population. The carrier of homozygous minor alleles of the TOX3/LOC643714 gene is not a risk factor for the devel opment of breast cancer under conditions of exposure to ionizing radiation in the study group of the Ukrainian population. S. I. Polinyk, L. A. Rybchenko, B. T. Klimyk.
Structures, Design and Test: Materials
NASA Technical Reports Server (NTRS)
2004-01-01
NASA Marshall has developed a technology that combines a film/adhesive laydown module with fiber placement technology to enable the processing of composite prepreg tow/tape and films, foils, or adhesives on the same placement machine. The deve!opment of this technology grew out of NASA's need for lightweight, permeation-resistant cryogenic propellant tanks.
Development Status of Optical and Electromagnetic Instruments onboard JEM-GLIMS
NASA Astrophysics Data System (ADS)
Sato, Mitsuteru; Ushio, Tomoo; Morimoto, Takeshi; Suzuki, Makoto; Yamazaki, Atsushi; Ishida, Ryohei; Takahashi, Yukihiro; Hobara, Yasuhide; Sakamoto, Yuji; Yoshita, Kengo
In order to study the generation mechanism of Transient Luminous Events (TLEs), global oc-currence rates and distributions of lightning and TLEs, and the relationship between lightning, TLEs and Terrestrial Gamma-ray Flashes (TGFs), we will carry out the lightning and TLE observation at Exposed Facility of Japanese Experiment Module (JEM-EF) of International Space Station (ISS). In this mission named JEM-GLIMS (Global Lightning and sprIte Mea-surementS on JEM-EF) two kinds of optical instruments and two sets of radio receivers will be integrated into the Multi mission Consolidated Equipment (MCE) which is the bus system and will be installed at JEM-EF. The optical instruments consist of two wide FOV CMOS cameras and six wide FOV photometers, and all these optical instruments are pointed to the nadir direction. CMOS cameras named LSI (Lightning and Sprite Imager) use the STAR-250 device as a detector, which has 512x512 pixels and 25x25 µm pixel size, and have 28.3x28.3 deg. FOV. One CMOS camera with a wide band filter (730-830 nm) mainly measures lightning emission, while another camera with a narrowband filter (766+/-6 nm) mainly measures TLE emission. Five of six photometers named as PH have 42.7 deg. FOV and use photomultiplier tube (PMT) as a photon detector. They equip band-pass filters (150-280 nm, 316+/-5 nm, 337+/-5 nm, 392+/-5 nm, and 762+/-5 nm) for the absolute intensity measurement of the TLE emission. One of six photometers equips a wide-band filter (600-900 nm) to detect light-ning occurring within 86.8 deg. FOV. These output signals will be recorded with the sampling frequency of 20 kHz with a 12-bit resolution. One of two electromagnetic instruments is a VLF receiver (VLFR), which measures electromagnetic waves in the frequency range of 1-40 kHz with 16-bit resolution. Another instrument is VHF interferometer (VITF), which measures VHF pulses generated lightning discharge in the frequency range of 70-100 MHz. JEM-GIMS will be launched in 2011. We have passed the critical design review (CDR) on January and February and have started the fabrication of the proto-flight model. We will present the devel-opment status of the JEM-GLISM optical instruments and discuss the scientific outputs derived from this mission more in detail.
Development and Optimization of Silver Nanoparticle Formulation for Fabrication
2015-08-14
Development and Optimization of Silver Nanoparticle Formulation for Fabrication Publication Type: DJournal/ Paper D Book Chapter ~ Tech Report D...leofPublicationorPresentation: Deve l opment and Optimization of Silver Nanoparticle Formulation for Fabrication 3. Author(s): (List authors starting...fabrication process of silver nanoparticl es could improve future silver containing products , which is i mpor tant to l owering toxicity and improving
Experiences to Go: Teaching with Intelligence Case Studies
2004-09-01
SPONSOR/MONITOR’S ACRONYM(S) 11. SPONSOR/MONITOR’S REPORT NUMBER(S) 12 . DISTRIBUTION/AVAILABILITY STATEMENT Approved for public release...opment (AID) and a public affairs specialist from the U.S. Information Service (USIS). There was no Marine Security Guard detachment. The Regional...also were present. At around 2100 hours, Pamela and the others heard a muffled explosion from the direction of the airport, some 12 kilo- meters away
Falcone, Emmanuela; Grandoni, Luca; Garibaldi, Francesca; Manni, Isabella; Filligoi, Giancarlo; Piaggio, Giulia; Gurtner, Aymone
2016-01-01
miRNAs are potent regulators of gene expression and modulate multiple cellular processes in physiology and pathology. Deregulation of miRNAs expression has been found in various cancer types, thus, miRNAs may be potential targets for cancer therapy. However, the mechanisms through which miRNAs are regulated in cancer remain unclear. Therefore, the identification of transcriptional factor-miRNA crosstalk is one of the most update aspects of the study of miRNAs regulation. In the present study we describe the development of a fast and user-friendly software, named infinity, able to find the presence of DNA matrices, such as binding sequences for transcriptional factors, on ~65kb (kilobase) of 939 human miRNA genomic sequences, simultaneously. Of note, the power of this software has been validated in vivo by performing chromatin immunoprecipitation assays on a subset of new in silico identified target sequences (CCAAT) for the transcription factor NF-Y on colon cancer deregulated miRNA loci. Moreover, for the first time, we have demonstrated that NF-Y, through its CCAAT binding activity, regulates the expression of miRNA-181a, -181b, -21, -17, -130b, -301b in colon cancer cells. The infinity software that we have developed is a powerful tool to underscore new TF/miRNA regulatory networks. Infinity was implemented in pure Java using Eclipse framework, and runs on Linux and MS Windows machine, with MySQL database. The software is freely available on the web at https://github.com/bio-devel/infinity. The website is implemented in JavaScript, PHP and HTML with all major browsers supported.
Garibaldi, Francesca; Manni, Isabella; Filligoi, Giancarlo; Piaggio, Giulia; Gurtner, Aymone
2016-01-01
Motivation miRNAs are potent regulators of gene expression and modulate multiple cellular processes in physiology and pathology. Deregulation of miRNAs expression has been found in various cancer types, thus, miRNAs may be potential targets for cancer therapy. However, the mechanisms through which miRNAs are regulated in cancer remain unclear. Therefore, the identification of transcriptional factor–miRNA crosstalk is one of the most update aspects of the study of miRNAs regulation. Results In the present study we describe the development of a fast and user-friendly software, named infinity, able to find the presence of DNA matrices, such as binding sequences for transcriptional factors, on ~65kb (kilobase) of 939 human miRNA genomic sequences, simultaneously. Of note, the power of this software has been validated in vivo by performing chromatin immunoprecipitation assays on a subset of new in silico identified target sequences (CCAAT) for the transcription factor NF-Y on colon cancer deregulated miRNA loci. Moreover, for the first time, we have demonstrated that NF-Y, through its CCAAT binding activity, regulates the expression of miRNA-181a, -181b, -21, -17, -130b, -301b in colon cancer cells. Conclusions The infinity software that we have developed is a powerful tool to underscore new TF/miRNA regulatory networks. Availability and Implementation Infinity was implemented in pure Java using Eclipse framework, and runs on Linux and MS Windows machine, with MySQL database. The software is freely available on the web at https://github.com/bio-devel/infinity. The website is implemented in JavaScript, PHP and HTML with all major browsers supported. PMID:27082112
Low-cost, distributed, sensor-based weigh-in-motion systems.
DOT National Transportation Integrated Search
2009-12-01
Monitoring truck weights is essential for traffic operations, roadway design, traffic safety, and regulations. : Traditional roadside static truck weighing stations have many operational shortcomings, and so there have : been ongoing efforts to devel...
JPRS Report, Science & Technology, USSR: Science & Technology Policy
1990-01-15
opment of theoretical and applied research in the field of cybernetic science was an unrealized dream . It did not receive support among the leaders... dream . Cooperative works with foreign organizations have made it possible to relieve the urgency of some problems, but one must not in all questions...Belonging to the first group, for example, is telepathy —the transmission of informa- tion from a human agent to the human percipient, who is isolated
Military Review: The Professional Journal of the U.S. Army. May-June 2002
2002-06-01
artisans formed corporations , and in the Middle Ages, tradesmen formed guilds.5 In the U.S. Army, recurring officers’ calls and lunchtime discussions...Analysis of Air-Based Mechanization and Vertical Envel- opment Concepts and Technologies, DB-321-A (Santa Monica, CA: RAND Corporation , 2001). 4. Colonel...AB-169-A/OSD (Santa Monica, CA: RAND Corporation , September 1997); and John Matsumura et al., Rapid Force Projection Technologies: Assessing the
Hazardous wildlife attractants on or near airports
DOT National Transportation Integrated Search
1997-05-01
This advisory circular (AC) provides guidance on locating certain land uses : having the potential to attract hazardous wildlife to or in the vicinity of : public-use airports. It also provides guidance concerning the placement of new : airport devel...
Measuring, achieving and promoting smoothness of Virginia's asphalt overlays.
DOT National Transportation Integrated Search
1999-01-01
This study was initiated with the goal of identifying the predominant factors affecting the achievable smoothness of asphalt overlays. In addition, it chronicles the evolution of Virginia's innovative special provision for smoothness, which was devel...
NASA Astrophysics Data System (ADS)
Istomin, V. A.
2018-05-01
The software package Planet Atmosphere Investigator of Non-equilibrium Thermodynamics (PAINeT) has been devel-oped for studying the non-equilibrium effects associated with electronic excitation, chemical reactions and ionization. These studies are necessary for modeling process in shock tubes, in high enthalpy flows, in nozzles or jet engines, in combustion and explosion processes, in modern plasma-chemical and laser technologies. The advantages and possibilities of the package implementation are stated. Within the framework of the package implementation, based on kinetic theory approximations (one-temperature and state-to-state approaches), calculations are carried out, and the limits of applicability of a simplified description of shock-heated air flows and any other mixtures chosen by the user are given. Using kinetic theory algorithms, a numerical calculation of the heat fluxes and relaxation terms can be performed, which is necessary for further comparison of engineering simulation with experi-mental data. The influence of state-to-state distributions over electronic energy levels on the coefficients of thermal conductivity, diffusion, heat fluxes and diffusion velocities of the components of various gas mixtures behind shock waves is studied. Using the software package the accuracy of different approximations of the kinetic theory of gases is estimated. As an example state-resolved atomic ionized mixture of N/N+/O/O+/e- is considered. It is shown that state-resolved diffusion coefficients of neutral and ionized species vary from level to level. Comparing results of engineering applications with those given by PAINeT, recommendations for adequate models selection are proposed.
Midwest Transportation Consortium annual progress report : October 2002.
DOT National Transportation Integrated Search
2002-10-01
From the Director: For the past three years, the Midwest Transportation Consortium (MTC) has focused its efforts in : supporting the development and use of asset management systems in transportation. The MTCs main : focus is on human capital devel...
DOT National Transportation Integrated Search
1998-10-01
The primary responsibility of the Virginia Department of Transportation's (VDOT) Geographic Information Systems Lead Unit is to develop and implement the department's geographic information system (GIS). To fulfill this responsibility, the unit devel...
North Korean Paradoxes. Circumstances, Costs, and Consequences of Korean Unification
2005-01-01
consequences of Korean unification / Charles Wolf, Jr., Kamil Akramov. p. cm. "MG-333." Includes bibliographical references. ISBN 0-8330-3762-5 (pbk. : alk ...Institute of Technology NBER National Bureau for Economic Research OECD Organization for Economic Cooperation and Develoment OSD Office of the Secretary of...opment ( OECD ) with a per capita income over $10,000 and the other a "lights-out" but nuclear-capable dynastic state-is the riddle; how to link economic
1992-10-01
sealed bidding and competitive proposals. governed by the same regulations and laws The sealed bidding procedure requires ade- that govern procurement ...Summary xiv NDI ACQUISITION: An Alternative to "Business as Usual" to successful, effective government procure - posal Cover Sheet). Moreover, the...became policy when the OPlP ;,;sued the first opment costs. These benefits may be offset by in a series of memoranda governing procure - performance
Railroad Redevelopment Planning.
1981-01-01
TEST CHART4A IONAL BUREAU’ Of STANDARDS- 1963-A -- m-ma REDQEVELcOPMENT PLANNIING *p W44 it -- 8 UNVRSITY OF C@O RAOO AT GENVER Tis docmr bpf Cr)o~d...officials began work on a set of guidelines in order to have some form of planned development u versus a piecemeal approach. According to a city...place. The city worked closely with various developers and their architects on the guidelines and the resulting ordinance was generally acceptable to
GIS-and Web-based Water Resource Geospatial Infrastructure for Oil Shale Development
DOE Office of Scientific and Technical Information (OSTI.GOV)
Zhou, Wei; Minnick, Matthew; Geza, Mengistu
2012-09-30
The Colorado School of Mines (CSM) was awarded a grant by the National Energy Technology Laboratory (NETL), Department of Energy (DOE) to conduct a research project en- titled GIS- and Web-based Water Resource Geospatial Infrastructure for Oil Shale Development in October of 2008. The ultimate goal of this research project is to develop a water resource geo-spatial infrastructure that serves as “baseline data” for creating solutions on water resource management and for supporting decisions making on oil shale resource development. The project came to the end on September 30, 2012. This final project report will report the key findings frommore » the project activity, major accomplishments, and expected impacts of the research. At meantime, the gamma version (also known as Version 4.0) of the geodatabase as well as other various deliverables stored on digital storage media will be send to the program manager at NETL, DOE via express mail. The key findings from the project activity include the quantitative spatial and temporal distribution of the water resource throughout the Piceance Basin, water consumption with respect to oil shale production, and data gaps identified. Major accomplishments of this project include the creation of a relational geodatabase, automated data processing scripts (Matlab) for database link with surface water and geological model, ArcGIS Model for hydrogeologic data processing for groundwater model input, a 3D geological model, surface water/groundwater models, energy resource development systems model, as well as a web-based geo-spatial infrastructure for data exploration, visualization and dissemination. This research will have broad impacts of the devel- opment of the oil shale resources in the US. The geodatabase provides a “baseline” data for fur- ther study of the oil shale development and identification of further data collection needs. The 3D geological model provides better understanding through data interpolation and visualization techniques of the Piceance Basin structure spatial distribution of the oil shale resources. The sur- face water/groundwater models quantify the water shortage and better understanding the spatial distribution of the available water resources. The energy resource development systems model reveals the phase shift of water usage and the oil shale production, which will facilitate better planning for oil shale development. Detailed descriptions about the key findings from the project activity, major accomplishments, and expected impacts of the research will be given in the sec- tion of “ACCOMPLISHMENTS, RESULTS, AND DISCUSSION” of this report.« less
Idea Project Final Report, Driver-Adaptive Warning System
DOT National Transportation Integrated Search
1995-03-31
THIS INVESTIGATION WAS COMPLETED AS PART OF THE ITS-IDEA PROGRAM, WHICH IS ONE OF THREE IDEA PROGRAMS MANAGED BY THE TRANSPORTATION RESEARCH BOARD (TRB) TO FOSTER INNOVATIONS IN SURFACE TRANSPORTATION. IT FOCUSES ON PRODUCTS AND RESULTS FOR THE DEVEL...
Three-dimensional modeling of flexible pavements : research implementation plan.
DOT National Transportation Integrated Search
2006-02-14
Many of the asphalt pavement analysis programs are based on linear elastic models. A linear viscoelastic models : would be superior to linear elastic models for analyzing the response of asphalt concrete pavements to loads. There : is a need to devel...
Extensive genetic diversity present within North American switchgrass germplasm
USDA-ARS?s Scientific Manuscript database
Switchgrass (Panicum virgatum L.) is a perennial, native North American grass currently grown for ecological restoration and forage purposes that has potential as a biofuel feedstock crop. Understanding the genetic diversity of switchgrass can provide insight into allelic variants important in devel...
SeqAPASS: Predicting chemical susceptibility to threatened/endangered species
Conservation of a molecular target across species can be used as a line-of-evidence to predict the likelihood of chemical susceptibility. The web-based Sequence Alignment to Predict Across Species Susceptibility (SeqAPASS; https://seqapass.epa.gov/seqapass/) application was devel...
A simple test procedure for evaluating low temperature crack resistance of asphalt concrete.
DOT National Transportation Integrated Search
2009-11-01
The current means of evaluating the low temperature cracking resistance of HMA relies on extensive test : methods that require assumptions about material behaviors and the use of complicated loading equipment. The purpose : of this study was to devel...
DOT National Transportation Integrated Search
2003-06-10
Geographic information systems (GIS) manipulate, analyze, and graphically present an array of information associated with geographic locations, have been invaluable to all levels of government. The federal government has long been attempting to devel...
Idea Project Final Report, Autoalert: Automated Acoustic Detection Of Incidents
DOT National Transportation Integrated Search
1995-12-26
THIS INVESTIGATION WAS COMPLETED AS PART OF THE ITS-IDEA PROGRAM, WHICH IS ONE OF THREE IDEA PROGRAMS MANAGED BY THE TRANSPORTATION RESEARCH BOARD (TRB) TO FOSTER INNOVATIONS IN SURFACE TRANSPORTATION. IT FOCUSES ON PRODUCTS AND RESULTS FOR THE DEVEL...
Meteorological Processes Affecting Air Quality – Research and Model Development Needs
Meteorology modeling is an important component of air quality modeling systems that defines the physical and dynamical environment for atmospheric chemistry. The meteorology models used for air quality applications are based on numerical weather prediction models that were devel...
Idea Project Final Report, An Improved Metropolitan Area Transportation System (Imats)
DOT National Transportation Integrated Search
1995-01-20
THIS INVESTIGATION WAS COMPLETED AS PART OF THE ITS-IDEA PROGRAM, WHICH IS ONE OF THREE IDEA PROGRAMS MANAGED BY THE TRANSPORTATION RESEARCH BOARD (TRB) TO FOSTER INNOVATIONS IN SURFACE TRANSPORTATION. IT FOCUSES ON PRODUCTS AND RESULTS FOR THE DEVEL...
USDA-ARS?s Scientific Manuscript database
This chapter discusses the history of the development of quality control tchnology, the principles and philosophy of assessing insect quality, and the relative importance of the various parameters used to assess insect quality in the context of mass-rearing for the SIT. Quality control is most devel...
Development of a 670 GHz Extended Interaction Klystron Power Amplifier
2011-03-01
Klystron Power Amplifier 5a. CONTRACT NUMBER 5b. GRANT NUMBER 5c. PROGRAM ELEMENT NUMBER 6. AUTHOR( S ) 5d. PROJECT NUMBER 5e. TASK NUMBER 5f. WORK UNIT...avelengths,” /40/EIK%20Tec W%20Wavelen oyski, R. Dobbs, act, High Power ction Klystron ,” Conf., Montere opments to the M or Modeling Cod 2005). ic...Research Projects Agency or the Department of Defense. Development of a 670 GHz Extended Interaction Klystron Power Amplifier David Chernin Science
1981-11-01
do not use program data during demand dpvel opment and subsequent sulpport periods- however, l,4Lngl. ?ep nent iaI smfot hi ug is applied . , P I orio...that DIA’s use of pr.g rain d, could bc Improved as foltlowe: (a) 1)rogram oriented items could b(, ident ified and procedures applied :or -mrlm.ditie...been promni sing i n imulat ion tests. If DFS(,-s new est imator proves sccec’sft I, it will he applIed to other DLA commodities. 5 . iter (rouping for
Wen, Bo; Xu, Shaohang; Sheynkman, Gloria M; Feng, Qiang; Lin, Liang; Wang, Quanhui; Xu, Xun; Wang, Jun; Liu, Siqi
2014-11-01
Single nucleotide variations (SNVs) located within a reading frame can result in single amino acid polymorphisms (SAPs), leading to alteration of the corresponding amino acid sequence as well as function of a protein. Accurate detection of SAPs is an important issue in proteomic analysis at the experimental and bioinformatic level. Herein, we present sapFinder, an R software package, for detection of the variant peptides based on tandem mass spectrometry (MS/MS)-based proteomics data. This package automates the construction of variation-associated databases from public SNV repositories or sample-specific next-generation sequencing (NGS) data and the identification of SAPs through database searching, post-processing and generation of HTML-based report with visualized interface. sapFinder is implemented as a Bioconductor package in R. The package and the vignette can be downloaded at http://bioconductor.org/packages/devel/bioc/html/sapFinder.html and are provided under a GPL-2 license. © The Author 2014. Published by Oxford University Press. All rights reserved. For Permissions, please e-mail: journals.permissions@oup.com.
Interaction between Soil Moisture and Air Temperature in the Mississippi River Basin
Increasing air temperatures are expected to continue in the future. The relation between soil moisture and near surface air temperature is significant for climate change and climate extremes. Evaluation of the relations between soil moisture and temperature was performed by devel...
An Assessment of Future Demands for and Benefits of Public Transit Services in Tennessee
DOT National Transportation Integrated Search
2002-03-01
This report documents results from a study carried out by Oak Ridge National Laboratory and the University of Tennessee at Knoxville for the Office of Public Transportation, Tennessee Department of Transportation. The study team was tasked with devel...
Optimization of Whole-body Zebrafish Sectioning Methods for Mass Spectrometry Imaging
Mass spectrometry imaging (MSI) methods and protocols have become widely adapted to a variety of tissues and species. However, the MSI literature lacks information on whole-body cryosection preparation for the zebrafish (ZF; Danio rerio), a model organism routinely used in devel...
USDA-ARS?s Scientific Manuscript database
Unregulated use of growth promoting antibiotics like Tetracyclines in agricultural feeds is becoming an increasing problem in antibiotic resistance. Undigested antibiotics leads to significant concentrations in livestock waste. These concentrations provide continuous selection pressure for the devel...
Novel Methods for Mosquito Control using RNAi.
USDA-ARS?s Scientific Manuscript database
The discovery and development of novel insecticides for vector control is a primary focus of toxicology research conducted at the Mosquito and Fly Research Unit, Gainesville, FL. Targeting critical genes/proteins in mosquitoes using RNA interference (RNAi) is being investigated as a method to devel...
EPA Office of Research and Development - I/I Research Information Update
The Nation’s sanitary sewer infrastructure is aging, and is currently one of the top national water program priorities. The U.S. Environmental Protection Agency (EPA) developed the Sanitary Sewer Overflow Analysis and Planning (SSOAP) Toolbox to assist communities in devel...
AN ECOLOGICAL PERSPECTIVE OF GENOMICS: ASSESSING ECOLOGICAL RISK THROUGH PARTNERSHIPS
A workshop attended by approximately 60 scientists from around the world met to discuss the application of new molecular biology tools to issues in environmental toxicology and chemistry. With the sequencing of the human genome, development of microarrays and DNA chips, and devel...
Commercial thermal process for inactivating Salmonella Poona on surfaces of whole fresh cantaloupes
USDA-ARS?s Scientific Manuscript database
Outbreaks of salmonellosis by Salmonella Poona and listeriosis by Listeria monocytogenes have been associated with the consumption of cantaloupes. Commercial washing processes for cantaloupes are limited in their ability to inactivate and/or remove these human pathogens. Our objective was to devel...
Susceptibility of a North American Culex quinquefasciatus to Japanese encephalitis virus
USDA-ARS?s Scientific Manuscript database
Japanese encephalitis virus (JEV) is a flavivirus that is transmitted by Culex (Cx.) tritaeniorhynchus in tropical and subtropical regions of Asia. The endemic transmission cycle involves domestic pigs and avian species that serve as amplification hosts; humans are incidental hosts that cannot devel...
Corn response and soil nutrient concentration from subsurface application of poultry litter
USDA-ARS?s Scientific Manuscript database
Nitrogen fertilizer management is vital to corn (Zea mays L.) production from financial and environmental perspectives. Poultry litter as a nutrient source in this cropping system is generally surface broadcast, potentially causing volatilization of NH3. Recently a new application method was devel...
HEDS - EPA DATABASE SYSTEM FOR PUBLIC ACCESS TO HUMAN EXPOSURE DATA
Human Exposure Database System (HEDS) is an Internet-based system developed to provide public access to human-exposure-related data from studies conducted by EPA's National Exposure Research Laboratory (NERL). HEDS was designed to work with the EPA Office of Research and Devel...
The etiology and impacts of human exposure to environmental pathogens are of major concern worldwide and, thus, the ability to assess exposure and infections using cost effective, high-throughput approaches would be indispensable. The principal objective of this work is to devel...
Understanding the biological effects of exposures to chemicals in the environment relies on classical methods and emerging technologies in the areas of genomics, proteomics, and metabonomics. Linkages between the historical and newer toxicological tools are currently being devel...
Developing a New Field-Validated Methodology for Landfill Methane Emissions in California
USDA-ARS?s Scientific Manuscript database
This project was initiated in the US by the California Energy Commission (CEC) in cooperation with the California Integrated Waste Management Board (CIWMB) to develop improved methods for landfill methane emissions for the California greenhouse gas inventory. This 3-year project (2007-2010) is devel...
Environmental parameters associated with stable fly development at hay feeding sites
USDA-ARS?s Scientific Manuscript database
Substrates composed of hay residues, dung, and urine accumulate around winter hay feeding sites in cattle pastures providing developmental habitat for stable flies. The objective of this study was to relate physiochemical and microbial properties of this substrate to the presence or absence of devel...
Rapid Field Measurement of Rubber Content in Russian Dandelion
USDA-ARS?s Scientific Manuscript database
Natural rubber is a critical and strategic raw material for industrial manufacturing and national defense. In 2008, 10 million tons of NR were produced for commercial use, most of it from Hevea brasiliensis in tropical countries. The annual US import deficit for NR is approximately $1 billion. Devel...
Ecological periodic tables for bentkhic macrofauna and nekton usage in estuarine habitats
In his presidential address to the British Ecological Society, T.R.E. Southwood (1977: Habitat, the templet for ecological strategies? Journal of Animal Ecology 46: 337-365; http://www.jstor.org/stable/3817) compared the situation in ecology to that in chemistry before the devel...
TEST REPORT FOR THE TRIAL BURN OF DINOSEB IN A PILOT-SCALE INCINERATOR
The U.S. Environmental Protection Agency (EPA) has determined that the herbicide Dinoseb represents a significant human health hazard. PA estimates that there are approximately 5 million gallons affected by this action. As part of a program by the EPA Office of Research and Devel...
USDA-ARS?s Scientific Manuscript database
Recent advances in DNA sequencing technologies have revolutionized the way we study bacterial biological control strains. These advances have provided the ability to rapidily characterize the secondary metabolite potential of these bacterial strains. A variety of bioinformatics tools have been devel...
Many EPA programs, including those under the Resource Conservation and Recovery Act (RCRA) and the Comprehensive Response, Compensation, and Liability Act (CERCLA), require subsurface characterization and monitoring to detect ground-water contamination and provide data to devel...
DOT National Transportation Integrated Search
1980-04-01
The Highway Safety Acts of 1973 and 1976, and the Surface Transportation Assistance Act of 1978, provide funds to individual states to improve safety at public rail-highway crossings. The report was undertaken in support of a U.S. DOT effort to devel...
USDA-ARS?s Scientific Manuscript database
There are few data available on the effect of micronutrient (MN) supplementation interventions during pregnancy/lactation on breast milk (BM) MN concentrations. Exclusive breast feeding is recommended fort 6mo and BM-MN concentrations are important determinants of infant MN status, growth and devel...
USDA-ARS?s Scientific Manuscript database
The limited availability of alternative foods to replace natural prey hinders cost-effective mass production of ladybird beetles for augmentative biological control. We compared the effects of powdered versus whole Artemia franciscana (brine shrimp) eggs with or without a dietary supplement on devel...
Body fat mass of exclusively breastfed infants born to overweight mothers
USDA-ARS?s Scientific Manuscript database
Although there is evidence that maternal prepregnancy obesity (body mass index [BMI; calculated as kg/m2] =30) results in elevated risk of obesity in the offspring later in life, maternal prepregnancy overweight (BMI 25 to 29.9) has not been clearly demonstrated as a risk factor for the future devel...
DOT National Transportation Integrated Search
2016-10-01
The objective of this study is to review the status quo in the development of autonomous vehicles and determine : what regulatory action needs to be taken that will permit their safe introduction in : Louisiana while not stifling innovation and devel...
A Climate Resilience Screening Index is being developed that is applicable at multiple scales for the United States. Those scales include national, state, county and community. The index will be applied at the first three scales and at selected communities. The index was devel...
A Climate Resilience Screening Index is being developed that is applicable at multiple scales for the United States. Those scales include national, state, county and community. The index will be applied at the first three scales and at selected communities. The index was devel...
Archiving for Rosetta: Lessons for IPDA
NASA Astrophysics Data System (ADS)
Heather, David
The Rosetta Project is unusual, possibly unique, in that all data must be archived both in NASA's Planetary Data System (PDS), and in ESA's Planetary Science Archive (PSA), ac-cording to an inter-agency agreement that predates the existence of ESA's PSA. This requires that all data are formatted according to NASA's PDS3 Standards. Scientific peer reviews of the data content for Rosetta have been carried out both in the US and in Europe and there was a very large overlap of the issues raised, illustrating the general scientific agreement, independent of geography, in what an archive must contain to be useful to the broader community of planetary scientists. However, validation of the data against the PDS Standards using both PSA and PDS devel-oped software has led to the discovery that many of the items that are validated are unstated assumptions in the written PDS Standards and are related, at least in large part, to how the two archiving systems operate rather than to the actual content that a scientist needs to use the data. The talk will illustrate some of these discrepancies with examples and suggest how to avoid such issues in future, optimizing the scientific return on the investment in archiving while minimizing the costs.
Analysis Of The IJCNN 2011 UTL Challenge
2012-01-13
large datasets from various application domains: handwriting recognition, image recognition, video processing, text processing, and ecology. The goal...validation and final evaluation sets consist of 4096 examples each. Dataset Domain Features Sparsity Devel. Transf. AVICENNA Handwriting 120 0% 150205...documents [3]. Transfer learning methods could accelerate the application of handwriting recognizers to historical manuscript by reducing the need for
USDA-ARS?s Scientific Manuscript database
Carrot is one of the most economically important vegetables worldwide, however, genetic and genomic resources supporting carrot breeding remain limited. We developed a Diversity Arrays Technology (DArT) platform for wild and cultivated carrot and used it to investigate genetic diversity and to devel...
Analysis of the IJCNN 2011 UTL Challenge
2012-01-13
large datasets from various application domains: handwriting recognition, image recognition, video processing, text processing, and ecology. The goal...http //clopinet.com/ul). We made available large datasets from various application domains handwriting recognition, image recognition, video...evaluation sets consist of 4096 examples each. Dataset Domain Features Sparsity Devel. Transf. AVICENNA Handwriting 120 0% 150205 50000 HARRY Video 5000 98.1
U.S. Naval Forces, Vietnam Monthly Historical Summary for May 1969
1969-06-01
were killed andla sanpans were destroyed. There were no U.S. casualties. Two targets of opportunity Wm , tan under fire by OV- lQA air- craft of TU...civilian, vol-=tary agencies 5;.- Average per-tent of self-help by M, civilians so *h Dy ftaenaitures (VIM~ "Econonic Devel.oprAnt 289 145,233 . - Education
USDA-ARS?s Scientific Manuscript database
Foot-and-mouth disease (FMD) is one of the most contagious viral diseases that can affect cloven-hoofed livestock and wild animals. Outbreaks of FMD have caused devastating economic losses and the slaughter of millions of animals in many regions of the world affecting the food chain and global devel...
USDA-ARS?s Scientific Manuscript database
The advantages of using molecular markers in modern genebanks are well documented. They are commonly used to understand the distribution of genetic diversity in populations and among species which is crucial for efficient management and effective utilization of the collections. We describe the devel...
“FEST-C 1.0 for CMAQ Bi-directional NH3 Modeling and Apatial Allocator 4.1”
Accurate estimation of ammonia emissions in space and time has been a challenge in meso-scale air quality modeling. For instance, fertilizer applications vary in the date of application and amount by crop types and geographical area. With the support of the U.S EPA, we have devel...
DOE Office of Scientific and Technical Information (OSTI.GOV)
Klise, Katherine A.; Siirola, John Daniel; Hart, David
The Water Security Toolkit (WST) is a suite of open source software tools that can be used by water utilities to create response strategies to reduce the impact of contamination in a water distribution network . WST includes hydraulic and water quality modeling software , optimizati on methodologies , and visualization tools to identify: (1) sensor locations to detect contamination, (2) locations in the network in which the contamination was introduced, (3) hydrants to remove contaminated water from the distribution system, (4) locations in the network to inject decontamination agents to inactivate, remove, or destroy contaminants, (5) locations in themore » network to take grab sample s to help identify the source of contamination and (6) valves to close in order to isolate contaminate d areas of the network. This user manual describes the different components of WST , along w ith examples and case studies. License Notice The Water Security Toolkit (WST) v.1.2 Copyright c 2012 Sandia Corporation. Under the terms of Contract DE-AC04-94AL85000, there is a non-exclusive license for use of this work by or on behalf of the U.S. government. This software is distributed under the Revised BSD License (see below). In addition, WST leverages a variety of third-party software packages, which have separate licensing policies: Acro Revised BSD License argparse Python Software Foundation License Boost Boost Software License Coopr Revised BSD License Coverage BSD License Distribute Python Software Foundation License / Zope Public License EPANET Public Domain EPANET-ERD Revised BSD License EPANET-MSX GNU Lesser General Public License (LGPL) v.3 gcovr Revised BSD License GRASP AT&T Commercial License for noncommercial use; includes randomsample and sideconstraints executable files LZMA SDK Public Domain nose GNU Lesser General Public License (LGPL) v.2.1 ordereddict MIT License pip MIT License PLY BSD License PyEPANET Revised BSD License Pyro MIT License PyUtilib Revised BSD License PyYAML MIT License runpy2 Python Software Foundation License setuptools Python Software Foundation License / Zope Public License six MIT License TinyXML zlib License unittest2 BSD License Utilib Revised BSD License virtualenv MIT License Vol Common Public License vpykit Revised BSD License Additionally, some precompiled WST binary distributions might bundle other third-party executables files: Coliny Revised BSD License (part of Acro project) Dakota GNU Lesser General Public License (LGPL) v.2.1 PICO Revised BSD License (part of Acro project) i Revised BSD License Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following conditions are met: * Redistributions of source code must retain the above copyright notice, this list of conditions and the following disclaimer. * Redistributions in binary form must reproduce the above copyright notice, this list of conditions and the following disclaimer in the documentation and/or other materials provided with the distribution. * Neither the name of Sandia National Laboratories nor Sandia Corporation nor the names of its con- tributors may be used to endorse or promote products derived from this software without specific prior written permission. THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IM- PLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL SANDIA CORPORATION BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUD- ING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. ii Acknowledgements This work was supported by the U.S. Environmental Protection Agency through its Office of Research and Development (Interagency Agreement # DW8992192801). The material in this document has been subject to technical and policy review by the U.S. EPA, and approved for publication. The views expressed by individual authors, however, are their own, and do not necessarily reflect those of the U.S. Environmental Protection Agency. Mention of trade names, products, or services does not convey official U.S. EPA approval, endorsement, or recommendation. The Water Security Toolkit is an extension of the Threat Ensemble Vulnerability Assessment-Sensor Place- ment Optimization Tool (TEVA-SPOT), which was also developed with funding from the U.S. Environ- mental Protection Agency through its Office of Research and Development (Interagency Agreement # DW8992192801). The authors acknowledge the following individuals for their contributions to the devel- opment of TEVA-SPOT: Jonathan Berry (Sandia National Laboratories), Erik Boman (Sandia National Laboratories), Lee Ann Riesen (Sandia National Laboratories), James Uber (University of Cincinnati), and Jean-Paul Watson (Sandia National Laboratories). iii Acronyms ATUS American Time-Use Survey BLAS Basic linear algebra sub-routines CFU Colony-forming unit CVAR Conditional value at risk CWS Contamination warning system EA Evolutionary algorithm EDS Event detection system EPA U.S. Environmental Protection Agency EC Extent of Contamination ERD EPANET results database file GLPK GNU Linear Programming Kit GRASP Greedy randomized adaptive sampling process HEX Hexadecimal HTML HyperText markup language INP EPANET input file LP Linear program MC Mass consumed MILP Mixed integer linear program MIP Mixed integer program MSX Multi-species extension for EPANET NFD Number of failed detections NS Number of sensors NZD Non-zero demand PD Population dosed PE Population exposed PK Population killed TAI Threat assessment input file TCE Tailed-conditioned expectation TD Time to detection TEC Timed extent of contamination TEVA Threat ensemble vulnerability assessment TSB Tryptic soy broth TSG Threat scenario generation file TSI Threat simulation input file VAR Value at risk VC Volume consumed WST Water Security Toolkit YML YAML configuration file format for WST iv Symbols Notation Definition Example { , } set brackets { 1,2,3 } means a set containing the values 1,2, and 3. [?] is an element of s [?] S means that s is an element of the set S . [?] for all s = 1 [?] s [?] S means that the statement s = 1 is true for all s in set S . P summation P n i =1 s i means s 1 + s 2 + * * * + s n . \\ set minus S \\ T means the set that contains all those elements of S that are not in set T . %7C given %7C is used to define conditional probability. P ( s %7C t ) means the prob- ability of s occurring given that t occurs. %7C ... %7C cardinality Cardinality of a set is the number of elements of the set. If set S = { 2,4,6 } , then %7C S %7C = 3. v« less
1987-11-03
external sources to hog and sheep embryos, creating optimistic prospects for raising livestock and poultry output and quality. British scientists...development in such areras as devel- oping crop, livestock, and poultry breeding, agricultural resource survey and analysis, plant disease and insect...are unfa- vorable for the deployment of large troop formations, to blindly stress "killing a chicken with a butcher knife" is bound to cause an
Draft SEI Program Plans: 1994-1998
1993-08-01
process must depersonalize risks so they are viewed as opportunities for program success. Factors for communication are in all the method devel...and the undergraduate level to adequately prepare new soft- ware engineers entering the work force. Educators and trainers of current professionals...learning opportu- nities. The technical foundation for many of these products is the evolving SEI model curricula for graduate and undergraduate degree
Correlated Attack Modeling (CAM)
2003-10-01
describing attack models to a scenario recognition engine, a prototype of such an engine was developed, using components of the EMERALD intrusion...content. Results – The attacker gains information enabling remote access to database (i.e., privileged login information, database layout to allow...engine that uses attack specifications written in CAML. The implementation integrates two advanced technologies devel- oped in the EMERALD program [27, 31
Atigeo at TREC 2014 Clinical Decision Support Task
2014-11-01
suffered from chronic menorrhagia was started on triptorelin , a gonad- otrophin-releasing hormone analogue. Three days later, she developed...rhagia was started on triptorelin , a gonadotrophin-releasing hormone ana- logue. Three days later, she devel- oped gradually worsening headaches...A 43-year-old Caucasian wom- an who suffered from chronic menor- rhagia was started on triptorelin , a gonadotrophin-releasing hormone ana- logue
1988-12-01
argument schema based on the one devel- oped by Toulmin et al. (1984). In Toulmin’s schema (Figure 4-2), a claim, or 3 conclusion whose merits we are seeking...probability judgment. Cognitive Science, 1985, 9, 309-339. Toulmin , S., Rieke, R., and Janik, A. An introduction to reasoning (2nd Edition). NY
Control of Hemotropic Diseases of Dogs.
1977-12-31
isolant. Inoculated dogs develo- ped signs of the disease which included fever , weight loss, lym- phodenopathy, corneal opacity, and pancytopenia. Of...in Alsatian dogs infected with E. canis, was not seen in thesedogs; however, 2 dogs devel- oped cutaneous petechial and ecchymotic hemorrhages at...included fever , weight loss, lymphadenopathy, - -- 19 corneal opacity, and pancytopenia. Of 3 dogs that died during the course of the study, one died with
NASA Astrophysics Data System (ADS)
Murdin, P.
2000-11-01
German space travel visionary, born in Sibiu, Hungary. His book Die Rakete zu den Planetenrämen (The Rocket into Interplanetary Space), established his reputation in 1923, and he became president of the German Society for Space Travel. In the Second World War he worked on rockets at Peenemünde, and went with WERNHER VON BRAUN to the US Army Ballistic Missile Agency in Huntsville, Alabama to devel...
Navy Manpower Planning and Programming: Basis for Systems Examination
1974-10-01
IRE5EARCH AND DEVEl. INAVAL RESEARCH] CHIEF OF NAVAL OPERATIONS OFFICE CHIIf OF NAVAL OPERATIONS NAVAL MATERIAL COMMAND •LitMARTERS NAVAL MATERIAL...DIVISION COMPENSATION BRANCH MANPOWER PROGRAMMING ■RANCH JOURNAL/TRADE TALK BRANCH 06A ASSISTANT FOR COMPUTER SCIENCES SYSTEMS DEVELOPMENT BRANCH...Assistant Director, Life Sciences , Air Force Office of Scientific Research Technical Library, Air Force Human Resources Laboratory, Lackland Air Force Base
Multi-Objective UAV Mission Planning Using Evolutionary Computation
2008-03-01
on a Solution Space. . . . . . . . . . . . . . . . . . . . 41 4.3. Crowding distance calculation. Dark points are non-dominated solutions. [14...SPEA2 was devel- oped by Zitzler [64] as an improvement to the original SPEA algorithm [65]. SPEA2 Figure 4.3: Crowding distance calculation. Dark ...thesis, Los Angeles, CA, USA, 2003. Adviser-Maja J. Mataric . 114 21. Homberger, Joerg and Hermann Gehring. “Two Evolutionary Metaheuristics for the
Review of Radioisotopes as Radiological Weapons
2016-06-01
doses of radiation . Two of the woodsmen devel- oped serious symptoms of Acute Radiation Syndrome (ARS) and beta radiation burns that required...or organs). Absorbed dose is usually defined as energy deposited (joule) per unit of mass (kilogram). See gray and rad. Acute Radiation Syndrome ...AI alveolar-interstitial ALARA as low as reasonably achievable ARS Acute Radiation Syndrome Bq becquerel C Activity of Concern CDC Centers for
USDA-ARS?s Scientific Manuscript database
Cotton is one of the major crops cultivated in the Texas Rolling Plains region and it is a major contributor to the regional economy. Cotton cultivation in this region is facing severe challenges due to the increase in the frequency of droughts and projected decrease in rainfall in the future. Devel...
Arthropods: Vectors of Disease Agents
1994-07-01
vector or glands in the tick legs. Filarid in some tick species, individuals of be passively regurgitated during worms (eg, dog heartworm) devel- which...Australia and an arthropod serves as the vector passively regurgitated during blood- Antarctica. An estimated 50 million transferring the etiologic agent...opossums, Biological ɝ More common in racoons, armadillos dogs than people Garbage, sewage, etc Mechanical NA I akwoator% %ledionc %.j. 2i, \\.I
1994-09-01
NRCCLDIAF N’~ Flood r-ntrol Channels Research Misce~lanm’us P.3per HL-94-4 arid De ’ opment Program Septernber 1994 Streams Above the Line: Channel IR...be used for advertiwing, pubhCaton, or pronmonal purposes. Citation of tra~ de names does rnot consttuC an official erndorsemterz or approvali for ehc...discharge, and cc. iain inferences are dr-awn,. Othur topIics disCu-sse ’rieLyV ilu~ de : relationships of’Iplanform type- to gradient and bed-material size
Advanced Materials Deposition for Semiconductor Nanostructures Using Supercritical Fluids
2007-04-01
thickness. Various shapes can be devel- obtained from water-in-hexanes microemulsionr:* usl rig a. end:t• ; im in tickness V molar ratio of the reducing...carbon dioxide and supported on multi- detection for aminoaromatics in soil has been reported.’ This walled carbon nanotubes. These aminoaromatics are...explosive vapors rather derivatizing agents such as fluorescamine. Corrected spectra for these than soil or ground water samples, most matrix and
1981-07-01
conditional, fault-isolation approach of the con- Data Base Requirements tent expert, photographs of normal and abnormal symp- The content-expert may...59 THE AUTOMATED INTERGRATION OF TRAINING AND AIDING INFORMATION FOR THE OPERATOR/TECHNICIAN Dr. Douglas Towne...Subsystem approach devel- until this Third Biennial Conference oped by the Air Force in the 1960’s for us to call a meeting devoted to integrate Human
Moving Horizon Estimation on a Chip
2014-06-26
description, e.g. VHDL or Verilog, for FPGA implementation . Especially for those whose main expertise is in control system design, writing algorithms in C...ditional Kalman Filter(KF) where recursive solution is available. We devel- oped various MHE designs and implemented them on the Xilinx Zynq ZC702 FPGA...practical deployment of the MHE technology. 2.2 Implementation of MHE on FPGA The next paper demonstrated the feasibility of implementing MHE algo
JPRS Report, Science & Technology China: Energy
1992-09-23
combined actual models and math - ematical models to conduct the research and established a total of nine actual models with boundary conditions supplied...10,000 ton-grade flotillas after the Three Gorges project is completed. Simulation experiments of actual passage of 10,000 ton-grade flotillas at...excavate the deep trench for the core wall of the weir for the second phase. Concrete tank cars, spreaders, and other equipment were also devel- oped
2010-06-01
a storytelling narrative of how the risk was mitigated and what worked or did not work. A knowledge-based risk is also a means of transferring...devel- oping a cadre of trained facilitators to assist teams in using Web-based deci- sion-support technology to support team brain - storming...and use “contextualization” (a.k.a. storytelling ) as an alternative method to analysis? Storytelling Instead of Analysis There have been some
European Science Notes. Volume 40, Number 6.
1986-06-01
34 ing section. preparation method for technical alco- hol, a modified upflow fermenter was Biotechnology constructed in which, among other In its research...Division of Technology for analysis and control program was devel- Society has achieved some interesting oped for research with this fermenter results...use in basic research studies and in tinuous production of ethanol in a assay procedures. fermenter using Z. h., one of the The organ and bone marrow
Resource Control in Large-Scale Mobile-Agents Systems
2005-07-01
wakeup node schedule , much energy can be conserved. We also designed several protocols for global clock synchronization. The most interesting one is...choice as to which remote hosts to visit and in which order. Scheduling mobile-agent migration in a way that minimizes bandwidth and other resource...use, therefore, is both feasible and attractive. Dartmouth considered several variations of the scheduling problem, and devel- oped an algorithm for
ONRASIA Scientific Information Bulletin, Volume 16, Number 1
1991-03-01
be expressed naturally in an and hence the programs produced by pline. They range from computing the algebraic language such as Fortran, these efforts...years devel- gram an iterative scheme to solve the function satisfies oping vectorizing compilers for Hitachi. problem. This is quite natural to do in...for it ential equations to be expressed in a on the plate, with 0,=1 at the outside to compile into efficient vectorizable natural mathematical syntax
2005-06-01
company has devel- oped an exciting prototype technology: … that lets users of PDAs and similar mobile devices put data into their handheld systems...for a class of small, easily carried electronic devices used to store and retrieve infor- mation” [2], were at one time viewed as lit- tle more than...some of the many ways that PDA technology is currently being used within the DoD: • The Pocket-Sized Forward Entry Device (PFED) is a ruggedized PDA
TQL in the Fleet: From Theory to Practice
1993-10-01
SUMMARY Overview O ver the past year , the Department of the Navy Total Quality Leadership Office (DON TQL Office) has been interviewing members of the...the Fleet: From Theory to Practice ix OVERVIEW ) ver the past year , the Department of the Navy Total Quality Leadership Office (DON TQL Office) has...in technical and of Naval Education and Training (CNET) in devel- military journals and deliver papers at conferences oping a TQL curriculum and in
The Ubuntu Chat Corpus for Multiparticipant Chat Analysis
2013-03-01
Intelligence (www.aaai.org). All rights reserved. the # LINUX corpus (Elsner and Charniak 2010), and the #IPHONE/#PHYSICS/#PYTHON corpus (Adams 2008). For many...made publicly available, making it difficult to comparatively evaluate dif- ferent techniques. Corpus Description Ubuntu, a Linux -based operating...Kubuntu (Ubuntu with KDE ) support #ubuntu-devel 2 112 074 12 140 53.7 2004-10-01 Developmental team coordination #ubuntu+1 1 621 680 26 805 52.6 2007-04-04
Biomolecular Principles of Matrix Assembly Related to Fracture Resistance
2013-06-24
homologous to both elastin and spider dragline silk protein elastomeric repeats.18,19 The second is a conformationally labile 20 AA Pro, Asn-rich...Katoh-Fukui, Y., et al., (1991) Devel. Biol. 145, 201-202. 18. Xu, G., Evans, J.S. (1999) Biopolymers 49, 303-312. 19. Zhang, B., Xu, G., Evans...J.S. (2000) Biopolymers 54, 464-475. 20. Gebauer, D., Volkel, A., Coelfen, H. (2008) Science 322, 1819-1822. 21. Gebauer, D., Coelfen, H. (2011) Nano
The Nation Builders: A Sesquicentennial History of the Corps of Topographical Engineers, 1838 - 1863
1988-06-01
Archimedes ................. 40 John McClellan’s Plan for Cribwork ............ 42 Buffalo Harbor ....................... 43 James D. Graham...Graham’s 1854 report. The screw - pile lighthouse is an example of early iron truss technology. It was devel- oped in England and imported by the Army...While on the West Coast, he invented a fog signal based on a locomotive steam whistle. Air forced through a pipe by the rush of seawater made the
1982-11-01
8217~ INTRODUCTION Since motion is perceived through stimulation of several physiological rec~ptor systems (visual, vestibular, haptic and auditory ), ~any...scenario. C? in battle is highly stressing. There- fore, a training simulator must stimulate the players both physically and mentally. On the physical...development of the concepts used today began in the early 70s Raytheon devel- oped a system that could stimulate the actual ship’s sonar system
JPRS Report, Soviet Union, World Economy & International Relations, No. 9 September 1987
1988-01-12
states have if in addition to the growing competition of beet sugar they are forced to reckon with the fact that today even corn sweeteners...policy of pressure. The reality today is such that (as graphically demon- strated at the Cancun meeting in 1981) the U.S. Admin- istration and, in ...markets of devel- oped capitalist countries no longer justify themselves as a means of competitive struggle and an increase in currency earnings. What
2012-08-01
est honor, to Manuel Marulanda (aka Tirofijo, or Sure Shot), the FARC’s supreme commander at the time.100 The government of Rafael Correa in Ecuador ... governments sanctioned criminal activities as part of coherent, mul- tistate instruments of statecraft. This monograph synthesizes research on such...criminalized states in Latin America. It documents how, through the growing alliance with Iran and other external actors, these governments have devel
JPRS Report, East Asia, Korea: Kulloja, No. 10, October 1988, No. 11, November 1988.
1989-07-10
them. Because our party always stands in the van of the revolution and construction, a continuing leap forward and innovation take place in every...which is daily undergoing transfiguration makes our people solidify their faith in our party and implanting in them the conviction that a sure...functionaries becomes an urgent demand of the devel- oping reality at a time when a new transition is taking place in the development of the party and
1986-06-01
planning, trout in the Lemhi River, Idaho . The and acquisition of interests in ecological requirements of the two streams threatened with adverse devel...and its effects on insects and fish. B. C., Inst. of Fish., Vancouver. Univ. Idaho Coop. Fish. Res. Unit Bull. 17. Completion Rep. Proj. Anderson, H.W...J. Morris, ed. Symposium, Idaho . Coll. of Forestry, Wildl., ForesT Land Uses and Stream and Range Sciences, Univ. of Idaho , Environment. Oregon State
Effects of Different Distributions of Training Time on the Acquisition of Contact Flying Skills
1981-07-01
evaluate their own performance. PERCEPTION OF TRAINING. Based orn their general response to the Student Opinion Survey, the students in both programs felt...analy- sis. Dr. Jerry M. Childs and Mr. Edward Miller of Seville aided in the devel- oment of the pilot performance measurement instruments. Mr. E. Peter...J. B., Childs , J. M., Prophet, W. W., & Spears, W. L. Human factors problems in general aviation (Tech. Rep. FAA-CT-80-194). Washington, DC: Federal
Hyperkalemia After Packed Red Blood Cell Transfusion in Trauma Patients
2008-02-01
Hyperkalemia After Packed Red Blood Cell Transfusion in Trauma Patients Matthew C. Aboudara, MD, Frank P. Hurst, MD, Kevin C. Abbott, MD, and Robert...packed red blood cell (PRBC) transfusion and those who did not. Pri- mary outcome was hyperkalemia (plasma potassium level >5.5 mmol/L). Results...mmol/L, vs. 4.0 0.78 mmol/L, p < 0.001). During the study period, 38.5% of transfusion patients devel- oped hyperkalemia , versus 2.9% of those who did
Validation of Model-Based Prognostics for Pneumatic Valves in a Demonstration Testbed
2014-10-02
predict end of life ( EOL ) and remaining useful life (RUL). The approach still follows the general estimation-prediction framework devel- oped in the...atmosphere, with linearly increasing leak area. kA2leak = Cleak (16) We define valve end of life ( EOL ) through open/close time limits of the valves, as in...represents end of life ( EOL ), and ∆kE represents remaining useful life (RUL). For valves, timing requirements are provided that de- fine the maximum
2008-05-01
biological systems. In the mosquito Aedes ae- gypti (L.), a primary vector of dengue and yellow fever viruses, the role of cytochrome c during devel...development of mosquitoes re- quiresmultigene regulation(Seversonet al. 2004,Fon- tenille et al. 2005,Raibaudet al. 2006, Strodeet al. 2006, van den...1.5% RH in an environ- mental chamber (L-C Incubator, Lab-Line Instru- ments, Inc., Melrose Park, IL) for the time course study. Sixty individuals (30
2008-12-01
1 DEVELOPMENT OF ULTRASONICALLY LEVITATED DROPS AS MICROREAC- TORS FOR STUDY OF ENZYME KINETICS AND POTENTIAL AS A UNIVERSAL PORTABLE ANALYSIS...microfluidic systems are incompatible with the chemistry one wishes to study. We have devel- oped an alternative approach. We use ultrasonically levitated ...since at least the 1940’s, we are the second group to carry out enzyme reactions in levitated drops, (Weis; Nardozzi 2005) and have fab- ricated the
Cynomolgus Macaque as an Animal Model for Severe Acute Respiratory Syndrome
2006-05-01
two viruses . Both icSARS-CoV-challenged animals devel- oped radiographic disease. Of the two animals infected with wild-type virus by a mucosal route...J Virol 78: 11416–11421. 12. Martina BE, Haagmans BL, Kuiken T, Fouchier RA, Rimmelzwaan GF, et al. (2003) Virology: SARS virus infection of cats and...was discovered quite quickly—a new virus known as SARS-associated coronavirus (SARS-CoV) ( corona being a description of the virus’s spiky, crown-like
A Two-Step Approach for Producing an Ultrafine-Grain Structure in Cu-30Zn Brass (Postprint)
2015-08-13
crystallization anneal at 400 °C (0.55Tm, where Tm is the melting point ) for times ranging from 1 min to 10 hours, followed by water quenching; an additional...200 words) A two-step approach involving cryogenic rolling and subsequent recrystallization annealing was developed to produce an ultrafine-grain...b s t r a c t A two-step approach involving cryogenic rolling and subsequent recrystallization annealing was devel- oped to produce an ultrafine
2006-02-01
pneumococcal surface adhesin A, and pneumolysin in relation to pneumo- coccal carriage and acute otitis media . J. Infect. Dis. 182:1146–1152. 29. Rawlings, D...Simell, B., M. Korkeila, H. Pursiainen, T. M. Kilpi, and H. Kayhty. 2001. Pneumococcal carriage and otitis media induce salivary antibodies to pneu...children with acute otitis media . Pediatr. Infect. Dis. J. 21:186–192. 41. Soininen, A., H. Pursiainen, T. Kilpi, and H. Kayhty. 2001. Natural devel
The Collins Center Update. Volume 1, Issue 3, December 1999
1999-12-01
CDN), devel oped and executed the FORO DE ESTRATEGIA NACIONAL 2005 Hon du ras en el Siglo XXI (FEN 2005) {Na tional Strategy Forum 2005 Hon du ras...tools and processes used to make strate gic leaders. Im pressed with this program, Gover nor Pat ton requested a return visit with his en tire...wide command post and field train ing exer cise which tests and vali dates nuclear command and control, and exe cu tion proce dures. It is based on a
2014-03-01
Freedorn and Iraqi Freedotn combat injury to improve care and treatment, and prevent poor physical, psychological , and social outcomes. We describe the...and Iraqi Freedom (OEF/OIF) is the highest in tnodem history primarily because of advanced protective gear and rapid effective medical care.’^ To date...useful to assess the need for care and rehabilitation.’" ’ ’ A theoretical model of trauma and its effect on QOL, devel- oped by Sprangers and Schwartz
Evaluation of Sampling and Sample Preparation Modifications for Soil Containing Metallic Residues
2012-01-01
assessed the procedures devel- oped and adopted for energetics using USEPA Method 8330B and whether they are applicable to soils containing metals. The...initially encourage the use of MI at sites where soil is contam- inated with petroleum hydrocarbons only. However, MI sampling may be applicable to...602 793 962 974 733 723 1065 839 162 19 Mn 41 38 54 54 39 42 90 51 19 37 Pb 277 345 549 549 264 720 370 445 175 39 W 429 625 1374 1374 292 142 777
PathVisio 3: an extendable pathway analysis toolbox.
Kutmon, Martina; van Iersel, Martijn P; Bohler, Anwesha; Kelder, Thomas; Nunes, Nuno; Pico, Alexander R; Evelo, Chris T
2015-02-01
PathVisio is a commonly used pathway editor, visualization and analysis software. Biological pathways have been used by biologists for many years to describe the detailed steps in biological processes. Those powerful, visual representations help researchers to better understand, share and discuss knowledge. Since the first publication of PathVisio in 2008, the original paper was cited more than 170 times and PathVisio was used in many different biological studies. As an online editor PathVisio is also integrated in the community curated pathway database WikiPathways. Here we present the third version of PathVisio with the newest additions and improvements of the application. The core features of PathVisio are pathway drawing, advanced data visualization and pathway statistics. Additionally, PathVisio 3 introduces a new powerful extension systems that allows other developers to contribute additional functionality in form of plugins without changing the core application. PathVisio can be downloaded from http://www.pathvisio.org and in 2014 PathVisio 3 has been downloaded over 5,500 times. There are already more than 15 plugins available in the central plugin repository. PathVisio is a freely available, open-source tool published under the Apache 2.0 license (http://www.apache.org/licenses/LICENSE-2.0). It is implemented in Java and thus runs on all major operating systems. The code repository is available at http://svn.bigcat.unimaas.nl/pathvisio. The support mailing list for users is available on https://groups.google.com/forum/#!forum/wikipathways-discuss and for developers on https://groups.google.com/forum/#!forum/wikipathways-devel.
1980-05-01
ADA 0 8 56. 33 A 0 3 O Report 80 -.2 PRCEDIGSLEVE SPROCEEDINGS OF THE TWENTY - FIFTJ CONFERENCE ON THE DESIGN OF - EXPERIMENTS IN ARMY RESEARCH ...by The Army Mathematics Steering Committee o* 4.,. on Behalf of 00 -•o ~ THE CHIEF OF RESEARCH , DEVEL 6 MENT ND ACQUIS ON 003 8 T6 19 0 •3,n U. S...Army Research Office Report No. 80-2 June 1980 PROCEEDINGS OF THE TWENTY-FIFTH CONFERENCE ON THE DESIGN OF EXPERIMENTS iI Sponsored by the Army
1980-02-01
PHOTOGRAPH THIS SHEET 0 FILE P.IwLEVEL IVETRY U- AFP65,f-7YA ga- - II IDS DTIBUTION T ATEMNT A App.-ove~d for public release; Di.-tribuilon Unlinitod... PHOTOGRAPH THIS SHEET AND RETURN TO DTIC-FDAC DTIC FORM 70A DOCUMENT PROCESSING SHEET PREVIOUS EDITION MAY BE USED UNTIL MAR 86 STOCK IS EXHAUSTED. IEEE 2rd...Kolm devel- transfers momencum from a massive ch..ically diven oped the "mass driver" as part of two NASA -AMES sum- armacure to a much lighter, hi h r
Bonizzoni, Paola; Rizzi, Raffaella; Pesole, Graziano
2005-10-05
Currently available methods to predict splice sites are mainly based on the independent and progressive alignment of transcript data (mostly ESTs) to the genomic sequence. Apart from often being computationally expensive, this approach is vulnerable to several problems--hence the need to develop novel strategies. We propose a method, based on a novel multiple genome-EST alignment algorithm, for the detection of splice sites. To avoid limitations of splice sites prediction (mainly, over-predictions) due to independent single EST alignments to the genomic sequence our approach performs a multiple alignment of transcript data to the genomic sequence based on the combined analysis of all available data. We recast the problem of predicting constitutive and alternative splicing as an optimization problem, where the optimal multiple transcript alignment minimizes the number of exons and hence of splice site observations. We have implemented a splice site predictor based on this algorithm in the software tool ASPIC (Alternative Splicing PredICtion). It is distinguished from other methods based on BLAST-like tools by the incorporation of entirely new ad hoc procedures for accurate and computationally efficient transcript alignment and adopts dynamic programming for the refinement of intron boundaries. ASPIC also provides the minimal set of non-mergeable transcript isoforms compatible with the detected splicing events. The ASPIC web resource is dynamically interconnected with the Ensembl and Unigene databases and also implements an upload facility. Extensive bench marking shows that ASPIC outperforms other existing methods in the detection of novel splicing isoforms and in the minimization of over-predictions. ASPIC also requires a lower computation time for processing a single gene and an EST cluster. The ASPIC web resource is available at http://aspic.algo.disco.unimib.it/aspic-devel/.
1978-06-01
FNO GlX GJP GMO HIP HJ( 11MN ILO JLN KLb: B ABCD AC? ADO AE1 AHL A J t’ Ar*N AD? CDL CEM CON CiJ ChP CN 0 DEN DFH D1K DJ? DMO EFJ ECK EHI’ EiD FUL FIN...Westlake Village, CA 91361 II.- CoN TIro I ING OFF 1C- NAME., AN C) AP"tOFF 12 R.. POFRT o AT " Air Force Office of Scientific Research September 1977...explains the techniques devel- oped by Box and Hunter (1961) and Daniel (1962) for con - structing Resolution IV screening designs from two Resolution
DOE Office of Scientific and Technical Information (OSTI.GOV)
Keith, W.J.; King, H.D.; Gettings, M.E.
1988-01-01
The Devel's Garden lava Bed, Squaw Ridge Lava Bed, and Four Craters Lava Bed Wilderness Study Areas include approximately 70,940 acres and are underlain entirely by Pleistocene or Holocene lava flows and associated sediments. There is no evidence of hydrothermal alteration in the study areas. No resources were identified in the study areas, but there is low potential for perlite resources in the southern part of the Devil's Garden Lava Bed and the northern half of the Squaw Ridge Lava Bed areas. All three study areas have low potential for geothermal resources and for oil and gas resources.
The Berlin Exoplanet Search Telescope
NASA Astrophysics Data System (ADS)
Rauer, H.; Erikson, A.; Voss, H.; Hatzes, A.; Eisloeffel, J.
Several authors have suggested that nonlinear internal waves (solitary waves) can transport plankton over considerable distances. In this talk we present a preliminary analysis of the data collected during a 10-day long experiment in Massachusetts Bay that was specifically designed to test this hipothesys. We sampled over 15 trains of solitary waves, collecting current data with the shipboard ADCP while at the same time sampling the concentration and taxonomic distribution of plankton in the water column by means of a towed Video Plankton Recorder, which also collected hydro- graphic data. In the analisys, we compare the current data with the data from the towed instrument to test wether the waves act as concentrator. We have also devel- oped a model to asses the effect of particular behavioral responses with regard to the ability to surf the waves.
Mandić, Vjekoslav; Martinović, Vlatka; Kvesić, Ante; Bukvić, Nado; Skitarelić, Nataša; Brekalo, Zdrinko; Ivanković, Krunoslav; Šetka, Violeta
2015-03-01
A shift of the diagnostics of urological malformations towards the fetal age by means of ultrasound, especially hydronephrosis which, apart from reflux, is the most frequent developmental urological disorder, opened many dilemmas and debates. In the course of more than three decades the application of this diagnostic approach to the problem of hydrone- phrosis became a routine clinical practice in all modern clinics. In this paper we present the problems related to this diagnostic method and its delayed application in the Mostar University Clinical Hospital. Along with the exposition of a general approach to the problem of hydronephrosis we briefly present our modest collection of cases which points to the most recent trend of a vigorous medical development in this region, despite unfavorable overall conditions which prevailed so far. The observation included 56 children with prenatal, perinatal and early age determination of pyelon dilatation by means of ultrasonic exploration who were treated surgically. Of this number 32 (57.14%) were male, and 24 (42.86%) female children. Of the observed patients 56 had unilateral and 6 had bilateral pyelon dilatation so that 62 kidneys in all were observed and treated. The dilatation was determined prenatally in 24 (38.7%) out of 62 kidneys observed in all, in 7 (11.29%) the disorder was observed perinatally and in remaining 31 cases (49.9%) it manifested during early childhood, school age, even at the age of pre-puberty. Of the children with prenatally and perinatally determined dilatation, in 14 (45.16%) out of 31 (100.0%) observed kidneys the ap radius of the dilated pyelon was between 10-15 mm, and in 17 (54.84%) more than 15 mm. Along with other examinations (MAG3 and DMSA) the patients were followed-up by ultrasonic exploration of the observed kidney for 6 to 30 (average 18) months after postnatal diagnosis; the ultrasonic exploration was repeated in intervals of 6 months. Within 12 months of birth surgical intervention on the pyeloureteral junction was done on all 17 kidneys with an ap radius of the pyelon greater than 15 mm, as well as on 4 kidneys in which ap radius was between 10 and 15 mm. In other 10 kidneys with prenatally and perinatally determined ap radius of 10 to 15 mm the follow-up period was 25 to 30 months (average 275). As the examinations (ultrasound, MAG3 and DMSA) even after this period showed no signs of regression of the dilatation, nor an improvement in patency this provided an indication for surgical intervention with the aim of establishing a normal flow across the pyeloureteral junction. Antibiotic prophylaxis was not applied systematically, but in a targeted manner if the uroinfection was confirmed clinically and in the lab. Through the presentation of cases we demonstrate the relationship of earlier and more recent procedures in the treatment of hydronephrosis in the gravitational area of the Mostar University Clinical Hospital. The fact that some children were subjected to surgical treatment due to hydronephrosis at the time of pre-puberty reflects earlier views on this clinical entity. The successfulness of surgical treatment of hydronephrosis in the observed patients is complete and comparable to medically more developed environments, and our diagnostic capabilities are getting close to that level too. We specially wish to stress the recent introduction of ultrasonic examination of pregnant women and foetus in the third trimester with the aim of an early detection of anomalies and malformations of the urotract as an indicator of a marked medical devel- opment. On the global level there are still inconclusive and opposing opinions on this subject, as is seen in recent literature. The controversies relate to the diagnostics as well as to therapy.
NASA Astrophysics Data System (ADS)
Dempster, William; Allen, John P.
Closed systems are desirable for a number of purposes: space life support systems where precious life-supporting resources need to be kept inside; biospheric systems; where global ecological pro-cesses can be studied in great detail and testbeds where research topics requiring isolation from the outside (e.g. genetically modified organisms; radioisotopes) can be studied in isolation from the outside environment and where their ecological interactions and fluxes can be studied. But to achieve and maintain closure raises both engineering and ecological challenges. Engineering challenges include methods of achieving closure for structures of different materials, and devel-oping methods of allowing energy (for heating and cooling) and information transfer through the materially closed structure. Methods of calculating degree of closure include measuring degradation rates of inert trace gases introduced into the system. An allied problem is devel-oping means of locating where leaks are located so that they may be repaired and degree of closure maintained. Once closure is achieved, methods of dealing with the pressure differen-tials between inside and outside are needed: from inflatable structures which might adjust to the pressure difference to variable volume chambers attached to the life systems component. These issues are illustrated through the engineering employed at Biosphere 2, the Biosphere 2 Test Module and the Laboratory Biosphere and a discussion of methods used by other closed ecological system facility engineers. Ecological challenges include being able to handle faster cycling rates and accentuated daily and seasonal fluxes of critical life elements such as carbon dioxide, oxygen, water, macro-and mico-nutrients. The problems of achieving sustainability in closed systems for life support include how to handle atmospheric dynamics including trace gases, producing a complete human diet and recycling nutrients and maintaining soil fertility, healthy air and water and preventing the loss of crucial elements from active circulation. In biospheric facilities the challenge is also to produce analogue to natural biomes and ecosys-tems, studying processes of self-organization and adaptation in systems that allow specification or determination of state variables and cycles which may be followed through all interactions from atmosphere to soils.
Petruczynik, Anna; Wroblewski, Karol; Szultka-Mlynska, Malgorzata; Buszewsk, Boguslaw; Karakula-Juchnowicz, Hanna; Gajewski, Jacek; Morylowska-Topolska, Justyna; Waksmundzka-Hajnosi, Monika
2017-05-01
A high performance liquid chromatography (HPLC) method for simultaneous analysis of venlafaxine and its major metabolite 0-desmethylvenlafaxine and vilazodone and its methabolite M10 have been devel- oped and validated. Chromatography was performed on the Phenyl-Hexyl column with mobile phase containing methanol, acetate buffer at pH 3.5 and diethylamine. The application of stationary phase with 7r-7c moieties and mobile phase containing diethylamine as silanol blocker lets to obtain double protection against silanols and thus very high theoretical plate numbers were obtained. The good separation selectivity, good peaks' symmetry and very high systems efficiency for all investigated compounds were obtained in applied chromatographic system. The method is very efficient and suitable for the analysis of investigated drugs and their metabolites in human serum for patients' pharmacotherapy control.
Schröter, Pauline; Schroeder, Sascha
2017-12-01
With the Developmental Lexicon Project (DeveL), we present a large-scale study that was conducted to collect data on visual word recognition in German across the lifespan. A total of 800 children from Grades 1 to 6, as well as two groups of younger and older adults, participated in the study and completed a lexical decision and a naming task. We provide a database for 1,152 German words, comprising behavioral data from seven different stages of reading development, along with sublexical and lexical characteristics for all stimuli. The present article describes our motivation for this project, explains the methods we used to collect the data, and reports analyses on the reliability of our results. In addition, we explored developmental changes in three marker effects in psycholinguistic research: word length, word frequency, and orthographic similarity. The database is available online.
DOE Office of Scientific and Technical Information (OSTI.GOV)
Kuharik, J.; Madrak, R.; Makarov, A.
A second harmonic tunable RF cavity is being devel-oped for the Fermilab Booster. This device, which prom-ises reduction of the particle beam loss at the injection, transition, and extraction stages, employs perpendicularly biased garnet material for frequency tuning. The required range of the tuning is significantly wider than in previously built and tested tunable RF devices. As a result, the mag-netic field in the garnet comes fairly close to the gyromag-netic resonance line at the lower end of the frequency range. The chosen design concept of a tuner for the cavity cannot ensure uniform magnetic field in the garnet mate-rial;more » thus, it is important to know the static magnetic prop-erties of the material to avoid significant increase in the lo-cal RF loss power density. This report summarizes studies performed at Fermilab to understand variations in the mag-netic properties of the AL800 garnet material used to build the tuner of the cavity.« less
Oxygen Generation from Carbon Dioxide for Advanced Life Support
NASA Technical Reports Server (NTRS)
Bishop, Sean; Duncan, Keith; Hagelin-Weaver, Helena; Neal, Luke; Sanchez, Jose; Paul, Heather L.; Wachsman, Eric
2007-01-01
The partial electrochemical reduction of carbon dioxide (CO2) using ceramic oxygen generators (COGs) is well known and widely studied. However, complete reduction of metabolically produced CO2 (into carbon and oxygen) has the potential of reducing oxygen storage weight for life support if the oxygen can be recovered. Recently, the University of Florida devel- oped novel ceramic oxygen generators employing a bilayer elec- trolyte of gadolinia-doped ceria and erbia-stabilized bismuth ox- ide (ESB) for NASA's future exploration of Mars. The results showed that oxygen could be reliably produced from CO2 at temperatures as low as 400 C. The strategy discussed here for advanced life support systems employs a catalytic layer com- bined with a COG cell so that CO2 is reduced all the way to solid carbon and oxygen without carbon buildup on the COG cell and subsequent deactivation.
OncoSimulR: genetic simulation with arbitrary epistasis and mutator genes in asexual populations.
Diaz-Uriarte, Ramon
2017-06-15
OncoSimulR implements forward-time genetic simulations of biallelic loci in asexual populations with special focus on cancer progression. Fitness can be defined as an arbitrary function of genetic interactions between multiple genes or modules of genes, including epistasis, restrictions in the order of accumulation of mutations, and order effects. Mutation rates can differ among genes, and can be affected by (anti)mutator genes. Also available are sampling from simulations (including single-cell sampling), plotting the genealogical relationships of clones and generating and plotting fitness landscapes. Implemented in R and C ++, freely available from BioConductor for Linux, Mac and Windows under the GNU GPL license. Version 2.5.9 or higher available from: http://www.bioconductor.org/packages/devel/bioc/html/OncoSimulR.html . GitHub repository at: https://github.com/rdiaz02/OncoSimul. ramon.diaz@iib.uam.es. Supplementary data are available at Bioinformatics online. © The Author 2017. Published by Oxford University Press.
Recent Progress In Infrared Chalcogenide Glass Fibers
NASA Astrophysics Data System (ADS)
Bornstein, A.; Croitoru, N.; Marom, E.
1984-10-01
Chalcogenide glasses containing elements like As, Ge, Sb and Se have been prepared. A new technique of preparing the raw material and subsequently drawing fibers has been devel-oped in order to avoid the forming of oxygen compounds. The fibers have been drawn by cru-cible and rod method from oxygen free raw material inside an Ar atmosphere glove box. The fibers drawn to date with air and glass cladding have a diameter of 50-500 pm and length of several meterd. Preliminary attenuation measurements indicate that the attentuation is better than 0.1 dB/cm and it is not affected even when the fiber is bent to 2 cm circular radius. The fibes were testes a CO laser beam and were not damaged at power densities below 10 kW/2cm2 CW &100 kw/cm using short pulses 75 n sec. The transmitted power density was 0.8 kW/cm2 which is an appropriate value to the needed for cutting and ablation of human tissues.
Restoration of Bhoj Wetlands At Bhopal, India
NASA Astrophysics Data System (ADS)
Shukla, S. S.; Kulshrestha, M.; Wetland Project, Bhoj
Bhoj Wetlands comprise the two lakes at Bhopal, India. These wetlands are listed amongst the 21 lakes recognized by Ministry of Environment and Forest, India and are under consideration for Ramsar lake status. The twin lakes have a total water- spread area of 32.29 sq. kms and catchment area of 370.6 sq. kms and both lakes support a rich and diverse range of flora and fauna. Currently with the help of 7055-m Yen soft loan from Japan Bank for International Cooperation (JBIC), a comprehen- sive project called the Bhoj Wetland Project has been launched for Eco-conservation management of twin lakes and this is one of the most reputed projects of its kind being undertaken in India. This paper presents details of the various works being undertaken for restoration of these wetlands at Bhopal. The Bhoj Wetlands are located at Bhopal, a city founded in 11th century AD by King Bhoj and which became known for the worst industrial Gas tragedy in 1984 when thousands lost their lives. The city is still recovering and the Bhoj Wetland Project is playing a very crucial role in improving the overall environmental status of the City. These wetlands are at present facing acute en- vironmental degradation due to pollution from a number of sources such as inflow of untreated sewage and solid waste, silt erosion and inflow from catchment, commercial activities like washing of clothes and cleaning of vehicles etc., inflow of agricultural residues and pesticides, and encroachment by builders all of which are fast eroding the rich eco-culture, flora fauna in and around the wetlands. The Bhoj Wetland Project is being implemented since the year 1995 and is scheduled to end in March 2002. The project works are being undertaken under the overall aegis of Ministry of Housing Environment, Govt. of Madhya Pradesh (M.P.) State, India. All the detailed project reports (DPRs) and preliminary ground work was undertaken by the in-house staff of Bhoj Wetland project, resulting in huge amounts of financial savings as well as devel- opment of in-house expertise. The works have also been taken up manually as far as possible, giving employment opportunities to thousands of poor residents of Bhopal City and nearby villages. This also has ensured participation of masses by default. The project had at the time of its inception envisaged a sum of Rs. 2470 millions. As a result of manual pursuance of work, development of in-house expertise and due to various other cost reduction exercises adopted by the project authorities and engineers the project has so far spent only Rs. 1100 millions thus resulting in huge savings. A part of savings (Rs. 500 millions) has been invested to form a Lake Conservation Authority U a Government body which will look after all the lakes in the entire state 1 of Madhya Pradesh, thus contributing immensely to the cause of lake conservation. One of the special features of this project has been the involvement of masses in its various developmental schemes. This has been ensured by involving more than 55 NGOs and dozens of local educational institutions. Millions of Rupees have been ear- marked for ensuring public participation in various sub-projects. The project on its completion within the next 4 months will contribute immensely to the conservation of both the lakes which can them become role models for other similar wetlands. The paper also details out the various project works like diversion and treatment of nearly 56 MLD of sewage, reduction of harmful inflows of chemicals from activities such as washing activity, idol immersions etc., reduction measures for silt inflow to the lakes, desilting and dredging operations to increase the lake capacity by more than 2.5 M.Cum, improvement in the water quality by reduction of pollution, deweeding oper- ations, nutrient removal by dredging, increased aquaculture activities etc., large scale afforestation (1.6 million trees have been planted in the catchment) and implementa- tion of solid waste management plan in the city. The direct beneficiaries of this project would be the common people who are set to gain by virtue of improved city environ- ment, increased forest produce, controlled fishing, eco-tourism and improvement in the quality of drinking water. 2
Chrysler Upset Protrusion Joining Techniques for Joining Dissimilar Metals
DOE Office of Scientific and Technical Information (OSTI.GOV)
Logan, Stephen
The project goal was to develop and demonstrate a robust, cost effective, and versatile joining technique, known as Upset Protrusion Joining (UPJ), for joining challenging dissimilar metal com-binations, especially those where one of the metals is a die cast magnesium (Mg) component. Since two of the key obstacles preventing more widespread use of light metals (especially in high volume automotive applications) are 1) a lack of robust joining techniques and 2) susceptibility to galvanic corrosion, and since the majority of the joint combinations evaluated in this project include die cast Mg (the lightest structural metal) as one of the twomore » materials being joined, and since die casting is the most common and cost effective process for producing Mg components, then successful project completion provides a key enabler to high volume application of lightweight materials, thus potentially leading to reduced costs, and encouraging implementation of lightweight multi-material vehicles for significant reductions in energy consumption and reduced greenhouse gas emissions. Eco-nomic benefits to end-use consumers are achieved primarily via the reduction in fuel consumption. Unlike currently available commercial processes, the UPJ process relies on a very robust mechanical joint rather than intermetallic bonding, so the more cathodic material can be coated prior to joining, thus creating a robust isolation against galvanic attack on the more anodic material. Additionally, since the UPJ protrusion is going through a hole that can be pre-drilled or pre-punched prior to coating, the UPJ process is less likely to damage the coating when the joint is being made. Further-more, since there is no additional cathodic material (such as a steel fastener) used to create the joint, there is no joining induced galvanic activity beyond that of the two parent materials. In accordance with its originally proposed plan, this project has successfully developed process variants of UPJ to enable joining of Mg die castings to aluminum (Al) and steel sheet components of various thicknesses, strengths and coating configurations. While most development focused on the simpler round boss version of the process, an additional phase of the work focused on devel-opment of an oval boss version to support applications with narrow flanges, while yet another vari-ant of the process, known as Upset Cast Riveting (UCR), was developed and evaluated for joining mixed metals that may not necessarily include Mg or Al die cast components. Although each varia-tion posed unique challenges described later in the report, all variations were successfully produced and evaluated, and each could be further developed for specific types of commercial applications. In this project, UPJ performed favorably against the benchmark self-pierce riveting (SPR) process in Mg AM60B to Al 6013 combinations although significant corrosion challenges were observed in both processes, especially for the bare Mg to bare Al configurations. Additional challenges were observed in joining Mg to steel with the UPJ process (SPR was not evaluated for this combination as it was not considered viable). To pass FCA’s specified corrosion tests with Mg/steel combina-tions, new steel treatments were evaluated, as well as adhesives and sealed edges. These showed significant improvement. In general, UPJ performed very well in Mg to Al 6016 combinations, even in corrosion evaluation of the bare Mg to bare Al configuration (again, SPR was not evaluated for this material combination as the 1.1 mm thick Al6016 sheet thickness was considered too thin for the SPR process). The improvement in corrosion performance of the Mg to Al 6016 combina-tion over the Mg to Al 6013 combination was thought to be a result of the lower copper content in the Al 6016 alloy. Oval boss joints showed substantial improvement in all joint strength criteria compared to 8.0-mm diameter round boss joints but were not evaluated for corrosion performance. The improved joint strength is likely a result of larger shear area. Cosmetic corrosion performance of all test assemblies (UPJ, UCR and SPR) was a challenge due to exposed edges and crevices al-lowing undercutting of the coatings. In real world component applications, the exposed edges, so prevalent on the joining test coupons, would be less prevalent and easier to protect.« less
ARCHITECT: The architecture-based technology evaluation and capability tradeoff method
NASA Astrophysics Data System (ADS)
Griendling, Kelly A.
The use of architectures for the design, development, and documentation of system-of-systems engineering has become a common practice in recent years. This practice became mandatory in the defense industry in 2004 when the Department of Defense Architecture Framework (DoDAF) Promulgation Memo mandated that all Department of Defense (DoD) architectures must be DoDAF compliant. Despite this mandate, there has been significant confusion and a lack of consistency in the creation and the use of the architecture products. Products are typically created as static documents used for communication and documentation purposes that are difficult to change and do not support engineering design activities and acquisition decision making. At the same time, acquisition guidance has been recently reformed to move from the bottom-up approach of the Requirements Generation System (RGS) to the top-down approach mandated by the Joint Capabilities Integration and Devel- opment System (JCIDS), which requires the use of DoDAF to support acquisition. Defense agencies have had difficulty adjusting to this new policy, and are struggling to determine how to meet new acquisition requirements. This research has developed the Architecture-based Technology Evaluation and Capability Tradeoff (ARCHITECT) Methodology to respond to these challenges and address concerns raised about the defense acquisition process, particularly the time required to implement parts of the process, the need to evaluate solutions across capability and mission areas, and the need to use a rigorous, traceable, repeatable method that utilizes modeling and simulation to better substantiate early-phase acquisition decisions. The objective is to create a capability-based systems engineering methodology for the early phases of design and acquisition (specifically Pre-Milestone A activities) which improves agility in defense acquisition by (1) streamlining the development of key elements of JCIDS and DoDAF, (2) moving the creation of DoDAF products forward in the defense acquisition process, and (3) using DoDAF products for more than documentation by integrating them into the problem definition and analysis of alternatives phases and applying executable architecting. This research proposes and demonstrates the plausibility of a prescriptive methodology for developing executable DoDAF products which will explicitly support decision-making in the early phases of JCIDS. A set of criteria by which CBAs should be judged is proposed, and the methodology is developed with these criteria in mind. The methodology integrates existing tools and techniques for systems engineering and system of systems engineering with several new modeling and simulation tools and techniques developed as part of this research to fill gaps noted in prior CBAs. A suppression of enemy air defenses (SEAD) mission is used to demonstrate the ap- plication of ARCHITECT and to show the plausibility of the approach. For the SEAD study, metrics are derived and a gap analysis is performed. The study then identifies and quantitatively compares system and operational architecture alternatives for performing SEAD. A series of down-selections is performed to identify promising architectures, and these promising solutions are subject to further analysis where the impacts of force structure and network structure are examined. While the numerical results of the SEAD study are notional and could not be applied to an actual SEAD CBA, the example served to highlight many of the salient features of the methodology. The SEAD study presented enabled pre-Milestone A tradeoffs to be performed quantitatively across a large number of architectural alternatives in a traceable and repeatable manner. The alternatives considered included variations on operations, systems, organizational responsibilities (through the assignment of systems to tasks), network (or collaboration) structure, interoperability level, and force structure. All of the information used in the study is preserved in the environment, which is dynamic and allows for on-the-fly analysis. The assumptions used were consistent, which was assured through the use of single file documenting all inputs, which was shared across all models. Furthermore, a model was made of the ARCHITECT methodology itself, and was used to demonstrate that even if the steps took twice as long to perform as they did in the case of the SEAD example, the methodology still provides the ability to conduct CBA analyses in less time than prior CBAs to date. Overall, it is shown that the ARCHITECT methodology results in an improvement over current CBAs in the criteria developed here.
Del Carratore, Francesco; Jankevics, Andris; Eisinga, Rob; Heskes, Tom; Hong, Fangxin; Breitling, Rainer
2017-09-01
The Rank Product (RP) is a statistical technique widely used to detect differentially expressed features in molecular profiling experiments such as transcriptomics, metabolomics and proteomics studies. An implementation of the RP and the closely related Rank Sum (RS) statistics has been available in the RankProd Bioconductor package for several years. However, several recent advances in the understanding of the statistical foundations of the method have made a complete refactoring of the existing package desirable. We implemented a completely refactored version of the RankProd package, which provides a more principled implementation of the statistics for unpaired datasets. Moreover, the permutation-based P -value estimation methods have been replaced by exact methods, providing faster and more accurate results. RankProd 2.0 is available at Bioconductor ( https://www.bioconductor.org/packages/devel/bioc/html/RankProd.html ) and as part of the mzMatch pipeline ( http://www.mzmatch.sourceforge.net ). rainer.breitling@manchester.ac.uk. Supplementary data are available at Bioinformatics online. © The Author(s) 2017. Published by Oxford University Press.
Li, Ruidong; Qu, Han; Wang, Shibo; Wei, Julong; Zhang, Le; Ma, Renyuan; Lu, Jianming; Zhu, Jianguo; Zhong, Wei-De; Jia, Zhenyu
2018-03-02
The large-scale multidimensional omics data in the Genomic Data Commons (GDC) provides opportunities to investigate the crosstalk among different RNA species and their regulatory mechanisms in cancers. Easy-to-use bioinformatics pipelines are needed to facilitate such studies. We have developed a user-friendly R/Bioconductor package, named GDCRNATools, for downloading, organizing, and analyzing RNA data in GDC with an emphasis on deciphering the lncRNA-mRNA related competing endogenous RNAs (ceRNAs) regulatory network in cancers. Many widely used bioinformatics tools and databases are utilized in our package. Users can easily pack preferred downstream analysis pipelines or integrate their own pipelines into the workflow. Interactive shiny web apps built in GDCRNATools greatly improve visualization of results from the analysis. GDCRNATools is an R/Bioconductor package that is freely available at Bioconductor (http://bioconductor.org/packages/devel/bioc/html/GDCRNATools.html). Detailed instructions, manual and example code are also available in Github (https://github.com/Jialab-UCR/GDCRNATools). arthur.jia@ucr.edu or zhongwd2009@live.cn or doctorzhujianguo@163.com.
Parma, Radosław; Zembala, Michał O; Dąbrowski, Maciej; Jagielak, Dariusz; Witkowski, Adam; Suwalski, Piotr; Dudek, Dariusz; Olszówka, Piotr; Wojakowski, Wojciech; Przybylski, Roman; Gil, Robert; Kuśmierczyk, Mariusz; Lesiak, Maciej; Sadowski, Jerzy; Dobrzycki, Sławomir; Ochała, Andrzej; Hoffman, Piotr; Kapelak, Bogusław; Kaźmierczak, Jarosław; Jasiński, Marek; Stępińska, Janina; Szymański, Piotr; Hryniewiecki, Tomasz; Kochman, Janusz; Grygier, Marek; Zembala, Marian; Legutko, Jacek; Różański, Jacek
2017-01-01
Patients with severe symptomatic aortic stenosis have a poor prognosis with medical management alone, and surgical aortic valve replacement can improve symptoms and survival. In recent years, transcatheter aortic valve implantation (TAVI) has been demonstrated to improve survival in inoperable patients and to be an alternative treatment in patients in whom the risk of surgical morbidity or mortality is high or intermediate. A representative expert committee, summoned by the Association of Cardiovascular Interventions of the Polish Cardiac Society (ACVI) and the Polish Society of Cardio-Thoracic Surgeons, devel-oped this Consensus Statement in transcatheter aortic valve implantation. It endorses the important role of a multi-disciplinary "TAVI team" in selecting patients for TAVI and defines operator and institutional requirements fundamental to the establish-ment of a successful TAVI programme. The article summarises current evidence and provides specific recommendations on organisation and conduct of transcatheter treatment of patients with aortic valve disease in Poland.
Weights, growth, and survival of timber wolf pups in Minnesota
Van Ballenberghe, V.; Mech, L.D.
1975-01-01
Weights, growth rates, canine tooth lengths, and survival data were obtained from 73 wild wolf (Canis lupus) pups that were 8 to 28 weeks old when live-trapped in three areas of northern Minnesota from 1969 to 1972. Relative weights of wild pups are expressed as percentages of a standard weight curve based on data from captive pups of similar age. These relative weights varied greatly within litters, between litters, and between years; extremes of 31 to 144 percent of the standard were observed. Growth rates ranging from 0.05 to 0.23 kilograms per day were observed, and similar variations in general devel pment and in replacement and growth of canine teeth were noted. Survival data based on radio-tracking and tag returns indicated that pups with relative weights less than 65 percent of standard have a poor chance of survival, whereas pups of at least 80 percent of standard weight have a high survivability. Pups born in 1972 were especially underweight, probably a result of declining white-tailed deer (Odocoileus virginianus) densities in the interior of the Superior National Forest study area.
NASA Astrophysics Data System (ADS)
Engebretson, M. J.; Valentic, T. A.; Stehle, R. H.; Hughes, W. J.
2004-05-01
The Magnetometer Array for Cusp and Cleft Studies (MACCS) is a two-dimensional array of eight fluxgate magnetometers that was established in 1992-1993 in the Eastern Canadian Arctic from 75° to over 80° MLAT to study electrodynamic interactions between the solar wind and Earth's magnetosphere and high-latitude ionosphere. A ninth site in Nain, Labrador, extends coverage down to 66° between existing Canadian and Greenland stations. Originally designed as part of NSF's GEM (Geospace Environment Modeling) Program, MACCS has contributed to the study of transients and waves at the magnetospheric boundary and in the near-cusp region as well as to large, cooperative, studies of ionospheric convection and substorm processes. Because of the limitations of existing telephone lines to each site, it has not been possible to economically access MACCS data promptly; instead, each month's collected data is recorded and mailed to the U.S. for processing and eventual posting on a publicly-accessible web site, http://space.augsburg.edu/space. As part of its recently renewed funding, NSF has supported the development of a near-real-time data transport system using the Iridium satellite network, which will be implemented at two MACCS sites in summer 2004. At the core of the new MACCS communications system is the Data Transport Network, software developed with NSF-ITR funding to automate the transfer of scientific data from remote field stations over unreliable, bandwidth-constrained network connections. The system utilizes a store-and-forward architecture based on sending data files as attachments to Usenet messages. This scheme not only isolates the instruments from network outages, but also provides a consistent framework for organizing and accessing multiple data feeds. Client programs are able to subscribe to data feeds to perform tasks such as system health monitoring, data processing, web page updates and e-mail alerts. The MACCS sites will employ the Data Transport Network on a small local Linux-based computer connected to an Iridium transceiver. Between 3-5Mb of data a day will be collected from the magnetometers and delivered in near-real-time for automatic distribution to modelers and index developers. More information about the Data Transport Network can be found at http://transport.sri.com/TransportDevel .
NASA Astrophysics Data System (ADS)
Alva, L.; Gogichaishvili, A.; Urrutia, J.
Ore mineral and host lithologies have been sampled with 89 oriented samples from 14 sites in the Naica District, northern Mexico. Magnetic parameters permit to charac- terise samples: saturation magnetization, density, low- high-temperature magnetic sus- ceptibility, remanence intensity, Koenigsberger ratio, Curie temperature and hystere- sis parameters. Rock magnetic properties are controlled by variations in titanomag- netite content and hydrothermal alteration. Post-mineralization hydrothermal alter- ation seems the major event that affected the minerals and magnetic properties. Curie temperatures are characteristic of titanomagnetites or titanomaghemites. Hysteresis parameters indicate that most samples have pseudo-single domain (PSD) magnetic grains. Alternating filed (AF) demagnetization and isothermal remanence (IRM) ac- quisition both indicate that natural and laboratory remanences are carried by MD-PSD spinels in the host rocks. The trend of NRM intensity vs susceptibility suggests that the carrier of remanent and induced magnetization is the same in all cases (spinels). The Koenigsberger ratio range from 0.05 to 34.04, indicating the presence of MD and PSD magnetic grains. Constraints on the geometry of the intrusive source body devel- oped in the model of the magnetic anomaly are obtained by quantifying the relative contributions of induced and remanent magnetization components.
Inverse modelling of radionuclide release rates using gamma dose rate observations
NASA Astrophysics Data System (ADS)
Hamburger, Thomas; Evangeliou, Nikolaos; Stohl, Andreas; von Haustein, Christoph; Thummerer, Severin; Wallner, Christian
2015-04-01
Severe accidents in nuclear power plants such as the historical accident in Chernobyl 1986 or the more recent disaster in the Fukushima Dai-ichi nuclear power plant in 2011 have drastic impacts on the population and environment. Observations and dispersion modelling of the released radionuclides help to assess the regional impact of such nuclear accidents. Modelling the increase of regional radionuclide activity concentrations, which results from nuclear accidents, underlies a multiplicity of uncertainties. One of the most significant uncertainties is the estimation of the source term. That is, the time dependent quantification of the released spectrum of radionuclides during the course of the nuclear accident. The quantification of the source term may either remain uncertain (e.g. Chernobyl, Devell et al., 1995) or rely on estimates given by the operators of the nuclear power plant. Precise measurements are mostly missing due to practical limitations during the accident. The release rates of radionuclides at the accident site can be estimated using inverse modelling (Davoine and Bocquet, 2007). The accuracy of the method depends amongst others on the availability, reliability and the resolution in time and space of the used observations. Radionuclide activity concentrations are observed on a relatively sparse grid and the temporal resolution of available data may be low within the order of hours or a day. Gamma dose rates, on the other hand, are observed routinely on a much denser grid and higher temporal resolution and provide therefore a wider basis for inverse modelling (Saunier et al., 2013). We present a new inversion approach, which combines an atmospheric dispersion model and observations of radionuclide activity concentrations and gamma dose rates to obtain the source term of radionuclides. We use the Lagrangian particle dispersion model FLEXPART (Stohl et al., 1998; Stohl et al., 2005) to model the atmospheric transport of the released radionuclides. The inversion method uses a Bayesian formulation considering uncertainties for the a priori source term and the observations (Eckhardt et al., 2008, Stohl et al., 2012). The a priori information on the source term is a first guess. The gamma dose rate observations are used to improve the first guess and to retrieve a reliable source term. The details of this method will be presented at the conference. This work is funded by the Bundesamt für Strahlenschutz BfS, Forschungsvorhaben 3612S60026. References Davoine, X. and Bocquet, M., Atmos. Chem. Phys., 7, 1549-1564, 2007. Devell, L., et al., OCDE/GD(96)12, 1995. Eckhardt, S., et al., Atmos. Chem. Phys., 8, 3881-3897, 2008. Saunier, O., et al., Atmos. Chem. Phys., 13, 11403-11421, 2013. Stohl, A., et al., Atmos. Environ., 32, 4245-4264, 1998. Stohl, A., et al., Atmos. Chem. Phys., 5, 2461-2474, 2005. Stohl, A., et al., Atmos. Chem. Phys., 12, 2313-2343, 2012.
DOE Office of Scientific and Technical Information (OSTI.GOV)
Brandt, James M.; Devine, Karen Dragon; Gentile, Ann C.
2014-09-01
As computer systems grow in both size and complexity, the need for applications and run-time systems to adjust to their dynamic environment also grows. The goal of the RAAMP LDRD was to combine static architecture information and real-time system state with algorithms to conserve power, reduce communication costs, and avoid network contention. We devel- oped new data collection and aggregation tools to extract static hardware information (e.g., node/core hierarchy, network routing) as well as real-time performance data (e.g., CPU uti- lization, power consumption, memory bandwidth saturation, percentage of used bandwidth, number of network stalls). We created application interfaces that allowedmore » this data to be used easily by algorithms. Finally, we demonstrated the benefit of integrating system and application information for two use cases. The first used real-time power consumption and memory bandwidth saturation data to throttle concurrency to save power without increasing application execution time. The second used static or real-time network traffic information to reduce or avoid network congestion by remapping MPI tasks to allocated processors. Results from our work are summarized in this report; more details are available in our publications [2, 6, 14, 16, 22, 29, 38, 44, 51, 54].« less
Stellarator Coil Design and Plasma Sensitivity
DOE Office of Scientific and Technical Information (OSTI.GOV)
Long-Poe Ku and Allen H. Boozer
2010-11-03
The rich information contained in the plasma response to external magnetic perturbations can be used to help design stellarator coils more effectively. We demonstrate the feasibility by first devel- oping a simple, direct method to study perturbations in stellarators that do not break stellarator symmetry and periodicity. The method applies a small perturbation to the plasma boundary and evaluates the resulting perturbed free-boundary equilibrium to build up a sensitivity matrix for the important physics attributes of the underlying configuration. Using this sensitivity information, design methods for better stellarator coils are then developed. The procedure and a proof-of-principle application are givenmore » that (1) determine the spatial distributions of external normal magnetic field at the location of the unperturbed plasma boundary to which the plasma properties are most sen- sitive, (2) determine the distributions of external normal magnetic field that can be produced most efficiently by distant coils, (3) choose the ratios of the magnitudes of the the efficiently produced magnetic distributions so the sensitive plasma properties can be controlled. Using these methods, sets of modular coils are found for the National Compact Stellarator Experiment (NCSX) that are either smoother or can be located much farther from the plasma boundary than those of the present design.« less
Draut, Amy E.; Redsteer, Margaret Hiza; Amoroso, Lee; Giosan, Liviu; Fuller, Dorian Q.; Nicoll, Kathleen; Flad, Rowan K.; Clift, Peter D.
2013-01-01
The socioeconomic impacts of climate change pose problems not only in devel- oping countries but also to residents of arid lands in the United States among marginalized societies with limited economic means. In the Navajo Nation, warming temperatures and recent drought have increased aeolian sediment mobility such that large, migrating sand dunes affect grazing lands, housing, and road access. Dust derived from this region also affects albedo and longevity of the Rocky Mountains snowpack, located downwind. We present initial results from a study that monitors sand transport and vegetation within a 0.2 km2 site in the Navajo lands, measuring the effects of drought on landscape stability since 2009. Sand mobility decreased substantially as 1 year with near-normal monsoon rainfall (2010) somewhat abated a decade-long drought, temporarily doubling vegetation cover. Vegetation that grew during 2010, with adequate rain, died off rapidly during dry conditions in 2011. Short-term increases in rainfall that promote annual, but not perennial, plant growth will not improve landscape stability in the long term. Climate projections suggest that a warmer, drier climate and potentially enhanced sediment supply from ephem- eral washes will further increase aeolian sand transport and dune activity, worsening the present challenges to people living in this region. Connections among climate, vegetation, and aeolian sediment erodibility in this region are highly relevant to other areas of the world with similar environmental problems.
Proposed mechanism for learning and memory erasure in a white-noise-driven sleeping cortex.
Steyn-Ross, Moira L; Steyn-Ross, D A; Sleigh, J W; Wilson, M T; Wilcocks, Lara C
2005-12-01
Understanding the structure and purpose of sleep remains one of the grand challenges of neurobiology. Here we use a mean-field linearized theory of the sleeping cortex to derive statistics for synaptic learning and memory erasure. The growth in correlated low-frequency high-amplitude voltage fluctuations during slow-wave sleep (SWS) is characterized by a probability density function that becomes broader and shallower as the transition into rapid-eye-movement (REM) sleep is approached. At transition, the Shannon information entropy of the fluctuations is maximized. If we assume Hebbian-learning rules apply to the cortex, then its correlated response to white-noise stimulation during SWS provides a natural mechanism for a synaptic weight change that will tend to shut down reverberant neural activity. In contrast, during REM sleep the weights will evolve in a direction that encourages excitatory activity. These entropy and weight-change predictions lead us to identify the final portion of deep SWS that occurs immediately prior to transition into REM sleep as a time of enhanced erasure of labile memory. We draw a link between the sleeping cortex and Landauer's dissipation theorem for irreversible computing [R. Landauer, IBM J. Res. Devel. 5, 183 (1961)], arguing that because information erasure is an irreversible computation, there is an inherent entropy cost as the cortex transits from SWS into REM sleep.
Kay, Robert T.
2006-01-01
The geologic and hydrologic characteristics of the sand-and-gravel deposits that compose the glacial drift aquifer in the vicinity of the Nelson Landfill site in Yor-kville, Illinois indicate that the aquifer could be devel-oped as a source of public water supply. The geology of these deposits within the Newark Bedrock Valley is com-plex, however, and a detailed investigation of their water bearing and transmitting properties will be required to successfully locate high-capacity wells. Volatile organic compounds, pesticides, and cyanide were not detected in ground water during this investiga-tion. Metals and nitrogen compounds were not detected at concentrations above their Maximum Contaminant Level. Iron, manganese, and aluminum were detected at concentrations above their Secondary Maximum Con-taminant Level and various constituents were detected at concentrations above background levels downgradi-ent of the landfill. Nitrate and ammonia, presumably derived from agricultural practices, also were detected in samples from locations hydraulically upgradient of the landfill. Oxidation-reduction conditions in the aquifer become more reducing with depth. This change is reflected by a change in the type of nitrogen compound detected and the concentration of dissolved oxygen and iron in the glacial drift aquifer. Concentrations of some of the major ions and metals may be affected by disso-lution of carbonate minerals in the aquifer and perhaps road salts.
DOE Office of Scientific and Technical Information (OSTI.GOV)
Hu, Shenyang; Burkes, Douglas E.; Lavender, Curt A.
2016-07-08
Nano-gas bubble superlattices are often observed in irradiated UMo nuclear fuels. However, the for- mation mechanism of gas bubble superlattices is not well understood. A number of physical processes may affect the gas bubble nucleation and growth; hence, the morphology of gas bubble microstructures including size and spatial distributions. In this work, a phase-field model integrating a first-passage Monte Carlo method to investigate the formation mechanism of gas bubble superlattices was devel- oped. Six physical processes are taken into account in the model: 1) heterogeneous generation of gas atoms, vacancies, and interstitials informed from atomistic simulations; 2) one-dimensional (1-D) migration of interstitials; 3) irradiation-induced dissolution of gas atoms; 4) recombination between vacancies and interstitials; 5) elastic interaction; and 6) heterogeneous nucleation of gas bubbles. We found that the elastic interaction doesn’t cause the gas bubble alignment, and fast 1-D migration of interstitials alongmore » $$\\langle$$110$$\\rangle$$ directions in the body-centered cubic U matrix causes the gas bubble alignment along $$\\langle$$110$$\\rangle$$ directions. It implies that 1-D interstitial migration along [110] direction should be the primary mechanism of a fcc gas bubble superlattice which is observed in bcc UMo alloys. Simulations also show that fission rates, saturated gas concentration, and elastic interaction all affect the morphology of gas bubble microstructures.« less
Proposed mechanism for learning and memory erasure in a white-noise-driven sleeping cortex
NASA Astrophysics Data System (ADS)
Steyn-Ross, Moira L.; Steyn-Ross, D. A.; Sleigh, J. W.; Wilson, M. T.; Wilcocks, Lara C.
2005-12-01
Understanding the structure and purpose of sleep remains one of the grand challenges of neurobiology. Here we use a mean-field linearized theory of the sleeping cortex to derive statistics for synaptic learning and memory erasure. The growth in correlated low-frequency high-amplitude voltage fluctuations during slow-wave sleep (SWS) is characterized by a probability density function that becomes broader and shallower as the transition into rapid-eye-movement (REM) sleep is approached. At transition, the Shannon information entropy of the fluctuations is maximized. If we assume Hebbian-learning rules apply to the cortex, then its correlated response to white-noise stimulation during SWS provides a natural mechanism for a synaptic weight change that will tend to shut down reverberant neural activity. In contrast, during REM sleep the weights will evolve in a direction that encourages excitatory activity. These entropy and weight-change predictions lead us to identify the final portion of deep SWS that occurs immediately prior to transition into REM sleep as a time of enhanced erasure of labile memory. We draw a link between the sleeping cortex and Landauer’s dissipation theorem for irreversible computing [R. Landauer, IBM J. Res. Devel. 5, 183 (1961)], arguing that because information erasure is an irreversible computation, there is an inherent entropy cost as the cortex transits from SWS into REM sleep.
NASA Astrophysics Data System (ADS)
Baumbick, Robert J.
1991-02-01
Fiber optic technology is expected to be used in future advanced weapons platforms as well as commercial aerospace applications. Fiber optic waveguides will be used to transmit noise free high speed data between a multitude of computers as well as audio and video information to the flight crew. Passive optical sensors connected to control computers with optical fiber interconnects will serve both control and monitoring functions. Implementation of fiber optic technology has already begun. Both the military and NASA have several programs in place. A cooperative program called FOCSI (Fiber Optic Control System Integration) between NASA Lewis and the NAVY to build environmentally test and flight demonstrate sensor systems for propul sion and flight control systems is currently underway. Integrated Optical Circuits (IOC''s) are also being given serious consideration for use in advanced aircraft sys tems. IOC''s will result in miniaturization and localization of components to gener ate detect optical signals and process them for use by the control computers. In some complex systems IOC''s may be required to perform calculations optically if the technology is ready replacing some of the electronic systems used today. IOC''s are attractive because they will result in rugged components capable of withstanding severe environments in advanced aerospace vehicles. Manufacturing technology devel oped for microelectronic integrated circuits applied to IOC''s will result in cost effective manufacturing. This paper reviews the current FOCSI program and describes the role of IOC''s in FOCSI applications.
2012-01-01
Background The robust identification of isotope patterns originating from peptides being analyzed through mass spectrometry (MS) is often significantly hampered by noise artifacts and the interference of overlapping patterns arising e.g. from post-translational modifications. As the classification of the recorded data points into either ‘noise’ or ‘signal’ lies at the very root of essentially every proteomic application, the quality of the automated processing of mass spectra can significantly influence the way the data might be interpreted within a given biological context. Results We propose non-negative least squares/non-negative least absolute deviation regression to fit a raw spectrum by templates imitating isotope patterns. In a carefully designed validation scheme, we show that the method exhibits excellent performance in pattern picking. It is demonstrated that the method is able to disentangle complicated overlaps of patterns. Conclusions We find that regularization is not necessary to prevent overfitting and that thresholding is an effective and user-friendly way to perform feature selection. The proposed method avoids problems inherent in regularization-based approaches, comes with a set of well-interpretable parameters whose default configuration is shown to generalize well without the need for fine-tuning, and is applicable to spectra of different platforms. The R package IPPD implements the method and is available from the Bioconductor platform (http://bioconductor.fhcrc.org/help/bioc-views/devel/bioc/html/IPPD.html). PMID:23137144
Ullah, Shahid A K M; Kaufman, W Reuben
2014-09-01
The feeding cycle of female ixodid ticks is divided into preparatory, slow, and rapid feeding phases. When a female Amblyomma hebraeum is removed from the host after achieving a minimum size of about 10-13× the unfed weight, various physiological and behavioural changes occur: (a) haemolymph ecdysteroid concentration rises dramatically, (b) the tick does not reattach to the host when given the opportunity, (c) its salivary glands degenerate within about 4 days (if mated) or 8 days (if virgin), and (d) oocyte maturation and oviposition occur (Kaufman and Lomas, 1996; Invert. Repr. Devel. 30: 191-198). None of these changes occur if the tick is removed from the host at smaller sizes. This transition, which occurs when the tick enters the rapid phase of engorgement, has been named the 'critical weight'. To date, the critical weight has been determined for A. hebraeum only. The present study established that, in both mated and virgin D. andersoni, the critical weight is similar to that of A. hebraeum. Although a small percentage of virgin A. hebraeum do exceed the critical weight, achieving perhaps 20× the unfed weight, virgin D. andersoni regularly fed well beyond their CW (>50× the unfed weight) and occasionally engorged completely (100× the unfed weight), although they did not detach spontaneously from the host within 21 days of attachment. Copyright © 2014 Elsevier GmbH. All rights reserved.
Xu, Xiuli; Zhao, Haixiang; Li, Li; Liu, Hanxia; Ren, Heling; Zhong, Weike
2012-03-01
A gas chromatography-mass spectrometry (GC-MS) method was developed for the determination of 40 pesticides in fruits. The effects of adding analyte protectants were evaluated for compensating matrix effects and the impacts on the quantitative results. A new combination of analyte protectants - Polyethylene Glycol 400 (PEG 400) and olive oil combination, which can be dissolved in acetone, was used for the quantitative analysis. The pesticides were extracted from fruit samples with acetonitrile and the extracts were cleaned up using micro-solid phase extraction. A GC-MS method in selective ion monitoring (SIM) mode coupled with large volume injection was finally developed. Using the newly developed analyte protectant combination of PEG 400 and olive oil, a good linearity was obtained in the range of 1 - 200 microg/L with coefficients better than 0.99, and the detection limits were between 0.1 - 3.0 microg/L. The mean recoveries of the pesticides were 75% - 119% with the relative standard deviation values less than 16.6% except for dimethoate. The performance of the analyte protectants was compared with matrix-matched standards calibration curves in terms of quantitative accuracy. The results showed that the method of adding analyte protectants can replace the matrix-matched standard calibration, and can also reduce the sample pretreatment. When the devel- oped method was used for the analysis of apple, peache, orange, banana, grape and other fruit samples, a good matrix compensation effect was achieved, and thus effectively reduced the bad effects of the water-soluble agents to the gas chromatographic column.
Inverse modelling of radionuclide release rates using gamma dose rate observations
NASA Astrophysics Data System (ADS)
Hamburger, Thomas; Stohl, Andreas; von Haustein, Christoph; Thummerer, Severin; Wallner, Christian
2014-05-01
Severe accidents in nuclear power plants such as the historical accident in Chernobyl 1986 or the more recent disaster in the Fukushima Dai-ichi nuclear power plant in 2011 have drastic impacts on the population and environment. The hazardous consequences reach out on a national and continental scale. Environmental measurements and methods to model the transport and dispersion of the released radionuclides serve as a platform to assess the regional impact of nuclear accidents - both, for research purposes and, more important, to determine the immediate threat to the population. However, the assessments of the regional radionuclide activity concentrations and the individual exposure to radiation dose underlie several uncertainties. For example, the accurate model representation of wet and dry deposition. One of the most significant uncertainty, however, results from the estimation of the source term. That is, the time dependent quantification of the released spectrum of radionuclides during the course of the nuclear accident. The quantification of the source terms of severe nuclear accidents may either remain uncertain (e.g. Chernobyl, Devell et al., 1995) or rely on rather rough estimates of released key radionuclides given by the operators. Precise measurements are mostly missing due to practical limitations during the accident. Inverse modelling can be used to realise a feasible estimation of the source term (Davoine and Bocquet, 2007). Existing point measurements of radionuclide activity concentrations are therefore combined with atmospheric transport models. The release rates of radionuclides at the accident site are then obtained by improving the agreement between the modelled and observed concentrations (Stohl et al., 2012). The accuracy of the method and hence of the resulting source term depends amongst others on the availability, reliability and the resolution in time and space of the observations. Radionuclide activity concentrations are observed on a relatively sparse grid and the temporal resolution of available data may be low within the order of hours or a day. Gamma dose rates on the other hand are observed routinely on a much denser grid and higher temporal resolution. Gamma dose rate measurements contain no explicit information on the observed spectrum of radionuclides and have to be interpreted carefully. Nevertheless, they provide valuable information for the inverse evaluation of the source term due to their availability (Saunier et al., 2013). We present a new inversion approach combining an atmospheric dispersion model and observations of radionuclide activity concentrations and gamma dose rates to obtain the source term of radionuclides. We use the Lagrangian particle dispersion model FLEXPART (Stohl et al., 1998; Stohl et al., 2005) to model the atmospheric transport of the released radionuclides. The gamma dose rates are calculated from the modelled activity concentrations. The inversion method uses a Bayesian formulation considering uncertainties for the a priori source term and the observations (Eckhardt et al., 2008). The a priori information on the source term is a first guess. The gamma dose rate observations will be used with inverse modelling to improve this first guess and to retrieve a reliable source term. The details of this method will be presented at the conference. This work is funded by the Bundesamt für Strahlenschutz BfS, Forschungsvorhaben 3612S60026. References Davoine, X. and Bocquet, M., Atmos. Chem. Phys., 7, 1549-1564, 2007. Devell, L., et al., OCDE/GD(96)12, 1995. Eckhardt, S., et al., Atmos. Chem. Phys., 8, 3881-3897, 2008. Saunier, O., et al., Atmos. Chem. Phys., 13, 11403-11421, 2013. Stohl, A., et al., Atmos. Environ., 32, 4245-4264, 1998. Stohl, A., et al., Atmos. Chem. Phys., 5, 2461-2474, 2005. Stohl, A., et al., Atmos. Chem. Phys., 12, 2313-2343, 2012.
Wright, Winfield G.; Moore, Bryan
2003-01-01
Tracer-injection studies were done in Belcher Gulch in the upper Animas River watershed, southwestern Colorado, to determine whether the alpine stream infiltrates into underground mine workings of the North Star Mine and other nearby mines in the area. The tracer-injection studies were designed to determine if and where along Belcher Gulch the stream infiltrates into the mine. Four separate tracer-injec-tion tests were done using lithium bromide (LiBr), optical brightener dye, and sodium chloride (NaCl) as tracer solu-tions. Two of the tracers (LiBr and dye) were injected con-tinuously for 24 hours, one of the NaCl tracers was injected continuously for 12 hours, and one of the NaCl tracers was injected over a period of 1 hour. Concentration increases of tracer constituents were detected in water discharging from the North Star Mine, substantiating a surface-water and ground-water connection between Belcher Gulch and the North Star Mine. Different timing and magnitude of tracer breakthroughs indicated multiple flow paths with different residence times from the stream to the mine. The Pittsburgh and Sultan Mines were thought to physically connect to the North Star Mine, but tracer breakthroughs were inconclusive in water from these mines. From the tracer-injection tests and synoptic measure-ments of streamflow discharge, a conceptual model was devel-oped for surface-water and ground-water interactions between Belcher Gulch and the North Star Mine. This information, combined with previous surface geophysical surveys indicat-ing the presence of subsurface voids, may assist with decision-making process for preventing infiltration and for the remedia-tion of mine drainage from these mines.
Multipurpose fiber-optic sensor with sloped tip
NASA Astrophysics Data System (ADS)
Melnik, Ivan S.; Krivokhizha, A. M.; Ptashnik, O. V.
1991-08-01
Fiber-optic sensors C FOS) are wi. del y used for rioncontact measurements due to their simplicity, small size, insensitivity to I nfl uence of el ectromagneti C fiel ds , hi gh metrol ogi cal characteristics, etc. The operation principle of FOS with intensity modul ati on techni que I s based on the photodetector regi strati on of 1ight , reflected from the control 1 ed surface E I ) . The i ntensi ty of detected 1 1 ght depends on th FOS' s di stance from the control 1 ed surface, its form and inclination to sensor's axis, FOS shift speed, etc. So they can be consider multipurpose. We are devel opi ng FOS wi th i ntensi ty modul ati on techni que wi th traight tips as well as with sloped tips. In FOS with sloped tips the light ring spot is appearing on the controlled surface due to the effect of symmetry. We use thi s phenomena to empl oy refl ected 1 i ght more efficiently and to increase the FOS characteristics. Tak i ng I nto account the fact that pr obl ems of cal cul aWl on of fibers with sloped tip were not analyzed in details earlier-, in particular, only the case of light distribution of parallel beams runni ng was consi dered E 2) we wi I 1 conduct a consi stent cal cul ati on of bounds of i rradi ance fi ci d , created by a fi ber wi th sl oped tip, esti mate I i ght di stri buti on I n a 1 1 ght spot , and determi. ne characteristics of the FOS with sloped tip.
Office Computer Software: A Comprehensive Review of Software Programs.
ERIC Educational Resources Information Center
Secretary, 1992
1992-01-01
Describes types of software including system software, application software, spreadsheets, accounting software, graphics packages, desktop publishing software, database, desktop and personal information management software, project and records management software, groupware, and shareware. (JOW)
Software Past, Present, and Future: Views from Government, Industry and Academia
NASA Technical Reports Server (NTRS)
Holcomb, Lee; Page, Jerry; Evangelist, Michael
2000-01-01
Views from the NASA CIO NASA Software Engineering Workshop on software development from the past, present, and future are presented. The topics include: 1) Software Past; 2) Software Present; 3) NASA's Largest Software Challenges; 4) 8330 Software Projects in Industry Standish Groups 1994 Report; 5) Software Future; 6) Capability Maturity Model (CMM): Software Engineering Institute (SEI) levels; 7) System Engineering Quality Also Part of the Problem; 8) University Environment Trends Will Increase the Problem in Software Engineering; and 9) NASA Software Engineering Goals.
Space Flight Software Development Software for Intelligent System Health Management
NASA Technical Reports Server (NTRS)
Trevino, Luis C.; Crumbley, Tim
2004-01-01
The slide presentation examines the Marshall Space Flight Center Flight Software Branch, including software development projects, mission critical space flight software development, software technical insight, advanced software development technologies, and continuous improvement in the software development processes and methods.
48 CFR 227.7202 - Commercial computer software and commercial computer software documentation.
Code of Federal Regulations, 2014 CFR
2014-10-01
... software and commercial computer software documentation. 227.7202 Section 227.7202 Federal Acquisition... REQUIREMENTS PATENTS, DATA, AND COPYRIGHTS Rights in Computer Software and Computer Software Documentation 227.7202 Commercial computer software and commercial computer software documentation. ...
48 CFR 227.7203 - Noncommercial computer software and noncommercial computer software documentation.
Code of Federal Regulations, 2012 CFR
2012-10-01
... software and noncommercial computer software documentation. 227.7203 Section 227.7203 Federal Acquisition... REQUIREMENTS PATENTS, DATA, AND COPYRIGHTS Rights in Computer Software and Computer Software Documentation 227.7203 Noncommercial computer software and noncommercial computer software documentation. ...
48 CFR 227.7203 - Noncommercial computer software and noncommercial computer software documentation.
Code of Federal Regulations, 2011 CFR
2011-10-01
... software and noncommercial computer software documentation. 227.7203 Section 227.7203 Federal Acquisition... REQUIREMENTS PATENTS, DATA, AND COPYRIGHTS Rights in Computer Software and Computer Software Documentation 227.7203 Noncommercial computer software and noncommercial computer software documentation. ...
48 CFR 227.7203 - Noncommercial computer software and noncommercial computer software documentation.
Code of Federal Regulations, 2013 CFR
2013-10-01
... software and noncommercial computer software documentation. 227.7203 Section 227.7203 Federal Acquisition... REQUIREMENTS PATENTS, DATA, AND COPYRIGHTS Rights in Computer Software and Computer Software Documentation 227.7203 Noncommercial computer software and noncommercial computer software documentation. ...
48 CFR 227.7202 - Commercial computer software and commercial computer software documentation.
Code of Federal Regulations, 2013 CFR
2013-10-01
... software and commercial computer software documentation. 227.7202 Section 227.7202 Federal Acquisition... REQUIREMENTS PATENTS, DATA, AND COPYRIGHTS Rights in Computer Software and Computer Software Documentation 227.7202 Commercial computer software and commercial computer software documentation. ...
48 CFR 227.7203 - Noncommercial computer software and noncommercial computer software documentation.
Code of Federal Regulations, 2014 CFR
2014-10-01
... software and noncommercial computer software documentation. 227.7203 Section 227.7203 Federal Acquisition... REQUIREMENTS PATENTS, DATA, AND COPYRIGHTS Rights in Computer Software and Computer Software Documentation 227.7203 Noncommercial computer software and noncommercial computer software documentation. ...
48 CFR 227.7202 - Commercial computer software and commercial computer software documentation.
Code of Federal Regulations, 2011 CFR
2011-10-01
... software and commercial computer software documentation. 227.7202 Section 227.7202 Federal Acquisition... REQUIREMENTS PATENTS, DATA, AND COPYRIGHTS Rights in Computer Software and Computer Software Documentation 227.7202 Commercial computer software and commercial computer software documentation. ...
48 CFR 227.7202 - Commercial computer software and commercial computer software documentation.
Code of Federal Regulations, 2010 CFR
2010-10-01
... software and commercial computer software documentation. 227.7202 Section 227.7202 Federal Acquisition... REQUIREMENTS PATENTS, DATA, AND COPYRIGHTS Rights in Computer Software and Computer Software Documentation 227.7202 Commercial computer software and commercial computer software documentation. ...
48 CFR 227.7202 - Commercial computer software and commercial computer software documentation.
Code of Federal Regulations, 2012 CFR
2012-10-01
... software and commercial computer software documentation. 227.7202 Section 227.7202 Federal Acquisition... REQUIREMENTS PATENTS, DATA, AND COPYRIGHTS Rights in Computer Software and Computer Software Documentation 227.7202 Commercial computer software and commercial computer software documentation. ...
48 CFR 227.7203 - Noncommercial computer software and noncommercial computer software documentation.
Code of Federal Regulations, 2010 CFR
2010-10-01
... software and noncommercial computer software documentation. 227.7203 Section 227.7203 Federal Acquisition... REQUIREMENTS PATENTS, DATA, AND COPYRIGHTS Rights in Computer Software and Computer Software Documentation 227.7203 Noncommercial computer software and noncommercial computer software documentation. ...
NASA Technical Reports Server (NTRS)
Uber, James G.
1988-01-01
Software itself is not hazardous, but since software and hardware share common interfaces there is an opportunity for software to create hazards. Further, these software systems are complex, and proven methods for the design, analysis, and measurement of software safety are not yet available. Some past software failures, future NASA software trends, software engineering methods, and tools and techniques for various software safety analyses are reviewed. Recommendations to NASA are made based on this review.
Code of Federal Regulations, 2011 CFR
2011-10-01
... software or computer software documentation to foreign governments, foreign contractors, or international... Rights in Computer Software and Computer Software Documentation 227.7203-16 Providing computer software or computer software documentation to foreign governments, foreign contractors, or international...
Code of Federal Regulations, 2013 CFR
2013-10-01
... software or computer software documentation to foreign governments, foreign contractors, or international... Rights in Computer Software and Computer Software Documentation 227.7203-16 Providing computer software or computer software documentation to foreign governments, foreign contractors, or international...
Code of Federal Regulations, 2012 CFR
2012-10-01
... software or computer software documentation to foreign governments, foreign contractors, or international... Rights in Computer Software and Computer Software Documentation 227.7203-16 Providing computer software or computer software documentation to foreign governments, foreign contractors, or international...
Code of Federal Regulations, 2014 CFR
2014-10-01
... software or computer software documentation to foreign governments, foreign contractors, or international... Rights in Computer Software and Computer Software Documentation 227.7203-16 Providing computer software or computer software documentation to foreign governments, foreign contractors, or international...
Code of Federal Regulations, 2010 CFR
2010-10-01
... software or computer software documentation to foreign governments, foreign contractors, or international... Rights in Computer Software and Computer Software Documentation 227.7203-16 Providing computer software or computer software documentation to foreign governments, foreign contractors, or international...
Avoidable Software Procurements
2012-09-01
software license, software usage, ELA, Software as a Service , SaaS , Software Asset...PaaS Platform as a Service SaaS Software as a Service SAM Software Asset Management SMS System Management Server SEWP Solutions for Enterprise Wide...delivery of full Cloud Services , we will see the transition of the Cloud Computing service model from Iaas to SaaS , or Software as a Service . Software
48 CFR 227.7203-15 - Subcontractor rights in computer software or computer software documentation.
Code of Federal Regulations, 2012 CFR
2012-10-01
... computer software or computer software documentation. 227.7203-15 Section 227.7203-15 Federal Acquisition... REQUIREMENTS PATENTS, DATA, AND COPYRIGHTS Rights in Computer Software and Computer Software Documentation 227.7203-15 Subcontractor rights in computer software or computer software documentation. (a...
48 CFR 227.7203-15 - Subcontractor rights in computer software or computer software documentation.
Code of Federal Regulations, 2014 CFR
2014-10-01
... computer software or computer software documentation. 227.7203-15 Section 227.7203-15 Federal Acquisition... REQUIREMENTS PATENTS, DATA, AND COPYRIGHTS Rights in Computer Software and Computer Software Documentation 227.7203-15 Subcontractor rights in computer software or computer software documentation. (a...
48 CFR 227.7203-15 - Subcontractor rights in computer software or computer software documentation.
Code of Federal Regulations, 2010 CFR
2010-10-01
... computer software or computer software documentation. 227.7203-15 Section 227.7203-15 Federal Acquisition... REQUIREMENTS PATENTS, DATA, AND COPYRIGHTS Rights in Computer Software and Computer Software Documentation 227.7203-15 Subcontractor rights in computer software or computer software documentation. (a...
48 CFR 227.7203-15 - Subcontractor rights in computer software or computer software documentation.
Code of Federal Regulations, 2011 CFR
2011-10-01
... computer software or computer software documentation. 227.7203-15 Section 227.7203-15 Federal Acquisition... REQUIREMENTS PATENTS, DATA, AND COPYRIGHTS Rights in Computer Software and Computer Software Documentation 227.7203-15 Subcontractor rights in computer software or computer software documentation. (a...
48 CFR 227.7203-15 - Subcontractor rights in computer software or computer software documentation.
Code of Federal Regulations, 2013 CFR
2013-10-01
... computer software or computer software documentation. 227.7203-15 Section 227.7203-15 Federal Acquisition... REQUIREMENTS PATENTS, DATA, AND COPYRIGHTS Rights in Computer Software and Computer Software Documentation 227.7203-15 Subcontractor rights in computer software or computer software documentation. (a...
Code of Federal Regulations, 2010 CFR
2010-10-01
... computer software or commercial computer software documentation. 227.7202-3 Section 227.7202-3 Federal... CONTRACTING REQUIREMENTS PATENTS, DATA, AND COPYRIGHTS Rights in Computer Software and Computer Software Documentation 227.7202-3 Rights in commercial computer software or commercial computer software documentation...
Code of Federal Regulations, 2011 CFR
2011-10-01
... computer software or commercial computer software documentation. 227.7202-3 Section 227.7202-3 Federal... CONTRACTING REQUIREMENTS PATENTS, DATA, AND COPYRIGHTS Rights in Computer Software and Computer Software Documentation 227.7202-3 Rights in commercial computer software or commercial computer software documentation...
Code of Federal Regulations, 2012 CFR
2012-10-01
... noncommercial computer software and computer software documentation. 227.7203-2 Section 227.7203-2 Federal... CONTRACTING REQUIREMENTS PATENTS, DATA, AND COPYRIGHTS Rights in Computer Software and Computer Software Documentation 227.7203-2 Acquisition of noncommercial computer software and computer software documentation. (a...
Code of Federal Regulations, 2011 CFR
2011-10-01
... noncommercial computer software and computer software documentation. 227.7203-2 Section 227.7203-2 Federal... CONTRACTING REQUIREMENTS PATENTS, DATA, AND COPYRIGHTS Rights in Computer Software and Computer Software Documentation 227.7203-2 Acquisition of noncommercial computer software and computer software documentation. (a...
Code of Federal Regulations, 2014 CFR
2014-10-01
... noncommercial computer software and computer software documentation. 227.7203-2 Section 227.7203-2 Federal... CONTRACTING REQUIREMENTS PATENTS, DATA, AND COPYRIGHTS Rights in Computer Software and Computer Software Documentation 227.7203-2 Acquisition of noncommercial computer software and computer software documentation. (a...
Code of Federal Regulations, 2014 CFR
2014-10-01
... and marking of computer software or computer software documentation to be furnished with restrictive... Rights in Computer Software and Computer Software Documentation 227.7203-10 Contractor identification and marking of computer software or computer software documentation to be furnished with restrictive markings...
Code of Federal Regulations, 2010 CFR
2010-10-01
... noncommercial computer software and computer software documentation. 227.7203-2 Section 227.7203-2 Federal... CONTRACTING REQUIREMENTS PATENTS, DATA, AND COPYRIGHTS Rights in Computer Software and Computer Software Documentation 227.7203-2 Acquisition of noncommercial computer software and computer software documentation. (a...
Code of Federal Regulations, 2013 CFR
2013-10-01
... computer software or commercial computer software documentation. 227.7202-3 Section 227.7202-3 Federal... CONTRACTING REQUIREMENTS PATENTS, DATA, AND COPYRIGHTS Rights in Computer Software and Computer Software Documentation 227.7202-3 Rights in commercial computer software or commercial computer software documentation...
Code of Federal Regulations, 2011 CFR
2011-10-01
... and marking of computer software or computer software documentation to be furnished with restrictive... Rights in Computer Software and Computer Software Documentation 227.7203-10 Contractor identification and marking of computer software or computer software documentation to be furnished with restrictive markings...
Code of Federal Regulations, 2014 CFR
2014-10-01
... computer software or commercial computer software documentation. 227.7202-3 Section 227.7202-3 Federal... CONTRACTING REQUIREMENTS PATENTS, DATA, AND COPYRIGHTS Rights in Computer Software and Computer Software Documentation 227.7202-3 Rights in commercial computer software or commercial computer software documentation...
Code of Federal Regulations, 2012 CFR
2012-10-01
... and marking of computer software or computer software documentation to be furnished with restrictive... Rights in Computer Software and Computer Software Documentation 227.7203-10 Contractor identification and marking of computer software or computer software documentation to be furnished with restrictive markings...
Code of Federal Regulations, 2012 CFR
2012-10-01
... computer software or commercial computer software documentation. 227.7202-3 Section 227.7202-3 Federal... CONTRACTING REQUIREMENTS PATENTS, DATA, AND COPYRIGHTS Rights in Computer Software and Computer Software Documentation 227.7202-3 Rights in commercial computer software or commercial computer software documentation...
Code of Federal Regulations, 2010 CFR
2010-10-01
... and marking of computer software or computer software documentation to be furnished with restrictive... Rights in Computer Software and Computer Software Documentation 227.7203-10 Contractor identification and marking of computer software or computer software documentation to be furnished with restrictive markings...
Code of Federal Regulations, 2013 CFR
2013-10-01
... and marking of computer software or computer software documentation to be furnished with restrictive... Rights in Computer Software and Computer Software Documentation 227.7203-10 Contractor identification and marking of computer software or computer software documentation to be furnished with restrictive markings...
Code of Federal Regulations, 2013 CFR
2013-10-01
... noncommercial computer software and computer software documentation. 227.7203-2 Section 227.7203-2 Federal... CONTRACTING REQUIREMENTS PATENTS, DATA, AND COPYRIGHTS Rights in Computer Software and Computer Software Documentation 227.7203-2 Acquisition of noncommercial computer software and computer software documentation. (a...
NASA Technical Reports Server (NTRS)
Lee, Alice T.; Gunn, Todd; Pham, Tuan; Ricaldi, Ron
1994-01-01
This handbook documents the three software analysis processes the Space Station Software Analysis team uses to assess space station software, including their backgrounds, theories, tools, and analysis procedures. Potential applications of these analysis results are also presented. The first section describes how software complexity analysis provides quantitative information on code, such as code structure and risk areas, throughout the software life cycle. Software complexity analysis allows an analyst to understand the software structure, identify critical software components, assess risk areas within a software system, identify testing deficiencies, and recommend program improvements. Performing this type of analysis during the early design phases of software development can positively affect the process, and may prevent later, much larger, difficulties. The second section describes how software reliability estimation and prediction analysis, or software reliability, provides a quantitative means to measure the probability of failure-free operation of a computer program, and describes the two tools used by JSC to determine failure rates and design tradeoffs between reliability, costs, performance, and schedule.
Code of Federal Regulations, 2010 CFR
2010-10-01
... computer software or computer software documentation to be furnished to the Government with restrictions on..., DATA, AND COPYRIGHTS Rights in Computer Software and Computer Software Documentation 227.7203-3 Early identification of computer software or computer software documentation to be furnished to the Government with...
Code of Federal Regulations, 2012 CFR
2012-10-01
... computer software or computer software documentation to be furnished to the Government with restrictions on..., DATA, AND COPYRIGHTS Rights in Computer Software and Computer Software Documentation 227.7203-3 Early identification of computer software or computer software documentation to be furnished to the Government with...
Code of Federal Regulations, 2011 CFR
2011-10-01
... computer software or computer software documentation to be furnished to the Government with restrictions on..., DATA, AND COPYRIGHTS Rights in Computer Software and Computer Software Documentation 227.7203-3 Early identification of computer software or computer software documentation to be furnished to the Government with...
Code of Federal Regulations, 2013 CFR
2013-10-01
... computer software or computer software documentation to be furnished to the Government with restrictions on..., DATA, AND COPYRIGHTS Rights in Computer Software and Computer Software Documentation 227.7203-3 Early identification of computer software or computer software documentation to be furnished to the Government with...
Code of Federal Regulations, 2014 CFR
2014-10-01
... computer software or computer software documentation to be furnished to the Government with restrictions on..., DATA, AND COPYRIGHTS Rights in Computer Software and Computer Software Documentation 227.7203-3 Early identification of computer software or computer software documentation to be furnished to the Government with...
Automated Reuse of Scientific Subroutine Libraries through Deductive Synthesis
NASA Technical Reports Server (NTRS)
Lowry, Michael R.; Pressburger, Thomas; VanBaalen, Jeffrey; Roach, Steven
1997-01-01
Systematic software construction offers the potential of elevating software engineering from an art-form to an engineering discipline. The desired result is more predictable software development leading to better quality and more maintainable software. However, the overhead costs associated with the formalisms, mathematics, and methods of systematic software construction have largely precluded their adoption in real-world software development. In fact, many mainstream software development organizations, such as Microsoft, still maintain a predominantly oral culture for software development projects; which is far removed from a formalism-based culture for software development. An exception is the limited domain of safety-critical software, where the high-assuiance inherent in systematic software construction justifies the additional cost. We believe that systematic software construction will only be adopted by mainstream software development organization when the overhead costs have been greatly reduced. Two approaches to cost mitigation are reuse (amortizing costs over many applications) and automation. For the last four years, NASA Ames has funded the Amphion project, whose objective is to automate software reuse through techniques from systematic software construction. In particular, deductive program synthesis (i.e., program extraction from proofs) is used to derive a composition of software components (e.g., subroutines) that correctly implements a specification. The construction of reuse libraries of software components is the standard software engineering solution for improving software development productivity and quality.
Annotated bibliography of Software Engineering Laboratory literature
NASA Technical Reports Server (NTRS)
Morusiewicz, Linda; Valett, Jon D.
1991-01-01
An annotated bibliography of technical papers, documents, and memorandums produced by or related to the Software Engineering Laboratory is given. More than 100 publications are summarized. These publications cover many areas of software engineering and range from research reports to software documentation. All materials have been grouped into eight general subject areas for easy reference: The Software Engineering Laboratory; The Software Engineering Laboratory: Software Development Documents; Software Tools; Software Models; Software Measurement; Technology Evaluations; Ada Technology; and Data Collection. Subject and author indexes further classify these documents by specific topic and individual author.
SAGA: A project to automate the management of software production systems
NASA Technical Reports Server (NTRS)
Campbell, Roy H.; Beckman-Davies, C. S.; Benzinger, L.; Beshers, G.; Laliberte, D.; Render, H.; Sum, R.; Smith, W.; Terwilliger, R.
1986-01-01
Research into software development is required to reduce its production cost and to improve its quality. Modern software systems, such as the embedded software required for NASA's space station initiative, stretch current software engineering techniques. The requirements to build large, reliable, and maintainable software systems increases with time. Much theoretical and practical research is in progress to improve software engineering techniques. One such technique is to build a software system or environment which directly supports the software engineering process, i.e., the SAGA project, comprising the research necessary to design and build a software development which automates the software engineering process. Progress under SAGA is described.
The social disutility of software ownership.
Douglas, David M
2011-09-01
Software ownership allows the owner to restrict the distribution of software and to prevent others from reading the software's source code and building upon it. However, free software is released to users under software licenses that give them the right to read the source code, modify it, reuse it, and distribute the software to others. Proponents of free software such as Richard M. Stallman and Eben Moglen argue that the social disutility of software ownership is a sufficient justification for prohibiting it. This social disutility includes the social instability of disregarding laws and agreements covering software use and distribution, inequality of software access, and the inability to help others by sharing software with them. Here I consider these and other social disutility claims against withholding specific software rights from users, in particular, the rights to read the source code, duplicate, distribute, modify, imitate, and reuse portions of the software within new programs. I find that generally while withholding these rights from software users does cause some degree of social disutility, only the rights to duplicate, modify and imitate cannot legitimately be denied to users on this basis. The social disutility of withholding the rights to distribute the software, read its source code and reuse portions of it in new programs is insufficient to prohibit software owners from denying them to users. A compromise between the software owner and user can minimise the social disutility of withholding these particular rights from users. However, the social disutility caused by software patents is sufficient for rejecting such patents as they restrict the methods of reducing social disutility possible with other forms of software ownership.
Proceedings of the Seventeenth Annual Software Engineering Workshop
NASA Technical Reports Server (NTRS)
1992-01-01
Proceedings of the Seventeenth Annual Software Engineering Workshop are presented. The software Engineering Laboratory (SEL) is an organization sponsored by NASA/Goddard Space Flight Center and created to investigate the effectiveness of software engineering technologies when applied to the development of applications software. Topics covered include: the Software Engineering Laboratory; process measurement; software reuse; software quality; lessons learned; and is Ada dying.
Four applications of a software data collection and analysis methodology
NASA Technical Reports Server (NTRS)
Basili, Victor R.; Selby, Richard W., Jr.
1985-01-01
The evaluation of software technologies suffers because of the lack of quantitative assessment of their effect on software development and modification. A seven-step data collection and analysis methodology couples software technology evaluation with software measurement. Four in-depth applications of the methodology are presented. The four studies represent each of the general categories of analyses on the software product and development process: blocked subject-project studies, replicated project studies, multi-project variation studies, and single project strategies. The four applications are in the areas of, respectively, software testing, cleanroom software development, characteristic software metric sets, and software error analysis.
Third-Party Software's Trust Quagmire.
Voas, J; Hurlburt, G
2015-12-01
Current software development has trended toward the idea of integrating independent software sub-functions to create more complete software systems. Software sub-functions are often not homegrown - instead they are developed by unknown 3 rd party organizations and reside in software marketplaces owned or controlled by others. Such software sub-functions carry plausible concern in terms of quality, origins, functionality, security, interoperability, to name a few. This article surveys key technical difficulties in confidently building systems from acquired software sub-functions by calling out the principle software supply chain actors.
NASA Technical Reports Server (NTRS)
Voigt, S. (Editor); Beskenis, S. (Editor)
1985-01-01
Issues in the development of software for the Space Station are discussed. Software acquisition and management, software development environment, standards, information system support for software developers, and a future software advisory board are addressed.
1992-06-01
presents the concept of software Total Quality Management (TQM) which focuses on the entire process of software acquisition, as a partial solution to...software TQM can be applied to software acquisition. Software Development, Software Acquisition, Total Quality management (TQM), Army Tactical Missile
Code of Federal Regulations, 2013 CFR
2013-10-01
... computer software and noncommercial computer software documentation. 252.227-7014 Section 252.227-7014... Rights in noncommercial computer software and noncommercial computer software documentation. As prescribed in 227.7203-6(a)(1), use the following clause. Rights in Noncommercial Computer Software and...
Code of Federal Regulations, 2012 CFR
2012-10-01
... computer software and noncommercial computer software documentation. 252.227-7014 Section 252.227-7014... Rights in noncommercial computer software and noncommercial computer software documentation. As prescribed in 227.7203-6(a)(1), use the following clause. Rights in Noncommercial Computer Software and...
Code of Federal Regulations, 2014 CFR
2014-10-01
..., and warranty of computer software and computer software documentation. 227.7203-14 Section 227.7203-14... GENERAL CONTRACTING REQUIREMENTS PATENTS, DATA, AND COPYRIGHTS Rights in Computer Software and Computer Software Documentation 227.7203-14 Conformity, acceptance, and warranty of computer software and computer...
Code of Federal Regulations, 2014 CFR
2014-10-01
... computer software and noncommercial computer software documentation. 252.227-7014 Section 252.227-7014... Rights in noncommercial computer software and noncommercial computer software documentation. As prescribed in 227.7203-6(a)(1), use the following clause. Rights in Noncommercial Computer Software and...
Code of Federal Regulations, 2010 CFR
2010-10-01
..., and warranty of computer software and computer software documentation. 227.7203-14 Section 227.7203-14... GENERAL CONTRACTING REQUIREMENTS PATENTS, DATA, AND COPYRIGHTS Rights in Computer Software and Computer Software Documentation 227.7203-14 Conformity, acceptance, and warranty of computer software and computer...
Code of Federal Regulations, 2011 CFR
2011-10-01
... computer software and noncommercial computer software documentation. 252.227-7014 Section 252.227-7014... Rights in noncommercial computer software and noncommercial computer software documentation. As prescribed in 227.7203-6(a)(1), use the following clause. Rights in Noncommercial Computer Software and...
Code of Federal Regulations, 2012 CFR
2012-10-01
..., and warranty of computer software and computer software documentation. 227.7203-14 Section 227.7203-14... GENERAL CONTRACTING REQUIREMENTS PATENTS, DATA, AND COPYRIGHTS Rights in Computer Software and Computer Software Documentation 227.7203-14 Conformity, acceptance, and warranty of computer software and computer...
Code of Federal Regulations, 2013 CFR
2013-10-01
..., and warranty of computer software and computer software documentation. 227.7203-14 Section 227.7203-14... GENERAL CONTRACTING REQUIREMENTS PATENTS, DATA, AND COPYRIGHTS Rights in Computer Software and Computer Software Documentation 227.7203-14 Conformity, acceptance, and warranty of computer software and computer...
Code of Federal Regulations, 2011 CFR
2011-10-01
..., and warranty of computer software and computer software documentation. 227.7203-14 Section 227.7203-14... GENERAL CONTRACTING REQUIREMENTS PATENTS, DATA, AND COPYRIGHTS Rights in Computer Software and Computer Software Documentation 227.7203-14 Conformity, acceptance, and warranty of computer software and computer...
Code of Federal Regulations, 2010 CFR
2010-10-01
... computer software and noncommercial computer software documentation. 252.227-7014 Section 252.227-7014... Rights in noncommercial computer software and noncommercial computer software documentation. As prescribed in 227.7203-6(a)(1), use the following clause. Rights in Noncommercial Computer Software and...
Software Quality Assurance Metrics
NASA Technical Reports Server (NTRS)
McRae, Kalindra A.
2004-01-01
Software Quality Assurance (SQA) is a planned and systematic set of activities that ensures conformance of software life cycle processes and products conform to requirements, standards and procedures. In software development, software quality means meeting requirements and a degree of excellence and refinement of a project or product. Software Quality is a set of attributes of a software product by which its quality is described and evaluated. The set of attributes includes functionality, reliability, usability, efficiency, maintainability, and portability. Software Metrics help us understand the technical process that is used to develop a product. The process is measured to improve it and the product is measured to increase quality throughout the life cycle of software. Software Metrics are measurements of the quality of software. Software is measured to indicate the quality of the product, to assess the productivity of the people who produce the product, to assess the benefits derived from new software engineering methods and tools, to form a baseline for estimation, and to help justify requests for new tools or additional training. Any part of the software development can be measured. If Software Metrics are implemented in software development, it can save time, money, and allow the organization to identify the caused of defects which have the greatest effect on software development. The summer of 2004, I worked with Cynthia Calhoun and Frank Robinson in the Software Assurance/Risk Management department. My task was to research and collect, compile, and analyze SQA Metrics that have been used in other projects that are not currently being used by the SA team and report them to the Software Assurance team to see if any metrics can be implemented in their software assurance life cycle process.
Software Configuration Management Guidebook
NASA Technical Reports Server (NTRS)
1995-01-01
The growth in cost and importance of software to NASA has caused NASA to address the improvement of software development across the agency. One of the products of this program is a series of guidebooks that define a NASA concept of the assurance processes which are used in software development. The Software Assurance Guidebook, SMAP-GB-A201, issued in September, 1989, provides an overall picture of the concepts and practices of NASA in software assurance. Lower level guidebooks focus on specific activities that fall within the software assurance discipline, and provide more detailed information for the manager and/or practitioner. This is the Software Configuration Management Guidebook which describes software configuration management in a way that is compatible with practices in industry and at NASA Centers. Software configuration management is a key software development process, and is essential for doing software assurance.
Computer-Aided Software Engineering - An approach to real-time software development
NASA Technical Reports Server (NTRS)
Walker, Carrie K.; Turkovich, John J.
1989-01-01
A new software engineering discipline is Computer-Aided Software Engineering (CASE), a technology aimed at automating the software development process. This paper explores the development of CASE technology, particularly in the area of real-time/scientific/engineering software, and a history of CASE is given. The proposed software development environment for the Advanced Launch System (ALS CASE) is described as an example of an advanced software development system for real-time/scientific/engineering (RT/SE) software. The Automated Programming Subsystem of ALS CASE automatically generates executable code and corresponding documentation from a suitably formatted specification of the software requirements. Software requirements are interactively specified in the form of engineering block diagrams. Several demonstrations of the Automated Programming Subsystem are discussed.
Product-oriented Software Certification Process for Software Synthesis
NASA Technical Reports Server (NTRS)
Nelson, Stacy; Fischer, Bernd; Denney, Ewen; Schumann, Johann; Richardson, Julian; Oh, Phil
2004-01-01
The purpose of this document is to propose a product-oriented software certification process to facilitate use of software synthesis and formal methods. Why is such a process needed? Currently, software is tested until deemed bug-free rather than proving that certain software properties exist. This approach has worked well in most cases, but unfortunately, deaths still occur due to software failure. Using formal methods (techniques from logic and discrete mathematics like set theory, automata theory and formal logic as opposed to continuous mathematics like calculus) and software synthesis, it is possible to reduce this risk by proving certain software properties. Additionally, software synthesis makes it possible to automate some phases of the traditional software development life cycle resulting in a more streamlined and accurate development process.
NASA Technical Reports Server (NTRS)
Morusiewicz, Linda; Valett, Jon
1992-01-01
This document is an annotated bibliography of technical papers, documents, and memorandums produced by or related to the Software Engineering Laboratory. More than 100 publications are summarized. These publications cover many areas of software engineering and range from research reports to software documentation. This document has been updated and reorganized substantially since the original version (SEL-82-006, November 1982). All materials have been grouped into eight general subject areas for easy reference: (1) the Software Engineering Laboratory; (2) the Software Engineering Laboratory: Software Development Documents; (3) Software Tools; (4) Software Models; (5) Software Measurement; (6) Technology Evaluations; (7) Ada Technology; and (8) Data Collection. This document contains an index of these publications classified by individual author.
SAGA: A project to automate the management of software production systems
NASA Technical Reports Server (NTRS)
Campbell, Roy H.; Laliberte, D.; Render, H.; Sum, R.; Smith, W.; Terwilliger, R.
1987-01-01
The Software Automation, Generation and Administration (SAGA) project is investigating the design and construction of practical software engineering environments for developing and maintaining aerospace systems and applications software. The research includes the practical organization of the software lifecycle, configuration management, software requirements specifications, executable specifications, design methodologies, programming, verification, validation and testing, version control, maintenance, the reuse of software, software libraries, documentation, and automated management.
Annotated bibliography of software engineering laboratory literature
NASA Technical Reports Server (NTRS)
Groves, Paula; Valett, Jon
1990-01-01
An annotated bibliography of technical papers, documents, and memorandums produced by or related to the Software Engineering Laboratory is given. More than 100 publications are summarized. These publications cover many areas of software engineering and range from research reports to software documentation. This document has been updated and reorganized substantially since the original version (SEL-82-006, November 1982). All materials have been grouped into eight general subject areas for easy reference: the Software Engineering Laboratory; the Software Engineering Laboratory-software development documents; software tools; software models; software measurement; technology evaluations; Ada technology; and data collection. Subject and author indexes further classify these documents by specific topic and individual author.
Annotated bibliography of Software Engineering Laboratory literature
NASA Technical Reports Server (NTRS)
Morusiewicz, Linda; Valett, Jon
1993-01-01
This document is an annotated bibliography of technical papers, documents, and memorandums produced by or related to the Software Engineering Laboratory. Nearly 200 publications are summarized. These publications cover many areas of software engineering and range from research reports to software documentation. This document has been updated and reorganized substantially since the original version (SEL-82-006, November 1982). All materials have been grouped into eight general subject areas for easy reference: the Software Engineering Laboratory; the Software Engineering Laboratory: software development documents; software tools; software models; software measurement; technology evaluations; Ada technology; and data collection. This document contains an index of these publications classified by individual author.
Code of Federal Regulations, 2011 CFR
2011-10-01
... deferred ordering of computer software and computer software documentation. 227.7203-8 Section 227.7203-8... GENERAL CONTRACTING REQUIREMENTS PATENTS, DATA, AND COPYRIGHTS Rights in Computer Software and Computer Software Documentation 227.7203-8 Deferred delivery and deferred ordering of computer software and computer...
Code of Federal Regulations, 2012 CFR
2012-10-01
... deferred ordering of computer software and computer software documentation. 227.7203-8 Section 227.7203-8... GENERAL CONTRACTING REQUIREMENTS PATENTS, DATA, AND COPYRIGHTS Rights in Computer Software and Computer Software Documentation 227.7203-8 Deferred delivery and deferred ordering of computer software and computer...
Code of Federal Regulations, 2014 CFR
2014-10-01
... deferred ordering of computer software and computer software documentation. 227.7203-8 Section 227.7203-8... GENERAL CONTRACTING REQUIREMENTS PATENTS, DATA, AND COPYRIGHTS Rights in Computer Software and Computer Software Documentation 227.7203-8 Deferred delivery and deferred ordering of computer software and computer...
Code of Federal Regulations, 2013 CFR
2013-10-01
... deferred ordering of computer software and computer software documentation. 227.7203-8 Section 227.7203-8... GENERAL CONTRACTING REQUIREMENTS PATENTS, DATA, AND COPYRIGHTS Rights in Computer Software and Computer Software Documentation 227.7203-8 Deferred delivery and deferred ordering of computer software and computer...
Code of Federal Regulations, 2010 CFR
2010-10-01
... deferred ordering of computer software and computer software documentation. 227.7203-8 Section 227.7203-8... GENERAL CONTRACTING REQUIREMENTS PATENTS, DATA, AND COPYRIGHTS Rights in Computer Software and Computer Software Documentation 227.7203-8 Deferred delivery and deferred ordering of computer software and computer...
A Framework of the Use of Information in Software Testing
ERIC Educational Resources Information Center
Kaveh, Payman
2010-01-01
With the increasing role that software systems play in our daily lives, software quality has become extremely important. Software quality is impacted by the efficiency of the software testing process. There are a growing number of software testing methodologies, models, and initiatives to satisfy the need to improve software quality. The main…
NASA's Approach to Software Assurance
NASA Technical Reports Server (NTRS)
Wetherholt, Martha
2015-01-01
NASA defines software assurance as: the planned and systematic set of activities that ensure conformance of software life cycle processes and products to requirements, standards, and procedures via quality, safety, reliability, and independent verification and validation. NASA's implementation of this approach to the quality, safety, reliability, security and verification and validation of software is brought together in one discipline, software assurance. Organizationally, NASA has software assurance at each NASA center, a Software Assurance Manager at NASA Headquarters, a Software Assurance Technical Fellow (currently the same person as the SA Manager), and an Independent Verification and Validation Organization with its own facility. An umbrella risk mitigation strategy for safety and mission success assurance of NASA's software, software assurance covers a wide area and is better structured to address the dynamic changes in how software is developed, used, and managed, as well as it's increasingly complex functionality. Being flexible, risk based, and prepared for challenges in software at NASA is essential, especially as much of our software is unique for each mission.
1990-02-01
inspections are performed before each formal review of each software life cycle phase. * Required software audits are performed . " The software is acceptable... Audits : Software audits are performed bySQA consistent with thegeneral audit rules and an auditreportis prepared. Software Quality Inspection (SQI...DSD Software Development Method 3-34 DEFINITION OF ACRONYMS Acronym Full Name or Description MACH Methode d’Analyse et de Conception Flierarchisee
Evolution of Secondary Software Businesses: Understanding Industry Dynamics
NASA Astrophysics Data System (ADS)
Tyrväinen, Pasi; Warsta, Juhani; Seppänen, Veikko
Primary software industry originates from IBM's decision to unbundle software-related computer system development activities to external partners. This kind of outsourcing from an enterprise internal software development activity is a common means to start a new software business serving a vertical software market. It combines knowledge of the vertical market process with competence in software development. In this research, we present and analyze the key figures of the Finnish secondary software industry, in order to quantify its interaction with the primary software industry during the period of 2000-2003. On the basis of the empirical data, we present a model for evolution of a secondary software business, which makes explicit the industry dynamics. It represents the shift from internal software developed for competitive advantage to development of products supporting standard business processes on top of standardized technologies. We also discuss the implications for software business strategies in each phase.
Secure software practices among Malaysian software practitioners: An exploratory study
NASA Astrophysics Data System (ADS)
Mohamed, Shafinah Farvin Packeer; Baharom, Fauziah; Deraman, Aziz; Yahya, Jamaiah; Mohd, Haslina
2016-08-01
Secure software practices is increasingly gaining much importance among software practitioners and researchers due to the rise of computer crimes in the software industry. It has become as one of the determinant factors for producing high quality software. Even though its importance has been revealed, its current practice in the software industry is still scarce, particularly in Malaysia. Thus, an exploratory study is conducted among software practitioners in Malaysia to study their experiences and practices in the real-world projects. This paper discusses the findings from the study, which involved 93 software practitioners. Structured questionnaire is utilized for data collection purpose whilst statistical methods such as frequency, mean, and cross tabulation are used for data analysis. Outcomes from this study reveal that software practitioners are becoming increasingly aware on the importance of secure software practices, however, they lack of appropriate implementation, which could affect the quality of produced software.
The Role and Quality of Software Safety in the NASA Constellation Program
NASA Technical Reports Server (NTRS)
Layman, Lucas; Basili, Victor R.; Zelkowitz, Marvin V.
2010-01-01
In this study, we examine software safety risk in the early design phase of the NASA Constellation spaceflight program. Obtaining an accurate, program-wide picture of software safety risk is difficult across multiple, independently-developing systems. We leverage one source of safety information, hazard analysis, to provide NASA quality assurance managers with information regarding the ongoing state of software safety across the program. The goal of this research is two-fold: 1) to quantify the relative importance of software with respect to system safety; and 2) to quantify the level of risk presented by software in the hazard analysis. We examined 154 hazard reports created during the preliminary design phase of three major flight hardware systems within the Constellation program. To quantify the importance of software, we collected metrics based on the number of software-related causes and controls of hazardous conditions. To quantify the level of risk presented by software, we created a metric scheme to measure the specificity of these software causes. We found that from 49-70% of hazardous conditions in the three systems could be caused by software or software was involved in the prevention of the hazardous condition. We also found that 12-17% of the 2013 hazard causes involved software, and that 23-29% of all causes had a software control. Furthermore, 10-12% of all controls were software-based. There is potential for inaccuracy in these counts, however, as software causes are not consistently scoped, and the presence of software in a cause or control is not always clear. The application of our software specificity metrics also identified risks in the hazard reporting process. In particular, we found a number of traceability risks in the hazard reports may impede verification of software and system safety.
A UML-based metamodel for software evolution process
NASA Astrophysics Data System (ADS)
Jiang, Zuo; Zhou, Wei-Hong; Fu, Zhi-Tao; Xiong, Shun-Qing
2014-04-01
A software evolution process is a set of interrelated software processes under which the corresponding software is evolving. An object-oriented software evolution process meta-model (OO-EPMM), abstract syntax and formal OCL constraint of meta-model are presented in this paper. OO-EPMM can not only represent software development process, but also represent software evolution.
48 CFR 227.7202-4 - Contract clause.
Code of Federal Regulations, 2012 CFR
2012-10-01
... Software and Computer Software Documentation 227.7202-4 Contract clause. A specific contract clause governing the Government's rights in commercial computer software or commercial computer software..., release, perform, display, or disclose computer software or computer software documentation shall be...
48 CFR 227.7202-4 - Contract clause.
Code of Federal Regulations, 2011 CFR
2011-10-01
... Software and Computer Software Documentation 227.7202-4 Contract clause. A specific contract clause governing the Government's rights in commercial computer software or commercial computer software..., release, perform, display, or disclose computer software or computer software documentation shall be...
48 CFR 227.7202-4 - Contract clause.
Code of Federal Regulations, 2014 CFR
2014-10-01
... Software and Computer Software Documentation 227.7202-4 Contract clause. A specific contract clause governing the Government's rights in commercial computer software or commercial computer software..., release, perform, display, or disclose computer software or computer software documentation shall be...
48 CFR 227.7202-4 - Contract clause.
Code of Federal Regulations, 2013 CFR
2013-10-01
... Software and Computer Software Documentation 227.7202-4 Contract clause. A specific contract clause governing the Government's rights in commercial computer software or commercial computer software..., release, perform, display, or disclose computer software or computer software documentation shall be...
48 CFR 227.7202-4 - Contract clause.
Code of Federal Regulations, 2010 CFR
2010-10-01
... Software and Computer Software Documentation 227.7202-4 Contract clause. A specific contract clause governing the Government's rights in commercial computer software or commercial computer software..., release, perform, display, or disclose computer software or computer software documentation shall be...
NASA Astrophysics Data System (ADS)
Yetman, G.; Downs, R. R.
2011-12-01
Software deployment is needed to process and distribute scientific data throughout the data lifecycle. Developing software in-house can take software development teams away from other software development projects and can require efforts to maintain the software over time. Adopting and reusing software and system modules that have been previously developed by others can reduce in-house software development and maintenance costs and can contribute to the quality of the system being developed. A variety of models are available for reusing and deploying software and systems that have been developed by others. These deployment models include open source software, vendor-supported open source software, commercial software, and combinations of these approaches. Deployment in Earth science data processing and distribution has demonstrated the advantages and drawbacks of each model. Deploying open source software offers advantages for developing and maintaining scientific data processing systems and applications. By joining an open source community that is developing a particular system module or application, a scientific data processing team can contribute to aspects of the software development without having to commit to developing the software alone. Communities of interested developers can share the work while focusing on activities that utilize in-house expertise and addresses internal requirements. Maintenance is also shared by members of the community. Deploying vendor-supported open source software offers similar advantages to open source software. However, by procuring the services of a vendor, the in-house team can rely on the vendor to provide, install, and maintain the software over time. Vendor-supported open source software may be ideal for teams that recognize the value of an open source software component or application and would like to contribute to the effort, but do not have the time or expertise to contribute extensively. Vendor-supported software may also have the additional benefits of guaranteed up-time, bug fixes, and vendor-added enhancements. Deploying commercial software can be advantageous for obtaining system or software components offered by a vendor that meet in-house requirements. The vendor can be contracted to provide installation, support and maintenance services as needed. Combining these options offers a menu of choices, enabling selection of system components or software modules that meet the evolving requirements encountered throughout the scientific data lifecycle.
Adopting Open Source Software to Address Software Risks during the Scientific Data Life Cycle
NASA Astrophysics Data System (ADS)
Vinay, S.; Downs, R. R.
2012-12-01
Software enables the creation, management, storage, distribution, discovery, and use of scientific data throughout the data lifecycle. However, the capabilities offered by software also present risks for the stewardship of scientific data, since future access to digital data is dependent on the use of software. From operating systems to applications for analyzing data, the dependence of data on software presents challenges for the stewardship of scientific data. Adopting open source software provides opportunities to address some of the proprietary risks of data dependence on software. For example, in some cases, open source software can be deployed to avoid licensing restrictions for using, modifying, and transferring proprietary software. The availability of the source code of open source software also enables the inclusion of modifications, which may be contributed by various community members who are addressing similar issues. Likewise, an active community that is maintaining open source software can be a valuable source of help, providing an opportunity to collaborate to address common issues facing adopters. As part of the effort to meet the challenges of software dependence for scientific data stewardship, risks from software dependence have been identified that exist during various times of the data lifecycle. The identification of these risks should enable the development of plans for mitigating software dependencies, where applicable, using open source software, and to improve understanding of software dependency risks for scientific data and how they can be reduced during the data life cycle.
Software technology insertion: A study of success factors
NASA Technical Reports Server (NTRS)
Lydon, Tom
1990-01-01
Managing software development in large organizations has become increasingly difficult due to increasing technical complexity, stricter government standards, a shortage of experienced software engineers, competitive pressure for improved productivity and quality, the need to co-develop hardware and software together, and the rapid changes in both hardware and software technology. The 'software factory' approach to software development minimizes risks while maximizing productivity and quality through standardization, automation, and training. However, in practice, this approach is relatively inflexible when adopting new software technologies. The methods that a large multi-project software engineering organization can use to increase the likelihood of successful software technology insertion (STI), especially in a standardized engineering environment, are described.
Software archeology: a case study in software quality assurance and design
DOE Office of Scientific and Technical Information (OSTI.GOV)
Macdonald, John M; Lloyd, Jane A; Turner, Cameron J
2009-01-01
Ideally, quality is designed into software, just as quality is designed into hardware. However, when dealing with legacy systems, demonstrating that the software meets required quality standards may be difficult to achieve. As the need to demonstrate the quality of existing software was recognized at Los Alamos National Laboratory (LANL), an effort was initiated to uncover and demonstrate that legacy software met the required quality standards. This effort led to the development of a reverse engineering approach referred to as software archaeology. This paper documents the software archaeology approaches used at LANL to document legacy software systems. A case studymore » for the Robotic Integrated Packaging System (RIPS) software is included.« less
Annotated bibliography of software engineering laboratory literature
NASA Technical Reports Server (NTRS)
Kistler, David; Bristow, John; Smith, Don
1994-01-01
This document is an annotated bibliography of technical papers, documents, and memorandums produced by or related to the Software Engineering Laboratory. Nearly 200 publications are summarized. These publications cover many areas of software engineering and range from research reports to software documentation. This document has been updated and reorganized substantially since the original version (SEL-82-006, November 1982). All materials have been grouped into eight general subject areas for easy reference: (1) The Software Engineering Laboratory; (2) The Software Engineering Laboratory: Software Development Documents; (3) Software Tools; (4) Software Models; (5) Software Measurement; (6) Technology Evaluations; (7) Ada Technology; and (8) Data Collection. This document contains an index of these publications classified by individual author.
Reuse Metrics for Object Oriented Software
NASA Technical Reports Server (NTRS)
Bieman, James M.
1998-01-01
One way to increase the quality of software products and the productivity of software development is to reuse existing software components when building new software systems. In order to monitor improvements in reuse, the level of reuse must be measured. In this NASA supported project we (1) derived a suite of metrics which quantify reuse attributes for object oriented, object based, and procedural software, (2) designed prototype tools to take these measurements in Ada, C++, Java, and C software, (3) evaluated the reuse in available software, (4) analyzed the relationship between coupling, cohesion, inheritance, and reuse, (5) collected object oriented software systems for our empirical analyses, and (6) developed quantitative criteria and methods for restructuring software to improve reusability.
48 CFR 12.212 - Computer software.
Code of Federal Regulations, 2012 CFR
2012-10-01
... 48 Federal Acquisition Regulations System 1 2012-10-01 2012-10-01 false Computer software. 12.212... software. (a) Commercial computer software or commercial computer software documentation shall be acquired... required to— (1) Furnish technical information related to commercial computer software or commercial...
48 CFR 12.212 - Computer software.
Code of Federal Regulations, 2011 CFR
2011-10-01
... 48 Federal Acquisition Regulations System 1 2011-10-01 2011-10-01 false Computer software. 12.212... software. (a) Commercial computer software or commercial computer software documentation shall be acquired... required to— (1) Furnish technical information related to commercial computer software or commercial...
48 CFR 227.7203-9 - Copyright.
Code of Federal Regulations, 2010 CFR
2010-10-01
... Software and Computer Software Documentation 227.7203-9 Copyright. (a) Copyright license. (1) The clause at 252.227-7014, Rights in Noncommercial Computer Software and Noncommercial Computer Software... Government to reproduce the software or documentation, distribute copies, perform or display the software or...
48 CFR 227.7203-9 - Copyright.
Code of Federal Regulations, 2013 CFR
2013-10-01
... Software and Computer Software Documentation 227.7203-9 Copyright. (a) Copyright license. (1) The clause at 252.227-7014, Rights in Noncommercial Computer Software and Noncommercial Computer Software... Government to reproduce the software or documentation, distribute copies, perform or display the software or...
48 CFR 227.7203-9 - Copyright.
Code of Federal Regulations, 2011 CFR
2011-10-01
... Software and Computer Software Documentation 227.7203-9 Copyright. (a) Copyright license. (1) The clause at 252.227-7014, Rights in Noncommercial Computer Software and Noncommercial Computer Software... Government to reproduce the software or documentation, distribute copies, perform or display the software or...
48 CFR 12.212 - Computer software.
Code of Federal Regulations, 2014 CFR
2014-10-01
... 48 Federal Acquisition Regulations System 1 2014-10-01 2014-10-01 false Computer software. 12.212... software. (a) Commercial computer software or commercial computer software documentation shall be acquired... required to— (1) Furnish technical information related to commercial computer software or commercial...
48 CFR 12.212 - Computer software.
Code of Federal Regulations, 2010 CFR
2010-10-01
... 48 Federal Acquisition Regulations System 1 2010-10-01 2010-10-01 false Computer software. 12.212... software. (a) Commercial computer software or commercial computer software documentation shall be acquired... required to— (1) Furnish technical information related to commercial computer software or commercial...
48 CFR 227.7203-9 - Copyright.
Code of Federal Regulations, 2014 CFR
2014-10-01
... Software and Computer Software Documentation 227.7203-9 Copyright. (a) Copyright license. (1) The clause at 252.227-7014, Rights in Noncommercial Computer Software and Noncommercial Computer Software... Government to reproduce the software or documentation, distribute copies, perform or display the software or...
48 CFR 12.212 - Computer software.
Code of Federal Regulations, 2013 CFR
2013-10-01
... 48 Federal Acquisition Regulations System 1 2013-10-01 2013-10-01 false Computer software. 12.212... software. (a) Commercial computer software or commercial computer software documentation shall be acquired... required to— (1) Furnish technical information related to commercial computer software or commercial...
48 CFR 227.7203-9 - Copyright.
Code of Federal Regulations, 2012 CFR
2012-10-01
... Software and Computer Software Documentation 227.7203-9 Copyright. (a) Copyright license. (1) The clause at 252.227-7014, Rights in Noncommercial Computer Software and Noncommercial Computer Software... Government to reproduce the software or documentation, distribute copies, perform or display the software or...
Educational Software Acquisition for Microcomputers.
ERIC Educational Resources Information Center
Erikson, Warren; Turban, Efraim
1985-01-01
Examination of issues involved in acquiring appropriate microcomputer software for higher education focuses on the following points: developing your own software; finding commercially available software; using published evaluations; pre-purchase testing; customizing and adapting commercial software; post-purchase testing; and software use. A…
A Model for Assessing the Liability of Seemingly Correct Software
NASA Technical Reports Server (NTRS)
Voas, Jeffrey M.; Voas, Larry K.; Miller, Keith W.
1991-01-01
Current research on software reliability does not lend itself to quantitatively assessing the risk posed by a piece of life-critical software. Black-box software reliability models are too general and make too many assumptions to be applied confidently to assessing the risk of life-critical software. We present a model for assessing the risk caused by a piece of software; this model combines software testing results and Hamlet's probable correctness model. We show how this model can assess software risk for those who insure against a loss that can occur if life-critical software fails.
NASA space station software standards issues
NASA Technical Reports Server (NTRS)
Tice, G. D., Jr.
1985-01-01
The selection and application of software standards present the NASA Space Station Program with the opportunity to serve as a pacesetter for the United States software in the area of software standards. The strengths and weaknesses of each of the NASA defined software standards issues are summerized and discussed. Several significant standards issues are offered for NASA consideration. A challenge is presented for the NASA Space Station Program to serve as a pacesetter for the U.S. Software Industry through: (1) Management commitment to software standards; (2) Overall program participation in software standards; and (3) Employment of the best available technology to support software standards
Statistical modelling of software reliability
NASA Technical Reports Server (NTRS)
Miller, Douglas R.
1991-01-01
During the six-month period from 1 April 1991 to 30 September 1991 the following research papers in statistical modeling of software reliability appeared: (1) A Nonparametric Software Reliability Growth Model; (2) On the Use and the Performance of Software Reliability Growth Models; (3) Research and Development Issues in Software Reliability Engineering; (4) Special Issues on Software; and (5) Software Reliability and Safety.
Software Engineering Guidebook
NASA Technical Reports Server (NTRS)
Connell, John; Wenneson, Greg
1993-01-01
The Software Engineering Guidebook describes SEPG (Software Engineering Process Group) supported processes and techniques for engineering quality software in NASA environments. Three process models are supported: structured, object-oriented, and evolutionary rapid-prototyping. The guidebook covers software life-cycles, engineering, assurance, and configuration management. The guidebook is written for managers and engineers who manage, develop, enhance, and/or maintain software under the Computer Software Services Contract.
A measurement system for large, complex software programs
NASA Technical Reports Server (NTRS)
Rone, Kyle Y.; Olson, Kitty M.; Davis, Nathan E.
1994-01-01
This paper describes measurement systems required to forecast, measure, and control activities for large, complex software development and support programs. Initial software cost and quality analysis provides the foundation for meaningful management decisions as a project evolves. In modeling the cost and quality of software systems, the relationship between the functionality, quality, cost, and schedule of the product must be considered. This explicit relationship is dictated by the criticality of the software being developed. This balance between cost and quality is a viable software engineering trade-off throughout the life cycle. Therefore, the ability to accurately estimate the cost and quality of software systems is essential to providing reliable software on time and within budget. Software cost models relate the product error rate to the percent of the project labor that is required for independent verification and validation. The criticality of the software determines which cost model is used to estimate the labor required to develop the software. Software quality models yield an expected error discovery rate based on the software size, criticality, software development environment, and the level of competence of the project and developers with respect to the processes being employed.
Certification Processes for Safety-Critical and Mission-Critical Aerospace Software
NASA Technical Reports Server (NTRS)
Nelson, Stacy
2003-01-01
This document is a quick reference guide with an overview of the processes required to certify safety-critical and mission-critical flight software at selected NASA centers and the FAA. Researchers and software developers can use this guide to jumpstart their understanding of how to get new or enhanced software onboard an aircraft or spacecraft. The introduction contains aerospace industry definitions of safety and safety-critical software, as well as, the current rationale for certification of safety-critical software. The Standards for Safety-Critical Aerospace Software section lists and describes current standards including NASA standards and RTCA DO-178B. The Mission-Critical versus Safety-Critical software section explains the difference between two important classes of software: safety-critical software involving the potential for loss of life due to software failure and mission-critical software involving the potential for aborting a mission due to software failure. The DO-178B Safety-critical Certification Requirements section describes special processes and methods required to obtain a safety-critical certification for aerospace software flying on vehicles under auspices of the FAA. The final two sections give an overview of the certification process used at Dryden Flight Research Center and the approval process at the Jet Propulsion Lab (JPL).
NASA PC software evaluation project
NASA Technical Reports Server (NTRS)
Dominick, Wayne D. (Editor); Kuan, Julie C.
1986-01-01
The USL NASA PC software evaluation project is intended to provide a structured framework for facilitating the development of quality NASA PC software products. The project will assist NASA PC development staff to understand the characteristics and functions of NASA PC software products. Based on the results of the project teams' evaluations and recommendations, users can judge the reliability, usability, acceptability, maintainability and customizability of all the PC software products. The objective here is to provide initial, high-level specifications and guidelines for NASA PC software evaluation. The primary tasks to be addressed in this project are as follows: to gain a strong understanding of what software evaluation entails and how to organize a structured software evaluation process; to define a structured methodology for conducting the software evaluation process; to develop a set of PC software evaluation criteria and evaluation rating scales; and to conduct PC software evaluations in accordance with the identified methodology. Communication Packages, Network System Software, Graphics Support Software, Environment Management Software, General Utilities. This report represents one of the 72 attachment reports to the University of Southwestern Louisiana's Final Report on NASA Grant NGT-19-010-900. Accordingly, appropriate care should be taken in using this report out of context of the full Final Report.
User systems guidelines for software projects
DOE Office of Scientific and Technical Information (OSTI.GOV)
Abrahamson, L.
1986-04-01
This manual presents guidelines for software standards which were developed so that software project-development teams and management involved in approving the software could have a generalized view of all phases in the software production procedure and the steps involved in completing each phase. Guidelines are presented for six phases of software development: project definition, building a user interface, designing software, writing code, testing code, and preparing software documentation. The discussions for each phase include examples illustrating the recommended guidelines. 45 refs. (DWL)
48 CFR 208.7400 - Scope of subpart.
Code of Federal Regulations, 2013 CFR
2013-10-01
... OF DEFENSE ACQUISITION PLANNING REQUIRED SOURCES OF SUPPLIES AND SERVICES Enterprise Software... commercial software and software maintenance, including software and software maintenance that is acquired...
48 CFR 208.7400 - Scope of subpart.
Code of Federal Regulations, 2012 CFR
2012-10-01
... OF DEFENSE ACQUISITION PLANNING REQUIRED SOURCES OF SUPPLIES AND SERVICES Enterprise Software... commercial software and software maintenance, including software and software maintenance that is acquired...
48 CFR 208.7400 - Scope of subpart.
Code of Federal Regulations, 2011 CFR
2011-10-01
... OF DEFENSE ACQUISITION PLANNING REQUIRED SOURCES OF SUPPLIES AND SERVICES Enterprise Software... commercial software and software maintenance, including software and software maintenance that is acquired...
48 CFR 208.7400 - Scope of subpart.
Code of Federal Regulations, 2014 CFR
2014-10-01
... OF DEFENSE ACQUISITION PLANNING REQUIRED SOURCES OF SUPPLIES AND SERVICES Enterprise Software... commercial software and software maintenance, including software and software maintenance that is acquired...
Guidance and Control Software Project Data - Volume 1: Planning Documents
NASA Technical Reports Server (NTRS)
Hayhurst, Kelly J. (Editor)
2008-01-01
The Guidance and Control Software (GCS) project was the last in a series of software reliability studies conducted at Langley Research Center between 1977 and 1994. The technical results of the GCS project were recorded after the experiment was completed. Some of the support documentation produced as part of the experiment, however, is serving an unexpected role far beyond its original project context. Some of the software used as part of the GCS project was developed to conform to the RTCA/DO-178B software standard, "Software Considerations in Airborne Systems and Equipment Certification," used in the civil aviation industry. That standard requires extensive documentation throughout the software development life cycle, including plans, software requirements, design and source code, verification cases and results, and configuration management and quality control data. The project documentation that includes this information is open for public scrutiny without the legal or safety implications associated with comparable data from an avionics manufacturer. This public availability has afforded an opportunity to use the GCS project documents for DO-178B training. This report provides a brief overview of the GCS project, describes the 4-volume set of documents and the role they are playing in training, and includes the planning documents from the GCS project. Volume 1 contains five appendices: A. Plan for Software Aspects of Certification for the Guidance and Control Software Project; B. Software Development Standards for the Guidance and Control Software Project; C. Software Verification Plan for the Guidance and Control Software Project; D. Software Configuration Management Plan for the Guidance and Control Software Project; and E. Software Quality Assurance Activities.
Improving Software Engineering on NASA Projects
NASA Technical Reports Server (NTRS)
Crumbley, Tim; Kelly, John C.
2010-01-01
Software Engineering Initiative: Reduces risk of software failure -Increases mission safety. More predictable software cost estimates and delivery schedules. Smarter buyer of contracted out software. More defects found and removed earlier. Reduces duplication of efforts between projects. Increases ability to meet the challenges of evolving software technology.
A Quantitative Study of Global Software Development Teams, Requirements, and Software Projects
ERIC Educational Resources Information Center
Parker, Linda L.
2016-01-01
The study explored the relationship between global software development teams, effective software requirements, and stakeholders' perception of successful software development projects within the field of information technology management. It examined the critical relationship between Global Software Development (GSD) teams creating effective…
Software Assurance Competency Model
2013-03-01
COTS) software , and software as a service ( SaaS ). L2: Define and analyze risks in the acquisition of contracted software , COTS software , and SaaS ...2010a]: Application of technologies and processes to achieve a required level of confidence that software systems and services function in the...
The Elements of an Effective Software Development Plan - Software Development Process Guidebook
2011-11-11
standards and practices required for all XMPL software development. This SDP implements the <corporate> Standard Software Process (SSP). as tailored...Developing and integrating reusable software products • Approach to managing COTS/Reuse software implementation • COTS/Reuse software selection...final selection and submit to change board for approval MAINTENANCE Monitor current products for obsolescence or end of support Track new
Software safety - A user's practical perspective
NASA Technical Reports Server (NTRS)
Dunn, William R.; Corliss, Lloyd D.
1990-01-01
Software safety assurance philosophy and practices at the NASA Ames are discussed. It is shown that, to be safe, software must be error-free. Software developments on two digital flight control systems and two ground facility systems are examined, including the overall system and software organization and function, the software-safety issues, and their resolution. The effectiveness of safety assurance methods is discussed, including conventional life-cycle practices, verification and validation testing, software safety analysis, and formal design methods. It is concluded (1) that a practical software safety technology does not yet exist, (2) that it is unlikely that a set of general-purpose analytical techniques can be developed for proving that software is safe, and (3) that successful software safety-assurance practices will have to take into account the detailed design processes employed and show that the software will execute correctly under all possible conditions.
Predicting Software Suitability Using a Bayesian Belief Network
NASA Technical Reports Server (NTRS)
Beaver, Justin M.; Schiavone, Guy A.; Berrios, Joseph S.
2005-01-01
The ability to reliably predict the end quality of software under development presents a significant advantage for a development team. It provides an opportunity to address high risk components earlier in the development life cycle, when their impact is minimized. This research proposes a model that captures the evolution of the quality of a software product, and provides reliable forecasts of the end quality of the software being developed in terms of product suitability. Development team skill, software process maturity, and software problem complexity are hypothesized as driving factors of software product quality. The cause-effect relationships between these factors and the elements of software suitability are modeled using Bayesian Belief Networks, a machine learning method. This research presents a Bayesian Network for software quality, and the techniques used to quantify the factors that influence and represent software quality. The developed model is found to be effective in predicting the end product quality of small-scale software development efforts.
The Effects of Development Team Skill on Software Product Quality
NASA Technical Reports Server (NTRS)
Beaver, Justin M.; Schiavone, Guy A.
2006-01-01
This paper provides an analysis of the effect of the skill/experience of the software development team on the quality of the final software product. A method for the assessment of software development team skill and experience is proposed, and was derived from a workforce management tool currently in use by the National Aeronautics and Space Administration. Using data from 26 smallscale software development projects, the team skill measures are correlated to 5 software product quality metrics from the ISO/IEC 9126 Software Engineering Product Quality standard. in the analysis of the results, development team skill is found to be a significant factor in the adequacy of the design and implementation. In addition, the results imply that inexperienced software developers are tasked with responsibilities ill-suited to their skill level, and thus have a significant adverse effect on the quality of the software product. Keywords: software quality, development skill, software metrics
An ontology based trust verification of software license agreement
NASA Astrophysics Data System (ADS)
Lu, Wenhuan; Li, Xiaoqing; Gan, Zengqin; Wei, Jianguo
2017-08-01
When we install software or download software, there will show up so big mass document to state the rights and obligations, for which lots of person are not patient to read it or understand it. That would may make users feel distrust for the software. In this paper, we propose an ontology based verification for Software License Agreement. First of all, this work proposed an ontology model for domain of Software License Agreement. The domain ontology is constructed by proposed methodology according to copyright laws and 30 software license agreements. The License Ontology can act as a part of generalized copyright law knowledge model, and also can work as visualization of software licenses. Based on this proposed ontology, a software license oriented text summarization approach is proposed which performances showing that it can improve the accuracy of software licenses summarizing. Based on the summarization, the underline purpose of the software license can be explicitly explored for trust verification.
Federal Register 2010, 2011, 2012, 2013, 2014
2012-08-22
... Computer Software and Complex Electronics Used in Safety Systems of Nuclear Power Plants AGENCY: Nuclear...-1209, ``Software Requirement Specifications for Digital Computer Software and Complex Electronics used... Electronics Engineers (ANSI/IEEE) Standard 830-1998, ``IEEE Recommended Practice for Software Requirements...
Impact of Agile Software Development Model on Software Maintainability
ERIC Educational Resources Information Center
Gawali, Ajay R.
2012-01-01
Software maintenance and support costs account for up to 60% of the overall software life cycle cost and often burdens tightly budgeted information technology (IT) organizations. Agile software development approach delivers business value early, but implications on software maintainability are still unknown. The purpose of this quantitative study…
Federal Register 2010, 2011, 2012, 2013, 2014
2012-08-22
... NUCLEAR REGULATORY COMMISSION [NRC-2012-0195] Developing Software Life Cycle Processes for Digital... Software Life Cycle Processes for Digital Computer Software used in Safety Systems of Nuclear Power Plants... clarifications, the enhanced consensus practices for developing software life-cycle processes for digital...
Proceedings of Tenth Annual Software Engineering Workshop
NASA Technical Reports Server (NTRS)
1985-01-01
Papers are presented on the following topics: measurement of software technology, recent studies of the Software Engineering Lab, software management tools, expert systems, error seeding as a program validation technique, software quality assurance, software engineering environments (including knowledge-based environments), the Distributed Computing Design System, and various Ada experiments.
Reducing Risk in DoD Software-Intensive Systems Development
2016-03-01
intensive systems development risk. This research addresses the use of the Technical Readiness Assessment (TRA) using the nine-level software Technology...The software TRLs are ineffective in reducing technical risk for the software component development. • Without the software TRLs, there is no...effective method to perform software TRA or reduce the technical development risk. The software component will behave as a new, untried technology in nearly
Software Formal Inspections Standard
NASA Technical Reports Server (NTRS)
1993-01-01
This Software Formal Inspections Standard (hereinafter referred to as Standard) is applicable to NASA software. This Standard defines the requirements that shall be fulfilled by the software formal inspections process whenever this process is specified for NASA software. The objective of this Standard is to define the requirements for a process that inspects software products to detect and eliminate defects as early as possible in the software life cycle. The process also provides for the collection and analysis of inspection data to improve the inspection process as well as the quality of the software.
Annotated bibliography of software engineering laboratory literature
NASA Technical Reports Server (NTRS)
Buhler, Melanie; Valett, Jon
1989-01-01
An annotated bibliography is presented of technical papers, documents, and memorandums produced by or related to the Software Engineering Laboratory. The bibliography was updated and reorganized substantially since the original version (SEL-82-006, November 1982). All materials were grouped into eight general subject areas for easy reference: (1) The Software Engineering Laboratory; (2) The Software Engineering Laboratory: Software Development Documents; (3) Software Tools; (4) Software Models; (5) Software Measurement; (6) Technology Evaluations; (7) Ada Technology; and (8) Data Collection. Subject and author indexes further classify these documents by specific topic and individual author.
Software Program: Software Management Guidebook
NASA Technical Reports Server (NTRS)
1996-01-01
The purpose of this NASA Software Management Guidebook is twofold. First, this document defines the core products and activities required of NASA software projects. It defines life-cycle models and activity-related methods but acknowledges that no single life-cycle model is appropriate for all NASA software projects. It also acknowledges that the appropriate method for accomplishing a required activity depends on characteristics of the software project. Second, this guidebook provides specific guidance to software project managers and team leaders in selecting appropriate life cycles and methods to develop a tailored plan for a software engineering project.
NASA Technical Reports Server (NTRS)
Mckee, James W.
1990-01-01
This volume (1 of 4) gives a summary of the original AMPS software system configuration, points out some of the problem areas in the original software design that this project is to address, and in the appendix collects all the bimonthly status reports. The purpose of AMPS is to provide a self reliant system to control the generation and distribution of power in the space station. The software in the AMPS breadboard can be divided into three levels: the operating environment software, the protocol software, and the station specific software. This project deals only with the operating environment software and the protocol software. The present station specific software will not change except as necessary to conform to new data formats.
NASA Technical Reports Server (NTRS)
Hayhurst, Kelly J. (Editor)
2008-01-01
The Guidance and Control Software (GCS) project was the last in a series of software reliability studies conducted at Langley Research Center between 1977 and 1994. The technical results of the GCS project were recorded after the experiment was completed. Some of the support documentation produced as part of the experiment, however, is serving an unexpected role far beyond its original project context. Some of the software used as part of the GCS project was developed to conform to the RTCA/DO-178B software standard, "Software Considerations in Airborne Systems and Equipment Certification," used in the civil aviation industry. That standard requires extensive documentation throughout the software development life cycle, including plans, software requirements, design and source code, verification cases and results, and configuration management and quality control data. The project documentation that includes this information is open for public scrutiny without the legal or safety implications associated with comparable data from an avionics manufacturer. This public availability has afforded an opportunity to use the GCS project documents for DO-178B training. This report provides a brief overview of the GCS project, describes the 4-volume set of documents and the role they are playing in training, and includes configuration management and quality assurance documents from the GCS project. Volume 4 contains six appendices: A. Software Accomplishment Summary for the Guidance and Control Software Project; B. Software Configuration Index for the Guidance and Control Software Project; C. Configuration Management Records for the Guidance and Control Software Project; D. Software Quality Assurance Records for the Guidance and Control Software Project; E. Problem Report for the Pluto Implementation of the Guidance and Control Software Project; and F. Support Documentation Change Reports for the Guidance and Control Software Project.
A Probabilistic Software System Attribute Acceptance Paradigm for COTS Software Evaluation
NASA Technical Reports Server (NTRS)
Morris, A. Terry
2005-01-01
Standard software requirement formats are written from top-down perspectives only, that is, from an ideal notion of a client s needs. Despite the exactness of the standard format, software and system errors in designed systems have abounded. Bad and inadequate requirements have resulted in cost overruns, schedule slips and lost profitability. Commercial off-the-shelf (COTS) software components are even more troublesome than designed systems because they are often provided as is and subsequently delivered with unsubstantiated validation of described capabilities. For COTS software, there needs to be a way to express the client s software needs in a consistent and formal manner using software system attributes derived from software quality standards. Additionally, the format needs to be amenable to software evaluation processes that integrate observable evidence garnered from historical data. This paper presents a paradigm that effectively bridges the gap between what a client desires (top-down) and what has been demonstrated (bottom-up) for COTS software evaluation. The paradigm addresses the specification of needs before the software evaluation is performed and can be used to increase the shared understanding between clients and software evaluators about what is required and what is technically possible.
Modular Rocket Engine Control Software (MRECS)
NASA Technical Reports Server (NTRS)
Tarrant, Charlie; Crook, Jerry
1997-01-01
The Modular Rocket Engine Control Software (MRECS) Program is a technology demonstration effort designed to advance the state-of-the-art in launch vehicle propulsion systems. Its emphasis is on developing and demonstrating a modular software architecture for a generic, advanced engine control system that will result in lower software maintenance (operations) costs. It effectively accommodates software requirements changes that occur due to hardware. technology upgrades and engine development testing. Ground rules directed by MSFC were to optimize modularity and implement the software in the Ada programming language. MRECS system software and the software development environment utilize Commercial-Off-the-Shelf (COTS) products. This paper presents the objectives and benefits of the program. The software architecture, design, and development environment are described. MRECS tasks are defined and timing relationships given. Major accomplishment are listed. MRECS offers benefits to a wide variety of advanced technology programs in the areas of modular software, architecture, reuse software, and reduced software reverification time related to software changes. Currently, the program is focused on supporting MSFC in accomplishing a Space Shuttle Main Engine (SSME) hot-fire test at Stennis Space Center and the Low Cost Boost Technology (LCBT) Program.
Software Reuse Within the Earth Science Community
NASA Technical Reports Server (NTRS)
Marshall, James J.; Olding, Steve; Wolfe, Robert E.; Delnore, Victor E.
2006-01-01
Scientific missions in the Earth sciences frequently require cost-effective, highly reliable, and easy-to-use software, which can be a challenge for software developers to provide. The NASA Earth Science Enterprise (ESE) spends a significant amount of resources developing software components and other software development artifacts that may also be of value if reused in other projects requiring similar functionality. In general, software reuse is often defined as utilizing existing software artifacts. Software reuse can improve productivity and quality while decreasing the cost of software development, as documented by case studies in the literature. Since large software systems are often the results of the integration of many smaller and sometimes reusable components, ensuring reusability of such software components becomes a necessity. Indeed, designing software components with reusability as a requirement can increase the software reuse potential within a community such as the NASA ESE community. The NASA Earth Science Data Systems (ESDS) Software Reuse Working Group is chartered to oversee the development of a process that will maximize the reuse potential of existing software components while recommending strategies for maximizing the reusability potential of yet-to-be-designed components. As part of this work, two surveys of the Earth science community were conducted. The first was performed in 2004 and distributed among government employees and contractors. A follow-up survey was performed in 2005 and distributed among a wider community, to include members of industry and academia. The surveys were designed to collect information on subjects such as the current software reuse practices of Earth science software developers, why they choose to reuse software, and what perceived barriers prevent them from reusing software. In this paper, we compare the results of these surveys, summarize the observed trends, and discuss the findings. The results are very similar, with the second, larger survey confirming the basic results of the first, smaller survey. The results suggest that reuse of ESE software can drive down the cost and time of system development, increase flexibility and responsiveness of these systems to new technologies and requirements, and increase effective and accountable community participation.
DOE Office of Scientific and Technical Information (OSTI.GOV)
Sturtevant, Judith E.; Heaphy, Robert; Hodges, Ann Louise
2006-09-01
The purpose of the Sandia National Laboratories Advanced Simulation and Computing (ASC) Software Quality Plan is to clearly identify the practices that are the basis for continually improving the quality of ASC software products. The plan defines the ASC program software quality practices and provides mappings of these practices to Sandia Corporate Requirements CPR 1.3.2 and 1.3.6 and to a Department of Energy document, ASCI Software Quality Engineering: Goals, Principles, and Guidelines. This document also identifies ASC management and software project teams responsibilities in implementing the software quality practices and in assessing progress towards achieving their software quality goals.
The Knowledge-Based Software Assistant: Beyond CASE
NASA Technical Reports Server (NTRS)
Carozzoni, Joseph A.
1993-01-01
This paper will outline the similarities and differences between two paradigms of software development. Both support the whole software life cycle and provide automation for most of the software development process, but have different approaches. The CASE approach is based on a set of tools linked by a central data repository. This tool-based approach is data driven and views software development as a series of sequential steps, each resulting in a product. The Knowledge-Based Software Assistant (KBSA) approach, a radical departure from existing software development practices, is knowledge driven and centers around a formalized software development process. KBSA views software development as an incremental, iterative, and evolutionary process with development occurring at the specification level.
Implementing Software Safety in the NASA Environment
NASA Technical Reports Server (NTRS)
Wetherholt, Martha S.; Radley, Charles F.
1994-01-01
Until recently, NASA did not consider allowing computers total control of flight systems. Human operators, via hardware, have constituted the ultimate safety control. In an attempt to reduce costs, NASA has come to rely more and more heavily on computers and software to control space missions. (For example. software is now planned to control most of the operational functions of the International Space Station.) Thus the need for systematic software safety programs has become crucial for mission success. Concurrent engineering principles dictate that safety should be designed into software up front, not tested into the software after the fact. 'Cost of Quality' studies have statistics and metrics to prove the value of building quality and safety into the development cycle. Unfortunately, most software engineers are not familiar with designing for safety, and most safety engineers are not software experts. Software written to specifications which have not been safety analyzed is a major source of computer related accidents. Safer software is achieved step by step throughout the system and software life cycle. It is a process that includes requirements definition, hazard analyses, formal software inspections, safety analyses, testing, and maintenance. The greatest emphasis is placed on clearly and completely defining system and software requirements, including safety and reliability requirements. Unfortunately, development and review of requirements are the weakest link in the process. While some of the more academic methods, e.g. mathematical models, may help bring about safer software, this paper proposes the use of currently approved software methodologies, and sound software and assurance practices to show how, to a large degree, safety can be designed into software from the start. NASA's approach today is to first conduct a preliminary system hazard analysis (PHA) during the concept and planning phase of a project. This determines the overall hazard potential of the system to be built. Shortly thereafter, as the system requirements are being defined, the second iteration of hazard analyses takes place, the systems hazard analysis (SHA). During the systems requirements phase, decisions are made as to what functions of the system will be the responsibility of software. This is the most critical time to affect the safety of the software. From this point, software safety analyses as well as software engineering practices are the main focus for assuring safe software. While many of the steps proposed in this paper seem like just sound engineering practices, they are the best technical and most cost effective means to assure safe software within a safe system.
Software and the future of programming languages.
Aho, Alfred V
2004-02-27
Although software is the key enabler of the global information infrastructure, the amount and extent of software in use in the world today are not widely understood, nor are the programming languages and paradigms that have been used to create the software. The vast size of the embedded base of existing software and the increasing costs of software maintenance, poor security, and limited functionality are posing significant challenges for the software R&D community.
Software engineering and the role of Ada: Executive seminar
NASA Technical Reports Server (NTRS)
Freedman, Glenn B.
1987-01-01
The objective was to introduce the basic terminology and concepts of software engineering and Ada. The life cycle model is reviewed. The application of the goals and principles of software engineering is applied. An introductory understanding of the features of the Ada language is gained. Topics addressed include: the software crises; the mandate of the Space Station Program; software life cycle model; software engineering; and Ada under the software engineering umbrella.
40 CFR 725.54 - Suspension of the review period.
Code of Federal Regulations, 2013 CFR
2013-07-01
... generated using e-PMN reporting software and be completed through the finalization step of the software, and e-PMN software must be used to print the request for suspension for submission to EPA. Paper... reporting software and be completed through the finalization step of the software, and e-PMN software must...
47 CFR 2.944 - Software defined radios.
Code of Federal Regulations, 2013 CFR
2013-10-01
... 47 Telecommunication 1 2013-10-01 2013-10-01 false Software defined radios. 2.944 Section 2.944... Authorization § 2.944 Software defined radios. (a) Manufacturers must take steps to ensure that only software that has been approved with a software defined radio can be loaded into the radio. The software must...
47 CFR 2.944 - Software defined radios.
Code of Federal Regulations, 2010 CFR
2010-10-01
... 47 Telecommunication 1 2010-10-01 2010-10-01 false Software defined radios. 2.944 Section 2.944... Authorization § 2.944 Software defined radios. (a) Manufacturers must take steps to ensure that only software that has been approved with a software defined radio can be loaded into the radio. The software must...
40 CFR 725.54 - Suspension of the review period.
Code of Federal Regulations, 2011 CFR
2011-07-01
... generated using e-PMN reporting software and be completed through the finalization step of the software, and e-PMN software must be used to print the request for suspension for submission to EPA. Paper... reporting software and be completed through the finalization step of the software, and e-PMN software must...
40 CFR 725.54 - Suspension of the review period.
Code of Federal Regulations, 2012 CFR
2012-07-01
... generated using e-PMN reporting software and be completed through the finalization step of the software, and e-PMN software must be used to print the request for suspension for submission to EPA. Paper... reporting software and be completed through the finalization step of the software, and e-PMN software must...
Federal Register 2010, 2011, 2012, 2013, 2014
2012-08-22
... NUCLEAR REGULATORY COMMISSION [NRC-2012-0195] Software Unit Testing for Digital Computer Software...) is issuing for public comment draft regulatory guide (DG), DG-1208, ``Software Unit Testing for Digital Computer Software used in Safety Systems of Nuclear Power Plants.'' The DG-1208 is proposed...
47 CFR 2.944 - Software defined radios.
Code of Federal Regulations, 2012 CFR
2012-10-01
... 47 Telecommunication 1 2012-10-01 2012-10-01 false Software defined radios. 2.944 Section 2.944... Authorization § 2.944 Software defined radios. (a) Manufacturers must take steps to ensure that only software that has been approved with a software defined radio can be loaded into the radio. The software must...
Federal Register 2010, 2011, 2012, 2013, 2014
2013-08-02
... NUCLEAR REGULATORY COMMISSION [NRC-2012-0195] Software Unit Testing for Digital Computer Software... revised regulatory guide (RG), revision 1 of RG 1.171, ``Software Unit Testing for Digital Computer Software Used in Safety Systems of Nuclear Power Plants.'' This RG endorses American National Standards...
47 CFR 2.944 - Software defined radios.
Code of Federal Regulations, 2011 CFR
2011-10-01
... 47 Telecommunication 1 2011-10-01 2011-10-01 false Software defined radios. 2.944 Section 2.944... Authorization § 2.944 Software defined radios. (a) Manufacturers must take steps to ensure that only software that has been approved with a software defined radio can be loaded into the radio. The software must...
Software Quality Perceptions of Stakeholders Involved in the Software Development Process
ERIC Educational Resources Information Center
Padmanabhan, Priya
2013-01-01
Software quality is one of the primary determinants of project management success. Stakeholders involved in software development widely agree that quality is important (Barney and Wohlin 2009). However, they may differ on what constitutes software quality, and which of its attributes are more important than others. Although, software quality…
47 CFR 2.944 - Software defined radios.
Code of Federal Regulations, 2014 CFR
2014-10-01
... 47 Telecommunication 1 2014-10-01 2014-10-01 false Software defined radios. 2.944 Section 2.944... Authorization § 2.944 Software defined radios. (a) Manufacturers must take steps to ensure that only software that has been approved with a software defined radio can be loaded into the radio. The software must...
40 CFR 725.54 - Suspension of the review period.
Code of Federal Regulations, 2010 CFR
2010-07-01
... generated using e-PMN reporting software and be completed through the finalization step of the software, and e-PMN software must be used to print the request for suspension for submission to EPA. Paper... reporting software and be completed through the finalization step of the software, and e-PMN software must...
High/Scope Buyer's Guide to Children's Software. 11th Edition.
ERIC Educational Resources Information Center
Hohmann, Charles; And Others
This 11th edition of the High/Scope Buyer's Guide to Children's Software was designed to help teachers, caregivers, and parents make good choices when purchasing software to enhance children's learning. The book consists of an introduction, a chapter on finding the best software, software reviews for 48 different software products. The…
Study of fault tolerant software technology for dynamic systems
NASA Technical Reports Server (NTRS)
Caglayan, A. K.; Zacharias, G. L.
1985-01-01
The major aim of this study is to investigate the feasibility of using systems-based failure detection isolation and compensation (FDIC) techniques in building fault-tolerant software and extending them, whenever possible, to the domain of software fault tolerance. First, it is shown that systems-based FDIC methods can be extended to develop software error detection techniques by using system models for software modules. In particular, it is demonstrated that systems-based FDIC techniques can yield consistency checks that are easier to implement than acceptance tests based on software specifications. Next, it is shown that systems-based failure compensation techniques can be generalized to the domain of software fault tolerance in developing software error recovery procedures. Finally, the feasibility of using fault-tolerant software in flight software is investigated. In particular, possible system and version instabilities, and functional performance degradation that may occur in N-Version programming applications to flight software are illustrated. Finally, a comparative analysis of N-Version and recovery block techniques in the context of generic blocks in flight software is presented.
DOE Office of Scientific and Technical Information (OSTI.GOV)
Turgeon, Jennifer L.; Minana, Molly A.; Hackney, Patricia
2009-01-01
The purpose of the Sandia National Laboratories (SNL) Advanced Simulation and Computing (ASC) Software Quality Plan is to clearly identify the practices that are the basis for continually improving the quality of ASC software products. Quality is defined in the US Department of Energy/National Nuclear Security Agency (DOE/NNSA) Quality Criteria, Revision 10 (QC-1) as 'conformance to customer requirements and expectations'. This quality plan defines the SNL ASC Program software quality engineering (SQE) practices and provides a mapping of these practices to the SNL Corporate Process Requirement (CPR) 001.3.6; 'Corporate Software Engineering Excellence'. This plan also identifies ASC management's and themore » software project teams responsibilities in implementing the software quality practices and in assessing progress towards achieving their software quality goals. This SNL ASC Software Quality Plan establishes the signatories commitments to improving software products by applying cost-effective SQE practices. This plan enumerates the SQE practices that comprise the development of SNL ASC's software products and explains the project teams opportunities for tailoring and implementing the practices.« less
Shuttle mission simulator software conceptual design
NASA Technical Reports Server (NTRS)
Burke, J. F.
1973-01-01
Software conceptual designs (SCD) are presented for meeting the simulator requirements for the shuttle missions. The major areas of the SCD discussed include: malfunction insertion, flight software, applications software, systems software, and computer complex.
SAO mission support software and data standards, version 1.0
NASA Technical Reports Server (NTRS)
Hsieh, P.
1993-01-01
This document defines the software developed by the SAO AXAF Mission Support (MS) Program and defines standards for the software development process and control of data products generated by the software. The SAO MS is tasked to develop and use software to perform a variety of functions in support of the AXAF mission. Software is developed by software engineers and scientists, and commercial off-the-shelf (COTS) software is used either directly or customized through the use of scripts to implement analysis procedures. Software controls real-time laboratory instruments, performs data archiving, displays data, and generates model predictions. Much software is used in the analysis of data to generate data products that are required by the AXAF project, for example, on-orbit mirror performance predictions or detailed characterization of the mirror reflection performance with energy.
Statistical modeling of software reliability
NASA Technical Reports Server (NTRS)
Miller, Douglas R.
1992-01-01
This working paper discusses the statistical simulation part of a controlled software development experiment being conducted under the direction of the System Validation Methods Branch, Information Systems Division, NASA Langley Research Center. The experiment uses guidance and control software (GCS) aboard a fictitious planetary landing spacecraft: real-time control software operating on a transient mission. Software execution is simulated to study the statistical aspects of reliability and other failure characteristics of the software during development, testing, and random usage. Quantification of software reliability is a major goal. Various reliability concepts are discussed. Experiments are described for performing simulations and collecting appropriate simulated software performance and failure data. This data is then used to make statistical inferences about the quality of the software development and verification processes as well as inferences about the reliability of software versions and reliability growth under random testing and debugging.
Promoting Science Software Best Practices: A Scientist's Perspective (Invited)
NASA Astrophysics Data System (ADS)
Blanton, B. O.
2013-12-01
Software is at the core of most modern scientific activities, and as societal awareness of, and impacts from, extreme weather, disasters, and climate and global change continue to increase, the roles that scientific software play in analyses and decision-making are brought more to the forefront. Reproducibility of research results (particularly those that enter into the decision-making arena) and open access to the software is essential for scientific and scientists' credibility. This has been highlighted in a recent article by Joppa et al (Troubling Trends in Scientific Software Use, Science Magazine, May 2013) that describes reasons for particular software being chosen by scientists, including that the "developer is well-respected" and on "recommendation from a close colleague". This reliance on recommendation, Joppa et al conclude, is fraught with risks to both sciences and scientists. Scientists must frequently take software for granted, assuming that it performs as expected and advertised and that the software itself has been validated and results verified. This is largely due to the manner in which much software is written and developed; in an ad hoc manner, with an inconsistent funding stream, and with little application of core software engineering best practices. Insufficient documentation, limited test cases, and code unavailability are significant barriers to informed and intelligent science software usage. This situation is exacerbated when the scientist becomes the software developer out of necessity due to resource constraints. Adoption of, and adherence to, best practices in scientific software development will substantially increase intelligent software usage and promote a sustainable evolution of the science as encoded in the software. We describe a typical scientist's perspective on using and developing scientific software in the context of storm surge research and forecasting applications that have real-time objectives and regulatory constraints. This include perspectives on what scientists/users of software can contribute back to the software development process and examples of successful scientist/developer interactions, and the competition between "getting it done" and "getting it done right".
NASA Technical Reports Server (NTRS)
Hancock, David W., III
1999-01-01
This document provides the Software Management Plan for the GLAS Standard Data Software (SDS) supporting the GLAS instrument of the EOS ICESat Spacecraft. The SDS encompasses the ICESat Science Investigator-led Processing System (I-SIPS) Software and the Instrument Support Terminal (IST) Software. For the I-SIPS Software, the SDS will produce Level 0, Level 1, and Level 2 data products as well as the associated product quality assessments and descriptive information. For the IST Software, the SDS will accommodate the GLAS instrument support areas of engineering status, command, performance assessment, and instrument health status.
NASA Astrophysics Data System (ADS)
Wang, Qiang
2017-09-01
As an important part of software engineering, the software process decides the success or failure of software product. The design and development feature of security software process is discussed, so is the necessity and the present significance of using such process. Coordinating the function software, the process for security software and its testing are deeply discussed. The process includes requirement analysis, design, coding, debug and testing, submission and maintenance. In each process, the paper proposed the subprocesses to support software security. As an example, the paper introduces the above process into the power information platform.
Software Engineering Improvement Activities/Plan
NASA Technical Reports Server (NTRS)
2003-01-01
bd Systems personnel accomplished the technical responsibilities for this reporting period, as planned. A close working relationship was maintained with personnel of the MSFC Avionics Department Software Group (ED14). Work accomplishments included development, evaluation, and enhancement of a software cost model, performing literature search and evaluation of software tools available for code analysis and requirements analysis, and participating in other relevant software engineering activities. Monthly reports were submitted. This support was provided to the Flight Software Group/ED 1 4 in accomplishing the software engineering improvement engineering activities of the Marshall Space Flight Center (MSFC) Software Engineering Improvement Plan.
A Prototype for the Support of Integrated Software Process Development and Improvement
NASA Astrophysics Data System (ADS)
Porrawatpreyakorn, Nalinpat; Quirchmayr, Gerald; Chutimaskul, Wichian
An efficient software development process is one of key success factors for quality software. Not only can the appropriate establishment but also the continuous improvement of integrated project management and of the software development process result in efficiency. This paper hence proposes a software process maintenance framework which consists of two core components: an integrated PMBOK-Scrum model describing how to establish a comprehensive set of project management and software engineering processes and a software development maturity model advocating software process improvement. Besides, a prototype tool to support the framework is introduced.
The relationships between software publications and software systems
NASA Astrophysics Data System (ADS)
Hogg, David W.
2017-01-01
When we build software systems or software tools for astronomy, we sometimes do and sometimes don't also write and publish standard scientific papers about those software systems. I will discuss the pros and cons of writing such publications. There are impacts of writing such papers immediately (they can affect the design and structure of the software project itself), in the short term (they can promote adoption and legitimize the software), in the medium term (they can provide a platform for all the literature's mechanisms for citation, criticism, and reuse), and in the long term (they can preserve ideas that are embodied in the software, possibly on timescales much longer than the lifetime of any software context). I will argue that as important as pure software contributions are to astronomy—and I am both a preacher and a practitioner—software contributions are even more valuable when they are associated with traditional scientific publications. There are exceptions and complexities of course, which I will discuss.
Building quality into medical product software design.
Mallory, S R
1993-01-01
The software engineering and quality assurance disciplines are a requisite to the design of safe and effective software-based medical devices. It is in the areas of software methodology and process that the most beneficial application of these disciplines to software development can be made. Software is a product of complex operations and methodologies and is not amenable to the traditional electromechanical quality assurance processes. Software quality must be built in by the developers, with the software verification and validation engineers acting as the independent instruments for ensuring compliance with performance objectives and with development and maintenance standards. The implementation of a software quality assurance program is a complex process involving management support, organizational changes, and new skill sets, but the benefits are profound. Its rewards provide safe, reliable, cost-effective, maintainable, and manageable software, which may significantly speed the regulatory review process and therefore potentially shorten the overall time to market. The use of a trial project can greatly facilitate the learning process associated with the first-time application of a software quality assurance program.
2016-01-06
of- breed software components and software products lines (SPLs) that are subject to different IP license and cybersecurity requirements. The... commercially priced closed source software components, to be used in the design, implementation, deployment, and evolution of open architecture (OA... breed software components and software products lines (SPLs) that are subject to different IP license and cybersecurity requirements. The Department
NASA Technical Reports Server (NTRS)
Lawrence, Stella
1992-01-01
This paper is concerned with methods of measuring and developing quality software. Reliable flight and ground support software is a highly important factor in the successful operation of the space shuttle program. Reliability is probably the most important of the characteristics inherent in the concept of 'software quality'. It is the probability of failure free operation of a computer program for a specified time and environment.
Artificial intelligence approaches to software engineering
NASA Technical Reports Server (NTRS)
Johannes, James D.; Macdonald, James R.
1988-01-01
Artificial intelligence approaches to software engineering are examined. The software development life cycle is a sequence of not so well-defined phases. Improved techniques for developing systems have been formulated over the past 15 years, but pressure continues to attempt to reduce current costs. Software development technology seems to be standing still. The primary objective of the knowledge-based approach to software development presented in this paper is to avoid problem areas that lead to schedule slippages, cost overruns, or software products that fall short of their desired goals. Identifying and resolving software problems early, often in the phase in which they first occur, has been shown to contribute significantly to reducing risks in software development. Software development is not a mechanical process but a basic human activity. It requires clear thinking, work, and rework to be successful. The artificial intelligence approaches to software engineering presented support the software development life cycle through the use of software development techniques and methodologies in terms of changing current practices and methods. These should be replaced by better techniques that that improve the process of of software development and the quality of the resulting products. The software development process can be structured into well-defined steps, of which the interfaces are standardized, supported and checked by automated procedures that provide error detection, production of the documentation and ultimately support the actual design of complex programs.
Software dependability in the Tandem GUARDIAN system
NASA Technical Reports Server (NTRS)
Lee, Inhwan; Iyer, Ravishankar K.
1995-01-01
Based on extensive field failure data for Tandem's GUARDIAN operating system this paper discusses evaluation of the dependability of operational software. Software faults considered are major defects that result in processor failures and invoke backup processes to take over. The paper categorizes the underlying causes of software failures and evaluates the effectiveness of the process pair technique in tolerating software faults. A model to describe the impact of software faults on the reliability of an overall system is proposed. The model is used to evaluate the significance of key factors that determine software dependability and to identify areas for improvement. An analysis of the data shows that about 77% of processor failures that are initially considered due to software are confirmed as software problems. The analysis shows that the use of process pairs to provide checkpointing and restart (originally intended for tolerating hardware faults) allows the system to tolerate about 75% of reported software faults that result in processor failures. The loose coupling between processors, which results in the backup execution (the processor state and the sequence of events) being different from the original execution, is a major reason for the measured software fault tolerance. Over two-thirds (72%) of measured software failures are recurrences of previously reported faults. Modeling, based on the data, shows that, in addition to reducing the number of software faults, software dependability can be enhanced by reducing the recurrence rate.
Testing Scientific Software: A Systematic Literature Review.
Kanewala, Upulee; Bieman, James M
2014-10-01
Scientific software plays an important role in critical decision making, for example making weather predictions based on climate models, and computation of evidence for research publications. Recently, scientists have had to retract publications due to errors caused by software faults. Systematic testing can identify such faults in code. This study aims to identify specific challenges, proposed solutions, and unsolved problems faced when testing scientific software. We conducted a systematic literature survey to identify and analyze relevant literature. We identified 62 studies that provided relevant information about testing scientific software. We found that challenges faced when testing scientific software fall into two main categories: (1) testing challenges that occur due to characteristics of scientific software such as oracle problems and (2) testing challenges that occur due to cultural differences between scientists and the software engineering community such as viewing the code and the model that it implements as inseparable entities. In addition, we identified methods to potentially overcome these challenges and their limitations. Finally we describe unsolved challenges and how software engineering researchers and practitioners can help to overcome them. Scientific software presents special challenges for testing. Specifically, cultural differences between scientist developers and software engineers, along with the characteristics of the scientific software make testing more difficult. Existing techniques such as code clone detection can help to improve the testing process. Software engineers should consider special challenges posed by scientific software such as oracle problems when developing testing techniques.
Programming Makes Software; Support Makes Users
NASA Astrophysics Data System (ADS)
Batcheller, A. L.
2010-12-01
Skilled software engineers may build fantastic software for climate modeling, yet fail to achieve their project’s objectives. Software support and related activities are just as critical as writing software. This study followed three different software projects in the climate sciences, using interviews, observation, and document analysis to examine the value added by support work. Supporting the project and interacting with users was a key task for software developers, who often spent 50% of their time on it. Such support work most often involved replying to questions on an email list, but also included talking to users on teleconference calls and in person. Software support increased adoption by building the software’s reputation and showing individuals how the software can meet their needs. In the process of providing support, developers often learned new of requirements as users reported features they desire and bugs they found. As software matures and gains widespread use, support work often increases. In fact, such increases can be one signal that the software has achieved broad acceptance. Maturing projects also find demand for instructional classes, online tutorials and detailed examples of how to use the software. The importance of support highlights the fact that building software systems involves both social and technical aspects. Yes, we need to build the software, but we also need to “build” the users and practices that can take advantage of it.
NASA Technical Reports Server (NTRS)
Dunn, William R.; Corliss, Lloyd D.
1991-01-01
Paper examines issue of software safety. Presents four case histories of software-safety analysis. Concludes that, to be safe, software, for all practical purposes, must be free of errors. Backup systems still needed to prevent catastrophic software failures.
Software Selection: A Primer on Source and Evaluation.
ERIC Educational Resources Information Center
Burston, Jack
2003-01-01
Provides guidance on making decisions regarding the selection of foreign language instructional software. Identifies sources of foreign language software, indicates sources of foreign language software reviews, and outlines essential procedures of software evaluation. (Author/VWL)
NASA Technical Reports Server (NTRS)
1995-01-01
The Software Engineering Laboratory (SEL) is an organization sponsored by NASA/GSFC and created to investigate the effectiveness of software engineering technologies when applied to the development of application software. The activities, findings, and recommendations of the SEL are recorded in the Software Engineering Laboratory Series, a continuing series of reports that includes this document.
Software Engineering Laboratory Series: Collected Software Engineering Papers. Volume 15
NASA Technical Reports Server (NTRS)
1997-01-01
The Software Engineering Laboratory (SEL) is an organization sponsored by NASA/GSFC and created to investigate the effectiveness of software engineering technologies when applied to the development of application software. The activities, findings, and recommendations of the SEL are recorded in the Software Engineering Laboratory Series, a continuing series of reports that includes this document.
ERIC Educational Resources Information Center
Clarke, Peter J.; Davis, Debra; King, Tariq M.; Pava, Jairo; Jones, Edward L.
2014-01-01
As software becomes more ubiquitous and complex, the cost of software bugs continues to grow at a staggering rate. To remedy this situation, there needs to be major improvement in the knowledge and application of software validation techniques. Although there are several software validation techniques, software testing continues to be one of the…
Software Engineering Laboratory Series: Collected Software Engineering Papers. Volume 14
NASA Technical Reports Server (NTRS)
1996-01-01
The Software Engineering Laboratory (SEL) is an organization sponsored by NASA/GSFC and created to investigate the effectiveness of software engineering technologies when applied to the development of application software. The activities, findings, and recommendations of the SEL are recorded in the Software Engineering Laboratory Series, a continuing series of reports that includes this document.
Software Engineering Laboratory Series: Collected Software Engineering Papers. Volume 13
NASA Technical Reports Server (NTRS)
1995-01-01
The Software Engineering Laboratory (SEL) is an organization sponsored by NASA/GSFC and created to investigate the effectiveness of software engineering technologies when applied to the development of application software. The activities, findings, and recommendations of the SEL are recorded in the Software Engineering Laboratory Series, a continuing series of reports that includes this document.
ERIC Educational Resources Information Center
Hurt, Andrew C.
2007-01-01
With technology advances, computer software becomes increasingly difficult to learn. Adults often rely on software training to keep abreast of these changes. Instructor-led software training is frequently used to teach adults new software skills; however there is limited research regarding the best practices in adult computer software training.…
Software cost/resource modeling: Software quality tradeoff measurement
NASA Technical Reports Server (NTRS)
Lawler, R. W.
1980-01-01
A conceptual framework for treating software quality from a total system perspective is developed. Examples are given to show how system quality objectives may be allocated to hardware and software; to illustrate trades among quality factors, both hardware and software, to achieve system performance objectives; and to illustrate the impact of certain design choices on software functionality.
MFV-class: a multi-faceted visualization tool of object classes.
Zhang, Zhi-meng; Pan, Yun-he; Zhuang, Yue-ting
2004-11-01
Classes are key software components in an object-oriented software system. In many industrial OO software systems, there are some classes that have complicated structure and relationships. So in the processes of software maintenance, testing, software reengineering, software reuse and software restructure, it is a challenge for software engineers to understand these classes thoroughly. This paper proposes a class comprehension model based on constructivist learning theory, and implements a software visualization tool (MFV-Class) to help in the comprehension of a class. The tool provides multiple views of class to uncover manifold facets of class contents. It enables visualizing three object-oriented metrics of classes to help users focus on the understanding process. A case study was conducted to evaluate our approach and the toolkit.
Software Quality Assurance Audits Guidebooks
NASA Technical Reports Server (NTRS)
1990-01-01
The growth in cost and importance of software to NASA has caused NASA to address the improvement of software development across the agency. One of the products of this program is a series of guidebooks that define a NASA concept of the assurance processes that are used in software development. The Software Assurance Guidebook, NASA-GB-A201, issued in September, 1989, provides an overall picture of the NASA concepts and practices in software assurance. Second level guidebooks focus on specific activities that fall within the software assurance discipline, and provide more detailed information for the manager and/or practitioner. This is the second level Software Quality Assurance Audits Guidebook that describes software quality assurance audits in a way that is compatible with practices at NASA Centers.
Four simple recommendations to encourage best practices in research software
Jiménez, Rafael C.; Kuzak, Mateusz; Alhamdoosh, Monther; Barker, Michelle; Batut, Bérénice; Borg, Mikael; Capella-Gutierrez, Salvador; Chue Hong, Neil; Cook, Martin; Corpas, Manuel; Flannery, Madison; Garcia, Leyla; Gelpí, Josep Ll.; Gladman, Simon; Goble, Carole; González Ferreiro, Montserrat; Gonzalez-Beltran, Alejandra; Griffin, Philippa C.; Grüning, Björn; Hagberg, Jonas; Holub, Petr; Hooft, Rob; Ison, Jon; Katz, Daniel S.; Leskošek, Brane; López Gómez, Federico; Oliveira, Luis J.; Mellor, David; Mosbergen, Rowland; Mulder, Nicola; Perez-Riverol, Yasset; Pergl, Robert; Pichler, Horst; Pope, Bernard; Sanz, Ferran; Schneider, Maria V.; Stodden, Victoria; Suchecki, Radosław; Svobodová Vařeková, Radka; Talvik, Harry-Anton; Todorov, Ilian; Treloar, Andrew; Tyagi, Sonika; van Gompel, Maarten; Vaughan, Daniel; Via, Allegra; Wang, Xiaochuan; Watson-Haigh, Nathan S.; Crouch, Steve
2017-01-01
Scientific research relies on computer software, yet software is not always developed following practices that ensure its quality and sustainability. This manuscript does not aim to propose new software development best practices, but rather to provide simple recommendations that encourage the adoption of existing best practices. Software development best practices promote better quality software, and better quality software improves the reproducibility and reusability of research. These recommendations are designed around Open Source values, and provide practical suggestions that contribute to making research software and its source code more discoverable, reusable and transparent. This manuscript is aimed at developers, but also at organisations, projects, journals and funders that can increase the quality and sustainability of research software by encouraging the adoption of these recommendations. PMID:28751965
Four simple recommendations to encourage best practices in research software.
Jiménez, Rafael C; Kuzak, Mateusz; Alhamdoosh, Monther; Barker, Michelle; Batut, Bérénice; Borg, Mikael; Capella-Gutierrez, Salvador; Chue Hong, Neil; Cook, Martin; Corpas, Manuel; Flannery, Madison; Garcia, Leyla; Gelpí, Josep Ll; Gladman, Simon; Goble, Carole; González Ferreiro, Montserrat; Gonzalez-Beltran, Alejandra; Griffin, Philippa C; Grüning, Björn; Hagberg, Jonas; Holub, Petr; Hooft, Rob; Ison, Jon; Katz, Daniel S; Leskošek, Brane; López Gómez, Federico; Oliveira, Luis J; Mellor, David; Mosbergen, Rowland; Mulder, Nicola; Perez-Riverol, Yasset; Pergl, Robert; Pichler, Horst; Pope, Bernard; Sanz, Ferran; Schneider, Maria V; Stodden, Victoria; Suchecki, Radosław; Svobodová Vařeková, Radka; Talvik, Harry-Anton; Todorov, Ilian; Treloar, Andrew; Tyagi, Sonika; van Gompel, Maarten; Vaughan, Daniel; Via, Allegra; Wang, Xiaochuan; Watson-Haigh, Nathan S; Crouch, Steve
2017-01-01
Scientific research relies on computer software, yet software is not always developed following practices that ensure its quality and sustainability. This manuscript does not aim to propose new software development best practices, but rather to provide simple recommendations that encourage the adoption of existing best practices. Software development best practices promote better quality software, and better quality software improves the reproducibility and reusability of research. These recommendations are designed around Open Source values, and provide practical suggestions that contribute to making research software and its source code more discoverable, reusable and transparent. This manuscript is aimed at developers, but also at organisations, projects, journals and funders that can increase the quality and sustainability of research software by encouraging the adoption of these recommendations.
Software Design Improvements. Part 2; Software Quality and the Design and Inspection Process
NASA Technical Reports Server (NTRS)
Lalli, Vincent R.; Packard, Michael H.; Ziemianski, Tom
1997-01-01
The application of assurance engineering techniques improves the duration of failure-free performance of software. The totality of features and characteristics of a software product are what determine its ability to satisfy customer needs. Software in safety-critical systems is very important to NASA. We follow the System Safety Working Groups definition for system safety software as: 'The optimization of system safety in the design, development, use and maintenance of software and its integration with safety-critical systems in an operational environment. 'If it is not safe, say so' has become our motto. This paper goes over methods that have been used by NASA to make software design improvements by focusing on software quality and the design and inspection process.
NASA Astrophysics Data System (ADS)
Zelt, C. A.
2017-12-01
Earth science attempts to understand how the earth works. This research often depends on software for modeling, processing, inverting or imaging. Freely sharing open-source software is essential to prevent reinventing the wheel and allows software to be improved and applied in ways the original author may never have envisioned. For young scientists, releasing software can increase their name ID when applying for jobs and funding, and create opportunities for collaborations when scientists who collect data want the software's creator to be involved in their project. However, we frequently hear scientists say software is a tool, it's not science. Creating software that implements a new or better way of earth modeling or geophysical processing, inverting or imaging should be viewed as earth science. Creating software for things like data visualization, format conversion, storage, or transmission, or programming to enhance computational performance, may be viewed as computer science. The former, ideally with an application to real data, can be published in earth science journals, the latter possibly in computer science journals. Citations in either case should accurately reflect the impact of the software on the community. Funding agencies need to support more software development and open-source releasing, and the community should give more high-profile awards for developing impactful open-source software. Funding support and community recognition for software development can have far reaching benefits when the software is used in foreseen and unforeseen ways, potentially for years after the original investment in the software development. For funding, an open-source release that is well documented should be required, with example input and output files. Appropriate funding will provide the incentive and time to release user-friendly software, and minimize the need for others to duplicate the effort. All funded software should be available through a single web site, ideally maintained by someone in a funded position. Perhaps the biggest challenge is the reality that researches who use software, as opposed to develop software, are more attractive university hires because they are more likely to be "big picture" scientists that publish in the highest profile journals, although sometimes the two go together.
NASA Astrophysics Data System (ADS)
Hwang, L.; Kellogg, L. H.
2017-12-01
Curation of software promotes discoverability and accessibility and works hand in hand with scholarly citation to ascribe value to, and provide recognition for software development. To meet this challenge, the Computational Infrastructure for Geodynamics (CIG) maintains a community repository built on custom and open tools to promote discovery, access, identification, credit, and provenance of research software for the geodynamics community. CIG (geodynamics.org) originated from recognition of the tremendous effort required to develop sound software and the need to reduce duplication of effort and to sustain community codes. CIG curates software across 6 domains and has developed and follows software best practices that include establishing test cases, documentation, and a citable publication for each software package. CIG software landing web pages provide access to current and past releases; many are also accessible through the CIG community repository on github. CIG has now developed abc - attribution builder for citation to enable software users to give credit to software developers. abc uses zenodo as an archive and as the mechanism to obtain a unique identifier (DOI) for scientific software. To assemble the metadata, we searched the software's documentation and research publications and then requested the primary developers to verify. In this process, we have learned that each development community approaches software attribution differently. The metadata gathered is based on guidelines established by groups such as FORCE11 and OntoSoft. The rollout of abc is gradual as developers are forward-looking, rarely willing to go back and archive prior releases in zenodo. Going forward all actively developed packages will utilize the zenodo and github integration to automate the archival process when a new release is issued. How to handle legacy software, multi-authored libraries, and assigning roles to software remain open issues.
Software platform virtualization in chemistry research and university teaching
2009-01-01
Background Modern chemistry laboratories operate with a wide range of software applications under different operating systems, such as Windows, LINUX or Mac OS X. Instead of installing software on different computers it is possible to install those applications on a single computer using Virtual Machine software. Software platform virtualization allows a single guest operating system to execute multiple other operating systems on the same computer. We apply and discuss the use of virtual machines in chemistry research and teaching laboratories. Results Virtual machines are commonly used for cheminformatics software development and testing. Benchmarking multiple chemistry software packages we have confirmed that the computational speed penalty for using virtual machines is low and around 5% to 10%. Software virtualization in a teaching environment allows faster deployment and easy use of commercial and open source software in hands-on computer teaching labs. Conclusion Software virtualization in chemistry, mass spectrometry and cheminformatics is needed for software testing and development of software for different operating systems. In order to obtain maximum performance the virtualization software should be multi-core enabled and allow the use of multiprocessor configurations in the virtual machine environment. Server consolidation, by running multiple tasks and operating systems on a single physical machine, can lead to lower maintenance and hardware costs especially in small research labs. The use of virtual machines can prevent software virus infections and security breaches when used as a sandbox system for internet access and software testing. Complex software setups can be created with virtual machines and are easily deployed later to multiple computers for hands-on teaching classes. We discuss the popularity of bioinformatics compared to cheminformatics as well as the missing cheminformatics education at universities worldwide. PMID:20150997
Software platform virtualization in chemistry research and university teaching.
Kind, Tobias; Leamy, Tim; Leary, Julie A; Fiehn, Oliver
2009-11-16
Modern chemistry laboratories operate with a wide range of software applications under different operating systems, such as Windows, LINUX or Mac OS X. Instead of installing software on different computers it is possible to install those applications on a single computer using Virtual Machine software. Software platform virtualization allows a single guest operating system to execute multiple other operating systems on the same computer. We apply and discuss the use of virtual machines in chemistry research and teaching laboratories. Virtual machines are commonly used for cheminformatics software development and testing. Benchmarking multiple chemistry software packages we have confirmed that the computational speed penalty for using virtual machines is low and around 5% to 10%. Software virtualization in a teaching environment allows faster deployment and easy use of commercial and open source software in hands-on computer teaching labs. Software virtualization in chemistry, mass spectrometry and cheminformatics is needed for software testing and development of software for different operating systems. In order to obtain maximum performance the virtualization software should be multi-core enabled and allow the use of multiprocessor configurations in the virtual machine environment. Server consolidation, by running multiple tasks and operating systems on a single physical machine, can lead to lower maintenance and hardware costs especially in small research labs. The use of virtual machines can prevent software virus infections and security breaches when used as a sandbox system for internet access and software testing. Complex software setups can be created with virtual machines and are easily deployed later to multiple computers for hands-on teaching classes. We discuss the popularity of bioinformatics compared to cheminformatics as well as the missing cheminformatics education at universities worldwide.
Software Fault Tolerance: A Tutorial
NASA Technical Reports Server (NTRS)
Torres-Pomales, Wilfredo
2000-01-01
Because of our present inability to produce error-free software, software fault tolerance is and will continue to be an important consideration in software systems. The root cause of software design errors is the complexity of the systems. Compounding the problems in building correct software is the difficulty in assessing the correctness of software for highly complex systems. After a brief overview of the software development processes, we note how hard-to-detect design faults are likely to be introduced during development and how software faults tend to be state-dependent and activated by particular input sequences. Although component reliability is an important quality measure for system level analysis, software reliability is hard to characterize and the use of post-verification reliability estimates remains a controversial issue. For some applications software safety is more important than reliability, and fault tolerance techniques used in those applications are aimed at preventing catastrophes. Single version software fault tolerance techniques discussed include system structuring and closure, atomic actions, inline fault detection, exception handling, and others. Multiversion techniques are based on the assumption that software built differently should fail differently and thus, if one of the redundant versions fails, it is expected that at least one of the other versions will provide an acceptable output. Recovery blocks, N-version programming, and other multiversion techniques are reviewed.
Software and package applicating for network meta-analysis: A usage-based comparative study.
Xu, Chang; Niu, Yuming; Wu, Junyi; Gu, Huiyun; Zhang, Chao
2017-12-21
To compare and analyze the characteristics and functions of software applications for network meta-analysis (NMA). PubMed, EMbase, The Cochrane Library, the official websites of Bayesian inference Using Gibbs Sampling (BUGS), Stata and R, and Google were searched to collect the software and packages for performing NMA; software and packages published up to March 2016 were included. After collecting the software, packages, and their user guides, we used the software and packages to calculate a typical example. All characteristics, functions, and computed results were compared and analyzed. Ten types of software were included, including programming and non-programming software. They were developed mainly based on Bayesian or frequentist theory. Most types of software have the characteristics of easy operation, easy mastery, exact calculation, or excellent graphing. However, there was no single software that performed accurate calculations with superior graphing; this could only be achieved through the combination of two or more types of software. This study suggests that the user should choose the appropriate software according to personal programming basis, operational habits, and financial ability. Then, the choice of the combination of BUGS and R (or Stata) software to perform the NMA is considered. © 2017 Chinese Cochrane Center, West China Hospital of Sichuan University and John Wiley & Sons Australia, Ltd.
Modular Rocket Engine Control Software (MRECS)
NASA Technical Reports Server (NTRS)
Tarrant, C.; Crook, J.
1998-01-01
The Modular Rocket Engine Control Software (MRECS) Program is a technology demonstration effort designed to advance the state-of-the-art in launch vehicle propulsion systems. Its emphasis is on developing and demonstrating a modular software architecture for advanced engine control systems that will result in lower software maintenance (operations) costs. It effectively accommodates software requirement changes that occur due to hardware technology upgrades and engine development testing. Ground rules directed by MSFC were to optimize modularity and implement the software in the Ada programming language. MRECS system software and the software development environment utilize Commercial-Off-the-Shelf (COTS) products. This paper presents the objectives, benefits, and status of the program. The software architecture, design, and development environment are described. MRECS tasks are defined and timing relationships given. Major accomplishments are listed. MRECS offers benefits to a wide variety of advanced technology programs in the areas of modular software architecture, reuse software, and reduced software reverification time related to software changes. MRECS was recently modified to support a Space Shuttle Main Engine (SSME) hot-fire test. Cold Flow and Flight Readiness Testing were completed before the test was cancelled. Currently, the program is focused on supporting NASA MSFC in accomplishing development testing of the Fastrac Engine, part of NASA's Low Cost Technologies (LCT) Program. MRECS will be used for all engine development testing.
An Interoperability Framework and Capability Profiling for Manufacturing Software
NASA Astrophysics Data System (ADS)
Matsuda, M.; Arai, E.; Nakano, N.; Wakai, H.; Takeda, H.; Takata, M.; Sasaki, H.
ISO/TC184/SC5/WG4 is working on ISO16100: Manufacturing software capability profiling for interoperability. This paper reports on a manufacturing software interoperability framework and a capability profiling methodology which were proposed and developed through this international standardization activity. Within the context of manufacturing application, a manufacturing software unit is considered to be capable of performing a specific set of function defined by a manufacturing software system architecture. A manufacturing software interoperability framework consists of a set of elements and rules for describing the capability of software units to support the requirements of a manufacturing application. The capability profiling methodology makes use of the domain-specific attributes and methods associated with each specific software unit to describe capability profiles in terms of unit name, manufacturing functions, and other needed class properties. In this methodology, manufacturing software requirements are expressed in terns of software unit capability profiles.
Wildlife software: procedures for publication of computer software
Samuel, M.D.
1990-01-01
Computers and computer software have become an integral part of the practice of wildlife science. Computers now play an important role in teaching, research, and management applications. Because of the specialized nature of wildlife problems, specific computer software is usually required to address a given problem (e.g., home range analysis). This type of software is not usually available from commercial vendors and therefore must be developed by those wildlife professionals with particular skill in computer programming. Current journal publication practices generally prevent a detailed description of computer software associated with new techniques. In addition, peer review of journal articles does not usually include a review of associated computer software. Thus, many wildlife professionals are usually unaware of computer software that would meet their needs or of major improvements in software they commonly use. Indeed most users of wildlife software learn of new programs or important changes only by word of mouth.
A Case Study of Measuring Process Risk for Early Insights into Software Safety
NASA Technical Reports Server (NTRS)
Layman, Lucas; Basili, Victor; Zelkowitz, Marvin V.; Fisher, Karen L.
2011-01-01
In this case study, we examine software safety risk in three flight hardware systems in NASA's Constellation spaceflight program. We applied our Technical and Process Risk Measurement (TPRM) methodology to the Constellation hazard analysis process to quantify the technical and process risks involving software safety in the early design phase of these projects. We analyzed 154 hazard reports and collected metrics to measure the prevalence of software in hazards and the specificity of descriptions of software causes of hazardous conditions. We found that 49-70% of 154 hazardous conditions could be caused by software or software was involved in the prevention of the hazardous condition. We also found that 12-17% of the 2013 hazard causes involved software, and that 23-29% of all causes had a software control. The application of the TPRM methodology identified process risks in the application of the hazard analysis process itself that may lead to software safety risk.
AVE-SESAME program for the REEDA System
NASA Technical Reports Server (NTRS)
Hickey, J. S.
1981-01-01
The REEDA system software was modified and improved to process the AVE-SESAME severe storm data. A random access file system for the AVE storm data was designed, tested, and implemented. The AVE/SESAME software was modified to incorporate the random access file input and to interface with new graphics hardware/software now available on the REEDA system. Software was developed to graphically display the AVE/SESAME data in the convention normally used by severe storm researchers. Software was converted to AVE/SESAME software systems and interfaced with existing graphics hardware/software available on the REEDA System. Software documentation was provided for existing AVE/SESAME programs underlining functional flow charts and interacting questions. All AVE/SESAME data sets in random access format was processed to allow developed software to access the entire AVE/SESAME data base. The existing software was modified to allow for processing of different AVE/SESAME data set types including satellite surface and radar data.
Space Station Software Recommendations
NASA Technical Reports Server (NTRS)
Voigt, S. (Editor)
1985-01-01
Four panels of invited experts and NASA representatives focused on the following topics: software management, software development environment, languages, and software standards. Each panel deliberated in private, held two open sessions with audience participation, and developed recommendations for the NASA Space Station Program. The major thrusts of the recommendations were as follows: (1) The software management plan should establish policies, responsibilities, and decision points for software acquisition; (2) NASA should furnish a uniform modular software support environment and require its use for all space station software acquired (or developed); (3) The language Ada should be selected for space station software, and NASA should begin to address issues related to the effective use of Ada; and (4) The space station software standards should be selected (based upon existing standards where possible), and an organization should be identified to promulgate and enforce them. These and related recommendations are described in detail in the conference proceedings.
A Novel Method for Mining SaaS Software Tag via Community Detection in Software Services Network
NASA Astrophysics Data System (ADS)
Qin, Li; Li, Bing; Pan, Wei-Feng; Peng, Tao
The number of online software services based on SaaS paradigm is increasing. However, users usually find it hard to get the exact software services they need. At present, tags are widely used to annotate specific software services and also to facilitate the searching of them. Currently these tags are arbitrary and ambiguous since mostly of them are generated manually by service developers. This paper proposes a method for mining tags from the help documents of software services. By extracting terms from the help documents and calculating the similarity between the terms, we construct a software similarity network where nodes represent software services, edges denote the similarity relationship between software services, and the weights of the edges are the similarity degrees. The hierarchical clustering algorithm is used for community detection in this software similarity network. At the final stage, tags are mined for each of the communities and stored as ontology.
NASA Technical Reports Server (NTRS)
Becker, D. D.
1980-01-01
The orbiter subsystems and interfacing program elements which interact with the orbiter computer flight software are analyzed. The failure modes identified in the subsystem/element failure mode and effects analysis are examined. Potential interaction with the software is examined through an evaluation of the software requirements. The analysis is restricted to flight software requirements and excludes utility/checkout software. The results of the hardware/software interaction analysis for the forward reaction control system are presented.
Semantic Metrics for Analysis of Software
NASA Technical Reports Server (NTRS)
Etzkorn, Letha H.; Cox, Glenn W.; Farrington, Phil; Utley, Dawn R.; Ghalston, Sampson; Stein, Cara
2005-01-01
A recently conceived suite of object-oriented software metrics focus is on semantic aspects of software, in contradistinction to traditional software metrics, which focus on syntactic aspects of software. Semantic metrics represent a more human-oriented view of software than do syntactic metrics. The semantic metrics of a given computer program are calculated by use of the output of a knowledge-based analysis of the program, and are substantially more representative of software quality and more readily comprehensible from a human perspective than are the syntactic metrics.
Current Practice in Software Development for Computational Neuroscience and How to Improve It
Gewaltig, Marc-Oliver; Cannon, Robert
2014-01-01
Almost all research work in computational neuroscience involves software. As researchers try to understand ever more complex systems, there is a continual need for software with new capabilities. Because of the wide range of questions being investigated, new software is often developed rapidly by individuals or small groups. In these cases, it can be hard to demonstrate that the software gives the right results. Software developers are often open about the code they produce and willing to share it, but there is little appreciation among potential users of the great diversity of software development practices and end results, and how this affects the suitability of software tools for use in research projects. To help clarify these issues, we have reviewed a range of software tools and asked how the culture and practice of software development affects their validity and trustworthiness. We identified four key questions that can be used to categorize software projects and correlate them with the type of product that results. The first question addresses what is being produced. The other three concern why, how, and by whom the work is done. The answers to these questions show strong correlations with the nature of the software being produced, and its suitability for particular purposes. Based on our findings, we suggest ways in which current software development practice in computational neuroscience can be improved and propose checklists to help developers, reviewers, and scientists to assess the quality of software and whether particular pieces of software are ready for use in research. PMID:24465191
Current practice in software development for computational neuroscience and how to improve it.
Gewaltig, Marc-Oliver; Cannon, Robert
2014-01-01
Almost all research work in computational neuroscience involves software. As researchers try to understand ever more complex systems, there is a continual need for software with new capabilities. Because of the wide range of questions being investigated, new software is often developed rapidly by individuals or small groups. In these cases, it can be hard to demonstrate that the software gives the right results. Software developers are often open about the code they produce and willing to share it, but there is little appreciation among potential users of the great diversity of software development practices and end results, and how this affects the suitability of software tools for use in research projects. To help clarify these issues, we have reviewed a range of software tools and asked how the culture and practice of software development affects their validity and trustworthiness. We identified four key questions that can be used to categorize software projects and correlate them with the type of product that results. The first question addresses what is being produced. The other three concern why, how, and by whom the work is done. The answers to these questions show strong correlations with the nature of the software being produced, and its suitability for particular purposes. Based on our findings, we suggest ways in which current software development practice in computational neuroscience can be improved and propose checklists to help developers, reviewers, and scientists to assess the quality of software and whether particular pieces of software are ready for use in research.
ERIC Educational Resources Information Center
Radulescu, Iulian Ionut
2006-01-01
Software complexity is the most important software quality attribute and a very useful instrument in the study of software quality. Is one of the factors that affect most of the software quality characteristics, including maintainability. It is very important to quantity this influence and identify the means to keep it under control; by using…
Proceedings of the Ninth Annual Software Engineering Workshop
NASA Technical Reports Server (NTRS)
1984-01-01
Experiences in measurement, utilization, and evaluation of software methodologies, models, and tools are discussed. NASA's involvement in ever larger and more complex systems, like the space station project, provides a motive for the support of software engineering research and the exchange of ideas in such forums. The topics of current SEL research are software error studies, experiments with software development, and software tools.
NASA Technical Reports Server (NTRS)
1996-01-01
The Software Engineering Laboratory (SEL) is an organization sponsored by NASA/GSFC and created to investigate the effectiveness of software engineering technologies when applied to the development of application software. The activities, findings, and recommendations of the SEL are recorded in the Software Engineering Laboratory Series, a continuing series of reports that includes this document.
FMT (Flight Software Memory Tracker) For Cassini Spacecraft-Software Engineering Using JAVA
NASA Technical Reports Server (NTRS)
Kan, Edwin P.; Uffelman, Hal; Wax, Allan H.
1997-01-01
The software engineering design of the Flight Software Memory Tracker (FMT) Tool is discussed in this paper. FMT is a ground analysis software set, consisting of utilities and procedures, designed to track the flight software, i.e., images of memory load and updatable parameters of the computers on-board Cassini spacecraft. FMT is implemented in Java.
NASA Technical Reports Server (NTRS)
1997-01-01
The Software Engineering Laboratory (SEL) is an organization sponsored by NASA/GSFC and created to investigate the effectiveness of software engineering technologies when applied to the development of application software. The activities, findings, and recommendations of the SEL are recorded in the Software Engineering Laboratory Series, a continuing series of reports that includes this document.
In the right order of brush strokes: a sketch of a software philosophy retrospective.
Pyshkin, Evgeny
2014-01-01
This paper follows a discourse on software recognized as a product of art and human creativity progressing probably for as long as software exists. A retrospective view on computer science and software philosophy development is introduced. In so doing we discover parallels between software and various branches of human creative manifestations. Aesthetic properties and mutual dependency of the form and matter of art works are examined in their application to software programs. While exploring some philosophical and even artistic reflection on software we consider extended comprehension of technical sciences of programming and software engineering within the realm of liberal arts.
OntoSoft: A Software Registry for Geosciences
NASA Astrophysics Data System (ADS)
Garijo, D.; Gil, Y.
2017-12-01
The goal of the EarthCube OntoSoft project is to enable the creation of an ecosystem for software stewardship in geosciences that will empower scientists to manage their software as valuable scientific assets. By sharing software metadata in OntoSoft, scientists enable broader access to that software by other scientists, software professionals, students, and decision makers. Our work to date includes: 1) an ontology for describing scientific software metadata, 2) a distributed scientific software repository that contains more than 750 entries that can be searched and compared across metadata fields, 3) an intelligent user interface that guides scientists to publish software and allows them to crowdsource its corresponding metadata. We have also developed a training program where scientists learn to describe and cite software in their papers in addition to data and provenance, and we are using OntoSoft to show them the benefits of publishing their software metadata. This training program is part of a Geoscience Papers of the Future Initiative, where scientists are reflecting on their current practices, benefits and effort for sharing software and data. This journal paper can be submitted to a Special Section of the AGU Earth and Space Science Journal.
Requirements: Towards an understanding on why software projects fail
NASA Astrophysics Data System (ADS)
Hussain, Azham; Mkpojiogu, Emmanuel O. C.
2016-08-01
Requirement engineering is at the foundation of every successful software project. There are many reasons for software project failures; however, poorly engineered requirements process contributes immensely to the reason why software projects fail. Software project failure is usually costly and risky and could also be life threatening. Projects that undermine requirements engineering suffer or are likely to suffer from failures, challenges and other attending risks. The cost of project failures and overruns when estimated is very huge. Furthermore, software project failures or overruns pose a challenge in today's competitive market environment. It affects the company's image, goodwill, and revenue drive and decreases the perceived satisfaction of customers and clients. In this paper, requirements engineering was discussed. Its role in software projects success was elaborated. The place of software requirements process in relation to software project failure was explored and examined. Also, project success and failure factors were also discussed with emphasis placed on requirements factors as they play a major role in software projects' challenges, successes and failures. The paper relied on secondary data and empirical statistics to explore and examine factors responsible for the successes, challenges and failures of software projects in large, medium and small scaled software companies.
Workflow-Based Software Development Environment
NASA Technical Reports Server (NTRS)
Izygon, Michel E.
2013-01-01
The Software Developer's Assistant (SDA) helps software teams more efficiently and accurately conduct or execute software processes associated with NASA mission-critical software. SDA is a process enactment platform that guides software teams through project-specific standards, processes, and procedures. Software projects are decomposed into all of their required process steps or tasks, and each task is assigned to project personnel. SDA orchestrates the performance of work required to complete all process tasks in the correct sequence. The software then notifies team members when they may begin work on their assigned tasks and provides the tools, instructions, reference materials, and supportive artifacts that allow users to compliantly perform the work. A combination of technology components captures and enacts any software process use to support the software lifecycle. It creates an adaptive workflow environment that can be modified as needed. SDA achieves software process automation through a Business Process Management (BPM) approach to managing the software lifecycle for mission-critical projects. It contains five main parts: TieFlow (workflow engine), Business Rules (rules to alter process flow), Common Repository (storage for project artifacts, versions, history, schedules, etc.), SOA (interface to allow internal, GFE, or COTS tools integration), and the Web Portal Interface (collaborative web environment
DOE Office of Scientific and Technical Information (OSTI.GOV)
Minana, Molly A.; Sturtevant, Judith E.; Heaphy, Robert
2005-01-01
The purpose of the Sandia National Laboratories (SNL) Advanced Simulation and Computing (ASC) Software Quality Plan is to clearly identify the practices that are the basis for continually improving the quality of ASC software products. Quality is defined in DOE/AL Quality Criteria (QC-1) as conformance to customer requirements and expectations. This quality plan defines the ASC program software quality practices and provides mappings of these practices to the SNL Corporate Process Requirements (CPR 1.3.2 and CPR 1.3.6) and the Department of Energy (DOE) document, ASCI Software Quality Engineering: Goals, Principles, and Guidelines (GP&G). This quality plan identifies ASC management andmore » software project teams' responsibilities for cost-effective software engineering quality practices. The SNL ASC Software Quality Plan establishes the signatories commitment to improving software products by applying cost-effective software engineering quality practices. This document explains the project teams opportunities for tailoring and implementing the practices; enumerates the practices that compose the development of SNL ASC's software products; and includes a sample assessment checklist that was developed based upon the practices in this document.« less
NASA Technical Reports Server (NTRS)
Pitman, C. L.; Erb, D. M.; Izygon, M. E.; Fridge, E. M., III; Roush, G. B.; Braley, D. M.; Savely, R. T.
1992-01-01
The United State's big space projects of the next decades, such as Space Station and the Human Exploration Initiative, will need the development of many millions of lines of mission critical software. NASA-Johnson (JSC) is identifying and developing some of the Computer Aided Software Engineering (CASE) technology that NASA will need to build these future software systems. The goal is to improve the quality and the productivity of large software development projects. New trends are outlined in CASE technology and how the Software Technology Branch (STB) at JSC is endeavoring to provide some of these CASE solutions for NASA is described. Key software technology components include knowledge-based systems, software reusability, user interface technology, reengineering environments, management systems for the software development process, software cost models, repository technology, and open, integrated CASE environment frameworks. The paper presents the status and long-term expectations for CASE products. The STB's Reengineering Application Project (REAP), Advanced Software Development Workstation (ASDW) project, and software development cost model (COSTMODL) project are then discussed. Some of the general difficulties of technology transfer are introduced, and a process developed by STB for CASE technology insertion is described.
Software Engineering for Human Spaceflight
NASA Technical Reports Server (NTRS)
Fredrickson, Steven E.
2014-01-01
The Spacecraft Software Engineering Branch of NASA Johnson Space Center (JSC) provides world-class products, leadership, and technical expertise in software engineering, processes, technology, and systems management for human spaceflight. The branch contributes to major NASA programs (e.g. ISS, MPCV/Orion) with in-house software development and prime contractor oversight, and maintains the JSC Engineering Directorate CMMI rating for flight software development. Software engineering teams work with hardware developers, mission planners, and system operators to integrate flight vehicles, habitats, robotics, and other spacecraft elements. They seek to infuse automation and autonomy into missions, and apply new technologies to flight processor and computational architectures. This presentation will provide an overview of key software-related projects, software methodologies and tools, and technology pursuits of interest to the JSC Spacecraft Software Engineering Branch.
Software Design Improvements. Part 1; Software Benefits and Limitations
NASA Technical Reports Server (NTRS)
Lalli, Vincent R.; Packard, Michael H.; Ziemianski, Tom
1997-01-01
Computer hardware and associated software have been used for many years to process accounting information, to analyze test data and to perform engineering analysis. Now computers and software also control everything from automobiles to washing machines and the number and type of applications are growing at an exponential rate. The size of individual program has shown similar growth. Furthermore, software and hardware are used to monitor and/or control potentially dangerous products and safety-critical systems. These uses include everything from airplanes and braking systems to medical devices and nuclear plants. The question is: how can this hardware and software be made more reliable? Also, how can software quality be improved? What methodology needs to be provided on large and small software products to improve the design and how can software be verified?
Software Engineering Improvement Plan
NASA Technical Reports Server (NTRS)
2006-01-01
In performance of this task order, bd Systems personnel provided support to the Flight Software Branch and the Software Working Group through multiple tasks related to software engineering improvement and to activities of the independent Technical Authority (iTA) Discipline Technical Warrant Holder (DTWH) for software engineering. To ensure that the products, comments, and recommendations complied with customer requirements and the statement of work, bd Systems personnel maintained close coordination with the customer. These personnel performed work in areas such as update of agency requirements and directives database, software effort estimation, software problem reports, a web-based process asset library, miscellaneous documentation review, software system requirements, issue tracking software survey, systems engineering NPR, and project-related reviews. This report contains a summary of the work performed and the accomplishments in each of these areas.
Khammarnia, Mohammad; Sharifian, Roxana; Zand, Farid; Keshtkaran, Ali; Barati, Omid
2016-09-01
This study aimed to identify the functional requirements of computerized provider order entry software and design this software in Iran. This study was conducted using review documentation, interview, and focus group discussions in Shiraz University of Medical Sciences, as the medical pole in Iran, in 2013-2015. The study sample consisted of physicians (n = 12) and nurses (n = 2) in the largest hospital in the southern part of Iran and information technology experts (n = 5) in Shiraz University of Medical Sciences. Functional requirements of the computerized provider order entry system were examined in three phases. Finally, the functional requirements were distributed in four levels, and accordingly, the computerized provider order entry software was designed. The software had seven main dimensions: (1) data entry, (2) drug interaction management system, (3) warning system, (4) treatment services, (5) ability to write in software, (6) reporting from all sections of the software, and (7) technical capabilities of the software. The nurses and physicians emphasized quick access to the computerized provider order entry software, order prescription section, and applicability of the software. The software had some items that had not been mentioned in other studies. Ultimately, the software was designed by a company specializing in hospital information systems in Iran. This study was the first specific investigation of computerized provider order entry software design in Iran. Based on the results, it is suggested that this software be implemented in hospitals.
Testing Scientific Software: A Systematic Literature Review
Kanewala, Upulee; Bieman, James M.
2014-01-01
Context Scientific software plays an important role in critical decision making, for example making weather predictions based on climate models, and computation of evidence for research publications. Recently, scientists have had to retract publications due to errors caused by software faults. Systematic testing can identify such faults in code. Objective This study aims to identify specific challenges, proposed solutions, and unsolved problems faced when testing scientific software. Method We conducted a systematic literature survey to identify and analyze relevant literature. We identified 62 studies that provided relevant information about testing scientific software. Results We found that challenges faced when testing scientific software fall into two main categories: (1) testing challenges that occur due to characteristics of scientific software such as oracle problems and (2) testing challenges that occur due to cultural differences between scientists and the software engineering community such as viewing the code and the model that it implements as inseparable entities. In addition, we identified methods to potentially overcome these challenges and their limitations. Finally we describe unsolved challenges and how software engineering researchers and practitioners can help to overcome them. Conclusions Scientific software presents special challenges for testing. Specifically, cultural differences between scientist developers and software engineers, along with the characteristics of the scientific software make testing more difficult. Existing techniques such as code clone detection can help to improve the testing process. Software engineers should consider special challenges posed by scientific software such as oracle problems when developing testing techniques. PMID:25125798
Software engineering methodologies and tools
NASA Technical Reports Server (NTRS)
Wilcox, Lawrence M.
1993-01-01
Over the years many engineering disciplines have developed, including chemical, electronic, etc. Common to all engineering disciplines is the use of rigor, models, metrics, and predefined methodologies. Recently, a new engineering discipline has appeared on the scene, called software engineering. For over thirty years computer software has been developed and the track record has not been good. Software development projects often miss schedules, are over budget, do not give the user what is wanted, and produce defects. One estimate is there are one to three defects per 1000 lines of deployed code. More and more systems are requiring larger and more complex software for support. As this requirement grows, the software development problems grow exponentially. It is believed that software quality can be improved by applying engineering principles. Another compelling reason to bring the engineering disciplines to software development is productivity. It has been estimated that productivity of producing software has only increased one to two percent a year in the last thirty years. Ironically, the computer and its software have contributed significantly to the industry-wide productivity, but computer professionals have done a poor job of using the computer to do their job. Engineering disciplines and methodologies are now emerging supported by software tools that address the problems of software development. This paper addresses some of the current software engineering methodologies as a backdrop for the general evaluation of computer assisted software engineering (CASE) tools from actual installation of and experimentation with some specific tools.
Software Engineering Education Directory
1990-04-01
and Engineering (CMSC 735) Codes: GPEV2 * Textiooks: IEEE Tutoria on Models and Metrics for Software Management and Engameeing by Basi, Victor R...Software Engineering (Comp 227) Codes: GPRY5 Textbooks: IEEE Tutoria on Software Design Techniques by Freeman, Peter and Wasserman, Anthony 1. Software
Finding Helpful Software Reviews.
ERIC Educational Resources Information Center
Kruse, Ted, Comp.
1987-01-01
Provides a list of evaluation services currently producing critical reviews of educational software. Includes information about The Apple K-12 Curriculum Software Reference, The Educational Software Preview, The Educational Software Selector, MicroSIFT, and Only The Best: The Discriminating Guide for Preschool-Grade 12. (TW)
Proceedings of the Thirteenth Annual Software Engineering Workshop
NASA Technical Reports Server (NTRS)
1988-01-01
Topics covered in the workshop included studies and experiments conducted in the Software Engineering Laboratory (SEL), a cooperative effort of NASA Goddard Space Flight Center, the University of Maryland, and Computer Sciences Corporation; software models; software products; and software tools.
TMT approach to observatory software development process
NASA Astrophysics Data System (ADS)
Buur, Hanne; Subramaniam, Annapurni; Gillies, Kim; Dumas, Christophe; Bhatia, Ravinder
2016-07-01
The purpose of the Observatory Software System (OSW) is to integrate all software and hardware components of the Thirty Meter Telescope (TMT) to enable observations and data capture; thus it is a complex software system that is defined by four principal software subsystems: Common Software (CSW), Executive Software (ESW), Data Management System (DMS) and Science Operations Support System (SOSS), all of which have interdependencies with the observatory control systems and data acquisition systems. Therefore, the software development process and plan must consider dependencies to other subsystems, manage architecture, interfaces and design, manage software scope and complexity, and standardize and optimize use of resources and tools. Additionally, the TMT Observatory Software will largely be developed in India through TMT's workshare relationship with the India TMT Coordination Centre (ITCC) and use of Indian software industry vendors, which adds complexity and challenges to the software development process, communication and coordination of activities and priorities as well as measuring performance and managing quality and risk. The software project management challenge for the TMT OSW is thus a multi-faceted technical, managerial, communications and interpersonal relations challenge. The approach TMT is using to manage this multifaceted challenge is a combination of establishing an effective geographically distributed software team (Integrated Product Team) with strong project management and technical leadership provided by the TMT Project Office (PO) and the ITCC partner to manage plans, process, performance, risk and quality, and to facilitate effective communications; establishing an effective cross-functional software management team composed of stakeholders, OSW leadership and ITCC leadership to manage dependencies and software release plans, technical complexities and change to approved interfaces, architecture, design and tool set, and to facilitate effective communications; adopting an agile-based software development process across the observatory to enable frequent software releases to help mitigate subsystem interdependencies; defining concise scope and work packages for each of the OSW subsystems to facilitate effective outsourcing of software deliverables to the ITCC partner, and to enable performance monitoring and risk management. At this stage, the architecture and high-level design of the software system has been established and reviewed. During construction each subsystem will have a final design phase with reviews, followed by implementation and testing. The results of the TMT approach to the Observatory Software development process will only be preliminary at the time of the submittal of this paper, but it is anticipated that the early results will be a favorable indication of progress.
Improving Software Sustainability: Lessons Learned from Profiles in Science.
Gallagher, Marie E
2013-01-01
The Profiles in Science® digital library features digitized surrogates of historical items selected from the archival collections of the U.S. National Library of Medicine as well as collaborating institutions. In addition, it contains a database of descriptive, technical and administrative metadata. It also contains various software components that allow creation of the metadata, management of the digital items, and access to the items and metadata through the Profiles in Science Web site [1]. The choices made building the digital library were designed to maximize the sustainability and long-term survival of all of the components of the digital library [2]. For example, selecting standard and open digital file formats rather than proprietary formats increases the sustainability of the digital files [3]. Correspondingly, using non-proprietary software may improve the sustainability of the software--either through in-house expertise or through the open source community. Limiting our digital library software exclusively to open source software or to software developed in-house has not been feasible. For example, we have used proprietary operating systems, scanning software, a search engine, and office productivity software. We did this when either lack of essential capabilities or the cost-benefit trade-off favored using proprietary software. We also did so knowing that in the future we would need to replace or upgrade some of our proprietary software, analogous to migrating from an obsolete digital file format to a new format as the technological landscape changes. Since our digital library's start in 1998, all of its software has been upgraded or replaced, but the digitized items have not yet required migration to other formats. Technological changes that compelled us to replace proprietary software included the cost of product licensing, product support, incompatibility with other software, prohibited use due to evolving security policies, and product abandonment. Sometimes these changes happen on short notice, so we continually monitor our library's software for signs of endangerment. We have attempted to replace proprietary software with suitable in-house or open source software. When the replacement involves a standalone piece of software with a nearly equivalent version, such as replacing a commercial HTTP server with an open source HTTP server, the replacement is straightforward. Recently we replaced software that functioned not only as our search engine but also as the backbone of the architecture of our Web site. In this paper, we describe the lessons learned and the pros and cons of replacing this software with open source software.
Automated support for experience-based software management
NASA Technical Reports Server (NTRS)
Valett, Jon D.
1992-01-01
To effectively manage a software development project, the software manager must have access to key information concerning a project's status. This information includes not only data relating to the project of interest, but also, the experience of past development efforts within the environment. This paper describes the concepts and functionality of a software management tool designed to provide this information. This tool, called the Software Management Environment (SME), enables the software manager to compare an ongoing development effort with previous efforts and with models of the 'typical' project within the environment, to predict future project status, to analyze a project's strengths and weaknesses, and to assess the project's quality. In order to provide these functions the tool utilizes a vast corporate memory that includes a data base of software metrics, a set of models and relationships that describe the software development environment, and a set of rules that capture other knowledge and experience of software managers within the environment. Integrating these major concepts into one software management tool, the SME is a model of the type of management tool needed for all software development organizations.
Software Architecture for Big Data Systems
2014-03-27
Software Architecture: Trends and New Directions #SEIswArch © 2014 Carnegie Mellon University Software Architecture for Big Data Systems...AND SUBTITLE Software Architecture for Big Data Systems 5a. CONTRACT NUMBER 5b. GRANT NUMBER 5c. PROGRAM ELEMENT NUMBER 6. AUTHOR(S) 5d. PROJECT...ih - . Software Architecture: Trends and New Directions #SEIswArch © 2014 Carnegie Mellon University WHAT IS BIG DATA ? FROM A SOFTWARE
Statistical Software Engineering
1998-04-13
multiversion software subject to coincident errors. IEEE Trans. Software Eng. SE-11:1511-1517. Eckhardt, D.E., A.K Caglayan, J.C. Knight, L.D. Lee, D.F...J.C. and N.G. Leveson. 1986. Experimental evaluation of the assumption of independence in multiversion software. IEEE Trans. Software
University Approaches to Software Copyright and Licensure Policies.
ERIC Educational Resources Information Center
Hawkins, Brian L.
Issues of copyright policy and software licensure at Drexel University that were developed during the introduction of a new microcomputing program are discussed. Channels for software distribution include: individual purchase of externally-produced software, distribution of internally-developed software, institutional licensure, and "read…
Software Reviews Since Acquisition Reform - The Artifact Perspective
2004-01-01
Risk Management OLD NEW Slide 13Acquisition of Software Intensive Systems 2004 – Peter Hantos Single, basic software paradigm Single processor Low...software risk mitigation related trade-offs must be done together Integral Software Engineering Activities Process Maturity and Quality Frameworks Quality
Code of Federal Regulations, 2014 CFR
2014-10-01
... OF DEFENSE GENERAL CONTRACTING REQUIREMENTS PATENTS, DATA, AND COPYRIGHTS Rights in Computer Software and Computer Software Documentation 227.7203-1 Policy. (a) DoD policy is to acquire only the computer software and computer software documentation, and the rights in such software or documentation, necessary...
Code of Federal Regulations, 2011 CFR
2011-10-01
... OF DEFENSE GENERAL CONTRACTING REQUIREMENTS PATENTS, DATA, AND COPYRIGHTS Rights in Computer Software and Computer Software Documentation 227.7203-1 Policy. (a) DoD policy is to acquire only the computer software and computer software documentation, and the rights in such software or documentation, necessary...
48 CFR 227.7203-4 - License rights.
Code of Federal Regulations, 2014 CFR
2014-10-01
... Software and Computer Software Documentation 227.7203-4 License rights. (a) Grant of license. The Government obtains rights in computer software or computer software documentation, including a copyright license, under an irrevocable license granted or obtained by the contractor which developed the software...
Code of Federal Regulations, 2010 CFR
2010-10-01
... OF DEFENSE GENERAL CONTRACTING REQUIREMENTS PATENTS, DATA, AND COPYRIGHTS Rights in Computer Software and Computer Software Documentation 227.7203-1 Policy. (a) DoD policy is to acquire only the computer software and computer software documentation, and the rights in such software or documentation, necessary...
48 CFR 227.7203-4 - License rights.
Code of Federal Regulations, 2013 CFR
2013-10-01
... Software and Computer Software Documentation 227.7203-4 License rights. (a) Grant of license. The Government obtains rights in computer software or computer software documentation, including a copyright license, under an irrevocable license granted or obtained by the contractor which developed the software...
Code of Federal Regulations, 2013 CFR
2013-10-01
... OF DEFENSE GENERAL CONTRACTING REQUIREMENTS PATENTS, DATA, AND COPYRIGHTS Rights in Computer Software and Computer Software Documentation 227.7203-1 Policy. (a) DoD policy is to acquire only the computer software and computer software documentation, and the rights in such software or documentation, necessary...
48 CFR 227.7203-4 - License rights.
Code of Federal Regulations, 2012 CFR
2012-10-01
... Software and Computer Software Documentation 227.7203-4 License rights. (a) Grant of license. The Government obtains rights in computer software or computer software documentation, including a copyright license, under an irrevocable license granted or obtained by the contractor which developed the software...
Code of Federal Regulations, 2012 CFR
2012-10-01
... OF DEFENSE GENERAL CONTRACTING REQUIREMENTS PATENTS, DATA, AND COPYRIGHTS Rights in Computer Software and Computer Software Documentation 227.7203-1 Policy. (a) DoD policy is to acquire only the computer software and computer software documentation, and the rights in such software or documentation, necessary...
48 CFR 227.7203-4 - License rights.
Code of Federal Regulations, 2010 CFR
2010-10-01
... Software and Computer Software Documentation 227.7203-4 License rights. (a) Grant of license. The Government obtains rights in computer software or computer software documentation, including a copyright license, under an irrevocable license granted or obtained by the contractor which developed the software...
48 CFR 227.7203-4 - License rights.
Code of Federal Regulations, 2011 CFR
2011-10-01
... Software and Computer Software Documentation 227.7203-4 License rights. (a) Grant of license. The Government obtains rights in computer software or computer software documentation, including a copyright license, under an irrevocable license granted or obtained by the contractor which developed the software...
48 CFR 227.7205 - Contracts for special works.
Code of Federal Regulations, 2014 CFR
2014-10-01
... Computer Software and Computer Software Documentation 227.7205 Contracts for special works. (a) Use the... a specific need to control the distribution of computer software or computer software documentation..., modification, reproduction, release, performance, display, or disclosure of such software or documentation. Use...
Low Cost Ways to Keep Software Current.
ERIC Educational Resources Information Center
Schultheis, Robert A.
1992-01-01
Discusses strategies for providing students with current computer software technology including acquiring previous versions of software, obtaining demonstration software, using student versions, getting examination software, buying from mail order firms, buying few copies, exploring site licenses, acquiring shareware or freeware, and applying for…
48 CFR 227.7205 - Contracts for special works.
Code of Federal Regulations, 2010 CFR
2010-10-01
... Computer Software and Computer Software Documentation 227.7205 Contracts for special works. (a) Use the... a specific need to control the distribution of computer software or computer software documentation..., modification, reproduction, release, performance, display, or disclosure of such software or documentation. Use...
48 CFR 208.7400 - Scope of subpart.
Code of Federal Regulations, 2010 CFR
2010-10-01
... OF DEFENSE ACQUISITION PLANNING REQUIRED SOURCES OF SUPPLIES AND SERVICES Enterprise Software... commercial software and software maintenance, including software and software maintenance that is acquired— (a) As part of a system or system upgrade, where practicable; (b) Under a service contract; (c) Under...
Infusing Reliability Techniques into Software Safety Analysis
NASA Technical Reports Server (NTRS)
Shi, Ying
2015-01-01
Software safety analysis for a large software intensive system is always a challenge. Software safety practitioners need to ensure that software related hazards are completely identified, controlled, and tracked. This paper discusses in detail how to incorporate the traditional reliability techniques into the entire software safety analysis process. In addition, this paper addresses how information can be effectively shared between the various practitioners involved in the software safety analyses. The author has successfully applied the approach to several aerospace applications. Examples are provided to illustrate the key steps of the proposed approach.
Software for aerospace education: A bibliography, 2nd edition
NASA Technical Reports Server (NTRS)
Vogt, Gregory L.; Roth, Susan Kies; Phelps, Malcom V.
1990-01-01
This is the second aerospace education software bibliography to be published by the NASA Educational Technology Branch in Washington, DC. Unlike many software bibliographies, this bibliography does not evaluate and grade software according to its quality and value to the classroom, nor does it make any endorsements or warrant scientific accuracy. Rather, it describes software, its subject, approach, and technical details. This bibliography is intended as a convenience to educators. The specific software included represents replies to more than 300 queries to software producers for aerospace education programs.
QuantWorm: a comprehensive software package for Caenorhabditis elegans phenotypic assays.
Jung, Sang-Kyu; Aleman-Meza, Boanerges; Riepe, Celeste; Zhong, Weiwei
2014-01-01
Phenotypic assays are crucial in genetics; however, traditional methods that rely on human observation are unsuitable for quantitative, large-scale experiments. Furthermore, there is an increasing need for comprehensive analyses of multiple phenotypes to provide multidimensional information. Here we developed an automated, high-throughput computer imaging system for quantifying multiple Caenorhabditis elegans phenotypes. Our imaging system is composed of a microscope equipped with a digital camera and a motorized stage connected to a computer running the QuantWorm software package. Currently, the software package contains one data acquisition module and four image analysis programs: WormLifespan, WormLocomotion, WormLength, and WormEgg. The data acquisition module collects images and videos. The WormLifespan software counts the number of moving worms by using two time-lapse images; the WormLocomotion software computes the velocity of moving worms; the WormLength software measures worm body size; and the WormEgg software counts the number of eggs. To evaluate the performance of our software, we compared the results of our software with manual measurements. We then demonstrated the application of the QuantWorm software in a drug assay and a genetic assay. Overall, the QuantWorm software provided accurate measurements at a high speed. Software source code, executable programs, and sample images are available at www.quantworm.org. Our software package has several advantages over current imaging systems for C. elegans. It is an all-in-one package for quantifying multiple phenotypes. The QuantWorm software is written in Java and its source code is freely available, so it does not require use of commercial software or libraries. It can be run on multiple platforms and easily customized to cope with new methods and requirements.
Ground Software Maintenance Facility (GSMF) system manual
NASA Technical Reports Server (NTRS)
Derrig, D.; Griffith, G.
1986-01-01
The Ground Software Maintenance Facility (GSMF) is designed to support development and maintenance of spacelab ground support software. THE GSMF consists of a Perkin Elmer 3250 (Host computer) and a MITRA 125s (ATE computer), with appropriate interface devices and software to simulate the Electrical Ground Support Equipment (EGSE). This document is presented in three sections: (1) GSMF Overview; (2) Software Structure; and (3) Fault Isolation Capability. The overview contains information on hardware and software organization along with their corresponding block diagrams. The Software Structure section describes the modes of software structure including source files, link information, and database files. The Fault Isolation section describes the capabilities of the Ground Computer Interface Device, Perkin Elmer host, and MITRA ATE.
Software reliability models for critical applications
DOE Office of Scientific and Technical Information (OSTI.GOV)
Pham, H.; Pham, M.
This report presents the results of the first phase of the ongoing EG G Idaho, Inc. Software Reliability Research Program. The program is studying the existing software reliability models and proposes a state-of-the-art software reliability model that is relevant to the nuclear reactor control environment. This report consists of three parts: (1) summaries of the literature review of existing software reliability and fault tolerant software reliability models and their related issues, (2) proposed technique for software reliability enhancement, and (3) general discussion and future research. The development of this proposed state-of-the-art software reliability model will be performed in the secondmore » place. 407 refs., 4 figs., 2 tabs.« less
Software reliability models for critical applications
DOE Office of Scientific and Technical Information (OSTI.GOV)
Pham, H.; Pham, M.
This report presents the results of the first phase of the ongoing EG&G Idaho, Inc. Software Reliability Research Program. The program is studying the existing software reliability models and proposes a state-of-the-art software reliability model that is relevant to the nuclear reactor control environment. This report consists of three parts: (1) summaries of the literature review of existing software reliability and fault tolerant software reliability models and their related issues, (2) proposed technique for software reliability enhancement, and (3) general discussion and future research. The development of this proposed state-of-the-art software reliability model will be performed in the second place.more » 407 refs., 4 figs., 2 tabs.« less
Advanced software development workstation project: Engineering scripting language. Graphical editor
NASA Technical Reports Server (NTRS)
1992-01-01
Software development is widely considered to be a bottleneck in the development of complex systems, both in terms of development and in terms of maintenance of deployed systems. Cost of software development and maintenance can also be very high. One approach to reducing costs and relieving this bottleneck is increasing the reuse of software designs and software components. A method for achieving such reuse is a software parts composition system. Such a system consists of a language for modeling software parts and their interfaces, a catalog of existing parts, an editor for combining parts, and a code generator that takes a specification and generates code for that application in the target language. The Advanced Software Development Workstation is intended to be an expert system shell designed to provide the capabilities of a software part composition system.
Developing sustainable software solutions for bioinformatics by the “ Butterfly” paradigm
Ahmed, Zeeshan; Zeeshan, Saman; Dandekar, Thomas
2014-01-01
Software design and sustainable software engineering are essential for the long-term development of bioinformatics software. Typical challenges in an academic environment are short-term contracts, island solutions, pragmatic approaches and loose documentation. Upcoming new challenges are big data, complex data sets, software compatibility and rapid changes in data representation. Our approach to cope with these challenges consists of iterative intertwined cycles of development (“ Butterfly” paradigm) for key steps in scientific software engineering. User feedback is valued as well as software planning in a sustainable and interoperable way. Tool usage should be easy and intuitive. A middleware supports a user-friendly Graphical User Interface (GUI) as well as a database/tool development independently. We validated the approach of our own software development and compared the different design paradigms in various software solutions. PMID:25383181
Software engineering and Ada in design
NASA Technical Reports Server (NTRS)
Oneill, Don
1986-01-01
Modern software engineering promises significant reductions in software costs and improvements in software quality. The Ada language is the focus for these software methodology and tool improvements. The IBM FSD approach, including the software engineering practices that guide the systematic design and development of software products and the management of the software process are examined. The revised Ada design language adaptation is revealed. This four level design methodology is detailed including the purpose of each level, the management strategy that integrates the software design activity with the program milestones, and the technical strategy that maps the Ada constructs to each level of design. A complete description of each design level is provided along with specific design language recording guidelines for each level. Finally, some testimony is offered on education, tools, architecture, and metrics resulting from project use of the four level Ada design language adaptation.
Simple solution to the medical instrumentation software problem
NASA Astrophysics Data System (ADS)
Leif, Robert C.; Leif, Suzanne B.; Leif, Stephanie H.; Bingue, E.
1995-04-01
Medical devices now include a substantial software component, which is both difficult and expensive to produce and maintain. Medical software must be developed according to `Good Manufacturing Practices', GMP. Good Manufacturing Practices as specified by the FDA and ISO requires the definition and compliance to a software processes which ensures quality products by specifying a detailed method of software construction. The software process should be based on accepted standards. US Department of Defense software standards and technology can both facilitate the development and improve the quality of medical systems. We describe the advantages of employing Mil-Std-498, Software Development and Documentation, and the Ada programming language. Ada provides the very broad range of functionalities, from embedded real-time to management information systems required by many medical devices. It also includes advanced facilities for object oriented programming and software engineering.
Open Architecture Standard for NASA's Software-Defined Space Telecommunications Radio Systems
NASA Technical Reports Server (NTRS)
Reinhart, Richard C.; Johnson, Sandra K.; Kacpura, Thomas J.; Hall, Charles S.; Smith, Carl R.; Liebetreu, John
2008-01-01
NASA is developing an architecture standard for software-defined radios used in space- and ground-based platforms to enable commonality among radio developments to enhance capability and services while reducing mission and programmatic risk. Transceivers (or transponders) with functionality primarily defined in software (e.g., firmware) have the ability to change their functional behavior through software alone. This radio architecture standard offers value by employing common waveform software interfaces, method of instantiation, operation, and testing among different compliant hardware and software products. These common interfaces within the architecture abstract application software from the underlying hardware to enable technology insertion independently at either the software or hardware layer. This paper presents the initial Space Telecommunications Radio System (STRS) Architecture for NASA missions to provide the desired software abstraction and flexibility while minimizing the resources necessary to support the architecture.
NASA Technical Reports Server (NTRS)
1992-01-01
This standard specifies the software assurance program for the provider of software. It also delineates the assurance activities for the provider and the assurance data that are to be furnished by the provider to the acquirer. In any software development effort, the provider is the entity or individual that actually designs, develops, and implements the software product, while the acquirer is the entity or individual who specifies the requirements and accepts the resulting products. This standard specifies at a high level an overall software assurance program for software developed for and by NASA. Assurance includes the disciplines of quality assurance, quality engineering, verification and validation, nonconformance reporting and corrective action, safety assurance, and security assurance. The application of these disciplines during a software development life cycle is called software assurance. Subsequent lower-level standards will specify the specific processes within these disciplines.
Clinical software development for the Web: lessons learned from the BOADICEA project
2012-01-01
Background In the past 20 years, society has witnessed the following landmark scientific advances: (i) the sequencing of the human genome, (ii) the distribution of software by the open source movement, and (iii) the invention of the World Wide Web. Together, these advances have provided a new impetus for clinical software development: developers now translate the products of human genomic research into clinical software tools; they use open-source programs to build them; and they use the Web to deliver them. Whilst this open-source component-based approach has undoubtedly made clinical software development easier, clinical software projects are still hampered by problems that traditionally accompany the software process. This study describes the development of the BOADICEA Web Application, a computer program used by clinical geneticists to assess risks to patients with a family history of breast and ovarian cancer. The key challenge of the BOADICEA Web Application project was to deliver a program that was safe, secure and easy for healthcare professionals to use. We focus on the software process, problems faced, and lessons learned. Our key objectives are: (i) to highlight key clinical software development issues; (ii) to demonstrate how software engineering tools and techniques can facilitate clinical software development for the benefit of individuals who lack software engineering expertise; and (iii) to provide a clinical software development case report that can be used as a basis for discussion at the start of future projects. Results We developed the BOADICEA Web Application using an evolutionary software process. Our approach to Web implementation was conservative and we used conventional software engineering tools and techniques. The principal software development activities were: requirements, design, implementation, testing, documentation and maintenance. The BOADICEA Web Application has now been widely adopted by clinical geneticists and researchers. BOADICEA Web Application version 1 was released for general use in November 2007. By May 2010, we had > 1200 registered users based in the UK, USA, Canada, South America, Europe, Africa, Middle East, SE Asia, Australia and New Zealand. Conclusions We found that an evolutionary software process was effective when we developed the BOADICEA Web Application. The key clinical software development issues identified during the BOADICEA Web Application project were: software reliability, Web security, clinical data protection and user feedback. PMID:22490389
Clinical software development for the Web: lessons learned from the BOADICEA project.
Cunningham, Alex P; Antoniou, Antonis C; Easton, Douglas F
2012-04-10
In the past 20 years, society has witnessed the following landmark scientific advances: (i) the sequencing of the human genome, (ii) the distribution of software by the open source movement, and (iii) the invention of the World Wide Web. Together, these advances have provided a new impetus for clinical software development: developers now translate the products of human genomic research into clinical software tools; they use open-source programs to build them; and they use the Web to deliver them. Whilst this open-source component-based approach has undoubtedly made clinical software development easier, clinical software projects are still hampered by problems that traditionally accompany the software process. This study describes the development of the BOADICEA Web Application, a computer program used by clinical geneticists to assess risks to patients with a family history of breast and ovarian cancer. The key challenge of the BOADICEA Web Application project was to deliver a program that was safe, secure and easy for healthcare professionals to use. We focus on the software process, problems faced, and lessons learned. Our key objectives are: (i) to highlight key clinical software development issues; (ii) to demonstrate how software engineering tools and techniques can facilitate clinical software development for the benefit of individuals who lack software engineering expertise; and (iii) to provide a clinical software development case report that can be used as a basis for discussion at the start of future projects. We developed the BOADICEA Web Application using an evolutionary software process. Our approach to Web implementation was conservative and we used conventional software engineering tools and techniques. The principal software development activities were: requirements, design, implementation, testing, documentation and maintenance. The BOADICEA Web Application has now been widely adopted by clinical geneticists and researchers. BOADICEA Web Application version 1 was released for general use in November 2007. By May 2010, we had > 1200 registered users based in the UK, USA, Canada, South America, Europe, Africa, Middle East, SE Asia, Australia and New Zealand. We found that an evolutionary software process was effective when we developed the BOADICEA Web Application. The key clinical software development issues identified during the BOADICEA Web Application project were: software reliability, Web security, clinical data protection and user feedback.
Telescience Resource Kit (TReK)
NASA Technical Reports Server (NTRS)
Lippincott, Jeff
2015-01-01
Telescience Resource Kit (TReK) is one of the Huntsville Operations Support Center (HOSC) remote operations solutions. It can be used to monitor and control International Space Station (ISS) payloads from anywhere in the world. It is comprised of a suite of software applications and libraries that provide generic data system capabilities and access to HOSC services. The TReK Software has been operational since 2000. A new cross-platform version of TReK is under development. The new software is being released in phases during the 2014-2016 timeframe. The TReK Release 3.x series of software is the original TReK software that has been operational since 2000. This software runs on Windows. It contains capabilities to support traditional telemetry and commanding using CCSDS (Consultative Committee for Space Data Systems) packets. The TReK Release 4.x series of software is the new cross platform software. It runs on Windows and Linux. The new TReK software will support communication using standard IP protocols and traditional telemetry and commanding. All the software listed above is compatible and can be installed and run together on Windows. The new TReK software contains a suite of software that can be used by payload developers on the ground and onboard (TReK Toolkit). TReK Toolkit is a suite of lightweight libraries and utility applications for use onboard and on the ground. TReK Desktop is the full suite of TReK software -most useful on the ground. When TReK Desktop is released, the TReK installation program will provide the option to choose just the TReK Toolkit portion of the software or the full TReK Desktop suite. The ISS program is providing the TReK Toolkit software as a generic flight software capability offered as a standard service to payloads. TReK Software Verification was conducted during the April/May 2015 timeframe. Payload teams using the TReK software onboard can reference the TReK software verification. TReK will be demonstrated on-orbit running on an ISS provided T61p laptop. Target Timeframe: September 2015 -2016. The on-orbit demonstration will collect benchmark metrics, and will be used in the future to provide live demonstrations during ISS Payload Conferences. Benchmark metrics and demonstrations will address the protocols described in SSP 52050-0047 Ku Forward section 3.3.7. (Associated term: CCSDS File Delivery Protocol (CFDP)).
48 CFR 227.7203-6 - Contract clauses.
Code of Federal Regulations, 2010 CFR
2010-10-01
... Software and Computer Software Documentation 227.7203-6 Contract clauses. (a)(1) Use the clause at 252.227-7014, Rights in Noncommercial Computer Software and Noncommercial Computer Software Documentation, in solicitations and contracts when the successful offeror(s) will be required to deliver computer software or...
48 CFR 227.7203-17 - Overseas contracts with foreign sources.
Code of Federal Regulations, 2013 CFR
2013-10-01
... COPYRIGHTS Rights in Computer Software and Computer Software Documentation 227.7203-17 Overseas contracts with foreign sources. (a) The clause at 252.227-7032, Rights in Technical Data and Computer Software... Noncommercial Computer Software and Noncommercial Computer Software Documentation, when the Government requires...
48 CFR 227.7203-17 - Overseas contracts with foreign sources.
Code of Federal Regulations, 2010 CFR
2010-10-01
... COPYRIGHTS Rights in Computer Software and Computer Software Documentation 227.7203-17 Overseas contracts with foreign sources. (a) The clause at 252.227-7032, Rights in Technical Data and Computer Software... Noncommercial Computer Software and Noncommercial Computer Software Documentation, when the Government requires...
48 CFR 227.7203-6 - Contract clauses.
Code of Federal Regulations, 2012 CFR
2012-10-01
... Software and Computer Software Documentation 227.7203-6 Contract clauses. (a)(1) Use the clause at 252.227-7014, Rights in Noncommercial Computer Software and Noncommercial Computer Software Documentation, in solicitations and contracts when the successful offeror(s) will be required to deliver computer software or...
48 CFR 227.7203-17 - Overseas contracts with foreign sources.
Code of Federal Regulations, 2014 CFR
2014-10-01
... COPYRIGHTS Rights in Computer Software and Computer Software Documentation 227.7203-17 Overseas contracts with foreign sources. (a) The clause at 252.227-7032, Rights in Technical Data and Computer Software... Noncommercial Computer Software and Noncommercial Computer Software Documentation, when the Government requires...
48 CFR 227.7203-6 - Contract clauses.
Code of Federal Regulations, 2014 CFR
2014-10-01
... Software and Computer Software Documentation 227.7203-6 Contract clauses. (a)(1) Use the clause at 252.227-7014, Rights in Noncommercial Computer Software and Noncommercial Computer Software Documentation, in solicitations and contracts when the successful offeror(s) will be required to deliver computer software or...
48 CFR 227.7203-6 - Contract clauses.
Code of Federal Regulations, 2011 CFR
2011-10-01
... Software and Computer Software Documentation 227.7203-6 Contract clauses. (a)(1) Use the clause at 252.227-7014, Rights in Noncommercial Computer Software and Noncommercial Computer Software Documentation, in solicitations and contracts when the successful offeror(s) will be required to deliver computer software or...
48 CFR 227.7203-17 - Overseas contracts with foreign sources.
Code of Federal Regulations, 2011 CFR
2011-10-01
... COPYRIGHTS Rights in Computer Software and Computer Software Documentation 227.7203-17 Overseas contracts with foreign sources. (a) The clause at 252.227-7032, Rights in Technical Data and Computer Software... Noncommercial Computer Software and Noncommercial Computer Software Documentation, when the Government requires...
48 CFR 227.7203-17 - Overseas contracts with foreign sources.
Code of Federal Regulations, 2012 CFR
2012-10-01
... COPYRIGHTS Rights in Computer Software and Computer Software Documentation 227.7203-17 Overseas contracts with foreign sources. (a) The clause at 252.227-7032, Rights in Technical Data and Computer Software... Noncommercial Computer Software and Noncommercial Computer Software Documentation, when the Government requires...
48 CFR 227.7203-6 - Contract clauses.
Code of Federal Regulations, 2013 CFR
2013-10-01
... Software and Computer Software Documentation 227.7203-6 Contract clauses. (a)(1) Use the clause at 252.227-7014, Rights in Noncommercial Computer Software and Noncommercial Computer Software Documentation, in solicitations and contracts when the successful offeror(s) will be required to deliver computer software or...
Software security checklist for the software life cycle
NASA Technical Reports Server (NTRS)
Gilliam, D. P.; Wolfe, T. L.; Sherif, J. S.
2002-01-01
A formal approach to security in the software life cycle is essential to protect corporate resources. However, little thought has been given to this aspect of software development. Due to its criticality, security should be integrated as a formal approach in the software life cycle.
NASA's Software Safety Standard
NASA Technical Reports Server (NTRS)
Ramsay, Christopher M.
2005-01-01
NASA (National Aeronautics and Space Administration) relies more and more on software to control, monitor, and verify its safety critical systems, facilities and operations. Since the 1960's there has hardly been a spacecraft (manned or unmanned) launched that did not have a computer on board that provided vital command and control services. Despite this growing dependence on software control and monitoring, there has been no consistent application of software safety practices and methodology to NASA's projects with safety critical software. Led by the NASA Headquarters Office of Safety and Mission Assurance, the NASA Software Safety Standard (STD-18l9.13B) has recently undergone a significant update in an attempt to provide that consistency. This paper will discuss the key features of the new NASA Software Safety Standard. It will start with a brief history of the use and development of software in safety critical applications at NASA. It will then give a brief overview of the NASA Software Working Group and the approach it took to revise the software engineering process across the Agency.
Software Safety Risk in Legacy Safety-Critical Computer Systems
NASA Technical Reports Server (NTRS)
Hill, Janice; Baggs, Rhoda
2007-01-01
Safety-critical computer systems must be engineered to meet system and software safety requirements. For legacy safety-critical computer systems, software safety requirements may not have been formally specified during development. When process-oriented software safety requirements are levied on a legacy system after the fact, where software development artifacts don't exist or are incomplete, the question becomes 'how can this be done?' The risks associated with only meeting certain software safety requirements in a legacy safety-critical computer system must be addressed should such systems be selected as candidates for reuse. This paper proposes a method for ascertaining formally, a software safety risk assessment, that provides measurements for software safety for legacy systems which may or may not have a suite of software engineering documentation that is now normally required. It relies upon the NASA Software Safety Standard, risk assessment methods based upon the Taxonomy-Based Questionnaire, and the application of reverse engineering CASE tools to produce original design documents for legacy systems.
A study of software standards used in the avionics industry
NASA Technical Reports Server (NTRS)
Hayhurst, Kelly J.
1994-01-01
Within the past decade, software has become an increasingly common element in computing systems. In particular, the role of software used in the aerospace industry, especially in life- or safety-critical applications, is rapidly expanding. This intensifies the need to use effective techniques for achieving and verifying the reliability of avionics software. Although certain software development processes and techniques are mandated by government regulating agencies, no one methodology has been shown to consistently produce reliable software. The knowledge base for designing reliable software simply has not reached the maturity of its hardware counterpart. In an effort to increase our understanding of software, the Langley Research Center conducted a series of experiments over 15 years with the goal of understanding why and how software fails. As part of this program, the effectiveness of current industry standards for the development of avionics is being investigated. This study involves the generation of a controlled environment to conduct scientific experiments on software processes.
NASA Technical Reports Server (NTRS)
1976-01-01
Only a few efforts are currently underway to develop an adequate technology base for the various themes. Particular attention must be given to software commonality and evolutionary capability, to increased system integrity and autonomy; and to improved communications among the program users, the program developers, and the programs themselves. There is a need for quantum improvement in software development methods and increasing the awareness of software by all concerned. Major thrusts identified include: (1) data and systems management; (2) software technology for autonomous systems; (3) technology and methods for improving the software development process; (4) advances related to systems of software elements including their architecture, their attributes as systems, and their interfaces with users and other systems; and (5) applications of software including both the basic algorithms used in a number of applications and the software specific to a particular theme or discipline area. The impact of each theme on software is assessed.
Modeling SMAP Spacecraft Attitude Control Estimation Error Using Signal Generation Model
NASA Technical Reports Server (NTRS)
Rizvi, Farheen
2016-01-01
Two ground simulation software are used to model the SMAP spacecraft dynamics. The CAST software uses a higher fidelity model than the ADAMS software. The ADAMS software models the spacecraft plant, controller and actuator models, and assumes a perfect sensor and estimator model. In this simulation study, the spacecraft dynamics results from the ADAMS software are used as CAST software is unavailable. The main source of spacecraft dynamics error in the higher fidelity CAST software is due to the estimation error. A signal generation model is developed to capture the effect of this estimation error in the overall spacecraft dynamics. Then, this signal generation model is included in the ADAMS software spacecraft dynamics estimate such that the results are similar to CAST. This signal generation model has similar characteristics mean, variance and power spectral density as the true CAST estimation error. In this way, ADAMS software can still be used while capturing the higher fidelity spacecraft dynamics modeling from CAST software.
NASA's Software Safety Standard
NASA Technical Reports Server (NTRS)
Ramsay, Christopher M.
2007-01-01
NASA relies more and more on software to control, monitor, and verify its safety critical systems, facilities and operations. Since the 1960's there has hardly been a spacecraft launched that does not have a computer on board that will provide command and control services. There have been recent incidents where software has played a role in high-profile mission failures and hazardous incidents. For example, the Mars Orbiter, Mars Polar Lander, the DART (Demonstration of Autonomous Rendezvous Technology), and MER (Mars Exploration Rover) Spirit anomalies were all caused or contributed to by software. The Mission Control Centers for the Shuttle, ISS, and unmanned programs are highly dependant on software for data displays, analysis, and mission planning. Despite this growing dependence on software control and monitoring, there has been little to no consistent application of software safety practices and methodology to NASA's projects with safety critical software. Meanwhile, academia and private industry have been stepping forward with procedures and standards for safety critical systems and software, for example Dr. Nancy Leveson's book Safeware: System Safety and Computers. The NASA Software Safety Standard, originally published in 1997, was widely ignored due to its complexity and poor organization. It also focused on concepts rather than definite procedural requirements organized around a software project lifecycle. Led by NASA Headquarters Office of Safety and Mission Assurance, the NASA Software Safety Standard has recently undergone a significant update. This new standard provides the procedures and guidelines for evaluating a project for safety criticality and then lays out the minimum project lifecycle requirements to assure the software is created, operated, and maintained in the safest possible manner. This update of the standard clearly delineates the minimum set of software safety requirements for a project without detailing the implementation for those requirements. This allows the projects leeway to meet these requirements in many forms that best suit a particular project's needs and safety risk. In other words, it tells the project what to do, not how to do it. This update also incorporated advances in the state of the practice of software safety from academia and private industry. It addresses some of the more common issues now facing software developers in the NASA environment such as the use of Commercial-Off-the-Shelf Software (COTS), Modified OTS (MOTS), Government OTS (GOTS), and reused software. A team from across NASA developed the update and it has had both NASA-wide internal reviews by software engineering, quality, safety, and project management. It has also had expert external review. This presentation and paper will discuss the new NASA Software Safety Standard, its organization, and key features. It will start with a brief discussion of some NASA mission failures and incidents that had software as one of their root causes. It will then give a brief overview of the NASA Software Safety Process. This will include an overview of the key personnel responsibilities and functions that must be performed for safety-critical software.
NASA Technical Reports Server (NTRS)
Keller, Richard M. (Editor); Barstow, David; Lowry, Michael R.; Tong, Christopher H.
1992-01-01
The goal of this workshop is to identify different architectural approaches to building domain-specific software design systems and to explore issues unique to domain-specific (vs. general-purpose) software design. Some general issues that cut across the particular software design domain include: (1) knowledge representation, acquisition, and maintenance; (2) specialized software design techniques; and (3) user interaction and user interface.
Empirical studies of software design: Implications for SSEs
NASA Technical Reports Server (NTRS)
Krasner, Herb
1988-01-01
Implications for Software Engineering Environments (SEEs) are presented in viewgraph format for characteristics of projects studied; significant problems and crucial problem areas in software design for large systems; layered behavioral model of software processes; implications of field study results; software project as an ecological system; results of the LIFT study; information model of design exploration; software design strategies; results of the team design study; and a list of publications.
Formal Validation of Aerospace Software
NASA Astrophysics Data System (ADS)
Lesens, David; Moy, Yannick; Kanig, Johannes
2013-08-01
Any single error in critical software can have catastrophic consequences. Even though failures are usually not advertised, some software bugs have become famous, such as the error in the MIM-104 Patriot. For space systems, experience shows that software errors are a serious concern: more than half of all satellite failures from 2000 to 2003 involved software. To address this concern, this paper addresses the use of formal verification of software developed in Ada.
Cost Estimation of Software Development and the Implications for the Program Manager
1992-06-01
Software Lifecycle Model (SLIM), the Jensen System-4 model, the Software Productivity, Quality, and Reliability Estimator ( SPQR \\20), the Constructive...function models in current use are the Software Productivity, Quality, and Reliability Estimator ( SPQR /20) and the Software Architecture Sizing and...Estimator ( SPQR /20) was developed by T. Capers Jones of Software Productivity Research, Inc., in 1985. The model is intended to estimate the outcome
Software Library: A Reusable Software Issue.
1984-06-01
On reverse aide it neceeary aid Identify by block number) Software Library; Program Library; Reusability; Generator 20 ABSTRACT (Cmlnue on revere... Software Library. A particular example of the Software Library, the Program Library, is described as a prototype of a reusable library. A hierarchical... programming libraries are described. Finally, non code products in the Software Library are discussed. Accesson Fo NTIS R~jS DrrC TA Availability Codes 0
Self-assembling software generator
Bouchard, Ann M [Albuquerque, NM; Osbourn, Gordon C [Albuquerque, NM
2011-11-25
A technique to generate an executable task includes inspecting a task specification data structure to determine what software entities are to be generated to create the executable task, inspecting the task specification data structure to determine how the software entities will be linked after generating the software entities, inspecting the task specification data structure to determine logic to be executed by the software entities, and generating the software entities to create the executable task.
Software Assurance: Five Essential Considerations for Acquisition Officials
2007-05-01
May 2007 www.stsc.hill.af.mil 17 2 • address security concerns in the software development life cycle ( SDLC )? • Are there formal software quality...What threat modeling process, if any, is used when designing the software ? What analysis, design, and construction tools are used by your software design...the-shelf (COTS), government off-the-shelf (GOTS), open- source, embedded, and legacy software . Attackers exploit unintentional vulnerabil- ities or
Factors That Affect Software Testability
NASA Technical Reports Server (NTRS)
Voas, Jeffrey M.
1991-01-01
Software faults that infrequently affect software's output are dangerous. When a software fault causes frequent software failures, testing is likely to reveal the fault before the software is releases; when the fault remains undetected during testing, it can cause disaster after the software is installed. A technique for predicting whether a particular piece of software is likely to reveal faults within itself during testing is found in [Voas91b]. A piece of software that is likely to reveal faults within itself during testing is said to have high testability. A piece of software that is not likely to reveal faults within itself during testing is said to have low testability. It is preferable to design software with higher testabilities from the outset, i.e., create software with as high of a degree of testability as possible to avoid the problems of having undetected faults that are associated with low testability. Information loss is a phenomenon that occurs during program execution that increases the likelihood that a fault will remain undetected. In this paper, I identify two brad classes of information loss, define them, and suggest ways of predicting the potential for information loss to occur. We do this in order to decrease the likelihood that faults will remain undetected during testing.
Survey of Verification and Validation Techniques for Small Satellite Software Development
NASA Technical Reports Server (NTRS)
Jacklin, Stephen A.
2015-01-01
The purpose of this paper is to provide an overview of the current trends and practices in small-satellite software verification and validation. This document is not intended to promote a specific software assurance method. Rather, it seeks to present an unbiased survey of software assurance methods used to verify and validate small satellite software and to make mention of the benefits and value of each approach. These methods include simulation and testing, verification and validation with model-based design, formal methods, and fault-tolerant software design with run-time monitoring. Although the literature reveals that simulation and testing has by far the longest legacy, model-based design methods are proving to be useful for software verification and validation. Some work in formal methods, though not widely used for any satellites, may offer new ways to improve small satellite software verification and validation. These methods need to be further advanced to deal with the state explosion problem and to make them more usable by small-satellite software engineers to be regularly applied to software verification. Last, it is explained how run-time monitoring, combined with fault-tolerant software design methods, provides an important means to detect and correct software errors that escape the verification process or those errors that are produced after launch through the effects of ionizing radiation.
Distributed and Collaborative Software Analysis
NASA Astrophysics Data System (ADS)
Ghezzi, Giacomo; Gall, Harald C.
Throughout the years software engineers have come up with a myriad of specialized tools and techniques that focus on a certain type of
Guidance and Control Software Project Data - Volume 3: Verification Documents
NASA Technical Reports Server (NTRS)
Hayhurst, Kelly J. (Editor)
2008-01-01
The Guidance and Control Software (GCS) project was the last in a series of software reliability studies conducted at Langley Research Center between 1977 and 1994. The technical results of the GCS project were recorded after the experiment was completed. Some of the support documentation produced as part of the experiment, however, is serving an unexpected role far beyond its original project context. Some of the software used as part of the GCS project was developed to conform to the RTCA/DO-178B software standard, "Software Considerations in Airborne Systems and Equipment Certification," used in the civil aviation industry. That standard requires extensive documentation throughout the software development life cycle, including plans, software requirements, design and source code, verification cases and results, and configuration management and quality control data. The project documentation that includes this information is open for public scrutiny without the legal or safety implications associated with comparable data from an avionics manufacturer. This public availability has afforded an opportunity to use the GCS project documents for DO-178B training. This report provides a brief overview of the GCS project, describes the 4-volume set of documents and the role they are playing in training, and includes the verification documents from the GCS project. Volume 3 contains four appendices: A. Software Verification Cases and Procedures for the Guidance and Control Software Project; B. Software Verification Results for the Pluto Implementation of the Guidance and Control Software; C. Review Records for the Pluto Implementation of the Guidance and Control Software; and D. Test Results Logs for the Pluto Implementation of the Guidance and Control Software.
SU-E-P-43: A Knowledge Based Approach to Guidelines for Software Safety
DOE Office of Scientific and Technical Information (OSTI.GOV)
Salomons, G; Kelly, D
Purpose: In the fall of 2012, a survey was distributed to medical physicists across Canada. The survey asked the respondents to comment on various aspects of software development and use in their clinic. The survey revealed that most centers employ locally produced (in-house) software of some kind. The respondents also indicated an interest in having software guidelines, but cautioned that the realities of cancer clinics include variations, that preclude a simple solution. Traditional guidelines typically involve periodically repeating a set of prescribed tests with defined tolerance limits. However, applying a similar formula to software is problematic since it assumes thatmore » the users have a perfect knowledge of how and when to apply the software and that if the software operates correctly under one set of conditions it will operate correctly under all conditions Methods: In the approach presented here the personnel involved with the software are included as an integral part of the system. Activities performed to improve the safety of the software are done with both software and people in mind. A learning oriented approach is taken, following the premise that the best approach to safety is increasing the understanding of those associated with the use or development of the software. Results: The software guidance document is organized by areas of knowledge related to use and development of software. The categories include: knowledge of the underlying algorithm and its limitations; knowledge of the operation of the software, such as input values, parameters, error messages, and interpretation of output; and knowledge of the environment for the software including both data and users. Conclusion: We propose a new approach to developing guidelines which is based on acquiring knowledge-rather than performing tests. The ultimate goal is to provide robust software guidelines which will be practical and effective.« less
Luckey, R.R.; Becker, M.F.
1998-01-01
A study of the High Plains aquifer in Okla homa was initiated in 1996 to: (1) provide the information needed by the Oklahoma Water Resources Board to manage the quantity of water produced from the aquifer; and (2) provide base line water-chemistry data. The approach used to meet the first objective is to develop a digital ground-water flow model. The model will be cali brated, in part, by comparing simulated and esti mated predevelopment discharge from the aquifer to streams and cross-boundary flow. This report presents the estimated predevelopment discharge to streams from the High Plains aquifer. Streamflow data were the primary source of information used to estimate predevelopment dis charge from the High Plains aquifer. Data from 30 streamflow stations between the Arkansas and Canadian Rivers were considered in the analysis, and winter low-flow frequencies for 7-, 14-, and 30-day periods were determined for 25 stations. The 14-day low flow with a recurrence interval of 2 years was the primary value used to estimate pre development discharge from the aquifer. The streams that drain the eastern part of the High Plains aquifer in Kansas (generally east of 99.5 longitude) are estimated to have had large predevelopment discharge from the aquifer, and most of them received discharge from near their headwaters. For streams with more than one streamflow gage, the upper perennial reaches appeared to have gained more discharge from the aquifer than the lower reaches. The total predevel opment discharge from the aquifer in this area to several streams is estimated to have been about 312 cubic feet per second, not including discharge that probably went directly to the Arkansas River. The Cimarron River and its tributaries are estimated to have gained about 78 cubic feet per second, but nearly one-half that amount was lost in the lower reaches of the river. The cause of the loss in the lower reaches is unknown. The Beaver River and its tributaries are estimated to have gained a net of about 10 cubic feet per second above Wolf Creek with the upper reaches gaining more than the lower reaches. Wolf Creek is estimated to have gained 30 cubic feet per second over its total length.
Software Development as Music Education Research
ERIC Educational Resources Information Center
Brown, Andrew R.
2007-01-01
This paper discusses how software development can be used as a method for music education research. It explains how software development can externalize ideas, stimulate action and reflection, and provide evidence to support the educative value of new software-based experiences. Parallels between the interactive software development process and…
Software Trends and Trendsetters: How They're Shaping an Industry.
ERIC Educational Resources Information Center
McGinty, Tony; And Others
1987-01-01
Discusses trends in educational software and the effects of new developments on publishers and on the computer industry. Marketing prospects for software are examined, and recent advances are highlighted, including integrated learning systems, skill-based software, software tied to textbooks, networking, and freeware. (LRW)
Requirements Engineering in Building Climate Science Software
ERIC Educational Resources Information Center
Batcheller, Archer L.
2011-01-01
Software has an important role in supporting scientific work. This dissertation studies teams that build scientific software, focusing on the way that they determine what the software should do. These requirements engineering processes are investigated through three case studies of climate science software projects. The Earth System Modeling…