WorldWideScience

Sample records for software guidelines volume

  1. Sandia software guidelines, Volume 4: Configuration management

    Energy Technology Data Exchange (ETDEWEB)

    1992-06-01

    This volume is one in a series of Sandia Software Guidelines for use in producing quality software within Sandia National Laboratories. This volume is based on the IEEE standard and guide for software configuration management. The basic concepts and detailed guidance on implementation of these concepts are discussed for several software project types. Example planning documents for both projects and organizations are included.

  2. Sandia Software Guidelines, Volume 2. Documentation

    Energy Technology Data Exchange (ETDEWEB)

    NONE

    1995-09-01

    This volume is one in a series of Sandia Software Guidelines intended for use in producing quality software within Sandia National Laboratories. In consonance with the IEEE Standards for software documentation, this volume provides guidance in the selection of an adequate document set for a software project and example formats for many types of software documentation. A tutorial on life cycle documentation is also provided. Extended document thematic outlines and working examples of software documents are available on electronic media as an extension of this volume.

  3. Sandia software guidelines. Volume 3. Standards, practices, and conventions

    Energy Technology Data Exchange (ETDEWEB)

    1986-07-01

    This volume is one in a series of Sandia Software Guidelines intended for use in producing quality software within Sandia National Laboratories. In consonance with the IEEE Standard for Software Quality Assurance Plans, this volume identifies software standards, conventions, and practices. These guidelines are the result of a collective effort within Sandia National Laboratories to define recommended deliverables and to document standards, practices, and conventions which will help ensure quality software. 66 refs., 5 figs., 6 tabs.

  4. Sandia software guidelines: Volume 5, Tools, techniques, and methodologies

    Energy Technology Data Exchange (ETDEWEB)

    1989-07-01

    This volume is one in a series of Sandia Software Guidelines intended for use in producing quality software within Sandia National Laboratories. This volume describes software tools and methodologies available to Sandia personnel for the development of software, and outlines techniques that have proven useful within the Laboratories and elsewhere. References and evaluations by Sandia personnel are included. 6 figs.

  5. Guidelines for the verification and validation of expert system software and conventional software: Bibliography. Volume 8

    International Nuclear Information System (INIS)

    Miller, L.A.; Hayes, J.E.; Mirsky, S.M.

    1995-03-01

    This volume contains all of the technical references found in Volumes 1-7 concerning the development of guidelines for the verification and validation of expert systems, knowledge-based systems, other AI systems, object-oriented systems, and conventional systems

  6. Guidelines for the verification and validation of expert system software and conventional software: Bibliography. Volume 8

    Energy Technology Data Exchange (ETDEWEB)

    Miller, L.A.; Hayes, J.E.; Mirsky, S.M. [Science Applications International Corp., McLean, VA (United States)

    1995-03-01

    This volume contains all of the technical references found in Volumes 1-7 concerning the development of guidelines for the verification and validation of expert systems, knowledge-based systems, other AI systems, object-oriented systems, and conventional systems.

  7. Guidelines for the verification and validation of expert system software and conventional software: Rationale and description of V ampersand V guideline packages and procedures. Volume 5

    International Nuclear Information System (INIS)

    Mirsky, S.M.; Hayes, J.E.; Miller, L.A.

    1995-03-01

    This report is the fifth volume in a series of reports describing the results of the Expert System Verification C, and Validation (V ampersand V) project which is jointly funded by the U.S. Nuclear Regulatory Commission and the Electric Power Research Institute toward the objective of formulating Guidelines for the V ampersand V of expert systems for use in nuclear power applications. This report provides the rationale for and description of those guidelines. The actual guidelines themselves are presented in Volume 7, open-quotes User's Manual.close quotes Three factors determine what V ampersand V is needed: (1) the stage of the development life cycle (requirements, design, or implementation); (2) whether the overall system or a specialized component needs to be tested (knowledge base component, inference engine or other highly reusable element, or a component involving conventional software); and (3) the stringency of V ampersand V that is needed (as judged from an assessment of the system's complexity and the requirement for its integrity to form three Classes). A V ampersand V Guideline package is provided for each of the combinations of these three variables. The package specifies the V ampersand V methods recommended and the order in which they should be administered, the assurances each method provides, the qualifications needed by the V ampersand V team to employ each particular method, the degree to which the methods should be applied, the performance measures that should be taken, and the decision criteria for accepting, conditionally accepting, or rejecting an evaluated system. In addition to the Guideline packages, highly detailed step-by-step procedures are provided for 11 of the more important methods, to ensure that they can be implemented correctly. The Guidelines can apply to conventional procedural software systems as well as all kinds of Al systems

  8. Software OT&E Guidelines. Volume 1. Software Test Manager’s Handbook

    Science.gov (United States)

    1981-02-01

    establishing good working relationship is critical). e) Work with the TEBC advanced planner to ensure early involvement of software data " thinking " (in the OT...Threat Enviromental Description (TED). (The implementing command or AFSC) will update or develop the TED and obtain AF/IN approval by (one year from

  9. Guidelines for the verification and validation of expert system software and conventional software. Volume 1: Project summary. Final report

    International Nuclear Information System (INIS)

    Miller, L.A.; Hayes, J.E.; Mirsky, S.M.

    1995-05-01

    This eight-volume report presents guidelines for performing verification and validation (V ampersand V) on Artificial Intelligence (AI) systems with nuclear applications. The guidelines have much broader application than just expert systems; they are also applicable to object-oriented programming systems, rule-based systems, frame-based systems, model-based systems, neural nets, genetic algorithms, and conventional software systems. This is because many of the components of AI systems are implemented in conventional procedural programming languages, so there is no real distinction. The report examines the state of the art in verifying and validating expert systems. V ampersand V methods traditionally applied to conventional software systems are evaluated for their applicability to expert systems. One hundred fifty-three conventional techniques are identified and evaluated. These methods are found to be useful for at least some of the components of expert systems, frame-based systems, and object-oriented systems. A taxonomy of 52 defect types and their delectability by the 153 methods is presented. With specific regard to expert systems, conventional V ampersand V methods were found to apply well to all the components of the expert system with the exception of the knowledge base. The knowledge base requires extension of the existing methods. Several innovative static verification and validation methods for expert systems have been identified and are described here, including a method for checking the knowledge base open-quotes semanticsclose quotes and a method for generating validation scenarios. Evaluation of some of these methods was performed both analytically and experimentally

  10. Guidelines for the verification and validation of expert system software and conventional software: Project summary. Volume 1

    International Nuclear Information System (INIS)

    Mirsky, S.M.; Hayes, J.E.; Miller, L.A.

    1995-03-01

    This eight-volume report presents guidelines for performing verification and validation (V ampersand V) on Artificial Intelligence (Al) systems with nuclear applications. The guidelines have much broader application than just expert systems; they are also applicable to object-oriented programming systems, rule-based systems, frame-based systems, model-based systems, neural nets, genetic algorithms, and conventional software systems. This is because many of the components of AI systems are implemented in conventional procedural programming languages, so there is no real distinction. The report examines the state of the art in verifying and validating expert systems. V ampersand V methods traditionally applied to conventional software systems are evaluated for their applicability to expert systems. One hundred fifty-three conventional techniques are identified and evaluated. These methods are found to be useful for at least some of the components of expert systems, frame-based systems, and object-oriented systems. A taxonomy of 52 defect types and their delectability by the 153 methods is presented. With specific regard to expert systems, conventional V ampersand V methods were found to apply well to all the components of the expert system with the exception of the knowledge base. The knowledge base requires extension of the existing methods. Several innovative static verification and validation methods for expert systems have been identified and are described here, including a method for checking the knowledge base open-quotes semanticsclose quotes and a method for generating validation scenarios. Evaluation of some of these methods was performed both analytically and experimentally. A V ampersand V methodology for expert systems is presented based on three factors: (1) a system's judged need for V ampersand V (based in turn on its complexity and degree of required integrity); (2) the life-cycle phase; and (3) the system component being tested

  11. Guidelines for the verification and validation of expert system software and conventional software: Project summary. Volume 1

    Energy Technology Data Exchange (ETDEWEB)

    Mirsky, S.M.; Hayes, J.E.; Miller, L.A. [Science Applications International Corp., McLean, VA (United States)

    1995-03-01

    This eight-volume report presents guidelines for performing verification and validation (V&V) on Artificial Intelligence (Al) systems with nuclear applications. The guidelines have much broader application than just expert systems; they are also applicable to object-oriented programming systems, rule-based systems, frame-based systems, model-based systems, neural nets, genetic algorithms, and conventional software systems. This is because many of the components of AI systems are implemented in conventional procedural programming languages, so there is no real distinction. The report examines the state of the art in verifying and validating expert systems. V&V methods traditionally applied to conventional software systems are evaluated for their applicability to expert systems. One hundred fifty-three conventional techniques are identified and evaluated. These methods are found to be useful for at least some of the components of expert systems, frame-based systems, and object-oriented systems. A taxonomy of 52 defect types and their delectability by the 153 methods is presented. With specific regard to expert systems, conventional V&V methods were found to apply well to all the components of the expert system with the exception of the knowledge base. The knowledge base requires extension of the existing methods. Several innovative static verification and validation methods for expert systems have been identified and are described here, including a method for checking the knowledge base {open_quotes}semantics{close_quotes} and a method for generating validation scenarios. Evaluation of some of these methods was performed both analytically and experimentally. A V&V methodology for expert systems is presented based on three factors: (1) a system`s judged need for V&V (based in turn on its complexity and degree of required integrity); (2) the life-cycle phase; and (3) the system component being tested.

  12. Guidelines for the verification and validation of expert system software and conventional software: Validation scenarios. Volume 6

    Energy Technology Data Exchange (ETDEWEB)

    Mirsky, S.M.; Hayes, J.E.; Miller, L.A. [Science Applications International Corp., McLean, VA (United States)

    1995-03-01

    This report is the sixth volume in a series of reports describing the results of the Expert System Verification and Validation (V&V) project which is jointly funded by the US Nuclear Regulatory Commission and the Electric Power Research Institute. The ultimate objective is the formulation of guidelines for the V&V of expert systems for use in nuclear power applications. This activity was concerned with the development of a methodology for selecting validation scenarios and subsequently applying it to two expert systems used for nuclear utility applications. Validation scenarios were defined and classified into five categories: PLANT, TEST, BASICS, CODE, and LICENSING. A sixth type, REGRESSION, is a composite of the others and refers to the practice of using trusted scenarios to ensure that modifications to software did not change unmodified functions. Rationale was developed for preferring scenarios selected from the categories in the order listed and for determining under what conditions to select scenarios from other types. A procedure incorporating all of the recommendations was developed as a generalized method for generating validation scenarios. The procedure was subsequently applied to two expert systems used in the nuclear industry and was found to be effective, given that an experienced nuclear engineer made the final scenario selections. A method for generating scenarios directly from the knowledge base component was suggested.

  13. High integrity software for nuclear power plants: Candidate guidelines, technical basis and research needs. Executive summary: Volume 1

    International Nuclear Information System (INIS)

    Seth, S.; Bail, W.; Cleaves, D.; Cohen, H.; Hybertson, D.; Schaefer, C.; Stark, G.; Ta, A.; Ulery, B.

    1995-06-01

    The work documented in this report was performed in support of the US Nuclear Regulatory Commission to examine the technical basis for candidate guidelines that could be considered in reviewing and evaluating high integrity computer software used in the safety systems of nuclear power plants. The framework for the work consisted of the following software development and assurance activities: requirements specification; design; coding; verification and validation, including static analysis and dynamic testing; safety analysis; operation and maintenance; configuration management; quality assurance; and planning and management. Each activity (framework element) was subdivided into technical areas (framework subelements). The report describes the development of approximately 200 candidate guidelines that span the entire range of software life-cycle activities; the assessment of the technical basis for those candidate guidelines; and the identification, categorization and prioritization of research needs for improving the technical basis. The report has two volumes: Volume 1, Executive Summary, includes an overview of the framework and of each framework element, the complete set of candidate guidelines, the results of the assessment of the technical basis for each candidate guideline, and a discussion of research needs that support the regulatory function; Volume 2 is the main report

  14. Guidelines for the verification and validation of expert system software and conventional software. Volume 7, User's manual: Final report

    International Nuclear Information System (INIS)

    Miller, L.A.; Hayes, J.E.; Mirsky, S.M.

    1995-05-01

    Reliable software is required for nuclear power industry applications. Verification and validation techniques applied during the software development process can help eliminate errors that could inhibit the proper operation of digital systems and cause availability and safety problems. Most of the techniques described in this report are valid for conventional software systems as well as for expert systems. The project resulted in a set of 16 V ampersand V guideline packages and 11 sets of procedures based on the class, development phase, and system component being tested. These guideline packages and procedures help a utility define the level of V ampersand V, which involves evaluating the complexity and type of software component along with the consequences of failure. In all, the project identified 153 V ampersand V techniques for conventional software systems and demonstrated their application to all aspects of expert systems except for the knowledge base, which requires specially developed tools. Each of these conventional techniques covers anywhere from 2-52 total types of conventional software defects, and each defect is covered by 21-50 V ampersand V techniques. The project also identified automated tools to Support V ampersand V activities

  15. Human-system interface design review guideline -- Review software and user's guide: Final report. Revision 1, Volume 3

    International Nuclear Information System (INIS)

    1996-06-01

    NUREG-0700, Revision 1, provides human factors engineering (HFE) guidance to the US Nuclear Regulatory Commission staff for its: (1) review of the human system interface (HSI) design submittals prepared by licensees or applications for a license or design certification of commercial nuclear power plants, and (2) performance of HSI reviews that could be undertaken as part of an inspection or other type of regulatory review involving HSI design or incidents involving human performance. The guidance consists of a review process and HFE guidelines. The document describes those aspects of the HSI design review process that are important to the identification and resolution of human engineering discrepancies that could adversely affect plant safety. Guidance is provided that could be used by the staff to review an applicant's HSI design review process or to guide the development of an HSI design review plan, e.g., as part of an inspection activity. The document also provides detailed HFE guidelines for the assessment of HSI design implementations. NUREG-0700, Revision 1, consists of three stand-alone volumes. Volume 3 contains an interactive software application of the NUREG-0700, Revision 1 guidance and a user's guide for this software. The software supports reviewers during review preparation, evaluation design using the human factors engineering guidelines, and in report preparation. The user's guide provides system requirements and installation instructions, detailed explanations of the software's functions and features, and a tutorial on using the software

  16. High integrity software for nuclear power plants: Candidate guidelines, technical basis and research needs. Main report, Volume 2

    International Nuclear Information System (INIS)

    Seth, S.; Bail, W.; Cleaves, D.; Cohen, H.; Hybertson, D.; Schaefer, C.; Stark, G.; Ta, A.; Ulery, B.

    1995-06-01

    The work documented in this report was performed in support of the US Nuclear Regulatory Commission to examine the technical basis for candidate guidelines that could be considered in reviewing and evaluating high integrity computer e following software development and assurance activities: Requirements specification; design; coding; verification and validation, inclukding static analysis and dynamic testing; safety analysis; operation and maintenance; configuration management; quality assurance; and planning and management. Each activity (framework element) was subdivided into technical areas (framework subelements). The report describes the development of approximately 200 candidate guidelines that span the entire ran e identification, categorization and prioritization of technical basis for those candidate guidelines; and the identification, categorization and prioritization of research needs for improving the technical basis. The report has two volumes: Volume 1, Executive Summary includes an overview of the framwork and of each framework element, the complete set of candidate guidelines, the results of the assessment of the technical basis for each candidate guideline, and a discussion of research needs that support the regulatory function; this document, Volume 2, is the main report

  17. High integrity software for nuclear power plants: Candidate guidelines, technical basis and research needs. Main report, Volume 2

    Energy Technology Data Exchange (ETDEWEB)

    Seth, S.; Bail, W.; Cleaves, D.; Cohen, H.; Hybertson, D.; Schaefer, C.; Stark, G.; Ta, A.; Ulery, B. [Mitre Corp., McLean, VA (United States)

    1995-06-01

    The work documented in this report was performed in support of the US Nuclear Regulatory Commission to examine the technical basis for candidate guidelines that could be considered in reviewing and evaluating high integrity computer e following software development and assurance activities: Requirements specification; design; coding; verification and validation, inclukding static analysis and dynamic testing; safety analysis; operation and maintenance; configuration management; quality assurance; and planning and management. Each activity (framework element) was subdivided into technical areas (framework subelements). The report describes the development of approximately 200 candidate guidelines that span the entire ran e identification, categorization and prioritization of technical basis for those candidate guidelines; and the identification, categorization and prioritization of research needs for improving the technical basis. The report has two volumes: Volume 1, Executive Summary includes an overview of the framwork and of each framework element, the complete set of candidate guidelines, the results of the assessment of the technical basis for each candidate guideline, and a discussion of research needs that support the regulatory function; this document, Volume 2, is the main report.

  18. Guidelines for the verification and validation of expert system software and conventional software: User's manual. Volume 7

    International Nuclear Information System (INIS)

    Mirsky, S.M.; Hayes, J.E.; Miller, L.A.

    1995-03-01

    This report provides a step-by-step guide, or user manual, for personnel responsible for the planning and execution of the verification and validation (V ampersand V), and developmental testing, of expert systems, conventional software systems, and various other types of artificial intelligence systems. While the guide was developed primarily for applications in the utility industry, it applies well to all industries. The user manual has three sections. In Section 1 the user assesses the stringency of V ampersand V needed for the system under consideration, identifies the development stage the system is in, and identifies the component(s) of the system to be tested next. These three pieces of information determine which Guideline Package of V ampersand V methods is most appropriate for those conditions. The V ampersand V Guideline Packages are provided in Section 2. Each package consists of an ordered set of V ampersand V techniques to be applied to the system, guides on choosing the review/evaluation team, measurement criteria, and references to a book or report which describes the application of the method. Section 3 presents details of 11 of the most important (or least well-explained in the literature) methods to assist the user in applying these techniques accurately

  19. Guidelines for the verification and validation of expert system software and conventional software: Survey and documentation of expert system verification and validation methodologies. Volume 3

    International Nuclear Information System (INIS)

    Groundwater, E.H.; Miller, L.A.; Mirsky, S.M.

    1995-03-01

    This report is the third volume in the final report for the Expert System Verification and Validation (V ampersand V) project which was jointly sponsored by the Nuclear Regulatory Commission and the Electric Power Research Institute. The ultimate objective is the formulation of guidelines for the V ampersand V of expert systems for use in nuclear power applications. The purpose of this activity was to survey and document techniques presently in use for expert system V ampersand V. The survey effort included an extensive telephone interviewing program, site visits, and a thorough bibliographic search and compilation. The major finding was that V ampersand V of expert systems is not nearly as established or prevalent as V ampersand V of conventional software systems. When V ampersand V was used for expert systems, it was almost always at the system validation stage after full implementation and integration usually employing the non-systematic dynamic method of open-quotes ad hoc testing.close quotes There were few examples of employing V ampersand V in the early phases of development and only weak sporadic mention of the possibilities in the literature. There is, however, a very active research area concerning the development of methods and tools to detect problems with, particularly, rule-based expert systems. Four such static-testing methods were identified which were not discovered in a comprehensive review of conventional V ampersand V methods in an earlier task

  20. Guidelines for the verification and validation of expert system software and conventional software: Survey and documentation of expert system verification and validation methodologies. Volume 3

    Energy Technology Data Exchange (ETDEWEB)

    Groundwater, E.H.; Miller, L.A.; Mirsky, S.M. [Science Applications International Corp., McLean, VA (United States)

    1995-03-01

    This report is the third volume in the final report for the Expert System Verification and Validation (V&V) project which was jointly sponsored by the Nuclear Regulatory Commission and the Electric Power Research Institute. The ultimate objective is the formulation of guidelines for the V&V of expert systems for use in nuclear power applications. The purpose of this activity was to survey and document techniques presently in use for expert system V&V. The survey effort included an extensive telephone interviewing program, site visits, and a thorough bibliographic search and compilation. The major finding was that V&V of expert systems is not nearly as established or prevalent as V&V of conventional software systems. When V&V was used for expert systems, it was almost always at the system validation stage after full implementation and integration usually employing the non-systematic dynamic method of {open_quotes}ad hoc testing.{close_quotes} There were few examples of employing V&V in the early phases of development and only weak sporadic mention of the possibilities in the literature. There is, however, a very active research area concerning the development of methods and tools to detect problems with, particularly, rule-based expert systems. Four such static-testing methods were identified which were not discovered in a comprehensive review of conventional V&V methods in an earlier task.

  1. Guidelines for the verification and validation of expert system software and conventional software: Survey and assessment of conventional software verification and validation methods. Volume 2

    Energy Technology Data Exchange (ETDEWEB)

    Mirsky, S.M.; Groundwater, E.H.; Hayes, J.E.; Miller, L.A. [Science Applications International Corp., McLean, VA (United States)

    1995-03-01

    By means of a literature survey, a comprehensive set of methods was identified for the verification and validation of conventional software. The 153 methods so identified were classified according to their appropriateness for various phases of a developmental life-cycle -- requirements, design, and implementation; the last category was subdivided into two, static testing and dynamic testing methods. The methods were then characterized in terms of eight rating factors, four concerning ease-of-use of the methods and four concerning the methods` power to detect defects. Based on these factors, two measurements were developed to permit quantitative comparisons among methods, a Cost-Benefit metric and an Effectiveness Metric. The Effectiveness Metric was further refined to provide three different estimates for each method, depending on three classes of needed stringency of V&V (determined by ratings of a system`s complexity and required-integrity). Methods were then rank-ordered for each of the three classes by terms of their overall cost-benefits and effectiveness. The applicability was then assessed of each for the identified components of knowledge-based and expert systems, as well as the system as a whole.

  2. Guidelines for the verification and validation of expert system software and conventional software: Survey and assessment of conventional software verification and validation methods. Volume 2

    International Nuclear Information System (INIS)

    Mirsky, S.M.; Groundwater, E.H.; Hayes, J.E.; Miller, L.A.

    1995-03-01

    By means of a literature survey, a comprehensive set of methods was identified for the verification and validation of conventional software. The 153 methods so identified were classified according to their appropriateness for various phases of a developmental life-cycle -- requirements, design, and implementation; the last category was subdivided into two, static testing and dynamic testing methods. The methods were then characterized in terms of eight rating factors, four concerning ease-of-use of the methods and four concerning the methods' power to detect defects. Based on these factors, two measurements were developed to permit quantitative comparisons among methods, a Cost-Benefit metric and an Effectiveness Metric. The Effectiveness Metric was further refined to provide three different estimates for each method, depending on three classes of needed stringency of V ampersand V (determined by ratings of a system's complexity and required-integrity). Methods were then rank-ordered for each of the three classes by terms of their overall cost-benefits and effectiveness. The applicability was then assessed of each for the identified components of knowledge-based and expert systems, as well as the system as a whole

  3. User systems guidelines for software projects

    Energy Technology Data Exchange (ETDEWEB)

    Abrahamson, L. (ed.)

    1986-04-01

    This manual presents guidelines for software standards which were developed so that software project-development teams and management involved in approving the software could have a generalized view of all phases in the software production procedure and the steps involved in completing each phase. Guidelines are presented for six phases of software development: project definition, building a user interface, designing software, writing code, testing code, and preparing software documentation. The discussions for each phase include examples illustrating the recommended guidelines. 45 refs. (DWL)

  4. Guidelines for the verification and validation of expert system software and conventional software: Evaluation of knowledge base certification methods. Volume 4

    International Nuclear Information System (INIS)

    Miller, L.A.; Hayes, J.E.; Mirsky, S.M.

    1995-03-01

    This report presents the results of the Knowledge Base Certification activity of the expert systems verification and validation (V ampersand V) guideline development project which is jointly funded by the US Nuclear Regulatory Commission and the Electric Power Research Institute. The ultimate objective is the formulation of guidelines for the V ampersand V of expert systems for use in nuclear power applications. This activity is concerned with the development and testing of various methods for assuring the quality of knowledge bases. The testing procedure used was that of behavioral experiment, the first known such evaluation of any type of V ampersand V activity. The value of such experimentation is its capability to provide empirical evidence for -- or against -- the effectiveness of plausible methods in helping people find problems in knowledge bases. The three-day experiment included 20 participants from three nuclear utilities, the Nuclear Regulatory Commission's Technical training Center, the University of Maryland, EG ampersand G Idaho, and SAIC. The study used two real nuclear expert systems: a boiling water reactor emergency operating procedures tracking system and a pressurized water reactor safety assessment systems. Ten participants were assigned to each of the expert systems. All participants were trained in and then used a sequence of four different V ampersand V methods selected as being the best and most appropriate for study on the basis of prior evaluation activities. These methods either involved the analysis and tracing of requirements to elements in the knowledge base (requirements grouping and requirements tracing) or else involved direct inspection of the knowledge base for various kinds of errors. Half of the subjects within each system group used the best manual variant of the V ampersand V methods (the control group), while the other half were supported by the results of applying real or simulated automated tools to the knowledge bases

  5. Guidelines for technical reviews of software products

    Energy Technology Data Exchange (ETDEWEB)

    Wilburn, N.P.

    1982-03-01

    A guideline is given for technical review of products developed during a software life cycle. Purposes and benefits of reviews are given. Varieties of reviews, when they should take place, roles of the reviewers and products of the review are described.

  6. Guidelines for technical reviews of software products

    International Nuclear Information System (INIS)

    Wilburn, N.P.

    1982-03-01

    A guideline is given for technical review of products developed during a software life cycle. Purposes and benefits of reviews are given. Varieties of reviews, when they should take place, roles of the reviewers and products of the review are described

  7. General guidelines for biomedical software development.

    Science.gov (United States)

    Silva, Luis Bastiao; Jimenez, Rafael C; Blomberg, Niklas; Luis Oliveira, José

    2017-01-01

    Most bioinformatics tools available today were not written by professional software developers, but by people that wanted to solve their own problems, using computational solutions and spending the minimum time and effort possible, since these were just the means to an end. Consequently, a vast number of software applications are currently available, hindering the task of identifying the utility and quality of each. At the same time, this situation has hindered regular adoption of these tools in clinical practice. Typically, they are not sufficiently developed to be used by most clinical researchers and practitioners. To address these issues, it is necessary to re-think how biomedical applications are built and adopt new strategies that ensure quality, efficiency, robustness, correctness and reusability of software components. We also need to engage end-users during the development process to ensure that applications fit their needs. In this review, we present a set of guidelines to support biomedical software development, with an explanation of how they can be implemented and what kind of open-source tools can be used for each specific topic.

  8. Guidelines for the verification and validation of expert system software and conventional software: Volume 2, Survey and assessment of conventional software verification and validation methods Revision 1, Final report

    International Nuclear Information System (INIS)

    Miller, L.A.; Groundwater, E.H.; Hayes, J.E.; Mirsky, S.M.

    1995-05-01

    By means of a literature survey, a comprehensive set of methods was identified for the verification and validation of conventional software. The 153 methods so identified were classified according to their appropriateness for various phases of a developmental life-cycle -- requirements, design, and implementation; the last category was subdivided into two, static testing and dynamic testing methods. The methods were then characterized in terms of eight rating factors, four concerning ease-of-use of the methods and four concerning the methods' power to detect defects. Based on these factors, two measurements were developed to permit quantitative comparisons among methods, a Cost-Benefit Metric and an Effectiveness Metric. The Effectiveness Metric was further refined to provide three different estimates for each method, depending on three classes of needed stringency of V ampersand V (determined by ratings of a system's complexity and required-integrity). Methods were then rank-ordered for each of the three classes in terms of their overall cost-benefits and effectiveness. The applicability was then assessed of each method for the four identified components of knowledge-based and expert systems, as well as the system as a whole

  9. Guidelines for upgrading of low volume roads

    CSIR Research Space (South Africa)

    Division of Roads and Transport Technology CSIR

    1993-03-01

    Full Text Available The purpose of this manual is to provide guidelines on the upgrading of gravel low volume roads to roads and maintenance personnel of road authorities of all sizes. Low volume is, for the purpose of this document, defined to be less than 500...

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

  11. Programming Guidelines for FBD Programs in Reactor Protection System Software

    International Nuclear Information System (INIS)

    Jung, Se Jin; Lee, Dong Ah; Kim, Eui Sub; Yoo, Jun Beom; Lee, Jang Su

    2014-01-01

    Properties of programming languages, such as reliability, traceability, etc., play important roles in software development to improve safety. Several researches are proposed guidelines about programming to increase the dependability of software which is developed for safety critical systems. Misra-c is a widely accepted programming guidelines for the C language especially in the sector of vehicle industry. NUREG/CR-6463 helps engineers in nuclear industry develop software in nuclear power plant systems more dependably. FBD (Function Block Diagram), which is one of programming languages defined in IEC 61131-3 standard, is often used for software development of PLC (programmable logic controllers) in nuclear power plants. Software development for critical systems using FBD needs strict guidelines, because FBD is a general language and has easily mistakable elements. There are researches about guidelines for IEC 61131-3 programming languages. They, however, do not specify details about how to use languages. This paper proposes new guidelines for the FBD based on NUREG/CR-6463. The paper introduces a CASE (Computer-Aided Software Engineering) tool to check FBD programs with the new guidelines and shows availability with a case study using a FBD program in a reactor protection system. The paper is organized as follows

  12. Collected software engineering papers, volume 9

    Science.gov (United States)

    1991-01-01

    This document is a collection of selected technical papers produced by participants in the Software Engineering Laboratory (SEL) from November 1990 through October 1991. The purpose of the document is to make available, in one reference, some results of SEL research that originally appeared in a number of different forums. This is the ninth such volume of technical papers produced by the SEL. Although these papers cover several topics related to software engineering, they do not encompass the entire scope of SEL activities and interests. For the convenience of this presentation, the eight papers contained here are grouped into three major categories: (1) software models studies; (2) software measurement studies; and (3) Ada technology studies. The first category presents studies on reuse models, including a software reuse model applied to maintenance and a model for an organization to support software reuse. The second category includes experimental research methods and software measurement techniques. The third category presents object-oriented approaches using Ada and object-oriented features proposed for Ada. The SEL is actively working to understand and improve the software development process at GSFC.

  13. Collected software engineering papers, volume 11

    Science.gov (United States)

    1993-01-01

    This document is a collection of selected technical papers produced by participants in the Software Engineering Laboratory (SEL) from November 1992 through November 1993. The purpose of the document is to make available, in one reference, some results of SEL research that originally appeared in a number of different forums. This is the 11th such volume of technical papers produced by the SEL. Although these papers cover several topics related to software engineering, they do not encompass the entire scope of SEL activities and interests. Additional information about the SEL and its research efforts may be obtained from the sources listed in the bibliography at the end of this document.

  14. Collected software engineering papers, volume 12

    Science.gov (United States)

    1994-01-01

    This document is a collection of selected technical papers produced by participants in the Software Engineering Laboratory (SEL) from November 1993 through October 1994. The purpose of the document is to make available, in one reference, some results of SEL research that originally appeared in a number of different forums. This is the 12th such volume of technical papers produced by the SEL. Although these papers cover several topics related to software engineering, they do not encompass the entire scope of SEL activities and interests. Additional information about the SEL and its research efforts may be obtained from the sources listed in the bibliography at the end of this document.

  15. Subsystem Design Guidelines for Extensible General-Purpose Software

    NARCIS (Netherlands)

    Grefen, P.W.P.J.; Wieringa, Roelf J.; Magee, J.N.; Perry, D.E.

    1998-01-01

    We discuss subsystem design for extensible general-purpose information systemswe extract guidelines from a case study of the redesign and extension of an advanced workflow management system and place them into the context of existing software engineering research. Key aspect is the distinction

  16. Management Guidelines for Database Developers' Teams in Software Development Projects

    Science.gov (United States)

    Rusu, Lazar; Lin, Yifeng; Hodosi, Georg

    Worldwide job market for database developers (DBDs) is continually increasing in last several years. In some companies, DBDs are organized as a special team (DBDs team) to support other projects and roles. As a new role, the DBDs team is facing a major problem that there are not any management guidelines for them. The team manager does not know which kinds of tasks should be assigned to this team and what practices should be used during DBDs work. Therefore in this paper we have developed a set of management guidelines, which includes 8 fundamental tasks and 17 practices from software development process, by using two methodologies Capability Maturity Model (CMM) and agile software development in particular Scrum in order to improve the DBDs team work. Moreover the management guidelines developed here has been complemented with practices from authors' experience in this area and has been evaluated in the case of a software company. The management guidelines for DBD teams presented in this paper could be very usefully for other companies too that are using a DBDs team and could contribute towards an increase of the efficiency of these teams in their work on software development projects.

  17. Guidelines for using empirical studies in software engineering education

    Directory of Open Access Journals (Sweden)

    Fabian Fagerholm

    2017-09-01

    Full Text Available Software engineering education is under constant pressure to provide students with industry-relevant knowledge and skills. Educators must address issues beyond exercises and theories that can be directly rehearsed in small settings. Industry training has similar requirements of relevance as companies seek to keep their workforce up to date with technological advances. Real-life software development often deals with large, software-intensive systems and is influenced by the complex effects of teamwork and distributed software development, which are hard to demonstrate in an educational environment. A way to experience such effects and to increase the relevance of software engineering education is to apply empirical studies in teaching. In this paper, we show how different types of empirical studies can be used for educational purposes in software engineering. We give examples illustrating how to utilize empirical studies, discuss challenges, and derive an initial guideline that supports teachers to include empirical studies in software engineering courses. Furthermore, we give examples that show how empirical studies contribute to high-quality learning outcomes, to student motivation, and to the awareness of the advantages of applying software engineering principles. Having awareness, experience, and understanding of the actions required, students are more likely to apply such principles under real-life constraints in their working life.

  18. Software Engineering Laboratory Series: Collected Software Engineering Papers. Volume 14

    Science.gov (United States)

    1996-01-01

    The Software Engineering Laboratory (SEL) is an organization sponsored by NASA/GSFC and created to investigate the effectiveness of software engineering technologies when applied to the development of application software. The activities, findings, and recommendations of the SEL are recorded in the Software Engineering Laboratory Series, a continuing series of reports that includes this document.

  19. Software Engineering Laboratory Series: Collected Software Engineering Papers. Volume 13

    Science.gov (United States)

    1995-01-01

    The Software Engineering Laboratory (SEL) is an organization sponsored by NASA/GSFC and created to investigate the effectiveness of software engineering technologies when applied to the development of application software. The activities, findings, and recommendations of the SEL are recorded in the Software Engineering Laboratory Series, a continuing series of reports that includes this document.

  20. Software Engineering Laboratory Series: Collected Software Engineering Papers. Volume 15

    Science.gov (United States)

    1997-01-01

    The Software Engineering Laboratory (SEL) is an organization sponsored by NASA/GSFC and created to investigate the effectiveness of software engineering technologies when applied to the development of application software. The activities, findings, and recommendations of the SEL are recorded in the Software Engineering Laboratory Series, a continuing series of reports that includes this document.

  1. Application Reuse Library for Software, Requirements, and Guidelines

    Science.gov (United States)

    Malin, Jane T.; Thronesbery, Carroll

    1994-01-01

    Better designs are needed for expert systems and other operations automation software, for more reliable, usable and effective human support. A prototype computer-aided Application Reuse Library shows feasibility of supporting concurrent development and improvement of advanced software by users, analysts, software developers, and human-computer interaction experts. Such a library expedites development of quality software, by providing working, documented examples, which support understanding, modification and reuse of requirements as well as code. It explicitly documents and implicitly embodies design guidelines, standards and conventions. The Application Reuse Library provides application modules with Demo-and-Tester elements. Developers and users can evaluate applicability of a library module and test modifications, by running it interactively. Sub-modules provide application code and displays and controls. The library supports software modification and reuse, by providing alternative versions of application and display functionality. Information about human support and display requirements is provided, so that modifications will conform to guidelines. The library supports entry of new application modules from developers throughout an organization. Example library modules include a timer, some buttons and special fonts, and a real-time data interface program. The library prototype is implemented in the object-oriented G2 environment for developing real-time expert systems.

  2. Collected software engineering papers, volume 2

    Science.gov (United States)

    1983-01-01

    Topics addressed include: summaries of the software engineering laboratory (SEL) organization, operation, and research activities; results of specific research projects in the areas of resource models and software measures; and strategies for data collection for software engineering research.

  3. Concrete containment integrity software: Procedure manual and guidelines

    International Nuclear Information System (INIS)

    Dameron, R.A.; Dunham, R.S.; Rashid, Y.R.

    1990-06-01

    This report is an executive summary describing the concrete containment analysis methodology and software that was developed in the EPRI-sponsored research to predict the overpressure behavior and leakage of concrete containments. A set of guidelines has been developed for performing reliable 2D axisymmetric concrete containment analysis with a cracking concrete constitutive model developed by ANATECH. The software package developed during this research phase is designed for use in conjunction with ABAQUS-EPGEN; it provides the concrete model and automates axisymmetric grid preparation, and rebar generation for 2D and 3D grids. The software offers the option of generating pre-programmed axisymmetric grids that can be tailored to a specific containment by input of a few geometry parameters. The goal of simplified axisymmetric analysis within the framework of the containment leakage prediction methodology is to compute global liner strain histories at various locations within the containment. A simplified approach for generating peak liner strains at structural discontinuities as function of the global liner strains has been presented in a separate leakage criteria document; the curves for strain magnification factors and liner stress triaxiality factors found in that document are intended to be applied to the global liner strain histories developed through global 2D analysis. This report summarizes the procedures for global 2D analysis and gives an overview of the constitutive model and the special purpose concrete containment analysis software developed in this research phase. 8 refs., 10 figs

  4. Collected Software Engineering Papers, Volume 10

    Science.gov (United States)

    1992-01-01

    This document is a collection of selected technical papers produced by participants in the Software Engineering Laboratory (SEL) from Oct. 1991 - Nov. 1992. The purpose of the document is to make available, in one reference, some results of SEL research that originally appeared in a number of different forums. Although these papers cover several topics related to software engineering, they do not encompass the entire scope of SEL activities and interests. Additional information about the SEL and its research efforts may be obtained from the sources listed in the bibliography at the end of this document. For the convenience of this presentation, the 11 papers contained here are grouped into 5 major sections: (1) the Software Engineering Laboratory; (2) software tools studies; (3) software models studies; (4) software measurement studies; and (5) Ada technology studies.

  5. TMS communications software. Volume 1: Computer interfaces

    Science.gov (United States)

    Brown, J. S.; Lenker, M. D.

    1979-01-01

    A prototype bus communications system, which is being used to support the Trend Monitoring System (TMS) as well as for evaluation of the bus concept is considered. Hardware and software interfaces to the MODCOMP and NOVA minicomputers are included. The system software required to drive the interfaces in each TMS computer is described. Documentation of other software for bus statistics monitoring and for transferring files across the bus is also included.

  6. Collected software engineering papers, volume 8

    Science.gov (United States)

    1990-01-01

    A collection of selected technical papers produced by participants in the Software Engineering Laboratory (SEL) during the period November 1989 through October 1990 is presented. The purpose of the document is to make available, in one reference, some results of SEL research that originally appeared in a number of different forums. Although these papers cover several topics related to software engineering, they do not encompass the entire scope of SEL activities and interests. Additional information about the SEL and its research efforts may be obtained from the sources listed in the bibliography. The seven presented papers are grouped into four major categories: (1) experimental research and evaluation of software measurement; (2) studies on models for software reuse; (3) a software tool evaluation; and (4) Ada technology and studies in the areas of reuse and specification.

  7. Collected software engineering papers, volume 7

    Science.gov (United States)

    1989-01-01

    A collection is presented of selected technical papers produced by participants in the Software Engineering Laboratory (SEL) during the period Dec. 1988 to Oct. 1989. The purpose of the document is to make available, in one reference, some results of SEL research that originally appeared in a number of different forums. For the convenience of this presentation, the seven papers contained here are grouped into three major categories: (1) Software Measurement and Technology Studies; (2) Measurement Environment Studies; and (3) Ada Technology Studies. The first category presents experimental research and evaluation of software measurement and technology; the second presents studies on software environments pertaining to measurement. The last category represents Ada technology and includes research, development, and measurement studies.

  8. CADDIS Volume 4. Data Analysis: Download Software

    Science.gov (United States)

    Overview of the data analysis tools available for download on CADDIS. Provides instructions for downloading and installing CADStat, access to Microsoft Excel macro for computing SSDs, a brief overview of command line use of R, a statistical software.

  9. KAERI software verification and validation guideline for developing safety-critical software in digital I and C system of NPP

    International Nuclear Information System (INIS)

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

    1997-07-01

    This technical report is to present V and V guideline development methodology for safety-critical software in NPP safety system. Therefore it is to present V and V guideline of planning phase for the NPP safety system in addition to critical safety items, for example, independence philosophy, software safety analysis concept, commercial off the shelf (COTS) software evaluation criteria, inter-relationships between other safety assurance organizations, including the concepts of existing industrial standard, IEEE Std-1012, IEEE Std-1059. This technical report includes scope of V and V guideline, guideline framework as part of acceptance criteria, V and V activities and task entrance as part of V and V activity and exit criteria, review and audit, testing and QA records of V and V material and configuration management, software verification and validation plan production etc., and safety-critical software V and V methodology. (author). 11 refs

  10. Guidance and Control Software Project Data - Volume 2: Development Documents

    Science.gov (United States)

    Hayhurst, Kelly J. (Editor)

    2008-01-01

    The Guidance and Control Software (GCS) project was the last in a series of software reliability studies conducted at Langley Research Center between 1977 and 1994. The technical results of the GCS project were recorded after the experiment was completed. Some of the support documentation produced as part of the experiment, however, is serving an unexpected role far beyond its original project context. Some of the software used as part of the GCS project was developed to conform to the RTCA/DO-178B software standard, "Software Considerations in Airborne Systems and Equipment Certification," used in the civil aviation industry. That standard requires extensive documentation throughout the software development life cycle, including plans, software requirements, design and source code, verification cases and results, and configuration management and quality control data. The project documentation that includes this information is open for public scrutiny without the legal or safety implications associated with comparable data from an avionics manufacturer. This public availability has afforded an opportunity to use the GCS project documents for DO-178B training. This report provides a brief overview of the GCS project, describes the 4-volume set of documents and the role they are playing in training, and includes the development documents from the GCS project. Volume 2 contains three appendices: A. Guidance and Control Software Development Specification; B. Design Description for the Pluto Implementation of the Guidance and Control Software; and C. Source Code for the Pluto Implementation of the Guidance and Control Software

  11. Software Assurance Curriculum Project Volume 4: Community College Education

    Science.gov (United States)

    2011-09-01

    ITiCSE) Information Assurance (IA) Curriculum Guidelines Working Group examined existing IA academic program curricula and governmental and industry...copyright, and plagiarism ; “Ten Commandments for Computer Ethics” C Overview of operating systems (1 hour): role and purpose of operating systems; simple... plagiarism , and software piracy. Chooses to respond professionally to ethical issues in computing, such as intellectual property, plagiarism

  12. Development of Automatic Visceral Fat Volume Calculation Software for CT Volume Data

    Directory of Open Access Journals (Sweden)

    Mitsutaka Nemoto

    2014-01-01

    Full Text Available Objective. To develop automatic visceral fat volume calculation software for computed tomography (CT volume data and to evaluate its feasibility. Methods. A total of 24 sets of whole-body CT volume data and anthropometric measurements were obtained, with three sets for each of four BMI categories (under 20, 20 to 25, 25 to 30, and over 30 in both sexes. True visceral fat volumes were defined on the basis of manual segmentation of the whole-body CT volume data by an experienced radiologist. Software to automatically calculate visceral fat volumes was developed using a region segmentation technique based on morphological analysis with CT value threshold. Automatically calculated visceral fat volumes were evaluated in terms of the correlation coefficient with the true volumes and the error relative to the true volume. Results. Automatic visceral fat volume calculation results of all 24 data sets were obtained successfully and the average calculation time was 252.7 seconds/case. The correlation coefficients between the true visceral fat volume and the automatically calculated visceral fat volume were over 0.999. Conclusions. The newly developed software is feasible for calculating visceral fat volumes in a reasonable time and was proved to have high accuracy.

  13. Review guidelines on software languages for use in nuclear power plant safety systems. Final report

    Energy Technology Data Exchange (ETDEWEB)

    Hecht, H.; Hecht, M.; Graff, S.; Green, W.; Lin, D.; Koch, S.; Tai, A.; Wendelboe, D. [SoHaR, Inc., Beverly Hills, CA (United States)

    1996-06-01

    Guidelines for the programming and auditing of software written in high level languages for safety systems are presented. The guidelines are derived from a framework of issues significant to software safety which was gathered from relevant standards and research literature. Language-specific adaptations of these guidelines are provided for the following high level languages: Ada, C/C++, Programmable Logic Controller (PLC) Ladder Logic, International Electrotechnical Commission (IEC) Standard 1131-3 Sequential Function Charts, Pascal, and PL/M. Appendices to the report include a tabular summary of the guidelines and additional information on selected languages.s

  14. A Guideline of Using Case Method in Software Engineering Courses

    Science.gov (United States)

    Zainal, Dzulaiha Aryanee Putri; Razali, Rozilawati; Shukur, Zarina

    2014-01-01

    Software Engineering (SE) education has been reported to fall short in producing high quality software engineers. In seeking alternative solutions, Case Method (CM) is regarded as having potential to solve the issue. CM is a teaching and learning (T&L) method that has been found to be effective in Social Science education. In principle,…

  15. SU-E-P-43: A Knowledge Based Approach to Guidelines for Software Safety

    International Nuclear Information System (INIS)

    Salomons, G; Kelly, D

    2015-01-01

    Purpose: In the fall of 2012, a survey was distributed to medical physicists across Canada. The survey asked the respondents to comment on various aspects of software development and use in their clinic. The survey revealed that most centers employ locally produced (in-house) software of some kind. The respondents also indicated an interest in having software guidelines, but cautioned that the realities of cancer clinics include variations, that preclude a simple solution. Traditional guidelines typically involve periodically repeating a set of prescribed tests with defined tolerance limits. However, applying a similar formula to software is problematic since it assumes that the users have a perfect knowledge of how and when to apply the software and that if the software operates correctly under one set of conditions it will operate correctly under all conditions Methods: In the approach presented here the personnel involved with the software are included as an integral part of the system. Activities performed to improve the safety of the software are done with both software and people in mind. A learning oriented approach is taken, following the premise that the best approach to safety is increasing the understanding of those associated with the use or development of the software. Results: The software guidance document is organized by areas of knowledge related to use and development of software. The categories include: knowledge of the underlying algorithm and its limitations; knowledge of the operation of the software, such as input values, parameters, error messages, and interpretation of output; and knowledge of the environment for the software including both data and users. Conclusion: We propose a new approach to developing guidelines which is based on acquiring knowledge-rather than performing tests. The ultimate goal is to provide robust software guidelines which will be practical and effective

  16. Software Engineering and Knowledge Engineering Theory and Practice Volume 2

    CERN Document Server

    2012-01-01

    The volume includes a set of selected papers extended and revised from the I2009 Pacific-Asia Conference on Knowledge Engineering and Software Engineering (KESE 2009) was held on December 19~ 20, 2009, Shenzhen, China.   Volume 2 is to provide a forum for researchers, educators, engineers, and government officials involved in the general areas of Knowledge Engineering and Communication Technology to disseminate their latest research results and exchange views on the future research directions of these fields. 135 high-quality papers are included in the volume. Each paper has been peer-reviewed by at least 2 program committee members and selected by the volume editor Prof.Yanwen Wu.   On behalf of the this volume, we would like to express our sincere appreciation to all of authors and referees for their efforts reviewing the papers. Hoping you can find lots of profound research ideas and results on the related fields of Knowledge Engineering and Communication Technology. 

  17. Guidelines for evaluating software configuration management plans for digital instrumentation and control systems

    International Nuclear Information System (INIS)

    Cheon, Se Woo; Park, Jong Kyun; Lee, Ki Young; Lee, Jang Soo; Kim, Jang Yeon

    2001-08-01

    Software configuration management (SCM) is the process for identifying software configuration items (CIs), controlling the implementation and changes to software, recording and reporting the status of changes, and verifying the completeness and correctness of the released software. SCM consists of two major aspects: planning and implementation. Effective SCM involves planning for how activities are to be performed, and performing these activities in accordance with the Plan. This report first reviews the background of SCM that include key standards, SCM disciplines, SCM basic functions, baselines, software entity, SCM process, the implementation of SCM, and the tools of SCM. In turn, the report provides the guidelines for evaluating the SCM Plan for digital I and C systems of nuclear power plants. Most of the guidelines in the report are based on IEEE Std 828 and ANSI/IEEE Std 1042. According to BTP-14, NUREG-0800, the evaluation topics on the SCM Plan is classified into three categories: management, implementation, and resource characteristics

  18. Human-system interface design review guideline -- Process and guidelines: Final report. Revision 1, Volume 1

    International Nuclear Information System (INIS)

    1996-06-01

    NUREG-0700, Revision 1, provides human factors engineering (HFE) guidance to the US Nuclear Regulatory Commission staff for its: (1) review of the human system interface (HSI) design submittals prepared by licensees or applications for a license or design certification of commercial nuclear power plants, and (2) performance of HSI reviews that could be undertaken as part of an inspection or other type of regulatory review involving HSI design or incidents involving human performance. The guidance consists of a review process and HFE guidelines. The document describes those aspects of the HSI design review process that are important to the identification and resolution of human engineering discrepancies that could adversely affect plant safety. Guidance is provided that could be used by the staff to review an applicant's HSI design review process or to guide the development of an HSI design review plan, e.g., as part of an inspection activity. The document also provides detailed HFE guidelines for the assessment of HSI design implementations. NUREG-0700, Revision 1, consists of three stand-alone volumes. Volume 1 consists of two major parts. Part 1 describes those aspects of the review process of the HSI design that are important to identifying and resolving human engineering discrepancies. Part 2 contains detailed guidelines for a human factors engineering review which identify criteria for assessing the implementation of an applicant's or licensee's HSI design

  19. Human-system interface design review guideline -- Process and guidelines: Final report. Revision 1, Volume 1

    Energy Technology Data Exchange (ETDEWEB)

    None

    1996-06-01

    NUREG-0700, Revision 1, provides human factors engineering (HFE) guidance to the US Nuclear Regulatory Commission staff for its: (1) review of the human system interface (HSI) design submittals prepared by licensees or applications for a license or design certification of commercial nuclear power plants, and (2) performance of HSI reviews that could be undertaken as part of an inspection or other type of regulatory review involving HSI design or incidents involving human performance. The guidance consists of a review process and HFE guidelines. The document describes those aspects of the HSI design review process that are important to the identification and resolution of human engineering discrepancies that could adversely affect plant safety. Guidance is provided that could be used by the staff to review an applicant`s HSI design review process or to guide the development of an HSI design review plan, e.g., as part of an inspection activity. The document also provides detailed HFE guidelines for the assessment of HSI design implementations. NUREG-0700, Revision 1, consists of three stand-alone volumes. Volume 1 consists of two major parts. Part 1 describes those aspects of the review process of the HSI design that are important to identifying and resolving human engineering discrepancies. Part 2 contains detailed guidelines for a human factors engineering review which identify criteria for assessing the implementation of an applicant`s or licensee`s HSI design.

  20. Verification and validation guidelines for high integrity systems. Volume 1

    Energy Technology Data Exchange (ETDEWEB)

    Hecht, H.; Hecht, M.; Dinsmore, G.; Hecht, S.; Tang, D. [SoHaR, Inc., Beverly Hills, CA (United States)

    1995-03-01

    High integrity systems include all protective (safety and mitigation) systems for nuclear power plants, and also systems for which comparable reliability requirements exist in other fields, such as in the process industries, in air traffic control, and in patient monitoring and other medical systems. Verification aims at determining that each stage in the software development completely and correctly implements requirements that were established in a preceding phase, while validation determines that the overall performance of a computer system completely and correctly meets system requirements. Volume I of the report reviews existing classifications for high integrity systems and for the types of errors that may be encountered, and makes recommendations for verification and validation procedures, based on assumptions about the environment in which these procedures will be conducted. The final chapter of Volume I deals with a framework for standards in this field. Volume II contains appendices dealing with specific methodologies for system classification, for dependability evaluation, and for two software tools that can automate otherwise very labor intensive verification and validation activities.

  1. Verification and validation guidelines for high integrity systems. Volume 1

    International Nuclear Information System (INIS)

    Hecht, H.; Hecht, M.; Dinsmore, G.; Hecht, S.; Tang, D.

    1995-03-01

    High integrity systems include all protective (safety and mitigation) systems for nuclear power plants, and also systems for which comparable reliability requirements exist in other fields, such as in the process industries, in air traffic control, and in patient monitoring and other medical systems. Verification aims at determining that each stage in the software development completely and correctly implements requirements that were established in a preceding phase, while validation determines that the overall performance of a computer system completely and correctly meets system requirements. Volume I of the report reviews existing classifications for high integrity systems and for the types of errors that may be encountered, and makes recommendations for verification and validation procedures, based on assumptions about the environment in which these procedures will be conducted. The final chapter of Volume I deals with a framework for standards in this field. Volume II contains appendices dealing with specific methodologies for system classification, for dependability evaluation, and for two software tools that can automate otherwise very labor intensive verification and validation activities

  2. Software de balanced scorecard: proposta de um roteiro de implantação Balanced scorecard software: proposal of a guideline implementation

    Directory of Open Access Journals (Sweden)

    Oswaldo Keiji Hikage

    2006-04-01

    Full Text Available Em 1992, o conceito de Balanced Scorecard (BSC foi apresentado por Robert Kaplan e David Norton e em razão de sua disseminação muitas empresas que o adotaram e passaram por processos de fusões e aquisições tiveram suas informações aumentadas consideravelmente em seus bancos de dados. Esta série de informações e a necessidade de gerenciar com eficiência os indicadores estratégicos, de disponibilizar rapidamente relatórios gerenciais, analisar e simular cenários levaram as empresas a buscar um sistema automatizado. Dessa forma, algumas preocupações passaram a ter importância: como selecionar um software de BSC? Como implantar um software de BSC? Além das dificuldades inerentes à aquisição de qualquer software, a situação especificamente tratada neste artigo apresenta algumas peculiaridades, diante da intensa interação entre a sistemática do BSC e os softwares que o suportam. Este artigo, por meio de um estudo de caso realizado em uma empresa do setor de telecomunicações, enfoca a implantação de um software de BSC, visando ao desenvolvimento de um roteiro que possa sistematizar o processo.Since 1992, when Robert Kaplan and David Norton developed the concepts of Balanced Scorecard (BSC, many companies that adopted these concepts and survived in a higher competitive environment charicterized of high number of mergers, purchases and shutdowns increased the volume of information in their database. So, in consequence of the adoption of BSC, there is the needed for implementing a computerized control system, due to the work with the BSC and the management of a great volume of information. In this context, when the companies decide to implement a BSC software, they faced two problems: how to choose the BSC software? How to implement the selected software? This study proposes to develop a guideline for the BSC software introduction based on a case study in a telecommunication company and the experience from the practice on

  3. Guidelines to minimize cost of software quality in agile scrum process

    OpenAIRE

    Vijay, Deepa; Ganapathy, Gopinath

    2014-01-01

    This paper presents a case study of Agile Scrum process followed in Retail Domain project. This paper also reveals the impacts of Cost of Software Quality, when agile scrum process is not followed efficiently. While analyzing the case study, the gaps were found and guidelines for process improvements were also suggested in this paper.

  4. Introducing new software tool : Guidelines for introducing new software tool to a team. Case study

    OpenAIRE

    Benni, Nupur

    2013-01-01

    The objective of this thesis is to investigate what are the main obstacles in introducing a new software tool to an organisation and how to overcome those obstacles. If there are any definite set practices that could be used by leaders and managers, to minimise the resistance towards the change and the effects of such practices– both upon employees and the businesses or organisations. In addition,the research study aims to validate pre-existing literature and relevance of certain traits and s...

  5. Requirements for guidelines systems: implementation challenges and lessons from existing software-engineering efforts.

    Science.gov (United States)

    Shah, Hemant; Allard, Raymond D; Enberg, Robert; Krishnan, Ganesh; Williams, Patricia; Nadkarni, Prakash M

    2012-03-09

    A large body of work in the clinical guidelines field has identified requirements for guideline systems, but there are formidable challenges in translating such requirements into production-quality systems that can be used in routine patient care. Detailed analysis of requirements from an implementation perspective can be useful in helping define sub-requirements to the point where they are implementable. Further, additional requirements emerge as a result of such analysis. During such an analysis, study of examples of existing, software-engineering efforts in non-biomedical fields can provide useful signposts to the implementer of a clinical guideline system. In addition to requirements described by guideline-system authors, comparative reviews of such systems, and publications discussing information needs for guideline systems and clinical decision support systems in general, we have incorporated additional requirements related to production-system robustness and functionality from publications in the business workflow domain, in addition to drawing on our own experience in the development of the Proteus guideline system (http://proteme.org). The sub-requirements are discussed by conveniently grouping them into the categories used by the review of Isern and Moreno 2008. We cite previous work under each category and then provide sub-requirements under each category, and provide example of similar work in software-engineering efforts that have addressed a similar problem in a non-biomedical context. When analyzing requirements from the implementation viewpoint, knowledge of successes and failures in related software-engineering efforts can guide implementers in the choice of effective design and development strategies.

  6. Guidelines for conducting and reporting case study research in software engineering

    OpenAIRE

    Runeson, Per; Höst, Martin

    2009-01-01

    Case study is a suitable research methodology for software engineering research since it studies contemporary phenomena in its natural context. However, the understanding of what constitutes a case study varies, and hence the quality of the resulting studies. This paper aims at providing an introduction to case study methodology and guidelines for researchers conducting case studies and readers studying reports of such studies. The content is based on the authors’ own experience from condu...

  7. Review guidelines for software languages for use in nuclear power plant safety systems: Final report. Revision 1

    Energy Technology Data Exchange (ETDEWEB)

    Hecht, M.; Decker, D.; Graff, S.; Green, W.; Lin, D.; Dinsmore, G.; Koch, S. [SoHaR, Inc., Beverly Hills, CA (United States)

    1997-10-01

    Guidelines for the programming and auditing of software written in high level languages for safety systems are presented. The guidelines are derived from a framework of issues significant to software safety which was gathered from relevant standards and research literature. Language-specific adaptations of these guidelines are provided for the following high level languages: Ada83 and Ada95; C and C++; International Electrochemical Commission (IEC) Standard 1131-3 Ladder Logic, Sequential Function Charts, Structured Text, and Function Block Diagrams; Pascal; and PL/M. Appendices to the report include a tabular summary of the guidelines and additional information on selected languages.

  8. Review guidelines for software languages for use in nuclear power plant safety systems: Final report. Revision 1

    International Nuclear Information System (INIS)

    Hecht, M.; Decker, D.; Graff, S.; Green, W.; Lin, D.; Dinsmore, G.; Koch, S.

    1997-10-01

    Guidelines for the programming and auditing of software written in high level languages for safety systems are presented. The guidelines are derived from a framework of issues significant to software safety which was gathered from relevant standards and research literature. Language-specific adaptations of these guidelines are provided for the following high level languages: Ada83 and Ada95; C and C++; International Electrochemical Commission (IEC) Standard 1131-3 Ladder Logic, Sequential Function Charts, Structured Text, and Function Block Diagrams; Pascal; and PL/M. Appendices to the report include a tabular summary of the guidelines and additional information on selected languages

  9. ICESat (GLAS) Science Processing Software Document Series. Volume 1; Science Software Management Plan; 3.0

    Science.gov (United States)

    Hancock, David W., III

    1999-01-01

    This document provides the Software Management Plan for the GLAS Standard Data Software (SDS) supporting the GLAS instrument of the EOS ICESat Spacecraft. The SDS encompasses the ICESat Science Investigator-led Processing System (I-SIPS) Software and the Instrument Support Terminal (IST) Software. For the I-SIPS Software, the SDS will produce Level 0, Level 1, and Level 2 data products as well as the associated product quality assessments and descriptive information. For the IST Software, the SDS will accommodate the GLAS instrument support areas of engineering status, command, performance assessment, and instrument health status.

  10. TMS communications software. Volume 2: Bus interface unit

    Science.gov (United States)

    Gregor, P. J.

    1979-01-01

    A data bus communication system to support the space shuttle's Trend Monitoring System (TMS) and to provide a basis for evaluation of the bus concept is described. Installation of the system included developing both hardware and software interfaces between the bus and the specific TMS computers and terminals. The software written for the microprocessor-based bus interface units is described. The software implements both the general bus communications protocol and also the specific interface protocols for the TMS computers and terminals.

  11. Reinforced soil structures. Volume I, Design and construction guidelines

    Science.gov (United States)

    1990-11-01

    This report presents comprehensive guidelines for evaluating and using soil reinforcement techniques in the construction of retaining walls, embankment slopes, and natural or cut slopes. A variety of available systems for reinforced soil including in...

  12. Formal verification of software-based medical devices considering medical guidelines.

    Science.gov (United States)

    Daw, Zamira; Cleaveland, Rance; Vetter, Marcus

    2014-01-01

    Software-based devices have increasingly become an important part of several clinical scenarios. Due to their critical impact on human life, medical devices have very strict safety requirements. It is therefore necessary to apply verification methods to ensure that the safety requirements are met. Verification of software-based devices is commonly limited to the verification of their internal elements without considering the interaction that these elements have with other devices as well as the application environment in which they are used. Medical guidelines define clinical procedures, which contain the necessary information to completely verify medical devices. The objective of this work was to incorporate medical guidelines into the verification process in order to increase the reliability of the software-based medical devices. Medical devices are developed using the model-driven method deterministic models for signal processing of embedded systems (DMOSES). This method uses unified modeling language (UML) models as a basis for the development of medical devices. The UML activity diagram is used to describe medical guidelines as workflows. The functionality of the medical devices is abstracted as a set of actions that is modeled within these workflows. In this paper, the UML models are verified using the UPPAAL model-checker. For this purpose, a formalization approach for the UML models using timed automaton (TA) is presented. A set of requirements is verified by the proposed approach for the navigation-guided biopsy. This shows the capability for identifying errors or optimization points both in the workflow and in the system design of the navigation device. In addition to the above, an open source eclipse plug-in was developed for the automated transformation of UML models into TA models that are automatically verified using UPPAAL. The proposed method enables developers to model medical devices and their clinical environment using clinical workflows as one

  13. General guidelines for biomedical software development [version 1; referees: 2 approved

    Directory of Open Access Journals (Sweden)

    Luis Bastiao Silva

    2017-03-01

    Full Text Available Most bioinformatics tools available today were not written by professional software developers, but by people that wanted to solve their own problems, using computational solutions and spending the minimum time and effort possible, since these were just the means to an end. Consequently, a vast number of software applications are currently available, hindering the task of identifying the utility and quality of each. At the same time, this situation has hindered regular adoption of these tools in clinical practice. Typically, they are not sufficiently developed to be used by most clinical researchers and practitioners. To address these issues, it is necessary to re-think how biomedical applications are built and adopt new strategies that ensure quality, efficiency, robustness, correctness and reusability of software components. We also need to engage end-users during the development process to ensure that applications fit their needs. In this review, we present a set of guidelines to support biomedical software development, with an explanation of how they can be implemented and what kind of open-source tools can be used for each specific topic.

  14. General guidelines for biomedical software development [version 2; referees: 2 approved

    Directory of Open Access Journals (Sweden)

    Luis Bastiao Silva

    2017-07-01

    Full Text Available Most bioinformatics tools available today were not written by professional software developers, but by people that wanted to solve their own problems, using computational solutions and spending the minimum time and effort possible, since these were just the means to an end. Consequently, a vast number of software applications are currently available, hindering the task of identifying the utility and quality of each. At the same time, this situation has hindered regular adoption of these tools in clinical practice. Typically, they are not sufficiently developed to be used by most clinical researchers and practitioners. To address these issues, it is necessary to re-think how biomedical applications are built and adopt new strategies that ensure quality, efficiency, robustness, correctness and reusability of software components. We also need to engage end-users during the development process to ensure that applications fit their needs. In this review, we present a set of guidelines to support biomedical software development, with an explanation of how they can be implemented and what kind of open-source tools can be used for each specific topic.

  15. Renal cortical volume measured using automatic contouring software for computed tomography and its relationship with BMI, age and renal function

    Energy Technology Data Exchange (ETDEWEB)

    Muto, Natalia Sayuri, E-mail: nataliamuto@gmail.com [Department of Radiology, Hokkaido University Hospital, N15 W7, kita-ku, Sapporo City, 0608638 (Japan); Kamishima, Tamotsu, E-mail: ktamotamo2@yahoo.co.jp [Department of Radiology, Hokkaido University Hospital, N15 W7, kita-ku, Sapporo City, 0608638 (Japan); Harris, Ardene A., E-mail: ardene_b@yahoo.com [Department of Radiology, Hokkaido University Hospital, N15 W7, kita-ku, Sapporo City, 0608638 (Japan); Kato, Fumi, E-mail: fumikato@med.hokudai.ac.jp [Department of Radiology, Hokkaido University Hospital, N15 W7, kita-ku, Sapporo City, 0608638 (Japan); Onodera, Yuya, E-mail: yuyaonodera@med.hokudai.ac.jp [Department of Radiology, Hokkaido University Hospital, N15 W7, kita-ku, Sapporo City, 0608638 (Japan); Terae, Satoshi, E-mail: saterae@yahoo.co.jp [Department of Radiology, Hokkaido University Hospital, N15 W7, kita-ku, Sapporo City, 0608638 (Japan); Shirato, Hiroki, E-mail: shirato@med.hokudai.ac.jp [Department of Radiology, Hokkaido University Hospital, N15 W7, kita-ku, Sapporo City, 0608638 (Japan)

    2011-04-15

    Purpose: To evaluate the relationship between renal cortical volume, measured by an automatic contouring software, with body mass index (BMI), age and renal function. Materials and methods: The study was performed in accordance to the institutional guidelines at our hospital. Sixty-four patients (34 men, 30 women), aged 19 to 79 years had their CT scans for diagnosis or follow-up of hepatocellular carcinoma retrospectively examined by a computer workstation using a software that automatically contours the renal cortex and the renal parenchyma. Body mass index and estimated glomerular filtration rate (eGFR) were calculated based on data collected. Statistical analysis was done using the Student t-test, multiple regression analysis, and intraclass correlation coefficient (ICC). Results: The ICC for total renal and renal cortical volumes were 0.98 and 0.99, respectively. Renal volume measurements yielded a mean cortical volume of 105.8 cm{sup 3} {+-} 28.4 SD, mean total volume of 153 cm{sup 3} {+-} 39 SD and mean medullary volume of 47.8 cm{sup 3} {+-} 19.5 SD. The correlation between body weight/height/BMI and both total renal and cortical volumes presented r = 0.6, 0.6 and 0.4, respectively, p < 0.05, while the correlation between renal cortex and age was r = -0.3, p < 0.05. eGFR showed correlation with renal cortical volume r = 0.6, p < 0.05. Conclusion: This study demonstrated that renal cortical volume had a moderate positive relationship with BMI, moderate negative relationship with age, and a strong positive relationship with the renal function, and provided a new method to routinely produce volumetric assessment of the kidney.

  16. Renal cortical volume measured using automatic contouring software for computed tomography and its relationship with BMI, age and renal function

    International Nuclear Information System (INIS)

    Muto, Natalia Sayuri; Kamishima, Tamotsu; Harris, Ardene A.; Kato, Fumi; Onodera, Yuya; Terae, Satoshi; Shirato, Hiroki

    2011-01-01

    Purpose: To evaluate the relationship between renal cortical volume, measured by an automatic contouring software, with body mass index (BMI), age and renal function. Materials and methods: The study was performed in accordance to the institutional guidelines at our hospital. Sixty-four patients (34 men, 30 women), aged 19 to 79 years had their CT scans for diagnosis or follow-up of hepatocellular carcinoma retrospectively examined by a computer workstation using a software that automatically contours the renal cortex and the renal parenchyma. Body mass index and estimated glomerular filtration rate (eGFR) were calculated based on data collected. Statistical analysis was done using the Student t-test, multiple regression analysis, and intraclass correlation coefficient (ICC). Results: The ICC for total renal and renal cortical volumes were 0.98 and 0.99, respectively. Renal volume measurements yielded a mean cortical volume of 105.8 cm 3 ± 28.4 SD, mean total volume of 153 cm 3 ± 39 SD and mean medullary volume of 47.8 cm 3 ± 19.5 SD. The correlation between body weight/height/BMI and both total renal and cortical volumes presented r = 0.6, 0.6 and 0.4, respectively, p < 0.05, while the correlation between renal cortex and age was r = -0.3, p < 0.05. eGFR showed correlation with renal cortical volume r = 0.6, p < 0.05. Conclusion: This study demonstrated that renal cortical volume had a moderate positive relationship with BMI, moderate negative relationship with age, and a strong positive relationship with the renal function, and provided a new method to routinely produce volumetric assessment of the kidney.

  17. Main-coolant-pump shaft-seal guidelines. Volume 3. Specification guidelines. Final report

    International Nuclear Information System (INIS)

    Fair, C.E.; Greer, A.O.

    1983-03-01

    This report presents a set of guidelines and criteria to aid in the generation of procurement specifications for Main Coolant Pump Shaft Seals. The noted guidelines are developed from EPRI sponsored nuclear power plant seal operating experience studies, a review of pump and shaft seal literature and discussions with pump and seal designers. This report is preliminary in nature and could be expanded and finalized subsequent to completion of further design, test and evaluation efforts

  18. Main-coolant-pump shaft-seal guidelines. Volume 2. Operational guidelines. Final report

    International Nuclear Information System (INIS)

    Fair, C.E.; Greer, A.O.

    1983-03-01

    This report presents a set of guidelines and criteria for improving main coolant pump shaft seal operational reliability. The noted guidelines are developed from EPRI sponsored nuclear power plant seal operating experience studies. Usage procedures/practices and operational environment influence on seal life and reliability from the most recent such survey are summarized. The shaft seal and its auxiliary supporting systems are discussed both from technical and operational related viewpoints

  19. Main-coolant-pump shaft-seal guidelines. Volume 1. Maintenance-manual guidelines. Final report

    International Nuclear Information System (INIS)

    Fair, C.E.; Greer, A.O.

    1983-03-01

    This report presents a set of guidelines and a listing of information and data which should be included in maintenance manuals and procedures for Main Coolant Pump Shaft Seals. The noted guidelines and data listing are developed from EPRI sponsored nuclear plant seal operating experience studies. The maintenance oriented results of the most recent such study is summarized. The shaft seal and its auxiliary supporting systems are discussed from both technical and maintenance related viewpoints

  20. IMAGE information monitoring and applied graphics software environment. Volume 2. Software description

    International Nuclear Information System (INIS)

    Hallam, J.W.; Ng, K.B.; Upham, G.L.

    1986-09-01

    The EPRI Information Monitoring and Applied Graphics Environment (IMAGE) system is designed for 'fast proto-typing' of advanced concepts for computer-aided plant operations tools. It is a flexible software system which can be used for rapidly creating, dynamically driving and evaluating advanced operator aid displays. The software is written to be both host computer and graphic device independent

  1. Guidance and Control Software Project Data - Volume 4: Configuration Management and Quality Assurance Documents

    Science.gov (United States)

    Hayhurst, Kelly J. (Editor)

    2008-01-01

    The Guidance and Control Software (GCS) project was the last in a series of software reliability studies conducted at Langley Research Center between 1977 and 1994. The technical results of the GCS project were recorded after the experiment was completed. Some of the support documentation produced as part of the experiment, however, is serving an unexpected role far beyond its original project context. Some of the software used as part of the GCS project was developed to conform to the RTCA/DO-178B software standard, "Software Considerations in Airborne Systems and Equipment Certification," used in the civil aviation industry. That standard requires extensive documentation throughout the software development life cycle, including plans, software requirements, design and source code, verification cases and results, and configuration management and quality control data. The project documentation that includes this information is open for public scrutiny without the legal or safety implications associated with comparable data from an avionics manufacturer. This public availability has afforded an opportunity to use the GCS project documents for DO-178B training. This report provides a brief overview of the GCS project, describes the 4-volume set of documents and the role they are playing in training, and includes configuration management and quality assurance documents from the GCS project. Volume 4 contains six appendices: A. Software Accomplishment Summary for the Guidance and Control Software Project; B. Software Configuration Index for the Guidance and Control Software Project; C. Configuration Management Records for the Guidance and Control Software Project; D. Software Quality Assurance Records for the Guidance and Control Software Project; E. Problem Report for the Pluto Implementation of the Guidance and Control Software Project; and F. Support Documentation Change Reports for the Guidance and Control Software Project.

  2. Best-practices guidelines for L2PSA development and applications. Volume 1 - General

    International Nuclear Information System (INIS)

    Raimond, E.; Pichereau, F.; Durin, T.; Rahni, N.; Loeffler, H.; Roesch, O.; Lajtha, G.; Santamaria, C.S.; Dienstbier, J.; Rydl, A.; Holmberg, J.E.; Lindholm, I.; Maennistoe, I.; Pauli, E.M.; Dirksen, G.; Grindon, L.; Peers, K.; Bassi, C.; Hulqvist, G.; Parozzi, F.; Polidoro, F.; Cazzoli, E.; Vitazkova, J.; Burgazzi, L.; Brinkman, H.; Seidel, A.; Schubert, B.; Wohlstein, R.; Guentay, S.; Oury, L.; Ngatchou, C.; Siltanen, S.; Niemela, I.; Routamo, T.; Vincon, L.; Helstroem, P.

    2010-01-01

    The objective of this coordinated action was to develop best practice guidelines for the performance and application of Level 2 PSA with a view to achieve harmonisation at EU level and to allow a meaningful and practical uncertainty evaluation in a Level 2 PSA. Specific relationships with communities in charge of nuclear reactor safety (utilities, safety authorities, vendors, and research or services companies) have been established in order to define the current needs in terms of guidelines for Level 2 PSA development and application. An international workshop was organised in Hamburg, with the support of VATTENFALL, in November 2008. The Level 2 PSA experts from ASAMPSA2 project partners have proposed some guidelines for the development and application of L2PSA based on their experience, open literature, and on information available from international cooperation (EC Severe Accident network of Excellence - SARNET, IAEA standards, OECD-NEA publications and workshop). There are a large number of technical issues addressed in the guideline which are not all covered with the same level of detail in the first version of the guideline. This version was submitted for external review in November 2010 by severe accident and PSA experts (especially from SARNET and OECD-NEA members). The feedback of the external review will be dis cussed during an international open works hop planned for March 2011 and all outcomes will be taken into consideration in the final version of this guideline (June 2011). The guideline includes 3 volumes: - Volume 1 - General considerations on L2PSA. - Volume 2 - Technical recommendations for Gen II and III reactors. - Volume 3 - Specific considerations for future reactors (Gen IV). The recommendations formulated in the guideline should not be considered as 'mandatory' but should help Level 2 PSA developers to achieve high quality studies with limited time and resources. It may also help Level 2 PSA reviewers by positioning one specific

  3. Software Assurance Curriculum Project Volume 1: Master of Software Assurance Reference Curriculum

    Science.gov (United States)

    2010-08-01

    the-shelf (COTS); and service acquisition through methods including service-oriented architecture ( SOA ), cloud computing, and virtualization... exams to allow a candidate to ―test out‖ of a prerequisite. In some areas there may be certification programs, such as the IEEE Certified Software...networks, humans, and operations For system types: systems, systems-of-systems, distributed systems, SOA and cloud systems, Systems, systems-of

  4. Software Assurance Curriculum Project Volume 3: Master of Software Assurance Course Syllabi

    Science.gov (United States)

    2011-07-01

    Design Level Security Vulnerabilities.” ACM SIGSOFT Software Engineering Notes 34, 6 (November 2009): 1–5. • The Open Group. TOGAF . http...www.opengroup.org/ togaf / (2010). TOGAF is an industry standard architecture framework that may be used freely by any organ- ization wishing to develop...information systems architecture for use within that organization. TOGAF has been developed and continuously evolved since the mid-90s by representatives of

  5. ESRS guidelines for software safety reviews. Reference document for the organization and conduct of Engineering Safety Review Services (ESRS) on software important to safety in nuclear power plants

    International Nuclear Information System (INIS)

    2000-01-01

    The IAEA provides safety review services to assist Member States in the application of safety standards and, in particular, to evaluate and facilitate improvements in nuclear power plant safety performance. Complementary to the Operational Safety Review Team (OSART) and the International Regulatory Review Team (IRRT) services are the Engineering Safety Review Services (ESRS), which include reviews of siting, external events and structural safety, design safety, fire safety, ageing management and software safety. Software is of increasing importance to safety in nuclear power plants as the use of computer based equipment and systems, controlled by software, is increasing in new and older plants. Computer based devices are used in both safety related applications (such as process control and monitoring) and safety critical applications (such as reactor protection). Their dependability can only be ensured if a systematic, fully documented and reviewable engineering process is used. The ESRS on software safety are designed to assist a nuclear power plant or a regulatory body of a Member State in the review of documentation relating to the development, application and safety assessment of software embedded in computer based systems important to safety in nuclear power plants. The software safety reviews can be tailored to the specific needs of the requesting organization. Examples of such reviews are: project planning reviews, reviews of specific issues and reviews prior final acceptance. This report gives information on the possible scope of ESRS software safety reviews and guidance on the organization and conduct of the reviews. It is aimed at Member States considering these reviews and IAEA staff and external experts performing the reviews. The ESRS software safety reviews evaluate the degree to which software documents show that the development process and the final product conform to international standards, guidelines and current practices. Recommendations are

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

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

  8. Building better guidelines with BRIDGE-Wiz: development and evaluation of a software assistant to promote clarity, transparency, and implementability

    Science.gov (United States)

    Michel, George; Rosenfeld, Richard M; Davidson, Caryn

    2011-01-01

    Objective To demonstrate the feasibility of capturing the knowledge required to create guideline recommendations in a systematic, structured, manner using a software assistant. Practice guidelines constitute an important modality that can reduce the delivery of inappropriate care and support the introduction of new knowledge into clinical practice. However, many guideline recommendations are vague and underspecified, lack any linkage to supporting evidence or documentation of how they were developed, and prove to be difficult to transform into systems that influence the behavior of care providers. Methods The BRIDGE-Wiz application (Building Recommendations In a Developer's Guideline Editor) uses a wizard approach to address the questions: (1) under what circumstances? (2) who? (3) ought (with what level of obligation?) (4) to do what? (5) to whom? (6) how and why? Controlled natural language was applied to create and populate a template for recommendation statements. Results The application was used by five national panels to develop guidelines. In general, panelists agreed that the software helped to formalize a process for authoring guideline recommendations and deemed the application usable and useful. Discussion Use of BRIDGE-Wiz promotes clarity of recommendations by limiting verb choices, building active voice recommendations, incorporating decidability and executability checks, and limiting Boolean connectors. It enhances transparency by incorporating systematic appraisal of evidence quality, benefits, and harms. BRIDGE-Wiz promotes implementability by providing a pseudocode rule, suggesting deontic modals, and limiting the use of ‘consider’. Conclusion Users found that BRIDGE-Wiz facilitates the development of clear, transparent, and implementable guideline recommendations. PMID:21846779

  9. Modelling the Process of Induction Heating in Volume of a Bar Strip Using Flux 2D Software, coupled with Minitab Experimental Design Software

    Directory of Open Access Journals (Sweden)

    CODREAN Marius

    2016-05-01

    Full Text Available The purpose of this optimization is the identification of optimal parameters for processing the workpiece (the OLC45 steel bar, using inductive heating in volume. Flux 9.3.2 software, in 2D plan, has been employed in order to perform numerical simulations, while Minitab software has been used to determine optimal parameters.

  10. Guidelines for the development of applicative software for supervising and remote electric power substations; Diretrizes de desenvolvimento de softwares aplicativos para as estacoes supervisoras e remotas

    Energy Technology Data Exchange (ETDEWEB)

    Ribeiro, Guilherme Moutinho; Soares, Wellington Zakhia; Morais, Arnoldo Magela [Companhia Energetica de Minas Gerais (CEMIG), Belo Horizonte, MG (Brazil)

    1995-12-31

    The increasing application of remote control supervision systems composed of regional operation centers (COR) and remote terminal units (UTR) creates the adequate conditions for the development and implementation of operational engineering functions in electric power substations (SE). In order to provide the necessary elements for such qualitative improvement, this work presents guidelines for the development of applicative soft-wares for the local control and supervision to be installed in CORs and UTRS, based in CEMIG`s, the electric power company of Minas Gerais State - Southeast Brazil, experience 4 refs.

  11. SHTEREOM I SIMPLE WINDOWS® BASED SOFTWARE FOR STEREOLOGY. VOLUME AND NUMBER ESTIMATIONS

    Directory of Open Access Journals (Sweden)

    Emin Oğuzhan Oğuz

    2011-05-01

    Full Text Available Stereology has been earlier defined by Wiebel (1970 to be: "a body of mathematical methods relating to three dimensional parameters defining the structure from two dimensional measurements obtainable on sections of the structure." SHTEREOM I is a simple windows-based software for stereological estimation. In this first part, we describe the implementation of the number and volume estimation tools for unbiased design-based stereology. This software is produced in Visual Basic and can be used on personal computers operated by Microsoft Windows® operating systems that are connected to a conventional camera attached to a microscope and a microcator or a simple dial gauge. Microsoft NET Framework version 1.1 also needs to be downloaded for full use. The features of the SHTEREOM I software are illustrated through examples of stereological estimations in terms of volume and particle numbers for different magnifications (4X–100X. Point-counting grids are available for area estimations and for use with the most efficient volume estimation tool, the Cavalieri technique and are applied to Lizard testicle volume. An unbiased counting frame system is available for number estimations of the objects under investigation, and an on-screen manual stepping module for number estimations through the optical fractionator method is also available for the measurement of increments along the X and Y axes of the microscope stage for the estimation of rat brain hippocampal pyramidal neurons.

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

  13. CrossTalk: The Journal of Defense Software Engineering. Volume 21, Number 6

    Science.gov (United States)

    2008-06-01

    those already doing the job. • We don’t need no stinkin’ tools. Just as everyone wants instant gratification , we also want a super tool to make our...Guidelines for CrossTalk, available on the Internet at <www.stsc.hill.af.mil/crosstalk>. We accept article submissions on software-related topics at any...an operating system (Windows XP, Apple OS X, Red Hat Linux), a browser ( Internet Explorer, Firefox), protocol stack (IPv4, IPv6), a processor (Intel

  14. Software development to estimate the leaked volume from ruptured submarine pipelines; Desenvolvimento de um software para estimativa do volume vazado a partir de dutos submarions rompidos

    Energy Technology Data Exchange (ETDEWEB)

    Quadri, Marintho B.; Machado, Ricardo A.F.; Nogueira, Andre L.; Lopes, Toni J. [Universidade Federal de Santa Catarina (UFSC), Florianopolis, SC (Brazil). Dept. de Engenharia Quimica; Baptista, Renan M. [PETROBRAS, Rio de Janeiro, RJ (Brazil). Centro de Pesquisas (CENPES)

    2004-07-01

    The considerable increasing in the world petroleum consumption as the exhaustion of onshore reserves in the last decades leads the companies to exploit petroleum in offshore reserves (both shallow and deep water). As in onshore operations, accidents may also occur in submarine exploration. Leaking from submarine pipelines arises from corrosion pit and from axial or radial breakage. In all these three situations, the leaking is divided in three steps: pipeline depressurization until the internal pressure becomes equal to the external one; advective migration in which the driven force is the difference in the physical properties of the fluids; oil spill movement in the sea surface. A great number of mathematical models are Also available for the first and third steps. For the second one and theoretically, the most important situation, there is a restricted number of works respected to the oil volume leaked. The present study presents a software that is capable to accurate simulate a leakage through the advective migration phenomena. The software was validated for situations for different holes radii located in the upper side of a horizontal pipeline. Model results presented very good agreement with experimental data. (author)

  15. Guidelines for selecting codes for ground-water transport modeling of low-level waste burial sites. Volume 1. Guideline approach

    International Nuclear Information System (INIS)

    Simmons, C.S.; Cole, C.R.

    1985-05-01

    This document was written for the National Low-Level Waste Management Program to provide guidance for managers and site operators who need to select ground-water transport codes for assessing shallow-land burial site performance. The guidance given in this report also serves the needs of applications-oriented users who work under the direction of a manager or site operator. The guidelines are published in two volumes designed to support the needs of users having different technical backgrounds. An executive summary, published separately, gives managers and site operators an overview of the main guideline report. This volume includes specific recommendations for decision-making managers and site operators on how to use these guidelines. The more detailed discussions about the code selection approach are provided. 242 refs., 6 figs

  16. Basic guidelines to introduce electric circuit simulation software in a general physics course

    Science.gov (United States)

    Moya, A. A.

    2018-05-01

    The introduction of electric circuit simulation software for undergraduate students in a general physics course is proposed in order to contribute to the constructive learning of electric circuit theory. This work focuses on the lab exercises based on dc, transient and ac analysis in electric circuits found in introductory physics courses, and shows how students can use the simulation software to do simple activities associated with a lab exercise itself and with related topics. By introducing electric circuit simulation programs in a general physics course as a brief activitiy complementing lab exercise, students develop basic skills in using simulation software, improve their knowledge on the topology of electric circuits and perceive that the technology contributes to their learning, all without reducing the time spent on the actual content of the course.

  17. Basic Guidelines to Introduce Electric Circuit Simulation Software in a General Physics Course

    Science.gov (United States)

    Moya, A. A.

    2018-01-01

    The introduction of electric circuit simulation software for undergraduate students in a general physics course is proposed in order to contribute to the constructive learning of electric circuit theory. This work focuses on the lab exercises based on dc, transient and ac analysis in electric circuits found in introductory physics courses, and…

  18. Software Infrastructure for Computer-aided Drug Discovery and Development, a Practical Example with Guidelines.

    Science.gov (United States)

    Moretti, Loris; Sartori, Luca

    2016-09-01

    In the field of Computer-Aided Drug Discovery and Development (CADDD) the proper software infrastructure is essential for everyday investigations. The creation of such an environment should be carefully planned and implemented with certain features in order to be productive and efficient. Here we describe a solution to integrate standard computational services into a functional unit that empowers modelling applications for drug discovery. This system allows users with various level of expertise to run in silico experiments automatically and without the burden of file formatting for different software, managing the actual computation, keeping track of the activities and graphical rendering of the structural outcomes. To showcase the potential of this approach, performances of five different docking programs on an Hiv-1 protease test set are presented. © 2016 WILEY-VCH Verlag GmbH & Co. KGaA, Weinheim.

  19. Number-Crunching Software and the Input Problem: Guidelines and a Case Study

    Directory of Open Access Journals (Sweden)

    Stefan Gerber

    1994-01-01

    Full Text Available Most of the number-crunching software running on supercomputers lack a concept for an error-free input processing. The programs often terminate after several hours due to user input errors. We present an analysis of this input problem. First, we separate the input parsing system from the number-crunching code. Second, we define a general grammar suitable for an automatic generation of a parsing system using the LEX/YACC tools. This concept leads to an input system that is easy to use and the generated input data for the number-crunching software is as error free as possible. We discuss the implementation of such an input system for an ab initio quantum chemical package.

  20. SU-F-P-54: Guidelines to Check Image Registration QA of a Clinical Deformation Registration Software: A Single Institution Preliminary Study

    Energy Technology Data Exchange (ETDEWEB)

    Gill, G; Souri, S; Rea, A; Chen, Y; Antone, J; Qian, X; Riegel, A; Taylor, P; Marrero, M; Diaz, F; Cao, Y; Jamshidi, A; Klein, E [Northwell Health, Lake Success, NY (United States); Barley, S; Sorell, V; Karangelis, G [Oncology Systems Limited, Longbow Close, Shrewsbury SY1 3GZ (United Kingdom); Button, T [Stony Brook University Hospital, Stony Brook, NY (United States)

    2016-06-15

    Purpose: The objective of this study is to verify and analyze the accuracy of a clinical deformable image registration (DIR) software. Methods: To test clinical DIR software qualitatively and quantitatively, we focused on lung radiotherapy and analyzed a single (Lung) patient CT scan. Artificial anatomical changes were applied to account for daily variations during the course of treatment including the planning target volume (PTV) and organs at risk (OAR). The primary CT (pCT) and the structure set (pST) was deformed with commercial tool (ImSimQA-Oncology Systems Limited) and after artificial deformation (dCT and dST) sent to another commercial tool (VelocityAI-Varian Medical Systems). In Velocity, the deformed CT and structures (dCT and dST) were inversely deformed back to original primary CT (dbpCT and dbpST). We compared the dbpST and pST structure sets using similarity metrics. Furthermore, a binary deformation field vector (BDF) was created and sent to ImSimQA software for comparison with known “ground truth” deformation vector fields (DVF). Results: An image similarity comparison was made by using “ground truth” DVF and “deformed output” BDF with an output of normalized “cross correlation (CC)” and “mutual information (MI)” in ImSimQA software. Results for the lung case were MI=0.66 and CC=0.99. The artificial structure deformation in both pST and dbpST was analyzed using DICE coefficient, mean distance to conformity (MDC) and deformation field error volume histogram (DFEVH) by comparing them before and after inverse deformation. We have noticed inadequate structure match for CTV, ITV and PTV due to close proximity of heart and overall affected by lung expansion. Conclusion: We have seen similarity between pCT and dbpCT but not so well between pST and dbpST, because of inadequate structure deformation in clinical DIR system. This system based quality assurance test will prepare us for adopting the guidelines of upcoming AAPM task group 132

  1. RELAP/MOD3 code manual: User`s guidelines. Volume 5, Revision 1

    Energy Technology Data Exchange (ETDEWEB)

    Fletcher, C.D.; Schultz, R.R. [Lockheed Idaho Technologies Co., Idaho Falls, ID (United States)

    1995-08-01

    The RELAP5 code has been developed for best estimate transient simulation of light water reactor coolant systems during postulated accidents. The code models the coupled behavior of the reactor coolant system and the core for loss-of-coolant accidents, and operational transients, such as anticipated transient without scram, loss of offsite power, loss of feedwater, and loss of flow. A generic modeling approach is used that permits simulating a variety of thermal hydraulic systems. Control system and secondary system components are included to permit modeling of plant controls, turbines, condensers, and secondary feedwater systems. Volume V contains guidelines that have solved over the past several years through the use of the RELAP5 code.

  2. RELAP/MOD3 code manual: User's guidelines. Volume 5, Revision 1

    International Nuclear Information System (INIS)

    Fletcher, C.D.; Schultz, R.R.

    1995-08-01

    The RELAP5 code has been developed for best estimate transient simulation of light water reactor coolant systems during postulated accidents. The code models the coupled behavior of the reactor coolant system and the core for loss-of-coolant accidents, and operational transients, such as anticipated transient without scram, loss of offsite power, loss of feedwater, and loss of flow. A generic modeling approach is used that permits simulating a variety of thermal hydraulic systems. Control system and secondary system components are included to permit modeling of plant controls, turbines, condensers, and secondary feedwater systems. Volume V contains guidelines that have solved over the past several years through the use of the RELAP5 code

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

  4. Human-system interface design review guideline -- Reviewer`s checklist: Final report. Revision 1, Volume 2

    Energy Technology Data Exchange (ETDEWEB)

    NONE

    1996-06-01

    NUREG-0700, Revision 1, provides human factors engineering (HFE) guidance to the US Nuclear Regulatory Commission staff for its: (1) review of the human system interface (HSI) design submittals prepared by licensees or applications for a license or design certification of commercial nuclear power plants, and (2) performance of HSI reviews that could be undertaken as part of an inspection or other type of regulatory review involving HSI design or incidents involving human performance. The guidance consists of a review process and HFE guidelines. The document describes those aspects of the HSI design review process that are important to the identification and resolution of human engineering discrepancies that could adversely affect plant safety. Guidance is provided that could be used by the staff to review an applicant`s HSI design review process or to guide the development of an HSI design review plan, e.g., as part of an inspection activity. The document also provides detailed HFE guidelines for the assessment of HSI design implementations. NUREG-0700, Revision 1, consists of three stand-alone volumes. Volume 2 is a complete set of the guidelines contained in Volume 1, Part 2, but in a checklist format that can be used by reviewers to assemble sets of individual guidelines for use in specific design reviews. The checklist provides space for reviewers to enter guidelines evaluations and comments.

  5. Anatomic guidelines defined by reformatting images on MRI for volume measurement of amygdala and hippocampus

    International Nuclear Information System (INIS)

    Hoshida, Tohru; Sakaki, Toshisuke; Uematsu, Sumio.

    1995-01-01

    Twelve patients with intractable partial epilepsy underwent MR scans at the Epilepsy Center of the Johns Hopkins Hospital. There were five women and seven men, ranging in age from five to 51 years (mean age: 26 years). Coronal images were obtained using a 3-D SPGR. The coronal images were transferred to an Allegro 5.1 workstation, and reformatted along the cardinal axes (axial and sagittal) in multiple view points. The anterior end of the amygdala was measured at the level just posterior to the disappearance of the temporal stem. The semilunar gyrus of the amygdala was separated from the ambient gyrus by the semianular sulcus that forms the boundary between the amygdala and the entorhinal cortex. The delineation of the hippocampal formation included the subicular complex, hippocampal proper, dentate gyrus, alveus, and fimbria. The uncal cleft separated the uncus above from the parahippocampal gyrus below. The roof of this cleft was formed by the hippocampus and the dentate gyrus, and the floor, by the presubiculum and subiculum. Although using some guidelines, strictly separating the hippocampal head from the posterior part of the amygdala was not feasible as was previously reported, because of the isointensity on MRI between the cortex of the amygdala and the hippocampus. The most posterior portion of the hippocampus was measured at the level of the subsplenial gyri, just below the splenium of the corpus callosum, to measure the hippocampal volume in its near totality. Therefore, it is reliable, and clinically useful, to measure the combined total volume of the amygdala and the hippocampus when comparing results with those of other centers. (S.Y.)

  6. Open-source software for demand forecasting of clinical laboratory test volumes using time-series analysis

    Directory of Open Access Journals (Sweden)

    Emad A Mohammed

    2017-01-01

    Full Text Available Background: Demand forecasting is the area of predictive analytics devoted to predicting future volumes of services or consumables. Fair understanding and estimation of how demand will vary facilitates the optimal utilization of resources. In a medical laboratory, accurate forecasting of future demand, that is, test volumes, can increase efficiency and facilitate long-term laboratory planning. Importantly, in an era of utilization management initiatives, accurately predicted volumes compared to the realized test volumes can form a precise way to evaluate utilization management initiatives. Laboratory test volumes are often highly amenable to forecasting by time-series models; however, the statistical software needed to do this is generally either expensive or highly technical. Method: In this paper, we describe an open-source web-based software tool for time-series forecasting and explain how to use it as a demand forecasting tool in clinical laboratories to estimate test volumes. Results: This tool has three different models, that is, Holt-Winters multiplicative, Holt-Winters additive, and simple linear regression. Moreover, these models are ranked and the best one is highlighted. Conclusion: This tool will allow anyone with historic test volume data to model future demand.

  7. Improvement of productivity in low volume production industry layout by using witness simulation software

    Science.gov (United States)

    Jaffrey, V.; Mohamed, N. M. Z. N.; Rose, A. N. M.

    2017-10-01

    In almost all manufacturing industry, increased productivity and better efficiency of the production line are the most important goals. Most factories especially small scale factory has less awareness of manufacturing system optimization and lack of knowledge about it and uses the traditional way of management. Problems that are commonly identified in the factory are a high idle time of labour and also small production. This study is done in a Small and Medium Enterprises (SME) low volume production company. Data collection and problems affecting productivity and efficiency are identified. In this study, Witness simulation software is being used to simulate the layout and the output is focusing on the improvement of layout in terms of productivity and efficiency. In this study, the layout is rearranged by reducing the travel time from a workstation to another workstation. Then, the improved layout is modelled and the machine and labour statistic of both, original and improved layout is taken. Productivity and efficiency are calculated for both layout and then being compared.

  8. Guidelines for Software Portability

    NARCIS (Netherlands)

    Tanenbaum, A.S.; Klint, P.; Bohm, W.

    1978-01-01

    The areas in which programs are most unlikely to be portable are discussed. Attention is paid to programming languages, operating systems, file systems, I/O device characteristics, machine architecture and documentation. Pitfalls are indicated and in some cases solutions are suggested. Copyright ©

  9. Clinical Application of an Open-Source 3D Volume Rendering Software to Neurosurgical Approaches.

    Science.gov (United States)

    Fernandes de Oliveira Santos, Bruno; Silva da Costa, Marcos Devanir; Centeno, Ricardo Silva; Cavalheiro, Sergio; Antônio de Paiva Neto, Manoel; Lawton, Michael T; Chaddad-Neto, Feres

    2018-02-01

    Preoperative recognition of the anatomic individualities of each patient can help to achieve more precise and less invasive approaches. It also may help to anticipate potential complications and intraoperative difficulties. Here we describe the use, accuracy, and precision of a free tool for planning microsurgical approaches using 3-dimensional (3D) reconstructions from magnetic resonance imaging (MRI). We used the 3D volume rendering tool of a free open-source software program for 3D reconstruction of images of surgical sites obtained by MRI volumetric acquisition. We recorded anatomic reference points, such as the sulcus and gyrus, and vascularization patterns for intraoperative localization of lesions. Lesion locations were confirmed during surgery by intraoperative ultrasound and/or electrocorticography and later by postoperative MRI. Between August 2015 and September 2016, a total of 23 surgeries were performed using this technique for 9 low-grade gliomas, 7 high-grade gliomas, 4 cortical dysplasias, and 3 arteriovenous malformations. The technique helped delineate lesions with an overall accuracy of 2.6 ± 1.0 mm. 3D reconstructions were successfully performed in all patients, and images showed sulcus, gyrus, and venous patterns corresponding to the intraoperative images. All lesion areas were confirmed both intraoperatively and at the postoperative evaluation. With the technique described herein, it was possible to successfully perform 3D reconstruction of the cortical surface. This reconstruction tool may serve as an adjunct to neuronavigation systems or may be used alone when such a system is unavailable. Copyright © 2017 Elsevier Inc. All rights reserved.

  10. ICESat (GLAS) Science Processing Software Document Series. Volume 2; Science Data Management Plan; 4.0

    Science.gov (United States)

    Jester, Peggy L.; Hancock, David W., III

    1999-01-01

    This document provides the Data Management Plan for the GLAS Standard Data Software (SDS) supporting the GLAS instrument of the EOS ICESat Spacecraft. The SDS encompasses the ICESat Science Investigator-led Processing System (I-SIPS) Software and the Instrument Support Facility (ISF) Software. This Plan addresses the identification, authority, and description of the interface nodes associated with the GLAS Standard Data Products and the GLAS Ancillary Data.

  11. CrossTalk: The Journal of Defense Software Engineering. Volume 20, Number 8, August 2007

    National Research Council Canada - National Science Library

    2007-01-01

    ... organizations in multiple countries. Next, Nelson Perez and Earnest Ambrose relate their story of successful software process improvement in "Lessons Learned in Using Agile Methods for Process Improvement...

  12. CrossTalk: The Journal of Defense Software Engineering. Volume 20, Number 2

    National Research Council Canada - National Science Library

    Phillips, Mike; Craig, Rushby; Jackelen, George; Humphrey, Watts S; Konrad, Michael D; Over, James W; Pries-Heje, Jan; Johansen, Joern; Christiansen, Mads; Korsaa, Morten; Laporte, Claude Y; April, Alain; Renault, Alain

    2007-01-01

    ...: This article describes how the 309th Software Maintenance Group used Standard Capability Maturity Model Integration Appraisal Method for Process Improvement B to identify opportunities for additional...

  13. Server-based enterprise collaboration software improves safety and quality in high-volume PET/CT practice.

    Science.gov (United States)

    McDonald, James E; Kessler, Marcus M; Hightower, Jeremy L; Henry, Susan D; Deloney, Linda A

    2013-12-01

    With increasing volumes of complex imaging cases and rising economic pressure on physician staffing, timely reporting will become progressively challenging. Current and planned iterations of PACS and electronic medical record systems do not offer workflow management tools to coordinate delivery of imaging interpretations with the needs of the patient and ordering physician. The adoption of a server-based enterprise collaboration software system by our Division of Nuclear Medicine has significantly improved our efficiency and quality of service.

  14. Crosstalk: The Journal of Defense Software Engineering. Volume 22, Number 4

    Science.gov (United States)

    2009-06-01

    networks, fuzzy logic, user interface design, software engineering, UML, sup- ply chain control, and customer relations management. Lipkin has a...quality; this provides a perfect incubator for substandard software. Professional engineers are taught to sacrifice non-essen- tial system capabilities

  15. CrossTalk. The Journal of Defense Software Engineering. Volume 25, Number 2

    Science.gov (United States)

    2012-04-01

    Visit us at: http://www.309SMXG.hill.af.mil Electrical Engineers and Computer Scientists Be on the Cutting Edge of Software Development Sajay Rai is the...has created and fostered not only a market niche but moreover an extension into a worldwide set of devices— engen - dering other software and hardware

  16. CrossTalk: The Journal of Defense Software Engineering. Volume 20, Number 3, March 2007

    National Research Council Canada - National Science Library

    2007-01-01

    .... Given that, why do we still have difficulty ensuring the integrity of software that is so key to protecting the infrastructure from threats and vulnerabilities, reducing overall risk to cyber attack...

  17. CrossTalk: The Journal of Defense Software Engineering. Volume 19, Number 6

    National Research Council Canada - National Science Library

    Jones, Capers; Jost, Alan C; Perkins, Timothy K; Fleming, Quentin W; Koppelman, Joel M; Lipke, Walt; Olson, Timothy G; Kimmerly, Paul

    2006-01-01

    "Social and Technical Reasons for Software Project Failures," by Capers Jones -- Applying a careful program of risk analysis and risk abatement can lower the effects of the technical and social issues...

  18. CrossTalk: The Journal of Defense Software Engineering. Volume 21, Number 3

    National Research Council Canada - National Science Library

    Crosby, Linda L; Schwalb, Jeff; Coe, David J; Gottesdiener, Ellen; Herrmannsdoerfer, Markus; Konrad, Sascha; Berenbach, Brian; Schmidt, Douglas C; Corsaro, Angelo; Van't Hag, Hans

    2008-01-01

    ...) Good Practices for Developing User Requirements by Ellen Gottesdiener: This article provides a requirements model road map that helps software development teams understand the effective use of requirements models. 4...

  19. CrossTalk: The Journal of Defense Software Engineering. Volume 20, Number 10, October 2007

    National Research Council Canada - National Science Library

    2007-01-01

    As the Department of Defense (DoD) moves into more complex systems of systems and family of systems with the accompanying challenges of architectures and product lines, software will further dominate development and deployment...

  20. Guidelines for the Patrol Commander. Criminal Justice Research. Prevention and Control of Collective Violence, Volume IV.

    Science.gov (United States)

    Callahan, W. Thomas; Knoblauch, Richard L.

    The objective of this study is to provide local law enforcement agencies with guidelines for the collection and dissemination of elements of information required for sound decision making in response to the threat or actual initiation of collective violence. Informal, semi-structured interviews in fourteen selected cities and six State police…

  1. Guidelines for Community Relations Personnel. Criminal Justice Research. Prevention and Control of Collective Violence, Volume II.

    Science.gov (United States)

    Callahan, W. Thomas; Knoblauch, Richard L.

    The objective of this study is to provide local law enforcement agencies with guidelines for the collection and dissemination of elements of information required for sound decision making in response to the threat or actual initiation of collective violence. Informal, semi-structured interviews in fourteen selected cities and six State police…

  2. Guidelines for Intelligence Personnel. Criminal Justice Research. Prevention and Control of Collective Violence, Volume III.

    Science.gov (United States)

    Callahan, W. Thomas; Knoblauch, Richard L.

    The objective of this study is to provide local law enforcement agencies with guidelines for the collection and dissemination of elements of information required for sound decision making in response to the threat or actual initiation of collective violence. Informal, semi-structured interviews in fourteen selected cities and six State police…

  3. Guidelines for Patrol Personnel. Criminal Justice Research. Prevention and Control of Collective Violence, Volume V.

    Science.gov (United States)

    Callahan, W. Thomas; Knoblauch, Richard L.

    The objective of this study is to provide local law enforcement agencies with guidelines for the collection and dissemination of elements of information required for sound decision making in response to the threat or actual initiation of collective violence. Informal, semi-structured interviews in fourteen selected cities and six State police…

  4. VOFTools - A software package of calculation tools for volume of fluid methods using general convex grids

    Science.gov (United States)

    López, J.; Hernández, J.; Gómez, P.; Faura, F.

    2018-02-01

    The VOFTools library includes efficient analytical and geometrical routines for (1) area/volume computation, (2) truncation operations that typically arise in VOF (volume of fluid) methods, (3) area/volume conservation enforcement (VCE) in PLIC (piecewise linear interface calculation) reconstruction and(4) computation of the distance from a given point to the reconstructed interface. The computation of a polyhedron volume uses an efficient formula based on a quadrilateral decomposition and a 2D projection of each polyhedron face. The analytical VCE method is based on coupling an interpolation procedure to bracket the solution with an improved final calculation step based on the above volume computation formula. Although the library was originally created to help develop highly accurate advection and reconstruction schemes in the context of VOF methods, it may have more general applications. To assess the performance of the supplied routines, different tests, which are provided in FORTRAN and C, were implemented for several 2D and 3D geometries.

  5. Formal Methods Specification and Verification Guidebook for Software and Computer Systems. Volume 1; Planning and Technology Insertion

    Science.gov (United States)

    1995-01-01

    The Formal Methods Specification and Verification Guidebook for Software and Computer Systems describes a set of techniques called Formal Methods (FM), and outlines their use in the specification and verification of computer systems and software. Development of increasingly complex systems has created a need for improved specification and verification techniques. NASA's Safety and Mission Quality Office has supported the investigation of techniques such as FM, which are now an accepted method for enhancing the quality of aerospace applications. The guidebook provides information for managers and practitioners who are interested in integrating FM into an existing systems development process. Information includes technical and administrative considerations that must be addressed when establishing the use of FM on a specific project. The guidebook is intended to aid decision makers in the successful application of FM to the development of high-quality systems at reasonable cost. This is the first volume of a planned two-volume set. The current volume focuses on administrative and planning considerations for the successful application of FM.

  6. Guidelines for selecting codes for ground-water transport modeling of low-level waste burial sites. Volume 2. Special test cases

    International Nuclear Information System (INIS)

    Simmons, C.S.; Cole, C.R.

    1985-08-01

    This document was written for the National Low-Level Waste Management Program to provide guidance for managers and site operators who need to select ground-water transport codes for assessing shallow-land burial site performance. The guidance given in this report also serves the needs of applications-oriented users who work under the direction of a manager or site operator. The guidelines are published in two volumes designed to support the needs of users having different technical backgrounds. An executive summary, published separately, gives managers and site operators an overview of the main guideline report. Volume 1, titled ''Guideline Approach,'' consists of Chapters 1 through 5 and a glossary. Chapters 2 through 5 provide the more detailed discussions about the code selection approach. This volume, Volume 2, consists of four appendices reporting on the technical evaluation test cases designed to help verify the accuracy of ground-water transport codes. 20 refs

  7. CrossTalk: The Journal of Defense Software Engineering. Volume 20, Number 1

    Science.gov (United States)

    2007-01-01

    software merely reads the amount of pedal depression and converts it to a value that is appropriate for the motor controller. (Changing the vehicle...January 2007 www.stsc.hill.af.mil 31 Iam a process-oriented guy. While I am on the safe side ofObsessive-Compulsive Disorder Guy, I’m not too far off. I

  8. CrossTalk: The Journal of Defense Software Engineering. Volume 19, Number 11

    Science.gov (United States)

    2006-11-01

    Maintenance. New York: McGraw Hill, 1994. 10. Wade, Stu and Andy Laws. Legacy System Management via the Triage Model, Software Triage. Liverpool , UK...shiminc.com Notes 1. Confucius, a Chinese philosopher and reformer (551-479 B.C.). 2. Bowl Championship Series, a system that selects the college football

  9. Achieving Better Buying Power through Acquisition of Open Architecture Software Systems: Volume 1

    Science.gov (United States)

    2016-01-06

    Bergey , J., & Jones, L. (2010). Exploring acquisition strategies for adopting a software product line approach. Proc. 7th Acquisition Research Symposium...education/13/2/ozone-widget- framework , accessed 8 June 2013. Also see, Ozone Widget Framework, https://www.owfgoss.org/ [JoB11] Jones, L. and Bergey

  10. CrossTalk. The Journal of Defense Software Engineering. Volume 26, Number 1

    Science.gov (United States)

    2013-02-01

    Quality management systems – Fundamentals and vocabulary. ISO , Geneva Switzerland, 2000. 26. ISO 9001 :2000, Quality management systems – Requirements...NUMBER(S) 12. DISTRIBUTION /AVAILABILITY STATEMENT Approved for public release; distribution unlimited 13. SUPPLEMENTARY NOTES 14. ABSTRACT 15...in the National Protection and Program Directorate. The USAF Software Technology Support Center (STSC) is the publisher of CrossTalk providing both

  11. Communications received from certain Member States regarding guidelines for transfers of nuclear-related dual-use equipment, materials, software and related technology

    International Nuclear Information System (INIS)

    2005-01-01

    The Director General of the International Atomic Energy Agency has received Notes Verbales dated 25 October 2004 from the Resident Representatives to the Agency of Argentina, Australia, Austria, Belgium, Brazil, Canada, Cyprus, Czech Republic, Estonia, Finland, France, Greece, Hungary, Italy, Japan, Malta, Netherlands, Norway, Republic of Korea, South Africa, Spain, Sweden, Turkey, Ukraine, the United Kingdom of Great Britain and Northern Ireland and the United States of America, relating to transfers of nuclear-related dual-use equipment, materials, software and related technology. The purpose of the Notes Verbales is to provide further information on those Governments' guidelines for transfers of nuclear-related dual-use equipment, materials, software and related technology. In the light of the wish expressed at the end of each Note Verbale, the text of the Notes Verbales is attached. The attachment to these Notes Verbales is also reproduced in full

  12. Communications received from certain Member States regarding guidelines for transfers of nuclear-related dual-use equipment, materials, software and related technology

    International Nuclear Information System (INIS)

    2003-01-01

    The Director General of the International Atomic Energy Agency has received Notes Verbales dated 28 February 2003 from the Resident Representatives to the Agency of Argentina, Austria, Belgium, Bulgaria, Canada, Cyprus, Czech Republic, Denmark, Finland, France, Germany, Greece, Hungary, Italy, Japan, Kazakhstan, Latvia, Netherlands, Norway, Portugal, Republic of Korea, Slovakia, Slovenia, South Africa, Spain, Sweden, Switzerland, Turkey, Ukraine, the United Kingdom of Great Britain and Northern Ireland, and the United States of America, relating to transfers of nuclear-related dual-use equipment, materials, software and related technology. The purpose of the Note Verbales is to provide further information on those Governments' Guidelines for Transfers of Nuclear-related Dual-use Equipment, Materials, Software and Related Technology. In the light of the wish expressed at the end of each Note Verbale, the text of the Notes Verbales is attached. The attachment to these Notes Verbales is also reproduced in full

  13. Practical guidelines for small-volume additions of uninhibited water to waste storage tanks

    International Nuclear Information System (INIS)

    Hsu, T.C.; Wiersma, B.J.; Zapp, P.E.; Pike, J.A.

    1994-01-01

    Allowable volumes of uninhibited water additions to waste tanks are limited to volumes in which hydroxide and nitrite inhibitors reach required concentrations by diffusion from the bulk waste within five days. This diffusion process was modeled conservatively by Fick's second law of diffusion. The solution to the model was applied to all applicable conditions which exist in the waste tanks. Plant engineers adapted and incorporated the results into a practical working procedure for controlling and monitoring the addition of uninhibited water. Research, technical support, and field engineers worked together to produce an effective solution to a potential waste tank corrosion problem

  14. CrossTalk: The Journal of Defense Software Engineering. Volume 20, Number 2

    Science.gov (United States)

    2007-02-01

    Related Risks. Reading, MA: Addison Wesley, 1995. 2. Petroski, Henry . To Engineer Is Human: The Role of Failure in Successful Design. New York: Random...Software 62 (2002): 71-84. 5. Strauss, A., and J. Corbin . Basics of Qualitative Research: Techniques and Procedures for Developing Grounded Theory...and potential solutions to help them apply standards. Alain Renault Public Research Center Henri Tudor Claude Y. Laporte and Alain April École de

  15. Self-Metric Software. Volume III. A Handbook. Part II. Performance Ripple Effect Analysis.

    Science.gov (United States)

    1980-04-01

    available for performing this task is JAVS 171. For each module X, a PDR is then defined from each module in the set of modules directly or indirectly...Requirements," IEEE Trans. 6n Software Engineering, Vol. SE-3, January 1977, pp. 60-69. [71 Gannon, C., Brooks, N. B. and Urban, R. J., " JAVS Technical Report, User’s Guide," RADC-TR-77-126, Vol. I, 1977. 39 N, DAT FILMEI ITI

  16. CrossTalk: The Journal of Defense Software Engineering. Volume 19, Number 6

    Science.gov (United States)

    2006-06-01

    telephones, cell phones, walkie-talkies, blueberries , blackberries, e-mail, v-mail, fax, eRooms, Docushare, meeting rooms, Sametime (Lotus instant messaging...principle (120), i.e., just a lapse of memory in what needed to be done, then gentle reminders from subordinates, peers, or supervisors can be a catalyst to...your memory at one time? For most people, I sus- pect this number peaks out around nine or 10. Unfortunately, large-scale software has millions of

  17. Cost Reporting Elements and Activity Cost Tradeoffs for Defense System Software. Volume I. Study Results.

    Science.gov (United States)

    1977-05-01

    software . Specifically , only the final delivered sizes of programa were reported ; how much of the programs was new in each release was unknown... programaing lang- uage. It was eiptimated22 that the impact of constrained hardware resources V is approximated by: Adjusted Coding Labor — (__ o.7 X Coding...LABOR HOURS (Resource Element Definitions Table 8.6) Resource Elements Interim PBC CPC LEVEL Design 42lxxB/ abc Coding 42lxxC/ abc Integration 42lxxD

  18. Portable microcomputer for the analysis of plutonium gamma-ray spectra. Volume II. Software description and listings

    International Nuclear Information System (INIS)

    Ruhter, W.D.

    1984-05-01

    A portable microcomputer has been developed and programmed for the International Atomic Energy Agency (IAEA) to perform in-field analysis of plutonium gamma-ray spectra. The unit includes a 16-bit LSI-11/2 microprocessor, 32-K words of memory, a 20-character display for user prompting, a numeric keyboard for user responses, and a 20-character thermal printer for hard-copy output of results. The unit weights 11 kg and has dimensions of 33.5 x 30.5 x 23.0 cm. This compactness allows the unit to be stored under an airline seat. Only the positions of the 148-keV 241 Pu and 208-keV 237 U peaks are required for spectral analysis that gives plutonium isotopic ratios and weight percent abundances. Volume I of this report provides a detailed description of the data analysis methodology, operation instructions, hardware, and maintenance and troubleshooting. Volume II describes the software and provides software listings

  19. GENII: The Hanford Environmental Radiation Dosimetry Software System: Volume 1, Conceptual representation

    Energy Technology Data Exchange (ETDEWEB)

    Napier, B.A.; Peloquin, R.A.; Strenge, D.L.; Ramsdell, J.V.

    1988-12-01

    The Hanford Environmental Dosimetry Upgrade Project was undertaken to incorporate the internal dosimetry models recommended by the International Commission on Radiological Protection (ICRP) in updated versions of the environmental pathway analysis models used at Hanford. The resulting second generation of Hanford environmental dosimetry computer codes is compiled in the Hanford Environmental Dosimetry System (Generation II, or GENII). The purpose of this coupled system of computer codes is to analyze environmental contamination resulting from acute or chronic releases to, or initial contamination of, air, water, or soil. This is accomplished by calculating radiation doses to individuals or populations. GENII is described in three volumes of documentation. The first volume describes the theoretical considerations of the system. The second volume is a Users' Manual, providing code structure, users' instructions, required system configurations, and QA-related topics. The third volume is a Code Maintenance Manual for the user who requires knowledge of code detail. It includes code logic diagrams, global dictionary, worksheets, example hand calculations, and listings of the code and its associated data libraries. 72 refs., 15 figs., 34 tabs.

  20. GENII: The Hanford Environmental Radiation Dosimetry Software System: Volume 1, Conceptual representation

    International Nuclear Information System (INIS)

    Napier, B.A.; Peloquin, R.A.; Strenge, D.L.; Ramsdell, J.V.

    1988-12-01

    The Hanford Environmental Dosimetry Upgrade Project was undertaken to incorporate the internal dosimetry models recommended by the International Commission on Radiological Protection (ICRP) in updated versions of the environmental pathway analysis models used at Hanford. The resulting second generation of Hanford environmental dosimetry computer codes is compiled in the Hanford Environmental Dosimetry System (Generation II, or GENII). The purpose of this coupled system of computer codes is to analyze environmental contamination resulting from acute or chronic releases to, or initial contamination of, air, water, or soil. This is accomplished by calculating radiation doses to individuals or populations. GENII is described in three volumes of documentation. The first volume describes the theoretical considerations of the system. The second volume is a Users' Manual, providing code structure, users' instructions, required system configurations, and QA-related topics. The third volume is a Code Maintenance Manual for the user who requires knowledge of code detail. It includes code logic diagrams, global dictionary, worksheets, example hand calculations, and listings of the code and its associated data libraries. 72 refs., 15 figs., 34 tabs

  1. Composite Materials Handbook. Volume 1. Polymer Matrix Composites Guidelines for Characterization of Structural Materials

    Science.gov (United States)

    2002-06-17

    Volume 1, Section 8.1.4. Fabric, Nonwoven -- A textile structure produced by bonding or interlocking of fibers, or both, ac- complished by...261) Dry Cleaning Solvent (Type 2) P-D-680 Hydrocarbon Washing Liquid TT-S-735 Polypropylene Glycol Deicer (Type 1) MIL-A-8243 Isopropyl Alcohol...mixer and immediately filter about 4 mL of the resin sample solution through a 0.2 µm Teflon™ membrane filter into a dry, clean glass vial. Immediately

  2. Qualifying codes under software quality assurance: Two examples as guidelines for codes that are existing or under development

    Energy Technology Data Exchange (ETDEWEB)

    Mangold, D.

    1993-05-01

    Software quality assurance is an area of concem for DOE, EPA, and other agencies due to the poor quality of software and its documentation they have received in the past. This report briefly summarizes the software development concepts and terminology increasingly employed by these agencies and provides a workable approach to scientific programming under the new requirements. Following this is a practical description of how to qualify a simulation code, based on a software QA plan that has been reviewed and officially accepted by DOE/OCRWM. Two codes have recently been baselined and qualified, so that they can be officially used for QA Level 1 work under the DOE/OCRWM QA requirements. One of them was baselined and qualified within one week. The first of the codes was the multi-phase multi-component flow code TOUGH version 1, an already existing code, and the other was a geochemistry transport code STATEQ that was under development The way to accomplish qualification for both types of codes is summarized in an easy-to-follow step-by step fashion to illustrate how to baseline and qualify such codes through a relatively painless procedure.

  3. The GLAS Science Algorithm Software (GSAS) Detailed Design Document Version 6. Volume 16

    Science.gov (United States)

    Lee, Jeffrey E.

    2013-01-01

    The Geoscience Laser Altimeter System (GLAS) is the primary instrument for the ICESat (Ice, Cloud and Land Elevation Satellite) laser altimetry mission. ICESat was the benchmark Earth Observing System (EOS) mission for measuring ice sheet mass balance, cloud and aerosol heights, as well as land topography and vegetation characteristics. From 2003 to 2009, the ICESat mission provided multi-year elevation data needed to determine ice sheet mass balance as well as cloud property information, especially for stratospheric clouds common over polar areas. It also provided topography and vegetation data around the globe, in addition to the polar-specific coverage over the Greenland and Antarctic ice sheets.This document describes the detailed design of GLAS Science Algorithm Software (GSAS). The GSAS is used to create the ICESat GLAS standard data products. The National Snow and Ice Data Center (NSDIC) distribute these products. The document contains descriptions, flow charts, data flow diagrams, and structure charts for each major component of the GSAS. The purpose of this document is to present the detailed design of the GSAS. It is intended as a reference source to assist the maintenance programmer in making changes that fix or enhance the documented software.

  4. The Environment for Application Software Integration and Execution (EASIE), version 1.0. Volume 2: Program integration guide

    Science.gov (United States)

    Jones, Kennie H.; Randall, Donald P.; Stallcup, Scott S.; Rowell, Lawrence F.

    1988-01-01

    The Environment for Application Software Integration and Execution, EASIE, provides a methodology and a set of software utility programs to ease the task of coordinating engineering design and analysis codes. EASIE was designed to meet the needs of conceptual design engineers that face the task of integrating many stand-alone engineering analysis programs. Using EASIE, programs are integrated through a relational data base management system. In volume 2, the use of a SYSTEM LIBRARY PROCESSOR is used to construct a DATA DICTIONARY describing all relations defined in the data base, and a TEMPLATE LIBRARY. A TEMPLATE is a description of all subsets of relations (including conditional selection criteria and sorting specifications) to be accessed as input or output for a given application. Together, these form the SYSTEM LIBRARY which is used to automatically produce the data base schema, FORTRAN subroutines to retrieve/store data from/to the data base, and instructions to a generic REVIEWER program providing review/modification of data for a given template. Automation of these functions eliminates much of the tedious, error prone work required by the usual approach to data base integration.

  5. Joint Logistics Commanders’ Workshop on Post Deployment Software Support (PDSS) for Mission-Critical Computer Software. Volume 2. Workshop Proceedings.

    Science.gov (United States)

    1984-06-01

    tremendous positive effect on the entire software life cycle. Its goal is to reduce the labor -intensiveness of the software process and thereby reduce...implementation. PDSS is, and will continue in the near future to bp, a labor -intensive activity. The availaoility of that qualified labor force is a determining...fit into the software life cycle? At what specific points is it employed? What is the relationship of IV&V to test, integracion , QA, system

  6. Early Site Permit Demonstration Program: Guidelines for determining design basis ground motions. Volume 2, Appendices

    Energy Technology Data Exchange (ETDEWEB)

    1993-03-18

    This report develops and applies a methodology for estimating strong earthquake ground motion. The motivation was to develop a much needed tool for use in developing the seismic requirements for structural designs. An earthquake`s ground motion is a function of the earthquake`s magnitude, and the physical properties of the earth through which the seismic waves travel from the earthquake fault to the site of interest. The emphasis of this study is on ground motion estimation in Eastern North America (east of the Rocky Mountains), with particular emphasis on the Eastern United States and southeastern Canada. Eastern North America is a stable continental region, having sparse earthquake activity with rare occurrences of large earthquakes. While large earthquakes are of interest for assessing seismic hazard, little data exists from the region to empirically quantify their effects. The focus of the report is on the attributes of ground motion in Eastern North America that are of interest for the design of facilities such as nuclear power plants. This document, Volume II, contains Appendices 2, 3, 5, 6, and 7 covering the following topics: Eastern North American Empirical Ground Motion Data; Examination of Variance of Seismographic Network Data; Soil Amplification and Vertical-to-Horizontal Ratios from Analysis of Strong Motion Data From Active Tectonic Regions; Revision and Calibration of Ou and Herrmann Method; Generalized Ray Procedure for Modeling Ground Motion Attenuation; Crustal Models for Velocity Regionalization; Depth Distribution Models; Development of Generic Site Effects Model; Validation and Comparison of One-Dimensional Site Response Methodologies; Plots of Amplification Factors; Assessment of Coupling Between Vertical & Horizontal Motions in Nonlinear Site Response Analysis; and Modeling of Dynamic Soil Properties.

  7. A consensus-based guideline defining clinical target volume for primary disease in external beam radiotherapy for intact uterine cervical cancer

    International Nuclear Information System (INIS)

    Toita, Takafumi; Ohno, Tatsuya; Kaneyasu, Yuko

    2011-01-01

    The objective of this study was to develop a consensus-based guideline to define clinical target volume for primary disease (clinical target volume primary) in external beam radiotherapy for intact uterine cervical cancer. The working subgroup of the Japan Clinical Oncology Group (JCOG) Radiation Therapy Study Group began developing a guideline for primary clinical target volume in November 2009. The group consisted of 10 radiation oncologists and 2 gynecologic oncologists. The process started with comparing the contouring on computed tomographic images of actual cervical cancer cases among the members. This was followed by a comprehensive literature review that included primary research articles and textbooks as well as information on surgical procedures. Extensive discussion occurred in face-to-face meetings (three occasions) and frequent e-mail communications until a consensus was reached. The working subgroup reached a consensus on the definition for the clinical target volume primary. The clinical target volume primary consists of the gross tumor volume, uterine cervix, uterine corpus, parametrium, vagina and ovaries. Definitions for these component structures were determined. Anatomical boundaries in all directions were defined for the parametrium. Examples delineating these boundaries were prepared for the posterior border of the parametrium for various clinical situations (id est (i.e.) central tumor bulk, degree of parametrial involvement). A consensus-based guideline defining the clinical target volume primary was developed for external beam radiotherapy for intact uterine cervical cancer. This guideline will serve as a template for radiotherapy protocols in future clinical trials. It may also be used in actual clinical practice in the setting of highly precise external beam radiotherapy, including intensity-modulated radiotherapy. (author)

  8. Storage management in Ada. Three reports. Volume 1: Storage management in Ada as a risk to the development of reliable software. Volume 2: Relevant aspects of language. Volume 3: Requirements of the language versus manifestations of current implementations

    Science.gov (United States)

    Auty, David

    1988-01-01

    The risk to the development of program reliability is derived from the use of a new language and from the potential use of new storage management techniques. With Ada and associated support software, there is a lack of established guidelines and procedures, drawn from experience and common usage, which assume reliable behavior. The risk is identified and clarified. In order to provide a framework for future consideration of dynamic storage management on Ada, a description of the relevant aspects of the language is presented in two sections: Program data sources, and declaration and allocation in Ada. Storage-management characteristics of the Ada language and storage-management characteristics of Ada implementations are differentiated. Terms that are used are defined in a narrow and precise sense. The storage-management implications of the Ada language are described. The storage-management options available to the Ada implementor and the implications of the implementor's choice for the Ada programmer are also described.

  9. EORTC-ROG expert opinion: radiotherapy volume and treatment guidelines for neoadjuvant radiation of adenocarcinomas of the gastroesophageal junction and the stomach.

    Science.gov (United States)

    Matzinger, Oscar; Gerber, Erich; Bernstein, Zvi; Maingon, Philippe; Haustermans, Karin; Bosset, Jean François; Gulyban, Akos; Poortmans, Philip; Collette, Laurence; Kuten, Abraham

    2009-08-01

    The Gastro-Intestinal Working Party of the EORTC Radiation Oncology Group (GIWP-ROG) developed guidelines for target volume definition in neoadjuvant radiation of adenocarcinomas of the gastroesophageal junction (GEJ) and the stomach. Guidelines about the definition of the clinical target volume (CTV) are based on a systematic literature review of the location and frequency of local recurrences and lymph node involvement in adenocarcinomas of the GEJ and the stomach. Therefore, MEDLINE was searched up to August 2008. Guidelines concerning prescription, planning and treatment delivery are based on a consensus between the members of the GIWP-ROG. In order to support a curative resection of GEJ and gastric cancer, an individualized preoperative treatment volume based on tumour location has to include the primary tumour and the draining regional lymph nodes area. Therefore we recommend to use the 2nd English Edition of the Japanese Classification of Gastric Carcinoma of the Japanese Gastric Cancer Association which developed the concept of assigning tumours of the GEJ and the stomach to anatomically defined sub-sites corresponding respectively to a distinct lymphatic spread pattern. The GIWP-ROG defined guidelines for preoperative irradiation of adenocarcinomas of the GEJ and the stomach to reduce variability in the framework of future clinical trials.

  10. A consensus-based guideline defining the clinical target volume for pelvic lymph nodes in external beam radiotherapy for uterine cervical cancer

    International Nuclear Information System (INIS)

    Toita, Takafumi; Ohno, Tatsuya; Kaneyasu, Yuko

    2010-01-01

    The objective of this study was to develop a consensus-based guideline as well as an atlas defining pelvic nodal clinical target volumes in external beam radiotherapy for uterine cervical cancer. A working subgroup to establish the consensus-based guideline on clinical target volumes for uterine cervical cancer was formulated by the Radiation Therapy Study Group of the Japan Clinical Oncology Group in July 2008. The working subgroup consisted of seven radiation oncologists. The process resulting in the consensus included a comparison of contouring on CT images among the members, reviewing of published textbooks and the relevant literature and a distribution analysis of metastatic nodes on computed tomography/magnetic resonance imaging of actual patients. The working subgroup defined the pelvic nodal clinical target volumes for cervical cancer and developed an associated atlas. As a basic criterion, the lymph node clinical target volume was defined as the area encompassed by a 7 mm margin around the applicable pelvic vessels. Modifications were made in each nodal area to cover adjacent adipose tissues at risk of microscopic nodal metastases. Although the bones and muscles were excluded, the bowel was not routinely excluded in the definition. Each of the following pelvic node regions was defined: common iliac, external iliac, internal iliac, obturator and presacral. Anatomical structures bordering each lymph node region were defined for six directions; anterior, posterior, lateral, medial, cranial and caudal. Drafts of the definition and the atlas were reviewed by members of the JCOG Gynecologic Cancer Study Group (GCSG). We developed a consensus-based guideline defining the pelvic node clinical target volumes that included an atlas. The guideline will be continuously updated to reflect the ongoing changes in the field. (author)

  11. Interim report on the development and application of environmental mapped data digitization, encoding, analysis, and display software for the ALICE system. Volume II. [MAP, CHAIN, FIX, and DOUT, in FORTRAN IV for PDP-10

    Energy Technology Data Exchange (ETDEWEB)

    Amiot, L.W.; Lima, R.J.; Scholbrock, S.D.; Shelman, C.B.; Wehman, R.H.

    1979-06-01

    Volume I of An Interim Report on the Development and Application of Environmental Mapped Data Digitization, Encoding, Analysis, and Display Software for the ALICE System provided an overall description of the software developed for the ALICE System and presented an example of its application. The scope of the information presented in Volume I was directed both to the users and developers of digitization, encoding, analysis, and display software. Volume II presents information which is directly related to the actual computer code and operational characteristics (keys and subroutines) of the software. Volume II will be of more interest to developers of software than to users of the software. However, developers of software should be aware that the code developed for the ALICE System operates in an environment where much of the peripheral hardware to the PDP-10 is ANL/AMD built. For this reason, portions of the code may have to be modified for implementation on other computer system configurations. 11 tables.

  12. Consensus Guidelines for Delineation of Clinical Target Volume for Intensity-Modulated Pelvic Radiotherapy for the Definitive Treatment of Cervix Cancer

    International Nuclear Information System (INIS)

    Lim, Karen; Small, William; Portelance, Lorraine; Creutzberg, Carien; Juergenliemk-Schulz, Ina M.; Mundt, Arno; Mell, Loren K.; Mayr, Nina; Viswanathan, Akila; Jhingran, Anuja; Erickson, Beth; De Los Santos, Jennifer; Gaffney, David; Yashar, Catheryn; Beriwal, Sushil; Wolfson, Aaron

    2011-01-01

    Purpose: Accurate target definition is vitally important for definitive treatment of cervix cancer with intensity-modulated radiotherapy (IMRT), yet a definition of clinical target volume (CTV) remains variable within the literature. The aim of this study was to develop a consensus CTV definition in preparation for a Phase 2 clinical trial being planned by the Radiation Therapy Oncology Group. Methods and Materials: A guidelines consensus working group meeting was convened in June 2008 for the purposes of developing target definition guidelines for IMRT for the intact cervix. A draft document of recommendations for CTV definition was created and used to aid in contouring a clinical case. The clinical case was then analyzed for consistency and clarity of target delineation using an expectation maximization algorithm for simultaneous truth and performance level estimation (STAPLE), with kappa statistics as a measure of agreement between participants. Results: Nineteen experts in gynecological radiation oncology generated contours on axial magnetic resonance images of the pelvis. Substantial STAPLE agreement sensitivity and specificity values were seen for gross tumor volume (GTV) delineation (0.84 and 0.96, respectively) with a kappa statistic of 0.68 (p < 0.0001). Agreement for delineation of cervix, uterus, vagina, and parametria was moderate. Conclusions: This report provides guidelines for CTV definition in the definitive cervix cancer setting for the purposes of IMRT, building on previously published guidelines for IMRT in the postoperative setting.

  13. Guidelines for target volume definition in post-operative radiotherapy for prostate cancer, on behalf of the EORTC Radiation Oncology Group

    International Nuclear Information System (INIS)

    Poortmans, Philip; Bossi, Alberto; Vandeputte, Katia; Bosset, Mathieu; Miralbell, Raymond; Maingon, Philippe; Boehmer, Dirk; Budiharto, Tom; Symon, Zvi; Bergh, Alfons C.M. van den; Scrase, Christopher; Poppel, Hendrik van; Bolla, Michel

    2007-01-01

    The appropriate application of 3-D conformal radiotherapy, intensity modulated radiotherapy or image guided radiotherapy for patients undergoing post-operative radiotherapy for prostate cancer requires a standardisation of the target volume definition and delineation as well as standardisation of the clinical quality assurance procedures. Recommendations for this are presented on behalf of the European Organisation for Research and Treatment of Cancer (EORTC) Radiation Oncology Group and in addition to the already published guidelines for radiotherapy as the primary treatment

  14. Software Maintainability Evaluator Guidelines Handbook.

    Science.gov (United States)

    1978-11-24

    chart (or equivalent) for each module which dia- gramatically illustrates the inputs, general processing, and out- puts for the module. 111-4 THE BDM...Clarification terminology: the general use of English and program terms should be simple, straightforward, easily understood; any terms needing to be

  15. Influence of Software Tool and Methodological Aspects of Total Metabolic Tumor Volume Calculation on Baseline [18F]FDG PET to Predict Survival in Hodgkin Lymphoma.

    Science.gov (United States)

    Kanoun, Salim; Tal, Ilan; Berriolo-Riedinger, Alina; Rossi, Cédric; Riedinger, Jean-Marc; Vrigneaud, Jean-Marc; Legrand, Louis; Humbert, Olivier; Casasnovas, Olivier; Brunotte, François; Cochet, Alexandre

    2015-01-01

    To investigate the respective influence of software tool and total metabolic tumor volume (TMTV0) calculation method on prognostic stratification of baseline 2-deoxy-2-[18F]fluoro-D-glucose positron emission tomography ([18F]FDG-PET) in newly diagnosed Hodgkin lymphoma (HL). 59 patients with newly diagnosed HL were retrospectively included. [18F]FDG-PET was performed before any treatment. Four sets of TMTV0 were calculated with Beth Israel (BI) software: based on an absolute threshold selecting voxel with standardized uptake value (SUV) >2.5 (TMTV02.5), applying a per-lesion threshold of 41% of the SUV max (TMTV041) and using a per-patient adapted threshold based on SUV max of the liver (>125% and >140% of SUV max of the liver background; TMTV0125 and TMTV0140). TMTV041 was also determined with commercial software for comparison of software tools. ROC curves were used to determine the optimal threshold for each TMTV0 to predict treatment failure. Median follow-up was 39 months. There was an excellent correlation between TMTV041 determined with BI and with the commercial software (r = 0.96, pfree survival (PFS) were respectively: 313 ml and 0.70, 432 ml and 0.68, 450 ml and 0.68, 330 ml and 0.68. There was no significant difference between ROC curves. High TMTV0 value was predictive of poor PFS in all methodologies: 4-years PFS was 83% vs 42% (p = 0.006) for TMTV02.5, 83% vs 41% (p = 0.003) for TMTV041, 85% vs 40% (p<0.001) for TMTV0125 and 83% vs 42% (p = 0.004) for TMTV0140. In newly diagnosed HL, baseline metabolic tumor volume values were significantly influenced by the choice of the method used for determination of volume. However, no significant differences were found in term of prognosis.

  16. CrossTalk. The Journal of Defense Software Engineering. Volume 27, Number 2. March/April 2014

    Science.gov (United States)

    2014-04-01

    Trust Trustworthy Software Engineering (TSE) Acquisition Trust Technical Debt ( TD ) Acquisition, Operations Trust, Austerity Software Project Management...I had pulled over near the Angelina River, a small and muddy river on the way to work. While I eventually was able to rub off most of the sticky

  17. CrossTalk, The Journal of Defense Software Engineering. Volume 26, Number 2. March/April 2013

    Science.gov (United States)

    2013-04-01

    to air gripes and general displeasure about software, bureaucracy, and the general process of producing software. There used to be several authors...ran out of things to gripe about. Luckily, the publishers still have me around. I can always find something to complain about—such as change. The

  18. CrossTalk: The Journal of Defense Software Engineering. Volume 24, Number 1, Jan/Feb 2011

    Science.gov (United States)

    2011-02-01

    Engine, Windows Azure , and Force.com. • Data-as-a-Service (DaaS): Frees organizations from buying high-cost database engines and mass storage. This...Microsoft SQL Azure Database. • Software-as-a-Service (SaaS): The ultimate form of cloud resources that delivers software applications to clients in

  19. Guidelines and workbook for assessment of organization and administration of utilities seeking operating license for a nuclear power plant. Guidelines for utility organization and administration plan. Volume 1, Revision 1

    International Nuclear Information System (INIS)

    Thurber, J.A.; Olson, J.; Osborn, R.N.; Sommers, P.; Widrig, R.D.

    1986-09-01

    Volumes 1 and 2 of this report are a partial response to the requirements of Item I.B.1.1 of the ''NRC Action Plan Developed as a Result of the TMI-2 Accident,'' NUREG-0660, and are designed to serve as a basis for replacing the earlier NUREG-0731, ''Guidelines for Utility Management Structure and Technical Resources.'' These Guidelines are intended to provide guidance to the user in preparing a written plan for a proposed nuclear organization and administration. The purpose of the Workbook (Vol. 2) is to guide the NRC reviewer through a systematic review and assessment of a proposed organization and administration. It is the NRC's intention to incorporate these Guidelines and Workbook into a future revision of the Standard Review Plan (SRP), NUREG-0800. However, at this time the report is being published so that the material may be used on a voluntary basis by industry to systematically prepare or evaluate their organization or administration plans. Use of the report by the NRC would not occur until after it has been incorpoarted in the SRP

  20. CrossTalk: The Journal of Defense Software Engineering. Volume 27, Number 5, September/October 2014

    Science.gov (United States)

    2014-10-01

    ACQUISITION OF SOFTWARE-RELIANT CAPABILITIES Abstract. Since the advent of applying Agile [1] practices on DoD projects, specifi- cally Scrum [2] practices...required to use the Waterfall model, a project can implement the Agile project management approach, Scrum , to work within the more traditional...experience in the imple- mentation and deployment of Agile, Lean, and Scrum values and principles in communications-electronics, and software and systems

  1. CrossTalk: The Journal of Defense Software Engineering. Volume 23, Number 1, Jan/Feb 2010

    Science.gov (United States)

    2010-02-01

    ISO /IEC 9126 quality model. It is well-established that the non-functional requirements for software can dramatically increase the work effort and...9100 and ISO 9000. See <www.309SMXG.hill.af.mil> for more information. Joe Jarzombek, Department of Homeland Security (DHS) – Director of Software...emerging option. Organizations may undergo an audit against ISO 20000, commonly known as the IT Service Management Standard. This stan- dard is somewhat

  2. Inter- and Intra-Observer Variability of the Volume of Cervical Ossification of the Posterior Longitudinal Ligament Using Medical Image Processing Software.

    Science.gov (United States)

    Shin, Dong Ah; Ji, Gyu Yeul; Oh, Chang Hyun; Kim, Keung Nyun; Yoon, Do Heum; Shin, Hyunchul

    2017-07-01

    Computed tomography (CT)-based method of three dimensional (3D) analysis (MIMICS ® , Materialise, Leuven, Belgium) is reported as very useful software for evaluation of OPLL, but its reliability and reproducibility are obscure. This study was conducted to evaluate the accuracy of MIMICS ® system, and inter- and intra-observer reliability in the measurement of OPLL. Three neurosurgeons independently analyzed the randomly selected 10 OPLL cases with medical image processing software (MIMICS ® ) which create 3D model with Digital Imaging and Communication in Medicine (DICOM) data from CT images after brief explanation was given to examiners before the image construction steps. To assess the reliability of inter- and intra-examiner intraclass correlation coefficient (ICC), 3 examiners measured 4 parameters (volume, length, width, and length) in 10 cases 2 times with 1-week interval. The inter-examiner ICCs among 3 examiners were 0.996 (95% confidence interval [CI], 0.987-0.999) for volume measurement, 0.973 (95% CI, 0.907-0.978) for thickness, 0.969 (95% CI, 0.895-0.993) for width, and 0.995 (95% CI, 0.983-0.999) for length. The intra-examiner ICCs were 0.994 (range, 0.991-0.996) for volume, 0.996 (range, 0.944-0.998) for length, 0.930 (range, 0.873-0.947) for width, and 0.987 (range, 0.985-0.995) for length. The medical image processing software (MIMICS ® ) provided detailed quantification OPLL volume with minimal error of inter- and intra-observer reliability in the measurement of OPLL.

  3. Guidelines for the Chief of Police. Criminal Justice Research. Prevention and Control of Collective Violence, Volume I.

    Science.gov (United States)

    Callahan, W. Thomas; Knoblauch, Richard L.

    The objective of this study is to provide local law enforcement agencies with guidelines for the collection and dissemination of elements of information required for sound decision making in response to the threat or actual initiation of collective violence. Informal, semi-structured interviews in fourteen selected cities and six State police…

  4. Evaluation of a new software tool for the automatic volume calculation of hepatic tumors. First results; Evaluation eines neuen Softwareassistenten zur automatischen Volumenbestimmung von intrahepatischen Tumoren. Erste Ergebnisse

    Energy Technology Data Exchange (ETDEWEB)

    Meier, S.; Mildenberger, P.; Pitton, M.; Thelen, M. [Klinik und Poliklinik fuer Radiologie, Univ. Mainz (Germany); Schenk, A.; Bourquain, H. [MeVis, Bremen (Germany)

    2004-02-01

    Purpose: computed tomography has become the preferred method in detecting liver carcinomas. The introduction of spiral CT added volumetric assessment of intrahepatic tumors, which was unattainable in the clinical routine with incremental CT due to complex planimetric revisions and excessive computing time. In an ongoing clinical study, a new software tool was tested for the automatic detection of tumor volume and the time needed for this procedure. Materials and methods: we analyzed patients suffering from hepatocellular carcinoma (HCC). All patients underwent treatment with repeated transcatheter chemoembolization of the hepatic arteria. The volumes of the HCC lesions detected in CT were measured with the new software tool in HepaVison (MeVis, Germany). The results were compared with manual planimetric calculation of the volume performed by three independent radiologists. Results: our first results in 16 patients show a correlation between the automatically and the manually calculated volumes (up to a difference of 2 ml) of 96.8%. While the manual method of analyzing the volume of a lesion requires 2.5 minutes on average, the automatic method merely requires about 30 seconds of user interaction time. Conclusion: These preliminary results show a good correlation between automatic and manual calculations of the tumor volume. The new software tool requires less time for accurate determination of the tumor volume and can be applied in the daily clinical routine. (orig.) [German] Ziel: Die Computertomographie hat sich bei der Verlaufskontrolle von Lebertumoren als wichtiges Verfahren etabliert. Mit dem Verfahren ist auch eine Angabe des Tumorvolumens moeglich, welche bisher jedoch aufgrund der aufwendigen planimetrischen Aufarbeitung nicht praktikabel ist. In einer laufenden klinischen Studie wird ein neuer Softwareassistent auf seine automatische Volumenerfassung von Lebertumoren getestet und die notwendige Zeit fuer diesen Vorgang erfasst. Material und Methoden: Es

  5. Communication Received from the Permanent Mission of the Republic of Serbia to the International Atomic Energy Agency Regarding Guidelines for the Export of Nuclear Material, Equipment and Technology and the Guidelines for Transfers of Nuclear-related Dual-use Equipment, Materials, Software and Related Technology

    International Nuclear Information System (INIS)

    2012-01-01

    The Director General has received a note verbale dated 28 September 2012 from the Permanent Mission of Serbia to the International Atomic Energy Agency providing information on the decision of the Government of Serbia to adhere to the 'Guidelines for the Export of Nuclear Material, Equipment and Technology', issued as document INFCIRC/254/Rev.10/Part 1, including its Annexes, and with the 'Guidelines for Transfers of Nuclear-Related Dual-Use Equipment, Material, Software and Related Technology', issued as document INFCIRC/254/Rev.8/Part 2 [es

  6. Communication Received from the PermanentMission of Mexico to the International Atomic Energy Agency Regarding Guidelines for the Export of Nuclear Material, Equipment and Technology and the Guidelines for Transfers of Nuclear-related Dual-use Equipment, Materials, Software and Related Technology

    International Nuclear Information System (INIS)

    2012-01-01

    The Director General has received a note verbale dated 15 June 2012 from the Permanent Mission of Mexico to the International Atomic Energy Agency providing information on the decision of the Government of Mexico to act in accordance with the 'Guidelines for the Export of Nuclear Material, Equipment and Technology', issued as document INFCIRC/254/Rev.10/Part 1, including its Annexes, and with the 'Guidelines for Transfers of Nuclear-Related Dual-Use Equipment, Material, Software and Related Technology', issued as document INFCIRC/254/Rev.8/Part 2

  7. Communication Received from the Permanent Mission of Mexico to the International Atomic Energy Agency Regarding Guidelines for the Export of Nuclear Material, Equipment and Technology and the Guidelines for Transfers of Nuclear-related Dual-use Equipment, Materials, Software and Related Technology

    International Nuclear Information System (INIS)

    2012-01-01

    The Director General has received a note verbale dated 15 June 2012 from the Permanent Mission of Mexico to the International Atomic Energy Agency providing information on the decision of the Government of Mexico to act in accordance with the 'Guidelines for the Export of Nuclear Material, Equipment and Technology', issued as document INFCIRC/254/Rev.10/Part 1, including its Annexes, and with the 'Guidelines for Transfers of Nuclear-Related Dual-Use Equipment, Material, Software and Related Technology', issued as document INFCIRC/254/Rev.8/Part 2

  8. Quantitative assessment of primary mitral regurgitation using left ventricular volumes obtained with new automated three-dimensional transthoracic echocardiographic software: A comparison with 3-Tesla cardiac magnetic resonance.

    Science.gov (United States)

    Levy, Franck; Marechaux, Sylvestre; Iacuzio, Laura; Schouver, Elie Dan; Castel, Anne Laure; Toledano, Manuel; Rusek, Stephane; Dor, Vincent; Tribouilloy, Christophe; Dreyfus, Gilles

    2018-03-30

    Quantitative assessment of primary mitral regurgitation (MR) using left ventricular (LV) volumes obtained with three-dimensional transthoracic echocardiography (3D TTE) recently showed encouraging results. Nevertheless, 3D TTE is not incorporated into everyday practice, as current LV chamber quantification software products are time consuming. To investigate the accuracy and reproducibility of new automated fast 3D TTE software (HeartModel A.I. ; Philips Healthcare, Andover, MA, USA) for the quantification of LV volumes and MR severity in patients with isolated degenerative primary MR; and to compare regurgitant volume (RV) obtained with 3D TTE with a cardiac magnetic resonance (CMR) reference. Fifty-three patients (37 men; mean age 64±12 years) with at least mild primary isolated MR, and having comprehensive 3D TTE and CMR studies within 24h, were eligible for inclusion. MR RV was calculated using the proximal isovelocity surface area (PISA) method and the volumetric method (total LV stroke volume minus aortic stroke volume) with either CMR or 3D TTE. Inter- and intraobserver reproducibility of 3D TTE was excellent (coefficient of variation≤10%) for LV volumes. MR RV was similar using CMR and 3D TTE (57±23mL vs 56±28mL; P=0.22), but was significantly higher using the PISA method (69±30mL; PTTE). The PISA method consistently overestimated MR RV compared with CMR (bias 12±21mL), while no significant bias was found between 3D TTE and CMR (bias 2±14mL). Concordance between echocardiography and CMR was higher using 3D TTE MR grading (intraclass correlation coefficient [ICC]=0.89) than with PISA MR grading (ICC=0.78). Complete agreement with CMR grading was more frequent with 3D TTE than with the PISA method (76% vs 63%). 3D TTE RV assessment using the new generation of automated software correlates well with CMR in patients with isolated degenerative primary MR. Copyright © 2018 Elsevier Masson SAS. All rights reserved.

  9. Photovoltaic system criteria documents. Volume 1: Guidelines for evaluating the management and operations planning of photovoltaic applications

    Science.gov (United States)

    Koenig, John C.; Billitti, Joseph W.; Tallon, John M.

    1979-01-01

    Guidelines are provided to the Field Centers for organization, scheduling, project and cost control, and performance in the areas of project management and operations planning for Photovoltaics Test and Applications. These guidelines may be used in organizing a T and A Project Team for system design/test, site construction and operation, and as the basis for evaluating T and A proposals. The attributes are described for project management and operations planning to be used by the Field Centers. Specifically, all project management and operational issues affecting costs, schedules and performance of photovoltaic systems are addressed. Photovoltaic tests and applications include residential, intermediate load center, central station, and stand-alone systems. The sub-categories of system maturity considered are: Initial System Evaluation Experiments (ISEE); System Readiness Experiments (SRE); and Commercial Readiness Demonstration Projects (CRDP).

  10. Commonality Study of the Pressure-Volume-Temperature Based Propellant Gaging Software Modules for the Auxiliary Power Unit, Reaction Control System, and Orbital Maneuvering System

    Science.gov (United States)

    Duhon, D. D.

    1975-01-01

    Computer storage requirements can be reduced if areas of commonality exist in two or more programs placed in the same computer and identical code can be used by more than one program. The pressure-volume-temperature (P-V-T) relationship for the propellant tank pressurant agent is utilized as the basis for either a primary of a backup propellant gaging program for the auxiliary power unit (APU), the reaction control system (RCS), and the orbital maneuvering system (OMS). These three propellant gaging programs were investigated. It was revealed that a very limited degree of software commonality exits among them. An examination of this common software indicated that only the computation of the helium compressibility factor in an external function subprogram accessible to both the RCS and OMS propellant gaging programs appears to offer a savings in computer storage requirements.

  11. CrossTalk. The Journal of Defense Software Engineering. Volume 25, Number 1, Jan/Feb 2012

    Science.gov (United States)

    2012-01-01

    today’s warfighter. We, who provide those men and women with the systems and software they need to do their job, must be similarly fit, equipped...Taco Bell closes anymore. • Your car insurance goes down instead of up. • You feed your dog Science Diet instead of McDonalds leftovers

  12. CrossTalk: The Journal of Defense Software Engineering. Volume 25, Number 1, January/February 2012

    Science.gov (United States)

    2012-02-01

    men and women with the systems and software they need to do their job, must be similarly fit, equipped, and ready to perform our responsibilities...insurance goes down instead of up. • You feed your dog Science Diet instead of McDonalds leftovers . • Sleeping on the couch makes your back hurt

  13. Software Components for Web Services

    OpenAIRE

    Ramachandran, Muthu; Nair, T. R. Gopalakrsihnan; Selvarani, R.

    2010-01-01

    Service-oriented computing has emerged as the new area to address software as a service. This paper proposes a model for component based development for service-oriented systems and have created best practice guidelines on software component design.

  14. ReViMS: Software tool for estimating the volumes of 3-D multicellular spheroids imaged using a light sheet fluorescence microscope.

    Science.gov (United States)

    Piccinini, Filippo; Tesei, Anna; Zanoni, Michele; Bevilacqua, Alessandro

    2017-11-01

    Cancer 3-D spheroids are widely used to test drugs and radiotherapy treatments. These 3-D cell clusters range from tens to hundreds of micrometers in size, with shapes that typically differ from a perfect sphere. Change in spheroid volume is one of the most important parameters for evaluating treatment efficacy, and using light sheet fluorescence microscopes (LSFM), optical sections of samples in that size range can be obtained. However, there remains a lack of validated methods for quantifying the volumes of 3-D multicellular aggregates. Here, we present Reconstruction and Visualization from Multiple Sections (ReViMS), an open-source, user-friendly software for automatically segmenting z-stacks of fluorescence images and estimating the volumes of 3-D multicellular spheroids. To assess the precision and accuracy of the volume estimates obtained with ReViMS, we used several cancer spheroids imaged with LSFM. Both the precision and accuracy were >95%, demonstrating the effectiveness of ReViMS.

  15. Guidelines for Mass Casualty Decontamination During a HAZMAT/Weapon of Mass Destruction Incident. Volumes 1 and 2 (Update)

    Science.gov (United States)

    2013-08-01

    sharp/pungent, garlic /horseradish, bitter almond, and newly mown hay. Unusual numbers of mass casualties Health problems including nausea, disori...radiation syndrome is generally supportive with blood transfusions and antibiotics . 26 Volume II of II V1.1 2013 Classically acute radiation syndrome

  16. CrossTalk: The Journal of Defense Software Engineering. Volume 27, Number 1, January/February 2014

    Science.gov (United States)

    2014-02-01

    Repository Service is propagated as satisficed label to the NFR softgoal Reliability [Phoenix] via the MAKE contri - bution between them, the satisficed label...help DoD programs better plan their financial investment in software sustainment to ensure that the products are sustainable for as long as...ity attributes. Good architectural designs anticipate change by encapsulating variabil ity to reduce cost and risk . In this approach, change-prone

  17. CrossTalk. The Journal of Defense Software Engineering. Volume 23, Number 6, Nov/Dec 2010

    Science.gov (United States)

    2010-11-01

    them and dearly love the time I spent with them. It was a high point in my career. Outside the software world, Richard Feynman is my abso- lute hero...iterations. Barry Boehm and Richard Turner discuss risk and agile pro- cesses [4] and the summary of their judgment is, “The essence of using risk... Richard Turner. Balancing Agility and Discipline: A Guide for the Perplexed. Addison-Wesley Professional, 2003. 5. Hofmeister, Christine, Robert Nord

  18. CrossTalk: The Journal of Defense Software Engineering. Volume 24, Number 3, May/June 2011

    Science.gov (United States)

    2011-05-01

    standards available such as ISO 12207, ISO 9001 and the Capability Maturity Model Integrated (CMMI®) [24,25,26]. The CMMI was a collaborative effort...Cycle Systems Engineering. 2007 24. CMMI® for Development, Version 1.2. Pittsburgh: Carnegie Mellon University, 2006. 25. “ ISO 9001 .” Quality Management...CrossTalk, The Journal of Defense Software Engineering is co-sponsored by the Under Secretary of Defense for Acquisition, Technology and Logistics

  19. CrossTalk: The Journal of Defense Software Engineering. Volume 27, Number 6, November/December 2014

    Science.gov (United States)

    2014-12-01

    part of the solution was relatively easy since process group was already realizing that they played a more strategic role in the development of the...IEEE Security and Privacy, vol. 2, pp. 18-25. 4. S. L. Pfleeger and J. M. Atlee, Software Engineering Theory and Practice, Prentice Hall, 2010. 5...Challenges,” ACM Computing Surveys, vol. 44, no. 3, pp. 11.1-11.46, 6 2012. 8. M. E. Moreira, Adapting Configuration Mangement for Agile Teams

  20. CrossTalk, The Journal of Defense Software Engineering. Volume 28 Number 1. Jan/Feb 2015

    Science.gov (United States)

    2015-02-01

    appreciate your continued loyalty and for sharing such valuable information to the software community. And finally, to our readers, thank you for...Promotion/Growth Opportunities 3 7 Working Conditions 4 9 Interesting/Challenging Work 5 6 Personal Loyalty to Workers 6 8 Tactful Discipline 7 10...messing up your schedule. What’s wrong is that you started too late. You could have flown in the night before, put up at the pleasant little hotel in

  1. CrossTalk. The Journal of Defense Software Engineering. Volume 25, Number 5. Sep/Oct 2012

    Science.gov (United States)

    2012-10-01

    Treasury; Management of Risk - Principles and Concepts; HM Treasury (Oct. 2004) 10. ISO / IEC 27000 ; Information technology -- Security techniques...the “ability to ensure performance” as opposed to just performance itself. 2. For additional information on the BIA refer to NIST 800-34 or ISO 27000 ...Information security management systems -- Overview and vocabulary; ISO / IEC (Working Draft March 2012) 11. Sommerville, I; Software Engineering (9th

  2. GENII [Generation II]: The Hanford Environmental Radiation Dosimetry Software System: Volume 3, Code maintenance manual: Hanford Environmental Dosimetry Upgrade Project

    International Nuclear Information System (INIS)

    Napier, B.A.; Peloquin, R.A.; Strenge, D.L.; Ramsdell, J.V.

    1988-09-01

    The Hanford Environmental Dosimetry Upgrade Project was undertaken to incorporate the internal dosimetry models recommended by the International Commission on Radiological Protection (ICRP) in updated versions of the environmental pathway analysis models used at Hanford. The resulting second generation of Hanford environmental dosimetry computer codes is compiled in the Hanford Environmental Dosimetry System (Generation II, or GENII). This coupled system of computer codes is intended for analysis of environmental contamination resulting from acute or chronic releases to, or initial contamination of, air, water, or soil, on through the calculation of radiation doses to individuals or populations. GENII is described in three volumes of documentation. This volume is a Code Maintenance Manual for the serious user, including code logic diagrams, global dictionary, worksheets to assist with hand calculations, and listings of the code and its associated data libraries. The first volume describes the theoretical considerations of the system. The second volume is a Users' Manual, providing code structure, users' instructions, required system configurations, and QA-related topics. 7 figs., 5 tabs

  3. GENII: The Hanford Environmental Radiation Dosimetry Software System: Volume 2, Users' manual: Hanford Environmental Dosimetry Upgrade Project

    Energy Technology Data Exchange (ETDEWEB)

    Napier, B.A.; Peloquin, R.A.; Strenge, D.L.; Ramsdell, J.V.

    1988-11-01

    The Hanford Environmental Dosimetry Upgrade Project was undertaken to incorporate the internal dosimetry models recommended by the International Commission on Radiological Protection (ICRP) in updated versions of the environmental pathway analysis models used at Hanford. The resulting second generation of Hanford environmental dosimetry computer codes is compiled in the Hanford Environmental Dosimetry System (Generation II, or GENII). The purpose of this coupled system of computer codes is to analyze environmental contamination of, air, water, or soil. This is accomplished by calculating radiation doses to individuals or populations. GENII is described in three volumes of documentation. This second volume is a Users' Manual, providing code structure, users' instructions, required system configurations, and QA-related topics. The first volume describes the theoretical considerations of the system. The third volume is a Code Maintenance Manual for the user who requires knowledge of code detail. It includes logic diagrams, global dictionary, worksheets, example hand calculations, and listings of the code and its associated data libraries. 27 refs., 17 figs., 23 tabs.

  4. GENII (Generation II): The Hanford Environmental Radiation Dosimetry Software System: Volume 3, Code maintenance manual: Hanford Environmental Dosimetry Upgrade Project

    Energy Technology Data Exchange (ETDEWEB)

    Napier, B.A.; Peloquin, R.A.; Strenge, D.L.; Ramsdell, J.V.

    1988-09-01

    The Hanford Environmental Dosimetry Upgrade Project was undertaken to incorporate the internal dosimetry models recommended by the International Commission on Radiological Protection (ICRP) in updated versions of the environmental pathway analysis models used at Hanford. The resulting second generation of Hanford environmental dosimetry computer codes is compiled in the Hanford Environmental Dosimetry System (Generation II, or GENII). This coupled system of computer codes is intended for analysis of environmental contamination resulting from acute or chronic releases to, or initial contamination of, air, water, or soil, on through the calculation of radiation doses to individuals or populations. GENII is described in three volumes of documentation. This volume is a Code Maintenance Manual for the serious user, including code logic diagrams, global dictionary, worksheets to assist with hand calculations, and listings of the code and its associated data libraries. The first volume describes the theoretical considerations of the system. The second volume is a Users' Manual, providing code structure, users' instructions, required system configurations, and QA-related topics. 7 figs., 5 tabs.

  5. GENII: The Hanford Environmental Radiation Dosimetry Software System: Volume 2, Users' manual: Hanford Environmental Dosimetry Upgrade Project

    International Nuclear Information System (INIS)

    Napier, B.A.; Peloquin, R.A.; Strenge, D.L.; Ramsdell, J.V.

    1988-11-01

    The Hanford Environmental Dosimetry Upgrade Project was undertaken to incorporate the internal dosimetry models recommended by the International Commission on Radiological Protection (ICRP) in updated versions of the environmental pathway analysis models used at Hanford. The resulting second generation of Hanford environmental dosimetry computer codes is compiled in the Hanford Environmental Dosimetry System (Generation II, or GENII). The purpose of this coupled system of computer codes is to analyze environmental contamination of, air, water, or soil. This is accomplished by calculating radiation doses to individuals or populations. GENII is described in three volumes of documentation. This second volume is a Users' Manual, providing code structure, users' instructions, required system configurations, and QA-related topics. The first volume describes the theoretical considerations of the system. The third volume is a Code Maintenance Manual for the user who requires knowledge of code detail. It includes logic diagrams, global dictionary, worksheets, example hand calculations, and listings of the code and its associated data libraries. 27 refs., 17 figs., 23 tabs

  6. ASAMPSA2 best-practices guidelines for L2 PSA development and applications. Volume 3 - Extension to Gen IV reactors

    International Nuclear Information System (INIS)

    Bassi, C.; Bonneville, H.; Brinkman, H.; Burgazzi, L.; Polidoro, F.; Vincon, L.; Jouve, S.

    2010-01-01

    The main objective assigned to the Work Package 4 (WP4) of the 'ASAMPSA2' project (EC 7. FPRD) consist in the verification of the potential compliance of L2PSA guidelines based on PWR/BWR reactors (which are specific tasks of WP2 and WP3) with Generation IV representative concepts. Therefore, in order to exhibit potential discrepancies between LWRs and new reactor types, the following work was based on the up-to-date designs of: - The European Fast Reactor (EFR) which will be considered as prototypical of a pool-type Sodium-cooled Fast Reactor (SFR); - The ELSY design for the Lead-cooled Fast Reactor (LFR) technology; - The ANTARES project which could be representative of a Very-High Temperature Reactor (VHTR); - The CEA 2400 MWth Gas-cooled Fast Reactor (GFR). (authors)

  7. Best-practices guidelines for L2PSA development and applications. Volume 2 - Best practices for the Gen II PWR, Gen II BWR L2PSAs. Extension to Gen III reactors

    International Nuclear Information System (INIS)

    Raimond, E.; Durin, T.; Rahni, N.; Meignen, R.; Cranga, M.; Pichereau, F.; Bentaib, A.; Guigueno, Y.; Loeffler, H.; Mildenberger, O.; Lajtha, G.; Santamaria, C.S.; Dienstbier, J.; Rydl, A.; Holmberg, J.E.; Lindholm, I.; Maennistoe, I.; Pauli, E.M.; Dirksen, G.; Grindon, L.; Peers, K.; Hulqvist, G.; Parozzi, F.; Polidoro, F.; Cazzoli, E.; Vitazkova, J.; Burgazzi, L.; Oury, L.; Ngatchou, C.; Siltanen, S.; Niemela, I.; Routamo, T.; Helstroem, P.; Bassi, C.; Brinkman, H.; Seidel, A.; Schubert, B.; Wohlstein, R.; Guentay, S.; Vincon, L.

    2010-01-01

    The objective of this coordinated action was to develop best practice guidelines for the performance of Level 2 PSA methodologies with a view of harmonisation at EU level and to allow meaningful and practical uncertainty evaluations in a Level 2 PSA. Specific relationships with community in charge of nuclear reactor safety (utilities, safety authorities, vendors, and research or services companies) have been established in order to define the current needs in terms of guidelines for level 2 PSA development and applications. An international workshop was organised in Hamburg, with the support of VATTENFALL, in November 2008. The level 2 PSA experts from the ASAMPSA2 project partners have proposed some guidelines for the development and application of L2PSA based on their experience and on information available from international cooperation (EC Severe Accident network of Excellence - SARNET, IAEA standards, OECD-NEA publications and workshop) or open literature. The number of technical issues addressed in the guideline is very large and all are not covered with the same relevancy in the first version of the guideline. This version is submitted for external review in November 2010 by severe accident experts and PSA, especially, from SARNET and OECD-NEA members. The feedback of the external review will be dis cussed during an international open works hop planned in March 2011 and all outcomes will be taken into consideration in the final version of this guideline (June 2011). The guideline includes 3 volumes: - Volume 1 - General considerations on L2PSA. - Volume 2 - Technical recommendations for Gen II and III reactors. - Volume 3 - Specific considerations for future reactor (Gen IV). The recommendations formulated in the guideline should not be considered as 'mandatory' but should help the L2PSA developers to achieve high quality studies with limited time and resources. It may also help the L2PSA reviewers by positioning one specific study in comparison

  8. An improved approach for flight readiness certification: Methodology for failure risk assessment and application examples. Volume 2: Software documentation

    Science.gov (United States)

    Moore, N. R.; Ebbeler, D. H.; Newlin, L. E.; Sutharshana, S.; Creager, M.

    1992-01-01

    An improved methodology for quantitatively evaluating failure risk of spaceflight systems to assess flight readiness and identify risk control measures is presented. This methodology, called Probabilistic Failure Assessment (PFA), combines operating experience from tests and flights with engineering analysis to estimate failure risk. The PFA methodology is of particular value when information on which to base an assessment of failure risk, including test experience and knowledge of parameters used in engineering analyses of failure phenomena, is expensive or difficult to acquire. The PFA methodology is a prescribed statistical structure in which engineering analysis models that characterize failure phenomena are used conjointly with uncertainties about analysis parameters and/or modeling accuracy to estimate failure probability distributions for specific failure modes, These distributions can then be modified, by means of statistical procedures of the PFA methodology, to reflect any test or flight experience. Conventional engineering analysis models currently employed for design of failure prediction are used in this methodology. The PFA methodology is described and examples of its application are presented. Conventional approaches to failure risk evaluation for spaceflight systems are discussed, and the rationale for the approach taken in the PFA methodology is presented. The statistical methods, engineering models, and computer software used in fatigue failure mode applications are thoroughly documented.

  9. Communications Received from Certain Member States Regarding Guidelines for Transfers of Nuclear-related Dual-use Equipment, Materials, Software and Related Technology

    International Nuclear Information System (INIS)

    2006-01-01

    The Director General of the International Atomic Energy Agency has received Notes Verbales, dated 1 December 2005, from the Resident Representatives to the Agency of Argentina, Australia, Austria, Belarus, Belgium, Brazil, Bulgaria, Canada, Croatia, Czech Republic, Estonia, Finland, France, Germany, Greece, Hungary, Ireland, Italy, Japan, Republic of Korea, Latvia, Lithuania, Luxembourg, Malta, the Netherlands, New Zealand, Poland, Portugal, Slovenia, South Africa, Spain, Sweden, Switzerland, Turkey, Ukraine, the United Kingdom of Great Britain and Northern Ireland and the United States of America, relating to transfers of nuclear-related dual-use equipment, materials, software and related technology

  10. Communications Received from Certain Member States Regarding Guidelines for Transfers of Nuclear-related Dual-use Equipment, Materials, Software and Related Technology

    International Nuclear Information System (INIS)

    2006-01-01

    The Director General of the International Atomic Energy Agency has received Notes Verbales, dated 1 December 2005, from the Resident Representatives to the Agency of Argentina, Australia, Austria, Belarus, Belgium, Brazil, Bulgaria, Canada, Croatia, Czech Republic, Estonia, Finland, France, Germany, Greece, Hungary, Ireland, Italy, Japan, Republic of Korea, Latvia, Lithuania, Luxembourg, Malta, the Netherlands, New Zealand, Poland, Portugal, Slovenia, South Africa, Spain, Sweden, Switzerland, Turkey, Ukraine, the United Kingdom of Great Britain and Northern Ireland and the United States of America, relating to transfers of nuclear-related dual-use equipment, materials, software and related technology [es

  11. Communications received from certain Member States regarding guidelines for transfers of nuclear-related dual-use equipment, materials, software and related technology

    International Nuclear Information System (INIS)

    2000-01-01

    The document reproduces the text of the Notes Verbales received by the Director General of the IAEA on 20 October 1999 from the Resident Representatives to the Agency of Argentina, Australia, Austria, Belgium, Brazil, Bulgaria, Canada, the Czech Republic, Denmark, Finland, France, Germany, Hungary, Ireland, Italy, Japan, Republic of Korea, Latvia, the Netherlands, New Zealand, Norway, Poland, Portugal, Romania, the Slovak Republic, South Africa, Spain, Sweden, Switzerland, Ukraine, the United Kingdom, and the United States of America relating to the transfers of nuclear-related dual-use equipment, materials, software and related technology

  12. Programming guidelines for computer systems of NPPs

    International Nuclear Information System (INIS)

    Suresh babu, R.M.; Mahapatra, U.

    1999-09-01

    Software quality is assured by systematic development and adherence to established standards. All national and international software quality standards have made it mandatory for the software development organisation to produce programming guidelines as part of software documentation. This document contains a set of programming guidelines for detailed design and coding phases of software development cycle. These guidelines help to improve software quality by increasing visibility, verifiability, testability and maintainability. This can be used organisation-wide for various computer systems being developed for our NPPs. This also serves as a guide for reviewers. (author)

  13. Communication Received from Certain Member States Regarding Guidelines for Transfers of Nuclear-related Dual-use Equipment, Material, Software and Related Technology

    International Nuclear Information System (INIS)

    2010-07-01

    The Agency has received a Note Verbale from the Permanent Mission of Hungary, dated 14 June 2010, in which it requests that the Agency circulate to all Member States a letter of 7 May 2010 from the Chairman of the Nuclear Suppliers Group, Ambassador Ms. Gyorgyi Martin Zanathy, to the Director General, on behalf of the Governments of Argentina, Australia, Austria, Belarus, Belgium, Brazil, Bulgaria, Canada, China, Croatia, Cyprus, Czech Republic, Denmark, Estonia, Finland, France, Germany, Greece, Hungary, Iceland, Ireland, Italy, Japan, Kazakhstan, Republic of Korea, Latvia, Lithuania, Luxemburg, Malta, Netherlands, New Zealand, Norway, Poland, Portugal, Romania, Russian Federation, Slovakia, Slovenia, South Africa, Spain, Sweden, Switzerland, Turkey, Ukraine, the United Kingdom of Great Britain and Northern Ireland and the United States of America,1 providing further information on those Governments’ Guidelines for Nuclear Transfers

  14. Communication Received from Certain Member States Regarding Guidelines for Transfers of Nuclear-related Dual-use Equipment, Material, Software and Related Technology

    International Nuclear Information System (INIS)

    2010-01-01

    The Agency has received a Note Verbale from the Permanent Mission of Hungary, dated 14 June 2010, in which it requests that the Agency circulate to all Member States a letter of 7 May 2010 from the Chairman of the Nuclear Suppliers Group, Ambassador Ms. Gyorgyi Martin Zanathy, to the Director General, on behalf of the Governments of Argentina, Australia, Austria, Belarus, Belgium, Brazil, Bulgaria, Canada, China, Croatia, Cyprus, Czech Republic, Denmark, Estonia, Finland, France, Germany, Greece, Hungary, Iceland, Ireland, Italy, Japan, Kazakhstan, Republic of Korea, Latvia, Lithuania, Luxemburg, Malta, Netherlands, New Zealand, Norway, Poland, Portugal, Romania, Russian Federation, Slovakia, Slovenia, South Africa, Spain, Sweden, Switzerland, Turkey, Ukraine, the United Kingdom of Great Britain and Northern Ireland and the United States of America,1 providing further information on those Governments’ Guidelines for Nuclear Transfers

  15. Communication Received from Certain Member States Regarding Guidelines for Transfers of Nuclear-related Dual-use Equipment, Material, Software and Related Technology

    International Nuclear Information System (INIS)

    2010-01-01

    The Agency has received a Note Verbale from the Permanent Mission of Hungary, dated 14 June 2010, in which it requests that the Agency circulate to all Member States a letter of 7 May 2010 from the Chairman of the Nuclear Suppliers Group, Ambassador Ms. Gyorgyi Martin Zanathy, to the Director General, on behalf of the Governments of Argentina, Australia, Austria, Belarus, Belgium, Brazil, Bulgaria, Canada, China, Croatia, Cyprus, Czech Republic, Denmark, Estonia, Finland, France, Germany, Greece, Hungary, Iceland, Ireland, Italy, Japan, Kazakhstan, Republic of Korea, Latvia, Lithuania, Luxemburg, Malta, Netherlands, New Zealand, Norway, Poland, Portugal, Romania, Russian Federation, Slovakia, Slovenia, South Africa, Spain, Sweden, Switzerland, Turkey, Ukraine, the United Kingdom of Great Britain and Northern Ireland and the United States of America,1 providing further information on those Governments’ Guidelines for Nuclear Transfers [es

  16. Transportable Maps Software. Volume I.

    Science.gov (United States)

    1982-07-01

    COMPRESSION STUDY, RADC-TR-BO- 2B7 , August 1980, Final lechnical Report, Contract No. F30602-79-C-00O. SPIE Proceeaings Articles: Laeonte, A. E., "Two...wan.A-0. 4"M -%_"~~ d 0-r4wt 0 "M womqUO--^rWne- ZA. hiM"t, -% Nt MVnO Wwt heoqt Mte.% dnm It c 0 hi 00000 o A. 0 40 a . oem: td W 3 0 ILA. ft d 4

  17. Reflections on Software Research

    Indian Academy of Sciences (India)

    Home; Journals; Resonance – Journal of Science Education; Volume 17; Issue 8. Reflections on Software Research. Dennis M Ritchie. Classics Volume 17 Issue 8 August 2012 pp 810-816. Fulltext. Click here to view fulltext PDF. Permanent link: http://www.ias.ac.in/article/fulltext/reso/017/08/0810-0816. Author Affiliations.

  18. Encyclopedia of Software Components

    Science.gov (United States)

    Warren, Lloyd V. (Inventor); Beckman, Brian C. (Inventor)

    1997-01-01

    Intelligent browsing through a collection of reusable software components is facilitated with a computer having a video monitor and a user input interface such as a keyboard or a mouse for transmitting user selections, by presenting a picture of encyclopedia volumes with respective visible labels referring to types of software, in accordance with a metaphor in which each volume includes a page having a list of general topics under the software type of the volume and pages having lists of software components for each one of the generic topics, altering the picture to open one of the volumes in response to an initial user selection specifying the one volume to display on the monitor a picture of the page thereof having the list of general topics and altering the picture to display the page thereof having a list of software components under one of the general topics in response to a next user selection specifying the one general topic, and then presenting a picture of a set of different informative plates depicting different types of information about one of the software components in response to a further user selection specifying the one component.

  19. Software for Library Management: Selection and Evaluation.

    Science.gov (United States)

    Notowitz, Carol I.

    1987-01-01

    This discussion of library software packages includes guidelines for library automation with microcomputers; criteria to aid in software selection; comparison of some features of available acquisitions, circulation and overdues software; references for software reviews; additional information on microsoftware; and a directory of producers and…

  20. Guide to software export

    CERN Document Server

    Philips, Roger A

    2014-01-01

    An ideal reference source for CEOs, marketing and sales managers, sales consultants, and students of international marketing, Guide to Software Export provides a step-by-step approach to initiating or expanding international software sales. It teaches you how to examine critically your candidate product for exportability; how to find distributors, agents, and resellers abroad; how to identify the best distribution structure for export; and much, much more!Not content with providing just the guidelines for setting up, expanding, and managing your international sales channels, Guide to Software

  1. Author Guidelines

    Directory of Open Access Journals (Sweden)

    Chief Editor

    2016-06-01

    Full Text Available AUTHOR GUIDELINES Indian Journal of Community Health (IJCH accepts only online submission of manuscript(s by using Open Journal software (OJS at http://www.iapsmupuk.org/journal/index.php/IJCH/login Online SubmissionsAlready have a Username/Password for Indian Journal of Community Health (IJCH? GO TO LOGINNeed a Username/Password?GO TO REGISTRATIONNote: Registration and login are required to submit items online and to track the status of current submissions.Author GuidelinesIJCH strictly adheres on the recommendations for the Conduct, Reporting, Editing and Publication of Scholarly Work in Medical Journals as per the standard universal guidelines given by International Committee of Medical Journal Editors (ICMJE - Recommendations for Uniform Requirements for Manuscripts. Authors are requested to visit http://www.icmje.org/index.html before making online submission of their manuscript(s. http://www.icmje.org/recommendations/browse/manuscript-preparation/preparing-for-submission.html Preparing for SubmissionGeneral PrinciplesReporting GuidelinesManuscript SectionsTitle PageAbstractIntroductionMethodsResultsDiscussionReferencesTablesIllustrations (FiguresUnits of MeasurementAbbreviations and Symbols 1. General PrinciplesThe text of articles reporting original research is usually divided into Introduction, Methods, Results, and Discussion sections. This so-called “IMRAD” structure is not an arbitrary publication format but a reflection of the process of scientific discovery. Articles often need subheadings within these sections to further organize their content. Other types of articles, such as meta-analyses, may require different formats, while case reports, narrative reviews, and editorials may have less structured or unstructured formats.Electronic formats have created opportunities for adding details or sections, layering information, cross-linking, or extracting portions of articles in electronic versions. Supplementary electronic

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

  3. Consistency in seroma contouring for partial breast radiotherapy: Impact of guidelines

    International Nuclear Information System (INIS)

    Wong, Elaine K.; Truong, Pauline T.; Kader, Hosam A.; Nichol, Alan M.; Salter, Lee; Petersen, Ross; Wai, Elaine S.; Weir, Lorna; Olivotto, Ivo A.

    2006-01-01

    Purpose: Inconsistencies in contouring target structures can undermine the precision of conformal radiation therapy (RT) planning and compromise the validity of clinical trial results. This study evaluated the impact of guidelines on consistency in target volume contouring for partial breast RT planning. Methods and Materials: Guidelines for target volume definition for partial breast radiation therapy (PBRT) planning were developed by members of the steering committee for a pilot trial of PBRT using conformal external beam planning. In phase 1, delineation of the breast seroma in 5 early-stage breast cancer patients was independently performed by a 'trained' cohort of four radiation oncologists who were provided with these guidelines and an 'untrained' cohort of four radiation oncologists who contoured without guidelines. Using automated planning software, the seroma target volume (STV) was expanded into a clinical target volume (CTV) and planning target volume (PTV) for each oncologist. Means and standard deviations were calculated, and two-tailed t tests were used to assess differences between the 'trained' and 'untrained' cohorts. In phase 2, all eight radiation oncologists were provided with the same contouring guidelines, and were asked to delineate the seroma in five new cases. Data were again analyzed to evaluate consistency between the two cohorts. Results: The 'untrained' cohort contoured larger seroma volumes and had larger CTVs and PTVs compared with the 'trained' cohort in three of five cases. When seroma contouring was performed after review of contouring guidelines, the differences in the STVs, CTVs, and PTVs were no longer statistically significant. Conclusion: Guidelines can improve consistency among radiation oncologists performing target volume delineation for PBRT planning

  4. Author Guidelines

    Directory of Open Access Journals (Sweden)

    Chief Editor

    2015-12-01

    Full Text Available Author GuidelinesIJCH strictly adheres on the recommendations for the Conduct, Reporting, Editing and Publication of Scholarly Work in Medical Journals as per the standard universal guidelines given by International Committee of Medical Journal Editors (ICMJE - Recommendations for Uniform Requirements for Manuscripts. Authors are requested to visit http://www.icmje.org/index.html before making online submission of their manuscript(s.  http://www.icmje.org/recommendations/browse/manuscript-preparation/preparing-for-submission.html Preparing for SubmissionPAGE CONTENTSGeneral PrinciplesReporting GuidelinesManuscript SectionsTitle PageAbstractIntroductionMethodsResultsDiscussionReferencesTablesIllustrations (FiguresUnits of MeasurementAbbreviations and Symbols1. General PrinciplesThe text of articles reporting original research is usually divided into Introduction, Methods, Results, and Discussion sections. This so-called “IMRAD” structure is not an arbitrary publication format but a reflection of the process of scientific discovery. Articles often need subheadings within these sections to further organize their content. Other types of articles, such as meta-analyses, may require different formats, while case reports, narrative reviews, and editorials may have less structured or unstructured formats.Electronic formats have created opportunities for adding details or sections, layering information, cross-linking, or extracting portions of articles in electronic versions. Supplementary electronic-only material should be submitted and sent for peer review simultaneously with the primary manuscript.2. Reporting GuidelinesReporting guidelines have been developed for different study designs; examples include CONSORT for randomized trials, STROBE for observational studies, PRISMA for systematic reviews and meta-analyses, and STARD for studies of diagnostic accuracy. Journals are encouraged to ask authors to follow these guidelines because

  5. Java look and feel design guidelines

    CERN Document Server

    Sun Microsystems

    1999-01-01

    Java Look and Feel Design Guidelines provides essential information for anyone involved in the process of creating cross-platform Java(TM) applications and applets. Offering design guidelines for software that uses the Java(TM) Foundation Classes (JFC) together with the Java look and feel, this book offers designers and software developers an unparalleled resource.

  6. R D software quality assurance

    Energy Technology Data Exchange (ETDEWEB)

    Hood, F.C.

    1991-10-01

    Research software quality assurance (QA) requirements must be adequate to strengthen development or modification objectives, but flexible enough not to restrict creativity. Application guidelines are needed for the different kinds of research and development (R D) software activities to assure project objectives are achieved.

  7. Software Engineering Education: Some Important Dimensions

    Science.gov (United States)

    Mishra, Alok; Cagiltay, Nergiz Ercil; Kilic, Ozkan

    2007-01-01

    Software engineering education has been emerging as an independent and mature discipline. Accordingly, various studies are being done to provide guidelines for curriculum design. The main focus of these guidelines is around core and foundation courses. This paper summarizes the current problems of software engineering education programs. It also…

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

  9. National Trends in Prostate Biopsy and Radical Prostatectomy Volumes Following the US Preventive Services Task Force Guidelines Against Prostate-Specific Antigen Screening.

    Science.gov (United States)

    Halpern, Joshua A; Shoag, Jonathan E; Artis, Amanda S; Ballman, Karla V; Sedrakyan, Art; Hershman, Dawn L; Wright, Jason D; Shih, Ya Chen Tina; Hu, Jim C

    2017-02-01

    Studies demonstrate that use of prostate-specific antigen screening decreased significantly following the US Preventive Services Task Force (USPSTF) recommendation against prostate-specific antigen screening in 2012. To determine downstream effects on practice patterns in prostate cancer diagnosis and treatment following the 2012 USPSTF recommendation. Procedural volumes of certifying and recertifying urologists from 2009 through 2016 were evaluated for variation in prostate biopsy and radical prostatectomy (RP) volume. Trends were confirmed using the New York Statewide Planning and Research Cooperative System and Nationwide Inpatient Sample. The study included a representative sample of urologists across practice settings and nationally representative sample of all RP discharges. We obtained operative case logs from the American Board of Urology and identified urologists performing at least 1 prostate biopsy (n = 5173) or RP (n = 3748), respectively. The 2012 USPSTF recommendation against routine population-wide prostate-specific antigen screening. Change in median biopsy and RP volume per urologist and national procedural volume. Following the USPSTF recommendation, median biopsy volume per urologist decreased from 29 to 21 (interquartile range [IQR}, 12-34; P following 2012 (parameter estimate, -0.25; SE, 0.03; P following the USPSTF recommendation, median RP volume per urologist decreased from 7 (IQR, 3-15) to 6 (IQR, 2-12) (P Following the 2012 USPSTF recommendation, prostate biopsy and RP volumes decreased significantly. A panoramic vantage point is needed to evaluate the long-term consequences of the 2012 USPSTF recommendation.

  10. Revisiting software ecosystems research

    DEFF Research Database (Denmark)

    Manikas, Konstantinos

    2016-01-01

    Software ecosystems’ is argued to first appear as a concept more than 10 years ago and software ecosystem research started to take off in 2010. We conduct a systematic literature study, based on the most extensive literature review in the field up to date, with two primarily aims: (a) to provide...... an updated overview of the field and (b) to document evolution in the field. In total, we analyze 231 papers from 2007 until 2014 and provide an overview of the research in software ecosystems. Our analysis reveals a field that is rapidly growing both in volume and empirical focus while becoming more mature...... from evolving. We propose means for future research and the community to address them. Finally, our analysis shapes the view of the field having evolved outside the existing definitions of software ecosystems and thus propose the update of the definition of software ecosystems....

  11. NASA PC software evaluation project

    Science.gov (United States)

    Dominick, Wayne D. (Editor); Kuan, Julie C.

    1986-01-01

    The USL NASA PC software evaluation project is intended to provide a structured framework for facilitating the development of quality NASA PC software products. The project will assist NASA PC development staff to understand the characteristics and functions of NASA PC software products. Based on the results of the project teams' evaluations and recommendations, users can judge the reliability, usability, acceptability, maintainability and customizability of all the PC software products. The objective here is to provide initial, high-level specifications and guidelines for NASA PC software evaluation. The primary tasks to be addressed in this project are as follows: to gain a strong understanding of what software evaluation entails and how to organize a structured software evaluation process; to define a structured methodology for conducting the software evaluation process; to develop a set of PC software evaluation criteria and evaluation rating scales; and to conduct PC software evaluations in accordance with the identified methodology. Communication Packages, Network System Software, Graphics Support Software, Environment Management Software, General Utilities. This report represents one of the 72 attachment reports to the University of Southwestern Louisiana's Final Report on NASA Grant NGT-19-010-900. Accordingly, appropriate care should be taken in using this report out of context of the full Final Report.

  12. Embedded Information Systems Technology Support (EISTS). Task Order 0006: Vulnerability Path Analysis and Demonstration (VPAD). Volume 2 - White Box Definitions of Software Fault Patterns

    Science.gov (United States)

    2011-12-01

    SFP # Software Fault Clusters Primary Secondary # of CWEs Primary CWE Totals Pattern...Condition Available? White- Box CWE SFP # Software Fault Clusters Primary Secondary # of CWEs Primary CWE Totals Pattern & Condition...Available? White- Box CWE SFP # 632 310 36 o o o o o o o o o o o o o o o o o o o o o o any o o o o o o o o o o o o o o o o o o o o o o o

  13. Special Report on Lessons Learned (1985-2011). Volume 2: Handbook of Recommended Design Practices (Fire Protection and Life Safety Design Guidelines for Special Purpose Underground Structures)

    Science.gov (United States)

    2012-10-01

    should be delivered in AUTOCAD or GIS format, all referenced to the same basic floor plan and assembled into an integrated package of drawings...ASD Aspirating Smoke Detector AutoCAD Computer-Aided Design (software by Autodesk, Inc.) BAS Building Automation System BSA Balance

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

  15. The engineering of microprocessor systems guidelines on system development

    CERN Document Server

    1979-01-01

    The Engineering of Microprocessor Systems: Guidelines on System Development provides economical and technical guidance for use when incorporating microprocessors in products or production processes and assesses the alternatives that are available. This volume is part of Project 0251 undertaken by The Electrical Research Association, which aims to give managers and development engineers advice and comment on the development process and the hardware and software needed to support the engineering of microprocessor systems. The results of Phase 1 of the five-phase project are contained in this fir

  16. Internal and external validation of an ESTRO delineation guideline

    DEFF Research Database (Denmark)

    Eldesoky, Ahmed R.; Yates, Esben Svitzer; Nyeng, Tine B

    2016-01-01

    multi-atlas libraries using MIM Maestro™ software. These libraries were used for auto-segmentation in two different patient groups (50 patients from the local institution and 40 patients from other institutions). Dice Similarity Coefficient, Average Hausdorff Distance, difference in volume and time were......Background and purpose To internally and externally validate an atlas based automated segmentation (ABAS) in loco-regional radiation therapy of breast cancer. Materials and methods Structures of 60 patients delineated according to the ESTRO consensus guideline were included in four categorized...

  17. Software Metrics and Software Metrology

    CERN Document Server

    Abran, Alain

    2010-01-01

    Most of the software measures currently proposed to the industry bring few real benefits to either software managers or developers. This book looks at the classical metrology concepts from science and engineering, using them as criteria to propose an approach to analyze the design of current software measures and then design new software measures (illustrated with the design of a software measure that has been adopted as an ISO measurement standard). The book includes several case studies analyzing strengths and weaknesses of some of the software measures most often quoted. It is meant for sof

  18. Performance of new automated transthoracic three-dimensional echocardiographic software for left ventricular volumes and function assessment in routine clinical practice: Comparison with 3 Tesla cardiac magnetic resonance.

    Science.gov (United States)

    Levy, Franck; Dan Schouver, Elie; Iacuzio, Laura; Civaia, Filippo; Rusek, Stephane; Dommerc, Carinne; Marechaux, Sylvestre; Dor, Vincent; Tribouilloy, Christophe; Dreyfus, Gilles

    2017-11-01

    Three-dimensional (3D) transthoracic echocardiography (TTE) is superior to two-dimensional Simpson's method for assessment of left ventricular (LV) volumes and LV ejection fraction (LVEF). Nevertheless, 3D TTE is not incorporated into everyday practice, as current LV chamber quantification software products are time-consuming. To evaluate the feasibility, accuracy and reproducibility of new fully automated fast 3D TTE software (HeartModel A.I. ; Philips Healthcare, Andover, MA, USA) for quantification of LV volumes and LVEF in routine practice; to compare the 3D LV volumes and LVEF obtained with a cardiac magnetic resonance (CMR) reference; and to optimize automated default border settings with CMR as reference. Sixty-three consecutive patients, who had comprehensive 3D TTE and CMR examinations within 24hours, were eligible for inclusion. Nine patients (14%) were excluded because of insufficient echogenicity in the 3D TTE. Thus, 54 patients (40 men; mean age 63±13 years) were prospectively included into the study. The inter- and intraobserver reproducibilities of 3D TTE were excellent (coefficient of variationTTE compared with CMR (bias=-22±34mL; PTTE and CMR for ESV and LVEF were excellent (r=0.93 and r=0.91, respectively; PTTE using new-generation fully automated software is a feasible, fast, reproducible and accurate imaging modality for LV volumetric quantification in routine practice. Optimization of border detection settings may increase agreement with CMR for EDV assessment in dilated ventricles. Copyright © 2017 Elsevier Masson SAS. All rights reserved.

  19. Sector-specific issues and reporting methodologies supporting the General Guidelines for the voluntary reporting of greenhouse gases under Section 1605(b) of the Energy Policy Act of 1992. Volume 2: Part 4, Transportation sector; Part 5, Forestry sector; Part 6, Agricultural sector

    International Nuclear Information System (INIS)

    1994-10-01

    This volume, the second of two such volumes, contains sector-specific guidance in support of the General Guidelines for the voluntary reporting of greenhouse gas emissions and carbon sequestration. This voluntary reporting program was authorized by Congress in Section 1605(b) of the Energy Policy Act of 1992. The General Guidelines, bound separately from this volume, provide the overall rationale for the program, discuss in general how to analyze emissions and emission reduction/carbon sequestration projects, and address programmatic issues such as minimum reporting requirements, time parameters, international projects, confidentiality, and certification. Together, the General Guidelines and the guidance in these supporting documents will provide concepts and approaches needed to prepare the reporting forms. This second volume of sector-specific guidance covers the transportation sector, the forestry sector, and the agricultural sector

  20. Sector-specific issues and reporting methodologies supporting the General Guidelines for the voluntary reporting of greenhouse gases under Section 1605(b) of the Energy Policy Act of 1992. Volume 2: Part 4, Transportation sector; Part 5, Forestry sector; Part 6, Agricultural sector

    Energy Technology Data Exchange (ETDEWEB)

    1994-10-01

    This volume, the second of two such volumes, contains sector-specific guidance in support of the General Guidelines for the voluntary reporting of greenhouse gas emissions and carbon sequestration. This voluntary reporting program was authorized by Congress in Section 1605(b) of the Energy Policy Act of 1992. The General Guidelines, bound separately from this volume, provide the overall rationale for the program, discuss in general how to analyze emissions and emission reduction/carbon sequestration projects, and address programmatic issues such as minimum reporting requirements, time parameters, international projects, confidentiality, and certification. Together, the General Guidelines and the guidance in these supporting documents will provide concepts and approaches needed to prepare the reporting forms. This second volume of sector-specific guidance covers the transportation sector, the forestry sector, and the agricultural sector.

  1. Forever software

    NARCIS (Netherlands)

    Rensink, Arend; Margaria, Tiziana; Steffen, Bernhard

    2014-01-01

    Any attempt to explain software engineering to a lay audience soon falls back on analogy: building software is like building a bridge, a car, a television set. A large part of the established practice within software engineering is also based on this premise. However, the analogy is false in some

  2. Software reliability

    CERN Document Server

    Bendell, A

    1986-01-01

    Software Reliability reviews some fundamental issues of software reliability as well as the techniques, models, and metrics used to predict the reliability of software. Topics covered include fault avoidance, fault removal, and fault tolerance, along with statistical methods for the objective assessment of predictive accuracy. Development cost models and life-cycle cost models are also discussed. This book is divided into eight sections and begins with a chapter on adaptive modeling used to predict software reliability, followed by a discussion on failure rate in software reliability growth mo

  3. Author Guidelines

    Directory of Open Access Journals (Sweden)

    Yunisrina Qismullah Yusuf

    2015-03-01

    Full Text Available Guidelines for Article Submission SiELE journal accepts articles on research and development in the field of teaching and learning of English, linguistics, educational development, policy and cultural studies in education. To be considered for publication, the article should be presented in the following system: First page: include a title page with the full title of the paper (must not exceed 16 words, the author(s’ name(s, affiliation(s, phone number(s and e-mail address of the corresponding author. A brief bio-data of the author(s (maximum of 100 words is provided in this page. Second page and subsequent page: Submissions should be between 4000-6000 (including abstract, table(s, figure(s and references in A4 size paper with margins as the following: top 3 cm, bottom 3 cm, right 2.5 cm and left 4 cm. The font is Times New Roman, size 12 and single spaced. The article should generally consist of the following sections: introduction, review of literature, method, findings, discussion and conclusion. Headings and subheadings should be presented as follows (provide a space between the headings and sub-headings. 1 INTRODUCTION 1.1 Subheading of the content 1.1.1 Subheading of the content For Tables, the title size is 12 and the content size is 10. Please number the tables subsequently throughout your article and the title is written above the table. For Figures, the title size is 12 and the content size (if any is 10. Please number the figures subsequently throughout your article and the title is written below the figure. The reference list should be arranged alphabetically following the guidelines of the Publication Manual of the American Psychological Association (5th ed.. See the following examples: Back Matter| 79 80 | STUDIES IN ENGLISH LANGUAGE AND EDUCATION, Volume 1, Number 1, March 2014 Book: Ellis, R. (2003. Task-based language learning and teaching. Oxford: Oxford University Press. Internet source: Andrewes, S. (2003. Group work v

  4. NASA software documentation standard software engineering program

    Science.gov (United States)

    1991-01-01

    The NASA Software Documentation Standard (hereinafter referred to as Standard) can be applied to the documentation of all NASA software. This Standard is limited to documentation format and content requirements. It does not mandate specific management, engineering, or assurance standards or techniques. This Standard defines the format and content of documentation for software acquisition, development, and sustaining engineering. Format requirements address where information shall be recorded and content requirements address what information shall be recorded. This Standard provides a framework to allow consistency of documentation across NASA and visibility into the completeness of project documentation. This basic framework consists of four major sections (or volumes). The Management Plan contains all planning and business aspects of a software project, including engineering and assurance planning. The Product Specification contains all technical engineering information, including software requirements and design. The Assurance and Test Procedures contains all technical assurance information, including Test, Quality Assurance (QA), and Verification and Validation (V&V). The Management, Engineering, and Assurance Reports is the library and/or listing of all project reports.

  5. Summary guidelines

    Energy Technology Data Exchange (ETDEWEB)

    Halsnaes, K.; Painuly, J.P.; Turkson, J.; Meyer, H.J.; Markandya, A.

    1999-09-01

    This document is a summary version of the methodological guidelines for climate change mitigation assessment developed as part of the Global Environment Facility (GEF) project Economics of Greenhouse Gas Limitations; Methodological Guidelines. The objectives of this project have been to develop a methodology, an implementing framework and a reporting system which countries can use in the construction of national climate change mitigation policies and in meeting their future reporting obligations under the FCCC. The methodological framework developed in the Methodological Guidelines covers key economic concepts, scenario building, modelling tools and common assumptions. It was used by several country studies included in the project. (au) 13 refs.

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

  7. Fundamental Approaches to Software Engineering

    NARCIS (Netherlands)

    Gnesi, S.; Rensink, Arend; Unknown, [Unknown

    This volume contains the proceedings of FASE 2014, the 17th International Conferences on Fundamental Approaches to Software Engineering, which was held in Grenoble, Italy, in April 2014 as part of the annual European Joint Conferences on Theory and Practice of Software (ETAPS).

  8. Modular Software-Defined Radio

    Directory of Open Access Journals (Sweden)

    Rhiemeier Arnd-Ragnar

    2005-01-01

    Full Text Available In view of the technical and commercial boundary conditions for software-defined radio (SDR, it is suggestive to reconsider the concept anew from an unconventional point of view. The organizational principles of signal processing (rather than the signal processing algorithms themselves are the main focus of this work on modular software-defined radio. Modularity and flexibility are just two key characteristics of the SDR environment which extend smoothly into the modeling of hardware and software. In particular, the proposed model of signal processing software includes irregular, connected, directed, acyclic graphs with random node weights and random edges. Several approaches for mapping such software to a given hardware are discussed. Taking into account previous findings as well as new results from system simulations presented here, the paper finally concludes with the utility of pipelining as a general design guideline for modular software-defined radio.

  9. Software Licensing

    OpenAIRE

    Nygrýnová, Dominika

    2014-01-01

    Summary: Software Licensing The thesis deals with different practical aspects of commercial software licensing from the perspective of the Czech legal system. The focus is put on software license agreement as the most important legal instrument granting rights of use for computer programs. The thesis opens with a summary of Czech legislation in force in this area in the context of European community law and international law. The legislation in effect is largely governed by the Copyright Act....

  10. Interconnection Guidelines

    Science.gov (United States)

    The Interconnection Guidelines provide general guidance on the steps involved with connecting biogas recovery systems to the utility electrical power grid. Interconnection best practices including time and cost estimates are discussed.

  11. OSART guidelines

    International Nuclear Information System (INIS)

    1988-02-01

    The IAEA Operational Safety Review Team (OSART) programme provides advice and assistance to Member States to enhance the operational safety of nuclear power plants. These OSART Guidelines provide overall guidance for the experts to ensure the consistency and comprehensiveness of the operational safety review. Specific guidelines are provided as guide for the systematic review in the following areas important to operational safety: management, organization and administration, training and qualification, operations, maintenance, technical support, radiation protection, chemistry, emergency planning and preparedness

  12. Author Guidelines

    Directory of Open Access Journals (Sweden)

    Yunisrina Qismullah Yusuf

    2014-09-01

    http://www.teachingenglish.org.uk/think/articles/group-work-v-whole-class-activities Journal: Yusuf, Y. Q., Pillai, S., & Mohd. Ali, N.T.A. (2013. Speaking Acehnese in Malaysia. Language and Communication, 33(1: 50-60. Chapter in an edited volume: Lee, E. M., & Lim, L. (2000. Diphthongs in Singaporean English: Their realizations across different formality levels, and some attitudes of listeners towards them. In A. Brown, D. Deterding & E. L. Low (Eds. The English language in Singapore: Research on pronunciation (pp. 101-111. Singapore: Singapore Association for Applied Linguistics. Conference proceedings publications: Al-Tamimi, J., & Ferragne, E. (2005. Does vowel space size depend on language vowel inventories? Evidence from two Arabic dialects and French. Proceedings of Interspeech (pp. 2465-2468. Lisbon, Portugal. Published dissertation: Asyik. A. G. (1987. A contextual grammar of Acehnese sentences. (Doctoral dissertation. University of Michigan, Ann Arbor. Retrieved February 4, 2014 from http://www.acehbooks.org/pdf/00402.pdf. (Order number: 8720237 Unpublished thesis/dissertation: Yasin, B. (2004. Sistem informasi manajemen pendidikan: Studi pengembangan model sistem informasi manajemen bidang adminsitrasi akademik dan kemahasiswaan pada FKIP Unsyiah. (Unpublished doctoral dissertation. Universitas Negeri Malang Malang.   Unpublished paper presented at a conference: Yasin, B. (2007, December. Membangun masa depan pendidikan Aceh Barat: Strategi dan kebijakan. Paper presented at the Seminar Pembangunan Pendidikan Kabupaten Aceh Barat, Universitas Syiah Kuala, Banda Aceh, Indonesia. Mass media/newspaper: Akmal, S. (2011, March 13. Nasib Bahsa Aceh di tengah euforia nasionalisme Keacehan. Serambi Indonesia, p. Opini column.   For in-text citations, use the name of the author(s followed by the year of publication.  Submit the article to sielejournal@gmail.com, with the subject: SUBMISSION TO SiELE. For further information on the submission guideline, please visit

  13. Author Guidelines

    Directory of Open Access Journals (Sweden)

    Yunisrina Qismullah Yusuf

    2016-03-01

    .uk/think/articles/group-work-v-whole-class-activities Journal: Yusuf, Y. Q., Pillai, S., & Mohd. Ali, N.T.A. (2013. Speaking Acehnese in Malaysia. Language and Communication, 33(1: 50-60. Chapter in an edited volume: Lee, E. M., & Lim, L. (2000. Diphthongs in Singaporean English: Their realizations across different formality levels, and some attitudes of listeners towards them. In A. Brown, D. Deterding & E. L. Low (Eds. The English language in Singapore: Research on pronunciation (pp. 101-111. Singapore: Singapore Association for Applied Linguistics. Conference proceedings publications: Al-Tamimi, J., & Ferragne, E. (2005. Does vowel space size depend on language vowel inventories? Evidence from two Arabic dialects and French. Proceedings of Interspeech (pp. 2465-2468. Lisbon, Portugal. Published dissertation: Asyik. A. G. (1987. A contextual grammar of Acehnese sentences. (Doctoral dissertation. University of Michigan, Ann Arbor. Retrieved February 4, 2014 from http://www.acehbooks.org/pdf/00402.pdf. (Order number: 8720237 Unpublished thesis/dissertation: Yasin, B. (2004. Sistem informasi manajemen pendidikan: Studi pengembangan model sistem informasi manajemen bidang adminsitrasi akademik dan kemahasiswaan pada FKIP Unsyiah. (Unpublished doctoral dissertation. Universitas Negeri Malang Malang.   Unpublished paper presented at a conference: Yasin, B. (2007, December. Membangun masa depan pendidikan Aceh Barat: Strategi dan kebijakan. Paper presented at the Seminar Pembangunan Pendidikan Kabupaten Aceh Barat, Universitas Syiah Kuala, Banda Aceh, Indonesia. Mass media/newspaper: Akmal, S. (2011, March 13. Nasib Bahsa Aceh di tengah euforia nasionalisme Keacehan. Serambi Indonesia, p. Opini column. For in-text citations, use the name of the author(s followed by the year of publication. Submit the article to sielejournal@gmail.com, with the subject: SUBMISSION TO SiELE. For further information on the submission guideline, please visit our page at http://www.jurnal.unsyiah.ac.id/SiELE. Once your article is accepted, the

  14. Author Guidelines

    Directory of Open Access Journals (Sweden)

    Yunisrina Qismullah Yusuf

    2015-10-01

    http://www.teachingenglish.org.uk/think/articles/group-work-v-whole-class-activities Journal: Yusuf, Y. Q., Pillai, S., & Mohd. Ali, N.T.A. (2013. Speaking Acehnese in Malaysia. Language and Communication, 33(1: 50-60. Chapter in an edited volume: Lee, E. M., & Lim, L. (2000. Diphthongs in Singaporean English: Their realizations across different formality levels, and some attitudes of listeners towards them. In A. Brown, D. Deterding & E. L. Low (Eds. The English language in Singapore: Research on pronunciation (pp. 101-111. Singapore: Singapore Association for Applied Linguistics. Conference proceedings publications: Al-Tamimi, J., & Ferragne, E. (2005. Does vowel space size depend on language vowel inventories? Evidence from two Arabic dialects and French. Proceedings of Interspeech (pp. 2465-2468. Lisbon, Portugal. Published dissertation: Asyik. A. G. (1987. A contextual grammar of Acehnese sentences. (Doctoral dissertation. University of Michigan, Ann Arbor. Retrieved February 4, 2014 from http://www.acehbooks.org/pdf/00402.pdf. (Order number: 8720237 Unpublished thesis/dissertation: Yasin, B. (2004. Sistem informasi manajemen pendidikan: Studi pengembangan model sistem informasi manajemen bidang adminsitrasi akademik dan kemahasiswaan pada FKIP Unsyiah. (Unpublished doctoral dissertation. Universitas Negeri Malang Malang.   Unpublished paper presented at a conference: Yasin, B. (2007, December. Membangun masa depan pendidikan Aceh Barat: Strategi dan kebijakan. Paper presented at the Seminar Pembangunan Pendidikan Kabupaten Aceh Barat, Universitas Syiah Kuala, Banda Aceh, Indonesia. Mass media/newspaper: Akmal, S. (2011, March 13. Nasib Bahsa Aceh di tengah euforia nasionalisme Keacehan. Serambi Indonesia, p. Opini column.   For in-text citations, use the name of the author(s followed by the year of publication.  Submit the article to sielejournal@gmail.com, with the subject: SUBMISSION TO SiELE. For further information on the submission guideline, please visit

  15. Author Guidelines

    Directory of Open Access Journals (Sweden)

    Yunisrina Qismullah Yusuf

    2014-03-01

    http://www.teachingenglish.org.uk/think/articles/group-work-v-whole-class-activities Journal: Yusuf, Y. Q., Pillai, S., & Mohd. Ali, N.T.A. (2013. Speaking Acehnese in Malaysia. Language and Communication, 33(1: 50-60. Chapter in an edited volume: Lee, E. M., & Lim, L. (2000. Diphthongs in Singaporean English: Their realizations across different formality levels, and some attitudes of listeners towards them. In A. Brown, D. Deterding & E. L. Low (Eds. The English language in Singapore: Research on pronunciation (pp. 101-111. Singapore: Singapore Association for Applied Linguistics. Conference proceedings publications: Al-Tamimi, J., & Ferragne, E. (2005. Does vowel space size depend on language vowel inventories? Evidence from two Arabic dialects and French. Proceedings of Interspeech (pp. 2465-2468. Lisbon, Portugal. Published dissertation: Asyik. A. G. (1987. A contextual grammar of Acehnese sentences. (Doctoral dissertation. University of Michigan, Ann Arbor. Retrieved February 4, 2014 from http://www.acehbooks.org/pdf/00402.pdf. (Order number: 8720237 Unpublished thesis/dissertation: Yasin, B. (2004. Sistem informasi manajemen pendidikan: Studi pengembangan model sistem informasi manajemen bidang adminsitrasi akademik dan kemahasiswaan pada FKIP Unsyiah. (Unpublished doctoral dissertation. Universitas Negeri Malang Malang.   Unpublished paper presented at a conference: Yasin, B. (2007, December. Membangun masa depan pendidikan Aceh Barat: Strategi dan kebijakan. Paper presented at the Seminar Pembangunan Pendidikan Kabupaten Aceh Barat, Universitas Syiah Kuala, Banda Aceh, Indonesia. Mass media/newspaper: Akmal, S. (2011, March 13. Nasib Bahsa Aceh di tengah euforia nasionalisme Keacehan. Serambi Indonesia, p. Opini column.   For in-text citations, use the name of the author(s followed by the year of publication.  Submit the article to sielejournal@gmail.com, with the subject: SUBMISSION TO SiELE. For further information on the submission guideline, please visit

  16. Feasibility and Accuracy of Automated Software for Transthoracic Three-Dimensional Left Ventricular Volume and Function Analysis: Comparisons with Two-Dimensional Echocardiography, Three-Dimensional Transthoracic Manual Method, and Cardiac Magnetic Resonance Imaging.

    Science.gov (United States)

    Tamborini, Gloria; Piazzese, Concetta; Lang, Roberto M; Muratori, Manuela; Chiorino, Elisa; Mapelli, Massimo; Fusini, Laura; Ali, Sarah Ghulam; Gripari, Paola; Pontone, Gianluca; Andreini, Daniele; Pepi, Mauro

    2017-11-01

    Recently, a new automated software package (HeartModel) was developed to obtain three-dimensional (3D) left ventricular (LV) volumes using a model-based algorithm (MBA) with a "one-button" simple system and user-adjustable slider. The aims of this study were to verify the feasibility and accuracy of the MBA in comparison with other commonly used imaging techniques in a large unselected population, to evaluate possible accuracy improvements of free operator border adjustments or changes of the slider's default position, and to identify differences in method accuracy related to specific pathologies. This prospective study included consecutive 200 patients. LV volumes and ejection fraction were obtained using the MBA and compared with the two-dimensional biplane method, the 3D full-volume (3DFV) modality, and, in 90 of 200 cases, cardiac magnetic resonance (CMR) measurements. To evaluate the optimal position of the slider with respect to the 3DFV and CMR modalities, a set of threefold cross-validation experiments was performed. Optimized and manually corrected LV volumes obtained using the MBA were also tested. Linear correlation and Bland-Altman analysis were used to assess intertechnique agreement. Automatic volumes were feasible in 194 patients (94.5%), with a mean processing time of 29 ± 10 sec. MBA-derived volumes correlated significantly with all evaluated methods, with slight overestimation of two-dimensional biplane and slight underestimation of CMR measurements. Higher correlations were found between MBA and 3DFV measurements, with negligible differences both in volumes (overestimation) and in LV ejection fraction (underestimation), respectively. Optimization of the user-adjustable slider position improved the correlation and markedly reduced the bias between the MBA and 3DFV or CMR. The accuracy of MBA volumes was lower in some pathologies for incorrect definition of LV endocardium. The MBA is highly feasible, reproducible, and rapid, and it correlates

  17. Comparison and Consensus Guidelines for Delineation of Clinical Target Volume for CT- and MR-Based Brachytherapy in Locally Advanced Cervical Cancer

    Energy Technology Data Exchange (ETDEWEB)

    Viswanathan, Akila N., E-mail: aviswanathan@lroc.harvard.edu [Brigham and Women' s Hospital/Dana-Farber Cancer Institute, Boston, Massachusetts (United States); Erickson, Beth [Medical College of Wisconsin, Milwaukee, Wisconsin (United States); Gaffney, David K. [University of Utah Huntsman Cancer Hospital, Salt Lake City, Utah (United States); Beriwal, Sushil [University of Pittsburgh Cancer Institute, Pittsburgh, Pennsylvania (United States); Bhatia, Sudershan K. [University of Iowa, Iowa City, Iowa (United States); Lee Burnett, Omer [University of Alabama, Birmingham, Alabama (United States); D' Souza, David P.; Patil, Nikhilesh [London Health Sciences Centre and Western University, London, Ontario (Canada); Haddock, Michael G. [Mayo Medical Center, Rochester, Minnesota (United States); Jhingran, Anuja [University of Texas MD Anderson Cancer Center, Houston, Texas (United States); Jones, Ellen L. [University of North Carolina, Chapel Hill, North Carolina (United States); Kunos, Charles A. [Case Western Reserve University, Cleveland, Ohio (United States); Lee, Larissa J. [Brigham and Women' s Hospital/Dana-Farber Cancer Institute, Boston, Massachusetts (United States); Lin, Lilie L. [University of Pennsylvania, Philadelphia, Pennsylvania (United States); Mayr, Nina A. [University of Washington, Seattle, Washington (United States); Petersen, Ivy [Mayo Medical Center, Rochester, Minnesota (United States); Petric, Primoz [Division of Radiotherapy, Institute of Oncology Ljubljana, Ljubljana (Slovenia); Department of Radiation Oncology, National Center for Cancer Care and Research, Doha (Qatar); Portelance, Lorraine [University of Miami Miller School of Medicine, Miami, Florida (United States); Small, William [Loyola University Strich School of Medicine, Chicago, Illinois (United States); Strauss, Jonathan B. [The Robert H. Lurie Comprehensive Cancer Center of Northwestern University, Chicago, Illinois (United States); and others

    2014-10-01

    Objective: To create and compare consensus clinical target volume (CTV) contours for computed tomography (CT) and 3-Tesla (3-T) magnetic resonance (MR) image-based cervical-cancer brachytherapy. Methods and Materials: Twenty-three experts in gynecologic radiation oncology contoured the same 3 cervical cancer brachytherapy cases: 1 stage IIB near-complete response (CR) case with a tandem and ovoid, 1 stage IIB partial response (PR) case with tandem and ovoid with needles, and 1 stage IB2 CR case with a tandem and ring applicator. The CT contours were completed before the MRI contours. These were analyzed for consistency and clarity of target delineation using an expectation maximization algorithm for simultaneous truth and performance level estimation (STAPLE), with κ statistics as a measure of agreement between participants. The conformity index was calculated for each of the 6 data sets. Dice coefficients were generated to compare the CT and MR contours of the same case. Results: For all 3 cases, the mean tumor volume was smaller on MR than on CT (P<.001). The κ and conformity index estimates were slightly higher for CT, indicating a higher level of agreement on CT. The Dice coefficients were 89% for the stage IB2 case with a CR, 74% for the stage IIB case with a PR, and 57% for the stage IIB case with a CR. Conclusion: In a comparison of MR-contoured with CT-contoured CTV volumes, the higher level of agreement on CT may be due to the more distinct contrast medium visible on the images at the time of brachytherapy. MR at the time of brachytherapy may be of greatest benefit in patients with large tumors with parametrial extension that have a partial or complete response to external beam. On the basis of these results, a 95% consensus volume was generated for CT and for MR. Online contouring atlases are available for instruction at (http://www.nrgoncology.org/Resources/ContouringAtlases/GYNCervicalBrachytherapy.aspx)

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

  19. AUTHOR GUIDELINES

    Directory of Open Access Journals (Sweden)

    Chief Editor

    2014-12-01

    Full Text Available AUTHOR GUIDELINESIndian Journal of Community Health (IJCH accepts only online submission of manuscript(s by using Open Journal software (OJS at http://www.iapsmupuk.org/journal/index.php/IJCH/loginOnline SubmissionsAlready have a Username/Password for Indian Journal of Community Health (IJCH? GO TO LOGINNeed a Username/Password?GO TO REGISTRATIONNote: Registration and login are required to submit items online and to track the status of current submissions.Author GuidelinesIJCH strictly adheres on the recommendations for the Conduct, Reporting, Editing and Publication of Scholarly Work in Medical Journals as per the standard universal guidelines given by International Committee of Medical Journal Editors (ICMJE - Recommendations for Uniform Requirements for Manuscripts. Authors are requested to visit http://www.icmje.org/index.html before making online submission of their manuscript(s.SectionsEditorial:On issues of current public health needAbout 1000 – 1200 wordsReferences: 5 – 10 (PubMed - Citation preferredInvited Commentary:Brief, provocative, opinionated communicationsOn issues of current public health needMain Text: 750-1000 words excluding referencesReferences: 5 – 10 (PubMed - Citation preferredOriginal Article:Articles from Original ResearchStructured abstract: 250 wordsMain Text: 2500 - 3000 words, IMRD formatKey Words: 5 - 8References: 20 – 25 (PubMed - Citation preferredTables / Figures: 3 – 4*Certificate of clearance from respective Institutional Ethical Committee (IECReview Article:On subject of public health relevanceAbstract: 250 wordsMain Text: 2500 - 3000 wordsKey Words: 3 - 4References: 20 – 25 (PubMed - Citation preferredTables / Figures: 3 – 4Short Communication / Article:Short report of a research project / outbreakMain Text : 1000 – 1200 wordsReferences: 10 – 15 (PubMed - Citation preferredTable / Figure: 01*Certificate of clearance from respective Institutional Ethical Committee (IECReport from the field

  20. Software Quality in the Objectory Software Development Process

    NARCIS (Netherlands)

    van den Berg, Klaas; Demeyer, S.; Bosch, J.

    In this paper we discuss how software quality assurance is realized in Rational Objectory. Although much support is given through guidelines and checkpoints, the tool fails to provide clear goals and metrics for quality assessments and it only partially supports the phases in a measurement program.

  1. Technical support for GEIS: radioactive waste isolation in geologic formations. Volume 20. Thermo-mechanical stress analysis and development of thermal loading guidelines

    International Nuclear Information System (INIS)

    1978-04-01

    This volume is one of a 23-volume series which supplements a Contribution to Draft Generic Environmental Impact Statement on Commercial Waste Management: Radioactive Waste Isolation in Geologic Formations, Y/OWI/TM-44. The series provides a more complete technical basis for the preconceptual designs, resource requirements, and environmental source terms associated with isolating commercial LWR wastes in underground repositories in salt, granite, shale and basalt. Wastes are considered from three fuel cycles: uranium and plutonium recycling, no recycling of spent fuel, and uranium-only recycling. The thermo-mechanical analysis of proposed preconceptual repositories in granite, shale and basalt have been undertaken. The analysis, was conducted on three different levels of scale (i) Very Near Field (canister scale), (ii) Near Field (excavation scale) and (iii) Far Field (regional scale) studies. Three numerical methods were used to undertake the thermo-mechanical calculations; namely, the finite element method for thermal stress analysis, the boundary element method for thermal and thermal stress analysis and the semi-analytical method also for thermal and thermal stresses analysis. From the thermo-mechanical studies with simplifying assumptions on rock mass behavior where applicable, recommendations for areal thermal loadings to assure retrievability of the canisters and long term safety of the repository are given

  2. Development document for the effluent limitations and guidelines for the ore mining and dressing point source category. Volume I. Final report

    International Nuclear Information System (INIS)

    Jarrett, B.M.; Kirby, R.G.

    1978-07-01

    To establish effluent limitation guidelines and standards of performance, the ore mining and dressing industry was divided into 41 separate categories and subcategories for which separate limitations were recommended. This report deals with the entire metal-ore mining and dressing industry and examines the industry by ten major categories: iron ore; copper ore; lead and zinc ores; gold ore; silver ore; bauxite ore; ferroalloy-metal ores; mercury ores; uranium, radium and vanadium ores; and metal ores, not elsewhere classified ((ores of antimony, beryllium, pltinum, rare earths, tin, titanium, and zirconium). The subcategorization of the ore categories is based primarily upon ore mineralogy and processing or extraction methods employed; however, other factors (such as size, climate or location, and method of mining) are used in some instances. With the best available technology economically achievable, facilities in 21 of the 41 subcategories can be operated with no discharge of process wastewater to navigable waters. No discharge of process wastewater is also achievable as a new source performance standard for facilities in 21 of the 41 subcategories

  3. Dietary guidelines

    DEFF Research Database (Denmark)

    Jelsøe, Erling

    2015-01-01

    Dietary guidelines are issued regularly in most developed countries. In almost all cases they are concerned solely with the nutritional aspects of food and eating and are based on an understanding of food exclusively as a source of nutrients. In recent years, however, a growing number of proposals...... in a number of countries have addressed the issue of making dietary guidelines that integrate health and sustainability, but in all cases they have been met with different kinds of resistance. This article reviews the development towards an integrated understanding of health and sustainability in relation...... to food and eating and the emergence of proposals for integrated guidelines. It explores the conflicts and controversies that have arisen in the wake of the various proposals and identifies a number of different types of conflicts. These relate to conflicts of interests between the various actors involved...

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

  5. CAD-guidelines

    International Nuclear Information System (INIS)

    Schlechtendahl, E.G.; Lang-Lendorff, G.

    1982-10-01

    The CAD-guidelines (CAD = Computer Aided Design) contain rules for programming, structuring and documentation of programs. The standard deals with the structure of CAD-programs, their components, the programming-methods, the language etc. It describes what documents and references are necessary for a CAD-program. In order to gain a broad application of CAD criteria like portability and completeness of the documentation for an effective maintenance are as important as a transparent way of producing CAD-software. (orig.) [de

  6. Software Reviews.

    Science.gov (United States)

    McGrath, Diane

    1990-01-01

    Reviews two programs: (1) "The Weather Machine" on understanding weather and weather forecasting and (2) "The Mystery of the Hotel Victoria" on problem solving in mathematics. Presents the descriptions, advantages, and weaknesses of the software. (YP)

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

  8. Software Reviews.

    Science.gov (United States)

    Slatta, Richard W. And Others

    1987-01-01

    Describes a variety of computer software. Subjects reviewed include history simulations and wordprocessing programs. Some of the eleven packages reviewed are Thog, North Utilities, HBJ Writer, Textra, Pro-cite, and Simulation Construction Kit. (BSR)

  9. Software Reviews.

    Science.gov (United States)

    Wulfson, Stephen, Ed.

    1990-01-01

    Reviewed are six computer software packages including "Lunar Greenhouse,""Dyno-Quest,""How Weather Works,""Animal Trackers,""Personal Science Laboratory," and "The Skeletal and Muscular Systems." Availability, functional, and hardware requirements are discussed. (CW)

  10. Software Reviews.

    Science.gov (United States)

    Dwyer, Donna; And Others

    1989-01-01

    Reviewed are seven software packages for Apple and IBM computers. Included are: "Toxicology"; "Science Corner: Space Probe"; "Alcohol and Pregnancy"; "Science Tool Kit Plus"; Computer Investigations: Plant Growth"; "Climatrolls"; and "Animal Watch: Whales." (CW)

  11. Twenty-second water reactor safety information meeting: Proceedings. Volume 1: Plenary session; Advanced instrumentation and control hardware and software; Human factors research; IPE and PRA

    Energy Technology Data Exchange (ETDEWEB)

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

    1995-04-01

    This three-volume report contains papers presented at the Twenty-Second Water Reactor Safety Information Meeting held at the Bethesda Marriott Hotel, Bethesda, Maryland, during the week of October 24--26, 1994. 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 Finland, France, Italy, Japan, Russia, and United Kingdom. The titles of the papers and the names of the authors have been updated and may differ from those that appeared in the final program of the meeting. Selected papers are indexed separately for inclusion in the Energy Science and Technology Database.

  12. Twenty-second water reactor safety information meeting: Proceedings. Volume 1: Plenary session; Advanced instrumentation and control hardware and software; Human factors research; IPE and PRA

    International Nuclear Information System (INIS)

    Monteleone, S.

    1995-04-01

    This three-volume report contains papers presented at the Twenty-Second Water Reactor Safety Information Meeting held at the Bethesda Marriott Hotel, Bethesda, Maryland, during the week of October 24--26, 1994. 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 Finland, France, Italy, Japan, Russia, and United Kingdom. The titles of the papers and the names of the authors have been updated and may differ from those that appeared in the final program of the meeting. Selected papers are indexed separately for inclusion in the Energy Science and Technology Database

  13. CONRAD Software Architecture

    Science.gov (United States)

    Guzman, J. C.; Bennett, T.

    2008-08-01

    The Convergent Radio Astronomy Demonstrator (CONRAD) is a collaboration between the computing teams of two SKA pathfinder instruments, MeerKAT (South Africa) and ASKAP (Australia). Our goal is to produce the required common software to operate, process and store the data from the two instruments. Both instruments are synthesis arrays composed of a large number of antennas (40 - 100) operating at centimeter wavelengths with wide-field capabilities. Key challenges are the processing of high volume of data in real-time as well as the remote mode of operations. Here we present the software architecture for CONRAD. Our design approach is to maximize the use of open solutions and third-party software widely deployed in commercial applications, such as SNMP and LDAP, and to utilize modern web-based technologies for the user interfaces, such as AJAX.

  14. Software Innovation

    DEFF Research Database (Denmark)

    Rose, Jeremy

      Innovation is the forgotten key to modern systems development - the element that defines the enterprising engineer, the thriving software firm and the cutting edge software application.  Traditional forms of technical education pay little attention to creativity - often encouraging overly ratio...... out the new field of software innovation. It organizes the existing scientific research into eight simple heuristics - guiding principles for organizing a system developer's work-life so that it focuses on innovation.......  Innovation is the forgotten key to modern systems development - the element that defines the enterprising engineer, the thriving software firm and the cutting edge software application.  Traditional forms of technical education pay little attention to creativity - often encouraging overly...... rationalistic ways of thinking which stifle the ability to innovate. Professional software developers are often drowned in commercial drudgery and overwhelmed by work pressure and deadlines. The topic that will both ensure success in the market and revitalize their work lives is never addressed. This book sets...

  15. Improving system quality through software evaluation.

    Science.gov (United States)

    McDaniel, James G

    2002-05-01

    The role of evaluation is examined with respect to quality of software in healthcare. Of particular note is the failure of the Therac-25 radiation therapy machine. This example provides evidence of several types of defect which could have been detected and corrected using appropriate evaluation procedures. The field of software engineering has developed metrics and guidelines to assist in software evaluation but this example indicates that software evaluation must be extended beyond the formally defined interfaces of the software to its real-life operating context.

  16. How the NWC handles software as product

    Energy Technology Data Exchange (ETDEWEB)

    Vinson, D.

    1997-11-01

    This tutorial provides a hands-on view of how the Nuclear Weapons Complex project should be handling (or planning to handle) software as a product in response to Engineering Procedure 401099. The SQAS has published the document SQAS96-002, Guidelines for NWC Processes for Handling Software Product, that will be the basis for the tutorial. The primary scope of the tutorial is on software products that result from weapons and weapons-related projects, although the information presented is applicable to many software projects. Processes that involve the exchange, review, or evaluation of software product between or among NWC sites, DOE, and external customers will be described.

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

  18. Methodological guidelines

    International Nuclear Information System (INIS)

    Halsnaes, K.; Callaway, J.M.; Meyer, H.J.

    1999-01-01

    The guideline document establishes a general overview of the main components of climate change mitigation assessment. This includes an outline of key economic concepts, scenario structure, common assumptions, modelling tools and country study assumptions. The guidelines are supported by Handbook Reports that contain more detailed specifications of calculation standards, input assumptions and available tools. The major objectives of the project have been provided a methodology, an implementing framework and a reporting system which countries can follow in meeting their future reporting obligations under the FCCC and for GEF enabling activities. The project builds upon the methodology development and application in the UNEP National Abatement Coasting Studies (UNEP, 1994a). The various elements provide countries with a road map for conducting climate change mitigation studies and submitting national reports as required by the FCCC. (au) 121 refs

  19. Methodological guidelines

    Energy Technology Data Exchange (ETDEWEB)

    Halsnaes, K.; Callaway, J.M.; Meyer, H.J.

    1999-04-01

    The guideline document establishes a general overview of the main components of climate change mitigation assessment. This includes an outline of key economic concepts, scenario structure, common assumptions, modelling tools and country study assumptions. The guidelines are supported by Handbook Reports that contain more detailed specifications of calculation standards, input assumptions and available tools. The major objectives of the project have been provided a methodology, an implementing framework and a reporting system which countries can follow in meeting their future reporting obligations under the FCCC and for GEF enabling activities. The project builds upon the methodology development and application in the UNEP National Abatement Coasting Studies (UNEP, 1994a). The various elements provide countries with a road map for conducting climate change mitigation studies and submitting national reports as required by the FCCC. (au) 121 refs.

  20. MIAWARE Software

    DEFF Research Database (Denmark)

    Wilkowski, Bartlomiej; Pereira, Oscar N. M.; Dias, Paulo

    2008-01-01

    This article presents MIAWARE, a software for Medical Image Analysis With Automated Reporting Engine, which was designed and developed for doctor/radiologist assistance. It allows to analyze an image stack from computed axial tomography scan of lungs (thorax) and, at the same time, to mark all...... is automatically generated. Furthermore, MIAWARE software is accompanied with an intelligent search engine for medical reports, based on the relations between parts of the lungs. A logical structure of the lungs is introduced to the search algorithm through the specially developed ontology. As a result...... pathologies on images and report their characteristics. The reporting process is normalized - radiologists cannot describe pathological changes with their own words, but can only use some terms from a specific vocabulary set provided by the software. Consequently, a normalized radiological report...

  1. Model-based software process improvement

    Science.gov (United States)

    Zettervall, Brenda T.

    1994-01-01

    The activities of a field test site for the Software Engineering Institute's software process definition project are discussed. Products tested included the improvement model itself, descriptive modeling techniques, the CMM level 2 framework document, and the use of process definition guidelines and templates. The software process improvement model represents a five stage cyclic approach for organizational process improvement. The cycles consist of the initiating, diagnosing, establishing, acting, and leveraging phases.

  2. Jogging Guidelines.

    Science.gov (United States)

    President's Council on Physical Fitness and Sports, Washington, DC.

    Jogging guidelines are set forth under the following headings: a) What Is Jogging; c) Why One Should Jog; c) How To Begin; d) What To Wear (with the emphasis on proper shoes); e) When and Where To Jog; and f) How To Jog. A 16-week basic program, outlined for inactive adults, recommends for each week the number of days to exercise, the distance,…

  3. ASCOT guidelines

    International Nuclear Information System (INIS)

    1994-05-01

    These guidelines describe an approach used in conducting an Assessment of Safety Culture in Organizations Team (ASCOT) review. They are intended to assist the team members in conducting their reviews and at the same time provide guidance to hosts preparing to receive an ASCOT review. They may also be used by any organization wishing to conduct their own self-assessment of safety culture, independent of an ASCOT review

  4. Software engineering

    CERN Document Server

    Thorin, Marc

    1985-01-01

    Software Engineering describes the conceptual bases as well as the main methods and rules on computer programming. This book presents software engineering as a coherent and logically built synthesis and makes it possible to properly carry out an application of small or medium difficulty that can later be developed and adapted to more complex cases. This text is comprised of six chapters and begins by introducing the reader to the fundamental notions of entities, actions, and programming. The next two chapters elaborate on the concepts of information and consistency domains and show that a proc

  5. Top considerations for creating bioinformatics software documentation.

    Science.gov (United States)

    Karimzadeh, Mehran; Hoffman, Michael M

    2017-01-14

    Investing in documenting your bioinformatics software well can increase its impact and save your time. To maximize the effectiveness of your documentation, we suggest following a few guidelines we propose here. We recommend providing multiple avenues for users to use your research software, including a navigable HTML interface with a quick start, useful help messages with detailed explanation and thorough examples for each feature of your software. By following these guidelines, you can assure that your hard work maximally benefits yourself and others. © The Author 2017. Published by Oxford University Press.

  6. Communication from the Permanent Mission of the Russian Federation to the International Atomic Energy Agency regarding guidelines for transfers of nuclear-related dual-use equipment, materials, software and related technology

    International Nuclear Information System (INIS)

    2000-01-01

    The document reproduces the text of the Note Verbale received by the Director General of the IAEA from the Permanent Mission of the Russian Federation to the International Atomic Energy Agency providing information on the export policies and practices of the Government of the Russian Federation with respect to the export of nuclear-related dual-use equipment, materials, software and related technology

  7. Software engineering and Ada in design

    Science.gov (United States)

    Oneill, Don

    1986-01-01

    Modern software engineering promises significant reductions in software costs and improvements in software quality. The Ada language is the focus for these software methodology and tool improvements. The IBM FSD approach, including the software engineering practices that guide the systematic design and development of software products and the management of the software process are examined. The revised Ada design language adaptation is revealed. This four level design methodology is detailed including the purpose of each level, the management strategy that integrates the software design activity with the program milestones, and the technical strategy that maps the Ada constructs to each level of design. A complete description of each design level is provided along with specific design language recording guidelines for each level. Finally, some testimony is offered on education, tools, architecture, and metrics resulting from project use of the four level Ada design language adaptation.

  8. Clinical and anatomical guidelines in pelvic cancer contouring for radiotherapy treatment planning; Definition de regles simples anatomocliniques dans la determination du volume cible des tumeurs pelviennes pour le planning radiotherapeutique

    Energy Technology Data Exchange (ETDEWEB)

    Portaluri, M.; Bambace, S.; Giuliano, G.; Pili, G.; Didonna, V. [General Hospital Di Summa-Perrino, Dept. of Radiation Oncology, Medical Physics, Brindisi (Italy); Perez, C.; Angone, G.; Alloro, E. [General Hospital Di Summa-Perrino, Dept. of Radiology, Medical Physics, Brindisi (Italy); Scialpi, M. [General Hospital SS. Annunziata, Dept. of Radiology, Taranto (Italy)

    2004-08-01

    Background and purpose. Many observations on potential inadequate coverage of tumour volume at risk in advanced cervical cancer (CC) when conventional radiation fields are used, have further substantiated by investigators using MRI, CT or lymph-angiographic imaging. This work tries to obtain three dimensional margins by observing enlarged nodes in CT scans in order to improve pelvic nodal chains clinical target volumes (CTVs) drawing, and by looking for corroborative evidence in the literature for a better delineation of tumour CTV. Method. Eleven consecutive patients (seven males, four females, mean age 62 years, range 43 8) with CT diagnosis of nodal involvement caused by pathologically proved carcinoma of the cervix (n = 2), carcinoma of the rectum (n = 2), carcinoma of the prostate (n = 2), non-Hodgkin lymphoma (n 2), Hodgkin lymphoma (n = 1), carcinoma of the penis (n = 1) and carcinoma of the corpus uteri (n = 1) were retrospectively reviewed. Sixty CT scans with 67 enlarged pelvic nodes were reviewed in order to record the more proximal structures (muscle, bone, vessels, cutis or sub-cutis and other organs) to each enlarged node or group of nodes according to the four surfaces (anterior, lateral, posterior and medial) in a clockwise direction. Results. summary of the observations of each nodal chain and the number of occurrences of every marginal structure on axial CT slices is presented. Finally, simple guidelines are proposed. Conclusions. Tumour CTV should be based on individual tumour anatomy mainly for lateral beams as it results from sagittal T2 weighted MRI images. Boundaries of pelvic nodes CTVs can be derived from observations of enlarged lymph nodes in CT scans. (author)

  9. Software Reviews.

    Science.gov (United States)

    Science Software Quarterly, 1984

    1984-01-01

    Provides extensive reviews of computer software, examining documentation, ease of use, performance, error handling, special features, and system requirements. Includes statistics, problem-solving (TK Solver), label printing, database management, experimental psychology, Encyclopedia Britannica biology, and DNA-sequencing programs. A program for…

  10. Educational Software.

    Science.gov (United States)

    Northwest Regional Educational Lab., Portland, OR.

    The third session of IT@EDU98 consisted of five papers on educational software and was chaired by Tran Van Hao (University of Education, Ho Chi Minh City, Vietnam). "Courseware Engineering" (Nguyen Thanh Son, Ngo Ngoc Bao Tran, Quan Thanh Tho, Nguyen Hong Lam) briefly describes the use of courseware. "Machine Discovery Theorems in Geometry: A…

  11. Prefabricated vertical drains, vol. I : engineering guidelines.

    Science.gov (United States)

    1986-09-01

    This volume presents procedures and guidelines applicable to the design and instal : tion of prefabricated vertical drains to accelerate consolidation of soils. The : contents represent the Consultant's interpretation of the state-of-the-art as of : ...

  12. A survey of Canadian medical physicists: software quality assurance of in-house software.

    Science.gov (United States)

    Salomons, Greg J; Kelly, Diane

    2015-01-05

    This paper reports on a survey of medical physicists who write and use in-house written software as part of their professional work. The goal of the survey was to assess the extent of in-house software usage and the desire or need for related software quality guidelines. The survey contained eight multiple-choice questions, a ranking question, and seven free text questions. The survey was sent to medical physicists associated with cancer centers across Canada. The respondents to the survey expressed interest in having guidelines to help them in their software-related work, but also demonstrated extensive skills in the area of testing, safety, and communication. These existing skills form a basis for medical physicists to establish a set of software quality guidelines.

  13. Framework for Small-Scale Experiments in Software Engineering: Guidance and Control Software Project: Software Engineering Case Study

    Science.gov (United States)

    Hayhurst, Kelly J.

    1998-01-01

    Software is becoming increasingly significant in today's critical avionics systems. To achieve safe, reliable software, government regulatory agencies such as the Federal Aviation Administration (FAA) and the Department of Defense mandate the use of certain software development methods. However, little scientific evidence exists to show a correlation between software development methods and product quality. Given this lack of evidence, a series of experiments has been conducted to understand why and how software fails. The Guidance and Control Software (GCS) project is the latest in this series. The GCS project is a case study of the Requirements and Technical Concepts for Aviation RTCA/DO-178B guidelines, Software Considerations in Airborne Systems and Equipment Certification. All civil transport airframe and equipment vendors are expected to comply with these guidelines in building systems to be certified by the FAA for use in commercial aircraft. For the case study, two implementations of a guidance and control application were developed to comply with the DO-178B guidelines for Level A (critical) software. The development included the requirements, design, coding, verification, configuration management, and quality assurance processes. This paper discusses the details of the GCS project and presents the results of the case study.

  14. Software preservation

    Directory of Open Access Journals (Sweden)

    Tadej Vodopivec

    2011-01-01

    Full Text Available Comtrade Ltd. covers a wide range of activities related to information and communication technologies; its deliverables include web applications, locally installed programs,system software, drivers, embedded software (used e.g. in medical devices, auto parts,communication switchboards. Also the extensive knowledge and practical experience about digital long-term preservation technologies have been acquired. This wide spectrum of activities puts us in the position to discuss the often overlooked aspect of the digital preservation - preservation of software programs. There are many resources dedicated to digital preservation of digital data, documents and multimedia records,but not so many about how to preserve the functionalities and features of computer programs. Exactly these functionalities - dynamic response to inputs - render the computer programs rich compared to documents or linear multimedia. The article opens the questions on the beginning of the way to the permanent digital preservation. The purpose is to find a way in the right direction, where all relevant aspects will be covered in proper balance. The following questions are asked: why at all to preserve computer programs permanently, who should do this and for whom, when we should think about permanent program preservation, what should be persevered (such as source code, screenshots, documentation, and social context of the program - e.g. media response to it ..., where and how? To illustrate the theoretic concepts given the idea of virtual national museum of electronic banking is also presented.

  15. Establishing software quality assurance

    International Nuclear Information System (INIS)

    Malsbury, J.

    1983-01-01

    This paper is concerned with four questions about establishing software QA: What is software QA. Why have software QA. What is the role of software QA. What is necessary to ensure the success of software QA

  16. Towards a Controlled Vocabulary on Software Engineering Education

    Science.gov (United States)

    Pizard, Sebastián; Vallespir, Diego

    2017-01-01

    Software engineering is the discipline that develops all the aspects of the production of software. Although there are guidelines about what topics to include in a software engineering curricula, it is usually unclear which are the best methods to teach them. In any science discipline the construction of a classification schema is a common…

  17. Communication from the Permanent Mission of the Russian Federation to the International Atomic Energy Agency regarding guidelines for transfers of nuclear-related dual-use equipment, materials, software and related technology

    International Nuclear Information System (INIS)

    2001-01-01

    The Director General of the International Atomic Energy Agency has received a Note Verbale from the Permanent Mission of the Russian Federation providing information on the export policies and practices of the Government of the Russian Federation with respect to the export of nuclear-related dual-use equipment, materials, software and related technology. In the light of the wish expressed at the end of the Note Verbale, the text of the Note Verbale is attached. The attachment to the Note Verbale was issued previously as INFCIRC/2541Rev. 4/Part 2

  18. Communication from the Permanent Missions of Brazil and Romania to the International Atomic Energy Agency Regarding Guidelines for the Transfers of Nuclear-Related Dual-Use Equipment, Materials, Software and Related Technology

    International Nuclear Information System (INIS)

    2003-01-01

    The Director General of the International Atomic Energy Agency has received Notes Verbale from the Permanent Missions of Brazil and Romania, dated 28 February 2003, providing information on the export policies and practices of the Governments of Brazil and Romania with respect to the export of nuclear-related dual-use equipment, materials, software and related technology. In the light of the wish expressed at the end of each Note Verbale, the text of the Notes Verbale is attached. The attachment referenced in the Note Verbale was issued previously as INFCIRC/254/Rev.5/Part 2

  19. The ANS mathematics and computation software standards

    International Nuclear Information System (INIS)

    Smetana, A. O.

    2006-01-01

    The Mathematics and Computations Div. of the American Nuclear Society sponsors the ANS-10 Standards Subcommittee. This subcommittee, which is part of the ANS Standards Committee, currently maintains three ANSI/ANS software standards. These standards are: Portability of Scientific and Engineering Software, ANS-10.2; Guidelines for the Verification and Validation of Scientific and Engineering Computer Programs for the Nuclear Industry, ANS-10.4; and Accommodating User Needs in Scientific and Engineering Computer Software Development, ANS-10.5. A fourth Standard, Documentation of Computer Software, ANS-10.3, is available as a historical Standard. (authors)

  20. Artificial Intelligence Software Acquisition Program. Volume 1.

    Science.gov (United States)

    1987-12-01

    formalize the concelpts, p: obl-ins and information flow into a iniore formal knowlodge representation which defines the data strittres, inference...imtrallcl with (,t(- developinent team, the test team translates the c us otneir spec iiica;t ii l to I- I procedures that trlodel the system behavior...task ait a~Ilo’ 4-llicien.N~ . FX.1I I I les- of Issies inItit Ivl: Ata I txectit iont of translated K( IIS programs, t tI at i. t.tit of .self

  1. A survey of Canadian medical physicists: software quality assurance of in‐house software

    Science.gov (United States)

    Kelly, Diane

    2015-01-01

    This paper reports on a survey of medical physicists who write and use in‐house written software as part of their professional work. The goal of the survey was to assess the extent of in‐house software usage and the desire or need for related software quality guidelines. The survey contained eight multiple‐choice questions, a ranking question, and seven free text questions. The survey was sent to medical physicists associated with cancer centers across Canada. The respondents to the survey expressed interest in having guidelines to help them in their software‐related work, but also demonstrated extensive skills in the area of testing, safety, and communication. These existing skills form a basis for medical physicists to establish a set of software quality guidelines. PACS number: 87.55.Qr PMID:25679168

  2. Software system safety

    Science.gov (United States)

    Uber, James G.

    1988-01-01

    Software itself is not hazardous, but since software and hardware share common interfaces there is an opportunity for software to create hazards. Further, these software systems are complex, and proven methods for the design, analysis, and measurement of software safety are not yet available. Some past software failures, future NASA software trends, software engineering methods, and tools and techniques for various software safety analyses are reviewed. Recommendations to NASA are made based on this review.

  3. ASSET guidelines

    International Nuclear Information System (INIS)

    1990-11-01

    The IAEA Assessment of Safety Significant Events Team (ASSET) Service provides advice and assistance to Member States to enhance the overall level of plant safety while dealing with the policy of prevention of incidents at nuclear power plants. The ASSET programme, initiated in 1986, is not restricted to any particular group of Member States, whether developing or industrialized, but is available to all countries with nuclear power plants in operation or approaching commercial operation. The IAEA Safety Series publications form common basis for the ASSET reviews, including the Nuclear Safety Standards (NUSS) and the Basic Safety Principles (Recommendations of Safety Series No. 75-INSAG-3). The ASSET Guidelines provide overall guidance for the experts to ensure the consistency and comprehensiveness of their review of incident investigations. Additional guidance and reference material is provided by the IAEA to complement the expertise of the ASSET members. ASSET reviews accept different approaches that contribute to ensuring an effective prevention of incidents at plants. Suggestions are offered to enhance plant safety performance. Commendable good practices are identified and generic lessons are communicated to other plants, where relevant, for long term improvement

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

  5. Software Support for the Classical, Contemporary and Future Project Management

    Directory of Open Access Journals (Sweden)

    Jakov Crnkovic

    2006-04-01

    Full Text Available The volume and complexity of Project Management (PM raises many questions for managers. What exactly are we managing? People? Performance? Efficiency? Effectiveness? Cost? Time? At what levels do projects become challenging and worthy of significant management attention? Can some projects be left on auto-pilot? Must others be managed more aggressively? What metrics are useful in Project Management? How can they be integrated with normal performance metrics in the organization? How can metrics be built into assessment programs that work? How can projects be monitored, re-planned to stay within the original budget and schedule deadlines? How good is the PM software support? Do we really need PM software packages or it should be the integral part of the company's information system (IS? Where is the knowledge about company's previous projects and performance? Are we able to establish company or even industry wide standards for project management? Can we (or should we move from the PMBOK® guidelines and use other approaches? We discussing important questions in PM: software products, responsibilities for concurrently executing several projects (multi-projects with multi objectives and multiple deadlines, introducing a need for initiation, design, execution, and control using a virtual project management and application of the organizational project maturity model.

  6. Software not as a service

    Science.gov (United States)

    Teal, Tracy

    2017-01-01

    With the expansion in the variety, velocity and volume of data being produced, computing and software development has become a crucial element of astronomy research. However, while we value the research, we place less importance on the development of the software itself, viewing software as a service to research. By viewing software as a service, we derate the effort and expertise it takes to produce, and the training required, for effective research computing. We also don’t provide support for the people doing the development, often expecting individual developers to provide systems administration, user support and training and produce documentation and user interfaces. With our increased reliance on research computing, accurate and reproducible research requires that software not be separate from the act of conducting research, but an integral component - a part of, rather than a service to research. Shifts in how we provide data skills and software development training, integrate development into research programs and academic departments and value software as a product can have an impact on the quality, creativity and types of research we can conduct.

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

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

    .onsolidate, collect and, if needed, develop common processes principles and other assets across the Agency in order to provide more consistency in software development and acquisition practices and to reduce the overall cost of maintaining or increasing current NASA CMMI maturity levels. 6. Provide additional support for small projects that includes: (a) guidance for appropriate tailoring of requirements for small projects, (b) availability of suitable tools, including support tool set-up and training, and (c) training for small project personnel, assurance personnel and technical authorities on the acceptable options for tailoring requirements and performing assurance on small projects. 7. Develop software training classes for the more experienced software engineers using on-line training, videos, or small separate modules of training that can be accommodated as needed throughout a project. 8. Create guidelines to structure non-classroom training opportunities such as mentoring, peer reviews, lessons learned sessions, and on-the-job training. 9. Develop a set of predictive software defect data and a process for assessing software testing metric data against it. 10. Assess Agency-wide licenses for commonly used software tools. 11. Fill the knowledge gap in common software engineering practices for new hires and co-ops.12. Work through the Science, Technology, Engineering and Mathematics (STEM) program with universities in strengthening education in the use of common software engineering practices and standards. 13. Follow up this benchmark study with a deeper look into what both internal and external organizations perceive as the scope of software assurance, the value they expect to obtain from it, and the shortcomings they experience in the current practice. 14. Continue interactions with external software engineering environment through collaborations, knowledge sharing, and benchmarking.

  9. Guidelines for PCC inputs to AASHTOWare Pavement ME.

    Science.gov (United States)

    2014-12-01

    The objective of this research study was to develop guidelines for portland cement concrete (PCC) material inputs to the : AASHTOWare Pavement ME Design program. The AASHTOWare Pavement ME Design is the software program used by the : Mississippi Depa...

  10. Advances in software science and technology

    CERN Document Server

    Hikita, Teruo; Kakuda, Hiroyasu

    1993-01-01

    Advances in Software Science and Technology, Volume 4 provides information pertinent to the advancement of the science and technology of computer software. This book discusses the various applications for computer systems.Organized into two parts encompassing 10 chapters, this volume begins with an overview of the historical survey of programming languages for vector/parallel computers in Japan and describes compiling methods for supercomputers in Japan. This text then explains the model of a Japanese software factory, which is presented by the logical configuration that has been satisfied by

  11. Software ecosystems analyzing and managing business networks in the software industry

    CERN Document Server

    Jansen, S; Cusumano, MA

    2013-01-01

    This book describes the state-of-the-art of software ecosystems. It constitutes a fundamental step towards an empirically based, nuanced understanding of the implications for management, governance, and control of software ecosystems. This is the first book of its kind dedicated to this emerging field and offers guidelines on how to analyze software ecosystems; methods for managing and growing; methods on transitioning from a closed software organization to an open one; and instruments for dealing with open source, licensing issues, product management and app stores. It is unique in bringing t

  12. Strategies for Using Plagiarism Software in the Screening of Incoming Journal Manuscripts

    DEFF Research Database (Denmark)

    Lykkesfeldt, Jens

    2016-01-01

    In recent years, several online tools have appeared capable of identifying potential plagiarism in science. While such tools may help to maintain or even increase the originality and ethical quality of the scientific literature, no apparent consensus exists among editors on the degree of plagiarism...... or self-plagiarism necessary to reject or retract manuscripts. In this study, two entire volumes of published original papers and reviews from Basic & Clinical Pharmacology & Toxicology were retrospectively scanned for similarity in anonymized form using iThenticate software to explore measures...... to predictively identify true plagiarism and self-plagiarism and to potentially provide guidelines for future screening of incoming manuscripts. Several filters were applied, all of which appeared to lower the noise from irrelevant hits. The main conclusions were that plagiarism software offers a unique...

  13. The software life cycle

    CERN Document Server

    Ince, Darrel

    1990-01-01

    The Software Life Cycle deals with the software lifecycle, that is, what exactly happens when software is developed. Topics covered include aspects of software engineering, structured techniques of software development, and software project management. The use of mathematics to design and develop computer systems is also discussed. This book is comprised of 20 chapters divided into four sections and begins with an overview of software engineering and software development, paying particular attention to the birth of software engineering and the introduction of formal methods of software develop

  14. Software and Network Engineering

    CERN Document Server

    2012-01-01

    The series "Studies in Computational Intelligence" (SCI) publishes new developments and advances in the various areas of computational intelligence – quickly and with a high quality. The intent is to cover the theory, applications, and design methods of computational intelligence, as embedded in the fields of engineering, computer science, physics and life science, as well as the methodologies behind them. The series contains monographs, lecture notes and edited volumes in computational intelligence spanning the areas of neural networks, connectionist systems, genetic algorithms, evolutionary computation, artificial intelligence, cellular automata, self-organizing systems, soft computing, fuzzy systems, and hybrid intelligent systems. Critical to both contributors and readers are the short publication time and world-wide distribution - this permits a rapid and broad dissemination of research results.   The purpose of the first ACIS International Symposium on Software and Network Engineering held on Decembe...

  15. Software attribute visualization for high integrity software

    Energy Technology Data Exchange (ETDEWEB)

    Pollock, G.M.

    1998-03-01

    This report documents a prototype tool developed to investigate the use of visualization and virtual reality technologies for improving software surety confidence. The tool is utilized within the execution phase of the software life cycle. It provides a capability to monitor an executing program against prespecified requirements constraints provided in a program written in the requirements specification language SAGE. The resulting Software Attribute Visual Analysis Tool (SAVAnT) also provides a technique to assess the completeness of a software specification.

  16. NASA Aerospace Flight Battery Program: Generic Safety, Handling and Qualification Guidelines for Lithium-Ion (Li-Ion) Batteries; Availability of Source Materials for Lithium-Ion (Li-Ion) Batteries; Maintaining Technical Communications Related to Aerospace Batteries (NASA Aerospace Battery Workshop). Volume 1, Part 1

    Science.gov (United States)

    Manzo, Michelle A.; Brewer, Jeffrey C.; Bugga, Ratnakumar V.; Darcy, Eric C.; Jeevarajan, Judith A.; McKissock, Barbara I.; Schmitz, Paul C.

    2010-01-01

    This NASA Aerospace Flight Battery Systems Working Group was chartered within the NASA Engineering and Safety Center (NESC). The Battery Working Group was tasked to complete tasks and to propose proactive work to address battery related, agency-wide issues on an annual basis. In its first year of operation, this proactive program addressed various aspects of the validation and verification of aerospace battery systems for NASA missions. Studies were performed, issues were discussed and in many cases, test programs were executed to generate recommendations and guidelines to reduce risk associated with various aspects of implementing battery technology in the aerospace industry. This document contains Part 1 - Volume I: Generic Safety, Handling and Qualification Guidelines for Lithium-Ion (Li-Ion) Batteries, Availability of Source Materials for Lithium-Ion (Li-Ion) Batteries, and Maintaining Technical Communications Related to Aerospace Batteries (NASA Aerospace Battery Workshop).

  17. Reliability of software

    International Nuclear Information System (INIS)

    Kopetz, H.

    1980-01-01

    Common factors and differences in the reliability of hardware and software; reliability increase by means of methods of software redundancy. Maintenance of software for long term operating behavior. (HP) [de

  18. Controlling Software Piracy.

    Science.gov (United States)

    King, Albert S.

    1992-01-01

    Explains what software manufacturers are doing to combat software piracy, recommends how managers should deal with this problem, and provides a role-playing exercise to help students understand the issues in software piracy. (SR)

  19. Space Flight Software Development Software for Intelligent System Health Management

    Science.gov (United States)

    Trevino, Luis C.; Crumbley, Tim

    2004-01-01

    The slide presentation examines the Marshall Space Flight Center Flight Software Branch, including software development projects, mission critical space flight software development, software technical insight, advanced software development technologies, and continuous improvement in the software development processes and methods.

  20. Software Metrics: Measuring Haskell

    OpenAIRE

    Ryder, Chris; Thompson, Simon

    2005-01-01

    Software metrics have been used in software engineering as a mechanism for assessing code quality and for targeting software development activities, such as testing or refactoring, at areas of a program that will most benefit from them. Haskell has many tools for software engineering, such as testing, debugging and refactoring tools, but software metrics have mostly been neglected. The work presented in this paper identifies a collection of software metrics for use with Haskell programs. Thes...

  1. Software systems as cities

    OpenAIRE

    Wettel, Richard; Lanza, Michele

    2010-01-01

    Software understanding takes up a large share of the total cost of a software system. The high costs attributed to software understanding activities are caused by the size and complexity of software systems, by the continuous evolution that these systems are subject to, and by the lack of physical presence which makes software intangible. Reverse engineering helps practitioners deal with the intrinsic complexity of software, by providing a broad range of patterns and techniques. One of...

  2. Software Engineering Guidebook

    Science.gov (United States)

    Connell, John; Wenneson, Greg

    1993-01-01

    The Software Engineering Guidebook describes SEPG (Software Engineering Process Group) supported processes and techniques for engineering quality software in NASA environments. Three process models are supported: structured, object-oriented, and evolutionary rapid-prototyping. The guidebook covers software life-cycles, engineering, assurance, and configuration management. The guidebook is written for managers and engineers who manage, develop, enhance, and/or maintain software under the Computer Software Services Contract.

  3. 1987 Statement on Software Copyright: An ICCE Policy Statement.

    Science.gov (United States)

    Computing Teacher, 1987

    1987-01-01

    Building on the 1983 policy statement developed by the International Council for Computers in Education (ICCE), this statement recommends the adoption of a school district copyright policy, adoption of the suggested software use guidelines, and use of the copyright page of software documentation to ascertain user's rights, obligations, and licence…

  4. Software Intensive Systems

    National Research Council Canada - National Science Library

    Horvitz, E; Katz, D. J; Rumpf, R. L; Shrobe, H; Smith, T. B; Webber, G. E; Williamson, W. E; Winston, P. H; Wolbarsht, James L

    2006-01-01

    .... Recommend that DoN create a software acquisition specialty, mandate basic schooling for software acquisition specialists, close certain acquisition loopholes that permit poor development practices...

  5. Software Release Management

    National Research Council Canada - National Science Library

    Hoek, Andre van der; Hall, Richard S; Heimbigner, Dennis; Wolf, Alexander L

    1996-01-01

    .... Both developers and users of such software are affected by these complications. Developers need to accurately document complex and changing dependencies among the systems constituting the software...

  6. Verification and validation of control system software

    International Nuclear Information System (INIS)

    Munro, J.K. Jr.; Kisner, R.A.; Bhadtt, S.C.

    1991-01-01

    The following guidelines are proposed for verification and validation (V ampersand V) of nuclear power plant control system software: (a) use risk management to decide what and how much V ampersand V is needed; (b) classify each software application using a scheme that reflects what type and how much V ampersand V is needed; (c) maintain a set of reference documents with current information about each application; (d) use Program Inspection as the initial basic verification method; and (e) establish a deficiencies log for each software application. The following additional practices are strongly recommended: (a) use a computer-based configuration management system to track all aspects of development and maintenance; (b) establish reference baselines of the software, associated reference documents, and development tools at regular intervals during development; (c) use object-oriented design and programming to promote greater software reliability and reuse; (d) provide a copy of the software development environment as part of the package of deliverables; and (e) initiate an effort to use formal methods for preparation of Technical Specifications. The paper provides background information and reasons for the guidelines and recommendations. 3 figs., 3 tabs

  7. Physical Activity Guidelines

    Science.gov (United States)

    ... use this site. health.gov Physical Activity Guidelines Physical Activity Physical activity is key to improving the health of the Nation. Based on the latest science, the Physical Activity Guidelines for Americans is an essential resource ...

  8. Agile Processes in Software Engineering and Extreme Programming

    DEFF Research Database (Denmark)

    The volume constitutes the proceedings of the 18th International Conference on Agile Software Development, XP 2017, held in Cologne, Germany, in May 2017. The 14 full and 6 short papers presented in this volume were carefully reviewed and selected from 46 submissions. They were organized in topical...... sections named: improving agile processes; agile in organization; and safety critical software. In addition, the volume contains 3 doctoral symposium papers (from 4 papers submitted)....

  9. Software Testing Techniques and Strategies

    OpenAIRE

    Isha,; Sunita Sangwan

    2014-01-01

    Software testing provides a means to reduce errors, cut maintenance and overall software costs. Numerous software development and testing methodologies, tools, and techniques have emerged over the last few decades promising to enhance software quality. This paper describes Software testing, need for software testing, Software testing goals and principles. Further it describe about different Software testing techniques and different software testing strategies.

  10. Statistical Software Engineering

    Science.gov (United States)

    1998-04-13

    multiversion software subject to coincident errors. IEEE Trans. Software Eng. SE-11:1511-1517. Eckhardt, D.E., A.K Caglayan, J.C. Knight, L.D. Lee, D.F...J.C. and N.G. Leveson. 1986. Experimental evaluation of the assumption of independence in multiversion software. IEEE Trans. Software

  11. Agile Software Development

    Science.gov (United States)

    Biju, Soly Mathew

    2008-01-01

    Many software development firms are now adopting the agile software development method. This method involves the customer at every level of software development, thus reducing the impact of change in the requirement at a later stage. In this article, the principles of the agile method for software development are explored and there is a focus on…

  12. Ensuring Software IP Cleanliness

    Directory of Open Access Journals (Sweden)

    Mahshad Koohgoli

    2007-12-01

    Full Text Available At many points in the life of a software enterprise, determination of intellectual property (IP cleanliness becomes critical. The value of an enterprise that develops and sells software may depend on how clean the software is from the IP perspective. This article examines various methods of ensuring software IP cleanliness and discusses some of the benefits and shortcomings of current solutions.

  13. Improving Software Developer's Competence

    DEFF Research Database (Denmark)

    Abrahamsson, Pekka; Kautz, Karlheinz; Sieppi, Heikki

    2002-01-01

    Emerging agile software development methods are people oriented development approaches to be used by the software industry. The personal software process (PSP) is an accepted method for improving the capabilities of a single software engineer. Five original hypotheses regarding the impact...

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

  15. Software unit testing in Ada environment

    Science.gov (United States)

    Warnock, Glenn

    1986-01-01

    A validation procedure for the Ada binding of the Graphical Kernel System (GKS) is being developed. PRIOR Data Sciences is also producing a version of the GKS written in Ada. These major software engineering projects will provide an opportunity to demonstrate a sound approach for software testing in an Ada environment. The GKS/Ada validation capability will be a collection of test programs and data, and test management guidelines. These products will be used to assess the correctness, completeness, and efficiency of any GKS/Ada implementation. The GKS/Ada developers will be able to obtain the validation software for their own use. It is anticipated that this validation software will eventually be taken over by an independent standards body to provide objective assessments of GKS/Ada implementations, using an approach similar to the validation testing currently applied to Ada compilers. In the meantime, if requested, this validation software will be used to assess GKS/Ada products. The second project, implementation of GKS using the Ada language, is a conventional software engineering tasks. It represents a large body of Ada code and has some interesting testing problems associated with automatic testing of graphics routines. Here the normal test practices which include automated regression testing, independent quality assistance, test configuration management, and the application of software quality metrics will be employed. The software testing methods emphasize quality enhancement and automated procedures. Ada makes some aspects of testing easier, and introduces some concerns. These issues are addressed.

  16. Great software debates

    CERN Document Server

    Davis, A

    2004-01-01

    The industry’s most outspoken and insightful critic explains how the software industry REALLY works. In Great Software Debates, Al Davis, shares what he has learned about the difference between the theory and the realities of business and encourages you to question and think about software engineering in ways that will help you succeed where others fail. In short, provocative essays, Davis fearlessly reveals the truth about process improvement, productivity, software quality, metrics, agile development, requirements documentation, modeling, software marketing and sales, empiricism, start-up financing, software research, requirements triage, software estimation, and entrepreneurship.

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

  18. Software component quality evaluation

    Science.gov (United States)

    Clough, A. J.

    1991-01-01

    The paper describes a software inspection process that can be used to evaluate the quality of software components. Quality criteria, process application, independent testing of the process and proposed associated tool support are covered. Early results indicate that this technique is well suited for assessing software component quality in a standardized fashion. With automated machine assistance to facilitate both the evaluation and selection of software components, such a technique should promote effective reuse of software components.

  19. Views on Software Testability

    OpenAIRE

    Shimeall, Timothy; Friedman, Michael; Chilenski, John; Voas, Jeffrey

    1994-01-01

    The field of testability is an active, well-established part of engineering of modern computer systems. However, only recently have technologies for software testability began to be developed. These technologies focus on accessing the aspects of software that improve or depreciate the ease of testing. As both the size of implemented software and the amount of effort required to test that software increase, so will the important of software testability technologies in influencing the softwa...

  20. The new hypertension guidelines.

    Science.gov (United States)

    Stern, Ralph H

    2013-10-01

    The Canadian Hypertension Education Program (CHEP) has published guidelines annually since 2000. The CHEP guidelines are a model of concise, comprehensive, up-to-date, evidence-rated guidelines for physicians who diagnose and treat hypertension. The guidelines address measurement of blood pressure and the definition of hypertension, secondary hypertension evaluation and treatment, and blood pressure targets and medication choices in patients with and without compelling indications. This review describes CHEP's process for developing guidelines and provides an overview of the 2013 recommendations. ©2013 Wiley Periodicals, Inc.

  1. Guidelines and workbook for of organization and administration of utilities seeking operating license for a nuclear power plant. Workbook for assessment of organization and management. Volume, 2, Revision 1

    International Nuclear Information System (INIS)

    Thurber, J.A.; Olson, J.; Osborn, R.N.; Sommers, P.; Widrig, R.D.

    1986-09-01

    This report is a partial response to the requirements of Item I.B.1.1 of the ''NRC Action Plan Developed as a Result of the TMI-2 Accident,'' NUREG-0660, and is designed to serve as a basis for replacing the earlier NUREG-0731, ''Guidelines for Utility Management Structure and Technical Resources.'' The Guidelines are intended to provide guidance to the user in preparing a written plan for a proposed nuclear organization and administration. The purpose of the Workbook is to guide the NRC reviewer through a systematic review and assessment of a proposed organization and administration. It is the NRC's intention to incorporate these Guidelines and Workbook into a future revision of the Standard Review Plan (SRP), NUREG-0800. However, at this time the report is being published so that the material may be used on a voluntary basis by industry to systematically prepare or evaluate their organization or administration plans. Use of the report by the NRC would not occur until after it has been incorporated in the SRP

  2. Software safety analysis techniques for developing safety critical software in the digital protection system of the LMR

    Energy Technology Data Exchange (ETDEWEB)

    Lee, Jang Soo; Cheon, Se Woo; Kim, Chang Hoi; Sim, Yun Sub

    2001-02-01

    This report has described the software safety analysis techniques and the engineering guidelines for developing safety critical software to identify the state of the art in this field and to give the software safety engineer a trail map between the code and standards layer and the design methodology and documents layer. We have surveyed the management aspects of software safety activities during the software lifecycle in order to improve the safety. After identifying the conventional safety analysis techniques for systems, we have surveyed in details the software safety analysis techniques, software FMEA(Failure Mode and Effects Analysis), software HAZOP(Hazard and Operability Analysis), and software FTA(Fault Tree Analysis). We have also surveyed the state of the art in the software reliability assessment techniques. The most important results from the reliability techniques are not the specific probability numbers generated, but the insights into the risk importance of software features. To defend against potential common-mode failures, high quality, defense-in-depth, and diversity are considered to be key elements in digital I and C system design. To minimize the possibility of CMFs and thus increase the plant reliability, we have provided D-in-D and D analysis guidelines.

  3. Software safety analysis techniques for developing safety critical software in the digital protection system of the LMR

    International Nuclear Information System (INIS)

    Lee, Jang Soo; Cheon, Se Woo; Kim, Chang Hoi; Sim, Yun Sub

    2001-02-01

    This report has described the software safety analysis techniques and the engineering guidelines for developing safety critical software to identify the state of the art in this field and to give the software safety engineer a trail map between the code and standards layer and the design methodology and documents layer. We have surveyed the management aspects of software safety activities during the software lifecycle in order to improve the safety. After identifying the conventional safety analysis techniques for systems, we have surveyed in details the software safety analysis techniques, software FMEA(Failure Mode and Effects Analysis), software HAZOP(Hazard and Operability Analysis), and software FTA(Fault Tree Analysis). We have also surveyed the state of the art in the software reliability assessment techniques. The most important results from the reliability techniques are not the specific probability numbers generated, but the insights into the risk importance of software features. To defend against potential common-mode failures, high quality, defense-in-depth, and diversity are considered to be key elements in digital I and C system design. To minimize the possibility of CMFs and thus increase the plant reliability, we have provided D-in-D and D analysis guidelines

  4. Advances in software science and technology

    CERN Document Server

    Ohno, Yoshio; Kamimura, Tsutomu

    1991-01-01

    Advances in Software Science and Technology, Volume 2 provides information pertinent to the advancement of the science and technology of computer software. This book discusses the various applications for computer systems.Organized into four parts encompassing 12 chapters, this volume begins with an overview of categorical frameworks that are widely used to represent data types in computer science. This text then provides an algorithm for generating vertices of a smoothed polygonal line from the vertices of a digital curve or polygonal curve whose position contains a certain amount of error. O

  5. Advances in software science and technology

    CERN Document Server

    Kamimura, Tsutomu

    1994-01-01

    This serial is a translation of the original works within the Japan Society of Software Science and Technology. A key source of information for computer scientists in the U.S., the serial explores the major areas of research in software and technology in Japan. These volumes are intended to promote worldwide exchange of ideas among professionals.This volume includes original research contributions in such areas as Augmented Language Logic (ALL), distributed C language, Smalltalk 80, and TAMPOPO-an evolutionary learning machine based on the principles of Realtime Minimum Skyline Detection.

  6. Advances in software science and technology

    CERN Document Server

    Kakuda, Hiroyasu; Ohno, Yoshio

    1992-01-01

    Advances in Software Science and Technology, Volume 3 provides information pertinent to the advancement of the science and technology of computer software. This book discusses the various applications for computer systems.Organized into two parts encompassing 11 chapters, this volume begins with an overview of the development of a system of writing tools called SUIKOU that analyzes a machine-readable Japanese document textually. This text then presents the conditioned attribute grammars (CAGs) and a system for evaluating them that can be applied to natural-language processing. Other chapters c

  7. Japan society for software science and technology

    CERN Document Server

    Nakajima, Reiji; Hagino, Tatsuya

    1990-01-01

    Advances in Software Science and Technology, Volume 1 provides information pertinent to the advancement of the science and technology of computer software. This book discusses the various applications for computer systems.Organized into three parts encompassing 13 chapters, this volume begins with an overview of the phase structure grammar for Japanese called JPSG, and a parser based on this grammar. This text then explores the logic-based knowledge representation called Uranus, which uses a multiple world mechanism. Other chapters consider the optimal file segmentation techniques for multi-at

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

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

  10. Software Acquisition and Software Engineering Best Practices

    National Research Council Canada - National Science Library

    Eslinger, S

    1999-01-01

    ...) of Senate Report 106-50, is given for reference in Table 1-1 of the body of this report. This paper recommends a set of software acquisition and software engineering best practices that addresses the issues raised in the Senate Report...

  11. Amalgamation of Personal Software Process in Software ...

    African Journals Online (AJOL)

    Today, concern for quality has become an international movement. Even though most industrial organizations have now adopted modern quality principles, the software community has continued to rely on testing as the principal quality management method. Different decades have different trends in software engineering.

  12. From Software Development to Software Assembly

    NARCIS (Netherlands)

    Sneed, Harry M.; Verhoef, Chris

    2016-01-01

    The lack of skilled programming personnel and the growing burden of maintaining customized software are forcing organizations to quit producing their own software. It's high time they turned to ready-made, standard components to fulfill their business requirements. Cloud services might be one way to

  13. Software tool for physics chart checks.

    Science.gov (United States)

    Li, H Harold; Wu, Yu; Yang, Deshan; Mutic, Sasa

    2014-01-01

    Physics chart check has long been a central quality assurance (QC) measure in radiation oncology. The purpose of this work is to describe a software tool that aims to accomplish simplification, standardization, automation, and forced functions in the process. Nationally recognized guidelines, including American College of Radiology and American Society for Radiation Oncology guidelines and technical standards, and the American Association of Physicists in Medicine Task Group reports were identified, studied, and summarized. Meanwhile, the reported events related to physics chart check service were analyzed using an event reporting and learning system. A number of shortfalls in the chart check process were identified. To address these problems, a software tool was designed and developed under Microsoft. Net in C# to hardwire as many components as possible at each stage of the process. The software consists of the following 4 independent modules: (1) chart check management; (2) pretreatment and during treatment chart check assistant; (3) posttreatment chart check assistant; and (4) quarterly peer-review management. The users were a large group of physicists in the author's radiation oncology clinic. During over 1 year of use the tool has proven very helpful in chart checking management, communication, documentation, and maintaining consistency. The software tool presented in this work aims to assist physicists at each stage of the physics chart check process. The software tool is potentially useful for any radiation oncology clinics that are either in the process of pursuing or maintaining the American College of Radiology accreditation.

  14. Delineation of the primary tumour Clinical Target Volumes (CTV-P) in laryngeal, hypopharyngeal, oropharyngeal and oral cavity squamous cell carcinoma: AIRO, CACA, DAHANCA, EORTC, GEORCC, GORTEC, HKNPCSG, HNCIG, IAG-KHT, LPRHHT, NCIC CTG, NCRI, NRG Oncology, PHNS, SBRT, SOMERA, SRO, SSHNO, TROG consensus guidelines.

    Science.gov (United States)

    Grégoire, Vincent; Evans, Mererid; Le, Quynh-Thu; Bourhis, Jean; Budach, Volker; Chen, Amy; Eisbruch, Abraham; Feng, Mei; Giralt, Jordi; Gupta, Tejpal; Hamoir, Marc; Helito, Juliana K; Hu, Chaosu; Hunter, Keith; Johansen, Jorgen; Kaanders, Johannes; Laskar, Sarbani Ghosh; Lee, Anne; Maingon, Philippe; Mäkitie, Antti; Micciche', Francesco; Nicolai, Piero; O'Sullivan, Brian; Poitevin, Adela; Porceddu, Sandro; Składowski, Krzysztof; Tribius, Silke; Waldron, John; Wee, Joseph; Yao, Min; Yom, Sue S; Zimmermann, Frank; Grau, Cai

    2018-01-01

    Few studies have reported large inter-observer variations in target volume selection and delineation in patients treated with radiotherapy for head and neck squamous cell carcinoma. Consensus guidelines have been published for the neck nodes (see Grégoire et al., 2003, 2014), but such recommendations are lacking for primary tumour delineation. For the latter, two main schools of thoughts are prevailing, one based on geometric expansion of the Gross Tumour Volume (GTV) as promoted by DAHANCA, and the other one based on anatomical expansion of the GTV using compartmentalization of head and neck anatomy. For each anatomic location within the larynx, hypopharynx, oropharynx and oral cavity, and for each T-stage, the DAHANCA proposal has been comprehensively reviewed and edited to include anatomic knowledge into the geometric Clinical Target Volume (CTV) delineation concept. A first proposal was put forward by the leading authors of this publication (VG and CG) and discussed with opinion leaders in head and neck radiation oncology from Europe, Asia, Australia/New Zealand, North America and South America to reach a worldwide consensus. This consensus proposes two CTVs for the primary tumour, the so called CTV-P1 and CVT-P2, corresponding to a high and lower tumour burden, and which should be associated with a high and a lower dose prescription, respectively. Implementation of these guidelines in the daily practice of radiation oncology should contribute to reduce treatment variations from clinicians to clinicians, facilitate the conduct of multi-institutional clinical trials, and contribute to improved care of patients with head and neck carcinoma. Copyright © 2017 Elsevier B.V. All rights reserved.

  15. Evidence in dentistry guidelines

    Directory of Open Access Journals (Sweden)

    Cristiane Rufino Macedo

    Full Text Available CONTEXT AND OBJECTIVE: Guidelines are suggestions for clinical practice based on the best available scientific evidence. Nevertheless, in drafting such guidelines, existing systematic reviews are often ignored and are replaced by general consensuses. This ends up compromising the quality of the instructions through bias. Our objective was to investigate whether Cochrane systematic reviews were present among the bibliographic references of prevention and treatment guidelines for dentistry that have been published in databases. DESIGN AND SETTING: This retrospective, observational study was conducted at the Brazilian Cochrane Center. METHODS: The databases were searched for guidelines. Any guidelines obtained were then checked to find whether Cochrane systematic reviews were present in the bibliographic references of the guidelines. In their absence, we checked whether such reviews had not been included because no reviews existed yet, or because such reviews had not been consulted despite already existing. RESULTS: 223 studies were initially selected; of these, 77 were excluded. Of the 146 guidelines included, 46 could have made reference to existing systematic reviews, but only 13 studies did so. Among these 13 studies, eight were systematic reviews following Cochrane methodology. Thirty-three guidelines had not been drafted using published systematic reviews as references, and 100 guidelines had been unable to use Cochrane references because no reviews existed yet. CONCLUSION: It is necessary to increase awareness of the importance of using systematic reviews in drafting dentistry guidelines. Likewise, it is necessary to develop systematic reviews that answer questions on the various topics that remain unanswered.

  16. Parallelization of an existing high energy physics event reconstruction software package

    International Nuclear Information System (INIS)

    Schiefer, R.; Francis, D.

    1996-01-01

    Software parallelization allows an efficient use of available computing power to increase the performance of applications. In a case study the authors have investigated the parallelization of high energy physics event reconstruction software in terms of costs (effort, computing resource requirements), benefits (performance increase) and the feasibility of a systematic parallelization approach. Guidelines facilitating a parallel implementation are proposed for future software development

  17. Public informations guidelines

    International Nuclear Information System (INIS)

    1986-06-01

    The purpose of these Public Information Guidelines is to provide principles for the implementation of the NWPA mandate and the Mission Plan requirements for the provision of public information. These Guidelines set forth the public information policy to be followed by all Office of Civilian Radioactive Waste Management (OCRWM) performance components. The OCRWM offices should observe these Guidelines in shaping and conducting public information activities

  18. Pragmatic Software Innovation

    DEFF Research Database (Denmark)

    Aaen, Ivan; Jensen, Rikke Hagensby

    2014-01-01

    We understand software innovation as concerned with introducing innovation into the development of software intensive systems, i.e. systems in which software development and/or integration are dominant considerations. Innovation is key in almost any strategy for competitiveness in existing markets......, for creating new markets, or for curbing rising public expenses, and software intensive systems are core elements in most such strategies. Software innovation therefore is vital for about every sector of the economy. Changes in software technologies over the last decades have opened up for experimentation......, learning, and flexibility in ongoing software projects, but how can this change be used to facilitate software innovation? How can a team systematically identify and pursue opportunities to create added value in ongoing projects? In this paper, we describe Deweyan pragmatism as the philosophical foundation...

  19. Software Engineering Improvement Plan

    Science.gov (United States)

    2006-01-01

    In performance of this task order, bd Systems personnel provided support to the Flight Software Branch and the Software Working Group through multiple tasks related to software engineering improvement and to activities of the independent Technical Authority (iTA) Discipline Technical Warrant Holder (DTWH) for software engineering. To ensure that the products, comments, and recommendations complied with customer requirements and the statement of work, bd Systems personnel maintained close coordination with the customer. These personnel performed work in areas such as update of agency requirements and directives database, software effort estimation, software problem reports, a web-based process asset library, miscellaneous documentation review, software system requirements, issue tracking software survey, systems engineering NPR, and project-related reviews. This report contains a summary of the work performed and the accomplishments in each of these areas.

  20. Improving Software Reliability Forecasting

    NARCIS (Netherlands)

    Burtsy, Bernard; Albeanu, Grigore; Boros, Dragos N.; Popentiu, Florin; Nicola, V.F.

    1996-01-01

    This work investigates some methods for software reliability forecasting. A supermodel is presented as a suited tool for prediction of reliability in software project development. Also, times series forecasting for cumulative interfailure time is proposed and illustrated.

  1. Spotting software errors sooner

    International Nuclear Information System (INIS)

    Munro, D.

    1989-01-01

    Static analysis is helping to identify software errors at an earlier stage and more cheaply than conventional methods of testing. RTP Software's MALPAS system also has the ability to check that a code conforms to its original specification. (author)

  2. Avionics and Software Project

    Data.gov (United States)

    National Aeronautics and Space Administration — The goal of the AES Avionics and Software (A&S) project is to develop a reference avionics and software architecture that is based on standards and that can be...

  3. Paladin Software Support Lab

    Data.gov (United States)

    Federal Laboratory Consortium — The Paladin Software Support Environment (SSE) occupies 2,241 square-feet. It contains the hardware and software tools required to support the Paladin Automatic Fire...

  4. Software service history report

    Science.gov (United States)

    2002-01-01

    The safe and reliable operation of software within civil aviation systems and equipment has historically been assured through the application of rigorous design assurance applied during the software development process. Increasingly, manufacturers ar...

  5. Software engineering measurement

    CERN Document Server

    Munson, PhD, John C

    2003-01-01

    By demonstrating how to develop simple experiments for the empirical validation of theoretical research and showing how to convert measurement data into meaningful and valuable information, this text fosters more precise use of software measurement in the computer science and software engineering literature. Software Engineering Measurement shows you how to convert your measurement data to valuable information that can be used immediately for software process improvement.

  6. Agent Building Software

    Science.gov (United States)

    2000-01-01

    AgentBuilder is a software component developed under an SBIR contract between Reticular Systems, Inc., and Goddard Space Flight Center. AgentBuilder allows software developers without experience in intelligent agent technologies to easily build software applications using intelligent agents. Agents are components of software that will perform tasks automatically, with no intervention or command from a user. AgentBuilder reduces the time and cost of developing agent systems and provides a simple mechanism for implementing high-performance agent systems.

  7. Software engineer's pocket book

    CERN Document Server

    Tooley, Michael

    2013-01-01

    Software Engineer's Pocket Book provides a concise discussion on various aspects of software engineering. The book is comprised of six chapters that tackle various areas of concerns in software engineering. Chapter 1 discusses software development, and Chapter 2 covers programming languages. Chapter 3 deals with operating systems. The book also tackles discrete mathematics and numerical computation. Data structures and algorithms are also explained. The text will be of great use to individuals involved in the specification, design, development, implementation, testing, maintenance, and qualit

  8. Software quality challenges.

    OpenAIRE

    Fitzpatrick, Ronan; Smith, Peter; O'Shea, Brendan

    2004-01-01

    This paper sets out a number of challenges facing the software quality community. These challenges relate to the broader view of quality and the consequences for software quality definitions. These definitions are related to eight perspectives of software quality in an end-to-end product life cycle. Research and study of software quality has traditionally focused on product quality for management information systems and this paper considers the challenge of defining additional quality factors...

  9. Software verification and testing

    Science.gov (United States)

    1985-01-01

    General procedures for software verification and validation are provided as a guide for managers, programmers, and analysts involved in software development. The verification and validation procedures described are based primarily on testing techniques. Testing refers to the execution of all or part of a software system for the purpose of detecting errors. Planning, execution, and analysis of tests are outlined in this document. Code reading and static analysis techniques for software verification are also described.

  10. Software Testing Requires Variability

    DEFF Research Database (Denmark)

    Christensen, Henrik Bærbak

    2003-01-01

    Software variability is the ability of a software system or artefact to be changed, customized or configured for use in a particular context. Variability in software systems is important from a number of perspectives. Some perspectives rightly receive much attention due to their direct economic...... impact in software production. As is also apparent from the call for papers these perspectives focus on qualities such as reuse, adaptability, and maintainability....

  11. Gammasphere software development

    International Nuclear Information System (INIS)

    Piercey, R.B.

    1994-01-01

    This report describes the activities of the nuclear physics group at Mississippi State University which were performed during 1993. Significant progress has been made in the focus areas: chairing the Gammasphere Software Working Group (SWG); assisting with the porting and enhancement of the ORNL UPAK histogramming software package; and developing standard formats for Gammasphere data products. In addition, they have established a new public ftp archive to distribute software and software development tools and information

  12. Software variability management

    NARCIS (Netherlands)

    Bosch, J; Nord, RL

    2004-01-01

    During recent years, the amount of variability that has to be supported by a software artefact is growing considerably and its management is evolving into a major challenge during development, usage, and evolution of software artefacts. Successful management of variability in software leads to

  13. Software Language Evolution

    NARCIS (Netherlands)

    Vermolen, S.D.

    2012-01-01

    Software plays a critical role in our daily life. Vast amounts of money are spent on more and more complex systems. All software, regardless if it controls a plane or the game on your phone is never finished. Software changes when it contains bugs or when new functionality is added. This process of

  14. Computer software quality assurance

    International Nuclear Information System (INIS)

    Ives, K.A.

    1986-06-01

    The author defines some criteria for the evaluation of software quality assurance elements for applicability to the regulation of the nuclear industry. The author then analyses a number of software quality assurance (SQA) standards. The major extracted SQA elements are then discussed, and finally specific software quality assurance recommendations are made for the nuclear industry

  15. Software Engineering for Portability.

    Science.gov (United States)

    Stanchev, Ivan

    1990-01-01

    Discussion of the portability of educational software focuses on the software design and development process. Topics discussed include levels of portability; the user-computer dialog; software engineering principles; design techniques for student performance records; techniques of courseware programing; and suggestions for further research and…

  16. Astronomical Software Directory Service

    Science.gov (United States)

    Hanisch, R. J.; Payne, H.; Hayes, J.

    1998-01-01

    This is the final report on the development of the Astronomical Software Directory Service (ASDS), a distributable, searchable, WWW-based database of software packages and their related documentation. ASDS provides integrated access to 56 astronomical software packages, with more than 16,000 URL's indexed for full-text searching.

  17. Software Architecture Evolution

    Science.gov (United States)

    Barnes, Jeffrey M.

    2013-01-01

    Many software systems eventually undergo changes to their basic architectural structure. Such changes may be prompted by new feature requests, new quality attribute requirements, changing technology, or other reasons. Whatever the causes, architecture evolution is commonplace in real-world software projects. Today's software architects, however,…

  18. Software Quality Assurance in Software Projects: A Study of Pakistan

    OpenAIRE

    Faisal Shafique Butt; Sundus Shaukat; M. Wasif Nisar; Ehsan Ullah Munir; Muhammad Waseem; Kashif Ayyub

    2013-01-01

    Software quality is specific property which tells what kind of standard software should have. In a software project, quality is the key factor of success and decline of software related organization. Many researches have been done regarding software quality. Software related organization follows standards introduced by Capability Maturity Model Integration (CMMI) to achieve good quality software. Quality is divided into three main layers which are Software Quality Assurance (SQA), Software Qu...

  19. Global Software Development : - Software Architecture - Organization - Communication

    OpenAIRE

    Førde, Dan Sørensen

    2003-01-01

    Our globalized world has an impact on almost any area of our lives. The globalization affecting the business running around the globe, and forces employees and managers to think of new ways of doing their business. Globalization in the software development industry increased through the 1990s and is still increasing. The Internet makes the collaboration possible and the developers do not need to be co-located to work together on a common software development project. The ...

  20. Guidelines for Learning Stations.

    Science.gov (United States)

    Fehrle, Carl C.; Schulz, Jolene

    Guidelines for designing and planning learning stations for pupils at the elementary grade level include suggestions on how to develop a station that will be successful in meeting the learners' needs. Instructions for the use of tapes at a station and matching pupils with stations are given, as are guidelines on classroom arrangement and record…

  1. Guidelines for Media Production.

    Science.gov (United States)

    Ely, Donald P.

    Presented are: (1) guidelines for the selection of appropriate and feasible media; (2) criteria for production in each media format; and (3) guidelines for evaluation of each medium. This is designed for grantees or contractors who will be producing audiovisual materials for the EPA, or as part of a related activity. The level of sophistication…

  2. Maintenance Trades Guidelines

    Science.gov (United States)

    Weidner, Theodore J.

    2008-01-01

    In 2002, APPA published "Maintenance Staffing Guidelines for Educational Facilities," the first building maintenance trades staffing guideline designed to assist educational facilities professionals with their staffing needs. addresses how facilities professionals can determine the appropriate size and mix of their organization. Contents…

  3. Measure Guideline: Ventilation Cooling

    Energy Technology Data Exchange (ETDEWEB)

    Springer, D. [Alliance for Residential Building Innovation (ARBI), David, CA (United States); Dakin, B. [Alliance for Residential Building Innovation (ARBI), David, CA (United States); German, A. [Alliance for Residential Building Innovation (ARBI), David, CA (United States)

    2012-04-01

    The purpose of this measure guideline is to provide information on a cost-effective solution for reducing cooling system energy and demand in homes located in hot-dry and cold-dry climates. This guideline provides a prescriptive approach that outlines qualification criteria, selection considerations, and design and installation procedures.

  4. Measure Guideline: Ventilation Cooling

    Energy Technology Data Exchange (ETDEWEB)

    Springer, D.; Dakin, B.; German, A.

    2012-04-01

    The purpose of this measure guideline on ventilation cooling is to provide information on a cost-effective solution for reducing cooling system energy and demand in homes located in hot-dry and cold-dry climates. This guideline provides a prescriptive approach that outlines qualification criteria, selection considerations, and design and installation procedures.

  5. D 59 Design Guidelines

    DEFF Research Database (Denmark)

    Burcharth, Hans F.; Lamberti, Alberto

    The present guidelines are specifically dedicated to Low Crested Structures on attempt to provide methodological tools both for the engineering design of structures and for prediction of performance and environmental impacts. It is anticipated that the guidelines will provide valuable inputs to c...

  6. Essence: Facilitating Software Innovation

    DEFF Research Database (Denmark)

    Aaen, Ivan

    2008-01-01

      This paper suggests ways to facilitate creativity and innovation in software development. The paper applies four perspectives – Product, Project, Process, and People –to identify an outlook for software innovation. The paper then describes a new facility–Software Innovation Research Lab (SIRL) ......) – and a new method concept for software innovation – Essence – based on views, modes, and team roles. Finally, the paper reports from an early experiment using SIRL and Essence and identifies further research.......  This paper suggests ways to facilitate creativity and innovation in software development. The paper applies four perspectives – Product, Project, Process, and People –to identify an outlook for software innovation. The paper then describes a new facility–Software Innovation Research Lab (SIRL...

  7. Strategy Guideline: Modeling Enclosure Design in Above-Grade Walls

    Energy Technology Data Exchange (ETDEWEB)

    Lstiburek, J. [Building Science Corporation, Westford, MA (United States); Ueno, K. [Building Science Corporation, Westford, MA (United States); Musunuru, S. [Building Science Corporation, Westford, MA (United States)

    2016-02-24

    The Strategy Guideline describes how to model and interpret results of models for above grade walls. The Measure Guideline analyzes the failure thresholds and criteria for above grade walls. A library of above-grade walls with historically successful performance was used to calibrate WUFI (Warme Und Feuchte Instationar) software models. The information is generalized for application to a broad population of houses within the limits of existing experience.

  8. Global Imaging referral guidelines

    International Nuclear Information System (INIS)

    Kawooya, M.; Perez, M.; Lau, L.; Reeed, M.

    2010-01-01

    The medical imaging specialists called for global referral guidelines which would be made available to referring doctors. These referral guidelines should be:- Applicable in different health care settings, including resource-poor settings; Inclusive in terms of the range of clinical conditions; User-friendly and accessible (format/media); Acceptable to stakeholders, in particular to the referrers as the main target audience. To conceive evidence-based medicine as an integration of best research evidence with clinical expertise and patient values. The Direct recipients of the Referral Guidelines would be:- Referrers: general practitioners / family doctors; paediatricians; emergency department doctors; other specialists and health workers. Providers (medical imaging practitioners): radiologists; nuclear medicine physicians; radiographers; other appropriately qualified practitioners providing diagnostic imaging services. For the Referral Guidelines to be effective there need to be: Credibility evidence-based Practicality end user involvement Context local resources, disease profiles Endorsement, opinion leaders Implementation- policy, education, CPOE - Monitoring of the use clinical audit, report feedback. The aim of the Referral Guidelines Project was to: Produce global referral guidelines that are evidence-based, cost effective and appropriate for the local setting, and include consideration of available equipment and expertise (RGWG; SIGs); Include supporting information about radiation doses, potential risks, protection of children and pregnant women (introductory chapter); Facilitate the implementation of the guidelines through guidance and tools (e.g. implementation guides, checklists, capacity building tools, guides on stakeholders engagement, audit support criteria); Conduct pilot testing in different clinical settings from each of the six WHO regions; Promote the inclusion of the referral guidelines in the curricula of medical schools; Develop and implement

  9. MDP challenges from a software provider's perspective

    Science.gov (United States)

    Ohara, Shuichiro

    2014-10-01

    This industry faces new challenges every day. It gets tougher as process nodes shrink and the data complexity and volume increase. We are a mask data preparation (MDP) software provider, and have been providing MDP systems to mask shops since 1990. As the industry has, MDP software providers also have been facing new challenges over time, and the challenges get tougher as process nodes shrink and the data complexity and volume increase. We discuss such MDP challenges and solutions in this paper from a MDP software provider's perspective. The data volume continuously increases, and it is caused by shrinking the process node. In addition, resolution enhancement techniques (RET) such as optical proximity correction (OPC) and inverse lithography technique (ILT) induce data complexity, and it contributes considerably to the increase in data volume. The growth of data volume and complexity brings challenges to MDP system, such as the computing speed, shot count, and mask process correction (MPC). New tools (especially mask writers) also bring new challenges. Variable-shaped E-beam (VSB) mask writers demand fracturing less slivers and lower figure counts for CD accuracy and write time requirements respectively. Now multibeam mask writers are under development and will definitely bring new challenges.

  10. Software licenses: Good fences make good neighbors

    International Nuclear Information System (INIS)

    McCreary, J.G.; Woodyard, A.

    1995-01-01

    The basis for a good contract is that it is beneficial to both parties. A good foundation will cement the responsibilities and obligations of the parties after areas of agreement have been negotiated. Unfortunately, software licenses do not always reflect what is best for all. Some clauses are definitely for the benefit of the vendor, while others are required by a prudent client. The resulting contract is then a matter of reasonable compromise to achieve a good business relationship. Major issues of warranty, liability, training, support, and payment may be in conflict. Such topics as maintenance, testing, patents, extent of use, and return of software are often overlooked or addressed unevenly. This paper addresses these subjects and provides guidelines for software licenses. An understanding of legal phrases is of value. A better understanding of the viewpoints of both the vendor and the client results in a better working relationship

  11. Model Driven Software Development for Agricultural Robotics

    DEFF Research Database (Denmark)

    Larsen, Morten

    processing, control engineering, etc. This thesis proposes a Model-Driven Software Develop- ment based approach to model, analyse and partially generate the software implementation of a agricultural robot. Furthermore, Guidelines for mod- elling the architecture of an agricultural robots are provided......The design and development of agricultural robots, consists of both mechan- ical, electrical and software components. All these components must be de- signed and combined such that the overall goal of the robot is fulfilled. The design and development of these systems require collaboration between...... mul- tiple engineering disciplines. To this end, architectural specifications can serve as means for communication between different engineering disciplines. Such specifications aid in establishing the interface between the different com- ponents, belonging to different domains such as image...

  12. 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...... serve as a supplement to the guidelines for SLRs in EBSE. We plan to further evaluate the proposed approach using a series of case studies on varying research topics in SE....

  13. Science and Software

    Science.gov (United States)

    Zelt, C. A.

    2017-12-01

    Earth science attempts to understand how the earth works. This research often depends on software for modeling, processing, inverting or imaging. Freely sharing open-source software is essential to prevent reinventing the wheel and allows software to be improved and applied in ways the original author may never have envisioned. For young scientists, releasing software can increase their name ID when applying for jobs and funding, and create opportunities for collaborations when scientists who collect data want the software's creator to be involved in their project. However, we frequently hear scientists say software is a tool, it's not science. Creating software that implements a new or better way of earth modeling or geophysical processing, inverting or imaging should be viewed as earth science. Creating software for things like data visualization, format conversion, storage, or transmission, or programming to enhance computational performance, may be viewed as computer science. The former, ideally with an application to real data, can be published in earth science journals, the latter possibly in computer science journals. Citations in either case should accurately reflect the impact of the software on the community. Funding agencies need to support more software development and open-source releasing, and the community should give more high-profile awards for developing impactful open-source software. Funding support and community recognition for software development can have far reaching benefits when the software is used in foreseen and unforeseen ways, potentially for years after the original investment in the software development. For funding, an open-source release that is well documented should be required, with example input and output files. Appropriate funding will provide the incentive and time to release user-friendly software, and minimize the need for others to duplicate the effort. All funded software should be available through a single web site

  14. Evaluation of atlas-based auto-segmentation software in prostate cancer patients

    Energy Technology Data Exchange (ETDEWEB)

    Greenham, Stuart, E-mail: stuart.greenham@ncahs.health.nsw.gov.au [Department of Radiation Oncology, North Coast Cancer Institute, Coffs Harbour Health Campus, Coffs Harbour, New South Wales (Australia); Dean, Jenna [North Coast Cancer Institute, Port Macquarie Health Campus, Port Macquarie, New South Wales (Australia); Fu, Cheuk Kuen Kenneth [North Coast Cancer Institute, Lismore Health Campus, Lismore, New South Wales (Australia); Goman, Joanne [Department of Radiation Oncology, Calvary Mater Newcastle, Newcastle, New South Wales (Australia); Mulligan, Jeremy [North Coast Cancer Institute, Port Macquarie Health Campus, Port Macquarie, New South Wales (Australia); Tune, Deanna [Department of Radiation Oncology, North Coast Cancer Institute, Coffs Harbour Health Campus, Coffs Harbour, New South Wales (Australia); Sampson, David [North Coast Cancer Institute, Lismore Health Campus, Lismore, New South Wales (Australia); Westhuyzen, Justin [Department of Radiation Oncology, North Coast Cancer Institute, Coffs Harbour Health Campus, Coffs Harbour, New South Wales (Australia); McKay, Michael [North Coast Cancer Institute, Lismore Health Campus, Lismore, New South Wales (Australia); Department of Radiation Oncology, North Coast Cancer Institute, Coffs Harbour Health Campus, Coffs Harbour, New South Wales (Australia)

    2014-09-15

    The performance and limitations of an atlas-based auto-segmentation software package (ABAS; Elekta Inc.) was evaluated using male pelvic anatomy as the area of interest. Contours from 10 prostate patients were selected to create atlases in ABAS. The contoured regions of interest were created manually to align with published guidelines and included the prostate, bladder, rectum, femoral heads and external patient contour. Twenty-four clinically treated prostate patients were auto-contoured using a randomised selection of two, four, six, eight or ten atlases. The concordance between the manually drawn and computer-generated contours were evaluated statistically using Pearson's product–moment correlation coefficient (r) and clinically in a validated qualitative evaluation. In the latter evaluation, six radiation therapists classified the degree of agreement for each structure using seven clinically appropriate categories. The ABAS software generated clinically acceptable contours for the bladder, rectum, femoral heads and external patient contour. For these structures, ABAS-generated volumes were highly correlated with ‘as treated’ volumes, manually drawn; for four atlases, for example, bladder r = 0.988 (P < 0.001), rectum r = 0.739 (P < 0.001) and left femoral head r = 0.560 (P < 0.001). Poorest results were seen for the prostate (r = 0.401, P < 0.05) (four atlases); however this was attributed to the comparison prostate volume being contoured on magnetic resonance imaging (MRI) rather than computed tomography (CT) data. For all structures, increasing the number of atlases did not consistently improve accuracy. ABAS-generated contours are clinically useful for a range of structures in the male pelvis. Clinically appropriate volumes were created, but editing of some contours was inevitably required. The ideal number of atlases to improve generated automatic contours is yet to be determined.

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

  16. Software for the international linear collider: Simulation and ...

    Indian Academy of Sciences (India)

    Home; Journals; Pramana – Journal of Physics; Volume 69; Issue 6. Software for the international linear collider: Simulation and reconstruction frameworks. Ties Behnke Frank Gaede ... In international collaboration a data format for the ILC detector and physics studies has been developed. Building upon this software ...

  17. TAPSOFT'95: Theory and Practice of Software Development

    DEFF Research Database (Denmark)

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

  18. Social software in global software development

    DEFF Research Database (Denmark)

    Giuffrida, Rosalba; Dittrich, Yvonne

    2010-01-01

    Social software (SoSo) is defined by Farkas as tools that (1) allow people to communicate, collaborate, and build community online (2) can be syndicated, shared, reused or remixed and (3) let people learn easily from and capitalize on the behavior and knowledge of others. [1]. SoSo include a wide...... variety of tools such as: instant messaging, internet forums, mailing lists, blogs, wikis, social network sites, social bookmarking, social libraries, virtual worlds. Though normally rather belonging to the private realm, the use of social software in corporate context has been reported, e.g. as a way...

  19. Software architecture evolution

    DEFF Research Database (Denmark)

    Barais, Olivier; Le Meur, Anne-Francoise; Duchien, Laurence

    2008-01-01

    Software architectures must frequently evolve to cope with changing requirements, and this evolution often implies integrating new concerns. Unfortunately, when the new concerns are crosscutting, existing architecture description languages provide little or no support for this kind of evolution...... one particular framework named Tran SAT, which addresses the above problems of software architecture evolution. Tran SAT provides a new element in the software architecture descriptions language, called an architectural aspect, for describing new concerns and their integration into an existing...... architecture. Following the early aspect paradigm, Tran SAT allows the software architect to design a software architecture stepwise in terms of aspects at the design stage. It realises the evolution as the weaving of new architectural aspects into an existing software architecture....

  20. Software engineering in industry

    Science.gov (United States)

    Story, C. M.

    1989-12-01

    Can software be "engineered"? Can a few people with limited resources and a negligible budget produce high quality software solutions to complex software problems? It is possible to resolve the conflict between research activities and the necessity to view software development as a means to an end rather than as an end in itself? The aim of this paper is to encourage further thought and discussion on various topics which, in the author's experience, are becoming increasingly critical in large current software production and development projects, inside and outside high energy physics (HEP). This is done by briefly exploring some of the software engineering ideas and technologies now used in the information industry, using, as a case-study, a project with many similarities to those currently under way in HEP.

  1. SWEBOS – The Software Engineering Body of Skills

    Directory of Open Access Journals (Sweden)

    Yvonne Sedelmaier

    2015-02-01

    Full Text Available The development of complex software systems requires a mixture of various technical and non-technical competencies. While some guidelines exist which technical knowledge is required to make a good software engineer, there is a lack of insight as to which non-technical or soft skills are necessary to master complex software projects. This paper proposes a body of skills (SWEBOS for soft-ware engineering. The collection of necessary skills is developed on the basis of a clear, data-driven research design. The resulting required soft skills for software engineering are described precisely and semantically rich in a three-level structure. This approach guarantees that skills are not just characterized in a broad and general manner, but rather they are specifically adapted to the domain of software engineering.

  2. Software verification for nuclear industry

    International Nuclear Information System (INIS)

    Wilburn, N.P.

    1985-08-01

    Why verification of software products throughout the software life cycle is necessary is considered. Concepts of verification, software verification planning, and some verification methodologies for products generated throughout the software life cycle are then discussed

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

  4. Software evolution and maintenance

    CERN Document Server

    Tripathy, Priyadarshi

    2014-01-01

    Software Evolution and Maintenance: A Practitioner's Approach is an accessible textbook for students and professionals, which collates the advances in software development and provides the most current models and techniques in maintenance.Explains two maintenance standards: IEEE/EIA 1219 and ISO/IEC14764Discusses several commercial reverse and domain engineering toolkitsSlides for instructors are available onlineInformation is based on the IEEE SWEBOK (Software Engineering Body of Knowledge)

  5. Software configuration management

    CERN Document Server

    Keyes, Jessica

    2004-01-01

    Software Configuration Management discusses the framework from a standards viewpoint, using the original DoD MIL-STD-973 and EIA-649 standards to describe the elements of configuration management within a software engineering perspective. Divided into two parts, the first section is composed of 14 chapters that explain every facet of configuration management related to software engineering. The second section consists of 25 appendices that contain many valuable real world CM templates.

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

  7. Software systems for astronomy

    CERN Document Server

    Conrad, Albert R

    2014-01-01

    This book covers the use and development of software for astronomy. It describes the control systems used to point the telescope and operate its cameras and spectrographs, as well as the web-based tools used to plan those observations. In addition, the book also covers the analysis and archiving of astronomical data once it has been acquired. Readers will learn about existing software tools and packages, develop their own software tools, and analyze real data sets.

  8. Software for microcircuit systems

    International Nuclear Information System (INIS)

    Kunz, P.F.

    1978-10-01

    Modern Large Scale Integration (LSI) microcircuits are meant to be programed in order to control the function that they perform. The basics of microprograming and new microcircuits have already been discussed. In this course, the methods of developing software for these microcircuits are explored. This generally requires a package of support software in order to assemble the microprogram, and also some amount of support software to test the microprograms and to test the microprogramed circuit itself. 15 figures, 2 tables

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

  10. Solar Asset Management Software

    Energy Technology Data Exchange (ETDEWEB)

    Iverson, Aaron [Ra Power Management, Inc., Oakland, CA (United States); Zviagin, George [Ra Power Management, Inc., Oakland, CA (United States)

    2016-09-30

    Ra Power Management (RPM) has developed a cloud based software platform that manages the financial and operational functions of third party financed solar projects throughout their lifecycle. RPM’s software streamlines and automates the sales, financing, and management of a portfolio of solar assets. The software helps solar developers automate the most difficult aspects of asset management, leading to increased transparency, efficiency, and reduction in human error. More importantly, our platform will help developers save money by improving their operating margins.

  11. Software evolution in prototyping

    OpenAIRE

    Berzins, V.; Qi, Lu

    1996-01-01

    This paper proposes a model of software changes for supporting the evolution of software prototypes. The software evolution steps are decomposed into primitive substeps that correspond to monotonic specification changes. This structure is used to rearrange chronological derivation sequences into structures containing only meaning-preserving changes. The authors indicate how this structure can be used to automatically combine different changes to a specification. A set of examples illustrates ...

  12. Gammasphere software development

    International Nuclear Information System (INIS)

    Piercey, R.B.

    1993-01-01

    Activities of the nuclear physics group are described. Progress was made in organizing the Gammasphere Software Working Group, establishing a nuclear computing facility, participating in software development at Lawrence Berkeley, developing a common data file format, and adapting the ORNL UPAK software to run at Gammasphere. A universal histogram object was developed that defines a file format and provides for an objective-oriented programming model. An automated liquid nitrogen fill system was developed for Gammasphere (110 Ge detectors comprise the sphere)

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

  14. Essence: Facilitating Software Innovation

    DEFF Research Database (Denmark)

    Aaen, Ivan

    2008-01-01

      This paper suggests ways to facilitate creativity and innovation in software development. The paper applies four perspectives – Product, Project, Process, and People –to identify an outlook for software innovation. The paper then describes a new facility–Software Innovation Research Lab (SIRL......) – and a new method concept for software innovation – Essence – based on views, modes, and team roles. Finally, the paper reports from an early experiment using SIRL and Essence and identifies further research....

  15. Agile software development

    CERN Document Server

    Dingsoyr, Torgeir; Moe, Nils Brede

    2010-01-01

    Agile software development has become an umbrella term for a number of changes in how software developers plan and coordinate their work, how they communicate with customers and external stakeholders, and how software development is organized in small, medium, and large companies, from the telecom and healthcare sectors to games and interactive media. Still, after a decade of research, agile software development is the source of continued debate due to its multifaceted nature and insufficient synthesis of research results. Dingsoyr, Dyba, and Moe now present a comprehensive snapshot of the kno

  16. Software architecture 1

    CERN Document Server

    Oussalah , Mourad Chabane

    2014-01-01

    Over the past 20 years, software architectures have significantly contributed to the development of complex and distributed systems. Nowadays, it is recognized that one of the critical problems in the design and development of any complex software system is its architecture, i.e. the organization of its architectural elements. Software Architecture presents the software architecture paradigms based on objects, components, services and models, as well as the various architectural techniques and methods, the analysis of architectural qualities, models of representation of architectural template

  17. Software architecture 2

    CERN Document Server

    Oussalah, Mourad Chabanne

    2014-01-01

    Over the past 20 years, software architectures have significantly contributed to the development of complex and distributed systems. Nowadays, it is recognized that one of the critical problems in the design and development of any complex software system is its architecture, i.e. the organization of its architectural elements. Software Architecture presents the software architecture paradigms based on objects, components, services and models, as well as the various architectural techniques and methods, the analysis of architectural qualities, models of representation of architectural templa

  18. Dtest Testing Software

    Science.gov (United States)

    Jain, Abhinandan; Cameron, Jonathan M.; Myint, Steven

    2013-01-01

    This software runs a suite of arbitrary software tests spanning various software languages and types of tests (unit level, system level, or file comparison tests). The dtest utility can be set to automate periodic testing of large suites of software, as well as running individual tests. It supports distributing multiple tests over multiple CPU cores, if available. The dtest tool is a utility program (written in Python) that scans through a directory (and its subdirectories) and finds all directories that match a certain pattern and then executes any tests in that directory as described in simple configuration files.

  19. Contractor Software Charges

    National Research Council Canada - National Science Library

    Granetto, Paul

    1994-01-01

    .... Examples of computer software costs that contractors charge through indirect rates are material management systems, security systems, labor accounting systems, and computer-aided design and manufacturing...

  20. Optimization of Antivirus Software

    Directory of Open Access Journals (Sweden)

    2007-01-01

    Full Text Available The paper describes the main techniques used in development of computer antivirus software applications. For this particular category of software, are identified and defined optimum criteria that helps determine which solution is better and what are the objectives of the optimization process. From the general viewpoint of software optimization are presented methods and techniques that are applied at code development level. Regarding the particularities of antivirus software, the paper analyzes some of the optimization concepts applied to this category of applications

  1. Software as quality product

    International Nuclear Information System (INIS)

    Enders, A.

    1975-01-01

    In many discussions on the reliability of computer systems, software is presented as the weak link in the chain. The contribution attempts to identify the reasons for this situation as seen from the software development. The concepts correctness and reliability of programmes are explained as they are understood in the specialist discussion of today. Measures and methods are discussed which are particularly relevant as far as the obtaining of fault-free and reliable programmes is concerned. Conclusions are drawn for the user of software so that he is in the position to judge himself what can be justly expected frm the product software compared to other products. (orig./LH) [de

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

  3. Decentralized Software Architecture

    National Research Council Canada - National Science Library

    Khare, Rohit

    2002-01-01

    .... While the term "decentralization" is familiar from political and economic contexts, it has been applied extensively, if indiscriminately, to describe recent trends in software architecture towards...

  4. London 2012 packaging guidelines

    OpenAIRE

    2013-01-01

    These guidelines are intended to provide supplemental advice to suppliers and licensees regarding the provisions of the LOCOG Sustainable Sourcing Code that relate to packaging design and materials selection.

  5. Adopting preoperative fasting guidelines.

    Science.gov (United States)

    Anderson, Megan; Comrie, Rhonda

    2009-07-01

    In 1999, the American Society of Anesthesiologists adopted preoperative fasting guidelines to enhance the quality and efficiency of patient care. Guidelines suggest that healthy, non-pregnant patients should fast six hours from solids and two hours from liquids. Although these guidelines are in place, studies suggest that providers are still using the blanket statement "NPO after midnight" without regard to patient characteristics, the procedure, or the time of the procedure. Using theory to help change provider's beliefs may help make change more successful. Rogers' Theory of Diffusion of Innovations can assist in changing long-time practice by laying the groundwork for an analysis of the benefits and disadvantages of proposed changes, such as changes to fasting orders, while helping initiate local protocols instead of additional national guidelines.

  6. Electrical safety guidelines

    Energy Technology Data Exchange (ETDEWEB)

    1993-09-01

    The Electrical Safety Guidelines prescribes the DOE safety standards for DOE field offices or facilities involved in the use of electrical energy. It has been prepared to provide a uniform set of electrical safety standards and guidance for DOE installations in order to affect a reduction or elimination of risks associated with the use of electrical energy. The objectives of these guidelines are to enhance electrical safety awareness and mitigate electrical hazards to employees, the public, and the environment.

  7. OSART guidelines. 1992 edition

    International Nuclear Information System (INIS)

    1992-01-01

    The IAEA Operational Safety Review Team (OSART) Guidelines provide overall guidance for the experts to ensure the consistency and comprehensiveness of the operational safety review. Specific guidelines are provided as a guide for the systematic review in the following areas important to operational safety: management, organization and administration, training and qualification, operations, maintenance, technical support, radiation protection, chemistry, emergency planning and preparedness. Additional guidance and reference material has been prepared by the IAEA to complement the expertise of the OSART members

  8. Relevance of biotic pathways to the long-term regulation of nuclear waste disposal. Estimation of radiation dose to man resulting from biotic transport: the BIOPORT/MAXI1 software package. Volume 5

    Energy Technology Data Exchange (ETDEWEB)

    McKenzie, D.H.; Cadwell, L.L.; Gano, K.A.; Kennedy, W.E. Jr.; Napier, B.A.; Peloquin, R.A.; Prohammer, L.A.; Simmons, M.A.

    1985-10-01

    BIOPORT/MAXI1 is a collection of five computer codes designed to estimate the potential magnitude of the radiation dose to man resulting from biotic transport processes. Dose to man is calculated for ingestion of agricultural crops grown in contaminated soil, inhalation of resuspended radionuclides, and direct exposure to penetrating radiation resulting from the radionuclide concentrations established in the available soil surface by the biotic transport model. This document is designed as both an instructional and reference document for the BIOPORT/MAXI1 computer software package and has been written for two major audiences. The first audience includes persons concerned with the mathematical models of biological transport of commercial low-level radioactive wastes and the computer algorithms used to implement those models. The second audience includes persons concerned with exercising the computer program and exposure scenarios to obtain results for specific applications. The report contains sections describing the mathematical models, user operation of the computer programs, and program structure. Input and output for five sample problems are included. In addition, listings of the computer programs, data libraries, and dose conversion factors are provided in appendices.

  9. Relevance of biotic pathways to the long-term regulation of nuclear waste disposal. Estimation of radiation dose to man resulting from biotic transport: the BIOPORT/MAXI1 software package. Volume 5

    International Nuclear Information System (INIS)

    McKenzie, D.H.; Cadwell, L.L.; Gano, K.A.; Kennedy, W.E. Jr.; Napier, B.A.; Peloquin, R.A.; Prohammer, L.A.; Simmons, M.A.

    1985-10-01

    BIOPORT/MAXI1 is a collection of five computer codes designed to estimate the potential magnitude of the radiation dose to man resulting from biotic transport processes. Dose to man is calculated for ingestion of agricultural crops grown in contaminated soil, inhalation of resuspended radionuclides, and direct exposure to penetrating radiation resulting from the radionuclide concentrations established in the available soil surface by the biotic transport model. This document is designed as both an instructional and reference document for the BIOPORT/MAXI1 computer software package and has been written for two major audiences. The first audience includes persons concerned with the mathematical models of biological transport of commercial low-level radioactive wastes and the computer algorithms used to implement those models. The second audience includes persons concerned with exercising the computer program and exposure scenarios to obtain results for specific applications. The report contains sections describing the mathematical models, user operation of the computer programs, and program structure. Input and output for five sample problems are included. In addition, listings of the computer programs, data libraries, and dose conversion factors are provided in appendices

  10. Software cost estimation

    NARCIS (Netherlands)

    Heemstra, F.J.; Heemstra, F.J.

    1993-01-01

    The paper gives an overview of the state of the art of software cost estimation (SCE). The main questions to be answered in the paper are: (1) What are the reasons for overruns of budgets and planned durations? (2) What are the prerequisites for estimating? (3) How can software development effort be

  11. UWB Tracking Software Development

    Science.gov (United States)

    Gross, Julia; Arndt, Dickey; Ngo, Phong; Phan, Chau; Dusl, John; Ni, Jianjun; Rafford, Melinda

    2006-01-01

    An Ultra-Wideband (UWB) two-cluster Angle of Arrival (AOA) tracking prototype system is currently being developed and tested at NASA Johnson Space Center for space exploration applications. This talk discusses the software development efforts for this UWB two-cluster AOA tracking system. The role the software plays in this system is to take waveform data from two UWB radio receivers as an input, feed this input into an AOA tracking algorithm, and generate the target position as an output. The architecture of the software (Input/Output Interface and Algorithm Core) will be introduced in this talk. The development of this software has three phases. In Phase I, the software is mostly Matlab driven and calls C++ socket functions to provide the communication links to the radios. This is beneficial in the early stage when it is necessary to frequently test changes in the algorithm. Phase II of the development is to have the software mostly C++ driven and call a Matlab function for the AOA tracking algorithm. This is beneficial in order to send the tracking results to other systems and also to improve the tracking update rate of the system. The third phase is part of future work and is to have the software completely C++ driven with a graphics user interface. This software design enables the fine resolution tracking of the UWB two-cluster AOA tracking system.

  12. Sustainability in Software Engineering

    NARCIS (Netherlands)

    Wolfram, N.J.E.; Lago, P.; Osborne, Francesco

    2017-01-01

    The intersection between software engineering research and issues related to sustainability and green IT has been the subject of increasing attention. In spite of that, we observe that sustainability is still not clearly defined, or understood, in the field of software engineering. This lack of

  13. Software evolution with XVCL

    DEFF Research Database (Denmark)

    Zhang, Weishan; Jarzabek, Stan; Zhang, Hongyu

    2004-01-01

    This chapter introduces software evolution with XVCL (XML-based Variant Configuration Language), which is an XML-based metaprogramming technique. As the software evolves, a large number of variants may arise, especially whtn such kinds of evolutions are related to multiple platforms as shown in our...

  14. Marketing Mix del Software.

    Directory of Open Access Journals (Sweden)

    Yudith del Carmen Rodríguez Pérez

    2006-03-01

    Por ello, en este trabajo se define el concepto de producto software, se caracteriza al mismo y se exponen sus atributos de calidad. Además, se aborda la mezcla de marketing del software necesaria y diferente a la de otros productos para que este triunfe en el mercado.

  15. ITOUGH2 software qualification

    Energy Technology Data Exchange (ETDEWEB)

    Finsterle, S.; Pruess, K.; Fraser, P.

    1996-10-01

    The purpose of this report is to provide all software baseline documents necessary for the software qualification of ITOUGH2. ITOUGH2 is a computer program providing inverse modeling capabilities for TOUGH2. TOUGH2 is a numerical simulation code for multi-dimensional coupled fluid and heat flow of multiphase, multicomponent fluid mixtures in porous and fractured media.

  16. Cactus: Software Priorities

    Science.gov (United States)

    Hyde, Hartley

    2009-01-01

    The early eighties saw a period of rapid change in computing and teachers lost control of how they used computers in their classrooms. Software companies produced computer tools that looked so good that teachers forgot about writing their own classroom materials and happily purchased software--that offered much more than teachers needed--from…

  17. Software engineering ethics

    Science.gov (United States)

    Bown, Rodney L.

    1991-01-01

    Software engineering ethics is reviewed. The following subject areas are covered: lack of a system viewpoint; arrogance of PC DOS software vendors; violation od upward compatibility; internet worm; internet worm revisited; student cheating and company hiring interviews; computing practitioners and the commodity market; new projects and old programming languages; schedule and budget; and recent public domain comments.

  18. Software architecture evolution

    DEFF Research Database (Denmark)

    Barais, Olivier; Le Meur, Anne-Francoise; Duchien, Laurence

    2008-01-01

    Software architectures must frequently evolve to cope with changing requirements, and this evolution often implies integrating new concerns. Unfortunately, when the new concerns are crosscutting, existing architecture description languages provide little or no support for this kind of evolution....... The software architect must modify multiple elements of the architecture manually, which risks introducing inconsistencies. This chapter provides an overview, comparison and detailed treatment of the various state-of-the-art approaches to describing and evolving software architectures. Furthermore, we discuss...... one particular framework named Tran SAT, which addresses the above problems of software architecture evolution. Tran SAT provides a new element in the software architecture descriptions language, called an architectural aspect, for describing new concerns and their integration into an existing...

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

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

  1. Software licenses: Stay honest!

    CERN Multimedia

    Computer Security Team

    2012-01-01

    Do you recall our article about copyright violation in the last issue of the CERN Bulletin, “Music, videos and the risk for CERN”? Now let’s be more precise. “Violating copyright” not only means the illegal download of music and videos, it also applies to software packages and applications.   Users must respect proprietary rights in compliance with the CERN Computing Rules (OC5). Not having legitimately obtained a program or the required licenses to run that software is not a minor offense. It violates CERN rules and puts the Organization at risk! Vendors deserve credit and compensation. Therefore, make sure that you have the right to use their software. In other words, you have bought the software via legitimate channels and use a valid and honestly obtained license. This also applies to “Shareware” and software under open licenses, which might also come with a cost. Usually, only “Freeware” is complete...

  2. Software quality in 1997

    Energy Technology Data Exchange (ETDEWEB)

    Jones, C. [Software Productivity Research, Inc., Burlington, MA (United States)

    1997-11-01

    For many years, software quality assurance lagged behind hardware quality assurance in terms of methods, metrics, and successful results. New approaches such as Quality Function Deployment (QFD) the ISO 9000-9004 standards, the SEI maturity levels, and Total Quality Management (TQM) are starting to attract wide attention, and in some cases to bring software quality levels up to a parity with manufacturing quality levels. Since software is on the critical path for many engineered products, and for internal business systems as well, the new approaches are starting to affect global competition and attract widespread international interest. It can be hypothesized that success in mastering software quality will be a key strategy for dominating global software markets in the 21st century.

  3. Software safety hazard analysis

    International Nuclear Information System (INIS)

    Lawrence, J.D.

    1996-02-01

    Techniques for analyzing the safety and reliability of analog-based electronic protection systems that serve to mitigate hazards in process control systems have been developed over many years, and are reasonably well understood. An example is the protection system in a nuclear power plant. The extension of these techniques to systems which include digital computers is not well developed, and there is little consensus among software engineering experts and safety experts on how to analyze such systems. One possible technique is to extend hazard analysis to include digital computer-based systems. Software is frequently overlooked during system hazard analyses, but this is unacceptable when the software is in control of a potentially hazardous operation. In such cases, hazard analysis should be extended to fully cover the software. A method for performing software hazard analysis is proposed in this paper

  4. The Relevance of HCI Guidelines for Educational Interfaces.

    Science.gov (United States)

    Gilmore, David J.

    1996-01-01

    Considers the relevance of human-computer interaction (HCI) guidelines for educational interface design, including why educational software is different from other products; differences in goal focus; performance and learning; and experiments that investigated transfer of learning, including implications for the design of educational technologies.…

  5. Effective organizational solutions for implementation of DBMS software packages

    Science.gov (United States)

    Jones, D.

    1984-01-01

    The space telescope management information system development effort is a guideline for discussing effective organizational solutions used in implementing DBMS software. Focus is on the importance of strategic planning. The value of constructing an information system architecture to conform to the organization's managerial needs, the need for a senior decision maker, dealing with shifting user requirements, and the establishment of a reliable working relationship with the DBMS vendor are examined. Requirements for a schedule to demonstrate progress against a defined timeline and the importance of continued monitoring for production software control, production data control, and software enhancements are also discussed.

  6. Software development with C++ maximizing reuse with object technology

    CERN Document Server

    Nielsen, Kjell

    2014-01-01

    Software Development with C++: Maximizing Reuse with Object Technology is about software development and object-oriented technology (OT), with applications implemented in C++. The basis for any software development project of complex systems is the process, rather than an individual method, which simply supports the overall process. This book is not intended as a general, all-encompassing treatise on OT. The intent is to provide practical information that is directly applicable to a development project. Explicit guidelines are offered for the infusion of OT into the various development phases.

  7. A consolidated process for software process simulation : State of the Art and Industry Experience

    OpenAIRE

    Ali, Nauman Bin; Petersen, Kai

    2012-01-01

    Software process simulation is a complex task and in order to conduct a simulation project practitioners require support through a process for software process simulation modelling (SPSM), including what steps to take and what guidelines to follow in each step. This paper provides a literature based consolidated process for SPSM where the steps and guidelines for each step are identified through a review of literature and are complemented by experience from using these recommendations in an a...

  8. Dam safety guidelines

    International Nuclear Information System (INIS)

    Anderson, I.; Raska, C.

    1999-01-01

    The objectives of this report are (1) to define the requirements and outline the guidelines so that the safety of existing dams can be investigated and identified in a consistent and adequate manner across Canada, (2) to enable the consistent evaluation of dam safety deficiencies leading to the construction of improvements which contribute to dam safety, and (3) to provide a basis for dam safety legislation and regulation. The document contains statements of safety requirements, explanatory guidelines and commentaries. These clarify and expand upon some of the requirements and guidelines, and discuss alternative approaches to meeting the safety requirements. The report is divided into 12 sections which address criteria for earthquakes, floods and emergency preparedness. Geotechnical considerations and the effects of the reservoir environment are also discussed. These guidelines are not intended as design specifications for dam safety evaluation, design, construction or rehabilitation. From time to time, portions of these guidelines will be updated and issued to CDSA members. The user is responsible for ensuring that the most up-to-date version is being used. refs, tabs

  9. Are BTS guidelines followed?

    Science.gov (United States)

    2002-03-01

    In 1993, the British Thoracic Society (BTS) issued guidelines for the management of spontaneous pneumothorax. The study's aim was to determine the level of adherence to these guidelines at a London teaching hospital. A retrospective case note audit of 59 episodes was performed. In patients undergoing intervention, the initial procedure was simple aspiration in 32 (73 per cent) and chest tube insertion in 12 (27 per cent) cases, contrasting with the BTS recommendation that aspiration should be attempted first in all such patients. Simple aspiration was successful on 34 per cent of occasions. Successful aspiration was associated with a significantly shorter hospital stay (median 3, range 1-11 days) than either failed aspiration (7, 3-66 days) or chest tube insertion without aspiration (9, 3-16 days). Other areas where practice differed from the BTS guidelines were clamping of chest tubes and use of a pursestring suture for wound closure. A follow up questionnaire suggested a lack of familiarity with the guidelines. These findings indicate that current management of spontaneous pneumothorax deviates from the BTS guidelines in potentially important respects.

  10. Colorado Conference on iterative methods. Volume 1

    Energy Technology Data Exchange (ETDEWEB)

    NONE

    1994-12-31

    The conference provided a forum on many aspects of iterative methods. Volume I topics were:Session: domain decomposition, nonlinear problems, integral equations and inverse problems, eigenvalue problems, iterative software kernels. Volume II presents nonsymmetric solvers, parallel computation, theory of iterative methods, software and programming environment, ODE solvers, multigrid and multilevel methods, applications, robust iterative methods, preconditioners, Toeplitz and circulation solvers, and saddle point problems. Individual papers are indexed separately on the EDB.

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

  12. Developing and Testing a Video Tutorial for Software Training

    NARCIS (Netherlands)

    van der Meij, Hans

    2014-01-01

    Purpose: Video tutorials for software training are rapidly becoming popular. A set of dedicated guidelines for the construction of such tutorials was recently advanced in Technical Communication (Van der Meij & Van der Meij, 2013). The present study set out to assess the cognitive and motivational

  13. Standards guide for space and earth sciences computer software

    Science.gov (United States)

    Mason, G.; Chapman, R.; Klinglesmith, D.; Linnekin, J.; Putney, W.; Shaffer, F.; Dapice, R.

    1972-01-01

    Guidelines for the preparation of systems analysis and programming work statements are presented. The data is geared toward the efficient administration of available monetary and equipment resources. Language standards and the application of good management techniques to software development are emphasized.

  14. Metrics to improve control in outsourcing software development projects

    NARCIS (Netherlands)

    Ponisio, Laura; van Eck, Pascal; Messnarz, R.; Ekert, D.; Christiansen, M.; Johansen, J.; Koinig, S.

    Measurements serve as vital instruments to control projects involving software development outsourcing. However, managers have found it difficult to develop and implement effective measurement programs, in part because guidelines for choosing among concrete measure-ments are scarce. We address this

  15. Data structure and software engineering challenges and improvements

    CERN Document Server

    Antonakos, James L

    2011-01-01

    Data structure and software engineering is an integral part of computer science. This volume presents new approaches and methods to knowledge sharing, brain mapping, data integration, and data storage. The author describes how to manage an organization's business process and domain data and presents new software and hardware testing methods. The book introduces a game development framework used as a learning aid in a software engineering at the university level. It also features a review of social software engineering metrics and methods for processing business information. It explains how to

  16. Software quality assurance handbook

    Energy Technology Data Exchange (ETDEWEB)

    1990-09-01

    There are two important reasons for Software Quality Assurance (SQA) at Allied-Signal Inc., Kansas City Division (KCD): First, the benefits from SQA make good business sense. Second, the Department of Energy has requested SQA. This handbook is one of the first steps in a plant-wide implementation of Software Quality Assurance at KCD. The handbook has two main purposes. The first is to provide information that you will need to perform software quality assurance activities. The second is to provide a common thread to unify the approach to SQA at KCD. 2 figs.

  17. Systematic Software Development

    DEFF Research Database (Denmark)

    Kuhrmann, Marco; Méndez Fernández, Daniel

    2015-01-01

    The speed of innovation and the global allocation of resources to accelerate development or to reduce cost put pressure on the software industry. In the global competition, especially so-called high-price countries have to present arguments why the higher development cost is justified and what...... project- and quality management and their implementation in practice. So far, our results suggest that the necessity for a systematic software development is well recognized, while software development still follows an ad-hoc rather than a systematized style. Our results provide initial findings, which we...

  18. Beginning software engineering

    CERN Document Server

    Stephens, Rod

    2015-01-01

    Beginning Software Engineering demystifies the software engineering methodologies and techniques that professional developers use to design and build robust, efficient, and consistently reliable software. Free of jargon and assuming no previous programming, development, or management experience, this accessible guide explains important concepts and techniques that can be applied to any programming language. Each chapter ends with exercises that let you test your understanding and help you elaborate on the chapter's main concepts. Everything you need to understand waterfall, Sashimi, agile, RAD, Scrum, Kanban, Extreme Programming, and many other development models is inside!

  19. Colors in kindergarten software

    Directory of Open Access Journals (Sweden)

    Montell, Ireivys

    2012-01-01

    Full Text Available The article aims to address elements related to the use of color in educational software for early ages. The meaning of colors in pre-school age is presented from a theoretical perspective. A psychoeducational assessment of the influence of colors in educational software as a teaching aid to develop general intellectual abilities is explained. Likewise, the paper explains how achieving a balance between colors and software design leads to a proper interaction of children with new technology, a new resource for achieving objectives in educations and stimulating cognitive process development, both in institutions and in non-institutional channels.

  20. Global Software Engineering

    DEFF Research Database (Denmark)

    Ebert, Christof; Kuhrmann, Marco; Prikladnicki, Rafael

    2016-01-01

    SOFTWARE, LIKE ALL industry products, is the result of complex multinational supply chains with many partners from concept to development to production and maintenance. Global software engineering (GSE), IT outsourcing, and business process outsourcing during the past decade have showed growth...... rates of 10 to 20 percent per year. This instalment of Practitioner’s Digest summarizes experiences and guidance from industry to facilitate knowledge and technology transfer for GSE. It’s based on industry feedback from the annual IEEE International Conference on Global Software Engineering, which had...

  1. Flow Analysis Software Toolkit

    Science.gov (United States)

    Watson, Velvin; Castagnera, Karen; Plessel, Todd; Merritt, Fergus; Kelaita, Paul; West, John; Sandstrom, Tim; Clucas, Jean; Globus, AL; Bancroft, Gordon; hide

    1993-01-01

    Flow Analysis Software Toolkit (FAST) computer program provides software environment facilitating visualization of data. Collection of separate programs (modules) running simultaneously and helps user to examine results of numerical and experimental simulations. Intended for graphical depiction of computed flows, also assists in analysis of other types of data. Combines capabilities of such programs as PLOT3D, RIP, SURF, and GAS into one software environment with modules sharing data. All modules have consistent, highly interactive graphical user interface. Modular construction makes it flexible and extensible. Environment custom-configured, and new modules developed and added as needed. Written in ANSI compliant FORTRAN 77 and C language.

  2. Software takes command

    CERN Document Server

    Manovich, Lev

    2013-01-01

    Software has replaced a diverse array of physical, mechanical, and electronic technologies used before 21st century to create, store, distribute and interact with cultural artifacts. It has become our interface to the world, to others, to our memory and our imagination - a universal language through which the world speaks, and a universal engine on which the world runs. What electricity and combustion engine were to the early 20th century, software is to the early 21st century. Offering the the first theoretical and historical account of software for media authoring and its effects on the prac

  3. Sobre software libre

    OpenAIRE

    Matellán Olivera, Vicente; González Barahona, Jesús; Heras Quirós, Pedro de las; Robles Martínez, Gregorio

    2004-01-01

    220 p. "Sobre software libre" reune casi una treintena de ensayos sobre temas de candente actualidad relacionados con el software libre (del cual Linux es su ex- ponente más conocido). Los ensayos que el lector encontrará están divididos en bloques temáticos que van desde la propiedad intelectual o las cuestiones económicas y sociales de este modelo hasta su uso en la educación y las administraciones publicas, pasando por alguno que repasa la historia del software libre en l...

  4. Cortical cartography and Caret software.

    Science.gov (United States)

    Van Essen, David C

    2012-08-15

    Caret software is widely used for analyzing and visualizing many types of fMRI data, often in conjunction with experimental data from other modalities. This article places Caret's development in a historical context that spans three decades of brain mapping--from the early days of manually generated flat maps to the nascent field of human connectomics. It also highlights some of Caret's distinctive capabilities. This includes the ease of visualizing data on surfaces and/or volumes and on atlases as well as individual subjects. Caret can display many types of experimental data using various combinations of overlays (e.g., fMRI activation maps, cortical parcellations, areal boundaries), and it has other features that facilitate the analysis and visualization of complex neuroimaging datasets. Copyright © 2011 Elsevier Inc. All rights reserved.

  5. Guideline Implementation: Radiation Safety.

    Science.gov (United States)

    Fencl, Jennifer L

    2015-12-01

    Because radiologic technology is used in a variety of perioperative procedures and settings, it is essential for perioperative RNs to be knowledgeable of the risks related to radiation and the ways to adequately protect patients and health care providers from unintended radiation exposure. The updated AORN "Guideline for radiation safety" provides guidance on preventing injury from ionizing radiation exposure during therapeutic, diagnostic, and interventional procedures. This article focuses on key points of the guideline to help perioperative personnel practice radiation safety. The key points address the requirements for an organization's radiation safety program, measures used to keep radiation exposure as low as reasonably achievable, proper handling and testing of radiation protection devices, and considerations for protecting employees and patients who are pregnant and who will be exposed to radiation. Perioperative RNs should review the complete guideline for additional information and for guidance when writing and updating policies and procedures. Copyright © 2015 AORN, Inc. Published by Elsevier Inc. All rights reserved.

  6. Guideline implementation: local anesthesia.

    Science.gov (United States)

    Fencl, Jennifer L

    2015-06-01

    It is not uncommon in perioperative settings for patients to receive local anesthesia for a variety of procedures. It is imperative for patient safety that the perioperative RN has a comprehensive understanding of best practices associated with the use of local anesthesia. The updated AORN "Guideline for care of the patient receiving local anesthesia" provides guidance on perioperative nursing assessments and interventions to safely care for patients receiving local anesthesia. This article focuses on key points of the guideline to help perioperative personnel become knowledgeable regarding best practice as they care for this patient population. The key points address patient assessment, the importance of having an overall understanding of the local agent being used, recommended monitoring requirements, and potential adverse events, including life-threatening events. Perioperative RNs should review the complete guideline for additional information and for guidance when writing and updating policies and procedures. Copyright © 2015 AORN, Inc. Published by Elsevier Inc. All rights reserved.

  7. Guidelines for Urban Labs

    DEFF Research Database (Denmark)

    Scholl, Christian; Agger Eriksen, Mette; Baerten, Nik

    2017-01-01

    These guidelines are intended for team members and managers of urban labs and, more generally, for civil servants and facilitators in cities working with experimental processes to tackle complex challenges. They aim to support the everyday practice of collaboratively experimenting and learning ho...... the result is inspiring and instructive for all those who want to wrap their minds around experimental co-creative approaches to urban governance and city development.......These guidelines are intended for team members and managers of urban labs and, more generally, for civil servants and facilitators in cities working with experimental processes to tackle complex challenges. They aim to support the everyday practice of collaboratively experimenting and learning how...... to create more sustainable and inclusive cities. Policy-makers and urban development stakeholders may struggle to implement urban labs, and seek guidance for further development. Evidence-based guidelines and design principles are needed to decide for which types of challeng- es urban labs are most suited...

  8. An Introduction to the Special Volume on

    Directory of Open Access Journals (Sweden)

    Micah Altman

    2011-08-01

    Full Text Available This special volume of the Journal of Statistical Software on political methodology includes 14 papers, with wide-ranging software contributions of political scientists to their own field, and more generally to statistical data analysis in the the social sciences and beyond. Special emphasis is given to software that is written in or can cooperate with the R system for statistical computing.

  9. Right-Turn Traffic Volume Adjustments in Traffic Signal Warrant Analysis

    Science.gov (United States)

    2015-01-01

    To accomplish this research, a comprehensive literature review of existing guidelines and findings based on national and local studies was conducted. Ultimately, guidelines for consistent application for adjusting right-turn traffic volumes were deve...

  10. Evidence-based guidelines

    DEFF Research Database (Denmark)

    Rovira, Àlex; Wattjes, Mike P; Tintoré, Mar

    2015-01-01

    The clinical use of MRI in patients with multiple sclerosis (MS) has advanced markedly over the past few years. Technical improvements and continuously emerging data from clinical trials and observational studies have contributed to the enhanced performance of this tool for achieving a prompt...... diagnosis in patients with MS. The aim of this article is to provide guidelines for the implementation of MRI of the brain and spinal cord in the diagnosis of patients who are suspected of having MS. These guidelines are based on an extensive review of the recent literature, as well as on the personal...... of MRI in clinical practice for the diagnosis of MS....

  11. Data Qualification guidelines

    International Nuclear Information System (INIS)

    Edwards, T.B.; Shine, E.P.

    1992-01-01

    Data Qualification (DQ) is a formal, technical process whose objective is to affirm that experimental data are suitable for their intended use. Although it is not possible to develop a fixed recipe for the DQ process to cover all test situations, these general guidelines have been developed for the Nuclear Engineering Section to establish a framework for qualifying data from steady-state processing. These guidelines outline the role of the DQ team providing insight into the planning and conducting of the DQ process

  12. Transparent Guideline Methodology Needed

    DEFF Research Database (Denmark)

    Lidal, Ingeborg; Norén, Camilla; Mäkelä, Marjukka

    2013-01-01

    As part of learning at the Nordic Workshop of Evidence-based Medicine, we have read with interest the practice guidelines for central venous access, published in your Journal in 2012.1 We appraised the quality of this guideline using the checklist developed by The Evidence-Based Medicine Working ...... are based on best currently available evidence. Our concerns are in two main categories: the rigor of development, including methodology of searching, evaluating, and combining the evidence; and editorial independence, including funding and possible conflicts of interest....

  13. Strategy Guideline. Demonstration Home

    Energy Technology Data Exchange (ETDEWEB)

    Hunt, A.; Savage, C.

    2012-12-01

    This guideline will provide a general overview of the different kinds of demonstration home projects, a basic understanding of the different roles and responsibilities involved in the successful completion of a demonstration home, and an introduction into some of the lessons learned from actual demonstration home projects. Also, this guideline will specifically look at the communication methods employed during demonstration home projects. And lastly, we will focus on how to best create a communication plan for including an energy efficient message in a demonstration home project and carry that message to successful completion.

  14. Strategy Guideline: Demonstration Home

    Energy Technology Data Exchange (ETDEWEB)

    Savage, C.; Hunt, A.

    2012-12-01

    This guideline will provide a general overview of the different kinds of demonstration home projects, a basic understanding of the different roles and responsibilities involved in the successful completion of a demonstration home, and an introduction into some of the lessons learned from actual demonstration home projects. Also, this guideline will specifically look at the communication methods employed during demonstration home projects. And lastly, we will focus on how to best create a communication plan for including an energy efficient message in a demonstration home project and carry that message to successful completion.

  15. OSART guidelines. 1994 edition

    International Nuclear Information System (INIS)

    1994-05-01

    These guidelines have been prepared to provide a basic structure and common reference both across the various areas covered by an OSART mission and across all the missions in the programme. As such, they are addressed, principally, to the team members of OSART missions but they will also provide guidance to a host nuclear plant preparing to receive a mission. The guidelines are intended to help each expert to formulate his review in the light of this own experience. They are not all inclusive and should not limit the expert's investigations, but are better considered as illustrating the adequate requirements for his review

  16. "IBSAR" Software 4.0

    Directory of Open Access Journals (Sweden)

    2004-06-01

    Full Text Available A review for Arabic software entitled "IBSAR" software assigned to help blinds in usage of the computer, the software pronounces the commands and the contents of screens and applications browsed by users, this review includes general introduction about the software, the components and commands of the software , system requirements , and its functions with Windows operating system and Microsoft Word.

  17. TestingScientificSoftware.pdf

    OpenAIRE

    Dubey, Anshu

    2017-01-01

    Testing scientific software is critical for producing credible results and for code maintenance. The IDEAS scientific software productivity project aims toward increasing software productivity and sustainability, with participants from many projects that define the state of practice in software engineering in the HPC community. This tutorial distills the combined knowledge of IDEAS team members in the area of scientific software testing.

  18. Sandia National Laboratories ASCI Applications Software Quality Engineering Practices; TOPICAL

    International Nuclear Information System (INIS)

    ZEPPER, JOHN D.; ARAGON, KATHRYN MARY; ELLIS, MOLLY A.; BYLE, KATHLEEN A.; EATON, DONNA SUE

    2002-01-01

    This document provides a guide to the deployment of the software verification activities, software engineering practices, and project management principles that guide the development of Accelerated Strategic Computing Initiative (ASCI) applications software at Sandia National Laboratories (Sandia). The goal of this document is to identify practices and activities that will foster the development of reliable and trusted products produced by the ASCI Applications program. Document contents include an explanation of the structure and purpose of the ASCI Quality Management Council, an overview of the software development lifecycle, an outline of the practices and activities that should be followed, and an assessment tool. These sections map practices and activities at Sandia to the ASCI Software Quality Engineering: Goals, Principles, and Guidelines, a Department of Energy document

  19. Core Flight Software

    Data.gov (United States)

    National Aeronautics and Space Administration — The AES Core Flight Software (CFS) project purpose is to analyze applicability, and evolve and extend the reusability of the CFS system originally developed by...

  20. Collaborative software development

    NARCIS (Netherlands)

    M. de Jonge (Merijn); E. Visser; J.M.W. Visser (Joost)

    2001-01-01

    textabstractWe present an approach to collaborative software development where obtaining components and contributing components across organizational boundaries are explicit phases in the development process. A lightweight generative infrastructure supports this approach with an online package base,

  1. Next Generation Hydro Software

    NARCIS (Netherlands)

    Donchyts, G.; Baart, F.; Van Dam, A.; De Goede, E.; Icke, J.; Putten, H.

    2014-01-01

    An overview paper, describes motivation and main deliverables of the Next Generation Hydro Software (NGHS) project. Important technological innovations include development of the new computational core Delft3D Flexible Mesh, as well as the open modelling environment Delta Shell.

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

  3. Managing Software Process Evolution

    DEFF Research Database (Denmark)

    and want to get an overview of the different aspects of the topic, and for those who are experts with many years of experience, it particularly targets the needs of researchers and Ph.D. students in the area of software and systems engineering or information systems who study advanced topics concerning...... 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......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...

  4. Global Software Engineering

    DEFF Research Database (Denmark)

    Ebert, Christof; Kuhrmann, Marco; Prikladnicki, Rafael

    2016-01-01

    Professional software products and IT systems and services today are developed mostly by globally distributed teams, projects, and companies. Successfully orchestrating Global Software Engineering (GSE) has become the major success factor both for organizations and practitioners. Yet, more than...... and experience reported at the IEEE International Conference on Software Engineering (ICGSE) series. The outcomes of our analysis show GSE as a field highly attached to industry and, thus, a considerable share of ICGSE papers address the transfer of Software Engineering concepts and solutions to the global stage....... We found collaboration and teams, processes and organization, sourcing and supplier management, and success factors to be the topics gaining the most interest of researchers and practitioners. Beyond the analysis of the past conferences, we also look at current trends in GSE to motivate further...

  5. Tier2 Submit Software

    Science.gov (United States)

    Download this tool for Windows or Mac, which helps facilities prepare a Tier II electronic chemical inventory report. The data can also be exported into the CAMEOfm (Computer-Aided Management of Emergency Operations) emergency planning software.

  6. SEER Data & Software

    Science.gov (United States)

    Options for accessing datasets for incidence, mortality, county populations, standard populations, expected survival, and SEER-linked and specialized data. Plus variable definitions, documentation for reporting and using datasets, statistical software (SEER*Stat), and observational research resources.

  7. Two Case Studies of Subsystem Design for General-Purpose CSCW Software Architectures

    NARCIS (Netherlands)

    Grefen, P.W.P.J.; Sikkel, Nicolaas; Wieringa, Roelf J.

    2000-01-01

    This paper discusses subsystem design guidelines for the software architecture of general-purpose computer supported cooperative work systems, i.e., systems that are designed to be applicable in various application areas requiring explicit collaboration support. In our opinion, guidelines for

  8. Technical guideline technology according to the X-ray regulations

    International Nuclear Information System (INIS)

    2011-01-01

    The guideline covers the required technical knowledge concerning radiation protection and knowledge concerning for the operation of X-ray devices for technical purposes and stray radiation sources requiring licensing, and requirements for the qualification of officially authorized inspectors. The guidelines includes the following chapters: (1) introductory regulations; (2) Volume of the required technical knowledge; (3) Acquirement and certification of the technical knowledge; (4) Actualization of the technical knowledge; (5)Approval of courses and other training measures; (6) Combination of courses and training measures according to the guideline; (7) Requirements for qualification of officially authorized inspectors; (8) Interim regulations.

  9. Social Software and Strategy

    OpenAIRE

    Haefliger S; Monteiro E; Foray D; von Krogh G

    2011-01-01

    Social software challenges strategic thinking in important ways: empowering creative independent individuals implies indeterminate and uncertain reactions and creations in support of or in opposition to management's original thinking. We build a framework that organizes research on social software taking perspectives from both inside and outside companies. We use this framework to introduce the contributions to this special issue in terms of strategy technology and community and to ask a seri...

  10. Deprogramming Large Software Systems

    OpenAIRE

    Coppel, Yohann; Candea, George

    2008-01-01

    Developers turn ideas, designs and patterns into source code, then compile the source code into executables. Decompiling turns executables back into source code, and deprogramming turns code back into designs and patterns. In this paper we introduce DeP, a tool for deprogramming software systems. DeP abstracts code into a dependency graph and mines this graph for patterns. It also gives programmers visual means for manipulating the program. We describe DeP's use in several software engineerin...

  11. Global software development

    DEFF Research Database (Denmark)

    Matthiesen, Stina

    2016-01-01

    This overview presents the mid stages of my doctoral research-based on ethnographic work conducted in IT companies in India and in Denmark-on collaborative work within global software development (GSD). In the following I briefly introduce how this research seeks to spark a debate in CSCW...... by challenging contemporary ideals about software development outsourcing through the exploration of the multiplicities and asymmetric dynamics inherent in the collaborative work of GSD....

  12. Assuring Software Reliability

    Science.gov (United States)

    2014-08-01

    Software’s Impact on System and System of Systems Reliability [ Goodenough 2010]. This report suggests some techniques that address those challenges...noted in Goodenough (2012), confidence for software intensive systems is a slippery subject [ Goodenough 2012]. There is a subjective aspect to it...on finding and removing code faults through code inspection and testing [ Goodenough 2010]. But funding a software reliability improvement program

  13. Software product quality measurement

    OpenAIRE

    Godliauskas, Eimantas

    2016-01-01

    This paper analyses Ruby product quality measures, suggesting three new measures for Ruby product quality measurement tool Rubocop to measure Ruby product quality characteristics defined in ISO 2502n standard series. This paper consists of four main chapters. The first chapter gives a brief view of software product quality and software product quality measurement. The second chapter analyses object oriented quality measures. The third chapter gives a brief view of the most popular Ruby qualit...

  14. A Framework for Instituting Software Metrics in Small Software Organizations

    OpenAIRE

    Hisham M. Haddad; Nancy C. Ross; Donald E. Meredith

    2012-01-01

    The role of metrics in software quality is well-recognized; however, software metrics are yet to be standardized and integrated into development practices across the software industry. Literature reports indicate that software companies with less than 50 employees may represent up to 85% of the software organizations in several countries, including the United States. While process, project, and product metrics share a common goal of contributing to software quality and reliability, utilizatio...

  15. Managing Research Software Development: Better Software, Better Research

    OpenAIRE

    Hong, Neil Chue

    2017-01-01

    Research in most domains relies on software, but many researchers have not had experience in managing software projects, and many institutions are only recently providing infrastructure and support for software development. This talk will highlight recent best practice and efforts to improve the development and maintenance of software used in research, including Software Management Plans and what we can learn from the Open Source Software community.

  16. Survey on Impact of Software Metrics on Software Quality

    OpenAIRE

    Mrinal Singh Rawat; Arpita Mittal; Sanjay Kumar Dubey

    2012-01-01

    Software metrics provide a quantitative basis for planning and predicting software development processes. Therefore the quality of software can be controlled and improved easily. Quality in fact aids higher productivity, which has brought software metrics to the forefront. This research paper focuses on different views on software quality. Moreover, many metrics and models have been developed; promoted and utilized resulting in remarkable successes. This paper examines the realm of software e...

  17. Software Process Assessment (SPA)

    Science.gov (United States)

    Rosenberg, Linda H.; Sheppard, Sylvia B.; Butler, Scott A.

    1994-01-01

    NASA's environment mirrors the changes taking place in the nation at large, i.e. workers are being asked to do more work with fewer resources. For software developers at NASA's Goddard Space Flight Center (GSFC), the effects of this change are that we must continue to produce quality code that is maintainable and reusable, but we must learn to produce it more efficiently and less expensively. To accomplish this goal, the Data Systems Technology Division (DSTD) at GSFC is trying a variety of both proven and state-of-the-art techniques for software development (e.g., object-oriented design, prototyping, designing for reuse, etc.). In order to evaluate the effectiveness of these techniques, the Software Process Assessment (SPA) program was initiated. SPA was begun under the assumption that the effects of different software development processes, techniques, and tools, on the resulting product must be evaluated in an objective manner in order to assess any benefits that may have accrued. SPA involves the collection and analysis of software product and process data. These data include metrics such as effort, code changes, size, complexity, and code readability. This paper describes the SPA data collection and analysis methodology and presents examples of benefits realized thus far by DSTD's software developers and managers.

  18. Guidelines for Authors

    Indian Academy of Sciences (India)

    IAS Admin

    Please follow the instructions given below while preparing the manuscript. Articles which do not conform to the guidelines will not be considered. Authors are encouraged to submit their article in ASCII/MS Word/Latex version in a CD or by email to resonanc@ias.ernet.in. Title: Authors are requested to provide a) first title ...

  19. Instructional Guidelines. Welding.

    Science.gov (United States)

    Fordyce, H. L.; Doshier, Dale

    Using the standards of the American Welding Society and the American Society of Mechanical Engineers, this welding instructional guidelines manual presents a course of study in accordance with the current practices in industry. Intended for use in welding programs now practiced within the Federal Prison System, the phases of the program are…

  20. Climate friendly dietary guidelines

    DEFF Research Database (Denmark)

    Trolle, Ellen; Mogensen, Lisbeth; Thorsen, Anne Vibeke

    2014-01-01

    ) modifying the average diet according to the Danish food based dietary guidelines, 2) and adjusting to ensure an iso-energy content and a nutrient content according to the Nordic Nutrient Recommendations. Afterwards the healthy diet were changed further to reduce CF. CF from the diet was reduced by 4...

  1. Formalization of Medical Guidelines

    Czech Academy of Sciences Publication Activity Database

    Peleška, Jan; Anger, Z.; Buchtela, David; Šebesta, K.; Tomečková, Marie; Veselý, Arnošt; Zvára, K.; Zvárová, Jana

    2005-01-01

    Roč. 1, - (2005), s. 133-141 ISSN 1801-5603 R&D Projects: GA AV ČR 1ET200300413 Institutional research plan: CEZ:AV0Z10300504 Keywords : GLIF model * formalization of guidelines * prevention of cardiovascular diseases Subject RIV: IN - Informatics, Computer Science

  2. Curricular Guidelines for Endodontics.

    Science.gov (United States)

    Journal of Dental Education, 1981

    1981-01-01

    Guidelines developed by the Section on Endodontics of the American Association of Dental Schools for use by educational institutions as curriculum development aids are provided. Endodontics is that branch of dentistry dealing with diagnosis and treatment of oral conditions that arise as a result of pathoses of dental pulp. (MLW)

  3. Guidelines for Authors

    Indian Academy of Sciences (India)

    IAS Admin

    general readers' attention). Author(s): A photograph and a brief biographical sketch (in less than 30 words) should be provided. The author's name and mailing address should also be given. Author's phone number and email address will help in expediting the processing of manuscripts. Guidelines for Authors. Resonance ...

  4. Field Campaign Guidelines

    Energy Technology Data Exchange (ETDEWEB)

    Voyles, J. W. [DOE ARM Climate Research Facility, Washington, DC (United States); Chapman, L. A. [DOE ARM Climate Research Facility, Washington, DC (United States)

    2015-12-01

    This document establishes a common set of guidelines for the Atmospheric Radiation Measurement (ARM) Climate Research Facility for planning, executing, and closing out field campaigns. The steps that guide individual field campaigns are described in the Field Campaign Tracking System and are specifically tailored to meet the scope of each field campaign.

  5. Guidelines for Urban Labs

    DEFF Research Database (Denmark)

    Scholl, Christian; Agger Eriksen, Mette; Baerten, Nik

    2017-01-01

    urban lab initiatives from five different European cities: Antwerp (B), Graz and Leoben (A), Maastricht (NL) and Malmö (S). We do not pretend that these guidelines touch upon all possible challenges an urban lab may be confronted with, but we have incorporated all those we encountered in our...

  6. Computing and software

    Directory of Open Access Journals (Sweden)

    White, G. C.

    2004-06-01

    Full Text Available The reality is that the statistical methods used for analysis of data depend upon the availability of software. Analysis of marked animal data is no different than the rest of the statistical field. The methods used for analysis are those that are available in reliable software packages. Thus, the critical importance of having reliable, up–to–date software available to biologists is obvious. Statisticians have continued to develop more robust models, ever expanding the suite of potential analysis methods available. But without software to implement these newer methods, they will languish in the abstract, and not be applied to the problems deserving them. In the Computers and Software Session, two new software packages are described, a comparison of implementation of methods for the estimation of nest survival is provided, and a more speculative paper about how the next generation of software might be structured is presented. Rotella et al. (2004 compare nest survival estimation with different software packages: SAS logistic regression, SAS non–linear mixed models, and Program MARK. Nests are assumed to be visited at various, possibly infrequent, intervals. All of the approaches described compute nest survival with the same likelihood, and require that the age of the nest is known to account for nests that eventually hatch. However, each approach offers advantages and disadvantages, explored by Rotella et al. (2004. Efford et al. (2004 present a new software package called DENSITY. The package computes population abundance and density from trapping arrays and other detection methods with a new and unique approach. DENSITY represents the first major addition to the analysis of trapping arrays in 20 years. Barker & White (2004 discuss how existing software such as Program MARK require that each new model’s likelihood must be programmed specifically for that model. They wishfully think that future software might allow the user to combine

  7. Computing and software

    Science.gov (United States)

    White, Gary C.; Hines, J.E.

    2004-01-01

    The reality is that the statistical methods used for analysis of data depend upon the availability of software. Analysis of marked animal data is no different than the rest of the statistical field. The methods used for analysis are those that are available in reliable software packages. Thus, the critical importance of having reliable, up–to–date software available to biologists is obvious. Statisticians have continued to develop more robust models, ever expanding the suite of potential analysis methodsavailable. But without software to implement these newer methods, they will languish in the abstract, and not be applied to the problems deserving them.In the Computers and Software Session, two new software packages are described, a comparison of implementation of methods for the estimation of nest survival is provided, and a more speculative paper about how the next generation of software might be structured is presented.Rotella et al. (2004) compare nest survival estimation with different software packages: SAS logistic regression, SAS non–linear mixed models, and Program MARK. Nests are assumed to be visited at various, possibly infrequent, intervals. All of the approaches described compute nest survival with the same likelihood, and require that the age of the nest is known to account for nests that eventually hatch. However, each approach offers advantages and disadvantages, explored by Rotella et al. (2004).Efford et al. (2004) present a new software package called DENSITY. The package computes population abundance and density from trapping arrays and other detection methods with a new and unique approach. DENSITY represents the first major addition to the analysis of trapping arrays in 20 years.Barker & White (2004) discuss how existing software such as Program MARK require that each new model’s likelihood must be programmed specifically for that model. They wishfully think that future software might allow the user to combine pieces of likelihood

  8. Inspector qualification guidelines

    International Nuclear Information System (INIS)

    Batty, A.C.; Van Binnebeek, J.J.; Ericsson, P.O.; Fisher, J.C.; Geiger, P.; Grandame, M.; Grimes, B.K.; Joode, A. de; Kaufer, B.; Kinoshita, M.; Klonk, H.; Koizumi, H.; Maeda, N.; Maqua, M.; Perez del Moral, C.; Roselli, F.; Warren, T.; Zimmerman, R.

    1994-07-01

    The OECD Nuclear Energy Agency Committee on Nuclear Regulatory Activities (CNRA) has a Working Group on Inspection Practices (WGIP). The WGIP provides a forum for the exchange of Information and experience on the safety Inspection practices of regulatory authorities In the CNRA member countries. A consistent qualification process and well defined level of training for all Inspectors who participate In the safety Inspections are needed to provide consistent Inspections and reliable Inspection results. The WGIP organized in 1992 a workshop on the conduct of inspections, inspector qualification and training, and shutdown inspections at the Technical Training Center of the US NRC in Chattanooga, Tennessee. In the connection of workshop the WGIP identified a need to develop guidance for inspector qualification which could be used as a model by those who are developing their qualification practices. The inspector qualification journals of US NRC provided a good basis for the work. The following inspector qualification guideline has been developed for guidance of qualification of a new inspector recruited to the regulatory body. This guideline has been developed for helping the supervisors and training officers to give the initial training and familiarization to the duties of a new inspector in a controlled manner. US NRC inspector qualification journals have been used to define the areas of attention. This guideline provides large flexibility for application in different type organizations. Large organizations can develop separate qualification journals for each inspector positions. Small regulatory bodies can develop individual training programmes by defining the necessary training topics on case by case basis. E.g. the guideline can be used to define the qualifications of contracted inspectors used in some countries. The appropriate part would apply. Annex 1 gives two examples how this guideline could be applied

  9. Software Engineering Reviews and Audits

    CERN Document Server

    Summers, Boyd L

    2011-01-01

    Accurate software engineering reviews and audits have become essential to the success of software companies and military and aerospace programs. These reviews and audits define the framework and specific requirements for verifying software development efforts. Authored by an industry professional with three decades of experience, Software Engineering Reviews and Audits offers authoritative guidance for conducting and performing software first article inspections, and functional and physical configuration software audits. It prepares readers to answer common questions for conducting and perform

  10. Property-Based Software Engineering Measurement

    Science.gov (United States)

    Briand, Lionel C.; Morasca, Sandro; Basili, Victor R.

    1997-01-01

    Little theory exists in the field of software system measurement. Concepts such as complexity, coupling, cohesion or even size are very often subject to interpretation and appear to have inconsistent definitions in the literature. As a consequence, there is little guidance provided to the analyst attempting to define proper measures for specific problems. Many controversies in the literature are simply misunderstandings and stem from the fact that some people talk about different measurement concepts under the same label (complexity is the most common case). There is a need to define unambiguously the most important measurement concepts used in the measurement of software products. One way of doing so is to define precisely what mathematical properties characterize these concepts, regardless of the specific software artifacts to which these concepts are applied. Such a mathematical framework could generate a consensus in the software engineering community and provide a means for better communication among researchers, better guidelines for analysts, and better evaluation methods for commercial static analyzers for practitioners. In this paper, we propose a mathematical framework which is generic, because it is not specific to any particular software artifact and rigorous, because it is based on precise mathematical concepts. We use this framework to propose definitions of several important measurement concepts (size, length, complexity, cohesion, coupling). It does not intend to be complete or fully objective; other frameworks could have been proposed and different choices could have been made. However, we believe that the formalisms and properties we introduce are convenient and intuitive. This framework contributes constructively to a firmer theoretical ground of software measurement.

  11. Software Engineering Laboratory (SEL) cleanroom process model

    Science.gov (United States)

    Green, Scott; Basili, Victor; Godfrey, Sally; Mcgarry, Frank; Pajerski, Rose; Waligora, Sharon

    1991-01-01

    The Software Engineering Laboratory (SEL) cleanroom process model is described. The term 'cleanroom' originates in the integrated circuit (IC) production process, where IC's are assembled in dust free 'clean rooms' to prevent the destructive effects of dust. When applying the clean room methodology to the development of software systems, the primary focus is on software defect prevention rather than defect removal. The model is based on data and analysis from previous cleanroom efforts within the SEL and is tailored to serve as a guideline in applying the methodology to future production software efforts. The phases that are part of the process model life cycle from the delivery of requirements to the start of acceptance testing are described. For each defined phase, a set of specific activities is discussed, and the appropriate data flow is described. Pertinent managerial issues, key similarities and differences between the SEL's cleanroom process model and the standard development approach used on SEL projects, and significant lessons learned from prior cleanroom projects are presented. It is intended that the process model described here will be further tailored as additional SEL cleanroom projects are analyzed.

  12. Advanced human-system interface design review guideline. General evaluation model, technical development, and guideline description

    International Nuclear Information System (INIS)

    O'Hara, J.M.

    1994-07-01

    Advanced control rooms will use advanced human-system interface (HSI) technologies that may have significant implications for plant safety in that they will affect the operator's overall role in the system, the method of information presentation, and the ways in which operators interact with the system. The U.S. Nuclear Regulatory Commission (NRC) reviews the HSI aspects of control rooms to ensure that they are designed to good human factors engineering principles and that operator performance and reliability are appropriately supported to protect public health and safety. The principal guidance available to the NRC, however, was developed more than ten years ago, well before these technological changes. Accordingly, the human factors guidance needs to be updated to serve as the basis for NRC review of these advanced designs. The purpose of this project was to develop a general approach to advanced HSI review and the human factors guidelines to support NRC safety reviews of advanced systems. This two-volume report provides the results of the project. Volume I describes the development of the Advanced HSI Design Review Guideline (DRG) including (1) its theoretical and technical foundation, (2) a general model for the review of advanced HSIs, (3) guideline development in both hard-copy and computer-based versions, and (4) the tests and evaluations performed to develop and validate the DRG. Volume I also includes a discussion of the gaps in available guidance and a methodology for addressing them. Volume 2 provides the guidelines to be used for advanced HSI review and the procedures for their use

  13. Advanced human-system interface design review guideline. General evaluation model, technical development, and guideline description

    Energy Technology Data Exchange (ETDEWEB)

    O`Hara, J.M.

    1994-07-01

    Advanced control rooms will use advanced human-system interface (HSI) technologies that may have significant implications for plant safety in that they will affect the operator`s overall role in the system, the method of information presentation, and the ways in which operators interact with the system. The U.S. Nuclear Regulatory Commission (NRC) reviews the HSI aspects of control rooms to ensure that they are designed to good human factors engineering principles and that operator performance and reliability are appropriately supported to protect public health and safety. The principal guidance available to the NRC, however, was developed more than ten years ago, well before these technological changes. Accordingly, the human factors guidance needs to be updated to serve as the basis for NRC review of these advanced designs. The purpose of this project was to develop a general approach to advanced HSI review and the human factors guidelines to support NRC safety reviews of advanced systems. This two-volume report provides the results of the project. Volume I describes the development of the Advanced HSI Design Review Guideline (DRG) including (1) its theoretical and technical foundation, (2) a general model for the review of advanced HSIs, (3) guideline development in both hard-copy and computer-based versions, and (4) the tests and evaluations performed to develop and validate the DRG. Volume I also includes a discussion of the gaps in available guidance and a methodology for addressing them. Volume 2 provides the guidelines to be used for advanced HSI review and the procedures for their use.

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

  15. 3-Dimensional Right Ventricular Volume Assessment

    NARCIS (Netherlands)

    Jainandunsing, Jayant S.; Matyal, Robina; Shahul, Sajid S.; Wang, Angela; Woltersom, Bozena; Mahmood, Feroze

    Purpose: The purpose of this review was to evaluate new computer software available for 3-dimensional right ventricular (RV) volume estimation. Description: Based on 2-dimensional echocardiography, various algorithms have been used for RV volume estimation. These are complex, time-consuming

  16. Object-Oriented Software Metrics for Predicting Reusability and Estimating Size

    Science.gov (United States)

    Sanderson, D. Peter; Tran, Tuyet-Lan; Sherif, Josef S.; Lee, Susan S.

    1995-01-01

    As object-oriented software development methods come into more widespread use, basic questions of software quality assurance must be reconsidered. We will highlight efforts now underway at NASA's Jet Propulsion Laboratory to both assess the quality of software systems developed using object oriented technology and develop guidelines for future development of such systems. The current focus is on design and code reusability., and system size estimation. A number of metrics are proposed and two software systems measured and analyzed. The preliminary results reported here should be useful to software development and quality assurance personnel working in C++ implementation environment.

  17. The Ettention software package

    International Nuclear Information System (INIS)

    Dahmen, Tim; Marsalek, Lukas; Marniok, Nico; Turoňová, Beata; Bogachev, Sviatoslav; Trampert, Patrick; Nickels, Stefan; Slusallek, Philipp

    2016-01-01

    We present a novel software package for the problem “reconstruction from projections” in electron microscopy. The Ettention framework consists of a set of modular building-blocks for tomographic reconstruction algorithms. The well-known block iterative reconstruction method based on Kaczmarz algorithm is implemented using these building-blocks, including adaptations specific to electron tomography. Ettention simultaneously features (1) a modular, object-oriented software design, (2) optimized access to high-performance computing (HPC) platforms such as graphic processing units (GPU) or many-core architectures like Xeon Phi, and (3) accessibility to microscopy end-users via integration in the IMOD package and eTomo user interface. We also provide developers with a clean and well-structured application programming interface (API) that allows for extending the software easily and thus makes it an ideal platform for algorithmic research while hiding most of the technical details of high-performance computing. - Highlights: • Novel software package for “reconstruction from projections” in electron microscopy. • Support for high-resolution reconstructions on iterative reconstruction algorithms. • Support for CPU, GPU and Xeon Phi. • Integration in the IMOD software. • Platform for algorithm researchers: object oriented, modular design.

  18. Managing Distributed Software Projects

    DEFF Research Database (Denmark)

    Persson, John Stouby

    Increasingly, software projects are becoming geographically distributed, with limited face-toface interaction between participants. These projects face particular challenges that need careful managerial attention. This PhD study reports on how we can understand and support the management of distr......Increasingly, software projects are becoming geographically distributed, with limited face-toface interaction between participants. These projects face particular challenges that need careful managerial attention. This PhD study reports on how we can understand and support the management...... of distributed software projects, based on a literature study and a case study. The main emphasis of the literature study was on how to support the management of distributed software projects, but also contributed to an understanding of these projects. The main emphasis of the case study was on how to understand...... the management of distributed software projects, but also contributed to supporting the management of these projects. The literature study integrates what we know about risks and risk-resolution techniques, into a framework for managing risks in distributed contexts. This framework was developed iteratively...

  19. Software reliability assessment

    International Nuclear Information System (INIS)

    Barnes, M.; Bradley, P.A.; Brewer, M.A.

    1994-01-01

    The increased usage and sophistication of computers applied to real time safety-related systems in the United Kingdom has spurred on the desire to provide a standard framework within which to assess dependable computing systems. Recent accidents and ensuing legislation have acted as a catalyst in this area. One particular aspect of dependable computing systems is that of software, which is usually designed to reduce risk at the system level, but which can increase risk if it is unreliable. Various organizations have recognized the problem of assessing the risk imposed to the system by unreliable software, and have taken initial steps to develop and use such assessment frameworks. This paper relates the approach of Consultancy Services of AEA Technology in developing a framework to assess the risk imposed by unreliable software. In addition, the paper discusses the experiences gained by Consultancy Services in applying the assessment framework to commercial and research projects. The framework is applicable to software used in safety applications, including proprietary software. Although the paper is written with Nuclear Reactor Safety applications in mind, the principles discussed can be applied to safety applications in all industries

  20. Overview of the ANS [American Nuclear Society] mathematics and computation software standards

    International Nuclear Information System (INIS)

    Smetana, A.O.

    1991-01-01

    The Mathematics and Computations Division of the American Nuclear Society sponsors the ANS-10 Standards Subcommittee. This subcommittee, which is part of the ANS Standards Committee, currently maintains four ANSI/ANS software standards. These standards are: Recommended Programming Practices to Facilitate the Portability of Scientific Computer Programs, ANS-10.2; Guidelines for the Documentation of Computer Software, ANS-10.3; Guidelines for the Verification and Validation of Scientific and Engineering Computer Programs for the Nuclear Industry, ANS-10.4; and Guidelines for Accommodating User Needs in Computer Program Development, ANS-10.5. 5 refs