Sample records for software guidelines issue

  1. Library and Classroom Use of Copyrighted Videotapes and Computer Software.

    ERIC Educational Resources Information Center

    Reed, Mary Hutchings; Stanek, Debra

    1986-01-01

    This pullout guide addresses issues regarding library use of copyrighted videotapes and computer software. Guidelines for videotapes cover in-classroom use, in-library use in public library, loan, and duplication. Guidelines for computer software cover purchase conditions, avoiding license restrictions, loaning, archival copies, and in-library and…

  2. Guideline for Software Documentation Management.

    ERIC Educational Resources Information Center

    National Bureau of Standards (DOC), Washington, DC.

    Designed as a basic reference for federal personnel concerned with the development, maintenance, enhancement, control, and management of computer-based systems, this manual provides a general overview of the software development process and software documentation issues so that managers can assess their own documentation requirements. Reference is…

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

    PubMed

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

    2010-09-01

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

  4. User-Centered Design Guidelines for Collaborative Software for Intelligence Analysis

    DOE Office of Scientific and Technical Information (OSTI.GOV)

    Scholtz, Jean; Endert, Alexander N.

    In this position paper we discuss the necessity of using User-Centered Design (UCD) methods in order to design collaborative software for the intelligence community. We present some standing issues in collaborative software based on existing work within the intelligence community. Based on this information we present opportunities to address some of these challenges.

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

    ERIC Educational Resources Information Center

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

  6. The integration of the risk management process with the lifecycle of medical device software.

    PubMed

    Pecoraro, F; Luzi, D

    2014-01-01

    The application of software in the Medical Device (MD) domain has become central to the improvement of diagnoses and treatments. The new European regulations that specifically address software as an important component of MD, require complex procedures to make software compliant with safety requirements, introducing thereby new challenges in the qualification and classification of MD software as well as in the performance of risk management activities. Under this perspective, the aim of this paper is to propose an integrated framework that combines the activities to be carried out by the manufacturer to develop safe software within the development lifecycle based on the regulatory requirements reported in US and European regulations as well as in the relevant standards and guidelines. A comparative analysis was carried out to identify the main issues related to the application of the current new regulations. In addition, standards and guidelines recently released to harmonise procedures for the validation of MD software have been used to define the risk management activities to be carried out by the manufacturer during the software development process. This paper highlights the main issues related to the qualification and classification of MD software, providing an analysis of the different regulations applied in Europe and the US. A model that integrates the risk management process within the software development lifecycle has been proposed too. It is based on regulatory requirements and considers software risk analysis as a central input to be managed by the manufacturer already at the initial stages of the software design, in order to prevent MD failures. Relevant changes in the process of MD development have been introduced with the recognition of software being an important component of MDs as stated in regulations and standards. This implies the performance of highly iterative processes that have to integrate the risk management in the framework of software development. It also makes it necessary to involve both medical and software engineering competences to safeguard patient and user safety.

  7. General guidelines for biomedical software development

    PubMed Central

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

    2017-01-01

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

  8. C style guide

    NASA Technical Reports Server (NTRS)

    Doland, Jerry; Valett, Jon

    1994-01-01

    This document discusses recommended practices and style for programmers using the C language in the Flight Dynamics Division environment. Guidelines are based on generally recommended software engineering techniques, industry resources, and local convention. The Guide offers preferred solutions to common C programming issues and illustrates through examples of C Code.

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

    DTIC Science & Technology

    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

  10. User systems guidelines for software projects

    DOE Office of Scientific and Technical Information (OSTI.GOV)

    Abrahamson, L.

    1986-04-01

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

  11. Guidance for the Design and Adoption of Analytic Tools.

    DOE Office of Scientific and Technical Information (OSTI.GOV)

    Bandlow, Alisa

    2015-12-01

    The goal is to make software developers aware of common issues that can impede the adoption of analytic tools. This paper provides a summary of guidelines, lessons learned and existing research to explain what is currently known about what analysts want and how to better understand what tools they do and don't need.

  12. Overview of the SAE G-11 RMSL (Reliability, Maintainability, Supportability, and Logistics) Division Activities and Technical Projects

    NASA Technical Reports Server (NTRS)

    Singhal, Surendra N.

    2003-01-01

    The SAE G-11 RMSL (Reliability, Maintainability, Supportability, and Logistics) Division activities include identification and fulfillment of joint industry, government, and academia needs for development and implementation of RMSL technologies. Four Projects in the Probabilistic Methods area and two in the area of RMSL have been identified. These are: (1) Evaluation of Probabilistic Technology - progress has been made toward the selection of probabilistic application cases. Future effort will focus on assessment of multiple probabilistic softwares in solving selected engineering problems using probabilistic methods. Relevance to Industry & Government - Case studies of typical problems encountering uncertainties, results of solutions to these problems run by different codes, and recommendations on which code is applicable for what problems; (2) Probabilistic Input Preparation - progress has been made in identifying problem cases such as those with no data, little data and sufficient data. Future effort will focus on developing guidelines for preparing input for probabilistic analysis, especially with no or little data. Relevance to Industry & Government - Too often, we get bogged down thinking we need a lot of data before we can quantify uncertainties. Not True. There are ways to do credible probabilistic analysis with little data; (3) Probabilistic Reliability - probabilistic reliability literature search has been completed along with what differentiates it from statistical reliability. Work on computation of reliability based on quantification of uncertainties in primitive variables is in progress. Relevance to Industry & Government - Correct reliability computations both at the component and system level are needed so one can design an item based on its expected usage and life span; (4) Real World Applications of Probabilistic Methods (PM) - A draft of volume 1 comprising aerospace applications has been released. Volume 2, a compilation of real world applications of probabilistic methods with essential information demonstrating application type and timehost savings by the use of probabilistic methods for generic applications is in progress. Relevance to Industry & Government - Too often, we say, 'The Proof is in the Pudding'. With help from many contributors, we hope to produce such a document. Problem is - not too many people are coming forward due to proprietary nature. So, we are asking to document only minimum information including problem description, what method used, did it result in any savings, and how much?; (5) Software Reliability - software reliability concept, program, implementation, guidelines, and standards are being documented. Relevance to Industry & Government - software reliability is a complex issue that must be understood & addressed in all facets of business in industry, government, and other institutions. We address issues, concepts, ways to implement solutions, and guidelines for maximizing software reliability; (6) Maintainability Standards - maintainability/serviceability industry standard/guidelines and industry best practices and methodologies used in performing maintainability/ serviceability tasks are being documented. Relevance to Industry & Government - Any industry or government process, project, and/or tool must be maintained and serviced to realize the life and performance it was designed for. We address issues and develop guidelines for optimum performance & life.

  13. Software Safety Progress in NASA

    NASA Technical Reports Server (NTRS)

    Radley, Charles F.

    1995-01-01

    NASA has developed guidelines for development and analysis of safety-critical software. These guidelines have been documented in a Guidebook for Safety Critical Software Development and Analysis. The guidelines represent a practical 'how to' approach, to assist software developers and safety analysts in cost effective methods for software safety. They provide guidance in the implementation of the recent NASA Software Safety Standard NSS-1740.13 which was released as 'Interim' version in June 1994, scheduled for formal adoption late 1995. This paper is a survey of the methods in general use, resulting in the NASA guidelines for safety critical software development and analysis.

  14. Implementations of the CC'01 Human-Computer Interaction Guidelines Using Bloom's Taxonomy

    ERIC Educational Resources Information Center

    Manaris, Bill; Wainer, Michael; Kirkpatrick, Arthur E.; Stalvey, RoxAnn H.; Shannon, Christine; Leventhal, Laura; Barnes, Julie; Wright, John; Schafer, J. Ben; Sanders, Dean

    2007-01-01

    In today's technology-laden society human-computer interaction (HCI) is an important knowledge area for computer scientists and software engineers. This paper surveys existing approaches to incorporate HCI into computer science (CS) and such related issues as the perceived gap between the interests of the HCI community and the needs of CS…

  15. Breaking the Communication Barrier: Guidelines to Aid Communication within Pair Programming

    ERIC Educational Resources Information Center

    Zarb, Mark; Hughes, Janet

    2015-01-01

    Pair programming is a software development technique with many cited benefits in learning and teaching. However, it is reported that novice programmers find several barriers to pairing up, typically due to the added communication that is required of this approach. This paper will present a literature review discussing the issue of communication,…

  16. The Computational Infrastructure for Geodynamics: An Example of Software Curation and Citation in the Geodynamics Community

    NASA Astrophysics Data System (ADS)

    Hwang, L.; Kellogg, L. H.

    2017-12-01

    Curation of software promotes discoverability and accessibility and works hand in hand with scholarly citation to ascribe value to, and provide recognition for software development. To meet this challenge, the Computational Infrastructure for Geodynamics (CIG) maintains a community repository built on custom and open tools to promote discovery, access, identification, credit, and provenance of research software for the geodynamics community. CIG (geodynamics.org) originated from recognition of the tremendous effort required to develop sound software and the need to reduce duplication of effort and to sustain community codes. CIG curates software across 6 domains and has developed and follows software best practices that include establishing test cases, documentation, and a citable publication for each software package. CIG software landing web pages provide access to current and past releases; many are also accessible through the CIG community repository on github. CIG has now developed abc - attribution builder for citation to enable software users to give credit to software developers. abc uses zenodo as an archive and as the mechanism to obtain a unique identifier (DOI) for scientific software. To assemble the metadata, we searched the software's documentation and research publications and then requested the primary developers to verify. In this process, we have learned that each development community approaches software attribution differently. The metadata gathered is based on guidelines established by groups such as FORCE11 and OntoSoft. The rollout of abc is gradual as developers are forward-looking, rarely willing to go back and archive prior releases in zenodo. Going forward all actively developed packages will utilize the zenodo and github integration to automate the archival process when a new release is issued. How to handle legacy software, multi-authored libraries, and assigning roles to software remain open issues.

  17. Effective Monitoring and Control of Outsourced Software Development Projects

    NASA Astrophysics Data System (ADS)

    Ponisio, Laura; Vruggink, Peter

    In our study of four outsourcing projects we discover mechanisms to support managerial decision making during software development processes. We report on Customer Office, a framework used in practice that facilitates reasoning about projects by highlighting information paths and making co-ordination issues explicit. The results suggest a key role of modularisation and standardisation to assist in value creation, by facilitating information flow and keeping the overview of the project. The practical implications of our findings are guidelines for managing outsourcing projects such as to have a modularised view of the project based on knowledge domains and to standardise co-ordination operations.

  18. The Future of Statistical Software. Proceedings of a Forum--Panel on Guidelines for Statistical Software (Washington, D.C., February 22, 1991).

    ERIC Educational Resources Information Center

    National Academy of Sciences - National Research Council, Washington, DC.

    The Panel on Guidelines for Statistical Software was organized in 1990 to document, assess, and prioritize problem areas regarding quality and reliability of statistical software; present prototype guidelines in high priority areas; and make recommendations for further research and discussion. This document provides the following papers presented…

  19. Software OT&E Guidelines. Volume 3. Software Maintainability Evaluator’s Handbook

    DTIC Science & Technology

    1980-04-01

    SOFTWARE OT&E " 1 GUIDELINES . VOLUME III SOFTWARE MAINTAINABILITY EVALUATOR’S HANDBOOK APRIL 1980 AIR FORCE TEST AND EVALUATION CENTER KIRTLAND AIR...FORCE BASE NEW MEXICO 87117 C-, -j AfTECP 800-3 AF’r...........3 ...... UNCLASSIFIED SECURITY CLASSIFICATION OF THIS PAGE (When D.. Entered) RE:PORT...c -. 5 TY!aJ0. PERIOD COVERED SOFTWARE OT& . GUIDELINES, Volume III .of five). -1 softare-R.aintainability Evaluator’s P-IEFnook’ 4ina. i 1980

  20. OHD/HL - National Weather Hydrology Laboratory

    Science.gov Websites

    resources and services. Design and Programming Standards and Guidelines General Programming C C++ FORTRAN Java v 2.0 updated 3/28/2008 Java v 1.9 Korn and Bash Shell Software Design Phase Guidelines OHD Design Specification Template OHD Design Specification Example Software Peer Review Guidelines and Checklists Software

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

    NASA Astrophysics Data System (ADS)

    1992-06-01

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

  2. Concurrent development of fault management hardware and software in the SSM/PMAD. [Space Station Module/Power Management And Distribution

    NASA Technical Reports Server (NTRS)

    Freeman, Kenneth A.; Walsh, Rick; Weeks, David J.

    1988-01-01

    Space Station issues in fault management are discussed. The system background is described with attention given to design guidelines and power hardware. A contractually developed fault management system, FRAMES, is integrated with the energy management functions, the control switchgear, and the scheduling and operations management functions. The constraints that shaped the FRAMES system and its implementation are considered.

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

    NASA Technical Reports Server (NTRS)

    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.

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

    NASA Astrophysics Data System (ADS)

    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. A survey of Canadian medical physicists: software quality assurance of in-house software.

    PubMed

    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.

  6. Guidelines for computer security in general practice.

    PubMed

    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 these guidelines relevant to local contexts should help maximise their uptake.

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

    DOE Office of Scientific and Technical Information (OSTI.GOV)

    Salomons, G; Kelly, D

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

  8. Ada (Trademark) Reusability Guidelines.

    DTIC Science & Technology

    1985-04-01

    generators. Neighbors discusses another approach to reusable software using models. He describes a particular modeling technique using the Draco System ...experience with the Draco system . Is Fx~~~~flP7 7. 4 .~-’ b.r SECTION 4 DESIGN GUIDEUiNES As noted earlier, reusability is first and foremost a design issue...to be reused in another system that had a different type of physical data storage device, only this layer needs to be changed to deal with the new

  9. Comparative seismic evaluation between numerical analysis and Italian guidelines on cultural heritage applied to the case study of a masonry building compound

    NASA Astrophysics Data System (ADS)

    Formisano, Antonio; Chiumiento, Giovanni; Fabbrocino, Francesco; Landolfo, Raffaele

    2017-07-01

    The general objective of the work is to draw attention to the issue of seismic vulnerability analysis of masonry building compounds, which characterise most of the Italian historic towns. The study is based on the analysis of an aggregated construction falling in the town of Arsita (Teramo, Italy) damaged after the 2009 L'Aquila earthquake. A comparison between the seismic verifications carried out by using the 3Muri commercial software and those deriving from the application of the Italian Guidelines on Cultural Heritage has been performed. The comparison has shown that Guidelines provide results on the safe side in predicting the seismic behaviour of the building compound under study. Further analyses should be performed aiming at suggesting some modifications of the used simplified calculation method to better interpret the behaviour of building compounds under earthquake.

  10. Software Engineering Education: Some Important Dimensions

    ERIC Educational Resources Information Center

    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…

  11. User-Centered Design Guidelines for Collaborative Software for Intelligence Analysis

    DOE Office of Scientific and Technical Information (OSTI.GOV)

    Scholtz, Jean; Endert, Alexander

    In this position paper we discuss the necessity of using User-Centered Design (UCD) methods in order to design collaborative software for the intelligence community. We discuss a number of studies of collaboration in the intelligence community and use this information to provide some guidelines for collaboration software.

  12. Software Engineering Laboratory (SEL) cleanroom process model

    NASA Technical Reports Server (NTRS)

    Green, Scott; Basili, Victor; Godfrey, Sally; Mcgarry, Frank; Pajerski, Rose; Waligora, Sharon

    1991-01-01

    The Software Engineering Laboratory (SEL) cleanroom process model is described. The term 'cleanroom' originates in the integrated circuit (IC) production process, where IC's are assembled in dust free 'clean rooms' to prevent the destructive effects of dust. When applying the clean room methodology to the development of software systems, the primary focus is on software defect prevention rather than defect removal. The model is based on data and analysis from previous cleanroom efforts within the SEL and is tailored to serve as a guideline in applying the methodology to future production software efforts. The phases that are part of the process model life cycle from the delivery of requirements to the start of acceptance testing are described. For each defined phase, a set of specific activities is discussed, and the appropriate data flow is described. Pertinent managerial issues, key similarities and differences between the SEL's cleanroom process model and the standard development approach used on SEL projects, and significant lessons learned from prior cleanroom projects are presented. It is intended that the process model described here will be further tailored as additional SEL cleanroom projects are analyzed.

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

    PubMed Central

    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

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

    DTIC Science & Technology

    1981-02-01

    on reverse side If neceeary and identify by block number) The Software OT&E Guidelines is a set of handbooks prepared by the Computer / Support Systems...is one of a set of handbooks prepared by the Computer /Support Systems Division of the Test and Evaluation Directorate, Air Force Test and Evaluation...15 E. Software Maintainability .. .. ........ ... 16 F. Standard Questionnaires. .. .. ....... .... 16 1. Operator- Computer Interface Evaluation

  15. Modeling Guidelines for Code Generation in the Railway Signaling Context

    NASA Technical Reports Server (NTRS)

    Ferrari, Alessio; Bacherini, Stefano; Fantechi, Alessandro; Zingoni, Niccolo

    2009-01-01

    Modeling guidelines constitute one of the fundamental cornerstones for Model Based Development. Their relevance is essential when dealing with code generation in the safety-critical domain. This article presents the experience of a railway signaling systems manufacturer on this issue. Introduction of Model-Based Development (MBD) and code generation in the industrial safety-critical sector created a crucial paradigm shift in the development process of dependable systems. While traditional software development focuses on the code, with MBD practices the focus shifts to model abstractions. The change has fundamental implications for safety-critical systems, which still need to guarantee a high degree of confidence also at code level. Usage of the Simulink/Stateflow platform for modeling, which is a de facto standard in control software development, does not ensure by itself production of high-quality dependable code. This issue has been addressed by companies through the definition of modeling rules imposing restrictions on the usage of design tools components, in order to enable production of qualified code. The MAAB Control Algorithm Modeling Guidelines (MathWorks Automotive Advisory Board)[3] is a well established set of publicly available rules for modeling with Simulink/Stateflow. This set of recommendations has been developed by a group of OEMs and suppliers of the automotive sector with the objective of enforcing and easing the usage of the MathWorks tools within the automotive industry. The guidelines have been published in 2001 and afterwords revisited in 2007 in order to integrate some additional rules developed by the Japanese division of MAAB [5]. The scope of the current edition of the guidelines ranges from model maintainability and readability to code generation issues. The rules are conceived as a reference baseline and therefore they need to be tailored to comply with the characteristics of each industrial context. Customization of these recommendations has been performed for the automotive control systems domain in order to enforce code generation [7]. The MAAB guidelines have been found profitable also in the aerospace/avionics sector [1] and they have been adopted by the MathWorks Aerospace Leadership Council (MALC). General Electric Transportation Systems (GETS) is a well known railway signaling systems manufacturer leading in Automatic Train Protection (ATP) systems technology. Inside an effort of adopting formal methods within its own development process, GETS decided to introduce system modeling by means of the MathWorks tools [2], and in 2008 chose to move to code generation. This article reports the experience performed by GETS in developing its own modeling standard through customizing the MAAB rules for the railway signaling domain and shows the result of this experience with a successful product development story.

  16. Nurturing reliable and robust open-source scientific software

    NASA Astrophysics Data System (ADS)

    Uieda, L.; Wessel, P.

    2017-12-01

    Scientific results are increasingly the product of software. The reproducibility and validity of published results cannot be ensured without access to the source code of the software used to produce them. Therefore, the code itself is a fundamental part of the methodology and must be published along with the results. With such a reliance on software, it is troubling that most scientists do not receive formal training in software development. Tools such as version control, continuous integration, and automated testing are routinely used in industry to ensure the correctness and robustness of software. However, many scientist do not even know of their existence (although efforts like Software Carpentry are having an impact on this issue; software-carpentry.org). Publishing the source code is only the first step in creating an open-source project. For a project to grow it must provide documentation, participation guidelines, and a welcoming environment for new contributors. Expanding the project community is often more challenging than the technical aspects of software development. Maintainers must invest time to enforce the rules of the project and to onboard new members, which can be difficult to justify in the context of the "publish or perish" mentality. This problem will continue as long as software contributions are not recognized as valid scholarship by hiring and tenure committees. Furthermore, there are still unsolved problems in providing attribution for software contributions. Many journals and metrics of academic productivity do not recognize citations to sources other than traditional publications. Thus, some authors choose to publish an article about the software and use it as a citation marker. One issue with this approach is that updating the reference to include new contributors involves writing and publishing a new article. A better approach would be to cite a permanent archive of individual versions of the source code in services such as Zenodo (zenodo.org). However, citations to these sources are not always recognized when computing citation metrics. In summary, the widespread development of reliable and robust open-source software relies on the creation of formal training programs in software development best practices and the recognition of software as a valid form of scholarship.

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

    NASA Astrophysics Data System (ADS)

    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. Expert system verification and validation guidelines/workshop task. Deliverable no. 1: ES V/V guidelines

    NASA Technical Reports Server (NTRS)

    French, Scott W.

    1991-01-01

    The goals are to show that verifying and validating a software system is a required part of software development and has a direct impact on the software's design and structure. Workshop tasks are given in the areas of statistics, integration/system test, unit and architectural testing, and a traffic controller problem.

  19. Recommended approach to software development, revision 3

    NASA Technical Reports Server (NTRS)

    Landis, Linda; Waligora, Sharon; Mcgarry, Frank; Pajerski, Rose; Stark, Mike; Johnson, Kevin Orlin; Cover, Donna

    1992-01-01

    Guidelines for an organized, disciplined approach to software development that is based on studies conducted by the Software Engineering Laboratory (SEL) since 1976 are presented. It describes methods and practices for each phase of a software development life cycle that starts with requirements definition and ends with acceptance testing. For each defined life cycle phase, guidelines for the development process and its management, and for the products produced and their reviews are presented.

  20. Review of guidelines and literature for handling missing data in longitudinal clinical trials with a case study.

    PubMed

    Liu, M; Wei, L; Zhang, J

    2006-01-01

    Missing data in clinical trials are inevitable. We highlight the ICH guidelines and CPMP points to consider on missing data. Specifically, we outline how we should consider missing data issues when designing, planning and conducting studies to minimize missing data impact. We also go beyond the coverage of the above two documents, provide a more detailed review of the basic concepts of missing data and frequently used terminologies, and examples of the typical missing data mechanism, and discuss technical details and literature for several frequently used statistical methods and associated software. Finally, we provide a case study where the principles outlined in this paper are applied to one clinical program at protocol design, data analysis plan and other stages of a clinical trial.

  1. Guidelines for applying the Composite Specification Model (CSM)

    NASA Technical Reports Server (NTRS)

    Agresti, William

    1987-01-01

    The Composite Specification Model (CSM) is an approach to representing software requirements. Guidelines are provided for applying CSM and developing each of the three descriptive views of the software: the contextual view, using entities and relationships; the dynamic view, using states and transitions; and the function view, using data flows and processes. Using CSM results in a software specification document, which is outlined.

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

    NASA Technical Reports Server (NTRS)

    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.

  3. Proceedings of the Joint Logistics Commanders Joint Policy Coordinating Group on Computer Resource Management; Computer Software Management Software Workshop, 2-5 April 1979.

    DTIC Science & Technology

    1979-08-21

    Appendix s - Outline and Draft Material for Proposed Triservice Interim Guideline on Application of Software Acceptance Criteria....... 269 Appendix 9...AND DRAFT MATERIAL FOR PROPOSED TRISERVICE INTERIM GUIDELINE ON APPLICATION OF SOFTWARE ACCEPTANCE CRITERIA I I INTRODUCTION The purpose of this guide...contract item (CPCI) (code) 5. CPCI test plan 6. CPCI test procedures 7. CPCI test report 8. Handbooks and manuals. Al though additional material does

  4. Quality Assurance Results for a Commercial Radiosurgery System: A Communication.

    PubMed

    Ruschin, Mark; Lightstone, Alexander; Beachey, David; Wronski, Matt; Babic, Steven; Yeboah, Collins; Lee, Young; Soliman, Hany; Sahgal, Arjun

    2015-10-01

    The purpose of this communication is to inform the radiosurgery community of quality assurance (QA) results requiring attention in a commercial FDA-approved linac-based cone stereo-tactic radiosurgery (SRS) system. Standard published QA guidelines as per the American Association of Physics in Medicine (AAPM) were followed during the SRS system's commissioning process including end-to-end testing, cone concentricity testing, image transfer verification, and documentation. Several software and hardware deficiencies that were deemed risky were uncovered during the process and QA processes were put in place to mitigate these risks during clinical practice. In particular, the present work focuses on daily cone concentricity testing and commissioning-related findings associated with the software. Cone concentricity/alignment is measured daily using both optical light field inspection, as well as quantitative radiation field tests with the electronic portal imager. In 10 out of 36 clini-cal treatments, adjustments to the cone position had to be made to align the cone with the collimator axis to less than 0.5 mm and on two occasions the pre-adjustment measured offset was 1.0 mm. Software-related errors discovered during commissioning included incorrect transfer of the isocentre in DICOM coordinates, improper handling of non-axial image sets, and complex handling of beam data, especially for multi-target treatments. QA processes were established to mitigate the occurrence of the software errors. With proper QA processes, the reported SRS system complies with tolerances set out in established guidelines. Discussions with the vendor are ongoing to address some of the hardware issues related to cone alignment. © The Author(s) 2014.

  5. Guidelines for testing and release procedures

    NASA Technical Reports Server (NTRS)

    Molari, R.; Conway, M.

    1984-01-01

    Guidelines and procedures are recommended for the testing and release of the types of computer software efforts commonly performed at NASA/Ames Research Center. All recommendations are based on the premise that testing and release activities must be specifically selected for the environment, size, and purpose of each individual software project. Guidelines are presented for building a Test Plan and using formal Test Plan and Test Care Inspections on it. Frequent references are made to NASA/Ames Guidelines for Software Inspections. Guidelines are presented for selecting an Overall Test Approach and for each of the four main phases of testing: (1) Unit Testing of Components, (2) Integration Testing of Components, (3) System Integration Testing, and (4) Acceptance Testing. Tools used for testing are listed, including those available from operating systems used at Ames, specialized tools which can be developed, unit test drivers, stub module generators, and the use of format test reporting schemes.

  6. Knowledge-based system V and V in the Space Station Freedom program

    NASA Technical Reports Server (NTRS)

    Kelley, Keith; Hamilton, David; Culbert, Chris

    1992-01-01

    Knowledge Based Systems (KBS's) are expected to be heavily used in the Space Station Freedom Program (SSFP). Although SSFP Verification and Validation (V&V) requirements are based on the latest state-of-the-practice in software engineering technology, they may be insufficient for Knowledge Based Systems (KBS's); it is widely stated that there are differences in both approach and execution between KBS V&V and conventional software V&V. In order to better understand this issue, we have surveyed and/or interviewed developers from sixty expert system projects in order to understand the differences and difficulties in KBS V&V. We have used this survey results to analyze the SSFP V&V requirements for conventional software in order to determine which specific requirements are inappropriate for KBS V&V and why they are inappropriate. Further work will result in a set of recommendations that can be used either as guidelines for applying conventional software V&V requirements to KBS's or as modifications to extend the existing SSFP conventional software V&V requirements to include KBS requirements. The results of this work are significant to many projects, in addition to SSFP, which will involve KBS's.

  7. Software verification plan for GCS. [guidance and control software

    NASA Technical Reports Server (NTRS)

    Dent, Leslie A.; Shagnea, Anita M.; Hayhurst, Kelly J.

    1990-01-01

    This verification plan is written as part of an experiment designed to study the fundamental characteristics of the software failure process. The experiment will be conducted using several implementations of software that were produced according to industry-standard guidelines, namely the Radio Technical Commission for Aeronautics RTCA/DO-178A guidelines, Software Consideration in Airborne Systems and Equipment Certification, for the development of flight software. This plan fulfills the DO-178A requirements for providing instructions on the testing of each implementation of software. The plan details the verification activities to be performed at each phase in the development process, contains a step by step description of the testing procedures, and discusses all of the tools used throughout the verification process.

  8. Recommended approach to sofware development

    NASA Technical Reports Server (NTRS)

    Mcgarry, F. E.; Page, J.; Eslinger, S.; Church, V.; Merwarth, P.

    1983-01-01

    A set of guideline for an organized, disciplined approach to software development, based on data collected and studied for 46 flight dynamics software development projects. Methods and practices for each phase of a software development life cycle that starts with requirements analysis and ends with acceptance testing are described; maintenance and operation is not addressed. For each defined life cycle phase, guidelines for the development process and its management, and the products produced and their reviews are presented.

  9. Guidelines for Writing (or Rewriting) Manuals for Instructional Software.

    ERIC Educational Resources Information Center

    Litchfield, Brenda C.

    1990-01-01

    Discusses the need for adequate student user manuals for computer software and presents guidelines to help teachers develop these manuals. The sections that a student manual should contain are outlined, including objectives, pretests and posttests for self-evaluation, and worksheets; and examples are given for further clarification. (LRW)

  10. Formal methods and their role in digital systems validation for airborne systems

    NASA Technical Reports Server (NTRS)

    Rushby, John

    1995-01-01

    This report is based on one prepared as a chapter for the FAA Digital Systems Validation Handbook (a guide to assist FAA certification specialists with advanced technology issues). Its purpose is to explain the use of formal methods in the specification and verification of software and hardware requirements, designs, and implementations; to identify the benefits, weaknesses, and difficulties in applying these methods to digital systems used in critical applications; and to suggest factors for consideration when formal methods are offered in support of certification. The presentation concentrates on the rationale for formal methods and on their contribution to assurance for critical applications within a context such as that provided by DO-178B (the guidelines for software used on board civil aircraft); it is intended as an introduction for those to whom these topics are new.

  11. Developing clinical practice guidelines: reviewing, reporting, and publishing guidelines; updating guidelines; and the emerging issues of enhancing guideline implementability and accounting for comorbid conditions in guideline development

    PubMed Central

    2012-01-01

    Clinical practice guidelines are one of the foundations of efforts to improve health care. In 1999, we authored a paper about methods to develop guidelines. Since it was published, the methods of guideline development have progressed both in terms of methods and necessary procedures and the context for guideline development has changed with the emergence of guideline clearing houses and large scale guideline production organisations (such as the UK National Institute for Health and Clinical Excellence). It therefore seems timely to, in a series of three articles, update and extend our earlier paper. In this third paper we discuss the issues of: reviewing, reporting, and publishing guidelines; updating guidelines; and the two emerging issues of enhancing guideline implementability and how guideline developers should approach dealing with the issue of patients who will be the subject of guidelines having co-morbid conditions. PMID:22762242

  12. Implementation of the NCSS Guidelines for Teaching Science-Related Social Issues: Exemplar Lessons.

    ERIC Educational Resources Information Center

    Otto, Robert A., Ed.

    This document contains the Guidelines for Teaching Science-Related Social Issues adopted in 1982 by the National Council for the Social Studies and 10 examplar lessons each keyed to particular guidelines and drawing upon contemporary issues. The premise upon which the guidelines are based is that science is a social issue and that the examination…

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

    PubMed

    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. Requirements for guidelines systems: implementation challenges and lessons from existing software-engineering efforts

    PubMed Central

    2012-01-01

    Background 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. Methods 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). Results 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. Conclusions 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. PMID:22405400

  15. Design software for reuse

    NASA Technical Reports Server (NTRS)

    Tracz, Will

    1990-01-01

    Viewgraphs are presented on the designing of software for reuse. Topics include terminology, software reuse maxims, the science of programming, an interface design example, a modularization example, and reuse and implementation guidelines.

  16. Software engineering standards and practices

    NASA Technical Reports Server (NTRS)

    Durachka, R. W.

    1981-01-01

    Guidelines are presented for the preparation of a software development plan. The various phases of a software development project are discussed throughout its life cycle including a general description of the software engineering standards and practices to be followed during each phase.

  17. Guidelines for Better Heart Health

    MedlinePlus

    Skip Navigation Bar Home Current Issue Past Issues Guidelines for Better Heart Health Past Issues / Winter 2007 ... women either had or did not have CVD. Guidelines at a Glance: Prevention should be tailored to ...

  18. New Asthma Guidelines What You Should Know

    MedlinePlus

    ... Bar Home Current Issue Past Issues Special Section New Asthma Guidelines: What You Should Know Past Issues / ... and chairs the Expert Panel that established the new guidelines. The report gives health care professionals new ...

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

    NASA Technical Reports Server (NTRS)

    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.

  20. Multibeam Sonar Backscatter Data Acquisition and Processing: Guidelines and Recommendations from the GEOHAB Backscatter Working Group

    NASA Astrophysics Data System (ADS)

    Heffron, E.; Lurton, X.; Lamarche, G.; Brown, C.; Lucieer, V.; Rice, G.; Schimel, A.; Weber, T.

    2015-12-01

    Backscatter data acquired with multibeam sonars are now commonly used for the remote geological interpretation of the seabed. The systems hardware, software, and processing methods and tools have grown in numbers and improved over the years, yet many issues linger: there are no standard procedures for acquisition, poor or absent calibration, limited understanding and documentation of processing methods, etc. A workshop organized at the GeoHab (a community of geoscientists and biologists around the topic of marine habitat mapping) annual meeting in 2013 was dedicated to seafloor backscatter data from multibeam sonars and concluded that there was an overwhelming need for better coherence and agreement on the topics of acquisition, processing and interpretation of data. The GeoHab Backscatter Working Group (BSWG) was subsequently created with the purpose of documenting and synthetizing the state-of-the-art in sensors and techniques available today and proposing methods for best practice in the acquisition and processing of backscatter data. Two years later, the resulting document "Backscatter measurements by seafloor-mapping sonars: Guidelines and Recommendations" was completed1. The document provides: An introduction to backscatter measurements by seafloor-mapping sonars; A background on the physical principles of sonar backscatter; A discussion on users' needs from a wide spectrum of community end-users; A review on backscatter measurement; An analysis of best practices in data acquisition; A review of data processing principles with details on present software implementation; and finally A synthesis and key recommendations. This presentation reviews the BSWG mandate, structure, and development of this document. It details the various chapter contents, its recommendations to sonar manufacturers, operators, data processing software developers and end-users and its implication for the marine geology community. 1: Downloadable at https://www.niwa.co.nz/coasts-and-oceans/research-projects/backscatter-measurement-guidelines

  1. GCS plan for software aspects of certification

    NASA Technical Reports Server (NTRS)

    Shagnea, Anita M.; Lowman, Douglas S.; Withers, B. Edward

    1990-01-01

    As part of the Guidance and Control Software (GCS) research project being sponsored by NASA to evaluate the failure processes of software, standard industry software development procedures are being employed. To ensure that these procedures are authentic, the guidelines outlined in the Radio Technical Commission for Aeronautics (RTCA/DO-178A document entitled, software considerations in airborne systems and equipment certification, were adopted. A major aspect of these guidelines is proper documentation. As such, this report, the plan for software aspects of certification, was produced in accordance with DO-178A. An overview is given of the GCS research project, including the goals of the project, project organization, and project schedules. It also specifies the plans for all aspects of the project which relate to the certification of the GCS implementations developed under a NASA contract. These plans include decisions made regarding the software specification, accuracy requirements, configuration management, implementation development and verification, and the development of the GCS simulator.

  2. Barriers for guideline adherence in knee osteoarthritis care: A qualitative study from the patients' perspective.

    PubMed

    Spitaels, David; Vankrunkelsven, Patrik; Desfosses, Jurgen; Luyten, Frank; Verschueren, Sabine; Van Assche, Dieter; Aertgeerts, Bert; Hermens, Rosella

    2017-02-01

    Guidelines for patients with knee osteoarthritis (OA) are suboptimally implemented in clinical care. To improve guideline adherence, patients' perceived barriers and facilitators in current care were investigated. Eleven patients with knee OA were extensively interviewed using a semistructured script based on quality indicators. Directed content analysis, within the framework of Grol and Wensing, was performed to describe barriers and facilitators in 6 domains: guideline, health care professional, patient, social environment, organization, and financial context. Data were analyzed using NVIVO 10 software. In total, 38 barriers, at all 6 domains, were identified. The most frequently mentioned barriers were in the domains of the patient and the health care professional, namely, patients' disagreement with guidelines recommendations, negative experience with drugs, patients' limited comprehension of the disease process, and poor communication by the health care professional. The patients' disagreement with recommendations is further explained by the following barriers: "insistence on medical imaging," "fear that physiotherapy aggravates pain," and "perception that knee OA is not a priority health issue". Patients also reported 20 facilitators, all of which are listed as opposing barriers. Patients indicate that both personal factors and factors related to health care professionals play an important role in nonadherence. An interview script, based on quality indicators, was a significant aid to structurally formulate barriers and facilitators in the perceived knee OA care. Future guideline implementation strategies should take the identified barriers and facilitators into account. © 2016 John Wiley & Sons, Ltd.

  3. Selecting and Buying Educational Software.

    ERIC Educational Resources Information Center

    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. Inclusion of ethical issues in dementia guidelines: a thematic text analysis.

    PubMed

    Knüppel, Hannes; Mertz, Marcel; Schmidhuber, Martina; Neitzke, Gerald; Strech, Daniel

    2013-08-01

    Clinical practice guidelines (CPGs) aim to improve professionalism in health care. However, current CPG development manuals fail to address how to include ethical issues in a systematic and transparent manner. The objective of this study was to assess the representation of ethical issues in general CPGs on dementia care. To identify national CPGs on dementia care, five databases of guidelines were searched and national psychiatric associations were contacted in August 2011 and in June 2013. A framework for the assessment of the identified CPGs' ethical content was developed on the basis of a prior systematic review of ethical issues in dementia care. Thematic text analysis and a 4-point rating score were employed to assess how ethical issues were addressed in the identified CPGs. Twelve national CPGs were included. Thirty-one ethical issues in dementia care were identified by the prior systematic review. The proportion of these 31 ethical issues that were explicitly addressed by each CPG ranged from 22% to 77%, with a median of 49.5%. National guidelines differed substantially with respect to (a) which ethical issues were represented, (b) whether ethical recommendations were included, (c) whether justifications or citations were provided to support recommendations, and (d) to what extent the ethical issues were explained. Ethical issues were inconsistently addressed in national dementia guidelines, with some guidelines including most and some including few ethical issues. Guidelines should address ethical issues and how to deal with them to help the medical profession understand how to approach care of patients with dementia, and for patients, their relatives, and the general public, all of whom might seek information and advice in national guidelines. There is a need for further research to specify how detailed ethical issues and their respective recommendations can and should be addressed in dementia guidelines. Please see later in the article for the Editors' Summary.

  5. Inclusion of Ethical Issues in Dementia Guidelines: A Thematic Text Analysis

    PubMed Central

    Knüppel, Hannes; Schmidhuber, Martina; Neitzke, Gerald

    2013-01-01

    Background Clinical practice guidelines (CPGs) aim to improve professionalism in health care. However, current CPG development manuals fail to address how to include ethical issues in a systematic and transparent manner. The objective of this study was to assess the representation of ethical issues in general CPGs on dementia care. Methods and Findings To identify national CPGs on dementia care, five databases of guidelines were searched and national psychiatric associations were contacted in August 2011 and in June 2013. A framework for the assessment of the identified CPGs' ethical content was developed on the basis of a prior systematic review of ethical issues in dementia care. Thematic text analysis and a 4-point rating score were employed to assess how ethical issues were addressed in the identified CPGs. Twelve national CPGs were included. Thirty-one ethical issues in dementia care were identified by the prior systematic review. The proportion of these 31 ethical issues that were explicitly addressed by each CPG ranged from 22% to 77%, with a median of 49.5%. National guidelines differed substantially with respect to (a) which ethical issues were represented, (b) whether ethical recommendations were included, (c) whether justifications or citations were provided to support recommendations, and (d) to what extent the ethical issues were explained. Conclusions Ethical issues were inconsistently addressed in national dementia guidelines, with some guidelines including most and some including few ethical issues. Guidelines should address ethical issues and how to deal with them to help the medical profession understand how to approach care of patients with dementia, and for patients, their relatives, and the general public, all of whom might seek information and advice in national guidelines. There is a need for further research to specify how detailed ethical issues and their respective recommendations can and should be addressed in dementia guidelines. Please see later in the article for the Editors' Summary PMID:23966839

  6. Guidelines for software inspections

    NASA Technical Reports Server (NTRS)

    1983-01-01

    Quality control inspections are software problem finding procedures which provide defect removal as well as improvements in software functionality, maintenance, quality, and development and testing methodology is discussed. The many side benefits include education, documentation, training, and scheduling.

  7. ICCE Policy Statement on Network and Multiple Machine Software.

    ERIC Educational Resources Information Center

    International Council for Computers in Education, Eugene, OR.

    Designed to provide educators with guidance for the lawful reproduction of computer software, this document contains suggested guidelines, sample forms, and several short articles concerning software copyright and license agreements. The initial policy statement calls for educators to provide software developers (or their agents) with a…

  8. A study of software management and guidelines for flight projects

    NASA Technical Reports Server (NTRS)

    1980-01-01

    A survey of present software development policies and practices, and an analysis of these policies and practices are summarized. Background information necessary to assess the adequacy of present NASA flight software development approaches is presented.

  9. Space Station Software Issues

    NASA Technical Reports Server (NTRS)

    Voigt, S. (Editor); Beskenis, S. (Editor)

    1985-01-01

    Issues in the development of software for the Space Station are discussed. Software acquisition and management, software development environment, standards, information system support for software developers, and a future software advisory board are addressed.

  10. Guidelines for preparing software user documentation

    NASA Technical Reports Server (NTRS)

    Miller, Diane F.

    1987-01-01

    Clear, easy-to-use software user's manuals make strong demands on special technical communication techniques. Principles and guidelines are given for analyzing the audience and dealing with wide-ranging backgrounds of potential users. Types of information to be included in a complete manual are suggested, with a technique for creating a user-oriented rather than process-oriented organization. Accuracy verification is emphasized. Simple tips are gievn for formatting for quick comprehension and reference, for deciding on packaging, for creating helpful illustrations and examples, and for setting up clear and consistent conventions. Simple guidelines are offered for writing clearly and concisely and for editing.

  11. 78 FR 26783 - Agency Information Collection Activities; Announcement of Office of Management and Budget...

    Federal Register 2010, 2011, 2012, 2013, 2014

    2013-05-08

    ...; Public Health Service Guideline on Infectious Disease Issues on Xenotransplantation AGENCY: Food and Drug... collection of information entitled ``Public Health Service Guideline on Infectious Disease Issues on... information entitled ``Public Health Service Guideline on Infectious Disease Issues on Xenotransplantation...

  12. Sneak Analysis Application Guidelines

    DTIC Science & Technology

    1982-06-01

    Hardware Program Change Cost Trend, Airborne Environment ....... ....................... 111 3-11 Relative Software Program Change Costs...113 3-50 Derived Software Program Change Cost by Phase,* Airborne Environment ..... ............... 114 3-51 Derived Software Program Change...Cost by Phase, Ground/Water Environment ... ............. .... 114 3-52 Total Software Program Change Costs ................ 115 3-53 Sneak Analysis

  13. Sociotechnical Challenges of Developing an Interoperable Personal Health Record

    PubMed Central

    Gaskin, G.L.; Longhurst, C.A.; Slayton, R.; Das, A.K.

    2011-01-01

    Objectives To analyze sociotechnical issues involved in the process of developing an interoperable commercial Personal Health Record (PHR) in a hospital setting, and to create guidelines for future PHR implementations. Methods This qualitative study utilized observational research and semi-structured interviews with 8 members of the hospital team, as gathered over a 28 week period of developing and adapting a vendor-based PHR at Lucile Packard Children’s Hospital at Stanford University. A grounded theory approach was utilized to code and analyze over 100 pages of typewritten field notes and interview transcripts. This grounded analysis allowed themes to surface during the data collection process which were subsequently explored in greater detail in the observations and interviews. Results Four major themes emerged: (1) Multidisciplinary teamwork helped team members identify crucial features of the PHR; (2) Divergent goals for the PHR existed even within the hospital team; (3) Differing organizational conceptions of the end-user between the hospital and software company differentially shaped expectations for the final product; (4) Difficulties with coordination and accountability between the hospital and software company caused major delays and expenses and strained the relationship between hospital and software vendor. Conclusions Though commercial interoperable PHRs have great potential to improve healthcare, the process of designing and developing such systems is an inherently sociotechnical process with many complex issues and barriers. This paper offers recommendations based on the lessons learned to guide future development of such PHRs. PMID:22003373

  14. OHD/HL - Staff

    Science.gov Websites

    Laboratory Branches Hydrologic Software Engineering Branch (HSEB) Hydrologic Science and Modeling Branch (HSMB) General Info Publications Documentation Software Standard and Guidelines Contact Us HL Staff resources and services. Staff Directory Chief, Hydrology Laboratory; Chief, Hydrologic Software Engineering

  15. DOE Office of Scientific and Technical Information (OSTI.GOV)

    Kirby, M.J.; Kramer, S.R.; Pittard, G.T.

    Jason Consultants International, Inc., under the sponsorship of the Gas Research Institute (GRI), has developed guidelines, procedures and software, which are described in this paper, for the installation of polyethylene gas pipe using guided horizontal drilling. Jason was aided in this development by two key subcontractors; Maurer Engineering who wrote the software and NICOR Technologies who reviewed the software and guidelines from a utility perspective. This program resulted in the development of commerically viable software for utilities, contractors, engineering firms, and others involved with the installation of pipes using guided horizontal drilling. The software is an interactive design tool thatmore » allows the user to enter ground elevation data, alignment information and pipe data. The software aides the engineer in designing a drill path and provides plan and profile views along with tabular data for pipe depth and surface profile. Finally, the software calculates installation loads and pipe stresses, compares these values against pipe manufacturer`s recommendations, and provides this information graphically and in tabular form. 5 refs., 18 figs., 2 tabs.« less

  16. Executable medical guidelines with Arden Syntax-Applications in dermatology and obstetrics.

    PubMed

    Seitinger, Alexander; Rappelsberger, Andrea; Leitich, Harald; Binder, Michael; Adlassnig, Klaus-Peter

    2016-08-12

    Clinical decision support systems (CDSSs) are being developed to assist physicians in processing extensive data and new knowledge based on recent scientific advances. Structured medical knowledge in the form of clinical alerts or reminder rules, decision trees or tables, clinical protocols or practice guidelines, score algorithms, and others, constitute the core of CDSSs. Several medical knowledge representation and guideline languages have been developed for the formal computerized definition of such knowledge. One of these languages is Arden Syntax for Medical Logic Systems, an International Health Level Seven (HL7) standard whose development started in 1989. Its latest version is 2.10, which was presented in 2014. In the present report we discuss Arden Syntax as a modern medical knowledge representation and processing language, and show that this language is not only well suited to define clinical alerts, reminders, and recommendations, but can also be used to implement and process computerized medical practice guidelines. This section describes how contemporary software such as Java, server software, web-services, XML, is used to implement CDSSs based on Arden Syntax. Special emphasis is given to clinical decision support (CDS) that employs practice guidelines as its clinical knowledge base. Two guideline-based applications using Arden Syntax for medical knowledge representation and processing were developed. The first is a software platform for implementing practice guidelines from dermatology. This application employs fuzzy set theory and logic to represent linguistic and propositional uncertainty in medical data, knowledge, and conclusions. The second application implements a reminder system based on clinically published standard operating procedures in obstetrics to prevent deviations from state-of-the-art care. A to-do list with necessary actions specifically tailored to the gestational week/labor/delivery is generated. Today, with the latest versions of Arden Syntax and the application of contemporary software development methods, Arden Syntax has become a powerful and versatile medical knowledge representation and processing language, well suited to implement a large range of CDSSs, including clinical-practice-guideline-based CDSSs. Moreover, such CDS is provided and can be shared as a service by different medical institutions, redefining the sharing of medical knowledge. Arden Syntax is also highly flexible and provides developers the freedom to use up-to-date software design and programming patterns for external patient data access. Copyright © 2016. Published by Elsevier B.V.

  17. 76 FR 5289 - Income Level for Individuals Eligible for Assistance

    Federal Register 2010, 2011, 2012, 2013, 2014

    2011-01-31

    ... amendments to the Federal Poverty Guidelines as issued by the Department of Health and Human Services. DATES... Poverty Guidelines. Since 1982, the Department of Health and Human Services has been responsible for updating and issuing the Federal Poverty Guidelines. On January 26, 2011, LSC issued a notice in the...

  18. Software production methodology tested project

    NASA Technical Reports Server (NTRS)

    Tausworthe, R. C.

    1976-01-01

    The history and results of a 3 1/2-year study in software development methodology are reported. The findings of this study have become the basis for DSN software development guidelines and standard practices. The article discusses accomplishments, discoveries, problems, recommendations and future directions.

  19. Towards a Controlled Vocabulary on Software Engineering Education

    ERIC Educational Resources Information Center

    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…

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

    ERIC Educational Resources Information Center

    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…

  1. Holistic Approaches to Reading (The Printout).

    ERIC Educational Resources Information Center

    Balajthy, Ernest

    1989-01-01

    Presents eight guidelines to consider when using computers for language instruction, emphasizing computer use in a social and purposeful context. Suggests computer software which adheres to these guidelines. (MM)

  2. Added value of involving patients in the first step of multidisciplinary guideline development: a qualitative interview study among infertile patients.

    PubMed

    den Breejen, Elvira M E; Hermens, Rosella P M G; Galama, Wienke H; Willemsen, Wim N P; Kremer, Jan A M; Nelen, Willianne L D M

    2016-06-01

    Patient involvement in scoping the guideline is emphasized, but published initiatives actively involving patients are generally limited to the writing and reviewing phase. To assess patients' added value to the scoping phase of a multidisciplinary guideline on infertility. Qualitative interview study. We conducted interviews among 12 infertile couples and 17 professionals. We listed and compared the couples' and professionals' key clinical issues (=care aspects that need improvement) to be addressed in the guideline according to four domains: current guidelines, professionals, patients and organization of care. Main key clinical issues suggested by more than three quarters of the infertile couples and/or at least two professionals were identified and compared. Overall, we identified 32 key clinical issues among infertile couples and 23 among professionals. Of the defined main key clinical issues, infertile couples mentioned eight issues that were not mentioned by the professionals. These main key clinical issues mainly concerned patient-centred (e.g. poor information provision and poor alignment of care) aspects of care on the professional and organizational domain. Both groups mentioned two main key clinical issues collectively that were interpreted differently: the lack of emotional support and respect for patients' values. Including patients from the first phase of the guideline development process leads to valuable additional main key clinical issues for the next step of a multidisciplinary guideline development process and broadens the scope of the guideline, particularly regarding patient-centredness and organizational issues from a patients' perspective. © The Author 2016. Published by Oxford University Press in association with the International Society for Quality in Health Care; all rights reserved.

  3. NASA space station software standards issues

    NASA Technical Reports Server (NTRS)

    Tice, G. D., Jr.

    1985-01-01

    The selection and application of software standards present the NASA Space Station Program with the opportunity to serve as a pacesetter for the United States software in the area of software standards. The strengths and weaknesses of each of the NASA defined software standards issues are summerized and discussed. Several significant standards issues are offered for NASA consideration. A challenge is presented for the NASA Space Station Program to serve as a pacesetter for the U.S. Software Industry through: (1) Management commitment to software standards; (2) Overall program participation in software standards; and (3) Employment of the best available technology to support software standards

  4. Evaluation of computer-generated guidelines for companions of paediatric patients undergoing chemotherapy.

    PubMed

    Lopes, Vagner José; Shmeil, Marcos Augusto Hochuli

    2017-04-27

    To compare computer-generated guidelines with and without the use of a Clinical Decision Support System - Oncology Care and Healthcare for Chemotherapy Patients, for the caregivers of children undergoing chemotherapy. This is a descriptive, evaluative, and quantitative study conducted at a paediatrics hospital in Curitiba, Paraná, Brazil, from December 2015 to January 2016. The sample consisted of 58 participants divided into two groups: Group 1, without the aid of software, and Group 2, with the aid of the software. The data were analysed using the Mann-Whitney U test. The guidelines revealed a statistical significance (p<0.05), with a prevalence of a higher concordance average in Group 2 in comparison with Group 1. Computer-generated guidelines are a valuable qualitative support tool for nurses.

  5. WE-F-201-00: Practical Guidelines for Commissioning Advanced Brachytherapy Dose Calculation Algorithms

    DOE Office of Scientific and Technical Information (OSTI.GOV)

    NONE

    2015-06-15

    With the recent introduction of heterogeneity correction algorithms for brachytherapy, the AAPM community is still unclear on how to commission and implement these into clinical practice. The recently-published AAPM TG-186 report discusses important issues for clinical implementation of these algorithms. A charge of the AAPM-ESTRO-ABG Working Group on MBDCA in Brachytherapy (WGMBDCA) is the development of a set of well-defined test case plans, available as references in the software commissioning process to be performed by clinical end-users. In this practical medical physics course, specific examples on how to perform the commissioning process are presented, as well as descriptions of themore » clinical impact from recent literature reporting comparisons of TG-43 and heterogeneity-based dosimetry. Learning Objectives: Identify key clinical applications needing advanced dose calculation in brachytherapy. Review TG-186 and WGMBDCA guidelines, commission process, and dosimetry benchmarks. Evaluate clinical cases using commercially available systems and compare to TG-43 dosimetry.« less

  6. Promoting entrepreneurship among informatics engineering students: insights from a case study

    NASA Astrophysics Data System (ADS)

    Fernandes, João M.; Afonso, Paulo; Fonte, Victor; Alves, Victor; Ribeiro, António Nestor

    2017-01-01

    Universities seek to promote entrepreneurship through effective education approaches, which need to be in permanent evolution. Nevertheless, the literature in entrepreneurship education lacks empirical evidence. This article discusses relevant issues related to promoting entrepreneurship in the software field, based on the experience of a 15-European Credit Transfer and Accumulation System course. This course seeks to instil in the students the recognition of the need to reconcile technical and business visions, organisational and commercial aspects, most of which have never been addressed previously. A series of semi-structured interviews made it possible to obtain relevant insights about the teaching-learning process underlying this course and its evolution over a seven-year period. Materials related with this course have been analysed, namely guidelines produced by the teachers and deliverables produced by the students. This article discusses the dimensions that were identified as fundamental for promoting entrepreneurship skills in the field of software, namely teamwork, project engagement, and contact with the market.

  7. Evaluating Math Drill and Practice Programs.

    ERIC Educational Resources Information Center

    Schnorr, Janice M.; Semmel, Dorothy S.

    1986-01-01

    General guidelines for a process evaluation of software for a specific subject and grade include: (1) Specify instructional objectives and list desired software program characteristics; (2) Access and review descriptions of programs (information sources for math programs are listed); (3) Preview software; and (4) Compare and make purchase…

  8. Educational Software--New Guidelines for Development.

    ERIC Educational Resources Information Center

    Gold, Patricia Cohen

    1984-01-01

    Discusses standards developed by the Educational Computer Service of the National Education Association that incorporate technical, educational, and documentation components to guide authors in the development of quality educational software. (Author/MBR)

  9. Psychosocial issues in evidence-based guidelines on inflammatory bowel diseases: A review

    PubMed Central

    Häuser, Winfried; Moser, Gabriele; Klose, Petra; Mikocka-Walus, Antonina

    2014-01-01

    AIM: To study statements and recommendations on psychosocial issues as presented in international evidence-based guidelines on the management of inflammatory bowel diseases (IBD). METHODS: MEDLINE, guidelines International Network, National Guideline Clearing House and National Institute for Health and Care Excellence were searched from January 2006 to June 30, 2013 for evidence-based guidelines on the management of IBD. RESULTS: The search yielded 364 hits. Thirteen guidelines were included in the review, of which three were prepared in Asia, eight in Europe and two in the United States. Eleven guidelines made statements and recommendations on psychosocial issues. The guidelines were concordant in that mental health disorders and stress do not contribute to the aetiology of IBD, but that they can influence its course. It was recommended that IBD-patients should be screened for psychological distress. If indicated, psychotherapy and/or psychopharmacological therapy should be recommended. IBD-centres should collaborate with mental health care specialists. Tobacco smoking patients with Crohn’s disease should be advised to quit. CONCLUSION: Patients and mental health specialists should be able to participate in future guideline groups to contribute to establishing recommendations on psychosocial issues in IBD. Future guidelines should acknowledge the presence of psychosocial problems in IBD-patients and encourage screening for psychological distress. PMID:24707152

  10. Guide to Software Conversion Management. [Final Report.

    ERIC Educational Resources Information Center

    Skall, M., Ed.

    Based mainly on interviews conducted at 14 federal agencies that had completed or were involved in software conversion projects, this publication provides guidelines for the entire process of software conversion. This is defined as the transformation, without functional change, of computer programs or data elements to permit their use on a…

  11. 15 CFR Supplement No. 6 to Part 742 - Guidelines for Submitting Review Requests for Encryption Items

    Code of Federal Regulations, 2010 CFR

    2010-01-01

    ... brochures or other documentation or specifications related to the technology, commodity or software... commodity or software, provide the following information: (1) Description of all the symmetric and... is provided by third-party hardware or software encryption components (if any). Identify the...

  12. Statistical modelling of software reliability

    NASA Technical Reports Server (NTRS)

    Miller, Douglas R.

    1991-01-01

    During the six-month period from 1 April 1991 to 30 September 1991 the following research papers in statistical modeling of software reliability appeared: (1) A Nonparametric Software Reliability Growth Model; (2) On the Use and the Performance of Software Reliability Growth Models; (3) Research and Development Issues in Software Reliability Engineering; (4) Special Issues on Software; and (5) Software Reliability and Safety.

  13. What do international pharmacoeconomic guidelines say about economic data transferability?

    PubMed

    Barbieri, Marco; Drummond, Michael; Rutten, Frans; Cook, John; Glick, Henry A; Lis, Joanna; Reed, Shelby D; Sculpher, Mark; Severens, Johan L

    2010-12-01

    The objectives of this article were to assess the positions of the various national pharmacoeconomic guidelines on the transferability (or lack of transferability) of clinical and economic data and to review the methods suggested in the guidelines for addressing issues of transferability. A review of existing national pharmacoeconomic guidelines was conducted to assess recommendations on the transferability of clinical and economic data, whether there are important differences between countries, and whether common methodologies have been suggested to address key transferability issues. Pharmacoeconomic guidelines were initially identified through the ISPOR Web site. In addition, those national guidelines not included in the ISPOR Web site, but known to us, were also considered. Across 27 sets of guidelines, baseline risk and unit costs were uniformly considered to be of low transferability, while treatment effect was classified as highly transferable. Results were more variable for resource use and utilities, which were considered to have low transferability in 63% and 45% of cases, respectively. There were some differences between older and more recent guidelines in the treatment of transferability issues. A growing number of jurisdictions are using guidelines for the economic evaluation of pharmaceuticals. The recommendations in existing guidelines regarding the transferability of clinical and economic data are quite diverse. There is a case for standardization in dealing with transferability issues. One important step would be to update guidelines more frequently. © 2010, International Society for Pharmacoeconomics and Outcomes Research (ISPOR).

  14. Guidelines for development structured FORTRAN programs

    NASA Technical Reports Server (NTRS)

    Earnest, B. M.

    1984-01-01

    Computer programming and coding standards were compiled to serve as guidelines for the uniform writing of FORTRAN 77 programs at NASA Langley. Software development philosophy, documentation, general coding conventions, and specific FORTRAN coding constraints are discussed.

  15. Certain aspects on medical devices software law regulation.

    PubMed

    Pashkov, Vitalii; Harkusha, Andrii

    some kind of easiness of entry in creating software products on various computing platforms has led to such products being made available perhaps without due consideration of potential risks to users and patients and the most valuable reason for this have been lack of regulatory clarity. Some key points on legal regulation of abovementioned sphere is a base of this study. Ukrainian legislation, European Union`s Guidelines on the qualification and classification of standalone software; Guidance for the Content of Premarket Submissions for Software Contained in Medical Devices that works in United States of America. Article is based on dialectical, comparative, analytic, synthetic and comprehensive research methods. in accordance with Ukrainian legislation, software that has a medical purpose could be a medical device. Ukrainian legislation which is established on European Union Medical Devices Directives divide all medical devices on classes. But there aren't any special recommendations or advices on classifications for software medical devices in Ukraine. It is necessary to develop and adopt guidelines on the qualification and classification of medical device software in Ukraine especially considering the harmonization of Ukrainian legislation with the EU legislation, develop special rules for the application of the national mark of conformity for medical device software and defined the « responsible organization » for the medical device software approval process.

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

    PubMed

    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.

  17. Model-based software process improvement

    NASA Technical Reports Server (NTRS)

    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.

  18. Personnel Training--Secondary Vocational Agriculture Teacher Education.

    ERIC Educational Resources Information Center

    Brown, Herman D.; And Others

    This document consists of three parts. The first part is a report on a project conducted to develop computer software needed by vocational agriculture teachers in Texas. The report details the process used to assess and develop software, and provides guidelines that can be used by others in evaluating computer software for vocational agriculture…

  19. A guidelines handbook for GPR surveys in tunnels: a COST Action TU1208 contribution

    NASA Astrophysics Data System (ADS)

    Bianchini Ciampoli, Luca; Alani, Amir M.; Pajewski, Lara; Benedetto, Andrea; Loizos, Andreas; Tosti, Fabio

    2016-04-01

    A significant open issue concerning the reliability of geophysical methods and in particular of ground penetrating radar (GPR), both in research and professional context, is a general lack of international standards. This is a major problem to be faced, in order to gain scientific strictness for the GPR practices, and to easily extend to the international community the results achieved within the area of single virtuous countries. Producing international guidelines can represent an important step forward, in this sense. In the memorandum of understanding of the COST Action TU1208 is clearly stated that one of the main purposes of the Action is the "development of innovative protocols and guidelines which will be published in a handbook and constitute a basis for European Standards, for an effective GPR application in CE tasks; safety, economic and financial criteria will be integrated within the protocols". Of course this is not a simple task to be accomplished. Firstly, survey procedures are highly dependent on the objective of the survey itself. On the basis of the objective of each geophysical test, the GPR system, the antenna configuration, and even the processing procedures may change. Besides, these procedures are also influenced by the environmental conditions in which the tests are performed. This affects several aspects spanning from hardware to software, but including, for instance, also safety issues. Due to these reasons, one of the main goal of the COST Action TU1208 is the development of several guidelines related to the main applications of GPR in the field of civil engineering. In this work, the structure of a guidelines handbook for GPR activities in tunnels is outlined. In the first sections, the principal references in the field are provided, and the most common GPR equipment and complementary technologies are described. Subsequently, the survey methodologies are explained. Particular attention is paid to the preliminary activities to be carried out prior to the GPR surveys, which can cover an important role in such a complex environment. Lastly, the main applications of GPR technology in tunnels are discussed. Acknowledgement The Authors thank COST, for funding the Action TU1208 "Civil Engineering Applications of Ground Penetrating Radar."

  20. Surrogate Safety Assessment Model (SSAM)--software user manual

    DOT National Transportation Integrated Search

    2008-05-01

    This document presents guidelines for the installation and use of the Surrogate Safety Assessment Model (SSAM) software. For more information regarding the SSAM application, including discussion of theoretical background and the results of a series o...

  1. Guidelines for PCC inputs to AASHTOWare Pavement ME.

    DOT National Transportation Integrated Search

    2014-12-01

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

  2. Ethics guidelines, health research and Indigenous Australians.

    PubMed

    Anderson, Ian; Griew, Robert; McAullay, Daniel

    2003-02-01

    In this paper we overview the findings of a literature review that was undertaken to guide the revision of the Guidelines on Ethical Matters in Aboriginal and Torres Strait Islander Health Research (NH&MRC, 1991). The literature reviewed, in general, supported the development of specific research guidelines for Aboriginal and Torres Strait Islander contexts. The findings of this review were analysed thematically, and a number of key issues were identified for consideration in the review process. We present a summary of these key issues. In the final section of the paper we consider in more detail two of the key issues raised in the review process (the assessment of relevance or benefit of proposed research; and the process of consultation and negotiation of collective consent) in order to critically consider how these issue should be engaged in revised guidelines. On the basis of this analysis, it is our contention that specific guidelines on key issues are limited to the extent to which they can anticipate all possible research contexts. In order to address this problem, and guide researchers, guidelines should also explicitly outline the values, from an Aboriginal and Torres Islander perspective that are foundational to an ethical research process.

  3. Evaluating geographic information systems technology

    USGS Publications Warehouse

    Guptill, Stephen C.

    1989-01-01

    Computerized geographic information systems (GISs) are emerging as the spatial data handling tools of choice for solving complex geographical problems. However, few guidelines exist for assisting potential users in identifying suitable hardware and software. A process to be followed in evaluating the merits of GIS technology is presented. Related standards and guidelines, software functions, hardware components, and benchmarking are discussed. By making users aware of all aspects of adopting GIS technology, they can decide if GIS is an appropriate tool for their application and, if so, which GIS should be used.

  4. Scientific authorship. Part 2. History, recurring issues, practices, and guidelines.

    PubMed

    Claxton, Larry D

    2005-01-01

    One challenge for most scientists is avoiding and resolving issues that center around authorship and the publishing of scientific manuscripts. While trying to place the research in proper context, impart new knowledge, follow proper guidelines, and publish in the most appropriate journal, the scientist often must deal with multi-collaborator issues like authorship allocation, trust and dependence, and resolution of publication conflicts. Most guidelines regarding publications, commentaries, and editorials have evolved from the ranks of editors in an effort to diminish the issues that faced them as editors. For example, the Ingelfinger rule attempts to prevent duplicate publications of the same study. This paper provides a historical overview of commonly encountered scientific authorship issues, a comparison of opinions on these issues, and the influence of various organizations and guidelines in regards to these issues. For example, a number of organizations provide guidelines for author allocation; however, a comparison shows that these guidelines differ on who should be an author, rules for ordering authors, and the level of responsibility for coauthors. Needs that emerge from this review are (a) a need for more controlled studies on authorship issues, (b) an increased awareness and a buy-in to consensus views by non-editor groups, e.g., managers, authors, reviewers, and scientific societies, and (c) a need for editors to express a greater understanding of authors' dilemmas and to exhibit greater flexibility. Also needed are occasions (e.g., an international congress) when editors and others (managers, authors, etc.) can directly exchange views, develop consensus approaches and solutions, and seek agreement on how to resolve authorship issues. Open dialogue is healthy, and it is essential for scientific integrity to be protected so that younger scientists can confidently follow the lead of their predecessors.

  5. Enterprise System Implementations: Lessons from the Trenches.

    ERIC Educational Resources Information Center

    McCredie, Jack; Updegrove, Dan

    1999-01-01

    Offers 20 practical guidelines for colleges and universities embarking on large-scale administrative software initiatives or enterprise resource planning systems. Guidelines are based on the extensive experience of the authors and a series of panel discussions at 1999 professional meetings. (DB)

  6. Design and Pedagogical Issues in the Development of the InSight Series of Instructional Software.

    ERIC Educational Resources Information Center

    Baro, John A.; Lehmkulke, Stephen

    1993-01-01

    Design issues in development of InSight software for optometric education include choice of hardware, identification of audience, definition of scope and limitations of content, selection of user interface and programing environment, obtaining user feedback, and software distribution. Pedagogical issues include practicality and improvement on…

  7. A Structure for Creating Quality Software.

    ERIC Educational Resources Information Center

    Christensen, Larry C.; Bodey, Michael R.

    1990-01-01

    Addresses the issue of assuring quality software for use in computer-aided instruction and presents a structure by which developers can create quality courseware. Differences between courseware and computer-aided instruction software are discussed, methods for testing software are described, and human factors issues as well as instructional design…

  8. Working Notes from the 1992 AAAI Workshop on Automating Software Design. Theme: Domain Specific Software Design

    NASA Technical Reports Server (NTRS)

    Keller, Richard M. (Editor); Barstow, David; Lowry, Michael R.; Tong, Christopher H.

    1992-01-01

    The goal of this workshop is to identify different architectural approaches to building domain-specific software design systems and to explore issues unique to domain-specific (vs. general-purpose) software design. Some general issues that cut across the particular software design domain include: (1) knowledge representation, acquisition, and maintenance; (2) specialized software design techniques; and (3) user interaction and user interface.

  9. 12 CFR 1.130 - Type II securities; guidelines for obligations issued for university and housing purposes.

    Code of Federal Regulations, 2014 CFR

    2014-01-01

    ...; guidelines for obligations issued for university and housing purposes. (a) Investment quality. An obligation issued for housing, university, or dormitory purposes is a Type II security only if it: (1) Qualifies as... issued for university and housing purposes. 1.130 Section 1.130 Banks and Banking COMPTROLLER OF THE...

  10. 12 CFR 1.130 - Type II securities; guidelines for obligations issued for university and housing purposes.

    Code of Federal Regulations, 2011 CFR

    2011-01-01

    ...; guidelines for obligations issued for university and housing purposes. (a) Investment quality. An obligation issued for housing, university, or dormitory purposes is a Type II security only if it: (1) Qualifies as... issued for university and housing purposes. 1.130 Section 1.130 Banks and Banking COMPTROLLER OF THE...

  11. 12 CFR 1.130 - Type II securities; guidelines for obligations issued for university and housing purposes.

    Code of Federal Regulations, 2012 CFR

    2012-01-01

    ...; guidelines for obligations issued for university and housing purposes. (a) Investment quality. An obligation issued for housing, university, or dormitory purposes is a Type II security only if it: (1) Qualifies as... issued for university and housing purposes. 1.130 Section 1.130 Banks and Banking COMPTROLLER OF THE...

  12. 12 CFR 1.130 - Type II securities; guidelines for obligations issued for university and housing purposes.

    Code of Federal Regulations, 2013 CFR

    2013-01-01

    ...; guidelines for obligations issued for university and housing purposes. (a) Investment quality. An obligation issued for housing, university, or dormitory purposes is a Type II security only if it: (1) Qualifies as... issued for university and housing purposes. 1.130 Section 1.130 Banks and Banking COMPTROLLER OF THE...

  13. Closing the loop on improvement: Packaging experience in the Software Engineering Laboratory

    NASA Technical Reports Server (NTRS)

    Waligora, Sharon R.; Landis, Linda C.; Doland, Jerry T.

    1994-01-01

    As part of its award-winning software process improvement program, the Software Engineering Laboratory (SEL) has developed an effective method for packaging organizational best practices based on real project experience into useful handbooks and training courses. This paper shares the SEL's experience over the past 12 years creating and updating software process handbooks and training courses. It provides cost models and guidelines for successful experience packaging derived from SEL experience.

  14. 7 CFR 622.5 - Guidelines.

    Code of Federal Regulations, 2010 CFR

    2010-01-01

    ... NEPA (40 CFR parts 1500-1508) issued by the Council on Environmental Quality, and in Economic and Environmental Principles and Guidelines for Water and Related Land Resources Implementation Studies issued by...

  15. Medical device software: defining key terms.

    PubMed

    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.

  16. A Strategy for Improved System Assurance

    DTIC Science & Technology

    2007-06-20

    Quality (Measurements Life Cycle Safety, Security & Others) ISO /IEC 12207 * Software Life Cycle Processes ISO 9001 Quality Management System...14598 Software Product Evaluation Related ISO /IEC 90003 Guidelines for the Application of ISO 9001:2000 to Computer Software IEEE 12207 Industry...Implementation of International Standard ISO /IEC 12207 IEEE 1220 Standard for Application and Management of the System Engineering Process Use in

  17. Designing the user interface: strategies for effective human-computer interaction

    NASA Astrophysics Data System (ADS)

    Shneiderman, B.

    1998-03-01

    In revising this popular book, Ben Shneiderman again provides a complete, current and authoritative introduction to user-interface design. The user interface is the part of every computer system that determines how people control and operate that system. When the interface is well designed, it is comprehensible, predictable, and controllable; users feel competent, satisfied, and responsible for their actions. Shneiderman discusses the principles and practices needed to design such effective interaction. Based on 20 years experience, Shneiderman offers readers practical techniques and guidelines for interface design. He also takes great care to discuss underlying issues and to support conclusions with empirical results. Interface designers, software engineers, and product managers will all find this book an invaluable resource for creating systems that facilitate rapid learning and performance, yield low error rates, and generate high user satisfaction. Coverage includes the human factors of interactive software (with a new discussion of diverse user communities), tested methods to develop and assess interfaces, interaction styles such as direct manipulation for graphical user interfaces, and design considerations such as effective messages, consistent screen design, and appropriate color.

  18. Space Station Freedom biomedical monitoring and countermeasures: Biomedical facility hardware catalog

    NASA Technical Reports Server (NTRS)

    1990-01-01

    This hardware catalog covers that hardware proposed under the Biomedical Monitoring and Countermeasures Development Program supported by the Johnson Space Center. The hardware items are listed separately by item, and are in alphabetical order. Each hardware item specification consists of four pages. The first page describes background information with an illustration, definition and a history/design status. The second page identifies the general specifications, performance, rack interface requirements, problems, issues, concerns, physical description, and functional description. The level of hardware design reliability is also identified under the maintainability and reliability category. The third page specifies the mechanical design guidelines and assumptions. Described are the material types and weights, modules, and construction methods. Also described is an estimation of percentage of construction which utilizes a particular method, and the percentage of required new mechanical design is documented. The fourth page analyzes the electronics, the scope of design effort, and the software requirements. Electronics are described by percentages of component types and new design. The design effort, as well as, the software requirements are identified and categorized.

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

    DOE Office of Scientific and Technical Information (OSTI.GOV)

    Sturtevant, Judith E.; Heaphy, Robert; Hodges, Ann Louise

    2006-09-01

    The purpose of the Sandia National Laboratories Advanced Simulation and Computing (ASC) Software Quality Plan is to clearly identify the practices that are the basis for continually improving the quality of ASC software products. The plan defines the ASC program software quality practices and provides mappings of these practices to Sandia Corporate Requirements CPR 1.3.2 and 1.3.6 and to a Department of Energy document, ASCI Software Quality Engineering: Goals, Principles, and Guidelines. This document also identifies ASC management and software project teams responsibilities in implementing the software quality practices and in assessing progress towards achieving their software quality goals.

  20. San Antonio I Software Workshop Proceedings. DoD Software for the 1990s, Held in San Antonio, Texas on 28 January - 1 February 1991

    DTIC Science & Technology

    1991-12-01

    management and engineering issues common to the military-industrial complex, - to learn from past experience, - to understand future software...prospective policy documents. - :Prepare a draft issue paper and presentation for the DAE. These items should address the key implementation issues with...respect to MCCR software metrics and establish a clear need for DAE support. Long Term Actions ( past 12-18 mcnths) ... Draft final implementation

  1. Unreasonable Compensation: The Hidden Issue in the IRS College and University Examination Guidelines.

    ERIC Educational Resources Information Center

    Harding, Bertrand M., Jr.; McClellan, Edgar D.

    1993-01-01

    Issues in Internal Revenue Service (IRS) guidelines for financial audit of colleges and universities that relate specifically to the institution's compensation of officers, directors, and employees are discussed. Institutions are advised that the "unreasonable compensation" issue may be raised, and they should review compensation…

  2. 32 CFR 199.10 - Appeal and hearing procedures.

    Code of Federal Regulations, 2011 CFR

    2011-07-01

    ... issues shall be bound by policy manuals, instructions, procedures, and other guidelines issued by the ASD..., procedures, instructions or guidelines by the ASD(HA), or a designee, when the final decision is issued in... Department of Defense in the administration of CHAMPUS. (ii) Referral for review by ASD(HA). The Director...

  3. Space Debris Modeling at NASA

    NASA Technical Reports Server (NTRS)

    Johnson, Nicholas L.

    2001-01-01

    Since the Second European Conference on Space Debris in 1997, the Orbital Debris Program Office at the NASA Johnson Space Center has undertaken a major effort to update and improve the principal software tools employed to model the space debris environment and to evaluate mission risks. NASA's orbital debris engineering model, ORDEM, represents the current and near-term Earth orbital debris population from the largest spacecraft to the smallest debris in a manner which permits spacecraft engineers and experimenters to estimate the frequency and velocity with which a satellite may be struck by debris of different sizes. Using expanded databases and a new program design, ORDEM2000 provides a more accurate environment definition combined with a much broader array of output products in comparison with its predecessor, ORDEM96. Studies of the potential long-term space debris environment are now conducted with EVOLVE 4.0, which incorporates significant advances in debris characterization and breakup modeling. An adjunct to EVOLVE 4.0, GEO EVOLVE has been created to examine debris issues near the geosynchronous orbital regime. In support of NASA Safety Standard 1740.14, which establishes debris mitigation guidelines for all NASA space programs, a set of evaluation tools called the Debris Assessment Software (DAS) is specifically designed for program offices to determine whether they are in compliance with NASA debris mitigation guidelines. DAS 1.5 has recently been released with improved WINDOWS compatibility and graphics functions. DAS 2.0 will incorporate guideline changes in a forthcoming revision to NASA Safety Standard 1740.14. Whereas DAS contains a simplified model to calculate possible risks associated with satellite reentries, NASA's higher fidelity Object Reentry Survival Analysis Tool (ORSAT) has been upgraded to Version 5.0. With the growing awareness of the potential risks posed by uncontrolled satellite reentries to people and property on Earth, the application of both DAS and ORSAT has increased markedly in the past two years.

  4. How to Choose a Media Retrieval System.

    ERIC Educational Resources Information Center

    Huber, Joe

    1995-01-01

    Provides guidelines for schools choosing a media retrieval system. Topics include broadband, baseband, coaxial cable, or fiber optic decisions; the control network; selecting scheduling software; presentation software; device control; control from the classroom; and a comparison of systems offered by five companies. (LRW)

  5. Standards guide for space and earth sciences computer software

    NASA Technical Reports Server (NTRS)

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

    1972-01-01

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

  6. Desktop Publishing Choices: Making an Appropriate Decision.

    ERIC Educational Resources Information Center

    Crawford, Walt

    1991-01-01

    Discusses various choices available for desktop publishing systems. Four categories of software are described, including advanced word processing, graphics software, low-end desktop publishing, and mainstream desktop publishing; appropriate hardware is considered; and selection guidelines are offered, including current and future publishing needs,…

  7. Computer Bits: Child Care Center Management Software Buying Guide Update.

    ERIC Educational Resources Information Center

    Neugebauer, Roger

    1987-01-01

    Compares seven center management programs used for basic financial and data management tasks such as accounting, payroll and attendance records, and mailing lists. Describes three other specialized programs and gives guidelines for selecting the best software for a particular center. (NH)

  8. Responsible Internet Use.

    ERIC Educational Resources Information Center

    Truett, Carol; And Others

    1997-01-01

    Provides advice for making school Internet-use guidelines. Outlines responsible proactive use of the Internet for educators and librarians, discusses strengths and weaknesses of Internet blocking software and rating systems, and describes acceptable-use policies (AUP). Lists resources for creating your own AUP, Internet filtering software, and…

  9. 45 CFR 307.1 - Definitions.

    Code of Federal Regulations, 2014 CFR

    2014-10-01

    ... system means the hardware, operational software, applications software and electronic linkages in an... further defined in the OCSE guideline entitled “Automated Systems for Child Support Enforcement: A Guide... training, testing, and conversion plans to install the computer system. (j) The following terms are defined...

  10. 45 CFR 307.1 - Definitions.

    Code of Federal Regulations, 2011 CFR

    2011-10-01

    ... system means the hardware, operational software, applications software and electronic linkages in an... further defined in the OCSE guideline entitled “Automated Systems for Child Support Enforcement: A Guide... training, testing, and conversion plans to install the computer system. (j) The following terms are defined...

  11. 45 CFR 307.1 - Definitions.

    Code of Federal Regulations, 2012 CFR

    2012-10-01

    ... system means the hardware, operational software, applications software and electronic linkages in an... further defined in the OCSE guideline entitled “Automated Systems for Child Support Enforcement: A Guide... training, testing, and conversion plans to install the computer system. (j) The following terms are defined...

  12. 45 CFR 307.1 - Definitions.

    Code of Federal Regulations, 2013 CFR

    2013-10-01

    ... system means the hardware, operational software, applications software and electronic linkages in an... further defined in the OCSE guideline entitled “Automated Systems for Child Support Enforcement: A Guide... training, testing, and conversion plans to install the computer system. (j) The following terms are defined...

  13. 45 CFR 307.1 - Definitions.

    Code of Federal Regulations, 2010 CFR

    2010-10-01

    ... system means the hardware, operational software, applications software and electronic linkages in an... further defined in the OCSE guideline entitled “Automated Systems for Child Support Enforcement: A Guide... training, testing, and conversion plans to install the computer system. (j) The following terms are defined...

  14. Implementing reusable software components for SNOMED CT diagram and expression concept representations.

    PubMed

    Bánfai, Balázs; Porció, Roland; Kovács, Tibor

    2014-01-01

    SNOMED CT is a vital component in the future of semantic interoperability in healthcare as it provides the meaning to EHRs via its semantically rich, controlled terminology. Communicating the concepts of this terminology to both humans and machines is crucial therefore formal guidelines for diagram and expression representations have been developed by the curators of SNOMED CT. This paper presents a novel, model-based approach to implementing these guidelines that allows simultaneous editing of a concept via both diagram and expression editors. The implemented extensible software component can be embedded both both desktop and web applications.

  15. Effects of an electronic reminder system on guideline-concordant treatment of psychotic disorders : Results from a pilot feasibility trial.

    PubMed

    Franke, Irina; Thier, Sarah; Riecher-Rössler, Anita

    2016-12-01

    Adherence to evidence-based guidelines is essential for the treatment outcome of psychotic disorders. Previous studies showed that IT-supported pathways are able to increase guideline adherence in psychiatric care. This paper describes a pilot study on the development of an electronic recall-reminder-system (RRS) for supporting guideline-adherent treatment in outpatient care of patients with chronic psychotic disorders and analyses its feasibility. Guidelines were integrated in the RRS software M.E.M.O.R.E.S. Software training for the staff was provided. We compared the number of conducted vs. guideline-recommended interventions 6 months before and after implementation. Subsequently both the caregivers' and the patients' satisfaction with the RRS was evaluated. Guideline adherence in general was low and the RRS was barely used. After its implementation a significant increase was observed in chemogram-check-ups and diagnostics regarding cardiovascular risks (esp. ECG). Both patients and professionals described problems with integrating the RRS in their daily routine and questioned the usefulness of the guidelines for chronically ill, although they basically approved its importance and usefulness. Participants appreciated the idea of supporting guideline adherence with an IT-system, but there seemed to be major obstacles to implementation: caregivers appear to be concerned of being exposed or questioned, technical difficulties might lead to avoidance, and there seems to be a lack of knowledge and awareness about the health risks for individuals with psychotic disorders. Possibly guidelines adapted for the chronically ill would find more acceptance. Technical simplifications and better information should be considered prior to further attempts to implement IT-supported guidelines in order to increase acceptance.

  16. Research and Design Issues Concerning the Development of Educational Software for Children. Technical Report No. 14.

    ERIC Educational Resources Information Center

    Char, Cynthia

    Several research and design issues to be considered when creating educational software were identified by a field test evaluation of three types of innovative software created at Bank Street College: (1) Probe, software for measuring and graphing temperature data; (2) Rescue Mission, a navigation game that illustrates the computer's use for…

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

    DOE Office of Scientific and Technical Information (OSTI.GOV)

    Lstiburek, J.; Ueno, K.; Musunuru, S.

    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.

  18. Software Cost Measuring and Reporting. One of the Software Acquisition Engineering Guidebook Series.

    DTIC Science & Technology

    1979-01-02

    through the peripherals. How- and performance criteria), ever, his interaction is usually minimal since, by difinition , the automatic test Since TS...performs its Software estimating is still heavily intended functions properly. dependent on experienced judgement. However, quantitative methods...apply to systems of totally different can be distributed to specialists who content. The Quantitative guideline may are most familiar with the work. One

  19. SQA of finite element method (FEM) codes used for analyses of pit storage/transport packages

    DOE Office of Scientific and Technical Information (OSTI.GOV)

    Russel, E.

    1997-11-01

    This report contains viewgraphs on the software quality assurance of finite element method codes used for analyses of pit storage and transport projects. This methodology utilizes the ISO 9000-3: Guideline for application of 9001 to the development, supply, and maintenance of software, for establishing well-defined software engineering processes to consistently maintain high quality management approaches.

  20. Quality control in urodynamics and the role of software support in the QC procedure.

    PubMed

    Hogan, S; Jarvis, P; Gammie, A; Abrams, P

    2011-11-01

    This article aims to identify quality control (QC) best practice, to review published QC audits in order to identify how closely good practice is followed, and to carry out a market survey of the software features that support QC offered by urodynamics machines available in the UK. All UK distributors of urodynamic systems were contacted and asked to provide information on the software features relating to data quality of the products they supply. The results of the market survey show that the features offered by manufacturers differ greatly. Automated features, which can be turned off in most cases, include: cough recognition, detrusor contraction detection, and high pressure alerts. There are currently no systems that assess data quality based on published guidelines. A literature review of current QC guidelines for urodynamics was carried out; QC audits were included in the literature review to see how closely guidelines were being followed. This review highlights the fact that basic QC is not being carried out effectively by urodynamicists. Based on the software features currently available and the results of the literature review there is both the need and capacity for a greater degree of automation in relation to urodynamic data quality and accuracy assessment. Some progress has been made in this area and certain manufacturers have already developed automated cough detection. Copyright © 2011 Wiley Periodicals, Inc.

  1. Copyright in a Digital Age: How To Comply with the Law--and Set a Good Example for Students.

    ERIC Educational Resources Information Center

    Becker, Gary H.

    2000-01-01

    As classroom technology has developed, so have copyright laws and guidelines. Guidelines are outlined for taping broadcasts, using "home use only" videocasettes, networking and duplicating computer software, incorporating copyrighted material for multimedia productions, creating materials for posting on Internet websites, and…

  2. Collecting and Using Networked Statistics: Current Status, Future Goals

    ERIC Educational Resources Information Center

    Hiott, Judith

    2004-01-01

    For more than five years the Houston Public Library has collected statistics for measuring networked collections and services based on emerging guidelines. While the guidelines have provided authority and stability to the process, the clarification process continues. The development of information discovery software, such as federated search tools…

  3. An Overview of Video Description: History, Benefits, and Guidelines

    ERIC Educational Resources Information Center

    Packer, Jaclyn; Vizenor, Katie; Miele, Joshua A.

    2015-01-01

    This article provides an overview of the historical context in which video description services have evolved in the United States, a summary of research demonstrating benefits to people with vision loss, an overview of current video description guidelines, and information about current software programs that are available to produce video…

  4. Developing and Using Ada Parts in Real-Time Embedded Applications

    DTIC Science & Technology

    1990-04-27

    ARCHTECTURAL DESIGN Guideline #3-a: Avoid duplication of data types packages. Guideline #3-b: Minimize variant proliferation. Concentrate on developing a...of SOFTWARE REUSE DEVELOPING and USING ADA PARTS in RTE APPUCATIONS ARCHTECTURAL DESIGN Table 5-10 illustrates the use of this more strongly data typed

  5. Guidelines for Developing Computer Based Resource Units. Revised.

    ERIC Educational Resources Information Center

    State Univ. of New York, Buffalo. Coll. at Buffalo. Educational Research and Development Complex.

    Presented for use with normal and handicapped children are guidelines for the development of computer based resource units organized into two operations: one of which is the production of software which includes the writing of instructional objectives, content, activities, materials, and measuring devices; and the other the coding of the software…

  6. Accelerated Math[TM]. What Works Clearinghouse Intervention Report

    ERIC Educational Resources Information Center

    What Works Clearinghouse, 2011

    2011-01-01

    "Accelerated Math"[TM], published by Renaissance Learning, is a software tool used to customize assignments and monitor progress in math for students in grades 1-12. The "Accelerated Math"[TM] software creates individualized assignments aligned with state standards and national guidelines, scores student work, and generates…

  7. Using hybrid expert system approaches for engineering applications

    NASA Technical Reports Server (NTRS)

    Allen, R. H.; Boarnet, M. G.; Culbert, C. J.; Savely, R. T.

    1987-01-01

    In this paper, the use of hybrid expert system shells and hybrid (i.e., algorithmic and heuristic) approaches for solving engineering problems is reported. Aspects of various engineering problem domains are reviewed for a number of examples with specific applications made to recently developed prototype expert systems. Based on this prototyping experience, critical evaluations of and comparisons between commercially available tools, and some research tools, in the United States and Australia, and their underlying problem-solving paradigms are made. Characteristics of the implementation tool and the engineering domain are compared and practical software engineering issues are discussed with respect to hybrid tools and approaches. Finally, guidelines are offered with the hope that expert system development will be less time consuming, more effective, and more cost-effective than it has been in the past.

  8. Improved access to life insurance after genetic diagnosis of familial hypercholesterolaemia: cross-sectional postal questionnaire study

    PubMed Central

    Huijgen, Roeland; Homsma, Sietske JM; Hutten, Barbara A; Kindt, Iris; Vissers, Maud N; Kastelein, John JP; van Rijckevorsel, Jan LA

    2012-01-01

    A decade ago, in the initial stage of genetic testing for familial hypercholesterolaemia (FH) in The Netherlands, it was reported that such screening decreased access to affordable life insurance for mutation carriers. In 2003, in order to improve access to insurance for FH mutation carriers, insurers agreed to underwrite according to a set of guidelines. In this cross-sectional study, we assessed whether access to insurance has improved since the advent of these guidelines. We approached 2825 subjects that had participated in the genetic testing for FH between 1998 and 2003. We compared unconditional acceptance rates before and after FH diagnosis and before and after the guidelines were issued by means of logistic regression analysis. Our study outcome pertains to 414 FH patients who applied for life insurance. Unconditional acceptance of a policy before DNA diagnosis and before the issue of guidelines occurred in 182 out of 255 (71%) cases, versus 27 out of 35 (77%) cases after DNA diagnosis, but before the issue of guidelines. De facto, 107 out of 124 (86%) patients received unconditional acceptance after DNA diagnosis and after the issue of guidelines (P for trend=0.002). Access to life insurance improved for FH patients after molecular diagnosis and it improved even further after the guidelines were issued. Therefore, we argue that limited access to life insurance on the basis of ‘DNA discrimination' is no longer a valid argument against genetic cascade testing for FH, at least not in our country. PMID:22293687

  9. Computer Software & Intellectual Property. Background Paper.

    ERIC Educational Resources Information Center

    Congress of the U.S., Washington, DC. Office of Technology Assessment.

    This background paper reviews copyright, patent, and trade secret protections as these issues are related to computer software. Topics discussed include current issues regarding legal protection for computer software including the necessity for defining intellectual property, determining what should or should not be protected, commerical piracy,…

  10. Development of user guidelines for ECAS display design, volume 1

    NASA Technical Reports Server (NTRS)

    Dodson, D. W.; Shields, N. L., Jr.

    1978-01-01

    Experiment computer application software (ECAS) display design and command usage guidelines were developed, which if followed by spacelab experiments, would standardize methods and techniques for data presentation and commanding via ECAS. These guidelines would provide some commonality among experiments which would enhance crew training and flight operations. The guidelines are applicable to all onboard experiment displays, whether allocated by ECAS or a dedicated experiment processor. A brief description of the spacelab data display system characteristics and of the services provided by the experiment computer operating system is included. Guidelines concerning data presentation and layout of alphanumeric and graphic information are presented along with guidelines concerning keyboard commanding and command feedback.

  11. How the NWC handles software as product

    DOE Office of Scientific and Technical Information (OSTI.GOV)

    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 customersmore » will be described.« less

  12. Technology-driven dietary assessment: a software developer’s perspective

    PubMed Central

    Buday, Richard; Tapia, Ramsey; Maze, Gary R.

    2015-01-01

    Dietary researchers need new software to improve nutrition data collection and analysis, but creating information technology is difficult. Software development projects may be unsuccessful due to inadequate understanding of needs, management problems, technology barriers or legal hurdles. Cost overruns and schedule delays are common. Barriers facing scientific researchers developing software include workflow, cost, schedule, and team issues. Different methods of software development and the role that intellectual property rights play are discussed. A dietary researcher must carefully consider multiple issues to maximize the likelihood of success when creating new software. PMID:22591224

  13. Space station: The role of software

    NASA Technical Reports Server (NTRS)

    Hall, D.

    1985-01-01

    Software will play a critical role throughout the Space Station Program. This presentation sets the stage and prompts participant interaction at the Software Issues Forum. The presentation is structured into three major topics: (1) an overview of the concept and status of the Space Station Program; (2) several charts designed to lay out the scope and role of software; and (3) information addressing the four specific areas selected for focus at the forum, specifically: software management, the software development environment, languages, and standards. NASA's current thinking is highlighted and some of the relevant critical issues are raised.

  14. Computers as Teaching Tools: Some Examples and Guidelines.

    ERIC Educational Resources Information Center

    Beins, Bernard C.

    The use of computers in the classroom has been touted as an important innovation in education. This article features some recently developed software for use in teaching psychology and different approaches to classroom computer use. Uses of software packages for psychological research designs are included as are applications and limitations of…

  15. Improving software maintenance through measurement

    NASA Technical Reports Server (NTRS)

    Rombach, H. Dieter; Ulery, Bradford T.

    1989-01-01

    A practical approach to improving software maintenance through measurements is presented. This approach is based on general models for measurement and improvement. Both models, their integration, and practical guidelines for transferring them into industrial maintenance settings are presented. Several examples of applications of the approach to real-world maintenance environments are discussed.

  16. Guidelines for Software Engineering Education Version 1.0

    DTIC Science & Technology

    1999-11-01

    Turbo Pascal and Software Design. Sudbury, Massachusetts: Jones and Bartlett, 1997. " Deitel, Harvey M. & Deitel, Paul J. C++: How to Program . Upper...Saddle River, New Jersey: Prentice-Hall, 1997. " Deitel, Harvey M. & Deitel, Paul J. Java: How to Program . Upper Saddle River, New Jersey: Prentice-Hall

  17. Risk Assessment Methodology for Software Supportability (RAMSS): guidelines for Adapting Software Supportability Evaluations

    DTIC Science & Technology

    1986-04-14

    CONCIPT DIFINITION OIVILOPMINTITIST I OPERATION ANO ■ MAINTENANCE ■ TRACK MOifCTIO PROGRAMS • «VIIW CRITICAL ISSUIS . Mt PARI INPUTS TO PMO...development and beyond, evaluation criteria must Include quantitative goals (the desired value) and thresholds (the value beyond which the charac

  18. Cancer screening in the United States, 2018: A review of current American Cancer Society guidelines and current issues in cancer screening.

    PubMed

    Smith, Robert A; Andrews, Kimberly S; Brooks, Durado; Fedewa, Stacey A; Manassaram-Baptiste, Deana; Saslow, Debbie; Brawley, Otis W; Wender, Richard C

    2018-05-30

    Each year, the American Cancer Society publishes a summary of its guidelines for early cancer detection, data and trends in cancer screening rates from the National Health Interview Survey, and select issues related to cancer screening. In this 2018 update, we also summarize the new American Cancer Society colorectal cancer screening guideline and include a clarification in the language of the 2013 lung cancer screening guideline. CA Cancer J Clin 2018. © 2018 American Cancer Society. © 2018 American Cancer Society.

  19. 76 FR 60017 - Technical Conference on Penalty Guidelines; Notice of Technical Conference on Penalty Guidelines

    Federal Register 2010, 2011, 2012, 2013, 2014

    2011-09-28

    ... Conference on Penalty Guidelines; Notice of Technical Conference on Penalty Guidelines The staff of the... the Penalty Guidelines, which the Commission issued on September 17, 2010.\\1\\ The conference will be... impact of the Penalty Guidelines on compliance and enforcement matters. More information on the topics to...

  20. Guidelines for Performing Regulatory Impact Analysis (1983/1991)

    EPA Pesticide Factsheets

    These 1983 guidelines as modified in 1991 provide guidance for preparing EPA Regulatory Impact Analyses including benefit-cost analyses. These guidelines have been superseded by the Guidelines for Preparing Economic Analyses issued in 2000 (see EE-0568).

  1. DOE Office of Scientific and Technical Information (OSTI.GOV)

    None

    Module-level power electronics, such as DC power optimizers, microinverters, and those found in AC modules, are increasing in popularity in smaller-scale photovoltaic (PV) systems as their prices continue to decline. Therefore, it is important to provide PV modelers with guidelines about how to model these distributed power electronics appropriately in PV modeling software. This paper extends the work completed at NREL that provided recommendations to model the performance of distributed power electronics in NREL’s popular PVWatts calculator [1], to provide similar guidelines for modeling these technologies in NREL's more complex System Advisor Model (SAM). Module-level power electronics - such asmore » DC power optimizers, microinverters, and those found in AC modules-- are increasing in popularity in smaller-scale photovoltaic (PV) systems as their prices continue to decline. Therefore, it is important to provide PV modelers with guidelines about how to model these distributed power electronics appropriately in PV modeling software.« less

  2. Revisiting Information Technology tools serving authorship and editorship: a case-guided tutorial to statistical analysis and plagiarism detection

    PubMed Central

    Bamidis, P D; Lithari, C; Konstantinidis, S T

    2010-01-01

    With the number of scientific papers published in journals, conference proceedings, and international literature ever increasing, authors and reviewers are not only facilitated with an abundance of information, but unfortunately continuously confronted with risks associated with the erroneous copy of another's material. In parallel, Information Communication Technology (ICT) tools provide to researchers novel and continuously more effective ways to analyze and present their work. Software tools regarding statistical analysis offer scientists the chance to validate their work and enhance the quality of published papers. Moreover, from the reviewers and the editor's perspective, it is now possible to ensure the (text-content) originality of a scientific article with automated software tools for plagiarism detection. In this paper, we provide a step-bystep demonstration of two categories of tools, namely, statistical analysis and plagiarism detection. The aim is not to come up with a specific tool recommendation, but rather to provide useful guidelines on the proper use and efficiency of either category of tools. In the context of this special issue, this paper offers a useful tutorial to specific problems concerned with scientific writing and review discourse. A specific neuroscience experimental case example is utilized to illustrate the young researcher's statistical analysis burden, while a test scenario is purpose-built using open access journal articles to exemplify the use and comparative outputs of seven plagiarism detection software pieces. PMID:21487489

  3. Revisiting Information Technology tools serving authorship and editorship: a case-guided tutorial to statistical analysis and plagiarism detection.

    PubMed

    Bamidis, P D; Lithari, C; Konstantinidis, S T

    2010-12-01

    With the number of scientific papers published in journals, conference proceedings, and international literature ever increasing, authors and reviewers are not only facilitated with an abundance of information, but unfortunately continuously confronted with risks associated with the erroneous copy of another's material. In parallel, Information Communication Technology (ICT) tools provide to researchers novel and continuously more effective ways to analyze and present their work. Software tools regarding statistical analysis offer scientists the chance to validate their work and enhance the quality of published papers. Moreover, from the reviewers and the editor's perspective, it is now possible to ensure the (text-content) originality of a scientific article with automated software tools for plagiarism detection. In this paper, we provide a step-bystep demonstration of two categories of tools, namely, statistical analysis and plagiarism detection. The aim is not to come up with a specific tool recommendation, but rather to provide useful guidelines on the proper use and efficiency of either category of tools. In the context of this special issue, this paper offers a useful tutorial to specific problems concerned with scientific writing and review discourse. A specific neuroscience experimental case example is utilized to illustrate the young researcher's statistical analysis burden, while a test scenario is purpose-built using open access journal articles to exemplify the use and comparative outputs of seven plagiarism detection software pieces.

  4. Long-term pavement performance compliance with Department of Transportation information dissemination quality guidelines

    DOT National Transportation Integrated Search

    2008-11-01

    This document provides information on the compliance of the LTPP program with the guidelines the Department of Transportation (DOT) issued Information Dissemination Quality Guidelines (IDQG). These guidelines were developed in response to requirement...

  5. Clinical imaging guidelines part 2: Risks, benefits, barriers, and solutions.

    PubMed

    Malone, James; del Rosario-Perez, Maria; Van Bladel, Lodewijk; Jung, Seung Eun; Holmberg, Ola; Bettmann, Michael A

    2015-02-01

    A recent international meeting was convened by two United Nations bodies to focus on international collaboration on clinical appropriateness/referral guidelines for use in medical imaging. This paper, the second of 4 from this technical meeting, addresses barriers to the successful development/deployment of clinical imaging guidelines and means of overcoming them. It reflects the discussions of the attendees, and the issues identified are treated under 7 headings: ■ Practical Strategy for Development and Deployment of Guidelines; ■ Governance Arrangements and Concerns with Deployment of Guidelines; ■ Finance, Sustainability, Reimbursement, and Related Issues; ■ Identifying Benefits and Radiation Risks from Radiological Examinations; ■ Information Given to Patients and the Public, and Consent Issues; ■ Special Concerns Related to Pregnancy; and ■ The Research Agenda. Examples of topics identified include the observation that guideline development is a global task and there is no case for continuing it as the project of the few professional organizations that have been brave enough to make the long-term commitment required. Advocacy for guidelines should include the expectations that they will facilitate: (1) better health care delivery; (2) lower cost of that delivery; with (3) reduced radiation dose and associated health risks. Radiation protection issues should not be isolated; rather, they should be integrated with the overall health care picture. The type of dose/radiation risk information to be provided with guidelines should include the uncertainty involved and advice on application of the precautionary principle with patients. This principle may be taken as an extension of the well-established medical principle of "first do no harm." Copyright © 2015. Published by Elsevier Inc.

  6. Primary care of adults with developmental disabilities

    PubMed Central

    Sullivan, William F.; Berg, Joseph M.; Bradley, Elspeth; Cheetham, Tom; Denton, Richard; Heng, John; Hennen, Brian; Joyce, David; Kelly, Maureen; Korossy, Marika; Lunsky, Yona; McMillan, Shirley

    2011-01-01

    Abstract Objective To update the 2006 Canadian guidelines for primary care of adults with developmental disabilities (DD) and to make practical recommendations based on current knowledge to address the particular health issues of adults with DD. Quality of evidence Knowledgeable health care providers participating in a colloquium and a subsequent working group discussed and agreed on revisions to the 2006 guidelines based on a comprehensive review of publications, feedback gained from users of the guidelines, and personal clinical experiences. Most of the available evidence in this area of care is from expert opinion or published consensus statements (level III). Main message Adults with DD have complex health issues, many of them differing from those of the general population. Good primary care identifies the particular health issues faced by adults with DD to improve their quality of life, to improve their access to health care, and to prevent suffering, morbidity, and premature death. These guidelines synthesize general, physical, behavioural, and mental health issues of adults with DD that primary care providers should be aware of, and they present recommendations for screening and management based on current knowledge that practitioners can apply. Because of interacting biologic, psychoaffective, and social factors that contribute to the health and well-being of adults with DD, these guidelines emphasize involving caregivers, adapting procedures when appropriate, and seeking input from a range of health professionals when available. Ethical care is also emphasized. The guidelines are formulated within an ethical framework that pays attention to issues such as informed consent and the assessment of health benefits in relation to risks of harm. Conclusion Implementation of the guidelines proposed here would improve the health of adults with DD and would minimize disparities in health and health care between adults with DD and those in the general population. PMID:21571716

  7. A Heuristic Evaluation of the Generalized Intelligent Framework for Tutoring (GIFT) Authoring Tools

    DTIC Science & Technology

    2016-03-01

    Software Is Difficult to Locate and Download from the GIFT Website 5 2.1.2 Issue: Unclear Process for Starting GIFT Software Installation 7 2.1.3 Issue...and change information availability as the user’s expertise in using the authoring tools grows. • Aesthetic and Minimalist Design: Dialogues should...public release; distribution is unlimited. 7 2.1.2 Issue: Unclear Process for Starting GIFT Software Installation Users may not understand how to

  8. Representing nursing guideline with unified modeling language to facilitate development of a computer system: a case study.

    PubMed

    Choi, Jeeyae; Choi, Jeungok E

    2014-01-01

    To provide best recommendations at the point of care, guidelines have been implemented in computer systems. As a prerequisite, guidelines are translated into a computer-interpretable guideline format. Since there are no specific tools to translate nursing guidelines, only a few nursing guidelines are translated and implemented in computer systems. Unified modeling language (UML) is a software writing language and is known to well and accurately represent end-users' perspective, due to the expressive characteristics of the UML. In order to facilitate the development of computer systems for nurses' use, the UML was used to translate a paper-based nursing guideline, and its ease of use and the usefulness were tested through a case study of a genetic counseling guideline. The UML was found to be a useful tool to nurse informaticians and a sufficient tool to model a guideline in a computer program.

  9. Early Childhood Educational Software: Specific Features and Issues of Localization

    ERIC Educational Resources Information Center

    Nikolopoulou, Kleopatra

    2007-01-01

    The computer has now become a recognized tool in the education of young children and when used appropriately can reinforce their learning experiences. This paper reviews specific features (relating to pedagogic design, software content and user-interface design) of early childhood educational software and discusses issues in favor of its…

  10. General purpose optimization software for engineering design

    NASA Technical Reports Server (NTRS)

    Vanderplaats, G. N.

    1990-01-01

    The author has developed several general purpose optimization programs over the past twenty years. The earlier programs were developed as research codes and served that purpose reasonably well. However, in taking the formal step from research to industrial application programs, several important lessons have been learned. Among these are the importance of clear documentation, immediate user support, and consistent maintenance. Most important has been the issue of providing software that gives a good, or at least acceptable, design at minimum computational cost. Here, the basic issues developing optimization software for industrial applications are outlined and issues of convergence rate, reliability, and relative minima are discussed. Considerable feedback has been received from users, and new software is being developed to respond to identified needs. The basic capabilities of this software are outlined. A major motivation for the development of commercial grade software is ease of use and flexibility, and these issues are discussed with reference to general multidisciplinary applications. It is concluded that design productivity can be significantly enhanced by the more widespread use of optimization as an everyday design tool.

  11. Consolidated View on Space Software Engineering Problems - An Empirical Study

    NASA Astrophysics Data System (ADS)

    Silva, N.; Vieira, M.; Ricci, D.; Cotroneo, D.

    2015-09-01

    Independent software verification and validation (ISVV) has been a key process for engineering quality assessment for decades, and is considered in several international standards. The “European Space Agency (ESA) ISVV Guide” is used for the European Space market to drive the ISVV tasks and plans, and to select applicable tasks and techniques. Software artefacts have room for improvement due to the amount if issues found during ISVV tasks. This article presents the analysis of the results of a large set of ISVV issues originated from three different ESA missions-amounting to more than 1000 issues. The study presents the main types, triggers and impacts related to the ISVV issues found and sets the path for a global software engineering improvement based on the most common deficiencies identified for space projects.

  12. Ruby on Rails Issue Tracker

    NASA Technical Reports Server (NTRS)

    Rodriguez, Juan Jared

    2014-01-01

    The purpose of this report is to detail the tasks accomplished as a NASA NIFS intern for the summer 2014 session. This internship opportunity is to develop an issue tracker Ruby on Rails web application to improve the communication of developmental anomalies between the Support Software Computer Software Configuration Item (CSCI) teams, System Build and Information Architecture. As many may know software development is an arduous, time consuming, collaborative effort. It involves nearly as much work designing, planning, collaborating, discussing, and resolving issues as effort expended in actual development. This internship opportunity was put in place to help alleviate the amount of time spent discussing issues such as bugs, missing tests, new requirements, and usability concerns that arise during development and throughout the life cycle of software applications once in production.

  13. Sustainable design guidelines to support the Washington State ferries terminal design manual : stormwater and material issues.

    DOT National Transportation Integrated Search

    2011-08-01

    In an effort to assist the developers of the terminal design manual in potentially addressing : sustainable design issues, the overall goal is to produce Sustainable Design Guidelines that : will specifically address the unique needs and requirements...

  14. An approach to software cost estimation

    NASA Technical Reports Server (NTRS)

    Mcgarry, F.; Page, J.; Card, D.; Rohleder, M.; Church, V.

    1984-01-01

    A general procedure for software cost estimation in any environment is outlined. The basic concepts of work and effort estimation are explained, some popular resource estimation models are reviewed, and the accuracy of source estimates is discussed. A software cost prediction procedure based on the experiences of the Software Engineering Laboratory in the flight dynamics area and incorporating management expertise, cost models, and historical data is described. The sources of information and relevant parameters available during each phase of the software life cycle are identified. The methodology suggested incorporates these elements into a customized management tool for software cost prediction. Detailed guidelines for estimation in the flight dynamics environment developed using this methodology are presented.

  15. Evidence-based and value-based formulary guidelines.

    PubMed

    Neumann, Peter J

    2004-01-01

    Health plans and hospitals have long used drug formularies, but the processes by which formulary committees made decisions have typically lacked transparency and scientific rigor. A growing number of organizations have begun implementing formulary guidelines issued by the Academy of Managed Care Pharmacy (AMCP). These guidelines call for health plans to request formally that drug companies present a standardized "dossier" that contains detailed information not only on the drug's effectiveness and safety but also on its economic value relative to alternative therapies. This paper describes the guidelines, reviews progress to date, and analyzes several critical issues for the future.

  16. 5 CFR 724.403 - Advisory guidelines.

    Code of Federal Regulations, 2010 CFR

    2010-01-01

    ... 5 Administrative Personnel 2 2010-01-01 2010-01-01 false Advisory guidelines. 724.403 Section 724.403 Administrative Personnel OFFICE OF PERSONNEL MANAGEMENT (CONTINUED) CIVIL SERVICE REGULATIONS... RETALIATION ACT OF 2002 Best Practices § 724.403 Advisory guidelines. OPM will issue advisory guidelines to...

  17. Development of a Learning-Oriented Computer Assisted Instruction Designed to Improve Skills in the Clinical Assessment of the Nutritional Status: A Pilot Evaluation

    PubMed Central

    García de Diego, Laura; Cuervo, Marta; Martínez, J. Alfredo

    2015-01-01

    Computer assisted instruction (CAI) is an effective tool for evaluating and training students and professionals. In this article we will present a learning-oriented CAI, which has been developed for students and health professionals to acquire and retain new knowledge through the practice. A two-phase pilot evaluation was conducted, involving 8 nutrition experts and 30 postgraduate students, respectively. In each training session, the software developed guides users in the integral evaluation of a patient’s nutritional status and helps them to implement actions. The program includes into the format clinical tools, which can be used to recognize possible patient’s needs, to improve the clinical reasoning and to develop professional skills. Among them are assessment questionnaires and evaluation criteria, cardiovascular risk charts, clinical guidelines and photographs of various diseases. This CAI is a complete software package easy to use and versatile, aimed at clinical specialists, medical staff, scientists, educators and clinical students, which can be used as a learning tool. This application constitutes an advanced method for students and health professionals to accomplish nutritional assessments combining theoretical and empirical issues, which can be implemented in their academic curriculum. PMID:25978456

  18. Development of a learning-oriented computer assisted instruction designed to improve skills in the clinical assessment of the nutritional status: a pilot evaluation.

    PubMed

    García de Diego, Laura; Cuervo, Marta; Martínez, J Alfredo

    2015-01-01

    Computer assisted instruction (CAI) is an effective tool for evaluating and training students and professionals. In this article we will present a learning-oriented CAI, which has been developed for students and health professionals to acquire and retain new knowledge through the practice. A two-phase pilot evaluation was conducted, involving 8 nutrition experts and 30 postgraduate students, respectively. In each training session, the software developed guides users in the integral evaluation of a patient's nutritional status and helps them to implement actions. The program includes into the format clinical tools, which can be used to recognize possible patient's needs, to improve the clinical reasoning and to develop professional skills. Among them are assessment questionnaires and evaluation criteria, cardiovascular risk charts, clinical guidelines and photographs of various diseases. This CAI is a complete software package easy to use and versatile, aimed at clinical specialists, medical staff, scientists, educators and clinical students, which can be used as a learning tool. This application constitutes an advanced method for students and health professionals to accomplish nutritional assessments combining theoretical and empirical issues, which can be implemented in their academic curriculum.

  19. Software Reuse Issues

    NASA Technical Reports Server (NTRS)

    Voigt, Susan J. (Editor); Smith, Kathryn A. (Editor)

    1989-01-01

    NASA Langley Research Center sponsored a Workshop on NASA Research in Software Reuse on November 17-18, 1988 in Melbourne, Florida, hosted by Software Productivity Solutions, Inc. Participants came from four NASA centers and headquarters, eight NASA contractor companies, and three research institutes. Presentations were made on software reuse research at the four NASA centers; on Eli, the reusable software synthesis system designed and currently under development by SPS; on Space Station Freedom plans for reuse; and on other reuse research projects. This publication summarizes the presentations made and the issues discussed during the workshop.

  20. Software engineering and Ada in design

    NASA Technical Reports Server (NTRS)

    Oneill, Don

    1986-01-01

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

  1. GCS programmer's manual

    NASA Technical Reports Server (NTRS)

    Lowman, Douglas S.; Withers, B. Edward; Shagnea, Anita M.; Dent, Leslie A.; Hayhurst, Kelly J.

    1990-01-01

    A variety of instructions to be used in the development of implementations of software for the Guidance and Control Software (GCS) project is described. This document fulfills the Radio Technical Commission for Aeronautics RTCA/DO-178A guidelines, 'Software Considerations in Airborne Systems and Equipment Certification' requirements for document No. 4, which specifies the information necessary for understanding and programming the host computer, and document No. 12, which specifies the software design and implementation standards that are applicable to the software development and testing process. Information on the following subjects is contained: activity recording, communication protocol, coding standards, change management, error handling, design standards, problem reporting, module testing logs, documentation formats, accuracy requirements, and programmer responsibilities.

  2. 78 FR 9743 - Event Reporting Guidelines

    Federal Register 2010, 2011, 2012, 2013, 2014

    2013-02-11

    ... NUCLEAR REGULATORY COMMISSION [NRC-2011-0237] Event Reporting Guidelines AGENCY: Nuclear... Regulatory Commission (NRC) has issued NUREG- 1022, Revision 3, ``Event Reporting Guidelines: 10 CFR 50.72 and 50.73.'' [[Page 9744

  3. Guidelines for Documentation of Computer Programs and Automated Data Systems. (Category: Software; Subcategory: Documentation).

    ERIC Educational Resources Information Center

    Federal Information Processing Standards Publication, 1976

    1976-01-01

    These guidelines provide a basis for determining the content and extent of documentation for computer programs and automated data systems. Content descriptions of ten document types plus examples of how management can determine when to use the various types are included. The documents described are (1) functional requirements documents, (2) data…

  4. Section 508 Standards

    EPA Pesticide Factsheets

    Guidelines, design tips, and tools for ensuring that all Information and Communications Technology; including websites, software, hardware, multimedia, and telecommunication; is accessible to disabled users.

  5. Cancer screening in the United States, 2017: A review of current American Cancer Society guidelines and current issues in cancer screening.

    PubMed

    Smith, Robert A; Andrews, Kimberly S; Brooks, Durado; Fedewa, Stacey A; Manassaram-Baptiste, Deana; Saslow, Debbie; Brawley, Otis W; Wender, Richard C

    2017-03-01

    Answer questions and earn CME/CNE Each year, the American Cancer Society publishes a summary of its guidelines for early cancer detection, data and trends in cancer screening rates, and select issues related to cancer screening. In this issue of the journal, the authors summarize current American Cancer Society cancer screening guidelines, describe an update of their guideline for using human papillomavirus vaccination for cancer prevention, describe updates in US Preventive Services Task Force recommendations for breast and colorectal cancer screening, discuss interim findings from the UK Collaborative Trial on Ovarian Cancer Screening, and provide the latest data on utilization of cancer screening from the National Health Interview Survey. CA Cancer J Clin 2017;67:100-121. © 2017 American Cancer Society. © 2017 American Cancer Society.

  6. Spacelab software development and integration concepts study report, volume 1

    NASA Technical Reports Server (NTRS)

    Rose, P. L.; Willis, B. G.

    1973-01-01

    The proposed software guidelines to be followed by the European Space Research Organization in the development of software for the Spacelab being developed for use as a payload for the space shuttle are documented. Concepts, techniques, and tools needed to assure the success of a programming project are defined as they relate to operation of the data management subsystem, support of experiments and space applications, use with ground support equipment, and for integration testing.

  7. Guide to data collection

    NASA Technical Reports Server (NTRS)

    1981-01-01

    Guidelines and recommendations are presented for the collection of software development data. Motivation and planning for, and implementation and management of, a data collection effort are discussed. Topics covered include types, sources, and availability of data; methods and costs of data collection; types of analyses supported; and warnings and suggestions based on software engineering laboratory (SEL) experiences. This document is intended as a practical guide for software managers and engineers, abstracted and generalized from 5 years of SEL data collection.

  8. System Engineering Issues for Avionics Survival in the Space Environment

    NASA Technical Reports Server (NTRS)

    Pavelitz, Steven

    1999-01-01

    This paper examines how the system engineering process influences the design of a spacecraft's avionics by considering the space environment. Avionics are susceptible to the thermal, radiation, plasma, and meteoroids/orbital debris environments. The environment definitions for various spacecraft mission orbits (LEO/low inclination, LEO/Polar, MEO, HEO, GTO, GEO and High ApogeeElliptical) are discussed. NASA models and commercial software used for environment analysis are reviewed. Applicability of technical references, such as NASA TM-4527 "Natural Orbital Environment Guidelines for Use in Aerospace Vehicle Development" is discussed. System engineering references, such as the MSFC System Engineering Handbook, are reviewed to determine how the environments are accounted for in the system engineering process. Tools and databases to assist the system engineer and avionics designer in addressing space environment effects on avionics are described and usefulness assessed.

  9. Inclusion of Sexual Orientation and Gender Identity in Stage 3 Meaningful Use Guidelines: A Huge Step Forward for LGBT Health.

    PubMed

    Cahill, Sean R; Baker, Kellan; Deutsch, Madeline B; Keatley, Joanne; Makadon, Harvey J

    2016-04-01

    Final rules issued by the Centers for Medicare and Medicaid Services and the Office of the National Coordinator for Health Information Technology in October 2015 require electronic health record software certified for Meaningful Use to include sexual orientation and gender identity (SO/GI) fields. This is a critical step toward making SO/GI data collection a standard practice in clinical settings. Sexual orientation identity-whether one identifies as gay, lesbian, or bisexual-correlates with behavioral health burden, and it is important to collect these data. Providers should also collect sex assigned at birth data as well as current gender identity data. Training of clinical staff in collection and use of SO/GI data, education of LGBT patients, and SO/GI nondiscrimination policies are critical for successful implementation.

  10. 41 CFR 101-27.102-2 - Guidelines.

    Code of Federal Regulations, 2010 CFR

    2010-07-01

    ... Replenishment § 101-27.102-2 Guidelines. Guidelines for implementing the EOQ principle of stock replenishment are in the GSA Handbook, The Economic Order Quantity Principle and Applications, issued by the Federal...

  11. Human factors issues in the design of user interfaces for planning and scheduling

    NASA Technical Reports Server (NTRS)

    Murphy, Elizabeth D.

    1991-01-01

    The purpose is to provide and overview of human factors issues that impact the effectiveness of user interfaces to automated scheduling tools. The following methods are employed: (1) a survey of planning and scheduling tools; (2) the identification and analysis of human factors issues; (3) the development of design guidelines based on human factors literature; and (4) the generation of display concepts to illustrate guidelines.

  12. 5 CFR 724.403 - Advisory guidelines.

    Code of Federal Regulations, 2011 CFR

    2011-01-01

    ... 5 Administrative Personnel 2 2011-01-01 2011-01-01 false Advisory guidelines. 724.403 Section 724... (CONTINUED) IMPLEMENTATION OF TITLE II OF THE NOTIFICATION AND FEDERAL EMPLOYEE ANTIDISCRIMINATION AND RETALIATION ACT OF 2002 Best Practices § 724.403 Advisory guidelines. OPM will issue advisory guidelines to...

  13. 5 CFR 724.403 - Advisory guidelines.

    Code of Federal Regulations, 2013 CFR

    2013-01-01

    ... 5 Administrative Personnel 2 2013-01-01 2013-01-01 false Advisory guidelines. 724.403 Section 724... (CONTINUED) IMPLEMENTATION OF TITLE II OF THE NOTIFICATION AND FEDERAL EMPLOYEE ANTIDISCRIMINATION AND RETALIATION ACT OF 2002 Best Practices § 724.403 Advisory guidelines. OPM will issue advisory guidelines to...

  14. 5 CFR 724.403 - Advisory guidelines.

    Code of Federal Regulations, 2014 CFR

    2014-01-01

    ... 5 Administrative Personnel 2 2014-01-01 2014-01-01 false Advisory guidelines. 724.403 Section 724... (CONTINUED) IMPLEMENTATION OF TITLE II OF THE NOTIFICATION AND FEDERAL EMPLOYEE ANTIDISCRIMINATION AND RETALIATION ACT OF 2002 Best Practices § 724.403 Advisory guidelines. OPM will issue advisory guidelines to...

  15. 5 CFR 724.403 - Advisory guidelines.

    Code of Federal Regulations, 2012 CFR

    2012-01-01

    ... 5 Administrative Personnel 2 2012-01-01 2012-01-01 false Advisory guidelines. 724.403 Section 724... (CONTINUED) IMPLEMENTATION OF TITLE II OF THE NOTIFICATION AND FEDERAL EMPLOYEE ANTIDISCRIMINATION AND RETALIATION ACT OF 2002 Best Practices § 724.403 Advisory guidelines. OPM will issue advisory guidelines to...

  16. 50 CFR 253.18 - Program operating guidelines.

    Code of Federal Regulations, 2010 CFR

    2010-10-01

    ... 50 Wildlife and Fisheries 7 2010-10-01 2010-10-01 false Program operating guidelines. 253.18 Section 253.18 Wildlife and Fisheries NATIONAL MARINE FISHERIES SERVICE, NATIONAL OCEANIC AND ATMOSPHERIC... Guarantee Program § 253.18 Program operating guidelines. The Division may issue Program operating guidelines...

  17. [Quality control in the follow-up of pulmonary tuberculosis contacts in Camagüey, Cuba (2008-2011)].

    PubMed

    Dair, Roberto; Torres, Etelivar; Rodríguez, Odalys; Cruz, Ramona; Hernández, Lizzie

    2014-02-19

    Tuberculosis is currently a health problem in the municipality of Camagüey. To assess compliance of guidelines issued by the National Program for the Control of Tuberculosis for the follow-up of contacts of positive cases of pulmonary tuberculosis in the municipality of Camagüey, Cuba. Descriptive cross-sectional design. 1,242 contacts resulting from 39 reported cases of tuberculosis during the study period were included in the municipality of Camagüey between 2008 and 2011. Epidemiological surveys and records of reported cases were reviewed. The results were processed and analyzed in SPSS 17.0 statistical software and subsequently presented in tables and graphs. The results were summarized by percentages. The “follow-up form for contacts of pulmonary tuberculosis” was used as main guideline, which was created by experts of the Investigation and Monitoring of Tuberculosis, Acute Respiratory Infections, and Leprosy Workshop of Tropical Medicine Institute Pedro Kourí. Contacts that had an initial examination and four checkups had 96.2% of acceptability. Contacts that had fewer than four checkups showed less than 10% acceptability (3.3%). All contacts were assessed from the outset and were treated, in accordance with program guidelines. We found adequate compliance of National Program for the Control of the Tuberculosis guidelines for follow-up of contacts of positive cases of pulmonary tuberculosis. Compliance is greater in younger age groups and in the actively employed (25 to 54 years). This evaluation contributed to identify existing weaknesses in follow-up, such as low interest of this population to undergo appropriate testing in the National Program of Control of Tuberculosis.

  18. Educational Software Acquisition for Microcomputers.

    ERIC Educational Resources Information Center

    Erikson, Warren; Turban, Efraim

    1985-01-01

    Examination of issues involved in acquiring appropriate microcomputer software for higher education focuses on the following points: developing your own software; finding commercially available software; using published evaluations; pre-purchase testing; customizing and adapting commercial software; post-purchase testing; and software use. A…

  19. Advocacy Groups Deliver Guidelines for Schools Facing Sexual-Orientation Issues

    ERIC Educational Resources Information Center

    Curriculum Review, 2006

    2006-01-01

    Groups that often find themselves on opposing sides of the cultural war over gay rights have bridged their divide to draft consensus guidelines designed to help public schools address sexual-orientation issues with sensitivity and respect. Representatives from the Christian Educators Association International and the Gay, Lesbian and Straight…

  20. AIDS: Workplace Issues. INFO-LINE. Practical Guidelines for Training and Development Professionals. Issue 9208.

    ERIC Educational Resources Information Center

    American Society for Training and Development, Alexandria, VA.

    Practical guidelines are presented for training and development professionals dealing with acquired immune deficiency syndrome (AIDS) in the workplace. The following topics are covered: AIDS in the workplace; AIDS basics, including information on the required corporate commitment and transmission of human immunodeficiency virus (HIV); employment…

  1. How Safe Is Control Software

    NASA Technical Reports Server (NTRS)

    Dunn, William R.; Corliss, Lloyd D.

    1991-01-01

    Paper examines issue of software safety. Presents four case histories of software-safety analysis. Concludes that, to be safe, software, for all practical purposes, must be free of errors. Backup systems still needed to prevent catastrophic software failures.

  2. A view of software management issues

    NASA Technical Reports Server (NTRS)

    Manley, J. H.

    1985-01-01

    The Software Development Environment (SDE) Panel addressed key programmatic, scope, and structural issues raised by its members and the general audience regarding the proposed software development environment for the Space Station program. The general team approach taken by this group led to a consensus on 18 recommendations to NASA mangament regarding the acquisition and definition of the SDE. This approach was keyed by the initial issues presentation given to the general audience. Additional issues (for a total of 23) were developed by the panelists in their first closed session from which key areas were selected and discussed in open session. These discussions led to key recommendations which are summarized and described.

  3. Is There a European View on Health Economic Evaluations? Results from a Synopsis of Methodological Guidelines Used in the EUnetHTA Partner Countries.

    PubMed

    Heintz, Emelie; Gerber-Grote, Andreas; Ghabri, Salah; Hamers, Francoise F; Rupel, Valentina Prevolnik; Slabe-Erker, Renata; Davidson, Thomas

    2016-01-01

    The objectives of this study were to review current methodological guidelines for economic evaluations of all types of technologies in the 33 countries with organizations involved in the European Network for Health Technology Assessment (EUnetHTA), and to provide a general framework for economic evaluation at a European level. Methodological guidelines for health economic evaluations used by EUnetHTA partners were collected through a survey. Information from each guideline was extracted using a pre-tested extraction template. On the basis of the extracted information, a summary describing the methods used by the EUnetHTA countries was written for each methodological item. General recommendations were formulated for methodological issues where the guidelines of the EUnetHTA partners were in agreement or where the usefulness of economic evaluations may be increased by presenting the results in a specific way. At least one contact person from all 33 EUnetHTA countries (100 %) responded to the survey. In total, the review included 51 guidelines, representing 25 countries (eight countries had no methodological guideline for health economic evaluations). On the basis of the results of the extracted information from all 51 guidelines, EUnetHTA issued ten main recommendations for health economic evaluations. The presented review of methodological guidelines for health economic evaluations and the consequent recommendations will hopefully improve the comparability, transferability and overall usefulness of economic evaluations performed within EUnetHTA. Nevertheless, there are still methodological issues that need to be investigated further.

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

    ERIC Educational Resources Information Center

    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…

  5. 5 CFR 1310.1 - Policy guidelines.

    Code of Federal Regulations, 2010 CFR

    2010-01-01

    ... 5 Administrative Personnel 3 2010-01-01 2010-01-01 false Policy guidelines. 1310.1 Section 1310.1 Administrative Personnel OFFICE OF MANAGEMENT AND BUDGET OMB DIRECTIVES OMB CIRCULARS § 1310.1 Policy guidelines. In carrying out its responsibilities, the Office of Management and Budget issues policy guidelines to...

  6. Accounting guidelines for HMOs: issues and practices.

    PubMed

    Ingram, R W; Robbins, W A

    1987-03-01

    HMOs are fast becoming an important part of the healthcare industry today. Unfortunately, specific accounting guidelines have not yet been established for them. This concern has led the AICPA to describe and offer recommendations concerning preferred accounting techniques for HMOs. This article looks at the issues raised by the AICPA and how current HMO financial officers feel about the practices that are recommended. It is suggested that the organization, taxability, and other attributes of an HMO must be clearly understood before strict accounting guidelines are imposed.

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

    PubMed

    Daw, Zamira; Cleaveland, Rance; Vetter, Marcus

    2014-01-01

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

  8. Effective organizational solutions for implementation of DBMS software packages

    NASA Technical Reports Server (NTRS)

    Jones, D.

    1984-01-01

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

  9. Software Issues at the User Interface

    DTIC Science & Technology

    1991-05-01

    successful integration of parallel computers into mainstream scientific computing. Clearly a compiler is the most important software tool available to a...Computer Science University of Colorado Boulder, CO 80309 ABSTRACT We review software issues that are critical to the successful integration of parallel...The development of an optimizing compiler of this quality, addressing communicaton instructions as well as computational instructions is a major

  10. NASA's Software Safety Standard

    NASA Technical Reports Server (NTRS)

    Ramsay, Christopher M.

    2007-01-01

    NASA relies more and more on software to control, monitor, and verify its safety critical systems, facilities and operations. Since the 1960's there has hardly been a spacecraft launched that does not have a computer on board that will provide command and control services. There have been recent incidents where software has played a role in high-profile mission failures and hazardous incidents. For example, the Mars Orbiter, Mars Polar Lander, the DART (Demonstration of Autonomous Rendezvous Technology), and MER (Mars Exploration Rover) Spirit anomalies were all caused or contributed to by software. The Mission Control Centers for the Shuttle, ISS, and unmanned programs are highly dependant on software for data displays, analysis, and mission planning. Despite this growing dependence on software control and monitoring, there has been little to no consistent application of software safety practices and methodology to NASA's projects with safety critical software. Meanwhile, academia and private industry have been stepping forward with procedures and standards for safety critical systems and software, for example Dr. Nancy Leveson's book Safeware: System Safety and Computers. The NASA Software Safety Standard, originally published in 1997, was widely ignored due to its complexity and poor organization. It also focused on concepts rather than definite procedural requirements organized around a software project lifecycle. Led by NASA Headquarters Office of Safety and Mission Assurance, the NASA Software Safety Standard has recently undergone a significant update. This new standard provides the procedures and guidelines for evaluating a project for safety criticality and then lays out the minimum project lifecycle requirements to assure the software is created, operated, and maintained in the safest possible manner. This update of the standard clearly delineates the minimum set of software safety requirements for a project without detailing the implementation for those requirements. This allows the projects leeway to meet these requirements in many forms that best suit a particular project's needs and safety risk. In other words, it tells the project what to do, not how to do it. This update also incorporated advances in the state of the practice of software safety from academia and private industry. It addresses some of the more common issues now facing software developers in the NASA environment such as the use of Commercial-Off-the-Shelf Software (COTS), Modified OTS (MOTS), Government OTS (GOTS), and reused software. A team from across NASA developed the update and it has had both NASA-wide internal reviews by software engineering, quality, safety, and project management. It has also had expert external review. This presentation and paper will discuss the new NASA Software Safety Standard, its organization, and key features. It will start with a brief discussion of some NASA mission failures and incidents that had software as one of their root causes. It will then give a brief overview of the NASA Software Safety Process. This will include an overview of the key personnel responsibilities and functions that must be performed for safety-critical software.

  11. Visualization of International Solar-Terrestrial Physics Program (ISTP) data

    NASA Technical Reports Server (NTRS)

    Kessel, Ramona L.; Candey, Robert M.; Hsieh, Syau-Yun W.; Kayser, Susan

    1995-01-01

    The International Solar-Terrestrial Physics Program (ISTP) is a multispacecraft, multinational program whose objective is to promote further understanding of the Earth's complex plasma environment. Extensive data sharing and data analysis will be needed to ensure the success of the overall ISTP program. For this reason, there has been a special emphasis on data standards throughout ISTP. One of the key tools will be the common data format (CDF), developed, maintained, and evolved at the National Space Science Data Center (NSSDC), with the set of ISTP implementation guidelines specially designed for space physics data sets by the Space Physics Data Facility (associated with the NSSDC). The ISTP guidelines were developed to facilitate searching, plotting, merging, and subsetting of data sets. We focus here on the plotting application. A prototype software package was developed to plot key parameter (KP) data from the ISTP program at the Science Planning and Operations Facility (SPOF). The ISTP Key Parameter Visualization Tool is based on the Interactive Data Language (IDL) and is keyed to the ISTP guidelines, reading data stored in CDF. With the combination of CDF, the ISTP guidelines, and the visualization software, we can look forward to easier and more effective data sharing and use among ISTP scientists.

  12. International Guidelines on Computer-Based and Internet-Delivered Testing

    ERIC Educational Resources Information Center

    International Journal of Testing, 2006

    2006-01-01

    Developed by the International Test Commission, the International Guidelines on Computer-Based and Internet-Delivered Testing are a set of guidelines specifically developed to highlight good practice issues in relation to computer/Internet tests and testing. These guidelines have been developed from an international perspective and are directed at…

  13. 76 FR 16724 - Child Nutrition Programs-Income Eligibility Guidelines

    Federal Register 2010, 2011, 2012, 2013, 2014

    2011-03-25

    ... for Children (7 CFR part 215). These eligibility guidelines are based on the Federal income poverty... price meals were obtained by multiplying the year 2011 Federal income poverty guidelines by 1.30 and 1... only the annual Federal poverty guidelines issued by the Department of Health and Human Services...

  14. Issues Related to Equipment and the Dietary Guidelines for Americans.

    ERIC Educational Resources Information Center

    Nettles, Mary Frances

    A multi-year project was initiated to examine production equipment issues related to implementation of the Dietary Guidelines for Americans (DGA). The purposes of the research project were to determine foodservice directors' opinions regarding use and appropriateness of equipment in school foodservice, to identify the number and variety of menu…

  15. Understanding Gender Equity in the Workplace.

    ERIC Educational Resources Information Center

    Nunnelley State Technical Coll., Childersburg, AL.

    This document discusses issues of gender equity in the workplace which are pertinent to the high school counselor. The first chapter provides guidelines for helping students to understand gender equity issues. These guidelines include asking the students if they would have the same career goals if they were of the other sex and challenging the…

  16. 76 FR 4550 - Income Level for Individuals Eligible for Assistance

    Federal Register 2010, 2011, 2012, 2013, 2014

    2011-01-26

    ... Poverty Guidelines as issued by the Department of Health and Human Services. DATES: Effective Date: This... maximum income level equivalent to one hundred and twenty-five percent (125%) of the Federal Poverty... issuing the Federal Poverty Guidelines. The figures for 2010 set out below are equivalent to 125% of the...

  17. SCIENTIFIC AUTHORSHIP, PART I: A WINDOW INOT SCIENTIFIC FRAUD SCIENTIFIC AUTHORSHIP, PART II: HISTORY, REOCCURRING ISSUES, PRACTICES, AND GUIDELINES (SEE COMMENTS)

    EPA Science Inventory

    Scientific Authorship: History, Reoccurring Issues, Practices, and Guidelines
    Introduction
    Often, the most challenging aspect of being a scientist is dealing with the intricacies of publishing one's research and knowledge. One must do much more than just accurately record...

  18. Programming support environment issues in the Byron programming environment

    NASA Technical Reports Server (NTRS)

    Larsen, Matthew J.

    1986-01-01

    Issues are discussed which programming support environments need to address in order to successfully support software engineering. These concerns are divided into two categories. The first category, issues of how software development is supported by an environment, includes support of the full life cycle, methodology flexibility, and support of software reusability. The second category contains issues of how environments should operate, such as tool reusability and integration, user friendliness, networking, and use of a central data base. This discussion is followed by an examination of Byron, an Ada based programming support environment developed at Intermetrics, focusing on the solutions Byron offers to these problems, including the support provided for software reusability and the test and maintenance phases of the life cycle. The use of Byron in project development is described briefly, and some suggestions for future Byron tools and user written tools are presented.

  19. 76 FR 67725 - Technical Conference on Penalty Guidelines; Second Notice of Technical Conference on Penalty...

    Federal Register 2010, 2011, 2012, 2013, 2014

    2011-11-02

    ... Conference on Penalty Guidelines; Second Notice of Technical Conference on Penalty Guidelines On September 21... Conference on Penalty Guidelines to be held on November 17, 2011. The conference will be held from 1 p.m. to... impact of the Penalty Guidelines, which the Commission issued on September 17, 2010,\\1\\ on compliance and...

  20. Study on Spacelab software development and integration concepts

    NASA Technical Reports Server (NTRS)

    1974-01-01

    A study was conducted to define the complexity and magnitude of the Spacelab software challenge. The study was based on current Spacelab program concepts, anticipated flight schedules, and ground operation plans. The study was primarily directed toward identifying and solving problems related to the experiment flight application and tests and checkout software executing in the Spacelab onboard command and data management subsystem (CDMS) computers and electrical ground support equipment (EGSE). The study provides a conceptual base from which it is possible to proceed into the development phase of the Software Test and Integration Laboratory (STIL) and establishes guidelines for the definition of standards which will ensure that the total Spacelab software is understood prior to entering development.

  1. The full spectrum of ethical issues in dementia care: systematic qualitative review.

    PubMed

    Strech, Daniel; Mertz, Marcel; Knüppel, Hannes; Neitzke, Gerald; Schmidhuber, Martina

    2013-06-01

    Integrating ethical issues in dementia-specific training material, clinical guidelines and national strategy plans requires an unbiased awareness of all the relevant ethical issues. To determine systematically and transparently the full spectrum of ethical issues in clinical dementia care. We conducted a systematic review in Medline (restricted to English and German literature published between 2000 and 2011) and Google books (with no restrictions). We applied qualitative text analysis and normative analysis to categorise the spectrum of ethical issues in clinical dementia care. The literature review retrieved 92 references that together mentioned a spectrum of 56 ethical issues in clinical dementia care. The spectrum was structured into seven major categories that consist of first- and second-order categories for ethical issues. The systematically derived spectrum of ethical issues in clinical dementia care presented in this paper can be used as training material for healthcare professionals, students and the public for raising awareness and understanding of the complexity of ethical issues in dementia care. It can also be used to identify ethical issues that should be addressed in dementia-specific training programmes, national strategy plans and clinical practice guidelines. Further research should evaluate whether this new genre of systematic reviews can be applied to the identification of ethical issues in other cognitive and somatic diseases. Also, the practical challenges in addressing ethical issues in training material, guidelines and policies need to be evaluated.

  2. Modeling a Nursing Guideline with Standard Terminology and Unified Modeling Language for a Nursing Decision Support System: A Case Study.

    PubMed

    Choi, Jeeyae; Jansen, Kay; Coenen, Amy

    In recent years, Decision Support Systems (DSSs) have been developed and used to achieve "meaningful use". One approach to developing DSSs is to translate clinical guidelines into a computer-interpretable format. However, there is no specific guideline modeling approach to translate nursing guidelines to computer-interpretable guidelines. This results in limited use of DSSs in nursing. Unified modeling language (UML) is a software writing language known to accurately represent the end-users' perspective, due to its expressive characteristics. Furthermore, standard terminology enabled DSSs have been shown to smoothly integrate into existing health information systems. In order to facilitate development of nursing DSSs, the UML was used to represent a guideline for medication management for older adults encode with the International Classification for Nursing Practice (ICNP®). The UML was found to be a useful and sufficient tool to model a nursing guideline for a DSS.

  3. Modeling a Nursing Guideline with Standard Terminology and Unified Modeling Language for a Nursing Decision Support System: A Case Study

    PubMed Central

    Choi, Jeeyae; Jansen, Kay; Coenen, Amy

    2015-01-01

    In recent years, Decision Support Systems (DSSs) have been developed and used to achieve “meaningful use”. One approach to developing DSSs is to translate clinical guidelines into a computer-interpretable format. However, there is no specific guideline modeling approach to translate nursing guidelines to computer-interpretable guidelines. This results in limited use of DSSs in nursing. Unified modeling language (UML) is a software writing language known to accurately represent the end-users’ perspective, due to its expressive characteristics. Furthermore, standard terminology enabled DSSs have been shown to smoothly integrate into existing health information systems. In order to facilitate development of nursing DSSs, the UML was used to represent a guideline for medication management for older adults encode with the International Classification for Nursing Practice (ICNP®). The UML was found to be a useful and sufficient tool to model a nursing guideline for a DSS. PMID:26958174

  4. GEM at 10: a decade's experience with the Guideline Elements Model.

    PubMed

    Hajizadeh, Negin; Kashyap, Nitu; Michel, George; Shiffman, Richard N

    2011-01-01

    The Guideline Elements Model (GEM) was developed in 2000 to organize the information contained in clinical practice guidelines using XML and to represent guideline content in a form that can be understood by human readers and processed by computers. In this work, we systematically reviewed the literature to better understand how GEM was being used, potential barriers to its use, and suggestions for improvement. Fifty external and twelve internally produced publications were identified and analyzed. GEM was used most commonly for modeling and ontology creation. Other investigators applied GEM for knowledge extraction and data mining, for clinical decision support for guideline generation. The GEM Cutter software-used to markup guidelines for translation into XML- has been downloaded 563 times since 2000. Although many investigators found GEM to be valuable, others critiqued its failure to clarify guideline semantics, difficulties in markup, and the fact that GEM files are not usually executable.

  5. Dietary Guidelines for the Asia Pacific Region.

    PubMed

    Binns, Colin W; Lee, Mi Kyung; Kagawa, Masaharu; Low, Wah Yun; Liqian, Qiu; Guldan, Georgia S; Hokama, Tomiko; Nanishi, Keiko; Oy, Sreymom; Tang, Li; Zerfas, Alfred

    2017-03-01

    Nutrition is a major determinant of health throughout all stages of life and together with smoking is the most important risk factor for morbidity and mortality in the Asia Pacific Region. The workshop participants examined Dietary Guidelines and Food Guides that are in use in our region, together with additional materials from the World Health Organization, UNICEF and the World Cancer Research Foundation. The resulting set of guidelines is meant as a reminder of the main issues to be covered in a general public health education program. It may also be of value in reminding public health practitioners, educators, administrators, and policy makers of current nutrition issues. It may additionally be useful as a checklist of the issues to be considered in public health programs and regulations. The main areas of nutrition that are included in the Guidelines are eating a variety of foods, including vegetables, fruits, whole grain cereals, and nuts. Choose fish, poultry, and meats grown in a sustainable way. Appropriate growth, including avoiding obesity, and physical activity are important. Breastfeeding is the basis of infant nutrition and nutrition of mothers is an important public health measure. Negative factors in the Asian diet include salt, refined sugar, alcohol and fats. The APACPH Dietary Guidelines will need to be kept under review and modified to meet regional differences in food supply. The Guidelines will be useful as a checklist of the issues to be considered in public health programs, addressing both acute and chronic diseases.

  6. The management of scabies outbreaks in residential care facilities for the elderly in England: a review of current health protection guidelines.

    PubMed

    White, L C J; Lanza, S; Middleton, J; Hewitt, K; Freire-Moran, L; Edge, C; Nicholls, M; Rajan-Iyer, J; Cassell, J A

    2016-11-01

    Commonly thought of as a disease of poverty and overcrowding in resource-poor settings globally, scabies is also an important public health issue in residential care facilities for the elderly (RCFE) in high-income countries such as the UK. We compared and contrasted current local Health Protection Team (HPT) guidelines for the management of scabies outbreaks in RCFE throughout England. We performed content analysis on 20 guidelines, and used this to create a quantitative report of their variation in key dimensions. Although the guidelines were generally consistent on issues such as the treatment protocols for individual patients, there was substantial variation in their recommendations regarding the prophylactic treatment of contacts, infection control measures and the roles and responsibilities of individual stakeholders. Most guidelines did not adequately address the logistical challenges associated with mass treatment in this setting. We conclude that the heterogeneous nature of the guidelines reviewed is an argument in favour of national guidelines being produced.

  7. Space Telecommunications Radio System (STRS) Compliance Testing

    NASA Technical Reports Server (NTRS)

    Handler, Louis M.

    2011-01-01

    The Space Telecommunications Radio System (STRS) defines an open architecture for software defined radios. This document describes the testing methodology to aid in determining the degree of compliance to the STRS architecture. Non-compliances are reported to the software and hardware developers as well as the NASA project manager so that any non-compliances may be fixed or waivers issued. Since the software developers may be divided into those that provide the operating environment including the operating system and STRS infrastructure (OE) and those that supply the waveform applications, the tests are divided accordingly. The static tests are also divided by the availability of an automated tool that determines whether the source code and configuration files contain the appropriate items. Thus, there are six separate step-by-step test procedures described as well as the corresponding requirements that they test. The six types of STRS compliance tests are: STRS application automated testing, STRS infrastructure automated testing, STRS infrastructure testing by compiling WFCCN with the infrastructure, STRS configuration file testing, STRS application manual code testing, and STRS infrastructure manual code testing. Examples of the input and output of the scripts are shown in the appendices as well as more specific information about what to configure and test in WFCCN for non-compliance. In addition, each STRS requirement is listed and the type of testing briefly described. Attached is also a set of guidelines on what to look for in addition to the requirements to aid in the document review process.

  8. Forge.mil

    Science.gov Websites

    Forge.mil Home About FAQs News Resources Support Top 10 FAQs What is the Forge.mil Program? What is SoftwareForge? What is ProjectForge? Is there a Forge.mil site on SIPRNET? What is the difference between SoftwareForge and ProjectForge? What capabilities are available in the system? What are the guidelines for

  9. Key Issues in Instructional Computer Graphics.

    ERIC Educational Resources Information Center

    Wozny, Michael J.

    1981-01-01

    Addresses key issues facing universities which plan to establish instructional computer graphics facilities, including computer-aided design/computer aided manufacturing systems, role in curriculum, hardware, software, writing instructional software, faculty involvement, operations, and research. Thirty-seven references and two appendices are…

  10. Lightning forecasting studies using LDAR, LLP, field mill, surface mesonet, and Doppler radar data

    NASA Technical Reports Server (NTRS)

    Forbes, Gregory S.; Hoffert, Steven G.

    1995-01-01

    The ultimate goal of this research is to develop rules, algorithms, display software, and training materials that can be used by the operational forecasters who issue weather advisories for daily ground operations and launches by NASA and the United States Air Force to improve real-time forecasts of lightning. Doppler radar, Lightning Detection and Ranging (LDAR), Lightning Location and Protection (LLP), field mill (Launch Pad Lightning Warning System -- LPLWS), wind tower (surface mesonet) and additional data sets have been utilized in 10 case studies of thunderstorms in the vicinity of KSC during the summers of 1994 and 1995. These case studies reveal many intriguing aspects of cloud-to-ground, cloud-to-cloud, in-cloud, and cloud-to-air lightning discharges in relation to radar thunderstorm structure and evolution. They also enable the formulation of some preliminary working rules of potential use in the forecasting of initial and final ground strike threat. In addition, LDAR and LLP data sets from 1993 have been used to quantify the lightning threat relative to the center and edges of LDAR discharge patterns. Software has been written to overlay and display the various data sets as color imagery. However, human intervention is required to configure the data sets for proper intercomparison. Future efforts will involve additional software development to automate the data set intercomparisons, to display multiple overlay combinations in a windows format, and to allow for animation of the imagery. The software package will then be used as a tool to examine more fully the current cases and to explore additional cases in a timely manner. This will enable the formulation of more general and reliable forecasting guidelines and rules.

  11. Field Programmable Gate Array Failure Rate Estimation Guidelines for Launch Vehicle Fault Tree Models

    NASA Technical Reports Server (NTRS)

    Al Hassan, Mohammad; Novack, Steven D.; Hatfield, Glen S.; Britton, Paul

    2017-01-01

    Today's launch vehicles complex electronic and avionic systems heavily utilize the Field Programmable Gate Array (FPGA) integrated circuit (IC). FPGAs are prevalent ICs in communication protocols such as MIL-STD-1553B, and in control signal commands such as in solenoid/servo valves actuations. This paper will demonstrate guidelines to estimate FPGA failure rates for a launch vehicle, the guidelines will account for hardware, firmware, and radiation induced failures. The hardware contribution of the approach accounts for physical failures of the IC, FPGA memory and clock. The firmware portion will provide guidelines on the high level FPGA programming language and ways to account for software/code reliability growth. The radiation portion will provide guidelines on environment susceptibility as well as guidelines on tailoring other launch vehicle programs historical data to a specific launch vehicle.

  12. Software tool for physics chart checks.

    PubMed

    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.

  13. Proposed Guidelines for Operating Counselor Education and Supervision Training Clinics

    ERIC Educational Resources Information Center

    Lauka, Justin D.; McCarthy, Amanda K.

    2013-01-01

    The purpose of this article is to justify and present a set of guidelines for the effective and ethical administration of counselor education and supervision training clinics. Responding directly to a call for creating guidelines, the authors address core issues surrounding their development. Benefits for clear and accessible guidelines and risks…

  14. Development of a Prototype Automation Simulation Scenario Generator for Air Traffic Management Software Simulations

    NASA Technical Reports Server (NTRS)

    Khambatta, Cyrus F.

    2007-01-01

    A technique for automated development of scenarios for use in the Multi-Center Traffic Management Advisor (McTMA) software simulations is described. The resulting software is designed and implemented to automate the generation of simulation scenarios with the intent of reducing the time it currently takes using an observational approach. The software program is effective in achieving this goal. The scenarios created for use in the McTMA simulations are based on data taken from data files from the McTMA system, and were manually edited before incorporation into the simulations to ensure accuracy. Despite the software s overall favorable performance, several key software issues are identified. Proposed solutions to these issues are discussed. Future enhancements to the scenario generator software may address the limitations identified in this paper.

  15. Piaget and Microcomputer Learning Environments.

    ERIC Educational Resources Information Center

    Hofmann, Rich

    1986-01-01

    Four studies are offered from a Piagetian perspective on providing children with an optimal microcomputer environment. Guidelines stress the importance of flexibility, and a hierarchical software environment. (CL)

  16. University Approaches to Software Copyright and Licensure Policies.

    ERIC Educational Resources Information Center

    Hawkins, Brian L.

    Issues of copyright policy and software licensure at Drexel University that were developed during the introduction of a new microcomputing program are discussed. Channels for software distribution include: individual purchase of externally-produced software, distribution of internally-developed software, institutional licensure, and "read…

  17. If you drink alcoholic beverages do so in moderation: what does this mean?

    PubMed

    Dufour, M C

    2001-02-01

    The changes in content of the alcohol guideline of the various editions of the Dietary Guidelines for Americans from 1980 to 2000 are discussed. This is followed by a capsule summary of the history and evolution of the discipline of alcohol epidemiology compared with that of nutrition epidemiology. Methods of assessment are discussed, and issues surrounding the validity and reliability of self-report of alcohol consumption are then outlined. Relevant objectives from Healthy People 2010 are discussed. Surveillance of the alcohol guideline discloses that, at present, very few American drinkers follow the recommendations of the alcohol guideline. Indications for future research needs to address this issue conclude the discussion.

  18. Autonomy Software: V&V Challenges and Characteristics

    NASA Technical Reports Server (NTRS)

    Schumann, Johann; Visser, Willem

    2006-01-01

    The successful operation of unmanned air vehicles requires software with a high degree of autonomy. Only if high level functions can be carried out without human control and intervention, complex missions in a changing and potentially unknown environment can be carried out successfully. Autonomy software is highly mission and safety critical: failures, caused by flaws in the software cannot only jeopardize the mission, but could also endanger human life (e.g., a crash of an UAV in a densely populated area). Due to its large size, high complexity, and use of specialized algorithms (planner, constraint-solver, etc.), autonomy software poses specific challenges for its verification, validation, and certification. -- - we have carried out a survey among researchers aid scientists at NASA to study these issues. In this paper, we will present major results of this study, discussing the broad spectrum. of notions and characteristics of autonomy software and its challenges for design and development. A main focus of this survey was to evaluate verification and validation (V&V) issues and challenges, compared to the development of "traditional" safety-critical software. We will discuss important issues in V&V of autonomous software and advanced V&V tools which can help to mitigate software risks. Results of this survey will help to identify and understand safety concerns in autonomy software and will lead to improved strategies for mitigation of these risks.

  19. Energy Emergency Management Information System (EEMIS): Functional requirements

    NASA Astrophysics Data System (ADS)

    1980-10-01

    These guidelines state that in order to create the widest practicable competition, the system's requirements, with few exceptions, must be expressed in functional terms without reference to specific hardware or software products, and that wherever exceptions are made a statement of justification must be provided. In addition, these guidelines set forth a recommended maximum threshold limit of annual contract value for schedule contract procurements.

  20. Developing Computer Use in Education: Guidelines, Trends and Issues.

    ERIC Educational Resources Information Center

    Anderson, Jonathan; And Others

    Designed to provide educational policy-makers and decision-makers with a basis for the development of guidelines for the development of education programs, this report presents an overview of trends and issues in computer education within the countries of the Asia and Pacific region. The impact of computers on society is described, as well as the…

  1. Into the Wild Country: Epistemic Issues in Professional Guidelines for Palliative Sedation in End-of-Life Care

    ERIC Educational Resources Information Center

    Wackers, Ger

    2015-01-01

    End-of-life care is an important object of governance. Using the linguistic notions of polysemy, metaphorical blending and counterfactual reasoning, this paper critically examines epistemic issues in professional guidelines for palliative sedation of the dying. As a last resort option, palliative sedation is described as the intentional,…

  2. Taking Ownership of the ITC's Guidelines for Computer-Based and Internet-Delivered Testing: A South African Application

    ERIC Educational Resources Information Center

    Foxcroft, Cheryl D.; Davies, Caroline

    2006-01-01

    The increased use of computer-based and Internet-delivered testing has raised a number of ethical and legal issues. The International Test Commission's (this issue) Guidelines for Computer-Based and Internet-Delivered Testing represent the most recent attempt to provide test users, publishers, and developers with guidance regarding the appropriate…

  3. Technology transfer in software engineering

    NASA Technical Reports Server (NTRS)

    Bishop, Peter C.

    1989-01-01

    The University of Houston-Clear Lake is the prime contractor for the AdaNET Research Project under the direction of NASA Johnson Space Center. AdaNET was established to promote the principles of software engineering to the software development industry. AdaNET will contain not only environments and tools, but also concepts, principles, models, standards, guidelines and practices. Initially, AdaNET will serve clients from the U.S. government and private industry who are working in software development. It will seek new clients from those who have not yet adopted the principles and practices of software engineering. Some of the goals of AdaNET are to become known as an objective, authoritative source of new software engineering information and parts, to provide easy access to information and parts, and to keep abreast of innovations in the field.

  4. Monitoring ethical, legal, and social issues in developing population genetic databases.

    PubMed

    Austin, Melissa A; Harding, Sarah E; McElroy, Courtney E

    2003-01-01

    To characterize ethical, legal, and social issues unique to population genetic database research and to determine the relevance of international recommendations and guidelines for addressing these issues in the development of "genebank" projects globally. Building on our previous description of eight international genebanks, we conducted a comprehensive electronic search and literature review of relevant publications and consulted national and international documents applicable to genebank research. We identified and characterized five categories of ethical, legal, and social issues unique to genebank development: sponsorship and benefit-sharing, neutrality and regulatory power of ethics committees, public engagement, consent, and data protection. We illustrate these issues with examples from specific genebanks. Not all of the issues are addressed in current international guidelines, many of which are nonspecific and unenforceable. The trend of genebank development promises to provide new discoveries to the field of medical science and to greatly improve public health. However, there is a growing need for more explicit, enforceable, and coordinated international guidelines relevant to the development and implementation of genebanks. By comparing ethical, legal and social issues as they arise in genebanks, researchers can better evaluate how to best use these projects to improve public health while protecting participating populations.

  5. Fact Sheet: EPA's Guidelines for Carcinogen Risk Assessment

    EPA Science Inventory

    March 29, 2005

    FACT SHEET: EPA's GUIDELINES FOR CARCINOGEN RISK ASSESSMENT

    On March 29, 2005, EPA issued the Guidelines for Carcinogen Risk A...

  6. Spatial variability and long-term analysis of groundwater quality of Faisalabad industrial zone

    NASA Astrophysics Data System (ADS)

    Nasir, Muhammad Salman; Nasir, Abdul; Rashid, Haroon; Shah, Syed Hamid Hussain

    2017-10-01

    Water is the basic necessity of life and is essential for healthy society. In this study, groundwater quality analysis was carried out for the industrial zone of Faisalabad city. Sixty samples of groundwater were collected from the study area. The quality maps of deliberately analyzed results were prepared in GIS. The collected samples were analyzed for chemical parameters and heavy metals, such as total hardness, alkalinity, cadmium, arsenic, nickel, lead, and fluoride, and then, the results were compared with the WHO guidelines. The values of these results were represented by a mapping of quality parameters using the ArcView GIS v9.3, and IDW was used for raster interpolation. The long-term analysis of these parameters has been carried out using the `R Statistical' software. It was concluded that water is partially not fit for drinking, and direct use of this groundwater may cause health issues.

  7. Activities of the healthcare team for women who smoke during pregnancy and the puerperium1

    PubMed Central

    Teixeira, Carolina de Castilhos; Lucena, Amália de Fátima; Echer, Isabel Cristina

    2014-01-01

    OBJECTIVE: to identify activities developed by the healthcare team for pregnant and postpartum women who smoke. METHOD: cross-sectional study with a sample of 135 healthcare team members who assist pregnant and postpartum women in a university hospital located in southern Brazil. The data was collected using questionnaires and analyzed using the Statistical Package for Social Sciences software. RESULTS: 76 (56.3%) staff members reported that they always addressed smoking cessation; however, the approach occurred in only two periods of the hospitalization and/or prenatal consultations, not including family members. In regard to the effectiveness of their actions, the health team assessed it as fair or poor, and mentioned the need for updating knowledge regarding this issue. CONCLUSIONS: the health team did not perform the approach as recommended by the tobacco control guidelines, requiring training to offer a qualified and efficient intervention. PMID:25296146

  8. Recommendations resulting from the SPDS Community-Wide Workshop

    NASA Technical Reports Server (NTRS)

    1993-01-01

    The Data Systems Panel identified three critical functionalities of a Space Physics Data System (SPDS): the delivery of self-documenting data, the existence of a matrix of translators between various standard formats (IDFS, CDF, netCDF, HDF, TENNIS, UCLA flat file, and FITS), and a network-based capability for browsing and examining inventory records for the system's data holdings. The recommendations resulting from the workshop include the philosophy, funding, and objectives of a SPDS. Access to quality data is seen as the most important objective by the Policy Panel, with curation and information about the data being integral parts of any accessible data set. The Data Issues Panel concluded that the SPDS can supply encouragement, guidelines, and ultimately provide a mechanism for financial support for data archiving, restoration, and curation. The Software Panel of the SPDS focused on defining the requirements and priorities for SPDS to support common data analysis and data visualization tools and packages.

  9. DOE Office of Scientific and Technical Information (OSTI.GOV)

    Rivard, M.

    With the recent introduction of heterogeneity correction algorithms for brachytherapy, the AAPM community is still unclear on how to commission and implement these into clinical practice. The recently-published AAPM TG-186 report discusses important issues for clinical implementation of these algorithms. A charge of the AAPM-ESTRO-ABG Working Group on MBDCA in Brachytherapy (WGMBDCA) is the development of a set of well-defined test case plans, available as references in the software commissioning process to be performed by clinical end-users. In this practical medical physics course, specific examples on how to perform the commissioning process are presented, as well as descriptions of themore » clinical impact from recent literature reporting comparisons of TG-43 and heterogeneity-based dosimetry. Learning Objectives: Identify key clinical applications needing advanced dose calculation in brachytherapy. Review TG-186 and WGMBDCA guidelines, commission process, and dosimetry benchmarks. Evaluate clinical cases using commercially available systems and compare to TG-43 dosimetry.« less

  10. DOE's Computer Incident Advisory Capability (CIAC)

    DOE Office of Scientific and Technical Information (OSTI.GOV)

    Schultz, E.

    1990-09-01

    Computer security is essential in maintaining quality in the computing environment. Computer security incidents, however, are becoming more sophisticated. The DOE Computer Incident Advisory Capability (CIAC) team was formed primarily to assist DOE sites in responding to computer security incidents. Among CIAC's other responsibilities are gathering and distributing information to DOE sites, providing training workshops, coordinating with other agencies, response teams, and vendors, creating guidelines for incident handling, and developing software tools. CIAC has already provided considerable assistance to DOE sites faced with virus infections and worm and hacker attacks, has issued over 40 information bulletins, and has developed andmore » presented a workshop on incident handling. CIAC's experience in helping sites has produced several lessons learned, including the need to follow effective procedures to avoid virus infections in small systems and the need for sound password management and system administration in networked systems. CIAC's activity and scope will expand in the future. 4 refs.« less

  11. Quality control and conduct of genome-wide association meta-analyses.

    PubMed

    Winkler, Thomas W; Day, Felix R; Croteau-Chonka, Damien C; Wood, Andrew R; Locke, Adam E; Mägi, Reedik; Ferreira, Teresa; Fall, Tove; Graff, Mariaelisa; Justice, Anne E; Luan, Jian'an; Gustafsson, Stefan; Randall, Joshua C; Vedantam, Sailaja; Workalemahu, Tsegaselassie; Kilpeläinen, Tuomas O; Scherag, André; Esko, Tonu; Kutalik, Zoltán; Heid, Iris M; Loos, Ruth J F

    2014-05-01

    Rigorous organization and quality control (QC) are necessary to facilitate successful genome-wide association meta-analyses (GWAMAs) of statistics aggregated across multiple genome-wide association studies. This protocol provides guidelines for (i) organizational aspects of GWAMAs, and for (ii) QC at the study file level, the meta-level across studies and the meta-analysis output level. Real-world examples highlight issues experienced and solutions developed by the GIANT Consortium that has conducted meta-analyses including data from 125 studies comprising more than 330,000 individuals. We provide a general protocol for conducting GWAMAs and carrying out QC to minimize errors and to guarantee maximum use of the data. We also include details for the use of a powerful and flexible software package called EasyQC. Precise timings will be greatly influenced by consortium size. For consortia of comparable size to the GIANT Consortium, this protocol takes a minimum of about 10 months to complete.

  12. C3 System Performance Simulation and User Manual. Getting Started: Guidelines for Users

    NASA Technical Reports Server (NTRS)

    2006-01-01

    This document is a User's Manual describing the C3 Simulation capabilities. The subject work was designed to simulate the communications involved in the flight of a Remotely Operated Aircraft (ROA) using the Opnet software. Opnet provides a comprehensive development environment supporting the modeling of communication networks and distributed systems. It has tools for model design, simulation, data collection, and data analysis. Opnet models are hierarchical -- consisting of a project which contains node models which in turn contain process models. Nodes can be fixed, mobile, or satellite. Links between nodes can be physical or wireless. Communications are packet based. The model is very generic in its current form. Attributes such as frequency and bandwidth can easily be modified to better reflect a specific platform. The model is not fully developed at this stage -- there are still more enhancements to be added. Current issues are documented throughout this guide.

  13. Quality control and conduct of genome-wide association meta-analyses

    PubMed Central

    Winkler, Thomas W; Day, Felix R; Croteau-Chonka, Damien C; Wood, Andrew R; Locke, Adam E; Mägi, Reedik; Ferreira, Teresa; Fall, Tove; Graff, Mariaelisa; Justice, Anne E; Luan, Jian'an; Gustafsson, Stefan; Randall, Joshua C; Vedantam, Sailaja; Workalemahu, Tsegaselassie; Kilpeläinen, Tuomas O; Scherag, André; Esko, Tonu; Kutalik, Zoltán; Heid, Iris M; Loos, Ruth JF

    2014-01-01

    Rigorous organization and quality control (QC) are necessary to facilitate successful genome-wide association meta-analyses (GWAMAs) of statistics aggregated across multiple genome-wide association studies. This protocol provides guidelines for [1] organizational aspects of GWAMAs, and for [2] QC at the study file level, the meta-level across studies, and the meta-analysis output level. Real–world examples highlight issues experienced and solutions developed by the GIANT Consortium that has conducted meta-analyses including data from 125 studies comprising more than 330,000 individuals. We provide a general protocol for conducting GWAMAs and carrying out QC to minimize errors and to guarantee maximum use of the data. We also include details for use of a powerful and flexible software package called EasyQC. For consortia of comparable size to the GIANT consortium, the present protocol takes a minimum of about 10 months to complete. PMID:24762786

  14. Synergi and E&P forum HSE management system helps companies improve HSE performance and reduce losses

    DOE Office of Scientific and Technical Information (OSTI.GOV)

    Grundt, H.J.

    1996-12-31

    This paper discusses the use of information on accidents and near-misses to improve HSE performance and reduce losses in Exploration and Production activities. Incidents are considered a result of management system failure. To avoid incidents and recurrence of incidents, companies should adopt an integrated HSE Management System and software especially designed for recording, analyzing and following up events. The E&P Forum has issued guidelines to support current company HSE Management systems and practices. Concurrently, the Synergi Project has been established to facilitate experience transfer and effective handling of incidents as part of an integrated HSE Management System. The paper describesmore » how important it is to learn from past mistakes, to have a management system which facilitates the implementation of the required corrective action, and that tools for improved loss control are available.« less

  15. NSPWG-recommended safety requirements and guidelines for SEI nuclear propulsion

    NASA Technical Reports Server (NTRS)

    Marshall, Albert C.; Sawyer, J. C., Jr.; Bari, Robert A.; Brown, Neil W.; Cullingford, Hatice S.; Hardy, Alva C.; Lee, James H.; Mcculloch, William H.; Niederauer, George F.; Remp, Kerry

    1992-01-01

    An interagency Nuclear Safety Policy Working Group (NSPWG) was chartered to recommend nuclear safety policy, requirements, and guidelines for the Space Exploration Initiative (SEI) nuclear propulsion program to facilitate the implementation of mission planning and conceptual design studies. The NSPWG developed a top-level policy to provide the guiding principles for the development and implementation of the nuclear propulsion safety program and the development of safety functional requirements. In addition, the NSPWG reviewed safety issues for nuclear propulsion and recommended top-level safety requirements and guidelines to address these issues. Safety requirements were developed for reactor start-up, inadvertent criticality, radiological release and exposure, disposal, entry, and safeguards. Guidelines were recommended for risk/reliability, operational safety, flight trajectory and mission abort, space debris and meteoroids, and ground test safety. In this paper the specific requirements and guidelines will be discussed.

  16. Perspective: Challenges and Controversial Issues in the Dietary Guidelines for Americans, 1980-2015.

    PubMed

    Nestle, Marion

    2018-03-01

    Since 1980, every edition of the Dietary Guidelines for Americans (DGAs) has recommended increased consumption of fruits, vegetables, and whole grains, but reduced consumption of saturated fat, sugars, and sodium and, therefore, their primary food sources. Every edition has generated controversy, mainly from producers of foods affected by "eat less" recommendations, particularly meat. Objections to the 2015 DGAs focused on environmental as well as scientific issues, but also on purported conflicts of interest among members of the Dietary Guidelines Advisory Committee. On this basis, critics induced Congress to authorize the National Academy of Medicine (NAM) to review the process of drawing up the guidelines. The NAM's 2017 reports should strengthen the process, but as long as science continues to support advice to reduce consumption of targeted foods, the guidelines will continue to elicit political controversy.

  17. 77 FR 50722 - Software Unit Testing for Digital Computer Software Used in Safety Systems of Nuclear Power Plants

    Federal Register 2010, 2011, 2012, 2013, 2014

    2012-08-22

    ... NUCLEAR REGULATORY COMMISSION [NRC-2012-0195] Software Unit Testing for Digital Computer Software...) is issuing for public comment draft regulatory guide (DG), DG-1208, ``Software Unit Testing for Digital Computer Software used in Safety Systems of Nuclear Power Plants.'' The DG-1208 is proposed...

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

    PubMed

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

  19. Assessing Compliance with United States Government Orbital Debris Mitigation Guidelines

    NASA Technical Reports Server (NTRS)

    Kelley, R. L.; Jarkey, D. R.

    2015-01-01

    There are currently no exceptions or special considerations for CubeSats in the United States Government (USG) Orbital Debris (OD) Mitigation Guidelines. For all objects launched into space the 2010 United States Space Policy requires that any failure to comply with the USG OD Mitigation Guidelines requires approval by the head of the launching agency. In addition it requires that the US Secretary of State be notified of any non-compliance. For these reasons it is important that missions consider these policies during their design phase. This paper will discuss methods to assess compliance with USG OD mitigation guidelines as they apply to CubeSat missions using tools such as the NASA Debris Assessment Software (DAS).

  20. Global Initiatives for Early Childhood Care and Education: Global Guidelines and Global Guidelines Assessment

    ERIC Educational Resources Information Center

    Trube, Mary Barbara

    2015-01-01

    This report focuses on the Association for Childhood Education International's (ACEI) Global Guidelines (GG) and Global Guidelines Assessment (GGA), which were developed in response to and in keeping with the prominence that the issue of quality early childhood care, development, and education has reached globally. Further, the paper positions the…

  1. Evaluation of Automated Fracture Risk Assessment Based on the Canadian Association of Radiologists and Osteoporosis Canada Assessment Tool.

    PubMed

    Allin, Sonya; Bleakney, Robert; Zhang, Julie; Munce, Sarah; Cheung, Angela M; Jaglal, Susan

    2016-01-01

    Fracture risk assessments are not always clearly communicated on bone mineral density (BMD) reports; evidence suggests that structured reporting (SR) tools may improve report clarity. The aim of this study is to compare fracture risk assessments automatically assigned by SR software in accordance with Canadian Association of Radiologists and Osteoporosis Canada (CAROC) recommendations to assessments from experts on narrative BMD reports. Charts for 500 adult patients who recently received a BMD exam were sampled from across University of Toronto's Joint Department of Medical Imaging. BMD measures and clinical details were manually abstracted from charts and were used to create structured reports with assessments generated by a software implementation of CAROC recommendations. CAROC calculations were statistically compared to experts' original assessments using percentage agreement (PA) and Krippendorff's alpha. Canadian FRAX calculations were also compared to experts', where possible. A total of 25 (5.0%) reported assessments did not conform to categorizations recommended by Canadian guidelines. Across the remainder, the Krippendorff's alpha relating software assigned assessments to physicians was high at 0.918; PA was 94.3%. Lower agreement was associated with reports for patients with documented modifying factors (alpha = 0.860, PA = 90.2%). Similar patterns of agreement related expert assessments to FRAX calculations, although statistics of agreement were lower. Categories of disagreement were defined by (1) gray areas in current guidelines, (2) margins of assessment categorizations, (3) dictation/transcription errors, (4) patients on low doses of steroids, and (5) ambiguous documentation of modifying factors. Results suggest that SR software can produce fracture risk assessments that agree with experts on most routine, adult BMD exams. Results also highlight situations where experts tend to diverge from guidelines and illustrate the potential for SR software to (1) reduce variability in, (2) ameliorate errors in, and (3) improve clarity of routine adult BMD exam reports. Copyright © 2016 International Society for Clinical Densitometry. Published by Elsevier Inc. All rights reserved.

  2. Blood bank on-call physician's experiences at a large university medical center.

    PubMed

    Bryant, Barbara J; Alperin, Jack B; Indrikovs, Alexander J

    2005-01-01

    The responsibilities of the blood bank on-call physician (blood bank physician from here on) encompass many aspects of transfusion medicine and physician education. This physician is available 24 hours a day to address any issues concerning the collection and transfusion of blood and blood components. The purpose of this study was to identify and categorize the issues that may confront a blood bank physician. Each call received over a 4-month period was logged and the resolution documented. The calls were grouped into five categories: donor issues, therapeutic procedure issues, patient issues, physician education issues, and requests for blood components not meeting previously defined transfusion guidelines. The blood bank physician received 224 calls during the study period. To resolve each issue, an additional 1 to 14 telephone calls were needed to gather further information. Number of calls by category were donor issues, 20 (8.9%); therapeutic procedure issues, 9 (4.0%); patient issues, 4 (1.8%); physician education issues, 33 (14.7%); and requests for blood components not meeting previously defined transfusion guidelines, 158 (70.6%). Requests for blood components were denied in 39.8 percent of the cases not meeting guidelines. Other forms of therapy were warranted in 20.9 percent of the cases. This study revealed that 85.3 percent of the calls referred to the blood bank physician related to physician education and the appropriateness of blood component orders. These results emphasize the need for ongoing education of medical staff in transfusion medicine issues.

  3. Using a web-based survey tool to undertake a Delphi study: application for nurse education research.

    PubMed

    Gill, Fenella J; Leslie, Gavin D; Grech, Carol; Latour, Jos M

    2013-11-01

    The Internet is increasingly being used as a data collection medium to access research participants. This paper reports on the experience and value of using web-survey software to conduct an eDelphi study to develop Australian critical care course graduate practice standards. The eDelphi technique used involved the iterative process of administering three rounds of surveys to a national expert panel. The survey was developed online using SurveyMonkey. Panel members responded to statements using one rating scale for round one and two scales for rounds two and three. Text boxes for panel comments were provided. For each round, the SurveyMonkey's email tool was used to distribute an individualized email invitation containing the survey web link. The distribution of panel responses, individual responses and a summary of comments were emailed to panel members. Stacked bar charts representing the distribution of responses were generated using the SurveyMonkey software. Panel response rates remained greater than 85% over all rounds. An online survey provided numerous advantages over traditional survey approaches including high quality data collection, ease and speed of survey administration, direct communication with the panel and rapid collation of feedback allowing data collection to be undertaken in 12 weeks. Only minor challenges were experienced using the technology. Ethical issues, specific to using the Internet to conduct research and external hosting of web-based software, lacked formal guidance. High response rates and an increased level of data quality were achieved in this study using web-survey software and the process was efficient and user-friendly. However, when considering online survey software, it is important to match the research design with the computer capabilities of participants and recognize that ethical review guidelines and processes have not yet kept pace with online research practices. Copyright © 2013 Elsevier Ltd. All rights reserved.

  4. Frequency Domain Identification Toolbox

    NASA Technical Reports Server (NTRS)

    Horta, Lucas G.; Juang, Jer-Nan; Chen, Chung-Wen

    1996-01-01

    This report documents software written in MATLAB programming language for performing identification of systems from frequency response functions. MATLAB is a commercial software environment which allows easy manipulation of data matrices and provides other intrinsic matrix functions capabilities. Algorithms programmed in this collection of subroutines have been documented elsewhere but all references are provided in this document. A main feature of this software is the use of matrix fraction descriptions and system realization theory to identify state space models directly from test data. All subroutines have templates for the user to use as guidelines.

  5. USL/DBMS NASA/PC R and D project system testing standards

    NASA Technical Reports Server (NTRS)

    Dominick, Wayne D. (Editor); Kavi, Srinu; Moreau, Dennis R.; Yan, Lin

    1984-01-01

    A set of system testing standards to be used in the development of all C software within the NASA/PC Research and Development Project is established. Testing will be considered in two phases: the program testing phase and the system testing phase. The objective of these standards is to provide guidelines for the planning and conduct of program and software system testing.

  6. Guidelines for Processing and Cataloging Computer Software for Schools and Area Education Agencies. Suggestions to Aid Schools and AEAs.

    ERIC Educational Resources Information Center

    Martin, Elizabeth; And Others

    Based on definitions of a machine-readable data file (MRDF) taken from the Anglo-American Cataloging Rules, second edition (AACR2) and Standards for Cataloging Nonprint Materials, the following recommendations for processing items of computer software are provided: (1) base main and added entry determination on AACR2; (2) place designation of form…

  7. Peeling the Onion: Okapi System Architecture and Software Design Issues.

    ERIC Educational Resources Information Center

    Jones, S.; And Others

    1997-01-01

    Discusses software design issues for Okapi, an information retrieval system that incorporates both search engine and user interface and supports weighted searching, relevance feedback, and query expansion. The basic search system, adjacency searching, and moving toward a distributed system are discussed. (Author/LRW)

  8. Managing Automation: A Process, Not a Project.

    ERIC Educational Resources Information Center

    Hoffmann, Ellen

    1988-01-01

    Discussion of issues in management of library automation includes: (1) hardware, including systems growth and contracts; (2) software changes, vendor relations, local systems, and microcomputer software; (3) item and authority databases; (4) automation and library staff, organizational structure, and managing change; and (5) environmental issues,…

  9. Technology Transfer Challenges for High-Assurance Software Engineering Tools

    NASA Technical Reports Server (NTRS)

    Koga, Dennis (Technical Monitor); Penix, John; Markosian, Lawrence Z.

    2003-01-01

    In this paper, we describe our experience with the challenges thar we are currently facing in our effort to develop advanced software verification and validation tools. We categorize these challenges into several areas: cost benefits modeling, tool usability, customer application domain, and organizational issues. We provide examples of challenges in each area and identrfj, open research issues in areas which limit our ability to transfer high-assurance software engineering tools into practice.

  10. A Legal Guide for the Software Developer.

    ERIC Educational Resources Information Center

    Minnesota Small Business Assistance Office, St. Paul.

    This booklet has been prepared to familiarize the inventor, creator, or developer of a new computer software product or software invention with the basic legal issues involved in developing, protecting, and distributing the software in the United States. Basic types of software protection and related legal matters are discussed in detail,…

  11. 78 FR 47015 - Software Requirement Specifications for Digital Computer Software Used in Safety Systems of...

    Federal Register 2010, 2011, 2012, 2013, 2014

    2013-08-02

    ... NUCLEAR REGULATORY COMMISSION [NRC-2012-0195] Software Requirement Specifications for Digital Computer Software Used in Safety Systems of Nuclear Power Plants AGENCY: Nuclear Regulatory Commission... issuing a revised regulatory guide (RG), revision 1 of RG 1.172, ``Software Requirement Specifications for...

  12. [Systematic Review of the Methodology Quality in Lung Cancer Screening Guidelines].

    PubMed

    Li, Jiang; Su, Kai; Li, Fang; Tang, Wei; Huang, Yao; Wang, Le; Huang, Huiyao; Shi, Jufang; Dai, Min

    2016-10-20

    Lung cancer is the most common malignancy and screening can decrease the mortality. High quality screening guideline is necessary and important for effective work. Our study is to review and evaluate the basic characteristics and methodology quality of the current global lung cancer screening guidelines so as to provide useful information for domestic study in the future. Electronic searches were done in English and Chinese databases including PubMed, the Cochrane Library, Web of Science, Embase, CNKI, CBM, Wanfang, and some cancer official websites. Articles were screened according to the predefined inclusion and exclusion criteria by two researchers. The quality of guidelines was assessed by AGREE II. At last, a total of 11 guidelines with methodology were included. The guidelines were issued mainly by USA (81%). Canada and China developed one, respectively. As for quality, the average score in the "Scale and objective" of all guidelines was 80, the average score in the "Participants" was 52, the average score in the "rigorism" was 50, the average score in the "clarity" was 76, the average score in the "application" was 43 and the average score in the "independence" was 59. The highest average score was found in 2013 and 2015. Canada guideline had higher quality in six domains. 7 guidelines were evaluated as A level. The number of clinical guidelines showed an increasing trend. Most guidelines were issued by developed countries with heavy burden. Multi-country contribution to one guideline was another trend. Evidence-based methodology was accepted globally in the guideline development.

  13. A recommended guideline for the development of mHealth Apps.

    PubMed

    Chatzipavlou, Ioannis A; Christoforidou, Sofia A; Vlachopoulou, Maro

    2016-01-01

    Mobile Health or mHealth applications cope with medical or health issues supported by smartphones. Being a part of great importance in healthcare, mHealth apps are able to improve both the quality of medical services and the safety of the patients. It is regarded to be a new field with great prospect that attracts the interest of the stakeholders and the developers, above all. Of all the entities involved, developers have to face many challenges classified in four pillars: the regulation framework, the market, the technical issues and society. This paper aims to describe the role of the developers in the mHealth apps' market, the barriers they deal with and also, the impact of their work in the mobile healthcare domain. In our viewpoint, we propose a guideline with all of the developers' requirements for the buildup of mHealth apps. The methodology followed includes a Boolean search strategy used in academic libraries (PubMed, IEEE Xplore, JMIR, The Cochrane Library) and search engines additionally (Google and Google Scholar), aiming to identify the developers' perspective. Our research from October until December of 2014 led us to academic papers referring to the various demands that developers have to confront. The major outcome of our research is the general acknowledgement of the dominant role that developers own in the mHealth apps' process. Mobile technology allies multiple groups such as users, patients, providers of medical services, software developers, governments and even, non-governmental organizations. In particular, the developers' perspective involves the legal boundaries, the side of the market, the technological requirements (programming, devices, designing) and the moral aspects, as well. Developers should define the purposes of their apps-either diagnostic or therapeutic-and gain the confidence of the users in order to dominate the market, yet comply with the regulations.

  14. Regulatory assessment of proposed accessibility guidelines for pedestrians in the public right-of-way

    DOT National Transportation Integrated Search

    2011-06-30

    This report assesses the potential costs and benefits of proposed accessibility guidelines issued by the Access Board for pedestrian facilities in the public right-of-way. The report also analyzes the potential impacts of the proposed guidelines on s...

  15. The Development of Human Factor Guidelines for Unmanned Aircraft System Control Stations

    NASA Technical Reports Server (NTRS)

    Hobbs, Alan

    2014-01-01

    Despite being referred to as unmanned some of the major challenges confronting unmanned aircraft systems (UAS) relate to human factors. NASA is conducting research to address the human factors relevant to UAS access to non-segregated airspace. This work covers the issues of pilot performance, interaction with ATC, and control station design. A major outcome of this research will be recommendations for human factors design guidelines for UAS control stations to support routine beyond-line-of-sight operations in the US national airspace system (NAS). To be effective, guidelines must be relevant to a wide range of systems, must not be overly prescriptive, and must not impose premature standardization on evolving technologies. In developing guidelines, we recognize that existing regulatory and guidance material may already provide adequate coverage of certain issues. In other cases suitable guidelines may be found in existing military or industry human factors standards. In cases where appropriate existing standards cannot be identified, original guidelines will be proposed.

  16. Rules of thumb to increase the software quality through testing

    NASA Astrophysics Data System (ADS)

    Buttu, M.; Bartolini, M.; Migoni, C.; Orlati, A.; Poppi, S.; Righini, S.

    2016-07-01

    The software maintenance typically requires 40-80% of the overall project costs, and this considerable variability mostly depends on the software internal quality: the more the software is designed and implemented to constantly welcome new changes, the lower will be the maintenance costs. The internal quality is typically enforced through testing, which in turn also affects the development and maintenance costs. This is the reason why testing methodologies have become a major concern for any company that builds - or is involved in building - software. Although there is no testing approach that suits all contexts, we infer some general guidelines learned during the Development of the Italian Single-dish COntrol System (DISCOS), which is a project aimed at producing the control software for the three INAF radio telescopes (the Medicina and Noto dishes, and the newly-built SRT). These guidelines concern both the development and the maintenance phases, and their ultimate goal is to maximize the DISCOS software quality through a Behavior-Driven Development (BDD) workflow beside a continuous delivery pipeline. We consider different topics and patterns; they involve the proper apportion of the tests (from end-to-end to low-level tests), the choice between hardware simulators and mockers, why and how to apply TDD and the dependency injection to increase the test coverage, the emerging technologies available for test isolation, bug fixing, how to protect the system from the external resources changes (firmware updating, hardware substitution, etc.) and, eventually, how to accomplish BDD starting from functional tests and going through integration and unit tests. We discuss pros and cons of each solution and point out the motivations of our choices either as a general rule or narrowed in the context of the DISCOS project.

  17. [Guidelines on medically assisted reproduction: legal issues and professional liability].

    PubMed

    Molinelli, A; Motroni Gherardi, S M; Picchioni, D M; Ventura, F

    2007-08-01

    The authors analyze the legal and medico-legal issues deriving from the recent Law No. 40 of February 19, 2004 concerning the Medically Assisted Reproduction. In particular, they analyze the contrasting points between the dispositions of Law No. 40/2004 and those of Law No. 194/1978 on the voluntary interruption of pregnancy, and they analyze the guidelines about the procedures and the techniques of the Medically Assisted Reproduction, issued by the Ministry of Health with D.M. of July 21, 2004. The Guidelines, as well as some sentences of several courts, lead to some reflections also about the consent and the professional liability, in particular considering the various moments of the medical action, from the first interview to the carrying out of the assisted reproduction techniques.

  18. Guideline for the utilization of commercial grade items in nuclear safety related applications: Final report. [Contains Glossary

    DOE Office of Scientific and Technical Information (OSTI.GOV)

    Tulay, M.P.; Yurich, F.J.; Schremser, F.M. Jr.

    1988-06-01

    This guideline provides direction for the procurement and use of Commercial Grade Items (CGI)in safety-related applications. It is divided into five major sections. A glossary of terms and definitions, an acronym listing, and seven appendices have been included. The glossary defines terms used in this guideline. In certain instances, the definitions may be unique to this guideline. Identification of acronyms utilized in this guideline is also provided. Section 1 provides a background of the commercial grade item issues facing the nuclear industry. It provides a historical perspective of commercial grade item issues. Section 2 discusses the generic process for themore » acceptance of a commercial grade item for safety-related use. Section 3 defines the four distinct methods used to accept commercial grade items for safety-related applications. Section 4 lists specific references that are identified in this guideline. Section 5 is a bibliography of documents that were considered in developed this guideline, but were not directly referenced in the document.« less

  19. Issues in Software System Safety: Polly Ann Smith Co. versus Ned I. Ludd

    NASA Technical Reports Server (NTRS)

    Holloway, C. Michael

    2002-01-01

    This paper is a work of fiction, but it is fiction with a very real purpose: to stimulate careful thought and friendly discussion about some questions for which thought is often careless and discussion is often unfriendly. To accomplish this purpose, the paper creates a fictional legal case. The most important issue in this fictional case is whether certain proffered expert testimony about software engineering for safety critical systems should be admitted. Resolving this issue requires deciding the extent to which current practices and research in software engineering, especially for safety-critical systems, can rightly be considered based on knowledge, rather than opinion.

  20. A new independent authority is needed to issue National Health Care guidelines.

    PubMed

    Keyhani, Salomeh; Kim, Azalea; Mann, Micah; Korenstein, Deborah

    2011-02-01

    Health experts emphasize that getting doctors to follow clinical guidelines can save both lives and money. Less attention has been paid to how the guidelines are developed and the variability in the recommendations they include. We examined the quality and content of screening guidelines as a proxy for guidelines in general and found that the source of the guidelines affects their quality. Guidelines with inconsistent recommendations are unlikely to serve patients or physicians well. The creation of an independent organization that would work with multiple stakeholders to develop guidelines holds the potential to improve their quality.

  1. Smartphone Application of Primary Care Guidelines used in Education of Medical Students

    PubMed Central

    Waldmann, Uta-Maria; Weckbecker, Klaus

    2013-01-01

    Background and Objective: The guidelines of the German College of General Practitioners and Family Physicians (DEGAM) on frequent and important reasons for encounter in Primary Care play a central role in the teaching of Family Medicine. They were edited by the authors into an app for mobile phones, making them available at all times to General Practitioners and medical students. This study examines the issue: how useful do students consider this application within their learning process in Family Medicine? Method: The short versions of the 15 DEGAM guidelines were processed as a web app (for all smartphone software systems) including offline utilisation, and offered to students in the Family Medicine course, during clinical attachments in General Practice, on elective compulsory courses or for their final year rotation in General Practice. The evaluation was made with a structured survey using the feedback function of the Moodle learning management system [http://www.elearning-allgemeinmedizin.de] with Likert scales and free-text comments. Results: Feedback for evaluation came from 14 (25%) of the student testers from the Family Medicine course (9), the clinical attachment in General Practice (1), the final year rotation in General Practice (1) and elective compulsory courses (4). Students rated the app as an additional benefit to the printed/pdf-form. They use it frequently and successfully during waiting periods and before, during, or after lectures. In addition to general interest and a desire to become acquainted with the guidelines and to learn, the app is consulted with regard to general (theoretical) questions, rather than in connection with contact with patients. Interest in and knowledge of the guidelines is stimulated by the app, and on the whole the application can be said to be well suited to the needs of this user group. Discussion: The students evaluated the guidelines app positively: as a modern way of familiarising them with the guidelines and expanding their knowledge, particularly through its use in waiting periods and the attractive medium smartphone. However, the latter prevents a mandatory curricular use in compulsory courses, since not all students use smartphones. It is a meaningful addition to existing teaching materials and supports evidence-based teaching in Family Medicine and is suitable for use not only in university course teaching but also during clinical training. PMID:23467657

  2. Smartphone application of primary care guidelines used in education of medical students.

    PubMed

    Waldmann, Uta-Maria; Weckbecker, Klaus

    2013-01-01

    The guidelines of the German College of General Practitioners and Family Physicians (DEGAM) on frequent and important reasons for encounter in Primary Care play a central role in the teaching of Family Medicine. They were edited by the authors into an app for mobile phones, making them available at all times to General Practitioners and medical students. This study examines the issue: how useful do students consider this application within their learning process in Family Medicine? The short versions of the 15 DEGAM guidelines were processed as a web app (for all smartphone software systems) including offline utilisation, and offered to students in the Family Medicine course, during clinical attachments in General Practice, on elective compulsory courses or for their final year rotation in General Practice. The evaluation was made with a structured survey using the feedback function of the Moodle learning management system [http://www.elearning-allgemeinmedizin.de] with Likert scales and free-text comments. Feedback for evaluation came from 14 (25%) of the student testers from the Family Medicine course (9), the clinical attachment in General Practice (1), the final year rotation in General Practice (1) and elective compulsory courses (4). Students rated the app as an additional benefit to the printed/pdf-form. They use it frequently and successfully during waiting periods and before, during, or after lectures. In addition to general interest and a desire to become acquainted with the guidelines and to learn, the app is consulted with regard to general (theoretical) questions, rather than in connection with contact with patients. Interest in and knowledge of the guidelines is stimulated by the app, and on the whole the application can be said to be well suited to the needs of this user group. The students evaluated the guidelines app positively: as a modern way of familiarising them with the guidelines and expanding their knowledge, particularly through its use in waiting periods and the attractive medium smartphone. However, the latter prevents a mandatory curricular use in compulsory courses, since not all students use smartphones. It is a meaningful addition to existing teaching materials and supports evidence-based teaching in Family Medicine and is suitable for use not only in university course teaching but also during clinical training.

  3. BioContainers: an open-source and community-driven framework for software standardization.

    PubMed

    da Veiga Leprevost, Felipe; Grüning, Björn A; Alves Aflitos, Saulo; Röst, Hannes L; Uszkoreit, Julian; Barsnes, Harald; Vaudel, Marc; Moreno, Pablo; Gatto, Laurent; Weber, Jonas; Bai, Mingze; Jimenez, Rafael C; Sachsenberg, Timo; Pfeuffer, Julianus; Vera Alvarez, Roberto; Griss, Johannes; Nesvizhskii, Alexey I; Perez-Riverol, Yasset

    2017-08-15

    BioContainers (biocontainers.pro) is an open-source and community-driven framework which provides platform independent executable environments for bioinformatics software. BioContainers allows labs of all sizes to easily install bioinformatics software, maintain multiple versions of the same software and combine tools into powerful analysis pipelines. BioContainers is based on popular open-source projects Docker and rkt frameworks, that allow software to be installed and executed under an isolated and controlled environment. Also, it provides infrastructure and basic guidelines to create, manage and distribute bioinformatics containers with a special focus on omics technologies. These containers can be integrated into more comprehensive bioinformatics pipelines and different architectures (local desktop, cloud environments or HPC clusters). The software is freely available at github.com/BioContainers/. yperez@ebi.ac.uk. © The Author(s) 2017. Published by Oxford University Press.

  4. BioContainers: an open-source and community-driven framework for software standardization

    PubMed Central

    da Veiga Leprevost, Felipe; Grüning, Björn A.; Alves Aflitos, Saulo; Röst, Hannes L.; Uszkoreit, Julian; Barsnes, Harald; Vaudel, Marc; Moreno, Pablo; Gatto, Laurent; Weber, Jonas; Bai, Mingze; Jimenez, Rafael C.; Sachsenberg, Timo; Pfeuffer, Julianus; Vera Alvarez, Roberto; Griss, Johannes; Nesvizhskii, Alexey I.; Perez-Riverol, Yasset

    2017-01-01

    Abstract Motivation BioContainers (biocontainers.pro) is an open-source and community-driven framework which provides platform independent executable environments for bioinformatics software. BioContainers allows labs of all sizes to easily install bioinformatics software, maintain multiple versions of the same software and combine tools into powerful analysis pipelines. BioContainers is based on popular open-source projects Docker and rkt frameworks, that allow software to be installed and executed under an isolated and controlled environment. Also, it provides infrastructure and basic guidelines to create, manage and distribute bioinformatics containers with a special focus on omics technologies. These containers can be integrated into more comprehensive bioinformatics pipelines and different architectures (local desktop, cloud environments or HPC clusters). Availability and Implementation The software is freely available at github.com/BioContainers/. Contact yperez@ebi.ac.uk PMID:28379341

  5. Architecture for interoperable software in biology.

    PubMed

    Bare, James Christopher; Baliga, Nitin S

    2014-07-01

    Understanding biological complexity demands a combination of high-throughput data and interdisciplinary skills. One way to bring to bear the necessary combination of data types and expertise is by encapsulating domain knowledge in software and composing that software to create a customized data analysis environment. To this end, simple flexible strategies are needed for interconnecting heterogeneous software tools and enabling data exchange between them. Drawing on our own work and that of others, we present several strategies for interoperability and their consequences, in particular, a set of simple data structures--list, matrix, network, table and tuple--that have proven sufficient to achieve a high degree of interoperability. We provide a few guidelines for the development of future software that will function as part of an interoperable community of software tools for biological data analysis and visualization. © The Author 2012. Published by Oxford University Press.

  6. Impact of Growing Business on Software Processes

    NASA Astrophysics Data System (ADS)

    Nikitina, Natalja; Kajko-Mattsson, Mira

    When growing their businesses, software organizations should not only put effort into developing and executing their business strategies, but also into managing and improving their internal software development processes and aligning them with business growth strategies. It is only in this way they may confirm that their businesses grow in a healthy and sustainable way. In this paper, we map out one software company's business growth on the course of its historical events and identify its impact on the company's software production processes and capabilities. The impact concerns benefits, challenges, problems and lessons learned. The most important lesson learned is that although business growth has become a stimulus for starting thinking and improving software processes, the organization lacked guidelines aiding it in and aligning it to business growth. Finally, the paper generates research questions providing a platform for future research.

  7. Exploiting Temporal Constraints of Clinical Guidelines by Applying OpenEHR Archetypes.

    PubMed

    Cintho, Lilian Mie Mukai; Garcia, Diego; da Silva Santos, Bruno Henrique; Sacchi, Lucia; Quaglini, Silvana; Moro, Claudia Maria Cabral

    2017-01-01

    Studies describing Computer-Interpretable Clinical Guidelines (CIG) with temporal constrains (TC) generally have not addressed issues related to their integration into Electronic Health Record (EHR) systems. This study aimed to represent TCs contained in clinical guidelines by applying archetypes and Guideline Definition Language (GDL) to incorporate decision support into EHRs. An example of each TC class in the clinical guideline for management of Atrial Fibrillation was represented using archetypes and GDL.

  8. Genetic Testing for Minors: Comparison between Italian and British Guidelines

    PubMed Central

    Tozzo, Pamela; Caenazzo, Luciana; Rodriguez, Daniele

    2012-01-01

    Genetic testing in children raises many important ethical, legal, and social issues. One of the main concerns is the ethically inappropriate genetic testing of minors. Various European countries established professional guidelines which reflect the different countries perspectives regarding the main ethical issues involved. In this paper, we analyze the Italian and the British guidelines by highlighting differences and similarities. We discuss presymptomatic, predictive, and carrier testing because we consider them to be the more ethically problematic types of genetic testing in minors. In our opinion, national guidelines should take into account the different needs in clinical practice. At the same time, in the case of genetic testing the national and supranational protection of minors could be strengthened by approving guidelines based on a common framework of principles and values. We suggest that the Oviedo Convention could represent an example of such a common framework or, at least, it could lead to articulate it. PMID:22567400

  9. Nephrology nurses' perspectives on difficult ethical issues and practice guideline for shared decision making.

    PubMed

    Rabetoy, Christy Price; Bair, Bradley C

    2007-01-01

    Nephrologists and nephrology nurses have struggled with the technological, financial, and ethical concerns surrounding the life sustaining treatment of hemodialysis for as long as this treatment as been available. One of the overriding issues for the nephrology community has been appropriate utilization of this technology and the appropriate restraint for prescribing dialysis. Since the inception of dialysis, there has been discussion of guidelines for deciding who should receive and who should not receive this therapy. In 2000, a clinical guideline was developed to assist in directing the care of patients. The knowledge and acceptance of this guideline by nephrologists has been researched in the past. However, there is no data of knowledge and acceptance of the guideline by nephrology clinical nurses or nephrology nurse practitioners. A survey was conducted to begin to ascertain this information in order to better understand the perspectives of nephrology nurses.

  10. Applying Cognitive Psychology to User Interfaces

    NASA Astrophysics Data System (ADS)

    Durrani, Sabeen; Durrani, Qaiser S.

    This paper explores some key aspects of cognitive psychology that may be mapped onto user interfaces. Major focus in existing user interface guidelines is on consistency, simplicity, feedback, system messages, display issues, navigation, colors, graphics, visibility and error prevention [8-10]. These guidelines are effective indesigning user interfaces. However, these guidelines do not handle the issues that may arise due to the innate structure of human brain and human limitations. For example, where to place graphics on the screen so that user can easily process them and what kind of background should be given on the screen according to the limitation of human motor system. In this paper we have collected some available guidelines from the area of cognitive psychology [1, 5, 7]. In addition, we have extracted few guidelines from theories and studies of cognitive psychology [3, 11] which may be mapped to user interfaces.

  11. Pathways to lean software development: An analysis of effective methods of change

    NASA Astrophysics Data System (ADS)

    Hanson, Richard D.

    This qualitative Delphi study explored the challenges that exist in delivering software on time, within budget, and with the original scope identified. The literature review identified many attempts over the past several decades to reform the methods used to develop software. These attempts found that the classical waterfall method, which is firmly entrenched in American business today was to blame for this difficulty (Chatterjee, 2010). Each of these proponents of new methods sought to remove waste, lighten out the process, and implement lean principles in software development. Through this study, the experts evaluated the barriers to effective development principles and defined leadership qualities necessary to overcome these barriers. The barriers identified were issues of resistance to change, risk and reward issues, and management buy-in. Thirty experts in software development from several Fortune 500 companies across the United States explored each of these issues in detail. The conclusion reached by these experts was that visionary leadership is necessary to overcome these challenges.

  12. Selection Criteria for Mathematical Models Used in Exposure Assessments: Atmospheric Dispersion Models

    EPA Science Inventory

    Before the U.S. Environmental Protection Agency issued the 1988 Guidelines for Estimating Exposures, it published proposed guidelines in the Federal Register for public review and comment. he guidelines are intended to give risk analysis a basic framework and the tools they need ...

  13. In the soft-to-hard technical spectrum: Where is software engineering?

    NASA Technical Reports Server (NTRS)

    Leibfried, Theodore F.; Macdonald, Robert B.

    1992-01-01

    In the computer journals and tabloids, there have been a plethora of articles written about the software engineering field. But while advocates of the need for an engineering approach to software development, it is impressive how many authors have treated the subject of software engineering without adequately addressing the fundamentals of what engineering as a discipline consists of. A discussion is presented of the various related facets of this issue in a logical framework to advance the thesis that the software development process is necessarily an engineering process. The purpose is to examine more of the details of the issue of whether or not the design and development of software for digital computer processing systems should be both viewed and treated as a legitimate field of professional engineering. Also, the type of academic and professional level education programs that would be required to support a software engineering discipline is examined.

  14. Effluent Guidelines

    EPA Pesticide Factsheets

    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.

  15. UTM TCL 2.0 Software Version Description (SVD) Document

    NASA Technical Reports Server (NTRS)

    Mcguirk, Patrick

    2017-01-01

    This is the Unmanned Aircraft Systems (UAS) Traffic Management (UTM) Technical Capability Level(TCL) 2.0 Software Version Description (SVD) document. This UTM TCL 2.0 SVD describes the following four topics: 1. Software Release Contents: A listing of the files comprising this release 2. Installation Instructions: How to install the release and get it running 3. Changes Since Previous Release: General updates since the previous UTM release 4. Known Issues: Known issues and limitations in this release

  16. NASA PC software evaluation project

    NASA Technical Reports Server (NTRS)

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

    1986-01-01

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

  17. Process Definition and Modeling Guidebook. Version 01.00.02

    DTIC Science & Technology

    1992-12-01

    material (and throughout the guidebook)process defnition is considered to be the act of representing the important characteristics of a process in a...characterized by software standards and guidelines, software inspections and reviews, and more formalized testing (including test plans, test sup- port tools...paper-based approach works well for training, examples, and possibly even small pilot projects and case studies. However, large projects will benefit from

  18. Security Vulnerability Profiles of Mission Critical Software: Empirical Analysis of Security Related Bug Reports

    NASA Technical Reports Server (NTRS)

    Goseva-Popstojanova, Katerina; Tyo, Jacob

    2017-01-01

    While some prior research work exists on characteristics of software faults (i.e., bugs) and failures, very little work has been published on analysis of software applications vulnerabilities. This paper aims to contribute towards filling that gap by presenting an empirical investigation of application vulnerabilities. The results are based on data extracted from issue tracking systems of two NASA missions. These data were organized in three datasets: Ground mission IVV issues, Flight mission IVV issues, and Flight mission Developers issues. In each dataset, we identified security related software bugs and classified them in specific vulnerability classes. Then, we created the security vulnerability profiles, i.e., determined where and when the security vulnerabilities were introduced and what were the dominating vulnerabilities classes. Our main findings include: (1) In IVV issues datasets the majority of vulnerabilities were code related and were introduced in the Implementation phase. (2) For all datasets, around 90 of the vulnerabilities were located in two to four subsystems. (3) Out of 21 primary classes, five dominated: Exception Management, Memory Access, Other, Risky Values, and Unused Entities. Together, they contributed from 80 to 90 of vulnerabilities in each dataset.

  19. Knowledge base methodology: Methodology for first Engineering Script Language (ESL) knowledge base

    NASA Technical Reports Server (NTRS)

    Peeris, Kumar; Izygon, Michel E.

    1992-01-01

    The primary goal of reusing software components is that software can be developed faster, cheaper and with higher quality. Though, reuse is not automatic and can not just happen. It has to be carefully engineered. For example a component needs to be easily understandable in order to be reused, and it has also to be malleable enough to fit into different applications. In fact the software development process is deeply affected when reuse is being applied. During component development, a serious effort has to be directed toward making these components as reusable. This implies defining reuse coding style guidelines and applying then to any new component to create as well as to any old component to modify. These guidelines should point out the favorable reuse features and may apply to naming conventions, module size and cohesion, internal documentation, etc. During application development, effort is shifted from writing new code toward finding and eventually modifying existing pieces of code, then assembling them together. We see here that reuse is not free, and therefore has to be carefully managed.

  20. 76 FR 47353 - Final Directives for Forest Service Wind Energy Special Use Authorizations, Forest Service Manual...

    Federal Register 2010, 2011, 2012, 2013, 2014

    2011-08-04

    ... siting wind energy turbines, evaluating a variety of resource interests, and addressing issues... power guidelines produced by the Wind Energy Turbines Guidelines Advisory Committee, which consists of... recognizes that recommendations from the Wind Energy Turbines Guidelines Advisory Committee will be used to...

  1. 77 FR 4909 - Income Level for Individuals Eligible for Assistance

    Federal Register 2010, 2011, 2012, 2013, 2014

    2012-02-01

    ... Poverty Guidelines as issued by the Department of Health and Human Services. DATES: Effective Date: This... level equivalent to one hundred and twenty-five percent (125%) of the Federal Poverty Guidelines. Since... Federal Poverty Guidelines. The figures for 2012 set out below are equivalent to 125% of the current...

  2. 75 FR 47487 - Income Level for Individuals Eligible for Assistance

    Federal Register 2010, 2011, 2012, 2013, 2014

    2010-08-06

    ... Poverty Guidelines as issued by the Department of Health and Human Services. DATES: Effective Date: This... level equivalent to one hundred and twenty-five percent (125%) of the Federal Poverty Guidelines. Since... Federal Poverty Guidelines. The figures for 2010 set out below are equivalent to 125% of the current...

  3. Occupational safety and health aspects of corporate social responsibility (CSR) in Japanese companies listed on the Tokyo Stock Exchange (TSE) first section.

    PubMed

    Kawashita, Futoshi; Taniyama, Yukari; Hwi, Song You; Fujisaki, Takeshi; Kameda, Takashi; Mori, Koji

    2005-11-01

    Recently, corporate social responsibility (CSR) is becoming widely recognized as an issue for Japanese companies. Corporate responsibility for employees is considered important by various stakeholders, and occupational safety and health is regarded as one of these responsibilities. The present authors examined this issue from the viewpoint of corporate management by analysis of statements found in CSR-related reports. For companies listed on the First Section of the Tokyo Stock Exchange (TSE), we searched for CSR-related reports, and titles and contents, based on two established guidelines: the GRI Sustainability Reporting Guidelines 2002 as the international reference and the Environmental Reporting Guidelines of the Ministry of the Environment, Government of Japan, as the domestic reference. Corporations that published CSR reports were 26.3% (416/1,581) of the total, and large differences were recognized by type of industry. Comparing the numbers of pages for various contents, more concern was shown about the environment than about social activity, indicating the environment to be the main issue of CSR in Japan. In the items included in the guidelines, many matters about occupational accidents were mentioned, but it was found that statements regarding HIV/AIDS, which is not of such strong social concern in Japan, and statements regarding the costs of safety that are difficult to calculate were few. However, statements regarding mental health, which is of high interest socially, were many, even though this issue is not included in the two guidelines used. In revising the guidelines, these matters should be reviewed. In the future, continuance of analysis of CSR-related reports with regard to changes and comparisons with overseas reports will help improve occupational safety and health.

  4. Study of a unified hardware and software fault-tolerant architecture

    NASA Technical Reports Server (NTRS)

    Lala, Jaynarayan; Alger, Linda; Friend, Steven; Greeley, Gregory; Sacco, Stephen; Adams, Stuart

    1989-01-01

    A unified architectural concept, called the Fault Tolerant Processor Attached Processor (FTP-AP), that can tolerate hardware as well as software faults is proposed for applications requiring ultrareliable computation capability. An emulation of the FTP-AP architecture, consisting of a breadboard Motorola 68010-based quadruply redundant Fault Tolerant Processor, four VAX 750s as attached processors, and four versions of a transport aircraft yaw damper control law, is used as a testbed in the AIRLAB to examine a number of critical issues. Solutions of several basic problems associated with N-Version software are proposed and implemented on the testbed. This includes a confidence voter to resolve coincident errors in N-Version software. A reliability model of N-Version software that is based upon the recent understanding of software failure mechanisms is also developed. The basic FTP-AP architectural concept appears suitable for hosting N-Version application software while at the same time tolerating hardware failures. Architectural enhancements for greater efficiency, software reliability modeling, and N-Version issues that merit further research are identified.

  5. [Clinical application evaluation of Guidelines for Diagnosis and Treatment of Common Diseases of Dermatology in Traditional Chinese Medicine].

    PubMed

    Wang, Yue-Xi; Liu, Meng-Yu; Wang, Li-Ying; Shi, Nan-Nan; Zhao, Xue-Yao; Liu, Yu-Qi; Wang, Yan-Ping; Han, Xue-Jie

    2017-09-01

    To assess the quality and application effect of Guidelines for Diagnosis and Treatment of Common Diseases of Dermatology in Traditional Chinese Medicine(Guidelines) through the applicability and applicability evaluation respectively. The questionnaire survey was adopted to evaluate the applicability of the Guidelines, including the utilization, quality, and clinical application conditions. The results showed that the familiarity rate and utilization rate of the Guidelines were 85.37%, 48.78%, respectively. The data showed that the familiarity and the utilization rates were different in the working staff with different professional titles. The evaluation level was the lowest given by the staff with junior professional title (70.97%, 29.03%) in comparison. The assessment showed the overall quality of the Guideline was good and slightly low level for the rationality scores of the other therapeutic methods as well as for the recuperation and prevention (80.49%, 85.37%), which was in line with the clinical compliance of the Guideline. The perspective observation of clinical cases was used for the applicability evaluation, including clinical compliance of the Guideline, effect evaluation, and comprehensive assessment, et al. The results showed that the safety score was the highest, followed by the economic issue and efficacy. For the comprehensive evaluation of the applicability, complete applicability accounted for 29.27%, and the general applicability accounted for 87.80%. It was showed in the three index scores of the applicability evaluation that the accumulative score 7-9 scores were 75.65%, 73.89%, 71.12%. Through the applicability and applicability evaluation, the Guideline was satisfactory in the overall quality, high in the safety of clinical application and good in efficacy and economic issues. There are some limits on the development method and technical issues in the Guideline, which is required to be supplemented in the revision. Additionally, the strategy study on the promotion of the Guideline should be enhanced so as to expedite the recognition and utilization of the Guideline. Copyright© by the Chinese Pharmaceutical Association.

  6. Streamlining Software Aspects of Certification: Report on the SSAC Survey

    NASA Technical Reports Server (NTRS)

    Hayhurst, Kelly J.; Dorsey, Cheryl A.; Knight, John C.; Leveson, Nancy G.; McCormick, G. Frank

    1999-01-01

    The aviation system now depends on information technology more than ever before to ensure safety and efficiency. To address concerns about the efficacy of software aspects of the certification process, the Federal Aviation Administration (FAA) began the Streamlining Software Aspects of Certification (SSAC) program. The SSAC technical team was commissioned to gather data, analyze results, and propose recommendations to maximize efficiency and minimize cost and delay, without compromising safety. The technical team conducted two public workshops to identify and prioritize software approval issues, and conducted a survey to validate the most urgent of those issues. The SSAC survey, containing over two hundred questions about the FAA's software approval process, reached over four hundred industry software developers, aircraft manufacturers, and FAA designated engineering representatives. Three hundred people responded. This report presents the SSAC program rationale, survey process, preliminary findings, and recommendations.

  7. FRAMEWORK FOR DEVELOPING AMBIENT WATER ...

    EPA Pesticide Factsheets

    Currently, Ambient Water Quality Criteria (AWQC) for aquatic life protection are derived according to the Guidelines for Derivation of Ambient Water Quality Criteria for the Protection of Aquatic Life and Their Uses, published in 1985. To ensure that AWQC are derived from the best available science, Office of Water assessed the need to update the Guidelines and identified issues that should be addressed in the revisions. In December 2002, EPA's Science Advisory Board concurred with EPA's assessment of the need to update the Guidelines as well as with the issues EPA identified to address. Updating the Guidelines is a Priority Strategic Action included in OST's Strategy for Water Quality Standards and Criteria (Next Priority Strategic Action #1). To revise existing methodology for deriving ambient water quality criteria for the protection of aquatic life.

  8. Is traditional Chinese medicine recommended in Western medicine clinical practice guidelines in China? A systematic analysis

    PubMed Central

    Ren, Jun; Li, Xun; Sun, Jin; Han, Mei; Yang, Guo-Yan; Li, Wen-Yuan; Robinson, Nicola; Lewith, George; Liu, Jian-Ping

    2015-01-01

    Background Evidence-based medicine promotes and relies on the use of evidence in developing clinical practice guidelines (CPGs). The Chinese healthcare system includes both traditional Chinese medicine (TCM) and Western medicine, which are expected to be equally reflected in Chinese CPGs. Objective To evaluate the inclusion of TCM-related information in Western medicine CPGs developed in China and the adoption of high level evidence. Methods All CPGs were identified from the China Guideline Clearinghouse (CGC), which is the main Chinese organisation maintaining the guidelines issued by the Ministry of Health of China, the Chinese Medical Association and the Chinese Medical Doctors’ Association. TCM-related contents were extracted from all the CPGs identified. Extracted information comprised the institution issuing the guideline, date of issue, disease, recommendations relating to TCM, evidence level of the recommended content and references supporting the recommendations. Results A total of 604 CPGs were identified, only a small number of which (74/604; 12%) recommended TCM therapy and only five guidelines (7%) had applied evidence grading. The 74 CPGs involved 13 disease systems according to the International Classification of Diseases 10th edition. TCM was mainly recommended in the treatment part of the guidelines (73/74, 99%), and more than half of the recommendations (43/74, 58%) were related to Chinese herbal medicine (single herbs or herbal treatment based on syndrome differentiation). Conclusions Few Chinese Western medicine CPGs recommend TCM therapies and very few provide evidence grading for the TCM recommendation. We suggest that future guideline development should be based on systematic searches for evidence to support CPG recommendations and involve a multidisciplinary approach including TCM expertise. PMID:26041487

  9. Is traditional Chinese medicine recommended in Western medicine clinical practice guidelines in China? A systematic analysis.

    PubMed

    Ren, Jun; Li, Xun; Sun, Jin; Han, Mei; Yang, Guo-Yan; Li, Wen-Yuan; Robinson, Nicola; Lewith, George; Liu, Jian-Ping

    2015-06-03

    Evidence-based medicine promotes and relies on the use of evidence in developing clinical practice guidelines (CPGs). The Chinese healthcare system includes both traditional Chinese medicine (TCM) and Western medicine, which are expected to be equally reflected in Chinese CPGs. To evaluate the inclusion of TCM-related information in Western medicine CPGs developed in China and the adoption of high level evidence. All CPGs were identified from the China Guideline Clearinghouse (CGC), which is the main Chinese organisation maintaining the guidelines issued by the Ministry of Health of China, the Chinese Medical Association and the Chinese Medical Doctors' Association.TCM-related contents were extracted from all the CPGs identified. Extracted information comprised the institution issuing the guideline, date of issue, disease, recommendations relating to TCM, evidence level of the recommended content and references supporting the recommendations. A total of 604 CPGs were identified, only a small number of which (74/604; 12%) recommended TCM therapy and only five guidelines (7%) had applied evidence grading. The 74 CPGs involved 13 disease systems according to the International Classification of Diseases 10th edition. TCM was mainly recommended in the treatment part of the guidelines (73/74, 99%), and more than half of the recommendations (43/74, 58%) were related to Chinese herbal medicine (single herbs or herbal treatment based on syndrome differentiation). Few Chinese Western medicine CPGs recommend TCM therapies and very few provide evidence grading for the TCM recommendation. We suggest that future guideline development should be based on systematic searches for evidence to support CPG recommendations and involve a multidisciplinary approach including TCM expertise. Published by the BMJ Publishing Group Limited. For permission to use (where not already granted under a licence) please go to http://group.bmj.com/group/rights-licensing/permissions.

  10. KCNSC Automated RAIL

    DOE Office of Scientific and Technical Information (OSTI.GOV)

    Branson, Donald

    The KCNSC Automated RAIL (Rolling Action Item List) system provides an electronic platform to manage and escalate rolling action items within an business and manufacturing environment at Honeywell. The software enables a tiered approach to issue management where issues are escalated up a management chain based on team input and compared to business metrics. The software manages action items at different levels of the organization and allows all users to discuss action items concurrently. In addition, the software drives accountability through timely emails and proper visibility during team meetings.

  11. Canadian Primary Care Physicians' Attitudes Toward Understanding Clinical Practice Guidelines for Diabetes Screening.

    PubMed

    Alexander, Paul E; Li, Shelly-Anne; Tonelli, Marcello; Guyatt, Gordon

    2016-12-01

    The Canadian Task Force on Preventive Health Care (CTFPHC) produces guidelines for Canadian physicians regarding screening and prevention. To better appreciate the barriers to and facilitators of guideline adherence, we sought to explore physicians' views of guidelines in general and their understanding of this CTFPHC diabetes screening guideline in particular because they pertain to screening and positive treatment. We included Canadian physicians (N=10) who agreed to be interviewed regarding their use of guidelines as part of practice, focusing on the CTFPHC 2012 diabetes screening guideline. Individual semistructured interviews explored primary care physicians' experiences and perspectives on the use, relevance and feasibility of guidelines as part of practice, approaches to screening for diabetes, and suggestions for improving guidelines. Overall, physicians recognized the need for guidelines and the benefits of using Grading of Recommendations Assessment, Development and Evaluation (GRADE) methods in the guideline development process. Physicians also noted several barriers to guideline adherence, including the lack of opportunity for physicians to provide input during guideline formulation, insufficient guidance on interpreting GRADE's weak or conditional recommendations, and feasibility issues concerning using risk calculators. The predominant challenge raised by physicians was the unclear guidance for pharmacologic interventions; all respondents were unclear about the guidelines' implicit assumption that screen-positive patients would be treated with statins and aspirin (ASA). These interviews suggest the need for greater clarity in guideline recommendations, including clarification of the quality of evidence ratings and the strength of recommendation grading. Our low participation rate raises the issue of representativeness; replication in samples with greater willingness to participate would be desirable. Copyright © 2016 Canadian Diabetes Association. Published by Elsevier Inc. All rights reserved.

  12. Canadian physicians' attitudes about and preferences regarding clinical practice guidelines.

    PubMed

    Hayward, R S; Guyatt, G H; Moore, K A; McKibbon, K A; Carter, A O

    1997-06-15

    To assess Canadian physicians' confidence in, attitudes about and preferences regarding clinical practice guidelines. Cross-sectional, self-administered mailed survey. Stratified random sample of 3000 Canadian physicians; 1878 (62.6%) responded. Canada. Physicians' use of various information sources; familiarity with and confidence in guidelines; attitudes about guidelines and their effect on medical care; rating of importance of guidelines and other sources of information in clinical decision-making; rating of importance of various considerations in deciding whether to adopt a set of guidelines; and rating of usefulness of different formats for presenting guidelines. In all, 52% of the respondents reported using guidelines at least monthly, substantially less frequently than traditional information sources. Most of the respondents expressed confidence in guidelines issued by various physician organizations, but 51% to 77% were not confident in guidelines issued by federal or provincial health ministries or by health insurance plans. The respondents were generally positive about guidelines (e.g., over 50% strongly agreed that they are a convenient source of advice and good educational tools); however, 22% to 26% had concerns about loss of autonomy, the rigidity of guidelines and decreased satisfaction with medical practice. Endorsement by respected colleagues or major organizations was identified as very important by 78% and 62% of the respondents respectively in deciding whether to adopt a set of guidelines in their practice. User friendliness of the guidelines format was thought to be very important by 62%; short pamphlets, manuals summarizing a number of guidelines, journal articles and pocket cards summarizing guidelines were the preferred formats (identified as most useful by 50% to 62% of the respondents). Canadian physicians, although generally positive about guidelines and confident in those developed by clinicians, have not yet integrated the use of guidelines into their practices to a large extent. Our results suggest that respected organizations and opinion leaders should be involved in the development of guidelines and that the acceptability of any proposed format and medium for guidelines presentation should be pretested.

  13. Micro sensor node for air pollutant monitoring: hardware and software issues.

    PubMed

    Choi, Sukwon; Kim, Nakyoung; Cha, Hojung; Ha, Rhan

    2009-01-01

    Wireless sensor networks equipped with various gas sensors have been actively used for air quality monitoring. Previous studies have typically explored system issues that include middleware or networking performance, but most research has barely considered the details of the hardware and software of the sensor node itself. In this paper, we focus on the design and implementation of a sensor board for air pollutant monitoring applications. Several hardware and software issues are discussed to explore the possibilities of a practical WSN-based air pollution monitoring system. Through extensive experiments and evaluation, we have determined the various characteristics of the gas sensors and their practical implications for air pollutant monitoring systems.

  14. STGT program: Ada coding and architecture lessons learned

    NASA Technical Reports Server (NTRS)

    Usavage, Paul; Nagurney, Don

    1992-01-01

    STGT (Second TDRSS Ground Terminal) is currently halfway through the System Integration Test phase (Level 4 Testing). To date, many software architecture and Ada language issues have been encountered and solved. This paper, which is the transcript of a presentation at the 3 Dec. meeting, attempts to define these lessons plus others learned regarding software project management and risk management issues, training, performance, reuse, and reliability. Observations are included regarding the use of particular Ada coding constructs, software architecture trade-offs during the prototyping, development and testing stages of the project, and dangers inherent in parallel or concurrent systems, software, hardware, and operations engineering.

  15. What does voice-processing technology support today?

    PubMed Central

    Nakatsu, R; Suzuki, Y

    1995-01-01

    This paper describes the state of the art in applications of voice-processing technologies. In the first part, technologies concerning the implementation of speech recognition and synthesis algorithms are described. Hardware technologies such as microprocessors and DSPs (digital signal processors) are discussed. Software development environment, which is a key technology in developing applications software, ranging from DSP software to support software also is described. In the second part, the state of the art of algorithms from the standpoint of applications is discussed. Several issues concerning evaluation of speech recognition/synthesis algorithms are covered, as well as issues concerning the robustness of algorithms in adverse conditions. Images Fig. 3 PMID:7479720

  16. ICCE Policy Statement on Network and Multiple Machine Software.

    ERIC Educational Resources Information Center

    Computing Teacher, 1983

    1983-01-01

    Issued to provide guidance for the resolution of problems inherent in providing and securing good educational software, this statement outlines responsibilities of educators, hardware vendors, and software developers/vendors. Sample policy statements for school districts and community colleges, suggested format for software licenses, and technical…

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

    ERIC Educational Resources Information Center

    Zuppiroli, Sara; Ciancarini, Paolo; Gabbrielli, Maurizio

    2012-01-01

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

  18. Guidelines for Creating, Implementing, and Evaluating Mind-Body Programs in a Military Healthcare Setting.

    PubMed

    Smith, Katherine; Firth, Kimberly; Smeeding, Sandra; Wolever, Ruth; Kaufman, Joanna; Delgado, Roxana; Bellanti, Dawn; Xenakis, Lea

    2016-01-01

    Research suggests that the development of mind-body skills can improve individual and family resilience, particularly related to the stresses of illness, trauma, and caregiving. To operationalize the research evidence that mind-body skills help with health and recovery, Samueli Institute, in partnership with experts in mind-body programming, created a set of guidelines for developing and evaluating mind-body programs for service members, veterans, and their families. The Guidelines for Creating, Implementing, and Evaluating Mind-Body Programs in a Military Healthcare Setting outline key strategies and issues to consider when developing, implementing, and evaluating a mind-body focused family empowerment approach in a military healthcare setting. Although these guidelines were developed specifically for a military setting, most of the same principles can be applied to the development of programs in the civilian setting as well. The guidelines particularly address issues unique to mind-body programs, such as choosing evidence-based modalities, licensure and credentialing, safety and contraindications, and choosing evaluation measures that capture the holistic nature of these types of programs. The guidelines are practical, practice-based guidelines, developed by experts in the fields of program development and evaluation, mind-body therapies, patient- and family-centered care, as well as, experts in military and veteran's health systems. They provide a flexible framework to create mind-body family empowerment programs and describe important issues that program developers and evaluators are encouraged to address to ensure the development of the most impactful, successful, evidence-supported programs possible. Copyright © 2016 Elsevier Inc. All rights reserved.

  19. Uncovering Student Values for Hiring in the Software Industry

    ERIC Educational Resources Information Center

    Chinn, Donald; Vandegrift, Tammy

    2008-01-01

    This article provides an analysis of student responses to an exercise used in a computer ethics and a software engineering course to raise awareness of issues related to hiring, including issues of professional responsibility and diversity. Students from two different universities were asked to evaluate four candidates for two positions in a…

  20. What Do Computer Science Students Think about Software Piracy?

    ERIC Educational Resources Information Center

    Konstantakis, Nikos I.; Palaigeorgiou, George E.; Siozos, Panos D.; Tsoukalas, Ioannis A.

    2010-01-01

    Today, software piracy is an issue of global importance. Computer science students are the future information and communication technologies professionals and it is important to study the way they approach this issue. In this article, we attempt to study attitudes, behaviours and the corresponding reasoning of computer science students in Greece…

  1. 75 FR 39472 - Airworthiness Directives; Eclipse Aerospace, Inc. Model EA500 Airplanes

    Federal Register 2010, 2011, 2012, 2013, 2014

    2010-07-09

    ..., altitude preselect, and/or transponder codes. We are proposing this AD to correct faulty integration of... determined to be a software communication integration issue between the EFIS display interface and associated... transponder codes. We are issuing this AD to correct faulty integration of hardware and software, which could...

  2. Feasibility of using a knowledge-based system concept for in-flight primary flight display research

    NASA Technical Reports Server (NTRS)

    Ricks, Wendell R.

    1991-01-01

    A study was conducted to determine the feasibility of using knowledge-based systems architectures for inflight research of primary flight display information management issues. The feasibility relied on the ability to integrate knowledge-based systems with existing onboard aircraft systems. And, given the hardware and software platforms available, the feasibility also depended on the ability to use interpreted LISP software with the real time operation of the primary flight display. In addition to evaluating these feasibility issues, the study determined whether the software engineering advantages of knowledge-based systems found for this application in the earlier workstation study extended to the inflight research environment. To study these issues, two integrated knowledge-based systems were designed to control the primary flight display according to pre-existing specifications of an ongoing primary flight display information management research effort. These two systems were implemented to assess the feasibility and software engineering issues listed. Flight test results were successful in showing the feasibility of using knowledge-based systems inflight with actual aircraft data.

  3. Ethical issues in the translation of social neuroscience: a policy analysis of current guidelines for public dialogue in human research.

    PubMed

    Zimmerman, Emma; Racine, Eric

    2012-01-01

    Social neuroscience and its potential implications create an interesting case study for examining human research ethics policies on the topic of public communication of research. We reviewed mainstream national and international human research ethics guidelines and policies on issues of public communication of research. Our analysis relied on five thematic nets to capture the interactions between research and the public: public understanding, knowledge translation, public participation, social outcomes, and dual use. Coverage of these topics is sparse and inconsistent in mainstream policies and guidelines. We identify three options to address these gaps and analyze their strengths and weaknesses.

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

    DOE Office of Scientific and Technical Information (OSTI.GOV)

    Minana, Molly A.; Sturtevant, Judith E.; Heaphy, Robert

    2005-01-01

    The purpose of the Sandia National Laboratories (SNL) Advanced Simulation and Computing (ASC) Software Quality Plan is to clearly identify the practices that are the basis for continually improving the quality of ASC software products. Quality is defined in DOE/AL Quality Criteria (QC-1) as conformance to customer requirements and expectations. This quality plan defines the ASC program software quality practices and provides mappings of these practices to the SNL Corporate Process Requirements (CPR 1.3.2 and CPR 1.3.6) and the Department of Energy (DOE) document, ASCI Software Quality Engineering: Goals, Principles, and Guidelines (GP&G). This quality plan identifies ASC management andmore » software project teams' responsibilities for cost-effective software engineering quality practices. The SNL ASC Software Quality Plan establishes the signatories commitment to improving software products by applying cost-effective software engineering quality practices. This document explains the project teams opportunities for tailoring and implementing the practices; enumerates the practices that compose the development of SNL ASC's software products; and includes a sample assessment checklist that was developed based upon the practices in this document.« less

  5. Ada developers' supplement to the recommended approach

    NASA Technical Reports Server (NTRS)

    Kester, Rush; Landis, Linda

    1993-01-01

    This document is a collection of guidelines for programmers and managers who are responsible for the development of flight dynamics applications in Ada. It is intended to be used in conjunction with the Recommended Approach to Software Development (SEL-81-305), which describes the software development life cycle, its products, reviews, methods, tools, and measures. The Ada Developers' Supplement provides additional detail on such topics as reuse, object-oriented analysis, and object-oriented design.

  6. Guidelines for Applying Video Simulation Technology to Training Land Design

    DTIC Science & Technology

    1993-02-01

    Training Land Design for Realism." The technical monitor was Dr. Victor Diersing, CEHSC-FN. This study was performed by the Environmental Resources...technology to their land management activities. 5 Objective The objective of this study was to provide a general overview of the use of video simulation...4). A market study of currently available hardware and software provided the basis for descriptions of hardware and software systems, and their

  7. Information Interface Related Standards, Guidelines, and Recommended Practices.

    DTIC Science & Technology

    1985-07-01

    Application Workshop, IEEE, October 1984 (11) Software Portability and Standards, by Ingemar Dahlstrand, Ellis Horwood Ltd., 1984 (12) World of EDP...March 29, 1985, p. 42-48 * 9. "IBM’s Topview Plays to Poor Reviews of Early Users," Computer World , March 4, 1985, p. 5 10. "Lack of Software Standards...Information Symbols ISOiTR 7239-1984 - Development and Principles for Application of Public Information Symbols ISO/TR 8545 -1984 - Technical Drawings

  8. Ethics in computer software design and development

    Treesearch

    Alan J. Thomson; Daniel L. Schmoldt

    2001-01-01

    Over the past 20 years, computer software has become integral and commonplace for operational and management tasks throughout agricultural and natural resource disciplines. During this software infusion, however, little thought has been afforded human impacts, both good and bad. This paper examines current ethical issues of software system design and development in...

  9. Guidelines for Management of Incidental Pulmonary Nodules Detected on CT Images: From the Fleischner Society 2017.

    PubMed

    MacMahon, Heber; Naidich, David P; Goo, Jin Mo; Lee, Kyung Soo; Leung, Ann N C; Mayo, John R; Mehta, Atul C; Ohno, Yoshiharu; Powell, Charles A; Prokop, Mathias; Rubin, Geoffrey D; Schaefer-Prokop, Cornelia M; Travis, William D; Van Schil, Paul E; Bankier, Alexander A

    2017-07-01

    The Fleischner Society Guidelines for management of solid nodules were published in 2005, and separate guidelines for subsolid nodules were issued in 2013. Since then, new information has become available; therefore, the guidelines have been revised to reflect current thinking on nodule management. The revised guidelines incorporate several substantive changes that reflect current thinking on the management of small nodules. The minimum threshold size for routine follow-up has been increased, and recommended follow-up intervals are now given as a range rather than as a precise time period to give radiologists, clinicians, and patients greater discretion to accommodate individual risk factors and preferences. The guidelines for solid and subsolid nodules have been combined in one simplified table, and specific recommendations have been included for multiple nodules. These guidelines represent the consensus of the Fleischner Society, and as such, they incorporate the opinions of a multidisciplinary international group of thoracic radiologists, pulmonologists, surgeons, pathologists, and other specialists. Changes from the previous guidelines issued by the Fleischner Society are based on new data and accumulated experience. © RSNA, 2017 Online supplemental material is available for this article. An earlier incorrect version of this article appeared online. This article was corrected on March 13, 2017.

  10. Guidelines for the Productive Employment of Older Adults in Child Care.

    ERIC Educational Resources Information Center

    Newman, Sally M.; And Others

    This publication offers guidelines that policymakers, advocates of children and older adults, and child care practitioners can use to provide older adults with opportunities to work in the child care field. Guidelines that address developmental issues relating to older adults concern employers' sensitivity to older adults and staffing patterns in…

  11. Guidelines for Curriculum Development for Undergraduate Medical Education in the Prevention of Pulmonary Diseases.

    ERIC Educational Resources Information Center

    National Heart, Lung, and Blood Inst. (DHHS/NIH), Bethesda, MD. Div. of Lung Diseases.

    These guidelines for developing an undergraduate medical education curriculum in pulmonary disease prevention emphasize not only the most current scientific practice but also the active application of cognitive and behavioral skills related to patient education. Chapter 1 introduces the guidelines and the issues and trends in preventative…

  12. 41 CFR 102-79.90 - What criteria must Executive agencies consider when evaluating antenna siting requests?

    Code of Federal Regulations, 2010 CFR

    2010-07-01

    ... radiofrequency exposure, ET Docket No. 93-62, entitled “Guidelines for Evaluating the Environmental Effects of Radiofrequency Radiation,” issued August 1, 1996, and any other order on reconsideration relating to radiofrequency guidelines and their enforcement. These are updated guidelines for meeting health concerns that...

  13. Drug Testing Guidelines and Practices for Juvenile Probation and Parole Agencies.

    ERIC Educational Resources Information Center

    American Probation and Parole Association, Lexington, KY.

    This document, intended as a resource manual, provides guidelines on drug testing. These topics are covered: (1) National Institute on Drug Abuse guidelines applicability; (2) introduction to legal issues, drug testing in juvenile probation and parole, and juvenile law; (3) mission of a juvenile parole agency; (4) purpose of testing; (5) drug…

  14. 78 FR 7679 - Income Level for Individuals Eligible for Assistance

    Federal Register 2010, 2011, 2012, 2013, 2014

    2013-02-04

    ... Poverty Guidelines as issued by the Department of Health and Human Services. DATES: Effective date: This... level equivalent to one hundred and twenty-five percent (125%) of the Federal Poverty Guidelines. Since... Federal Poverty Guidelines. The figures for 2013 set out below are equivalent to 125 percent (125%) of the...

  15. The Council for International Organizations and Medical Sciences (CIOMS) guidelines on ethics of clinical trials.

    PubMed

    Macrae, Duncan J

    2007-05-01

    Numerous bodies from many countries, including governments, government regulatory departments, research organizations, medical professional bodies, and health care providers, have issued guidance or legislation on the ethical conduct of clinical trials. It is possible to trace the development of current guidelines back to the post-World War II Nuremburg war crimes trials, more specifically the "Doctors' Trial." From that trial emerged the Nuremburg Code, which set out basic principles to be observed when conducting research involving human subjects and which subsequently formed the basis for comprehensive international guidelines on medical research, such as the Declaration of Helsinki. Most recently, the Council for International Organizations and Medical Sciences (CIOMS) produced detailed guidelines (originally published in 1993 and updated in 2002) on the implementation of the principles outlined in the Declaration of Helsinki. The CIOMS guidelines set in an appropriate context the challenges of present-day clinical research, by addressing complex issues including HIV/AIDS research, availability of study treatments after a study ends, women as research subjects, safeguarding confidentiality, compensation for adverse events, as well guidelines on consent.

  16. DOE Office of Scientific and Technical Information (OSTI.GOV)

    Dr. George L Mesina

    Our ultimate goal is to create and maintain RELAP5-3D as the best software tool available to analyze nuclear power plants. This begins with writing excellent programming and requires thorough testing. This document covers development of RELAP5-3D software, the behavior of the RELAP5-3D program that must be maintained, and code testing. RELAP5-3D must perform in a manner consistent with previous code versions with backward compatibility for the sake of the users. Thus file operations, code termination, input and output must remain consistent in form and content while adding appropriate new files, input and output as new features are developed. As computermore » hardware, operating systems, and other software change, RELAP5-3D must adapt and maintain performance. The code must be thoroughly tested to ensure that it continues to perform robustly on the supported platforms. The coding must be written in a consistent manner that makes the program easy to read to reduce the time and cost of development, maintenance and error resolution. The programming guidelines presented her are intended to institutionalize a consistent way of writing FORTRAN code for the RELAP5-3D computer program that will minimize errors and rework. A common format and organization of program units creates a unifying look and feel to the code. This in turn increases readability and reduces time required for maintenance, development and debugging. It also aids new programmers in reading and understanding the program. Therefore, when undertaking development of the RELAP5-3D computer program, the programmer must write computer code that follows these guidelines. This set of programming guidelines creates a framework of good programming practices, such as initialization, structured programming, and vector-friendly coding. It sets out formatting rules for lines of code, such as indentation, capitalization, spacing, etc. It creates limits on program units, such as subprograms, functions, and modules. It establishes documentation guidance on internal comments. The guidelines apply to both existing and new subprograms. They are written for both FORTRAN 77 and FORTRAN 95. The guidelines are not so rigorous as to inhibit a programmer’s unique style, but do restrict the variations in acceptable coding to create sufficient commonality that new readers will find the coding in each new subroutine familiar. It is recognized that this is a “living” document and must be updated as languages, compilers, and computer hardware and software evolve.« less

  17. • New guidelines for national airline caterers.

    PubMed

    1989-06-24

    The Government is to issue new guidelines to prevent food poisoning from airline meals. The proposed action comes in response to recent survey evidence which found contaminated meals served up to passengers.

  18. Developing clinical practice guidelines: target audiences, identifying topics for guidelines, guideline group composition and functioning and conflicts of interest

    PubMed Central

    2012-01-01

    Clinical practice guidelines are one of the foundations of efforts to improve health care. In 1999, we authored a paper about methods to develop guidelines. Since it was published, the methods of guideline development have progressed both in terms of methods and necessary procedures and the context for guideline development has changed with the emergence of guideline clearing houses and large scale guideline production organisations (such as the UK National Institute for Health and Clinical Excellence). It therefore seems timely to, in a series of three articles, update and extend our earlier paper. In this first paper we discuss: the target audience(s) for guidelines and their use of guidelines; identifying topics for guidelines; guideline group composition (including consumer involvement) and the processes by which guideline groups function and the important procedural issue of managing conflicts of interest in guideline development. PMID:22762776

  19. Developing clinical practice guidelines: target audiences, identifying topics for guidelines, guideline group composition and functioning and conflicts of interest.

    PubMed

    Eccles, Martin P; Grimshaw, Jeremy M; Shekelle, Paul; Schünemann, Holger J; Woolf, Steven

    2012-07-04

    Clinical practice guidelines are one of the foundations of efforts to improve health care. In 1999, we authored a paper about methods to develop guidelines. Since it was published, the methods of guideline development have progressed both in terms of methods and necessary procedures and the context for guideline development has changed with the emergence of guideline clearing houses and large scale guideline production organisations (such as the UK National Institute for Health and Clinical Excellence). It therefore seems timely to, in a series of three articles, update and extend our earlier paper. In this first paper we discuss: the target audience(s) for guidelines and their use of guidelines; identifying topics for guidelines; guideline group composition (including consumer involvement) and the processes by which guideline groups function and the important procedural issue of managing conflicts of interest in guideline development.

  20. Addressing implementation challenges during guideline development - a case study of Swedish national guidelines for methods of preventing disease.

    PubMed

    Richter-Sundberg, Linda; Kardakis, Therese; Weinehall, Lars; Garvare, Rickard; Nyström, Monica E

    2015-01-22

    Many of the world's life threatening diseases (e.g. cancer, heart disease, stroke) could be prevented by eliminating life-style habits such as tobacco use, unhealthy diet, physical inactivity and excessive alcohol use. Incorporating evidence-based research on methods to change unhealthy lifestyle habits in clinical practice would be equally valuable. However gaps between guideline development and implementation are well documented, with implications for health care quality, safety and effectiveness. The development phase of guidelines has been shown to be important both for the quality in guideline content and for the success of implementation. There are, however, indications that guidelines related to general disease prevention methods encounter specific barriers compared to guidelines that are diagnosis-specific. In 2011 the Swedish National board for Health and Welfare launched guidelines with a preventive scope. The aim of this study was to investigate how implementation challenges were addressed during the development process of these disease preventive guidelines. Seven semi-structured interviews were conducted with members of the guideline development management group. Archival data detailing the guideline development process were also collected and used in the analysis. Qualitative data were analysed using content analysis as the analytical framework. The study identified several strategies and approaches that were used to address implementation challenges during guideline development. Four themes emerged from the analysis: broad agreements and consensus about scope and purpose; a formalized and structured development procedure; systematic and active involvement of stakeholders; and openness and transparency in the specific guideline development procedure. Additional factors concerning the scope of prevention and the work environment of guideline developers were perceived to influence the possibilities to address implementation issues. This case study provides examples of how guideline developers perceive and approach the issue of implementation during the development and early launch of prevention guidelines. Models for guideline development could benefit from an initial assessment of how the guideline topic, its target context and stakeholders will affect the upcoming implementation.

  1. SU-E-I-97: Smart Auto-Planning Framework in An EMR Environment (SAFEE)

    DOE Office of Scientific and Technical Information (OSTI.GOV)

    Zhang, B; Chen, S; Mutaf, Y

    2014-06-01

    Purpose: Our Radiation Oncology Department uses clinical practice guidelines for patient treatment, including normal tissue sparing and other dosimetric constraints. These practice guidelines were adapted from national guidelines, clinical trials, literature reviews, and practitioner's own experience. Modern treatment planning systems (TPS) have the capability of incorporating these practice guidelines to automatically create radiation therapy treatment plans with little human intervention. We are developing a software infrastructure to integrate clinical practice guidelines and radiation oncology electronic medical record (EMR) system into radiation therapy treatment planning system (TPS) for auto planning. Methods: Our Smart Auto-Planning Framework in an EMR environment (SAFEE) usesmore » a software pipeline framework to integrate practice guidelines,EMR, and TPS together. The SAFEE system starts with retrieving diagnosis information and physician's prescription from the EMR system. After approval of contouring, SAFEE will automatically create plans according to our guidelines. Based on clinical objectives, SAFEE will automatically select treatment delivery techniques (such as, 3DRT/IMRT/VMAT) and optimize plans. When necessary, SAFEE will create multiple treatment plans with different combinations of parameters. SAFEE's pipeline structure makes it very flexible to integrate various techniques, such as, Model-Base Segmentation (MBS) and plan optimization algorithms, e.g., Multi-Criteria Optimization (MCO). In addition, SAFEE uses machine learning, data mining techniques, and an integrated database to create clinical knowledgebase and then answer clinical questions, such as, how to score plan quality or how volume overlap affects physicians' decision in beam and treatment technique selection. Results: In our institution, we use Varian Aria EMR system and RayStation TPS from RaySearch, whose ScriptService API allows control by external programs. These applications are the building blocks of our SAFEE system. Conclusion: SAFEE is a feasible method of integrating clinical information to develop an auto-planning paradigm to improve clinical workflow in cancer patient care.« less

  2. Review Guidelines for Software Languages for use in Nuclear Power Plant Safety Systems

    DTIC Science & Technology

    1997-10-01

    desirable to segregate base classes from derived classes. Review is facilitated and safety is enhanced if project-specific guidance is provided on the... Segregate base from derived classes. In C++, it is desirable to segregate base classes from derived classes. 4.4.1.8 Minimizing Use of Literals...memory utilization. At the lowest level are base attributes, i.e., attributes xv NUREG/CR-6463 Rev. 1 sufficiently specific to define guidelines. An

  3. The UK water crisis: What actions the government and private sector need to take.

    PubMed

    Skelton, Emmeline

    2015-01-01

    The paper discusses why resilience is increasingly important for companies to measure and address, thinking about relevant issues such as climate change and extreme weather. It gives insight on how companies measure their resilience and that it is more than a business continuity issue; indeed, it is a board issue. The paper looks at the role of regulation for companies with national critical infrastructure in putting in resilience guidelines and discusses the benefits of regulation in resilience, presenting a case study of the UK Water Services Regulation Authority resilience guidelines.

  4. A NASA-wide approach toward cost-effective, high-quality software through reuse

    NASA Technical Reports Server (NTRS)

    Scheper, Charlotte O. (Editor); Smith, Kathryn A. (Editor)

    1993-01-01

    NASA Langley Research Center sponsored the second Workshop on NASA Research in Software Reuse on May 5-6, 1992 at the Research Triangle Park, North Carolina. The workshop was hosted by the Research Triangle Institute. Participants came from the three NASA centers, four NASA contractor companies, two research institutes and the Air Force's Rome Laboratory. The purpose of the workshop was to exchange information on software reuse tool development, particularly with respect to tool needs, requirements, and effectiveness. The participants presented the software reuse activities and tools being developed and used by their individual centers and programs. These programs address a wide range of reuse issues. The group also developed a mission and goals for software reuse within NASA. This publication summarizes the presentations and the issues discussed during the workshop.

  5. Caring for Your Videodiscs, CD-ROM Discs, and Players.

    ERIC Educational Resources Information Center

    Ekhaml, Leticia; Saygan, Bobby

    1993-01-01

    Presents guidelines for the proper care and handling of videodisc and CD-ROM hardware and software. Topics discussed include handling the equipment, moving, cleaning techniques, storage considerations, ventilation requirements, and climate control. (LRW)

  6. Computer Series, 4: Bits, Bytes, Boards, Buses, and Beyond.

    ERIC Educational Resources Information Center

    Gerhold, George; And Others

    1979-01-01

    Presents a general introduction to microprocessors and microcomputers. Guidelines for purchasing software and hardware are intended to familiarize potential buyers with the current equipment on the market and the terminology in use. (SA)

  7. Guidance for Catastrophic Emergency Situations Involving Asbestos

    EPA Pesticide Factsheets

    This document addresses the types of asbestos issues that may arise during catastrophic events and how EPA has addressed such issues. It replaces the Guidelines for Catastrophic Emergency Situations Involving Asbestos which was issued in 1992.

  8. Software Library: A Reusable Software Issue.

    DTIC Science & Technology

    1984-06-01

    On reverse aide it neceeary aid Identify by block number) Software Library; Program Library; Reusability; Generator 20 ABSTRACT (Cmlnue on revere... Software Library. A particular example of the Software Library, the Program Library, is described as a prototype of a reusable library. A hierarchical... programming libraries are described. Finally, non code products in the Software Library are discussed. Accesson Fo NTIS R~jS DrrC TA Availability Codes 0

  9. The cost of software fault tolerance

    NASA Technical Reports Server (NTRS)

    Migneault, G. E.

    1982-01-01

    The proposed use of software fault tolerance techniques as a means of reducing software costs in avionics and as a means of addressing the issue of system unreliability due to faults in software is examined. A model is developed to provide a view of the relationships among cost, redundancy, and reliability which suggests strategies for software development and maintenance which are not conventional.

  10. WISE: Automated support for software project management and measurement. M.S. Thesis

    NASA Technical Reports Server (NTRS)

    Ramakrishnan, Sudhakar

    1995-01-01

    One important aspect of software development and IV&V is measurement. Unless a software development effort is measured in some way, it is difficult to judge the effectiveness of current efforts and predict future performances. Collection of metrics and adherence to a process are difficult tasks in a software project. Change activity is a powerful indicator of project status. Automated systems that can handle change requests, issues, and other process documents provide an excellent platform for tracking the status of the project. A World Wide Web based architecture is developed for (a) making metrics collection an implicit part of the software process, (b) providing metric analysis dynamically, (c) supporting automated tools that can complement current practices of in-process improvement, and (d) overcoming geographical barrier. An operational system (WISE) instantiates this architecture allowing for the improvement of software process in a realistic environment. The tool tracks issues in software development process, provides informal communication between the users with different roles, supports to-do lists (TDL), and helps in software process improvement. WISE minimizes the time devoted to metrics collection, analysis, and captures software change data. Automated tools like WISE focus on understanding and managing the software process. The goal is improvement through measurement.

  11. Personalized Guideline-Based Treatment Recommendations Using Natural Language Processing Techniques.

    PubMed

    Becker, Matthias; Böckmann, Britta

    2017-01-01

    Clinical guidelines and clinical pathways are accepted and proven instruments for quality assurance and process optimization. Today, electronic representation of clinical guidelines exists as unstructured text, but is not well-integrated with patient-specific information from electronic health records. Consequently, generic content of the clinical guidelines is accessible, but it is not possible to visualize the position of the patient on the clinical pathway, decision support cannot be provided by personalized guidelines for the next treatment step. The Systematized Nomenclature of Medicine - Clinical Terms (SNOMED CT) provides common reference terminology as well as the semantic link for combining the pathways and the patient-specific information. This paper proposes a model-based approach to support the development of guideline-compliant pathways combined with patient-specific structured and unstructured information using SNOMED CT. To identify SNOMED CT concepts, a software was developed to extract SNOMED CT codes out of structured and unstructured German data to map these with clinical pathways annotated in accordance with the systematized nomenclature.

  12. Measure Guideline. Transitioning to a Tankless Water Heater

    DOE Office of Scientific and Technical Information (OSTI.GOV)

    Brozyna, K.; Rapport, A.

    2012-09-01

    This measure guideline provides information to help residential builders and retrofitters with the design, specification, selection, implementation, installation, and maintenance issues of transitioning from tank-type water heaters to tankless water heaters.

  13. Adopting Open Source Software to Address Software Risks during the Scientific Data Life Cycle

    NASA Astrophysics Data System (ADS)

    Vinay, S.; Downs, R. R.

    2012-12-01

    Software enables the creation, management, storage, distribution, discovery, and use of scientific data throughout the data lifecycle. However, the capabilities offered by software also present risks for the stewardship of scientific data, since future access to digital data is dependent on the use of software. From operating systems to applications for analyzing data, the dependence of data on software presents challenges for the stewardship of scientific data. Adopting open source software provides opportunities to address some of the proprietary risks of data dependence on software. For example, in some cases, open source software can be deployed to avoid licensing restrictions for using, modifying, and transferring proprietary software. The availability of the source code of open source software also enables the inclusion of modifications, which may be contributed by various community members who are addressing similar issues. Likewise, an active community that is maintaining open source software can be a valuable source of help, providing an opportunity to collaborate to address common issues facing adopters. As part of the effort to meet the challenges of software dependence for scientific data stewardship, risks from software dependence have been identified that exist during various times of the data lifecycle. The identification of these risks should enable the development of plans for mitigating software dependencies, where applicable, using open source software, and to improve understanding of software dependency risks for scientific data and how they can be reduced during the data life cycle.

  14. Current husbandry of red pandas (Ailurus fulgens) in zoos.

    PubMed

    Eriksson, P; Zidar, J; White, D; Westander, J; Andersson, M

    2010-01-01

    The endangered red panda (Ailurus fulgens) is held in zoos worldwide. The aim of this study was to examine how red pandas are kept and managed in captivity and to compare it with the management guidelines. Sixty-nine zoos, mainly from Europe but also from North America and Australia/New Zealand, responded to our survey. The results revealed that in general zoos follow the management guidelines for most of the investigated issues. The average enclosure is almost four times larger than the minimum size recommended by the management guidelines, although seven zoos have smaller enclosures. About half the zoos do not follow the guidelines concerning visitor access and number of nest boxes. Other issues that may compromise animal welfare include proximity of neighboring carnivore species and placement of nest boxes. © 2010 Wiley-Liss, Inc.

  15. Design and Implementation of a C++ Software Package to scan for and parse Tsunami Messages issued by the Tsunami Warning Centers for Operational use at the Pacific Tsunami Warning Center

    NASA Astrophysics Data System (ADS)

    Sardina, V.

    2012-12-01

    The US Tsunami Warning Centers (TWCs) have traditionally generated their tsunami message products primarily as blocks of text then tagged with headers that identify them on each particular communications' (comms) circuit. Each warning center has a primary area of responsibility (AOR) within which it has an authoritative role regarding parameters such as earthquake location and magnitude. This means that when a major tsunamigenic event occurs the other warning centers need to quickly access the earthquake parameters issued by the authoritative warning center before issuing their message products intended for customers in their own AOR. Thus, within the operational context of the TWCs the scientists on duty have an operational need to access the information contained in the message products issued by other warning centers as quickly as possible. As a solution to this operational problem we designed and implemented a C++ software package that allows scanning for and parsing the entire suite of tsunami message products issued by the Pacific Tsunami Warning Center (PTWC), the West Coast and Alaska Tsunami Warning Center (WCATWC), and the Japan Meteorological Agency (JMA). The scanning and parsing classes composing the resulting C++ software package allow parsing both non-official message products(observatory messages) routinely issued by the TWCs, and all official tsunami message products such as tsunami advisories, watches, and warnings. This software package currently allows scientists on duty at the PTWC to automatically retrieve the parameters contained in tsunami messages issued by WCATWC, JMA, or PTWC itself. Extension of the capabilities of the classes composing the software package would make it possible to generate XML and CAP compliant versions of the TWCs' message products until new messaging software natively adds this capabilities. Customers who receive the TWCs' tsunami message products could also use the package to automatically retrieve information from messages sent via any text-based communications' circuit currently used by the TWCs to disseminate their tsunami message products.

  16. Legal and ethical issues in research.

    PubMed

    Yip, Camille; Han, Nian-Lin Reena; Sng, Ban Leong

    2016-09-01

    Legal and ethical issues form an important component of modern research, related to the subject and researcher. This article seeks to briefly review the various international guidelines and regulations that exist on issues related to informed consent, confidentiality, providing incentives and various forms of research misconduct. Relevant original publications (The Declaration of Helsinki, Belmont Report, Council for International Organisations of Medical Sciences/World Health Organisation International Guidelines for Biomedical Research Involving Human Subjects, World Association of Medical Editors Recommendations on Publication Ethics Policies, International Committee of Medical Journal Editors, CoSE White Paper, International Conference on Harmonisation of Technical Requirements for Registration of Pharmaceuticals for Human Use-Good Clinical Practice) form the literature that are relevant to the ethical and legal aspects of conducting research that researchers should abide by when conducting translational and clinical research. Researchers should note the major international guidelines and regional differences in legislation. Hence, specific ethical advice should be sought at local Ethics Review Committees.

  17. Increasing Interest, Confidence and Understanding of Ethical Issues in Science through Case-Based Instructional Technology.

    ERIC Educational Resources Information Center

    Lundeberg, Mary A.; Bergland, Mark; Klyczek, Karen; Mogen, Kim; Johnson, Doug; Harmes, Nina

    Software designed to promote the use of open-ended investigations in science education was evaluated in a study of whether using case-based simulation enhances students' understanding of ethical issues and data interpretation in science. The software was a DNA gel electrophoresis simulation that enabled students to conduct simulated genetic tests.…

  18. The Issue of (Software) Plagiarism: A Student View

    ERIC Educational Resources Information Center

    Chuda, D.; Navrat, P.; Kovacova, B.; Humay, P.

    2012-01-01

    The issue of plagiarism is discussed in the context of university education in disciplines related to computing. The focus is therefore mainly on software plagiarism. First, however, a case is made for the claim that the most important reason that plagiarism cannot be tolerated lies in the essence of the concept of a university as it is rooted in…

  19. Developing Open Source Software To Advance High End Computing. Report to the President.

    ERIC Educational Resources Information Center

    National Coordination Office for Information Technology Research and Development, Arlington, VA.

    This is part of a series of reports to the President and Congress developed by the President's Information Technology Advisory Committee (PITAC) on key contemporary issues in information technology. This report defines open source software, explains PITAC's interest in this model, describes the process used to investigate issues in open source…

  20. Current Strategies for Managing Providers Infected with Bloodborne Pathogens

    PubMed Central

    Turkel, Sarah; Henderson, David K.

    2016-01-01

    Background In 1991 CDC issued guidelines to reduce risks for provider-to-patient transmission of bloodborne pathogens. These guidelines, unchanged since 1991, recommend management strategies for hepatitis B ‘e’ antigen-positive providers and for providers infected with human immunodeficiency virus (HIV); they do not address hepatitis-C-virus (HCV)-infected providers. Objective We summarize current state practices and surveyed state health departments to determine: 1) if state policies have been modified since 1991; 2), if state laws require prospective notification of patients and/or expert review panels to manage infected providers; 3) the frequency with which infected-providers issues come to the attention of state health departments; and 4) how state health departments intervene. Methods We reviewed all 50 states’ laws and guidelines to determine current practices and conducted a structured telephone survey of all state health departments. Results Whereas only 19 states require infected providers to notify patients of the providers’ bloodborne pathogen infection, these 19 states require notification under highly varied circumstances. Only ten of 50 state health department officials identified these issues as requiring significant departmental effort. No state law or guideline incorporates information about providers’ viral burdens as part of the risk assessment. Only 3/50 States have modified policies or laws since initial passage; and only 1/50 discusses the management of HCV-infected providers.. Conclusions These results identify a need for incorporating contemporary scientific information into guidelines and also suggest that infected-provider issues are not occurring commonly, are not being detected, or that they are being managed at levels below the state health department. PMID:21515972

  1. National origin harassment in the work place: recent guideline developments from the EEOC.

    PubMed

    Hollon, C J; Bright, T L

    1982-01-01

    In December 1980 the EEOC published its revised "Guidelines on Discrimination Because of National Origin." The revised guidelines expand the definition of national origin harassment and declare it a violation of Title Vii. According to the EEOC, the guidelines reaffirm the position the Commission has taken in earlier decisions. In the following article, the authors examine the EEOC's position on national origin harassment. Using the guidelines as a frame of reference, they look at both EEOC decisions issued prior to the guidelines and court decisions that may offer employers guidance regarding impermissible conduct and liability in this area.

  2. Navy Stock Point Local Unique Computer Programs: An Analysis for Transition and Management Under the Stock Point ADP Replacement (SPAR) Project.

    DTIC Science & Technology

    1987-03-01

    Project (SPAR). An impor- tant issue of the replacement will be the conversion of existing co uter software to allow transition from the current... issue of the replacement will be the conversion of existing computer software to allow transition from the current hardware environment to the replacement...36 G. LOCAL PROGRAM C1/C2 CONVERSION CONTRACT . . . 38 5 H. LOCAL PROGRAM COMMONALITY ISSUES ....... 41 I. SUMMARY

  3. Potential toxic effects of aircraft de-icers and wastewater samples containing these compounds.

    PubMed

    Mohiley, A; Franzaring, J; Calvo, O C; Fangmeier, A

    2015-09-01

    One of the major problems of airport operation is the impact of pollution caused by runoff waters. Runoff waters at an airport may contain high concentrations of different contaminants resulting from various activities of its operation. High quantities of aircraft de-icing/anti-icing fluids are used annually at airports worldwide. Aircraft de-icers and anti-icers may have negative environmental impacts, but their effects on aquatic organisms are virtually unknown. In order to address this issue, aircraft de-icers, pavement de-icers and wastewater samples were obtained from a regional airport. To evaluate the toxicity of wastewater samples and aircraft de-icing/anti-icing fluids (ADAFs), two bio-tests were performed: the Lemna growth inhibition test according to OECD guideline 221 and the luminescent bacteria test according to ISO guideline 11348-2. In the Lemna growth inhibition test, phytotoxicity was assessed using the endpoints frond number and frond area. The luminescent bacteria test involved the marine bacterium Vibrio fischeri. The estimates of effective concentrations (EC50) values were determined using the free software R and the "drc" library. Aquatic plants and marine bacteria showed a higher sensitivity towards ADAFs than to wastewater samples. Experiments showed that aircraft de-icing/anti-icing fluids and wastewater samples were relatively more toxic towards Lemna gibba L. in comparison to V. fischeri.

  4. Strategies for Involvement in Wildlife Issues.

    ERIC Educational Resources Information Center

    Kennedy, Carolyn L.; Nye, Donna I.

    1984-01-01

    Highlights a workshop with children focusing on the treatment of controversial issues and guidelines typically provided by school districts or organizations. Activities designed to stimulate discussion on three issues (endangered species, acid rain, and predator control) are included. (BC)

  5. Copyright and the Assurance of Quality Courseware.

    ERIC Educational Resources Information Center

    Helm, Virginia M.

    Issues related to the illegal copying or piracy of educational software in the schools and its potential effect on quality software availability are discussed. Copyright violation is examined as a reason some software producers may be abandoning the school software market. An explanation of what the copyright allows and prohibits in terms of…

  6. 78 FR 47012 - Developing Software Life Cycle Processes Used in Safety Systems of Nuclear Power Plants

    Federal Register 2010, 2011, 2012, 2013, 2014

    2013-08-02

    ... NUCLEAR REGULATORY COMMISSION [NRC-2012-0195] Developing Software Life Cycle Processes Used in... revised regulatory guide (RG), revision 1 of RG 1.173, ``Developing Software Life Cycle Processes for... Developing a Software Project Life Cycle Process,'' issued 2006, with the clarifications and exceptions as...

  7. Blended Training on Scientific Software: A Study on How Scientific Data Are Generated

    ERIC Educational Resources Information Center

    Skordaki, Efrosyni-Maria; Bainbridge, Susan

    2018-01-01

    This paper presents the results of a research study on scientific software training in blended learning environments. The investigation focused on training approaches followed by scientific software users whose goal is the reliable application of such software. A key issue in current literature is the requirement for a theory-substantiated…

  8. 76 FR 66350 - Eighteenth Meeting: RTCA Special Committee 205/EUROCAE WG-71: Software Considerations in...

    Federal Register 2010, 2011, 2012, 2013, 2014

    2011-10-26

    ... Committee 205/EUROCAE WG-71: Software Considerations in Aeronautical Systems AGENCY: Federal Aviation.../EUROCAE WG-71 meeting: Software Considerations in Aeronautical Systems. SUMMARY: The FAA is issuing this notice to advise the public of a meeting of RTCA Special Committee 205/EUROCAE WG-71: Software...

  9. Title VII Sexual Harassment Guidelines and Educational Employment [and] What Can Students Do About Sex Discrimination?

    ERIC Educational Resources Information Center

    Howard, Susan; And Others

    Guidelines concerning sexual harassment of employees at educational institutions under Title VII of the Civil Rights Act of 1964 are considered. November 1980 final interpretive guidelines issued by the Equal Employment Opportunity Commission state that Title VII prohibits sexual harassment of employees, that employers are responsible for the…

  10. 48 CFR 47.403 - Guidelines for implementation of the Fly America Act.

    Code of Federal Regulations, 2014 CFR

    2014-10-01

    ... implementation of the Fly America Act. 47.403 Section 47.403 Federal Acquisition Regulations System FEDERAL... Guidelines for implementation of the Fly America Act. This section 47.403 is based on the Guidelines for Implementation of the Fly America Act (case number B-138942), issued by the Comptroller General of the United...

  11. 48 CFR 47.403 - Guidelines for implementation of the Fly America Act.

    Code of Federal Regulations, 2011 CFR

    2011-10-01

    ... implementation of the Fly America Act. 47.403 Section 47.403 Federal Acquisition Regulations System FEDERAL... Guidelines for implementation of the Fly America Act. This section 47.403 is based on the Guidelines for Implementation of the Fly America Act (case number B-138942), issued by the Comptroller General of the United...

  12. 48 CFR 47.403 - Guidelines for implementation of the Fly America Act.

    Code of Federal Regulations, 2012 CFR

    2012-10-01

    ... implementation of the Fly America Act. 47.403 Section 47.403 Federal Acquisition Regulations System FEDERAL... Guidelines for implementation of the Fly America Act. This section 47.403 is based on the Guidelines for Implementation of the Fly America Act (case number B-138942), issued by the Comptroller General of the United...

  13. 48 CFR 47.403 - Guidelines for implementation of the Fly America Act.

    Code of Federal Regulations, 2013 CFR

    2013-10-01

    ... implementation of the Fly America Act. 47.403 Section 47.403 Federal Acquisition Regulations System FEDERAL... Guidelines for implementation of the Fly America Act. This section 47.403 is based on the Guidelines for Implementation of the Fly America Act (case number B-138942), issued by the Comptroller General of the United...

  14. Product Engineering Class in the Software Safety Risk Taxonomy for Building Safety-Critical Systems

    NASA Technical Reports Server (NTRS)

    Hill, Janice; Victor, Daniel

    2008-01-01

    When software safety requirements are imposed on legacy safety-critical systems, retrospective safety cases need to be formulated as part of recertifying the systems for further use and risks must be documented and managed to give confidence for reusing the systems. The SEJ Software Development Risk Taxonomy [4] focuses on general software development issues. It does not, however, cover all the safety risks. The Software Safety Risk Taxonomy [8] was developed which provides a construct for eliciting and categorizing software safety risks in a straightforward manner. In this paper, we present extended work on the taxonomy for safety that incorporates the additional issues inherent in the development and maintenance of safety-critical systems with software. An instrument called a Software Safety Risk Taxonomy Based Questionnaire (TBQ) is generated containing questions addressing each safety attribute in the Software Safety Risk Taxonomy. Software safety risks are surfaced using the new TBQ and then analyzed. In this paper we give the definitions for the specialized Product Engineering Class within the Software Safety Risk Taxonomy. At the end of the paper, we present the tool known as the 'Legacy Systems Risk Database Tool' that is used to collect and analyze the data required to show traceability to a particular safety standard

  15. Challenges of Implementing Free and Open Source Software (FOSS): Evidence from the Indian Educational Setting

    ERIC Educational Resources Information Center

    Thankachan, Briju; Moore, David Richard

    2017-01-01

    The use of Free and Open Source Software (FOSS), a subset of Information and Communication Technology (ICT), can reduce the cost of purchasing software. Despite the benefit in the initial purchase price of software, deploying software requires total cost that goes beyond the initial purchase price. Total cost is a silent issue of FOSS and can only…

  16. A cognitive operating system (COGNOSYS) for JPL's robot, phase 1 report

    NASA Technical Reports Server (NTRS)

    Mathur, F. P.

    1972-01-01

    The most important software requirement for any robot development is the COGNitive Operating SYStem (COGNOSYS). This report describes the Stanford University Artificial Intelligence Laboratory's hand eye software system from the point of view of developing a cognitive operating system for JPL's robot. In this, the Phase 1 of the JPL robot COGNOSYS task the installation of a SAIL compiler and a FAIL assembler on Caltech's PDP-10 have been accomplished and guidelines have been prepared for the implementation of a Stanford University type hand eye software system on JPL-Caltech's computing facility. The alternatives offered by using RAND-USC's PDP-10 Tenex operating sytem are also considered.

  17. Requirements UML Tool (RUT) Expanded for Extreme Programming (CI02)

    NASA Technical Reports Server (NTRS)

    McCoy, James R.

    2003-01-01

    A procedure for capturing and managing system requirements that incorporates XP user stories. Because costs associated with identifying problems in requirements increase dramatically over the lifecycle of a project, a method for identifying sources of software risks in user stories is urgently needed. This initiative aims to determine a set of guide-lines for user stories that will result in high-quality requirement. To further this initiative, a tool is needed to analyze user stories that can assess the quality of individual user stories, detect sources cf software risk's, produce software metrics, and identify areas in user stories that can be improved.

  18. Simulation verification techniques study. Subsystem simulation validation techniques

    NASA Technical Reports Server (NTRS)

    Duncan, L. M.; Reddell, J. P.; Schoonmaker, P. B.

    1974-01-01

    Techniques for validation of software modules which simulate spacecraft onboard systems are discussed. An overview of the simulation software hierarchy for a shuttle mission simulator is provided. A set of guidelines for the identification of subsystem/module performance parameters and critical performance parameters are presented. Various sources of reference data to serve as standards of performance for simulation validation are identified. Environment, crew station, vehicle configuration, and vehicle dynamics simulation software are briefly discussed from the point of view of their interfaces with subsystem simulation modules. A detailed presentation of results in the area of vehicle subsystems simulation modules is included. A list of references, conclusions and recommendations are also given.

  19. Diabetes and end of life: ethical and methodological issues in gathering evidence to guide care.

    PubMed

    Dunning, Trisha; Duggan, Nicole; Savage, Sally; Martin, Peter

    2013-03-01

    Providing palliative care for people with diabetes at the end of life is part of the chronic disease care trajectory, but end of life care is complex and the presence of diabetes further complicates management. The aim of the paper is to discuss the ethical and methodological issues encountered when undertaking research to develop guidelines for managing diabetes at the end of life and the strategies used to address the issues. The issues emerged as we developed guidelines for managing diabetes at the end of life, which included conducting individual interviews with 14 people with diabetes requiring palliative care and 10 family members. A reflexive researcher journal was maintained throughout the guideline development process. The interview transcripts and researcher's journal were analysed to determine key methodological, ethical and researcher-related issues. Key themes were vulnerability of the sampling population, methodological issues included recruiting participants and ensuring rigor, ethical issues concerned benefit and risk, justice, autonomy, privacy, professional boundaries and informed consent. Researcher-related issues were identified such as managing participant distress and their own emotional distress. People were willing to discuss end of life diabetes management preferences. Undertaking research with people at the end of life is complex because of their vulnerability and the ethical issues involved. However, the ethical principles of autonomy and justice apply and people should be given the relevant information and opportunity to decide whether to participate or not. © 2012 The Authors. Scandinavian Journal of Caring Sciences © 2012 Nordic College of Caring Science.

  20. Strategy Guideline. Modeling Enclosure Design in Above-Grade Walls

    DOE Office of Scientific and Technical Information (OSTI.GOV)

    J. Lstiburek; Ueno, K.; Musunuru, S.

    2016-02-01

    The Strategy Guideline, written by the U.S. Department of Energy's research team Building Science Corporation, 1) describes how to model and interpret results of models for above-grade walls, and 2) 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 (Wärme und Feuchte instationär) software models. The information is generalized for application to a broad population of houses within the limits of existing experience.

  1. Integrating the Master of Software Assurance Reference Curriculum into the Model Curriculum and Guidelines for Graduate Degree Programs in Information Systems

    DTIC Science & Technology

    2011-02-01

    Model Curriculum and Guidelines for Graduate Degree Programs in Information Systems (MSIS) 2006 is the latest product of a project that has been...conducted for nearly 40 years [Gor- gone 2006]. Various organizations affiliated with the project have developed specifications for the teaching of...considerations helps ensure that an institution’s individual courses of study are relevant to the industry that its students are preparing to enter

  2. Canadian physicians' attitudes about and preferences regarding clinical practice guidelines

    PubMed Central

    Hayward, R S; Guyatt, G H; Moore, K A; McKibbon, K A; Carter, A O

    1997-01-01

    OBJECTIVE: To assess Canadian physicians' confidence in, attitudes about and preferences regarding clinical practice guidelines. DESIGN: Cross-sectional, self-administered mailed survey. PARTICIPANTS: Stratified random sample of 3000 Canadian physicians; 1878 (62.6%) responded. SETTING: Canada. OUTCOME MEASURES: Physicians' use of various information sources; familiarity with and confidence in guidelines; attitudes about guidelines and their effect on medical care; rating of importance of guidelines and other sources of information in clinical decision-making; rating of importance of various considerations in deciding whether to adopt a set of guidelines; and rating of usefulness of different formats for presenting guidelines. MAIN RESULTS: In all, 52% of the respondents reported using guidelines at least monthly, substantially less frequently than traditional information sources. Most of the respondents expressed confidence in guidelines issued by various physician organizations, but 51% to 77% were not confident in guidelines issued by federal or provincial health ministries or by health insurance plans. The respondents were generally positive about guidelines (e.g., over 50% strongly agreed that they are a convenient source of advice and good educational tools); however, 22% to 26% had concerns about loss of autonomy, the rigidity of guidelines and decreased satisfaction with medical practice. Endorsement by respected colleagues or major organizations was identified as very important by 78% and 62% of the respondents respectively in deciding whether to adopt a set of guidelines in their practice. User friendliness of the guidelines format was thought to be very important by 62%; short pamphlets, manuals summarizing a number of guidelines, journal articles and pocket cards summarizing guidelines were the preferred formats (identified as most useful by 50% to 62% of the respondents). CONCLUSIONS: Canadian physicians, although generally positive about guidelines and confident in those developed by clinicians, have not yet integrated the use of guidelines into their practices to a large extent. Our results suggest that respected organizations and opinion leaders should be involved in the development of guidelines and that the acceptability of any proposed format and medium for guidelines presentation should be pretested. PMID:9220923

  3. Knowledge-based verification of clinical guidelines by detection of anomalies.

    PubMed

    Duftschmid, G; Miksch, S

    2001-04-01

    As shown in numerous studies, a significant part of published clinical guidelines is tainted with different types of semantical errors that interfere with their practical application. The adaptation of generic guidelines, necessitated by circumstances such as resource limitations within the applying organization or unexpected events arising in the course of patient care, further promotes the introduction of defects. Still, most current approaches for the automation of clinical guidelines are lacking mechanisms, which check the overall correctness of their output. In the domain of software engineering in general and in the domain of knowledge-based systems (KBS) in particular, a common strategy to examine a system for potential defects consists in its verification. The focus of this work is to present an approach, which helps to ensure the semantical correctness of clinical guidelines in a three-step process. We use a particular guideline specification language called Asbru to demonstrate our verification mechanism. A scenario-based evaluation of our method is provided based on a guideline for the artificial ventilation of newborn infants. The described approach is kept sufficiently general in order to allow its application to several other guideline representation formats.

  4. Guidelines for establishing and maintaining construction quality databases.

    DOT National Transportation Integrated Search

    2006-11-01

    The main objective of this study was to develop and present guidelines for State highway agencies (SHAs) in establishing and maintaining database systems geared towards construction quality issues for asphalt and concrete paving projects. To accompli...

  5. Investigation of user stereotypes and preferences

    DOT National Transportation Integrated Search

    1999-12-01

    The presentation of in-vehicle information to the driver is an important issue for highway safety. A review of the guideline literature revealed that although attempts have been made to develop guidelines for in-vehicle information systems, few guide...

  6. New EPA Guidelines for Review of Surface Coal Mining Operations in Appalachia (released in AEO2010)

    EIA Publications

    2010-01-01

    On April 1, 2010, the Environmental Protection Agency (EPA) issued a set of new guidelines to several of its Regional offices regarding the compliance of surface coal mining operations in Appalachia with the provisions of the Clean Water Act (CWA), the National Environmental Policy Act, and the environmental justice Executive Order (E.O. 12898). The stated purpose of the guidance was to explain more fully the approach that the EPA will be following in permit reviews, and to provide additional assurance that its Regional offices use clear, consistent, and science-based standards in reviewing the permits. Although the new guidelines go into effect immediately, they will be subjected to review both by the public and by the EPA's Science Advisory Board, with a set of final guidelines to be issued no later than April 1, 2011.

  7. Whole-slide imaging: routine pathologic diagnosis.

    PubMed

    Cornish, Toby C; Swapp, Ryan E; Kaplan, Keith J

    2012-05-01

    Digital pathology systems offer pathologists an alternate, emerging mechanism to manage and interpret information. They offer increasingly fast and scalable hardware platforms for slide scanning and software that facilitates remote viewing, slide conferencing, archiving, and image analysis. Deployed initially and validated largely within the research and biopharmaceutical industries, WSI is increasingly being implemented for direct patient care. Improvements in image quality, scan times, and imageviewing browsers will hopefully allow pathologists to more seamlessly convert to digital pathology, much like our radiology colleagues have done before us. However, WSI creates both opportunities and challenges. Although niche applications of WSI technology for clinical, educational, and research purposes are clearly successful, it is evident that several areas still require attention and careful consideration before more widespread clinical adoption of WSI takes place. These include regulatory issues, development of standards of practice and validation guidelines, workflow modifications, as well as defining situations where WSI technology will really improve practice in a cost-effective way. Current progress on these and other issues, along with improving technology, will no doubt pave the way for increased adoption over the next decade, allowing the pathology community as a whole to harness the true potential of WSI for patient care. The digital decade will likely redefine how pathology is practiced and the role of the pathologist.

  8. Implementation Issues of Adaptive Energy Detection in Heterogeneous Wireless Networks

    PubMed Central

    Sobron, Iker; Eizmendi, Iñaki; Martins, Wallace A.; Diniz, Paulo S. R.; Ordiales, Juan Luis; Velez, Manuel

    2017-01-01

    Spectrum sensing (SS) enables the coexistence of non-coordinated heterogeneous wireless systems operating in the same band. Due to its computational simplicity, energy detection (ED) technique has been widespread employed in SS applications; nonetheless, the conventional ED may be unreliable under environmental impairments, justifying the use of ED-based variants. Assessing ED algorithms from theoretical and simulation viewpoints relies on several assumptions and simplifications which, eventually, lead to conclusions that do not necessarily meet the requirements imposed by real propagation environments. This work addresses those problems by dealing with practical implementation issues of adaptive least mean square (LMS)-based ED algorithms. The paper proposes a new adaptive ED algorithm that uses a variable step-size guaranteeing the LMS convergence in time-varying environments. Several implementation guidelines are provided and, additionally, an empirical assessment and validation with a software defined radio-based hardware is carried out. Experimental results show good performance in terms of probabilities of detection (Pd>0.9) and false alarm (Pf∼0.05) in a range of low signal-to-noise ratios around [-4,1] dB, in both single-node and cooperative modes. The proposed sensing methodology enables a seamless monitoring of the radio electromagnetic spectrum in order to provide band occupancy information for an efficient usage among several wireless communications systems. PMID:28441751

  9. Comparative assessment of bioanalytical method validation guidelines for pharmaceutical industry.

    PubMed

    Kadian, Naveen; Raju, Kanumuri Siva Rama; Rashid, Mamunur; Malik, Mohd Yaseen; Taneja, Isha; Wahajuddin, Muhammad

    2016-07-15

    The concepts, importance, and application of bioanalytical method validation have been discussed for a long time and validation of bioanalytical methods is widely accepted as pivotal before they are taken into routine use. United States Food and Drug Administration (USFDA) guidelines issued in 2001 have been referred for every guideline released ever since; may it be European Medical Agency (EMA) Europe, National Health Surveillance Agency (ANVISA) Brazil, Ministry of Health and Labour Welfare (MHLW) Japan or any other guideline in reference to bioanalytical method validation. After 12 years, USFDA released its new draft guideline for comments in 2013, which covers the latest parameters or topics encountered in bioanalytical method validation and approached towards the harmonization of bioanalytical method validation across the globe. Even though the regulatory agencies have general agreement, significant variations exist in acceptance criteria and methodology. The present review highlights the variations, similarities and comparison between bioanalytical method validation guidelines issued by major regulatory authorities worldwide. Additionally, other evaluation parameters such as matrix effect, incurred sample reanalysis including other stability aspects have been discussed to provide an ease of access for designing a bioanalytical method and its validation complying with the majority of drug authority guidelines. Copyright © 2016. Published by Elsevier B.V.

  10. Design Considerations in Development of a Mobile Health Intervention Program: The TEXT ME and TEXTMEDS Experience

    PubMed Central

    Thakkar, Jay; Barry, Tony; Thiagalingam, Aravinda; Redfern, Julie; McEwan, Alistair L; Rodgers, Anthony

    2016-01-01

    Background Mobile health (mHealth) has huge potential to deliver preventative health services. However, there is paucity of literature on theoretical constructs, technical, practical, and regulatory considerations that enable delivery of such services. Objectives The objective of this study was to outline the key considerations in the development of a text message-based mHealth program; thus providing broad recommendations and guidance to future researchers designing similar programs. Methods We describe the key considerations in designing the intervention with respect to functionality, technical infrastructure, data management, software components, regulatory requirements, and operationalization. We also illustrate some of the potential issues and decision points utilizing our experience of developing text message (short message service, SMS) management systems to support 2 large randomized controlled trials: TEXT messages to improve MEDication adherence & Secondary prevention (TEXTMEDS) and Tobacco, EXercise and dieT MEssages (TEXT ME). Results The steps identified in the development process were: (1) background research and development of the text message bank based on scientific evidence and disease-specific guidelines, (2) pilot testing with target audience and incorporating feedback, (3) software-hardware customization to enable delivery of complex personalized programs using prespecified algorithms, and (4) legal and regulatory considerations. Additional considerations in developing text message management systems include: balancing the use of customized versus preexisting software systems, the level of automation versus need for human inputs, monitoring, ensuring data security, interface flexibility, and the ability for upscaling. Conclusions A merging of expertise in clinical and behavioral sciences, health and research data management systems, software engineering, and mobile phone regulatory requirements is essential to develop a platform to deliver and manage support programs to hundreds of participants simultaneously as in TEXT ME and TEXTMEDS trials. This research provides broad principles that may assist other researchers in developing mHealth programs. PMID:27847350

  11. Design Considerations in Development of a Mobile Health Intervention Program: The TEXT ME and TEXTMEDS Experience.

    PubMed

    Thakkar, Jay; Barry, Tony; Thiagalingam, Aravinda; Redfern, Julie; McEwan, Alistair L; Rodgers, Anthony; Chow, Clara K

    2016-11-15

    Mobile health (mHealth) has huge potential to deliver preventative health services. However, there is paucity of literature on theoretical constructs, technical, practical, and regulatory considerations that enable delivery of such services. The objective of this study was to outline the key considerations in the development of a text message-based mHealth program; thus providing broad recommendations and guidance to future researchers designing similar programs. We describe the key considerations in designing the intervention with respect to functionality, technical infrastructure, data management, software components, regulatory requirements, and operationalization. We also illustrate some of the potential issues and decision points utilizing our experience of developing text message (short message service, SMS) management systems to support 2 large randomized controlled trials: TEXT messages to improve MEDication adherence & Secondary prevention (TEXTMEDS) and Tobacco, EXercise and dieT MEssages (TEXT ME). The steps identified in the development process were: (1) background research and development of the text message bank based on scientific evidence and disease-specific guidelines, (2) pilot testing with target audience and incorporating feedback, (3) software-hardware customization to enable delivery of complex personalized programs using prespecified algorithms, and (4) legal and regulatory considerations. Additional considerations in developing text message management systems include: balancing the use of customized versus preexisting software systems, the level of automation versus need for human inputs, monitoring, ensuring data security, interface flexibility, and the ability for upscaling. A merging of expertise in clinical and behavioral sciences, health and research data management systems, software engineering, and mobile phone regulatory requirements is essential to develop a platform to deliver and manage support programs to hundreds of participants simultaneously as in TEXT ME and TEXTMEDS trials. This research provides broad principles that may assist other researchers in developing mHealth programs. ©Jay Thakkar, Tony Barry, Aravinda Thiagalingam, Julie Redfern, Alistair L McEwan, Anthony Rodgers, Clara K Chow. Originally published in JMIR Mhealth and Uhealth (http://mhealth.jmir.org), 15.11.2016.

  12. [Dietary guidelines for the Brazilian population: implications for the Brazilian National Policy on Oral Health].

    PubMed

    Freire, Maria do Carmo Matias; Balbo, Patrícia Lima; Amador, Maiara de Andrade; Sardinha, Luciana Monteiro Vasconcelos

    2012-01-01

    Dietary guidelines are intended to orient dietary habits and policies for health promotion and disease prevention. This article discusses Brazil's national dietary guidelines, aiming to identify issues that can support the strategies proposed by the National Policy on Oral Health. The two currently available official guidelines produced by the Ministry of Health were reviewed: the Dietary Guidelines for Children under Two and the Population Dietary Guidelines. The guidelines recommend reduction in sugar intake, essential for caries prevention, and other measures to prevent tooth decay and oral cancer. These guidelines are thus a key part of an oral and overall health promotion strategy and should be integrated into the National Policy on Oral Health.

  13. The Economics of Educational Software Portability.

    ERIC Educational Resources Information Center

    Oliveira, Joao Batista Araujo e

    1990-01-01

    Discusses economic issues that affect the portability of educational software. Topics discussed include economic reasons for portability, including cost effectiveness; the nature and behavior of educational computer software markets; the role of producers, buyers, and consumers; potential effects of government policies; computer piracy; and…

  14. Transforming Aggregate Object-Oriented Formal Specifications to Code

    DTIC Science & Technology

    1999-03-01

    integration issues associated with a formal-based software transformation system, such as the source specification, the problem space architecture , design architecture ... design transforms, and target software transforms. Software is critical in today’s Air Force, yet its specification, design, and development

  15. 75 FR 30010 - Improving Market and Planning Efficiency Through Improved Software; Notice of Agenda and...

    Federal Register 2010, 2011, 2012, 2013, 2014

    2010-05-28

    ... Market and Planning Efficiency Through Improved Software; Notice of Agenda and Procedures for Staff... conference to be held on June 2, 2010 and June 3, 2010, to discuss issues related to unit commitment software... Unit Commitment Software Federal Energy Regulatory Commission June 2, 2010 8 a.m Richard O'Neill, FERC...

  16. Copyright Protection for Computer Software: Is There a Need for More Protection?

    ERIC Educational Resources Information Center

    Ku, Linlin

    Because the computer industry's expansion has been much faster than has the development of laws protecting computer software and since the practice of software piracy seems to be alive and well, the issue of whether existing laws can provide effective protection for software needs further discussion. Three bodies of law have been used to protect…

  17. Analysis of scanner data for crop inventories

    NASA Technical Reports Server (NTRS)

    Horvath, R. (Principal Investigator); Cicone, R. C.; Kauth, R. J.; Malila, W. A.

    1981-01-01

    Progress and technical issues are reported in the development of corn/soybeans area estimation procedures for use on data from South America, with particular emphasis on Argentina. Aspects related to the supporting research section of the AgRISTARS Project discussed include: (1) multisegment corn/soybean estimation; (2) through the season separability of corn and soybeans within the U.S. corn belt; (3) TTS estimation; (4) insights derived from the baseline corn and soybean procedure; (5) small fields research; and (6) simulating the spectral appearance of wheat as a function of its growth and development. To assist the foreign commodity production forecasting, the performance of the baseline corn/soybean procedure was analyzed and the procedure modified. Fundamental limitations were found in the existing guidelines for discriminating these two crops. The temporal and spectral characteristics of corn and soybeans must be determined because other crops grow with them in Argentina. The state of software technology is assessed and the use of profile techniques for estimation is considered.

  18. WE-F-201-03: Evaluate Clinical Cases Using Commercially Available Systems and Compare to TG-43 Dosimetry

    DOE Office of Scientific and Technical Information (OSTI.GOV)

    Beaulieu, L.

    With the recent introduction of heterogeneity correction algorithms for brachytherapy, the AAPM community is still unclear on how to commission and implement these into clinical practice. The recently-published AAPM TG-186 report discusses important issues for clinical implementation of these algorithms. A charge of the AAPM-ESTRO-ABG Working Group on MBDCA in Brachytherapy (WGMBDCA) is the development of a set of well-defined test case plans, available as references in the software commissioning process to be performed by clinical end-users. In this practical medical physics course, specific examples on how to perform the commissioning process are presented, as well as descriptions of themore » clinical impact from recent literature reporting comparisons of TG-43 and heterogeneity-based dosimetry. Learning Objectives: Identify key clinical applications needing advanced dose calculation in brachytherapy. Review TG-186 and WGMBDCA guidelines, commission process, and dosimetry benchmarks. Evaluate clinical cases using commercially available systems and compare to TG-43 dosimetry.« less

  19. Optimizing IV and V for Mature Organizations

    NASA Technical Reports Server (NTRS)

    Fuhman, Christopher

    2003-01-01

    NASA is intending for its future software development agencies to have at least a Level 3 rating in the Carnegie Mellon University Capability Maturity Model (CMM). The CMM has built-in Verification and Validation (V&V) processes that support higher software quality. Independent Verification and Validation (IV&V) of software developed by mature agencies can be therefore more effective than for software developed by less mature organizations. How is Independent V&V different with respect to the maturity of an organization? Knowing a priori the maturity of an organization's processes, how can IV&V planners better identify areas of need choose IV&V activities, etc? The objective of this research is to provide a complementary set of guidelines and criteria to assist the planning of IV&V activities on a project using a priori knowledge of the measurable levels of maturity of the organization developing the software.

  20. Towards a controlled vocabulary on software engineering education

    NASA Astrophysics Data System (ADS)

    Pizard, Sebastián; Vallespir, Diego

    2017-11-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 approach to understand a thematic area. This study examines previous publications in software engineering education to obtain a first controlled vocabulary (a more formal definition of a classification schema) in the field. Publications from 1988 to 2014 were collected and processed using automatic clustering techniques and the outcomes were analysed manually. The result is an initial controlled vocabulary with a taxonomy form with 43 concepts that were identified as the most used in the research publications. We present the classification of the concepts in three facets: 'what to teach', 'how to teach' and 'where to teach' and the evolution of concepts over time.

  1. Computer-based guidelines for concrete pavements : volume III, technical appendices.

    DOT National Transportation Integrated Search

    2006-01-01

    This report documents enhancements incorporated in the (HIgh PERformance PAVing) HIPERPAV II software. Enhancements made : within this project include the addition of two major modules: a module to predict the performance of JPCP as affected by early...

  2. Computer-based guidelines for concrete pavements : HIPERPAV III : user manual

    DOT National Transportation Integrated Search

    2009-10-01

    This user manual provides guidance on how to use the new High PERformance PAVing (HIPERPAV) III software program for the analysis of early-age Portland cement concrete pavement (PCCP) behavior. HIPERPAV III includes several improvements over prev...

  3. Issues in Defining Software Architectures in a GIS Environment

    NASA Technical Reports Server (NTRS)

    Acosta, Jesus; Alvorado, Lori

    1997-01-01

    The primary mission of the Pan-American Center for Earth and Environmental Studies (PACES) is to advance the research areas that are relevant to NASA's Mission to Planet Earth program. One of the activities at PACES is the establishment of a repository for geographical, geological and environmental information that covers various regions of Mexico and the southwest region of the U.S. and that is acquired from NASA and other sources through remote sensing, ground studies or paper-based maps. The center will be providing access of this information to other government entities in the U.S. and Mexico, and research groups from universities, national laboratories and industry. Geographical Information Systems(GIS) provide the means to manage, manipulate, analyze and display geographically referenced information that will be managed by PACES. Excellent off-the-shelf software exists for a complete GIS as well as software for storing and managing spatial databases, processing images, networking and viewing maps with layered information. This allows the user flexibility in combining systems to create a GIS or to mix these software packages with custom-built application programs. Software architectural languages provide the ability to specify the computational components and interactions among these components, an important topic in the domain of GIS because of the need to integrate numerous software packages. This paper discusses the characteristics that architectural languages address with respect to the issues relating to the data that must be communicated between software systems and components when systems interact. The paper presents a background on GIS in section 2. Section 3 gives an overview of software architecture and architectural languages. Section 4 suggests issues that may be of concern when defining the software architecture of a GIS. The last section discusses the future research effort and finishes with a summary.

  4. Best Practices for Mental Health in Child Welfare: Parent Support and Youth Empowerment Guidelines

    ERIC Educational Resources Information Center

    Romanelli, Lisa Hunter; Hoagwood, Kimberly E.; Kaplan, Sandra J.; Kemp, Susan P.; Hartman, Robert L.; Trupin, Casey; Soto, Wilfredo; Pecora, Peter J.; LaBarrie, Theresa L.; Jensen, Peter S.

    2009-01-01

    This paper, the second in a series of two guideline papers emerging from the 2007 Best Practices for Mental Health in Child Welfare Consensus Conference, provides an overview of the key issues related to parent support and youth empowerment in child welfare and presents consensus guidelines in these important areas. The paper also discusses some…

  5. Developing prehospital clinical practice guidelines for resource limited settings: why re-invent the wheel?

    PubMed

    McCaul, Michael; de Waal, Ben; Hodkinson, Peter; Pigoga, Jennifer L; Young, Taryn; Wallis, Lee A

    2018-02-05

    Methods on developing new (de novo) clinical practice guidelines (CPGs) have received substantial attention. However, the volume of literature is not matched by research into alternative methods of CPG development using existing CPG documents-a specific issue for guideline development groups in low- and middle-income countries. We report on how we developed a context specific prehospital CPG using an alternative guideline development method. Difficulties experienced and lessons learnt in applying existing global guidelines' recommendations to a national context are highlighted. The project produced the first emergency care CPG for prehospital providers in Africa. It included > 270 CPGs and produced over 1000 recommendations for prehospital emergency care. We encountered various difficulties, including (1) applicability issues: few pre-hospital CPGs applicable to Africa, (2) evidence synthesis: heterogeneous levels of evidence classifications and (3) guideline quality. Learning points included (1) focusing on key CPGs and evidence mapping, (2) searching other resources for CPGs, (3) broad representation on CPG advisory boards and (4) transparency and knowledge translation. Re-inventing the wheel to produce CPGs is not always feasible. We hope this paper will encourage further projects to use existing CPGs in developing guidance to improve patient care in resource-limited settings.

  6. Development of a software safety process and a case study of its use

    NASA Technical Reports Server (NTRS)

    Knight, John C.

    1993-01-01

    The goal of this research is to continue the development of a comprehensive approach to software safety and to evaluate the approach with a case study. The case study is a major part of the project, and it involves the analysis of a specific safety-critical system from the medical equipment domain. The particular application being used was selected because of the availability of a suitable candidate system. We consider the results to be generally applicable and in no way particularly limited by the domain. The research is concentrating on issues raised by the specification and verification phases of the software lifecycle since they are central to our previously-developed rigorous definitions of software safety. The theoretical research is based on our framework of definitions for software safety. In the area of specification, the main topics being investigated are the development of techniques for building system fault trees that correctly incorporate software issues and the development of rigorous techniques for the preparation of software safety specifications. The research results are documented. Another area of theoretical investigation is the development of verification methods tailored to the characteristics of safety requirements. Verification of the correct implementation of the safety specification is central to the goal of establishing safe software. The empirical component of this research is focusing on a case study in order to provide detailed characterizations of the issues as they appear in practice, and to provide a testbed for the evaluation of various existing and new theoretical results, tools, and techniques. The Magnetic Stereotaxis System is summarized.

  7. Appropriate evidence sources for populating decision analytic models within health technology assessment (HTA): a systematic review of HTA manuals and health economic guidelines.

    PubMed

    Zechmeister-Koss, Ingrid; Schnell-Inderst, Petra; Zauner, Günther

    2014-04-01

    An increasing number of evidence sources are relevant for populating decision analytic models. What is needed is detailed methodological advice on which type of data is to be used for what type of model parameter. We aim to identify standards in health technology assessment manuals and economic (modeling) guidelines on appropriate evidence sources and on the role different types of data play within a model. Documents were identified via a call among members of the International Network of Agencies for Health Technology Assessment and by hand search. We included documents from Europe, the United States, Canada, Australia, and New Zealand as well as transnational guidelines written in English or German. We systematically summarized in a narrative manner information on appropriate evidence sources for model parameters, their advantages and limitations, data identification methods, and data quality issues. A large variety of evidence sources for populating models are mentioned in the 28 documents included. They comprise research- and non-research-based sources. Valid and less appropriate sources are identified for informing different types of model parameters, such as clinical effect size, natural history of disease, resource use, unit costs, and health state utility values. Guidelines do not provide structured and detailed advice on this issue. The article does not include information from guidelines in languages other than English or German, and the information is not tailored to specific modeling techniques. The usability of guidelines and manuals for modeling could be improved by addressing the issue of evidence sources in a more structured and comprehensive format.

  8. A comparative review of the pharmacoeconomic guidelines in South Africa.

    PubMed

    Carapinha, João L

    2017-01-01

    To compare the pharmacoeconomic guidelines in South Africa (SA) with other middle- and high-income countries. A comparative review of key features of the pharmacoeconomic guidelines in SA was undertaken using the Comparative Table of Pharmacoeconomic Guidelines developed by the International Society of Pharmacoeconomics and Outcomes Research, and published country-level pharmacoeconomics guidelines. A random sample of guidelines in high- and middle-income countries were analyzed if data on all key features were available. Key features of the pharmacoeconomic guidelines in SA were compared with those in other countries, and divergent features were identified and elaborated. Five upper middle-income countries (Brazil, Colombia, Cuba, Malaysia, and Mexico), one lower middle-income country (Egypt), and six high-income countries (Germany, Ireland, Norway, Portugal, Taiwan, and the Netherlands) were analyzed. The pharmacoeconomic guidelines in SA differ in important areas when compared with other countries. In SA, the study perspective and costs are limited to private health-insurance companies, complex modelling is discouraged and models require pre-approval, equity issues are not explicitly stated, a budget impact analysis is not required, and pharmacoeconomic submissions are voluntary. Future updates to the pharmacoeconomic guidelines in SA may include a societal perspective with limitations, incentivize complex and transparent models, and integrate equity issues. The pharmacoeconomic guidelines could be improved by addressing conflicting objectives with policies on National Health Insurance, incentivize private health insurance companies to disclose reimbursement data, and require the inclusion of a budget impact analysis in all pharmacoeconomic submissions. Further research is also needed on the impact of mandatory pharmacoeconomic submissions in middle-income countries.

  9. Development of an Ada package library

    NASA Technical Reports Server (NTRS)

    Burton, Bruce; Broido, Michael

    1986-01-01

    A usable prototype Ada package library was developed and is currently being evaluated for use in large software development efforts. The library system is comprised of an Ada-oriented design language used to facilitate the collection of reuse information, a relational data base to store reuse information, a set of reusable Ada components and tools, and a set of guidelines governing the system's use. The prototyping exercise is discussed and the lessons learned from it have led to the definition of a comprehensive tool set to facilitate software reuse.

  10. Photo-editing in Orthodontics: How Much is Too Much?.

    PubMed

    Kapoor, Priyanka

    2015-01-01

    Digital photography and radiology are the mainstay of orthodontic records but current image editing software programs nave led to increase in instances of digital forgery and scientific misconduct. In the present study, digital image data of orthodontic study casts and photographs were altered using software such as [Microsoft Paint6 1, Picasa3.1, Adobe Photoshop3.6]. Based on ethical guidelines on digital image manipulations, cropping or intensity adjustments in moderation to entire image were considered permissible while cloning or color adjustments were deemed unethical.

  11. Simulation verification techniques study: Simulation performance validation techniques document. [for the space shuttle system

    NASA Technical Reports Server (NTRS)

    Duncan, L. M.; Reddell, J. P.; Schoonmaker, P. B.

    1975-01-01

    Techniques and support software for the efficient performance of simulation validation are discussed. Overall validation software structure, the performance of validation at various levels of simulation integration, guidelines for check case formulation, methods for real time acquisition and formatting of data from an all up operational simulator, and methods and criteria for comparison and evaluation of simulation data are included. Vehicle subsystems modules, module integration, special test requirements, and reference data formats are also described.

  12. Science Facilities Design Guidelines.

    ERIC Educational Resources Information Center

    Maryland State Dept. of Education, Baltimore.

    These guidelines, presented in five chapters, propose a framework to support the planning, designing, constructing, and renovating of school science facilities. Some program issues to be considered in the articulation of a science program include environmental concerns, interdisciplinary approaches, space flexibility, and electronic…

  13. [Proposal for a media guideline to improve medical and health journalism].

    PubMed

    Kojima, Masami

    2012-01-01

    A lot of healthcare professionals experienced annoyance with biased mass media news regarding medical and health issues. In this paper, I propose "news profiling method" and "media guideline" to improve the medical and health journalism.

  14. Copyright: Know Your Electronic Rights!

    ERIC Educational Resources Information Center

    Valauskas, Edward J.

    1992-01-01

    Defines copyright and examines the interests of computer software publishers. Issues related to the rights of libraries in the circulation of software are discussed, including the fair use principle, software vendors' licensing agreements, and cooperation between libraries and vendors. An inset describes procedures for internal auditing of…

  15. Software process assessments

    NASA Technical Reports Server (NTRS)

    Miller, Sharon E.; Tucker, George T.; Verducci, Anthony J., Jr.

    1992-01-01

    Software process assessments (SPA's) are part of an ongoing program of continuous quality improvements in AT&T. Their use was found to be very beneficial by software development organizations in identifying the issues facing the organization and the actions required to increase both quality and productivity in the organization.

  16. 48 CFR 252.251-7000 - Ordering from Government supply sources.

    Code of Federal Regulations, 2010 CFR

    2010-10-01

    ... Enterprise Software Agreements, the Contractor shall follow the terms of the applicable schedule or agreement... Enterprise Software Agreement contractor). (2) The following statement: Any price reductions negotiated as part of an Enterprise Software Agreement issued under a Federal Supply Schedule contract shall control...

  17. Legal decision-making by people with aphasia: critical incidents for speech pathologists.

    PubMed

    Ferguson, Alison; Duffield, Gemma; Worrall, Linda

    2010-01-01

    The assessment and management of a person with aphasia for whom decision-making capacity is queried represents a highly complex clinical issue. In addition, there are few published guidelines and even fewer published accounts of empirical research to assist. The research presented in this paper aimed to identify the main issues for speech pathologists when decision-making capacity for legal and related matters arose for their clients with aphasia, and to describe qualitatively the nature of these issues and the practices of the speech pathologists in these situations. The methodology was informed by the qualitative research paradigm and made use of the semi-structured interview methods developed for the Critical Incident Technique. Nine speech pathologists, with a range of clinical experience between three and 27 years, were interviewed by telephone, with verbatim notes being taken on-line by the interviewer. The speech pathologists described a total of 21 clients (15 male, six female) with acquired neurological communication disorders (including cerebral vascular accident, traumatic brain injury, and tumour) whose care had raised critical incidents for the speech pathologist in relation to legal and related matters. These verbatim notes were qualitatively analysed using NVivo qualitative analysis software. The main incidents related to legal decisions (for example, power of attorney, will-making), as well as decisions involving consent for medical treatment, discharge, accommodation, and business/financial decisions. In all but one of the incidents recounted, the issues centred on a situation of conflict between the person with aphasia and their family, friends or with the multidisciplinary team. The roles taken by the speech pathologists ranged from those expected within a speech pathology scope of practice, such as that of assessor and consultant, to those which arguably present dilemmas and conflict of interest, for example, interpreter, advocate. The assessment practices involved some standardized testing, but this was stressed by all participants to be of lesser importance than informal observations of function. Speech pathologists emphasized the importance of multiple observations, and multimodal means of communication. The findings indicate that speech pathologists are currently playing an active role when questions arise regarding capacity for legal and related decision-making by people with aphasia. At the same time, the findings support the need for further research to develop guidelines for practice and to build educational experiences for students and novice clinicians to assist them when they engage with the complex case management issues in this area. 2010 Royal College of Speech & Language Therapists.

  18. Considering health equity when moving from evidence-based guideline recommendations to implementation: a case study from an upper-middle income country on the GRADE approach

    PubMed Central

    Mosquera, Paola; Alzate, Juan Pablo; Pottie, Kevin; Welch, Vivian; Akl, Elie A; Jull, Janet; Lang, Eddy; Katikireddi, Srinivasa Vittal; Morton, Rachel; Thabane, Lehana; Shea, Bev; Stein, Airton T; Singh, Jasvinder; Florez, Ivan D; Guyatt, Gordon; Schünemann, Holger; Tugwell, Peter

    2017-01-01

    Abstract The availability of evidence-based guidelines does not ensure their implementation and use in clinical practice or policy making. Inequities in health have been defined as those inequalities within or between populations that are avoidable, unnecessary and also unjust and unfair. Evidence-based clinical practice and public health guidelines (‘guidelines’) can be used to target health inequities experienced by disadvantaged populations, although guidelines may unintentionally increase health inequities. For this reason, there is a need for evidence-based clinical practice and public health guidelines to intentionally target health inequities experienced by disadvantaged populations. Current guideline development processes do not include steps for planned implementation of equity-focused guidelines. This article describes nine steps that provide guidance for consideration of equity during guideline implementation. A critical appraisal of the literature followed by a process to build expert consensus was undertaken to define how to include consideration of equity issues during the specific GRADE guideline development process. Using a case study from Colombia we describe nine steps that were used to implement equity-focused GRADE recommendations: (1) identification of disadvantaged groups, (2) quantification of current health inequities, (3) development of equity-sensitive recommendations, (4) identification of key actors for implementation of equity-focused recommendations, (5) identification of barriers and facilitators to the implementation of equity-focused recommendations, (6) development of an equity strategy to be included in the implementation plan, (7) assessment of resources and incentives, (8) development of a communication strategy to support an equity focus and (9) development of monitoring and evaluation strategies. This case study can be used as model for implementing clinical practice guidelines, taking into account equity issues during guideline development and implementation. PMID:29029068

  19. Guidelines warfare over interventional techniques: is there a lack of discourse or straw man?

    PubMed

    Manchikanti, Laxmaiah; Benyamin, Ramsin M; Falco, Frank J E; Caraway, David L; Datta, Sukdeb; Hirsch, Joshua A

    2012-01-01

    Guideline development seems to have lost some of its grounding as a medical science. At their best, guidelines should be a constructive response to assist practicing physicians in applying the exponentially expanding body of medical knowledge. In fact, guideline development seems to be evolving into a cottage industry with multiple, frequently discordant guidance on the same subject. Evidence Based Medicine does not always provide for conclusive opinions. With competing interests of payers, practitioners, health policy makers, and third parties benefiting from development of the guidelines as cost saving measures, guideline preparation has been described as based on pre-possession, vagary, rationalization, or congeniality of conclusion. Beyond legitimate differences in opinions regarding the evidence that could yield different guidelines there are potentials for conflicts of interest and various other issues play a major role in guideline development. As is always the case, conflicts of interest in guideline preparation must be evaluated and considered. Following the development of American Pain Society (APS) guidelines there has been an uproar in interventional pain management communities on various issues related to not only the evidence synthesis, but conflicts of interest. A recent manuscript published by Chou et al, in addition to previous publications, appears to have limited clinician involvement in the development of APS guidelines, and demonstrates some of these challenges clearly. This manuscript illustrates the deficiencies of Chou et al's criticisms, and demonstrates their significant conflicts of interest, and use a lack of appropriate evaluations in interventional pain management as a straw man to support their argument. Further, this review will attempt to demonstrate that excessive focus on this straw man has inhibited critique of what we believe to be flaws in the approach.  

  20. Pre-implementation guidelines for infectious disease point-of-care testing in medical institutions.

    PubMed

    van der Eijk, Annemiek A; Tintu, Andrei N; Hays, John P

    2017-01-01

    Infectious disease point-of-care test (ID-POCT) devices are becoming widely available, and in this respect, international quality standards and guidelines are available for consultation once ID-POCT has been implemented into medical institutions. However, specific guidelines for consultation during the initial pre-implementation decision-making process are currently lacking. Further, there exist pre-implementation issues specific to ID-POCT. Here we present pre-implementation guidelines for consultation when considering the implementation of ID-POCT in medical institutions.

  1. Flight software issues in onboard automated planning: lessons learned on EO-1

    NASA Technical Reports Server (NTRS)

    Tran, Daniel; Chien, Steve; Rabideau, Gregg; Cichy, Benjamin

    2004-01-01

    This paper focuses on the onboard planner and scheduler CASPER, whose core planning engine is based on the ground system ASPEN. Given the challenges of developing flight software, we discuss several of the issues encountered in preparing the planner for flight, including reducing the code image size, determining what data to place within the engineering telemetry packet, and performing long term planning.

  2. Guidelines for preparing high school psychology teachers: course-based and standards-based approaches.

    PubMed

    2013-01-01

    Psychology is one of the most popular elective high school courses. The high school psychology course provides the foundation for students to benefit from psychological perspectives on personal and contemporary issues and learn the rules of evidence and theoretical frameworks of the discipline. The guidelines presented here constitute the second of two reports in this issue of the American Psychologist (January 2013) representing recent American Psychological Association (APA) policies that support high-quality instruction in the teaching of high school psychology. These guidelines, aligned to the standards presented in the preceding report, describe models for the preparation of preservice psychology teachers. The two reports together demonstrate the rigor and competency that should be expected in psychology instruction at the high school level.

  3. Software Effort Estimation Accuracy: A Comparative Study of Estimations Based on Software Sizing and Development Methods

    ERIC Educational Resources Information Center

    Lafferty, Mark T.

    2010-01-01

    The number of project failures and those projects completed over cost and over schedule has been a significant issue for software project managers. Among the many reasons for failure, inaccuracy in software estimation--the basis for project bidding, budgeting, planning, and probability estimates--has been identified as a root cause of a high…

  4. Imaging Systems: What, When, How.

    ERIC Educational Resources Information Center

    Lunin, Lois F.; And Others

    1992-01-01

    The three articles in this special section on document image files discuss intelligent character recognition, including comparison with optical character recognition; selection of displays for document image processing, focusing on paperlike displays; and imaging hardware, software, and vendors, including guidelines for system selection. (MES)

  5. Integrated testing and verification system for research flight software

    NASA Technical Reports Server (NTRS)

    Taylor, R. N.

    1979-01-01

    The MUST (Multipurpose User-oriented Software Technology) program is being developed to cut the cost of producing research flight software through a system of software support tools. An integrated verification and testing capability was designed as part of MUST. Documentation, verification and test options are provided with special attention on real-time, multiprocessing issues. The needs of the entire software production cycle were considered, with effective management and reduced lifecycle costs as foremost goals.

  6. CrossTalk: The Journal of Defense Software Engineering. Volume 24, Number 6. November/December 2011

    DTIC Science & Technology

    2011-11-01

    Software Development.” Software Quality Professional Journal, American Society for Quality (ASQ), (March 2010) 4-14. 3. Nair, Gopalakrishnan T.R...Inspection Performance Metric”. Software Quality Professional Journal, American Society for Quality (ASQ), Volume 13, Issue 2, (March 2011) 14-26...the discovery process and are marketed by compa- nies such as Black Duck Software, OpenLogic, Palamida, and Protecode, among others.7 A number of open

  7. Designing Distributed Learning Environments with Intelligent Software Agents

    ERIC Educational Resources Information Center

    Lin, Fuhua, Ed.

    2005-01-01

    "Designing Distributed Learning Environments with Intelligent Software Agents" reports on the most recent advances in agent technologies for distributed learning. Chapters are devoted to the various aspects of intelligent software agents in distributed learning, including the methodological and technical issues on where and how intelligent agents…

  8. 1989-90 Statewide Computer Survey Report.

    ERIC Educational Resources Information Center

    South Carolina State Dept. of Education, Columbia. Office of Instructional Technology.

    This report presents the findings from South Carolina's seventh statewide computer survey. The survey solicited information on computer equipment and software, and dealt with such issues as the instructional and administrative uses of computers and the availability and use of Software Evaluation Exchange Dissemination (SEED) software reviews and a…

  9. A look at statin cost-effectiveness in view of the 2013 ACC/AHA cholesterol management guidelines.

    PubMed

    Deaño, Roderick C; Pandya, Ankur; Jones, Erica C; Borden, William B

    2014-09-01

    The 2013 cholesterol management guidelines presented a major shift in recommendations on which patients at risk of cardiovascular disease should be treated and how to treat them. Implementation of the guidelines is estimated to increase substantially the number of people who would be eligible for statin therapy. As the medical community considers the broad population impact of the new cholesterol guidelines, the issue of cost-effectiveness plays a role. This review covers the basic fundamentals of cost-effectiveness analysis and summarizes the key cost-effectiveness studies that relate to the new cholesterol guidelines.

  10. Practical guidelines for feminist research in nursing.

    PubMed

    Im, Eun-Ok

    2013-01-01

    With increasing interests in oppressed groups, the number of feminist studies in nursing has steadily increased. Despite the increasing number of feminist studies, very few articles have been written to provide practical guidelines for feminist research in nursing. In this article, guidelines for feminist research in nursing are proposed on the basis of 3 previous feminist studies. First, characteristics of feminist research are concisely described. Then, the 3 studies that are the basis for the guidelines are described. Finally, practical guidelines for feminist nursing research are proposed on the basis of 10 idea categories related to issues/concerns from the 3 studies.

  11. ClinGen Pathogenicity Calculator: a configurable system for assessing pathogenicity of genetic variants.

    PubMed

    Patel, Ronak Y; Shah, Neethu; Jackson, Andrew R; Ghosh, Rajarshi; Pawliczek, Piotr; Paithankar, Sameer; Baker, Aaron; Riehle, Kevin; Chen, Hailin; Milosavljevic, Sofia; Bizon, Chris; Rynearson, Shawn; Nelson, Tristan; Jarvik, Gail P; Rehm, Heidi L; Harrison, Steven M; Azzariti, Danielle; Powell, Bradford; Babb, Larry; Plon, Sharon E; Milosavljevic, Aleksandar

    2017-01-12

    The success of the clinical use of sequencing based tests (from single gene to genomes) depends on the accuracy and consistency of variant interpretation. Aiming to improve the interpretation process through practice guidelines, the American College of Medical Genetics and Genomics (ACMG) and the Association for Molecular Pathology (AMP) have published standards and guidelines for the interpretation of sequence variants. However, manual application of the guidelines is tedious and prone to human error. Web-based tools and software systems may not only address this problem but also document reasoning and supporting evidence, thus enabling transparency of evidence-based reasoning and resolution of discordant interpretations. In this report, we describe the design, implementation, and initial testing of the Clinical Genome Resource (ClinGen) Pathogenicity Calculator, a configurable system and web service for the assessment of pathogenicity of Mendelian germline sequence variants. The system allows users to enter the applicable ACMG/AMP-style evidence tags for a specific allele with links to supporting data for each tag and generate guideline-based pathogenicity assessment for the allele. Through automation and comprehensive documentation of evidence codes, the system facilitates more accurate application of the ACMG/AMP guidelines, improves standardization in variant classification, and facilitates collaborative resolution of discordances. The rules of reasoning are configurable with gene-specific or disease-specific guideline variations (e.g. cardiomyopathy-specific frequency thresholds and functional assays). The software is modular, equipped with robust application program interfaces (APIs), and available under a free open source license and as a cloud-hosted web service, thus facilitating both stand-alone use and integration with existing variant curation and interpretation systems. The Pathogenicity Calculator is accessible at http://calculator.clinicalgenome.org . By enabling evidence-based reasoning about the pathogenicity of genetic variants and by documenting supporting evidence, the Calculator contributes toward the creation of a knowledge commons and more accurate interpretation of sequence variants in research and clinical care.

  12. Computer systems and software engineering

    NASA Technical Reports Server (NTRS)

    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.

  13. Critical analysis of the Council for International Organizations of Medical Sciences 2016 International Guidelines for health-related research involving humans.

    PubMed

    Kottow Lang, Miguel Hugo

    2017-05-15

    This paper presents a preliminary discussion of the Council for International Organizations of Medical Sciences (CIOMS), recently issued “International Ethical Guidelines for Health-related Research Involving Humans” (2016) that acknowledges the document’s declared concern of the protection of human subjects and awareness of their needs and interests in “low-resource settings”. Nevertheless, guideline recommendations present exceptional situations –vulnerability, mental incompetence- wherein voluntary and consented participation may be reduced or omitted under three concurrent conditions: compelling scientific value, the need to include persons that will not benefit directly from participation, exposure to minimal or slight risks. CIOMS 2016 extends the range of issues than need deliberation and regulation, but it does not clarify controversial issues in research ethics. The indetermination of special situations that would allow incomplete or absent informed disclosure weakens rigorous ethical norms and opens up to slippery slopes of permissiveness that may be harmful to host-nations and participants of biomedical studies.

  14. Legal and ethical issues in research

    PubMed Central

    Yip, Camille; Han, Nian-Lin Reena; Sng, Ban Leong

    2016-01-01

    Legal and ethical issues form an important component of modern research, related to the subject and researcher. This article seeks to briefly review the various international guidelines and regulations that exist on issues related to informed consent, confidentiality, providing incentives and various forms of research misconduct. Relevant original publications (The Declaration of Helsinki, Belmont Report, Council for International Organisations of Medical Sciences/World Health Organisation International Guidelines for Biomedical Research Involving Human Subjects, World Association of Medical Editors Recommendations on Publication Ethics Policies, International Committee of Medical Journal Editors, CoSE White Paper, International Conference on Harmonisation of Technical Requirements for Registration of Pharmaceuticals for Human Use-Good Clinical Practice) form the literature that are relevant to the ethical and legal aspects of conducting research that researchers should abide by when conducting translational and clinical research. Researchers should note the major international guidelines and regional differences in legislation. Hence, specific ethical advice should be sought at local Ethics Review Committees. PMID:27729698

  15. Scalability and Validation of Big Data Bioinformatics Software.

    PubMed

    Yang, Andrian; Troup, Michael; Ho, Joshua W K

    2017-01-01

    This review examines two important aspects that are central to modern big data bioinformatics analysis - software scalability and validity. We argue that not only are the issues of scalability and validation common to all big data bioinformatics analyses, they can be tackled by conceptually related methodological approaches, namely divide-and-conquer (scalability) and multiple executions (validation). Scalability is defined as the ability for a program to scale based on workload. It has always been an important consideration when developing bioinformatics algorithms and programs. Nonetheless the surge of volume and variety of biological and biomedical data has posed new challenges. We discuss how modern cloud computing and big data programming frameworks such as MapReduce and Spark are being used to effectively implement divide-and-conquer in a distributed computing environment. Validation of software is another important issue in big data bioinformatics that is often ignored. Software validation is the process of determining whether the program under test fulfils the task for which it was designed. Determining the correctness of the computational output of big data bioinformatics software is especially difficult due to the large input space and complex algorithms involved. We discuss how state-of-the-art software testing techniques that are based on the idea of multiple executions, such as metamorphic testing, can be used to implement an effective bioinformatics quality assurance strategy. We hope this review will raise awareness of these critical issues in bioinformatics.

  16. Security Vulnerability Profiles of NASA Mission Software: Empirical Analysis of Security Related Bug Reports

    NASA Technical Reports Server (NTRS)

    Goseva-Popstojanova, Katerina; Tyo, Jacob P.; Sizemore, Brian

    2017-01-01

    NASA develops, runs, and maintains software systems for which security is of vital importance. Therefore, it is becoming an imperative to develop secure systems and extend the current software assurance capabilities to cover information assurance and cybersecurity concerns of NASA missions. The results presented in this report are based on the information provided in the issue tracking systems of one ground mission and one flight mission. The extracted data were used to create three datasets: Ground mission IVV issues, Flight mission IVV issues, and Flight mission Developers issues. In each dataset, we identified the software bugs that are security related and classified them in specific security classes. This information was then used to create the security vulnerability profiles (i.e., to determine how, why, where, and when the security vulnerabilities were introduced) and explore the existence of common trends. The main findings of our work include:- Code related security issues dominated both the Ground and Flight mission IVV security issues, with 95 and 92, respectively. Therefore, enforcing secure coding practices and verification and validation focused on coding errors would be cost effective ways to improve mission's security. (Flight mission Developers issues dataset did not contain data in the Issue Category.)- In both the Ground and Flight mission IVV issues datasets, the majority of security issues (i.e., 91 and 85, respectively) were introduced in the Implementation phase. In most cases, the phase in which the issues were found was the same as the phase in which they were introduced. The most security related issues of the Flight mission Developers issues dataset were found during Code Implementation, Build Integration, and Build Verification; the data on the phase in which these issues were introduced were not available for this dataset.- The location of security related issues, as the location of software issues in general, followed the Pareto principle. Specifically, for all three datasets, from 86 to 88 the security related issues were located in two to four subsystems.- The severity levels of most security issues were moderate, in all three datasets.- Out of 21 primary security classes, five dominated: Exception Management, Memory Access, Other, Risky Values, and Unused Entities. Together, these classes contributed from around 80 to 90 of all security issues in each dataset. This again proves the Pareto principle of uneven distribution of security issues, in this case across CWE classes, and supports the fact that addressing these dominant security classes provides the most cost efficient way to improve missions' security. The findings presented in this report uncovered the security vulnerability profiles and identified the common trends and dominant classes of security issues, which in turn can be used to select the most efficient secure design and coding best practices compiled by the part of the SARP project team associated with the NASA's Johnson Space Center. In addition, these findings provide valuable input to the NASA IVV initiative aimed at identification of the two 25 CWEs of ground and flight missions.

  17. A critical appraisal of clinical practice guidelines for the treatment of lower-limb osteoarthritis

    PubMed Central

    Pencharz, James N; Grigoriadis, Elizabeth; Jansz, Gwenderlyn F; Bombardier, Claire

    2002-01-01

    Clinical practice guidelines are important tools to assist clinical decision-making. Recently, several guidelines addressing the management of osteoarthritis (OA) have been published. Clinicians treating patients with OA must ensure that these guidelines are developed with consistency and methodological rigour. We undertook a qualitative summary and critical appraisal of six medical treatment guidelines for the management of lower-limb OA published in the medical literature within the past 5 years. A review of these six guidelines revealed that each possesses strengths and weakness. While most described the scope and intended patient populations, the guidelines varied considerably in the rigour of their development, coverage of implementation issues, and disclosure of conflicts of interest. PMID:11879536

  18. Foreword: Biomonitoring Equivalents special issue.

    PubMed

    Meek, M E; Sonawane, B; Becker, R A

    2008-08-01

    The challenge of interpreting results of biomonitoring for environmental chemicals in humans is highlighted in this Foreword to the Biomonitoring Equivalents (BEs) special issue of Regulatory Toxicology and Pharmacology. There is a pressing need to develop risk-based tools in order to empower scientists and health professionals to interpret and communicate the significance of human biomonitoring data. The BE approach, which integrates dosimetry and risk assessment methods, represents an important advancement on the path toward achieving this objective. The articles in this issue, developed as a result of an expert panel meeting, present guidelines for derivation of BEs, guidelines for communication using BEs and several case studies illustrating application of the BE approach for specific substances.

  19. Multidisciplinary and Active/Collaborative Approaches in Teaching Requirements Engineering

    ERIC Educational Resources Information Center

    Rosca, Daniela

    2005-01-01

    The requirements engineering course is a core component of the curriculum for the Master's in Software Engineering programme, at Monmouth University (MU). It covers the process, methods and tools specific to this area, together with the corresponding software quality issues. The need to produce software engineers with strong teamwork and…

  20. Guidance on Software Maintenance. Final Report. Reports on Computer Science and Technology.

    ERIC Educational Resources Information Center

    Martin, Roger J.; Osborne, Wilma M.

    Based on informal discussions with personnel at selected federal agencies and private sector organizations and on additional research, this publication addresses issues and problems of software maintenance and suggests actions and procedures which can help software maintenance organizations meet the growing demands of maintaining existing systems.…

  1. Software Engineering Infrastructure in a Large Virtual Campus

    ERIC Educational Resources Information Center

    Cristobal, Jesus; Merino, Jorge; Navarro, Antonio; Peralta, Miguel; Roldan, Yolanda; Silveira, Rosa Maria

    2011-01-01

    Purpose: The design, construction and deployment of a large virtual campus are a complex issue. Present virtual campuses are made of several software applications that complement e-learning platforms. In order to develop and maintain such virtual campuses, a complex software engineering infrastructure is needed. This paper aims to analyse the…

  2. 77 FR 50720 - Test Documentation for Digital Computer Software Used in Safety Systems of Nuclear Power Plants

    Federal Register 2010, 2011, 2012, 2013, 2014

    2012-08-22

    ... NUCLEAR REGULATORY COMMISSION [NRC-2012-0195] Test Documentation for Digital Computer Software...) is issuing for public comment draft regulatory guide (DG), DG-1207, ``Test Documentation for Digital... practices for test documentation for software and computer systems as described in the Institute of...

  3. Moving Secure Software Assurance into Higher Education: A Roadmap for Change

    DTIC Science & Technology

    2011-06-02

    Summarized: The Issue: 6/2/20118 Software defects are currently a fact of life Software defects are avenues of security vulnerabilities that cyber ... criminals , terrorists, or hostile nations can exploit. We (THE ENTIRE INDUSTY) need to change the way we build systems Decrease the number of defects

  4. Pediatric Sepsis Guidelines: Summary for resource-limited countries

    PubMed Central

    Khilnani, Praveen; Singhi, Sunit; Lodha, Rakesh; Santhanam, Indumathi; Sachdev, Anil; Chugh, Krishan; Jaishree, M.; Ranjit, Suchitra; Ramachandran, Bala; Ali, Uma; Udani, Soonu; Uttam, Rajiv; Deopujari, Satish

    2010-01-01

    Justification: Pediatric sepsis is a commonly encountered global issue. Existing guidelines for sepsis seem to be applicable to the developed countries, and only few articles are published regarding application of these guidelines in the developing countries, especially in resource-limited countries such as India and Africa. Process: An expert representative panel drawn from all over India, under aegis of Intensive Care Chapter of Indian Academy of Pediatrics (IAP) met to discuss and draw guidelines for clinical practice and feasibility of delivery of care in the early hours in pediatric patient with sepsis, keeping in view unique patient population and limited availability of equipment and resources. Discussion included issues such as sepsis definitions, rapid cardiopulmonary assessment, feasibility of early aggressive fluid therapy, inotropic support, corticosteriod therapy, early endotracheal intubation and use of positive end expiratory pressure/mechanical ventilation, initial empirical antibiotic therapy, glycemic control, and role of immunoglobulin, blood, and blood products. Objective: To achieve a reasonable evidence-based consensus on the basis of published literature and expert opinion to formulating clinical practice guidelines applicable to resource-limited countries such as India. Recommendations: Pediatric sepsis guidelines are presented in text and flow chart format keeping resource limitations in mind for countries such as India and Africa. Levels of evidence are indicated wherever applicable. It is anticipated that once the guidelines are used and outcomes data evaluated, further modifications will be necessary. It is planned to periodically review and revise these guidelines every 3–5 years as new body of evidence accumulates. PMID:20606908

  5. Management of stable angina: A commentary on the European Society of Cardiology guidelines.

    PubMed

    Ambrosio, Giuseppe; Mugelli, Alessandro; Lopez-Sendón, José; Tamargo, Juan; Camm, John

    2016-09-01

    In 2013 the European Society of Cardiology (ESC) released new guidelines on the management of stable coronary artery disease. These guidelines update and replace the previous ESC guidelines on the management of stable angina pectoris, issued in 2006. There are several new aspects in the 2013 ESC guidelines compared with the 2006 version. This opinion paper provides an in-depth interpretation of the ESC guidelines with regard to these issues, to help physicians in making evidence-based therapeutic choices in their routine clinical practice. The first new element is the definition of stable coronary artery disease itself, which has now broadened from a 'simple' symptom, angina pectoris, to a more complex disease that can even be asymptomatic. In the first-line setting, the major changes in the new guidelines are the upgrading of calcium channel blockers, the distinction between dihydropyridines and non-dihydropyridine calcium channel blockers, and the presence of important statements regarding the combination of calcium channel blockers with beta-blockers. In the second-line setting, the 2013 ESC guidelines recommend the addition of long-acting nitrates, ivabradine, nicorandil or ranolazine to first-line agents. Trimetazidine may also be considered. However, no clear distinction is made among different second-line drugs, despite different quality of evidence in favour of these agents. For example, the use of ranolazine is supported by strong and recent evidence, while data supporting the use of the traditional agents appear relatively scanty. © The European Society of Cardiology 2016.

  6. Nipype: a flexible, lightweight and extensible neuroimaging data processing framework in python.

    PubMed

    Gorgolewski, Krzysztof; Burns, Christopher D; Madison, Cindee; Clark, Dav; Halchenko, Yaroslav O; Waskom, Michael L; Ghosh, Satrajit S

    2011-01-01

    Current neuroimaging software offer users an incredible opportunity to analyze their data in different ways, with different underlying assumptions. Several sophisticated software packages (e.g., AFNI, BrainVoyager, FSL, FreeSurfer, Nipy, R, SPM) are used to process and analyze large and often diverse (highly multi-dimensional) data. However, this heterogeneous collection of specialized applications creates several issues that hinder replicable, efficient, and optimal use of neuroimaging analysis approaches: (1) No uniform access to neuroimaging analysis software and usage information; (2) No framework for comparative algorithm development and dissemination; (3) Personnel turnover in laboratories often limits methodological continuity and training new personnel takes time; (4) Neuroimaging software packages do not address computational efficiency; and (5) Methods sections in journal articles are inadequate for reproducing results. To address these issues, we present Nipype (Neuroimaging in Python: Pipelines and Interfaces; http://nipy.org/nipype), an open-source, community-developed, software package, and scriptable library. Nipype solves the issues by providing Interfaces to existing neuroimaging software with uniform usage semantics and by facilitating interaction between these packages using Workflows. Nipype provides an environment that encourages interactive exploration of algorithms, eases the design of Workflows within and between packages, allows rapid comparative development of algorithms and reduces the learning curve necessary to use different packages. Nipype supports both local and remote execution on multi-core machines and clusters, without additional scripting. Nipype is Berkeley Software Distribution licensed, allowing anyone unrestricted usage. An open, community-driven development philosophy allows the software to quickly adapt and address the varied needs of the evolving neuroimaging community, especially in the context of increasing demand for reproducible research.

  7. Nipype: A Flexible, Lightweight and Extensible Neuroimaging Data Processing Framework in Python

    PubMed Central

    Gorgolewski, Krzysztof; Burns, Christopher D.; Madison, Cindee; Clark, Dav; Halchenko, Yaroslav O.; Waskom, Michael L.; Ghosh, Satrajit S.

    2011-01-01

    Current neuroimaging software offer users an incredible opportunity to analyze their data in different ways, with different underlying assumptions. Several sophisticated software packages (e.g., AFNI, BrainVoyager, FSL, FreeSurfer, Nipy, R, SPM) are used to process and analyze large and often diverse (highly multi-dimensional) data. However, this heterogeneous collection of specialized applications creates several issues that hinder replicable, efficient, and optimal use of neuroimaging analysis approaches: (1) No uniform access to neuroimaging analysis software and usage information; (2) No framework for comparative algorithm development and dissemination; (3) Personnel turnover in laboratories often limits methodological continuity and training new personnel takes time; (4) Neuroimaging software packages do not address computational efficiency; and (5) Methods sections in journal articles are inadequate for reproducing results. To address these issues, we present Nipype (Neuroimaging in Python: Pipelines and Interfaces; http://nipy.org/nipype), an open-source, community-developed, software package, and scriptable library. Nipype solves the issues by providing Interfaces to existing neuroimaging software with uniform usage semantics and by facilitating interaction between these packages using Workflows. Nipype provides an environment that encourages interactive exploration of algorithms, eases the design of Workflows within and between packages, allows rapid comparative development of algorithms and reduces the learning curve necessary to use different packages. Nipype supports both local and remote execution on multi-core machines and clusters, without additional scripting. Nipype is Berkeley Software Distribution licensed, allowing anyone unrestricted usage. An open, community-driven development philosophy allows the software to quickly adapt and address the varied needs of the evolving neuroimaging community, especially in the context of increasing demand for reproducible research. PMID:21897815

  8. Conditions That Facilitate the Implementation of Educational Technology Innovations.

    ERIC Educational Resources Information Center

    Ely, Donald P.

    1990-01-01

    Describes eight conditions that facilitate the adoption, implementation, and institutionalization of educational technology innovations and suggests applications to the transfer of portable software. Applications of these conditions involving educational technology in Indonesia, Chile, and Peru are evaluated, and guidelines for successful…

  9. Administrator's Guide to Technology: Planning, Funding & Implementation.

    ERIC Educational Resources Information Center

    Aspen Education Development Group, Gaithersburg, MD.

    This document provides guidelines for administrators related to instructional technology and planning. Chapter 1 discusses planning, including developing a technology plan, facility assessment, e-rate planning, formation of a technology committee, budget planning, and hardware/software replacement plan and costs. Chapter 2 addresses…

  10. Guidelines for Tailoring DOD-STD-2167A for SDS (Strategic Defense System) Software Development

    DTIC Science & Technology

    1988-02-01

    UNCLASSIFIED APPENDIX A LIST OF ACRONYMS ABM Anti-Ballistic Missle AP Advanced Prototypes BM/C3 Battle Management/Command, Control, Communications CDRL...32 5.7.5 Configuration management ................................. 32 5.8 Sytem integration and testing ....... ............................. 34 t

  11. Warm Hearts/Cold Type: Desktop Publishing Arrives.

    ERIC Educational Resources Information Center

    Kramer, Felix

    1991-01-01

    Describes desktop publishing (DTP) that may be suitable for community, activist, and nonprofit groups and discusses how it is changing written communication. Topics discussed include costs; laser printers; time savings; hardware and software selection; and guidelines to consider when establishing DTP capability. (LRW)

  12. Desktop Publishing Made Simple.

    ERIC Educational Resources Information Center

    Wentling, Rose Mary

    1989-01-01

    The author discusses the types of computer hardware and software necessary to set up a desktop publishing system, both for use in educational administration and for instructional purposes. Classroom applications of desktop publishing are presented. The author also provides guidelines for preparing to teach desktop publishing. (CH)

  13. Best Practice Guidelines for Computer Technology in the Montessori Early Childhood Classroom.

    ERIC Educational Resources Information Center

    Montminy, Peter

    1999-01-01

    Presents a draft for a principle-centered position statement of a Montessori early childhood program in central Pennsylvania, on the pros and cons of computer use in a Montessori 3-6 classroom. Includes computer software rating form. (Author/KB)

  14. The Promise of MIDI Technology: A Reflection on Musical Intelligence.

    ERIC Educational Resources Information Center

    Ohler, Jason

    1998-01-01

    Describes MIDI (Musical Instrument Digital Interface) technology and music education; provides information on conducting a MIDI workshop for all ages; and offers guidelines for creating a MIDI workstation for the classroom. Hardware and software vendor contact information is provided. (PEN)

  15. Proceedings of the Center for National Software Studies Workshop on Trustworthy Software

    DTIC Science & Technology

    2004-05-10

    just the de - velopment cost) to achieve a sustained level of software trustworthiness. • Reforming the procurement process. We could reform the...failure or breach of security. Some examples include software used in safety systems of nuclear power plants, transportation systems, medical devices...issue in many vital systems, including those found in transportation , telecommunications, utilities, health care, and financial services. Any lack of

  16. The embedded software life cycle - An expanded view

    NASA Technical Reports Server (NTRS)

    Larman, Brian T.; Loesh, Robert E.

    1989-01-01

    Six common issues that are encountered in the development of software for embedded computer systems are discussed from the perspective of their interrelationships with the development process and/or the system itself. Particular attention is given to concurrent hardware/software development, prototyping, the inaccessibility of the operational system, fault tolerance, the long life cycle, and inheritance. It is noted that the life cycle for embedded software must include elements beyond simply the specification and implementation of the target software.

  17. Software Engineering Laboratory (SEL) Ada performance study report

    NASA Technical Reports Server (NTRS)

    Booth, Eric W.; Stark, Michael E.

    1991-01-01

    The goals of the Ada Performance Study are described. The methods used are explained. Guidelines for future Ada development efforts are given. The goals and scope of the study are detailed, and the background of Ada development in the Flight Dynamics Division (FDD) is presented. The organization and overall purpose of each test are discussed. The purpose, methods, and results of each test and analyses of these results are given. Guidelines for future development efforts based on the analysis of results from this study are provided. The approach used on the performance tests is discussed.

  18. Return of the pulmonary nodule: the radiologist's key role in implementing the 2015 BTS guidelines on the investigation and management of pulmonary nodules.

    PubMed

    Graham, Richard N J; Baldwin, David R; Callister, Matthew E J; Gleeson, Fergus V

    2016-01-01

    The British Thoracic Society has published new comprehensive guidelines for the management of pulmonary nodules. These guidelines are significantly different from those previously published, as they use two malignancy prediction calculators to better characterize the risk of malignancy. There are recommendations for a higher nodule size threshold for follow-up (≥5 mm or ≥80 mm(3)) and a reduction of the follow-up period to 1 year for solid pulmonary nodules; both of these will reduce the number of follow-up CT scans. PET-CT plays a crucial role in characterization also, with an ordinal scale being recommended for reporting. Radiologists will be the key in implementing these guidelines, and routine use of volumetric image-analysis software will be required to manage patients with pulmonary nodules correctly.

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

    NASA Astrophysics Data System (ADS)

    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.

  20. Development of a Common User Interface for the Launch Decision Support System

    NASA Technical Reports Server (NTRS)

    Scholtz, Jean C.

    1991-01-01

    The Launch Decision Support System (LDSS) is software to be used by the NASA Test Director (NTD) in the firing room during countdown. This software is designed to assist the NTD with time management, that is, when to resume from a hold condition. This software will assist the NTD in making and evaluating alternate plans and will keep him advised of the existing situation. As such, the interface to this software must be designed to provide the maximum amount of information in the clearest fashion and in a timely manner. This research involves applying user interface guidelines to a mature prototype of LDSS and developing displays that will enable the users to easily and efficiently obtain information from the LDSS displays. This research also extends previous work on organizing and prioritizing human-computer interaction knowledge.

  1. A recommended guideline for the development of mHealth Apps

    PubMed Central

    Christoforidou, Sofia A.; Vlachopoulou, Maro

    2016-01-01

    Background Mobile Health or mHealth applications cope with medical or health issues supported by smartphones. Being a part of great importance in healthcare, mHealth apps are able to improve both the quality of medical services and the safety of the patients. It is regarded to be a new field with great prospect that attracts the interest of the stakeholders and the developers, above all. Of all the entities involved, developers have to face many challenges classified in four pillars: the regulation framework, the market, the technical issues and society. This paper aims to describe the role of the developers in the mHealth apps’ market, the barriers they deal with and also, the impact of their work in the mobile healthcare domain. In our viewpoint, we propose a guideline with all of the developers’ requirements for the buildup of mHealth apps. Methods The methodology followed includes a Boolean search strategy used in academic libraries (PubMed, IEEE Xplore, JMIR, The Cochrane Library) and search engines additionally (Google and Google Scholar), aiming to identify the developers’ perspective. Results Our research from October until December of 2014 led us to academic papers referring to the various demands that developers have to confront. The major outcome of our research is the general acknowledgement of the dominant role that developers own in the mHealth apps’ process. Conclusions Mobile technology allies multiple groups such as users, patients, providers of medical services, software developers, governments and even, non-governmental organizations. In particular, the developers’ perspective involves the legal boundaries, the side of the market, the technological requirements (programming, devices, designing) and the moral aspects, as well. Developers should define the purposes of their apps—either diagnostic or therapeutic—and gain the confidence of the users in order to dominate the market, yet comply with the regulations. PMID:28293597

  2. Ethical issues of cost effectiveness analysis and guideline setting in mental health care.

    PubMed

    Berghmans, R; Berg, M; van den Burg, M; ter Meulen, R

    2004-04-01

    This article discusses ethical issues which are raised as a result of the introduction of economic evidence in mental health care in order to rationalise clinical practice. Cost effectiveness studies and guidelines based on such studies are often seen as impartial, neutral instruments which try to reduce the influence of non-scientific factors. However, such rationalising instruments often hide normative assumptions about the goals of treatment, the selection of treatments, the role of the patient, and the just distribution of scarce resources. These issues are dealt with in the context of increased control over clinical practice by third parties. In particular, health insurers have a great interest in economic evidence in clinical care settings in order to control access to and quality of (mental) health care. The authors conclude that guideline setting and cost effectiveness analysis may be seen as important instruments for making choices in health care, including mental health care, but that such an approach should always go hand in hand with a social and political debate about the goals of medicine and (mental) health care. This article is partly based on the results of a research project on the normative aspects of guideline setting in psychiatry and cardiology which was conducted under the guidance of the Royal Dutch Medical Association.

  3. Executable assertions and flight software

    NASA Technical Reports Server (NTRS)

    Mahmood, A.; Andrews, D. M.; Mccluskey, E. J.

    1984-01-01

    Executable assertions are used to test flight control software. The techniques used for testing flight software; however, are different from the techniques used to test other kinds of software. This is because of the redundant nature of flight software. An experimental setup for testing flight software using executable assertions is described. Techniques for writing and using executable assertions to test flight software are presented. The error detection capability of assertions is studied and many examples of assertions are given. The issues of placement and complexity of assertions and the language features to support efficient use of assertions are discussed.

  4. SWiFT Software Quality Assurance Plan.

    DOE Office of Scientific and Technical Information (OSTI.GOV)

    Berg, Jonathan Charles

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

  5. Strategic Planning for Deepening the All-Around Structural Reform of Education: Issues of Structural Reform in the "National Medium- and Long-Term Educational Reform and Development Guideline (2010-20)"

    ERIC Educational Resources Information Center

    Songhua, Tan; Wang, Catherine Yan

    2012-01-01

    The "National Medium- and Long-Term Educational Reform and Development Guideline (2010-20)" (hereafter abbreviated as the "Guideline") posits that the development of education must be driven by reform and innovation. It devotes six chapters to mapping out the targets, tasks, and major policy measures for reforming the…

  6. An interagency space nuclear propulsion safety policy for SEI - Issues and discussion

    NASA Technical Reports Server (NTRS)

    Marshall, A. C.; Sawyer, J. C., Jr.

    1991-01-01

    An interagency Nuclear Safety Policy Working Group (NSPWG) was chartered to recommend nuclear safety policy, requirements, and guidelines for the Space Exploration Initiative nuclear propulsion program to facilitate the implementation of mission planning and conceptual design studies. The NSPWG developed a top level policy to provide the guiding principles for the development and implementation of the nuclear propulsion safety program and the development of Safety Functional Requirements. In addition, the NSPWG reviewed safety issues for nuclear propulsion and recommended top level safety requirements and guidelines to address these issues. Safety topics include reactor start-up, inadvertent criticality, radiological release and exposure, disposal, entry, safeguards, risk/reliability, operational safety, ground testing, and other considerations. In this paper the emphasis is placed on the safety policy and the issues and considerations that are addressed by the NSPWG recommendations.

  7. Computerization of guidelines: towards a "guideline markup language".

    PubMed

    Dart, T; Xu, Y; Chatellier, G; Degoulet, P

    2001-01-01

    Medical decision making is one of the most difficult daily tasks for physicians. Guidelines have been designed to reduce variance between physicians in daily practice, to improve patient outcomes and to control costs. In fact, few physicians use guidelines in daily practice. A way to ease the use of guidelines is to implement computerised guidelines (computer reminders). We present in this paper a method of computerising guidelines. Our objectives were: 1) to propose a generic model that can be instantiated for any specific guidelines; 2) to use eXtensible Markup Language (XML) as a guideline representation language to instantiate the generic model for a specific guideline. Our model is an object representation of a clinical algorithm, it has been validated by running two different guidelines issued by a French official Agency. In spite of some limitations, we found that this model is expressive enough to represent complex guidelines devoted to diabetes and hypertension management. We conclude that XML can be used as a description format to structure guidelines and as an interface between paper-based guidelines and computer applications.

  8. Considerations in the Derivation of Water Quality Criteria for Endocrine-disrupting Chemicals

    EPA Science Inventory

    When the USEPA’s 1985 guidelines for deriving numerical water quality criteria (WQC) for the protection of aquatic life were developed there was little anticipation that endocrine-disrupting chemicals (EDCs) would be come a widespread environmental issue. While the basic guidelin...

  9. Curriculum Planning Guidelines for Tobacco Use Prevention and Education.

    ERIC Educational Resources Information Center

    Montana State Office of Public Instruction, Helena.

    This curriculum planning guide is designed to help Montana school districts design an appropriate tobacco use prevention and education program. It focuses on: "Tobacco Use Prevention Education: The OPI (Office of Public Instruction) Perspective"; "Instructional Guidelines" (key issues in program planning and major health…

  10. Curricular Guidelines for Pharmacy Education: Substance Abuse and Addictive Disease.

    ERIC Educational Resources Information Center

    Baldwin, Jeffrey N.; And Others

    1991-01-01

    American Association of Colleges of Pharmacy guidelines for required and elective instructional content concerning substance abuse for pharmacy students is presented. Recommended required content includes psychosocial aspects of drug use; pharmacology and toxicology; identification, intervention, and treatment of addiction; and legal issues.…

  11. 78 FR 39649 - Passenger Vessels Accessibility Guidelines

    Federal Register 2010, 2011, 2012, 2013, 2014

    2013-07-02

    ... ARCHITECTURAL AND TRANSPORTATION BARRIERS COMPLIANCE BOARD 36 CFR Part 1196 [Docket No. ATBCB-2013-0003] RIN 3014-AA11 Passenger Vessels Accessibility Guidelines Correction In proposed rule document 2013-14367, appearing on pages 38102- 38159 in the issue of Tuesday, June 25, 2013, make the following...

  12. Practical Design Guidelines of qZSI Based Step-Up DC/DC Converter

    NASA Astrophysics Data System (ADS)

    Zakis, Janis; Vinnikov, Dmitri; Roasto, Indrek; Jalakas, Tanel

    2010-01-01

    This paper presents some design guidelines for a new voltage fed step-up DC/DC isolated converter. The most significant advantage of proposed converter is voltage buck-boost operation on single stage. The most promising application for proposed converter is in the field of distributed power generation e.g. fuel cells or photovoltaic. The most sensitive issues - such as power losses caused by high currents in the input side of converter and high transient overvoltages across the inverter bridge caused by stray inductances were discussed and solved. The proposals and recommendations to overcome these issues are given in the paper. The Selection and design guidelines of converter elements are proposed and explained. The prototype of proposed converter was built and experimentally tested. Some results are presented and evaluated.

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

    DOE Office of Scientific and Technical Information (OSTI.GOV)

    Not Available

    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 documentsmore » 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.« less

  14. The State of Software for Evolutionary Biology.

    PubMed

    Darriba, Diego; Flouri, Tomáš; Stamatakis, Alexandros

    2018-05-01

    With Next Generation Sequencing data being routinely used, evolutionary biology is transforming into a computational science. Thus, researchers have to rely on a growing number of increasingly complex software. All widely used core tools in the field have grown considerably, in terms of the number of features as well as lines of code and consequently, also with respect to software complexity. A topic that has received little attention is the software engineering quality of widely used core analysis tools. Software developers appear to rarely assess the quality of their code, and this can have potential negative consequences for end-users. To this end, we assessed the code quality of 16 highly cited and compute-intensive tools mainly written in C/C++ (e.g., MrBayes, MAFFT, SweepFinder, etc.) and JAVA (BEAST) from the broader area of evolutionary biology that are being routinely used in current data analysis pipelines. Because, the software engineering quality of the tools we analyzed is rather unsatisfying, we provide a list of best practices for improving the quality of existing tools and list techniques that can be deployed for developing reliable, high quality scientific software from scratch. Finally, we also discuss journal as well as science policy and, more importantly, funding issues that need to be addressed for improving software engineering quality as well as ensuring support for developing new and maintaining existing software. Our intention is to raise the awareness of the community regarding software engineering quality issues and to emphasize the substantial lack of funding for scientific software development.

  15. Scientific Reporting: Raising the Standards.

    PubMed

    McLeroy, Kenneth R; Garney, Whitney; Mayo-Wilson, Evan; Grant, Sean

    2016-10-01

    This article is based on a presentation that was made at the 2014 annual meeting of the editorial board of Health Education & Behavior. The article addresses critical issues related to standards of scientific reporting in journals, including concerns about external and internal validity and reporting bias. It reviews current reporting guidelines, effects of adopting guidelines, and offers suggestions for improving reporting. The evidence about the effects of guideline adoption and implementation is briefly reviewed. Recommendations for adoption and implementation of appropriate guidelines, including considerations for journals, are provided. © 2016 Society for Public Health Education.

  16. Periodontics and the new CDC guidelines.

    PubMed

    Basquill, Linda C; Basquill, Patrick J

    2004-07-01

    On December 19, 2003, the Centers for Disease Control and Prevention released the Guidelines for Infection Control in Dental Health-Care Settings--2003. The publication was the first comprehensive dental infection control update since 1993. Although the guidelines are not directed toward a particular dental specialty, some recommendations may have a significant impact on the practice of periodontics because of the nature of the procedures that are considered routine to the specialty. This article deals with some of the issues addressed in the guidelines, highlighting topics of special interest to periodontists.

  17. Introduction to resuscitation of the newborn infant. ARC and NZRC Guideline 2010.

    PubMed

    2011-08-01

    • Introduction to Resuscitation of the Newborn Infant. ARC and NZRC Guideline 2010 • Planning for Neonatal Resuscitation and Identification of the Newborn Infant at Risk. ARC and NZRC Guideline 2010 • Assessment of the Newborn Infant. ARC and NZRC Guideline 2010 • Airway Management and Mask Ventilation of the Newborn Infant. ARC and NZRC Guideline 2010 • Tracheal Intubation and Ventilation of the Newborn Infant. ARC and NZRC Guideline 2010 • Chest Compressions during Resuscitation of the Newborn Infant. ARC and NZRC Guideline 2010 • Medication or Fluids for the Resuscitation of the Newborn Infant. ARC and NZRC Guideline 2010 • The Resuscitation of the Newborn Infant in Special Circumstances. ARC and NZRC Guideline 2010 • After the Resuscitation of a Newborn Infant. ARC and NZRC Guideline 2010 • Ethical Issues in Resuscitation of the Newborn Infant. ARC and NZRC Guideline 2010. © 2011 The Authors. EMA © 2011 Australasian College for Emergency Medicine and Australasian Society for Emergency Medicine.

  18. DNA Commission of the International Society for Forensic Genetics (ISFG): Guidelines on the use of X-STRs in kinship analysis.

    PubMed

    Tillmar, Andreas O; Kling, Daniel; Butler, John M; Parson, Walther; Prinz, Mechthild; Schneider, Peter M; Egeland, Thore; Gusmão, Leonor

    2017-07-01

    Forensic genetic laboratories perform an increasing amount of genetic analyses of the X chromosome, in particular to solve complex cases of kinship analysis. For some biological relationships X-chromosomal markers can be more informative than autosomal markers, and there are a large number of markers, methods and databases that have been described for forensic use. Due to their particular mode of inheritance, and their physical location on a single chromosome, some specific considerations are required when estimating the weight of evidence for X-chromosomal marker DNA data. The DNA Commission of the International Society for Forensic Genetics (ISFG) hereby presents guidelines and recommendations for the use of X-chromosomal markers in kinship analysis with a special focus on the biostatistical evaluation. Linkage and linkage disequilibrium (association of alleles) are of special importance for such evaluations and these concepts and the implications for likelihood calculations are described in more detail. Furthermore it is important to use appropriate computer software that accounts for linkage and linkage disequilibrium among loci, as well as for mutations. Even though some software exist, there is still a need for further improvement of dedicated software. Copyright © 2017 Elsevier B.V. All rights reserved.

  19. Academic integrity and plagiarism: perceptions and experience of staff and students in a school of dentistry: a situational analysis of staff and student perspectives.

    PubMed

    Ford, P J; Hughes, C

    2012-02-01

    This project has investigated student and staff perceptions and experience of plagiarism in a large Australian dental school to develop a response to an external audit report. Workshops designed to enhance participants' understanding of plagiarism and to assist with practical ways to promote academic integrity within the school were provided to all students and staff. Anonymous surveys were used to investigate perceptions and experience of plagiarism and to assess the usefulness of the workshops. Most participants felt that plagiarism was not a problem in the school, but a significant number were undecided. The majority of participants reported that the guidelines for dealing with plagiarism were inadequate and most supported the mandatory use of text-matching software in all courses. High proportions of participants indicated that the workshops were useful and that they would consider improving their practice as a result. The study provided data that enhanced understanding of aspects of plagiarism highlighted in the report at the school level and identified areas in need of attention, such as refining and raising awareness of the guidelines and incorporation of text-matching software into courses, as well as cautions to be considered (how text-matching software is used) in planning responsive action. © 2011 John Wiley & Sons A/S.

  20. Manual on the proper use of lutetium-177-labeled somatostatin analogue (Lu-177-DOTA-TATE) injectable in radionuclide therapy (2nd ed.).

    PubMed

    Hosono, Makoto; Ikebuchi, Hideharu; Nakamura, Yoshihide; Nakamura, Nobutaka; Yamada, Takahiro; Yanagida, Sachiko; Kitaoka, Asami; Kojima, Kiyotaka; Sugano, Hiroyasu; Kinuya, Seigo; Inoue, Tomio; Hatazawa, Jun

    2018-04-01

    Here we present the guideline for the treatment of neuroendocrine tumors using Lu-177-DOTA-TATE on the basis of radiation safety aspects in Japan. This guideline was prepared by a study supported by Ministry of Health, Labour, and Welfare, and approved by Japanese Society of Nuclear Medicine. Lu-177-DOTA-TATE treatment in Japan should be carried out according to this guideline. Although this guideline is applied in Japan, the issues for radiation protection shown in this guideline are considered internationally useful as well. Only the original Japanese version is the formal document.

  1. The current situation regarding the establishment of national ethical guidelines for biomedical research in Thailand and its neighboring countries.

    PubMed

    Kojima, Somei; Waikagul, Jitra; Rojekittikhun, Wichit; Keicho, Naoto

    2005-05-01

    This study discusses the establishment of ethical guidelines for ethical review for biomedical research performed in Thailand, and to some extent, in neighboring countries. There are differences, from country to country, at national and institutional levels regarding guidelines for ethical review committees. Only a handbook issued by Mahidol University describes guidelines for human genetic research and on research dealing with reproductive technology. Both these areas require special consideration to avoid violating human dignity, rights, and confidentiality. This indicates that further efforts should be made to establish research guidelines and/or principles dealing with the human genome.

  2. Exploring Music through Technology.

    ERIC Educational Resources Information Center

    Willard, Joanne B.

    1992-01-01

    Describes a high school music technology course that uses a project-oriented approach to teach students about hardware and software tools for sequencing, arranging, multitrack recording, and mixing. Course equipment is listed, and the MIDI (Musical Instrument Digital Interface) is briefly described. Copyright guidelines for educational uses of…

  3. Resource Sharing of Micro-Software, or, What Ever Happened to All That CP/M Compatibility?

    ERIC Educational Resources Information Center

    DeYoung, Barbara

    1984-01-01

    Explores incompatible operating systems as the basic reason why software packages will not work on different microcomputers; defines operating system; explores compatibility issues surrounding the IBM MS-DOS; and presents two future trends in hardware and software developments which indicate a return to true compatibility. (Author/MBR)

  4. Learning Fraction Comparison by Using a Dynamic Mathematics Software--GeoGebra

    ERIC Educational Resources Information Center

    Poon, Kin Keung

    2018-01-01

    GeoGebra is a mathematics software system that can serve as a tool for inquiry-based learning. This paper deals with the application of a fraction comparison software, which is constructed by GeoGebra, for use in a dynamic mathematics environment. The corresponding teaching and learning issues have also been discussed.

  5. Software Quality and Copyright: Issues in Computer-Assisted Instruction.

    ERIC Educational Resources Information Center

    Helm, Virginia

    The two interconnected problems of educational quality and piracy are described and analyzed in this book, which begins with an investigation of the accusations regarding the alleged dismal quality of educational software. The reality behind accusations of rampant piracy and the effect of piracy on the quality of educational software is examined…

  6. Learning fraction comparison by using a dynamic mathematics software - GeoGebra

    NASA Astrophysics Data System (ADS)

    Poon, Kin Keung

    2018-04-01

    GeoGebra is a mathematics software system that can serve as a tool for inquiry-based learning. This paper deals with the application of a fraction comparison software, which is constructed by GeoGebra, for use in a dynamic mathematics environment. The corresponding teaching and learning issues have also been discussed.

  7. 78 FR 21314 - Medicare and State Health Care Programs: Fraud and Abuse; Electronic Health Records Safe Harbor...

    Federal Register 2010, 2011, 2012, 2013, 2014

    2013-04-10

    ... health records software or information technology and training services. The final rule for this safe... health records software or information technology and training services. In the same issue of the Federal..., licenses, and intellectual property related to electronic health records software; connectivity services...

  8. 78 FR 22432 - Airworthiness Directives; Airbus Airplanes

    Federal Register 2010, 2011, 2012, 2013, 2014

    2013-04-16

    ... electrical rudder], through Airbus Service Bulletin (SB) A330-27-3176, --software standard P12A/M21A on FCPC.... Since we issued that AD, we have determined that new software standards for the flight control primary.... This proposed AD would require that operators modify or replace all three FCPCs with new software...

  9. gSRT-Soft: a generic software application and some methodological guidelines to investigate implicit learning through visual-motor sequential tasks.

    PubMed

    Chambaron, Stéphanie; Ginhac, Dominique; Perruchet, Pierre

    2008-05-01

    Serial reaction time tasks and, more generally, the visual-motor sequential paradigms are increasingly popular tools in a variety of research domains, from studies on implicit learning in laboratory contexts to the assessment of residual learning capabilities of patients in clinical settings. A consequence of this success, however, is the increased variability in paradigms and the difficulty inherent in respecting the methodological principles that two decades of experimental investigations have made more and more stringent. The purpose of the present article is to address those problems. We present a user-friendly application that simplifies running classical experiments, but is flexible enough to permit a broad range of nonstandard manipulations for more specific objectives. Basic methodological guidelines are also provided, as are suggestions for using the software to explore unconventional directions of research. The most recent version of gSRT-Soft may be obtained for free by contacting the authors.

  10. Combining Agile and Traditional: Customer Communication in Distributed Environment

    NASA Astrophysics Data System (ADS)

    Korkala, Mikko; Pikkarainen, Minna; Conboy, Kieran

    Distributed development is a radically increasing phenomenon in modern software development environments. At the same time, traditional and agile methodologies and combinations of those are being used in the industry. Agile approaches place a large emphasis on customer communication. However, existing knowledge on customer communication in distributed agile development seems to be lacking. In order to shed light on this topic and provide practical guidelines for companies in distributed agile environments, a qualitative case study was conducted in a large globally distributed software company. The key finding was that it might be difficult for an agile organization to get relevant information from a traditional type of customer organization, even though the customer communication was indicated to be active and utilized via multiple different communication media. Several challenges discussed in this paper referred to "information blackout" indicating the importance of an environment fostering meaningful communication. In order to evaluate if this environment can be created a set of guidelines is proposed.

  11. Prospectus 2000

    NASA Astrophysics Data System (ADS)

    Holmes, Jon L.; Gettys, Nancy S.

    2000-01-01

    We begin 2000 with a message about our plans for JCE Software and what you will be seeing in this column as the year progresses. Floppy Disk --> CD-ROM Most software today is distributed on CD-ROM or by downloading from the Internet. Several new computers no longer include a floppy disk drive as "standard equipment". Today's software no longer fits on one or two floppies (the installation software alone can require two disks) and the cost of reproducing and distributing several disks is prohibitive. In short, distribution of software on floppy disks is no longer practical. Therefore, JCE Software will distribute all new software publications on CD-ROM rather than on disks. Regular Issues --> Collections Distribution of all our software on CD-ROM allows us to extend our concept of software collections that we started with the General Chemistry Collection. Such collections will contain all the previously published software that is still "in print" (i.e., is compatible with current operating systems and hardware) and any new programs that fall under the topic of the collection. Proposed topics in addition to General Chemistry currently include Advanced Chemistry, Instrument and Laboratory Simulations, and Spectroscopy. Eventually, all regular issues will be replaced by these collections, which will be updated annually or semiannually with new programs and updates to existing programs. Abstracts for all new programs will continue to appear in this column when a collection or its update is ready for publication. We will continue to offer special issues of single larger programs (e.g. Periodic Table Live!, Chemistry Comes Alive! volumes) on CD-ROM and video on videotape. Connect with Your Students outside Class JCE Software has always offered network licenses to allow instructors to make our software available to students in computer labs, but that model no longer fits the way many instructors and students work with computers. Many students (or their families) own a personal computer allowing them much more flexibility than a campus computer lab. Many instructors utilize the World Wide Web, creating HTML pages for students to use. JCE Software has options available to take advantage of both of these developments. Software Adoption To provide students who own computers access to JCE Software programs, consider adopting one or more of our CD-ROMs as you would a textbook. The General Chemistry Collection has been adopted by several general chemistry courses. We can arrange to bundle CDs with laboratory manuals or to be sold separately to students through the campus bookstore. The cost per CD can be quite low (as little as $5) when large numbers are ordered, making this a cost-effective method of allowing students access to the software they need whenever and wherever they desire. Web-Ready Publications Several JCE Software programs use HTML to present the material. Viewed with the ubiquitous Internet Browser, HTML is compatible with both Mac OS and Windows (as well most other current operating systems) and provides a flexible hypermedia interface that is familiar to an increasing number of instructors and students. HTML-based publications are also ready for use on local intranets, with appropriate licensing, and can be readily incorporated into other HTML-based materials. Already published in this format are: Chemistry Comes Alive!, Volumes 1 and 2 (Special Issues 18 and 21), Flying over Atoms (Special Issue 19), and Periodic Table Live! Second Edition (Special Issue 17). Solid State Resources Second Edition (Special Issue 12) and Chemistry Comes Alive!, Volume 3 (Special Issue 23) will be available soon. Other submissions being developed in HTML format include ChemPages Laboratory and Multimedia General Chemistry Problems. Contact the JCE Software office to learn about licensing alternatives that take advantage of the World Wide Web. Periodic Table Live! 2nd ed. is one of JCE Software's "Web-ready" publications. Publication Plans for 2000 We have several exciting new issues planned for publication in the coming year. Chemistry Comes Alive! The Chemistry Comes Alive! (CCA!) series continues with additional CD-ROMs for Mac OS and Windows. Each volume in this series contains video and animations of chemical reactions that can be easily incorporated into your own computer-based presentations. Our digital video now uses state-of-the-art compression that yields higher quality video with smaller file sizes and data rates more suited for WWW delivery. Video for Periodic Table Live! 2nd edition, Chemistry Comes Alive! Volumes 3, ChemPages Laboratory, and Multimedia General Chemistry Problems use this new format. We will be releasing updates of CCA! Volumes 1 and 2 to take advantage of this new technology. We are very pleased with the results and think you will be also. The reaction of aluminum with chlorine is included in Chemistry Comes Alive! Volume 3. ChemPages Laboratory ChemPages Laboratory, developed by the New Traditions Curriculum Project at the University of Wisconsin-Madison, is an HTML-based CD-ROM for Mac OS and Windows that contains lessons and tutorials to prepare introductory chemistry students to work in the laboratory. It includes text, photographs, computer graphics, animations, digital video, and voice narration to introduce students to the laboratory equipment and procedures. ChemPages Laboratory teaches introductory chemistry students about laboratory instruments, equipment, and procedures. Versatile Video Video demonstrating the "drinking bird" is included in the Chemistry Comes Alive! video collection. Video from this collection can be incorporated into many other projects. As an example, David Whisnant has used the drinking bird in his Multimedia General Chemistry Problems, where students view the video and are asked to explain why the bird bobs up and down. JCE Software anticipates publication of Multimedia General Chemistry Problems on CD-ROM for Mac OS and Windows in 2000. It will be "Web-ready". General Chemistry Collection, 4th Edition The General Chemistry Collection will be revised early in the summer and CDs will be shipped in time for fall adoptions. The 4th edition will include JCE Software publications for general chemistry published in 1999, as well as any programs for general chemistry accepted in 2000. Regular Issues We have had many recent submissions and submissions of work in progress. In 2000 we will work with the authors and our peer-reviewers to complete and publish these submissions individually or as part of a software collection on CD-ROM. An Invitation In collaboration with JCE Online we plan to make available in 2000 more support files for JCE Software. These will include not only troubleshooting tips and technical support notes, but also supporting information submitted by users such as lessons, specific assignments, and activities using JCE Software publications. All JCE Software users are invited to contribute to this area. Get in touch with JCE Software and let us know how you are using our materials so that we can share your ideas with others! Although the word software is in our name, many of our publications are not traditional software. We also publish video on videotape, videodisc, and CD-ROM and electronic documents (Mathcad and Mathematica, spreadsheet files and macros, HTML documents, and PowerPoint presentations). Most chemistry instructors who use a computer in their teaching have created or considered creating one or more of these for their classes. If you have an original computer presentation, electronic document, animation, video, or any other item that is not printed text it is probably an appropriate submission for JCE Software. By publishing your work in any branch of the Journal of Chemical Education, you will share your efforts with chemistry instructors and students all over the world and get professional recognition for your achievements. All JCE Software publications are Y2K compliant.

  12. Unresolved Technical Issues in Fair Interest Measurement.

    ERIC Educational Resources Information Center

    Cole, Nancy S.

    The problem of sex differences in interest measurement involves many technical issues and procedures. The purpose of this paper is to provide a description of the technical problems involved in construction, scoring, and interpretation of interest measures as related to sex differences and to suggest guidelines within these technical issues which…

  13. Cloud Security: Issues and Research Directions

    DTIC Science & Technology

    2014-11-18

    4. Cloud Computing Security: What Changes with Software - Defined Networking ? Maur´ıcio Tsugawa, Andr´ea Matsunaga, and Jos´e A. B. Fortes 5...machine’s memory from an untrusted or malicious hypervisor. In Chapter 4, Tsugawa et al. discuss the security issues introduced when Software - Defined ... Networking ( SDN ) is deployed within and across clouds. Chapters 5-9 are focused on the protection of data stored in the cloud. In Chapter 5, Wang et

  14. An Investigation of Agility Issues in Scrum Teams Using Agility Indicators

    NASA Astrophysics Data System (ADS)

    Pikkarainen, Minna; Wang, Xiaofeng

    Agile software development methods have emerged and become increasingly popular in recent years; yet the issues encountered by software development teams that strive to achieve agility using agile methods are yet to be explored systematically. Built upon a previous study that has established a set of indicators of agility, this study investigates what issues are manifested in software development teams using agile methods. It is focussed on Scrum teams particularly. In other words, the goal of the chapter is to evaluate Scrum teams using agility indicators and therefore to further validate previously presented agility indicators within the additional cases. A multiple case study research method is employed. The findings of the study reveal that the teams using Scrum do not necessarily achieve agility in terms of team autonomy, sharing, stability and embraced uncertainty. The possible reasons include previous organizational plan-driven culture, resistance towards the Scrum roles and changing resources.

  15. [European community guidelines and standards in indoor air quality: what proposals for Italy].

    PubMed

    Settimo, Gaetano; D'Alessandro, Daniela

    2014-01-01

    Indoor air quality is an issue on which to focus because of the increasing number of exposed population and in view of the strong public feeling on this issue. This paper reports the rules of EU and several European countries about indoor air quality, focusing on the initiatives performed in Italy to respond to WHO recommendations. Several EU countries have introduced in their legislation rules relating to indoor air quality. At the moment, in Italy, a reference rule has not been issued. For this reason, up to date main informations concerning some guidelines or reference values in indoor air, to be used for a first comparison, are those obtained by the scientific literature, or by the guidelines issued by other European countries or, for analogy, by other standard values such as limit or reference values regarding outdoor air. Even the EU, while reaffirming the priority of energy efficiency measures, recommends healthier indoor environments and the development of a specific European strategy on the issue of indoor air quality. The National Study Group on indoor pollution of the Italian National Health Institute (ISS), is working for the development of shared technical and scientific documents, in order to provide greater uniformity of actions at national level, waiting for a legal framework for indoor air quality, in the light of the indication already produced by the WHO.

  16. Orbiter subsystem hardware/software interaction analysis. Volume 8: Forward reaction control system

    NASA Technical Reports Server (NTRS)

    Becker, D. D.

    1980-01-01

    The results of the orbiter hardware/software interaction analysis for the AFT reaction control system are presented. The interaction between hardware failure modes and software are examined in order to identify associated issues and risks. All orbiter subsystems and interfacing program elements which interact with the orbiter computer flight software are analyzed. The failure modes identified in the subsystem/element failure mode and effects analysis are discussed.

  17. Pilot interaction with automated airborne decision making systems

    NASA Technical Reports Server (NTRS)

    Rouse, W. B.; Hammer, J. M.; Mitchell, C. M.; Morris, N. M.; Lewis, C. M.; Yoon, W. C.

    1985-01-01

    Progress was made in the three following areas. In the rule-based modeling area, two papers related to identification and significane testing of rule-based models were presented. In the area of operator aiding, research focused on aiding operators in novel failure situations; a discrete control modeling approach to aiding PLANT operators was developed; and a set of guidelines were developed for implementing automation. In the area of flight simulator hardware and software, the hardware will be completed within two months and initial simulation software will then be integrated and tested.

  18. NASA Software Engineering Benchmarking Study

    NASA Technical Reports Server (NTRS)

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

    2013-01-01

    To identify best practices for the improvement of software engineering on projects, NASA's Offices of Chief Engineer (OCE) and Safety and Mission Assurance (OSMA) formed a team led by Heather Rarick and Sally Godfrey to conduct this benchmarking study. The primary goals of the study are to identify best practices that: Improve the management and technical development of software intensive systems; Have a track record of successful deployment by aerospace industries, universities [including research and development (R&D) laboratories], and defense services, as well as NASA's own component Centers; and Identify candidate solutions for NASA's software issues. Beginning in the late fall of 2010, focus topics were chosen and interview questions were developed, based on the NASA top software challenges. Between February 2011 and November 2011, the Benchmark Team interviewed a total of 18 organizations, consisting of five NASA Centers, five industry organizations, four defense services organizations, and four university or university R and D laboratory organizations. A software assurance representative also participated in each of the interviews to focus on assurance and software safety best practices. Interviewees provided a wealth of information on each topic area that included: software policy, software acquisition, software assurance, testing, training, maintaining rigor in small projects, metrics, and use of the Capability Maturity Model Integration (CMMI) framework, as well as a number of special topics that came up in the discussions. NASA's software engineering practices compared favorably with the external organizations in most benchmark areas, but in every topic, there were ways in which NASA could improve its practices. Compared to defense services organizations and some of the industry organizations, one of NASA's notable weaknesses involved communication with contractors regarding its policies and requirements for acquired software. One of NASA's strengths was its software assurance practices, which seemed to rate well in comparison to the other organizational groups and also seemed to include a larger scope of activities. An unexpected benefit of the software benchmarking study was the identification of many opportunities for collaboration in areas including metrics, training, sharing of CMMI experiences and resources such as instructors and CMMI Lead Appraisers, and even sharing of assets such as documented processes. A further unexpected benefit of the study was the feedback on NASA practices that was received from some of the organizations interviewed. From that feedback, other potential areas where NASA could improve were highlighted, such as accuracy of software cost estimation and budgetary practices. The detailed report contains discussion of the practices noted in each of the topic areas, as well as a summary of observations and recommendations from each of the topic areas. The resulting 24 recommendations from the topic areas were then consolidated to eliminate duplication and culled into a set of 14 suggested actionable recommendations. This final set of actionable recommendations, listed below, are items that can be implemented to improve NASA's software engineering practices and to help address many of the items that were listed in the NASA top software engineering issues. 1. Develop and implement standard contract language for software procurements. 2. Advance accurate and trusted software cost estimates for both procured and in-house software and improve the capture of actual cost data to facilitate further improvements. 3. Establish a consistent set of objectives and expectations, specifically types of metrics at the Agency level, so key trends and models can be identified and used to continuously improve software processes and each software development effort. 4. Maintain the CMMI Maturity Level requirement for critical NASA projects and use CMMI to measure organizations developing software for NASA. 5.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.

  19. Contingency theoretic methodology for agent-based web-oriented manufacturing systems

    NASA Astrophysics Data System (ADS)

    Durrett, John R.; Burnell, Lisa J.; Priest, John W.

    2000-12-01

    The development of distributed, agent-based, web-oriented, N-tier Information Systems (IS) must be supported by a design methodology capable of responding to the convergence of shifts in business process design, organizational structure, computing, and telecommunications infrastructures. We introduce a contingency theoretic model for the use of open, ubiquitous software infrastructure in the design of flexible organizational IS. Our basic premise is that developers should change in the way they view the software design process from a view toward the solution of a problem to one of the dynamic creation of teams of software components. We postulate that developing effective, efficient, flexible, component-based distributed software requires reconceptualizing the current development model. The basic concepts of distributed software design are merged with the environment-causes-structure relationship from contingency theory; the task-uncertainty of organizational- information-processing relationships from information processing theory; and the concept of inter-process dependencies from coordination theory. Software processes are considered as employees, groups of processes as software teams, and distributed systems as software organizations. Design techniques already used in the design of flexible business processes and well researched in the domain of the organizational sciences are presented. Guidelines that can be utilized in the creation of component-based distributed software will be discussed.

  20. ISEES: an institute for sustainable software to accelerate environmental science

    NASA Astrophysics Data System (ADS)

    Jones, M. B.; Schildhauer, M.; Fox, P. A.

    2013-12-01

    Software is essential to the full science lifecycle, spanning data acquisition, processing, quality assessment, data integration, analysis, modeling, and visualization. Software runs our meteorological sensor systems, our data loggers, and our ocean gliders. Every aspect of science is impacted by, and improved by, software. Scientific advances ranging from modeling climate change to the sequencing of the human genome have been rendered possible in the last few decades due to the massive improvements in the capabilities of computers to process data through software. This pivotal role of software in science is broadly acknowledged, while simultaneously being systematically undervalued through minimal investments in maintenance and innovation. As a community, we need to embrace the creation, use, and maintenance of software within science, and address problems such as code complexity, openness,reproducibility, and accessibility. We also need to fully develop new skills and practices in software engineering as a core competency in our earth science disciplines, starting with undergraduate and graduate education and extending into university and agency professional positions. The Institute for Sustainable Earth and Environmental Software (ISEES) is being envisioned as a community-driven activity that can facilitate and galvanize activites around scientific software in an analogous way to synthesis centers such as NCEAS and NESCent that have stimulated massive advances in ecology and evolution. We will describe the results of six workshops (Science Drivers, Software Lifecycles, Software Components, Workforce Development and Training, Sustainability and Governance, and Community Engagement) that have been held in 2013 to envision such an institute. We will present community recommendations from these workshops and our strategic vision for how ISEES will address the technical issues in the software lifecycle, sustainability of the whole software ecosystem, and the critical issue of computational training for the scientific community. Process for envisioning ISEES.

Top