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

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

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

  6. Sandia software guidelines: Software quality planning

    Energy Technology Data Exchange (ETDEWEB)

    1987-08-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 procedures to follow in producing a Software Quality Assurance Plan for an organization or a project, and provides an example project SQA plan. 2 figs., 4 tabs.

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

    International Nuclear Information System (INIS)

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

    1995-05-01

    This report is the fifth volume in a series of reports describing the results of the Expert System Verification and Validation (V ampersand V) project which is jointly funded by US NRC and EPRI toward formulating guidelines for 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 (and the accompanying 11 step by step Procedures) are presented in Volume 7, User's Manual. 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 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 AI systems

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

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

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

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

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

    International Nuclear Information System (INIS)

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

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

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

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

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

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

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

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

    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 provides a step-by-step guide, or user manual, for personnel responsible for the planning and execution of the verification and validation (V&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&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&V methods is most appropriate for those conditions. The V&V Guideline Packages are provided in Section 2. Each package consists of an ordered set of V&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.

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

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

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

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

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

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

    International Nuclear Information System (INIS)

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

    1995-05-01

    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 of V ampersand V activity; the value lies in the 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, 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. These methods either involved the analysis and tracing of requirements to elements in the knowledge base or direct inspection of the knowledge base for various kinds of errors. Half of the subjects within each system group used the best annual 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 (the experimental group). The four groups of participants were similar in nuclear engineering and software experience characteristics. It is concluded that the use of tools in static knowledge base certification results in significant improvement in detecting all types of defects, avoiding false alarms, and completing the effort in less time. The simulated knowledge-checking tool, based on supplemental engineering information about the systems

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

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

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

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

  10. Guidelines for upgrading of low volume roads

    CSIR Research Space (South Africa)

    Division of Roads

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

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

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

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

    Energy Technology Data Exchange (ETDEWEB)

    Jung, Se Jin; Lee, Dong Ah; Kim, Eui Sub; Yoo, Jun Beom [Division of Computer Science and Engineering College of Information and Communication, Konkuk University, Seoul (Korea, Republic of); Lee, Jang Su [Man-Machine Interface System team Korea Atomic Energy Research Institute, Daejeon (Korea, Republic of)

    2014-10-15

    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.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

  9. Collected software engineering papers, volume 6

    Science.gov (United States)

    1988-01-01

    A collection is presented of technical papers produced by participants in the Software Engineering Laboratory (SEL) during the period 1 Jun. 1987 to 1 Jan. 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 twelve 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.

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

    Energy Technology Data Exchange (ETDEWEB)

    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.

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

  12. Guidance and Control Software Project Data - Volume 1: Planning 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 planning documents from the GCS project. Volume 1 contains five appendices: A. Plan for Software Aspects of Certification for the Guidance and Control Software Project; B. Software Development Standards for the Guidance and Control Software Project; C. Software Verification Plan for the Guidance and Control Software Project; D. Software Configuration Management Plan for the Guidance and Control Software Project; and E. Software Quality Assurance Activities.

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

  14. Technical Reviews and Audits for Systems, Equipment and Computer Software. Volume 1

    Science.gov (United States)

    2009-09-15

    acquisitions and technology developments. 2. This new-issue SMC standard comprises the text of The Aerospace Corporation report number TOR-2007( 8583 )-6414...TRA) Deskbook – DUSD(S&T) (May 2005) 17. IMP & IMS Preparation and Use Guide Version 0.9 (21 October 2005) 18. ISO /IEC STD 15939 Software...1521B, TOR-2007( 8583 )-6414_Volume 1. 110.2 Purpose A. The guidelines contained herein implement the Department of Defense Directive 4120.21

  15. Guidance and Control Software Project Data - Volume 3: Verification 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 verification documents from the GCS project. Volume 3 contains four appendices: A. Software Verification Cases and Procedures for the Guidance and Control Software Project; B. Software Verification Results for the Pluto Implementation of the Guidance and Control Software; C. Review Records for the Pluto Implementation of the Guidance and Control Software; and D. Test Results Logs for the Pluto Implementation of the Guidance and Control Software.

  16. Ground and Space Radar Volume Matching and Comparison Software

    Science.gov (United States)

    Morris, Kenneth; Schwaller, Mathew

    2010-01-01

    This software enables easy comparison of ground- and space-based radar observations. The software was initially designed to compare ground radar reflectivity from operational, ground based Sand C-band meteorological radars with comparable measurements from the Tropical Rainfall Measuring Mission (TRMM) satellite s Precipitation Radar (PR) instrument. The software is also applicable to other ground-based and space-based radars. The ground and space radar volume matching and comparison software was developed in response to requirements defined by the Ground Validation System (GVS) of Goddard s Global Precipitation Mission (GPM) project. This software innovation is specifically concerned with simplifying the comparison of ground- and spacebased radar measurements for the purpose of GPM algorithm and data product validation. This software is unique in that it provides an operational environment to routinely create comparison products, and uses a direct geometric approach to derive common volumes of space- and ground-based radar data. In this approach, spatially coincident volumes are defined by the intersection of individual space-based Precipitation Radar rays with the each of the conical elevation sweeps of the ground radar. Thus, the resampled volume elements of the space and ground radar reflectivity can be directly compared to one another.

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

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

    International Nuclear Information System (INIS)

    Hecht, H.; Hecht, M.; Graff, S.; Green, W.; Lin, D.; Koch, S.; Tai, A.; Wendelboe, D.

    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

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

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

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

    Energy Technology Data Exchange (ETDEWEB)

    Salomons, G [Cancer Center of Southeastern Ontario & Queen’s University, Kingston, ON (Canada); Kelly, D [Royal Military College of Canada, Kingston, ON, CA (Canada)

    2015-06-15

    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.

  2. Guideline for Bayesian Net based Software Fault Estimation Method for Reactor Protection System

    International Nuclear Information System (INIS)

    Eom, Heung Seop; Park, Gee Yong; Jang, Seung Cheol

    2011-01-01

    The purpose of this paper is to provide a preliminary guideline for the estimation of software faults in a safety-critical software, for example, reactor protection system's software. As the fault estimation method is based on Bayesian Net which intensively uses subjective probability and informal data, it is necessary to define formal procedure of the method to minimize the variability of the results. The guideline describes assumptions, limitations and uncertainties, and the product of the fault estimation method. The procedure for conducting a software fault-estimation method is then outlined, highlighting the major tasks involved. The contents of the guideline are based on our own experience and a review of research guidelines developed for a PSA

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

  4. Communication Management Guidelines for Software Organizations in Pakistan with clients from Afghanistan

    Science.gov (United States)

    Arif Shah, Muhammad; Hashim, Rathiah; Shah, Adil Ali; Farooq Khattak, Umar

    2016-11-01

    Developing software through Global Software Development (GSD) became very common now days in the software industry. Pakistan is one of the countries where projects are taken and designed from different countries including Afghanistan. The purpose of this paper is to identify and provide an analysis on several communication barriers that can have a negative impact on the project and to provide management guidelines for medium size software organizations working in Pakistan with clients from Afghanistan and to overcome these communication barriers and challenges organizations face when coordinating with client. Initially we performed a literature review to identify different communication barriers and to check if there are any standardized communications management guidelines for medium size software houses provided in the past. The second stage of the research paper involves guidelines with vendor's perspective that include interviews and focus group discussions with different stakeholders and employees of software houses with clients from Afghanistan. Based on those interviews and discussions we established communication management guidelines in order to overcome the communication problems and barriers working with clients from Afghanistan. As a result of the literature review, we have identified that barriers such as cultural barriers and language barrier were one of the main reasons behind the project failure and suggested that software organizations working in Pakistan should follow certain defined communication guidelines in order to overcome communication barriers that affect the project directly.

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

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

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

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

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

  10. Application of industry-standard guidelines for the validation of avionics software

    Science.gov (United States)

    Hayhurst, Kelly J.; Shagnea, Anita M.

    1990-01-01

    The application of industry standards to the development of avionics software is discussed, focusing on verification and validation activities. It is pointed out that the procedures that guide the avionics software development and testing process are under increased scrutiny. The DO-178A guidelines, Software Considerations in Airborne Systems and Equipment Certification, are used by the FAA for certifying avionics software. To investigate the effectiveness of the DO-178A guidelines for improving the quality of avionics software, guidance and control software (GCS) is being developed according to the DO-178A development method. It is noted that, due to the extent of the data collection and configuration management procedures, any phase in the life cycle of a GCS implementation can be reconstructed. Hence, a fundamental development and testing platform has been established that is suitable for investigating the adequacy of various software development processes. In particular, the overall effectiveness and efficiency of the development method recommended by the DO-178A guidelines are being closely examined.

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

  12. Radiologic measurement of extraocular muscle volumes in patients with Graves' orbitopathy: a review and guideline

    NARCIS (Netherlands)

    Bijlsma, Ward R.; Mourits, Maarten Ph

    2006-01-01

    OBJECTIVE: To evaluate and compare techniques for extraocular muscle (EOM) volume measurement and to provide guidelines for future measurements. DESIGN: Systematic review. RESULTS: Existing techniques used to measure extraocular muscle volumes on radiologic scans can be divided into manual

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

  14. IMAGE information monitoring and applied graphics software environment. Volume 4. Applications 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. This four volume report includes an Executive Overview of the IMAGE package (Volume 1), followed by Software Description (Volume II), User's Guide (Volume III), and Description of Example Applications (Volume IV)

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

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

  17. Software

    Energy Technology Data Exchange (ETDEWEB)

    Macedo, R.; Budd, G.; Ross, E.; Wells, P.

    2010-07-15

    The software section of this journal presented new software programs that have been developed to help in the exploration and development of hydrocarbon resources. Software provider IHS Inc. has made additions to its geological and engineering analysis software tool, IHS PETRA, a product used by geoscientists and engineers to visualize, analyze and manage well production, well log, drilling, reservoir, seismic and other related information. IHS PETRA also includes a directional well module and a decline curve analysis module to improve analysis capabilities in unconventional reservoirs. Petris Technology Inc. has developed a software to help manage the large volumes of data. PetrisWinds Enterprise (PWE) helps users find and manage wellbore data, including conventional wireline and MWD core data; analysis core photos and images; waveforms and NMR; and external files documentation. Ottawa-based Ambercore Software Inc. has been collaborating with Nexen on the Petroleum iQ software for steam assisted gravity drainage (SAGD) producers. Petroleum iQ integrates geology and geophysics data with engineering data in 3D and 4D. Calgary-based Envirosoft Corporation has developed a software that reduces the costly and time-consuming effort required to comply with Directive 39 of the Alberta Energy Resources Conservation Board. The product includes an emissions modelling software. Houston-based Seismic Micro-Technology (SMT) has developed the Kingdom software that features the latest in seismic interpretation. Holland-based Joa Oil and Gas and Calgary-based Computer Modelling Group have both supplied the petroleum industry with advanced reservoir simulation software that enables reservoir interpretation. The 2010 software survey included a guide to new software applications designed to facilitate petroleum exploration, drilling and production activities. Oil and gas producers can use the products for a range of functions, including reservoir characterization and accounting. In

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

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

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

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

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

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

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

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

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

    Science.gov (United States)

    2010-08-01

    developed products. The above definition was derived from these references: [IEEE-CS 2008] ISO /IEC 12207 , IEEE Std 12207 -2008, Systems and Software...Systems [CNSS 2009]. Software quality Capability of a software product to satisfy stated and implied needs when used under specified conditions [ ISO ...Curriculum ISO International Organization for Standardization IT information technology KA knowledge area KU knowledge unit MBA Master of

  7. [Definition of nodal volumes in breast cancer treatment and segmentation guidelines].

    Science.gov (United States)

    Kirova, Y M; Castro Pena, P; Dendale, R; Campana, F; Bollet, M A; Fournier-Bidoz, N; Fourquet, A

    2009-06-01

    To assist in the determination of breast and nodal volumes in the setting of radiotherapy for breast cancer and establish segmentation guidelines. Materials and methods. Contrast metarial enhanced CT examinations were obtained in the treatment position in 25 patients to clearly define the target volumes. The clinical target volume (CTV) including the breast, internal mammary nodes, supraclavicular and subclavicular regions and axxilary region were segmented along with the brachial plexus and interpectoral nodes. The following critical organs were also segmented: heart, lungs, contralateral breast, thyroid, esophagus and humeral head. A correlation between clinical and imaging findings and meeting between radiation oncologists and breast specialists resulted in a better definition of irradiation volumes for breast and nodes with establishement of segmentation guidelines and creation of an anatomical atlas. A practical approach, based on anatomical criteria, is proposed to assist in the segmentation of breast and node volumes in the setting of breast cancer treatment along with a definition of irradiation volumes.

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

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

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

  11. Dynamic Displays for Tactical Planning. Volume 3. Software Documentation

    Science.gov (United States)

    1979-12-01

    Figure 3-7. High-Level Flow of Data. -18- I 4.0 MAJOR SOFTWARE MODULES This section contains write -ups on the major subprograms in TOMM. Criteria for...pages, arranged in alphabetical order. Each write -up includes the name of the subprogram at the top of the page, followed by: (1) a list of the overlays...IEN1, iELt ,0tl.3) CALL 6HLT 900 F IM AT (13) IEL= IEL*5 GO TO 20 10 CALL tPUT(IELrII4,-3Gp0J CALL GCHA(lFNfIEIL~l*009I) CALL tIiL I vA 11H15,99*J) CLAd

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

    Science.gov (United States)

    2011-07-01

    thods and process of model-driven development. • Pressman , Roger S., Software Engineering: A Practitioner’s Approach, 6th ed. McGraw Hill, 2009...audience • [Bishop 2002] Chapter 18 • [Allen 2008] Chapters 1, 2 • [ Pressman 2009] Chapter 1 • [Merkow 2010] Chapter 3 • [Mouratidis 2007...Allen 2008] Chapters 3,4 • [ Pressman 2009] Chapters 3,4 • [Merkow 2010] Chapter 5 • [DHS 2008-2009a] • [Mellado 2010] • [CERT 2009] 3

  13. Evaluation of a new software tool for the automatic volume calculation of hepatic tumors. First results

    International Nuclear Information System (INIS)

    Meier, S.; Mildenberger, P.; Pitton, M.; Thelen, M.; Schenk, A.; Bourquain, H.

    2004-01-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.) [de

  14. International Spine Radiosurgery Consortium Consensus Guidelines for Target Volume Definition in Spinal Stereotactic Radiosurgery

    International Nuclear Information System (INIS)

    Cox, Brett W.; Spratt, Daniel E.; Lovelock, Michael; Bilsky, Mark H.; Lis, Eric; Ryu, Samuel; Sheehan, Jason; Gerszten, Peter C.; Chang, Eric; Gibbs, Iris; Soltys, Scott; Sahgal, Arjun; Deasy, Joe; Flickinger, John; Quader, Mubina; Mindea, Stefan

    2012-01-01

    Purpose: Spinal stereotactic radiosurgery (SRS) is increasingly used to manage spinal metastases. However, target volume definition varies considerably and no consensus target volume guidelines exist. This study proposes consensus target volume definitions using common scenarios in metastatic spine radiosurgery. Methods and Materials: Seven radiation oncologists and 3 neurological surgeons with spinal radiosurgery expertise independently contoured target and critical normal structures for 10 cases representing common scenarios in metastatic spine radiosurgery. Each set of volumes was imported into the Computational Environment for Radiotherapy Research. Quantitative analysis was performed using an expectation maximization algorithm for Simultaneous Truth and Performance Level Estimation (STAPLE) with kappa statistics calculating agreement between physicians. Optimized confidence level consensus contours were identified using histogram agreement analysis and characterized to create target volume definition guidelines. Results: Mean STAPLE agreement sensitivity and specificity was 0.76 (range, 0.67-0.84) and 0.97 (range, 0.94-0.99), respectively, for gross tumor volume (GTV) and 0.79 (range, 0.66-0.91) and 0.96 (range, 0.92-0.98), respectively, for clinical target volume (CTV). Mean kappa agreement was 0.65 (range, 0.54-0.79) for GTV and 0.64 (range, 0.54-0.82) for CTV (P<.01 for GTV and CTV in all cases). STAPLE histogram agreement analysis identified optimal consensus contours (80% confidence limit). Consensus recommendations include that the CTV should include abnormal marrow signal suspicious for microscopic invasion and an adjacent normal bony expansion to account for subclinical tumor spread in the marrow space. No epidural CTV expansion is recommended without epidural disease, and circumferential CTVs encircling the cord should be used only when the vertebral body, bilateral pedicles/lamina, and spinous process are all involved or there is extensive metastatic

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

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

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

  18. CrossTalk. The Journal of Defense Software Engineering. Volume 15, Number 12, December 2002

    Science.gov (United States)

    2002-12-01

    Journal of Defense Software Engineering. Volume 15, Number 12, December 2002 5a. CONTRACT NUMBER 5b. GRANT NUMBER 5c. PROGRAM ELEMENT NUMBER 6...You sit backwards on Disneyland rides to see how they do the special effects. • You’ve tried to repair a $5 radio. • You look forward to Christmas so

  19. Measuring stone volume - three-dimensional software reconstruction or an ellipsoid algebra formula?

    Science.gov (United States)

    Finch, William; Johnston, Richard; Shaida, Nadeem; Winterbottom, Andrew; Wiseman, Oliver

    2014-04-01

    To determine the optimal method for assessing stone volume, and thus stone burden, by comparing the accuracy of scalene, oblate, and prolate ellipsoid volume equations with three-dimensional (3D)-reconstructed stone volume. Kidney stone volume may be helpful in predicting treatment outcome for renal stones. While the precise measurement of stone volume by 3D reconstruction can be accomplished using modern computer tomography (CT) scanning software, this technique is not available in all hospitals or with routine acute colic scanning protocols. Therefore, maximum diameters as measured by either X-ray or CT are used in the calculation of stone volume based on a scalene ellipsoid formula, as recommended by the European Association of Urology. In all, 100 stones with both X-ray and CT (1-2-mm slices) were reviewed. Complete and partial staghorn stones were excluded. Stone volume was calculated using software designed to measure tissue density of a certain range within a specified region of interest. Correlation coefficients among all measured outcomes were compared. Stone volumes were analysed to determine the average 'shape' of the stones. The maximum stone diameter on X-ray was 3-25 mm and on CT was 3-36 mm, with a reasonable correlation (r = 0.77). Smaller stones (15 mm towards scalene ellipsoids. There was no difference in stone shape by location within the kidney. As the average shape of renal stones changes with diameter, no single equation for estimating stone volume can be recommended. As the maximum diameter increases, calculated stone volume becomes less accurate, suggesting that larger stones have more asymmetric shapes. We recommend that research looking at stone clearance rates should use 3D-reconstructed stone volumes when available, followed by prolate, oblate, or scalene ellipsoid formulas depending on the maximum stone diameter. © 2013 The Authors. BJU International © 2013 BJU International.

  20. A treatment planning comparison of four target volume contouring guidelines for locally advanced pancreatic cancer radiotherapy

    International Nuclear Information System (INIS)

    Fokas, Emmanouil; Eccles, Cynthia; Patel, Neel; Chu, Kwun-Ye; Warren, Samantha; McKenna, W. Gillies; Brunner, Thomas B.

    2013-01-01

    Background and purpose: Contouring of target volumes varies significantly in radiotherapy of pancreatic ductal adenocarcinoma (PDAC). There is a lack of consensus as to whether elective lymph nodes (eLN’s) should be included or not in the planning target volume (PTV). In the present study we analyzed the dosimetric coverage of the eLN’s and organs at risk (OAR) by comparing four different contouring guidelines. Methods and materials: PTVs were delineated with (Oxford and RTOG guidelines) or without (Michigan and SCALOP guidelines) including the eLNs in eleven patients with PDAC. eLNs included the peripancreatic, paraaortic, paracaval, celiac trunk, superior mesenteric and portal vein clinical target volumes (CTVs). A 3D-CRT plan (50.40 Gy in 28 fractions) was performed to analyze and compare the dosimetric coverage of all eLNs and OAR between the 4 contouring guidelines. Results: The size of Oxford and RTOG PTVs was comparable and significantly larger than the SCALOP and Michigan PTVs. Interestingly the eLNs received a significant amount of incidental dose irradiation by PTV-based plans that only aimed to treat the tumor without the eLNs. The dosimetric coverage of eLN presented a large variability according to the respective contouring methods. The difference in the size of the 4 PTVs was reflected to the dose distribution at the OAR. Conclusions: Our study provides important information regarding the impact of different contouring guidelines on the dose distribution to the eLNs and the OAR in patients with locally advanced PDAC treated with radiotherapy

  1. Radiologic measurement of extraocular muscle volumes in patients with Graves' orbitopathy: a review and guideline.

    Science.gov (United States)

    Bijlsma, Ward R; Mourits, Maarten Ph

    2006-06-01

    To evaluate and compare techniques for extraocular muscle (EOM) volume measurement and to provide guidelines for future measurements. Systematic review. Existing techniques used to measure extraocular muscle volumes on radiologic scans can be divided into manual outlining, computer assisted and automated segmentation. Both computed tomography (CT) and magnetic resonance (MR) image datasets can be used. On CT scans, one best measures muscle volume using region grow segmentation, accepting an overestimation of true volume by inevitable inclusion of non-muscular tissue. On high resolution MRI scans, single muscles can be outlined manually, but measurements include only part of the muscle due to poor tissue contrast at the orbital apex. Measurement errors can be reduced 3.5% by exact horizontal repositioning. A measured volume change of at least 6-17% is required to demonstrate a significant difference. Currently the best choice for EOM volume measurements on CT images is computer assisted grey value segmentation and on MRI images is manual outlining of individual muscles. Because of the time required and the complexity of the measurements, present EOM volume measurement is as yet only suitable for research purposes.

  2. [Development of analysis software package for the two kinds of Japanese fluoro-d-glucose-positron emission tomography guideline].

    Science.gov (United States)

    Matsumoto, Keiichi; Endo, Keigo

    2013-06-01

    Two kinds of Japanese guidelines for the data acquisition protocol of oncology fluoro-D-glucose-positron emission tomography (FDG-PET)/computed tomography (CT) scans were created by the joint task force of the Japanese Society of Nuclear Medicine Technology (JSNMT) and the Japanese Society of Nuclear Medicine (JSNM), and published in Kakuigaku-Gijutsu 27(5): 425-456, 2007 and 29(2): 195-235, 2009. These guidelines aim to standardize PET image quality among facilities and different PET/CT scanner models. The objective of this study was to develop a personal computer-based performance measurement and image quality processor for the two kinds of Japanese guidelines for oncology (18)F-FDG PET/CT scans. We call this software package the "PET quality control tool" (PETquact). Microsoft Corporation's Windows(™) is used as the operating system for PETquact, which requires 1070×720 image resolution and includes 12 different applications. The accuracy was examined for numerous applications of PETquact. For example, in the sensitivity application, the system sensitivity measurement results were equivalent when comparing two PET sinograms obtained from the PETquact and the report. PETquact is suited for analysis of the two kinds of Japanese guideline, and it shows excellent spec to performance measurements and image quality analysis. PETquact can be used at any facility if the software package is installed on a laptop computer.

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

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

  5. Software Engineering Laboratory (SEL) data base reporting software user's guide and system description. Volume 1: Introduction and user's guide

    Science.gov (United States)

    1983-01-01

    Reporting software programs provide formatted listings and summary reports of the Software Engineering Laboratory (SEL) data base contents. The operating procedures and system information for 18 different reporting software programs are described. Sample output reports from each program are provided.

  6. Three Software Tools for Viewing Sectional Planes, Volume Models, and Surface Models of a Cadaver Hand.

    Science.gov (United States)

    Chung, Beom Sun; Chung, Min Suk; Shin, Byeong Seok; Kwon, Koojoo

    2018-02-19

    The hand anatomy, including the complicated hand muscles, can be grasped by using computer-assisted learning tools with high quality two-dimensional images and three-dimensional models. The purpose of this study was to present up-to-date software tools that promote learning of stereoscopic morphology of the hand. On the basis of horizontal sectioned images and outlined images of a male cadaver, vertical planes, volume models, and surface models were elaborated. Software to browse pairs of the sectioned and outlined images in orthogonal planes and software to peel and rotate the volume models, as well as a portable document format (PDF) file to select and rotate the surface models, were produced. All of the software tools were downloadable free of charge and usable off-line. The three types of tools for viewing multiple aspects of the hand could be adequately employed according to individual needs. These new tools involving the realistic images of a cadaver and the diverse functions are expected to improve comprehensive knowledge of the hand shape. © 2018 The Korean Academy of Medical Sciences.

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

  8. Network, system, and status software enhancements for the autonomously managed electrical power system breadboard. Volume 1: Project summary

    Science.gov (United States)

    Mckee, James W.

    1990-01-01

    This volume (1 of 4) gives a summary of the original AMPS software system configuration, points out some of the problem areas in the original software design that this project is to address, and in the appendix collects all the bimonthly status reports. The purpose of AMPS is to provide a self reliant system to control the generation and distribution of power in the space station. The software in the AMPS breadboard can be divided into three levels: the operating environment software, the protocol software, and the station specific software. This project deals only with the operating environment software and the protocol software. The present station specific software will not change except as necessary to conform to new data formats.

  9. Factors controlling volume errors through 2D gully erosion assessment: guidelines for optimal survey design

    Science.gov (United States)

    Castillo, Carlos; Pérez, Rafael

    2017-04-01

    The assessment of gully erosion volumes is essential for the quantification of soil losses derived from this relevant degradation process. Traditionally, 2D and 3D approaches has been applied for this purpose (Casalí et al., 2006). Although innovative 3D approaches have recently been proposed for gully volume quantification, a renewed interest can be found in literature regarding the useful information that cross-section analysis still provides in gully erosion research. Moreover, the application of methods based on 2D approaches can be the most cost-effective approach in many situations such as preliminary studies with low accuracy requirements or surveys under time or budget constraints. The main aim of this work is to examine the key factors controlling volume error variability in 2D gully assessment by means of a stochastic experiment involving a Monte Carlo analysis over synthetic gully profiles in order to 1) contribute to a better understanding of the drivers and magnitude of gully erosion 2D-surveys uncertainty and 2) provide guidelines for optimal survey designs. Owing to the stochastic properties of error generation in 2D volume assessment, a statistical approach was followed to generate a large and significant set of gully reach configurations to evaluate quantitatively the influence of the main factors controlling the uncertainty of the volume assessment. For this purpose, a simulation algorithm in Matlab® code was written, involving the following stages: - Generation of synthetic gully area profiles with different degrees of complexity (characterized by the cross-section variability) - Simulation of field measurements characterised by a survey intensity and the precision of the measurement method - Quantification of the volume error uncertainty as a function of the key factors In this communication we will present the relationships between volume error and the studied factors and propose guidelines for 2D field surveys based on the minimal survey

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

    Energy Technology Data Exchange (ETDEWEB)

    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.

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

  12. LLCEDATA and LLCECALC for Windows version 1.0, Volume 3: Software verification and validation

    International Nuclear Information System (INIS)

    McFadden, J.G.

    1998-01-01

    LLCEDATA and LLCECALC for Windows are user-friendly computer software programs that work together to determine the proper waste designation, handling, and disposition requirements for Long Length Contaminated Equipment (LLCE). LLCEDATA reads from a variety of data bases to produce an equipment data file(EDF) that represents a snapshot of both the LLCE and the tank from which it originates. LLCECALC reads the EDF and the gamma assay file (AV2) that is produced by the flexible Receiver Gamma Energy Analysis System. LLCECALC performs corrections to the AV2 file as it is being read and characterizes the LLCE. Both programs produce a variety of reports, including a characterization report and a status report. The status report documents each action taken by the user, LLCEDATA, and LLCECALC. Documentation for LLCEDATA and LLCECALC for Windows is available in three volumes. Volume 1 is a user's manual, which is intended as a quick reference for both LLCEDATA and LLCECALC. Volume 2 is a technical manual, which discusses system limitations and provides recommendations to the LLCE process. Volume 3 documents LLCEDATA and LLCECALC's verification and validation. Two of the three installation test cases, from Volume 1, are independently confirmed. Data bases used in LLCEDATA are verified and referenced. Both phases of LLCECALC process gamma and characterization, are extensively tested to verify that the methodology and algorithms used are correct

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

  14. Comparison of Perfusion CT Software to Predict the Final Infarct Volume After Thrombectomy.

    Science.gov (United States)

    Austein, Friederike; Riedel, Christian; Kerby, Tina; Meyne, Johannes; Binder, Andreas; Lindner, Thomas; Huhndorf, Monika; Wodarg, Fritz; Jansen, Olav

    2016-09-01

    Computed tomographic perfusion represents an interesting physiological imaging modality to select patients for reperfusion therapy in acute ischemic stroke. The purpose of our study was to determine the accuracy of different commercial perfusion CT software packages (Philips (A), Siemens (B), and RAPID (C)) to predict the final infarct volume (FIV) after mechanical thrombectomy. Single-institutional computed tomographic perfusion data from 147 mechanically recanalized acute ischemic stroke patients were postprocessed. Ischemic core and FIV were compared about thrombolysis in cerebral infarction (TICI) score and time interval to reperfusion. FIV was measured at follow-up imaging between days 1 and 8 after stroke. In 118 successfully recanalized patients (TICI 2b/3), a moderately to strongly positive correlation was observed between ischemic core and FIV. The highest accuracy and best correlation are shown in early and fully recanalized patients (Pearson r for A=0.42, B=0.64, and C=0.83; P<0.001). Bland-Altman plots and boxplots demonstrate smaller ranges in package C than in A and B. Significant differences were found between the packages about over- and underestimation of the ischemic core. Package A, compared with B and C, estimated more than twice as many patients with a malignant stroke profile (P<0.001). Package C best predicted hypoperfusion volume in nonsuccessfully recanalized patients. Our study demonstrates best accuracy and approximation between the results of a fully automated software (RAPID) and FIV, especially in early and fully recanalized patients. Furthermore, this software package overestimated the FIV to a significantly lower degree and estimated a malignant mismatch profile less often than other software. © 2016 American Heart Association, Inc.

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

  16. Extrusion Process by Finite Volume Method Using OpenFoam Software

    International Nuclear Information System (INIS)

    Matos Martins, Marcelo; Tonini Button, Sergio; Divo Bressan, Jose; Ivankovic, Alojz

    2011-01-01

    The computational codes are very important tools to solve engineering problems. In the analysis of metal forming process, such as extrusion, this is not different because the computational codes allow analyzing the process with reduced cost. Traditionally, the Finite Element Method is used to solve solid mechanic problems, however, the Finite Volume Method (FVM) have been gaining force in this field of applications. This paper presents the velocity field and friction coefficient variation results, obtained by numerical simulation using the OpenFoam Software and the FVM to solve an aluminum direct cold extrusion process.

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

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

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

    International Nuclear Information System (INIS)

    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; Barley, S; Sorell, V; Karangelis, G; Button, T

    2016-01-01

    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

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

  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. ESTRO consensus guideline on target volume delineation for elective radiation therapy of early stage breast cancer

    International Nuclear Information System (INIS)

    Offersen, Birgitte V.; Boersma, Liesbeth J.; Kirkove, Carine; Hol, Sandra; Aznar, Marianne C.; Biete Sola, Albert; Kirova, Youlia M.; Pignol, Jean-Philippe; Remouchamps, Vincent; Verhoeven, Karolien; Weltens, Caroline; Arenas, Meritxell; Gabrys, Dorota; Kopek, Neil; Krause, Mechthild; Lundstedt, Dan; Marinko, Tanja

    2015-01-01

    Background and purpose: Delineation of clinical target volumes (CTVs) is a weak link in radiation therapy (RT), and large inter-observer variation is seen in breast cancer patients. Several guidelines have been proposed, but most result in larger CTVs than based on conventional simulator-based RT. The aim was to develop a delineation guideline obtained by consensus between a broad European group of radiation oncologists. Material and methods: During ESTRO teaching courses on breast cancer, teachers sought consensus on delineation of CTV through dialogue based on cases. One teacher delineated CTV on CT scans of 2 patients, followed by discussion and adaptation of the delineation. The consensus established between teachers was sent to other teams working in the same field, both locally and on a national level, for their input. This was followed by developing a broad consensus based on discussions. Results: Borders of the CTV encompassing a 5 mm margin around the large veins, running through the regional lymph node levels were agreed, and for the breast/thoracic wall other vessels were pointed out to guide delineation, with comments on margins for patients with advanced breast cancer. Conclusion: The ESTRO consensus on CTV for elective RT of breast cancer, endorsed by a broad base of the radiation oncology community, is presented to improve consistency

  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. Isobio software: biological dose distribution and biological dose volume histogram from physical dose conversion using linear-quadratic-linear model.

    Science.gov (United States)

    Jaikuna, Tanwiwat; Khadsiri, Phatchareewan; Chawapun, Nisa; Saekho, Suwit; Tharavichitkul, Ekkasit

    2017-02-01

    To develop an in-house software program that is able to calculate and generate the biological dose distribution and biological dose volume histogram by physical dose conversion using the linear-quadratic-linear (LQL) model. The Isobio software was developed using MATLAB version 2014b to calculate and generate the biological dose distribution and biological dose volume histograms. The physical dose from each voxel in treatment planning was extracted through Computational Environment for Radiotherapy Research (CERR), and the accuracy was verified by the differentiation between the dose volume histogram from CERR and the treatment planning system. An equivalent dose in 2 Gy fraction (EQD 2 ) was calculated using biological effective dose (BED) based on the LQL model. The software calculation and the manual calculation were compared for EQD 2 verification with pair t -test statistical analysis using IBM SPSS Statistics version 22 (64-bit). Two and three-dimensional biological dose distribution and biological dose volume histogram were displayed correctly by the Isobio software. Different physical doses were found between CERR and treatment planning system (TPS) in Oncentra, with 3.33% in high-risk clinical target volume (HR-CTV) determined by D 90% , 0.56% in the bladder, 1.74% in the rectum when determined by D 2cc , and less than 1% in Pinnacle. The difference in the EQD 2 between the software calculation and the manual calculation was not significantly different with 0.00% at p -values 0.820, 0.095, and 0.593 for external beam radiation therapy (EBRT) and 0.240, 0.320, and 0.849 for brachytherapy (BT) in HR-CTV, bladder, and rectum, respectively. The Isobio software is a feasible tool to generate the biological dose distribution and biological dose volume histogram for treatment plan evaluation in both EBRT and BT.

  7. Open-source Software for Demand Forecasting of Clinical Laboratory Test Volumes Using Time-series Analysis.

    Science.gov (United States)

    Mohammed, Emad A; Naugler, Christopher

    2017-01-01

    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. 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. 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. This tool will allow anyone with historic test volume data to model future demand.

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

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

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

    Science.gov (United States)

    2013-02-01

    comprehen- sive software development process, which incorporates best practices as well as standards such as IEEE 12207 -2008. The contractor will be...5], defines software quality as the degree to which software possesses a desired combination of attributes. Similarly, ISO /IEC 9126-1:2001 [6], one...attributes of the quality characteristics defined in ISO /IEC 9126-1. It should be noted that the 9126-series is being revised as part of the Software Product

  11. Spacelab user implementation assessment study. (Software requirements analysis). Volume 2: Technical report

    Science.gov (United States)

    1976-01-01

    The engineering analyses and evaluation studies conducted for the Software Requirements Analysis are discussed. Included are the development of the study data base, synthesis of implementation approaches for software required by both mandatory onboard computer services and command/control functions, and identification and implementation of software for ground processing activities.

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

  13. CrossTalk: The Journal of Defense Software Engineering. Volume 19, Number 9

    Science.gov (United States)

    2006-09-01

    activities to ISO /IEC 15288 system life cycle and ISO /IEC 12207 software life cycle processes. • Microsoft Security Development Lifecycle (SDL) [18, 19...Standardization/International Electrotechnical Commission ( ISO / IEC) Standard 15026 System and Software Assurance, which adds securi- ty assurance...Software ProcessSM (TSPSM Secure) [21]. The CMM and ISO /IEC process models are defined at a higher level of abstraction than SDL and CLASP, which

  14. CrossTalk: The Journal of Defense Software Engineering. Volume 21, Number 8

    Science.gov (United States)

    2008-08-01

    distributed black -and-white copy to its current form and shape. It is my hope that CrossTalk continues to publish insightful articles for another 20...Free: The Art of Making Quality Certain. New York: Mentor, New American Library, 1979. 7. Humphrey, Watts S. Managing the Software Process. Reading, MA...managing editor. The jazz trio worked their magic attracting a broader software audience as they infused topics outside the original embedded software

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

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

  17. Network, system, and status software enhancements for the autonomously managed electrical power system breadboard. Volume 3: Commands specification

    Science.gov (United States)

    Mckee, James W.

    1990-01-01

    This volume (3 of 4) contains the specification for the command language for the AMPS system. The volume contains a requirements specification for the operating system and commands and a design specification for the operating system and command. The operating system and commands sits on top of the protocol. The commands are an extension of the present set of AMPS commands in that the commands are more compact, allow multiple sub-commands to be bundled into one command, and have provisions for identifying the sender and the intended receiver. The commands make no change to the actual software that implement the commands.

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

  19. ESTRO ACROP guidelines for target volume definition in the treatment of locally advanced non-small cell lung cancer.

    Science.gov (United States)

    Nestle, Ursula; De Ruysscher, Dirk; Ricardi, Umberto; Geets, Xavier; Belderbos, Jose; Pöttgen, Christoph; Dziadiuszko, Rafal; Peeters, Stephanie; Lievens, Yolande; Hurkmans, Coen; Slotman, Ben; Ramella, Sara; Faivre-Finn, Corinne; McDonald, Fiona; Manapov, Farkhad; Putora, Paul Martin; LePéchoux, Cécile; Van Houtte, Paul

    2018-04-01

    Radiotherapy (RT) plays a major role in the curative treatment of locally advanced non-small cell lung cancer (NSCLC). Therefore, the ACROP committee was asked by the ESTRO to provide recommendations on target volume delineation for standard clinical scenarios in definitive (chemo)radiotherapy (RT) and adjuvant RT for locally advanced NSCLC. The guidelines given here are a result of the evaluation of a structured questionnaire followed by a consensus discussion, voting and writing procedure within the committee. Hence, we provide advice for methods and time-points of diagnostics and imaging before the start of treatment planning and for the mandatory and optional imaging to be used for planning itself. Concerning target volumes, recommendations are given for GTV delineation of primary tumour and lymph nodes followed by issues related to the delineation of CTVs for definitive and adjuvant radiotherapy. In the context of PTV delineation, recommendations about the management of geometric uncertainties and target motion are given. We further provide our opinions on normal tissue delineation and organisational and responsibility questions in the process of target volume delineation. This guideline intends to contribute to the standardisation and optimisation of the process of RT treatment planning for clinical practice and prospective studies. Copyright © 2018 Elsevier B.V. All rights reserved.

  20. A Handbook for Public Playground Safety. Volume II: Technical Guidelines for Equipment and Surfacing.

    Science.gov (United States)

    Consumer Product Safety Commission, Washington, DC.

    This handbook suggests safety guidelines for public playground equipment and describes various surfaces used under the equipment and possible injuries resulting from falls. The handbook is intended for use mainly by manufacturers, installers, school and park officials, and others interested in technical criteria for public playground equipment.…

  1. CrossTalk: The Journal of Defense Software Engineering. Volume 21, Number 4

    National Research Council Canada - National Science Library

    Jones, Capers; Henderson, Kym; Zwikael, Ofer; Lipke, Walt; Coe, David J; Premeaux, David; Armour, Phillip G

    2008-01-01

    CONTENTS: 1) Software Tracking:The Last Defense Against Failure by Capers Jones: This article concentrates on four worst practices and the factors that most often lead to failure and litigation and gives advice on how to avoid them. 2...

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

    National Research Council Canada - National Science Library

    Jones, Capers; Huff, Lloyd; Novak, George; Lau, Yun-Tung; Torri, Stephen; Sanders, Derek; Hamilton, Drew; Evans, Gordon; Frost, Alison A; Campo, Michael J

    2007-01-01

    CONTENTS: 1) Geriatric Issues of Aging Software by Capers Jones: Capers Jones discusses the need of every company to evaluate and consider best practices for maintenance and to avoid common worst practices. 2...

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

  4. Crosstalk: The Journal of Defense Software Engineering. Volume 22, Number 2, February 2009

    Science.gov (United States)

    2009-02-01

    possible system attacks. by Ron Greenfield and Dr. Charley Tichenor Enforcing Static Program Properties to Enable Safety-Critical Use of Java Software...Assurance by Ron Greenfield and Dr. Charley Tichenor, and Dr. Kelvin Nilsen’s Enforcing Static Program Properties in Safety-Critical Java Software Components...01&lang=en>. 5. Shakespeare, William. The Tempest. 6. Intel. “How Chips are Made.” 2008 <www.intel.com/ education /making chips/preparation.htm>. 7

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

    Science.gov (United States)

    2016-01-06

    markets [GuW12]. We thus believe our complementary research places us at an extraordinary advantage to conduct the proposed study that addresses a major...supporting “Bring Your Own Devices” (BYOD)? 22 New business models for OA software components ● Franchising ● Enterprise licensing ● Metered usage...paths IP and cybersecurity requirements will need continuous attention! 35 New business models for OA software components ● Franchising ● Enterprise

  6. Research to develop guidelines for cathodic protection of concentric neutral cables, volume 3

    Science.gov (United States)

    Hanck, J. A.; Nekoksa, G.

    1982-08-01

    Data associated with the corrosion of concentric neutral (CN) wires of direct buried primary cables were statistically analyzed, and guidelines for cathodic protection of CN wires for the electric utility industry were developed. The cathodic protection are reported. Field tests conducted at 36 bellholes excavated in California, Oklahoma, and North Carolina are described. Details of the electrochemical, chemical, bacteriological, and sieve analyses of native soil and imported backfill samples are also included.

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

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

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

    Science.gov (United States)

    2006-11-01

    8>. 7. Wallace, Delores R. Practical Soft- ware Reliability Modeling. Proc. of the 26th Annual NASA Goddard Software Engineering Workshop, Nov. 2001...STAR WARS TO STAR TREK To Request Back Issues on Topics Not Listed Above, Please Contact <stsc. customerservice@hill.af.mil>. About the Authors Kym

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

    Science.gov (United States)

    2012-04-01

    both editorial oversight and technical review of the journal. CrossTalk’s mission is to encour- age the engineering development of software to improve...sending e-mail. (Robertson, 2011) Mobile Workers and related products - Telecommuting -- the home office - Pressure to provide tools and access to

  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)

    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

  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)

    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

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

    Energy Technology Data Exchange (ETDEWEB)

    NONE

    2003-05-16

    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.

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

    Energy Technology Data Exchange (ETDEWEB)

    NONE

    2005-02-23

    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.

  15. Site locality identification study: Hanford Site. Volume I. Methodology, guidelines, and screening

    International Nuclear Information System (INIS)

    1980-07-01

    Presented in this report are the results of the site locality identification study for the Hanford Site using a screening process. To enable evaluation of the entire Hanford Site, the screening process was applied to a somewhat larger area; i.e., the Pasco Basin. The study consisted of a series of screening steps that progressively focused on smaller areas which are within the Hanford Site and which had a higher potential for containing suitable repository sites for nuclear waste than the areas not included for further study. Five site localities, designated H-1, H-2, H-3, H-4, H-5 (Figure A), varying in size from approximately 10 to 50 square miles, were identified on the Hanford Site. It is anticipated that each site locality may contain one or more candidate sites suitable for a nuclear waste repository. The site locality identification study began with definition of objectives and the development of guidelines for screening. Three objectives were defined: (1) maximize public health and safety; (2) minimize adverse environmental and socioeconomic impacts; and (3) minimize system costs. The screening guidelines have numerical values that provided the basis for the successive reduction of the area under study and to focus on smaller areas that had a higher likelihood of containing suitable sites

  16. Computer-generated display system guidelines. Volume 2. Developing an evaluation plan

    International Nuclear Information System (INIS)

    1984-09-01

    Volume 1 of this report provides guidance to utilities on the design of displays and the selection and retrofit of a computer-generated display system in the control room of an operating nuclear power plant. Volume 2 provides guidance on planning and managing empirical evaluation of computer-generated display systems, particularly when these displays are primary elements of computer-based operator aids. The guidance provided is in terms of a multilevel evaluation methodology that enables sequential consideration of three primary issues: (1) compatibility; (2) understandability; and (3) effectiveness. The evaluation process approaches these three issues with a top-down review of system objectives, functions, tasks, and information requirements. The process then moves bottom-up from lower-level to higher-level issues, employing different evaluation methods at each level in order to maximize the efficiency and effectiveness of the evaluation process

  17. CrossTalk: The Journal of Defense Software Engineering. Volume 19, Number 12, December 2006

    Science.gov (United States)

    2006-12-01

    process. The industry average for project investment in its requirements process is 3 percent of project costs; data from NASA shows that when 8- 14...requirements error is a defect that is dis- covered in delivered code that is a result of a requirement statement. Data from NASA provided by requirements...CENTRICITY AUG2006 c ADA 2005 SEPT2006 c SOFTWARE ASSURANCE OCT2006 c STAR WARS TO STAR TREK NOV2006 c MANAGEMENT BASICS To Request Back Issues on Topics

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

    Science.gov (United States)

    2005-06-01

    Bollinger The MITRE Corporation1 Progress brings new dangers: Powerful home computers, inexpensive high-speed Internet access, telecommuting , and software...been using for years. Sure enough, GIANT was able to finish removing the hard - core spyware. At some point, my Internet security package had been... The sad truth is that if you do nothing more than attach a Windows PC to the Internet over a high- speed line, it will be subjected to the first

  19. Computer-Aided Design for Built-In-Test (CADBIT) - Software Specification. Volume 3

    Science.gov (United States)

    1989-10-01

    CADD COMAN WIDO IO-CNURET MSL PPLYING~ TET ATEN Figur 3-13- TUTORIA FIGUR PLCMI IN CAD-NVIOMENT ON BOAR SEFTST- 1"os-rnenu, long-tur d nnnih que- list...have software package for reliability calculation A-8 LIBRARY ELEMENT DATA SHE T’" BIT TECHNIQUE: ON-BOARD ROM CATEGORY: L’ONG TUTORIA PAGE ,5 of 14

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

    Science.gov (United States)

    2009-06-01

    to measure impacted functions not covered by the International Function Point User’s Group (IFPUG) Counting Practices Manual ( CPM ) 4.2. If you are...foggy on the ins and outs of IFPUG or CPM 4.2, or just want a refresher, Total Metrics has simplified the concepts down to an easily under- stood two...information from your organization’s perspective with the software defense industry. • Dedicated space in each issue. • Advertisements ranging from a full

  1. NASA System Safety Handbook. Volume 2: System Safety Concepts, Guidelines, and Implementation Examples

    Science.gov (United States)

    Dezfuli, Homayoon; Benjamin, Allan; Everett, Christopher; Feather, Martin; Rutledge, Peter; Sen, Dev; Youngblood, Robert

    2015-01-01

    This is the second of two volumes that collectively comprise the NASA System Safety Handbook. Volume 1 (NASASP-210-580) was prepared for the purpose of presenting the overall framework for System Safety and for providing the general concepts needed to implement the framework. Volume 2 provides guidance for implementing these concepts as an integral part of systems engineering and risk management. This guidance addresses the following functional areas: 1.The development of objectives that collectively define adequate safety for a system, and the safety requirements derived from these objectives that are levied on the system. 2.The conduct of system safety activities, performed to meet the safety requirements, with specific emphasis on the conduct of integrated safety analysis (ISA) as a fundamental means by which systems engineering and risk management decisions are risk-informed. 3.The development of a risk-informed safety case (RISC) at major milestone reviews to argue that the systems safety objectives are satisfied (and therefore that the system is adequately safe). 4.The evaluation of the RISC (including supporting evidence) using a defined set of evaluation criteria, to assess the veracity of the claims made therein in order to support risk acceptance decisions.

  2. Research to develop guidelines for cathodic protection of concentric neutral cables, volume 1

    Science.gov (United States)

    Hanck, J. A.; Nekoksa, G.

    1981-08-01

    Data associated with corrosion of concentric neutrals (CN) of direct buried cables from field tests conducted at 36 bellholes excavated in California, Oklahoma, and North Carolina are presented. The electrochemical, chemical, bacteriological, and sieve analyses of native soil and imported backfill samples are included. Up to 129 values were determined for each bellhole and stored on cards as a data bank. All values were statistically analyzed and correlated with corrosion found. The severity of corrosion correlated best with CN corrosion potentials, CN resistance measurements, coarseness of backfill, and soil resistivity. The guidelines for installation of cathodic protection on CN cables are to be based upon the evaluation of over 100 experimental cathodic protection systems and upon laboratory testing for protection criteria with and without ac effects.

  3. Comparison of automatic quantification software for the measurement of ventricular volume and ejection fraction in gated myocardial perfusion SPECT

    International Nuclear Information System (INIS)

    Van Staden, J.A.; Herbst, C.P.; Du Raan, H.; Lotter, M.G.; Otto, A.C.

    2004-01-01

    Full text: Introduction: Gated myocardial perfusion SPECT has been used to calculate left ventricular ejection fraction (LVEF) and left ventricular end-diastolic volume (LVEDV) and has correlated well with conventional methods. However, the comparative accuracy of and correlations across various types of gated SPECT software are not well understood. Materials and methods: Twelve patients participated in a radionuclide gated blood-pool (GBP) study in addition to undergoing 99m Tc-sestamibi gated SPECT. Three different software algorithms, Quantitative Gated SPECT (QGS) from Cedars-Sinai, MultiDim from Stanford University Medical School and GQUANT from Alfa Nuclear were used to compute LVEF and LVEDV. These software algorithms operate in 3-dimensional space, two dependent on surface detection and the other on statistical parameters. The LVEF as calculated from gated SPECT myocardial perfusion images were compared with LVEF calculated from the GBP studies in the same patients to assess accuracy of the three software algorithms. Results: The software success-rate was 92% (11/12 pts) for MultiDim and 100% for the QGS and GQUANT. Agreement between LVEF measured with MultiDim and QGS, MultiDim and GQUANT and QGS and GQUANT were excellent (LVEF-MuItidim 0.80 LVEF QGS +5.02, r = 0.93, LVEF GQUANT = 1.10 LVEF MuItidim -1.33, r 0.90 and LVEF GQUANT = 1.02 LVEF QGS -1.40, r = 0.96). The correlation coefficient for LVEF between gated SPECT and the GBP study was 0.95, 0.95 and 0.97, for MultiDim, GQUANT and QGS, respectively. Conclusion: All 3 software programs showed good correlation between LVEF for gated SPECT and the GBP study. Good agreement for LVEF was observed also between the three software algorithms. However, because each method has unique characteristics that depend on its specific algorithm and thus behaves differently in the various patients, the methods should not be used interchangeably. (author)

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

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

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

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

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

    International Nuclear Information System (INIS)

    Mangold, D.

    1993-05-01

    Software quality assurance is an area of concern 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

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

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

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

  12. Maintenance Manual for AUDIT. A System for Analyzing SESCOMP Software. Volume 4: Appendix D. Listings of the AUDIT Software for the IBM 360.

    Science.gov (United States)

    1977-08-01

    The AUDIT documentation provides the maintenance programmer personnel with the information to effectively maintain and use the AUDIT software. The ...SESCOMPSPEC’s) and produces reports detailing the deviations from those standards. The AUDIT software also examines a program unit to detect and report...changes in word length on the output of computer programs. This report contains the listings of the AUDIT software for the IBM 360. (Author)

  13. Maintenance Manual for AUDIT. A System for Analyzing SESCOMP Software. Volume 3: Appendix C - Listings of the AUDIT Software for the UNIVAC 1108.

    Science.gov (United States)

    1977-08-01

    The AUDIT documentation provides the maintenance programmer personnel with the information to effectively maintain and use the AUDIT software. The ...SESCOMPSPEC’s) and produces reports detailing the deviations from those standards. The AUDIT software also examines a program unit to detect and report...changes in word length on the output of computer programs. This report contains the listings of the AUDIT software for the UNIVAC 1108. (Author)

  14. Maintenance Manual for AUDIT. A System for Analyzing SESCOMP Software. Volume 2: Appendix B. Listings of the Audit Software for the CDC 6000.

    Science.gov (United States)

    1977-08-01

    The AUDIT documentation provides the maintenance programmer personnel with the information to effectively maintain and use the AUDIT software. The ...SESCOMPSPEC’s) and produces reports detailing the deviations from those standards. The AUDIT software also examines a program unit to detect and report...changes in word length on the output of computer programs. This report contains the listings of the AUDIT software for the CDC 6000. (Author)

  15. Guidelines for the content of records to support nuclear power plant operation, maintenance, and modification (NCIG-08): Volume 1, Guidelines: Final report

    International Nuclear Information System (INIS)

    Reedy, R.F.; Hegglin, D.P.

    1988-11-01

    The record systems at many nuclear power plant sites are becoming overloaded with unnecessary and superfluous records. The reason for this overload is that although the Codes and Standards list the record types to be retained, there is no definition for the contents of the records. This encourages varied interpretations which often lead to the approach of ''save everything''. This document provides guidelines for the content of records to support nuclear power plant operation, maintenance and modification. These Guidelines are based on an engineering approach to identify which data in the records are of ''significant value'' in (1) demonstrating capability for safe operation; (2) maintaining, reworking, repairing, replacing, or modifying an item; (3) determining the cause of an accident or malfunction of an item; and (4) providing required baseline data for in-service inspection. Particular topical issues affecting record retention needs, such as plant life extension activities, may require additional evaluation of data or records. By identifying the data to be retained in the records, it is possible to modify the record management system to substantially reduce the amount of unnecessary information being retained in the records. These Guidelines will provide for more uniform interpretation of requirements. The Guidelines are meant as an interpretation of current Codes, Standards and Regulatory Guides, and not as new requirements. Should any conflict exist between these Guidelines and the specified requirements of the NRC Regulations, the regulations govern. 4 tabs

  16. SU-F-BRA-14: Optimization of Dosimetric Guidelines for Accelerated Partial Breast Irradiation (APBI) Using the Strut-Adjusted Volume Implant (SAVI)

    International Nuclear Information System (INIS)

    Mooney, K; Altman, M; Garcia-Ramirez, J; Thomas, M; Zoberi, I; Mullen, D; DeWees, T; Esthappan, J

    2015-01-01

    Purpose: Treatment planning guidelines for accelerated partial breast irradiation (ABPI) using the strut-adjusted volume implant (SAVI) are inconsistent between the manufacturer and NSABP B-39/RTOG 0413 protocol. Furthermore neither set of guidelines accounts for different applicator sizes. The purpose of this work is to establish guidelines specific to the SAVI that are based on clinically achievable dose distributions. Methods: Sixty-two consecutive patients were implanted with a SAVI and prescribed to receive 34 Gy in 10 fractions twice daily using high dose-rate (HDR) Ir-192 brachytherapy. The target (PTV-EVAL) was defined per NSABP. The treatments were planned and evaluated using a combination of dosimetric planning goals provided by the NSABP, the manufacturer, and our prior clinical experience. Parameters evaluated included maximum doses to skin and ribs, and volumes of PTV-EVAL receiving 90%, 95%, 100%, 150%, and 200% of the prescription (V90, etc). All target parameters were evaluated for correlation with device size using the Pearson correlation coefficient. Revised dosimetric guidelines for target coverage and heterogeneity were determined from this population. Results: Revised guidelines for minimum target coverage (ideal in parentheses): V90≥95%(97%), V95≥90%(95%), V100≥88%(91%). The only dosimetric parameters that were significantly correlated (p<0.05) with device size were V150 and V200. Heterogeneity criteria were revised for the 6–1 Mini/6-1 applicators to V150≤30cc and V200≤15cc, and unchanged for the other sizes. Re-evaluation of patient plans showed 90% (56/62) met the revised minimum guidelines and 76% (47/62) met the ideal guidelines. All and 56/62 patients met our institutional guidelines for maximum skin and rib dose, respectively. Conclusions: We have optimized dosimetric guidelines for the SAVI applicators, and found that implementation of these revised guidelines for SAVI treatment planning yielded target coverage exceeding

  17. Evidence synthesis software.

    Science.gov (United States)

    Park, Sophie Elizabeth; Thomas, James

    2018-06-07

    It can be challenging to decide which evidence synthesis software to choose when doing a systematic review. This article discusses some of the important questions to consider in relation to the chosen method and synthesis approach. Software can support researchers in a range of ways. Here, a range of review conditions and software solutions. For example, facilitating contemporaneous collaboration across time and geographical space; in-built bias assessment tools; and line-by-line coding for qualitative textual analysis. EPPI-Reviewer is a review software for research synthesis managed by the EPPI-centre, UCL Institute of Education. EPPI-Reviewer has text mining automation technologies. Version 5 supports data sharing and re-use across the systematic review community. Open source software will soon be released. EPPI-Centre will continue to offer the software as a cloud-based service. The software is offered via a subscription with a one-month (extendible) trial available and volume discounts for 'site licences'. It is free to use for Cochrane and Campbell reviews. The next EPPI-Reviewer version is being built in collaboration with National Institute for Health and Care Excellence using 'surveillance' of newly published research to support 'living' iterative reviews. This is achieved using a combination of machine learning and traditional information retrieval technologies to identify the type of research each new publication describes and determine its relevance for a particular review, domain or guideline. While the amount of available knowledge and research is constantly increasing, the ways in which software can support the focus and relevance of data identification are also developing fast. Software advances are maximising the opportunities for the production of relevant and timely reviews. © Article author(s) (or their employer(s) unless otherwise stated in the text of the article) 2018. All rights reserved. No commercial use is permitted unless otherwise

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

    International Nuclear Information System (INIS)

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

    1985-08-01

    The Guidelines are intended to provide guidance to the user in preparing a written plan for a proposed nuclear organization and administration. The Guidelines allow for individual approaches to organizational structures to account for differences in plant size, number of operating units, number of plant sites, and the individual utility approach to providing technical support. These unique approaches, however, should meet the criteria of a reasoned, fully developed, and logically consistent focus on the user's organization in terms of organization of work, policies and procedures, staffing, and external relationships

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

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

  1. Impact of target volume coverage with Radiation Therapy Oncology Group (RTOG) 98-05 guidelines for transrectal ultrasound guided permanent Iodine-125 prostate implants

    International Nuclear Information System (INIS)

    Horwitz, Eric M.; Mitra, Raj K.; Uzzo, Robert G.; Das, Indra J.; Pinover, Wayne H.; Hanlon, Alexandra L.; McNeeley, Shawn W.; Hanks, Gerald E.

    2003-01-01

    Purpose: Despite the wide use of permanent prostate implants for the treatment of early stage prostate cancer, there is no consensus for optimal pre-implant planning guidelines that results in maximal post-implant target coverage. The purpose of this study was to compare post-implant target volume coverage and dosimetry between patients treated before and after Radiation Therapy Oncology Group (RTOG) 98-05 guidelines were adopted using several dosimetric endpoints. Materials and methods: Ten consecutively treated patients before the adoption of the RTOG 98-05 planning guidelines were compared with ten consecutively treated patients after implementation of the guidelines. Pre-implant planning for patients treated pre-RTOG was based on the clinical target volume (CTV) defined by the pre-implant TRUS definition of the prostate. The CTV was expanded in each dimension according to RTOG 98-05 and defined as the planning target volume. The evaluation target volume was defined as the post-implant computed tomography definition of the prostate based on RTOG 98-05 protocol recommendations. Implant quality indicators included V 100 , V 90 , V 100 , and Coverage Index (CI). Results: The pre-RTOG median V 100 , V 90 , D 90 , and CI values were 82.8, 88.9%, 126.5 Gy, and 17.1, respectively. The median post-RTOG V 100 , V 90 , D 90 , and CI values were 96.0, 97.8%, 169.2 Gy, and 4.0, respectively. These differences were all statistically significant. Conclusions: Implementation of the RTOG 98-05 implant planning guidelines has increased coverage of the prostate by the prescription isodose lines compared with our previous technique, as indicated by post-implant dosimetry indices such as V 100 , V 90 , D 90 . The CI was also improved significantly with the protocol guidelines. Our data confirms the validity of the RTOG 98-05 implant guidelines for pre-implant planning as it relates to enlargement of the CTV to ensure adequate margin between the CTV and the prescription isodose

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

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

  4. Achieving Better Buying Power through Acquisition of Open Architecture Software Systems. Volume 2 Understanding Open Architecture Software Systems: Licensing and Security Research and Recommendations

    Science.gov (United States)

    2016-01-06

    KWD00], as are  CORBA, Microsoft’s .NET, and Enterprise  Java  Beans.    ● Configured system or sub­system​ – These are software systems built to conform to...background.  55 Some OSS is multiply­licensed, or distributed under two or more licenses. The  MySQL  database  software is distributed either under GPLv2 for...Automation    The license metamodel, calculation, and an assortment of license interpretations are implemented  in a  Java  package. The calculation

  5. Proposal of a post-prostatectomy clinical target volume based on pre-operative MRI: volumetric and dosimetric comparison to the RTOG guidelines

    International Nuclear Information System (INIS)

    Croke, Jennifer; Maclean, Jillian; Nyiri, Balazs; Li, Yan; Malone, Kyle; Avruch, Leonard; Kayser, Cathleen; Malone, Shawn

    2014-01-01

    Recurrence rates following radiotherapy for prostate cancer in the post-operative adjuvant or salvage setting remain substantial. Previous work from our institution demonstrated that published prostate bed CTV guidelines frequently do not cover the pre-operative MRI defined prostate. Inadequate target delineation may contribute to the high recurrence rates, but increasing target volumes may increase dose to organs at risk. We propose guidelines for delineating post-prostatectomy target volumes based upon an individual’s co-registered pre-operative MRI. MRI-based CTVs and PTVs were compared to those created using the RTOG guidelines in 30 patients. Contours were analysed in terms of absolute volume, intersection volume (Jaccard Index) and the ability to meet the RADICALS and QUANTEC rectal and bladder constraints (tomotherapy IMRT plans with PTV coverage of V98% ≥98%). CTV MRI was a mean of 18.6% larger than CTV RTOG: CTV MRI mean 138 cc (range 72.3 - 222.2 cc), CTV RTOG mean 116.3 cc (range 62.1 - 176.6 cc), (p < 0.0001). The difference in mean PTV was only 4.6%: PTV MRI mean 386.9 cc (range 254.4 – 551.2), PTV RTOG mean 370 cc (range 232.3 - 501.6) (p = 0.05). The mean Jaccard Index representing intersection volume between CTVs was 0.72 and 0.84 for PTVs. Both criteria had a similar ability to meet rectal and bladder constraints. Rectal DVH: 77% of CTV RTOG cases passed all RADICALS criteria and 37% all QUANTEC criteria; versus 73% and 40% for CTV MRI (p = 1.0 for both). Bladder DVH; 47% of CTV RTOG cases passed all RADICALS criteria and 67% all QUANTEC criteria, versus 57% and 60% for CTV MRI (p = 0.61for RADICALS, p = 0.79 for QUANTEC). CTV MRI spares more of the lower anterior bladder wall than CTV RTOG but increases coverage of the superior lateral bladder walls. CTV contours based upon the patient’s co-registered pre-operative MRI in the post-prostatectomy setting may improve coverage of the individual’s prostate bed without substantially increasing

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

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

    Science.gov (United States)

    2011-02-01

    Aircraft Sustainment Group Tony Henderson 309th Software Maintenance Group Lt. Col. Brian Hermann, Ph.D. Defense Information Systems Agency Lt. Col...Solutions, Inc. Gordon Sleve Robbins Gioia LLC Larry Smith Software Technology Support Center Dr. John Sohl Weber State University Elizabeth Starrett OO-ALC

  8. Freely-available, true-color volume rendering software and cryohistology data sets for virtual exploration of the temporal bone anatomy.

    Science.gov (United States)

    Kahrs, Lüder Alexander; Labadie, Robert Frederick

    2013-01-01

    Cadaveric dissection of temporal bone anatomy is not always possible or feasible in certain educational environments. Volume rendering using CT and/or MRI helps understanding spatial relationships, but they suffer in nonrealistic depictions especially regarding color of anatomical structures. Freely available, nonstained histological data sets and software which are able to render such data sets in realistic color could overcome this limitation and be a very effective teaching tool. With recent availability of specialized public-domain software, volume rendering of true-color, histological data sets is now possible. We present both feasibility as well as step-by-step instructions to allow processing of publicly available data sets (Visible Female Human and Visible Ear) into easily navigable 3-dimensional models using free software. Example renderings are shown to demonstrate the utility of these free methods in virtual exploration of the complex anatomy of the temporal bone. After exploring the data sets, the Visible Ear appears more natural than the Visible Human. We provide directions for an easy-to-use, open-source software in conjunction with freely available histological data sets. This work facilitates self-education of spatial relationships of anatomical structures inside the human temporal bone as well as it allows exploration of surgical approaches prior to cadaveric testing and/or clinical implementation. Copyright © 2013 S. Karger AG, Basel.

  9. CrossTalk, The Journal of Defense Software Engineering. Volume 27, Number 4. July/August 2014

    Science.gov (United States)

    2014-07-01

    his writing. His works include “The Psychology of Computer Program- ming, An Introduction to General Systems Thinking, Becoming a Technical Leader ...en.wikipedia.org/wiki/Six_phases_of_a_big_ project). I am certainly not the originator. In 1997, Robert Glass published a book entitled “Software Runaways ...failures. In fact, to quote from the Amazon.com “blurb” on the book, Runaways brings a software engineer’s perspective to projects like: American

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

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

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

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

    Energy Technology Data Exchange (ETDEWEB)

    NONE

    2012-06-19

    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.

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

    Energy Technology Data Exchange (ETDEWEB)

    NONE

    2012-06-19

    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.

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

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

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

  18. 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; P<0.05 compared with CMR and 3D TTE). 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.

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

    Science.gov (United States)

    2015-02-01

    minority participation is low [24]. At UT Tyler, we conduct science camps for high-school girl students in the summer to encourage them to pursue STEM ...Intellectual Property Rights (Data Rights for commercial built software applications), CLE074 on Cybersecurity (March 2015 deployment), and CLL

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

    Science.gov (United States)

    2010-02-01

    Maintenance Group Weber State University Arrowpoint Solutions, Inc. Robbins Gioia LLC Software Technology Support Center Weber State University OO-ALC...Les Dupaix Monika Fast Robert W. Ferguson Dr. Doretta Gordon Dr. John A. “Drew” Hamilton Jr. Gary Hebert Tony Henderson Lt. Col. Brian Hermann, Ph.D

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

    Science.gov (United States)

    2014-04-01

    integrity and authenticity of the end product The Software Maintenance Group at Hill Air Force Base is recruiting civilians (U.S. Citizenship...B.Claise, “ Cisco Systems NetFlow Services Export Version 9”, October 2004, RFC 3954, <http://tools.ietf.org/html/rfc3954> 6. L. Daigle, “WHOIS

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

    Science.gov (United States)

    2012-02-01

    February 2012 25 HIGH MATURITY - THE PAYOFF expanded target audience of producers, buyers, and users of software products and systems bring with it...diet Pepsi and Ho-Hos. • You have read this list, and realized that several items apply to you. And it got less and less funny as you kept

  3. Selecting and Buying Educational Software.

    Science.gov (United States)

    Ahl, David H.

    1983-01-01

    Guidelines for selecting/buying educational software are discussed under the following headings: educational soundness; appropriateness; challenge and progress; motivation and reward; correctness; compatibility with systems; instructions and handlings. Includes several sources of software reviews. (JN)

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

    Science.gov (United States)

    2014-12-01

    conclusion lest the analysis is biased . 6 CrossTalk—November/December 2014 SOFTWARE ENGINEERING TOOLS AND THE PROCESSES THEY SUPPORT To demonstrate...In some Agile development environments the relative separa- tion between tools and processes is so seamless as to be almost subconscious to process...a well-articulated process description, but if the performer is a tool lover, he will find fault with the defined process, always having a bias for

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

    Science.gov (United States)

    2010-11-01

    such standards are International Standards Organization/ International Electrotechnical Commission ( ISO / IEC) standards 15288 for system engineering...and 12207 for software development. 13. Office of the DoD CIO. White Paper Phase I: A Competency Framework for the DoD Architect. Washington...processes in later phases. DoD-Centric Use Case Current support for net-centric operations is based on iso - lated deployments of relevant services in

  6. CrossTalk. The Journal of Defense Software Engineering. Volume 24, Number 5, Sep/Oct 2011

    Science.gov (United States)

    2011-09-01

    ancillary materials is counterfeit. Coun- terfeiting of ancillary materials may involve copying and slightly altering legitimate product data or...tools that implemented/applied the software protection mechanisms were authentic and trustworthy. IPR Enforcement Efforts In 2005, KPMG and the...2005. 5. KPMG and the Alliance for Gray Market and Counterfeit Abatement. “Managing the Risks of Counterfeiting in the Information Technology Industry

  7. CrossTalk: The Journal of Defense Software Engineering. Volume 22, Number 7, Nov/Dec 2009

    Science.gov (United States)

    2009-12-01

    anyone, and a public key, which is publicly advertised . A signer encrypts data using the recipient’s public key, and the receiver decrypts it with...of service. 6. Encryption certificates are advertised in the DoD via the Joint Enterprise Directory Service (located at <https:// jeds.gds.disa.mil...mainframe legacy code into an iPhone app. In Hell’s Kitchen, programmers try to find a software bug nestled inside two mil- lion lines of undocumented

  8. CrossTalk: The Journal of Defense Software Engineering. Volume 28, Number 2, March/April 2015

    Science.gov (United States)

    2015-04-01

    software is like striking gold in that you get a very high return on investment for testing. Optimization Technique #2 - Apply the Pareto Principle The... Pareto Principle (the 80/20 rule) that says you can get the majority of value from the minority of people, time or effort. In fact, my experience is...week test in two weeks. So, the client and I worked together to focus on key areas and skip minor areas. The test design was based on critical

  9. CrossTalk: The Journal of Defense Software Engineering. Volume 26, Number 3, May-June 2013

    Science.gov (United States)

    2013-06-01

    in which the pieces are being shaped at the same time they are being as- sembled. If I am honest, software is probably more like a Rube Goldberg ...losing the focus on architecting activities that help maintain the desired state, enable cost savings, and ensure delivery tempo when other agile...masters degrees and working as developers), accepted by the same in- structor, with counted LOC identically, yielded variations as great as 22:1, and

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

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

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

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

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

  15. CrossTalk: The Journal of Defense Software Engineering. Volume 22, Number 6, September/October 2009

    Science.gov (United States)

    2009-10-01

    distinguished intermediate gates (Y6, Y7) known as out- puts. We define a signal as a vertical reading of a column in the truth table (a fully enu...glanced at the EKG and noticed severe brady- cardia. He realized he had never re- started the ventilator. This patient ultimately died. [10] This accident...attacker to achieve his objective. Google “Ariane 5 Flight 501,” “Therac-25 accidents,” or “Toyota Prius software bug” to read about some dramat- ic

  16. Feasibility and performance of novel software to quantify metabolically active volumes and 3D partial volume corrected SUV and metabolic volumetric products of spinal bone marrow metastases on 18F-FDG-PET/CT.

    Science.gov (United States)

    Torigian, Drew A; Lopez, Rosa Fernandez; Alapati, Sridevi; Bodapati, Geetha; Hofheinz, Frank; van den Hoff, Joerg; Saboury, Babak; Alavi, Abass

    2011-01-01

    Our aim was to assess feasibility and performance of novel semi-automated image analysis software called ROVER to quantify metabolically active volume (MAV), maximum standardized uptake value-maximum (SUV(max)), 3D partial volume corrected mean SUV (cSUV(mean)), and 3D partial volume corrected mean MVP (cMVP(mean)) of spinal bone marrow metastases on fluorine-18 fluorodeoxyglucose-positron emission tomography/computerized tomography ((18)F-FDG-PET/CT). We retrospectively studied 16 subjects with 31 spinal metastases on FDG-PET/CT and MRI. Manual and ROVER determinations of lesional MAV and SUV(max), and repeated ROVER measurements of MAV, SUV(max), cSUV(mean) and cMVP(mean) were made. Bland-Altman and correlation analyses were performed to assess reproducibility and agreement. Our results showed that analyses of repeated ROVER measurements revealed MAV mean difference (D)=-0.03±0.53cc (95% CI(-0.22, 0.16)), lower limit of agreement (LLOA)=-1.07cc, and upper limit of agreement (ULOA)=1.01cc; SUV(max) D=0.00±0.00 with LOAs=0.00; cSUV(mean) D=-0.01±0.39 (95% CI(-0.15, 0.13)), LLOA=-0.76, and ULOA=0.75; cMVP(mean) D=-0.52±4.78cc (95% CI(-2.23, 1.23)), LLOA=-9.89cc, and ULOA=8.86cc. Comparisons between ROVER and manual measurements revealed volume D= -0.39±1.37cc (95% CI (-0.89, 0.11)), LLOA=-3.08cc, and ULOA=2.30cc; SUV(max) D=0.00±0.00 with LOAs=0.00. Mean percent increase in lesional SUV(mean) and MVP(mean) following partial volume correction using ROVER was 84.25±36.00% and 84.45±35.94% , respectively. In conclusion, it is feasible to estimate MAV, SUV(max), cSUV(mean), and cMVP(mean) of spinal bone marrow metastases from (18)F-FDG-PET/CT quickly and easily with good reproducibility via ROVER software. Partial volume correction is imperative, as uncorrected SUV(mean) and MVP(mean) are significantly underestimated, even for large lesions. This novel approach has great potential for practical, accurate, and precise combined structural-functional PET

  17. Network, system, and status software enhancements for the autonomously managed electrical power system breadboard. Volume 4: Graphical status display

    Science.gov (United States)

    Mckee, James W.

    1990-01-01

    This volume (4 of 4) contains the description, structured flow charts, prints of the graphical displays, and source code to generate the displays for the AMPS graphical status system. The function of these displays is to present to the manager of the AMPS system a graphical status display with the hot boxes that allow the manager to get more detailed status on selected portions of the AMPS system. The development of the graphical displays is divided into two processes; the creation of the screen images and storage of them in files on the computer, and the running of the status program which uses the screen images.

  18. IMAGE Programming Guidelines

    Energy Technology Data Exchange (ETDEWEB)

    Stehfest, E; De Waal, L.

    2010-09-15

    This document describes the requirements and guidelines for the software of the IMAGE system. The motivation for this report was a substantial restructuring of the source code for IMAGE version 2.5. The requirements and guidelines relate to design considerations as well as to aspects of maintainability and portability. The design considerations determine guidelines about subjects, such as program structure, model hierarchy, the use of data modules, and the error message system. Maintainability and portability aspects determine the guidelines on, for example, the Fortran 90 standard, naming conventions, code lay-out, and internal documentation.

  19. Network, system, and status software enhancements for the autonomously managed electrical power system breadboard. Volume 2: Protocol specification

    Science.gov (United States)

    Mckee, James W.

    1990-01-01

    This volume (2 of 4) contains the specification, structured flow charts, and code listing for the protocol. The purpose of an autonomous power system on a spacecraft is to relieve humans from having to continuously monitor and control the generation, storage, and distribution of power in the craft. This implies that algorithms will have been developed to monitor and control the power system. The power system will contain computers on which the algorithms run. There should be one control computer system that makes the high level decisions and sends commands to and receive data from the other distributed computers. This will require a communications network and an efficient protocol by which the computers will communicate. One of the major requirements on the protocol is that it be real time because of the need to control the power elements.

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

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

    Energy Technology Data Exchange (ETDEWEB)

    NONE

    2000-03-09

    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.

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

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

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

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

  6. Desiderata for Linguistic Software Design

    Science.gov (United States)

    Garretson, Gregory

    2008-01-01

    This article presents a series of guidelines both for researchers in search of software to be used in linguistic analysis and for programmers designing such software. A description of the intended audience and the types of software under consideration and a review of some relevant literature are followed by a discussion of several important…

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

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

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

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

  11. Framework Programmable Platform for the Advanced Software Development Workstation (FPP/ASDW). Demonstration framework document. Volume 1: Concepts and activity descriptions

    Science.gov (United States)

    Mayer, Richard J.; Blinn, Thomas M.; Dewitte, Paul S.; Crump, John W.; Ackley, Keith A.

    1992-01-01

    The Framework Programmable Software Development Platform (FPP) is a project aimed at effectively combining tool and data integration mechanisms with a model of the software development process to provide an intelligent integrated software development environment. Guided by the model, this system development framework will take advantage of an integrated operating environment to automate effectively the management of the software development process so that costly mistakes during the development phase can be eliminated. The Advanced Software Development Workstation (ASDW) program is conducting research into development of advanced technologies for Computer Aided Software Engineering (CASE).

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

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

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

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

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

  17. Quality Guidelines

    Science.gov (United States)

    ... this page: https://medlineplus.gov/criteria.html MedlinePlus Quality Guidelines To use the sharing features on this ... materials must also meet our existing quality guidelines. Quality, authority and accuracy of health content The organization's ...

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

  19. Space Guidelines for Libraries.

    Science.gov (United States)

    Wisconsin Coordinating Committee for Higher Education, Madison.

    The following guidelines are recommended: stack space--for each 10 volumes, one square foot of space; reading room--25 square feet per station x 20% of the total undergraduate population; carrel space--25% of the graduate enrollment x 45 square feet; office and auxilliary space--135 square feet x full time equivalent staff. (NI)

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

  1. Design Guidelines and Criteria for User/Operator Transactions with Battlefield Automated Systems. Volume III-A. Human Factors Analyses of User/ Operator Transactions with TACFIRE - The Tactical Fire Direction System

    Science.gov (United States)

    1981-02-01

    7. Reseaarch Product 81-26 - DESIGN GUIDELINES AND CRITERIA FOR USER/ I;. I’OPERATOR TRANSACTIONS WITH BATTLEFIELD AUTOMIATED SYSTEMS I’ /HVtAN...FACTORS XWLYSES :’F K~R/ OPERATOR TRANSACTIONS WTHT TACFIRE - THE TACTICAL FIRE DiRECTION SY2T3EM A HUMAN FACTORS TECHNICAL AREA L~h~h K L-J 1’ U~~i~ ll...Battlefield Auto- Inter : Oct 1979-Feb 1981 mated Systems Volume III-A: Human Factors 4t C/ Analyses of User/Operator Transactions with 6. PERFORMING

  2. Joint Logistics Commanders’ Biennial Software Workshop (4th) Orlando II: Solving the PDSS (Post Deployment Software Support) Challenge Held in Orlando, Florida on 27-29 January 87. Volume 2. Proceedings

    Science.gov (United States)

    1987-06-01

    described the state )f ruaturity of software engineering as being equivalent to the state of maturity of Civil Engineering before Pythagoras invented the...formal verification languages, theorem provers or secure configuration 0 management tools would have to be maintained and used in the PDSS Center to

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

  4. Clinical trials radiotherapy treatment plan review software : is this the first quantified assessment

    International Nuclear Information System (INIS)

    Hatton, J.A.; Cornes, D.A.

    2011-01-01

    Full text: Clinical trials require robust quality assurance (QA) procedures to ensure commonality of all treatments, with independent reviews to assess compliance with trial protocols. All clinical trials tools, including QA software, require testing for validity and reliability. enabling inter- and intra-trial comparison. Unlike clinical radiotherapy treatment planning (RTP) systems, review software has no published guidelines. This study describes the design and development of a test suite to quantify the performance of review software in TROG clinical trials. Test areas are image handling and reconstruction; geometric accuracy; dosimetric accuracy; dose-volume histogram (DVH) calculation; display of plan parameters. TROG have developed tests for commissioning plan review software, assessed with SWAN 2.3, and CMS Elekta FocalPro. While image handling tests were based on published guidelines for RTP systems, dosimetric tests used the TROG QA case review requirements. Treatment plans represented systems of all manufacturers (Pinnacle, Eclipse, Xio and Oncentra) used in Australasian centres. The test suite identified areas for SW A software development, including the DVH algorithm, changed to reduce calculation time. Results, in Fig. I, for known volumes of varying shapes and sizes, demonstrate differences between SWAN 2.1 and 2.3 when compared with Eclipse. Liaison with SWAN programmers enabled re-instatement of 2.1 algorithm. The test suite has quantified the RTP review software, prioritised areas for development with the programmers, and improved the user experience.

  5. Exploiting thesauri knowledge in medical guideline formalization

    OpenAIRE

    Serban, R.C.; ten Teije, A.C.M.

    2009-01-01

    Objectives: As in software product lifecycle, the effort spent in maintaining medical knowl edge in guidelines can be reduced, if modularization, formalization and tracking of domain knowledge are employed across the guideline development phases. Methods: We propose to exploit and combine knowledge templates with medical background knowledge from existing thesauri in order to produce reusable building blocks used in guideline development. These tem- plates enable easier guideline formalizatio...

  6. Upgrade Software and Computing

    CERN Document Server

    The LHCb Collaboration, CERN

    2018-01-01

    This document reports the Research and Development activities that are carried out in the software and computing domains in view of the upgrade of the LHCb experiment. The implementation of a full software trigger implies major changes in the core software framework, in the event data model, and in the reconstruction algorithms. The increase of the data volumes for both real and simulated datasets requires a corresponding scaling of the distributed computing infrastructure. An implementation plan in both domains is presented, together with a risk assessment analysis.

  7. 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 prostate biopsy and RP volumes decreased significantly. A panoramic vantage point is needed to evaluate the long-term consequences of the 2012 USPSTF recommendation.

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

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

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

  11. 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 variation<10%) for end-diastolic volume (EDV), end-systolic volume (ESV) and LVEF. Despite a slight underestimation of EDV using 3D TTE compared with CMR (bias=-22±34mL; P<0.0001), a significant correlation was found between the two measurements (r=0.93; P=0.0001). Enlarging default border detection settings leads to frequent volume overestimation in the general population, but improved agreement with CMR in patients with LVEF≤50%. Correlations between 3D TTE and CMR for ESV and LVEF were excellent (r=0.93 and r=0.91, respectively; P<0.0001). 3D TTE 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

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

  13. 23 CFR 650.211 - Guidelines.

    Science.gov (United States)

    2010-04-01

    ... 23 Highways 1 2010-04-01 2010-04-01 false Guidelines. 650.211 Section 650.211 Highways FEDERAL..., STRUCTURES, AND HYDRAULICS Erosion and Sediment Control on Highway Construction Projects § 650.211 Guidelines. (a) The FHWA adopts the AASHTO Highway Drainage Guidelines, Volume III, “Erosion and Sediment Control...

  14. Software Epistemology

    Science.gov (United States)

    2016-03-01

    in-vitro decision to incubate a startup, Lexumo [7], which is developing a commercial Software as a Service ( SaaS ) vulnerability assessment...LTS Label Transition System MUSE Mining and Understanding Software Enclaves RTEMS Real-Time Executive for Multi-processor Systems SaaS Software ...as a Service SSA Static Single Assignment SWE Software Epistemology UD/DU Def-Use/Use-Def Chains (Dataflow Graph)

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

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

  17. NASA's Software Safety Standard

    Science.gov (United States)

    Ramsay, Christopher M.

    2007-01-01

    NASA relies more and more on software to control, monitor, and verify its safety critical systems, facilities and operations. Since the 1960's there has hardly been a spacecraft launched that does not have a computer on board that will provide command and control services. There have been recent incidents where software has played a role in high-profile mission failures and hazardous incidents. For example, the Mars Orbiter, Mars Polar Lander, the DART (Demonstration of Autonomous Rendezvous Technology), and MER (Mars Exploration Rover) Spirit anomalies were all caused or contributed to by software. The Mission Control Centers for the Shuttle, ISS, and unmanned programs are highly dependant on software for data displays, analysis, and mission planning. Despite this growing dependence on software control and monitoring, there has been little to no consistent application of software safety practices and methodology to NASA's projects with safety critical software. Meanwhile, academia and private industry have been stepping forward with procedures and standards for safety critical systems and software, for example Dr. Nancy Leveson's book Safeware: System Safety and Computers. The NASA Software Safety Standard, originally published in 1997, was widely ignored due to its complexity and poor organization. It also focused on concepts rather than definite procedural requirements organized around a software project lifecycle. Led by NASA Headquarters Office of Safety and Mission Assurance, the NASA Software Safety Standard has recently undergone a significant update. This new standard provides the procedures and guidelines for evaluating a project for safety criticality and then lays out the minimum project lifecycle requirements to assure the software is created, operated, and maintained in the safest possible manner. This update of the standard clearly delineates the minimum set of software safety requirements for a project without detailing the implementation for those

  18. Computer software.

    Science.gov (United States)

    Rosenthal, L E

    1986-10-01

    Software is the component in a computer system that permits the hardware to perform the various functions that a computer system is capable of doing. The history of software and its development can be traced to the early nineteenth century. All computer systems are designed to utilize the "stored program concept" as first developed by Charles Babbage in the 1850s. The concept was lost until the mid-1940s, when modern computers made their appearance. Today, because of the complex and myriad tasks that a computer system can perform, there has been a differentiation of types of software. There is software designed to perform specific business applications. There is software that controls the overall operation of a computer system. And there is software that is designed to carry out specialized tasks. Regardless of types, software is the most critical component of any computer system. Without it, all one has is a collection of circuits, transistors, and silicone chips.

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

  20. Evaluation of automated decisionmaking methodologies and development of an integrated robotic system simulation, volume 2, part 1. Appendix A: Software documentation

    Science.gov (United States)

    Lowrie, J. W.; Fermelia, A. J.; Haley, D. C.; Gremban, K. D.; Vanbaalen, J.; Walsh, R. W.

    1982-01-01

    Documentation of the preliminary software developed as a framework for a generalized integrated robotic system simulation is presented. The program structure is composed of three major functions controlled by a program executive. The three major functions are: system definition, analysis tools, and post processing. The system definition function handles user input of system parameters and definition of the manipulator configuration. The analysis tools function handles the computational requirements of the program. The post processing function allows for more detailed study of the results of analysis tool function executions. Also documented is the manipulator joint model software to be used as the basis of the manipulator simulation which will be part of the analysis tools capability.

  1. Three-dimensional computer reconstruction of large tissue volumes based on composing series of high-resolution confocal images by GlueMRC and LinkMRC software

    Czech Academy of Sciences Publication Activity Database

    Karen, Petr; Jirkovská, M.; Tomori, Z.; Demjénová, E.; Janáček, Jiří; Kubínová, Lucie

    2003-01-01

    Roč. 62, č. 5 (2003), s. 415-422 ISSN 1059-910X R&D Projects: GA ČR GA304/01/0257 Grant - others:VEGA(SK) 2/1146/21; CZ-SK GA MŠk(CZ) KONTAKT 126/184 Institutional research plan: CEZ:AV0Z5011922 Keywords : 3D reconstruction * confocal microscopy * image processing Subject RIV: JC - Computer Hardware ; Software Impact factor: 2.307, year: 2003

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

  3. Effluent Guidelines

    Science.gov (United States)

    Effluent guidelines are national standards for wastewater discharges to surface waters and municipal sewage treatment plants. We issue the regulations for industrial categories based on the performance of treatment and control technologies.

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

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

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

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

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

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

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

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

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

  13. Demand-side management project for Tenaga Nasional Berhad. Energy efficiency guidelines. Progress report No. 3. Volume 1. Final report. Export trade information

    Energy Technology Data Exchange (ETDEWEB)

    NONE

    1993-05-01

    This study, conducted by the California Energy Commission, was funded by the U.S. Trade and Development Agency. The report summarizes a demand-side management study performed for the Tenaga Nasional Berhad Headquarters Building. The purpose of the study was to identify and evaluate demand side management measures (DSMs) that would reduce energy costs of the facility. Volume 1 is divided into the following sections: (1.0) Executive Summary; (2.0) Facility Background; (3.0) Ventilating and Air Conditioning Systems Description; (4.0) Lightning System Description; Figures, Tables, and Appendices.

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

    International Nuclear Information System (INIS)

    Viswanathan, Akila N.; Erickson, Beth; Gaffney, David K.; Beriwal, Sushil; Bhatia, Sudershan K.; Lee Burnett, Omer; D'Souza, David P.; Patil, Nikhilesh; Haddock, Michael G.; Jhingran, Anuja; Jones, Ellen L.; Kunos, Charles A.; Lee, Larissa J.; Lin, Lilie L.; Mayr, Nina A.; Petersen, Ivy; Petric, Primoz; Portelance, Lorraine; Small, William; Strauss, Jonathan B.

    2014-01-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)

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

  16. Software quality - how is it achieved?

    International Nuclear Information System (INIS)

    Straker, E.A.

    1986-01-01

    Although software quality can't be quantified, the tools and techniques to achieve high quality are available. As management stresses the need for definable software quality programs from vendors and subcontractors and provides the incentives for these programs, the quality of software will improve. EPRI could provide the leadership in establishing guidelines for a balanced software quality program and through workshops provide training to utility staff and management on the methods for evaluating the characteristics of quality software. With the more complex systems discussed at this workshop and particularly with the trend toward the use of artificial intelligence, the importance of quality software will grow dramatically

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

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

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

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

  1. Toward Prostate Cancer Contouring Guidelines on Magnetic Resonance Imaging: Dominant Lesion Gross and Clinical Target Volume Coverage Via Accurate Histology Fusion

    International Nuclear Information System (INIS)

    Gibson, Eli; Bauman, Glenn S.; Romagnoli, Cesare; Cool, Derek W.; Bastian-Jordan, Matthew; Kassam, Zahra; Gaed, Mena; Moussa, Madeleine; Gómez, José A.; Pautler, Stephen E.; Chin, Joseph L.; Crukley, Cathie; Haider, Masoom A.

    2016-01-01

    Purpose: Defining prostate cancer (PCa) lesion clinical target volumes (CTVs) for multiparametric magnetic resonance imaging (mpMRI) could support focal boosting or treatment to improve outcomes or lower morbidity, necessitating appropriate CTV margins for mpMRI-defined gross tumor volumes (GTVs). This study aimed to identify CTV margins yielding 95% coverage of PCa tumors for prospective cases with high likelihood. Methods and Materials: Twenty-five men with biopsy-confirmed clinical stage T1 or T2 PCa underwent pre-prostatectomy mpMRI, yielding T2-weighted, dynamic contrast-enhanced, and apparent diffusion coefficient images. Digitized whole-mount histology was contoured and registered to mpMRI scans (error ≤2 mm). Four observers contoured lesion GTVs on each mpMRI scan. CTVs were defined by isotropic and anisotropic expansion from these GTVs and from multiparametric (unioned) GTVs from 2 to 3 scans. Histologic coverage (proportions of tumor area on co-registered histology inside the CTV, measured for Gleason scores [GSs] ≥6 and ≥7) and prostate sparing (proportions of prostate volume outside the CTV) were measured. Nonparametric histologic-coverage prediction intervals defined minimal margins yielding 95% coverage for prospective cases with 78% to 92% likelihood. Results: On analysis of 72 true-positive tumor detections, 95% coverage margins were 9 to 11 mm (GS ≥ 6) and 8 to 10 mm (GS ≥ 7) for single-sequence GTVs and were 8 mm (GS ≥ 6) and 6 mm (GS ≥ 7) for 3-sequence GTVs, yielding CTVs that spared 47% to 81% of prostate tissue for the majority of tumors. Inclusion of T2-weighted contours increased sparing for multiparametric CTVs with 95% coverage margins for GS ≥6, and inclusion of dynamic contrast-enhanced contours increased sparing for GS ≥7. Anisotropic 95% coverage margins increased the sparing proportions to 71% to 86%. Conclusions: Multiparametric magnetic resonance imaging–defined GTVs expanded by appropriate margins

  2. Toward Prostate Cancer Contouring Guidelines on Magnetic Resonance Imaging: Dominant Lesion Gross and Clinical Target Volume Coverage Via Accurate Histology Fusion

    Energy Technology Data Exchange (ETDEWEB)

    Gibson, Eli [Robarts Research Institute, University of Western Ontario, London, Ontario (Canada); Biomedical Engineering, University of Western Ontario, London, Ontario (Canada); Centre for Medical Image Computing, University College London, London (United Kingdom); Department of Radiology, Radboud University Medical Centre, Nijmegen (Netherlands); Bauman, Glenn S., E-mail: glenn.bauman@lhsc.on.ca [Lawson Health Research Institute, London, Ontario (Canada); Department of Oncology, University of Western Ontario, London, Ontario (Canada); Romagnoli, Cesare; Cool, Derek W. [Department of Medical Imaging, University of Western Ontario, London, Ontario (Canada); Bastian-Jordan, Matthew [Department of Medical Imaging, University of Western Ontario, London, Ontario (Canada); Queensland Health, Brisbane, Queensland (Australia); Kassam, Zahra [Department of Medical Imaging, University of Western Ontario, London, Ontario (Canada); Gaed, Mena [Robarts Research Institute, University of Western Ontario, London, Ontario (Canada); Department of Pathology, University of Western Ontario, London, Ontario (Canada); Moussa, Madeleine; Gómez, José A. [Department of Pathology, University of Western Ontario, London, Ontario (Canada); Pautler, Stephen E.; Chin, Joseph L. [Lawson Health Research Institute, London, Ontario (Canada); Department of Urology, University of Western Ontario, London, Ontario (Canada); Crukley, Cathie [Robarts Research Institute, University of Western Ontario, London, Ontario (Canada); Lawson Health Research Institute, London, Ontario (Canada); Haider, Masoom A. [Department of Medical Imaging, Sunnybrook Health Sciences Centre, Toronto, Ontario (Canada); and others

    2016-09-01

    Purpose: Defining prostate cancer (PCa) lesion clinical target volumes (CTVs) for multiparametric magnetic resonance imaging (mpMRI) could support focal boosting or treatment to improve outcomes or lower morbidity, necessitating appropriate CTV margins for mpMRI-defined gross tumor volumes (GTVs). This study aimed to identify CTV margins yielding 95% coverage of PCa tumors for prospective cases with high likelihood. Methods and Materials: Twenty-five men with biopsy-confirmed clinical stage T1 or T2 PCa underwent pre-prostatectomy mpMRI, yielding T2-weighted, dynamic contrast-enhanced, and apparent diffusion coefficient images. Digitized whole-mount histology was contoured and registered to mpMRI scans (error ≤2 mm). Four observers contoured lesion GTVs on each mpMRI scan. CTVs were defined by isotropic and anisotropic expansion from these GTVs and from multiparametric (unioned) GTVs from 2 to 3 scans. Histologic coverage (proportions of tumor area on co-registered histology inside the CTV, measured for Gleason scores [GSs] ≥6 and ≥7) and prostate sparing (proportions of prostate volume outside the CTV) were measured. Nonparametric histologic-coverage prediction intervals defined minimal margins yielding 95% coverage for prospective cases with 78% to 92% likelihood. Results: On analysis of 72 true-positive tumor detections, 95% coverage margins were 9 to 11 mm (GS ≥ 6) and 8 to 10 mm (GS ≥ 7) for single-sequence GTVs and were 8 mm (GS ≥ 6) and 6 mm (GS ≥ 7) for 3-sequence GTVs, yielding CTVs that spared 47% to 81% of prostate tissue for the majority of tumors. Inclusion of T2-weighted contours increased sparing for multiparametric CTVs with 95% coverage margins for GS ≥6, and inclusion of dynamic contrast-enhanced contours increased sparing for GS ≥7. Anisotropic 95% coverage margins increased the sparing proportions to 71% to 86%. Conclusions: Multiparametric magnetic resonance imaging–defined GTVs expanded by appropriate margins

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

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

  5. Results of a Survey Software Development Project Management in the U.S. Aerospace Industry. Volume II. Project Management Techniques, Procedures and Tools.

    Science.gov (United States)

    1979-12-18

    I Z I UO W-1 eu 0 - 0 tD CL 0, 0 -I7 NW 2 - x M.j a CL W2 X 41 a ~ 0 0,a 4~~ 0 Z .D .J 0 2. N 0 ~N IU 0 4 - 2 0 ~. 0 Q. ’o ~ 0, 𔃺e U - U ~- 0, 0 -a...0 .44 A A A Ao 0 - 2. -U 2- 4’ A 4’ A o .~ 0 .~ 2. flJ 2. A Ao ~. a 2. 𔃾 2- @2 @2 @2 A 0 .~. a I- 2. Xii - 0 2 @2 ON AXe Re 2- Oi. K A.. A A AU .40...Project manager or person appointed by him SE/ TD project manager b. Senior ADP Manager Director Director computer programming Software program design

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

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

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

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

  10. Software Reviews.

    Science.gov (United States)

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

    1984-01-01

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

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

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

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

  14. AIDS guidelines.

    Science.gov (United States)

    Berger, R

    1986-04-30

    The Sun article, "Employers finding that AIDS in the workplace is a managerial nightmare" (April 3), did not accurately portray the status of AIDS in the workplace. The AIDS virus, HTLV III, is transmitted by body fluids, primarily semen and blood, and there is no known risk of transmitting the virus by casual contact in the workplace. The Center for Disease Control (CDC) released guidelines for child care workers last August. Guidelines on preventing transmission of AIDS in the workplace were issued by CDC in November 1985. These guidelines specifically discussed health care, personal service, and food service workers. The recommendations were against routine screening. Furthermore, employment should not be restricted on the basis of a positive HTLV III antibody test. A person with HTLV III infection should be exempt from the workplace only if there are circumstances interfering with job performance. In Maryland, the Governor's Task Force on AIDS has gone on record as endorsing CDC guidelines related to employment. Furthermore, the task force condemns discrimination based on the disease AIDS, AIDS Related Complex (ARC), or HTLV III infection. Increasingly AIDS patients are being considered legally disabled and therefore are protected by federal and state laws prohibiting discrimination on the basis of a handicap. Marylanders who are subjected to mandatory HTLV III screening in the workplace, or if discriminated against on the basis of HTLV III inefction, should contact the Maryland Commission on Human Relations, the Maryland Department of Health and Mental Hygiene, or the Health Education Resource Organization (HERO). All 3 of these resources guarantee confidentiality. It is only by employees reporting incidents that a nightmare in the workplace can be avoided in Maryland. full text

  15. GRADE guidelines

    DEFF Research Database (Denmark)

    Guyatt, Gordon H; Thorlund, Kristian; Oxman, Andrew D

    2013-01-01

    Presenting continuous outcomes in Summary of Findings tables presents particular challenges to interpretation. When each study uses the same outcome measure, and the units of that measure are intuitively interpretable (e.g., duration of hospitalization, duration of symptoms), presenting differences...... and absolute effects, presenting the ratio of the means of intervention and control groups, and presenting the results in minimally important difference units. We outline the merits and limitations of each alternative and provide guidance for meta-analysts and guideline developers....

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

  17. Guidelines for optimization of planar HDR implants

    International Nuclear Information System (INIS)

    Zwicker, R.D.; Schmidt-Ullrich, R.

    1996-01-01

    Purpose: Conventional low dose rate (LDR) planar Ir-192 implants are typically carried out using at most a few different source strengths. Remote afterloading offers a much higher degree of flexibility with individually programmable dwell times. Dedicated software is available to generate individual dwell times producing isodose surfaces which contour as closely as possible the target volume. The success of these algorithms in enclosing the target volume while sparing normal tissues is dependent on the positioning of the source guides which constrain the dwell points. In this work we provide source placement guidelines for optimal coverage and dose uniformity in planar high dose rate (HDR) implants. The resulting distributions are compared with LDR treatments in terms of dose uniformity and early and late tissue effects. Materials and methods: Computer studies were undertaken to determine source positions and dwell times for optimal dose uniformity in planar HDR implants, and the results were compared to those obtained using corresponding LDR implant geometries. The improvements in the dose distributions achieved with the remote after loader are expected to help offset the increased late tissue effects which can occur when LDR irradiation is replaced with a few large HDR fractions. Equivalent differential volume-dose (DVD) curves for early and late effects were calculated for different numbers of HDR fractions using a linear-quadratic model and compared to the corresponding curves for the LDR regime. Results: Tables of source placement parameters were generated as guidelines for achieving highly homogeneous planar HDR dose distributions. Differential volume-dose data generated inside the target volume provide a quantitative measure of the improvement in real dose homogeneity obtained with remote afterloading. The net result is a shift of the peak in the DVD curve toward lower doses relative to the LDR implant. The equivalent DVD curves for late effects obtained

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

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

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

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

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

    Energy Technology Data Exchange (ETDEWEB)

    NONE

    2000-08-04

    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.

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

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

  5. Software Authentication

    International Nuclear Information System (INIS)

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

    2001-01-01

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

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

  7. Dietary guidelines

    DEFF Research Database (Denmark)

    Jelsøe, Erling

    2015-01-01

    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...... and political resistance against initiatives that are perceived as being in conflict with the values of a market economy and free trade. Furthermore, there are controversies that can be broadly characterised as relating to the politics of knowledge and have to do with the differentiation of expertise...

  8. Reviews, Software.

    Science.gov (United States)

    Science Teacher, 1988

    1988-01-01

    Reviews two computer software packages for use in physical science, physics, and chemistry classes. Includes "Physics of Model Rocketry" for Apple II, and "Black Box" for Apple II and IBM compatible computers. "Black Box" is designed to help students understand the concept of indirect evidence. (CW)

  9. Software Reviews.

    Science.gov (United States)

    Kinnaman, Daniel E.; And Others

    1988-01-01

    Reviews four educational software packages for Apple, IBM, and Tandy computers. Includes "How the West was One + Three x Four,""Mavis Beacon Teaches Typing,""Math and Me," and "Write On." Reviews list hardware requirements, emphasis, levels, publisher, purchase agreements, and price. Discusses the strengths…

  10. Software Review.

    Science.gov (United States)

    McGrath, Diane, Ed.

    1989-01-01

    Reviewed is a computer software package entitled "Audubon Wildlife Adventures: Grizzly Bears" for Apple II and IBM microcomputers. Included are availability, hardware requirements, cost, and a description of the program. The murder-mystery flavor of the program is stressed in this program that focuses on illegal hunting and game…

  11. Software Reviews.

    Science.gov (United States)

    Teles, Elizabeth, Ed.; And Others

    1990-01-01

    Reviewed are two computer software packages for Macintosh microcomputers including "Phase Portraits," an exploratory graphics tool for studying first-order planar systems; and "MacMath," a set of programs for exploring differential equations, linear algebra, and other mathematical topics. Features, ease of use, cost, availability, and hardware…

  12. MIAWARE Software

    DEFF Research Database (Denmark)

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

    2008-01-01

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

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

  14. Severe accident management guidelines tool

    International Nuclear Information System (INIS)

    Gutierrez Varela, Javier; Tanarro Onrubia, Augustin; Martinez Fanegas, Rafael

    2014-01-01

    Severe Accident is addressed by means of a great number of documents such as guidelines, calculation aids and diagnostic trees. The response methodology often requires the use of several documents at the same time while Technical Support Centre members need to assess the appropriate set of equipment within the adequate mitigation strategies. In order to facilitate the response, TECNATOM has developed SAMG TOOL, initially named GGAS TOOL, which is an easy to use computer program that clearly improves and accelerates the severe accident management. The software is designed with powerful features that allow the users to focus on the decision-making process. Consequently, SAMG TOOL significantly improves the severe accident training, ensuring a better response under a real situation. The software is already installed in several Spanish Nuclear Power Plants and trainees claim that the methodology can be followed easier with it, especially because guidelines, calculation aids, equipment information and strategies availability can be accessed immediately (authors)

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

  16. Software Tools for Software Maintenance

    Science.gov (United States)

    1988-10-01

    COMMUNICATIONS, AND COMPUTER SCIENCES I ,(AIRMICS) FO~SOFTWARE TOOLS (.o FOR SOF1 ’ARE MAINTENANCE (ASQBG-1-89-001) October, 1988 DTIC ELECTE -ifB...SUNWW~. B..c Program An~Iysw HA.c C-Tractr C Cobol Stncturing Facility VS Cobol 11 F-Scan Foctma Futbol Cobol Fortran Sltiuc Code Anaiyaer Fortran IS

  17. EPIQR software

    Energy Technology Data Exchange (ETDEWEB)

    Flourentzos, F. [Federal Institute of Technology, Lausanne (Switzerland); Droutsa, K. [National Observatory of Athens, Athens (Greece); Wittchen, K.B. [Danish Building Research Institute, Hoersholm (Denmark)

    1999-11-01

    The support of the EPIQR method is a multimedia computer program. Several modules help the users of the method to treat the data collected during a diagnosis survey, to set up refurbishment scenario and calculate their cost or energy performance, and finally to visualize the results in a comprehensive way and to prepare quality reports. This article presents the structure and the main features of the software. (au)

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

  19. Instructor Support Feature Guidelines. Volume 2.

    Science.gov (United States)

    1986-05-01

    starts his final approach, the display formats change to provide graphic depictions of glideslope, lineup and airspeed parameters, and indications of...and evaluate several facets of student performance simultaneously . It may also provide objective, standardized performance measurement of the student’s...procedures monitoring feature shall provide the instructor cation with a method of monitoring the sequential mission training activities of a student. The

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

    Energy Technology Data Exchange (ETDEWEB)

    NONE

    2001-12-10

    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.

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

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

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

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

  5. Toward objective software process information : experiences from a case study

    NARCIS (Netherlands)

    Samalikova, J.; Kusters, R.J.; Trienekens, J.J.M.; Weijters, A.J.M.M.; Siemons, P.

    2011-01-01

    A critical problem in software development is the monitoring, control and improvement in the processes of software developers. Software processes are often not explicitly modeled, and manuals to support the development work contain abstract guidelines and procedures. Consequently, there are huge

  6. The ANS mathematics and computation software standards

    Energy Technology Data Exchange (ETDEWEB)

    Smetana, A. O. [Savannah River National Laboratory, Washington Savannah River Company, Aiken, SC 29808 (United States)

    2006-07-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)

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

  8. Study of evaluation techniques of software configuration management and reliability

    Energy Technology Data Exchange (ETDEWEB)

    Youn, Cheong; Baek, Y. W.; Kim, H. C.; Han, H. C.; Choi, C. R. [Chungnam National Univ., Taejon (Korea, Republic of)

    2001-03-15

    The Study of activities to solve software safety and quality must be executed in base of establishing software development process for digitalized nuclear plant. Especially study of software testing and Verification and Validation must executed. For this purpose methodologies and tools which can improve software qualities are evaluated and software Testing, V and V and Configuration Management which can be applied to software life cycle are investigated. This study establish a guideline that can be used to assure software safety and reliability requirements in digitalized nuclear plant systems.

  9. Software Prototyping

    Science.gov (United States)

    Del Fiol, Guilherme; Hanseler, Haley; Crouch, Barbara Insley; Cummins, Mollie R.

    2016-01-01

    Summary Background Health information exchange (HIE) between Poison Control Centers (PCCs) and Emergency Departments (EDs) could improve care of poisoned patients. However, PCC information systems are not designed to facilitate HIE with EDs; therefore, we are developing specialized software to support HIE within the normal workflow of the PCC using user-centered design and rapid prototyping. Objective To describe the design of an HIE dashboard and the refinement of user requirements through rapid prototyping. Methods Using previously elicited user requirements, we designed low-fidelity sketches of designs on paper with iterative refinement. Next, we designed an interactive high-fidelity prototype and conducted scenario-based usability tests with end users. Users were asked to think aloud while accomplishing tasks related to a case vignette. After testing, the users provided feedback and evaluated the prototype using the System Usability Scale (SUS). Results Survey results from three users provided useful feedback that was then incorporated into the design. After achieving a stable design, we used the prototype itself as the specification for development of the actual software. Benefits of prototyping included having 1) subject-matter experts heavily involved with the design; 2) flexibility to make rapid changes, 3) the ability to minimize software development efforts early in the design stage; 4) rapid finalization of requirements; 5) early visualization of designs; 6) and a powerful vehicle for communication of the design to the programmers. Challenges included 1) time and effort to develop the prototypes and case scenarios; 2) no simulation of system performance; 3) not having all proposed functionality available in the final product; and 4) missing needed data elements in the PCC information system. PMID:27081404

  10. Formal Verification of Mathematical Software. Volume 2

    Science.gov (United States)

    1990-05-01

    nplus i 1) (nplus ,j k) iter ZERO f s =s iter (SUCC n) f s = iter n f (f s) PROVE x=(SUCC x)’=’(!x)’ PROVE ’ nplus ZERO n’ = ent PROVE ’ nplus ( SUCO n...PROVE ’niess (SUCC n) (SUCC mn)’ = ’niess n mn’ PROVE ’niess n ( SUCO mn)’ = ’true’, (’nim’=’true’ V/ ’niess n in’=’true’) PROVE ’niess (SUCC n) mn

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

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

  13. Global Software Engineering: A Software Process Approach

    Science.gov (United States)

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

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

  14. Medical device software: defining key terms.

    Science.gov (United States)

    Pashkov, Vitalii; Gutorova, Nataliya; Harkusha, Andrii

    one of the areas of significant growth in medical devices has been the role of software - as an integral component of a medical device, as a standalone device and more recently as applications on mobile devices. The risk related to a malfunction of the standalone software used within healthcare is in itself not a criterion for its qualification or not as a medical device. It is therefore, necessary to clarify some criteria for the qualification of stand-alone software as medical devices Materials and methods: Ukrainian, European Union, United States of America legislation, Guidelines developed by European Commission and Food and Drug Administration's, recommendations represented by international voluntary group and scientific works. This article is based on dialectical, comparative, analytic, synthetic and comprehensive research methods. the legal regulation of software which is used for medical purpose in Ukraine limited to one definition. In European Union and United States of America were developed and applying special guidelines that help developers, manufactures and end users to difference software on types standing on medical purpose criteria. Software becomes more and more incorporated into medical devices. Developers and manufacturers may not have initially appreciated potential risks to patients and users such situation could have dangerous results for patients or users. It is necessary to develop and adopt the legislation that will intend to define the criteria for the qualification of medical device software and the application of the classification criteria to such software, provide some illustrative examples and step by step recommendations to qualify software as medical device.

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

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

  17. Guidelines for Description

    NARCIS (Netherlands)

    Links, P.; Horsman, Peter; Kühnel, Karsten; Priddy, M.; Reijnhoudt, Linda; Merenmies, Mark

    2013-01-01

    The Guidelines follow the conceptual metadata model (deliverable 17.2). They include guidelines for description of collection-holding institutions, document collections, organisations, personalities, events, camps and ghettos. As much as possible the guidelines comply with the descriptive standards

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

  19. Study of evaluation techniques of software testing and V and V in Nuclear Power Plants

    Energy Technology Data Exchange (ETDEWEB)

    Youn, Cheong; Baek, Y. W.; Kim, H. C.; Shin, C. Y.; Park, N. J. [Chungnam Nationl Univ., Taejon (Korea, Republic of)

    2000-03-15

    The study of activities to solve software safety and quality must be executed in base of establishing software development process for digitalized nuclear plant. Especially study of software testing and verification and validation must executed. For this purpose methodologies and tools which can improve software qualities are evaluated and software testing and V and V which can be applied to software life cycle are investigated. This study establish a guideline that can assure software safety and reliability requirements in digitalized nuclear plant systems and can be used as a guidebook of software development process to assure software quality many software development organization.

  20. Avoidable Software Procurements

    Science.gov (United States)

    2012-09-01

    software license, software usage, ELA, Software as a Service , SaaS , Software Asset...PaaS Platform as a Service SaaS Software as a Service SAM Software Asset Management SMS System Management Server SEWP Solutions for Enterprise Wide...delivery of full Cloud Services , we will see the transition of the Cloud Computing service model from Iaas to SaaS , or Software as a Service . Software

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

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

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

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

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

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

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

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

  9. ESTSC - Software Best Practices

    Science.gov (United States)

    DOE Scientific and Technical Software Best Practices December 2010 Table of Contents 1.0 Introduction 2.0 Responsibilities 2.1 OSTI/ESTSC 2.2 SIACs 2.3 Software Submitting Sites/Creators 2.4 Software Sensitivity Review 3.0 Software Announcement and Submission 3.1 STI Software Appropriate for Announcement 3.2

  10. Software Assurance Competency Model

    Science.gov (United States)

    2013-03-01

    COTS) software , and software as a service ( SaaS ). L2: Define and analyze risks in the acquisition of contracted software , COTS software , and SaaS ...2010a]: Application of technologies and processes to achieve a required level of confidence that software systems and services function in the...

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

  12. Communications Received from Certain Member States Regarding Guidelines for Transfers of Nuclear-related Dual-use Equipment, Materials, Software and Related Technology; Comunicaciones recibidas de diversos Estados Miembros relativas a las directrices para las transferencias de equipos, materiales y programas informaticos (software) de doble uso del ambito nuclear y tecnologia relacionada

    Energy Technology Data Exchange (ETDEWEB)

    NONE

    2006-04-11

    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 [Spanish] El Director General del Organismo Internacional de Energia Atomica ha recibido Notas verbales de fecha 1 de diciembre de 2005 de los Representantes Permanentes ante el Organismo de Alemania, Argentina, Australia, Austria, Belarus, Belgica, Brasil, Bulgaria, Canada, Croacia, Eslovenia, Espana, Estados Unidos de America, Estonia, Finlandia, Francia, Grecia, Hungria, Irlanda, Italia, Japon, Letonia, Lituania, Luxemburgo, Malta, Nueva Zelandia, Paises Bajos, Polonia, Portugal, Reino Unido de Gran Bretana e Irlanda del Norte, Republica Checa, Republica de Corea, Sudafrica, Suecia, Suiza, Turquia y Ucrania relativas a las transferencias de equipos, materiales y programas informaticos de doble uso del ambito nuclear y tecnologia relacionada.

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

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

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

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

  17. Visitor's Computer Guidelines | CTIO

    Science.gov (United States)

    Visitor's Computer Guidelines Network Connection Request Instruments Instruments by Telescope IR Instruments Guidelines Library Facilities Outreach NOAO-S EPO Program team Art of Darkness Image Gallery EPO/CADIAS ‹› You are here CTIO Home » Astronomers » Visitor's Computer Guidelines Visitor's Computer

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

  19. Factors influencing adherence to dietary guidelines: a qualitative ...

    African Journals Online (AJOL)

    2014-01-17

    Jan 17, 2014 ... Original Research: Factors influencing adherence to dietary guidelines. 76. 2014 Volume ..... eat, because they dik (tired) of giving you special food. Then they go .... patients in this study were satisfied with the advice received ...

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

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

  3. Guideline of guidelines: asymptomatic microscopic haematuria.

    Science.gov (United States)

    Linder, Brian J; Bass, Edward J; Mostafid, Hugh; Boorjian, Stephen A

    2018-02-01

    The aim of the present study was to review major organizational guidelines on the evaluation and management of asymptomatic microscopic haematuria (AMH). We reviewed the haematuria guidelines from: the American Urological Association; the consensus statement by the Canadian Urological Association, Canadian Urologic Oncology Group and Bladder Cancer Canada; the American College of Physicians; the Joint Consensus Statement of the Renal Association and British Association of Urological Surgeons; and the National Institute for Health and Care Excellence. All guidelines reviewed recommend evaluation for AMH in the absence of potential benign aetiologies, with the evaluation including cystoscopy and upper urinary tract imaging. Existing guidelines vary in their definition of AMH (role of urine dipstick vs urine microscopy), the age threshold for recommending evaluation, and the optimal imaging method (computed tomography vs ultrasonography). Of the reviewed guidelines, none recommended the use of urine cytology or urine markers during the initial AMH evaluation. Patients should have ongoing follow-up after a negative initial AMH evaluation. Significant variation exists among current guidelines for AMH with respect to who should be evaluated and in what manner. Given the patient and health system implications of balancing appropriately focused and effective diagnostic evaluation, AMH represents a valuable future research opportunity. © 2017 The Authors BJU International © 2017 BJU International Published by John Wiley & Sons Ltd.

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

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

  6. Commercial Literacy Software.

    Science.gov (United States)

    Balajthy, Ernest

    1997-01-01

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

  7. Ensuring Software IP Cleanliness

    OpenAIRE

    Mahshad Koohgoli; Richard Mayer

    2007-01-01

    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.

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

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

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

  11. Software - Naval Oceanography Portal

    Science.gov (United States)

    are here: Home › USNO › Earth Orientation › Software USNO Logo USNO Navigation Earth Orientation Products GPS-based Products VLBI-based Products EO Information Center Publications about Products Software Search databases Auxiliary Software Supporting Software Form Folder Earth Orientation Matrix Calculator

  12. Software Engineering Education Directory

    Science.gov (United States)

    1990-04-01

    and Engineering (CMSC 735) Codes: GPEV2 * Textiooks: IEEE Tutoria on Models and Metrics for Software Management and Engameeing by Basi, Victor R...Software Engineering (Comp 227) Codes: GPRY5 Textbooks: IEEE Tutoria on Software Design Techniques by Freeman, Peter and Wasserman, Anthony 1. Software

  13. Comparison of computed tomography dose reporting software

    International Nuclear Information System (INIS)

    Abdullah, A.; Sun, Z.; Pongnapang, N.; Ng, K. H.

    2008-01-01

    Computed tomography (CT) dose reporting software facilitates the estimation of doses to patients undergoing CT examinations. In this study, comparison of three software packages, i.e. CT-Expo (version 1.5, Medizinische Hochschule, Hannover (Germany)), ImPACT CT Patients Dosimetry Calculator (version 0.99x, Imaging Performance Assessment on Computed Tomography, www.impactscan.org) and WinDose (version 2.1a, Wellhofer Dosimetry, Schwarzenbruck (Germany)), has been made in terms of their calculation algorithm and the results of calculated doses. Estimations were performed for head, chest, abdominal and pelvic examinations based on the protocols recommended by European guidelines using single-slice CT (SSCT) (Siemens Somatom Plus 4, Erlangen (Germany)) and multi-slice CT (MSCT) (Siemens Sensation 16, Erlangen (Germany)) for software-based female and male phantoms. The results showed that there are some differences in final dose reporting provided by these software packages. There are deviations of effective doses produced by these software packages. Percentages of coefficient of variance range from 3.3 to 23.4 % in SSCT and from 10.6 to 43.8 % in MSCT. It is important that researchers state the name of the software that is used to estimate the various CT dose quantities. Users must also understand the equivalent terminologies between the information obtained from the CT console and the software packages in order to use the software correctly. (authors)

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

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

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

  17. Agile software assessment

    OpenAIRE

    Nierstrasz Oscar; Lungu Mircea

    2012-01-01

    Informed decision making is a critical activity in software development but it is poorly supported by common development environments which focus mainly on low level programming tasks. We posit the need for agile software assessment which aims to support decision making by enabling rapid and effective construction of software models and custom analyses. Agile software assessment entails gathering and exploiting the broader context of software information related to the system at hand as well ...

  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. Radiological risk comparison guidelines

    International Nuclear Information System (INIS)

    Hallinan, E.J.; Muhlestein, L.D.; Brown, L.F.; Yoder, R.E.

    1992-01-01

    An important aspect of DOE safety analyses is estimating potential accident risk. The estimates are used to: determine if additional controls are needed, identify Safety Class Items, and demonstrate adequate risk reduction. Thus, guidelines are needed to measure comparative risks. The Westinghouse M ampersand O Nuclear Facility Safety Committee and the Safety Envelope Working Group have developed radiological risk guidelines for comparing the risks from individual accident analyses. These guidelines were prepared under contract with the US Department of Energy. These guidelines are based on historical DOE guidelines and current requirements, and satisfy DOE and technical community proposals. for goals that demonstrate acceptable risk. The guidelines consist of a frequency versus consequence curve for credible accidents. Offsite and onsite guidelines are presented. The offsite risk acceptance guidelines are presented in Figure 1. The guidelines are nearly isorisk for anticipated events where impacts are chronic, and provide additional reduction for unlikely events where impacts may be acute and risk uncertainties may be significant. The guidelines are applied to individual release accident scenarios where a discrete frequency and consequence has been estimated. The guideline curves are not to be used for total risk assessments. Common cause events are taken into consideration only for an individual facility. Frequencies outside the guideline range are considered to be local site option (analyst judgement) as far as assessments of risk acceptance are concerned. If the curve is exceeded, then options include either a more detailed analysis or imposing additional preventive or mitigative features. Another presentation discusses implementation in detail. Additional work is needed to provide risk comparison guidelines for releases from multiple facilities and for toxic releases

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

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

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

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

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

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

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

  8. Strategies for Using Plagiarism Software in the Screening of Incoming Journal Manuscripts: Recommendations Based on a Recent Literature Survey.

    Science.gov (United States)

    Lykkesfeldt, Jens

    2016-08-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 opportunity to screen for plagiarism easily but also that it has to be employed with caution as automated or uncritical use is far too unreliable to allow a fair basis for judging the degree of plagiarism in a manuscript. This remains the job of senior editors. Whereas a few cases of self-plagiarism that would not likely have been accepted with today's guidelines were indeed identified, no cases of fraud or serious plagiarism were found. Potential guidelines are discussed. © 2016 Nordic Association for the Publication of BCPT (former Nordic Pharmacological Society).

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

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

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

  13. Public informations guidelines

    Energy Technology Data Exchange (ETDEWEB)

    None

    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.

  14. Guidelines for radiological interventions

    International Nuclear Information System (INIS)

    Kauffmann, G.W.

    1998-01-01

    The German Radiological Society, in cooperation with other German professional bodies, set up draft Guidelines for Radiological Interventions and submitted them to the professional community for discussion. The Guidelines are meant to assess the potential of radiological interventions as treatment alternatives to surgery or aggressive therapy such as chemotherapy. In fact, technical practicability on its own is insufficient to warrant intervention. The Guidelines are systematically compiled notions and recommendations whose aim it is to provide support to physicians and patients in choosing suitable medical care provisions (prevention, diagnosis, therapy, aftertreatment) in specific circumstances. A complete Czech translation of the Guidelines is given. (P.A.)

  15. Computer Software: Copyright and Licensing Considerations for Schools and Libraries. ERIC Digest.

    Science.gov (United States)

    Reed, Mary Hutchings

    This digest notes that the terms and conditions of computer software package license agreements control the use of software in schools and libraries, and examines the implications of computer software license agreements for classroom use and for library lending policies. Guidelines are provided for interpreting the Copyright Act, and insuring the…

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

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

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

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

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

  2. Process mining software repositories

    NARCIS (Netherlands)

    Poncin, W.; Serebrenik, A.; Brand, van den M.G.J.

    2011-01-01

    Software developers' activities are in general recorded in software repositories such as version control systems, bug trackers and mail archives. While abundant information is usually present in such repositories, successful information extraction is often challenged by the necessity to

  3. Bioassay guideline 2: guidelines for tritium bioassay

    International Nuclear Information System (INIS)

    1983-01-01

    This guideline is one of a series under preparation by the Federal-Provincial Working Group on Bioassay and In Vivo Monitoring Criteria. In this report tritium compounds have been grouped into four categories for the purpose of calculating Annual Limits on Intake and Investigation Levels: tritium gas, tritiated water, tritium-labelled compounds and nucleic acid precursors

  4. Optimization of Antivirus Software

    OpenAIRE

    Catalin BOJA; Adrian VISOIU

    2007-01-01

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

  5. Open Source Software Development

    Science.gov (United States)

    2011-01-01

    appropriate to refer to FOSS or FLOSS (L for Libre , where the alternative term “ libre software ” has popularity in some parts of the world) in order...Applying Social Network Analysis to Community-Drive Libre Software Projects, Intern. J. Info. Tech. and Web Engineering, 2006, 1(3), 27-28. 17...Open Source Software Development* Walt Scacchi Institute for Software Researcher University of California, Irvine Irvine, CA 92697-3455 USA Abstract

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

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

  9. Evidence-based guidelines

    DEFF Research Database (Denmark)

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

    2015-01-01

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

  10. Whitebark pine planting guidelines

    Science.gov (United States)

    Ward McCaughey; Glenda L. Scott; Kay L. Izlar

    2009-01-01

    This article incorporates new information into previous whitebark pine guidelines for planting prescriptions. Earlier 2006 guidelines were developed based on review of general literature, research studies, field observations, and standard US Forest Service survival surveys of high-elevation whitebark pine plantations. A recent study of biotic and abiotic factors...

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

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

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

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

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

  16. 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,…

  17. XES Software Communication Extension

    NARCIS (Netherlands)

    Leemans, M.; Liu, C.

    2017-01-01

    During the execution of software, execution data can be recorded. With the development of process mining techniques on the one hand, and the growing availability of software execution data on the other hand, a new form of software analytics comes into reach. That is, applying process mining

  18. Neutron Scattering Software

    Science.gov (United States)

    Home Page | Facilities | Reference | Software | Conferences | Announcements | Mailing Lists Neutron Scattering Banner Neutron Scattering Software A new portal for neutron scattering has just been established sets KUPLOT: data plotting and fitting software ILL/TAS: Matlab probrams for analyzing triple axis data

  19. XES Software Event Extension

    NARCIS (Netherlands)

    Leemans, M.; Liu, C.

    2017-01-01

    During the execution of software, execution data can be recorded. With the development of process mining techniques on the one hand, and the growing availability of software execution data on the other hand, a new form of software analytics comes into reach. That is, applying process mining

  20. ARC Software and Models

    Science.gov (United States)

    Archives RESEARCH ▼ Research Areas Ongoing Projects Completed Projects SOFTWARE CONTACT ▼ Primary Contacts Researchers External Link MLibrary Deep Blue Software Archive Most research conducted at the ARC produce software code and methodologies that are transferred to TARDEC and industry partners. These

  1. XES Software Telemetry Extension

    NARCIS (Netherlands)

    Leemans, M.; Liu, C.

    2017-01-01

    During the execution of software, execution data can be recorded. With the development of process mining techniques on the one hand, and the growing availability of software execution data on the other hand, a new form of software analytics comes into reach. That is, applying process mining

  2. Specifications in software prototyping

    OpenAIRE

    Luqi; Chang, Carl K.; Zhu, Hong

    1998-01-01

    We explore the use of software speci®cations for software prototyping. This paper describes a process model for software prototyping, and shows how specifications can be used to support such a process via a cellular mobile phone switch example.

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

  4. Primary care guidelines

    DEFF Research Database (Denmark)

    Ijäs, Jarja; Alanen, Seija; Kaila, Minna

    2009-01-01

    OBJECTIVE: To describe the adoption of the national Hypertension Guideline in primary care and to evaluate the consistency of the views of the health centre senior executives on the guideline's impact on clinical practices in the treatment of hypertension in their health centres. DESIGN: A cross...... Guideline. RESULTS: Data were available from 143 health centres in Finland (49%). The views of head physicians and senior nursing officers on the adoption of the Hypertension Guideline were not consistent. Head physicians more often than senior nursing officers (44% vs. 29%, p ...: Hypertension Guideline recommendations that require joint agreements between professionals are less often adopted than simple, precise recommendations. More emphasis on effective multidisciplinary collaboration is needed....

  5. Software Acquisition and Software Engineering Best Practices

    National Research Council Canada - National Science Library

    Eslinger, S

    1999-01-01

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

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

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

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

  9. Licensing safety critical software

    International Nuclear Information System (INIS)

    Archinoff, G.H.; Brown, R.A.

    1990-01-01

    Licensing difficulties with the shutdown system software at the Darlington Nuclear Generating Station contributed to delays in starting up the station. Even though the station has now been given approval by the Atomic Energy Control Board (AECB) to operate, the software issue has not disappeared - Ontario Hydro has been instructed by the AECB to redesign the software. This article attempts to explain why software based shutdown systems were chosen for Darlington, why there was so much difficulty licensing them, and what the implications are for other safety related software based applications

  10. HAZARD ANALYSIS SOFTWARE

    International Nuclear Information System (INIS)

    Sommer, S; Tinh Tran, T.

    2008-01-01

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

  11. Software Validation in ATLAS

    International Nuclear Information System (INIS)

    Hodgkinson, Mark; Seuster, Rolf; Simmons, Brinick; Sherwood, Peter; Rousseau, David

    2012-01-01

    The ATLAS collaboration operates an extensive set of protocols to validate the quality of the offline software in a timely manner. This is essential in order to process the large amounts of data being collected by the ATLAS detector in 2011 without complications on the offline software side. We will discuss a number of different strategies used to validate the ATLAS offline software; running the ATLAS framework software, Athena, in a variety of configurations daily on each nightly build via the ATLAS Nightly System (ATN) and Run Time Tester (RTT) systems; the monitoring of these tests and checking the compilation of the software via distributed teams of rotating shifters; monitoring of and follow up on bug reports by the shifter teams and periodic software cleaning weeks to improve the quality of the offline software further.

  12. Procedure guideline for radioiodine test (version 3)

    International Nuclear Information System (INIS)

    Dietlein, M.; Schicha, H.; Eschner, W.; Deutsche Gesellschaft fuer Medizinische Physik; Koeln Univ.; Lassmann, M.; Deutsche Gesellschaft fuer Medizinische Physik; Wuerzburg Univ.; Leisner, B.; Allgemeines Krankenhaus St. Georg, Hamburg; Reiners, C.; Wuerzburg Univ.

    2007-01-01

    The version 3 of the procedure guideline for radioiodine test is an update of the guideline previously published in 2003. The procedure guideline discusses the pros and cons of a single measurement or of repeated measurements of the iodine-131 uptake and their optimal timing. Different formulas are described when one, two or three values of the radioiodine kinetic are available. The probe with a sodium-iodine crystal, alternatively or additionally the gamma camera using the ROI-technique are instrumentations for the measurement of iodine-131 uptake. A possible source of error is an inappropriate measurement (sonography) of the target volume. The patients' preparation includes the withdrawal of antithyroid drugs 2-3 days before radioiodine administration. The patient has to avoid iodine-containing medication and the possibility of additives of iodine in vitamin- and electrolyte-supplementation has to be considered. (orig.)

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

  14. Model Driven Software Development for Agricultural Robotics

    DEFF Research Database (Denmark)

    Larsen, Morten

    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...... 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......, assisting with bridging the different engineering disciplines. Timing play an important role in agricultural robotic applications, synchronisation of robot movement and implement actions is important in order to achieve precision spraying, me- chanical weeding, individual feeding, etc. Discovering...

  15. Guidelines for computer security in general practice.

    Science.gov (United States)

    Schattner, Peter; Pleteshner, Catherine; Bhend, Heinz; Brouns, Johan

    2007-01-01

    As general practice becomes increasingly computerised, data security becomes increasingly important for both patient health and the efficient operation of the practice. To develop guidelines for computer security in general practice based on a literature review, an analysis of available information on current practice and a series of key stakeholder interviews. While the guideline was produced in the context of Australian general practice, we have developed a template that is also relevant for other countries. Current data on computer security measures was sought from Australian divisions of general practice. Semi-structured interviews were conducted with general practitioners (GPs), the medical software industry, senior managers within government responsible for health IT (information technology) initiatives, technical IT experts, divisions of general practice and a member of a health information consumer group. The respondents were asked to assess both the likelihood and the consequences of potential risks in computer security being breached. The study suggested that the most important computer security issues in general practice were: the need for a nominated IT security coordinator; having written IT policies, including a practice disaster recovery plan; controlling access to different levels of electronic data; doing and testing backups; protecting against viruses and other malicious codes; installing firewalls; undertaking routine maintenance of hardware and software; and securing electronic communication, for example via encryption. This information led to the production of computer security guidelines, including a one-page summary checklist, which were subsequently distributed to all GPs in Australia. This paper maps out a process for developing computer security guidelines for general practice. The specific content will vary in different countries according to their levels of adoption of IT, and cultural, technical and other health service factors. Making

  16. Flexible manufacturing system handbook. Volume 1: Executive summary

    Science.gov (United States)

    1983-02-01

    Flexible Manufacturing Systems (FMSs) represent a relatively new strategy to increase productivity. The technology is especially attractive for manufacturers who produce in the middle ranges of production volumes, neither mass production nor one of a kind. Today's unpredictable market environment demands low-cost solutions that provide quick product start-up, adaptability and responsiveness to changes in demand, and the capacity to easily resurrect out-of-production designs. In many instances, FMSs provide a direct hardware/software solution to this threefold management challenge. The adoption of FMS technology requires that one address many questions beforehand. This handbook provides a methodical approach to answering these questions. But it is not a cookbook; it cannot be. Each application of FMS technology is unique, therefore, the guidelines presented are fairly general.

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

    International Nuclear Information System (INIS)

    Greenham, Stuart; Dean, Jenna; Fu, Cheuk Kuen Kenneth; Goman, Joanne; Mulligan, Jeremy; Tune, Deanna; Sampson, David; Westhuyzen, Justin; McKay, Michael

    2014-01-01

    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

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

  19. Software Maintenance and Evolution: The Implication for Software ...

    African Journals Online (AJOL)

    Software Maintenance and Evolution: The Implication for Software Development. ... Software maintenance is the process of modifying existing operational software by correcting errors, ... EMAIL FREE FULL TEXT EMAIL FREE FULL TEXT

  20. EMI Messaging Guidelines

    CERN Document Server

    Cons, L.

    2011-01-01

    Guidelines for potential users of messaging within EMI. The goal is to provide enough practical information so that EMI product teams can start investigating whether using messaging in their products can be beneficial or not.

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

  2. Curriculum Guidelines for Periodontics.

    Science.gov (United States)

    Journal of Dental Education, 1985

    1985-01-01

    Guidelines describe the interrelationships of this and other dental fields, give an overview of the curriculum and its primary educational objectives, and outline the suggested prerequisites, core content, specific behavioral objectives, sequencing, and faculty requirements. (MSE)

  3. 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....... Group.2 Similar criteria for guideline quality have been suggested elsewhere.3 Our conclusion was that this much needed guideline is currently unclear about several aspects of the methodology used in developing the recommendations. This means potential users cannot be certain that the recommendations...

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

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

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

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

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

  9. Ecologo guidelines spark disagreement

    International Nuclear Information System (INIS)

    Anon.

    1999-01-01

    Defining what renewable means has been a challenge, but the authors of a new set of guidelines for the Ecologo certification of renewable low-impact electrcity expect after some delay to have the new rules on the street by March 2000.. There was contention in developing the guideline, according to Terra Choice Environmental Services, the company that created and applied criteria for Ecologo certification under the federal government's Environmetal Choice Program. Interim guidleines were developed and have been in place for renewable power since 1996, and have since been used to certify wood-waste biomass, landfill gas, small hydro and wind power plants, in addition to three green power marketing programs. The first draft of the revised guidelines was issued in March. It was one of the harder guidelines to have been worked on because Canadian power producers did not readily agree on what should qualify as renewable, particularly around the whole area of hydro. While small run-of-river hydro plants will continue to fit within the Ecologo guidelines, larger projects will not. Wind power producers are relatively happy with the latest version of TerraChoice's draft guidelines, released at the end of November. A significant revision of the original rules is a limit on the amount of older generation green power marketers who want to promote the green power Ecologo electricity can sell. At least 50% of their capacity must originate from plants installed after January 1, 1991

  10. Web Accessibility and Guidelines

    Science.gov (United States)

    Harper, Simon; Yesilada, Yeliz

    Access to, and movement around, complex online environments, of which the World Wide Web (Web) is the most popular example, has long been considered an important and major issue in the Web design and usability field. The commonly used slang phrase ‘surfing the Web’ implies rapid and free access, pointing to its importance among designers and users alike. It has also been long established that this potentially complex and difficult access is further complicated, and becomes neither rapid nor free, if the user is disabled. There are millions of people who have disabilities that affect their use of the Web. Web accessibility aims to help these people to perceive, understand, navigate, and interact with, as well as contribute to, the Web, and thereby the society in general. This accessibility is, in part, facilitated by the Web Content Accessibility Guidelines (WCAG) currently moving from version one to two. These guidelines are intended to encourage designers to make sure their sites conform to specifications, and in that conformance enable the assistive technologies of disabled users to better interact with the page content. In this way, it was hoped that accessibility could be supported. While this is in part true, guidelines do not solve all problems and the new WCAG version two guidelines are surrounded by controversy and intrigue. This chapter aims to establish the published literature related to Web accessibility and Web accessibility guidelines, and discuss limitations of the current guidelines and future directions.

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

  12. A software product certification model

    NARCIS (Netherlands)

    Heck, P.M.; Klabbers, M.D.; van Eekelen, Marko

    2010-01-01

    Certification of software artifacts offers organizations more certainty and confidence about software. Certification of software helps software sales, acquisition, and can be used to certify legislative compliance or to achieve acceptable deliverables in outsourcing. In this article, we present a

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

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

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

  16. Hospital Management Software Development

    OpenAIRE

    sobogunGod, olawale

    2012-01-01

    The purpose of this thesis was to implement a hospital management software which is suitable for small private hospitals in Nigeria, especially for the ones that use a file based system for storing information rather than having it stored in a more efficient and safer environment like databases or excel programming software. The software developed within this thesis project was specifically designed for the Rainbow specialist hospital which is based in Lagos, the commercial neurological cente...

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

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

  19. Software quality management

    International Nuclear Information System (INIS)

    Bishop, D.C.; Pymm, P.

    1991-01-01

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

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

  1. Assuring Software Reliability

    Science.gov (United States)

    2014-08-01

    technologies and processes to achieve a required level of confidence that software systems and services function in the intended manner. 1.3 Security Example...that took three high-voltage lines out of service and a software fail- ure (a race condition3) that disabled the computing service that notified the... service had failed. Instead of analyzing the details of the alarm server failure, the reviewers asked why the following software assurance claim had

  2. 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...... case study. Handling variants and tracing the impact of variants across the development lifecycle is a challenge. This chapter shows how we can maintain different versions of software in a reuse-based way....

  3. FASTBUS software status

    International Nuclear Information System (INIS)

    Gustavson, D.B.

    1980-10-01

    Computer software will be needed in addition to the mechanical, electrical, protocol and timing specifications of the FASTBUS, in order to facilitate the use of this flexible new multiprocessor and multisegment data acquisition and processing system. Software considerations have been important in the FASTBUS design, but standard subroutines and recommended algorithms will be needed as the FASTBUS comes into use. This paper summarizes current FASTBUS software projects, goals and status

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

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

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

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

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

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

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

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

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

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

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

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

    .... Additionally, recommend that DoN invest in software engineering, particularly as it complements commercial industry developments and promotes the application of systems engineering methodology...

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

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

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

  20. Software Radar Technology

    Directory of Open Access Journals (Sweden)

    Tang Jun

    2015-08-01

    Full Text Available In this paper, the definition and the key features of Software Radar, which is a new concept, are proposed and discussed. We consider the development of modern radar system technology to be divided into three stages: Digital Radar, Software radar and Intelligent Radar, and the second stage is just commencing now. A Software Radar system should be a combination of various modern digital modular components conformed to certain software and hardware standards. Moreover, a software radar system with an open system architecture supporting to decouple application software and low level hardware would be easy to adopt "user requirements-oriented" developing methodology instead of traditional "specific function-oriented" developing methodology. Compared with traditional Digital Radar, Software Radar system can be easily reconfigured and scaled up or down to adapt to the changes of requirements and technologies. A demonstration Software Radar signal processing system, RadarLab 2.0, which has been developed by Tsinghua University, is introduced in this paper and the suggestions for the future development of Software Radar in China are also given in the conclusion.

  1. Social software in global software development

    DEFF Research Database (Denmark)

    Giuffrida, Rosalba; Dittrich, Yvonne

    2010-01-01

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

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

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

  4. Customer Interaction in Software Development: A Comparison of Software Methodologies Deployed in Namibian Software Firms

    CSIR Research Space (South Africa)

    Iyawa, GE

    2016-01-01

    Full Text Available within the Namibian context. An implication for software project managers and software developers is that customer interaction should be properly managed to ensure that the software methodologies for improving software development processes...

  5. Study of evaluation techniques of software safety and reliability in nuclear power plants

    Energy Technology Data Exchange (ETDEWEB)

    Youn, Cheong; Baek, Y. W.; Kim, H. C.; Park, N. J.; Shin, C. Y. [Chungnam National Univ., Taejon (Korea, Republic of)

    1999-04-15

    Software system development process and software quality assurance activities are examined in this study. Especially software safety and reliability requirements in nuclear power plant are investigated. For this purpose methodologies and tools which can be applied to software analysis, design, implementation, testing, maintenance step are evaluated. Necessary tasks for each step are investigated. Duty, input, and detailed activity for each task are defined to establish development process of high quality software system. This means applying basic concepts of software engineering and principles of system development. This study establish a guideline that can assure software safety and reliability requirements in digitalized nuclear plant systems and can be used as a guidebook of software development process to assure software quality many software development organization.

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

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

  8. Software cost estimation

    NARCIS (Netherlands)

    Heemstra, F.J.

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

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

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

  11. Computer Software Reviews.

    Science.gov (United States)

    Hawaii State Dept. of Education, Honolulu. Office of Instructional Services.

    Intended to provide guidance in the selection of the best computer software available to support instruction and to make optimal use of schools' financial resources, this publication provides a listing of computer software programs that have been evaluated according to their currency, relevance, and value to Hawaii's educational programs. The…

  12. Software product family evaluation

    NARCIS (Netherlands)

    van der Linden, F; Bosch, J; Kamsties, E; Kansala, K; Krzanik, L; Obbink, H; VanDerLinden, F

    2004-01-01

    This paper proposes a 4-dimensional software product family engineering evaluation model. The 4 dimensions relate to the software engineering concerns of business, architecture, organisation and process. The evaluation model is meant to be used within organisations to determine the status of their

  13. Selecting the Right Software.

    Science.gov (United States)

    Shearn, Joseph

    1987-01-01

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

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

    DEFF Research Database (Denmark)

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

  15. Design patterns for modelling guidelines

    NARCIS (Netherlands)

    Serban, Radu; Ten Teije, Annette; Marcos, Mar; Polo-Conde, Cristina; Rosenbrand, Kitty C J G M; Wittenberg, Jolanda; van Croonenborg, Joyce

    2005-01-01

    It is by now widely accepted that medical guidelines can help to significantly improve the quality of medical care. Unfortunately, constructing the required medical guidelines is a very labour intensive and costly process. The cost of guideline construction would decrease if guidelines could be

  16. Development of cancer treatment guidelines

    African Journals Online (AJOL)

    Krystyna Kiel

    2011-05-26

    May 26, 2011 ... KEYWORDS. Cancer;. Therapy;. Guidelines. Contents. 1. Why develop guidelines? ... Widely available guideline resources in cancer care. ... The use of guidelines in medicine has a long history. Many .... She has a negative family history. ... The patient has 1 cm grade 3 infiltrating ductal carcinoma.

  17. Japanese Guideline for Atopic Dermatitis

    Directory of Open Access Journals (Sweden)

    Ichiro Katayama

    2011-01-01

    The basics of treatment discussed in this guideline are based on the “Guidelines for the Treatment of Atopic Dermatitis 2008” prepared by the Health and Labour Sciences Research and the “Guidelines for the Management of Atopic Dermatitis 2009 (ADGL2009” prepared by the Atopic Dermatitis Guidelines Advisory Committee, Japanese Society of Allergology in principle.

  18. BWR emergency procedure guidelines

    International Nuclear Information System (INIS)

    Post, J.S.; Karner, E.F.; Stratman, R.A.

    1984-01-01

    This chapter describes plans for dealing with reactor accidents developed by the Boiling Water Reactor (BWR) Owners' Group in response to post-Three Mile Island US NRC requirements. The devised Emergency Procedure Guidelines (EPGs), applicable to all BWRs, are symptom-based rather than event-based. According to the EPGs, the operator does not need to identify what event is occurring in the plant in order to decide what action to take, but need only observe the symptoms (values and trends of key control parameters) which exist and take appropriate action to control these symptoms. The original objective was to provide reactor operator guidance in responding to a small break loss-of-coolant accident (LOCA), but subsequent revisions have included other types of reactor accidents. Topics considered include the reactor pressure vessel (RPV) control guideline, the primary containment control guideline, the secondary containment control guideline, the radioactivity release control guideline, multiple failures vs. the design basis, safe limits vs. technical specifications, the technical status, licensing, and implementation. The EPGs are based upon maintaining both adequate core cooling and primary containment integrity

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

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