Practical methods to improve the development of computational software

International Nuclear Information System (INIS)

Osborne, A. G.; Harding, D. W.; Deinert, M. R.

2013-01-01

The use of computation has become ubiquitous in science and engineering. As the complexity of computer codes has increased, so has the need for robust methods to minimize errors. Past work has show that the number of functional errors is related the number of commands that a code executes. Since the late 1960's, major participants in the field of computation have encouraged the development of best practices for programming to help reduce coder induced error, and this has lead to the emergence of 'software engineering' as a field of study. Best practices for coding and software production have now evolved and become common in the development of commercial software. These same techniques, however, are largely absent from the development of computational codes by research groups. Many of the best practice techniques from the professional software community would be easy for research groups in nuclear science and engineering to adopt. This paper outlines the history of software engineering, as well as issues in modern scientific computation, and recommends practices that should be adopted by individual scientific programmers and university research groups. (authors)

Software metrics a rigorous and practical approach

CERN Document Server

Fenton, Norman

2014-01-01

A Framework for Managing, Measuring, and Predicting Attributes of Software Development Products and ProcessesReflecting the immense progress in the development and use of software metrics in the past decades, Software Metrics: A Rigorous and Practical Approach, Third Edition provides an up-to-date, accessible, and comprehensive introduction to software metrics. Like its popular predecessors, this third edition discusses important issues, explains essential concepts, and offers new approaches for tackling long-standing problems.New to the Third EditionThis edition contains new material relevant

Sandia National Laboratories Advanced Simulation and Computing (ASC) software quality plan. Part 1 : ASC software quality engineering practices version 1.0.

Energy Technology Data Exchange (ETDEWEB)

Minana, Molly A.; Sturtevant, Judith E.; Heaphy, Robert; Hodges, Ann Louise; Boucheron, Edward A.; Drake, Richard Roy; Forsythe, Christi A.; Schofield, Joseph Richard, Jr.; Pavlakos, Constantine James; Williamson, Charles Michael; Edwards, Harold Carter

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 and 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.

Agile Scientists? : Investigating Agile Practices in Scientific Software Development

OpenAIRE

Sletholt, Magnus Thorstein

2011-01-01

The topic of this master thesis is development of scientific software. The research questions put forth are oriented towards specific agile practices and whether these are present in the development processes of scientific software projects. Moreover, the effects of applying such agile practices, particularly pertaining to the handling of requirements and testing, in scientific software projects are addressed in the thesis. In order to answer the proposed research questions a table consisting...

Sandia National Laboratories Advanced Simulation and Computing (ASC) software quality plan. Part 1: ASC software quality engineering practices, Version 2.0.

Energy Technology Data Exchange (ETDEWEB)

Sturtevant, Judith E.; Heaphy, Robert; Hodges, Ann Louise; Boucheron, Edward A.; Drake, Richard Roy; Minana, Molly A.; Hackney, Patricia; Forsythe, Christi A.; Schofield, Joseph Richard, Jr. (,; .); Pavlakos, Constantine James; Williamson, Charles Michael; Edwards, Harold Carter

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.

Software war stories case studies in software management

CERN Document Server

Reifer, Donald J

2014-01-01

This book provides readers with practical advice on how to handle the many issues that can arise as a software project unfolds. The book uses twelve case studies to communicate lessons learned addressing such issues as they occur in government, industrial and academic settings. These cases focus on addressing the things that can be done to establish and meet reasonable expectations.  Such corrective actions often involve more than just dealing with project issues.  For example, software practitioners may have to address obstacles placed in their way by procurement, organizational procedures an

Using Case Study Videos as an Effective Active Learning Tool to Teach Software Development Best Practices (Invited Paper

Directory of Open Access Journals (Sweden)

Sushil Acharya

2017-06-01

Full Text Available The fundamental challenge to a solution to improve software quality is in the people and processes that develop software products. Imparting real world experiences in software development best practices to undergraduate students is often a challenge due to the lack of effective learning tools. This pedagogical requirement is important because graduates are expected to develop software that meets rigorous quality standards. Certain best practices are difficult to comprehend by course lectures alone and are enhanced with supplemental learning tools. Realizing the necessity of such teaching tools, we designed and developed six (6 delivery hours of case study videos for use in courses that impart knowledge on Software Verification & Validation (SV&V topics viz. requirements engineering, and software reviews. We see case study videos as an effective active learning tool in our flipped classroom approach. We present our design of the case study video in its generic components envisioning how it may be used in general. To evaluate our active learning tools we mapped the learning objectives of the case Study videos to the expected learning outcomes for ABET accreditation of an undergraduate engineering program. Our implementation has been disseminated to partner institutions. Results of delivery in a faculty workshop and in two different university courses are shared.

BCI meeting 2005--workshop on technology: hardware and software.

Science.gov (United States)

Cincotti, Febo; Bianchi, Luigi; Birch, Gary; Guger, Christoph; Mellinger, Jürgen; Scherer, Reinhold; Schmidt, Robert N; Yáñez Suárez, Oscar; Schalk, Gerwin

2006-06-01

This paper describes the outcome of discussions held during the Third International BCI Meeting at a workshop to review and evaluate the current state of BCI-related hardware and software. Technical requirements and current technologies, standardization procedures and future trends are covered. The main conclusion was recognition of the need to focus technical requirements on the users' needs and the need for consistent standards in BCI research.

HAZARD ANALYSIS SOFTWARE

International Nuclear Information System (INIS)

Sommer, S; Tinh Tran, T.

2008-01-01

Washington Safety Management Solutions, LLC developed web-based software to improve the efficiency and consistency of hazard identification and analysis, control selection and classification, and to standardize analysis reporting at Savannah River Site. In the new nuclear age, information technology provides methods to improve the efficiency of the documented safety analysis development process which includes hazard analysis activities. This software provides a web interface that interacts with a relational database to support analysis, record data, and to ensure reporting consistency. A team of subject matter experts participated in a series of meetings to review the associated processes and procedures for requirements and standard practices. Through these meetings, a set of software requirements were developed and compiled into a requirements traceability matrix from which software could be developed. The software was tested to ensure compliance with the requirements. Training was provided to the hazard analysis leads. Hazard analysis teams using the software have verified its operability. The software has been classified as NQA-1, Level D, as it supports the analysis team but does not perform the analysis. The software can be transported to other sites with alternate risk schemes. The software is being used to support the development of 14 hazard analyses. User responses have been positive with a number of suggestions for improvement which are being incorporated as time permits. The software has enforced a uniform implementation of the site procedures. The software has significantly improved the efficiency and standardization of the hazard analysis process

Assessment of best practice of software development in developing ...

African Journals Online (AJOL)

... Understand the technology of the software (4.03), Memory limit set (3.91), Application pool not shared (3.88) and other parameters were examined for software development. The analysis shows the variance of the assessment of best practices in Software development firms and they are in conformity with the global trend.

Effects of the Meetings-Flow Approach on Quality Teamwork in the Training of Software Capstone Projects

Science.gov (United States)

Chen, Chung-Yang; Hong, Ya-Chun; Chen, Pei-Chi

2014-01-01

Software development relies heavily on teamwork; determining how to streamline this collaborative development is an essential training subject in computer and software engineering education. A team process known as the meetings-flow (MF) approach has recently been introduced in software capstone projects in engineering programs at various…

On the Current Measurement Practices in Agile Software Development

OpenAIRE

Javdani, Taghi; Zulzalil, Hazura; Ghani, Abdul Azim Abd; Sultan, Abu Bakar Md; Parizi, Reza Meimandi

2013-01-01

Agile software development (ASD) methods were introduced as a reaction to traditional software development methods. Principles of these methods are different from traditional methods and so there are some different processes and activities in agile methods comparing to traditional methods. Thus ASD methods require different measurement practices comparing to traditional methods. Agile teams often do their projects in the simplest and most effective way so, measurement practices in agile metho...

Practical open source software for libraries

CERN Document Server

Engard, Nicole

2010-01-01

Open source refers to an application whose source code is made available for use or modification as users see fit. This means libraries gain more flexibility and freedom than with software purchased with license restrictions. Both the open source community and the library world live by the same rules and principles. Practical Open Source Software for Libraries explains the facts and dispels myths about open source. Chapters introduce librarians to open source and what it means for libraries. The reader is provided with links to a toolbox full of freely available open source products to use in

Seismology software: state of the practice

Science.gov (United States)

Smith, W. Spencer; Zeng, Zheng; Carette, Jacques

2018-05-01

We analyzed the state of practice for software development in the seismology domain by comparing 30 software packages on four aspects: product, implementation, design, and process. We found room for improvement in most seismology software packages. The principal areas of concern include a lack of adequate requirements and design specification documents, a lack of test data to assess reliability, a lack of examples to get new users started, and a lack of technological tools to assist with managing the development process. To assist going forward, we provide recommendations for a document-driven development process that includes a problem statement, development plan, requirement specification, verification and validation (V&V) plan, design specification, code, V&V report, and a user manual. We also provide advice on tool use, including issue tracking, version control, code documentation, and testing tools.

Seismology software: state of the practice

Science.gov (United States)

Smith, W. Spencer; Zeng, Zheng; Carette, Jacques

2018-02-01

We analyzed the state of practice for software development in the seismology domain by comparing 30 software packages on four aspects: product, implementation, design, and process. We found room for improvement in most seismology software packages. The principal areas of concern include a lack of adequate requirements and design specification documents, a lack of test data to assess reliability, a lack of examples to get new users started, and a lack of technological tools to assist with managing the development process. To assist going forward, we provide recommendations for a document-driven development process that includes a problem statement, development plan, requirement specification, verification and validation (V&V) plan, design specification, code, V&V report, and a user manual. We also provide advice on tool use, including issue tracking, version control, code documentation, and testing tools.

Four simple recommendations to encourage best practices in research software [version 1; referees: 2 approved

Directory of Open Access Journals (Sweden)

Rafael C. Jiménez

2017-06-01

Full Text Available 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.

Sandia National Laboratories Advanced Simulation and Computing (ASC) software quality plan part 2 mappings for the ASC software quality engineering practices, version 2.0.

Energy Technology Data Exchange (ETDEWEB)

Heaphy, Robert; Sturtevant, Judith E.; Hodges, Ann Louise; Boucheron, Edward A.; Drake, Richard Roy; Minana, Molly A.; Hackney, Patricia; Forsythe, Christi A.; Schofield, Joseph Richard, Jr. (,; .); Pavlakos, Constantine James; Williamson, Charles Michael; Edwards, Harold Carter

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 CPR001.3.2 and CPR001.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.

Software: our quest for excellence. Honoring 50 years of software history, progress, and process

Energy Technology Data Exchange (ETDEWEB)

NONE

1997-06-01

The Software Quality Forum was established by the Software Quality Assurance (SQA) Subcommittee, which serves as a technical advisory group on software engineering and quality initiatives and issues for DOE`s quality managers. The forum serves as an opportunity for all those involved in implementing SQA programs to meet and share ideas and concerns. Participation from managers, quality engineers, and software professionals provides an ideal environment for identifying and discussing issues and concerns. The interaction provided by the forum contributes to the realization of a shared goal--high quality software product. Topics include: testing, software measurement, software surety, software reliability, SQA practices, assessments, software process improvement, certification and licensing of software professionals, CASE tools, software project management, inspections, and management`s role in ensuring SQA. The bulk of this document consists of vugraphs. Selected papers have been indexed separately for inclusion in the Energy Science and Technology Database.

Teaching practice and effect of the curriculum design and simulation courses under the support of professional optical software

Science.gov (United States)

Lin, YuanFang; Zheng, XiaoDong; Huang, YuJia

2017-08-01

Curriculum design and simulation courses are bridges to connect specialty theories, engineering practice and experimental skills. In order to help students to have the computer aided optical system design ability adapting to developments of the times, a professional optical software-Advanced System of Analysis Program (ASAP) was used in the research teaching of curriculum design and simulation courses. The ASAP tutorials conducting, exercises both complementing and supplementing the lectures, hands-on practice in class, autonomous learning and independent design after class were bridged organically, to guide students "learning while doing, learning by doing", paying more attention to the process instead of the results. Several years of teaching practice of curriculum design and simulation courses shows that, project-based learning meets society needs of training personnel with knowledge, ability and quality. Students have obtained not only skills of using professional software, but also skills of finding and proposing questions in engineering practice, the scientific method of analyzing and solving questions with specialty knowledge, in addition, autonomous learning ability, teamwork spirit and innovation consciousness, still scientific attitude of facing failure and scientific spirit of admitting deficiency in the process of independent design and exploration.

Linear mixed models a practical guide using statistical software

CERN Document Server

West, Brady T; Galecki, Andrzej T

2006-01-01

Simplifying the often confusing array of software programs for fitting linear mixed models (LMMs), Linear Mixed Models: A Practical Guide Using Statistical Software provides a basic introduction to primary concepts, notation, software implementation, model interpretation, and visualization of clustered and longitudinal data. This easy-to-navigate reference details the use of procedures for fitting LMMs in five popular statistical software packages: SAS, SPSS, Stata, R/S-plus, and HLM. The authors introduce basic theoretical concepts, present a heuristic approach to fitting LMMs based on bo

TAPSOFT'95: Theory and Practice of Software Development

DEFF Research Database (Denmark)

This volume presents the proceedings of the Sixth International Joint Conference on the Theory and Practice of Software Engineering, TAPSOFT '95, held in Aarhus, Denmark in May 1995. TAPSOFT '95 celebrates the 10th anniversary of this conference series started in Berlin in 1985 to bring together...... theoretical computer scientists and software engineers (researchers and practitioners) with a view to discussing how formal methods can usefully be applied in software development. The volume contains seven invited papers, among them one by Vaugham Pratt on the recently revealed bug in the Pentium chip...

Software and the Scientist: Coding and Citation Practices in Geodynamics

Science.gov (United States)

Hwang, Lorraine; Fish, Allison; Soito, Laura; Smith, MacKenzie; Kellogg, Louise H.

2017-11-01

In geodynamics as in other scientific areas, computation has become a core component of research, complementing field observation, laboratory analysis, experiment, and theory. Computational tools for data analysis, mapping, visualization, modeling, and simulation are essential for all aspects of the scientific workflow. Specialized scientific software is often developed by geodynamicists for their own use, and this effort represents a distinctive intellectual contribution. Drawing on a geodynamics community that focuses on developing and disseminating scientific software, we assess the current practices of software development and attribution, as well as attitudes about the need and best practices for software citation. We analyzed publications by participants in the Computational Infrastructure for Geodynamics and conducted mixed method surveys of the solid earth geophysics community. From this we learned that coding skills are typically learned informally. Participants considered good code as trusted, reusable, readable, and not overly complex and considered a good coder as one that participates in the community in an open and reasonable manor contributing to both long- and short-term community projects. Participants strongly supported citing software reflected by the high rate a software package was named in the literature and the high rate of citations in the references. However, lacking are clear instructions from developers on how to cite and education of users on what to cite. In addition, citations did not always lead to discoverability of the resource. A unique identifier to the software package itself, community education, and citation tools would contribute to better attribution practices.

More about software requirements thorny issues and practical advice

CERN Document Server

Wiegers, Karl E

2006-01-01

No matter how much instruction you've had on managing software requirements, there's no substitute for experience. Too often, lessons about requirements engineering processes lack the no-nonsense guidance that supports real-world solutions. Complementing the best practices presented in his book, Software Requirements, Second Edition, requirements engineering authority Karl Wiegers tackles even more of the real issues head-on in this book. With straightforward, professional advice and practical solutions based on actual project experiences, this book answers many of the tough questions rais

Hybrid Software and System Development in Practice: Waterfall, Scrum, and Beyond

DEFF Research Database (Denmark)

Kuhrmann, Marco; Diebold, Philipp; Münch, Jürgen

2017-01-01

Software and system development faces numerous challenges of rapidly changing markets. To address such challenges, companies and projects design and adopt specific development approaches by combining well-structured comprehensive methods and flexible agile practices. Yet, the number of methods...... and practices is large, and available studies argue that the actual process composition is carried out in a fairly ad-hoc manner. The present paper reports on a survey on hybrid software development approaches. We study which approaches are used in practice, how different approaches are combined, and what...... contextual factors influence the use and combination of hybrid software development approaches. Our results from 69 study participants show a variety of development approaches used and combined in practice. We show that most combinations follow a pattern in which a traditional process model serves...

Fourth Workshop on Sustainable Software for Science: Practice and Experiences (WSSSPE4)

NARCIS (Netherlands)

Katz, Daniel S; Niemeyer, Kyle E; Gesing, Sandra; Hwang, Lorraine; Bangerth, Wolfgang; Hettrick, Simon; Idaszak, Ray; Salac, Jean; Chue Hong, Neil; Núñez-Corrales, Santiago; Allen, Alice; Geiger, R Stuart; Miller, Jonah; Chen, Emily; Dubey, Anshu; Lago, Patricia

2018-01-01

This article summarizes motivations, organization, and activities of the Fourth Workshop on Sustainable Software for Science: Practice and Experiences (WSSSPE4). The WSSSPE series promotes sustainable research software by positively impacting principles and best practices, careers, learning, and

76 FR 16785 - Meeting for Software Developers on the Technical Specifications for Common Formats for Patient...

Science.gov (United States)

2011-03-25

... designed as an interactive forum where PSOs and software developers can provide input on these technical... contact the Food and Drug Administration (FDA) Office of Equal Employment Opportunity and Disability.... Throughout the meeting there will be interactive discussion to allow meeting participants not only to provide...

Flexible software process lines in practice: A metamodel-based approach to effectively construct and manage families of software process models

DEFF Research Database (Denmark)

Kuhrmann, Marco; Ternité, Thomas; Friedrich, Jan

2017-01-01

Process flexibility and adaptability is frequently discussed, and several proposals aim to improve software processes for a given organization-/project context. A software process line (SPrL) is an instrument to systematically construct and manage variable software processes, by combining pre-def......: A metamodel-based approach to effectively construct and manage families of software process models [Ku16]. This paper was published as original research article in the Journal of Systems and Software.......Process flexibility and adaptability is frequently discussed, and several proposals aim to improve software processes for a given organization-/project context. A software process line (SPrL) is an instrument to systematically construct and manage variable software processes, by combining pre...... to construct flexible SPrLs and show its practical application in the German V-Modell XT. We contribute a proven approach that is presented as metamodel fragment for reuse and implementation in further process modeling approaches. This summary refers to the paper Flexible software process lines in practice...

Accelerating Software Development through Agile Practices--A Case Study of a Small-Scale, Time-Intensive Web Development Project at a College-Level IT Competition

Science.gov (United States)

Zhang, Xuesong; Dorn, Bradley

2012-01-01

Agile development has received increasing interest both in industry and academia due to its benefits in developing software quickly, meeting customer needs, and keeping pace with the rapidly changing requirements. However, agile practices and scrum in particular have been mainly tested in mid- to large-size projects. In this paper, we present…

Industry best practices for the software development life cycle

Science.gov (United States)

2007-11-01

In the area of software development, there are many different views of what constitutes a best practice. The goal of this project was to identify a set of industry best practice techniques that fit the needs of the Montana Department of Transportatio...

Usability challenges in an Ethiopian software development organization

DEFF Research Database (Denmark)

Teka, Degif; Dittrich, Yvonne; Kifle, Mesfin

2016-01-01

Usability and user centered design (UCD) are central to software development. In developing countries, the gap between IT development and the local use situation is larger than in western countries. However, usability is neither well addressed in software practice nor at the policy making level...... in Ethiopia. Software practitioners focus on functional requirements, meeting deadlines and budget. The software development industry in Ethiopia is in its early stage. The article aims at understanding usability practices in an Ethiopian software development company. Developers, system analysts, product...... configuration, their experience, cultural knowledge and common sense regarding the users' situation guided the design. Prototypes and fast delivery of working versions helped in getting user feedback even if early user focus proved to be a challenge as communication between developers and users suffered from...

A Practical Software Architecture for Virtual Universities

Science.gov (United States)

Xiang, Peifeng; Shi, Yuanchun; Qin, Weijun

2006-01-01

This article introduces a practical software architecture called CUBES, which focuses on system integration and evolvement for online virtual universities. The key of CUBES is a supporting platform that helps to integrate and evolve heterogeneous educational applications developed by different organizations. Both standardized educational…

Scientific Software - the role of best practices and recommendations

Science.gov (United States)

Fritzsch, Bernadette; Bernstein, Erik; Castell, Wolfgang zu; Diesmann, Markus; Haas, Holger; Hammitzsch, Martin; Konrad, Uwe; Lähnemann, David; McHardy, Alice; Pampel, Heinz; Scheliga, Kaja; Schreiber, Andreas; Steglich, Dirk

2017-04-01

In Geosciences - like in most other communities - scientific work strongly depends on software. For big data analysis, existing (closed or open source) program packages are often mixed with newly developed codes. Different versions of software components and varying configurations can influence the result of data analysis. This often makes reproducibility of results and reuse of codes very difficult. Policies for publication and documentation of used and newly developed software, along with best practices, can help tackle this problem. Within the Helmholtz Association a Task Group "Access to and Re-use of scientific software" was implemented by the Open Science Working Group in 2016. The aim of the Task Group is to foster the discussion about scientific software in the Open Science context and to formulate recommendations for the production and publication of scientific software, ensuring open access to it. As a first step, a workshop gathered interested scientists from institutions across Germany. The workshop brought together various existing initiatives from different scientific communities to analyse current problems, share established best practices and come up with possible solutions. The subjects in the working groups covered a broad range of themes, including technical infrastructures, standards and quality assurance, citation of software and reproducibility. Initial recommendations are presented and discussed in the talk. They are the foundation for further discussions in the Helmholtz Association and the Priority Initiative "Digital Information" of the Alliance of Science Organisations in Germany. The talk aims to inform about the activities and to link with other initiatives on the national or international level.

Aligning the economic modeling of software reuse with reuse practices

NARCIS (Netherlands)

Postmus, D.; Meijler, 27696

In contrast to current practices where software reuse is applied recursively and reusable assets are tailored trough parameterization or specialization, existing reuse economic models assume that (i) the cost of reusing a software asset depends on its size and (ii) reusable assets are developed from

Software that meets its Intent

NARCIS (Netherlands)

Huisman, Marieke; Bos, Herbert; Brinkkemper, Sjaak; van Deursen, Arie; Groote, Jan Friso; Lago, Patricia; van de Pol, Jaco; Visser, Eelco; Margaria, Tiziana; Steffen, Bernhard

2016-01-01

Software is widely used, and society increasingly depends on its reliability. However, software has become so complex and it evolves so quickly that we fail to keep it under control. Therefore, we propose intents: fundamental laws that capture a software systems’ intended behavior (resilient,

Continuous software quality analysis for the ATLAS experiment

CERN Document Server

Washbrook, Andrew; The ATLAS collaboration

2017-01-01

The software for the ATLAS experiment on the Large Hadron Collider at CERN has evolved over many years to meet the demands of Monte Carlo simulation, particle detector reconstruction and data analysis. At present over 3.8 million lines of C++ code (and close to 6 million total lines of code) are maintained by an active worldwide developer community. In order to run the experiment software efficiently at hundreds of computing centres it is essential to maintain a high level of software quality standards. The methods proposed to improve software quality practices by incorporating checks into the new ATLAS software build infrastructure.

The Art of Lean Software Development A Practical and Incremental Approach

CERN Document Server

Hibbs, Curt; Sullivan, Mike

2009-01-01

This succinct book explains how to you can apply the practices of Lean software development to dramatically increase productivity and quality. Lean principles are being applied successfully to product design, engineering, the supply chain, and now software development. You'll learn how to adopt Lean practices one at a time, rather than taking on the entire methodology at once. At each stage, you'll see significant, measurable results.

Top 10 metrics for life science software good practices [version 1; referees: 2 approved

Directory of Open Access Journals (Sweden)

Haydee Artaza

2016-08-01

Full Text Available Metrics for assessing adoption of good development practices are a useful way to ensure that software is sustainable, reusable and functional. Sustainability means that the software used today will be available - and continue to be improved and supported - in the future. We report here an initial set of metrics that measure good practices in software development. This initiative differs from previously developed efforts in being a community-driven grassroots approach where experts from different organisations propose good software practices that have reasonable potential to be adopted by the communities they represent. We not only focus our efforts on understanding and prioritising good practices, we assess their feasibility for implementation and publish them here.

Current practice in software development for computational neuroscience and how to improve it.

Science.gov (United States)

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.

Current practice in software development for computational neuroscience and how to improve it.

Directory of Open Access Journals (Sweden)

Marc-Oliver Gewaltig

2014-01-01

Full Text Available 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.

Student perceptions of drill-and-practice mathematics software in primary education

Science.gov (United States)

Kuiper, Els; de Pater-Sneep, Martie

2014-06-01

Drill-and-practice mathematics software offers teachers a relatively simple way to use technology in the classroom. One of the reasons to use the software may be that it motivates children, working on the computer being more "fun" than doing regular school work. However, students' own perceptions of such software are seldom studied. This article reports on a study on the opinions of Grade 5 and 6 students regarding two mathematics drill-and-practice software packages. In total, 329 students from ten Dutch primary schools took part in the study. The results show that a majority of the students preferred to work in their exercise book, for various reasons. Especially the rigid structure of the software is mentioned as a negative aspect by students. The elaborate arguments students used illustrate the importance of taking their opinions into account already at the primary level. Students' perceptions also show that the idea of ICT as naturally motivating for students may need modification.

Hybrid Software and System Development in Practice: Waterfall, Scrum, and Beyond

OpenAIRE

Kuhrmann, Marco; Diebold, Philipp; Münch, Jürgen; Tell, Paolo; Garousi, Vahid; Felderer, Michael; Trektere, Kitija; McCaffery, Fergal; Linssen, Oliver; Hanser, Eckhart; Prause, Christian

2017-01-01

Software and system development faces numerous challenges of rapidly changing markets. To address such challenges, companies and projects design and adopt specific development approaches by combining well-structured comprehensive methods and flexible agile practices. Yet, the number of methods and practices is large, and available studies argue that the actual process composition is carried out in a fairly ad-hoc manner. The present paper reports on a survey on hybrid software development app...

Linear mixed models a practical guide using statistical software

CERN Document Server

West, Brady T; Galecki, Andrzej T

2014-01-01

Highly recommended by JASA, Technometrics, and other journals, the first edition of this bestseller showed how to easily perform complex linear mixed model (LMM) analyses via a variety of software programs. Linear Mixed Models: A Practical Guide Using Statistical Software, Second Edition continues to lead readers step by step through the process of fitting LMMs. This second edition covers additional topics on the application of LMMs that are valuable for data analysts in all fields. It also updates the case studies using the latest versions of the software procedures and provides up-to-date information on the options and features of the software procedures available for fitting LMMs in SAS, SPSS, Stata, R/S-plus, and HLM.New to the Second Edition A new chapter on models with crossed random effects that uses a case study to illustrate software procedures capable of fitting these models Power analysis methods for longitudinal and clustered study designs, including software options for power analyses and suggest...

Referrals and relationships: in-practice referrals meetings in a general practice.

Science.gov (United States)

Rowlands, G; Willis, S; Singleton, A

2001-08-01

GP referrals to secondary care are an important factor in the cost of running the NHS. The known variation in referral rates between doctors has the potential to cause tension within primary care which will be exacerbated by the latest reorganization of primary care and the trend towards capitation-based budgets. The importance of postgraduate learning for GPs has been recognized; continuing professional development is moving towards self-directed practice-based learning programmes. Educational interventions have been shown to alter doctors' prescribing behaviour. This, together with the pressure on accounting for referral activity, makes the prospect of improving, and possibly reducing, referral activity through educational interventions very attractive. This study complemented a randomized controlled trial (RCT) which investigated whether an intervention of the type which had reduced prescribing costs would have a similar effect on referral activity. The context of the study, description of the characteristics of the practice and the issues seen as important by the doctors and practice manager were identified through preliminary semi-structured interviews. The practice then held a series of educational in-practice meetings to discuss referrals and issues arising from referrals. The audio- and videotaped transcripts were interpreted using content and group dynamic analysis. Participants commented upon our preliminary findings. In addition, we used dimensional analysis to induce a preliminary theory describing the effect of the intervention on this general practice which enabled us to review the findings of the parallel RCT. The educational value of the meetings and the learning needs of the participants were also assessed. Our complementary study showed no alteration of practice referral rates following the educational intervention. The qualitative study, unencumbered by the assumptions inherent in the development of the hypothesis tested in the RCT, highlighted

EISA 432 Energy Audits Best Practices: Software Tools

Energy Technology Data Exchange (ETDEWEB)

Maryl Fisher

2014-11-01

Five whole building analysis software tools that can aid an energy manager with fulfilling energy audit and commissioning/retro-commissioning requirements were selected for review in this best practices study. A description of each software tool is provided as well as a discussion of the user interface and level of expertise required for each tool, a review of how to use the tool for analyzing energy conservation opportunities, the format and content of reports generated by the tool, and a discussion on the applicability of the tool for commissioning.

Real-time Kernel Implementation Practice Program for Embedded Software Engineers' Education and its Evaluation

Science.gov (United States)

Yoshida, Toshio; Matsumoto, Masahide; Seo, Katsuhiko; Chino, Shinichiro; Sugino, Eiji; Sawamoto, Jun; Koizumi, Hisao

A real-time kernel (henceforth RTK) is in the center place of embedded software technology, and the understanding of RTK is indispensable for the embedded system design. To implement RTK, it is necessary to understand languages that describe RTK software program code, system programming manners, software development tools, CPU on that RTK runs and the interface between software and hardware, etc. in addition to understanding of RTK itself. This means RTK implementation process largely covers embedded software implementation process. Therefore, it is thought that RTK implementation practice program is very effective as a means of the acquisition of common embedded software skill in addition to deeper acquisition of RTK itself. In this paper, we propose to apply RTK implementing practice program to embedded software engineers educational program. We newly developed very small and step-up type RTK named μK for educational use, and held a seminar that used μK as a teaching material for the students of information science and engineers of the software house. As a result, we confirmed that RTK implementation practice program is very effective for the acquisition of embedded software common skill.

The intersection of software and strengths: Using internet technology and case management software to assist Strength-Based Practice.

Science.gov (United States)

Clark, Michael D; Brien, Dale W

2016-01-01

The focus of this investigation is the helping professionals working within American Indian and Alaska Native (AI/AN) communities. This article looks at how innovative technology-in the form of automated case management software and Internet connectivity-can assist effective implementation of Strength-based Practice and agency services within tribal courts and the many other helping agencies that serve AI/AN populations. We seek to expand practice knowledge by reviewing the benefits that this software and Internet connectivity can offer to agency operations and exploring how they can assist case management services.

Agile Software Development: An Introduction and Overview

Science.gov (United States)

Dingsøyr, Torgeir; Dybå, Tore; Moe, Nils Brede

Agile software development is an important topic in software engineering and information systems. This chapter provides a characterization and definition of agile software development, an overview of research through a summary of existing overview studies, an analysis of the research literature so far, and an introduction to the main themes of this book. The first part of the book provides foundations and background of agile development. The second part describes findings from studies of agile methods in practice. The third part identifies principal challenges and discusses new frontiers that agile development methods will meet in the future.

A Systematic Analysis of Functional Safety Certification Practices in Industrial Robot Software Development

Directory of Open Access Journals (Sweden)

Tong Xie

2017-01-01

Full Text Available For decades, industry robotics have delivered on the promise of speed, efficiency and productivity. The last several years have seen a sharp resurgence in the orders of industrial robots in China, and the areas addressed within industrial robotics has extended into safety-critical domains. However, safety standards have not yet been implemented widely in academia and engineering applications, particularly in robot software development. This paper presents a systematic analysis of functional safety certification practices in software development for the safety-critical software of industrial robots, to identify the safety certification practices used for the development of industrial robots in China and how these practices comply with the safety standard requirements. Reviewing from Chinese academic papers, our research shows that safety standards are barely used in software development of industrial robot. The majority of the papers propose various solutions to achieve safety, but only about two thirds of the papers refer to non-standardized approaches that mainly address the systematic level rather than the software development level. In addition, our research shows that with the development of artificial intelligent, an emerging field is still on the quest for standardized and suitable approaches to develop safety-critical software.

40 CFR 63.10390 - What management practice standard must I meet?

Science.gov (United States)

2010-07-01

... 40 Protection of Environment 14 2010-07-01 2010-07-01 false What management practice standard must I meet? 63.10390 Section 63.10390 Protection of Environment ENVIRONMENTAL PROTECTION AGENCY....10390 What management practice standard must I meet? You must sterilize full loads of items having a...

On the Use of Safety Certification Practices in Autonomous Field Robot Software Development

DEFF Research Database (Denmark)

Mogensen, Johann Thor Ingibergsson; Schultz, Ulrik Pagh; Kuhrmann, Marco

2015-01-01

reactions or performance in malfunctioning systems, and influence industry regarding software development and project management. However, academia seemingly did not reach the same degree of utilisation of standards. This paper presents the findings from a systematic mapping study in which we study...... the state-of-the-art in developing software for safety-critical software for autonomous field robots. The purpose of the study is to identify practices used for the development of autonomous field robots and how these practices relate to available safety standards. Our findings from reviewing 49 papers show...... on the quest for suitable approaches to develop safety-critical software, awaiting appropriate standards for this support....

Software engineering the current practice

CERN Document Server

Rajlich, Vaclav

2011-01-01

INTRODUCTION History of Software EngineeringSoftware PropertiesOrigins of SoftwareBirth of Software EngineeringThird Paradigm: Iterative ApproachSoftware Life Span ModelsStaged ModelVariants of Staged ModelSoftware Technologies Programming Languages and CompilersObject-Oriented TechnologyVersion Control SystemSoftware ModelsClass DiagramsUML Activity DiagramsClass Dependency Graphs and ContractsSOFTWARE CHANGEIntroduction to Software ChangeCharacteristics of Software ChangePhases of Software ChangeRequirements and Their ElicitationRequirements Analysis and Change InitiationConcepts and Concept

A Generic Software Development Process Refined from Best Practices for Cloud Computing

Directory of Open Access Journals (Sweden)

Soojin Park

2015-04-01

Full Text Available Cloud computing has emerged as more than just a piece of technology, it is rather a new IT paradigm. The philosophy behind cloud computing shares its view with green computing where computing environments and resources are not as subjects to own but as subjects of sustained use. However, converting currently used IT services to Software as a Service (SaaS cloud computing environments introduces several new risks. To mitigate such risks, existing software development processes must undergo significant remodeling. This study analyzes actual cases of SaaS cloud computing environment adoption as a way to derive four new best practices for software development and incorporates the identified best practices for currently-in-use processes. Furthermore, this study presents a design for generic software development processes that implement the proposed best practices. The design for the generic process has been applied to reinforce the weak points found in SaaS cloud service development practices used by eight enterprises currently developing or operating actual SaaS cloud computing services. Lastly, this study evaluates the applicability of the proposed SaaS cloud oriented development process through analyzing the feedback data collected from actual application to the development of a SaaS cloud service Astation.

Student perceptions of drill-and-practice mathematics software in primary education

NARCIS (Netherlands)

Kuiper, E.; de Pater-Sneep, M.

2014-01-01

Drill-and-practice mathematics software offers teachers a relatively simple way to use technology in the classroom. One of the reasons to use the software may be that it motivates children, working on the computer being more "fun" than doing regular school work. However, students’ own perceptions of

[Software for illustrating a cost-quality balance carried out by clinical laboratory practice].

Science.gov (United States)

Nishibori, Masahiro; Asayama, Hitoshi; Kimura, Satoshi; Takagi, Yasushi; Hagihara, Michio; Fujiwara, Mutsunori; Yoneyama, Akiko; Watanabe, Takashi

2010-09-01

We have no proper reference indicating the quality of clinical laboratory practice, which should clearly illustrates that better medical tests require more expenses. Japanese Society of Laboratory Medicine was concerned about recent difficult medical economy and issued a committee report proposing a guideline to evaluate the good laboratory practice. According to the guideline, we developed software that illustrate a cost-quality balance carried out by clinical laboratory practice. We encountered a number of controversial problems, for example, how to measure and weight each quality-related factor, how to calculate costs of a laboratory test and how to consider characteristics of a clinical laboratory. Consequently we finished only prototype software within the given period and the budget. In this paper, software implementation of the guideline and the above-mentioned problems are summarized. Aiming to stimulate these discussions, the operative software will be put on the Society's homepage for trial

Of deadlocks and peopleware-collaborative work practices in global software development

OpenAIRE

Avram, Gabriela

2007-01-01

peer-reviewed As part of a research project dedicated to the Social Organizational and Cultural Aspects of Global Software Development, the author has chosen to focus on collaborative work practices and knowledge management aspects of collaborative work. More precisely, the focus is on how the global distribution of software development affects collaborative work. The current paper is a first attempt to unveil, through a concrete situation observed in a distributed software development ...

Intrafirm knowledge transfer of agile software practices: barriers and their relations

DEFF Research Database (Denmark)

Tordrup Heeager, Lise; Nielsen, Peter Axel

2018-01-01

to knowledge transfer, we modify and extend the framework to transferring knowledge of agile practices. This framework is subsequently applied for interpreting and analyzing the case study data. The analysis shows how these barriers (e.g., the organizational culture, time and resources, knowledge strategy......Agile software practices are widely used in a great variety of organizations, and the shift from traditional plan-driven approaches entails a redefinition of processes in these organizations. Intrafirm knowledge transfer of agile software practices between projects is a key concern...... in this redefinition. While knowledge transfer is essential for an organization to develop or keep its competitive advantage, it is also both difficult and time consuming, due to a wide range of barriers. Transferring knowledge on agile practices is even more complex due to there being a high degree of tacit knowledge...

Implementing Software Defined Radio

CERN Document Server

Grayver, Eugene

2013-01-01

Software Defined Radio makes wireless communications easier, more efficient, and more reliable. This book bridges the gap between academic research and practical implementation. When beginning a project, practicing engineers, technical managers, and graduate students can save countless hours by considering the concepts presented in these pages. The author covers the myriad options and trade-offs available when selecting an appropriate hardware architecture. As demonstrated here, the choice between hardware- and software-centric architecture can mean the difference between meeting an aggressive schedule and bogging down in endless design iterations. Because of the author’s experience overseeing dozens of failed and successful developments, he is able to present many real-life examples. Some of the key concepts covered are: Choosing the right architecture for the market – laboratory, military, or commercial Hardware platforms – FPGAs, GPPs, specialized and hybrid devices Standardization efforts to ens...

Software design practice using two SCADA software packages

DEFF Research Database (Denmark)

Basse, K.P.; Christensen, Georg Kronborg; Frederiksen, P. K.

1996-01-01

Typical software development for manufacturing control is done either by specialists with consideral real-time programming experience or done by the adaptation of standard software packages for manufacturing control. After investigation and test of two commercial software packages: "InTouch" and ......Touch" and "Fix", it is argued, that a more efficient software solution can be achieved by utilising an integrated specification for SCADA and PLC-programming. Experiences gained from process control is planned investigated for descrete parts manufacturing....

What does it mean to use a method? Towards a practice theory for software engineering

DEFF Research Database (Denmark)

Dittrich, Yvonne

2016-01-01

Context Methods and processes, along with the tools to support them, are at the heart of software engineering as a discipline. However, as we all know, that often the use of the same method neither impacts software projects in a comparable manner nor the software they result in. What is lacking...... software development and teaching are indicated. Conclusion The theoretical/philosophical concepts allow the explaining of heterogeneity in application of software engineering methods in line with empirical research results....... is an understanding of how methods affect software development. Objective The article develops a set of concepts based on the practice-concept in philosophy of sociology as a base to describe software development as social practice, and develop an understanding of methods and their application that explains...

78 FR 22890 - National Advisory Council on Nurse Education and Practice; Notice of Meeting

Science.gov (United States)

2013-04-17

... Advisory Council on Nurse Education and Practice; Notice of Meeting In accordance with section 10(a)(2) of... meeting: Name: National Advisory Council on Nurse Education and Practice (NACNEP) Dates and Times: April... the nursing workforce is ready to meet these challenges. The objectives of the meeting are: (1) To...

Evaluation of PMBOK and scrum practices for software development in the vision of specialists

Directory of Open Access Journals (Sweden)

Elton Fernandes Gonçalves

2017-07-01

Full Text Available In project management, the challenge for software development is to achieve success for the proposed projects, using methods such as PMBOK and Scrum. Knowledge of the advantages of these methods are critical success factors for product development. Therefore, the proposal of this study was to verify the perception of specialists of the area of software development on practices of project management. The used methods in this study were the bibliographic, exploratory and qualitative research, with the construction of a questionnaire with 14 items on the advantages of project management practices of various natures, size and complexity, which were applied in 90 specialists. The results of the research demonstrated that all the experts agreed with the advantages of the project management practices, identified based on the literature review, for software development, thus validating the proposed items of the questionnaire. It is recommended for future researches the accomplishment of case studies that explore practical models of evaluation of the use of the practices studied in the scope of software development. It is important in these future studies that metrics and indicators are drawn for each of the advantages cited in the present study.

Testing and Deployment of Software Systems (in practice)

DEFF Research Database (Denmark)

Nyborg, Mads; Høgh, Stig

2014-01-01

. The aim of this paper is to describe: • the unified software development process and compare this with CDIO. • the activities covering the ‘O’ part in software engineering. • the course structure and schedule. • the evaluations and comments received from students. The paper concludes that: It is possible......The CDIO concept is now well integrated into many curricula at universities around the world and it has meant an increase in the quality of engineering education. However, the main focus has been on design-build projects and less on the ‘C’ and ‘O’ part. In particular, the ‘O’ part of CDIO has...... received very little focus, since this is probably the most difficult part to implement in a university environment. Because of this observation, in 2011 we decided to launch a new elective course, ‘Testing and deployment of software systems (in practice)’, focusing entirely on the ‘O’ part in CDIO...

The Dynamics of Agile Practices for Safety-Critical Software Development

DEFF Research Database (Denmark)

Nielsen, Peter Axel; Tordrup Heeager, Lise

2017-01-01

This short paper reports from a case study of the agile development of safety-critical software. It utilizes a framework of dynamic relationships between agile practices with the purpose of demonstrating the utility of the framework to understand a case in its context, and it shows significant...... dynamics. The study is concluded by pointing at which further research on the framework is required to use the framework in managing the agile development of safety-critical software....

78 FR 65342 - National Advisory Council on Nurse Education and Practice; Notice of Meeting

Science.gov (United States)

2013-10-31

... Advisory Council on Nurse Education and Practice; Notice of Meeting In accordance with section 10(a)(2) of... meeting: Name: National Advisory Council on Nurse Education and Practice (NACNEP). Dates and Times.... The objectives of the meeting are: (1) To articulate the key challenges facing nursing workforce...

75 FR 12554 - National Advisory Council on Nurse Education and Practice; Notice of Meeting

Science.gov (United States)

2010-03-16

... Advisory Council on Nurse Education and Practice; Notice of Meeting In accordance with section 10(a)(2) of... meetings: Name: National Advisory Council on Nurse Education and Practice (NACNEP). Dates and Times: April... meeting is to address issues relating to the role of nursing in primary care and implications for...

76 FR 64953 - National Advisory Council on Nurse Education and Practice; Notice of Meeting

Science.gov (United States)

2011-10-19

... Advisory Council on Nurse Education and Practice; Notice of Meeting In accordance with section 10(a)(2) of...: Name: National Advisory Council on Nurse Education and Practice (NACNEP). Dates and Times: November 7... vision and agenda for NACNEP in meeting those challenges. The objectives of the meeting are: (1) To...

Report on the Second Workshop on Sustainable Software for Science: Practice and Experiences (WSSSPE2)

Science.gov (United States)

Katz, Daniel S.; Choi, Sou-Cheng T.; Wilkins-Diehr, Nancy; Chue Hong, Neil; Venters, Colin C.; Howison, James; Seinstra, Frank; Jones, Matthew; Cranston, Karen; Clune, Thomas L.; de Val-Borro, Miguel; Littauer, Richard

2016-02-01

This technical report records and discusses the Second Workshop on Sustainable Software for Science: Practice and Experiences (WSSSPE2). The report includes a description of the alternative, experimental submission and review process, two workshop keynote presentations, a series of lightning talks, a discussion on sustainability, and five discussions from the topic areas of exploring sustainability; software development experiences; credit & incentives; reproducibility & reuse & sharing; and code testing & code review. For each topic, the report includes a list of tangible actions that were proposed and that would lead to potential change. The workshop recognized that reliance on scientific software is pervasive in all areas of world-leading research today. The workshop participants then proceeded to explore different perspectives on the concept of sustainability. Key enablers and barriers of sustainable scientific software were identified from their experiences. In addition, recommendations with new requirements such as software credit files and software prize frameworks were outlined for improving practices in sustainable software engineering. There was also broad consensus that formal training in software development or engineering was rare among the practitioners. Significant strides need to be made in building a sense of community via training in software and technical practices, on increasing their size and scope, and on better integrating them directly into graduate education programs. Finally, journals can define and publish policies to improve reproducibility, whereas reviewers can insist that authors provide sufficient information and access to data and software to allow them reproduce the results in the paper. Hence a list of criteria is compiled for journals to provide to reviewers so as to make it easier to review software submitted for publication as a "Software Paper."

Incorrect results in software engineering experiments: How to improve research practices

OpenAIRE

Jørgensen, Magne; Dybå, Tore; Liestøl, Knut; Sjøberg, Dag

2016-01-01

Context The trustworthiness of research results is a growing concern in many empirical disciplines. Aim The goals of this paper are to assess how much the trustworthiness of results reported in software engineering experiments is affected by researcher and publication bias, given typical statistical power and significance levels, and to suggest improved research practices. Method First, we conducted a small-scale survey to document the presence of researcher and publication biases in software...

Report on the Second Workshop on Sustainable Software for Science: Practice and Experiences (WSSSPE2

Directory of Open Access Journals (Sweden)

Daniel S. Katz

2016-02-01

Full Text Available This technical report records and discusses the Second Workshop on Sustainable Software for Science: Practice and Experiences (WSSSPE2. The report includes a description of the alternative, experimental submission and review process, two workshop keynote presentations, a series of lightning talks, a discussion on sustainability, and five discussions from the topic areas of exploring sustainability; software development experiences; credit & incentives; reproducibility & reuse & sharing; and code testing & code review. For each topic, the report includes a list of tangible actions that were proposed and that would lead to potential change. The workshop recognized that reliance on scientific software is pervasive in all areas of world-leading research today. The workshop participants then proceeded to explore different perspectives on the concept of sustainability. Key enablers and barriers of sustainable scientific software were identified from their experiences. In addition, recommendations with new requirements such as software credit files and software prize frameworks were outlined for improving practices in sustainable software engineering. There was also broad consensus that formal training in software development or engineering was rare among the practitioners. Significant strides need to be made in building a sense of community via training in software and technical practices, on increasing their size and scope, and on better integrating them directly into graduate education programs. Finally, journals can define and publish policies to improve reproducibility, whereas reviewers can insist that authors provide sufficient information and access to data and software to allow them reproduce the results in the paper. Hence a list of criteria is compiled for journals to provide to reviewers so as to make it easier to review software submitted for publication as a “Software Paper.” 

A systematic review of knowledge sharing challenges and practices in global software development

DEFF Research Database (Denmark)

Zahedi, Mansooreh; Shahin, Mojtaba; Babar, Muhammad Ali

2016-01-01

the data extracted from the reviewed primary studies. Results: Our findings revealed that knowledge sharing challenges and practices in GSD could be classi- fied in 6 main themes: management, team structure, work processes/practices, team cognition, social attributes and technology. In regard to contextual......Context: Global Software Development (GSD) presents significant challenges to share and understand knowledge required for developing software. Organizations are expected to implement appropriate practices to address knowledge-sharing challenges in GSD. With the growing literature on GSD and its...... and practices fall under the theme of “work practices”. (c) The technology related knowledge-sharing challenges are the least reported; we discussed the available technologies for sup- porting knowledge sharing needs in GSD. (d) The organizational contextual information is missing from a large number of studies...

Ignoring "Best Practice": Why Irish Software SMEs are Rejecting CMMI and ISO 9000

Directory of Open Access Journals (Sweden)

Rory V. O’Connor

2009-08-01

Full Text Available Software Process Improvement (SPI "best practice" models such as ISO 9000 and the Capability Maturity Model Integrated (CMMI have been developed to assist software development organisations by harnessing their experience and providing them with support so that they can produce software products on time, within budget and to a high level of quality. However there is increasing evidence that these models are not being adopted by Small and Medium sized Enterprises (SMEs and primarily remain the remit of large organisations. This paper presents the results of a Grounded Theory study into why Irish SME software product companies are not using these SPI models. The key inhibiting factor found was the issue of cost. We discuss the findings in relation to cost of process and the factors affecting it, including bureaucracy, documentation, communication, tacit knowledge and organisational creativity and flexibility, and the associated impact on the adoption of SPI best practice models.

Designing SCADA application software a practical approach

CERN Document Server

McCrady, Stuart G

2013-01-01

Automation systems, often referred to as SCADA systems, involve programming at several levels; these systems include computer type field controllers that monitor and control plant equipment such as conveyor systems, pumps, and user workstations that allow the user to monitor and control the equipment through color graphic displays. All of the components of these systems are integrated through a network, such as Ethernet for fast communications. This book provides a practical guide to developing the application software for all aspects of the automation system, from the field controll

SOFTWARE TRAINING AIDS DEVELOPMENT AND IMPLEMENTATION IN PROFESSIONAL PREPARATION PRACTICE OF TECHNOLOGICAL EDUCATION TEACHER

Directory of Open Access Journals (Sweden)

Anatoliy G. Gritchenko

2013-03-01

Full Text Available The article outlines the theoretical and practical aspects of software training aids development and implementation in professional preparation practice of technological education teacher. The myriad opportunities of new information technologies are described; the characteristic features of modern software training tool (STT are revealed; the main algorithmic structure circuits of training programs construction (linear, cyclic, with hyperlinks, to the labels, which enable the development of STT variety and functionality are given; the methodology of STT creating is described based on the analysis of the technology teacher preparation in HEE content, MITE didactic functions and selection criteria of educational software for this area of specialist’s preparation.

Earth Science Informatics Community Requirements for Improving Sustainable Science Software Practices: User Perspectives and Implications for Organizational Action

Science.gov (United States)

Downs, R. R.; Lenhardt, W. C.; Robinson, E.

2014-12-01

Science software is integral to the scientific process and must be developed and managed in a sustainable manner to ensure future access to scientific data and related resources. Organizations that are part of the scientific enterprise, as well as members of the scientific community who work within these entities, can contribute to the sustainability of science software and to practices that improve scientific community capabilities for science software sustainability. As science becomes increasingly digital and therefore, dependent on software, improving community practices for sustainable science software will contribute to the sustainability of science. Members of the Earth science informatics community, including scientific data producers and distributers, end-user scientists, system and application developers, and data center managers, use science software regularly and face the challenges and the opportunities that science software presents for the sustainability of science. To gain insight on practices needed for the sustainability of science software from the science software experiences of the Earth science informatics community, an interdisciplinary group of 300 community members were asked to engage in simultaneous roundtable discussions and report on their answers to questions about the requirements for improving scientific software sustainability. This paper will present an analysis of the issues reported and the conclusions offered by the participants. These results provide perspectives for science software sustainability practices and have implications for actions that organizations and their leadership can initiate to improve the sustainability of science software.

Ignoring 'Best Practice': why Irish software SMEs are rejecting CMMI and ISO 9000

OpenAIRE

O'Connor, Rory V.; Coleman, Gerry

2009-01-01

peer-reviewed Software Process Improvement (SPI) "best practice" models such as ISO 9000 and the Capability Maturity Model Integrated (CMMI) have been developed to assist software development organisations by harnessing their experience and providing them with support so that they can produce software products on time, within budget and to a high level of quality. However there is increasing evidence that these models are not being adopted by Small and Medium sized Enterprises ...

Software engineering design theory and practice

CERN Document Server

Otero, Carlos

2012-01-01

… intended for use as a textbook for an advanced course in software design. Each chapter ends with review questions and references. … provides an overview of the software development process, something that would not be out of line in a course on software engineering including such topics as software process, software management, balancing conflicting values of stakeholders, testing, quality, and ethics. The author has principally focused on software design though, extracting the design phase from the surrounding software development lifecycle. … Software design strategies are addressed

Conceptual process models and quantitative analysis of classification problems in Scrum software development practices

NARCIS (Netherlands)

Helwerda, L.S.; Niessink, F.; Verbeek, F.J.

2017-01-01

We propose a novel classification method that integrates into existing agile software development practices by collecting data records generated by software and tools used in the development process. We extract features from the collected data and create visualizations that provide insights,

When constructions of the future meet curriculum development and teaching practice

DEFF Research Database (Denmark)

Rasmussen, Jens

in direction of still better learning outcomes, personal development and Bildung. On the other hand the educational system’s environment such as for example the economic system, the political system or other parts of the educational system requires outcomes that meet the needs of these systems as well...... and teaching practices that are especially suited to promote such selected constructs. How are these efforts met by curriculum development and how are they met by classroom practitioners? What happens when the constructions of future meets curriculum development and teaching practice?...

Global Software Engineering: A Software Process Approach

Science.gov (United States)

Richardson, Ita; Casey, Valentine; Burton, John; McCaffery, Fergal

Our research has shown that many companies are struggling with the successful implementation of global software engineering, due to temporal, cultural and geographical distance, which causes a range of factors to come into play. For example, cultural, project managementproject management and communication difficulties continually cause problems for software engineers and project managers. While the implementation of efficient software processes can be used to improve the quality of the software product, published software process models do not cater explicitly for the recent growth in global software engineering. Our thesis is that global software engineering factors should be included in software process models to ensure their continued usefulness in global organisations. Based on extensive global software engineering research, we have developed a software process, Global Teaming, which includes specific practices and sub-practices. The purpose is to ensure that requirements for successful global software engineering are stipulated so that organisations can ensure successful implementation of global software engineering.

Software engineering turning theory into practice

CERN Document Server

Jones, Robert

1996-01-01

The term 'Software Engineering' was coined in the mid 1960s, it is said, as a challenge to the software community to start rationalising the software production process. Software engineering is a very young discipline and this challenge still eludes LHC demands software production on a scale far beyond that previously addressed in HEP and we are relying on software engineering to allow a significant number of people address this problem collectively. This series of lectures presents the basics of software engineering from the developer's point of view. The aim is to show how individual developers can improve the quality of the software they produce while avoiding the conflict between the creative process of designing software and the organisational needs of large projects.The Laser Interferometer Gravitanional Wave Observatory (LIGO) is being constructed with a goal to detect these waves and then to use them as a new tool to explore and study The sources of gravitanional waves and techniques for detection wil...

A software engineering process for safety-critical software application

International Nuclear Information System (INIS)

Kang, Byung Heon; Kim, Hang Bae; Chang, Hoon Seon; Jeon, Jong Sun

1995-01-01

Application of computer software to safety-critical systems in on the increase. To be successful, the software must be designed and constructed to meet the functional and performance requirements of the system. For safety reason, the software must be demonstrated not only to meet these requirements, but also to operate safely as a component within the system. For longer-term cost consideration, the software must be designed and structured to ease future maintenance and modifications. This paper presents a software engineering process for the production of safety-critical software for a nuclear power plant. The presentation is expository in nature of a viable high quality safety-critical software development. It is based on the ideas of a rational design process and on the experience of the adaptation of such process in the production of the safety-critical software for the shutdown system number two of Wolsung 2, 3 and 4 nuclear power generation plants. This process is significantly different from a conventional process in terms of rigorous software development phases and software design techniques, The process covers documentation, design, verification and testing using mathematically precise notations and highly reviewable tabular format to specify software requirements and software requirements and software requirements and code against software design using static analysis. The software engineering process described in this paper applies the principle of information-hiding decomposition in software design using a modular design technique so that when a change is required or an error is detected, the affected scope can be readily and confidently located. it also facilitates a sense of high degree of confidence in the 'correctness' of the software production, and provides a relatively simple and straightforward code implementation effort. 1 figs., 10 refs. (Author)

A new practice-driven approach to develop software in a cyber-physical system environment

Science.gov (United States)

Jiang, Yiping; Chen, C. L. Philip; Duan, Junwei

2016-02-01

Cyber-physical system (CPS) is an emerging area, which cannot work efficiently without proper software handling of the data and business logic. Software and middleware is the soul of the CPS. The software development of CPS is a critical issue because of its complicity in a large scale realistic system. Furthermore, object-oriented approach (OOA) is often used to develop CPS software, which needs some improvements according to the characteristics of CPS. To develop software in a CPS environment, a new systematic approach is proposed in this paper. It comes from practice, and has been evolved from software companies. It consists of (A) Requirement analysis in event-oriented way, (B) architecture design in data-oriented way, (C) detailed design and coding in object-oriented way and (D) testing in event-oriented way. It is a new approach based on OOA; the difference when compared with OOA is that the proposed approach has different emphases and measures in every stage. It is more accord with the characteristics of event-driven CPS. In CPS software development, one should focus on the events more than the functions or objects. A case study of a smart home system is designed to reveal the effectiveness of the approach. It shows that the approach is also easy to be operated in the practice owing to some simplifications. The running result illustrates the validity of this approach.

78 FR 2275 - National Advisory Council on Nurse Education and Practice; Notice of Meeting

Science.gov (United States)

2013-01-10

... Advisory Council on Nurse Education and Practice; Notice of Meeting In accordance with section 10(a)(2) of...: Name: National Advisory Council on Nurse Education and Practice (NACNEP). Dates and Times: January 31... the Secretary to ensure the nursing workforce is ready to meet these challenges. The objectives of the...

Best practices for International eSourcing of Software Products and Services

OpenAIRE

Käkölä, Timo

2008-01-01

This paper analyzes how the information and communications technology-supported international eSourcing of software products and services (IeS) can be effectively executed. The extant literature falls short of providing a systematic and detailed enough set of best practices to guide IeS. This paper presents best practices for IeS to facilitate further research, and to help managers and other stakeholders to understand, execute, and proactively improve and manage international eSourcing. The p...

Reproducibility and Practical Adoption of GEOBIA with Open-Source Software in Docker Containers

Directory of Open Access Journals (Sweden)

Christian Knoth

2017-03-01

Full Text Available Geographic Object-Based Image Analysis (GEOBIA mostly uses proprietary software,but the interest in Free and Open-Source Software (FOSS for GEOBIA is growing. This interest stems not only from cost savings, but also from benefits concerning reproducibility and collaboration. Technical challenges hamper practical reproducibility, especially when multiple software packages are required to conduct an analysis. In this study, we use containerization to package a GEOBIA workflow in a well-defined FOSS environment. We explore the approach using two software stacks to perform an exemplary analysis detecting destruction of buildings in bi-temporal images of a conflict area. The analysis combines feature extraction techniques with segmentation and object-based analysis to detect changes using automatically-defined local reference values and to distinguish disappeared buildings from non-target structures. The resulting workflow is published as FOSS comprising both the model and data in a ready to use Docker image and a user interface for interaction with the containerized workflow. The presented solution advances GEOBIA in the following aspects: higher transparency of methodology; easier reuse and adaption of workflows; better transferability between operating systems; complete description of the software environment; and easy application of workflows by image analysis experts and non-experts. As a result, it promotes not only the reproducibility of GEOBIA, but also its practical adoption.

Ethics and Practice of Free Software

CERN Document Server

CERN. Geneva

2007-01-01

About the speaker Richard Matthew Stallman is a software freedom activist, hacker, and software developer. In September 1983, he launched the GNU Project to create a free Unix-like operating system, and has been the project's lead architect and organizer. With the launch of the GNU project he started the free software movement, and in October 1985 set up the Free Software Foundation. He co-founded the League for Programming Freedom. Stallman pioneered the concept of copyleft and is the main author of several copyleft licenses including the GNU General Public License, the most widely used free software license. (from Wikipedia)

Investigation of the current requirements engineering practices among software developers at the Universiti Utara Malaysia Information Technology (UUMIT) centre

Science.gov (United States)

Hussain, Azham; Mkpojiogu, Emmanuel O. C.; Abdullah, Inam

2016-08-01

Requirements Engineering (RE) is a systemic and integrated process of eliciting, elaborating, negotiating, validating and managing of the requirements of a system in a software development project. UUM has been supported by various systems developed and maintained by the UUM Information Technology (UUMIT) Centre. The aim of this study was to assess the current requirements engineering practices at UUMIT. The main problem that prompted this research is the lack of studies that support software development activities at the UUMIT. The study is geared at helping UUMIT produce quality but time and cost saving software products by implementing cutting edge and state of the art requirements engineering practices. Also, the study contributes to UUM by identifying the activities needed for software development so that the management will be able to allocate budget to provide adequate and precise training for the software developers. Three variables were investigated: Requirement Description, Requirements Development (comprising: Requirements Elicitation, Requirements Analysis and Negotiation, Requirements Validation), and Requirement Management. The results from the study showed that the current practice of requirement engineering in UUMIT is encouraging, but still need further development and improvement because a few RE practices were seldom practiced.

SOFTWARE QUALITY ASSURANCE FOR EMERGENCY RESPONSE CONSEQUENCE ASSESSMENT MODELS AT DOE'S SAVANNAH RIVER SITE

International Nuclear Information System (INIS)

Hunter, C

2007-01-01

The Savannah River National Laboratory's (SRNL) Atmospheric Technologies Group develops, maintains, and operates computer-based software applications for use in emergency response consequence assessment at DOE's Savannah River Site. These applications range from straightforward, stand-alone Gaussian dispersion models run with simple meteorological input to complex computational software systems with supporting scripts that simulate highly dynamic atmospheric processes. A software quality assurance program has been developed to ensure appropriate lifecycle management of these software applications. This program was designed to meet fully the overall structure and intent of SRNL's institutional software QA programs, yet remain sufficiently practical to achieve the necessary level of control in a cost-effective manner. A general overview of this program is described

Testing digital safety system software with a testability measure based on a software fault tree

International Nuclear Information System (INIS)

Sohn, Se Do; Hyun Seong, Poong

2006-01-01

Using predeveloped software, a digital safety system is designed that meets the quality standards of a safety system. To demonstrate the quality, the design process and operating history of the product are reviewed along with configuration management practices. The application software of the safety system is developed in accordance with the planned life cycle. Testing, which is a major phase that takes a significant time in the overall life cycle, can be optimized if the testability of the software can be evaluated. The proposed testability measure of the software is based on the entropy of the importance of basic statements and the failure probability from a software fault tree. To calculate testability, a fault tree is used in the analysis of a source code. With a quantitative measure of testability, testing can be optimized. The proposed testability can also be used to demonstrate whether the test cases based on uniform partitions, such as branch coverage criteria, result in homogeneous partitions that is known to be more effective than random testing. In this paper, the testability measure is calculated for the modules of a nuclear power plant's safety software. The module testing with branch coverage criteria required fewer test cases if the module has higher testability. The result shows that the testability measure can be used to evaluate whether partitions have homogeneous characteristics

The Diverse Worlds and Research Practices of Qualitative Software

Directory of Open Access Journals (Sweden)

Nigel Fielding

2012-05-01

Full Text Available The article considers the way that digital research technologies and online environments increasingly support new forms of qualitative research that have emerged as a result of new user groups taking up the practice of social research. New practitioners of qualitative research have entered the field from societies where qualitative research is a newly-established practice, and new cadres of "citizen researchers" have turned to qualitative methods for non-academic purposes. These groups challenge accepted understandings of qualitative methods. The article uses the example of qualitative software as a case study of how qualitative research is enabled by new digital tools that help new user groups extend the application of qualitative research methods. URN: http://nbn-resolving.de/urn:nbn:de:0114-fqs1202124

Software Acquisition and Software Engineering Best Practices

National Research Council Canada - National Science Library

Eslinger, S

1999-01-01

The purpose of this white paper is to address the issues raised in the recently published Senate Armed Services Committee Report 106-50 concerning Software Management Improvements for the Department of Defense (DoD...

Summary of the First Workshop on Sustainable Software for Science: Practice and Experiences (WSSSPE1

Directory of Open Access Journals (Sweden)

Daniel S Katz

2014-07-01

Full Text Available Challenges related to development, deployment, and maintenance of reusable software for science are becoming a growing concern. Many scientists’ research increasingly depends on the quality and availability of software upon which their works are built. To highlight some of these issues and share experiences, the First Workshop on Sustainable Software for Science: Practice and Experiences (WSSSPE1 was held in November 2013 in conjunction with the SC13 Conference. The workshop featured keynote presentations and a large number (54 of solicited extended abstracts that were grouped into three themes and presented via panels. A set of collaborative notes of the presentations and discussion was taken during the workshop. Unique perspectives were captured about issues such as comprehensive documentation, development and deployment practices, software licenses and career paths for developers. Attribution systems that account for evidence of software contribution and impact were also discussed. These include mechanisms such as Digital Object Identifiers, publication of “software papers”, and the use of online systems, for example source code repositories like GitHub. This paper summarizes the issues and shared experiences that were discussed, including cross-cutting issues and use cases. It joins a nascent literature seeking to understand what drives software work in science, and how it is impacted by the reward systems of science. These incentives can determine the extent to which developers are motivated to build software for the long-term, for the use of others, and whether to work collaboratively or separately. It also explores community building, leadership, and dynamics in relation to successful scientific software.

Implementation of Software Configuration Management Process by Models: Practical Experiments and Learned Lessons

Directory of Open Access Journals (Sweden)

Bartusevics Arturs

2014-12-01

Full Text Available Nowadays software configuration management process is not only dilemma which system should be used for version control or how to merge changes from one source code branch to other. There are multiple tasks such as version control, build management, deploy management, status accounting, bug tracking and many others that should be solved to support full configuration management process according to most popular quality standards. The main scope of the mentioned process is to include only valid and tested software items to final version of product and prepare a new version as soon as possible. To implement different tasks of software configuration management process, a set of different tools, scripts and utilities should be used. The current paper provides a new model-based approach to implementation of configuration management. Using different models, a new approach helps to organize existing solutions and develop new ones by a parameterized way, thus increasing reuse of solutions. The study provides a general description of new model-based conception and definitions of all models needed to implement a new approach. The second part of the paper contains an overview of criteria, practical experiments and lessons learned from using new models in software configuration management. Finally, further works are defined based on results of practical experiments and lessons learned.

Software engineering architecture-driven software development

CERN Document Server

Schmidt, Richard F

2013-01-01

Software Engineering: Architecture-driven Software Development is the first comprehensive guide to the underlying skills embodied in the IEEE's Software Engineering Body of Knowledge (SWEBOK) standard. Standards expert Richard Schmidt explains the traditional software engineering practices recognized for developing projects for government or corporate systems. Software engineering education often lacks standardization, with many institutions focusing on implementation rather than design as it impacts product architecture. Many graduates join the workforce with incomplete skil

Evaluation of features to support safety and quality in general practice clinical software

Science.gov (United States)

2011-01-01

Background Electronic prescribing is now the norm in many countries. We wished to find out if clinical software systems used by general practitioners in Australia include features (functional capabilities and other characteristics) that facilitate improved patient safety and care, with a focus on quality use of medicines. Methods Seven clinical software systems used in general practice were evaluated. Fifty software features that were previously rated as likely to have a high impact on safety and/or quality of care in general practice were tested and are reported here. Results The range of results for the implementation of 50 features across the 7 clinical software systems was as follows: 17-31 features (34-62%) were fully implemented, 9-13 (18-26%) partially implemented, and 9-20 (18-40%) not implemented. Key findings included: Access to evidence based drug and therapeutic information was limited. Decision support for prescribing was available but varied markedly between systems. During prescribing there was potential for medicine mis-selection in some systems, and linking a medicine with its indication was optional. The definition of 'current medicines' versus 'past medicines' was not always clear. There were limited resources for patients, and some medicines lists for patients were suboptimal. Results were provided to the software vendors, who were keen to improve their systems. Conclusions The clinical systems tested lack some of the features expected to support patient safety and quality of care. Standards and certification for clinical software would ensure that safety features are present and that there is a minimum level of clinical functionality that clinicians could expect to find in any system.

78 FR 12068 - Device Good Manufacturing Practice Advisory Committee; Notice of Meeting

Science.gov (United States)

2013-02-21

... DEPARTMENT OF HEALTH AND HUMAN SERVICES Food and Drug Administration [Docket No. FDA-2013-N-0001] Device Good Manufacturing Practice Advisory Committee; Notice of Meeting AGENCY: Food and Drug... Committee: Device Good Manufacturing Practice Advisory Committee. General Function of the Committee: To...

Software for nuclear spectrometry

International Nuclear Information System (INIS)

1998-10-01

The Advisory Group Meeting (AGM) on Software for Nuclear Spectrometry was dedicated to review the present status of software for nuclear spectrometry and to advise on future activities in this field. Because similar AGM and consultant's meetings had been held in the past; together with an attempt to get more streamlined, this AGM was devoted to the specific field of software for gamma ray spectrometry. Nevertheless, many of the issues discussed and the recommendations made are of general concern for any software on nuclear spectrometry. The report is organized by sections. The 'Summary' gives conclusions and recommendations adopted at the AGM. These conclusions and recommendations resulted from the discussions held during and after presentations of the scientific and technical papers. These papers are reported here in their integral form in the following Sections

Managing the Testing Process Practical Tools and Techniques for Managing Hardware and Software Testing

CERN Document Server

Black, Rex

2011-01-01

New edition of one of the most influential books on managing software and hardware testing In this new edition of his top-selling book, Rex Black walks you through the steps necessary to manage rigorous testing programs of hardware and software. The preeminent expert in his field, Mr. Black draws upon years of experience as president of both the International and American Software Testing Qualifications boards to offer this extensive resource of all the standards, methods, and tools you'll need. The book covers core testing concepts and thoroughly examines the best test management practices

NASA's Software Safety Standard

Science.gov (United States)

Ramsay, Christopher M.

2007-01-01

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.

Improving Software Engineering on NASA Projects

Science.gov (United States)

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.

Theory and Practice Meets in Industrial Process Design -Educational Perspective-

Science.gov (United States)

Aramo-Immonen, Heli; Toikka, Tarja

Software engineer should see himself as a business process designer in enterprise resource planning system (ERP) re-engineering project. Software engineers and managers should have design dialogue. The objective of this paper is to discuss the motives to study the design research in connection of management education in order to envision and understand the soft human issues in the management context. Second goal is to develop means of practicing social skills between designers and managers. This article explores the affective components of design thinking in industrial management domain. In the conceptual part of this paper are discussed concepts of network and project economy, creativity, communication, use of metaphors, and design thinking. Finally is introduced empirical research plan and first empirical results from design method experiments among the multi-disciplined groups of the master-level students of industrial engineering and management and software engineering.

A survey of quality assurance practices in biomedical open source software projects.

Science.gov (United States)

Koru, Günes; El Emam, Khaled; Neisa, Angelica; Umarji, Medha

2007-05-07

Open source (OS) software is continuously gaining recognition and use in the biomedical domain, for example, in health informatics and bioinformatics. Given the mission critical nature of applications in this domain and their potential impact on patient safety, it is important to understand to what degree and how effectively biomedical OS developers perform standard quality assurance (QA) activities such as peer reviews and testing. This would allow the users of biomedical OS software to better understand the quality risks, if any, and the developers to identify process improvement opportunities to produce higher quality software. A survey of developers working on biomedical OS projects was conducted to examine the QA activities that are performed. We took a descriptive approach to summarize the implementation of QA activities and then examined some of the factors that may be related to the implementation of such practices. Our descriptive results show that 63% (95% CI, 54-72) of projects did not include peer reviews in their development process, while 82% (95% CI, 75-89) did include testing. Approximately 74% (95% CI, 67-81) of developers did not have a background in computing, 80% (95% CI, 74-87) were paid for their contributions to the project, and 52% (95% CI, 43-60) had PhDs. A multivariate logistic regression model to predict the implementation of peer reviews was not significant (likelihood ratio test = 16.86, 9 df, P = .051) and neither was a model to predict the implementation of testing (likelihood ratio test = 3.34, 9 df, P = .95). Less attention is paid to peer review than testing. However, the former is a complementary, and necessary, QA practice rather than an alternative. Therefore, one can argue that there are quality risks, at least at this point in time, in transitioning biomedical OS software into any critical settings that may have operational, financial, or safety implications. Developers of biomedical OS applications should invest more effort

Usability Evaluation Method for Agile Software Development

Directory of Open Access Journals (Sweden)

Saad Masood Butt

2015-02-01

Full Text Available Agile methods are the best fit for tremendously growing software industry due to its flexible and dynamic nature. But the software developed using agile methods do meet the usability standards? To answer this question we can see that majority of agile software development projects currently involve interactive user interface designs, which can only be possible by following User Centered Design (UCD in agile methods. The question here is, how to integrate UCD with agile models. Both Agile models and UCD are iterative in nature but agile models focus on coding and development of software; whereas, UCD focuses on user interface of the software. Similarly, both of them have testing features where the agile model involves automated tested code while UCD involves an expert or a user to test the user interface. In this paper, a new agile usability model is proposed and the evaluation is of the proposed model is presented by practically implementing it in three real life projects. . Key results from these projects clearly show: the proposed agile model incorporates usability evaluation methods, improves the relationship between usability experts to work with agile software experts; in addition, allows agile developers to incorporate the result from UCD into subsequent interactions.

Software vulnerability: Definition, modelling, and practical evaluation for E-mail: transfer software

International Nuclear Information System (INIS)

Kimura, Mitsuhiro

2006-01-01

This paper proposes a method of assessing software vulnerability quantitatively. By expanding the concept of the IPO (input-program-output) model, we first define the software vulnerability and construct a stochastic model. Then we evaluate the software vulnerability of the sendmail system by analyzing the actual security-hole data, which were collected from its release note. Also we show the relationship between the estimated software reliability and vulnerability of the analyzed system

Design of Embedded Real-time Systems: Developing a Method for Practical Software Engineering

DEFF Research Database (Denmark)

Løvengreen, Hans Henrik; Ravn, Anders P.; Rischel, Hans

1990-01-01

The methodological issues and practical problems in development and industrial use of a theory-based design method for embedded, real-time systems are discussed. The method has been used for several years in a number of smaller industries that develop both electronics and software for a professio......The methodological issues and practical problems in development and industrial use of a theory-based design method for embedded, real-time systems are discussed. The method has been used for several years in a number of smaller industries that develop both electronics and software...... for a professional market. The design is expressed in a notation for communicating sequential processes, while data types and operations are expressed in a notation built on mathematical set theory. The authors present an order in which to use the notations, a technique for deriving states and operations...

eXascale PRogramming Environment and System Software (XPRESS)

Energy Technology Data Exchange (ETDEWEB)

Chapman, Barbara [Univ. of Houston, TX (United States); Gabriel, Edgar [Univ. of Houston, TX (United States)

2015-11-30

Exascale systems, with a thousand times the compute capacity of today’s leading edge petascale computers, are expected to emerge during the next decade. Their software systems will need to facilitate the exploitation of exceptional amounts of concurrency in applications, and ensure that jobs continue to run despite the occurrence of system failures and other kinds of hard and soft errors. Adapting computations at runtime to cope with changes in the execution environment, as well as to improve power and performance characteristics, is likely to become the norm. As a result, considerable innovation is required to develop system support to meet the needs of future computing platforms. The XPRESS project aims to develop and prototype a revolutionary software system for extreme-­scale computing for both exascale and strong­scaled problems. The XPRESS collaborative research project will advance the state-­of-­the-­art in high performance computing and enable exascale computing for current and future DOE mission-­critical applications and supporting systems. The goals of the XPRESS research project are to: A. enable exascale performance capability for DOE applications, both current and future, B. develop and deliver a practical computing system software X-­stack, OpenX, for future practical DOE exascale computing systems, and C. provide programming methods and environments for effective means of expressing application and system software for portable exascale system execution.

Examining software complexity and quality for scientific software

International Nuclear Information System (INIS)

Kelly, D.; Shepard, T.

2005-01-01

Research has not found a simple relationship between software complexity and software quality, and particularly no relationship between commonly used software complexity metrics and the occurrence of software faults. A study with an example of scientific software from the nuclear power industry illustrates the importance of addressing cognitive complexity, the complexity related to understanding the intellectual content of the software. Simple practices such as aptly-named variables contributes more to high quality software than limiting code sizes. This paper examines the research into complexity and quality and reports on a longitudinal study using the example of nuclear software. (author)

Selecting the Right Software.

Science.gov (United States)

Shearn, Joseph

1987-01-01

Selection of administrative software requires analyzing present needs and, to meet future needs, choosing software that will function with a more powerful computer system. Other important factors to include are a professional system demonstration, maintenance and training, and financial considerations that allow leasing or renting alternatives.…

77 FR 70466 - Meeting of the Judicial Conference Committee on Rules of Practice and Procedure

Science.gov (United States)

2012-11-26

... Procedure. ACTION: Notice of open meeting. SUMMARY: The Committee on Rules of Practice and Procedure will hold a two-day meeting. The meeting will be open to public observation but not participation. DATE: January 3-4, 2013. TIME: 8:30 a.m. to 5:00 p.m. ADDRESSES: The Charles Hotel, Harvard Square, One Bennett...

Software quality assurance

CERN Document Server

Laporte, Claude Y

2018-01-01

This book introduces Software Quality Assurance (SQA) and provides an overview of standards used to implement SQA. It defines ways to assess the effectiveness of how one approaches software quality across key industry sectors such as telecommunications, transport, defense, and aerospace. * Includes supplementary website with an instructor's guide and solutions * Applies IEEE software standards as well as the Capability Maturity Model Integration for Development (CMMI) * Illustrates the application of software quality assurance practices through the use of practical examples, quotes from experts, and tips from the authors

Inside a VAMDC data node—putting standards into practical software

Science.gov (United States)

Regandell, Samuel; Marquart, Thomas; Piskunov, Nikolai

2018-03-01

Access to molecular and atomic data is critical for many forms of remote sensing analysis across different fields. Many atomic and molecular databases are however highly specialised for their intended application, complicating querying and combination data between sources. The Virtual Atomic and Molecular Data Centre, VAMDC, is an electronic infrastructure that allows each database to register as a ‘node’. Through services such as VAMDC’s portal website, users can then access and query all nodes in a homogenised way. Today all major Atomic and Molecular databases are attached to VAMDC This article describes the software tools we developed to help data providers create and manage a VAMDC node. It gives an overview of the VAMDC infrastructure and of the various standards it uses. The article then discusses the development choices made and how the standards are implemented in practice. It concludes with a full example of implementing a VAMDC node using a real-life case as well as future plans for the node software.

Report on the Third Workshop on Sustainable Software for Science: Practice and Experiences (WSSSPE3

Directory of Open Access Journals (Sweden)

Daniel S. Katz

2016-10-01

Full Text Available This report records and discusses the Third Workshop on Sustainable Software for Science: Practice and Experiences (WSSSPE3. The report includes a description of the keynote presentation of the workshop, which served as an overview of sustainable scientific software. It also summarizes a set of lightning talks in which speakers highlighted to-the-point lessons and challenges pertaining to sustaining scientific software. The final and main contribution of the report is a summary of the discussions, future steps, and future organization for a set of self-organized working groups on topics including developing pathways to funding scientific software; constructing useful common metrics for crediting software stakeholders; identifying principles for sustainable software engineering design; reaching out to research software organizations around the world; and building communities for software sustainability. For each group, we include a point of contact and a landing page that can be used by those who want to join that group’s future activities. The main challenge left by the workshop is to see if the groups will execute these activities that they have scheduled, and how the WSSSPE community can encourage this to happen.

Report on the Third Workshop on Sustainable Software for Science: Practice and Experiences (WSSSPE3)

Science.gov (United States)

Katz, Daniel S.; Choi, Sou-Cheng T.; Niemeyer, Kyle E.; Hetherington, James; Löffler, Frank; Gunter, Dan; Idaszak, Ray; Brandt, Steven R.; Miller, Mark A.; Gesing, Sandra; Jones, Nick D.; Weber, Nic; Marru, Suresh; Allen, Gabrielle; Penzenstadler, Birgit; Venters, Colin C.; Davis, Ethan; Hwang, Lorraine; Todorov, Ilian; Patra, Abani; de Val-Borro, Miguel

2016-02-01

This report records and discusses the Third Workshop on Sustainable Software for Science: Practice and Experiences (WSSSPE3). The report includes a description of the keynote presentation of the workshop, which served as an overview of sustainable scientific software. It also summarizes a set of lightning talks in which speakers highlighted to-the-point lessons and challenges pertaining to sustaining scientific software. The final and main contribution of the report is a summary of the discussions, future steps, and future organization for a set of self-organized working groups on topics including developing pathways to funding scientific software; constructing useful common metrics for crediting software stakeholders; identifying principles for sustainable software engineering design; reaching out to research software organizations around the world; and building communities for software sustainability. For each group, we include a point of contact and a landing page that can be used by those who want to join that group's future activities. The main challenge left by the workshop is to see if the groups will execute these activities that they have scheduled, and how the WSSSPE community can encourage this to happen.

Light Duty Utility Arm Software Test Plan

International Nuclear Information System (INIS)

Kiebel, G.R.

1995-01-01

This plan describes how validation testing of the software will be implemented for the integrated control and data acquisition system of the Light Duty Utility Arm System (LDUA). The purpose of LDUA software validation testing is to demonstrate and document that the LDUA software meets its software requirements specification

Software for people fundamentals, trends and best practices

CERN Document Server

Maedche, Alexander; Neer, Ludwig

2012-01-01

The highly competitive and globalized software market is creating pressure on software companies. Given the current boundary conditions, it is critical to continuously increase time-to-market and reduce development costs. In parallel, driven by private life experiences with mobile computing devices, the World Wide Web and software-based services, people, general expectations with regards to software are growing. They expect software that is simple and joyful to use. In the light of the changes that have taken place in recent years, software companies need to fundamentally reconsider the way th

Software engineering

CERN Document Server

Sommerville, Ian

2010-01-01

The ninth edition of Software Engineering presents a broad perspective of software engineering, focusing on the processes and techniques fundamental to the creation of reliable, software systems. Increased coverage of agile methods and software reuse, along with coverage of 'traditional' plan-driven software engineering, gives readers the most up-to-date view of the field currently available. Practical case studies, a full set of easy-to-access supplements, and extensive web resources make teaching the course easier than ever.

Software: University Courses versus Workplace Practice

Science.gov (United States)

Liebenberg, Janet; Huisman, Magda; Mentz, Elsa

2015-01-01

There is a shortage of software developers with the right skills and knowledge, not only in South Africa but worldwide. Despite reports of gap between industry needs and software education, the gap has mostly been explored in developed countries and in quantitative studies. This paper reports on a mixed methods study of the perceptions of…

An empirical evaluation of software quality assurance practices and challenges in a developing country: a comparison of Nigeria and Turkey.

Science.gov (United States)

Sowunmi, Olaperi Yeside; Misra, Sanjay; Fernandez-Sanz, Luis; Crawford, Broderick; Soto, Ricardo

2016-01-01

The importance of quality assurance in the software development process cannot be overemphasized because its adoption results in high reliability and easy maintenance of the software system and other software products. Software quality assurance includes different activities such as quality control, quality management, quality standards, quality planning, process standardization and improvement amongst others. The aim of this work is to further investigate the software quality assurance practices of practitioners in Nigeria. While our previous work covered areas on quality planning, adherence to standardized processes and the inherent challenges, this work has been extended to include quality control, software process improvement and international quality standard organization membership. It also makes comparison based on a similar study carried out in Turkey. The goal is to generate more robust findings that can properly support decision making by the software community. The qualitative research approach, specifically, the use of questionnaire research instruments was applied to acquire data from software practitioners. In addition to the previous results, it was observed that quality assurance practices are quite neglected and this can be the cause of low patronage. Moreover, software practitioners are neither aware of international standards organizations or the required process improvement techniques; as such their claimed standards are not aligned to those of accredited bodies, and are only limited to their local experience and knowledge, which makes it questionable. The comparison with Turkey also yielded similar findings, making the results typical of developing countries. The research instrument used was tested for internal consistency using the Cronbach's alpha, and it was proved reliable. For the software industry in developing countries to grow strong and be a viable source of external revenue, software assurance practices have to be taken seriously

Applied software risk management a guide for software project managers

CERN Document Server

Pandian, C Ravindranath

2006-01-01

Few software projects are completed on time, on budget, and to their original specifications. Focusing on what practitioners need to know about risk in the pursuit of delivering software projects, Applied Software Risk Management: A Guide for Software Project Managers covers key components of the risk management process and the software development process, as well as best practices for software risk identification, risk planning, and risk analysis. Written in a clear and concise manner, this resource presents concepts and practical insight into managing risk. It first covers risk-driven project management, risk management processes, risk attributes, risk identification, and risk analysis. The book continues by examining responses to risk, the tracking and modeling of risks, intelligence gathering, and integrated risk management. It concludes with details on drafting and implementing procedures. A diary of a risk manager provides insight in implementing risk management processes.Bringing together concepts ...

Software Defined Networking Demands on Software Technologies

DEFF Research Database (Denmark)

Galinac Grbac, T.; Caba, Cosmin Marius; Soler, José

2015-01-01

Software Defined Networking (SDN) is a networking approach based on a centralized control plane architecture with standardised interfaces between control and data planes. SDN enables fast configuration and reconfiguration of the network to enhance resource utilization and service performances....... This new approach enables a more dynamic and flexible network, which may adapt to user needs and application requirements. To this end, systemized solutions must be implemented in network software, aiming to provide secure network services that meet the required service performance levels. In this paper......, we review this new approach to networking from an architectural point of view, and identify and discuss some critical quality issues that require new developments in software technologies. These issues we discuss along with use case scenarios. Here in this paper we aim to identify challenges...

The Software Invention Cube: A classification scheme for software inventions

NARCIS (Netherlands)

Bergstra, J.A.; Klint, P.

2008-01-01

The patent system protects inventions. The requirement that a software invention should make ‘a technical contribution’ turns out to be untenable in practice and this raises the question, what constitutes an invention in the realm of software. The authors developed the Software Invention Cube

CERN Apps meet in a forum

CERN Multimedia

Antonella Del Rosso

2013-01-01

In the fast-evolving world of mobile apps, creativity and usability are key words. For the time being, the number of CERN apps is quite limited but the situation could quickly change. An information-sharing forum set up by the IT Department is a starting point to channel your creativity with the help of experts, best practices and useful guidelines.   The CAPPS (CERN Apps) Forum was set up about a year ago. Its members come from various departments and meet every two or three months to update each other on the apps that are in preparation, share the latest news on the available software, discuss best practices and so on. “The Forum is open to anybody wanting to develop apps at CERN,” explains David Foster, Deputy Department Head and initiator of the CAPPS Forum. “Developers, communication experts and IT infrastructure experts meet and discuss various topics, from branding-related issues to coding and implementation solutions. The aim is to go forward in a coherent way...

A Practical Introduction to HardwareSoftware Codesign

CERN Document Server

Schaumont, Patrick R

2013-01-01

This textbook provides an introduction to embedded systems design, with emphasis on integration of custom hardware components with software. The key problem addressed in the book is the following: how can an embedded systems designer strike a balance between flexibility and efficiency? The book describes how combining hardware design with software design leads to a solution to this important computer engineering problem. The book covers four topics in hardware/software codesign: fundamentals, the design space of custom architectures, the hardware/software interface and application examples. The book comes with an associated design environment that helps the reader to perform experiments in hardware/software codesign. Each chapter also includes exercises and further reading suggestions. Improvements in this second edition include labs and examples using modern FPGA environments from Xilinx and Altera, which make the material applicable to a greater number of courses where these tools are already in use.  Mo...

Software testability and its application to avionic software

Science.gov (United States)

Voas, Jeffrey M.; Miller, Keith W.; Payne, Jeffery E.

1993-01-01

Randomly generated black-box testing is an established yet controversial method of estimating software reliability. Unfortunately, as software applications have required higher reliabilities, practical difficulties with black-box testing have become increasingly problematic. These practical problems are particularly acute in life-critical avionics software, where requirements of 10 exp -7 failures per hour of system reliability can translate into a probability of failure (POF) of perhaps 10 exp -9 or less for each individual execution of the software. This paper describes the application of one type of testability analysis called 'sensitivity analysis' to B-737 avionics software; one application of sensitivity analysis is to quantify whether software testing is capable of detecting faults in a particular program and thus whether we can be confident that a tested program is not hiding faults. We so 80 by finding the testabilities of the individual statements of the program, and then use those statement testabilities to find the testabilities of the functions and modules. For the B-737 system we analyzed, we were able to isolate those functions that are more prone to hide errors during system/reliability testing.

Commercial Literacy Software.

Science.gov (United States)

Balajthy, Ernest

1997-01-01

Presents the first year's results of a continuing project to monitor the availability of software of relevance for literacy education purposes. Concludes there is an enormous amount of software available for use by teachers of reading and literacy--whereas drill-and-practice software is the largest category of software available, large numbers of…

NASA Software Engineering Benchmarking Study

Science.gov (United States)

Rarick, Heather L.; Godfrey, Sara H.; Kelly, John C.; Crumbley, Robert T.; Wifl, Joel M.

2013-01-01

To identify best practices for the improvement of software engineering on projects, NASA's Offices of Chief Engineer (OCE) and Safety and Mission Assurance (OSMA) formed a team led by Heather Rarick and Sally Godfrey to conduct this benchmarking study. The primary goals of the study are to identify best practices that: Improve the management and technical development of software intensive systems; Have a track record of successful deployment by aerospace industries, universities [including research and development (R&D) laboratories], and defense services, as well as NASA's own component Centers; and Identify candidate solutions for NASA's software issues. Beginning in the late fall of 2010, focus topics were chosen and interview questions were developed, based on the NASA top software challenges. Between February 2011 and November 2011, the Benchmark Team interviewed a total of 18 organizations, consisting of five NASA Centers, five industry organizations, four defense services organizations, and four university or university R and D laboratory organizations. A software assurance representative also participated in each of the interviews to focus on assurance and software safety best practices. Interviewees provided a wealth of information on each topic area that included: software policy, software acquisition, software assurance, testing, training, maintaining rigor in small projects, metrics, and use of the Capability Maturity Model Integration (CMMI) framework, as well as a number of special topics that came up in the discussions. NASA's software engineering practices compared favorably with the external organizations in most benchmark areas, but in every topic, there were ways in which NASA could improve its practices. Compared to defense services organizations and some of the industry organizations, one of NASA's notable weaknesses involved communication with contractors regarding its policies and requirements for acquired software. One of NASA's strengths

Influence of HRM Practices on Organizational Commitment: A Study among Software Professionals in India

Science.gov (United States)

Paul, A. K.; Anantharaman, R. N.

2004-01-01

Although organizational commitment has been discussed frequently in organizational psychology for almost four decades, few studies have involved software professionals. A study in India reveals that HRM practices such as employee-friendly work environment, career development, development oriented appraisal, and comprehensive training show a…

Training the Knowledge Worker: A Descriptive Study of Training Practices in Irish Software Companies.

Science.gov (United States)

Acton, Thomas; Golden, Willie

2003-01-01

Employees (n=200) of 39 Irish software companies indicated the following about training practices: organizational commitment to and provision for training was positively associated with employee expectations; well-designed training increased job satisfaction and helped retain organizational knowledge. One-third believed training has not helped…

Use of voice recognition software in an outpatient pediatric specialty practice.

Science.gov (United States)

Issenman, Robert M; Jaffer, Iqbal H

2004-09-01

Voice recognition software (VRS), with specialized medical vocabulary, is being promoted to enhance physician efficiency, decrease costs, and improve patient safety. This study reports the experience of a pediatric subspecialist (pediatric gastroenterology) physician with the use of Dragon Naturally Speaking (version 6; ScanSoft Inc, Peabody, MA), incorporated for use with a proprietary electronic medical record, in a large university medical center ambulatory care service. After 2 hours of group orientation and 2 hours of individual VRS instruction, the physician trained the software for 1 month (30 letters) during a hospital slowdown. Set-up, dictation, and correction times for the physician and medical transcriptionist were recorded for these training sessions, as well as for 42 subsequently dictated letters. Figures were extrapolated to the yearly clinic volume for the physician, to estimate costs (physician: 110 dollars per hour; transcriptionist: 11 dollars per hour, US dollars). The use of VRS required an additional 200% of physician dictation and correction time (9 minutes vs 3 minutes), compared with the use of electronic signatures for letters typed by an experienced transcriptionist and imported into the electronic medical record. When the cost of the license agreement and the costs of physician and transcriptionist time were included, the use of the software cost 100% more, for the amount of dictation performed annually by the physician. VRS is an intriguing technology. It holds the possibility of streamlining medical practice. However, the learning curve and accuracy of the tested version of the software limit broad physician acceptance at this time.

Software life after in-service

International Nuclear Information System (INIS)

Tseng, M.; Eng, P.

1993-01-01

Software engineers and designers tend to conclude a software project at the in-service milestone of the software life cycle. But the reality is that the 'life after in-service' is significantly longer than other phases of the life cycle, typically 20 years or more depending on the maintainability of the hardware platform and the designed life of the plant. During this period, the software asset (as with other physical assets in the plant) continues to be upgraded to correct deficiencies, meet new requirements, cope with obsolescence of equipment and so on. The software life cycle ends with a migration of the software to a different platform. It is typical in a software development project to put a great deal of emphasis on design methodologies, techniques, tools, development environment, standard procedures, and project management to ensure quality product is delivered on schedule and within budget. More often than not, a disproportion of emphasis is placed on the issues and needs of the in-service phase. Once the software is in-service, the designers move on to other projects, while the maintenance and support staff must manage the software. This paper examines the issues in three steps. First it presents a view of software from maintenance and support staff perspectives, including complexity of software, suitability of documentation, configuration management, training, difficulties and risks associated with making changes, required skills and knowledge. Second, it identifies the concerns raised from these viewpoints, including costs of maintaining the software, ability to meet additional requirements, availability of support tools, length of time required to engineer and install changes, and a strategy for the migration of software asset. Finally it discusses some approaches to deal with the concerns. (Author) 5 refs., fig

Analysis of free geo-server software usability from the viewpoint of INSPIRE requirementsAnalysis of free geo-server software usability from the viewpoint of INSPIRE requirements

Directory of Open Access Journals (Sweden)

Tomasz  Grasza

2014-06-01

Full Text Available The paper presents selected server platforms based on free and open source license, coherent with the standards of the Open Geospatial Consortium. The presented programs are evaluated in the context of the INSPIRE Directive. The first part describes the requirements of the Directive, and afterwards presented are the pros and cons of each platform, to meet these demands. This article provides an answer to the question whether the use of free software can provide interoperable network services in accordance with the requirements of the INSPIRE Directive, on the occasion of presenting the application examples and practical tips on the use of particular programs.[b]Keywords[/b]: GIS, INSPIRE, free software, OGC, geoportal, network services, GeoServer, deegree, GeoNetwork

Software safety analysis practice in installation phase

Energy Technology Data Exchange (ETDEWEB)

Huang, H. W.; Chen, M. H.; Shyu, S. S., E-mail: hwhwang@iner.gov.t [Institute of Nuclear Energy Research, No. 1000 Wenhua Road, Chiaan Village, Longtan Township, 32546 Taoyuan County, Taiwan (China)

2010-10-15

This work performed a software safety analysis in the installation phase of the Lung men nuclear power plant in Taiwan, under the cooperation of Institute of Nuclear Energy Research and Tpc. The US Nuclear Regulatory Commission requests licensee to perform software safety analysis and software verification and validation in each phase of software development life cycle with Branch Technical Position 7-14. In this work, 37 safety grade digital instrumentation and control systems were analyzed by failure mode and effects analysis, which is suggested by IEEE standard 7-4.3.2-2003. During the installation phase, skew tests for safety grade network and point to point tests were performed. The failure mode and effects analysis showed all the single failure modes can be resolved by the redundant means. Most of the common mode failures can be resolved by operator manual actions. (Author)

Software safety analysis practice in installation phase

International Nuclear Information System (INIS)

Huang, H. W.; Chen, M. H.; Shyu, S. S.

2010-10-01

This work performed a software safety analysis in the installation phase of the Lung men nuclear power plant in Taiwan, under the cooperation of Institute of Nuclear Energy Research and Tpc. The US Nuclear Regulatory Commission requests licensee to perform software safety analysis and software verification and validation in each phase of software development life cycle with Branch Technical Position 7-14. In this work, 37 safety grade digital instrumentation and control systems were analyzed by failure mode and effects analysis, which is suggested by IEEE standard 7-4.3.2-2003. During the installation phase, skew tests for safety grade network and point to point tests were performed. The failure mode and effects analysis showed all the single failure modes can be resolved by the redundant means. Most of the common mode failures can be resolved by operator manual actions. (Author)

Practical requirements for software tools to assist in the validation and verification of hybrid expert systems

International Nuclear Information System (INIS)

Singh, G.P.; Cadena, D.; Burgess, J.

1992-01-01

Any practical software development effort must remain focused on verification and validation of user requirements. Knowledge-based system development is no different in this regard. In industry today, most expert systems being produced are, in reality, hybrid software systems which, in addition to those components that provide the knowledge base and expert reasoning over the problem domain using various rule-based and object-oriented paradigms, incorporate significant bodies of code based on more traditional software techniques such as database management, graphical user interfaces, hypermedia, spreadsheets, as well as specially developed sequential code. Validation and verification of such hybrid systems must perforce integrate suitable methodologies from all such fields. This paper attempts to provide a broad overview of the practical requirements for methodologies and the concomitant groupware tools which would assist in such an enterprise. These methodologies and groupware tools would facilitate the teamwork efforts necessary to validate and verify all components of such hybrid systems by emphasizing cooperative recording of requirements and negotiated resolutions of any conflicts grounded in a solid understanding of the semantics of such a system

Space Station: NASA's software development approach increases safety and cost risks. Report to the Chairman, Committee on Science, Space, and Technology, House of Representatives

Science.gov (United States)

1992-06-01

The House Committee on Science, Space, and Technology asked NASA to study software development issues for the space station. How well NASA has implemented key software engineering practices for the station was asked. Specifically, the objectives were to determine: (1) if independent verification and validation techniques are being used to ensure that critical software meets specified requirements and functions; (2) if NASA has incorporated software risk management techniques into program; (3) whether standards are in place that will prescribe a disciplined, uniform approach to software development; and (4) if software support tools will help, as intended, to maximize efficiency in developing and maintaining the software. To meet the objectives, NASA proceeded: (1) reviewing and analyzing software development objectives and strategies contained in NASA conference publications; (2) reviewing and analyzing NASA, other government, and industry guidelines for establishing good software development practices; (3) reviewing and analyzing technical proposals and contracts; (4) reviewing and analyzing software management plans, risk management plans, and program requirements; (4) reviewing and analyzing reports prepared by NASA and contractor officials that identified key issues and challenges facing the program; (5) obtaining expert opinions on what constitutes appropriate independent V-and-V and software risk management activities; (6) interviewing program officials at NASA headquarters in Washington, DC; at the Space Station Program Office in Reston, Virginia; and at the three work package centers; Johnson in Houston, Texas; Marshall in Huntsville, Alabama; and Lewis in Cleveland, Ohio; and (7) interviewing contractor officials doing work for NASA at Johnson and Marshall. The audit work was performed in accordance with generally accepted government auditing standards, between April 1991 and May 1992.

Software Toolkits: Practical Aspects of the Internet of Things—A Survey

OpenAIRE

Wang, Feng; Hu, Liang; Zhou, Jin; Wu, Yang; Hu, Jiejun; Zhao, Kuo

2015-01-01

The Internet of Things (IoT) is neither science fiction nor industry hype; rather it is based on solid technological advances and visions of network ubiquity that are zealously being realized. The paper serves to provide guidance regarding the practical aspects of the IoT. Such guidance is largely missing in the current literature in which the focus has been more on research problems and less on issues describing how to set up an IoT system and what software toolkits are required. This paper ...

Software Development Standard Processes (SDSP)

Science.gov (United States)

Lavin, Milton L.; Wang, James J.; Morillo, Ronald; Mayer, John T.; Jamshidian, Barzia; Shimizu, Kenneth J.; Wilkinson, Belinda M.; Hihn, Jairus M.; Borgen, Rosana B.; Meyer, Kenneth N.;

Software Quality Assurance Audits Guidebooks

Science.gov (United States)

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.

40 CFR 63.7925 - What emissions limitations and work practice standards must I meet for closed vent systems and...

Science.gov (United States)

2010-07-01

... What emissions limitations and work practice standards must I meet for closed vent systems and control... 40 Protection of Environment 13 2010-07-01 2010-07-01 false What emissions limitations and work practice standards must I meet for closed vent systems and control devices? 63.7925 Section 63.7925...

Software Reviews.

Science.gov (United States)

Davis, Shelly J., Ed.; Knaupp, Jon, Ed.

1984-01-01

Reviewed is computer software on: (1) classification of living things, a tutorial program for grades 5-10; and (2) polynomial practice using tiles, a drill-and-practice program for algebra students. (MNS)

Good practices for educational software engineering projects

NARCIS (Netherlands)

van der Duim, Louwarnoud; Andersson, Jesper; Sinnema, Marco

2007-01-01

Recent publications indicate the importance of software engineering in the computer science curriculum. In this paper, we present the final part of software engineering education at University of Groningen in the Netherlands and Vaxjo University in Sweden, where student teams perform an industrial

The impact of continuous integration on other software development practices: a large-scale empirical study

NARCIS (Netherlands)

Zhao, Y.; Serebrenik, A.; Zhou, Y.; Filkov, V.; Vasilescu, B.N.

2017-01-01

Continuous Integration (CI) has become a disruptive innovation in software development: with proper tool support and adoption, positive effects have been demonstrated for pull request throughput and scaling up of project sizes. As any other innovation, adopting CI implies adapting existing practices

Open source software in a practical approach for post processing of radiologic images.

Science.gov (United States)

Valeri, Gianluca; Mazza, Francesco Antonino; Maggi, Stefania; Aramini, Daniele; La Riccia, Luigi; Mazzoni, Giovanni; Giovagnoni, Andrea

2015-03-01

The purpose of this paper is to evaluate the use of open source software (OSS) to process DICOM images. We selected 23 programs for Windows and 20 programs for Mac from 150 possible OSS programs including DICOM viewers and various tools (converters, DICOM header editors, etc.). The programs selected all meet the basic requirements such as free availability, stand-alone application, presence of graphical user interface, ease of installation and advanced features beyond simple display monitor. Capabilities of data import, data export, metadata, 2D viewer, 3D viewer, support platform and usability of each selected program were evaluated on a scale ranging from 1 to 10 points. Twelve programs received a score higher than or equal to eight. Among them, five obtained a score of 9: 3D Slicer, MedINRIA, MITK 3M3, VolView, VR Render; while OsiriX received 10. OsiriX appears to be the only program able to perform all the operations taken into consideration, similar to a workstation equipped with proprietary software, allowing the analysis and interpretation of images in a simple and intuitive way. OsiriX is a DICOM PACS workstation for medical imaging and software for image processing for medical research, functional imaging, 3D imaging, confocal microscopy and molecular imaging. This application is also a good tool for teaching activities because it facilitates the attainment of learning objectives among students and other specialists.

The Computer-based Health Evaluation Software (CHES: a software for electronic patient-reported outcome monitoring

Directory of Open Access Journals (Sweden)

Holzner Bernhard

2012-11-01

Full Text Available Abstract Background Patient-reported Outcomes (PROs capturing e.g., quality of life, fatigue, depression, medication side-effects or disease symptoms, have become important outcome parameters in medical research and daily clinical practice. Electronic PRO data capture (ePRO with software packages to administer questionnaires, storing data, and presenting results has facilitated PRO assessment in hospital settings. Compared to conventional paper-pencil versions of PRO instruments, ePRO is more economical with regard to staff resources and time, and allows immediate presentation of results to the medical staff. The objective of our project was to develop software (CHES – Computer-based Health Evaluation System for ePRO in hospital settings and at home with a special focus on the presentation of individual patient’s results. Methods Following the Extreme Programming development approach architecture was not fixed up-front, but was done in close, continuous collaboration with software end users (medical staff, researchers and patients to meet their specific demands. Developed features include sophisticated, longitudinal charts linking patients’ PRO data to clinical characteristics and to PRO scores from reference populations, a web-interface for questionnaire administration, and a tool for convenient creating and editing of questionnaires. Results By 2012 CHES has been implemented at various institutions in Austria, Germany, Switzerland, and the UK and about 5000 patients participated in ePRO (with around 15000 assessments in total. Data entry is done by the patients themselves via tablet PCs with a study nurse or an intern approaching patients and supervising questionnaire completion. Discussion During the last decade several software packages for ePRO have emerged for different purposes. Whereas commercial products are available primarily for ePRO in clinical trials, academic projects have focused on data collection and presentation in daily

LDUA software custodian's notebook

International Nuclear Information System (INIS)

Aftanas, B.L.

1998-01-01

This plan describes the activities to be performed and controls to be applied to the process of specifying, obtaining, and qualifying the control and data acquisition software for the Light Duty Utility Arm (LDUA) System. It serves the purpose of a software quality assurance plan, a verification and validation plan, and a configuration management plan. This plan applies to all software that is an integral part of the LDUA control and data acquisition system, that is, software that is installed in the computers that are part of the LDUA system as it is deployed in the field. This plan applies to the entire development process, including: requirements; design; implementation; and operations and maintenance. This plan does not apply to any software that is not integral with the LDUA system. This plan has-been prepared in accordance with WHC-CM-6-1 Engineering Practices, EP-2.1; WHC-CM-3-10 Software Practices; and WHC-CM-4-2, QR 19.0, Software Quality Assurance Requirements

77 FR 50726 - Software Requirement Specifications for Digital Computer Software and Complex Electronics Used in...

Science.gov (United States)

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...

Software packages for food engineering needs

OpenAIRE

Abakarov, Alik

2011-01-01

The graphic user interface (GUI) software packages “ANNEKs” and “OPT-PROx” are developed to meet food engineering needs. “OPT-RROx” (OPTimal PROfile) is software developed to carry out thermal food processing optimization based on the variable retort temperature processing and global optimization technique. “ANNEKs” (Artificial Neural Network Enzyme Kinetics) is software designed for determining the kinetics of enzyme hydrolysis of protein at different initial reaction parameters based on the...

Software quality assurance plans for safety-critical software

International Nuclear Information System (INIS)

Liddle, P.

2006-01-01

Application software is defined as safety-critical if a fault in the software could prevent the system components from performing their nuclear-safety functions. Therefore, for nuclear-safety systems, the AREVA TELEPERM R XS (TXS) system is classified 1E, as defined in the Inst. of Electrical and Electronics Engineers (IEEE) Std 603-1998. The application software is classified as Software Integrity Level (SIL)-4, as defined in IEEE Std 7-4.3.2-2003. The AREVA NP Inc. Software Program Manual (SPM) describes the measures taken to ensure that the TELEPERM XS application software attains a level of quality commensurate with its importance to safety. The manual also describes how TELEPERM XS correctly performs the required safety functions and conforms to established technical and documentation requirements, conventions, rules, and standards. The program manual covers the requirements definition, detailed design, integration, and test phases for the TELEPERM XS application software, and supporting software created by AREVA NP Inc. The SPM is required for all safety-related TELEPERM XS system applications. The program comprises several basic plans and practices: 1. A Software Quality-Assurance Plan (SQAP) that describes the processes necessary to ensure that the software attains a level of quality commensurate with its importance to safety function. 2. A Software Safety Plan (SSP) that identifies the process to reasonably ensure that safety-critical software performs as intended during all abnormal conditions and events, and does not introduce any new hazards that could jeopardize the health and safety of the public. 3. A Software Verification and Validation (V and V) Plan that describes the method of ensuring the software is in accordance with the requirements. 4. A Software Configuration Management Plan (SCMP) that describes the method of maintaining the software in an identifiable state at all times. 5. A Software Operations and Maintenance Plan (SO and MP) that

Aligning Requirements-Driven Software Processes with IT Governance

OpenAIRE

Nguyen Huynh Anh, Vu; Kolp, Manuel; Heng, Samedi; Wautelet, Yves

2017-01-01

Requirements Engineering is closely intertwined with Information Technology (IT) Governance. Aligning IT Governance principles with Requirements-Driven Software Processes allows them to propose governance and management rules for software development to cope with stakeholders’ requirements and expectations. Typically, the goal of IT Governance in software engineering is to ensure that the results of a software organization business processes meet the strategic requirements of the organization...

Testing Software Development Project Productivity Model

Science.gov (United States)

Lipkin, Ilya

Software development is an increasingly influential factor in today's business environment, and a major issue affecting software development is how an organization estimates projects. If the organization underestimates cost, schedule, and quality requirements, the end results will not meet customer needs. On the other hand, if the organization overestimates these criteria, resources that could have been used more profitably will be wasted. There is no accurate model or measure available that can guide an organization in a quest for software development, with existing estimation models often underestimating software development efforts as much as 500 to 600 percent. To address this issue, existing models usually are calibrated using local data with a small sample size, with resulting estimates not offering improved cost analysis. This study presents a conceptual model for accurately estimating software development, based on an extensive literature review and theoretical analysis based on Sociotechnical Systems (STS) theory. The conceptual model serves as a solution to bridge organizational and technological factors and is validated using an empirical dataset provided by the DoD. Practical implications of this study allow for practitioners to concentrate on specific constructs of interest that provide the best value for the least amount of time. This study outlines key contributing constructs that are unique for Software Size E-SLOC, Man-hours Spent, and Quality of the Product, those constructs having the largest contribution to project productivity. This study discusses customer characteristics and provides a framework for a simplified project analysis for source selection evaluation and audit task reviews for the customers and suppliers. Theoretical contributions of this study provide an initial theory-based hypothesized project productivity model that can be used as a generic overall model across several application domains such as IT, Command and Control

Development of the quality assessment model of EHR software in family medicine practices: research based on user satisfaction

Directory of Open Access Journals (Sweden)

Damir Kralj

2015-09-01

Full Text Available Background Family medicine practices (FMPs make the basis for the Croatian health care system. Use of electronic health record (EHR software is mandatory and it plays an important role in running these practices, but important functional features still remain uneven and largely left to the will of the software developers.Objective The objective of this study was to develop a novel and comprehensive model for functional evaluation of the EHR software in FMPs, based on current world standards, models and projects, as well as on actual user satisfaction and requirements.Methods Based on previous theoretical and experimental research in this area, we made the initial framework model consisting of six basic categories as a base for online survey questionnaire. Family doctors assessed perceived software quality by using a five-point Likert-type scale. Using exploratory factor analysis and appropriate statistical methods over the collected data, the final optimal structure of the novel model was formed. Special attention was focused on the validity and quality of the novel model.Results The online survey collected a total of 384 cases. The obtained results indicate both the quality of the assessed software and the quality in use of the novel model. The intense ergonomic orientation of the novel measurement model was particularly emphasised.Conclusions The resulting novel model is multiple validated, comprehensive and universal. It could be used to assess the user-perceived quality of almost all forms of the ambulatory EHR software and therefore useful to all stakeholders in this area of the health care informatisation. 

Development of the quality assessment model of EHR software in family medicine practices: research based on user satisfaction.

Science.gov (United States)

Kralj, Damir; Kern, Josipa; Tonkovic, Stanko; Koncar, Miroslav

2015-09-09

Family medicine practices (FMPs) make the basis for the Croatian health care system. Use of electronic health record (EHR) software is mandatory and it plays an important role in running these practices, but important functional features still remain uneven and largely left to the will of the software developers. The objective of this study was to develop a novel and comprehensive model for functional evaluation of the EHR software in FMPs, based on current world standards, models and projects, as well as on actual user satisfaction and requirements. Based on previous theoretical and experimental research in this area, we made the initial framework model consisting of six basic categories as a base for online survey questionnaire. Family doctors assessed perceived software quality by using a five-point Likert-type scale. Using exploratory factor analysis and appropriate statistical methods over the collected data, the final optimal structure of the novel model was formed. Special attention was focused on the validity and quality of the novel model. The online survey collected a total of 384 cases. The obtained results indicate both the quality of the assessed software and the quality in use of the novel model. The intense ergonomic orientation of the novel measurement model was particularly emphasised. The resulting novel model is multiple validated, comprehensive and universal. It could be used to assess the user-perceived quality of almost all forms of the ambulatory EHR software and therefore useful to all stakeholders in this area of the health care informatisation.

Software Engineering Program: Software Process Improvement Guidebook

Science.gov (United States)

1996-01-01

The purpose of this document is to provide experience-based guidance in implementing a software process improvement program in any NASA software development or maintenance community. This guidebook details how to define, operate, and implement a working software process improvement program. It describes the concept of the software process improvement program and its basic organizational components. It then describes the structure, organization, and operation of the software process improvement program, illustrating all these concepts with specific NASA examples. The information presented in the document is derived from the experiences of several NASA software organizations, including the SEL, the SEAL, and the SORCE. Their experiences reflect many of the elements of software process improvement within NASA. This guidebook presents lessons learned in a form usable by anyone considering establishing a software process improvement program within his or her own environment. This guidebook attempts to balance general and detailed information. It provides material general enough to be usable by NASA organizations whose characteristics do not directly match those of the sources of the information and models presented herein. It also keeps the ideas sufficiently close to the sources of the practical experiences that have generated the models and information.

Repository-based software engineering program

Science.gov (United States)

Wilson, James

1992-01-01

The activities performed during September 1992 in support of Tasks 01 and 02 of the Repository-Based Software Engineering Program are outlined. The recommendations and implementation strategy defined at the September 9-10 meeting of the Reuse Acquisition Action Team (RAAT) are attached along with the viewgraphs and reference information presented at the Institute for Defense Analyses brief on legal and patent issues related to software reuse.

Interface-based software integration

Directory of Open Access Journals (Sweden)

Aziz Ahmad Rais

2016-07-01

Full Text Available Enterprise architecture frameworks define the goals of enterprise architecture in order to make business processes and IT operations more effective, and to reduce the risk of future investments. These enterprise architecture frameworks offer different architecture development methods that help in building enterprise architecture. In practice, the larger organizations become, the larger their enterprise architecture and IT become. This leads to an increasingly complex system of enterprise architecture development and maintenance. Application software architecture is one type of architecture that, along with business architecture, data architecture and technology architecture, composes enterprise architecture. From the perspective of integration, enterprise architecture can be considered a system of interaction between multiple examples of application software. Therefore, effective software integration is a very important basis for the future success of the enterprise architecture in question. This article will provide interface-based integration practice in order to help simplify the process of building such a software integration system. The main goal of interface-based software integration is to solve problems that may arise with software integration requirements and developing software integration architecture.

Avionics Simulation, Development and Software Engineering

Science.gov (United States)

2002-01-01

During this reporting period, all technical responsibilities were accomplished as planned. A close working relationship was maintained with personnel of the MSFC Avionics Department Software Group (ED14), the MSFC EXPRESS Project Office (FD31), and the Huntsville Boeing Company. Accomplishments included: performing special tasks; supporting Software Review Board (SRB), Avionics Test Bed (ATB), and EXPRESS Software Control Panel (ESCP) activities; participating in technical meetings; and coordinating issues between the Boeing Company and the MSFC Project Office.

Software requirements

CERN Document Server

Wiegers, Karl E

2003-01-01

Without formal, verifiable software requirements-and an effective system for managing them-the programs that developers think they've agreed to build often will not be the same products their customers are expecting. In SOFTWARE REQUIREMENTS, Second Edition, requirements engineering authority Karl Wiegers amplifies the best practices presented in his original award-winning text?now a mainstay for anyone participating in the software development process. In this book, you'll discover effective techniques for managing the requirements engineering process all the way through the development cy

Software technology for power control

Energy Technology Data Exchange (ETDEWEB)

Kakizoe, Hiroyuki; Suganuma, Isao; Yamaguchi, Shiu; Yasuda, Takashi

1987-04-27

High reliability, high-speed computing processing at the time of trouble, and easy data maintenance are required for a power control system. Design concept, materializing methods, tools and practical applications of the system software are presented. To enhance maintenability, structures and simulation functions, etc. were developed. To meet the requirement for high speed processing, systems for high speed filing and queueing, and a service subsystem were developed. To automate the overall system, a dual system was established by AIP subsystems to improve reliability. Discs can be protected by the dual system. A fallback system was employed which will separate a troubled portion to enable the continuous operation of the total system. Error logging and performance analysis tools were also developed. Data maintenance feature and application simulation programs were also developed to help operators easily modify the facilities data. (9 figs)

Monitoring Student Activity in Collaborative Software Development

DEFF Research Database (Denmark)

Dietsch, Daniel; Podelski, Andreas; Nam, Jaechang

2013-01-01

year of studies formed 20 groups and worked collaboratively to develop video games. Throughout the lab, students have to use a variety of tools for managing and developing their projects, such as software version control, static analysis tools, wikis, mailing lists, etc. The students are also supported......This paper presents data analysis from a course on Software Engineering in an effort to identify metrics and techniques that would allow instructor to act proactively and identify patterns of low engagement and inefficient peer collaboration. Over the last two terms, 106 students in their second...... by weekly meetings with teaching assistants and instructors regarding group progress, code quality, and management issues. Through these meetings and their interactions with the software tools, students leave a detailed trace of data related to their individual engagement and their collaboration behavior...

Practical JIRA Plugins

CERN Document Server

Doar, Matthew

2011-01-01

One advantage of using JIRA for issue tracking, bug tracking, or project management is the ability to extend this tool with hundreds of plugins from the JIRA community. In this concise book, software toolsmith Matt Doar-the author of Practical JIRA Administration-shows you how to create and maintain your own JIRA plugins to meet the specific needs of a project. This book uses detailed examples to clarify some of the more confusing aspects of JIRA plugins, and serves as an ideal supplement to the extensive documentation already available. Use JIRA's Plugin SDK, and learn several aspects commo

Analysis of Agile Practices Adoption on CMMI Organizations through a Systematic Literature Review

Directory of Open Access Journals (Sweden)

Marco Palomino

2017-11-01

Full Text Available In the recent years, the adoption of agile frameworks and methodologies in Software Development Organizations (SDO has grown up considerably. Unfortunately, the level required of formal documentation in bigger or longer software development projects is not full covered by agile practices alone; likewise, this kind of situations happen frequently in a context of CMMI organizations. The aim of this study is identify, review and analyze the most used agile practices that are being used in combination with CMMI within SDO. To accomplish this, a systematic literature review has been performed according to relevant guidelines. This study has identified multiple practices such as Daily Meeting and Product Backlog management that are being used constantly in combination with CMMI. In addition, we could identify that there are specific benefits of implementing practices from both approaches.

Software Distribution Statement and Disclaimer | OSTI, US Dept of Energy

Science.gov (United States)

Search Search Software Distribution Statement and Disclaimer Rights-in-technical-data clauses for many . The following distribution statement and disclaimer meet those requirements for software and should be affixed to all distributed DOE-sponsored software. Contractors may have specific requirements and required

Exploring the organizational impact of software-as-a-Service on software vendors the role of organizational integration in software-as-a-Service development and operation

CERN Document Server

Stuckenberg, Sebastian

2014-01-01

Software-as-a-Service has gained momentum as a software delivery and pricing model within the software industry. Existing practices of software vendors are challenged by a potential paradigm shift. This book analyzes the implications of Software-as-a-Service on software vendors using a business model and value chain perspective. The analysis of qualitative data from software vendors highlights the role of organizational integration within software vendors. By providing insights regarding the impact of Software-as-a-Service on organizational structures and processes of software vendors, this st

Quality assurance of EDP software in practical application

International Nuclear Information System (INIS)

Winkler, H.

1982-01-01

Alongside the specific properties of the soft software, it is mainly points outside the traditional testing field which apply for the quality assurance thereof. Measures for quality assurance must in particular, start in the development. This presupposes a partial-result orientated development process of software. Due to the high qualitative demands, implements for testing and inspection are of great importance. The problems in software quality assurance are typical for a young technical field where the necessity of which is indisputed, but which has to effect on an empirical-pragmatical level still, due to insufficient scientific foundation. (orig.) [de

AAS Publishing News: Astronomical Software Citation Workshop

Science.gov (United States)

Kohler, Susanna

2015-07-01

Do you write code for your research? Use astronomical software? Do you wish there were a better way of citing, sharing, archiving, or discovering software for astronomy research? You're not alone! In April 2015, AAS's publishing team joined other leaders in the astronomical software community in a meeting funded by the Sloan Foundation, with the purpose of discussing these issues and potential solutions. In attendance were representatives from academic astronomy, publishing, libraries, for-profit software sharing platforms, telescope facilities, and grantmaking institutions. The goal of the group was to establish “protocols, policies, and platforms for astronomical software citation, sharing, and archiving,” in the hopes of encouraging a set of normalized standards across the field. The AAS is now collaborating with leaders at GitHub to write grant proposals for a project to develop strategies for software discoverability and citation, in astronomy and beyond. If this topic interests you, you can find more details in this document released by the group after the meeting: http://astronomy-software-index.github.io/2015-workshop/ The group hopes to move this project forward with input and support from the broader community. Please share the above document, discuss it on social media using the hashtag #astroware (so that your conversations can be found!), or send private comments to julie.steffen@aas.org.

The reproduction of difference in the practices of Free/Libre Open Source Software Communities

OpenAIRE

Meyer, Silke

2013-01-01

Free software is developed and distributed by communities. These communities seek to enable themselves and others to design technologies by and for themselves, rather than accepting technologies as given artefacts. These communities attempt to practise a very open approach towards spreading and sharing knowledge. This thesis analyzes how social power relations are reproduced in the sociotechnological practices of these communities. Based on participant obeservation in Linux User Groups, four ...

CERN software developers gathering in September

CERN Document Server

Antonella Del Rosso

2015-01-01

Hundreds of developers work on many different projects at CERN – from data analysis to beam operations and administrative applications. As of this September, they will have an opportunity to meet each other at the newly established Developers@CERN Forum.   “We go to conferences elsewhere but we hardly ever meet here at CERN, where we all work on our own separate software projects,” says José Carlos Luna, a member of the IT department and one of the organisers of the first Developers@CERN Forum. Indeed, although several CERN departments have software developers working in their teams, there is no proper “community” built around them. The first Developers@CERN Forum will be held on 28 and 29 September. The event is being organised by a few developers from the IT department, together with colleagues from the GS and EN departments. Its main scope is to reach out to all the departments in an effort to bring all CERN’s software dev...

Upgradable Software Product Customization by Code Query

DEFF Research Database (Denmark)

Vaucouleur, Sebastien

The professional press on enterprise systems warns its readers: Costly., A return on investment killer. , Be prepared!. What can create some much af- iction and turmoil in an otherwise very successful industry? Come and meet the dreadful upgrade problem. Enterprise systems are prime examples...... of a subset of software systems that we call software products: software that needs special support for customization. Through customization, external companies can modify part of the original product to better t the needs of a niche market. Upon the release of a new version of the original software product...

Practices and developments in spent fuel burnup credit applications. Proceedings of a technical committee meeting

Energy Technology Data Exchange (ETDEWEB)

NONE

2003-10-01

The International Atomic Energy Agency convened a technical committee Meeting on Requirements, Practices and Developments in Burnup Credit (BUC) Applications in Madrid, Spain, from 22 to 26 April 2002. The purpose of this meeting was to explore the progress and status of international activities related to the BUC applications for spent nuclear fuel. This meeting was the third major meeting on the uses of BUC for spent fuel management systems held since the IAEA began to monitor the uses of BUC in spent fuel management systems in 1997. The first major meeting was an Advisory Group meeting (AGM), which was held in Vienna, in October 1997. The second major meeting was a technical committee meeting (TCM), which was held in Vienna, in July 2000. Several consultants meetings were held since 1997 to advise and assist the IAEA in planning and conducting its BUC activities. The proceedings of the 1997 AGM were published as IAEA-TECDOC-1013, and the proceedings of the 2000 TCM as IAEA-TECDOC-1241. BUC for wet and dry storage systems, spent fuel transport, reprocessing and final disposal is needed in many Member States to allow for increased enrichment, and to increase storage capacities, cask capacities and dissolver capacities avoiding the need for extensive modifications. The use of BUC is a necessity for spent fuel disposal.

Software quality management

International Nuclear Information System (INIS)

Bishop, D.C.; Pymm, P.

1991-01-01

As programmable electronic (software-based) systems are increasingly being proposed as design solutions for high integrity applications in nuclear power stations, the need to adopt suitable quality management arrangements is paramount. The authors describe Scottish Nuclear's strategy for software quality management and, using the main on-line monitoring system at Torness Power Station as an example, explain how this strategy is put into practice. Particular attention is given to the topics of software quality planning and change control. (author)

Secondary Mathematics Teachers' Beliefs, Attitudes, Knowledge Base, and Practices in Meeting the Needs of English Language Learners

Science.gov (United States)

Gann, Linda

2013-01-01

The research centered on secondary mathematics teachers' beliefs, attitudes, knowledge base, and practices in meeting the academic and language needs of English language learners. Using socio-cultural theory and social practice theory to frame the study, the research design employed a mixed methods approach incorporating self-reported surveys,…

Open source software migration: Best practices

CSIR Research Space (South Africa)

Molefe, Onkgopotse M

2010-09-01

Full Text Available Open source software (OSS) has gained prominence worldwide, largely due to cost savings and security considerations. This has caused a change in the IT sector and has led to the migration of desktops from proprietary to OSS. The problem...

Evaluating the feasibility of using online software to collect patient information in a chiropractic practice-based research network.

Science.gov (United States)

Kania-Richmond, Ania; Weeks, Laura; Scholten, Jeffrey; Reney, Mikaël

2016-03-01

Practice based research networks (PBRNs) are increasingly used as a tool for evidence based practice. We developed and tested the feasibility of using software to enable online collection of patient data within a chiropractic PBRN to support clinical decision making and research in participating clinics. To assess the feasibility of using online software to collect quality patient information. The study consisted of two phases: 1) Assessment of the quality of information provided, using a standardized form; and 2) Exploration of patients' perspectives and experiences regarding online information provision through semi-structured interviews. Data analysis was descriptive. Forty-five new patients were recruited. Thirty-six completed online forms, which were submitted by an appropriate person 100% of the time, with an error rate of less than 1%, and submitted in a timely manner 83% of the time. Twenty-one participants were interviewed. Overall, online forms were preferred given perceived security, ease of use, and enabling provision of more accurate information. Use of online software is feasible, provides high quality information, and is preferred by most participants. A pen-and-paper format should be available for patients with this preference and in case of technical difficulties.

Essential software architecture

CERN Document Server

Gorton, Ian

2011-01-01

Job titles like ""Technical Architect"" and ""Chief Architect"" nowadays abound in software industry, yet many people suspect that ""architecture"" is one of the most overused and least understood terms in professional software development. Gorton's book tries to resolve this dilemma. It concisely describes the essential elements of knowledge and key skills required to be a software architect. The explanations encompass the essentials of architecture thinking, practices, and supporting technologies. They range from a general understanding of structure and quality attributes through technical i

Software Quality Assurance Metrics

Science.gov (United States)

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 engineering

CERN Document Server

Sommerville, Ian

2016-01-01

For courses in computer science and software engineering The Fundamental Practice of Software Engineering Software Engineering introduces readers to the overwhelmingly important subject of software programming and development. In the past few years, computer systems have come to dominate not just our technological growth, but the foundations of our world's major industries. This text seeks to lay out the fundamental concepts of this huge and continually growing subject area in a clear and comprehensive manner. The Tenth Edition contains new information that highlights various technological updates of recent years, providing readers with highly relevant and current information. Sommerville's experience in system dependability and systems engineering guides the text through a traditional plan-based approach that incorporates some novel agile methods. The text strives to teach the innovators of tomorrow how to create software that will make our world a better, safer, and more advanced place to live.

Development of software to provide practical guidance in the managing of a radiological emergency

International Nuclear Information System (INIS)

Ferreira Filho, Alfredo L.; Lima, Fernando R.A.; Loureiro, Eduardo C.M.

2008-01-01

One of the most important aspects of managing a radiological emergency is the ability to promptly and adequately determine and take actions to protect members of public and emergency workers. This work brings up to date a computer software program in Delphi, with the tools, generic procedures and the data necessary to support the Incident Commander, the Radiological Assessor and other members of a generic response organization in case of radiological accident. The aim is also to provide practical guidance for the first responders who will respond during the first few hours to a radiological emergency and for the national officials who would support this early response. Software is now based on the Manual for First Responders to a Radiological Emergency (EPR-First Responders), published in 2006 as part of the IAEA Emergency Preparedness and Response Series, as well as in the IAEA technical document, Generic Procedures for Assessment and Response during a Radiological Emergency, the IAEA-TECDOC-1162, taking account of the lessons learned from using this last document in the area of early response and first responders' actions. The proposed procedures provide action criteria that are clear, concise and predetermined, based on the present knowledge and the accumulated experiences, allowing the immediate decision-making. The objective is to provide, through a portable computer, practical guidance, in the form of action guides, instructions, and supporting data for emergency response that, if implemented, will provide a basic assessment and the response capability needed to protect public and workers in case of different types of radiological emergencies. In addition to appropriate protective action recommendations, it will also provide, when it is necessary, general guidance on the recovery of radioactive sources and initial cleanup operations. The philosophy is to keep the process simple and fast, yet effective. Software is available in Spanish, English and Portuguese

Software package as an information center product

International Nuclear Information System (INIS)

Butler, M.K.

1977-01-01

The Argonne Code Center serves as a software exchange and information center for the U.S. Energy Research and Development Administration and the Nuclear Regulatory Commission. The goal of the Center's program is to provide a means for sharing of software among agency offices and contractors, and for transferring computing applications and technology, developed within the agencies, to the information-processing community. A major activity of the Code Center is the acquisition, review, testing, and maintenance of a collection of software--computer systems, applications programs, subroutines, modules, and data compilations--prepared by agency offices and contractors to meet programmatic needs. A brief review of the history of computer program libraries and software sharing is presented to place the Code Center activity in perspective. The state-of-the-art discussion starts off with an appropriate definition of the term software package, together with descriptions of recommended package contents and the Carter's package evaluation activity. An effort is made to identify the various users of the product, to enumerate their individual needs, to document the Center's efforts to meet these needs and the ongoing interaction with the user community. Desirable staff qualifications are considered, and packaging problems, reviewed. The paper closes with a brief look at recent developments and a forecast of things to come. 2 tables

IT Project Management in Very Small Software Companies

DEFF Research Database (Denmark)

Shakir, Shahid Nadeem; Nørbjerg, Jacob

2013-01-01

In developing countries very small software companies (VSSCs) with only 1-10 employees play an important role both in the local economy and as providers of software and services to customers in other parts of the world. Understanding and improving their IT project management (ITPM) practices...... and challenges are, therefore, important in the local as well as the larger context of globalized software development. There is, however, very little research into small shop software practices in developing countries. The current paper explores actual ITPM practices in Pakistani VSSCs based on a qualitative...... study of seven Pakistani VSSCs. We find that some Pakistani ITPM practices are similar to what is reported from VSSCs in other parts of the world, while others seem to be related to the companies' position in the global software development chain. This paper is part of a larger research project aiming...

Open source IPSEC software in manned and unmanned space missions

Science.gov (United States)

Edwards, Jacob

Network security is a major topic of research because cyber attackers pose a threat to national security. Securing ground-space communications for NASA missions is important because attackers could endanger mission success and human lives. This thesis describes how an open source IPsec software package was used to create a secure and reliable channel for ground-space communications. A cost efficient, reproducible hardware testbed was also created to simulate ground-space communications. The testbed enables simulation of low-bandwidth and high latency communications links to experiment how the open source IPsec software reacts to these network constraints. Test cases were built that allowed for validation of the testbed and the open source IPsec software. The test cases also simulate using an IPsec connection from mission control ground routers to points of interest in outer space. Tested open source IPsec software did not meet all the requirements. Software changes were suggested to meet requirements.

On the Prospects and Concerns of Integrating Open Source Software Environment in Software Engineering Education

Science.gov (United States)

Kamthan, Pankaj

2007-01-01

Open Source Software (OSS) has introduced a new dimension in software community. As the development and use of OSS becomes prominent, the question of its integration in education arises. In this paper, the following practices fundamental to projects and processes in software engineering are examined from an OSS perspective: project management;…

The Impact of Software Culture on the Management of Community Data

Science.gov (United States)

Collins, J. A.; Pulsifer, P. L.; Sheffield, E.; Lewis, S.; Oldenburg, J.

2013-12-01

The Exchange for Local Observations and Knowledge of the Arctic (ELOKA), a program hosted at the National Snow and Ice Data Center (NSIDC), supports the collection, curation, and distribution of Local and Traditional Knowledge (LTK) data, as well as some quantitative data products. Investigations involving LTK data often involve community participation, and therefore require flexible and robust user interfaces to support a reliable process of data collection and management. Often, investigators focused on LTK and community-based monitoring choose to use ELOKA's data services based on our ability to provide rapid proof-of-concepts and economical delivery of a usable product. To satisfy these two overarching criteria, ELOKA is experimenting with modifications to its software development culture both in terms of how the software applications are developed as well as the kind of software applications (or components) being developed. Over the past several years, NSIDC has shifted its software development culture from one of assigning individual scientific programmers to support particular principal investigators or projects, to an Agile Software Methodology implementation using Scrum practices. ELOKA has participated in this process by working with other product owners to schedule and prioritize development work which is then implemented by a team of application developers. Scrum, along with practices such as Test Driven Development (TDD) and paired programming, improves the quality of the software product delivered to the user community. To meet the need for rapid prototyping and to maximize product development and support with limited developer input, our software development efforts are now focused on creating a platform of application modules that can be quickly customized to suit the needs of a variety of LTK projects. This approach is in contrast to the strategy of delivering custom applications for individual projects. To date, we have integrated components of

Automated Software Testing : A Study of the State of Practice

OpenAIRE

Rafi, Dudekula Mohammad; Reddy, Kiran Moses Katam

2012-01-01

Context: Software testing is expensive, labor intensive and consumes lot of time in a software development life cycle. There was always a need in software testing to decrease the testing time. This also resulted to focus on Automated Software Testing (AST), because using automated testing, with specific tools, this effort can be dramatically reduced and the costs related with testing can decrease [11]. Manual Testing (MT) requires lot of effort and hard work, if we measure in terms of person ...

The art of software modeling

CERN Document Server

Lieberman, Benjamin A

2007-01-01

Modeling complex systems is a difficult challenge and all too often one in which modelers are left to their own devices. Using a multidisciplinary approach, The Art of Software Modeling covers theory, practice, and presentation in detail. It focuses on the importance of model creation and demonstrates how to create meaningful models. Presenting three self-contained sections, the text examines the background of modeling and frameworks for organizing information. It identifies techniques for researching and capturing client and system information and addresses the challenges of presenting models to specific audiences. Using concepts from art theory and aesthetics, this broad-based approach encompasses software practices, cognitive science, and information presentation. The book also looks at perception and cognition of diagrams, view composition, color theory, and presentation techniques. Providing practical methods for investigating and organizing complex information, The Art of Software Modeling demonstrate...

Software for Optimizing Quality Assurance of Other Software

Science.gov (United States)

Feather, Martin; Cornford, Steven; Menzies, Tim

2004-01-01

Software assurance is the planned and systematic set of activities that ensures that software processes and products conform to requirements, standards, and procedures. Examples of such activities are the following: code inspections, unit tests, design reviews, performance analyses, construction of traceability matrices, etc. In practice, software development projects have only limited resources (e.g., schedule, budget, and availability of personnel) to cover the entire development effort, of which assurance is but a part. Projects must therefore select judiciously from among the possible assurance activities. At its heart, this can be viewed as an optimization problem; namely, to determine the allocation of limited resources (time, money, and personnel) to minimize risk or, alternatively, to minimize the resources needed to reduce risk to an acceptable level. The end result of the work reported here is a means to optimize quality-assurance processes used in developing software.

Supporting Usability Engineering in Small Software Development Organizations

DEFF Research Database (Denmark)

Bornoe, Nis; Stage, Jan

2013-01-01

Despite an interest and use of different usability engineering methods small software development organizations find it challenging to implement usability engineering into the software development process. We present the results from a study about usability engineering in practice. Through a series...... of semistructured interviews we want to get an understanding of how usability is implemented into the organizations and how it’s practiced in reality. We found that the developers found it problematic to combine agile software development methods with classic usability engineering methods. A lack of solid usability...... engineering expertise and not least experience seems to be a main obstacle for a successful implementation of usability engineering into current software development practices. They are requesting methods and procedures that fit better with their current practices and strategies to implement usability...

Regionalisation of general practice training--are we meeting the needs of rural Australia?

Science.gov (United States)

Campbell, David G; Greacen, Jane H; Giddings, Patrick H; Skinner, Lesley P

2011-06-06

The concept of "social accountability" has underpinned the development of many medical education programs over the past decade. Success of the regionalisation of the general practice training program in Australia will ultimately be measured by the ability of the program to deliver a sufficient rural general practice workforce to meet the health needs of rural communities. Regionalisation of general practice training in Australia arose from the 1998 recommendations of the Ministerial Review of General Practice Training. The resultant competitive structure adopted by government was not the preferred option of the Review Committee, and may be a negative influence on rural workforce, as the competitive corporate structure of regional training providers has created barriers to meaningful vertical integration. Available data suggest that the regionalised training program is not yet providing a sustainable general practice workforce to rural Australia. The current increase in medical student and general practice training places provides an opportunity to address some of these issues. In particular, it is recommended that changes be made to registrar selection processes, the rural pipeline and vertical integration of training, and training for procedural rural practice. To achieve these goals, perhaps it is time for another comprehensive ministerial review of general practice training in Australia.

Developing Software Simulations

Directory of Open Access Journals (Sweden)

Tom Hall

2007-06-01

Full Text Available Programs in education and business often require learners to develop and demonstrate competence in specified areas and then be able to effectively apply this knowledge. One method to aid in developing a skill set in these areas is through the use of software simulations. These simulations can be used for learner demonstrations of competencies in a specified course as well as a review of the basic skills at the beginning of subsequent courses. The first section of this paper discusses ToolBook, the software used to develop our software simulations. The second section discusses the process of developing software simulations. The third part discusses how we have used software simulations to assess student knowledge of research design by providing simulations that allow the student to practice using SPSS and Excel.

SAGA: A project to automate the management of software production systems

Science.gov (United States)

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.

Laboratory and software applications for clinical trials: the global laboratory environment.

Science.gov (United States)

Briscoe, Chad

2011-11-01

The Applied Pharmaceutical Software Meeting is held annually. It is sponsored by The Boston Society, a not-for-profit organization that coordinates a series of meetings within the global pharmaceutical industry. The meeting generally focuses on laboratory applications, but in recent years has expanded to include some software applications for clinical trials. The 2011 meeting emphasized the global laboratory environment. Global clinical trials generate massive amounts of data in many locations that must be centralized and processed for efficient analysis. Thus, the meeting had a strong focus on establishing networks and systems for dealing with the computer infrastructure to support such environments. In addition to the globally installed laboratory information management system, electronic laboratory notebook and other traditional laboratory applications, cloud computing is quickly becoming the answer to provide efficient, inexpensive options for managing the large volumes of data and computing power, and thus it served as a central theme for the meeting.

CFD analyses in regulatory practice

International Nuclear Information System (INIS)

Bloemeling, F.; Pandazis, P.; Schaffrath, A.

2012-01-01

Numerical software is used in nuclear regulatory procedures for many problems in the fields of neutron physics, structural mechanics, thermal hydraulics etc. Among other things, the software is employed in dimensioning and designing systems and components and in simulating transients and accidents. In nuclear technology, analyses of this kind must meet strict requirements. Computational Fluid Dynamics (CFD) codes were developed for computing multidimensional flow processes of the type occurring in reactor cooling systems or in containments. Extensive experience has been accumulated by now in selected single-phase flow phenomena. At the present time, there is a need for development and validation with respect to the simulation of multi-phase and multi-component flows. As insufficient input by the user can lead to faulty results, the validity of the results and an assessment of uncertainties are guaranteed only through consistent application of so-called Best Practice Guidelines. The authors present the possibilities now available to CFD analyses in nuclear regulatory practice. This includes a discussion of the fundamental requirements to be met by numerical software, especially the demands upon computational analysis made by nuclear rules and regulations. In conclusion, 2 examples are presented of applications of CFD analysis to nuclear problems: Determining deboration in the condenser reflux mode of operation, and protection of the reactor pressure vessel (RPV) against brittle failure. (orig.)

An Assessment of risk response strategies practiced in software projects

Directory of Open Access Journals (Sweden)

Vanita Bhoola

2014-11-01

Full Text Available Risk management and success in projects are highly intertwined – better approaches to project risk management tend to increase chances of project success in terms of achieving scope & quality, schedule and cost targets. The process of responding to risk factors during a project’s life cycle is a crucial aspect of risk management referred to as risk response strategies, in this paper. The current research explores the status of risk response strategies applied in the software development projects in India. India provides a young IT-savvy English-speaking population, which is also cost effective. Other than the workforce, the environment for implementation of software projects in India is different from the matured economies. Risk management process is a commonly discussed theme, though its implementation in practice has a huge scope for improvement in India. The paper talks about four fundamental treatments to risk response – Avoidance, Transference, Mitigation and Acceptance (ATMA. From a primary data of 302 project managers, the paper attempts to address the risk response factors that lead to successful achievement of project scope & quality, schedule and cost targets, by using a series of regressions followed with Seemingly Unrelated Regression Equations (SURE modelling. Mitigation emerged as the most significant risk response strategy to achieve project targets. Acceptance, transference, and avoidance of risk were mostly manifested in the forms of transparency in communication across stakeholders, careful study of the nature of risks and close coordination between project team, customers/end-users and top management.

Incorporating Gaming in Software Engineering Projects: Case of RMU Monopoly

Directory of Open Access Journals (Sweden)

Sushil Acharya

2009-02-01

Full Text Available A major challenge in engineering education is retaining student interest in the engineering discipline. Active student involvement in engineering projects is one way of retaining student interest. Such involvement can only be realized if project inception comes entirely from the student. This paper presents a software game, RMU Monopoly, developed as a project requirement for a software engineering course and describes the challenges and gains of implementing such a project. The RMU Monopoly was proposed by three junior software engineering students. The game is a multi-platform software program that allows up to eight players and implements the rules of the Monopoly board game. To ensure agility the game was developed using the spiral software development model. The Software Requirements Specification (SRS document was finalized through an iterative procedure. Standard Unified Modeling Language (UML diagrams were used for product design. A Risk Mitigation, Monitoring, and Management Plan (RMMM was developed to ensure proactive risk management. Gantt chart, weekly progress meetings and weekly scrum meetings were used to track project progress. C# and Sub- Version were used in a client-server architecture to develop the software. The project was successful in retaining student interest in the software engineering discipline

KAERI software safety guideline for developing safety-critical software in digital instrumentation and control system of nuclear power plant

International Nuclear Information System (INIS)

Lee, Jang Soo; Kim, Jang Yeol; Eum, Heung Seop.

1997-07-01

Recently, the safety planning for safety-critical software systems is being recognized as the most important phase in the software life cycle, and being developed new regulatory positions and standards by the regulatory and the standardization organization. The requirements for software important to safety of nuclear reactor are described in such positions and standards. Most of them are describing mandatory requirements, what shall be done, for the safety-critical software. The developers of such a software. However, there have been a lot of controversial factors on whether the work practices satisfy the regulatory requirements, and to justify the safety of such a system developed by the work practices, between the licenser and the licensee. We believe it is caused by the reason that there is a gap between the mandatory requirements (What) and the work practices (How). We have developed a guidance to fill such gap, which can be useful for both licenser and licensee to conduct a justification of the safety in the planning phase of developing the software for nuclear reactor protection systems. (author). 67 refs., 13 tabs., 2 figs

KAERI software safety guideline for developing safety-critical software in digital instrumentation and control system of nuclear power plant

Energy Technology Data Exchange (ETDEWEB)

Lee, Jang Soo; Kim, Jang Yeol; Eum, Heung Seop

1997-07-01

Recently, the safety planning for safety-critical software systems is being recognized as the most important phase in the software life cycle, and being developed new regulatory positions and standards by the regulatory and the standardization organization. The requirements for software important to safety of nuclear reactor are described in such positions and standards. Most of them are describing mandatory requirements, what shall be done, for the safety-critical software. The developers of such a software. However, there have been a lot of controversial factors on whether the work practices satisfy the regulatory requirements, and to justify the safety of such a system developed by the work practices, between the licenser and the licensee. We believe it is caused by the reason that there is a gap between the mandatory requirements (What) and the work practices (How). We have developed a guidance to fill such gap, which can be useful for both licenser and licensee to conduct a justification of the safety in the planning phase of developing the software for nuclear reactor protection systems. (author). 67 refs., 13 tabs., 2 figs.

Infusing Software Engineering Technology into Practice at NASA

Science.gov (United States)

Pressburger, Thomas; Feather, Martin S.; Hinchey, Michael; Markosia, Lawrence

2006-01-01

We present an ongoing effort of the NASA Software Engineering Initiative to encourage the use of advanced software engineering technology on NASA projects. Technology infusion is in general a difficult process yet this effort seems to have found a modest approach that is successful for some types of technologies. We outline the process and describe the experience of the technology infusions that occurred over a two year period. We also present some lessons from the experiences.

A conceptual framework to study the role of communication through social software for coordination in globally-distributed software teams

DEFF Research Database (Denmark)

Giuffrida, Rosalba; Dittrich, Yvonne

2015-01-01

Background In Global Software Development (GSD) the lack of face-to-face communication is a major challenge and effective computer-mediated practices are necessary to mitigate the effect of physical distance. Communication through Social Software (SoSo) supports team coordination, helping to deal...... with geographical distance; however, in Software Engineering literature, there is a lack of suitable theoretical concepts to analyze and describe everyday practices of globally-distributed software development teams and to study the role of communication through SoSo. Objective The paper proposes a theoretical...... framework for analyzing how communicative and coordinative practices are constituted and maintained in globally-distributed teams. Method The framework is based on the concepts of communicative genres and coordination mechanisms; it is motivated and explicated through examples from two qualitative empirical...

Software Process Improvement Defined

DEFF Research Database (Denmark)

Aaen, Ivan

2002-01-01

This paper argues in favor of the development of explanatory theory on software process improvement. The last one or two decades commitment to prescriptive approaches in software process improvement theory may contribute to the emergence of a gulf dividing theorists and practitioners....... It is proposed that this divide be met by the development of theory evaluating prescriptive approaches and informing practice with a focus on the software process policymaking and process control aspects of improvement efforts...

Bringing Model Checking Closer to Practical Software Engineering

CERN Document Server

AUTHOR|(CDS)2079681; Templon, J A; Willemse, T.A.C.

Software grows in size and complexity, making it increasingly challenging to ensure that it behaves correctly. This is especially true for distributed systems, where a multitude of components are running concurrently, making it dicult to anticipate all the possible behaviors emerging in the system as a whole. Certain design errors, such as deadlocks and race-conditions, can often go unnoticed when testing is the only form of verication employed in the software engineering life-cycle. Even when bugs are detected in a running software, revealing the root cause and reproducing the behavior can be time consuming (and even impossible), given the lack of control the engineer has over the execution of the concurrent components, as well as the number of possible scenarios that could have produced the problem. This is especially pronounced for large-scale distributed systems such as the Worldwide Large Hadron Collider Computing Grid. Formal verication methods oer more rigorous means of determining whether a system sat...

Software development methodologies and practices in startups:systematic literature review

OpenAIRE

Tegegne, E. (Esubalew)

2018-01-01

Abstract Startups are newly created companies with little or no operating history and with limited resources and markets. Software startup are aiming to develop cutting edge software products under highly uncertain conditions, overcoming fast-growing markets under multiple influences. The significance of startups for economic development is growing in software business due to their ability to quickly create innovative techn...

HPCMP CREATE (trademark)-AV Quality Assurance: Best Practices for Validating and Supporting Computation-Based Engineering Software

Science.gov (United States)

2015-09-30

30/2015 Oct 2008-Sep 2015 HPCMP CREATE™- AV Quality Assurance: Best Practices for Validating and Supporting Computation-Based Engineering Software...2) “Does this tool adequately perform any and all advertised capabilities?” This paper will describe how the HPCMP CREATE Air Vehicles ( AV ...discussed and their strengths and weaknesses within the CREATE- AV framework addressed. Work toward the HPCMP CREATE, Quality Assurance, Aviation

Software Reviews.

Science.gov (United States)

Miller, Anne, Ed.; Radziemski, Cathy, Ed.

1988-01-01

Three pieces of computer software are described and reviewed: HyperCard, to build and use varied applications; Iggy's Gnees, for problem solving with shapes in grades kindergarten-two; and Algebra Shop, for practicing skills and problem solving. (MNS)

Ready! Set! Go! An Action Research Agenda for Software Architecture

DEFF Research Database (Denmark)

Christensen, Henrik Bærbak; Hansen, Klaus Marius; Schougaard, Kari Rye

2008-01-01

Software architecture practice is highly complex. Software architects interact with business as well as technical aspects of systems, often embedded in large and changing organizations. We first make an argument that an appropriate research agenda for understanding, describing, and changing...... architectural practice in this context is based on an action research agenda in which researchers use ethnographic techniques to understand practice and engages directly with and in practice when proposing and designing new practices. Secondly, we present an overview of an ongoing project which applies action...... research techniques to understand and potentially change architectural practice in four Danish software companies....

Using ethnographic methods in software engineering research

DEFF Research Database (Denmark)

Sharp, Helen, C.; Dittrich, Yvonne; De Souza, Cleidson

2010-01-01

This tutorial provides an overview of the role of ethnography in Software Engineering research. It describes the use of ethnographic methods as a means to provide an in-depth understanding of the socio-technological realities surrounding everyday software development practice. The knowledge gained......-depth discussion of methods for data collection and analysis used in ethnographic studies. It then describes how these methods can be and have been used by software engineering researchers to understand developers' work practices, to inform the development of processes, methods and tools and to evaluate...... can be used to improve processes, methods and tools as well as develop observed industrial practices. The tutorial begins with a brief historical account of ethnography in the fields of Software Engineering, CSCW, Information Systems and other related areas. This sets the stage for a more in...

Simple solution to the medical instrumentation software problem

Science.gov (United States)

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.

Good analytical practice in the analysis of IAEA materials for certification. Report of a consultants' meeting

International Nuclear Information System (INIS)

1999-01-01

The purpose of this Consultant's Meeting report was to provide basic guidelines to the analysts involved in IAEA certification analysis for IAEA-392 and IAEA-393 Algae Reference Materials and to harmonise the analytical approach. The experience of this exercise will be combined with the requirements of ISO Guide 34 and 35 and should be the basis for a planned guide book on this topic. The Meeting was focused on on the practical implementation of the quality requirements for Reference Material analysis and certification procedures from ISO Guide 34 and ISO Guide 35

Observation-Driven Configuration of Complex Software Systems

Science.gov (United States)

Sage, Aled

2010-06-01

The ever-increasing complexity of software systems makes them hard to comprehend, predict and tune due to emergent properties and non-deterministic behaviour. Complexity arises from the size of software systems and the wide variety of possible operating environments: the increasing choice of platforms and communication policies leads to ever more complex performance characteristics. In addition, software systems exhibit different behaviour under different workloads. Many software systems are designed to be configurable so that policies can be chosen to meet the needs of various stakeholders. For complex software systems it can be difficult to accurately predict the effects of a change and to know which configuration is most appropriate. This thesis demonstrates that it is useful to run automated experiments that measure a selection of system configurations. Experiments can find configurations that meet the stakeholders' needs, find interesting behavioural characteristics, and help produce predictive models of the system's behaviour. The design and use of ACT (Automated Configuration Tool) for running such experiments is described, in combination a number of search strategies for deciding on the configurations to measure. Design Of Experiments (DOE) is discussed, with emphasis on Taguchi Methods. These statistical methods have been used extensively in manufacturing, but have not previously been used for configuring software systems. The novel contribution here is an industrial case study, applying the combination of ACT and Taguchi Methods to DC-Directory, a product from Data Connection Ltd (DCL). The case study investigated the applicability of Taguchi Methods for configuring complex software systems. Taguchi Methods were found to be useful for modelling and configuring DC- Directory, making them a valuable addition to the techniques available to system administrators and developers.

Computer software configuration management

International Nuclear Information System (INIS)

Pelletier, G.

1987-08-01

This report reviews the basic elements of software configuration management (SCM) as defined by military and industry standards. Several software configuration management standards are evaluated given the requirements of the nuclear industry. A survey is included of available automated tools for supporting SCM activities. Some information is given on the experience of establishing and using SCM plans of other organizations that manage critical software. The report concludes with recommendations of practices that would be most appropriate for the nuclear power industry in Canada

Taking minutes of meetings

CERN Document Server

Gutmann, Joanna

2016-01-01

aking Minutes of Meetings guides you through the entire process behind minute taking: arranging the meeting; writing the agenda; creating the optimum environment; structuring the meeting and writing notes up accurately. The minute-taker is one of the most important and powerful people in a meeting and you can use this opportunity to develop your knowledge, broaden your horizons and build credibility within the organization. Taking Minutes of Meetings is an easy to read 'dip-in, dip-out' guide which shows you how to confidently arrange meetings and produce minutes. It provides hands-on advice about the sections of a meeting as well as tips on how to create an agenda, personal preparation, best practice advice on taking notes and how to improve your accuracy. Brand new chapters of this 4th edition include guidance on using technology to maximize effectiveness and practical help with taking minutes for a variety of different types of meetings. The creating success series of books... With over one million copi...

Large-scale visualization projects for teaching software engineering.

Science.gov (United States)

Müller, Christoph; Reina, Guido; Burch, Michael; Weiskopf, Daniel

2012-01-01

The University of Stuttgart's software engineering major complements the traditional computer science major with more practice-oriented education. Two-semester software projects in various application areas offered by the university's different computer science institutes are a successful building block in the curriculum. With this realistic, complex project setting, students experience the practice of software engineering, including software development processes, technologies, and soft skills. In particular, visualization-based projects are popular with students. Such projects offer them the opportunity to gain profound knowledge that would hardly be possible with only regular lectures and homework assignments.

Assuring Software Cost Estimates: Is it an Oxymoron?

Science.gov (United States)

Hihn, Jarius; Tregre, Grant

2013-01-01

The software industry repeatedly observes cost growth of well over 100% even after decades of cost estimation research and well-known best practices, so "What's the problem?" In this paper we will provide an overview of the current state oj software cost estimation best practice. We then explore whether applying some of the methods used in software assurance might improve the quality of software cost estimates. This paper especially focuses on issues associated with model calibration, estimate review, and the development and documentation of estimates as part alan integrated plan.

Storage system software solutions for high-end user needs

Science.gov (United States)

Hogan, Carole B.

1992-01-01

Today's high-end storage user is one that requires rapid access to a reliable terabyte-capacity storage system running in a distributed environment. This paper discusses conventional storage system software and concludes that this software, designed for other purposes, cannot meet high-end storage requirements. The paper also reviews the philosophy and design of evolving storage system software. It concludes that this new software, designed with high-end requirements in mind, provides the potential for solving not only the storage needs of today but those of the foreseeable future as well.

Software process improvement, quality assurance and measurement

NARCIS (Netherlands)

Trienekens, J.J.M.; Kusters, R.J.; Balla, K.; Kontogiannis, K.; Zou, Y.; Di Penta, M.

2006-01-01

The aim of this workshop was to present and discuss emergent software quality improvement approaches, with an emphasis on practical applications. Different views on the improvement of software processes, software products, and their interrelations, have been addressed during the workshop.

The 7 C's for Creating Living Software: A Research Perspective for Quality-Oriented Software Engineering

NARCIS (Netherlands)

Aksit, Mehmet

2004-01-01

This article proposes the 7 C's for realizing quality-oriented software engineering practices. All the desired qualities of this approach are expressed in short by the term living software. The 7 C's are: Concern-oriented processes, Canonical models, Composable models, Certifiable models,

IOM and DHHS meeting on making clinical practice guidelines appropriate for patients with multiple chronic conditions.

Science.gov (United States)

Goodman, Richard A; Boyd, Cynthia; Tinetti, Mary E; Von Kohorn, Isabelle; Parekh, Anand K; McGinnis, J Michael

2014-01-01

The increasing prevalence of Americans with multiple (2 or more) chronic conditions raises concerns about the appropriateness and applicability of clinical practice guidelines for patient management. Most guidelines clinicians currently rely on have been designed with a single chronic condition in mind, and many such guidelines are inattentive to issues related to comorbidities. In response to the need for guideline developers to address comorbidities in guidelines, the Department of Health and Human Services convened a meeting in May 2012 in partnership with the Institute of Medicine to identify principles and action options. Eleven principles to improve guidelines' attentiveness to the population with multiple chronic conditions were identified during the meeting. They are grouped into 3 interrelated categories: (1) principles intended to improve the stakeholder technical process for developing guidelines; (2) principles intended to strengthen content of guidelines in terms of multiple chronic conditions; and (3) principles intended to increase focus on patient-centered care. This meeting built upon previously recommended actions by identifying additional principles and options for government, guideline developers, and others to use in strengthening the applicability of clinical practice guidelines to the growing population of people with multiple chronic conditions. The suggested principles are helping professional societies to improve guidelines' attentiveness to persons with multiple chronic conditions.

1251 seed calibration using afterloading equipment SeedSelectron. Practical solution to meet the recommendations of the AAPM

International Nuclear Information System (INIS)

Perez-Calatayud, J.; Richart, J.; Perez-Garcia, J.; Guirado, D.; Ballester, F.; Rodriguez, S.; Santos, M.; Depiaggio, M.; Carmona, V.; Lliso, F.; Camacho, C.; Pujades, M. C.

2011-01-01

SeedSelectron is a system used in the afterloader permanent implant brachytherapy seeds 1-125 interstitial prostate. Two aspects are critical when you can meet the recommendations of the AAPM: a practical difficulty to check the quantity of seed required, and the great uncertainty of all measured diodes. The purpose of this paper is to present a practical solution that has been adopted to implement the recommendations of the AAPM

Applying Agile MethodstoWeapon/Weapon-Related Software

Energy Technology Data Exchange (ETDEWEB)

Adams, D; Armendariz, M; Blackledge, M; Campbell, F; Cloninger, M; Cox, L; Davis, J; Elliott, M; Granger, K; Hans, S; Kuhn, C; Lackner, M; Loo, P; Matthews, S; Morrell, K; Owens, C; Peercy, D; Pope, G; Quirk, R; Schilling, D; Stewart, A; Tran, A; Ward, R; Williamson, M

2007-05-02

This white paper provides information and guidance to the Department of Energy (DOE) sites on Agile software development methods and the impact of their application on weapon/weapon-related software development. The purpose of this white paper is to provide an overview of Agile methods, examine the accepted interpretations/uses/practices of these methodologies, and discuss the applicability of Agile methods with respect to Nuclear Weapons Complex (NWC) Technical Business Practices (TBPs). It also provides recommendations on the application of Agile methods to the development of weapon/weapon-related software.

16 CFR 240.14 - Meeting competition.

Science.gov (United States)

2010-01-01

... 16 Commercial Practices 1 2010-01-01 2010-01-01 false Meeting competition. 240.14 Section 240.14 Commercial Practices FEDERAL TRADE COMMISSION GUIDES AND TRADE PRACTICE RULES GUIDES FOR ADVERTISING ALLOWANCES AND OTHER MERCHANDISING PAYMENTS AND SERVICES § 240.14 Meeting competition. A seller charged with...

Open-source software gets boost at UN

CERN Multimedia

Schenker, J L

2003-01-01

"A months-long backroom battle led by Brazil, with support from India, South Africa and China, against the United States over open-source software took center stage Wednesday at the UN information summit meeting" (1 page)

An engineering context for software engineering

OpenAIRE

Riehle, Richard D.

2008-01-01

New engineering disciplines are emerging in the late Twentieth and early Twenty-first Century. One such emerging discipline is software engineering. The engineering community at large has long harbored a sense of skepticism about the validity of the term software engineering. During most of the fifty-plus years of software practice, that skepticism was probably justified. Professional education of software developers often fell short of the standard expected for conventional engineers; so...

Theory Meets Practice

DEFF Research Database (Denmark)

Schlamovitz, Jesper

2015-01-01

Process thinking and process-based theory are receiving increased attention in the field of organization studies and organization theory development (Tsoukas & Chia, 2002; Langley & Tsoukas, 2010; Hernes, 2014). The aim has been to study processes rather than structures, in organizations. This has...... recently inspired research on the organizing of projects and the development of a (new) theory of temporary organizations (Bakker, 2010; Blomquist et al. 2010; Söderlund, 2013). These theories are still under development and need empirical studies that can show their relevance for practice. This paper...... will give an overview of this theoretical development and discuss the consequences for the practice of project management. The paper finds that the focus on processes such as time and temporality, meaning structures, and articulation are covered in project management research, but sparsely documented...

SWiFT Software Quality Assurance Plan.

Energy Technology Data Exchange (ETDEWEB)

Berg, Jonathan Charles [Sandia National Lab. (SNL-NM), Albuquerque, NM (United States)

2016-01-01

This document describes the software development practice areas and processes which contribute to the ability of SWiFT software developers to provide quality software. These processes are designed to satisfy the requirements set forth by the Sandia Software Quality Assurance Program (SSQAP). APPROVALS SWiFT Software Quality Assurance Plan (SAND2016-0765) approved by: Department Manager SWiFT Site Lead Dave Minster (6121) Date Jonathan White (6121) Date SWiFT Controls Engineer Jonathan Berg (6121) Date CHANGE HISTORY Issue Date Originator(s) Description A 2016/01/27 Jon Berg (06121) Initial release of the SWiFT Software Quality Assurance Plan

Software Certification - Coding, Code, and Coders

Science.gov (United States)

Havelund, Klaus; Holzmann, Gerard J.

2011-01-01

We describe a certification approach for software development that has been adopted at our organization. JPL develops robotic spacecraft for the exploration of the solar system. The flight software that controls these spacecraft is considered to be mission critical. We argue that the goal of a software certification process cannot be the development of "perfect" software, i.e., software that can be formally proven to be correct under all imaginable and unimaginable circumstances. More realistically, the goal is to guarantee a software development process that is conducted by knowledgeable engineers, who follow generally accepted procedures to control known risks, while meeting agreed upon standards of workmanship. We target three specific issues that must be addressed in such a certification procedure: the coding process, the code that is developed, and the skills of the coders. The coding process is driven by standards (e.g., a coding standard) and tools. The code is mechanically checked against the standard with the help of state-of-the-art static source code analyzers. The coders, finally, are certified in on-site training courses that include formal exams.

Criteria for software modularization

Science.gov (United States)

Card, David N.; Page, Gerald T.; Mcgarry, Frank E.

1985-01-01

A central issue in programming practice involves determining the appropriate size and information content of a software module. This study attempted to determine the effectiveness of two widely used criteria for software modularization, strength and size, in reducing fault rate and development cost. Data from 453 FORTRAN modules developed by professional programmers were analyzed. The results indicated that module strength is a good criterion with respect to fault rate, whereas arbitrary module size limitations inhibit programmer productivity. This analysis is a first step toward defining empirically based standards for software modularization.

Reflective approach for software design decision making

NARCIS (Netherlands)

Razavian, M.; Tang, A.; Capilla, R.; Lago, P.

2016-01-01

Good software design practice is difficult to define and teach. Despite the many software design methods and processes that are available, the quality of software design relies on human factors. We notice from literature and our own experiments that some of these factors concern design reasoning and

Common Practices from Two Decades of Water Resources Modelling Published in Environmental Modelling & Software: 1997 to 2016

Science.gov (United States)

Ames, D. P.; Peterson, M.; Larsen, J.

2016-12-01

A steady flow of manuscripts describing integrated water resources management (IWRM) modelling has been published in Environmental Modelling & Software since the journal's inaugural issue in 1997. These papers represent two decades of peer-reviewed scientific knowledge regarding methods, practices, and protocols for conducting IWRM. We have undertaken to explore this specific assemblage of literature with the intention of identifying commonly reported procedures in terms of data integration methods, modelling techniques, approaches to stakeholder participation, means of communication of model results, and other elements of the model development and application life cycle. Initial results from this effort will be presented including a summary of commonly used practices, and their evolution over the past two decades. We anticipate that results will show a pattern of movement toward greater use of both stakeholder/participatory modelling methods as well as increased use of automated methods for data integration and model preparation. Interestingly, such results could be interpreted to show that the availability of better, faster, and more integrated software tools and technologies free the modeler to take a less technocratic and more human approach to water resources modelling.

Ten recommendations for software engineering in research.

Science.gov (United States)

Hastings, Janna; Haug, Kenneth; Steinbeck, Christoph

2014-01-01

Research in the context of data-driven science requires a backbone of well-written software, but scientific researchers are typically not trained at length in software engineering, the principles for creating better software products. To address this gap, in particular for young researchers new to programming, we give ten recommendations to ensure the usability, sustainability and practicality of research software.

RT-Syn: A real-time software system generator

Science.gov (United States)

Setliff, Dorothy E.

1992-01-01

This paper presents research into providing highly reusable and maintainable components by using automatic software synthesis techniques. This proposal uses domain knowledge combined with automatic software synthesis techniques to engineer large-scale mission-critical real-time software. The hypothesis centers on a software synthesis architecture that specifically incorporates application-specific (in this case real-time) knowledge. This architecture synthesizes complex system software to meet a behavioral specification and external interaction design constraints. Some examples of these external constraints are communication protocols, precisions, timing, and space limitations. The incorporation of application-specific knowledge facilitates the generation of mathematical software metrics which are used to narrow the design space, thereby making software synthesis tractable. Success has the potential to dramatically reduce mission-critical system life-cycle costs not only by reducing development time, but more importantly facilitating maintenance, modifications, and extensions of complex mission-critical software systems, which are currently dominating life cycle costs.

Safety review on unit testing of safety system software of nuclear power plant

International Nuclear Information System (INIS)

Liu Le; Zhang Qi

2013-01-01

Software unit testing has an important place in the testing of safety system software of nuclear power plants, and in the wider scope of the verification and validation. It is a comprehensive, systematic process, and its documentation shall meet the related requirements. When reviewing software unit testing, attention should be paid to the coverage of software safety requirements, the coverage of software internal structure, and the independence of the work. (authors)

Practicing What We Teach: Adherence to Healthy Meeting Guidelines at Extension Meetings and Events

Directory of Open Access Journals (Sweden)

Carol A. Smathers

2018-02-01

Full Text Available Cooperative Extension promotes healthy behaviors, including nutritious eating and physical activity. Research-based healthy meeting guidelines pertaining to foods and beverages served at Extension-sponsored events have been adopted in some states. The extent of adherence to Healthy Eating at Meetings guidelines was assessed by observing foods and beverages served at Extension-sponsored events across one state. Over a four-month period, 69 events involving foods and/or beverages were observed, including 33 events on a state university’s campus and 46 events across 36 counties. Observed events included meetings, workshops and conferences for faculty and staff, agricultural trainings and field days for the public, 4-H camps and special activities for youth and their families, and county and state fair events. Photos and menus of the foods and beverages served were assessed using a seven-item scorecard based on the Healthy Eating at Meetings guidelines. The average score for adherence to the guidelines was 57%, with a range of 10%-93%. Results suggest that adopting healthy meeting guidelines may not be enough to ensure that nutritious foods are served and that healthy eating is modeled at Extension-sponsored events. This study indicates that further research to explore Extension professionals’ knowledge of and attitudes toward healthy meeting guidelines is needed.

IT Software Development and IT Operations Strategic Alignment: An Agile DevOps Model

Science.gov (United States)

Hart, Michael

2017-01-01

Information Technology (IT) departments that include development and operations are essential to develop software that meet customer needs. DevOps is a term originally constructed from software development and IT operations. DevOps includes the collaboration of all stakeholders such as software engineers and systems administrators involved in the…

Safety certification of airborne software: An empirical study

International Nuclear Information System (INIS)

Dodd, Ian; Habli, Ibrahim

2012-01-01

Many safety-critical aircraft functions are software-enabled. Airborne software must be audited and approved by the aerospace certification authorities prior to deployment. The auditing process is time-consuming, and its outcome is unpredictable, due to the criticality and complex nature of airborne software. To ensure that the engineering of airborne software is systematically regulated and is auditable, certification authorities mandate compliance with safety standards that detail industrial best practice. This paper reviews existing practices in software safety certification. It also explores how software safety audits are performed in the civil aerospace domain. The paper then proposes a statistical method for supporting software safety audits by collecting and analysing data about the software throughout its lifecycle. This method is then empirically evaluated through an industrial case study based on data collected from 9 aerospace projects covering 58 software releases. The results of this case study show that our proposed method can help the certification authorities and the software and safety engineers to gain confidence in the certification readiness of airborne software and predict the likely outcome of the audits. The results also highlight some confidentiality issues concerning the management and retention of sensitive data generated from safety-critical projects.

Adopting to Agile Software Development

Directory of Open Access Journals (Sweden)

Linkevics Gusts

2014-12-01

Full Text Available Agile software development can be made successful, but there is no well-defined way how to achieve this. The problem is that the successful adoption of agile methods and practices is a complex process and this process should be customizable for a particular organization or a team. This research focuses on identification of agile methods and practices. Result of the research is the ranking of agile methods, practices and their usage trends. As some terms of agile software development are interpreted differently in different organizations and teams, terminology used is analyzed. Results of the research can be used as a reference material for those who are planning to adopt agile methods or are looking for the next agile practice to implement. Results will be used for the development of an expert system to support agile adoption.

Software project effort estimation foundations and best practice guidelines for success

CERN Document Server

Trendowicz, Adam

2014-01-01

Software effort estimation is one of the oldest and most important problems in software project management, and thus today there are a large number of models, each with its own unique strengths and weaknesses in general, and even more importantly, in relation to the environment and context in which it is to be applied.Trendowicz and Jeffery present a comprehensive look at the principles of software effort estimation and support software practitioners in systematically selecting and applying the most suitable effort estimation approach. Their book not only presents what approach to take and how

Characterizing the Development and Usage of Diagrams in Embedded Software Systems

NARCIS (Netherlands)

Akdur, Deniz; Demirörs, Onur; Garousi, V.

2017-01-01

To cope with growing complexity of embedded software, modeling has become popular. The usage of models in embedded software industry and the relevant practices usually vary since the purposes of diagram development and usage differ. Since a large variety of software modeling practices used in

Software Authentication

International Nuclear Information System (INIS)

Wolford, J.K.; Geelhood, B.D.; Hamilton, V.A.; Ingraham, J.; MacArthur, D.W.; Mitchell, D.J.; Mullens, J.A.; Vanier, P. E.; White, G.K.; Whiteson, R.

2001-01-01

The effort to define guidance for authentication of software for arms control and nuclear material transparency measurements draws on a variety of disciplines and has involved synthesizing established criteria and practices with newer methods. Challenges include the need to protect classified information that the software manipulates as well as deal with the rapid pace of innovation in the technology of nuclear material monitoring. The resulting guidance will shape the design of future systems and inform the process of authentication of instruments now being developed. This paper explores the technical issues underlying the guidance and presents its major tenets

A 'Toolbox' Equivalent Process for Safety Analysis Software

International Nuclear Information System (INIS)

O'Kula, K.R.; Eng, Tony

2004-01-01

Defense Nuclear Facilities Safety Board (DNFSB) Recommendation 2002-1 (Quality Assurance for Safety-Related Software) identified a number of quality assurance issues on the use of software in Department of Energy (DOE) facilities for analyzing hazards, and designing and operating controls that prevent or mitigate potential accidents. The development and maintenance of a collection, or 'toolbox', of multiple-site use, standard solution, Software Quality Assurance (SQA)-compliant safety software is one of the major improvements identified in the associated DOE Implementation Plan (IP). The DOE safety analysis toolbox will contain a set of appropriately quality-assured, configuration-controlled, safety analysis codes, recognized for DOE-broad, safety basis applications. Currently, six widely applied safety analysis computer codes have been designated for toolbox consideration. While the toolbox concept considerably reduces SQA burdens among DOE users of these codes, many users of unique, single-purpose, or single-site software may still have sufficient technical justification to continue use of their computer code of choice, but are thwarted by the multiple-site condition on toolbox candidate software. The process discussed here provides a roadmap for an equivalency argument, i.e., establishing satisfactory SQA credentials for single-site software that can be deemed ''toolbox-equivalent''. The process is based on the model established to meet IP Commitment 4.2.1.2: Establish SQA criteria for the safety analysis ''toolbox'' codes. Implementing criteria that establish the set of prescriptive SQA requirements are based on implementation plan/procedures from the Savannah River Site, also incorporating aspects of those from the Waste Isolation Pilot Plant (SNL component) and the Yucca Mountain Project. The major requirements are met with evidence of a software quality assurance plan, software requirements and design documentation, user's instructions, test report, a

Implementing Large Projects in Software Engineering Courses

Science.gov (United States)

Coppit, David

2006-01-01

In software engineering education, large projects are widely recognized as a useful way of exposing students to the real-world difficulties of team software development. But large projects are difficult to put into practice. First, educators rarely have additional time to manage software projects. Second, classrooms have inherent limitations that…

The software architecture of the real-time on-line decision support system 'RODOS'

International Nuclear Information System (INIS)

Rafat, M.; Schuele, O.

1998-01-01

The RODOS project aims at the development of an integrated and comprehensive real-time on-line decision support system for off-site emergency management of nuclear accidents in Europe, applicable for the vicinity of the release and the early phase up to far distant areas and the later stages of an accident. The architecture of the RODOS software framework is described as a tool for processing and managing a large variety of different types of information, including those which are categorized in terms of meteorology, radiology, economy, emergency actions and countermeasures, rules, preferences, facts, maps, statistics, catalogues, models and methods. The conceptual design of the software structure based on the Client-Server model and the practical co-operation between a set of autonomous applications meeting the user requirements and objectives are discussed. Details of co-operation management are described by explaining the concepts of the inter-module communication, data exchange, control of operation and data model. (author)

Education and information for practicing school nurses: which technology-supported resources meet their needs?

Science.gov (United States)

Anderson, Lori S; Enge, Karmin J

2012-10-01

School nurses care for children with a variety of health-related conditions and they need information about managing these conditions, which is accessible, current, and useful. The goal of this literature review was to gather and synthesize information on technology-supported resources and to determine which met the educational needs of school nurses. Successful online educational programs were interactive and self-directed. The most common barriers were lack of time to find educational information, lack of knowledge about computers, technology, the Internet and specific programs, and lack of administrative support from school officials to use technology to access information and evidence for practice. Recommendations for successful use of technology to meet practicing school nurse's educational needs are offered.

Implementing Software Safety in the NASA Environment

Science.gov (United States)

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 Computational Infrastructure for Geodynamics: An Example of Software Curation and Citation in the Geodynamics Community

Science.gov (United States)

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.

Computational intelligence and quantitative software engineering

CERN Document Server

Succi, Giancarlo; Sillitti, Alberto

2016-01-01

In a down-to-the earth manner, the volume lucidly presents how the fundamental concepts, methodology, and algorithms of Computational Intelligence are efficiently exploited in Software Engineering and opens up a novel and promising avenue of a comprehensive analysis and advanced design of software artifacts. It shows how the paradigm and the best practices of Computational Intelligence can be creatively explored to carry out comprehensive software requirement analysis, support design, testing, and maintenance. Software Engineering is an intensive knowledge-based endeavor of inherent human-centric nature, which profoundly relies on acquiring semiformal knowledge and then processing it to produce a running system. The knowledge spans a wide variety of artifacts, from requirements, captured in the interaction with customers, to design practices, testing, and code management strategies, which rely on the knowledge of the running system. This volume consists of contributions written by widely acknowledged experts ...

What we know about software testability: a survey

OpenAIRE

Garousi, Vahid; Felderer, Michael; Kilicaslan, Feyza Nur

2018-01-01

Software testability is the degree to which a software system or a unit under test supports its own testing. To predict and improve software testability, a large number of techniques and metrics have been proposed by both practitioners and researchers in the last several decades. Reviewing and getting an overview of the entire state-of-the-art and -practice in this area is often challenging for a practitioner or a new researcher. Our objective is to summarize the state-of-the-art and -practic...

An algebraic approach to modeling in software engineering

International Nuclear Information System (INIS)

Loegel, C.J.; Ravishankar, C.V.

1993-09-01

Our work couples the formalism of universal algebras with the engineering techniques of mathematical modeling to develop a new approach to the software engineering process. Our purpose in using this combination is twofold. First, abstract data types and their specification using universal algebras can be considered a common point between the practical requirements of software engineering and the formal specification of software systems. Second, mathematical modeling principles provide us with a means for effectively analyzing real-world systems. We first use modeling techniques to analyze a system and then represent the analysis using universal algebras. The rest of the software engineering process exploits properties of universal algebras that preserve the structure of our original model. This paper describes our software engineering process and our experience using it on both research and commercial systems. We need a new approach because current software engineering practices often deliver software that is difficult to develop and maintain. Formal software engineering approaches use universal algebras to describe ''computer science'' objects like abstract data types, but in practice software errors are often caused because ''real-world'' objects are improperly modeled. There is a large semantic gap between the customer's objects and abstract data types. In contrast, mathematical modeling uses engineering techniques to construct valid models for real-world systems, but these models are often implemented in an ad hoc manner. A combination of the best features of both approaches would enable software engineering to formally specify and develop software systems that better model real systems. Software engineering, like mathematical modeling, should concern itself first and foremost with understanding a real system and its behavior under given circumstances, and then with expressing this knowledge in an executable form

The Astrophysics Source Code Library: Supporting software publication and citation

Science.gov (United States)

Allen, Alice; Teuben, Peter

2018-01-01

The Astrophysics Source Code Library (ASCL, ascl.net), established in 1999, is a free online registry for source codes used in research that has appeared in, or been submitted to, peer-reviewed publications. The ASCL is indexed by the SAO/NASA Astrophysics Data System (ADS) and Web of Science and is citable by using the unique ascl ID assigned to each code. In addition to registering codes, the ASCL can house archive files for download and assign them DOIs. The ASCL advocations for software citation on par with article citation, participates in multidiscipinary events such as Force11, OpenCon, and the annual Workshop on Sustainable Software for Science, works with journal publishers, and organizes Special Sessions and Birds of a Feather meetings at national and international conferences such as Astronomical Data Analysis Software and Systems (ADASS), European Week of Astronomy and Space Science, and AAS meetings. In this presentation, I will discuss some of the challenges of gathering credit for publishing software and ideas and efforts from other disciplines that may be useful to astronomy.

A Methodology for Integrating Maintainability Using Software Metrics

OpenAIRE

Lewis, John A.; Henry, Sallie M.

1989-01-01

Maintainability must be integrated into software early in the development process. But for practical use, the techniques used must be as unobtrusive to the existing software development process as possible. This paper defines a methodology for integrating maintainability into large-scale software and describes an experiment which implemented the methodology into a major commercial software development environment.

[Development and practice evaluation of blood acid-base imbalance analysis software].

Science.gov (United States)

Chen, Bo; Huang, Haiying; Zhou, Qiang; Peng, Shan; Jia, Hongyu; Ji, Tianxing

2014-11-01

To develop a blood gas, acid-base imbalance analysis computer software to diagnose systematically, rapidly, accurately and automatically determine acid-base imbalance type, and evaluate the clinical application. Using VBA programming language, a computer aided diagnostic software for the judgment of acid-base balance was developed. The clinical data of 220 patients admitted to the Second Affiliated Hospital of Guangzhou Medical University were retrospectively analyzed. The arterial blood gas [pH value, HCO(3)(-), arterial partial pressure of carbon dioxide (PaCO₂)] and electrolytes included data (Na⁺ and Cl⁻) were collected. Data were entered into the software for acid-base imbalances judgment. At the same time the data generation was calculated manually by H-H compensation formula for determining the type of acid-base imbalance. The consistency of judgment results from software and manual calculation was evaluated, and the judgment time of two methods was compared. The clinical diagnosis of the types of acid-base imbalance for the 220 patients: 65 cases were normal, 90 cases with simple type, mixed type in 41 cases, and triplex type in 24 cases. The accuracy of the judgment results of the normal and triplex types from computer software compared with which were calculated manually was 100%, the accuracy of the simple type judgment was 98.9% and 78.0% for the mixed type, and the total accuracy was 95.5%. The Kappa value of judgment result from software and manual judgment was 0.935, P=0.000. It was demonstrated that the consistency was very good. The time for software to determine acid-base imbalances was significantly shorter than the manual judgment (seconds:18.14 ± 3.80 vs. 43.79 ± 23.86, t=7.466, P=0.000), so the method of software was much faster than the manual method. Software judgment can replace manual judgment with the characteristics of rapid, accurate and convenient, can improve work efficiency and quality of clinical doctors and has great

48 CFR 9903.302-3 - Illustrations of changes which meet the definition of “change to a cost accounting practice.”

Science.gov (United States)

2010-10-01

... which meet the definition of âchange to a cost accounting practice.â 9903.302-3 Section 9903.302-3 Federal Acquisition Regulations System COST ACCOUNTING STANDARDS BOARD, OFFICE OF FEDERAL PROCUREMENT POLICY, OFFICE OF MANAGEMENT AND BUDGET PROCUREMENT PRACTICES AND COST ACCOUNTING STANDARDS CONTRACT...

Saltwell PIC Skid Programmable Logic Controller (PLC) Software Configuration Management Plan

International Nuclear Information System (INIS)

KOCH, M.R.

1999-01-01

This document provides the procedures and guidelines necessary for computer software configuration management activities during the operation and maintenance phases of the Saltwell PIC Skids as required by LMH-PRO-309/Rev. 0, Computer Software Quality Assurance, Section 2.6, Software Configuration Management. The software configuration management plan (SCMP) integrates technical and administrative controls to establish and maintain technical consistency among requirements, physical configuration, and documentation for the Saltwell PIC Skid Programmable Logic Controller (PLC) software during the Hanford application, operations and maintenance. This SCMP establishes the Saltwell PIC Skid PLC Software Baseline, status changes to that baseline, and ensures that software meets design and operational requirements and is tested in accordance with their design basis

Software reengineering

Science.gov (United States)

Fridge, Ernest M., III

1991-01-01

Today's software systems generally use obsolete technology, are not integrated properly with other software systems, and are difficult and costly to maintain. The discipline of reverse engineering is becoming prominent as organizations try to move their systems up to more modern and maintainable technology in a cost effective manner. JSC created a significant set of tools to develop and maintain FORTRAN and C code during development of the Space Shuttle. This tool set forms the basis for an integrated environment to re-engineer existing code into modern software engineering structures which are then easier and less costly to maintain and which allow a fairly straightforward translation into other target languages. The environment will support these structures and practices even in areas where the language definition and compilers do not enforce good software engineering. The knowledge and data captured using the reverse engineering tools is passed to standard forward engineering tools to redesign or perform major upgrades to software systems in a much more cost effective manner than using older technologies. A beta vision of the environment was released in Mar. 1991. The commercial potential for such re-engineering tools is very great. CASE TRENDS magazine reported it to be the primary concern of over four hundred of the top MIS executives.

THE ROLE OF HUMAN RESOURCE PRACTICES ON PROFITS GENERATED BY THE INNOVATIONS: THE ROLE OF TOP MANAGEMENT SUPPORT AND REGULARITY OF EMPLOYEES MEETINGS

Directory of Open Access Journals (Sweden)

Tatjana Stanovcic

2016-12-01

Full Text Available Previous scholars argue that human resource practices advance valuable knowledge what could be reflected positively on innovations. Accordingly, we empirically investigate whether human resource related practices such as top management support and regularity of employees meetings are related to profit generated by the innovation activities. Using survey data of Montenegrin firms, we find that firms in which top management supports employees' idea and have regular employees meetings related to innovation activities are likely to report higher profit generated by innovations. Therefore, our results underline the crucial role of human resource practices in the process of innovation that generates profitability for firms.

Practicality for Software Hazard Analysis for Nuclear Safety I and C System

International Nuclear Information System (INIS)

Kim, Yong-Ho; Moon, Kwon-Ki; Chang, Young-Woo; Jeong, Soo-Hyun

2016-01-01

We are using the concept of system safety in engineering. It is difficult to make any system perfectly safe and probably a complete system may not easily be achieved. The standard definition of a system from MIL-STD- 882E is: “The organization of hardware, software, material, facilities, personnel, data, and services needed to perform a designated function within a stated environment with specified results.” From the perspective of the system safety engineer and the hazard analysis process, software is considered as a subsystem. Regarding hazard analysis, to date, methods for identifying software failures and determining their effects is still a research problem. Since the success of software development is based on rigorous test of hardware and software, it is necessary to check the balance between software test and hardware test, and in terms of efficiency. Lessons learned and experience from similar systems are important for the work of hazard analysis. No major hazard has been issued for the software developed and verified in Korean NPPs. In addition to hazard analysis, software development, and verification and validation were thoroughly performed. It is reasonable that the test implementation including the development of the test case, stress and abnormal conditions, error recovery situations, and high risk hazardous situations play a key role in detecting and preventing software faults

Practicality for Software Hazard Analysis for Nuclear Safety I and C System

Energy Technology Data Exchange (ETDEWEB)

Kim, Yong-Ho; Moon, Kwon-Ki; Chang, Young-Woo; Jeong, Soo-Hyun [KEPCO Engineering and Construction Co., Deajeon (Korea, Republic of)

2016-10-15

We are using the concept of system safety in engineering. It is difficult to make any system perfectly safe and probably a complete system may not easily be achieved. The standard definition of a system from MIL-STD- 882E is: “The organization of hardware, software, material, facilities, personnel, data, and services needed to perform a designated function within a stated environment with specified results.” From the perspective of the system safety engineer and the hazard analysis process, software is considered as a subsystem. Regarding hazard analysis, to date, methods for identifying software failures and determining their effects is still a research problem. Since the success of software development is based on rigorous test of hardware and software, it is necessary to check the balance between software test and hardware test, and in terms of efficiency. Lessons learned and experience from similar systems are important for the work of hazard analysis. No major hazard has been issued for the software developed and verified in Korean NPPs. In addition to hazard analysis, software development, and verification and validation were thoroughly performed. It is reasonable that the test implementation including the development of the test case, stress and abnormal conditions, error recovery situations, and high risk hazardous situations play a key role in detecting and preventing software faults.

Requirements Engineering in Building Climate Science Software

Science.gov (United States)

Batcheller, Archer L.

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 Framework assists modeling applications, the Earth System Grid distributes data via a web portal, and the NCAR (National Center for Atmospheric Research) Command Language is used to convert, analyze and visualize data. Document analysis, observation, and interviews were used to investigate the requirements-related work. The first research question is about how and why stakeholders engage in a project, and what they do for the project. Two key findings arise. First, user counts are a vital measure of project success, which makes adoption important and makes counting tricky and political. Second, despite the importance of quantities of users, a few particular "power users" develop a relationship with the software developers and play a special role in providing feedback to the software team and integrating the system into user practice. The second research question focuses on how project objectives are articulated and how they are put into practice. The team seeks to both build a software system according to product requirements but also to conduct their work according to process requirements such as user support. Support provides essential communication between users and developers that assists with refining and identifying requirements for the software. It also helps users to learn and apply the software to their real needs. User support is a vital activity for scientific software teams aspiring to create infrastructure. The third research question is about how change in scientific practice and knowledge leads to changes in the software, and vice versa. The "thickness" of a layer of software infrastructure impacts whether the

Robust variance estimation with dependent effect sizes: practical considerations including a software tutorial in Stata and spss.

Science.gov (United States)

Tanner-Smith, Emily E; Tipton, Elizabeth

2014-03-01

Methodologists have recently proposed robust variance estimation as one way to handle dependent effect sizes in meta-analysis. Software macros for robust variance estimation in meta-analysis are currently available for Stata (StataCorp LP, College Station, TX, USA) and spss (IBM, Armonk, NY, USA), yet there is little guidance for authors regarding the practical application and implementation of those macros. This paper provides a brief tutorial on the implementation of the Stata and spss macros and discusses practical issues meta-analysts should consider when estimating meta-regression models with robust variance estimates. Two example databases are used in the tutorial to illustrate the use of meta-analysis with robust variance estimates. Copyright © 2013 John Wiley & Sons, Ltd.

Resource utilization during software development

Science.gov (United States)

Zelkowitz, Marvin V.

1988-01-01

This paper discusses resource utilization over the life cycle of software development and discusses the role that the current 'waterfall' model plays in the actual software life cycle. Software production in the NASA environment was analyzed to measure these differences. The data from 13 different projects were collected by the Software Engineering Laboratory at NASA Goddard Space Flight Center and analyzed for similarities and differences. The results indicate that the waterfall model is not very realistic in practice, and that as technology introduces further perturbations to this model with concepts like executable specifications, rapid prototyping, and wide-spectrum languages, we need to modify our model of this process.

Practicality of Elementary Statistics Module Based on CTL Completed by Instructions on Using Software R

Science.gov (United States)

Delyana, H.; Rismen, S.; Handayani, S.

2018-04-01

This research is a development research using 4-D design model (define, design, develop, and disseminate). The results of the define stage are analyzed for the needs of the following; Syllabus analysis, textbook analysis, student characteristics analysis and literature analysis. The results of textbook analysis obtained the description that of the two textbooks that must be owned by students also still difficulty in understanding it, the form of presentation also has not facilitated students to be independent in learning to find the concept, textbooks are also not equipped with data processing referrals by using software R. The developed module is considered valid by the experts. Further field trials are conducted to determine the practicality and effectiveness. The trial was conducted to the students of Mathematics Education Study Program of STKIP PGRI which was taken randomly which has not taken Basic Statistics Course that is as many as 4 people. Practical aspects of attention are easy, time efficient, easy to interpret, and equivalence. The practical value in each aspect is 3.7; 3.79, 3.7 and 3.78. Based on the results of the test students considered that the module has been very practical use in learning. This means that the module developed can be used by students in Elementary Statistics learning.

Lean software development in action

CERN Document Server

Janes, Andrea

2014-01-01

This book illustrates how goal-oriented, automated measurement can be used to create Lean organizations and to facilitate the development of Lean software, while also demonstrating the practical implementation of Lean software development by combining tried and trusted tools. In order to be successful, a Lean orientation of software development has to go hand in hand with a company's overall business strategy. To achieve this, two interrelated aspects require special attention: measurement and experience management. In this book, Janes and Succi provide the necessary knowledge to establish "

Trends in software testing

CERN Document Server

Mohanty, J; Balakrishnan, Arunkumar

2017-01-01

This book is focused on the advancements in the field of software testing and the innovative practices that the industry is adopting. Considering the widely varied nature of software testing, the book addresses contemporary aspects that are important for both academia and industry. There are dedicated chapters on seamless high-efficiency frameworks, automation on regression testing, software by search, and system evolution management. There are a host of mathematical models that are promising for software quality improvement by model-based testing. There are three chapters addressing this concern. Students and researchers in particular will find these chapters useful for their mathematical strength and rigor. Other topics covered include uncertainty in testing, software security testing, testing as a service, test technical debt (or test debt), disruption caused by digital advancement (social media, cloud computing, mobile application and data analytics), and challenges and benefits of outsourcing. The book w...

Statistics of software vulnerability detection in certification testing

Science.gov (United States)

Barabanov, A. V.; Markov, A. S.; Tsirlov, V. L.

2018-05-01

The paper discusses practical aspects of introduction of the methods to detect software vulnerability in the day-to-day activities of the accredited testing laboratory. It presents the approval results of the vulnerability detection methods as part of the study of the open source software and the software that is a test object of the certification tests under information security requirements, including software for communication networks. Results of the study showing the allocation of identified vulnerabilities by types of attacks, country of origin, programming languages used in the development, methods for detecting vulnerability, etc. are given. The experience of foreign information security certification systems related to the detection of certified software vulnerabilities is analyzed. The main conclusion based on the study is the need to implement practices for developing secure software in the development life cycle processes. The conclusions and recommendations for the testing laboratories on the implementation of the vulnerability analysis methods are laid down.

Multi-Level Formation of Complex Software Systems

Directory of Open Access Journals (Sweden)

Hui Li

2016-05-01

Full Text Available We present a multi-level formation model for complex software systems. The previous works extract the software systems to software networks for further studies, but usually investigate the software networks at the class level. In contrast to these works, our treatment of software systems as multi-level networks is more realistic. In particular, the software networks are organized by three levels of granularity, which represents the modularity and hierarchy in the formation process of real-world software systems. More importantly, simulations based on this model have generated more realistic structural properties of software networks, such as power-law, clustering and modularization. On the basis of this model, how the structure of software systems effects software design principles is then explored, and it could be helpful for understanding software evolution and software engineering practices.

Lightning talk slide for "SLACKHA: Software Library for Accelerating Chemical Kinetics on Hybrid Architectures"

OpenAIRE

Niemeyer, Kyle; Sung, Chih-Jen

2018-01-01

Lightning talk slide describing the "SLACKHA: Software Library for Accelerating Chemical Kinetics on Hybrid Architectures" project at the 2018 NSF SI2 PI meeting: https://si2-pi-community.github.io/2018-meeting/

Workshop on cooperative and human aspects of software engineering (CHASE 2011)

DEFF Research Database (Denmark)

Cataldo, Marcelo; de Souza, Cleidson; Dittrich, Yvonne

2011-01-01

is to provide a forum for discussing high quality research on human and cooperative aspects of software engineering. We aim at providing both a meeting place for the growing community and the possibility for researchers interested in joining the field to present their work in progress and get an overview over......Software is created by people for people working in varied environments, under various conditions. Thus understanding cooperative and human aspects of software development is crucial to comprehend how methods and tools are used, and thereby improve the creation and maintenance of software. Over...

Factors negatively influencing knowledge sharing in software development

Directory of Open Access Journals (Sweden)

Lucas T. Khoza

2017-07-01

Objective: This study seeks to identify factors that negatively influence knowledge sharing in software development in the developing country context. Method: Expert sampling as a subcategory of purposive sampling was employed to extract information, views and opinions from experts in the field of information and communication technology, more specifically from those who are involved in software development projects. Four Johannesburg-based software developing organisations listed on the Johannesburg Stock Exchange (JSE, South Africa, participated in this research study. Quantitative data were collected using an online questionnaire with closed-ended questions. Results: Findings of this research reveal that job security, motivation, time constraints, physiological factors, communication, resistance to change and rewards are core factors negatively influencing knowledge sharing in software developing organisations. Conclusions: Improved understanding of factors negatively influencing knowledge sharing is expected to assist software developing organisations in closing the gap for software development projects failing to meet the triple constraint of time, cost and scope.

Continuous Software Quality analysis for the ATLAS experiment

CERN Document Server

Washbrook, Andrew; The ATLAS collaboration

2017-01-01

The regular application of software quality tools in large collaborative projects is required to reduce code defects to an acceptable level. If left unchecked the accumulation of defects invariably results in performance degradation at scale and problems with the long-term maintainability of the code. Although software quality tools are effective for identification there remains a non-trivial sociological challenge to resolve defects in a timely manner. This is a ongoing concern for the ATLAS software which has evolved over many years to meet the demands of Monte Carlo simulation, detector reconstruction and data analysis. At present over 3.8 million lines of C++ code (and close to 6 million total lines of code) are maintained by a community of hundreds of developers worldwide. It is therefore preferable to address code defects before they are introduced into a widely used software release. Recent wholesale changes to the ATLAS software infrastructure have provided an ideal opportunity to apply software quali...

A Role-Playing Game for a Software Engineering Lab: Developing a Product Line

Science.gov (United States)

Zuppiroli, Sara; Ciancarini, Paolo; Gabbrielli, Maurizio

2012-01-01

Software product line development refers to software engineering practices and techniques for creating families of similar software systems from a basic set of reusable components, called shared assets. Teaching how to deal with software product lines in a university lab course is a challenging task, because there are several practical issues that…

16 CFR 1012.4 - Public attendance at agency meetings.

Science.gov (United States)

2010-01-01

... 16 Commercial Practices 2 2010-01-01 2010-01-01 false Public attendance at agency meetings. 1012.4 Section 1012.4 Commercial Practices CONSUMER PRODUCT SAFETY COMMISSION GENERAL MEETINGS POLICY-MEETINGS BETWEEN AGENCY PERSONNEL AND OUTSIDE PARTIES § 1012.4 Public attendance at agency meetings. (a) Any person...

Software as a bridge between theory and practice in life cycle assessment

NARCIS (Netherlands)

Heijungs, Reinout; Guinée, Jeroen B.

1993-01-01

Three mutually dependent elements are required for the application of life cycle assessment: methodology, data and software. Obviously, the design of software is determined by the methodology and the type of data available. Conversely, the development of software dictates the way in which data

Flexible, reliable software using patterns and agile development

CERN Document Server

Christensen, Henrik B

2010-01-01

…This book brings together a careful selection of topics that are relevant, indeed crucial, for developing good quality software with a carefully designed pedagogy that leads the reader through an experience of active learning. The emphasis in the content is on practical goals-how to construct reliable and flexible software systems-covering many topics that every software engineer should have studied. The emphasis in the method is on providing a practical context, hands-on projects, and guidance on process. … The text discusses not only what the end product should be like, but also how to get

Toward Intelligent Software Defect Detection

Science.gov (United States)

Benson, Markland J.

2011-01-01

Source code level software defect detection has gone from state of the art to a software engineering best practice. Automated code analysis tools streamline many of the aspects of formal code inspections but have the drawback of being difficult to construct and either prone to false positives or severely limited in the set of defects that can be detected. Machine learning technology provides the promise of learning software defects by example, easing construction of detectors and broadening the range of defects that can be found. Pinpointing software defects with the same level of granularity as prominent source code analysis tools distinguishes this research from past efforts, which focused on analyzing software engineering metrics data with granularity limited to that of a particular function rather than a line of code.

Practices around Customization of Standard Systems

DEFF Research Database (Denmark)

Dittrich, Yvonne; Vaucouleur, Sebastien

2008-01-01

More and more software systems are developed by customizing a standard product that provide the major part of the functionality. The customization of Enterprise Resource Planning systems is such a product based software development practice. Little empirical research on the specificities...... of these software development practices is available. We present an empirical study on customization practices based on video recordings, interviews and a survey. The observed and reported practices challenge some of the principles of software engineering. Based on the analysis, we discuss the specificity...

The role of morbidity and mortality meetings in interventional radiology

International Nuclear Information System (INIS)

Mok, Philip S.; Tan, Eva Y.; Baerlocher, Mark O.; Athreya, Sriharsha

2012-01-01

Purpose: To understand the current practice of interventional radiology (IR) morbidity and mortality (M and M) meetings among interventional radiologists in Europe, and to develop a set of results-based recommendations to increase the prevalence of IR M and M meetings. Materials and methods: Online electronic surveys were sent to members of the Cardiovascular and Interventional Radiology Society of Europe (CIRSE). Each survey consisted of 18 questions pertaining to IR M and M meetings. Results: A total of 150 CIRSE members responded to the survey. Approximately 47% of respondents held IR M and M meetings in their departments. Among those who held IR M and M meetings, 42% held them monthly and 68% rated the quality of the meetings as good or excellent. Of those who did not have M and M meetings, 94% were interested in incorporating M and M meetings into their future practice. The most common reasons for not holding IR M and M meetings were lack of time (68%) and small IR practice groups (43%). A total of 85% were interested in learning more about IR M and M meetings. The preferred method of education about M and M meetings included annual radiology meetings (44%), peer-reviewed articles in radiology journals (31%), websites (26%), and newsletters (15%). Conclusions: The data demonstrate that although current practice of M and M meetings in European IR departments is limited, the majority of respondents believe that M and M meetings are beneficial to their practice. There is a need for guidelines or standards of practice to incorporate such meetings in IR departments to prevent medical errors, which may ultimately lead to enhanced patient safety and outcomes.

Cooperative and Human Aspects of Software Engineering (CHASE 2010)

DEFF Research Database (Denmark)

Dittrich, Yvonne; De Souza, Cleidson; Korpela, Mikko

2010-01-01

Software is created by people---software engineers---working in varied environments, under various conditions. Thus understanding cooperative and human aspect of software development is crucial to comprehend how methods and tools are used, and thereby improving the creation and maintenance...... research on human and cooperative aspects of software engineering. We aim at providing both a meeting place for the growing community and the possibility for researchers interested in joining the field to present their work in progress and get an overview over the field....... of software. Inspired by the hosting country's concept of co-responsibility -- ubuntu -- we especially invited contributions that address community-based development like open source development and sustainability of ICT eco-systems. The goal of this workshop is to provide a forum for discussing high quality...

Practical Findings from Applying the PSD Model for Evaluating Software Design Specifications

Science.gov (United States)

Räisänen, Teppo; Lehto, Tuomas; Oinas-Kukkonen, Harri

This paper presents practical findings from applying the PSD model to evaluating the support for persuasive features in software design specifications for a mobile Internet device. On the one hand, our experiences suggest that the PSD model fits relatively well for evaluating design specifications. On the other hand, the model would benefit from more specific heuristics for evaluating each technique to avoid unnecessary subjectivity. Better distinction between the design principles in the social support category would also make the model easier to use. Practitioners who have no theoretical background can apply the PSD model to increase the persuasiveness of the systems they design. The greatest benefit of the PSD model for researchers designing new systems may be achieved when it is applied together with a sound theory, such as the Elaboration Likelihood Model. Using the ELM together with the PSD model, one may increase the chances for attitude change.

Summary of the International Conference on Software and System Processes

DEFF Research Database (Denmark)

Kuhrmann, Marco; O'Connor, Rory V.; Perry, Dewayne E.

2016-01-01

The International Conference on Software and Systems Process (ICSSP), continuing the success of Software Process Workshop (SPW), the Software Process Modeling and Simulation Workshop (ProSim) and the International Conference on Software Process (ICSP) conference series, has become the established...... premier event in the field of software and systems engineering processes. It provides a leading forum for the exchange of research outcomes and industrial best-practices in process development from software and systems disciplines. ICSSP 2016 was held in Austin, Texas, from 14-15 May 2016, co......-located with the 38th International Conference on Software Engineering (ICSE). The theme of mICSSP 2016 was studying "Process(es) in Action" by recognizing that the AS-Planned and AS-Practiced processes can be quite different in many ways including their ows, their complexity and the evolving needs of stakeholders...

From policy to practice: strategies to meet physical activity standards in YMCA afterschool programs.

Science.gov (United States)

Beets, Michael W; Weaver, Robert G; Moore, Justin B; Turner-McGrievy, Gabriel; Pate, Russell R; Webster, Collin; Beighle, Aaron

2014-03-01

In 2011, the U.S. Young Men's Christian Association (YMCA) adopted activity standards recommending that afterschool programs (ASPs) ensure all children engage in a minimum of 30 minutes of moderate to vigorous physical activity (MVPA) daily during the ASP. ASPs decide how to accomplish this standard, for which few effective strategies exist. To evaluate strategies designed to help ASPs meet the MVPA standard. Single group intervention with pretest and three follow-up measures repeated-cross-sectional design with a subsample cohort. Four large-scale YMCA ASPs, serving approximately 500 children each day. Community-based participatory development of strategies focused on modification of program schedules, professional development training, and weekly checklists to evaluate activity opportunities. Accelerometry-derived MVPA classified as meet or fail-to-meet the 30 minutes' MVPA/day standard collected over a minimum of 4 nonconsecutive days at baseline (fall 2011) and three follow-up assessments (spring 2012, fall 2012, spring 2013). Random intercept logistic regression models evaluated the probability of meeting the standard for boys and girls, separately (analyzed summer 2013). A total of 895 children (aged 5-12 years, 48.4% girls) representing 3654 daily measures were collected across the four assessments. The percentage of girls and boys meeting the MVPA standard at baseline was 13.3% and 28.0%, respectively. By spring 2013, this increased to 29.3% and 49.6%. These changes represented an increase in the odds of meeting the 30 minutes' MVPA/day standard by 1.5 (95% CI=1.1, 2.0) and 2.4 (95% CI=1.2, 4.8) for girls and boys, respectively. The strategies developed herein represent an effective approach to enhancing current practice within YMCA ASPs to achieve existing MVPA standards. Additional work is necessary to evaluate the scalability of the strategies in a larger sample of ASPs. © 2014 American Journal of Preventive Medicine Published by American Journal of

Requirements Specification for Open Source Software Selection

OpenAIRE

YANG, YING

2008-01-01

Open source software has been widely used. The software world is enjoying the advantages of collaboration and cooperation in software development and use with the advent of open source movement. However, little research is concerned about the practical guidelines of OSS selection. It is hard for an organization to make a decision whether they should use the OSS or not, and to select an appropriate one from a number of OSS candidates. This thesis studies how to select an open source software f...

Validation of geotechnical software for repository performance assessment

International Nuclear Information System (INIS)

LeGore, T.; Hoover, J.D.; Khaleel, R.; Thornton, E.C.; Anantatmula, R.P.; Lanigan, D.C.

1989-01-01

An important step in the characterization of a high level nuclear waste repository is to demonstrate that geotechnical software, used in performance assessment, correctly models validation. There is another type of validation, called software validation. It is based on meeting the requirements of specifications documents (e.g. IEEE specifications) and does not directly address the correctness of the specifications. The process of comparing physical experimental results with the predicted results should incorporate an objective measure of the level of confidence regarding correctness. This paper reports on a methodology developed that allows the experimental uncertainties to be explicitly included in the comparison process. The methodology also allows objective confidence levels to be associated with the software. In the event of a poor comparison, the method also lays the foundation for improving the software

Lean principles applied to software development – avoiding waste

Directory of Open Access Journals (Sweden)

Ionel NAFTANAILA

2009-12-01

Full Text Available Under the current economic conditions many organizations strive to continue the trend towards adopting better software development processes, in order to take advantage of the numerous benefits that these can offer. Those benefits include quicker return on investment, better software quality, and higher customer satisfaction. To date, however, there is little body of research that can guide organizations in adopting modern software development practices, especially when it comes to Lean thinking and principles. To address this situation, the current paper identifies and structures the main wastes (or muda in Lean terms in software development as described by Lean principles, in an attempt to bring into researchers’ and practitioners’ attention Lean Software Development, a modern development methodology based on well-established practices such as Lean Manufacturing or Toyota Production System.

Managing Software Process Evolution

DEFF Research Database (Denmark)

This book focuses on the design, development, management, governance and application of evolving software processes that are aligned with changing business objectives, such as expansion to new domains or shifting to global production. In the context of an evolving business world, it examines...... the complete software process lifecycle, from the initial definition of a product to its systematic improvement. In doing so, it addresses difficult problems, such as how to implement processes in highly regulated domains or where to find a suitable notation system for documenting processes, and provides...... essential insights and tips to help readers manage process evolutions. And last but not least, it provides a wealth of examples and cases on how to deal with software evolution in practice. Reflecting these topics, the book is divided into three parts. Part 1 focuses on software business transformation...

4. Meeting on cooling towers. From practice - for practice; 4. Kuehlturm-Tagung. Aus der Praxis - Fuer die Praxis

Energy Technology Data Exchange (ETDEWEB)

NONE

1998-09-01

The 4th Cooling Tower meeting brought into focus aspects of economic efficiency of the water cooling system, i.e. the papers analyse investment cost and operating cost taking into account environmental policy and interests. Numerous examples from practice are discussed in the papers showing how wet cooling tower design and application-specific selection of design features can influence the performance of the entire system. (orig./CB) [Deutsch] Im Mittelpunkt der 4. Kuehlturm-Tagung steht die Wirtschaftlichkeit der Wasserrueckkuehlanlage, d.h. die Betrachtung der Investitions- und Betriebskosten unter Beruecksichtigung der Belange des Umweltschutzes. Mit Beispielen aus der Praxis zeigen die Referenten, wie sich die Auslegung und Auswahl eines Nasskuehlturms auf das Betriebsergebnis der Anlage auswirken. (orig./GL)

Guidelines for verification and validation of software related to nuclear power plant control and instrumentation. Working material

International Nuclear Information System (INIS)

1993-01-01

The main purpose of the consultancy organized by the IAEA and held form 6 to 10 September 1993 was to prepare an extended outline of a new technical document in which a current status of Verification and Validation of software related to NPP I and C systems and guidance on the practical use of Verification and Validation methods for solving special problems in design, operation and maintenance of nuclear power plants are to be presented. The present volume contains: (1) report of the meeting; (2) reports presented by the national delegates; and (3) technical draft document. Ref and figs

Software engineering frameworks for the cloud computing paradigm

CERN Document Server

Mahmood, Zaigham

2013-01-01

This book presents the latest research on Software Engineering Frameworks for the Cloud Computing Paradigm, drawn from an international selection of researchers and practitioners. The book offers both a discussion of relevant software engineering approaches and practical guidance on enterprise-wide software deployment in the cloud environment, together with real-world case studies. Features: presents the state of the art in software engineering approaches for developing cloud-suitable applications; discusses the impact of the cloud computing paradigm on software engineering; offers guidance an

A quantitative calculation for software reliability evaluation

Energy Technology Data Exchange (ETDEWEB)

Lee, Young-Jun; Lee, Jang-Soo [Korea Atomic Energy Research Institute, Daejeon (Korea, Republic of)

2016-10-15

To meet these regulatory requirements, the software used in the nuclear safety field has been ensured through the development, validation, safety analysis, and quality assurance activities throughout the entire process life cycle from the planning phase to the installation phase. A variety of activities, such as the quality assurance activities are also required to improve the quality of a software. However, there are limitations to ensure that the quality is improved enough. Therefore, the effort to calculate the reliability of the software continues for a quantitative evaluation instead of a qualitative evaluation. In this paper, we propose a quantitative calculation method for the software to be used for a specific operation of the digital controller in an NPP. After injecting random faults in the internal space of a developed controller and calculating the ability to detect the injected faults using diagnostic software, we can evaluate the software reliability of a digital controller in an NPP. We tried to calculate the software reliability of the controller in an NPP using a new method that differs from a traditional method. It calculates the fault detection coverage after injecting the faults into the software memory space rather than the activity through the life cycle process. We attempt differentiation by creating a new definition of the fault, imitating the software fault using the hardware, and giving a consideration and weights for injection faults.

Safety and reliability of automatization software

Energy Technology Data Exchange (ETDEWEB)

Kapp, K; Daum, R [Karlsruhe Univ. (TH) (Germany, F.R.). Lehrstuhl fuer Angewandte Informatik, Transport- und Verkehrssysteme

1979-02-01

Automated technical systems have to meet very high requirements concerning safety, security and reliability. Today, modern computers, especially microcomputers, are used as integral parts of those systems. In consequence computer programs must work in a safe and reliable mannter. Methods are discussed which allow to construct safe and reliable software for automatic systems such as reactor protection systems and to prove that the safety requirements are met. As a result it is shown that only the method of total software diversification can satisfy all safety requirements at tolerable cost. In order to achieve a high degree of reliability, structured and modular programming in context with high level programming languages are recommended.

Twenty-third water reactor safety information meeting: Volume 2, Human factors research; Advanced I and C hardware and software; Severe accident research; Probabilistic risk assessment topics; Individual plant examination: Proceedings

Energy Technology Data Exchange (ETDEWEB)

Monteleone, S. [comp.] [Brookhaven National Lab., Upton, NY (United States)

1996-03-01

This three-volume report contains papers presented at the Twenty- Third Water Reactor Safety Information Meeting held at the Bethesda Marriott Hotel, Bethesda, Maryland, October 23-25, 1995. The papers are printed in the order of their presentation in each session and describe progress and results of programs in nuclear safety research conducted in this country and abroad. Foreign participation in the meeting included papers presented by researchers from France, Italy, Japan, Norway, Russia, Sweden, and Switzerland. This document, Volume 2, present topics in human factors research, advanced instrumentation and control hardware and software, severe accident research, probabilistic risk assessment, and individual plant examination. Individual papers have been cataloged separately.

Product-based Safety Certification for Medical Devices Embedded Software.

Science.gov (United States)

Neto, José Augusto; Figueiredo Damásio, Jemerson; Monthaler, Paul; Morais, Misael

2015-01-01

Worldwide medical device embedded software certification practices are currently focused on manufacturing best practices. In Brazil, the national regulatory agency does not hold a local certification process for software-intensive medical devices and admits international certification (e.g. FDA and CE) from local and international industry to operate in the Brazilian health care market. We present here a product-based certification process as a candidate process to support the Brazilian regulatory agency ANVISA in medical device software regulation. Center of Strategic Technology for Healthcare (NUTES) medical device embedded software certification is based on a solid safety quality model and has been tested with reasonable success against the Class I risk device Generic Infusion Pump (GIP).

Rapport fra forbedringsaktivitet: Software udviklingsmodel, Brüel & Kjær CMS

DEFF Research Database (Denmark)

Nørbjerg, Jacob; Vinter, Otto

1999-01-01

Final report from a software process improvement initiative at Brüel & Kjær CMS. The initiative aimed to develop and obtain practical experience with a software development model based on incremental development and timeboxing.......Final report from a software process improvement initiative at Brüel & Kjær CMS. The initiative aimed to develop and obtain practical experience with a software development model based on incremental development and timeboxing....

Advances in Multimedia, Software Engineering and Computing Vol.1 : Proceedings of the 2011 MSEC International Conference on Multimedia, Software Engineering and Computing

CERN Document Server

Lin, Sally

2012-01-01

MSEC2011 is an integrated conference concentrating its focus upon Multimedia ,Software Engineering, Computing and Education. In the proceeding, you can learn much more knowledge about Multimedia, Software Engineering ,Computing and Education of researchers all around the world. The main role of the proceeding is to be used as an exchange pillar for researchers who are working in the mentioned field. In order to meet high standard of Springer, AISC series ,the organization committee has made their efforts to do the following things. Firstly, poor quality paper has been refused after reviewing course by anonymous referee experts. Secondly, periodically review meetings have been held around the reviewers about five times for exchanging reviewing suggestions. Finally, the conference organization had several preliminary sessions before the conference. Through efforts of different people and departments, the conference will be successful and fruitful.

Advances in Multimedia, Software Engineering and Computing Vol.2 : Proceedings of the 2011 MSEC International Conference on Multimedia, Software Engineering and Computing

CERN Document Server

Lin, Sally

2012-01-01

MSEC2011 is an integrated conference concentrating its focus upon Multimedia ,Software Engineering, Computing and Education. In the proceeding, you can learn much more knowledge about Multimedia, Software Engineering, Computing and Education of researchers all around the world. The main role of the proceeding is to be used as an exchange pillar for researchers who are working in the mentioned field. In order to meet high standard of Springer, AISC series ,the organization committee has made their efforts to do the following things. Firstly, poor quality paper has been refused after reviewing course by anonymous referee experts. Secondly, periodically review meetings have been held around the reviewers about five times for exchanging reviewing suggestions. Finally, the conference organization had several preliminary sessions before the conference. Through efforts of different people and departments, the conference will be successful and fruitful.

Overcoming public speaking anxiety of software engineers using virtual reality exposure therapy.

OpenAIRE

Nazligul, Merve Denizc; Yilmaz, Murat; Gulec, Ulas; Ali Gozcu, Mert; O'Connor, Rory; Clarke, Paul

2017-01-01

Public speaking anxiety is a type of social phobia, which might be commonly seen in novice software engineers. It is usually triggered by a fear of social performance especially when the performer is unfamiliar with the audience. Today, many software engineering activities (e.g. code inspection, peer review, daily meetings, etc.) require social gatherings where individuals need to present their work. However, novice software engineers may not be able to reduce their performance anxiety during...

An Architecture, System Engineering, and Acquisition Approach for Space System Software Resiliency

Science.gov (United States)

Phillips, Dewanne Marie

Software intensive space systems can harbor defects and vulnerabilities that may enable external adversaries or malicious insiders to disrupt or disable system functions, risking mission compromise or loss. Mitigating this risk demands a sustained focus on the security and resiliency of the system architecture including software, hardware, and other components. Robust software engineering practices contribute to the foundation of a resilient system so that the system "can take a hit to a critical component and recover in a known, bounded, and generally acceptable period of time". Software resiliency must be a priority and addressed early in the life cycle development to contribute a secure and dependable space system. Those who develop, implement, and operate software intensive space systems must determine the factors and systems engineering practices to address when investing in software resiliency. This dissertation offers methodical approaches for improving space system resiliency through software architecture design, system engineering, increased software security, thereby reducing the risk of latent software defects and vulnerabilities. By providing greater attention to the early life cycle phases of development, we can alter the engineering process to help detect, eliminate, and avoid vulnerabilities before space systems are delivered. To achieve this objective, this dissertation will identify knowledge, techniques, and tools that engineers and managers can utilize to help them recognize how vulnerabilities are produced and discovered so that they can learn to circumvent them in future efforts. We conducted a systematic review of existing architectural practices, standards, security and coding practices, various threats, defects, and vulnerabilities that impact space systems from hundreds of relevant publications and interviews of subject matter experts. We expanded on the system-level body of knowledge for resiliency and identified a new software

Safety Software Guide Perspectives for the Design of New Nuclear Facilities (U)

International Nuclear Information System (INIS)

VINCENT, Andrew

2005-01-01

In June of this year, the Department of Energy (DOE) issued directives DOE O 414.1C and DOE G 414.1-4 to improve quality assurance programs, processes, and procedures among its safety contractors. Specifically, guidance entitled, ''Safety Software Guide for use with 10 CFR 830 Subpart A, Quality Assurance Requirements, and DOE O 414.1C, Quality Assurance, DOE G 414.1-4'', provides information and acceptable methods to comply with safety software quality assurance (SQA) requirements. The guidance provides a roadmap for meeting DOE O 414.1C, ''Quality Assurance'', and the quality assurance program (QAP) requirements of Title 10 Code of Federal Regulations (CFR) 830, Subpart A, Quality Assurance, for DOE nuclear facilities and software application activities. [1, 2] The order and guide are part of a comprehensive implementation plan that addresses issues and concerns documented in Defense Nuclear Facilities Safety Board (DNFSB) Recommendation 2002-1. [3] Safety SQA requirements for DOE as well as National Nuclear Security Administration contractors are necessary to implement effective quality assurance (QA) processes and achieve safe nuclear facility operations. DOE G 414.1-4 was developed to provide guidance on establishing and implementing effective QA processes tied specifically to nuclear facility safety software applications. The Guide includes software application practices covered by appropriate national and international consensus standards and various processes currently in use at DOE facilities. While the safety software guidance is considered to be of sufficient rigor and depth to ensure acceptable reliability of safety software at all DOE nuclear facilities, new nuclear facilities are well suited to take advantage of the guide to ensure compliant programs and processes are implemented. Attributes such as the facility life-cycle stage and the hazardous nature of each facility operations are considered, along with the category and level of importance of the

The primary protection system software

International Nuclear Information System (INIS)

Tooley, P.A.

1992-01-01

This paper continues the detailed description of the Primary Protection System for Sizewell-B by providing an overview of design and implementation of the software, including the features of the design process which ensure that quality is delivered by the contractor. The Nuclear Electric software assessment activities are also described. The argument for the excellence of the software is made on the basis of a quality product delivered by the equipment supplier's design process, and the confirmation of this provided by the Nuclear Electric assessment process, which is as searching and complete an examination as is reasonably practicable to achieve. (author)

Organizational Stresses and Practices Impeding Quality Software Development in Government Procurements

Science.gov (United States)

Holcomb, Glenda S.

2010-01-01

This qualitative, phenomenological doctoral dissertation research study explored the software project team members perceptions of changing organizational cultures based on management decisions made at project deviation points. The research study provided a view into challenged or failing government software projects through the lived experiences…

Empirical Evaluation of Two Best-Practices for Energy-Efficient Software Development

NARCIS (Netherlands)

Procaccianti, G.; Fernandez, H.J.; Lago, P.

2016-01-01

Background. Energy efficiency is an increasingly important property of software. A large number of empirical studies have been conducted on the topic. However, current state-of-the-Art does not provide empirically-validated guidelines for developing energy-efficient software. Aim. This study aims at

CheMentor Software System by H. A. Peoples

Science.gov (United States)

Reid, Brian P.

1997-09-01

CheMentor Software System H. A. Peoples. Computerized Learning Enhancements: http://www.ecis.com/~clehap; email: clehap@ecis.com; 1996 - 1997. CheMentor is a series of software packages for introductory-level chemistry, which includes Practice Items (I), Stoichiometry (I), Calculating Chemical Formulae, and the CheMentor Toolkit. The first three packages provide practice problems for students and various types of help to solve them; the Toolkit includes "calculators" for determining chemical quantities as well as the Practice Items (I) set of problems. The set of software packages is designed so that each individual product acts as a module of a common CheMentor program. As the name CheMentor implies, the software is designed as a "mentor" for students learning introductory chemistry concepts and problems. The typical use of the software would be by individual students (or perhaps small groups) as an adjunct to lectures. CheMentor is a HyperCard application and the modules are HyperCard stacks. The requirements to run the packages include a Macintosh computer with at least 1 MB of RAM, a hard drive with several MB of available space depending upon the packages selected (10 MB were required for all the packages reviewed here), and the Mac operating system 6.0.5 or later.

Pushouts in software architecture design

OpenAIRE

Riché, T. L.; Gonçalves, Rui; Marker, B.; Batory, D.

2012-01-01

A classical approach to program derivation is to progressively extend a simple specification and then incrementally refine it to an implementation. We claim this approach is hard or impractical when reverse engineering legacy software architectures. We present a case study that shows optimizations and pushouts--in addition to refinements and extensions--are essential for practical stepwise development of complex software architectures. NSF CCF 0724979 NSF CNS 0509338 NSF CCF 0917167 ...

Software inspections at Fermilab -- Use and experience

International Nuclear Information System (INIS)

Berman, E.F.

1998-01-01

Because of the critical nature of DA/Online software it is important to commission software which is correct, usable, reliable, and maintainable, i.e., has the highest quality possible. In order to help meet these goals Fermi National Accelerator Laboratory (Fermilab) has begun implementing a formal software inspection process. Formal Inspections are used to reduce the number of defects in software at as early a stage as possible. These Inspections, in use at a wide variety of institutions (e.g., NASA, Motorola), implement a well-defined procedure that can be used to improve the quality of many different types of deliverables. The inspection process, initially designed by Michael Fagan, will be described as it was developed and as it is currently implemented at Fermilab where it has been used to improve the quality of a variety of different experiment DA/Online software. Benefits of applying inspections at many points in the software life-cycle and benefits to the people involved will be investigated. Experience with many different types of Inspections and the lessons learned about the inspection process itself will be detailed. Finally, the future of Inspections at Fermilab will be given

Human-centred radiological software techniques supporting improved nuclear safety

International Nuclear Information System (INIS)

Szoeke, Istvan; Johnsen, Terje

2013-01-01

The Institute for Energy Technology (IFE) is an international research foundation for energy and nuclear technology. IFE is also the host for the international OECD Halden Reactor Project. The Software Engineering Department in the Man Technology Organisation at IFE is a leading international centre of competence for the development and evaluation of human-centred technologies, process visualisation, and the lifecycle of high integrity software important to safety. This paper is an attempt to give a general overview of the current, and some of the foreseen, research and development of human-centred radiological software technologies at the Software Engineering department to meet with the need of improved radiological safety for not only nuclear industry but also other industries around the world. (author)

Finding Security Patterns to Countermeasure Software Vulnerabilities

OpenAIRE

Borstad, Ole Gunnar

2008-01-01

Software security is an increasingly important part of software development as the risk from attackers is constantly evolving through increased exposure, threats and economic impact of security breaches. Emerging security literature describes expert knowledge such as secure development best practices. This knowledge is often not applied by software developers because they lack security awareness, security training and secure development methods and tools. Existing methods and tools require to...

[Use of Adobe Photoshop software in medical criminology].

Science.gov (United States)

Nikitin, S A; Demidov, I V

2000-01-01

Describes the method of comparative analysis of various objects in practical medical criminology and making of high-quality photographs with the use of Adobe Photoshop software. Options of the software needed for expert evaluations are enumerated.

9th Transgenic Technology Meeting (TT2010) in Berlin, Germany: a meeting report.

Science.gov (United States)

Saunders, Thomas L; Sobieszczuk, Peter

2010-12-01

The first Transgenic Technology (TT) Meeting was organized in 1999 by Johannes Wilbertz, Karolinska Institute, Stockholm, Sweden as a regional meeting. The TT Meetings continued in this way, constantly gathering additional practitioners of transgenic methodologies until the breakthrough in 2005 when the 6th TT Meeting in Barcelona, Spain, hosted by Lluis Montoliu (Centro Nacional de Biotecnologia, Madrid, Spain), generated the momentum to establish the International Society for Transgenic Technologies (ISTT). Since 2006, the ISTT has continued to promote the TT Meetings and provide its membership with a forum to discuss best practices and new methods in the field. The TT2010 Meeting was held at the Max Delbrück Center for Molecular Medicine (Berlin, Germany). Participation at the TT2010 Meeting exceeded the registration capacity and set a new attendance record. Session topics included methods for the generation of rat and mouse models of human disease, fundamental and advanced topics in rodent embryonic stem cells, and the newest transgenic technologies. Short presentations from selected abstracts were of especial interest. Roundtable discussions on transgenic facility establishment and cryoarchiving of mouse lines were favorably received. Students, technical staff, and professors participated in numerous discussions and came away with practical methods and new ideas for research.

The Role of Ethnographic Studies in Empirical Software Engineering

DEFF Research Database (Denmark)

Sharp, Helen; Dittrich, Yvonne; Souza, Cleidson R. B. de

2016-01-01

Ethnography is a qualitative research method used to study people and cultures. It is largely adopted in disciplines outside software engineering, including different areas of computer science. Ethnography can provide an in-depth understanding of the socio-technological realities surrounding ever...... as a useful and usable approach to empirical software engineering research. Throughout the paper, relevant examples of ethnographic studies of software practice are used to illustrate the points being made.......Ethnography is a qualitative research method used to study people and cultures. It is largely adopted in disciplines outside software engineering, including different areas of computer science. Ethnography can provide an in-depth understanding of the socio-technological realities surrounding...... everyday software development practice, i.e., it can help to uncover not only what practitioners do, but also why they do it. Despite its potential, ethnography has not been widely adopted by empirical software engineering researchers, and receives little attention in the related literature. The main goal...

A new paradigm for the development of analysis software

International Nuclear Information System (INIS)

Kelly, D.; Harauz, J.

2012-01-01

For the CANDU industry, analysis software is an important tool for scientists and engineers to examine issues related to safety, operation, and design. However, the software quality assurance approach currently used for these tools assumes the software is the delivered product. In this paper, we present a model that shifts the emphasis from software being the end-product to software being support for the end-product, the science. We describe a novel software development paradigm that supports this shift and provides the groundwork for re-examining the quality assurance practices used for analysis software. (author)

Software architecture design patterns in Java

CERN Document Server

Kuchana, Partha

2004-01-01

AN INTRODUCTION TO DESIGN PATTERNSDesign Patterns: Origin and HistoryArchitectural to Software Design PatternsWhat is a Design Pattern?More about Design PatternsAbout This BookUNIFIED MODELING LANGUAGE (UML)UML: A Quick ReferenceClass DiagramsSequence diagramsBASIC PATTERNSInterfaceDescriptionExamplePractice QuestionsAbstract Parent ClassDescriptionExamplePractice QuestionsPrivate MethodsDescriptionExamplePractice QuestionsAccessor MethodsDescriptionAccessor Method NomenclatureExampleDirect Reference versus Accessor MethodsPractice QuestionsConstant Data ManagerDescriptionExamplePractice Quest

Agile distributed software development

DEFF Research Database (Denmark)

Persson, John Stouby; Mathiassen, Lars; Aaen, Ivan

2012-01-01

While face-to-face interaction is fundamental in agile software development, distributed environments must rely extensively on mediated interactions. Practicing agile principles in distributed environments therefore poses particular control challenges related to balancing fixed vs. evolving quality...... requirements and people vs. process-based collaboration. To investigate these challenges, we conducted an in-depth case study of a successful agile distributed software project with participants from a Russian firm and a Danish firm. Applying Kirsch’s elements of control framework, we offer an analysis of how...

Green in software engineering

CERN Document Server

Calero Munoz, Coral

2015-01-01

This is the first book that presents a comprehensive overview of sustainability aspects in software engineering. Its format follows the structure of the SWEBOK and covers the key areas involved in the incorporation of green aspects in software engineering, encompassing topics from requirement elicitation to quality assurance and maintenance, while also considering professional practices and economic aspects. The book consists of thirteen chapters, which are structured in five parts. First the "Introduction" gives an overview of the primary general concepts related to Green IT, discussing wha

The Generalizability of Private Sector Research on Software Project Management in Two USAF Organizations: An Exploratory Study

National Research Council Canada - National Science Library

Garman, Michael

2003-01-01

... budget. However, software projects frequently fail to meet these criteria. Software engineers, acquisition officers, and project managers have all studied this issue and made recommendations for achieving success...

The conformity of asset control software to the principles of CPC 27 and ICPC 10

Directory of Open Access Journals (Sweden)

Paulo Roberto da Cunha

2014-07-01

Full Text Available The convergence of Brazilian accounting to international standards also requires adjusting accounting software to the new rules. In 2009, SEC Resolution No. 583 and CFC Resolution No. 1177 made it mandatory toapply Pronouncement 27 of the Accounting Procedures Committee, concerning Fixed Assets. The goal of this study is to verify whether the asset control software meets the requirements of CPC 27 and ICPC 10. A descriptive, qualitative study was carried out using a multi case study. An interview guide, with the items discussed in CPC 27 and ICPC 10, was applied to the software developers to control assets of three software companies in southern Brazil. The survey results show that the overall average of the three companies examined was 86% of compliance to the topics covered in this research. It was concluded that, in general, asset control software meets the precepts of CPC 27 and ICPC10, except for impairment and deemed cost concepts, which were not covered.

Identifying Relevant Studies in Software Engineering

DEFF Research Database (Denmark)

Zhang, He; Ali Babar, Muhammad; Tell, Paolo

2011-01-01

Context: Systematic literature review (SLR) has become an important research methodology in software engineering since the introduction of evidence-based software engineering (EBSE) in 2004. One critical step in applying this methodology is to design and execute appropriate and effective search....... Objective: The main objective of the research reported in this paper is to improve the search step of undertaking SLRs in software engineering (SE) by devising and evaluating systematic and practical approaches to identifying relevant studies in SE. Method: We have systematically selected and analytically...

Software Estimation Demystifying the Black Art

CERN Document Server

McConnell, Steve

2009-01-01

Often referred to as the "black art" because of its complexity and uncertainty, software estimation is not as difficult or puzzling as people think. In fact, generating accurate estimates is straightforward-once you understand the art of creating them. In his highly anticipated book, acclaimed author Steve McConnell unravels the mystery to successful software estimation-distilling academic information and real-world experience into a practical guide for working software professionals. Instead of arcane treatises and rigid modeling techniques, this guide highlights a proven set of procedures,

Toward an Agile Approach to Managing the Effect of Requirements on Software Architecture during Global Software Development

Directory of Open Access Journals (Sweden)

Abdulaziz Alsahli

2016-01-01

Full Text Available Requirement change management (RCM is a critical activity during software development because poor RCM results in occurrence of defects, thereby resulting in software failure. To achieve RCM, efficient impact analysis is mandatory. A common repository is a good approach to maintain changed requirements, reusing and reducing effort. Thus, a better approach is needed to tailor knowledge for better change management of requirements and architecture during global software development (GSD.The objective of this research is to introduce an innovative approach for handling requirements and architecture changes simultaneously during global software development. The approach makes use of Case-Based Reasoning (CBR and agile practices. Agile practices make our approach iterative, whereas CBR stores requirements and makes them reusable. Twin Peaks is our base model, meaning that requirements and architecture are handled simultaneously. For this research, grounded theory has been applied; similarly, interviews from domain experts were conducted. Interview and literature transcripts formed the basis of data collection in grounded theory. Physical saturation of theory has been achieved through a published case study and developed tool. Expert reviews and statistical analysis have been used for evaluation. The proposed approach resulted in effective change management of requirements and architecture simultaneously during global software development.

Meeting summary of the second CSNI specialist meeting on simulators and plant analyzers - Current Issues in Nuclear Power Plant Simulation

International Nuclear Information System (INIS)

1998-01-01

simulators and plant analyzers. One of the main interests were the interconnection of analysis level models in real time applications. Session V: Plant analysis applications. This session was planned to cover the various applications of plant analyzers in plant design evaluation, system qualification, development of operation procedures and safety analysis. The new concepts such as multifunctional simulators and Living Plant Analyzers supporting many of the above mentioned applications and adding features like evaluation and testing of new control systems and operator support tools. Session VI: Simulator validation and qualification. This session concentrated on simulator validation and qualification procedures followed in the training centers as well as on the problems encountered in areas such as severe accidents and accident management. The requalification of the simulator was also a topic of discussion. Major conclusions of the meeting: The major conclusions of the meeting can be summarised as follows: - The role of simulators is changing and the applications are becoming more diverse. - The differences between training simulator and plant analyzer software are disappearing. - It would be useful to establish a basis, or a set of rules for comparison of simulators. A small group of experts should be formed to study feasibility and benefits of such an exercise and possible comparison criteria. - The themes of SAMOA meetings appear almost as a subset of this series of meetings. In the future, these meetings could well be combined. - A suggestion was made to develop a simulator for plant maintenance procedure practices

A Reference Architecture for Distributed Software Deployment

NARCIS (Netherlands)

Van der Burg, S.

2013-01-01

Nowadays, software systems are bigger and more complicated than people may think. Apart from the fact that a system has to be correctly constructed and should meet the client's wishes, they also have to be made ready for use to end-users or in an isolated test environment. This process is known as

Saltwell Leak Detector Station Programmable Logic Controller (PLC) Software Configuration Management Plan (SCMP)

International Nuclear Information System (INIS)

WHITE, K.A.

2000-01-01

This document provides the procedures and guidelines necessary for computer software configuration management activities during the operation and maintenance phases of the Saltwell Leak Detector Stations as required by HNF-PRO-309/Rev.1, Computer Software Quality Assurance, Section 2.4, Software Configuration Management. The software configuration management plan (SCMP) integrates technical and administrative controls to establish and maintain technical consistency among requirements, physical configuration, and documentation for the Saltwell Leak Detector Station Programmable Logic Controller (PLC) software during the Hanford application, operations and maintenance. This SCMP establishes the Saltwell Leak Detector Station PLC Software Baseline, status changes to that baseline, and ensures that software meets design and operational requirements and is tested in accordance with their design basis

Web Application Software for Ground Operations Planning Database (GOPDb) Management

Science.gov (United States)

Lanham, Clifton; Kallner, Shawn; Gernand, Jeffrey

2013-01-01

A Web application facilitates collaborative development of the ground operations planning document. This will reduce costs and development time for new programs by incorporating the data governance, access control, and revision tracking of the ground operations planning data. Ground Operations Planning requires the creation and maintenance of detailed timelines and documentation. The GOPDb Web application was created using state-of-the-art Web 2.0 technologies, and was deployed as SaaS (Software as a Service), with an emphasis on data governance and security needs. Application access is managed using two-factor authentication, with data write permissions tied to user roles and responsibilities. Multiple instances of the application can be deployed on a Web server to meet the robust needs for multiple, future programs with minimal additional cost. This innovation features high availability and scalability, with no additional software that needs to be bought or installed. For data governance and security (data quality, management, business process management, and risk management for data handling), the software uses NAMS. No local copy/cloning of data is permitted. Data change log/tracking is addressed, as well as collaboration, work flow, and process standardization. The software provides on-line documentation and detailed Web-based help. There are multiple ways that this software can be deployed on a Web server to meet ground operations planning needs for future programs. The software could be used to support commercial crew ground operations planning, as well as commercial payload/satellite ground operations planning. The application source code and database schema are owned by NASA.

Software quality assurance (SQA) for Savannah River reactors

Energy Technology Data Exchange (ETDEWEB)

Schaumann, C.M.

1990-01-01

Over the last 25 years, the Savannah River Site (SRS) has developed a strong Software Quality Assurance (SQA) program. It provides the information and management controls required of a high quality auditable system. The SRS SQA program provides the framework to meet the requirements in increasing regulation.

Learning software testing with Test Studio

CERN Document Server

Madi, Rawane

2013-01-01

Learning Software Testing with Test Studio is a practical, hands-on guide that will help you get started with Test Studio to design your automated solution and tests. All through the book, there are best practices and tips and tricks inside Test Studio which can be employed to improve your solution just like an experienced QA.If you are a beginner or a professional QA who is seeking a fast, clear, and direct to the point start in automated software testing inside Test Studio, this book is for you. You should be familiar with the .NET framework, mainly Visual Studio, C#, and SQL, as the book's

Training managers to facilitate their meetings: An intervention study

DEFF Research Database (Denmark)

Ravn, Ib

2014-01-01

-based intervention effort to improve organisational meetings. It reconceptualises classical meeting management, offering instead the practice of ‘meeting facilitation’: a more active and supportive approach, in which the manager-as-facilitator guides and directs conversations in meetings towards a positive goal...... showed that in the employees’ judgement, there were significant improvements in their managers’ competencies in both new meeting facilitation and classical meeting management, whereas other meeting outcomes resisted change.......Meetings in organisations are a common object of popular frustration. They are often run by managers who picked up their meeting skills from their superiors a generation previously, thus perpetuating obsolescent practices unsuited to today’s world of work. This paper reports on a research...

Practical Software Measurement: Measuring for Process Management and Improvement

National Research Council Canada - National Science Library

Florac, William

1997-01-01

This guidebook shows how well-established principles and methods for evaluating and controlling process performance can be applied in software settings to help achieve an organization's business and technical goals...

Development of an intelligent ultrasonic welding defect classification software

International Nuclear Information System (INIS)

Song, Sung Jin; Kim, Hak Joon; Jeong, Hee Don

1997-01-01

Ultrasonic pattern recognition is the most effective approach to the problem of discriminating types of flaws in weldments based on ultrasonic flaw signals. In spite of significant progress in the research on this methodology, it has not been widely used in many practical ultrasonic inspections of weldments in industry. Hence, for the convenient application of this approach in many practical situations, we develop an intelligent ultrasonic signature classification software which can discriminate types of flaws in weldments based on their ultrasonic signals using various tools in artificial intelligence such as neural networks. This software shows the excellent performance in an experimental problem where flaws in weldments are classified into two categories of cracks and non-cracks. This performance demonstrates the high possibility of this software as a practical tool for ultrasonic flaw classification in weldments.

A folk theory of meetings -- and beyond

DEFF Research Database (Denmark)

Ravn, Ib

2013-01-01

with managers and employees we extracted six common assumptions about meetings, termed a folk theory of meetings, which most office workers seem to carry in the back of their minds. Findings This folk theory holds meetings to be places for excessive talk, whether by a domineering leader or highly vocal...... participants, the purpose of which is to walk through the items on the agenda and dispose of each. This bleak and conservative concept of a meeting impedes intellectual as well as practical progress. Practical implications An alternative theory of meetings is proposed, one based on the group facilitation...... training, this view of meetings—and the widely available facilitation tools that go with it—may render meetings at work the subject of conscious organizational development. Originality/value The proposed "folk theory of meetings" is novel, as is the contrast provided with the facilitation approach...

SCaN Testbed Software Development and Lessons Learned

Science.gov (United States)

Kacpura, Thomas J.; Varga, Denise M.

2012-01-01

National Aeronautics and Space Administration (NASA) has developed an on-orbit, adaptable, Software Defined Radio (SDR)Space Telecommunications Radio System (STRS)-based testbed facility to conduct a suite of experiments to advance technologies, reduce risk, and enable future mission capabilities on the International Space Station (ISS). The SCAN Testbed Project will provide NASA, industry, other Government agencies, and academic partners the opportunity to develop and field communications, navigation, and networking technologies in the laboratory and space environment based on reconfigurable, SDR platforms and the STRS Architecture.The SDRs are a new technology for NASA, and the support infrastructure they require is different from legacy, fixed function radios. SDRs offer the ability to reconfigure on-orbit communications by changing software for new waveforms and operating systems to enable new capabilities or fix any anomalies, which was not a previous option. They are not stand alone devices, but required a new approach to effectively control them and flow data. This requires extensive software to be developed to utilize the full potential of these reconfigurable platforms. The paper focuses on development, integration and testing as related to the avionics processor system, and the software required to command, control, monitor, and interact with the SDRs, as well as the other communication payload elements. An extensive effort was required to develop the flight software and meet the NASA requirements for software quality and safety. The flight avionics must be radiation tolerant, and these processors have limited capability in comparison to terrestrial counterparts. A big challenge was that there are three SDRs onboard, and interfacing with multiple SDRs simultaneously complicatesd the effort. The effort also includes ground software, which is a key element for both the command of the payload, and displaying data created by the payload. The verification of

Alinhando objetivos estratégicos e processo de desenvolvimento em empresas de software Aligning strategic objectives and development practices at software companies

Directory of Open Access Journals (Sweden)

André Leme Fleury

2013-01-01

Full Text Available Sistemas de software são atualmente responsáveis por parte significativa das inovações tecnológicas viabilizadas em produtos e serviços. A história do software é recente, assim como são recentes as pesquisas sobre o tema, que tem como foco principal o aprimoramento dos seus processos de desenvolvimento. Apesar das contribuições trazidas por essas teorias, a questão do alinhamento entre objetivos estratégicos e o processo de desenvolvimento nas empresas de software considerando as suas principais capacidades produtivas permanece um tema inexplorado. Como consequência, técnicas da engenharia de software são aplicadas sem incorporar considerações de valor nos processos de análise e na tomada de decisões. Este artigo analisa e apresenta soluções para duas questões: como diferenciar as empresas de software de acordo com seus processos produtivos mais relevantes e como garantir que esses processos de desenvolvimento encontram-se alinhados com os objetivos do negócio. A abordagem resultante inclui um referencial para classificação de empresas de software e uma técnica de planejamento tecnológico para essas empresas. O projeto de pesquisa incluiu a realização de surveys, pesquisa-ação e estudos de caso.Software systems are currently responsible for a significant part of the technological innovations introduced in products and services. software history is recent and research concerning software usually aims to improve process capabilities. Despite the contributions of these theories, questions concerning the alignment between strategic objectives and development process at software companies considering their most important capabilities have not been clarified. Consequently, software engineering techniques are applied without value considerations for analysis and decision. This paper analyses and proposes solutions for two issues: how to differentiate software companies according with their most relevant development

A Hybrid Hardware and Software Component Architecture for Embedded System Design

Science.gov (United States)

Marcondes, Hugo; Fröhlich, Antônio Augusto

Embedded systems are increasing in complexity, while several metrics such as time-to-market, reliability, safety and performance should be considered during the design of such systems. A component-based design which enables the migration of its components between hardware and software can cope to achieve such metrics. To enable that, we define hybrid hardware and software components as a development artifact that can be deployed by different combinations of hardware and software elements. In this paper, we present an architecture for developing such components in order to construct a repository of components that can migrate between the hardware and software domains to meet the design system requirements.

Software Quality in the Trenches: Two Case Studies of Quality Assurance Practices in Free/Libre and Open Source Software (FLOSS)

OpenAIRE

Vestbø, Tor Arne

2007-01-01

When proponents of open source software are asked to explain the success of their movement they typically point to the quality of the software produced, which is in turn attributed to the rather unconventional development model of releasing unfinished versions of the software and having users look over the code and report and fix bugs. This thesis investigates the open source quality assurance model from a knowledge management perspective based on the assumption that debugging involves a h...

Requirements engineering for software and systems

CERN Document Server

Laplante, Phillip A

2014-01-01

Solid requirements engineering has increasingly been recognized as the key to improved, on-time and on-budget delivery of software and systems projects. This book provides practical teaching for graduate and professional systems and software engineers. It uses extensive case studies and exercises to help students grasp concepts and techniques. With a focus on software-intensive systems, this text provides a probing and comprehensive review of recent developments in intelligent systems, soft computing techniques, and their diverse applications in manufacturing. The second edition contains 100% revised content and approximately 30% new material

Using MIQUEST in General Practice

Directory of Open Access Journals (Sweden)

Victoria Hammersley

1998-11-01

Full Text Available This paper describes ten months' experience with MIQUEST software used for the collection of data from computerised databases in General Practice. We report on the following: the MIQUEST software in use, the time costs to the practice, the completeness of confidentiality barriers and the accuracy of data collected using MIQUEST compared with similar data collected by the practice system (EMIS. There were no problems encountered with installation of MIQUEST-related software. With experience, MIQUEST was equal to the practice system for speed and ease of use. The confidentiality safeguards were found to be in accordance with the GMSC/RCGP Guidelines - patients could not be directly, or indirectly, identified from the data extracted by external searches. Inaccuracies in the data collected using MIQUEST were identified, but these were largely attributable to problems with the EMIS-written interpreter available on the practice system at the time, or with the coding schemes used by the practice. In an individual practice, MIQUEST represents an alternative data collection method to the practice-based software. For data collection from multiple general practices it should prove an invaluable tool for Health Authorities and research organisations.

The Legacy of Space Shuttle Flight Software

Science.gov (United States)

Hickey, Christopher J.; Loveall, James B.; Orr, James K.; Klausman, Andrew L.

2011-01-01

The initial goals of the Space Shuttle Program required that the avionics and software systems blaze new trails in advancing avionics system technology. Many of the requirements placed on avionics and software were accomplished for the first time on this program. Examples include comprehensive digital fly-by-wire technology, use of a digital databus for flight critical functions, fail operational/fail safe requirements, complex automated redundancy management, and the use of a high-order software language for flight software development. In order to meet the operational and safety goals of the program, the Space Shuttle software had to be extremely high quality, reliable, robust, reconfigurable and maintainable. To achieve this, the software development team evolved a software process focused on continuous process improvement and defect elimination that consistently produced highly predictable and top quality results, providing software managers the confidence needed to sign each Certificate of Flight Readiness (COFR). This process, which has been appraised at Capability Maturity Model (CMM)/Capability Maturity Model Integration (CMMI) Level 5, has resulted in one of the lowest software defect rates in the industry. This paper will present an overview of the evolution of the Primary Avionics Software System (PASS) project and processes over thirty years, an argument for strong statistical control of software processes with examples, an overview of the success story for identifying and driving out errors before flight, a case study of the few significant software issues and how they were either identified before flight or slipped through the process onto a flight vehicle, and identification of the valuable lessons learned over the life of the project.

Applying object-oriented software engineering at the BaBar collaboration

International Nuclear Information System (INIS)

Jacobsen, B.

1997-01-01

The BaBar experiment at SLAC will start taking data in 1999. We are attempting to build its reconstruction software using good software engineering practices, including the use of object-oriented technology. We summarize our experience to date with analysis and design activities, training, CASE and documentation tools, C++ programming practice and similar topics. The emphasis is on the practical issues of simultaneously introducing new techniques to a large collaboration while under a deadline for system delivery. (orig.)

Software important to safety in nuclear power plants

International Nuclear Information System (INIS)

1994-01-01

The report provides guidance on current practices, documenting their strengths and weaknesses for dealing with the important issues of software engineering that nuclear power plant system designers, software producers and regulators are facing. The focus of the report is on safety critical applications of general purpose processors controlled by custom developed software; however, it should also have application in safety related applications and for other types of computers. In addition to system designers, software producers and regulators, the intended readership of this report includes users of software based systems, who should be aware of the relevant issues in specifying and obtaining software for systems important to safety. Refs, 1 fig., tabs

Advanced engineering software for in-space assembly and manned planetary spacecraft

Science.gov (United States)

Delaquil, Donald; Mah, Robert

1990-01-01

Meeting the objectives of the Lunar/Mars initiative to establish safe and cost-effective extraterrestrial bases requires an integrated software/hardware approach to operational definitions and systems implementation. This paper begins this process by taking a 'software-first' approach to systems design, for implementing specific mission scenarios in the domains of in-space assembly and operations of the manned Mars spacecraft. The technological barriers facing implementation of robust operational systems within these two domains are discussed, and preliminary software requirements and architectures that resolve these barriers are provided.

Computer systems and software engineering

Science.gov (United States)

Mckay, Charles W.

1988-01-01

The High Technologies Laboratory (HTL) was established in the fall of 1982 at the University of Houston Clear Lake. Research conducted at the High Tech Lab is focused upon computer systems and software engineering. There is a strong emphasis on the interrelationship of these areas of technology and the United States' space program. In Jan. of 1987, NASA Headquarters announced the formation of its first research center dedicated to software engineering. Operated by the High Tech Lab, the Software Engineering Research Center (SERC) was formed at the University of Houston Clear Lake. The High Tech Lab/Software Engineering Research Center promotes cooperative research among government, industry, and academia to advance the edge-of-knowledge and the state-of-the-practice in key topics of computer systems and software engineering which are critical to NASA. The center also recommends appropriate actions, guidelines, standards, and policies to NASA in matters pertinent to the center's research. Results of the research conducted at the High Tech Lab/Software Engineering Research Center have given direction to many decisions made by NASA concerning the Space Station Program.

FRAMES Software System: Linking to the Statistical Package R

Energy Technology Data Exchange (ETDEWEB)

Castleton, Karl J.; Whelan, Gene; Hoopes, Bonnie L.

2006-12-11

This document provides requirements, design, data-file specifications, test plan, and Quality Assurance/Quality Control protocol for the linkage between the statistical package R and the Framework for Risk Analysis in Multimedia Environmental Systems (FRAMES) Versions 1.x and 2.0. The requirements identify the attributes of the system. The design describes how the system will be structured to meet those requirements. The specification presents the specific modifications to FRAMES to meet the requirements and design. The test plan confirms that the basic functionality listed in the requirements (black box testing) actually functions as designed, and QA/QC confirms that the software meets the client’s needs.

A study on quantitative V and V of safety-critical software

International Nuclear Information System (INIS)

Eom, H. S.; Kang, H. G.; Chang, S. C.; Ha, J. J.; Son, H. S.

2004-03-01

Recently practical needs have required quantitative features for the software reliability for Probabilistic Safety Assessment which is one of the important methods being used in assessing the overall safety of nuclear power plant. But the conventional assessment methods of software reliability could not provide enough information for PSA of NPP, therefore current assessments of a digital system which includes safety-critical software usually exclude the software part or use arbitrary values. This paper describes a Bayesian Belief Networks based method that models the rule-based qualitative software assessment method for a practical use and can produce quantitative results for PSA. The framework was constructed by utilizing BBN that can combine the qualitative and quantitative evidence relevant to the reliability of safety-critical software and can infer a conclusion in a formal and a quantitative way. The case study was performed by applying the method for assessing the quality of software requirement specification of safety-critical software that will be embedded in reactor protection system

A Conceptual Framework for Lean Regulated Software Development

DEFF Research Database (Denmark)

Cawley, Oisin; Richardson, Ita; Wang, Xiaofeng

2015-01-01

for software development within a regulated environment? This poster presents the results of our empirical research into lean and regulated software development. Built from a combination of data sources, we have developed a conceptual framework comprising five primary components. In addition the relationships...... they have with both the central focus of the framework (the situated software development practices) and with each other are indicated....

Software Quality Assurance for Nuclear Safety Systems

International Nuclear Information System (INIS)

Sparkman, D R; Lagdon, R

2004-01-01

The US Department of Energy has undertaken an initiative to improve the quality of software used to design and operate their nuclear facilities across the United States. One aspect of this initiative is to revise or create new directives and guides associated with quality practices for the safety software in its nuclear facilities. Safety software includes the safety structures, systems, and components software and firmware, support software and design and analysis software used to ensure the safety of the facility. DOE nuclear facilities are unique when compared to commercial nuclear or other industrial activities in terms of the types and quantities of hazards that must be controlled to protect workers, public and the environment. Because of these differences, DOE must develop an approach to software quality assurance that ensures appropriate risk mitigation by developing a framework of requirements that accomplishes the following goals: (sm b ullet) Ensures the software processes developed to address nuclear safety in design, operation, construction and maintenance of its facilities are safe (sm b ullet) Considers the larger system that uses the software and its impacts (sm b ullet) Ensures that the software failures do not create unsafe conditions Software designers for nuclear systems and processes must reduce risks in software applications by incorporating processes that recognize, detect, and mitigate software failure in safety related systems. It must also ensure that fail safe modes and component testing are incorporated into software design. For nuclear facilities, the consideration of risk is not necessarily sufficient to ensure safety. Systematic evaluation, independent verification and system safety analysis must be considered for software design, implementation, and operation. The software industry primarily uses risk analysis to determine the appropriate level of rigor applied to software practices. This risk-based approach distinguishes safety

A data model for clinical legal medicine practice and the development of a dedicated software for both practitioners and researchers.

Science.gov (United States)

Dang, Catherine; Phuong, Thomas; Beddag, Mahmoud; Vega, Anabel; Denis, Céline

2018-07-01

To present a data model for clinical legal medicine and the software based on that data model for both practitioners and researchers. The main functionalities of the presented software are computer-assisted production of medical certificates and data capture, storage and retrieval. The data model and the software were jointly developed by the department of forensic medicine of the Jean Verdier Hospital (Bondy, France) and an bioinformatics laboratory (LIMICS, Paris universities 6-13) between November 2015 and May 2016. The data model was built based on four sources: i) a template used in our department for producing standardised medical certificates; ii) a random sample of medical certificates produced by the forensic department; iii) anterior consensus between four healthcare professionals (two forensic practitioners, a psychologist and a forensic psychiatrist) and iv) anatomical dictionaries. The trial version of the open source software was first designed for examination of physical assault survivors. An UML-like data model dedicated to clinical legal practice was built. The data model describes the terminology for examinations of sexual assault survivors, physical assault survivors, individuals kept in police custody and undocumented migrants for age estimation. A trial version of a software relying on the data model was developed and tested by three physicians. The software allows files archiving, standardised data collection, extraction and assistance for certificate generation. It can be used for research purpose, by data exchange and analysis. Despite some current limitations of use, it is a tool which can be shared and used by other departments of forensic medicine and other specialties, improving data management and exploitation. Full integration with external sources, analytics software and use of a semantic interoperability framework are planned for the next months. Copyright © 2016 Elsevier Ltd and Faculty of Forensic and Legal Medicine. All rights

Software Testing An ISTQB-ISEB Foundation Guide

CERN Document Server

Hambling, Brian; Morgan, Peter; Samaroo, Angelina; Thompson, Geoff; Williams, Peter

2010-01-01

This practical guide provides insight into software testing, explaining the basics of the testing process and how to perform effective tests. It provides an overview of different techniques and how to apply them. It is the bestselling official textbook of the ISTQB - ISEB Foundation Certificate in Software Testing, updated to the 2010 syllabus.

Trust in Co-sourced Software Development

DEFF Research Database (Denmark)

Schlichter, Bjarne Rerup; Persson, John Stouby

2014-01-01

Software development projects are increasingly geographical distributed with offshoring. Co-sourcing is a highly integrative and cohesive approach, seen successful, to software development offshoring. However, research of how dynamic aspects of trust are shaped in co-sourcing activities is limite...... understanding or personal trust relations. The paper suggests how certain work practices among developers and managers can be explained using a dynamic trust lens based on Abstract Systems, especially dis- and re-embedding mechanisms......Software development projects are increasingly geographical distributed with offshoring. Co-sourcing is a highly integrative and cohesive approach, seen successful, to software development offshoring. However, research of how dynamic aspects of trust are shaped in co-sourcing activities is limited...

CMS Software and Computing Ready for Run 2

CERN Document Server

Bloom, Kenneth

2015-01-01

In Run 1 of the Large Hadron Collider, software and computing was a strategic strength of the Compact Muon Solenoid experiment. The timely processing of data and simulation samples and the excellent performance of the reconstruction algorithms played an important role in the preparation of the full suite of searches used for the observation of the Higgs boson in 2012. In Run 2, the LHC will run at higher intensities and CMS will record data at a higher trigger rate. These new running conditions will provide new challenges for the software and computing systems. Over the two years of Long Shutdown 1, CMS has built upon the successes of Run 1 to improve the software and computing to meet these challenges. In this presentation we will describe the new features in software and computing that will once again put CMS in a position of physics leadership.

Case Study Research in Software Engineering Guidelines and Examples

CERN Document Server

Runeson, Per; Rainer, Austen; Regnell, Bjorn

2012-01-01

Based on their own experiences of in-depth case studies of software projects in international corporations, in this book the authors present detailed practical guidelines on the preparation, conduct, design and reporting of case studies of software engineering.  This is the first software engineering specific book on the case study research method.

78 FR 14091 - Sunshine Act Meetings

Science.gov (United States)

2013-03-04

... business requires that this notice be issued less than one week prior to the meeting and that earlier... Vice President, Business Development and Strategy, Communications and Data Services, Comcast 2:35 p.m... Emergency Management Fred Wolens, Public Policy Team Member, Facebook Ari Gesher, Senior Software Engineer...

Network-based analysis of software change propagation.

Science.gov (United States)

Wang, Rongcun; Huang, Rubing; Qu, Binbin

2014-01-01

The object-oriented software systems frequently evolve to meet new change requirements. Understanding the characteristics of changes aids testers and system designers to improve the quality of softwares. Identifying important modules becomes a key issue in the process of evolution. In this context, a novel network-based approach is proposed to comprehensively investigate change distributions and the correlation between centrality measures and the scope of change propagation. First, software dependency networks are constructed at class level. And then, the number of times of cochanges among classes is minded from software repositories. According to the dependency relationships and the number of times of cochanges among classes, the scope of change propagation is calculated. Using Spearman rank correlation analyzes the correlation between centrality measures and the scope of change propagation. Three case studies on java open source software projects Findbugs, Hibernate, and Spring are conducted to research the characteristics of change propagation. Experimental results show that (i) change distribution is very uneven; (ii) PageRank, Degree, and CIRank are significantly correlated to the scope of change propagation. Particularly, CIRank shows higher correlation coefficient, which suggests it can be a more useful indicator for measuring the scope of change propagation of classes in object-oriented software system.

Exploring the Role of Usability in the Software Process: A Study of Irish Software SMEs

Science.gov (United States)

O'Connor, Rory V.

This paper explores the software processes and usability techniques used by Small and Medium Enterprises (SMEs) that develop web applications. The significance of this research is that it looks at development processes used by SMEs in order to assess to what degree usability is integrated into the process. This study seeks to gain an understanding into the level of awareness of usability within SMEs today and their commitment to usability in practice. The motivation for this research is to explore the current development processes used by SMEs in developing web applications and to understand how usability is represented in those processes. The background for this research is provided by the growth of the web application industry beyond informational web sites to more sophisticated applications delivering a broad range of functionality. This paper presents an analysis of the practices of several Irish SMEs that develop web applications through a series of case studies. With the focus on SMEs that develop web applications as Management Information Systems and not E-Commerce sites, informational sites, online communities or web portals. This study gathered data about the usability techniques practiced by these companies and their awareness of usability in the context of the software process in those SMEs. The contribution of this study is to further the understanding of the current role of usability within the software development processes of SMEs that develop web applications.

New Media as Software

Directory of Open Access Journals (Sweden)

Manuel Portela

2014-03-01

Full Text Available Review of Lev Manovich, Software Takes Command: Extending the Language of New Media. London: Bloomsbury, 2013, 358 pp. ISBN 978-1-6235-6817-7. In Lev Manovich’s most recent book, this programmatic interrogation of our medial condition leads to the following question: do media still exist after software? This is the question that triggers Manovich’s dialogue both with computing history and with theories of digital media of recent decades, including the extension of his own previous formulations in The Language of New Media, published in 2001, and which became a major reference work in the field. The subtitle of the new book points precisely to this critical revisiting of his earlier work in the context of ubiquitous computing and accelerated transcoding of social, cultural and artistic practices by software.

NASA's TReK Project: A Case Study in Using the Spiral Model of Software Development

Science.gov (United States)

Hendrix, T. Dean; Schneider, Michelle P.

1998-01-01

Software development projects face numerous challenges that threaten their successful completion. Whether it is not enough money, too little time, or a case of "requirements creep" that has turned into a full sprint, projects must meet these challenges or face possible disastrous consequences. A robust, yet flexible process model can provide a mechanism through which software development teams can meet these challenges head on and win. This article describes how the spiral model has been successfully tailored to a specific project and relates some notable results to date.

Automating the management of software projects in a developing IT ...

African Journals Online (AJOL)

The resultant network-based software tool was developed on object-oriented technology using Java. The study established that good management practices may still be applied by the Nigerian software industry that lacks expertise in software management. Multi-site development approach facilitates large projects by using ...

A Quantitative Inquiry into Software Developers' Intentions to Use Agile Scrum Method

Science.gov (United States)

Huq, M. Shamsul

2017-01-01

In recent years, organizations have shown increasing willingness to adopt agile scrum method (ASM) to meet the demand of modern-day software development; that is to deliver faster and better software, with a built-in flexibility to absorb last minute changes in requirements. This research study was undertaken to uncover the underlying factors that…

48 CFR 9903.302-4 - Illustrations of changes which do not meet the definition of “Change to a cost accounting practice.”

Science.gov (United States)

2010-10-01

... which do not meet the definition of âChange to a cost accounting practice.â 9903.302-4 Section 9903.302-4 Federal Acquisition Regulations System COST ACCOUNTING STANDARDS BOARD, OFFICE OF FEDERAL... definition of “Change to a cost accounting practice.” Description Accounting treatment (a) Changes in the...

Learning to Facilitate (Online) Meetings

DEFF Research Database (Denmark)

Reimann, Peter; Bull, Susan; Vatrapu, Ravi

2013-01-01

We describe an approach to teaching collaboration skills directly by building on competences for meeting facilitation. (Online) meetings provide a rich arena to practice collaboration since they can serve multiple purposes: learning, problem solving, decision making, idea generation and advancement...

Software Maintenance Management Evaluation and Continuous Improvement

CERN Document Server

April, Alain

2008-01-01

This book explores the domain of software maintenance management and provides road maps for improving software maintenance organizations. It describes full maintenance maturity models organized by levels 1, 2, and 3, which allow for benchmarking and continuous improvement paths. Goals for each key practice area are also provided, and the model presented is fully aligned with the architecture and framework of software development maturity models of CMMI and ISO 15504. It is complete with case studies, figures, tables, and graphs.

DAQ: Software Architecture for Data Acquisition in Sounding Rockets

Science.gov (United States)

Ahmad, Mohammad; Tran, Thanh; Nichols, Heidi; Bowles-Martinez, Jessica N.

2011-01-01

A multithreaded software application was developed by Jet Propulsion Lab (JPL) to collect a set of correlated imagery, Inertial Measurement Unit (IMU) and GPS data for a Wallops Flight Facility (WFF) sounding rocket flight. The data set will be used to advance Terrain Relative Navigation (TRN) technology algorithms being researched at JPL. This paper describes the software architecture and the tests used to meet the timing and data rate requirements for the software used to collect the dataset. Also discussed are the challenges of using commercial off the shelf (COTS) flight hardware and open source software. This includes multiple Camera Link (C-link) based cameras, a Pentium-M based computer, and Linux Fedora 11 operating system. Additionally, the paper talks about the history of the software architecture's usage in other JPL projects and its applicability for future missions, such as cubesats, UAVs, and research planes/balloons. Also talked about will be the human aspect of project especially JPL's Phaeton program and the results of the launch.

Insights into software development in Japan

Science.gov (United States)

Duvall, Lorraine M.

1992-01-01

The interdependence of the U.S.-Japanese economies makes it imperative that we in the United States understand how business and technology developments take place in Japan. We can gain insight into these developments in software engineering by studying the context in which Japanese software is developed, the practices that are used, the problems encountered, the setting surrounding these problems, and the resolution of these problems. Context includes the technological and sociological characteristics of the software development environment, the software processes applied, personnel involved in the development process, and the corporate and social culture surrounding the development. Presented in this paper is a summary of results of a study that addresses these issues. Data for this study was collected during a three month visit to Japan where the author interviewed 20 software managers representing nine companies involved in developing software in Japan. These data are compared to similar data from the United States in which 12 managers from five companies were interviewed.

arXiv HEP Software Foundation Community White Paper Working Group - Software Development, Deployment and Validation

CERN Document Server

Couturier, Benjamin; Grasland, Hadrien; Hegner, Benedikt; Jouvin, Michel; Kane, Meghan; Katz, Daniel S.; Kuhr, Thomas; Lange, David; Mendez Lorenzo, Patricia; Ritter, Martin; Stewart, Graeme Andrew; Valassi, Andrea

The High Energy Phyiscs community has developed and needs to maintain many tens of millions of lines of code and to integrate effectively the work of thousands of developers across large collaborations. Software needs to be built, validated, and deployed across hundreds of sites. Software also has a lifetime of many years, frequently beyond that of the original developer, it must be developed with sustainability in mind. Adequate recognition of software development as a critical task in the HEP community needs to be fostered and an appropriate publication and citation strategy needs to be developed. As part of the HEP Softare Foundation's Community White Paper process a working group on Software Development, Deployment and Validation was formed to examine all of these issues, identify best practice and to formulare recommendations for the next decade. Its report is presented here.

Ethical issues and best practice in clinically based genomic research: Exeter Stakeholders Meeting Report.

Science.gov (United States)

Carrieri, D; Bewshea, C; Walker, G; Ahmad, T; Bowen, W; Hall, A; Kelly, S

2016-09-27

Current guidelines on consenting individuals to participate in genomic research are diverse. This creates problems for participants and also for researchers, particularly for clinicians who provide both clinical care and research to their patients. A group of 14 stakeholders met on 7 October 2015 in Exeter to discuss the ethical issues and the best practice arising in clinically based genomic research, with particular emphasis on the issue of returning results to study participants/patients in light of research findings affecting research and clinical practices. The group was deliberately multidisciplinary to ensure that a diversity of views was represented. This report outlines the main ethical issues, areas of best practice and principles underlying ethical clinically based genomic research discussed during the meeting. The main point emerging from the discussion is that ethical principles, rather than being formulaic, should guide researchers/clinicians to identify who the main stakeholders are to consult with for a specific project and to incorporate their voices/views strategically throughout the lifecycle of each project. We believe that the mix of principles and practical guidelines outlined in this report can contribute to current debates on how to conduct ethical clinically based genomic research. Published by the BMJ Publishing Group Limited. For permission to use (where not already granted under a licence) please go to http://www.bmj.com/company/products-services/rights-and-licensing/

OntoSoft: A Software Registry for Geosciences

Science.gov (United States)

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.

Analyser Framework to Verify Software Components

Directory of Open Access Journals (Sweden)

Rolf Andreas Rasenack

2009-01-01

Full Text Available Today, it is important for software companies to build software systems in a short time-interval, to reduce costs and to have a good market position. Therefore well organized and systematic development approaches are required. Reusing software components, which are well tested, can be a good solution to develop software applications in effective manner. The reuse of software components is less expensive and less time consuming than a development from scratch. But it is dangerous to think that software components can be match together without any problems. Software components itself are well tested, of course, but even if they composed together problems occur. Most problems are based on interaction respectively communication. Avoiding such errors a framework has to be developed for analysing software components. That framework determines the compatibility of corresponding software components. The promising approach discussed here, presents a novel technique for analysing software components by applying an Abstract Syntax Language Tree (ASLT. A supportive environment will be designed that checks the compatibility of black-box software components. This article is concerned to the question how can be coupled software components verified by using an analyzer framework and determines the usage of the ASLT. Black-box Software Components and Abstract Syntax Language Tree are the basis for developing the proposed framework and are discussed here to provide the background knowledge. The practical implementation of this framework is discussed and shows the result by using a test environment.

A Study on the Quantitative Assessment Method of Software Requirement Documents Using Software Engineering Measures and Bayesian Belief Networks

International Nuclear Information System (INIS)

Eom, Heung Seop; Kang, Hyun Gook; Park, Ki Hong; Kwon, Kee Choon; Chang, Seung Cheol

2005-01-01

One of the major challenges in using the digital systems in a NPP is the reliability estimation of safety critical software embedded in the digital safety systems. Precise quantitative assessment of the reliability of safety critical software is nearly impossible, since many of the aspects to be considered are of qualitative nature and not directly measurable, but they have to be estimated for a practical use. Therefore an expert's judgment plays an important role in estimating the reliability of the software embedded in safety-critical systems in practice, because they can deal with all the diverse evidence relevant to the reliability and can perform an inference based on the evidence. But, in general, the experts' way of combining the diverse evidence and performing an inference is usually informal and qualitative, which is hard to discuss and will eventually lead to a debate about the conclusion. We have been carrying out research on a quantitative assessment of the reliability of safety critical software using Bayesian Belief Networks (BBN). BBN has been proven to be a useful modeling formalism because a user can represent a complex set of events and relationships in a fashion that can easily be interpreted by others. In the previous works we have assessed a software requirement specification of a reactor protection system by using our BBN-based assessment model. The BBN model mainly employed an expert's subjective probabilities as inputs. In the process of assessing the software requirement documents we found out that the BBN model was excessively dependent on experts' subjective judgments in a large part. Therefore, to overcome the weakness of our methodology we employed conventional software engineering measures into the BBN model as shown in this paper. The quantitative relationship between the conventional software measures and the reliability of software were not identified well in the past. Then recently there appeared a few researches on a ranking of

Software Development in the Water Sciences: a view from the divide (Invited)

Science.gov (United States)

Miles, B.; Band, L. E.

2013-12-01

While training in statistical methods is an important part of many earth scientists' training, these scientists often learn the bulk of their software development skills in an ad hoc, just-in-time manner. Yet to carry out contemporary research scientists are spending more and more time developing software. Here I present perspectives - as an earth sciences graduate student with professional software engineering experience - on the challenges scientists face adopting software engineering practices, with an emphasis on areas of the science software development lifecycle that could benefit most from improved engineering. This work builds on experience gained as part of the NSF-funded Water Science Software Institute (WSSI) conceptualization award (NSF Award # 1216817). Throughout 2013, the WSSI team held a series of software scoping and development sprints with the goals of: (1) adding features to better model green infrastructure within the Regional Hydro-Ecological Simulation System (RHESSys); and (2) infusing test-driven agile software development practices into the processes employed by the RHESSys team. The goal of efforts such as the WSSI is to ensure that investments by current and future scientists in software engineering training will enable transformative science by improving both scientific reproducibility and researcher productivity. Experience with the WSSI indicates: (1) the potential for achieving this goal; and (2) while scientists are willing to adopt some software engineering practices, transformative science will require continued collaboration between domain scientists and cyberinfrastructure experts for the foreseeable future.

Selecting information technology for physicians' practices: a cross-sectional study

Directory of Open Access Journals (Sweden)

Eden Karen

2002-04-01

Full Text Available Abstract Background Many physicians are transitioning from paper to electronic formats for billing, scheduling, medical charts, communications, etc. The primary objective of this research was to identify the relationship (if any between the software selection process and the office staff's perceptions of the software's impact on practice activities. Methods A telephone survey was conducted with office representatives of 407 physician practices in Oregon who had purchased information technology. The respondents, usually office managers, answered scripted questions about their selection process and their perceptions of the software after implementation. Results Multiple logistic regression revealed that software type, selection steps, and certain factors influencing the purchase were related to whether the respondents felt the software improved the scheduling and financial analysis practice activities. Specifically, practices that selected electronic medical record or practice management software, that made software comparisons, or that considered prior user testimony as important were more likely to have perceived improvements in the scheduling process than were other practices. Practices that considered value important, that did not consider compatibility important, that selected managed care software, that spent less than $10,000, or that provided learning time (most dramatic increase in odds ratio, 8.2 during implementation were more likely to perceive that the software had improved the financial analysis process than were other practices. Conclusion Perhaps one of the most important predictors of improvement was providing learning time during implementation, particularly when the software involves several practice activities. Despite this importance, less than half of the practices reported performing this step.

Managing Risks in Distributed Software Projects: An Integrative Framework

DEFF Research Database (Denmark)

Persson, John Stouby; Mathiassen, Lars; Boeg, Jesper

2009-01-01

techniques into an integrative framework for managing risks in distributed contexts. Subsequent implementation of a Web-based tool helped us refine the framework based on empirical evaluation of its practical usefulness.We conclude by discussing implications for both research and practice.......Software projects are increasingly geographically distributed with limited face-to-face interaction between participants. These projects face particular challenges that need carefulmanagerial attention. While risk management has been adopted with success to address other challenges within software...... development, there are currently no frameworks available for managing risks related to geographical distribution. On this background, we systematically review the literature on geographically distributed software projects. Based on the review, we synthesize what we know about risks and risk resolution...

Geologic software for nuclear waste repository studies: A quality assurance program

International Nuclear Information System (INIS)

Figuli, S.; English, S.L.

1987-04-01

This paper discusses a Quality Assurance (QA) program that Kent State University (KSU) has implemented for the development of geologic software. The software being developed at KSU will be used in the site characterization of nuclear waste repositories and must meet the requirements of federal regulations. This QA program addresses the development of models that will be used in the evaluation of the long-term climatic stability of three sites in the western US

METHOD FOR SECURITY SPECIFICATION SOFTWARE REQUIREMENTS AS A MEANS FOR IMPLEMENTING A SOFTWARE DEVELOPMENT PROCESS SECURE - MERSEC

Directory of Open Access Journals (Sweden)

Castro Mecías, L.T.

2015-06-01

Full Text Available Often security incidents that have the object or use the software as a means of causing serious damage and legal, economic consequences, etc. Results of a survey by Kaspersky Lab reflectvulnerabilities in software are the main cause of security incidents in enterprises, the report shows that 85% of them have reported security incidents and vulnerabilities in software are the main reason is further estimated that incidents can cause significant losses estimated from 50,000 to $ 649.000. (1 In this regard academic and industry research focuses on proposals based on reducing vulnerabilities and failures of technology, with a positive influence on how the software is developed. A development process for improved safety practices and should include activities from the initial phases of the software; so that security needs are identified, manage risk and appropriate measures are implemented. This article discusses a method of analysis, acquisition and requirements specification of the software safety analysis on the basis of various proposals and deficiencies identified from participant observation in software development teams. Experiments performed using the proposed yields positive results regarding the reduction of security vulnerabilities and compliance with the safety objectives of the software.

Trust in agile teams in distributed software development

DEFF Research Database (Denmark)

Tjørnehøj, Gitte; Fransgård, Mette; Skalkam, Signe

2012-01-01

Distributed software development (DSD) is becoming everyday practice in the software market. Difficult challenges and difficulty reaching the expected benefits are well documented. Recently agile software development has become common in DSD, even though important incompatibilities between...... that leads to team success. This article reports from a study of two agile DSD teams with very different organization and collaboration patterns. It addresses the role of trust and distrust in DSD by analyzing how the team members’ trust developed and erode through the lifetime of the two collaborations...... and how management actions influenced this. We find that some agile practice can empower teams to take over responsibility for managing their own trust building and sustaining and that management neglect of trust-building in other situations can hinder the development of beneficial balanced agile DSD...

A Preliminary Study of Staff Meetings as Viewed by Dental Hygienists

Directory of Open Access Journals (Sweden)

Patrick Anderson

2011-12-01

Full Text Available Staff meetings in general dental practices represent what is be-lieved to be a key management strategy to build teams and to enhance efficiency and effec-tiveness. However, very little research has been done regarding staff meetings in dental offices. This study examined staff meetings from the viewpoint of dental hygienists who grow in unique careers in that they work largely independently of the dentist and yet typically within a dental practice while providing patient care and education. One-hundred-six dental hygienists completed a survey about staff meetings in dental offices. Key findings include: only approximately 43% of dental offices conduct morning huddles to get the day off to a smooth and organized start, 72% of dental practices conduct longer staff meetings with largely positive outcomes, including increasing practice efficiency and productivity, few practices (12% hold specific meetings only for the hygiene-department (and probably thereby miss some opportunities for practice im-provement, the most important variable by far to hygienists' job satisfaction is respect from the owner-dentist, and there exists an important and synergistic relationship among job sa-tisfaction, relationships with other staff and relationship with the owner-dentist.

Radiobiology software for educational purpose

International Nuclear Information System (INIS)

Pandey, A.K.; Sharma, S.K.; Kumar, R.; Bal, C.S.; Nair, O.; Haresh, K.P.; Julka, P.K.

2014-01-01

To understand radio-nuclide therapy and the basis of radiation protection, it is essential to understand radiobiology. With limited time for classroom teaching and limited time and resources for radiobiology experiments students do not acquire firm grasp of theoretical mathematical models and experimental knowledge of target theory and Linear quadratic models that explain nature of cell survival curves. We believe that this issue might be addressed with numerical simulation of cell survival curves using mathematical models. Existing classroom teaching can be reoriented to understand the subject using the concept of modeling, simulation and virtual experiments. After completion of the lecture, students can practice with simulation tool at their convenient time. In this study we have developed software that can help the students to acquire firm grasp of theoretical and experimental radiobiology. The software was developed using FreeMat ver 4.0, open source software. Target theory, linear quadratic model, cell killing based on Poisson model have been included. The implementation of the program structure was to display the menu for the user choice to be made and then program flows depending on the users choice. The program executes by typing 'Radiobiology' on the command line interface. Students can investigate the effect of radiation dose on cell, interactively. They can practice to draw the cell survival curve based on the input and output data and they can also compare their handmade graphs with automatically generated graphs by the program. This software is in the early stage of development and will evolve on user feedback. We feel this simulation software will be quite useful for students entering in the nuclear medicine, radiology and radiotherapy disciplines. (author)

Knowledge coordination in distributed software management

DEFF Research Database (Denmark)

Persson, John Stouby; Mathiassen, Lars

2012-01-01

Software organizations are increasingly relying on cross-organizational and cross-border collaboration, requiring effective coordination of distributed knowledge. However, such coordination is challenging due to spatial separation, diverging communities-of-practice, and unevenly distributed...... communication breakdowns on recordings of their combined teleconferencing and real-time collaborative modeling. As a result, we offer theoretical propositions that explain how distributed software managers can deal with communication breakdowns and effectively coordinate knowledge through multimodal virtual...

Software Development Methods and Tools: a New Zealand study

OpenAIRE

Chris Phillips; Elizabeth Kemp; Duncan Hedderley

2005-01-01

This study is a more detailed follow-up to a preliminary investigation of the practices of software engineers in New Zealand. The focus of this study is on the methods and tools used by software developers in their current organisation. The project involved detailed questionnaires being piloted and sent out to several hundred software developers. A central part of the research involved the identification of factors affecting the use and take-up of existing software development tools in the wo...

Learning Meetings and Conferences in Practice

DEFF Research Database (Denmark)

Elsborg, Steen; Ravn, Ib

, Speaker's Cornered, Presentations as Interviews, A Lunch that Fosters Contacts, and Two Free Consultants. The book is based on results from the research and development project "The Learning Meeting." It was conducted by Learning Lab Denmark in collaboration with Danske Bank, Rezidor SAS Hospitality (the...... Radisson SAS hotels), Hotel Legoland, Best Western Nyborg Strand, and Odense Congress Center. This book is a translation of the authors' "Lærende møder og konferencer i praksis", People's Press, 2006....

Status of REBUS fuel management software development for RERTR applications

International Nuclear Information System (INIS)

Olson, Arne P.

2000-01-01

The REBUS-5 burnup code has evolved substantially in order to meet the needs of the ANL RERTR Program. This paper presents a summary of the past changes and improvements in the capabilities of this software, and also identifies future plans. (author)

Software for Simulation of Hyperspectral Images

Science.gov (United States)

Richtsmeier, Steven C.; Singer-Berk, Alexander; Bernstein, Lawrence S.

2002-01-01

A package of software generates simulated hyperspectral images for use in validating algorithms that generate estimates of Earth-surface spectral reflectance from hyperspectral images acquired by airborne and spaceborne instruments. This software is based on a direct simulation Monte Carlo approach for modeling three-dimensional atmospheric radiative transport as well as surfaces characterized by spatially inhomogeneous bidirectional reflectance distribution functions. In this approach, 'ground truth' is accurately known through input specification of surface and atmospheric properties, and it is practical to consider wide variations of these properties. The software can treat both land and ocean surfaces and the effects of finite clouds with surface shadowing. The spectral/spatial data cubes computed by use of this software can serve both as a substitute for and a supplement to field validation data.

Proceedings of the 19th Annual Software Engineering Workshop

Science.gov (United States)

1994-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 applications software. The goals of the SEL are: (1) to understand the software development process in the GSFC environment; (2) to measure the effects of various methodologies, tools, and models on this process; and (3) to identify and then to apply successful development practices. The activities, findings, and recommendations of the SEL are recorded in the Software Engineering Laboratory Series, a continuing series of reports that include this document.

Inside a Secret Software Laboratory

CERN Document Server

Grimm, Christine

2012-01-01

How does one of the world's biggest Enterprise Resource Planning (ERP) suppliers develop software? How do Oracle, SAP, Microsoft and Co really work? Christine Grimm presents a first-hand account of a social researcher who entered the software laboratory of one of the biggest ERP providers. Presenting an in-depth ethnography on how people act within such labs, she reveals the highly unexpected social character of programming and shows how the vendor reorganizes himself to find new ways to respond to the expectations of the market. Furthermore, the author highlights the informal practices when a

Software Engineering Research/Developer Collaborations in 2005

Science.gov (United States)

Pressburger, Tom

2006-01-01

In CY 2005, three collaborations between software engineering technology providers and NASA software development personnel deployed three software engineering technologies on NASA development projects (a different technology on each project). The main purposes were to benefit the projects, infuse the technologies if beneficial into NASA, and give feedback to the technology providers to improve the technologies. Each collaboration project produced a final report. Section 2 of this report summarizes each project, drawing from the final reports and communications with the software developers and technology providers. Section 3 indicates paths to further infusion of the technologies into NASA practice. Section 4 summarizes some technology transfer lessons learned. Also included is an acronym list.

Creating the next generation control system software

International Nuclear Information System (INIS)

Schultz, D.E.

1989-01-01

A new 1980's style support package for future accelerator control systems is proposed. It provides a way to create accelerator applications software without traditional programming. Visual Interactive Applications (VIA) is designed to meet the needs of expanded accelerator complexes in a more cost effective way than past experience with procedural languages by using technology from the personal computer and artificial intelligence communities. 4 refs

Adoption of open source software in library management: an ...

African Journals Online (AJOL)

This literature and practical knowledge based opinion paper explored Koha software, bringing to limelight its applicability in the library. The various modules contained in the software (Circulation, Patrons, Advanced Search/OPAC, Cataloguing, Serials, Acquisition, Report and Tools) and the various specific services that ...

Appliance of software engineering in development of nuclear power plant

Energy Technology Data Exchange (ETDEWEB)

Baek, Y. W.; Kim, H. C.; Yun, C. [Chungnam National Univ., Taejon (Korea, Republic of); Kim, B. R. [KINS, Taejon (Korea, Republic of)

1999-10-01

Application of computer technology in nuclear power plant is also a necessary transformation as in other industry fields. But until now, application of software technology was not wide-spread because of its potential effect to safety in nuclear field. It is an urgent theme to develop evaluation guide and regulation techniques to guarantee safety, reliability and quality assurance. To meet these changes, techniques for development and operation should be enhanced to ensure the quality of software systems. In this study, we show the difference between waterfall model and software life-cycle needed in development of nuclear power plant and propose the consistent framework needed in development of instrumentation and control system of nuclear power plant.

Appliance of software engineering in development of nuclear power plant

International Nuclear Information System (INIS)

Baek, Y. W.; Kim, H. C.; Yun, C.; Kim, B. R.

1999-01-01

Application of computer technology in nuclear power plant is also a necessary transformation as in other industry fields. But until now, application of software technology was not wide-spread because of its potential effect to safety in nuclear field. It is an urgent theme to develop evaluation guide and regulation techniques to guarantee safety, reliability and quality assurance. To meet these changes, techniques for development and operation should be enhanced to ensure the quality of software systems. In this study, we show the difference between waterfall model and software life-cycle needed in development of nuclear power plant and propose the consistent framework needed in development of instrumentation and control system of nuclear power plant

Software package evaluation for the TJ-II Data Acquisition System

International Nuclear Information System (INIS)

Cremy, C.; Sanchez, E.; Portas, A.; Vega, J.

1996-01-01

The TJ-II Data Acquisition System (DAS) has to provide a user interface which will allow setup for sampling channels, discharge signal visualization and reduce data processing, all in run time. On the other hand, the DAS will provide a high level software capability for signal analysis, processing and data visualization either in run time or off line. A set of software packages including Builder Xcessory, X-designer, llog Builder, Toolmaster, AVS 5, AVS/Express, PV-WAVE and Iris Explorer, have been evaluated by the Data Acquisition Group of the Fusion Division. the software evaluation, resumed in this paper, has resulted in a global solution being found which meets all of the DAS requirements. (Author)

Role of courtyard counselling meeting in improving household food safety knowledge and practices in Munshiganj district of Bangladesh.

Science.gov (United States)

Riaz, Baizid Khoorshid; Alim, Md Abdul; Islam, Anm Shamsul; Amin, Km Bayzid; Sarker, Mohammad Abul Bashar; Hasan, Khaled; Ashad-Uz-Zaman, Md Noor; Selim, Shahjada; Quaiyum, Salman; Haque, Emdadul; Monir Hossain, Shah; Ryder, John; Khanam, Rokeya

2016-12-01

Unsafe food is linked to the deaths of an estimated two million people annually. Food containing harmful agents is responsible for more than 200 diseases ranging from diarrhoea to cancers. A one-sample pilot intervention study was conducted to evaluate the role of courtyard counselling meetings as the means of intervention for improving food safety knowledge and practices among household food handlers in a district of Bangladesh. The study was conducted in three phases: a baseline survey, the intervention and an end-line survey between April and November 2015 where 194 food handlers took part. Data were collected through observations and face-to-face interviews. The mean age of the respondents was 38.8 (±12.4) years, all of whom were females. Hand washing before eating, and washing utensils with soap were significantly improved at the end-line in comparison to the baseline (57% vs. 40% and 83% vs. 69%, respectively). Hand washing with soap was increased by 4%. The mean score of food handling practices was significantly increased after the intervention (20.5 vs. 22.1; Pfood and the necessity of thorough cooking were significantly increased after the intervention (88% from 64% and 34% from 21%, respectively). Mean scores of knowledge and practice on food safety were significantly increased by 1.9 and 1.6, respectively after the one month intervention. Thus this food safety education in rural communities should be scaled up and, indeed, strengthened using the courtyard counselling meetings in Bangladesh.

The need for scientific software engineering in the pharmaceutical industry.

Science.gov (United States)

Luty, Brock; Rose, Peter W

2017-03-01

Scientific software engineering is a distinct discipline from both computational chemistry project support and research informatics. A scientific software engineer not only has a deep understanding of the science of drug discovery but also the desire, skills and time to apply good software engineering practices. A good team of scientific software engineers can create a software foundation that is maintainable, validated and robust. If done correctly, this foundation enable the organization to investigate new and novel computational ideas with a very high level of efficiency.

The need for scientific software engineering in the pharmaceutical industry

Science.gov (United States)

Luty, Brock; Rose, Peter W.

2017-03-01

Scientific software engineering is a distinct discipline from both computational chemistry project support and research informatics. A scientific software engineer not only has a deep understanding of the science of drug discovery but also the desire, skills and time to apply good software engineering practices. A good team of scientific software engineers can create a software foundation that is maintainable, validated and robust. If done correctly, this foundation enable the organization to investigate new and novel computational ideas with a very high level of efficiency.

ACCU MEETING

CERN Multimedia

Chris Onions

2002-01-01

DRAFT Agenda for the meeting to be held on Wednesday 4 December 2002 At 9:15 a.m. in room 60-6-002 Chairman's remarks Adoption of the agenda Minutes of the previous meeting Matters arising News from the CERN Management Fellows, Associates and Summer Student Programmes Particle Data Book distribution Revoking Computer accounts Equipment insurance on site Reports from ACCU representatives on other committees Users' Office news Any Other Business Dates for meetings in 2003 Agenda for the next meeting Anyone wishing to raise any points under item 12 is invited to send them to the Chairman in writing or by e-mail to Christopher.Onions@cern.ch   ACCU is the forum for discussion between the CERN Management and the representatives of CERN Users to review the practical means taken by CERN for the work of Users of the Laboratory. The User Representatives to ACCU are (CERN internal telephone numbers in brackets): Austria W. Adam (71661) Belgium G. Wilquet (74664) Bulgaria R. Tzenov (74837...

ACCU Meeting

CERN Multimedia

PH Department

2011-01-01

DRAFT Agenda for the meeting to be held on Wednesday 15 June 2011 At 9:15 a.m. in room 60-6-002 Chairperson’s remarks Adoption of the agenda Minutes of the previous meeting Matters arising News from the CERN Management Report on services from GS department Update on Safety at CERN Reports from ACCU representatives on other Committees a. Scientific Information Policy Board (SIPB) b. IT Service Review Meeting (ITSRM) c. GS User Commission Users’ Office news Any Other Business Agenda for the next meeting Anyone wishing to raise any points under item 10 is invited to send them to the Chairperson in writing or by e-mail to Michael.Hauschild@cern.ch Michael Hauschild (Secretary) ACCU is the forum for discussion between the CERN Management and the representatives of CERN Users to review the practical means taken by CERN for the work of Users of the Laboratory. The User Representatives to ACCU are (CERN internal telephone numbers in bra...

Standard practice for classification of computed radiology systems

CERN Document Server

American Society for Testing and Materials. Philadelphia

2005-01-01

1.1 This practice describes the evaluation and classification of a computed radiography (CR) system, a particular phosphor imaging plate (IP), system scanner and software, in combination with specified metal screens for industrial radiography. It is intended to ensure that the evaluation of image quality, as far as this is influenced by the scanner/IP system, meets the needs of users. 1.2 The practice defines system tests to be used to classify the systems of different suppliers and make them comparable for users. 1.3 The CR system performance is described by signal and noise parameters. For film systems, the signal is represented by gradient and the noise by granularity. The signal-to-noise ratio is normalized by the basic spatial resolution of the system and is part of classification. The normalization is given by the scanning aperture of 100 µm diameter for the micro-photometer, which is defined in Test Method E1815 for film system classification. This practice describes how the parameters shall be meas...

Competency-structured case discussion in the morning meeting: enhancing CanMEDS integration in daily practice

Directory of Open Access Journals (Sweden)

Hassan IS

2015-05-01

Full Text Available Imad Salah Hassan, Hadi Kuriry, Lina Al Ansari, Ali Al-Khathami, Mohammed Al Qahtani, Thari Al Anazi, Mahfooz Farooqui, Hamdan Al Jahdali Department of Medicine 1443, King Saud bin Abdulaziz University for Health Sciences, King Abdulaziz Medical City, Riyadh, Kingdom of Saudi Arabia Abstract: Outcome-focused, competency-based educational curricula have become the norm in residency training programs. The Canadian Medical Education Directives for Specialists (CanMEDS framework is one example of such a curriculum. However, models for incorporating all the competencies in everyday clinical practice have been difficult to accomplish. In this manuscript, a CanMEDS, competency-structured, acute case discussion in a regular morning meeting was undertaken. All the diagnostic and therapeutic interventions were explicitly organized and discussed under their respective CanMEDS competency headings. Post exercise, the majority of residents felt that they were more competent in all the competencies and indicated their willingness to continue having similarly structured acute case discussions in the future. Keywords: CanMEDS roles, residents, morning meeting

75 FR 16817 - Meeting for Software Developers on the Technical Specifications for Common Formats for Patient...

Science.gov (United States)

2010-04-02

... and electronically comparable. This meeting is designed as an interactive forum where PSOs and... contact the Food and Drug Administration (FDA) Office of Equal Employment Opportunity and Disability... specifications. Throughout the meeting there will be interactive discussion to allow meeting participants not...

Instructional Uses of Web-Based Survey Software

Directory of Open Access Journals (Sweden)

Concetta A. DePaolo, Ph.D.

2006-07-01

Full Text Available Recent technological advances have led to changes in how instruction is delivered. Such technology can create opportunities to enhance instruction and make instructors more efficient in performing instructional tasks, especially if the technology is easy to use and requires no training. One such technology, web-based survey software, is extremely accessible for anyone with basic computer skills. Web-based survey software can be used for a variety of instructional purposes to streamline instructor tasks, as well as enhance instruction and communication with students. Following a brief overview of the technology, we discuss how Web Forms from nTreePoint can be used to conduct instructional surveys, collect course feedback, conduct peer evaluations of group work, collect completed assignments, schedule meeting times among multiple people, and aid in pedagogical research. We also discuss our experiences with these tasks within traditional on-campus courses and how they were enhanced or expedited by the use of web-based survey software.

SOFTWARE OPEN SOURCE, SOFTWARE GRATIS?

Directory of Open Access Journals (Sweden)

Nur Aini Rakhmawati

2006-01-01

Full Text Available Normal 0 false false false IN X-NONE X-NONE MicrosoftInternetExplorer4 Berlakunya Undang – undang Hak Atas Kekayaan Intelektual (HAKI, memunculkan suatu alternatif baru untuk menggunakan software open source. Penggunaan software open source menyebar seiring dengan isu global pada Information Communication Technology (ICT saat ini. Beberapa organisasi dan perusahaan mulai menjadikan software open source sebagai pertimbangan. Banyak konsep mengenai software open source ini. Mulai dari software yang gratis sampai software tidak berlisensi. Tidak sepenuhnya isu software open source benar, untuk itu perlu dikenalkan konsep software open source mulai dari sejarah, lisensi dan bagaimana cara memilih lisensi, serta pertimbangan dalam memilih software open source yang ada. Kata kunci :Lisensi, Open Source, HAKI

Method and practice on safety software verification and validation for digital reactor protection system

International Nuclear Information System (INIS)

Li Duo; Zhang Liangju; Feng Junting

2010-01-01

The key issue arising from digitalization of reactor protection system for Nuclear Power Plant (NPP) is in essence, how to carry out Verification and Validation (V and V), to demonstrate and confirm the software is reliable enough to perform reactor safety functions. Among others the most important activity of software V and V process is unit testing. This paper discusses the basic concepts on safety software V and V and the appropriate technique for software unit testing, focusing on such aspects as how to ensure test completeness, how to establish test platform, how to develop test cases and how to carry out unit testing. The technique discussed herein was successfully used in the work of unit testing on safety software of a digital reactor protection system. (author)

Command and Data Handling Flight Software test framework: A Radiation Belt Storm Probes practice

Science.gov (United States)

Hill, T. A.; Reid, W. M.; Wortman, K. A.

During the Radiation Belt Storm Probes (RBSP) mission, a test framework was developed by the Embedded Applications Group in the Space Department at the Johns Hopkins Applied Physics Laboratory (APL). The test framework is implemented for verification of the Command and Data Handling (C& DH) Flight Software. The RBSP C& DH Flight Software consists of applications developed for use with Goddard Space Flight Center's core Flight Executive (cFE) architecture. The test framework's initial concept originated with tests developed for verification of the Autonomy rules that execute with the Autonomy Engine application of the RBSP C& DH Flight Software. The test framework was adopted and expanded for system and requirements verification of the RBSP C& DH Flight Software. During the evolution of the RBSP C& DH Flight Software test framework design, a set of script conventions and a script library were developed. The script conventions and library eased integration of system and requirements verification tests into a comprehensive automated test suite. The comprehensive test suite is currently being used to verify releases of the RBSP C& DH Flight Software. In addition to providing the details and benefits of the test framework, the discussion will include several lessons learned throughout the verification process of RBSP C& DH Flight Software. Our next mission, Solar Probe Plus (SPP), will use the cFE architecture for the C& DH Flight Software. SPP also plans to use the same ground system as RBSP. Many of the RBSP C& DH Flight Software applications are reusable on the SPP mission, therefore there is potential for test design and test framework reuse for system and requirements verification.

Developing safety-critical software: a practical guide for aviation software and DO-178c compliance

National Research Council Canada - National Science Library

Rierson, Leanna

2013-01-01

... of a particular pedagogical approach or particular use of the MATLAB® and Simulink® software. CRC Press Taylor & Francis Group 6000 Broken Sound Parkway NW, Suite 300 Boca Raton, FL 33487-2742 © 2013 by Taylor & Francis Group, LLC CRC Press is an imprint of Taylor & Francis Group, an Informa business No claim to original U.S. Government works Versi...

Surveillance Analysis Computer System (SACS): Software requirements specification (SRS). Revision 2

International Nuclear Information System (INIS)

Glasscock, J.A.

1995-01-01

This document is the primary document establishing requirements for the Surveillance Analysis Computer System (SACS) database, an Impact Level 3Q system. SACS stores information on tank temperatures, surface levels, and interstitial liquid levels. This information is retrieved by the customer through a PC-based interface and is then available to a number of other software tools. The software requirements specification (SRS) describes the system requirements for the SACS Project, and follows the Standard Engineering Practices (WHC-CM-6-1), Software Practices (WHC-CM-3-10) and Quality Assurance (WHC-CM-4-2, QR 19.0) policies

Practical guide to machine vision software an introduction with LabVIEW

CERN Document Server

Kwon, Kye-Si

2014-01-01

For both students and engineers in R&D, this book explains machine vision in a concise, hands-on way, using the Vision Development Module of the LabView software by National Instruments. Following a short introduction to the basics of machine vision and the technical procedures of image acquisition, the book goes on to guide readers in the use of the various software functions of LabView's machine vision module. It covers typical machine vision tasks, including particle analysis, edge detection, pattern and shape matching, dimension measurements as well as optical character recognition, enabli

Software engineering and automatic continuous verification of scientific software

Science.gov (United States)

Piggott, M. D.; Hill, J.; Farrell, P. E.; Kramer, S. C.; Wilson, C. R.; Ham, D.; Gorman, G. J.; Bond, T.

2011-12-01

Software engineering of scientific code is challenging for a number of reasons including pressure to publish and a lack of awareness of the pitfalls of software engineering by scientists. The Applied Modelling and Computation Group at Imperial College is a diverse group of researchers that employ best practice software engineering methods whilst developing open source scientific software. Our main code is Fluidity - a multi-purpose computational fluid dynamics (CFD) code that can be used for a wide range of scientific applications from earth-scale mantle convection, through basin-scale ocean dynamics, to laboratory-scale classic CFD problems, and is coupled to a number of other codes including nuclear radiation and solid modelling. Our software development infrastructure consists of a number of free tools that could be employed by any group that develops scientific code and has been developed over a number of years with many lessons learnt. A single code base is developed by over 30 people for which we use bazaar for revision control, making good use of the strong branching and merging capabilities. Using features of Canonical's Launchpad platform, such as code review, blueprints for designing features and bug reporting gives the group, partners and other Fluidity uers an easy-to-use platform to collaborate and allows the induction of new members of the group into an environment where software development forms a central part of their work. The code repositoriy are coupled to an automated test and verification system which performs over 20,000 tests, including unit tests, short regression tests, code verification and large parallel tests. Included in these tests are build tests on HPC systems, including local and UK National HPC services. The testing of code in this manner leads to a continuous verification process; not a discrete event performed once development has ceased. Much of the code verification is done via the "gold standard" of comparisons to analytical

A Roadmap to Continuous Integration for ATLAS Software Development

Science.gov (United States)

Elmsheuser, J.; Krasznahorkay, A.; Obreshkov, E.; Undrus, A.; ATLAS Collaboration

2017-10-01

The ATLAS software infrastructure facilitates efforts of more than 1000 developers working on the code base of 2200 packages with 4 million lines of C++ and 1.4 million lines of python code. The ATLAS offline code management system is the powerful, flexible framework for processing new package versions requests, probing code changes in the Nightly Build System, migration to new platforms and compilers, deployment of production releases for worldwide access and supporting physicists with tools and interfaces for efficient software use. It maintains multi-stream, parallel development environment with about 70 multi-platform branches of nightly releases and provides vast opportunities for testing new packages, for verifying patches to existing software and for migrating to new platforms and compilers. The system evolution is currently aimed on the adoption of modern continuous integration (CI) practices focused on building nightly releases early and often, with rigorous unit and integration testing. This paper describes the CI incorporation program for the ATLAS software infrastructure. It brings modern open source tools such as Jenkins and GitLab into the ATLAS Nightly System, rationalizes hardware resource allocation and administrative operations, provides improved feedback and means to fix broken builds promptly for developers. Once adopted, ATLAS CI practices will improve and accelerate innovation cycles and result in increased confidence in new software deployments. The paper reports the status of Jenkins integration with the ATLAS Nightly System as well as short and long term plans for the incorporation of CI practices.

Improving Software Systems By Flow Control Analysis

Directory of Open Access Journals (Sweden)

Piotr Poznanski

2012-01-01

Full Text Available Using agile methods during the implementation of the system that meets mission critical requirements can be a real challenge. The change in the system built of dozens or even hundreds of specialized devices with embedded software requires the cooperation of a large group of engineers. This article presents a solution that supports parallel work of groups of system analysts and software developers. Deployment of formal rules to the requirements written in natural language enables using formal analysis of artifacts being a bridge between software and system requirements. Formalism and textual form of requirements allowed the automatic generation of message flow graph for the (sub system, called the “big-picture-model”. Flow diagram analysis helped to avoid a large number of defects whose repair cost in extreme cases could undermine the legitimacy of agile methods in projects of this scale. Retrospectively, a reduction of technical debt was observed. Continuous analysis of the “big picture model” improves the control of the quality parameters of the software architecture. The article also tries to explain why the commercial platform based on UML modeling language may not be sufficient in projects of this complexity.

Clinical software for MR imaging system, 4

International Nuclear Information System (INIS)

Shimizu, Koji; Kasai, Akira; Okamura, Shoichi

1992-01-01

Magnetic resonance imaging continues to elicit new application software through the recent technological advances of MR equipment. This paper describes several applications of our newly developed clinical software. The fast SE sequence (RISE) has proved to reduce routine examination time and to improve image quality, and ultra-fast FE sequence (SMASH) was found to extend the diagnostic capabilities in the field of cardiac study. Diffusion/perfusion imaging achieved in our MR system showed significant promise for providing novel information regarding tissue characterization. Furthermore, Image quality and practicalities of MR angiography have been improved by advanced imaging sequences and sophisticated post-processing software. (author)

Software Safety Risk in Legacy Safety-Critical Computer Systems

Science.gov (United States)

Hill, Janice L.; Baggs, Rhoda

2007-01-01

Safety Standards contain technical and process-oriented safety requirements. Technical requirements are those such as "must work" and "must not work" functions in the system. Process-Oriented requirements are software engineering and safety management process requirements. Address the system perspective and some cover just software in the system > NASA-STD-8719.13B Software Safety Standard is the current standard of interest. NASA programs/projects will have their own set of safety requirements derived from the standard. Safety Cases: a) Documented demonstration that a system complies with the specified safety requirements. b) Evidence is gathered on the integrity of the system and put forward as an argued case. [Gardener (ed.)] c) Problems occur when trying to meet safety standards, and thus make retrospective safety cases, in legacy safety-critical computer systems.

A Web-Based Learning System for Software Test Professionals

Science.gov (United States)

Wang, Minhong; Jia, Haiyang; Sugumaran, V.; Ran, Weijia; Liao, Jian

2011-01-01

Fierce competition, globalization, and technology innovation have forced software companies to search for new ways to improve competitive advantage. Web-based learning is increasingly being used by software companies as an emergent approach for enhancing the skills of knowledge workers. However, the current practice of Web-based learning is…

Do intervention plans meet criteria for effective practice to reduce recidivism? How probation officers forget about social capital and basic needs

NARCIS (Netherlands)

Bosker, J.; Witteman, C.; Hermanns, J.

2013-01-01

The increased use of instruments for assessing risks and needs in probation should lead to intervention plans that meet the criteria for effective practice. An analysis of 300 intervention plans from the Dutch probation service showed that the match between the assessed criminogenic needs and the

Developing software is not an easy matter

Directory of Open Access Journals (Sweden)

Tina Cardrige

2014-12-01

Full Text Available Why is it so difficult to learn to develop software? This question has been trying to answer for a long time, but has not yet found a solution to this issue. Moreover, it tends to confuse development with programming, and this also creates problems to elucidate the question. In an era in which urgently required improve the quality, and reliability, and safety of software it becomes urgent to potentiate or develop skills and abilities in professionals to meet these needs. But students are not interested in making careers involving these concepts, they prefer other less demanding and easier to achieve a certification. This article attempts to answer the question and present some suggestions for overcoming this difficulty.

Proceedings of the Fifteenth Annual Software Engineering Workshop