WorldWideScience

Sample records for software requirements specifications

  1. Light duty utility arm software requirements specification

    Kiebel, G.R.

    1995-01-01

    This document defines the software requirements for the integrated control and data acquisition system of the Light Duty Utility Arm (LDUA) System. It is intended to be used to guide the design of the application software, to be a basis for assessing the application software design, and to establish what is to be tested in the finished application software product

  2. Incubator Display Software Cost Reduction Toolset Software Requirements Specification

    Moran, Susanne; Jeffords, Ralph

    2005-01-01

    The Incubator Display Software Requirements Specification was initially developed by Intrinsyx Technologies Corporation (Intrinsyx) under subcontract to Lockheed Martin, Contract Number NAS2-02090, for the National Aeronautics and Space Administration (NASA) Ames Research Center (ARC) Space Station Biological Research Project (SSBRP). The Incubator Display is a User Payload Application (UPA) used to control an Incubator subrack payload for the SSBRP. The Incubator Display functions on-orbit as part of the subrack payload laptop, on the ground as part of the Communication and Data System (CDS) ground control system, and also as part of the crew training environment.

  3. Requirements Specification for Open Source Software Selection

    YANG, YING

    2008-01-01

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

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

    2012-08-22

    ... Computer Software and Complex Electronics Used in Safety Systems of Nuclear Power Plants AGENCY: Nuclear...-1209, ``Software Requirement Specifications for Digital Computer Software and Complex Electronics used... Electronics Engineers (ANSI/IEEE) Standard 830-1998, ``IEEE Recommended Practice for Software Requirements...

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

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

  6. Solid Waste Information and Tracking System (SWITS) Software Requirements Specification

    MAY, D.L.

    2000-01-01

    This document is the primary document establishing requirements for the Solid Waste Information and Tracking System (SWITS) as it is converted to a client-server architecture. The purpose is to provide the customer and the performing organizations with the requirements for the SWITS in the new environment. This Software Requirement Specification (SRS) describes the system requirements for the SWITS Project, and follows the PHMC Engineering Requirements, HNF-PRO-1819, and Computer Software Qualify Assurance Requirements, HNF-PRO-309, policies. This SRS includes sections on general description, specific requirements, references, appendices, and index. The SWITS system defined in this document stores information about the solid waste inventory on the Hanford site. Waste is tracked as it is generated, analyzed, shipped, stored, and treated. In addition to inventory reports a number of reports for regulatory agencies are produced

  7. Solid Waste Information and Tracking System (SWITS) Software Requirements Specification

    MAY, D.L.

    2000-03-22

    This document is the primary document establishing requirements for the Solid Waste Information and Tracking System (SWITS) as it is converted to a client-server architecture. The purpose is to provide the customer and the performing organizations with the requirements for the SWITS in the new environment. This Software Requirement Specification (SRS) describes the system requirements for the SWITS Project, and follows the PHMC Engineering Requirements, HNF-PRO-1819, and Computer Software Qualify Assurance Requirements, HNF-PRO-309, policies. This SRS includes sections on general description, specific requirements, references, appendices, and index. The SWITS system defined in this document stores information about the solid waste inventory on the Hanford site. Waste is tracked as it is generated, analyzed, shipped, stored, and treated. In addition to inventory reports a number of reports for regulatory agencies are produced.

  8. Specification for Visual Requirements of Work-Centered Software Systems

    Knapp, James R; Chung, Soon M; Schmidt, Vincent A

    2006-01-01

    .... In order to ensure the coherent development and delivery of work-centered software products, WCSS visual requirements must be specified to capture the cognitive aspects of the user interface design...

  9. Software requirements

    Wiegers, Karl E

    2003-01-01

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

  10. Surveillance Analysis Computer System (SACS) software requirements specification (SRS)

    Glasscock, J.A.; Flanagan, M.J.

    1995-09-01

    This document is the primary document establishing requirements for the Surveillance Analysis Computer System (SACS) Database, an Impact Level 3Q system. The purpose is to provide the customer and the performing organization with the requirements for the SACS Project

  11. A requirements specification for a software design support system

    Noonan, Robert E.

    1988-01-01

    Most existing software design systems (SDSS) support the use of only a single design methodology. A good SDSS should support a wide variety of design methods and languages including structured design, object-oriented design, and finite state machines. It might seem that a multiparadigm SDSS would be expensive in both time and money to construct. However, it is proposed that instead an extensible SDSS that directly implements only minimal database and graphical facilities be constructed. In particular, it should not directly implement tools to faciliate language definition and analysis. It is believed that such a system could be rapidly developed and put into limited production use, with the experience gained used to refine and evolve the systems over time.

  12. An effective technique for the software requirements analysis of NPP safety-critical systems, based on software inspection, requirements traceability, and formal specification

    Koo, Seo Ryong; Seong, Poong Hyun; Yoo, Junbeom; Cha, Sung Deok; Yoo, Yeong Jae

    2005-01-01

    A thorough requirements analysis is indispensable for developing and implementing safety-critical software systems such as nuclear power plant (NPP) software systems because a single error in the requirements can generate serious software faults. However, it is very difficult to completely analyze system requirements. In this paper, an effective technique for the software requirements analysis is suggested. For requirements verification and validation (V and V) tasks, our technique uses software inspection, requirement traceability, and formal specification with structural decomposition. Software inspection and requirements traceability analysis are widely considered the most effective software V and V methods. Although formal methods are also considered an effective V and V activity, they are difficult to use properly in the nuclear fields as well as in other fields because of their mathematical nature. In this work, we propose an integrated environment (IE) approach for requirements, which is an integrated approach that enables easy inspection by combining requirement traceability and effective use of a formal method. The paper also introduces computer-aided tools for supporting IE approach for requirements. Called the nuclear software inspection support and requirements traceability (NuSISRT), the tool incorporates software inspection, requirement traceability, and formal specification capabilities. We designed the NuSISRT to partially automate software inspection and analysis of requirement traceability. In addition, for the formal specification and analysis, we used the formal requirements specification and analysis tool for nuclear engineering (NuSRS)

  13. Software Requirement Specifications For ASocial Media Threat Assessment Tool

    2017-12-01

    media means a much higher volume of threats than before, which taxes law enforcement’s ability to investigate each one. Complicating the investigation...Obtaining the identity of a Twitter account holder requires court paperwork based on probable cause or exigent circumstances. Second, social media...instant connectivity of social media means a much higher number of threats than before, which taxes law enforcement’s ability to investigate each one

  14. Software requirements specification document for the AREST code development

    Engel, D.W.; McGrail, B.P.; Whitney, P.D.; Gray, W.J.; Williford, R.E.; White, M.D.; Eslinger, P.W.; Altenhofen, M.K.

    1993-11-01

    The Analysis of the Repository Source Term (AREST) computer code was selected in 1992 by the U.S. Department of Energy. The AREST code will be used to analyze the performance of an underground high level nuclear waste repository. The AREST code is being modified by the Pacific Northwest Laboratory (PNL) in order to evaluate the engineered barrier and waste package designs, model regulatory compliance, analyze sensitivities, and support total systems performance assessment modeling. The current version of the AREST code was developed to be a very useful tool for analyzing model uncertainties and sensitivities to input parameters. The code has also been used successfully in supplying source-terms that were used in a total systems performance assessment. The current version, however, has been found to be inadequate for the comparison and selection of a design for the waste package. This is due to the assumptions and simplifications made in the selection of the process and system models. Thus, the new version of the AREST code will be designed to focus on the details of the individual processes and implementation of more realistic models. This document describes the requirements of the new models that will be implemented. Included in this document is a section describing the near-field environmental conditions for this waste package modeling, description of the new process models that will be implemented, and a description of the computer requirements for the new version of the AREST code

  15. Evaluation procedure of software requirements specification for digital I and C of KNGR

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

    2001-06-01

    The accuracy of the specification of requirements of a digital system is of prime importance to the acceptance and success of the system. The development, use, and regulation of computer systems in nuclear reactor Instrumentation and Control (I and C) systems to enhance reliability and safety is a complex issue. This report is one of a series of reports from the Korean Next Generation Reactor (KNGR) Software Safety Verification and Validation (SSVV) Task, Korea Atomic Energy Research Institute, which investigates different aspects of computer software in reactor I and C systems, and describes the engineering procedures for developing such a software. The purpose of this guideline is to give the software safety evaluator the trail map between the code and standards layer and the design methodology and documents layer for the software important to safety in nuclear power plants. Recently, the requirements specification of safety-critical software systems and safety analysis of them are being recognized as one of the important issues in the software life cycle, and being developed new regulatory positions and standards by the regulatory and the standardization organizations such as IAEA, IEC, and IEEE. We presented the procedure for evaluating the software requirements specifications of the KNGR protection systems. We believe it can be useful for both licenser and licensee to conduct an evaluation of the safety in the requirements phase of developing the software. The guideline consists of the requirements engineering for software of KNGR protection systems in chapter 1, the evaluation checklist of software requirements specification in chapter2.3, and the safety evaluation procedure of KNGR software requirements specification in chapter 2.4

  16. Hazard Analysis of Software Requirements Specification for Process Module of FPGA-based Controllers in NPP

    Jung; Sejin; Kim, Eui-Sub; Yoo, Junbeom [Konkuk University, Seoul (Korea, Republic of); Keum, Jong Yong; Lee, Jang-Soo [Korea Atomic Energy Research Institute, Daejeon (Korea, Republic of)

    2016-10-15

    Software in PLC, FPGA which are used to develop I and C system also should be analyzed to hazards and risks before used. NUREG/CR-6430 proposes the method for performing software hazard analysis. It suggests analysis technique for software affected hazards and it reveals that software hazard analysis should be performed with the aspects of software life cycle such as requirements analysis, design, detailed design, implements. It also provides the guide phrases for applying software hazard analysis. HAZOP (Hazard and operability analysis) is one of the analysis technique which is introduced in NUREG/CR-6430 and it is useful technique to use guide phrases. HAZOP is sometimes used to analyze the safety of software. Analysis method of NUREG/CR-6430 had been used in Korea nuclear power plant software for PLC development. Appropriate guide phrases and analysis process are selected to apply efficiently and NUREG/CR-6430 provides applicable methods for software hazard analysis is identified in these researches. We perform software hazard analysis of FPGA software requirements specification with two approaches which are NUREG/CR-6430 and HAZOP with using general GW. We also perform the comparative analysis with them. NUREG/CR-6430 approach has several pros and cons comparing with the HAZOP with general guide words and approach. It is enough applicable to analyze the software requirements specification of FPGA.

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

    Glasscock, J.A.

    1995-01-01

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

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

    Castro Mecías, L.T.

    2015-06-01

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

  19. Treated effluent disposal system process control computer software requirements and specification

    Graf, F.A. Jr.

    1994-01-01

    The software requirements for the monitor and control system that will be associated with the effluent collection pipeline system known as the 200 Area Treated Effluent Disposal System is covered. The control logic for the two pump stations and specific requirements for the graphic displays are detailed

  20. A discussion of higher order software concepts as they apply to functional requirements and specifications. [space shuttles and guidance

    Hamilton, M.

    1973-01-01

    The entry guidance software functional requirements (requirements design phase), its architectural requirements (specifications design phase), and the entry guidance software verified code are discussed. It was found that the proper integration of designs at both the requirements and specifications levels are of high priority consideration.

  1. Effects of Using Requirements Catalogs on Effectiveness and Productivity of Requirements Specification in a Software Project Management Course

    Fernández-Alemán, José Luis; Carrillo-de-Gea, Juan Manuel; Meca, Joaquín Vidal; Ros, Joaquín Nicolás; Toval, Ambrosio; Idri, Ali

    2016-01-01

    This paper presents the results of two educational experiments carried out to determine whether the process of specifying requirements (catalog-based reuse as opposed to conventional specification) has an impact on effectiveness and productivity in co-located and distributed software development environments. The participants in the experiments…

  2. Writing testable software requirements

    Knirk, D. [Sandia National Labs., Albuquerque, NM (United States)

    1997-11-01

    This tutorial identifies common problems in analyzing requirements in the problem and constructing a written specification of what the software is to do. It deals with two main problem areas: identifying and describing problem requirements, and analyzing and describing behavior specifications.

  3. Definition and specification for PACS. A checklist based on the standard ''IEEE Recommended Practice for Software Requirements Specifications''

    Koenig, H.; Klose, K.J.

    1999-01-01

    Problem: The formulation of requirements is necessary to control the goals of a PACS project. Furthermore, in this way, the scope of functionality necessary to support radiological working processes becomes clear. Method: Definitions of requirements and specification are formulated independently of systems according to the IEEE standard 'Recommended Practice for Software Requirements Specifications'. Definitions are given in the Request for Information, specifications in the Request for Proposal. Functional and non-functional requirements are distinguished. The solutions are rated with respect to scope, appropriateness and quality of implementation. Results: A PACS checklist was created according to the methods described above. It is published on the homepage of the 'Arbeitsgemeinschaft Informationstechnologie' (AGIT) within the 'Deutsche Roentgengesellschaft' (DRG) (http://www.uni-marburg.de/mzr.agit). Conclusion: The checklist provides a discussion forum which should contribute to an agreement on accepted basic PACS functionalities. (orig.) [de

  4. High-Level software requirements specification for the TWRS controlled baseline database system

    Spencer, S.G.

    1998-01-01

    This Software Requirements Specification (SRS) is an as-built document that presents the Tank Waste Remediation System (TWRS) Controlled Baseline Database (TCBD) in its current state. It was originally known as the Performance Measurement Control System (PMCS). Conversion to the new system name has not occurred within the current production system. Therefore, for simplicity, all references to TCBD are equivalent to PMCS references. This SRS will reference the PMCS designator from this point forward to capture the as-built SRS. This SRS is written at a high-level and is intended to provide the design basis for the PMCS. The PMCS was first released as the electronic data repository for cost, schedule, and technical administrative baseline information for the TAAS Program. During its initial development, the PMCS was accepted by the customer, TARS Business Management, with no formal documentation to capture the initial requirements

  5. [Definition and specification requirements for PAC-systems (picture archiving and communication system). A performance index with reference to the standard "IEEE Recommended Practice for Software Requirement Specifications"].

    König, H; Klose, K J

    1999-04-01

    The formulation of requirements is necessary to control the goals of a PACS project. Furthermore, in this way, the scope of functionality necessary to support radiological working processes becomes clear. Definitions of requirements and specification are formulated independently of systems according to the IEEE standard "Recommended Practice for Software Requirements Specifications". Definitions are given in the Request for Information, specifications in the Request for Proposal. Functional and non-functional requirements are distinguished. The solutions are rated with respect to scope, appropriateness and quality of implementation. A PACS checklist was created according to the methods described above. It is published on the homepage of the "Arbeitsgemeinschaft Informationstechnologie" (AGIT) within the "Deutsche Röntgengesellschaft" (DRG) (http://www.uni-marburg.de/mzr/agit). The checklist provides a discussion forum which should contribute to an agreement on accepted basic PACS functionalities.

  6. Neutrosophy for software requirement prioritization

    Ronald Barriga Dias

    2017-09-01

    Full Text Available Software engineers are involved in complex decisions that require multiples viewpoints. A specific case is the requirement prioritization process. This process is used to decide which software requirement to develop in certain release from a group of candidate requirements. Criteria involved in this process can involve indeterminacy. In this paper a software requirement prioritization model is develop based SVN numbers. Finally, an illustrative example is presented in order to show the proposed model.

  7. Waste Receiving and Processing Facility Module 1 Data Management System software requirements specification

    Rosnick, C.K.

    1996-01-01

    This document provides the software requirements for Waste Receiving and Processing (WRAP) Module 1 Data Management System (DMS). The DMS is one of the plant computer systems for the new WRAP 1 facility (Project W-0126). The DMS will collect, store and report data required to certify the low level waste (LLW) and transuranic (TRU) waste items processed at WRAP 1 as acceptable for shipment, storage, or disposal

  8. Waste Receiving and Processing Facility Module 1 Data Management System Software Requirements Specification

    Brann, E.C. II.

    1994-01-01

    This document provides the software requirements for Waste Receiving and Processing (WRAP) Module 1 Data Management System (DMS). The DMS is one of the plant computer systems for the new WRAP 1 facility (Project W-026). The DMS will collect, store and report data required to certify the low level waste (LLW) and transuranic (TRU) waste items processed at WRAP 1 as acceptable for shipment, storage, or disposal

  9. Waste Receiving and Processing Facility Module 1 Data Management System Software Requirements Specification

    Brann, E.C. II

    1994-09-09

    This document provides the software requirements for Waste Receiving and Processing (WRAP) Module 1 Data Management System (DMS). The DMS is one of the plant computer systems for the new WRAP 1 facility (Project W-026). The DMS will collect, store and report data required to certify the low level waste (LLW) and transuranic (TRU) waste items processed at WRAP 1 as acceptable for shipment, storage, or disposal.

  10. Specifications in software prototyping

    Luqi; Chang, Carl K.; Zhu, Hong

    1998-01-01

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

  11. TWRSview system requirements specification

    Caldwell, J.A.; Lee, A.K.

    1995-12-01

    This document provides the system requirements specification for the TWRSview software system. The TWRSview software system is being developed to integrate electronic data supporting the development of the TWRS technical baseline

  12. Software requirements specification for the program analysis and control system risk management module

    SCHAEFER, J.C.

    1999-01-01

    TWR Program Analysis and Control System Risk Module is used to facilitate specific data processes surrounding the Risk Management program of the Tank Waste Retrieval environment. This document contains the Risk Management system requirements of the database system

  13. Improving software requirements specification for safety-related systems using the fault tree developed by an object-based method

    Cepin, M.; Mavko, B.

    1998-01-01

    A modification of the fault tree analysis is presented. The new fault tree integrates structural and behavioral models of a system. Information on the system structure is captured in the name of each gate and basic event of the fault tree. Information on the system behavior is captured in their description. Behavior is expressed using the axiomatic notation based on first order predicate logic. The new fault tree is a useful model for analysis and improvement of software requirements specification. The benefit of such improvements is reduced probability of failures in specification, which in turn results in increased reliability of the software.(author)

  14. Solid Waste Information Tracking System (SWITS), Backlog Waste Modifications, Software Requirements Specification (SRS)

    Clark, R.E.

    1995-01-01

    Purpose of this document is to define the system requirements necessary to improve computer support for the WHC backlog waste business process through enhancements to the backlog waste function of the SWITS system. This SRS document covers enhancements to the SWITS system to support changes to the existing Backlog Waste screens including new data elements, label changes, and new pop-up screens. The pop-ups will allow the user to flag the processes that a waste container must have performed on it, and will provide history tracking of changes to data. A new screen will also be provided allowing Acceptable Services to perform mass updates to specific data in Backlog Waste table. The SWITS Backlog Waste enhancements in this document will support the project goals in WHC-SD-WM-003 and its Revision 1 (Radioactive Solid Waste Tracking System Conceptual Definition) for the control, tracing, and inventory management of waste as the packages are generated and moved through final disposal (cradle-to-grave)

  15. Specification of problems from the business goals in the context of early software requirements elicitation

    Carlos Mario Zapata-J.

    2014-01-01

    Full Text Available Una de las principales actividades de la educción temprana de requisitos de software es el reconocimiento y especificación de los problemas de la organización. Esta actividad tiene por objeto la definición de los requisitos iniciales y la satisfacción de las necesidades de los interesados. Estos problemas deben tener relación con los objetivos de la organización para lograr una aplicación de software contextualizada y alineada con la razón de ser de la organización. En los métodos de educción actuales basados en objetivos y problemas, las relaciones se detectan con la ayuda de la experiencia y conocimiento del analista y el interesado. Sin embargo aún no se logra trazabilidad entre objetivos y problemas. En este artículo se propone un método para la especificación de problemas a partir de objetivos organizacionales. Este método se compone de un conjunto de reglas sintácticas y semánticas que el analista usa para expresar los problemas a partir de las declaraciones de los objetivos. También, se presenta un ejemplo de laboratorio basado en el diagrama de objetivos de KAOS.

  16. The NLC Software Requirements Methodology

    Shoaee, Hamid

    2002-08-20

    We describe the software requirements and development methodology developed for the NLC control system. Given the longevity of that project, and the likely geographical distribution of the collaborating engineers, the planned requirements management process is somewhat more formal than the norm in high energy physics projects. The short term goals of the requirements process are to accurately estimate costs, to decompose the problem, and to determine likely technologies. The long term goal is to enable a smooth transition from high level functional requirements to specific subsystem and component requirements for individual programmers, and to support distributed development. The methodology covers both ends of that life cycle. It covers both the analytical and documentary tools for software engineering, and project management support. This paper introduces the methodology, which is fully described in [1].

  17. Software Testing Requires Variability

    Christensen, Henrik Bærbak

    2003-01-01

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

  18. Requirements Engineering for Software Integrity and Safety

    Leveson, Nancy G.

    2002-01-01

    Requirements flaws are the most common cause of errors and software-related accidents in operational software. Most aerospace firms list requirements as one of their most important outstanding software development problems and all of the recent, NASA spacecraft losses related to software (including the highly publicized Mars Program failures) can be traced to requirements flaws. In light of these facts, it is surprising that relatively little research is devoted to requirements in contrast with other software engineering topics. The research proposed built on our previous work. including both criteria for determining whether a requirements specification is acceptably complete and a new approach to structuring system specifications called Intent Specifications. This grant was to fund basic research on how these ideas could be extended to leverage innovative approaches to the problems of (1) reducing the impact of changing requirements, (2) finding requirements specification flaws early through formal and informal analysis, and (3) avoiding common flaws entirely through appropriate requirements specification language design.

  19. UTM TCL2 Software Requirements

    Smith, Irene S.; Rios, Joseph L.; McGuirk, Patrick O.; Mulfinger, Daniel G.; Venkatesan, Priya; Smith, David R.; Baskaran, Vijayakumar; Wang, Leo

    2017-01-01

    The Unmanned Aircraft Systems (UAS) Traffic Management (UTM) Technical Capability Level (TCL) 2 software implements the UTM TCL 2 software requirements described herein. These software requirements are linked to the higher level UTM TCL 2 System Requirements. Each successive TCL implements additional UTM functionality, enabling additional use cases. TCL 2 demonstrated how to enable expanded multiple operations by implementing automation for beyond visual line-of-sight, tracking operations, and operations flying over sparsely populated areas.

  20. Mining software specifications methodologies and applications

    Lo, David

    2011-01-01

    An emerging topic in software engineering and data mining, specification mining tackles software maintenance and reliability issues that cost economies billions of dollars each year. The first unified reference on the subject, Mining Software Specifications: Methodologies and Applications describes recent approaches for mining specifications of software systems. Experts in the field illustrate how to apply state-of-the-art data mining and machine learning techniques to address software engineering concerns. In the first set of chapters, the book introduces a number of studies on mining finite

  1. Exploration on Automated Software Requirement Document Readability Approaches

    Chen, Mingda; He, Yao

    2017-01-01

    Context. The requirements analysis phase, as the very beginning of software development process, has been identified as a quite important phase in the software development lifecycle. Software Requirement Specification (SRS) is the output of requirements analysis phase, whose quality factors play an important role in the evaluation work. Readability is a quite important SRS quality factor, but there are few available automated approaches for readability measurement, because of the tight depend...

  2. ENVIRONMENTAL SPECIFICATION REQUIREMENTS

    TIFFT, S.R.

    2003-01-01

    Through regulations, permitting or binding negotiations, Regulators establish requirements, limits, permit conditions and Notice of Construction (NOC) conditions with which the Office of River Protection (ORP) and the Tank Farm Contractor (TFC) must comply. Operating Specifications are technical limits which are set on a process to prevent injury to personnel, or damage to the facility or environment. The main purpose of this document is to provide specification limits and recovery actions for the TFC Environmental Surveillance Program at the Hanford Site. Specification limits are given for monitoring frequencies and permissible variation of readings from an established baseline or previous reading. The requirements in this document are driven by environmental considerations and data analysis issues, rather than facility design or personnel safety issues. This document is applicable to all single-shell tank (SST) and double-shell tank (DST) waste tanks, and the associated catch tanks and receiver tanks, and transfer systems. This Tank Farm Environmental Specifications Document (ESD) implements environmental-regulatory limits on the configuration and operation of the Hanford Tank Farms facility that have been established by Regulators. This ESD contains specific field operational limits and recovery actions for compliance with airborne effluent regulations and agreements, liquid effluents regulations and agreements, and environmental tank system requirements. The scope of this ESD is limited to conditions that have direct impact on Operations Projects or that Operations/Projects have direct impact upon. This document does not supercede or replace any DOE Orders, regulatory permits, notices of construction, or Regulatory agency agreements binding on the ORP or the TFC. Refer to the appropriate regulation, permit, or NOC for an inclusive listing of requirements

  3. ENVIRONMENTAL SPECIFICATION REQUIREMENTS

    TIFFT, S.R.

    2003-01-01

    Through regulations, permitting or binding negotiations, Regulators establish requirements, limits, permit conditions and Notice of Construction (NOC) conditions with which the Office of River Protection (ORP) and the Tank Farm Contractor (TFC) must comply. Operating Specifications are technical limits which are set on a process to prevent injury to personnel, or damage to the facility or environment. The main purpose of this document is to provide specification limits and recovery actions for the TFC Environmental Surveillance Program at the Hanford Site. Specification limits are given for monitoring frequencies and permissible variation of readings from an established baseline or previous reading. The requirements in this document are driven by environmental considerations and data analysis issues, rather than facility design or personnel safety issues. This document is applicable to all SST and DST waste tanks, and the associated catch tanks and receiver tanks, and transfer systems. This Tank Farm ESD implements environmental-regulatory limits on the configuration and operation of the Hanford Tank Farms facility that have been established by Regulators. This ESD contains specific field operational limits and recovery actions for compliance with airborne effluent regulations and agreements, liquid effluents regulations and agreements, and environmental tank system requirements. The scope of this ESD is limited to conditions that have direct impact on Operations/Projects or that Operations/Projects have direct impact upon. This document does not supercede or replace any DOE Orders, regulatory permits, notices of construction, or Regulatory agency agreements binding on the ORP or the TFC. Refer to the appropriate regulation, permit, or NOC for an inclusive listing of requirements

  4. Requirements engineering: foundation for software quality

    Daneva, Maia; Pastor, Oscar

    2016-01-01

    Welcome to the proceedings of the 22nd edition of REFSQ: the International Working Conference on Requirements Engineering – Foundation for Software Quality! Requirements engineering (RE) has been recognized as a critical factor that impacts the quality of software, systems, and services. Since the

  5. Proposing an Evidence-Based Strategy for Software Requirements Engineering.

    Lindoerfer, Doris; Mansmann, Ulrich

    2016-01-01

    This paper discusses an evidence-based approach to software requirements engineering. The approach is called evidence-based, since it uses publications on the specific problem as a surrogate for stakeholder interests, to formulate risks and testing experiences. This complements the idea that agile software development models are more relevant, in which requirements and solutions evolve through collaboration between self-organizing cross-functional teams. The strategy is exemplified and applied to the development of a Software Requirements list used to develop software systems for patient registries.

  6. Identify and Manage the Software Requirements Volatility

    Khloud Abd Elwahab; Mahmoud Abd EL Latif; Sherif Kholeif

    2016-01-01

    Management of software requirements volatility through development of life cycle is a very important stage. It helps the team to control significant impact all over the project (cost, time and effort), and also it keeps the project on track, to finally satisfy the user which is the main success criteria for the software project. In this research paper, we have analysed the root causes of requirements volatility through a proposed framework presenting the requirements volatility causes and how...

  7. Analyzing Software Requirements Errors in Safety-Critical, Embedded Systems

    Lutz, Robyn R.

    1993-01-01

    This paper analyzes the root causes of safety-related software errors in safety-critical, embedded systems. The results show that software errors identified as potentially hazardous to the system tend to be produced by different error mechanisms than non- safety-related software errors. Safety-related software errors are shown to arise most commonly from (1) discrepancies between the documented requirements specifications and the requirements needed for correct functioning of the system and (2) misunderstandings of the software's interface with the rest of the system. The paper uses these results to identify methods by which requirements errors can be prevented. The goal is to reduce safety-related software errors and to enhance the safety of complex, embedded systems.

  8. Requirements Engineering in Building Climate Science Software

    Batcheller, Archer L.

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

  9. Software engineering with application-specific languages

    Campbell, David J.; Barker, Linda; Mitchell, Deborah; Pollack, Robert H.

    1993-01-01

    Application-Specific Languages (ASL's) are small, special-purpose languages that are targeted to solve a specific class of problems. Using ASL's on software development projects can provide considerable cost savings, reduce risk, and enhance quality and reliability. ASL's provide a platform for reuse within a project or across many projects and enable less-experienced programmers to tap into the expertise of application-area experts. ASL's have been used on several software development projects for the Space Shuttle Program. On these projects, the use of ASL's resulted in considerable cost savings over conventional development techniques. Two of these projects are described.

  10. Requirements engineering for software and systems

    Laplante, Phillip A

    2014-01-01

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

  11. Software requirements management based on use cases

    Xiao Jin

    2009-01-01

    In this paper, the requirements management based on use cases is theoretically explored, and a multi-layer use-case model is introduced, which combined with three levels of use cases and a single use-case refinement model. Through the practice in a software project, the multi-layer use-case model provides a good solution on how to control the requirements scope and change, and provides the balance of work assignment between customer departments, information management departments and software development outsourcing team. (authors)

  12. Capturing security requirements for software systems.

    El-Hadary, Hassan; El-Kassas, Sherif

    2014-07-01

    Security is often an afterthought during software development. Realizing security early, especially in the requirement phase, is important so that security problems can be tackled early enough before going further in the process and avoid rework. A more effective approach for security requirement engineering is needed to provide a more systematic way for eliciting adequate security requirements. This paper proposes a methodology for security requirement elicitation based on problem frames. The methodology aims at early integration of security with software development. The main goal of the methodology is to assist developers elicit adequate security requirements in a more systematic way during the requirement engineering process. A security catalog, based on the problem frames, is constructed in order to help identifying security requirements with the aid of previous security knowledge. Abuse frames are used to model threats while security problem frames are used to model security requirements. We have made use of evaluation criteria to evaluate the resulting security requirements concentrating on conflicts identification among requirements. We have shown that more complete security requirements can be elicited by such methodology in addition to the assistance offered to developers to elicit security requirements in a more systematic way.

  13. Capturing security requirements for software systems

    Hassan El-Hadary

    2014-07-01

    Full Text Available Security is often an afterthought during software development. Realizing security early, especially in the requirement phase, is important so that security problems can be tackled early enough before going further in the process and avoid rework. A more effective approach for security requirement engineering is needed to provide a more systematic way for eliciting adequate security requirements. This paper proposes a methodology for security requirement elicitation based on problem frames. The methodology aims at early integration of security with software development. The main goal of the methodology is to assist developers elicit adequate security requirements in a more systematic way during the requirement engineering process. A security catalog, based on the problem frames, is constructed in order to help identifying security requirements with the aid of previous security knowledge. Abuse frames are used to model threats while security problem frames are used to model security requirements. We have made use of evaluation criteria to evaluate the resulting security requirements concentrating on conflicts identification among requirements. We have shown that more complete security requirements can be elicited by such methodology in addition to the assistance offered to developers to elicit security requirements in a more systematic way.

  14. Capturing security requirements for software systems

    El-Hadary, Hassan; El-Kassas, Sherif

    2014-01-01

    Security is often an afterthought during software development. Realizing security early, especially in the requirement phase, is important so that security problems can be tackled early enough before going further in the process and avoid rework. A more effective approach for security requirement engineering is needed to provide a more systematic way for eliciting adequate security requirements. This paper proposes a methodology for security requirement elicitation based on problem frames. The methodology aims at early integration of security with software development. The main goal of the methodology is to assist developers elicit adequate security requirements in a more systematic way during the requirement engineering process. A security catalog, based on the problem frames, is constructed in order to help identifying security requirements with the aid of previous security knowledge. Abuse frames are used to model threats while security problem frames are used to model security requirements. We have made use of evaluation criteria to evaluate the resulting security requirements concentrating on conflicts identification among requirements. We have shown that more complete security requirements can be elicited by such methodology in addition to the assistance offered to developers to elicit security requirements in a more systematic way. PMID:25685514

  15. BBN based Quantitative Assessment of Software Design Specification

    Eom, Heung-Seop; Park, Gee-Yong; Kang, Hyun-Gook; Kwon, Kee-Choon; Chang, Seung-Cheol

    2007-01-01

    Probabilistic Safety Assessment (PSA), which is one of the important methods in assessing the overall safety of a nuclear power plant (NPP), requires quantitative reliability information of safety-critical software, but the conventional reliability assessment methods can not provide enough information for PSA of a NPP. Therefore current PSA which includes safety-critical software does not usually consider the reliability of the software or uses arbitrary values for it. In order to solve this situation this paper proposes a method that can produce quantitative reliability information of safety-critical software for PSA by making use of Bayesian Belief Networks (BBN). BBN has generally been used to model an uncertain system in many research fields including the safety assessment of software. The proposed method was constructed by utilizing BBN which can combine the qualitative and the quantitative evidence relevant to the reliability of safety critical software. The constructed BBN model can infer a conclusion in a formal and a quantitative way. A case study was carried out with the proposed method to assess the quality of software design specification (SDS) of safety-critical software that will be embedded in a reactor protection system. The intermediate V and V results of the software design specification were used as inputs to the BBN model

  16. Spectrum analysis on quality requirements consideration in software design documents.

    Kaiya, Haruhiko; Umemura, Masahiro; Ogata, Shinpei; Kaijiri, Kenji

    2013-12-01

    Software quality requirements defined in the requirements analysis stage should be implemented in the final products, such as source codes and system deployment. To guarantee this meta-requirement, quality requirements should be considered in the intermediate stages, such as the design stage or the architectural definition stage. We propose a novel method for checking whether quality requirements are considered in the design stage. In this method, a technique called "spectrum analysis for quality requirements" is applied not only to requirements specifications but also to design documents. The technique enables us to derive the spectrum of a document, and quality requirements considerations in the document are numerically represented in the spectrum. We can thus objectively identify whether the considerations of quality requirements in a requirements document are adapted to its design document. To validate the method, we applied it to commercial software systems with the help of a supporting tool, and we confirmed that the method worked well.

  17. A Requirement Specification Language for AADL

    2016-06-01

    models. The objective of ReqSpec is to support the elicitation , definition, and modeling of requirements for real-time embedded systems in an iterative...A Requirement Specification Language for AADL Peter H. Feiler Julien Delange Lutz Wrage June 2016 TECHNICAL REPORT CMU/SEI-2016-TR-008...is required for any other external and/or commercial use. Requests for permission should be directed to the Software En- gineering Institute at

  18. Property Specification Patterns for intelligence building software

    Chun, Seungsu

    2018-03-01

    In this paper, through the property specification pattern research for Modal MU(μ) logical aspects present a single framework based on the pattern of intelligence building software. In this study, broken down by state property specification pattern classification of Dwyer (S) and action (A) and was subdivided into it again strong (A) and weaknesses (E). Through these means based on a hierarchical pattern classification of the property specification pattern analysis of logical aspects Mu(μ) was applied to the pattern classification of the examples used in the actual model checker. As a result, not only can a more accurate classification than the existing classification systems were easy to create and understand the attributes specified.

  19. Knowledge-based requirements analysis for automating software development

    Markosian, Lawrence Z.

    1988-01-01

    We present a new software development paradigm that automates the derivation of implementations from requirements. In this paradigm, informally-stated requirements are expressed in a domain-specific requirements specification language. This language is machine-understable and requirements expressed in it are captured in a knowledge base. Once the requirements are captured, more detailed specifications and eventually implementations are derived by the system using transformational synthesis. A key characteristic of the process is that the required human intervention is in the form of providing problem- and domain-specific engineering knowledge, not in writing detailed implementations. We describe a prototype system that applies the paradigm in the realm of communication engineering: the prototype automatically generates implementations of buffers following analysis of the requirements on each buffer.

  20. Using Computer-Aided Software Engineering (CASE)--tools to document the current logical model of a system for DoD requirements specifications.

    Ganzer, Donna A.

    1987-01-01

    Approved for public release; distribution is unlimited The Naval Postgraduate School's final exam scheduling system serves as a test case with which to compare two commercially available Computer-Aided Software Engineering (CASE) tools. The tools, Nastec Corporation's DesignAid (Release 3.55) and Index Technology's Excelerator (Release 1.7) are used to create Section 4.1 of two Abbreviated Systems Decision Papers to determine if their output can satisfy and should replace some of the Life...

  1. Technical specifications requirements: Automated reasoning applications

    Lidsky, L.M.; Dobrzeniecki, A.B.

    1990-03-01

    Several software systems were developed and tested to determine what advantages could be gained from explicitly translating complicated regulatory requirements into computerized relationships. The Technical Specifications for US nuclear power plants were chosen as the test-bed application domain, and two analysis systems were developed to monitor plant compliance with operational limits, and track and schedule equipment test and maintenance activities mandated by Technical Specifications. Choosing PROLOG as the computer language to represent these regulatory requirements resulted in a natural match between the semantic structure of the written specifications and the corollary coded rules. Additional research results affirmed the utility of declarative programming styles, explicit management of problem complexity, and attention to the robustness and flexibility of the overall software systems. 5 refs., 2 figs

  2. Graph-based software specification and verification

    Kastenberg, H.

    2008-01-01

    The (in)correct functioning of many software systems heavily influences the way we qualify our daily lives. Software companies as well as academic computer science research groups spend much effort on applying and developing techniques for improving the correctness of software systems. In this

  3. Aligning Requirements-Driven Software Processes with IT Governance

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

    2017-01-01

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

  4. ROS signalling - specificity is required

    Møller, Ian M; Sweetlove, Lee J

    2010-01-01

    Reactive oxygen species (ROS) production increases in plants under stress. ROS can damage cellular components, but they can also act in signal transduction to help the cell counteract the oxidative damage in the stressed compartment. H2O2 might induce a general stress response, but it does not have...... the required specificity to selectively regulate nuclear genes required for dealing with localized stress, e.g. in chloroplasts or mitochondria. Here we argue that peptides deriving from proteolytic breakdown of oxidatively damaged proteins have the requisite specificity to act as secondary ROS messengers...... and regulate source-specific genes and in this way contribute to retrograde ROS signalling during oxidative stress. Likewise, unmodified peptides deriving from the breakdown of redundant proteins could help coordinate organellar and nuclear gene expression...

  5. Graph Based Verification of Software Evolution Requirements

    Ciraci, S.

    2009-01-01

    Due to market demands and changes in the environment, software systems have to evolve. However, the size and complexity of the current software systems make it time consuming to incorporate changes. During our collaboration with the industry, we observed that the developers spend much time on the

  6. A Quantitative Study of Global Software Development Teams, Requirements, and Software Projects

    Parker, Linda L.

    2016-01-01

    The study explored the relationship between global software development teams, effective software requirements, and stakeholders' perception of successful software development projects within the field of information technology management. It examined the critical relationship between Global Software Development (GSD) teams creating effective…

  7. Outsourcing the development of specific application software using the ESA software engineering standards the SPS software Interlock System

    Denis, B

    1995-01-01

    CERN is considering outsourcing as a solution to the reduction of staff. To need to re-engineer the SPS Software Interlock System provided an opportunity to explore the applicability of outsourcing to our specific controls environment and the ESA PSS-05 standards were selected for the requirements specification, the development, the control and monitoring and the project management. The software produced by the contractor is now fully operational. After outlining the scope and the complexity of the project, a discussion on the ESA PSS-05 will be presented: the choice, the way these standards improve the outsourcing process, the quality induced but also the need to adapt them and their limitation in the definition of the customer-supplier relationship. The success factors and the difficulties of development under contract will also be discussed. The maintenance aspect and the impact on in-house developments will finally be addressed.

  8. Generic Safety Requirements for Developing Safe Insulin Pump Software

    Zhang, Yi; Jetley, Raoul; Jones, Paul L; Ray, Arnab

    2011-01-01

    Background The authors previously introduced a highly abstract generic insulin infusion pump (GIIP) model that identified common features and hazards shared by most insulin pumps on the market. The aim of this article is to extend our previous work on the GIIP model by articulating safety requirements that address the identified GIIP hazards. These safety requirements can be validated by manufacturers, and may ultimately serve as a safety reference for insulin pump software. Together, these two publications can serve as a basis for discussing insulin pump safety in the diabetes community. Methods In our previous work, we established a generic insulin pump architecture that abstracts functions common to many insulin pumps currently on the market and near-future pump designs. We then carried out a preliminary hazard analysis based on this architecture that included consultations with many domain experts. Further consultation with domain experts resulted in the safety requirements used in the modeling work presented in this article. Results Generic safety requirements for the GIIP model are presented, as appropriate, in parameterized format to accommodate clinical practices or specific insulin pump criteria important to safe device performance. Conclusions We believe that there is considerable value in having the diabetes, academic, and manufacturing communities consider and discuss these generic safety requirements. We hope that the communities will extend and revise them, make them more representative and comprehensive, experiment with them, and use them as a means for assessing the safety of insulin pump software designs. One potential use of these requirements is to integrate them into model-based engineering (MBE) software development methods. We believe, based on our experiences, that implementing safety requirements using MBE methods holds promise in reducing design/implementation flaws in insulin pump development and evolutionary processes, therefore improving

  9. Requirements: Towards an understanding on why software projects fail

    Hussain, Azham; Mkpojiogu, Emmanuel O. C.

    2016-08-01

    Requirement engineering is at the foundation of every successful software project. There are many reasons for software project failures; however, poorly engineered requirements process contributes immensely to the reason why software projects fail. Software project failure is usually costly and risky and could also be life threatening. Projects that undermine requirements engineering suffer or are likely to suffer from failures, challenges and other attending risks. The cost of project failures and overruns when estimated is very huge. Furthermore, software project failures or overruns pose a challenge in today's competitive market environment. It affects the company's image, goodwill, and revenue drive and decreases the perceived satisfaction of customers and clients. In this paper, requirements engineering was discussed. Its role in software projects success was elaborated. The place of software requirements process in relation to software project failure was explored and examined. Also, project success and failure factors were also discussed with emphasis placed on requirements factors as they play a major role in software projects' challenges, successes and failures. The paper relied on secondary data and empirical statistics to explore and examine factors responsible for the successes, challenges and failures of software projects in large, medium and small scaled software companies.

  10. Training Requirements and Information Management System. Software user guide

    Cillan, T.F.; Hodgson, M.A.

    1992-05-01

    This is the software user`s guide for the Training Requirements and Information Management System. This guide defines and describes the software operating procedures as they apply to the end user of the software program. This guide is intended as a reference tool for the user who already has an indepth knowledge of the Training Requirements and Information Management System functions and data reporting requirement.

  11. Traceability of Requirements and Software Architecture for Change Management

    Göknil, Arda

    2011-01-01

    At the present day, software systems get more and more complex. The requirements of software systems change continuously and new requirements emerge frequently. New and/or modified requirements are integrated with the existing ones, and adaptations to the architecture and source code of the system

  12. Section 508 Electronic Information Accessibility Requirements for Software Development

    Ellis, Rebecca

    2014-01-01

    Section 508 Subpart B 1194.21 outlines requirements for operating system and software development in order to create a product that is accessible to users with various disabilities. This portion of Section 508 contains a variety of standards to enable those using assistive technology and with visual, hearing, cognitive and motor difficulties to access all information provided in software. The focus on requirements was limited to the Microsoft Windows® operating system as it is the predominant operating system used at this center. Compliance with this portion of the requirements can be obtained by integrating the requirements into the software development cycle early and by remediating issues in legacy software if possible. There are certain circumstances with software that may arise necessitating an exemption from these requirements, such as design or engineering software using dynamically changing graphics or numbers to convey information. These exceptions can be discussed with the Section 508 Coordinator and another method of accommodation used.

  13. Traceability of Software Safety Requirements in Legacy Safety Critical Systems

    Hill, Janice L.

    2007-01-01

    How can traceability of software safety requirements be created for legacy safety critical systems? Requirements in safety standards are imposed most times during contract negotiations. On the other hand, there are instances where safety standards are levied on legacy safety critical systems, some of which may be considered for reuse for new applications. Safety standards often specify that software development documentation include process-oriented and technical safety requirements, and also require that system and software safety analyses are performed supporting technical safety requirements implementation. So what can be done if the requisite documents for establishing and maintaining safety requirements traceability are not available?

  14. Experimental analysis of specification language diversity impact on NPP software diversity

    Yoo, Chang Sik

    1999-02-01

    In order to increase computer system reliability, software fault tolerance methods have been adopted to some safety critical systems including NPP. Prevention of software common mode failure is very crucial problem in software fault tolerance, but the effective method for this problem is not found yet. In our research, to find out an effective method for prevention of software common mode failure, the impact of specification language diversity on NPP software diversity was examined experimentally. Three specification languages were used to compose three requirements specifications, and programmers made twelve product codes from the specifications. From the product codes analysis, using fault diversity criteria, we concluded that diverse specification language method would enhance program diversity through diversification of requirements specification imperfections

  15. Enhancing requirements engineering for patient registry software systems with evidence-based components.

    Lindoerfer, Doris; Mansmann, Ulrich

    2017-07-01

    Patient registries are instrumental for medical research. Often their structures are complex and their implementations use composite software systems to meet the wide spectrum of challenges. Commercial and open-source systems are available for registry implementation, but many research groups develop their own systems. Methodological approaches in the selection of software as well as the construction of proprietary systems are needed. We propose an evidence-based checklist, summarizing essential items for patient registry software systems (CIPROS), to accelerate the requirements engineering process. Requirements engineering activities for software systems follow traditional software requirements elicitation methods, general software requirements specification (SRS) templates, and standards. We performed a multistep procedure to develop a specific evidence-based CIPROS checklist: (1) A systematic literature review to build a comprehensive collection of technical concepts, (2) a qualitative content analysis to define a catalogue of relevant criteria, and (3) a checklist to construct a minimal appraisal standard. CIPROS is based on 64 publications and covers twelve sections with a total of 72 items. CIPROS also defines software requirements. Comparing CIPROS with traditional software requirements elicitation methods, SRS templates and standards show a broad consensus but differences in issues regarding registry-specific aspects. Using an evidence-based approach to requirements engineering for registry software adds aspects to the traditional methods and accelerates the software engineering process for registry software. The method we used to construct CIPROS serves as a potential template for creating evidence-based checklists in other fields. The CIPROS list supports developers in assessing requirements for existing systems and formulating requirements for their own systems, while strengthening the reporting of patient registry software system descriptions. It may be

  16. PDSS/IMC requirements and functional specifications

    1983-01-01

    The system (software and hardware) requirements for the Payload Development Support System (PDSS)/Image Motion Compensator (IMC) are provided. The PDSS/IMC system provides the capability for performing Image Motion Compensator Electronics (IMCE) flight software test, checkout, and verification and provides the capability for monitoring the IMC flight computer system during qualification testing for fault detection and fault isolation.

  17. Experimental analysis of specification language impact on NPP software diversity

    Yoo, Chang Sik; Seong, Poong Hyun

    1998-01-01

    When redundancy and diversity is applied in NPP digital computer system, diversification of system software may be a critical point for the entire system dependability. As the means of enhancing software diversity, specification language diversity is suggested in this study. We set up a simple hypothesis for the specification language impact on common errors, and an experiment based on NPP protection system application was performed. Experiment result showed that this hypothesis could be justified and specification language diversity is effective in overcoming software common mode failure problem

  18. The Use of UML for Software Requirements Expression and Management

    Murray, Alex; Clark, Ken

    2015-01-01

    It is common practice to write English-language "shall" statements to embody detailed software requirements in aerospace software applications. This paper explores the use of the UML language as a replacement for the English language for this purpose. Among the advantages offered by the Unified Modeling Language (UML) is a high degree of clarity and precision in the expression of domain concepts as well as architecture and design. Can this quality of UML be exploited for the definition of software requirements? While expressing logical behavior, interface characteristics, timeliness constraints, and other constraints on software using UML is commonly done and relatively straight-forward, achieving the additional aspects of the expression and management of software requirements that stakeholders expect, especially traceability, is far less so. These other characteristics, concerned with auditing and quality control, include the ability to trace a requirement to a parent requirement (which may well be an English "shall" statement), to trace a requirement to verification activities or scenarios which verify that requirement, and to trace a requirement to elements of the software design which implement that requirement. UML Use Cases, designed for capturing requirements, have not always been satisfactory. Some applications of them simply use the Use Case model element as a repository for English requirement statements. Other applications of Use Cases, in which Use Cases are incorporated into behavioral diagrams that successfully communicate the behaviors and constraints required of the software, do indeed take advantage of UML's clarity, but not in ways that support the traceability features mentioned above. Our approach uses the Stereotype construct of UML to precisely identify elements of UML constructs, especially behaviors such as State Machines and Activities, as requirements, and also to achieve the necessary mapping capabilities. We describe this approach in the

  19. Automatic Visualization of Software Requirements: Reactive Systems

    Castello, R.; Mili, R.; Tollis, I.G.; Winter, V.

    1999-01-01

    In this paper we present an approach that facilitates the validation of high consequence system requirements. This approach consists of automatically generating a graphical representation from an informal document. Our choice of a graphical notation is statecharts. We proceed in two steps: we first extract a hierarchical decomposition tree from a textual description, then we draw a graph that models the statechart in a hierarchical fashion. The resulting drawing is an effective requirements assessment tool that allows the end user to easily pinpoint inconsistencies and incompleteness

  20. Green Software Engineering Adaption In Requirement Elicitation Process

    Umma Khatuna Jannat

    2015-08-01

    Full Text Available A recent technology investigates the role of concern in the environment software that is green software system. Now it is widely accepted that the green software can fit all process of software development. It is also suitable for the requirement elicitation process. Now a days software companies have used requirements elicitation techniques in an enormous majority. Because this process plays more and more important roles in software development. At the present time most of the requirements elicitation process is improved by using some techniques and tools. So that the intention of this research suggests to adapt green software engineering for the intention of existing elicitation technique and recommend suitable actions for improvement. This research being involved qualitative data. I used few keywords in my searching procedure then searched IEEE ACM Springer Elsevier Google scholar Scopus and Wiley. Find out articles which published in 2010 until 2016. Finding from the literature review Identify 15 traditional requirement elicitations factors and 23 improvement techniques to convert green engineering. Lastly The paper includes a squat review of the literature a description of the grounded theory and some of the identity issues related finding of the necessity for requirements elicitation improvement techniques.

  1. Quality assurance requirements for the computer software and safety analyses

    Husarecek, J.

    1992-01-01

    The requirements are given as placed on the development, procurement, maintenance, and application of software for the creation or processing of data during the design, construction, operation, repair, maintenance and safety-related upgrading of nuclear power plants. The verification and validation processes are highlighted, and the requirements put on the software documentation are outlined. The general quality assurance principles applied to safety analyses are characterized. (J.B.). 1 ref

  2. More about software requirements thorny issues and practical advice

    Wiegers, Karl E

    2006-01-01

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

  3. A report on NASA software engineering and Ada training requirements

    Legrand, Sue; Freedman, Glenn B.; Svabek, L.

    1987-01-01

    NASA's software engineering and Ada skill base are assessed and information that may result in new models for software engineering, Ada training plans, and curricula are provided. A quantitative assessment which reflects the requirements for software engineering and Ada training across NASA is provided. A recommended implementation plan including a suggested curriculum with associated duration per course and suggested means of delivery is also provided. The distinction between education and training is made. Although it was directed to focus on NASA's need for the latter, the key relationships to software engineering education are also identified. A rationale and strategy for implementing a life cycle education and training program are detailed in support of improved software engineering practices and the transition to Ada.

  4. Psychosocial Risks Generated By Assets Specific Design Software

    Remus, Furtună; Angela, Domnariu; Petru, Lazăr

    2015-07-01

    The human activity concerning an occupation is resultant from the interaction between the psycho-biological, socio-cultural and organizational-occupational factors. Tehnological development, automation and computerization that are to be found in all the branches of activity, the level of speed in which things develop, as well as reaching their complexity, require less and less physical aptitudes and more cognitive qualifications. The person included in the work process is bound in most of the cases to come in line with the organizational-occupational situations that are specific to the demands of the job. The role of the programmer is essencial in the process of execution of ordered softwares, thus the truly brilliant ideas can only come from well-rested minds, concentrated on their tasks. The actual requirements of the jobs, besides the high number of benefits and opportunities, also create a series of psycho-social risks, which can increase the level of stress during work activity, especially for those who work under pressure.

  5. A Method for Software Requirement Volatility Analysis Using QFD

    Yunarso Anang

    2016-10-01

    Full Text Available Changes of software requirements are inevitable during the development life cycle. Rather than avoiding the circumstance, it is easier to just accept it and find a way to anticipate those changes. This paper proposes a method to analyze the volatility of requirement by using the Quality Function Deployment (QFD method and the introduced degree of volatility. Customer requirements are deployed to software functions and subsequently to architectural design elements. And then, after determining the potential for changes of the design elements, the degree of volatility of the software requirements is calculated. In this paper the method is described using a flow diagram and illustrated using a simple example, and is evaluated using a case study.

  6. Software design specification and analysis(NuFDS) approach for the safety critical software based on porgrammable logic controller(PLC)

    Koo, Seo Ryong; Seong, Poong Hyun; Jung, Jin Yong; Choi, Seong Soo

    2004-01-01

    This paper introduces the software design specification and analysis technique for the safety-critical system based on Programmable Logic Controller (PLC). During software development phases, the design phase should perform an important role to connect between requirements phase and implementation phase as a process of translating problem requirements into software structures. In this work, the Nuclear FBD-style Design Specification and analysis (NuFDS) approach was proposed. The NuFDS approach for nuclear Instrumentation and Control (I and C) software are suggested in a straight forward manner. It consists of four major specifications as follows; Database, Software Architecture, System Behavior, and PLC Hardware Configuration. Additionally, correctness, completeness, consistency, and traceability check techniques are also suggested for the formal design analysis in NuFDS approach. In addition, for the tool supporting, we are developing NuSDS tool based on the NuFDS approach which is a tool, especially for the software design specification in nuclear fields

  7. A SYSTEMATIC LITERATURE REVIEW ABOUT SOFTWARE REQUIREMENTS ELICITATION

    LENIS R. WONG

    2017-02-01

    Full Text Available Requirements Elicitation is recognized as one of the most important activity in software development process as it has direct impact on its success. Although there are many proposals for improving this task, still there are issues which have to be solved. This paper aims to identify the current status of the latest researches related to software requirements elicitation through general framework for literature review, in order to answer the following research questions: Q1 What aspects have been covered by different proposal of requirements elicitation? Q2 What activities of the requirements elicitation process have been covered? And Q3 What factors influence on requirements elicitation and how? A cross-analysis of the outcome was performed. One of the results showed that requirements elicitation process needs improvements.

  8. Computer Software Configuration Item-Specific Flight Software Image Transfer Script Generator

    Bolen, Kenny; Greenlaw, Ronald

    2010-01-01

    A K-shell UNIX script enables the International Space Station (ISS) Flight Control Team (FCT) operators in NASA s Mission Control Center (MCC) in Houston to transfer an entire or partial computer software configuration item (CSCI) from a flight software compact disk (CD) to the onboard Portable Computer System (PCS). The tool is designed to read the content stored on a flight software CD and generate individual CSCI transfer scripts that are capable of transferring the flight software content in a given subdirectory on the CD to the scratch directory on the PCS. The flight control team can then transfer the flight software from the PCS scratch directory to the Electronically Erasable Programmable Read Only Memory (EEPROM) of an ISS Multiplexer/ Demultiplexer (MDM) via the Indirect File Transfer capability. The individual CSCI scripts and the CSCI Specific Flight Software Image Transfer Script Generator (CFITSG), when executed a second time, will remove all components from their original execution. The tool will identify errors in the transfer process and create logs of the transferred software for the purposes of configuration management.

  9. Development of a specific geological mapping software under MAPGIS

    Zhang Wenkai

    2010-01-01

    The most often used mapping software in geological exploration is MAPGIS system, and related standard is established based on it. The software has more agile functions, except for the following shortages: more parameters to select, difficult to master, different parameters to use for each one, low efficiency. As a result, a specific software is developed for geological mapping by using VC++ on the platform of MAPGIS. According to the standards, toolbars are built for strata, rock, geographic information and materials, etc. By pushing on the buttons, the parameters are selected, and menus of toolbars can be modified to select parameters for each working areas, legends can be sorted automatically. So, the speed can be improved greatly, and the parameters can be identical. The software can complete the transition between Gauss coordinate and longitude-latitude coordinate, drawing points, frames by longitude-latitude, responsible form, plain diagram and profile, etc. The software also improves the way of clipping, topologizing, node catching methods. The application of the software indicates that it can improve the speed of geological mapping greatly, and can improve the standardized level of the final maps. (authors)

  10. Application software, domain-specific languages, and language design assistants

    J. Heering (Jan)

    2000-01-01

    textabstractWhile application software does the real work, domain-specific languages (DSLs) are tools to help produce it efficiently, and language design assistants in turn are meta-tools to help produce DSLs quickly. DSLs are already in wide use (HTML for web pages, Excel macros for spreadsheet

  11. Metric-based method of software requirements correctness improvement

    Yaremchuk Svitlana

    2017-01-01

    Full Text Available The work highlights the most important principles of software reliability management (SRM. The SRM concept construes a basis for developing a method of requirements correctness improvement. The method assumes that complicated requirements contain more actual and potential design faults/defects. The method applies a newer metric to evaluate the requirements complexity and double sorting technique evaluating the priority and complexity of a particular requirement. The method enables to improve requirements correctness due to identification of a higher number of defects with restricted resources. Practical application of the proposed method in the course of demands review assured a sensible technical and economic effect.

  12. Software safety analysis on the model specified by NuSCR and SMV input language at requirements phase of software development life cycle using SMV

    Koh, Kwang Yong; Seong, Poong Hyun

    2005-01-01

    Safety-critical software process is composed of development process, verification and validation (V and V) process and safety analysis process. Safety analysis process has been often treated as an additional process and not found in a conventional software process. But software safety analysis (SSA) is required if software is applied to a safety system, and the SSA shall be performed independently for the safety software through software development life cycle (SDLC). Of all the phases in software development, requirements engineering is generally considered to play the most critical role in determining the overall software quality. NASA data demonstrate that nearly 75% of failures found in operational software were caused by errors in the requirements. The verification process in requirements phase checks the correctness of software requirements specification, and the safety analysis process analyzes the safety-related properties in detail. In this paper, the method for safety analysis at requirements phase of software development life cycle using symbolic model verifier (SMV) is proposed. Hazard is discovered by hazard analysis and in other to use SMV for the safety analysis, the safety-related properties are expressed by computation tree logic (CTL)

  13. Synthesizing Flight Software (FSW) Discrete Controllers from Formal Specifications

    National Aeronautics and Space Administration — This project will develop a Domain Specific Language (DSL) approach to interpret requirements and map them to formal specifications and legacy formats; explore and...

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

    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.

  15. Functional requirements for gas characterization system computer software

    Tate, D.D.

    1996-01-01

    This document provides the Functional Requirements for the Computer Software operating the Gas Characterization System (GCS), which monitors the combustible gasses in the vapor space of selected tanks. Necessary computer functions are defined to support design, testing, operation, and change control. The GCS requires several individual computers to address the control and data acquisition functions of instruments and sensors. These computers are networked for communication, and must multi-task to accommodate operation in parallel

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

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

    2005-01-01

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

  17. Application software, domain-specific languages, and language design assistants

    Heering, Jan

    2000-01-01

    textabstractWhile application software does the real work, domain-specific languages (DSLs) are tools to help produce it efficiently, and language design assistants in turn are meta-tools to help produce DSLs quickly. DSLs are already in wide use (HTML for web pages, Excel macros for spreadsheet applications, VHDL for hardware design, ...), but many more will be needed for both new as well as existing application domains. Language design assistants to help develop them currently exist only in...

  18. Generating Safety-Critical PLC Code From a High-Level Application Software Specification

    2008-01-01

    The benefits of automatic-application code generation are widely accepted within the software engineering community. These benefits include raised abstraction level of application programming, shorter product development time, lower maintenance costs, and increased code quality and consistency. Surprisingly, code generation concepts have not yet found wide acceptance and use in the field of programmable logic controller (PLC) software development. Software engineers at Kennedy Space Center recognized the need for PLC code generation while developing the new ground checkout and launch processing system, called the Launch Control System (LCS). Engineers developed a process and a prototype software tool that automatically translates a high-level representation or specification of application software into ladder logic that executes on a PLC. All the computer hardware in the LCS is planned to be commercial off the shelf (COTS), including industrial controllers or PLCs that are connected to the sensors and end items out in the field. Most of the software in LCS is also planned to be COTS, with only small adapter software modules that must be developed in order to interface between the various COTS software products. A domain-specific language (DSL) is a programming language designed to perform tasks and to solve problems in a particular domain, such as ground processing of launch vehicles. The LCS engineers created a DSL for developing test sequences of ground checkout and launch operations of future launch vehicle and spacecraft elements, and they are developing a tabular specification format that uses the DSL keywords and functions familiar to the ground and flight system users. The tabular specification format, or tabular spec, allows most ground and flight system users to document how the application software is intended to function and requires little or no software programming knowledge or experience. A small sample from a prototype tabular spec application is

  19. Predictive Software Measures based on Z Specifications - A Case Study

    Andreas Bollin

    2012-07-01

    Full Text Available Estimating the effort and quality of a system is a critical step at the beginning of every software project. It is necessary to have reliable ways of calculating these measures, and, it is even better when the calculation can be done as early as possible in the development life-cycle. Having this in mind, metrics for formal specifications are examined with a view to correlations to complexity and quality-based code measures. A case study, based on a Z specification and its implementation in ADA, analyzes the practicability of these metrics as predictors.

  20. A software architectural framework specification for neutron activation analysis

    Preston, J.A.; Grant, C.N.

    2013-01-01

    Neutron Activation Analysis (NAA) is a sensitive multi-element nuclear analytical technique that has been routinely applied by research reactor (RR) facilities to environmental, nutritional, health related, geological and geochemical studies. As RR facilities face calls to increase their research output and impact, with existing or reducing budgets, automation of NAA offers a possible solution. However, automation has many challenges, not the least of which is a lack of system architecture standards to establish acceptable mechanisms for the various hardware/software and software/software interactions among data acquisition systems, specialised hardware such as sample changers, sample loaders, and data processing modules. This lack of standardization often results in automation hardware and software being incompatible with existing system components, in a facility looking to automate its NAA operations. This limits the availability of automation to a few RR facilities with adequate budgets or in-house engineering resources. What is needed is a modern open system architecture for NAA, that provides the required set of functionalities. This paper describes such an 'architectural framework' (OpenNAA), and portions of a reference implementation. As an example of the benefits, calculations indicate that applying this architecture to the compilation and QA steps associated with the analysis of 35 elements in 140 samples, with 14 SRM's, can reduce the time required by over 80 %. The adoption of open standards in the nuclear industry has been very successful over the years in promoting interchangeability and maximising the lifetime and output of nuclear measurement systems. OpenNAA will provide similar benefits within the NAA application space, safeguarding user investments in their current system, while providing a solid path for development into the future. (author)

  1. Software use cases to elicit the software requirements analysis within the ASTRI project

    Conforti, Vito; Antolini, Elisa; Bonnoli, Giacomo; Bruno, Pietro; Bulgarelli, Andrea; Capalbi, Milvia; Fioretti, Valentina; Fugazza, Dino; Gardiol, Daniele; Grillo, Alessandro; Leto, Giuseppe; Lombardi, Saverio; Lucarelli, Fabrizio; Maccarone, Maria Concetta; Malaguti, Giuseppe; Pareschi, Giovanni; Russo, Federico; Sangiorgi, Pierluca; Schwarz, Joseph; Scuderi, Salvatore; Tanci, Claudio; Tosti, Gino; Trifoglio, Massimo; Vercellone, Stefano; Zanmar Sanchez, Ricardo

    2016-07-01

    The Italian National Institute for Astrophysics (INAF) is leading the Astrofisica con Specchi a Tecnologia Replicante Italiana (ASTRI) project whose main purpose is the realization of small size telescopes (SST) for the Cherenkov Telescope Array (CTA). The first goal of the ASTRI project has been the development and operation of an innovative end-to-end telescope prototype using a dual-mirror optical configuration (SST-2M) equipped with a camera based on silicon photo-multipliers and very fast read-out electronics. The ASTRI SST-2M prototype has been installed in Italy at the INAF "M.G. Fracastoro" Astronomical Station located at Serra La Nave, on Mount Etna, Sicily. This prototype will be used to test several mechanical, optical, control hardware and software solutions which will be used in the ASTRI mini-array, comprising nine telescopes proposed to be placed at the CTA southern site. The ASTRI mini-array is a collaborative and international effort led by INAF and carried out by Italy, Brazil and South-Africa. We present here the use cases, through UML (Unified Modeling Language) diagrams and text details, that describe the functional requirements of the software that will manage the ASTRI SST-2M prototype, and the lessons learned thanks to these activities. We intend to adopt the same approach for the Mini Array Software System that will manage the ASTRI miniarray operations. Use cases are of importance for the whole software life cycle; in particular they provide valuable support to the validation and verification activities. Following the iterative development approach, which breaks down the software development into smaller chunks, we have analysed the requirements, developed, and then tested the code in repeated cycles. The use case technique allowed us to formalize the problem through user stories that describe how the user procedurally interacts with the software system. Through the use cases we improved the communication among team members, fostered

  2. Independent Verification and Validation Of SAPHIRE 8 Software Requirements Project Number: N6423 U.S. Nuclear Regulatory Commission

    Kent Norris

    2009-09-01

    The purpose of the Independent Verification and Validation (IV&V) role in the evaluation of the SAPHIRE requirements definition is to assess the activities that results in the specification, documentation, and review of the requirements that the software product must satisfy, including functionality, performance, design constraints, attributes and external interfaces. The IV&V team began this endeavor after the software engineering and software development of SAPHIRE had already been in production. IV&V reviewed the requirements specified in the NRC Form 189s to verify these requirements were included in SAPHIRE’s Software Verification and Validation Plan (SVVP).

  3. IAEA/NDS requirements related to database software

    Pronyaev, V.; Zerkin, V.

    2001-01-01

    Full text: The Nuclear Data Section of the IAEA disseminates data to the NDS users through Internet or on CD-ROMs and diskettes. OSU Web-server on DEC Alpha with Open VMS and Oracle/DEC DBMS provides via CGI scripts and FORTRAN retrieval programs access to the main nuclear databases supported by the networks of Nuclear Reactions Data Centres and Nuclear Structure and Decay Data Centres (CINDA, EXFOR, ENDF, NSR, ENSDF). For Web-access to data from other libraries and files, hyper-links to the files stored in ASCII text or other formats are used. Databases on CD-ROM are usually provided with some retrieval system. They are distributed in the run-time mode and comply with all license requirements for software used in their development. Although major development work is done now at the PC with MS-Windows and Linux, NDS may not at present, due to some institutional conditions, use these platforms for organization of the Web access to the data. Starting the end of 1999, the NDS, in co-operation with other data centers, began to work out the strategy of migration of main network nuclear data bases onto platforms other than DEC Alpha/Open VMS/DBMS. Because the different co-operating centers have their own preferences for hardware and software, the requirement to provide maximum platform independence for nuclear databases is the most important and desirable feature. This requirement determined some standards for the nuclear database software development. Taking into account the present state and future development, these standards can be formulated as follows: 1. All numerical data (experimental, evaluated, recommended values and their uncertainties) prepared for inclusion in the IAEA/NDS nuclear database should be submitted in the form of the ASCII text files and will be kept at NDS as a master file. 2. Databases with complex structure should be submitted in the form of the files with standard SQL statements describing all its components. All extensions of standard SQL

  4. Development to requirements for a procedures software tool

    Yasutake, J.Y.; Hachiro Isoda

    1993-01-01

    In 1989, the Electric Power Research Institute (EPRI) and the Central Research Institute of the Electric Power Industry (CRIEPI) in Japan initiated a joint research program to investigate various interventions to reduce personnel errors and inefficiencies in the maintenance of nuclear power plants. This program, consisting of several interrelated projects, was initiated because of the mutual recognition of the importance of the human element in the efficient and safe operation of utilities and the continuing need to enhance personnel performance to sustain plant safety and availability. This paper summarizes one of the projects, jointly funded by EPRI and CRIEPI, to analyze the requirements for, and prepare a functional description of, a procedures software tool (PST). The primary objective of this project was to develop a description of the features and functions of a software tool that would help procedure writers to improve the quality of maintenance and testing procedures, thereby enhancing the performance of both procedure writers and maintenance personnel

  5. ROS signalling – Specificity is required

    Møller, Ian Max; Sweetlove, Lee J

    2011-01-01

    The production of reactive oxygen species (ROS) increases in plants under stress. ROS can damage cellular components, but they can also act in signal transduction to help the cell counteract the oxidative damage in the stressed compartment. H2O2 may induce a general stress response, but it does...... messengers and regulate source-specific genes and in this way contribute to retrograde ROS signalling during oxidative stress. (This is a new project funded by FNU) References: Møller, I.M. & Sweetlove, L.J. 2010. ROS signalling – Specificity is required. Trends Plant Sci. 15: 370-374...... not have the required specificity to selectively regulate nuclear genes required for dealing with localized stress, e.g., in chloroplasts or mitochondria. We here argue that peptides deriving from proteolytic breakdown of oxidatively damaged proteins have the requisite specificity to act as secondary ROS...

  6. Improvements to Technical Specifications surveillance requirements

    Lobel, R.; Tjader, T.R.

    1992-12-01

    In August 1983 an NRC task group was formed to investigate problems with surveillance testing required by Technical Specifications, and to recommend approaches to effect improvements. NUREG-1024 (''Technical Specifications-Enhancing Safety Impact'') resulted, and it contained recommendations to review the basis for test frequencies; to ensure that the tests promote safety and do not degrade equipment; and to review surveillance tests so that they do not unnecessarily burden personnel. The Technical Specifications Improvement Program (TSIP) was established in December 1984 to provide the framework for rewriting and improving the Technical Specifications. As an element of the TSIP, all Technical Specifications surveillance requirements were comprehensively examined as recommended in NUREG-1024. The results of that effort are presented in this report. The study found that while some testing at power is essential to verify equipment and system operability, safety can be improved, equipment degradation decreased, and unnecessary personnel burden relaxed by reducing the amount of testing at power

  7. Radiological equipment analyzed by specific developed phantoms and software

    Soto, M.; Campayo, J. M.; Mayo, P.; Verdu, G.; Rodenas, F.

    2010-10-01

    The use of radiographic phantoms specifically designed to evaluate the operation of the radiographic equipment lets the study of the image quality obtained by this equipment in an objective way. In digital radiographic equipment, the analysis of the image quality can be computerized because the acquisition of the image is possible in different technologies that are, computerized radiography or phosphor plate and direct radiography or detector. In case of film-screen equipment s this analysis could be applied digitalising the image in a professional scanner. In this work we have shown an application to assess automatically the constancy quality image in the image chain of the radiographic equipment s. This application is integrated by designed radiographic phantoms which are adapted to conventional, dental equipment s and specific developed software for the automatic evaluation of the phantom image quality. The software is based on digital image processing techniques that let the automatic detection of the different phantom tests by edge detector, morphological operators, threshold histogram techniques... etc. The utility developed is enough sensitive to the radiographic equipment of operating conditions of voltage (kV) and charge (m As). It is a friendly user programme connected with a data base of the hospital or clinic where it has been used. After the phantom image processing the user can obtain an inform with a resume of the imaging system state with accepting and constancy results. (Author)

  8. Radiological equipment analyzed by specific developed phantoms and software

    Soto, M.; Campayo, J. M. [Logistica y Acondicionamientos Industriales SAU, Sorolla Center, Local 10, Av. de las Cortes Valencianas No. 58, 46015 Valencia (Spain); Mayo, P. [TITANIA Servicios Tecnologicos SL, Sorolla Center, Local 10, Av. de las Cortes Valencianas No. 58, 46015 Valencia (Spain); Verdu, G.; Rodenas, F., E-mail: m.soto@lainsa.co [ISIRYIM Universidad Politecnica de Valencia, Camino de Vera s/n, Valencia (Spain)

    2010-10-15

    The use of radiographic phantoms specifically designed to evaluate the operation of the radiographic equipment lets the study of the image quality obtained by this equipment in an objective way. In digital radiographic equipment, the analysis of the image quality can be computerized because the acquisition of the image is possible in different technologies that are, computerized radiography or phosphor plate and direct radiography or detector. In case of film-screen equipment s this analysis could be applied digitalising the image in a professional scanner. In this work we have shown an application to assess automatically the constancy quality image in the image chain of the radiographic equipment s. This application is integrated by designed radiographic phantoms which are adapted to conventional, dental equipment s and specific developed software for the automatic evaluation of the phantom image quality. The software is based on digital image processing techniques that let the automatic detection of the different phantom tests by edge detector, morphological operators, threshold histogram techniques... etc. The utility developed is enough sensitive to the radiographic equipment of operating conditions of voltage (kV) and charge (m As). It is a friendly user programme connected with a data base of the hospital or clinic where it has been used. After the phantom image processing the user can obtain an inform with a resume of the imaging system state with accepting and constancy results. (Author)

  9. Formalization of software requirements for information systems using fuzzy logic

    Yegorov, Y. S.; Milov, V. R.; Kvasov, A. S.; Sorokoumova, S. N.; Suvorova, O. V.

    2018-05-01

    The paper considers an approach to the design of information systems based on flexible software development methodologies. The possibility of improving the management of the life cycle of information systems by assessing the functional relationship between requirements and business objectives is described. An approach is proposed to establish the relationship between the degree of achievement of business objectives and the fulfillment of requirements for the projected information system. It describes solutions that allow one to formalize the process of formation of functional and non-functional requirements with the help of fuzzy logic apparatus. The form of the objective function is formed on the basis of expert knowledge and is specified via learning from very small data set.

  10. NuSEE: an integrated environment of software specification and V and V for PLC based safety-critical systems

    Koo, Seo Ryong; Seong, Poong Hyun; Yoo, Jun Beom; Cha, Sung Deok; Youn, Cheong; Han, Hyun Chul

    2006-01-01

    As the use of digital systems becomes more prevalent, adequate techniques for software specification and analysis have become increasingly important in Nuclear Power Plant (NPP) safety-critical systems. Additionally, the importance of software Verification and Validation (V and V) based on adequate specification has received greater emphasis in view of improving software quality. For thorough V and V of safety-critical systems, V and V should be performed throughout the software lifecycle. However, systematic V and V is difficult as it involves many manual-oriented tasks. Tool support is needed in order to more conveniently perform software V and V. In response, we developed four kinds of Computer Aided Software Engineering (CASE) tools to support system specification for a formal-based analysis according to the software lifecycle. In this work, we achieved optimized integration of each tool. The toolset, NuSEE, is an integrated environment for software specification and V and V for PLC based safety-critical systems. In accordance with the software lifecycle, NuSEE consists of NuSISRT for the concept phase, NuSRS for the requirements phase, NuSDS for the design phase and NuSCM for configuration management. It is believed that after further development our integrated environment will be a unique and promising software specification and analysis toolset that will support the entire software lifecycle for the development of PLC based NPP safety-critical systems

  11. Software

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

    2010-07-15

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

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

    Alsahli, Abdulaziz; Khan, Hameed; Alyahya, Sultan

    2016-01-01

    Requirement change management (RCM) is a critical activity during software development because poor RCM results in occurrence of defects, thereby resulting in software failure. To achieve RCM, efficient impact analysis is mandatory. A common repository is a good approach to maintain changed requirements, reusing and reducing effort. Thus, a better approach is needed to tailor knowledge for better change management of requirements and architecture during global software development (GSD).The o...

  13. Software requirements definition Shipping Cask Analysis System (SCANS)

    Johnson, G.L.; Serbin, R.

    1985-01-01

    The US Nuclear Regulatory Commission (NRC) staff reviews the technical adequacy of applications for certification of designs of shipping casks for spent nuclear fuel. In order to confirm an acceptable design, the NRC staff may perform independent calculations. The current NRC procedure for confirming cask design analyses is laborious and tedious. Most of the work is currently done by hand or through the use of a remote computer network. The time required to certify a cask can be long. The review process may vary somewhat with the engineer doing the reviewing. Similarly, the documentation on the results of the review can also vary with the reviewer. To increase the efficiency of this certification process, LLNL was requested to design and write an integrated set of user-oriented, interactive computer programs for a personal microcomputer. The system is known as the NRC Shipping Cask Analysis System (SCANS). The computer codes and the software system supporting these codes are being developed and maintained for the NRC by LLNL. The objective of this system is generally to lessen the time and effort needed to review an application. Additionally, an objective of the system is to assure standardized methods and documentation of the confirmatory analyses used in the review of these cask designs. A software system should be designed based on NRC-defined requirements contained in a requirements document. The requirements document is a statement of a project's wants and needs as the users and implementers jointly understand them. The requirements document states the desired end products (i.e. WHAT's) of the project, not HOW the project provides them. This document describes the wants and needs for the SCANS system. 1 fig., 3 tabs

  14. Space shuttle orbiter guidance, naviagation and control software functional requirements: Horizontal flight operations

    1972-01-01

    The shuttle GN&C software functions for horizontal flight operations are defined. Software functional requirements are grouped into two categories: first horizontal flight requirements and full mission horizontal flight requirements. The document privides the intial step in the shuttle GN&C software design process. It also serves as a management tool to identify analyses which are required to define requirements.

  15. Quantifying Functional Reuse from Object Oriented Requirements Specifications

    Condori-Fernandez, Nelly; Condori-Fernández, N.; Pastor, O; Daneva, Maia; Abran, A.; Castro, J.; Quer, C.; Carvallo, J. B.; Fernandes da Silva, L.

    2008-01-01

    Software reuse is essential in improving efficiency and productivity in the software development process. This paper analyses reuse within requirements engineering phase by taking and adapting a standard functional size measurement method, COSMIC FFP. Our proposal attempts to quantify reusability

  16. Software Safety Analysis of Digital Protection System Requirements Using a Qualitative Formal Method

    Lee, Jang-Soo; Kwon, Kee-Choon; Cha, Sung-Deok

    2004-01-01

    The safety analysis of requirements is a key problem area in the development of software for the digital protection systems of a nuclear power plant. When specifying requirements for software of the digital protection systems and conducting safety analysis, engineers find that requirements are often known only in qualitative terms and that existing fault-tree analysis techniques provide little guidance on formulating and evaluating potential failure modes. A framework for the requirements engineering process is proposed that consists of a qualitative method for requirements specification, called the qualitative formal method (QFM), and a safety analysis method for the requirements based on causality information, called the causal requirements safety analysis (CRSA). CRSA is a technique that qualitatively evaluates causal relationships between software faults and physical hazards. This technique, extending the qualitative formal method process and utilizing information captured in the state trajectory, provides specific guidelines on how to identify failure modes and the relationship among them. The QFM and CRSA processes are described using shutdown system 2 of the Wolsong nuclear power plants as the digital protection system example

  17. Reusable Software Usability Specifications for mHealth Applications.

    Cruz Zapata, Belén; Fernández-Alemán, José Luis; Toval, Ambrosio; Idri, Ali

    2018-01-25

    One of the key factors for the adoption of mobile technologies, and in particular of mobile health applications, is usability. A usable application will be easier to use and understand by users, and will improve user's interaction with it. This paper proposes a software requirements catalog for usable mobile health applications, which can be used for the development of new applications, or the evaluation of existing ones. The catalog is based on the main identified sources in literature on usability and mobile health applications. Our catalog was organized according to the ISO/IEC/IEEE 29148:2011 standard and follows the SIREN methodology to create reusable catalogs. The applicability of the catalog was verified by the creation of an audit method, which was used to perform the evaluation of a real app, S Health, application created by Samsung Electronics Co. The usability requirements catalog, along with the audit method, identified several usability flaws on the evaluated app, which scored 83%. Some flaws were detected in the app related to the navigation pattern. Some more issues related to the startup experience, empty screens or writing style were also found. The way a user navigates through an application improves or deteriorates user's experience with the application. We proposed a reusable usability catalog and an audit method. This proposal was used to evaluate a mobile health application. An audit report was created with the usability issues identified on the evaluated application.

  18. Knowledge Base for an Intelligent System in order to Identify Security Requirements for Government Agencies Software Projects

    Adán Beltrán G.

    2016-01-01

    Full Text Available It has been evidenced that one of the most common causes in the failure of software security is the lack of identification and specification of requirements for information security, it is an activity with an insufficient importance in the software development or software acquisition We propose the knowledge base of CIBERREQ. CIBERREQ is an intelligent knowledge-based system used for the identification and specification of security requirements in the software development cycle or in the software acquisition. CIBERREQ receives functional software requirements written in natural language and produces non-functional security requirements through a semi-automatic process of risk management. The knowledge base built is formed by an ontology developed collaboratively by experts in information security. In this process has been identified six types of assets: electronic data, physical data, hardware, software, person and service; as well as six types of risk: competitive disadvantage, loss of credibility, economic risks, strategic risks, operational risks and legal sanctions. In addition there are defined 95 vulnerabilities, 24 threats, 230 controls, and 515 associations between concepts. Additionally, automatic expansion was used with Wikipedia for the asset types Software and Hardware, obtaining 7125 and 5894 software and hardware subtypes respectively, achieving thereby an improvement of 10% in the identification of the information assets candidates, one of the most important phases of the proposed system.

  19. The Role of Requirements in the Success or Failure of Software Projects

    Hussain, Azham; Mkpojiogu, Emmanuel O.C.; Kamal, Fazillah Mohmad

    2016-01-01

    Requirements engineering is pivotal and central to every successful software development project. There are several reasons why software projects fail; however, poorly elicited, documented, validated and managed requirements contribute grossly to software projects failure. Software project failures are normally very costly and risky and these could even a times be life threatening also. Projects that overlook requirements engineering processes often suffer or are most likely to suffer from fa...

  20. Development of requirements tracking and verification technology for the NPP software

    Jung, Chul Hwan; Kim, Jang Yeol; Lee, Jang Soo; Song, Soon Ja; Lee, Dong Young; Kwon, Kee Choon

    1998-12-30

    Searched and analyzed the technology of requirements engineering in the areas of aerospace and defense industry, medical industry and nuclear industry. Summarized the status of tools for the software design and requirements management. Analyzed the software design methodology for the safety software of NPP. Development of the design requirements for the requirements tracking and verification system. Development of the background technology to design the prototype tool for the requirements tracking and verification.

  1. Development of requirements tracking and verification technology for the NPP software

    Jung, Chul Hwan; Kim, Jang Yeol; Lee, Jang Soo; Song, Soon Ja; Lee, Dong Young; Kwon, Kee Choon

    1998-01-01

    Searched and analyzed the technology of requirements engineering in the areas of aerospace and defense industry, medical industry and nuclear industry. Summarized the status of tools for the software design and requirements management. Analyzed the software design methodology for the safety software of NPP. Development of the design requirements for the requirements tracking and verification system. Development of the background technology to design the prototype tool for the requirements tracking and verification

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

    1976-01-01

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

  3. Technical Specification action statements requiring shutdown

    Mankamo, T.; Kim, I.S.; Samanta, P.K.

    1993-11-01

    When safety systems fail during power operation, the limiting conditions for operation (LCOs) and associated action statements of technical specifications typically require that the plant be shut down within the limits of allowed outage time (AOT). However, when a system needed to remove decay heat, such as the residual heat removal (RHR) system, is inoperable or degraded, shutting down the plant may not necessarily be preferable, from a risk perspective, to continuing power operation over a usual repair time, giving priority to the repairs. The risk impact of the basic operational alternatives, i.e., continued operation or shutdown, was evaluated for failures in the RHR and standby service water (SSW) systems of a boiling-water reactor (BWR) nuclear power plant. A complete or partial failure of the SSW system fails or degrades not only the RHR system but other front-line safety systems supported by the SSW system. This report presents the methodology to evaluate the risk impact of LCOs and associated AOT; the results of risk evaluation from its application to the RHR and SSW systems of a BWR; the findings from the risk-sensitivity analyses to identify alternative operational policies; and the major insights and recommendations to improve the technical specifications action statements

  4. Characterizing the contribution of quality requirements to software sustainability

    Condori-Fernandez, Nelly; Lago, Patricia

    2018-01-01

    Most respondents considered modifiability as relevant for addressing both technical and environmental sustainability. Functional correctness, availability, modifiability, interoperability and recoverability favor positively the endurability of software systems. This study has also identified

  5. Diversity requirements for safety critical software-based automation systems

    Korhonen, J.; Pulkkinen, U.; Haapanen, P.

    1998-03-01

    System vendors nowadays propose software-based systems even for the most critical safety functions in nuclear power plants. Due to the nature and mechanisms of influence of software faults new methods are needed for the safety and reliability evaluation of these systems. In the research project 'Programmable automation systems in nuclear power plants (OHA)' various safety assessment methods and tools for software based systems are developed and evaluated. This report first discusses the (common cause) failure mechanisms in software-based systems, then defines fault-tolerant system architectures to avoid common cause failures, then studies the various alternatives to apply diversity and their influence on system reliability. Finally, a method for the assessment of diversity is described. Other recently published reports in OHA-report series handles the statistical reliability assessment of software based (STUK-YTO-TR 119), usage models in reliability assessment of software-based systems (STUK-YTO-TR 128) and handling of programmable automation in plant PSA-studies (STUK-YTO-TR 129)

  6. Requirements and specifications for a particle database

    2015-01-01

    simple as possible, the database will include unique names (or 'id's) for every particle that it stores. Reaction databases can then refer to a specific particle either by id. Where possible, particle ids should be made descriptive to assist human readers in understanding the contents of reaction and particle databases. The particle database is being primarily developed to store nuclei and nuclear states, but it must also be capable of storing some atomic and molecular properties. In particular the database must support atomic electron configurations since they can play an important role in nuclear reactions and decays. Excited nuclear states sometimes decay via internal conversion, 'kicking out' an electron from an inner shell and leaving the remaining electrons to de-excite (emitting x-rays) to fill the new vacancy. Excited atomic states can also be populated through photo-atomic reactions Adding electronic configurations to the database has the potential to drastically increase its size: if unique ids must be given not only to each nucleus and excited nuclear level but also to every possible electron configuration for each nucleus and level, the database will quickly grow to an unmaintainable size. In order to get around this problem and support atomic and molecular properties without drastically increasing the number of particles, the database will allow the use of 'qualifiers' that can be added to a particle to modify its properties. This document describes the requirements and specifications for a particle data hierarchy, including documentation, bibliography information, particle qualifiers as well as particle families and particle groups. This document uses the XML meta-language to illustrate examples of how particle data will be stored. However, like other tasks under SG38, it should be possible to store the particle database in other meta-languages (that is, languages that define a general syntax that can be used to define more specific languages) that support

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

    Abdulaziz Alsahli

    2016-01-01

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

  8. Delivering Software Process-Specific Project Courses in Tertiary Education Environment: Challenges and Solution

    Rong, Guoping; Shao, Dong

    2012-01-01

    The importance of delivering software process courses to software engineering students has been more and more recognized in China in recent years. However, students usually cannot fully appreciate the value of software process courses by only learning methodology and principle in the classroom. Therefore, a process-specific project course was…

  9. Fault-specific verification (FSV) - An alternative VV ampersand T strategy for high reliability nuclear software systems

    Miller, L.A.

    1994-01-01

    The author puts forth an argument that digital instrumentation and control systems can be safely applied in the nuclear industry, but it will require changes to the way software for such systems is developed and tested. He argues for a fault-specific verification procedure to be applied to software development. This plan includes enumerating and classifying all software faults at all levels of the product development, over the whole development process. While collecting this data, develop and validate different methods for software verification, validation and testing, and apply them against all the detected faults. Force all of this development toward an automated product for doing this testing. Continue to develop, expand, test, and share these testing methods across a wide array of software products

  10. Disposal of Radioactive Waste. Specific Safety Requirements

    2011-01-01

    This publication establishes requirements applicable to all types of radioactive waste disposal facility. It is linked to the fundamental safety principles for each disposal option and establishes a set of strategic requirements that must be in place before facilities are developed. Consideration is also given to the safety of existing facilities developed prior to the establishment of present day standards. The requirements will be complemented by Safety Guides that will provide guidance on good practice for meeting the requirements for different types of waste disposal facility. Contents: 1. Introduction; 2. Protection of people and the environment; 3. Safety requirements for planning for the disposal of radioactive waste; 4. Requirements for the development, operation and closure of a disposal facility; 5. Assurance of safety; 6. Existing disposal facilities; Appendices.

  11. Synergy of Technical Specification, functional specifications and scenarios in requirements specifications

    Miedema, J.; van der Voort, Mascha C.; Lutters, Diederick; van Houten, Frederikus J.A.M.; Krause, Frank-Lothar

    2007-01-01

    In the (mechanical) design process, the requirements specification is a formal registration of the conditions that are imposed on a new or altered product design, both preceding as well as during the corresponding product development cycle. For a long time, the use of technical specifications has

  12. Interplay between requirements, software architecture, and hardware constraints in the development of a home control user interface

    Loft, M.S.; Nielsen, S.S.; Nørskov, Kim

    2012-01-01

    is to propose the hardware platform as a third Twin Peaks element that must be given attention in projects such as the one described in this paper. Specifically, we discuss how the presence of severe hardware constraints exacerbates making trade-offs between requirements and architecture.......We have developed a new graphical user interface for a home control device for a large industrial customer. In this industrial case study, we first present our approaches to requirements engineering and to software architecture; we also describe the given hardware platform. Then we make two...... contributions. Our first contribution is to provide a specific example of a real-world project in which a Twin Peaks-compliant approach to software development has been used, and to describe and discuss three examples of interplay between requirements and software architecture decisions. Our second contribution...

  13. Security Requirements Management in Software Product Line Engineering

    Mellado, Daniel; Fernández-Medina, Eduardo; Piattini, Mario

    Security requirements engineering is both a central task and a critical success factor in product line development due to the complexity and extensive nature of product lines. However, most of the current product line practices in requirements engineering do not adequately address security requirements engineering. Therefore, in this chapter we will propose a security requirements engineering process (SREPPLine) driven by security standards and based on a security requirements decision model along with a security variability model to manage the variability of the artefacts related to security requirements. The aim of this approach is to deal with security requirements from the early stages of the product line development in a systematic way, in order to facilitate conformance with the most relevant security standards with regard to the management of security requirements, such as ISO/IEC 27001 and ISO/IEC 15408.

  14. Application of a path sensitizing method on automated generation of test specifications for control software

    Morimoto, Yuuichi; Fukuda, Mitsuko

    1995-01-01

    An automated generation method for test specifications has been developed for sequential control software in plant control equipment. Sequential control software can be represented as sequential circuits. The control software implemented in a control equipment is designed from these circuit diagrams. In logic tests of VLSI's, path sensitizing methods are widely used to generate test specifications. But the method generates test specifications at a single time only, and can not be directly applied to sequential control software. The basic idea of the proposed method is as follows. Specifications of each logic operator in the diagrams are defined in the software design process. Therefore, test specifications of each operator in the control software can be determined from these specifications, and validity of software can be judged by inspecting all of the operators in the logic circuit diagrams. Candidates for sensitized paths, on which test data for each operator propagates, can be generated by the path sensitizing method. To confirm feasibility of the method, it was experimentally applied to control software in digital control equipment. The program could generate test specifications exactly, and feasibility of the method was confirmed. (orig.) (3 refs., 7 figs.)

  15. State of the Art : Integrated Management of Requirements in Model-Based Software Engineering

    Thörn, Christer

    2006-01-01

    This report describes the background and future of research concerning integrated management of requirements in model-based software engineering. The focus is on describing the relevant topics and existing theoretical backgrounds that form the basis for the research. The report describes the fundamental difficulties of requirements engineering for software projects, and proposes that the results and methods of models in software engineering can help leverage those problems. Taking inspiration...

  16. Assessing students' performance in software requirements engineering education using scoring rubrics

    Mkpojiogu, Emmanuel O. C.; Hussain, Azham

    2017-10-01

    The study investigates how helpful the use of scoring rubrics is, in the performance assessment of software requirements engineering students and whether its use can lead to students' performance improvement in the development of software requirements artifacts and models. Scoring rubrics were used by two instructors to assess the cognitive performance of a student in the design and development of software requirements artifacts. The study results indicate that the use of scoring rubrics is very helpful in objectively assessing the performance of software requirements or software engineering students. Furthermore, the results revealed that the use of scoring rubrics can also produce a good achievement assessments direction showing whether a student is either improving or not in a repeated or iterative assessment. In a nutshell, its use leads to the performance improvement of students. The results provided some insights for further investigation and will be beneficial to researchers, requirements engineers, system designers, developers and project managers.

  17. Simulation Data Management - Requirements and Design Specification

    Clay, Robert L. [Sandia National Lab. (SNL-NM), Albuquerque, NM (United States); Friedman-Hill, Ernest J. [Sandia National Lab. (SNL-NM), Albuquerque, NM (United States); Gibson, Marcus J. [Sandia National Lab. (SNL-NM), Albuquerque, NM (United States); Hoffman, Edward L. [Sandia National Lab. (SNL-NM), Albuquerque, NM (United States); Olson, Kevin H. [Science Applications International Corporation (SAIC), Reston, VA (United States); Laney, Daniel [Lawrence Livermore National Lab. (LLNL), Livermore, CA (United States)

    2017-11-01

    Simulation Data Management (SDM), the ability to securely organize, archive, and share analysis models and the artifacts used to create them, is a fundamental requirement for modern engineering analysis based on computational simulation. We have worked separately to provide secure, network SDM services to engineers and scientists at our respective laboratories for over a decade. We propose to leverage our experience and lessons learned to help develop and deploy a next-generation SDM service as part of a multi-laboratory team. This service will be portable across multiple sites and platforms, and will be accessible via a range of command-line tools and well-documented APIs. In this document, we’ll review our high-level and low-level requirements for such a system, review one existing system, and briefly discuss our proposed implementation.

  18. LHCb electronics - requirements, specifications and implementation

    Bibby, J

    2001-01-01

    This document is intended to serve as a requirements document, a design manual and an implementation reference for the RICH electronics systems. At the current time, the electronics design is under active consideration and this is reflected in this document which represents a working proposal as regards both the functional model and physical implementation. Comments on installation, commissioning, and maintenance are included. For convenience a description of the proposed RICH data formats is appended.

  19. Smart grid standards specifications, requirements, and technologies

    Sato, Takuro; Duan, Bin; Macuha, Martin; Zhou, Zhenyu; Wu, Jun; Tariq, Muhammad; Asfaw, Solomon A

    2015-01-01

    With numerous existing Smart Grid standards, it is clear that governments and industrial organizations world-wide have understood and acknowledged the critical role they play. This timely book is a useful guide for Smart Grid professionals in easily classifying fundamental Smart Grid standards, and to quickly find the building blocks they need to analyse and implement a Smart Grid system. The standards are organized in a systematic manner that aids identification, according to grid requirements. It also covers broader Smart Grid areas including, but not limited to, the following: A fully c

  20. Development of requirements tracking and verification system for the software design of distributed control system

    Jung, Chul Hwan; Kim, Jang Yeol; Kim, Jung Tack; Lee, Jang Soo; Ham, Chang Shik [Korea Atomic Energy Research Institute, Taejon (Korea, Republic of)

    1999-12-31

    In this paper a prototype of Requirement Tracking and Verification System(RTVS) for a Distributed Control System was implemented and tested. The RTVS is a software design and verification tool. The main functions required by the RTVS are managing, tracking and verification of the software requirements listed in the documentation of the DCS. The analysis of DCS software design procedures and interfaces with documents were performed to define the user of the RTVS, and the design requirements for RTVS were developed. 4 refs., 3 figs. (Author)

  1. Development of requirements tracking and verification system for the software design of distributed control system

    Jung, Chul Hwan; Kim, Jang Yeol; Kim, Jung Tack; Lee, Jang Soo; Ham, Chang Shik [Korea Atomic Energy Research Institute, Taejon (Korea, Republic of)

    1998-12-31

    In this paper a prototype of Requirement Tracking and Verification System(RTVS) for a Distributed Control System was implemented and tested. The RTVS is a software design and verification tool. The main functions required by the RTVS are managing, tracking and verification of the software requirements listed in the documentation of the DCS. The analysis of DCS software design procedures and interfaces with documents were performed to define the user of the RTVS, and the design requirements for RTVS were developed. 4 refs., 3 figs. (Author)

  2. SecureCore Software Architecture: Trusted Path Application (TPA) Requirements

    Clark, Paul C; Irvine, Cynthia E; Levin, Timothy E; Nguyen, Thuy D; Vidas, Timothy M

    2007-01-01

    .... The purpose of the SecureCore research project is to investigate fundamental architectural features required for the trusted operation of mobile computing devices so the security is built-in, transparent and flexible...

  3. FLECH PowerMax Service Requirement Specification

    It is expected that in the future, ancillary services will be required at distribution level. This work describes how one of these ancillary services, the PowerMax service, must be spec ified within a market framework. The basis of this work is the Flexibility Clearing House (FLE CH) platform...... and the Distribution System Operator (DSO) services defined in [1]. The PowerMax service has been further discussed in [2], and this technical report seeks to clarify the implementation details first discussed in that paper. The aim of the PowerMax service it to relieve congestion issue s in the distribution system...... by establishing a maximum power that a cluster of consumer devices may draw from the syste m. The consumers will receive a payment for providing this service, and the DSO will be able to postpone grid reinfo rcement...

  4. Software development minimum guidance system. Algorithm and specifications of realizing special hardware processor data prefilter program

    Baginyan, S.A.; Govorun, N.N.; Tkhang, T.L.; Shigaev, V.N.

    1982-01-01

    Software development minimum guidance system for measuring pictures of bubble chamber on the base of a scanner (HPD) and special hardware processor (SHP) is described. The algorithm of selective filter is proposed. The local software structure and functional specifications of its major parts are described. Some examples of processing picture from HBC-1 (JINR) are also presented

  5. Application of software quality assurance to a specific scientific code development task

    Dronkers, J.J.

    1986-03-01

    This paper describes an application of software quality assurance to a specific scientific code development program. The software quality assurance program consists of three major components: administrative control, configuration management, and user documentation. The program attempts to be consistent with existing local traditions of scientific code development while at the same time providing a controlled process of development

  6. Software Prototyping: A Case Report of Refining User Requirements for a Health Information Exchange Dashboard.

    Nelson, Scott D; Del Fiol, Guilherme; Hanseler, Haley; Crouch, Barbara Insley; Cummins, Mollie R

    2016-01-01

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

  7. SecureCore Software Architecture: Trusted Path Application (TPA) Requirements

    Clark, Paul C; Irvine, Cynthia E; Levin, Timothy E; Nguyen, Thuy D; Vidas, Timothy M

    2007-01-01

    .... A high-level architecture is described to provide such features. In addition, a usage scenario is described for a potential use of the architecture, with emphasis on the trusted path, a non-spoofable user interface to the trusted components of the system. Detailed requirements for the trusted path are provided.

  8. Relating Business Goals to Architecturally Significant Requirements for Software Systems

    2010-05-01

    must respond within five seconds” [ EPF 2010]. A major source of architecturally significant requirements is the set of business goals that led to the...Projects for Competitive Advantage, Center for Business Practices, 1999. [ EPF 2010] Eclipse Process Framework Project. Concept: Architecturally

  9. Questioning the Role of Requirements Engineering in the Causes of Safety-Critical Software Failures

    Johnson, C. W.; Holloway, C. M.

    2006-01-01

    Many software failures stem from inadequate requirements engineering. This view has been supported both by detailed accident investigations and by a number of empirical studies; however, such investigations can be misleading. It is often difficult to distinguish between failures in requirements engineering and problems elsewhere in the software development lifecycle. Further pitfalls arise from the assumption that inadequate requirements engineering is a cause of all software related accidents for which the system fails to meet its requirements. This paper identifies some of the problems that have arisen from an undue focus on the role of requirements engineering in the causes of major accidents. The intention is to provoke further debate within the emerging field of forensic software engineering.

  10. Software/firmware design specification for 10-MWe solar-thermal central-receiver pilot plant

    Ladewig, T.D.

    1981-03-01

    The software and firmware employed for the operation of the Barstow Solar Pilot Plant are completely described. The systems allow operator control of up to 2048 heliostats, and include the capability of operator-commanded control, graphic displays, status displays, alarm generation, system redundancy, and interfaces to the Operational Control System, the Data Acquisition System, and the Beam Characterization System. The requirements are decomposed into eleven software modules for execution in the Heliostat Array Controller computer, one firmware module for execution in the Heliostat Field Controller microprocessor, and one firmware module for execution in the Heliostat Controller microprocessor. The design of the modules to satisfy requirements, the interfaces between the computers, the software system structure, and the computers in which the software and firmware will execute are detailed. The testing sequence for validation of the software/firmware is described. (LEW)

  11. Towards an Early Software Effort Estimation Based on Functional and Non-Functional Requirements

    Kassab, M.; Daneva, Maia; Ormanjieva, Olga; Abran, A.; Braungarten, R.; Dumke, R.; Cuadrado-Gallego, J.; Brunekreef, J.

    2009-01-01

    The increased awareness of the non-functional requirements as a key to software project and product success makes explicit the need to include them in any software project effort estimation activity. However, the existing approaches to defining size-based effort relationships still pay insufficient

  12. Core Community Specifications for Electron Microprobe Operating Systems: Software, Quality Control, and Data Management Issues

    Fournelle, John; Carpenter, Paul

    2006-01-01

    Modem electron microprobe systems have become increasingly sophisticated. These systems utilize either UNIX or PC computer systems for measurement, automation, and data reduction. These systems have undergone major improvements in processing, storage, display, and communications, due to increased capabilities of hardware and software. Instrument specifications are typically utilized at the time of purchase and concentrate on hardware performance. The microanalysis community includes analysts, researchers, software developers, and manufacturers, who could benefit from exchange of ideas and the ultimate development of core community specifications (CCS) for hardware and software components of microprobe instrumentation and operating systems.

  13. Basic Requirements for Systems Software Research and Development

    Kuszmaul, Chris; Nitzberg, Bill

    1996-01-01

    Our success over the past ten years evaluating and developing advanced computing technologies has been due to a simple research and development (R/D) model. Our model has three phases: (a) evaluating the state-of-the-art, (b) identifying problems and creating innovations, and (c) developing solutions, improving the state- of-the-art. This cycle has four basic requirements: a large production testbed with real users, a diverse collection of state-of-the-art hardware, facilities for evalua- tion of emerging technologies and development of innovations, and control over system management on these testbeds. Future research will be irrelevant and future products will not work if any of these requirements is eliminated. In order to retain our effectiveness, the numerical aerospace simulator (NAS) must replace out-of-date production testbeds in as timely a fashion as possible, and cannot afford to ignore innovative designs such as new distributed shared memory machines, clustered commodity-based computers, and multi-threaded architectures.

  14. Structuring Formal Requirements Specifications for Reuse and Product Families

    Heimdahl, Mats P. E.

    2001-01-01

    In this project we have investigated how formal specifications should be structured to allow for requirements reuse, product family engineering, and ease of requirements change, The contributions of this work include (1) a requirements specification methodology specifically targeted for critical avionics applications, (2) guidelines for how to structure state-based specifications to facilitate ease of change and reuse, and (3) examples from the avionics domain demonstrating the proposed approach.

  15. A Framework for the Management of Evolving Requirements in Software Systems Supporting Network-Centric Warfare

    Reynolds, Linda K

    2006-01-01

    .... There are many sources of requirements for these software systems supporting NCO, which may increase in number as the Services continue to develop the capabilities necessary for the transformation...

  16. Attributes Of Quality Scenarios/Scenario Sets Used In Software Requirements Elicitation

    Braun, Kimberly

    1997-01-01

    .... This thesis examines scenarios used in software requirements elicitation. Many different definitions, formats, and ideas exist on scenarios, but no thorough work has been done on what makes a good, quality scenario and scenario set...

  17. Report on the working conference on requirements engineering: foundation for software quality (REFSQ'09)

    Glinz, Martin; Heymans, Patrick; Persson, Anne; Sindre, Guttorm; Aurum, Aybüke; Madhavji, Nazim; Madhavji, N.; Paech, Barbara; Regev, Gil; Wieringa, Roelf J.

    This report summarizes the presentations and discussions at REFSQ’09, the 15th International Working Conference on Requirements Engineering: Foundation for Software Quality which was held on June 8-9, 2009 in Amsterdam, The Netherlands.

  18. Requirements Report Computer Software System for a Semi-Automatic Pipe Handling System and Fabrication Facility

    1980-01-01

    .... This report is to present the requirements of the computer software that must be developed to create Pipe Detail Drawings and to support the processing of the Pipe Detail Drawings through the Pipe Shop...

  19. Requirements on software lifecycle process (RSLP) for KALIMER digital computer-based MMIS design

    Lee, Jang Soo; Kwon, Kee Choon; Kim, Jang Yeol [Korea Atomic Energy Research Institute, Taejon (Korea)

    1998-04-01

    Digital Man Machine Interface System (MMIS) systems of Korea Advanced Liquid MEtal Reactor (KALIMER) may share code, data transmission, data, and process equipment to a greater degree than analog systems. Although this sharing is the basis for many of the advantages of digital systems, it also raises a key concern: a design using shared data or code has the potential to propagate a common-cause or common-mode failure via software errors, thus defeating the redundancy achieved by the hardware architectural structure. Greater sharing of process equipment among functions within a channel increases the consequences of the failure of a single hardware module and reduces the amount of diversity available within a single safety channel. The software safety plan describes the safety analysis implementation tasks that are to be carried out during the software life cycle. Documentation should exist that shows that the safety analysis activities have been successfully accomplished for each life cycle activity group. In particular, the documentation should show that the system safety requirement have been adequately addressed for each life cycle activity group, that no new hazards have been introduced, and that the software requirements, design elements, and code elements that can affect safety have been identified. Because the safety of software can be assured through both the process Verification and Validation (V and V) itself and the V and V of all the intermediate and final products during the software development lifecycle, the development of KALIMER Software Safety Framework (KSSF) must be established. As the first activity for establishing KSSF, we have developed this report, Requirement on Software Life-cycle Process (RSLP) for designing KALIMER digital MMIS. This report is organized as follows. Section I describes the background, definitions, and references of RSLP. Section II describes KALIMER safety software categorization. In Section III, we define the

  20. Introducing a game approach towards IS requirements specification

    Jensen, Mika Yasuoka; Kadoya, Kyoichi; Niwa, Takashi

    2014-01-01

    Devising a system requirements specification is a challenging task. Even after several decades of system development research, specifications for large-scale, widely-used systems remain difficult. In this paper, we suggest a first step toward a requirements specification through a stakeholder inv...

  1. National Ignition Facility subsystem design requirements supervisory control software SSDR 1.5.2

    Woodruff, J.; VanArsdall, P.; Bliss, E.

    1996-01-01

    This System Design Requirement document establishes the performance, design, development, and test requirements for the Supervisory Control Software, WBS 1.5.2, which is part of the NIF Integrated Computer Control System (ICCS). This document responds directly to the requirements detailed in ICCS (WBS 1-5)

  2. Computer Support of Semantic Text Analysis of a Technical Specification on Designing Software

    Zaboleeva-Zotova, Alla; Orlova, Yulia

    2009-01-01

    The given work is devoted to development of the computer-aided system of semantic text analysis of a technical specification. The purpose of this work is to increase efficiency of software engineering based on automation of semantic text analysis of a technical specification. In work it is offered and investigated a technique of the text analysis of a technical specification is submitted, the expanded fuzzy attribute grammar of a technical specification, intended for formaliza...

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

    Mckee, James W.

    1990-01-01

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

  4. CARDS: A blueprint and environment for domain-specific software reuse

    Wallnau, Kurt C.; Solderitsch, Anne Costa; Smotherman, Catherine

    1992-01-01

    CARDS (Central Archive for Reusable Defense Software) exploits advances in domain analysis and domain modeling to identify, specify, develop, archive, retrieve, understand, and reuse domain-specific software components. An important element of CARDS is to provide visibility into the domain model artifacts produced by, and services provided by, commercial computer-aided software engineering (CASE) technology. The use of commercial CASE technology is important to provide rich, robust support for the varied roles involved in a reuse process. We refer to this kind of use of knowledge representation systems as supporting 'knowledge-based integration.'

  5. Software attribute visualization for high integrity software

    Pollock, G.M.

    1998-03-01

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

  6. HeteroGenius: A Framework for Hybrid Analysis of Heterogeneous Software Specifications

    Manuel Giménez

    2014-01-01

    Full Text Available Nowadays, software artifacts are ubiquitous in our lives being an essential part of home appliances, cars, cell phones, and even in more critical activities like aeronautics and health sciences. In this context software failures may produce enormous losses, either economical or, in the worst case, in human lives. Software analysis is an area in software engineering concerned with the application of diverse techniques in order to prove the absence of errors in software pieces. In many cases different analysis techniques are applied by following specific methodological combinations that ensure better results. These interactions between tools are usually carried out at the user level and it is not supported by the tools. In this work we present HeteroGenius, a framework conceived to develop tools that allow users to perform hybrid analysis of heterogeneous software specifications. HeteroGenius was designed prioritising the possibility of adding new specification languages and analysis tools and enabling a synergic relation of the techniques under a graphical interface satisfying several well-known usability enhancement criteria. As a case-study we implemented the functionality of Dynamite on top of HeteroGenius.

  7. A PLC generic requirements and specification for safety-related applications in nuclear power plants

    Han, Jea Bok; Lee, C. K.; Lee, D. Y.

    2001-12-01

    This report presents the requirements and specification to be applied to the generic qualification of programmable Logic Controller(PLC), which is being developed as part of the KNICS project, 'Development of the Digital Reactor Safety Systems' of which purpose is the application to safety-related instrumentation and control systems in nuclear power plants. This report defines the essential and critical characteristics that shall be included as part of a PLC design for safety-related application. The characteristics include performance, reliability, accuracy, the overall response time from an input to the PLC exceeding it trip condition to the resulting outputs, and the specification of processors and memories in digital controller. It also specifies the quality assurance process for software development, dealing with executive software, firmware, application software tools for developing the application software, and human machine interface(HMI). In addition, this report reviews the published standards and guidelines that are required for the PLC development and the quality assurance processes such as environment requirements, seismic withstand requirements, EMI/RFI withstand requirements, and isolation test

  8. Towards an Early Software Effort Estimation Based on Functional and Non-Functional Requirements

    Kassab, Mohamed; Daneva, Maya; Ormandjieva, Olga

    The increased awareness of the non-functional requirements as a key to software project and product success makes explicit the need to include them in any software project effort estimation activity. However, the existing approaches to defining size-based effort relationships still pay insufficient attention to this need. This paper presents a flexible, yet systematic approach to the early requirements-based effort estimation, based on Non-Functional Requirements ontology. It complementarily uses one standard functional size measurement model and a linear regression technique. We report on a case study which illustrates the application of our solution approach in context and also helps evaluate our experiences in using it.

  9. Qualification of Simulation Software for Safety Assessment of Sodium Cooled Fast Reactors. Requirements and Recommendations

    Brown, Nicholas R. [Oak Ridge National Lab. (ORNL), Oak Ridge, TN (United States); Pointer, William David [Oak Ridge National Lab. (ORNL), Oak Ridge, TN (United States); Sieger, Matt [Oak Ridge National Lab. (ORNL), Oak Ridge, TN (United States); Flanagan, George F. [Oak Ridge National Lab. (ORNL), Oak Ridge, TN (United States); Moe, Wayne [Oak Ridge National Lab. (ORNL), Oak Ridge, TN (United States); HolbrookINL, Mark [Oak Ridge National Lab. (ORNL), Oak Ridge, TN (United States)

    2016-04-01

    The goal of this review is to enable application of codes or software packages for safety assessment of advanced sodium-cooled fast reactor (SFR) designs. To address near-term programmatic needs, the authors have focused on two objectives. First, the authors have focused on identification of requirements for software QA that must be satisfied to enable the application of software to future safety analyses. Second, the authors have collected best practices applied by other code development teams to minimize cost and time of initial code qualification activities and to recommend a path to the stated goal.

  10. An integrated approach for requirement selection and scheduling in software release planning

    Li, C.; van den Akker, Marjan; Brinkkemper, Sjaak; Diepen, Guido

    2010-01-01

    It is essential for product software companies to decide which requirements should be included in the next release and to make an appropriate time plan of the development project. Compared to the extensive research done on requirement selection, very little research has been performed on time

  11. Automated Translation of Safety Critical Application Software Specifications into PLC Ladder Logic

    Leucht, Kurt W.; Semmel, Glenn S.

    2008-01-01

    The numerous benefits of automatic application code generation are widely accepted within the software engineering community. A few of these benefits include raising the abstraction level of application programming, shorter product development time, lower maintenance costs, and increased code quality and consistency. Surprisingly, code generation concepts have not yet found wide acceptance and use in the field of programmable logic controller (PLC) software development. Software engineers at the NASA Kennedy Space Center (KSC) recognized the need for PLC code generation while developing their new ground checkout and launch processing system. They developed a process and a prototype software tool that automatically translates a high-level representation or specification of safety critical application software into ladder logic that executes on a PLC. This process and tool are expected to increase the reliability of the PLC code over that which is written manually, and may even lower life-cycle costs and shorten the development schedule of the new control system at KSC. This paper examines the problem domain and discusses the process and software tool that were prototyped by the KSC software engineers.

  12. Identified adjustability dimensions when generating a product specific requirements specification by requirements reuse

    Hauksdóttir, Dagný; Mortensen, Niels Henrik; Nielsen, Poul Erik

    2014-01-01

    . An extensive state of the art is included to introduce the presented methods related to each adjustability dimensions. The options for implementing each adjustability dimensions in a requirement reuse approach are illustrated along with a discussion regarding the benefits and issues resulting from each option....... This discussion should help practitioners to better understand the possible methods that can be implemented and to design a user friendly and sustainable approach. A case study, describing how the dimensions are incorporated in two requirements reuse approaches, for Danfoss Solar Inverters (SI) and Danfoss...

  13. Requirement analysis of the safety-critical software implementation for the nuclear power plant

    Chang, Hoon Seon; Jung, Jae Cheon; Kim, Jae Hack; Nam, Sang Ku; Kim, Hang Bae

    2005-01-01

    The safety critical software shall be implemented under the strict regulation and standards along with hardware qualification. In general, the safety critical software has been implemented using functional block language (FBL) and structured language like C in the real project. Software design shall comply with such characteristics as; modularity, simplicity, minimizing the use of sub-routine, and excluding the interrupt logic. To meet these prerequisites, we used the computer-aided software engineering (CASE) tool to substantiate the requirements traceability matrix that were manually developed using Word processors or Spreadsheets. And the coding standard and manual have been developed to confirm the quality of software development process, such as; readability, consistency, and maintainability in compliance with NUREG/CR-6463. System level preliminary hazard analysis (PHA) is performed by analyzing preliminary safety analysis report (PSAR) and FMEA document. The modularity concept is effectively implemented for the overall module configurations and functions using RTP software development tool. The response time imposed on the basis of the deterministic structure of the safety-critical software was measured

  14. A Systematic Mapping on Supporting Approaches for Requirements Traceability in the Context of Software Projects

    MALCHER, P R.C.

    2015-12-01

    Full Text Available The Requirements Traceability is seen as a quality factor with regard to software development, being present in standards and quality models. In this context, several techniques, models, frameworks and tools have been used to support it. Thus, the purpose of this paper is to present a systematic mapping carried out in order to find in the literature approaches to support the requirements traceability in the context of software projects and make the categorization of the data found in order to demonstrate, by means of a reliable, accurate and auditable method, how this area has developed and what are the main approaches are used to implement it.

  15. Design Requirements, Epistemic Uncertainty and Solution Development Strategies in Software Design

    Ball, Linden J.; Onarheim, Balder; Christensen, Bo Thomas

    2010-01-01

    This paper investigates the potential involvement of “epistemic uncertainty” in mediating between complex design requirements and strategic switches in software design strategies. The analysis revealed that the designers produced an initial “first-pass” solution to the given design brief in a bre...... a view of software design as involving a mixed breadth-first and depth-first solution development approach, with strategic switching to depth-first design being triggered by requirement complexity and being mediated by associated feelings of uncertainty....

  16. A Hybrid Parallel Execution Model for Logic Based Requirement Specifications (Invited Paper

    Jeffrey J. P. Tsai

    1999-05-01

    Full Text Available It is well known that undiscovered errors in a requirements specification is extremely expensive to be fixed when discovered in the software maintenance phase. Errors in the requirement phase can be reduced through the validation and verification of the requirements specification. Many logic-based requirements specification languages have been developed to achieve these goals. However, the execution and reasoning of a logic-based requirements specification can be very slow. An effective way to improve their performance is to execute and reason the logic-based requirements specification in parallel. In this paper, we present a hybrid model to facilitate the parallel execution of a logic-based requirements specification language. A logic-based specification is first applied by a data dependency analysis technique which can find all the mode combinations that exist within a specification clause. This mode information is used to support a novel hybrid parallel execution model, which combines both top-down and bottom-up evaluation strategies. This new execution model can find the failure in the deepest node of the search tree at the early stage of the evaluation, thus this new execution model can reduce the total number of nodes searched in the tree, the total processes needed to be generated, and the total communication channels needed in the search process. A simulator has been implemented to analyze the execution behavior of the new model. Experiments show significant improvement based on several criteria.

  17. SafetyAnalyst : software tools for safety management of specific highway sites

    2010-07-01

    SafetyAnalyst provides a set of software tools for use by state and local highway agencies for highway safety management. SafetyAnalyst can be used by highway agencies to improve their programming of site-specific highway safety improvements. SafetyA...

  18. Seafood Spoilage Predictor - development and distribution of a product specific application software

    Dalgaard, Paw; Buch, P.; Silberg, Steen

    2002-01-01

    To allow shelf-life prediction of a range of products, the Seafood Spoilage Predictor (SSP) software has been developed to include both kinetic models for growth of specific spoilage microorganisms and empirical relative rates of spoilage models. SSP can read and evaluate temperature profile data...

  19. Hepsoft - an approach for up to date multi-platform deployment of HEP specific software

    Roiser, S

    2011-01-01

    LHC experiments are depending on a rich palette of software components to build their specific applications. These underlying software components include the ROOT analysis framework, the Geant4 simulation toolkit, Monte Carlo generators, grid middle-ware, graphics libraries, scripting languages, databases, tools, etc. which are provided centrally in up to date versions on multiple platforms (Linux, Mac, Windows). Until recently this set of packages has been tested and released in a tree like structure as a consistent set of versions across operating systems, architectures and compilers for LHC experiments only. Because of the tree like deployment these releases were only usable in connection with a configuration management tool which provided the proper build and run-time environments and was hindering other parties outside LHC from easily using this palette of packages. In a new approach the releases will be grouped in 'flat structure' such that interested parties can start using it without configuration management, retaining all the above mentioned advantages. In addition to an increased usability the software shall also be distributed via system provided package deployment systems (rpm, apt, etc.). The approach of software deployment is following the ideas of providing a wide range of HEP specific software packages and tools in a coherent, up to date and modular way on multiple platforms. The target audience for such software deployments are individual developers or smaller development groups / experiments who don't have the resources to maintain this kind of infrastructure. This new software deployment strategy has already been successfully implemented for groups at CERN.

  20. Global Software Engineering: A Software Process Approach

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

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

  1. Dependencies among Architectural Views Got from Software Requirements Based on a Formal Model

    Osis Janis

    2014-12-01

    Full Text Available A system architect has software requirements and some unspecified knowledge about a problem domain (e.g., an enterprise as source information for assessment and evaluation of possible solutions and getting the target point, a preliminary software design. The solving factor is architect’s experience and expertise in the problem domain (“AS-IS”. A proposed approach is dedicated to assist a system architect in making an appropriate decision on the solution (“TO-BE”. It is based on a formal mathematical model, Topological Functioning Model (TFM. Compliant TFMs can be transformed into software architectural views. The paper demonstrates and discusses tracing dependency links from the requirements to and between the architectural views.

  2. Planning is not sufficient - Reliable computers need good requirements specifications

    Matras, J.R.

    1992-01-01

    Computer system reliability is the assurance that a computer system will perform its functions when required to do so. To ensure such reliability, it is important to plan the activities needed for computer system development. These development activities, in turn, require a Computer Quality Assurance Plan (CQAP) that provides the following: a Configuration Management Plan, a Verification and Validation (V and V) Plan, documentation requirements, a defined life cycle, review requirements, and organizational responsibilities. These items are necessary for system reliability; ultimately, however, they are not enough. Development of a reliable system is dependent on the requirements specification. This paper discusses how to use existing industry standards to develop a CQAP. In particular, the paper emphasizes the importance of the requirements specification and of methods for establishing reliability goals. The paper also describes how the revision of ANSI/IEE-ANS-7-4.3.2, Application Criteria for Digital Computer Systems of Nuclear Power Generating Stations, has addressed these issues

  3. 47 CFR 76.75 - Specific EEO program requirements.

    2010-10-01

    ... MULTICHANNEL VIDEO AND CABLE TELEVISION SERVICE Equal Employment Opportunity Requirements § 76.75 Specific EEO... or sex is prohibited and that they may notify the Equal Employment Opportunity Commission, the... necessary. Nothing in this section shall be interpreted to require a multichannel video programming...

  4. Software development for specific geometry and safe design of isotropic material multicell beams

    Tariq, M.M.; Ahmed, M.A.

    2011-01-01

    Comparison of analytical results with finite element results for analysis of isotropic material multicell beams subjected to free torsion case is the main idea of this paper. Progress in the fundamentals and applications of advanced materials and their processing technologies involves costly experiments and prototype testing for reliability. The software development for design analysis of structures with advanced materials is a low cost but challenging research. Multicell beams have important industrial applications in the aerospace and automotive sectors. This paper explains software development to test different materials in design of a multicell beam. Objective of this paper is to compute the torsional loading of multicell beams of isotropic materials for safe design in both symmetrical and asymmetrical geometries. Software has been developed in Microsoft Visual Basic. Distribution of Saint Venant shear flows, shear stresses, factors of safety, volume, mass, weight, twist, polar moment of inertia and aspect ratio for free torsion in multicell beam have been calculated using this software. The software works on four algorithms, these are, Specific geometry algorithm, material selection algorithm, factor of safety algorithm and global algorithm. User can specify new materials analytically, or choose a pre-defined material from the list, which includes, plain carbon steels, low alloy steels, stainless steels, cast irons, aluminum alloys, copper alloys, magnesium alloys, titanium alloys, precious metals and refractory metals. Although this software is restricted to multicell beam comprising of three cells, however future versions can have ability to address more complicated shapes and cases of multicell beams. Software also describes nomenclature and mathematical formulas applied to help user understand the theoretical background. User can specify geometry of multicell beam for three rectangular cells. Software computes shear flows, shear stresses, safety factors

  5. Software Hardware Asset Reuse Enterprise (SHARE) Repository Framework Final Report: Component Specification and Ontology

    Johnson, Jean; Blais, Curtis

    2008-01-01

    ...) was tasked to develop a component specification and ontology for the SHARE repository. A description of SHARE and the requirements for a component specification and ontology supporting this repository are available in Johnson (2007...

  6. A Framework for RFID Survivability Requirement Analysis and Specification

    Zuo, Yanjun; Pimple, Malvika; Lande, Suhas

    Many industries are becoming dependent on Radio Frequency Identification (RFID) technology for inventory management and asset tracking. The data collected about tagged objects though RFID is used in various high level business operations. The RFID system should hence be highly available, reliable, and dependable and secure. In addition, this system should be able to resist attacks and perform recovery in case of security incidents. Together these requirements give rise to the notion of a survivable RFID system. The main goal of this paper is to analyze and specify the requirements for an RFID system to become survivable. These requirements, if utilized, can assist the system in resisting against devastating attacks and recovering quickly from damages. This paper proposes the techniques and approaches for RFID survivability requirements analysis and specification. From the perspective of system acquisition and engineering, survivability requirement is the important first step in survivability specification, compliance formulation, and proof verification.

  7. Detailed requirements document for common software of shuttle program information management system

    Everette, J. M.; Bradfield, L. D.; Horton, C. L.

    1975-01-01

    Common software was investigated as a method for minimizing development and maintenance cost of the shuttle program information management system (SPIMS) applications while reducing the time-frame of their development. Those requirements satisfying these criteria are presented along with the stand-alone modules which may be used directly by applications. The SPIMS applications operating on the CYBER 74 computer, are specialized information management systems which use System 2000 as a data base manager. Common software provides the features to support user interactions on a CRT terminal using form input and command response capabilities. These features are available as subroutines to the applications.

  8. Safety of Nuclear Power Plants: Design. Specific Safety Requirements

    2012-01-01

    On the basis of the principles included in the Fundamental Safety Principles, IAEA Safety Standards Series No. SF-1, this Safety Requirements publication establishes requirements applicable to the design of nuclear power plants. It covers the design phase and provides input for the safe operation of the power plant. It elaborates on the safety objective, safety principles and concepts that provide the basis for deriving the safety requirements that must be met for the design of a nuclear power plant. Contents: 1. Introduction; 2. Applying the safety principles and concepts; 3. Management of safety in design; 4. Principal technical requirements; 5. General plant design; 6. Design of specific plant systems.

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

    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.

  10. Active Mirror Predictive and Requirements Verification Software (AMP-ReVS)

    Basinger, Scott A.

    2012-01-01

    This software is designed to predict large active mirror performance at various stages in the fabrication lifecycle of the mirror. It was developed for 1-meter class powered mirrors for astronomical purposes, but is extensible to other geometries. The package accepts finite element model (FEM) inputs and laboratory measured data for large optical-quality mirrors with active figure control. It computes phenomenological contributions to the surface figure error using several built-in optimization techniques. These phenomena include stresses induced in the mirror by the manufacturing process and the support structure, the test procedure, high spatial frequency errors introduced by the polishing process, and other process-dependent deleterious effects due to light-weighting of the mirror. Then, depending on the maturity of the mirror, it either predicts the best surface figure error that the mirror will attain, or it verifies that the requirements for the error sources have been met once the best surface figure error has been measured. The unique feature of this software is that it ties together physical phenomenology with wavefront sensing and control techniques and various optimization methods including convex optimization, Kalman filtering, and quadratic programming to both generate predictive models and to do requirements verification. This software combines three distinct disciplines: wavefront control, predictive models based on FEM, and requirements verification using measured data in a robust, reusable code that is applicable to any large optics for ground and space telescopes. The software also includes state-of-the-art wavefront control algorithms that allow closed-loop performance to be computed. It allows for quantitative trade studies to be performed for optical systems engineering, including computing the best surface figure error under various testing and operating conditions. After the mirror manufacturing process and testing have been completed, the

  11. Designing for Change: Minimizing the Impact of Changing Requirements in the Later Stages of a Spaceflight Software Project

    Allen, B. Danette

    1998-01-01

    In the traditional 'waterfall' model of the software project life cycle, the Requirements Phase ends and flows into the Design Phase, which ends and flows into the Development Phase. Unfortunately, the process rarely, if ever, works so smoothly in practice. Instead, software developers often receive new requirements, or modifications to the original requirements, well after the earlier project phases have been completed. In particular, projects with shorter than ideal schedules are highly susceptible to frequent requirements changes, as the software requirements analysis phase is often forced to begin before the overall system requirements and top-level design are complete. This results in later modifications to the software requirements, even though the software design and development phases may be complete. Requirements changes received in the later stages of a software project inevitably lead to modification of existing developed software. Presented here is a series of software design techniques that can greatly reduce the impact of last-minute requirements changes. These techniques were successfully used to add built-in flexibility to two complex software systems in which the requirements were expected to (and did) change frequently. These large, real-time systems were developed at NASA Langley Research Center (LaRC) to test and control the Lidar In-Space Technology Experiment (LITE) instrument which flew aboard the space shuttle Discovery as the primary payload on the STS-64 mission.

  12. Importance of Requirements Analysis & Traceability to Improve Software Quality and Reduce Cost and Risk

    Kapoor, Manju M.; Mehta, Manju

    2010-01-01

    The goal of this paper is to emphasize the importance of developing complete and unambiguous requirements early in the project cycle (prior to Preliminary Design Phase). Having a complete set of requirements early in the project cycle allows sufficient time to generate a traceability matrix. Requirements traceability and analysis are the key elements in improving verification and validation process, and thus overall software quality. Traceability can be most beneficial when the system changes. If changes are made to high-level requirements it implies that low-level requirements need to be modified. Traceability ensures that requirements are appropriately and efficiently verified at various levels whereas analysis ensures that a rightly interpreted set of requirements is produced.

  13. Towards an Ontology of Software

    Wang, Xiaowei

    2016-01-01

    Software is permeating every aspect of our personal and social life. And yet, the cluster of concepts around the notion of software, such as the notions of a software product, software requirements, software specifications, are still poorly understood with no consensus on the horizon. For many, software is just code, something intangible best defined in contrast with hardware, but it is not particularly illuminating. This erroneous notion, software is just code, presents both in the ontology ...

  14. Transforming Multidisciplinary Customer Requirements to Product Design Specifications

    Ma, Xiao-Jie; Ding, Guo-Fu; Qin, Sheng-Feng; Li, Rong; Yan, Kai-Yin; Xiao, Shou-Ne; Yang, Guang-Wu

    2017-09-01

    With the increasing of complexity of complex mechatronic products, it is necessary to involve multidisciplinary design teams, thus, the traditional customer requirements modeling for a single discipline team becomes difficult to be applied in a multidisciplinary team and project since team members with various disciplinary backgrounds may have different interpretations of the customers' requirements. A new synthesized multidisciplinary customer requirements modeling method is provided for obtaining and describing the common understanding of customer requirements (CRs) and more importantly transferring them into a detailed and accurate product design specifications (PDS) to interact with different team members effectively. A case study of designing a high speed train verifies the rationality and feasibility of the proposed multidisciplinary requirement modeling method for complex mechatronic product development. This proposed research offersthe instruction to realize the customer-driven personalized customization of complex mechatronic product.

  15. Functional requirement specification in the packaging development chain

    Lutters, Diederick; ten Klooster, Roland

    2008-01-01

    As it is clear that the full packaging life cycle – at least partially – coincides with the product life cycle, both cycles are interwoven. Each has a network of functional requirements, with specific hierarchic propensities. These networks overlap, with prevailing hierarchies playing important

  16. Information Requirements Specification II: Brainstorming Collective Decision-Making Technique.

    Telem, Moshe

    1988-01-01

    Information requirements specification (IRS) constitutes an Achilles heel in the system life cycle of management information systems. This article establishes a systematic overall IRS technique applicable to organizations of all types and sizes. The technique's integration of brainstorming and theory Z principles creates an effective, stimulating,…

  17. 49 CFR 179.401-1 - Individual specification requirements.

    2010-10-01

    ...) § 179.400-5(d). Standard heat transfer rate. (Btu per day per lb. of water capacity, max.) (see § 179... FOR TANK CARS Specification for Cryogenic Liquid Tank Car Tanks and Seamless Steel Tanks (Classes DOT... restrictions § 179.400-20 179.400-20. Transfer line insulation § 179.400-17 Not required. [Amdt. 179-32, 48 FR...

  18. Draft Geologic Disposal Requirements Basis for STAD Specification

    Ilgen, Anastasia G. [Sandia National Lab. (SNL-NM), Albuquerque, NM (United States); Bryan, Charles R. [Sandia National Lab. (SNL-NM), Albuquerque, NM (United States); Hardin, Ernest [Sandia National Lab. (SNL-NM), Albuquerque, NM (United States)

    2015-03-25

    This document provides the basis for requirements in the current version of Performance Specification for Standardized Transportation, Aging, and Disposal Canister Systems, (FCRD-NFST-2014-0000579) that are driven by storage and geologic disposal considerations. Performance requirements for the Standardized Transportation, Aging, and Disposal (STAD) canister are given in Section 3.1 of that report. Here, the requirements are reviewed and the rationale for each provided. Note that, while FCRD-NFST-2014-0000579 provides performance specifications for other components of the STAD storage system (e.g. storage overpack, transfer and transportation casks, and others), these have no impact on the canister performance during disposal, and are not discussed here.

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

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

    1992-01-01

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

  20. System requirements for one-time-use ENRAF control panel software

    HUBER, J.H.

    1999-01-01

    An Enraf Densitometer is installed on tank 241-AY-102. The Densitometer will frequently be tasked to obtain and log density profiles. The activity can be effected a number of ways. Enraf Incorporated provides a software package called ''Logger18'' to its customers for the purpose of in-shop testing of their gauges. Logger18 is capable of accepting an input file which can direct the gauge to obtain a density profile for a given tank level and bottom limit. Logger18 is a complex, DOS based program which will require trained technicians and/or tank farm entries to obtain the data. ALARA considerations have prompted the development of a more user-friendly, computer-based interface to the Enraf densitometers. This document records the plan by which this new Enraf data acquisition software will be developed, reviewed, verified, and released. This plan applies to the development and implementation of a one-time-use software program, which will be called ''Enraf Control Panel.'' The software will be primarily used for remote operation of Enraf Densitometers for the purpose of obtaining and logging tank product density profiles

  1. Software requirements elicitation to support internal monitoring of quality assurance system for higher education in Indonesia

    Amalia, A.; Gunawan, D.; Hardi, S. M.; Rachmawati, D.

    2018-02-01

    The Internal Quality Assurance System (in Indonesian: SPMI (Sistem Penjaminan Mutu Internal) is a systemic activity of quality assurance of higher education in Indonesia. SPMI should be done by all higher education or universities in Indonesia based on the Regulation of the Minister of Research, Technology and Higher Education of the Republic of Indonesia Number 62 of 2016. Implementation of SPMI must refer to the principle of SPMI that is independent, standardize, accurate, well planned and sustainable, documented and systematic. To assist the SPMI cycle properly, universities need a supporting software to monitor all the activities of SPMI. But in reality, many universities are not optimal in building this SPMI monitoring system. One of the obstacles is the determination of system requirements in support of SPMI principles is difficult to achieve. In this paper, we observe the initial phase of the engineering requirements elicitation. Unlike other methods that collect system requirements from users and stakeholders, we find the system requirements of the SPMI principles from SPMI guideline book. The result of this paper can be used as a choice in determining SPMI software requirements. This paper can also be used by developers and users to understand the scenario of SPMI so that could overcome the problems of understanding between this two parties.

  2. Using formal specification in the Guidance and Control Software (GCS) experiment. Formal design and verification technology for life critical systems

    Weber, Doug; Jamsek, Damir

    1994-01-01

    The goal of this task was to investigate how formal methods could be incorporated into a software engineering process for flight-control systems under DO-178B and to demonstrate that process by developing a formal specification for NASA's Guidance and Controls Software (GCS) Experiment. GCS is software to control the descent of a spacecraft onto a planet's surface. The GCS example is simplified from a real example spacecraft, but exhibits the characteristics of realistic spacecraft control software. The formal specification is written in Larch.

  3. Romanian regulatory requirements on nuclear field specific education needs

    Biro, L.; Velicu, O.

    2004-01-01

    This work is intended as a general presentation of the educational system and research field, with reference to nuclear sciences, and the legal system, with reference to requirements established by the regulatory body for the professional qualification and periodic training of personnel involved in different activities in the nuclear field. Thus, part 2 and 3 of the work present only public information regarding the education in nuclear sciences and nuclear research in Romania; in part 4 the CNCAN requirements for the personnel training, specific to nuclear activities are slightly detailed; part 5 consists of few words about the public information activities in Romania; and part 6 tries to draw a conclusion. (authors)

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

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

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

  5. A Research Agenda for Identifying and Developing Required Competencies in Software Engineering

    Yvonne Sedelmaier

    2013-04-01

    Full Text Available 0 0 1 130 820 Hochschule Coburg 6 1 949 14.0 96 Normal 0 21 false false false DE JA X-NONE /* Style Definitions */ table.MsoNormalTable {mso-style-name:"Normale Tabelle"; mso-tstyle-rowband-size:0; mso-tstyle-colband-size:0; mso-style-noshow:yes; mso-style-priority:99; mso-style-parent:""; mso-padding-alt:0cm 5.4pt 0cm 5.4pt; mso-para-margin:0cm; mso-para-margin-bottom:.0001pt; mso-pagination:widow-orphan; font-size:10.0pt; font-family:"Times New Roman";} Various issues make learning and teaching software engineering a challenge for both students and instructors. Since there are no standard curricula and no cookbook recipes for successful software engineering, it is fairly hard to figure out which specific topics and competencies should be learned or acquired by a particular group of students. Furthermore, it is not clear which particular didactic approaches might work well for a specific topic and a particular group of students. This contribution presents a research agenda that aims at identifying relevant competencies and environmental constraints as well as their effect on learning and teaching software engineering. To that end, an experimental approach will be taken. As a distinctive feature, this approach iteratively introduces additional or modified didactical methods into existing courses and carefully evaluates their appropriateness. Thus, it continuously improves these methods.

  6. Risk impact of BWR technical specifications requirements during shutdown

    Staple, B.D.; Kirk, H.K.; Yakle, J.

    1994-10-01

    This report presents an application of probabilistic models and risk based criteria for determining the risk impact of the Limiting Conditions of Operations (LCOs) in the Technical Specifications (TSs) of a boiling water reactor during shutdown. This analysis studied the risk impact of the current requirements of Allowed Outage Times (AOTs) and Surveillance Test Intervals (STIs) in eight Plant Operational States (POSs) which encompass power operations, shutdown, and refueling. This report also discusses insights concerning TS action statements

  7. Modeling of requirement specification for safety critical real time computer system using formal mathematical specifications

    Sankar, Bindu; Sasidhar Rao, B.; Ilango Sambasivam, S.; Swaminathan, P.

    2002-01-01

    Full text: Real time computer systems are increasingly used for safety critical supervision and control of nuclear reactors. Typical application areas are supervision of reactor core against coolant flow blockage, supervision of clad hot spot, supervision of undesirable power excursion, power control and control logic for fuel handling systems. The most frequent cause of fault in safety critical real time computer system is traced to fuzziness in requirement specification. To ensure the specified safety, it is necessary to model the requirement specification of safety critical real time computer systems using formal mathematical methods. Modeling eliminates the fuzziness in the requirement specification and also helps to prepare the verification and validation schemes. Test data can be easily designed from the model of the requirement specification. Z and B are the popular languages used for modeling the requirement specification. A typical safety critical real time computer system for supervising the reactor core of prototype fast breeder reactor (PFBR) against flow blockage is taken as case study. Modeling techniques and the actual model are explained in detail. The advantages of modeling for ensuring the safety are summarized

  8. A Data Specification for Software Project Performance Measures: Results of a Collaboration on Performance Measurement

    Kasunic, Mark

    2008-01-01

    ... between completed projects. These terms and definitions were developed using a collaborative, consensus-based approach involving the Software Engineering Institute's Software Engineering Process Management program and service...

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

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

    2014-12-01

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

  10. Development of an expert system prototype for determining software functional requirements for command management activities at NASA Goddard

    Liebowitz, J.

    1986-01-01

    The development of an expert system prototype for software functional requirement determination for NASA Goddard's Command Management System, as part of its process of transforming general requests into specific near-earth satellite commands, is described. The present knowledge base was formulated through interactions with domain experts, and was then linked to the existing Knowledge Engineering Systems (KES) expert system application generator. Steps in the knowledge-base development include problem-oriented attribute hierarchy development, knowledge management approach determination, and knowledge base encoding. The KES Parser and Inspector, in addition to backcasting and analogical mapping, were used to validate the expert system-derived requirements for one of the major functions of a spacecraft, the solar Maximum Mission. Knowledge refinement, evaluation, and implementation procedures of the expert system were then accomplished.

  11. Specific developed phantoms and software to assess radiological equipment image quality

    Verdu, G., E-mail: gverdu@iqn.upv.es [Universidad Politecnica de Valencia (Spain). Dept. de Ingenieria Quimica y Nuclear; Mayo, P., E-mail: p.mayo@titaniast.com [TITANIA Servicios Teconologicos, Valencia (Spain); Rodenas, F., E-mail: frodenas@mat.upv.es [Universidad Politecnica de Valencia (Spain). Dept. de Matematica Aplicada; Campayo, J.M., E-mail: j.campayo@lainsa.com [Logistica y Acondicionamientos Industriales S.A.U (LAINSA), Valencia (Spain)

    2011-07-01

    The use of radiographic phantoms specifically designed to evaluate the operation of the radiographic equipment lets the study of the image quality obtained by this equipment in an objective way. In digital radiographic equipment, the analysis of the image quality can be automatized because the acquisition of the image is possible in different technologies that are, computerized radiography or phosphor plate and direct radiography or detector. In this work we have shown an application to assess automatically the constancy quality image in the image chain of the radiographic equipment. This application is integrated by designed radiographic phantoms which are adapted to conventional, dental equipment and specific developed software for the automatic evaluation of the phantom image quality. The software is based on digital image processing techniques that let the automatic detection of the different phantom tests by edge detector, morphological operators, threshold histogram techniques, etc. The utility developed is enough sensitive to the radiographic equipment of operating conditions of voltage (kV) and charge (mAs). It is a friendly user programme connected with a data base of the hospital or clinic where it has been used. After the phantom image processing the user can obtain an inform with a resume of the imaging system state with accepting and constancy results. (author)

  12. Specific developed phantoms and software to assess radiological equipment image quality

    Verdu, G.; Rodenas, F.

    2011-01-01

    The use of radiographic phantoms specifically designed to evaluate the operation of the radiographic equipment lets the study of the image quality obtained by this equipment in an objective way. In digital radiographic equipment, the analysis of the image quality can be automatized because the acquisition of the image is possible in different technologies that are, computerized radiography or phosphor plate and direct radiography or detector. In this work we have shown an application to assess automatically the constancy quality image in the image chain of the radiographic equipment. This application is integrated by designed radiographic phantoms which are adapted to conventional, dental equipment and specific developed software for the automatic evaluation of the phantom image quality. The software is based on digital image processing techniques that let the automatic detection of the different phantom tests by edge detector, morphological operators, threshold histogram techniques, etc. The utility developed is enough sensitive to the radiographic equipment of operating conditions of voltage (kV) and charge (mAs). It is a friendly user programme connected with a data base of the hospital or clinic where it has been used. After the phantom image processing the user can obtain an inform with a resume of the imaging system state with accepting and constancy results. (author)

  13. Getting the balance right between functional and non-functional requirements: the case of requirement specification in IT procurement

    Björn Johansson

    2013-01-01

    Full Text Available IT procurement represents a business process of high importance, including the ability to articulate requirements that the procurement deals with. Furthermore, specifying requirements is of importance for both procurer and potential supplier, as it functions as central contractual element between the two. The purpose of this article is two-fold: (i to show how established terminology for requirement specification is represented in current call for bids for the procurement of IT; and (ii to introduce an organizing framework that may assist procurers in actively addressing functional requirements and business requirements. Ten “call for bids” were examined from a Swedish national procurement database. From the analysis of the bids, it can be concluded that: (i the call for bids displays a high degree of precision regarding hardware aspects, but less precision regarding software; (ii supplier experience and competence is stressed, but rarely elaborated on in detail; and (iii call for bids vagueness may be used as a lock-in opportunity for suppliers. From the discussion on this, a tentative procurement framework is suggested, aiming on increasing the logical transparency for the procurement of IT.

  14. Software Engineering Reviews and Audits

    Summers, Boyd L

    2011-01-01

    Accurate software engineering reviews and audits have become essential to the success of software companies and military and aerospace programs. These reviews and audits define the framework and specific requirements for verifying software development efforts. Authored by an industry professional with three decades of experience, Software Engineering Reviews and Audits offers authoritative guidance for conducting and performing software first article inspections, and functional and physical configuration software audits. It prepares readers to answer common questions for conducting and perform

  15. Evaluation of a Game to Teach Requirements Collection and Analysis in Software Engineering at Tertiary Education Level

    Hainey, Thomas; Connolly, Thomas M.; Stansfield, Mark; Boyle, Elizabeth A.

    2011-01-01

    A highly important part of software engineering education is requirements collection and analysis which is one of the initial stages of the Database Application Lifecycle and arguably the most important stage of the Software Development Lifecycle. No other conceptual work is as difficult to rectify at a later stage or as damaging to the overall…

  16. RELAP-7 Software Verification and Validation Plan: Requirements Traceability Matrix (RTM) Part 1 – Physics and numerical methods

    Choi, Yong Joon [Idaho National Lab. (INL), Idaho Falls, ID (United States); Yoo, Jun Soo [Idaho National Lab. (INL), Idaho Falls, ID (United States); Smith, Curtis Lee [Idaho National Lab. (INL), Idaho Falls, ID (United States)

    2015-09-01

    This INL plan comprehensively describes the Requirements Traceability Matrix (RTM) on main physics and numerical method of the RELAP-7. The plan also describes the testing-based software verification and validation (SV&V) process—a set of specially designed software models used to test RELAP-7.

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

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

    2016-08-01

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

  18. Evaluation of a patient-specific Monte Carlo software for CT dosimetry

    Myronakis, M.; Perisinakis, K.; Tzedakis, A.; Gourtsoyianni, S.; Damilakis, J.

    2009-01-01

    The aim was to validate the ImpactMC computed tomography (CT) dosimetry software that allows patient-specific dose determination. Measured values of head- and body-weighted CT dose index (CTDIw) were compared with corresponding values derived using ImpactMC software. A physical anthropomorphic phantom simulating the average adult was employed to study the effect of exposure parameters used to produce the input image set on a normalised dose output and the relationship between exposure parameters selected for simulation on the dose output. The difference between CTDIw values obtained through measurements and simulations were found to be up to 12.8 and 18.3% for head and body phantoms, respectively. Exposure parameters of the image set used as input were found to have a minor impact on the normalised dose output. Simulations confirmed the expected linear relationship between dose and tube load and the power law relationship between dose and tube potential. Results demonstrate that ImpactMC may be capable of providing reliable CT dose estimates. (authors)

  19. Investigation of Classification and Design Requirements for Digital Software for Advanced Research Reactors

    Park, Gee Young; Jung, H. S.; Ryu, J. S.; Park, C

    2005-06-15

    software for use in I and C systems in nuclear power plants and describes the requirements for software development recommended by international standard.

  20. Earth Observing System (EOS)/ Advanced Microwave Sounding Unit-A (AMSU-A): Special Test Equipment. Software Requirements

    Schwantje, Robert

    1995-01-01

    This document defines the functional, performance, and interface requirements for the Earth Observing System/Advanced Microwave Sounding Unit-A (EOS/AMSU-A) Special Test Equipment (STE) software used in the test and integration of the instruments.

  1. ZebrafishMiner: an open source software for interactive evaluation of domain-specific fluorescence in zebrafish

    Reischl Markus

    2017-09-01

    Full Text Available High-throughput microscopy makes it possible to observe the morphology of zebrafish on large scale to quantify genetic, toxic or drug effects. The image acquisition is done by automated microscopy, images are evaluated automatically by image processing pipelines, tailored specifically to the requirements of the scientific question. The transfer of such algorithms to other projects, however, is complex due to missing guidelines and lack of mathematical or programming knowledge. In this work, we implement an image processing pipeline for automatic fluorescence quantification in user-defined domains of zebrafish embryos and larvae of different age. The pipeline is capable of detecting embryos and larvae in image stacks and quantifying domain activity. To make this protocol available to the community, we developed an open source software package called „ZebrafishMiner“ which guides the user through all steps of the processing pipeline and makes the algorithms available and easy to handle. We implemented all routines in an MATLAB-based graphical user interface (GUI that gives the user control over all image processing parameters. The software is shipped with a manual of 30 pages and three tutorial datasets, which guide the user through the manual step by step. It can be downloaded at https://sourceforge.net/projects/scixminer/.

  2. Alloy 800 specifications in compliance with component requirements

    Diehl, H.; Bodmann, E.

    1990-01-01

    In view of the importance of the material Alloy 800 in high-temperature reactor plants (HTR), a material data bank was established which is used for statistical evaluation of mechanical and physical material behaviour. Based on investigations on the interconnection between the mechanical properties at high temperatures and the metallurgical parameters, different types of Alloy 800 were specified in compliance with the component requirements. In addition, aspects of corrosion and toughness behaviour were taken into consideration. The specifications and strength characteristics for the different variants of Alloy 800 were incorporated into draft DIN standards after discussion and approval in expert committees. Further important characteristics of the mechanical and physical material behaviour were summarized in HTR material data sheets so as to furnish an improved basis for the design and stress analyses of Alloy 800 components. (orig.)

  3. [Technological innovations in radiation oncology require specific quality controls].

    Lenaerts, E; Mathot, M

    2014-01-01

    During the last decade, the field of radiotherapy has benefited from major technological innovations and continuously improving treatment efficacy, comfort and safety of patients. This mainly concerns the imaging techniques that allow 4D CT scan recording the respiratory phases, on-board imaging on linear accelerators that ensure perfect positioning of the patient for treatment and irradiation techniques that reduce very significantly the duration of treatment sessions without compromising quality of the treatment plan, including IMRT (Intensity Modulated Radiation Therapy) and VMAT (Volumetric Modulated Arc therapy). In this context of rapid technological change, it is the responsibility of medical physicists to regularly and precisely monitor the perfect functioning of new techniques to ensure patient safety. This requires the use of specific quality control equipment best suited to these new techniques. We will briefly describe the measurement system Delta4 used to control individualized treatment plan for each patient treated with VMAT technology.

  4. A Platform for the Development and the Validation of HW IP Components Starting from Reference Software Specifications

    2009-02-01

    Full Text Available Signal processing algorithms become more and more efficient as a result of the developments of new standards. It is particularly true in the field video compression. However, at each improvement in efficiency and functionality, the complexity of the algorithms is also increasing. Textual specifications, that in the past were the original form of specifications, have been substituted by reference software which became the starting point of any design flow leading to implementation. Therefore, designing an embedded application has become equivalent to port a generic software on a, possibly heterogeneous, embedded platform. Such operation is getting more and more difficult because of the increased algorithm complexity and the wide range of architectural solutions. This paper describes a new platform aiming at supporting a step-by-step mapping of reference software (i.e., generic and nonoptimized software into software and hardware implementations. The platform provides a seamless interface between the software and hardware environments with profiling capabilities for the analysis of data transfers between hardware and software. Such profiling capabilities help the designer to achieve different implementations aiming at specific objectives such as the optimization of hardware processing resources, of the memory architectures, or the minimization of data transfers to reach low-power designs.

  5. Development of Occupational Safety and Health Requirement Management System (OSHREMS Software Using Adobe Dreamweaver CS5 for Building Construction Project

    Abas Nor Haslinda

    2017-01-01

    Full Text Available The construction industry sector is considered as being risky with frequent and high accident rate. According to Social Security Organization (SOCSO, the construction accidents has arisen from time to time. Construction Industry Development Board (CIDB has developed the Safety and Health Assessment System in Construction (SHASSIC for evaluating the performance of a contractor in construction project by setting out the safety and health management and practices, however the requirement checklist provided is not comprehensive. Therefore, this study aims to develop a software system for facilitating OSH in building construction project, namely OSH requirements management system (OSHREMS, using Adobe Dreamweaver CS5 and Sublime Text as PHP editor. The results from a preliminary study which was conducted through interviews showed that, the respondents were only implementing the basic requirements that comply with legislations, with the absence of appropriate and specific guideline in ensuring occupational safety and health (OSH at the workplace. The tool will be benefits for contractors and other parties to effectively manage the OSH requirements for their projects based on project details.

  6. Individual radiation therapy patient whole-body phantoms for peripheral dose evaluations: method and specific software

    Alziar, I; Vicente, C; Giordana, G; Ben-Harrath, O; De Vathaire, F; Diallo, I; Bonniaud, G; Couanet, D; Chavaudra, J; Lefkopoulos, D; Ruaud, J B; Diaz, J C; Grandjean, P; Kafrouni, H

    2009-01-01

    This study presents a method aimed at creating radiotherapy (RT) patient-adjustable whole-body phantoms to permit retrospective and prospective peripheral dose evaluations for enhanced patient radioprotection. Our strategy involves virtual whole-body patient models (WBPM) in different RT treatment positions for both genders and for different age groups. It includes a software tool designed to match the anatomy of the phantoms with the anatomy of the actual patients, based on the quality of patient data available. The procedure for adjusting a WBPM to patient morphology includes typical dimensions available in basic auxological tables for the French population. Adjustment is semi-automatic. Because of the complexity of the human anatomy, skilled personnel are required to validate changes made in the phantom anatomy. This research is part of a global project aimed at proposing appropriate methods and software tools capable of reconstituting the anatomy and dose evaluations in the entire body of RT patients in an adapted treatment planning system (TPS). The graphic user interface is that of a TPS adapted to obtain a comfortable working process. Such WBPM have been used to supplement patient therapy planning images, usually restricted to regions involved in treatment. Here we report, as an example, the case of a patient treated for prostate cancer whose therapy planning images were complemented by an anatomy model. Although present results are preliminary and our research is ongoing, they appear encouraging, since such patient-adjusted phantoms are crucial in the optimization of radiation protection of patients and for follow-up studies. (note)

  7. Individual radiation therapy patient whole-body phantoms for peripheral dose evaluations: method and specific software.

    Alziar, I; Bonniaud, G; Couanet, D; Ruaud, J B; Vicente, C; Giordana, G; Ben-Harrath, O; Diaz, J C; Grandjean, P; Kafrouni, H; Chavaudra, J; Lefkopoulos, D; de Vathaire, F; Diallo, I

    2009-09-07

    This study presents a method aimed at creating radiotherapy (RT) patient-adjustable whole-body phantoms to permit retrospective and prospective peripheral dose evaluations for enhanced patient radioprotection. Our strategy involves virtual whole-body patient models (WBPM) in different RT treatment positions for both genders and for different age groups. It includes a software tool designed to match the anatomy of the phantoms with the anatomy of the actual patients, based on the quality of patient data available. The procedure for adjusting a WBPM to patient morphology includes typical dimensions available in basic auxological tables for the French population. Adjustment is semi-automatic. Because of the complexity of the human anatomy, skilled personnel are required to validate changes made in the phantom anatomy. This research is part of a global project aimed at proposing appropriate methods and software tools capable of reconstituting the anatomy and dose evaluations in the entire body of RT patients in an adapted treatment planning system (TPS). The graphic user interface is that of a TPS adapted to obtain a comfortable working process. Such WBPM have been used to supplement patient therapy planning images, usually restricted to regions involved in treatment. Here we report, as an example, the case of a patient treated for prostate cancer whose therapy planning images were complemented by an anatomy model. Although present results are preliminary and our research is ongoing, they appear encouraging, since such patient-adjusted phantoms are crucial in the optimization of radiation protection of patients and for follow-up studies.

  8. Experiences from the formal specification of the integration platform and the synthesis of SDT with the software bus

    Thunem, Harald; Mohn, Peter; Sandmark, Haakon; Stoelen, Ketil

    1999-04-01

    The three year programme 1997-1999 for the OECD Halden Reactor Project (HRP) identifies the need to gain experience from applying formal techniques in real-life system developments. This motivated the initiation of the HRP research activity Integration of Formal Specification in the Development of HAMMLAB 2000 (INT-FS). The principal objective was to experiment with formal techniques in system developments at the HRP; in particular, system developments connected to HAMMLAB 2000 - the computerised laboratory for man-machine-interaction experiments currently under construction. It was hoped that this experimentation with formal techniques should result in a better understanding of how such techniques should be utilised in a more industrial setting. To obtain more knowledge with respect to the practical effects and consequences of an increased level of formalization was another objective. This report summarises experiences, results and conclusions from a pre-study addressing INT-FS related issues connected to the development of the HAMMLAB 2000 Integration Platform (IP). The report starts by giving a brief overview of the IP. Then it describes and summarises experiences from the formalization of a top-level requirements specification for the IP. Finally, it discusses various approaches for the integration of applications generated automatically through the CASE-tool SDT and the Software Bus on which the communication within HAMMLAB 2000 will be based. The report concludes that the selected formalisms and tools are well-suited to describe IP-like systems. The report also concludes that the integration of SDT applications with the Software Bus will not be a major obstacle, and finally that a monitoring component for the IP is well-suited for development within INT-FS (author) (ml)

  9. Evaluation of Dosimetry Check software for IMRT patient-specific quality assurance.

    Narayanasamy, Ganesh; Zalman, Travis; Ha, Chul S; Papanikolaou, Niko; Stathakis, Sotirios

    2015-05-08

    The purpose of this study is to evaluate the use of the Dosimetry Check system for patient-specific IMRT QA. Typical QA methods measure the dose in an array dosimeter surrounded by homogenous medium for which the treatment plan has been recomputed. With the Dosimetry Check system, fluence measurements acquired on a portal dosimeter is applied to the patient's CT scans. Instead of making dose comparisons in a plane, Dosimetry Check system produces isodose lines and dose-volume histograms based on the planning CT images. By exporting the dose distribution from the treatment planning system into the Dosimetry Check system, one is able to make a direct comparison between the calculated dose and the planned dose. The versatility of the software is evaluated with respect to the two IMRT techniques - step and shoot and volumetric arc therapy. The system analyzed measurements made using EPID, PTW seven29, and IBA MatriXX, and an intercomparison study was performed. Plans from patients previously treated at our institution with treated anatomical site on brain, head & neck, liver, lung, and prostate were analyzed using Dosimetry Check system for any anatomical site dependence. We have recommendations and possible precautions that may be necessary to ensure proper QA with the Dosimetry Check system.

  10. Specification and Generation of Environment for Model Checking of Software Components

    Pařízek, P.; Plášil, František

    2007-01-01

    Roč. 176, - (2007), s. 143-154 ISSN 1571-0661 R&D Projects: GA AV ČR 1ET400300504 Institutional research plan: CEZ:AV0Z10300504 Keywords : software components * behavior protocols * model checking * automated generation of environment Subject RIV: JC - Computer Hardware ; Software

  11. Understanding the technical content of requirements in specification document

    Sudin, Mohd Nizam Bin; Ahmed-Kristensen, Saeema

    2011-01-01

    development process, is essential to be devised in advance. To achieve this aim, understanding how to formulate a good requirement is necessary and it is only possible if design engineers understand the technical content of a requirement. In aiming to understand the technical content of a requirement...

  12. Expected requirements in support tool for software process improvement in SMEs

    Muñoz Mata, Mirna; Mejía Miranda, Jezreel; Amescua Seco, Antonio; Calvo-Manzano Villalón, José Antonio; Cuevas Agustín, Gonzalo; San Feliu Gilabert, Tomás

    2012-01-01

    Nowadays being competitive is an important challenge for software development organizations. In order to achieve this, since last years, software process improvement has been an obvious and logical way. Unfortunately, even when many organizations are motivated to implement software process initiatives, not all know how best to do so, especially in Small and Medium Enterprises (SMEs) where due to its especial features, they have to be carefully in how to manage its resources to assure their ma...

  13. Supporting Early Math--Rationales and Requirements for High Quality Software

    Haake, Magnus; Husain, Layla; Gulz, Agneta

    2015-01-01

    There is substantial evidence that preschooler's performance in early math is highly correlated to math performance throughout school as well as academic skills in general. One way to help children attain early math skills is by using targeted educational software and the paper discusses potential gains of using such software to support early math…

  14. 49 CFR 178.35 - General requirements for specification cylinders.

    2010-10-01

    ... of part 107 of this chapter; or (2) For DOT Specifications 3B, 3BN, 3E, 4B, 4BA, 4D (water capacity...) The word “spun” or “plug” must be placed near the DOT specification marking when an end closure in the... certifies that the processes of manufacture and heat treatment of cylinders were observed and found...

  15. Software to support planning for future waste treatment, storage, transport, and disposal requirements

    Holter, G.M.; Shay, M.R.; Stiles, D.L.

    1990-04-01

    Planning for adequate and appropriate treatment, storage, transport and disposal of wastes to be generated or received in the future is a complex but critical task that can be significantly enhanced by the development and use of appropriate software. This paper describes a software system that has been developed at Pacific Northwest Laboratory to aid in such planning. The basic needs for such a system are outlined, and the approach adopted in developing the software is described. The individual components of the system, and their integration into a unified system, are discussed. Typical analytical applications of this type of software are summarized. Conclusions concerning the development of such software systems and the necessary supporting data are then presented. 2 figs

  16. Disposal of Radioactive Waste. Specific Safety Requirements (Spanish Edition)

    2012-01-01

    This Safety Requirements publication applies to the disposal of radioactive waste of all types by means of emplacement in designed disposal facilities, subject to the necessary limitations and controls being placed on the disposal of the waste and on the development, operation and closure of facilities. The classification of radioactive waste is discussed. This Safety Requirements publication establishes requirements to provide assurance of the radiation safety of the disposal of radioactive waste, in the operation of a disposal facility and especially after its closure. The fundamental safety objective is to protect people and the environment from harmful effects of ionizing radiation. This is achieved by setting requirements on the site selection and evaluation and design of a disposal facility, and on its construction, operation and closure, including organizational and regulatory requirements.

  17. Safety of Research Reactors. Specific Safety Requirements (French Edition)

    2017-01-01

    This Safety Requirements publication establishes requirements for all main areas of safety for research reactors, with particular emphasis on requirements for design and operation. It explains the safety objectives and concepts that form the basis for safety and safety assessment for all stages in the lifetime of a research reactor. Technical and administrative requirements for the safety of new research reactors are established in accordance with these objectives and concepts, and they are to be applied to the extent practicable for existing research reactors. The safety requirements established in this publication for the management of safety and regulatory supervision apply to site evaluation, design, manufacturing, construction, commissioning, operation (including utilization and modification), and planning for decommissioning of research reactors (including critical assemblies and subcritical assemblies). The publication is intended for use by regulatory bodies and other organizations with responsibilities in these areas and in safety analysis, verification and review, and the provision of technical support.

  18. Input data required for specific performance assessment codes

    Seitz, R.R.; Garcia, R.S.; Starmer, R.J.; Dicke, C.A.; Leonard, P.R.; Maheras, S.J.; Rood, A.S.; Smith, R.W.

    1992-02-01

    The Department of Energy's National Low-Level Waste Management Program at the Idaho National Engineering Laboratory generated this report on input data requirements for computer codes to assist States and compacts in their performance assessments. This report gives generators, developers, operators, and users some guidelines on what input data is required to satisfy 22 common performance assessment codes. Each of the codes is summarized and a matrix table is provided to allow comparison of the various input required by the codes. This report does not determine or recommend which codes are preferable

  19. Adaptive software synthesis from extended dataflow specifications = Síntese de Software Adaptativo baseada em Especificações Extended Dataflow

    Ivanilton Polato

    2005-07-01

    Full Text Available Embedded software development approaches used models of computationsuch as dataflow, discrete events, synchronous/reactive, among others. Due to the specialization of the existing models, each one can be better applied to a specific application domain. Nevertheless, when there is no solution for applications in a specific domain,heterogeneous models have been used. In this context, this paper discusses a heterogeneous model called Extended Dataflow. It is an extension of the dataflow model with support to event handling. This paper also addresses how software can be synthesized from extendeddataflow specifications and discusses the development of a code generation tool prototype. This takes into account the possibility of component reuse for developing digital signal processing applications. A case study of adaptative applications using digital filters is used to illustrate our approach.As abordagens de desenvolvimento de software embutido têm feito o uso de modelos de computação, tais como fluxo de dados, eventos discretos, síncrono/reativo, dentre outros. A especialização desses modelos faz com que sejam apropriados a um domínio específico de aplicações. Entretanto, quando não existe uma solução adequada paradeterminada aplicação, os modelos heterogêneos têm sido utilizados. Neste contexto, este artigo discute um modelo heterogêneo, chamado Extended Dataflow, que é uma extensão do modelo de fluxo de dados com suporte ao tratamento de eventos. O artigo mostra ainda como um software pode ser obtido a partir de especificações usando Extended Dataflow e discute o desenvolvimento de um protótipo de ferramenta de geração de código. Isso leva em consideração a possibilidade de reuso de componentes em aplicações de processamento digital de sinais. Um estudo de caso sobre aplicações adaptativas envolvendo filtros digitais é utilizado para ilustrar o trabalho.

  20. Strengthening requirement specification in sustainable procurement - an investigation of challenges

    Eriksen, Marlene Stenberg Hagen; Bjarløv, Søren Peter; Rode, Carsten

    2017-01-01

    To reap the benefits of sustainability in the construction sector, it is crucial that the stakeholders involved can implement it in practice. Investigations have shown that choices made in the early phases of the building process are of very great importance for the outcome and the initiatives...... and decisions taken by the building owner are crucial.This paper presents research on Danish building practitioners' ability to make requirements for sustainability in procurement. On the basis of an action research strategy, we asked practitioners to help identify the challenges involved in requiring...

  1. 30 CFR 23.7 - Specific requirements for approval.

    2010-07-01

    ... adequate instructions for the installation and connection of telephones and signal devices in order that the safety of these devices and other circuits shall not be diminished by improper installation. MSHA reserves the right to require the attachment of wiring diagrams to the cases of telephones and signal...

  2. Risk-Based Confidentiality Requirements Specification for Outsourced IT Systems

    Morali, A.; Wieringa, Roelf J.

    Today, companies are required to be in control of their IT assets, and to provide proof of this in the form of independent IT audit reports. However, many companies have outsourced various parts of their IT systems to other companies, which potentially threatens the control they have of their IT

  3. Practical Relevance of Experiments in Comprehensibility of Requirements Specifications

    Condori-Fernandez, Nelly; Daneva, Maia; Sikkel, Nicolaas; Herrmann, Andrea

    2011-01-01

    Recently, the Requirements Engineering (RE) community has become increasingly aware of the importance of carrying out industry-relevant research. Researchers and practitioners should be able to evaluate the relevance of their empirical research to increase the likely adoption of RE methods in

  4. System requirements specification for waste information and control system

    Harris, R.R.

    1994-09-01

    This document defines the requirements for the Waste Information and Control System (WICS). The document defines the functions, constraints, and objectives that pertain to WICS. This shall serve as the baseline document to ensure the needs of the Hazardous Material Control group (HMC) at 222-S Laboratory are met with regard to assurance of accuracy and quality of data taken with WICS

  5. 40 CFR 35.3135 - Specific capitalization grant agreement requirements.

    2010-07-01

    ... received a capitalization grant and, if the deposit was expended, it was expended in accordance with title... after it receives the payment, the RA may withhold future quarterly grant payments, and require... procedures regarding the commitment or expenditure of revenues. (h) State accounting and auditing procedures...

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

    2011-03-25

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

  7. A Study on Quantitative Assessment of Design Specification of Reactor Protection System Software Using Bayesian Belief Networks

    Eom, H. S.; Kang, H. G.; Chang, S. C.; Park, G. Y.; Kwon, K. C.

    2007-02-01

    This report propose a method that can produce quantitative reliability of safety-critical software for PSA by making use of Bayesian Belief Networks (BBN). BBN has generally been used to model the uncertain system in many research fields. The proposed method was constructed by utilizing BBN that can combine the qualitative and the quantitative evidence relevant to the reliability of safety-critical software, and then can infer a conclusion in a formal and a quantitative way. A case study was also carried out with the proposed method to assess the quality of software design specification of safety-critical software that will be embedded in reactor protection system. The V and V results of the software were used as inputs for the BBN model. The calculation results of the BBN model showed that its conclusion is mostly equivalent to those of the V and V expert for a given input data set. The method and the results of the case study will be utilized in PSA of NPP. The method also can support the V and V expert's decision making process in controlling further V and V activities

  8. Evaluation of expert systems - An approach and case study. [of determining software functional requirements for command management of satellites

    Liebowitz, J.

    1985-01-01

    Techniques that were applied in defining an expert system prototype for first-cut evaluations of the software functional requirements of NASA satellite command management activities are described. The prototype was developed using the Knowledge Engineering System. Criteria were selected for evaluating the satellite software before defining the expert system prototype. Application of the prototype system is illustrated in terms of the evaluation procedures used with the COBE satellite to be launched in 1988. The limited number of options which can be considered by the program mandates that biases in the system output must be well understood by the users.

  9. Light Duty Utility Arm Software Test Plan

    Kiebel, G.R.

    1995-01-01

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

  10. Fast index based algorithms and software for matching position specific scoring matrices

    Homann Robert

    2006-08-01

    Full Text Available Abstract Background In biological sequence analysis, position specific scoring matrices (PSSMs are widely used to represent sequence motifs in nucleotide as well as amino acid sequences. Searching with PSSMs in complete genomes or large sequence databases is a common, but computationally expensive task. Results We present a new non-heuristic algorithm, called ESAsearch, to efficiently find matches of PSSMs in large databases. Our approach preprocesses the search space, e.g., a complete genome or a set of protein sequences, and builds an enhanced suffix array that is stored on file. This allows the searching of a database with a PSSM in sublinear expected time. Since ESAsearch benefits from small alphabets, we present a variant operating on sequences recoded according to a reduced alphabet. We also address the problem of non-comparable PSSM-scores by developing a method which allows the efficient computation of a matrix similarity threshold for a PSSM, given an E-value or a p-value. Our method is based on dynamic programming and, in contrast to other methods, it employs lazy evaluation of the dynamic programming matrix. We evaluated algorithm ESAsearch with nucleotide PSSMs and with amino acid PSSMs. Compared to the best previous methods, ESAsearch shows speedups of a factor between 17 and 275 for nucleotide PSSMs, and speedups up to factor 1.8 for amino acid PSSMs. Comparisons with the most widely used programs even show speedups by a factor of at least 3.8. Alphabet reduction yields an additional speedup factor of 2 on amino acid sequences compared to results achieved with the 20 symbol standard alphabet. The lazy evaluation method is also much faster than previous methods, with speedups of a factor between 3 and 330. Conclusion Our analysis of ESAsearch reveals sublinear runtime in the expected case, and linear runtime in the worst case for sequences not shorter than |A MathType@MTEF@5@5@+=feaafiart1ev1aaatCvAUfKttLearuWrP9MDH5MBPbIqV92Aae

  11. Are patient specific meshes required for EIT head imaging?

    Jehl, Markus; Aristovich, Kirill; Faulkner, Mayo; Holder, David

    2016-06-01

    Head imaging with electrical impedance tomography (EIT) is usually done with time-differential measurements, to reduce time-invariant modelling errors. Previous research suggested that more accurate head models improved image quality, but no thorough analysis has been done on the required accuracy. We propose a novel pipeline for creation of precise head meshes from magnetic resonance imaging and computed tomography scans, which was applied to four different heads. Voltages were simulated on all four heads for perturbations of different magnitude, haemorrhage and ischaemia, in five different positions and for three levels of instrumentation noise. Statistical analysis showed that reconstructions on the correct mesh were on average 25% better than on the other meshes. However, the stroke detection rates were not improved. We conclude that a generic head mesh is sufficient for monitoring patients for secondary strokes following head trauma.

  12. Specification of advanced safety modeling requirements (Rev. 0)

    Fanning, T. H.; Tautges, T. J.

    2008-01-01

    The U.S. Department of Energy's Global Nuclear Energy Partnership has lead to renewed interest in liquid-metal-cooled fast reactors for the purpose of closing the nuclear fuel cycle and making more efficient use of future repository capacity. However, the U.S. has not designed or constructed a fast reactor in nearly 30 years. Accurate, high-fidelity, whole-plant dynamics safety simulations will play a crucial role by providing confidence that component and system designs will satisfy established design limits and safety margins under a wide variety of operational, design basis, and beyond design basis transient conditions. Current modeling capabilities for fast reactor safety analyses have resulted from several hundred person-years of code development effort supported by experimental validation. The broad spectrum of mechanistic and phenomenological models that have been developed represent an enormous amount of institutional knowledge that needs to be maintained. Complicating this, the existing code architectures for safety modeling evolved from programming practices of the 1970s. This has lead to monolithic applications with interdependent data models which require significant knowledge of the complexities of the entire code in order for each component to be maintained. In order to develop an advanced fast reactor safety modeling capability, the limitations of the existing code architecture must be overcome while preserving the capabilities that already exist. To accomplish this, a set of advanced safety modeling requirements is defined, based on modern programming practices, that focuses on modular development within a flexible coupling framework. An approach for integrating the existing capabilities of the SAS4A/SASSYS-1 fast reactor safety analysis code into the SHARP framework is provided in order to preserve existing capabilities while providing a smooth transition to advanced modeling capabilities. In doing this, the advanced fast reactor safety models will

  13. Executable Behavioral Modeling of System and Software Architecture Specifications to Inform Resourcing Decisions

    2016-09-01

    Infrastructure software projects: 1. The earliest phases or spiral cycles will generally involve prototyping, using the Application Composition model...case needs to achieve, expected results, post conditions, information about the environment, infrastructure to support execution of the tests, and...Leanpub, Feb. 5, 2016. [Online]. Available: http:// microservices -book.com/. Accessed Aug. 20, 2016. [59] M. Farah-Stapleton, M. Auguston, R. Madachy

  14. A Data Specification for Software Project Performance Measures: Results of a Collaboration on Performance Measurement

    2008-07-01

    cycle Evolution of a system, product, service, project or other human-made entity from conception through retirement [ ISO 12207 ]. Logical line of...012 [ ISO 1995] International Organization for Standardization. ISO /IEC 12207 :1995—Information technology— Software life cycle processes. http...definitions, authors were asked to use or align with already existing standards such as those available through ISO and IEEE when possible. Literature

  15. Specification Improvement Through Analysis of Proof Structure (SITAPS): High Assurance Software Development

    2016-02-01

    proof in mathematics. For example, consider the proof of the Pythagorean Theorem illustrated at: http://www.cut-the-knot.org/ pythagoras / where 112...methods and tools have made significant progress in their ability to model software designs and prove correctness theorems about the systems modeled...assumption criticality” or “ theorem root set size” SITAPS detects potentially brittle verification cases. SITAPS provides tools and techniques that

  16. Specification, Synthesis, and Verification of Software-based Control Protocols for Fault-Tolerant Space Systems

    2016-08-16

    rights or permission to manufacture, use, or sell any patented invention that may relate to them. This report is the result of contracted...ASSUMPTIONS, AND PROCEDURES Despite the relatively unique and emerging complications in the control software for space systems, their design often...the satisfaction of logical proposition . Furthermore, suitable transitions must be defined between the discrete states such that they properly capture

  17. Solid construction waste management in large civil construction companies through use of specific software - case study

    Caio Dalla Zanna; Fernando Fernandes; José Carlos Gasparine

    2017-01-01

    In the current construction market there is a high demand for sustainability. In addition to that the Brazilian government is enacting tougher and tougher legislation on the disposal of solid construction waste. These demands increasingly make the construction company responsible for the entire lifecycle of its waste as well as the accompanying cost and environmental impact of solid waste. A software program was used in the research which allows construction companies gather information about...

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

    1989-10-01

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

  19. Solid construction waste management in large civil construction companies through use of specific software - case study

    Caio Dalla Zanna

    2017-05-01

    Full Text Available In the current construction market there is a high demand for sustainability. In addition to that the Brazilian government is enacting tougher and tougher legislation on the disposal of solid construction waste. These demands increasingly make the construction company responsible for the entire lifecycle of its waste as well as the accompanying cost and environmental impact of solid waste. A software program was used in the research which allows construction companies gather information about waste. This helps the decision makers, at all different levels of the company improving waste management through better decisions. The software program was used during the construction of two residential buildings, constructed by a large construction company in the South of Brazil. Five key performance indicators were used by the construction company team: Generated Waste Height (cm, cost per built area (R$ m-², Waste Segregation Quality Index (WSQI, Effective Waste Management Index (EWMI and Waste Management Quality Index (WMQI. After four months the total cost of waste management was R$ 83,551.71 for site A and R$ 91,668.02 for site B. About 70% of the waste was raw material waste. The software program provided information not previously available, which made it possible to calculate the cost of material loss, indicating corrective actions, all without losing sight of cost reduction opportunities for the management of Solid construction Waste (SCW.

  20. Specification of advanced safety modeling requirements (Rev. 0).

    Fanning, T. H.; Tautges, T. J.

    2008-06-30

    The U.S. Department of Energy's Global Nuclear Energy Partnership has lead to renewed interest in liquid-metal-cooled fast reactors for the purpose of closing the nuclear fuel cycle and making more efficient use of future repository capacity. However, the U.S. has not designed or constructed a fast reactor in nearly 30 years. Accurate, high-fidelity, whole-plant dynamics safety simulations will play a crucial role by providing confidence that component and system designs will satisfy established design limits and safety margins under a wide variety of operational, design basis, and beyond design basis transient conditions. Current modeling capabilities for fast reactor safety analyses have resulted from several hundred person-years of code development effort supported by experimental validation. The broad spectrum of mechanistic and phenomenological models that have been developed represent an enormous amount of institutional knowledge that needs to be maintained. Complicating this, the existing code architectures for safety modeling evolved from programming practices of the 1970s. This has lead to monolithic applications with interdependent data models which require significant knowledge of the complexities of the entire code in order for each component to be maintained. In order to develop an advanced fast reactor safety modeling capability, the limitations of the existing code architecture must be overcome while preserving the capabilities that already exist. To accomplish this, a set of advanced safety modeling requirements is defined, based on modern programming practices, that focuses on modular development within a flexible coupling framework. An approach for integrating the existing capabilities of the SAS4A/SASSYS-1 fast reactor safety analysis code into the SHARP framework is provided in order to preserve existing capabilities while providing a smooth transition to advanced modeling capabilities. In doing this, the advanced fast reactor safety models

  1. Adding Timing Requirements to the CODARTS Real-Time Software Design Method

    Bach, K.R.

    The CODARTS software design method consideres how concurrent, distributed and real-time applications can be designed. Although accounting for the important issues of task and communication, the method does not provide means for expressing the timeliness of the tasks and communication directly...

  2. Asymmetric cell division requires specific mechanisms for adjusting global transcription.

    Mena, Adriana; Medina, Daniel A; García-Martínez, José; Begley, Victoria; Singh, Abhyudai; Chávez, Sebastián; Muñoz-Centeno, Mari C; Pérez-Ortín, José E

    2017-12-01

    Most cells divide symmetrically into two approximately identical cells. There are many examples, however, of asymmetric cell division that can generate sibling cell size differences. Whereas physical asymmetric division mechanisms and cell fate consequences have been investigated, the specific problem caused by asymmetric division at the transcription level has not yet been addressed. In symmetrically dividing cells the nascent transcription rate increases in parallel to cell volume to compensate it by keeping the actual mRNA synthesis rate constant. This cannot apply to the yeast Saccharomyces cerevisiae, where this mechanism would provoke a never-ending increasing mRNA synthesis rate in smaller daughter cells. We show here that, contrarily to other eukaryotes with symmetric division, budding yeast keeps the nascent transcription rates of its RNA polymerases constant and increases mRNA stability. This control on RNA pol II-dependent transcription rate is obtained by controlling the cellular concentration of this enzyme. © The Author(s) 2017. Published by Oxford University Press on behalf of Nucleic Acids Research.

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

    Tomasz  Grasza

    2014-06-01

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

  4. Harmonized Constraints in Software Engineering and Acquisition Process Management Requirements are the Clue to Meet Future Performance Goals Successfully in an Environment of Scarce Resources

    Reich, Holger

    2008-01-01

    This MBA project investigates the importance of correctly deriving requirements from the capability gap and operational environment, and translating them into the processes of contracting, software...

  5. SREM (Software Requirements Engineering Methodology) Evaluation. Volume 2. Specifications and Technical Data.

    1984-02-01

    NEII 0 ’~, 1 m3 f’ESCw IflT(T 0’: h TNFUO MA To) rUNCFRJ.IM(x A FFA ’IALF TAQ6L, T". FNTtO0 l,4#-YY "o ’ARTM.(Am. rPAh,;F: "SuI.AOT,90?TH". 15F; : JCTH...DATAS ’)*’I Q.NELS-E’I SSIO: ISTAWTI4INt4E#DA TA DATA: De19-IL&mqIN*SAT.IE-)T FILE: F.1 b.NELS4ITTEP*.FIt.E. notruNEENTED SYS SOURCE: ASE* bPP ..6424i...0R,.FLASTI3LE,.ACTT viIVI4RFA*FILF IDRFAL is D4l ŗ*X*LfiC.. FFAS 12LE*VATA iFOR EACH F*19Q JELSFPE’IUFNrYb5CAN4.FILE Rfnk 10 bF6rN 0,O924NL#FHFWSCAWP

  6. Software requirements specifications of a proposed plant property management information system for the Naval Postgraduate School

    Carter, James B.

    1982-01-01

    Approved for Public Release; Distribution Unlimited The current system used to administer Plant Account equipment for academic departments at the Naval Postgraduate School involves four categories of system users and accountability for more than 2000 individual equipment items worth over seven million dollars. Implementation of a management information system (MIS) to support Plant Account equipment related functions could eliminate data handling redundancy and improve Pl...

  7. Requirements Analysis Study for Master Pump Shutdown System Project Development Specification [SEC 1 and 2

    BEVINS, R.R.

    2000-01-01

    This document has been updated during the definitive design portion of the first phase of the W-314 Project to capture additional software requirements and is planned to be updated during the second phase of the W-314 Project to cover the second phase of the Project's scope. The objective is to provide requirement traceability by recording the analysis/basis for the functional descriptions of the master pump shutdown system. This document identifies the sources of the requirements and/or how these were derived. Each requirement is validated either by quoting the source or an analysis process involving the required functionality, performance characteristics, operations input or engineering judgment

  8. Environmental Molecular Sciences Laboratory Operations System: Version 4.0 - system requirements specification

    Kashporenko, D.

    1996-07-01

    This document is intended to provide an operations standard for the Environmental Molecular Sciences Laboratory OPerations System (EMSL OPS). It is directed toward three primary audiences: (1) Environmental Molecular Sciences Laboratory (EMSL) facility and operations personnel; (2) laboratory line managers and staff; and (3) researchers, equipment operators, and laboratory users. It is also a statement of system requirements for software developers of EMSL OPS. The need for a finely tuned, superior research environment as provided by the US Department of Energy`s (DOE) Environmental Molecular Sciences Laboratory has never been greater. The abrupt end of the Cold War and the realignment of national priorities caused major US and competing overseas laboratories to reposition themselves in a highly competitive research marketplace. For a new laboratory such as the EMSL, this means coming into existence in a rapidly changing external environment. For any major laboratory, these changes create funding uncertainties and increasing global competition along with concomitant demands for higher standards of research product quality and innovation. While more laboratories are chasing fewer funding dollars, research ideas and proposals, especially for molecular-level research in the materials and biological sciences, are burgeoning. In such an economically constrained atmosphere, reduced costs, improved productivity, and strategic research project portfolio building become essential to establish and maintain any distinct competitive advantage. For EMSL, this environment and these demands require clear operational objectives, specific goals, and a well-crafted strategy. Specific goals will evolve and change with the evolution of the nature and definition of DOE`s environmental research needs. Hence, EMSL OPS is designed to facilitate migration of these changes with ease into every pertinent job function, creating a facile {open_quotes}learning organization.{close_quotes}

  9. Comparison of the Safety Critical Software V and V Requirements for the Research Reactor Instrumentation and Control System

    Joo, Sungmoon; Suh, Yong-Suk; Park, Cheol [Korea Atomic Energy Research Institute, Daejeon (Korea, Republic of)

    2016-10-15

    This study was motivated by a research reactor project where the owner of the project and the equipment vendors are from two different standards frameworks. This paper reviews two major standards frameworks - NRC-IEEE and IAEA-IEC - and the software classification schemes as a background, then discuss the V and V issue. The purpose of this paper is by no means to solve the cross-standards-framework qualification issue, but, rather, is to remind the stakeholders of research reactor projects. V and V are also essential for the approval from regulatory bodies. As standards define or recommend consolidated engineering practices, methods, or criteria, V and V activities for software qualification are not exceptional. Within a standards framework, usually, the processes for the qualification of safety-critical software are well-established such that the safety is maximized while minimizing the compromises in software quality, safety, and reliability. When, however, multiple standards frameworks are involved in a research reactor project, it is difficult for equipment vendors to implement appropriate V and V activities as there is no unified view on this cross-standards-framework qualification issue yet. There are two major standards frameworks for safety-critical software development in nuclear industry. Unfortunately different safety classifications for software and thus different requirements for qualification are in place. What makes things worse is that (i) there are ambiguities in the standards and rooms for each stakeholders’ interpretation, and (ii) there is no one-to-one mapping between the associated V and V methods and activities. These may put the stakeholders of research reactor projects in trouble.

  10. Comparison of the Safety Critical Software V and V Requirements for the Research Reactor Instrumentation and Control System

    Joo, Sungmoon; Suh, Yong-Suk; Park, Cheol

    2016-01-01

    This study was motivated by a research reactor project where the owner of the project and the equipment vendors are from two different standards frameworks. This paper reviews two major standards frameworks - NRC-IEEE and IAEA-IEC - and the software classification schemes as a background, then discuss the V and V issue. The purpose of this paper is by no means to solve the cross-standards-framework qualification issue, but, rather, is to remind the stakeholders of research reactor projects. V and V are also essential for the approval from regulatory bodies. As standards define or recommend consolidated engineering practices, methods, or criteria, V and V activities for software qualification are not exceptional. Within a standards framework, usually, the processes for the qualification of safety-critical software are well-established such that the safety is maximized while minimizing the compromises in software quality, safety, and reliability. When, however, multiple standards frameworks are involved in a research reactor project, it is difficult for equipment vendors to implement appropriate V and V activities as there is no unified view on this cross-standards-framework qualification issue yet. There are two major standards frameworks for safety-critical software development in nuclear industry. Unfortunately different safety classifications for software and thus different requirements for qualification are in place. What makes things worse is that (i) there are ambiguities in the standards and rooms for each stakeholders’ interpretation, and (ii) there is no one-to-one mapping between the associated V and V methods and activities. These may put the stakeholders of research reactor projects in trouble

  11. Robust design requirements specification: a quantitative method for requirements development using quality loss functions

    Pedersen, Søren Nygaard; Christensen, Martin Ebro; Howard, Thomas J.

    2016-01-01

    Product requirements serve many purposes in the product development process. Most importantly, they are meant to capture and facilitate product goals and acceptance criteria, as defined by stakeholders. Accurately communicating stakeholder goals and acceptance criteria can be challenging and more...

  12. Considerations for control system software verification and validation specific to implementations using distributed processor architectures

    Munro, J.K. Jr.

    1993-01-01

    Until recently, digital control systems have been implemented on centralized processing systems to function in one of several ways: (1) as a single processor control system; (2) as a supervisor at the top of a hierarchical network of multiple processors; or (3) in a client-server mode. Each of these architectures uses a very different set of communication protocols. The latter two architectures also belong to the category of distributed control systems. Distributed control systems can have a central focus, as in the cases just cited, or be quite decentralized in a loosely coupled, shared responsibility arrangement. This last architecture is analogous to autonomous hosts on a local area network. Each of the architectures identified above will have a different set of architecture-associated issues to be addressed in the verification and validation activities during software development. This paper summarizes results of efforts to identify, describe, contrast, and compare these issues

  13. The definitive analysis of the Bendandi's methodology performed with a specific software

    Ballabene, Adriano; Pescerelli Lagorio, Paola; Georgiadis, Teodoro

    2015-04-01

    The presentation aims to clarify the "Method Bendandi" supposed, in the past, to be able to forecast earthquakes and never let expressly resolved by the geophysicist from Faenza to posterity. The geoethics implications of the Bendandi's forecasts, and those that arise around the speculation of possible earthquakes inferred from suppositories "Bendandiane" methodologies, rose up in previous years caused by social alarms during supposed occurrences of earthquakes which never happened but where widely spread by media following some 'well informed' non conventional scientists. The analysis was conducted through an extensive literature search of the archive 'Raffaele Bendandi' at Geophy sical Observatory of Faenza and the forecasts analyzed utilising a specially developed software, called "Bendandiano Dashboard", that can reproduce the planetary configurations reported in the graphs made by Italian geophysicist. This analysis should serve to clarify 'definitively' what are the basis of the Bendandi's calculations as well as to prevent future unwarranted warnings issued on the basis of supposed prophecies and illusory legacy documents.

  14. RELAP-7 Software Verification and Validation Plan - Requirements Traceability Matrix (RTM) Part 2: Code Assessment Strategy, Procedure, and RTM Update

    Yoo, Jun Soo [Idaho National Lab. (INL), Idaho Falls, ID (United States); Choi, Yong Joon [Idaho National Lab. (INL), Idaho Falls, ID (United States); Smith, Curtis Lee [Idaho National Lab. (INL), Idaho Falls, ID (United States)

    2016-09-01

    This document addresses two subjects involved with the RELAP-7 Software Verification and Validation Plan (SVVP): (i) the principles and plan to assure the independence of RELAP-7 assessment through the code development process, and (ii) the work performed to establish the RELAP-7 assessment plan, i.e., the assessment strategy, literature review, and identification of RELAP-7 requirements. Then, the Requirements Traceability Matrices (RTMs) proposed in previous document (INL-EXT-15-36684) are updated. These RTMs provide an efficient way to evaluate the RELAP-7 development status as well as the maturity of RELAP-7 assessment through the development process.

  15. SecureCore Software Architecture: Trusted Management Layer (TML) Kernel Extension Module Interface Specification

    Shifflett, David J; Clark, Paul C; Irvine, Cynthia E; Nguyen, Thuy D; Vidas, Timothy M; Levin, Timothy E

    2008-01-01

    .... The purpose of the SecureCore research project is to investigate fundamental architectural features required for the trusted operation of mobile computing devices such as smart cards, embedded...

  16. 40 CFR 166.32 - Reporting and recordkeeping requirements for specific, quarantine, and public health exemptions.

    2010-07-01

    ... requirements for specific, quarantine, and public health exemptions. 166.32 Section 166.32 Protection of... AGENCIES FOR USE OF PESTICIDES UNDER EMERGENCY CONDITIONS Specific, Quarantine, and Public Health Exemptions § 166.32 Reporting and recordkeeping requirements for specific, quarantine, and public health...

  17. Computer-Aided Discovery of Formal Specification Behavioral Requirements and Requirement to Implementation Mappings

    2014-01-01

    the executable SRM is developed according to the specification and marketing documents. Hence, for example, the Vehicles, Car, and Truck classes in...transitions ternary relation: transitions ⊆ states x transitionIDs x states, such as <"Init", "Tr1", " stP "> • A conditions unary relation bound to

  18. CH2M Hill Hanford Group, Inc., Standards and Requirements Identification Document (SRID) Requirements Management System and Requirements Specification

    JOHNSON, A.L.

    2000-01-01

    The current Tank Farm Contractor (TFC) for the U. S. Department of Energy, Office of River Protection (ORP), River Protection Project (RPP), CH2M Hill Hanford Group, Inc. (CHG), will use a computer based requirements management system. The system will serve as a tool to assist in identifying, capturing, and maintaining the Standards/Requirements Identification Document (S/RID) requirements and links to implementing procedures and other documents. By managing requirements as one integrated set, CHG will be able to carry out its mission more efficiently and effectively. CHG has chosen the Dynamic Object Oriented Requirements System (DOORS(trademark)) as the preferred computer based requirements management system. Accordingly, the S/RID program will use DOORS(trademark). DOORS(trademark) will replace the Environmental Requirements Management Interface (ERMI) system as the tool for S/RID data management. The DOORS(trademark) S/RID test project currently resides on the DOORSTM test server. The S/RID project will be migrated to the DOORS(trademark) production server. After the migration the S/RID project will be considered a production project and will no longer reside on the test server

  19. Identification of RNA molecules by specific enzyme digestion and mass spectrometry: software for and implementation of RNA mass mapping

    Matthiesen, Rune; Kirpekar, Finn

    2009-01-01

    The idea of identifying or characterizing an RNA molecule based on a mass spectrum of specifically generated RNA fragments has been used in various forms for well over a decade. We have developed software-named RRM for 'RNA mass mapping'-which can search whole prokaryotic genomes or RNA FASTA...... sequence databases to identify the origin of a given RNA based on a mass spectrum of RNA fragments. As input, the program uses the masses of specific RNase cleavage of the RNA under investigation. RNase T1 digestion is used here as a demonstration of the usability of the method for RNA identification....... The concept for identification is that the masses of the digestion products constitute a specific fingerprint, which characterize the given RNA. The search algorithm is based on the same principles as those used in peptide mass fingerprinting, but has here been extended to work for both RNA sequence databases...

  20. Discrete Choice Experiments: A Guide to Model Specification, Estimation and Software.

    Lancsar, Emily; Fiebig, Denzil G; Hole, Arne Risa

    2017-07-01

    We provide a user guide on the analysis of data (including best-worst and best-best data) generated from discrete-choice experiments (DCEs), comprising a theoretical review of the main choice models followed by practical advice on estimation and post-estimation. We also provide a review of standard software. In providing this guide, we endeavour to not only provide guidance on choice modelling but to do so in a way that provides a 'way in' for researchers to the practicalities of data analysis. We argue that choice of modelling approach depends on the research questions, study design and constraints in terms of quality/quantity of data and that decisions made in relation to analysis of choice data are often interdependent rather than sequential. Given the core theory and estimation of choice models is common across settings, we expect the theoretical and practical content of this paper to be useful to researchers not only within but also beyond health economics.

  1. Handling requirements dependencies in agile projects: A focus group with agile software development practitioners

    Martakis, Aias; Daneva, Maia; Wieringa, Roelf J.; Jean-Louis Cavarero, S.; Rolland, C; Cavarero, J.L.

    2013-01-01

    Agile practices on requirements dependencies are a relatively unexplored topic in literature. Empirical studies on it are scarce. This research sets out to uncover concepts that practitioners in companies of various sizes across the globe and in various industries, use for dealing with requirements

  2. A software package for patient-specific dosimetry in the locoregional RIT of gliomas using 188Re labelled NIMOTUZUMAB

    Torres, L.A.; Coca, M.A.; Sanchez, Y.; Cornejo, N.; Catasus, C.; Denaro, M. de

    2008-01-01

    Full text: The locoregional treatment of high-grade gliomas using beta emitter compounds allows delivering high radiation doses in the tumor bed and the brain adjacent tissues of patients suffering these aggressive malignancies. The main goal of this work was to implement patient-specific dosimetry procedures using a voxel-based methodology in order to compute and analyze the three-dimensional doses distributions received by the patients undergoing loco-regional treatment of gliomas with the 188 Re labeled MAb NIMOTUZUMAB. A software package called TRIDOSE has been developed to perform the image managing, volume registration, dose calculations and qualitative and quantitative analysis of the results, including dose-volume histograms and isodose curves. The dosimetric factors at voxel level for 188 Re ('S' values) were estimated using two different methods, Monte Carlo simulations of energy transport and deposition and the integration of the dose kernel functions. A quality control module was also implemented in order to test the software using well-known 3D distribution of activities or counts. The TRIDOSE outputs were compared with other commercial software showing relative differences lower than 1.10% for different sphere sizes. The established dosimetric procedures constitute a useful tool to compute the absorbed doses received by patients undergoing radioimmunotherapy of brain tumors with 188 Re-NIMOTUZUMAB. (author)

  3. Behavioral data requirements for translating cognitive theories into computer software algorithms

    Meister, D.

    1992-01-01

    This paper reviews the characteristics of cognitive theories and their links to behavioral science and advanced intelligent systems. Cognitive theories model human cognition, perception, and communication. They suggest the human functions the system should have, serve as a philosophical basis for system development, and provide abstract design guidelines. The underlying assumption behind this paper is that if the cognitive theories are to have any value at all, they must be translated into usable systems. A process for testing a cognitive theory in terms of conceptual criteria, behavioral predictions and tests, and software development and tests, is suggested. Criteria for measuring the problem solving success of the advanced system are described. A theory of the system as an intelligent problem solver is presented. (author)

  4. Functions and Requirements and Specifications for Replacement of the Computer Automated Surveillance System (CASS)

    SCAIEF, C.C.

    1999-01-01

    This functions, requirements and specifications document defines the baseline requirements and criteria for the design, purchase, fabrication, construction, installation, and operation of the system to replace the Computer Automated Surveillance System (CASS) alarm monitoring

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

    2010-04-02

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

  6. Report on functional requirements and software architecture for the IDTO prototype : phase I demonstration site (Columbus).

    2013-08-01

    This report documents the System Requirements and Architecture for the Phase I implementation of the Integrated Dynamic : Transit Operations (IDTO) Prototype bundle within the Dynamic Mobility Applications (DMA) portion of the Connected Vehicle : Pro...

  7. Report on functional requirements and software architecture for the IDTO prototype phase 2 : central Florida demonstration.

    2015-05-01

    This report documents the System Requirements and Architecture for the Phase 2 implementation of the Integrated Dynamic : Transit Operations (IDTO) Prototype bundle within the Dynamic Mobility Applications (DMA) portion of the Connected Vehicle : Pro...

  8. Requirements Analysis Study for Master Pump Shutdown System Project Development Specification

    BEVINS, R.R.

    2000-01-01

    This study is a requirements document that presents analysis for the functional description for the master pump shutdown system. This document identifies the sources of the requirements and/or how these were derived. Each requirement is validated either by quoting the source or an analysis process involving the required functionality, performance characteristics, operations input or engineering judgment. The requirements in this study apply to the first phase of the W314 Project. This document has been updated during the definitive design portion of the first phase of the W314 Project to capture additional software requirements and is planned to be updated during the second phase of the W314 Project to cover the second phase of the project's scope

  9. Implementation of electronic medical records requires more than new software: Lessons on integrating and managing health technologies from Mbarara, Uganda.

    Madore, Amy; Rosenberg, Julie; Muyindike, Winnie R; Bangsberg, David R; Bwana, Mwebesa B; Martin, Jeffrey N; Kanyesigye, Michael; Weintraub, Rebecca

    2015-12-01

    Implementation lessons: • Technology alone does not necessarily lead to improvement in health service delivery, in contrast to the common assumption that advanced technology goes hand in hand with progress. • Implementation of electronic medical record (EMR) systems is a complex, resource-intensive process that, in addition to software, hardware, and human resource investments, requires careful planning, change management skills, adaptability, and continuous engagement of stakeholders. • Research requirements and goals must be balanced with service delivery needs when determining how much information is essential to collect and who should be interfacing with the EMR system. • EMR systems require ongoing monitoring and regular updates to ensure they are responsive to evolving clinical use cases and research questions. • High-quality data and analyses are essential for EMRs to deliver value to providers, researchers, and patients. Copyright © 2015 Elsevier Inc. All rights reserved.

  10. Software Radar Technology

    Tang Jun

    2015-08-01

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

  11. NASA software documentation standard software engineering program

    1991-01-01

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

  12. Information quality and quantity-based model to represent the appropriateness of software requirements elicitation techniques

    Luis Aguirre-Arredondo

    2017-01-01

    Full Text Available Para capturar información de las necesidades de los stakeholders y del dominio del problema, y luego conformar los requisitos del software a construir, los desarrolladores tienen a disposición una miríada de técnicas de educción, provenientes de diversas ciencias como las ciencias sociales o la sicología. Por su naturaleza, cada técnica tiene un desempeño diferente dependiendo del contexto en que aplica. Por lo tanto, para saber qué técnica de educción de requisitos es la más adecuada es necesario saber qué deberíamos entender por “técnica más adecuada”. Tanto desarrolladores como investigadores, y entre investigadores, tienen visiones diferentes de la bondad de las técnicas. Este trabajo propone un modelo para representar el constructo de adecuación de las técnicas de educción. Este modelo utiliza un estimador de adecuación, el cual se calcula a través de las variables de cantidad y calidad de requisitos. El modelo propuesto fue validado con datos de un experimento encontrado en la literatura. Este modelo pretende unificar el constructo de adecuación, lo que puede contribuir a uniformar futuros estudios empíricos y así, facilitar la conformación de un cuerpo de conocimientos sobre las técnicas de educción de requisitos.

  13. Software engineering methodologies and tools

    Wilcox, Lawrence M.

    1993-01-01

    Over the years many engineering disciplines have developed, including chemical, electronic, etc. Common to all engineering disciplines is the use of rigor, models, metrics, and predefined methodologies. Recently, a new engineering discipline has appeared on the scene, called software engineering. For over thirty years computer software has been developed and the track record has not been good. Software development projects often miss schedules, are over budget, do not give the user what is wanted, and produce defects. One estimate is there are one to three defects per 1000 lines of deployed code. More and more systems are requiring larger and more complex software for support. As this requirement grows, the software development problems grow exponentially. It is believed that software quality can be improved by applying engineering principles. Another compelling reason to bring the engineering disciplines to software development is productivity. It has been estimated that productivity of producing software has only increased one to two percent a year in the last thirty years. Ironically, the computer and its software have contributed significantly to the industry-wide productivity, but computer professionals have done a poor job of using the computer to do their job. Engineering disciplines and methodologies are now emerging supported by software tools that address the problems of software development. This paper addresses some of the current software engineering methodologies as a backdrop for the general evaluation of computer assisted software engineering (CASE) tools from actual installation of and experimentation with some specific tools.

  14. Electronic Health Record in Occupational Medicine: Specific Aspects and Requirements of Data Structuring and Standardization

    Dorin TRIFF

    2009-07-01

    Full Text Available The service of occupational medicine of a specific economic agent, as integrated part of the System of Labor Health and Safety, requires efficient, well-organized information management through standardized and computerized data processing and exploitation. Legal requirements and practical aspects of information management in occupational medicine trigger necessary operational modifications in the Electronic Health File. The goal of the paper is to present basic requirements of structuring the electronic health file and the necessary standards in recording specific data.

  15. SATISFACTION OF QUALIFICATION REQUIREMENTS OF EMPLOYERS APPLIED TO SOFTWARE ENGINEERS IN THE PROCESS OF TRAINING AT HIGHER EDUCATIONAL INSTITUTIONS

    Vladislav Kruhlyk

    2017-03-01

    Full Text Available In the article, based on the analysis of the problems of the professional training of software engineers in higher educational institutions, was shown that the contents of the curricula for the training of software engineers in basic IT specialties in higher education institutions generally meet the requirements to them at the labor market. It is stated that at the present time there are certain changes in the job market not only in the increasing demand for IT professionals but also in the requirements settled for future specialists. To scientists’ opinion, at present there is a gap between the level of expectation of employers and the level of education of graduates of IT-specialties of universities. Due to the extremely fast pace of IT development, already at the end of the studies, students' knowledge may become obsolete. We are talking about a complex of competencies offered by university during training of specialist for their relevance and competitiveness at the labor market. At the same time, the practical training of students does not fully correspond to the current state of information technology. Therefore, it is necessary to ensure the updating of the contents of the academic disciplines with the aim of providing quality training of specialists.

  16. An expert system prototype for aiding in the development of software functional requirements for NASA Goddard's command management system: A case study and lessons learned

    Liebowitz, Jay

    1986-01-01

    At NASA Goddard, the role of the command management system (CMS) is to transform general requests for spacecraft opeerations into detailed operational plans to be uplinked to the spacecraft. The CMS is part of the NASA Data System which entails the downlink of science and engineering data from NASA near-earth satellites to the user, and the uplink of command and control data to the spacecraft. Presently, it takes one to three years, with meetings once or twice a week, to determine functional requirements for CMS software design. As an alternative approach to the present technique of developing CMS software functional requirements, an expert system prototype was developed to aid in this function. Specifically, the knowledge base was formulated through interactions with domain experts, and was then linked to an existing expert system application generator called 'Knowledge Engineering System (Version 1.3).' Knowledge base development focused on four major steps: (1) develop the problem-oriented attribute hierachy; (2) determine the knowledge management approach; (3) encode the knowledge base; and (4) validate, test, certify, and evaluate the knowledge base and the expert system prototype as a whole. Backcasting was accomplished for validating and testing the expert system prototype. Knowledge refinement, evaluation, and implementation procedures of the expert system prototype were then transacted.

  17. 49 CFR 179.301 - Individual specification requirements for multi-unit tank car tanks.

    2010-10-01

    ...-unit tank car tanks. 179.301 Section 179.301 Transportation Other Regulations Relating to... MATERIALS REGULATIONS SPECIFICATIONS FOR TANK CARS Specifications for Multi-Unit Tank Car Tanks (Classes DOT-106A and 110AW) § 179.301 Individual specification requirements for multi-unit tank car tanks. (a) In...

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

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

  19. [Software as medical devices/medical apps : Tasks, requirements, and experiences from the point of view of a competent authority].

    Terhechte, Arno

    2018-03-01

    Software can be classified as a medical device according to the Medical Device Directive 93/42/EEC. The number of software products and medical apps is continuously increasing and so too is the use in health institutions (e. g., in hospitals and doctors' surgeries) for diagnosis and therapy.Different aspects of standalone software and medical apps from the perspective of the authority responsible are presented. The quality system implemented to establish a risk-based systematic inspection and supervision of manufacturers is discussed. The legal framework, as well as additional standards that are the basis for inspection, are outlined. The article highlights special aspects that occur during inspection like verification of software and interfaces, and the clinical evaluation of software. The Bezirksregierung, as the local government authority responsible in North Rhine-Westphalia, is also in charge of inspection of health institutions. Therefore this article is not limited to the manufacturers placing the software on the market, but in addition it describes the management and use of software as a medical device in hospitals.The future legal framework, the Medical Device Regulation, will strengthen the requirements and engage notified bodies more than today in the conformity assessment of software as a medical device.Manufacturers, health institutions, notified bodies and the authorities responsible are in charge of intensifying their efforts towards software as a medical device. Mutual information, improvement of skills, and inspections will lead to compliance with regulatory requirements.

  20. Certification of packagings: compliance with DOT specification 7A packaging requirements

    Edling, D.A.

    1976-01-01

    A study was conducted to determine which of the packagings currently listed in CFR 49 Section 173.395 a.1-5, meet the Specification 7A requirements (CFR 49 Section 173.350). According to DOT HM-111 the present listing of various authorized DOT specifications in Section 173.394 and Section 173.395 (Type A containers) of ICC Tariff No. 27 would be deleted with complete reliance being placed on the use of DOT 7A, Type A general packaging specification. Each user of a Specification 7A package would be required to document and maintain on file for one year a written record of his determination of compliance with the DOT Specification 7A performance requirements. All the specification packagings listed in CFR 49 Section 173.395a.1-5 were tested and shown to meet the Specification 7A criteria; however, in many cases qualifications were placed on their use. Forty-nine specification packagings were tested and shown to meet the DOT Specification 7A performance requirements and since there were several styles of some specific packagings, this amounts to greater than 80 packagings. The extensive testing generally indicated a high degree of containment integrity in the packagings tested and the documentation discussed is a valuable tool for shippers of Type A quantities of radioactive materials

  1. Software Prototyping

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

    2016-01-01

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

  2. The Mitochondrial Lon Protease Is Required for Age-Specific and Sex-Specific Adaptation to Oxidative Stress.

    Pomatto, Laura C D; Carney, Caroline; Shen, Brenda; Wong, Sarah; Halaszynski, Kelly; Salomon, Matthew P; Davies, Kelvin J A; Tower, John

    2017-01-09

    Multiple human diseases involving chronic oxidative stress show a significant sex bias, including neurodegenerative diseases, cancer, immune dysfunction, diabetes, and cardiovascular disease. However, a possible molecular mechanism for the sex bias in physiological adaptation to oxidative stress remains unclear. Here, we report that Drosophila melanogaster females but not males adapt to hydrogen peroxide stress, whereas males but not females adapt to paraquat (superoxide) stress. Stress adaptation in each sex requires the conserved mitochondrial Lon protease and is associated with sex-specific expression of Lon protein isoforms and proteolytic activity. Adaptation to oxidative stress is lost with age in both sexes. Transgenic expression of transformer gene during development transforms chromosomal males into pseudo-females and confers the female-specific pattern of Lon isoform expression, Lon proteolytic activity induction, and H 2 O 2 stress adaptation; these effects were also observed using adult-specific transformation. Conversely, knockdown of transformer in chromosomal females eliminates the female-specific Lon isoform expression, Lon proteolytic activity induction, and H 2 O 2 stress adaptation and produces the male-specific paraquat (superoxide) stress adaptation. Sex-specific expression of alternative Lon isoforms was also observed in mouse tissues. The results develop Drosophila melanogaster as a model for sex-specific stress adaptation regulated by the Lon protease, with potential implications for understanding sexual dimorphism in human disease. Copyright © 2017 Elsevier Ltd. All rights reserved.

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

    Campbell, Roy H.; Laliberte, D.; Render, H.; Sum, R.; Smith, W.; Terwilliger, R.

    1987-01-01

    The Software Automation, Generation and Administration (SAGA) project is investigating the design and construction of practical software engineering environments for developing and maintaining aerospace systems and applications software. The research includes the practical organization of the software lifecycle, configuration management, software requirements specifications, executable specifications, design methodologies, programming, verification, validation and testing, version control, maintenance, the reuse of software, software libraries, documentation, and automated management.

  4. Computer software.

    Rosenthal, L E

    1986-10-01

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

  5. Specific requirements of GS-R3 related to process implementation

    Florescu, N.

    2009-01-01

    The PowerPoint presentation gives: an overview of IAEA management system requirements or topics; - the requirements specific to processes and process implementation; - the key practical challenge of using the process approach specified in IAEA SG GS-G3.1 and GS-G3.5. The following items are thoroughly discussed: - Requirements related to specific process implementation and developing processes; - Process management; Generic management; - System processes: - Control of documents; Control of products; Control of records; - Purchasing; - Communication; - Managing organizational change; - Other requirements concerning the process management system; - General management system; - Grading; - Documentation; - Fulfilling the requirements of interested parties; - Management responsibility; - Planning responsibility and authority for the management system monitoring and measurement; - Independent assessment; - Management system review; - Non-conformances, corrective and preventive actions; - Improvement key practical challenge of using the process approach specified in IAEA SG GS-G3.1 and GS-G3.5; - Key challenge: - Process common to all stages; - Phases of process development proposed by IAEA. The following conclusions complete the presentation: GS-R-3 sets basic requirements for process-based integrated management system; - Some key generic processes required, no specific process model favoured namely, no reference to management, core and support processes; - Up to organization to determine appropriate process model; - Easily applicable to a wide range of facilities and activities, including those of a regulatory body; - Specific requirements are found in specific Safety Guide. (author)

  6. Software specification methods

    Habrias, Henri

    2010-01-01

    This title provides a clear overview of the main methods, and has a practical focus that allows the reader to apply their knowledge to real-life situations. The following are just some of the techniques covered: UML, Z, TLA+, SAZ, B, OMT, VHDL, Estelle, SDL and LOTOS.

  7. Specification of Behavioural Requirements within Compositional Multi-Agent System Design

    Herlea, D.E.; Jonker, C.M.; Treur, J.; Wijngaards, N.J.E.

    1999-01-01

    In this paper it is shown how informal and formal specification of behavioural requirements and scenarios for agents and multi-agent systems can be integrated within multi-agent system design. In particular, it is addressed how a compositional

  8. System requirement specifications for the Z-plant materials information tracking system (ZMITS)

    NEGIN, C.A.

    1999-01-01

    This is a system requirement specification for a database which will be developed to track classified information related to nuclear materials stored at PFP. The system will supplement existing databases to support both processing and disposition information needs

  9. Appraisal of work ability in relation to job-specific health requirements in ambulance workers

    van Schaaijk, A.; Boschman, J. S.; Frings-Dresen, M. H. W.; Sluiter, J. K.

    2016-01-01

    Purpose To gain insight into which job-specific health requirements relate to work ability, the following two research questions were formulated: Which job-specific health requirements are associated with the appraisal of work ability in ambulance drivers and paramedics? How are appraisals of physical and mental work ability associated with the appraisal of overall work ability in ambulance drivers and paramedics? Method Workers Health Surveillance cross-sectional data of 506 ambulance worker...

  10. Some remarks on software reliability

    Gonzalez Hernando, J.; Sanchez Izquierdo, J.

    1978-01-01

    Trend in modern NPPCI is toward a broad use of programmable elements. Some aspects concerning present status of programmable digital systems reliability are reported. Basic differences between software and hardware concept require a specific approach in all the reliability topics concerning software systems. The software reliability theory was initialy developed upon hardware models analogies. At present this approach is changing and specific models are being developed. The growing use of programmable systems necessitates emphasizing the importance of more adequate regulatory requirements to include this technology in NPPCI. (author)

  11. Patient-specific IMRT verification using independent fluence-based dose calculation software: experimental benchmarking and initial clinical experience

    Georg, Dietmar; Stock, Markus; Kroupa, Bernhard; Olofsson, Joergen; Nyholm, Tufve; Ahnesjoe, Anders; Karlsson, Mikael

    2007-01-01

    Experimental methods are commonly used for patient-specific intensity-modulated radiotherapy (IMRT) verification. The purpose of this study was to investigate the accuracy and performance of independent dose calculation software (denoted as 'MUV' (monitor unit verification)) for patient-specific quality assurance (QA). 52 patients receiving step-and-shoot IMRT were considered. IMRT plans were recalculated by the treatment planning systems (TPS) in a dedicated QA phantom, in which an experimental 1D and 2D verification (0.3 cm 3 ionization chamber; films) was performed. Additionally, an independent dose calculation was performed. The fluence-based algorithm of MUV accounts for collimator transmission, rounded leaf ends, tongue-and-groove effect, backscatter to the monitor chamber and scatter from the flattening filter. The dose calculation utilizes a pencil beam model based on a beam quality index. DICOM RT files from patient plans, exported from the TPS, were directly used as patient-specific input data in MUV. For composite IMRT plans, average deviations in the high dose region between ionization chamber measurements and point dose calculations performed with the TPS and MUV were 1.6 ± 1.2% and 0.5 ± 1.1% (1 S.D.). The dose deviations between MUV and TPS slightly depended on the distance from the isocentre position. For individual intensity-modulated beams (total 367), an average deviation of 1.1 ± 2.9% was determined between calculations performed with the TPS and with MUV, with maximum deviations up to 14%. However, absolute dose deviations were mostly less than 3 cGy. Based on the current results, we aim to apply a confidence limit of 3% (with respect to the prescribed dose) or 6 cGy for routine IMRT verification. For off-axis points at distances larger than 5 cm and for low dose regions, we consider 5% dose deviation or 10 cGy acceptable. The time needed for an independent calculation compares very favourably with the net time for an experimental approach

  12. 24 CFR 200.936 - Supplementary specific procedural requirements under HUD building products certification program...

    2010-04-01

    ... requirements under HUD building products certification program for solid fuel type room heaters and fireplace... Supplementary specific procedural requirements under HUD building products certification program for solid fuel... fireplace stoves certified under the HUD Building Products Certification Program shall be designed...

  13. 24 CFR 200.940 - Supplementary specific requirements under the HUD building product standards and certification...

    2010-04-01

    ... under the HUD building product standards and certification program for sealed insulating glass units... Supplementary specific requirements under the HUD building product standards and certification program for... specific building product certification program. In the case of sealed insulating glass units, testing and...

  14. 24 CFR 200.955 - Supplementary specific requirements under the HUD building product standard and certification...

    2010-04-01

    ... under the HUD building product standard and certification program for fenestration products (windows and... Supplementary specific requirements under the HUD building product standard and certification program for... testing for a product shall be described in the specific building product certification program. In the...

  15. 40 CFR 53.51 - Demonstration of compliance with design specifications and manufacturing and test requirements.

    2010-07-01

    ... Methods and Class I and Class II Equivalent Methods for PM2.5 or PM10â2.5 § 53.51 Demonstration of... standard specification 8625F, Type II, Class I (reference 4 in appendix A of this subpart) in the same way... specifications and manufacturing and test requirements. 53.51 Section 53.51 Protection of Environment...

  16. The graphics software of the Saclay Linear Accelerator control system

    Gournay, J.F.

    1988-01-01

    The graphics software used for the control of the Saclay Linear Accelerator is described. The specific requirements that such a software must have in this environment are outlined and some typical applications are presented. (orig.)

  17. Specification of requirements for the virtual environment for reactor applications simulation environment

    Hess, S. M.; Pytel, M.

    2012-01-01

    In 2010, the United States Dept. of Energy initiated a research and development effort to develop modern modeling and simulation methods that could utilize high performance computing capabilities to address issues important to nuclear power plant operation, safety and sustainability. To respond to this need, a consortium of national laboratories, academic institutions and industry partners (the Consortium for Advanced Simulation of Light Water Reactors - CASL) was formed to develop an integrated Virtual Environment for Reactor Applications (VERA) modeling and simulation capability. A critical element for the success of the CASL research and development effort was the development of an integrated set of overarching requirements that provides guidance in the planning, development, and management of the VERA modeling and simulation software. These requirements also provide a mechanism from which the needs of a broad array of external CASL stakeholders (e.g. reactor / fuel vendors, plant owner / operators, regulatory personnel, etc.) can be identified and integrated into the VERA development plans. This paper presents an overview of the initial set of requirements contained within the VERA Requirements Document (VRD) that currently is being used to govern development of the VERA software within the CASL program. The complex interdisciplinary nature of these requirements together with a multi-physics coupling approach to realize a core simulator capability pose a challenge to how the VRD should be derived and subsequently revised to accommodate the needs of different stakeholders. Thus, the VRD is viewed as an evolving document that will be updated periodically to reflect the changing needs of identified CASL stakeholders and lessons learned during the progress of the CASL modeling and simulation program. (authors)

  18. Online Rule Generation Software Process Model

    Sudeep Marwaha; Alka Aroa; Satma M C; Rajni Jain; R C Goyal

    2013-01-01

    For production systems like expert systems, a rule generation software can facilitate the faster deployment. The software process model for rule generation using decision tree classifier refers to the various steps required to be executed for the development of a web based software model for decision rule generation. The Royce’s final waterfall model has been used in this paper to explain the software development process. The paper presents the specific output of various steps of modified wat...

  19. Requirement Volatility, Standardization and Knowledge Integration in Software Projects: An Empirical Analysis on Outsourced IS Development Projects

    Rajesri Govindaraju

    2015-08-01

    Full Text Available Information systems development (ISD projects are highly complex, with different groups of people having  to collaborate and exchange their knowledge. Considering the intensity of knowledge exchange that takes place in outsourced ISD projects, in this study a conceptual model was developed, aiming to examine the influence of four antecedents, i.e. standardization, requirement volatility, internal integration, and external integration, on two dependent variables, i.e. process performance and product performance. Data  were collected from 46 software companies in four big cities in Indonesia. The collected data were examined to verify the proposed theoretical model using the partial least square structural equation modeling (PLS-SEM technique. The results show that process performance is significantly influenced by internal integration and standardization, while product performance is  significantly influenced by external integration and  requirement volatility. This study contributes  to a better understanding of how knowledge integration can be managed in outsourced ISD projects in view of increasing their success.

  20. Safety of Nuclear Power Plants: Design. Specific Safety Requirements (Chinese Ed.)

    2012-01-01

    On the basis of the principles included in the Fundamental Safety Principles, IAEA Safety Standards Series No. SF-1, this Safety Requirements publication establishes requirements applicable to the design of nuclear power plants. It covers the design phase and provides input for the safe operation of the power plant. It elaborates on the safety objective, safety principles and concepts that provide the basis for deriving the safety requirements that must be met for the design of a nuclear power plant. Contents: 1. Introduction; 2. Applying the safety principles and concepts; 3. Management of safety in design; 4. Principal technical requirements; 5. General plant design; 6. Design of specific plant systems.

  1. Safety of Nuclear Power Plants: Design. Specific Safety Requirements (French Ed.)

    2012-01-01

    On the basis of the principles included in the Fundamental Safety Principles, IAEA Safety Standards Series No. SF-1, this Safety Requirements publication establishes requirements applicable to the design of nuclear power plants. It covers the design phase and provides input for the safe operation of the power plant. It elaborates on the safety objective, safety principles and concepts that provide the basis for deriving the safety requirements that must be met for the design of a nuclear power plant. Contents: 1. Introduction; 2. Applying the safety principles and concepts; 3. Management of safety in design; 4. Principal technical requirements; 5. General plant design; 6. Design of specific plant systems.

  2. Safety of Nuclear Power Plants: Design. Specific Safety Requirements (Arabic Ed.)

    2012-01-01

    On the basis of the principles included in the Fundamental Safety Principles, IAEA Safety Standards Series No. SF-1, this Safety Requirements publication establishes requirements applicable to the design of nuclear power plants. It covers the design phase and provides input for the safe operation of the power plant. It elaborates on the safety objective, safety principles and concepts that provide the basis for deriving the safety requirements that must be met for the design of a nuclear power plant. Contents: 1. Introduction; 2. Applying the safety principles and concepts; 3. Management of safety in design; 4. Principal technical requirements; 5. General plant design; 6. Design of specific plant systems.

  3. Certification of ERDA contractors' packaging with respect to compliance with DOT specification 7A performance requirements

    Edling, D.A.; Griffin, J.F.

    1975-01-01

    The purpose of this study was to have one ERDA contractor: (1) compile a list of specification packagings, proposed by ERDA contractors, for shipping Type A quantities of radioactive material, and (2) analyze these packages for conformance to Specification 7A requirements. This study was divided into two phases. Phase I provides a report on those packages which could be shown, based on existing test data and engineering analyses, to conform to DOT Specification 7A packaging requirements. The results of Phase I are discussed in detail in the publication, ''Certification of AEC Contractor's Packagings With Respect to Compliance with DOT Specification 7A Performance Requirements -- Phase I Summary Report,'' D. A. Edling, H. E. Meyer and G. L. Phillabaum (Schedule 189C, May 26, 1974). The objectives of Phase II were: (1) identification of packages from Phase I for which available information was not adequate for certification. (Those specification containers used by ERDA contractors and those containers for which adequate information was available for certification are listed in the Phase I summary report.); (2) identification of specific test/engineering analysis data required; (3) generation/procurement of these data; and (4) documentation of study results for use by all ERDA contractors and private industry. The results of Phase II of the study are presented. (U.S.)

  4. WEB MAPPING ARCHITECTURES BASED ON OPEN SPECIFICATIONS AND FREE AND OPEN SOURCE SOFTWARE IN THE WATER DOMAIN

    C. Arias Muñoz

    2017-09-01

    Full Text Available The availability of water-related data and information across different geographical and jurisdictional scales is of critical importance for the conservation and management of water resources in the 21st century. Today information assets are often found fragmented across multiple agencies that use incompatible data formats and procedures for data collection, storage, maintenance, analysis, and distribution. The growing adoption of Web mapping systems in the water domain is reducing the gap between data availability and its practical use and accessibility. Nevertheless, more attention must be given to the design and development of these systems to achieve high levels of interoperability and usability while fulfilling different end user informational needs. This paper first presents a brief overview of technologies used in the water domain, and then presents three examples of Web mapping architectures based on free and open source software (FOSS and the use of open specifications (OS that address different users’ needs for data sharing, visualization, manipulation, scenario simulations, and map production. The purpose of the paper is to illustrate how the latest developments in OS for geospatial and water-related data collection, storage, and sharing, combined with the use of mature FOSS projects facilitate the creation of sophisticated interoperable Web-based information systems in the water domain.

  5. Web Mapping Architectures Based on Open Specifications and Free and Open Source Software in the Water Domain

    Arias Muñoz, C.; Brovelli, M. A.; Kilsedar, C. E.; Moreno-Sanchez, R.; Oxoli, D.

    2017-09-01

    The availability of water-related data and information across different geographical and jurisdictional scales is of critical importance for the conservation and management of water resources in the 21st century. Today information assets are often found fragmented across multiple agencies that use incompatible data formats and procedures for data collection, storage, maintenance, analysis, and distribution. The growing adoption of Web mapping systems in the water domain is reducing the gap between data availability and its practical use and accessibility. Nevertheless, more attention must be given to the design and development of these systems to achieve high levels of interoperability and usability while fulfilling different end user informational needs. This paper first presents a brief overview of technologies used in the water domain, and then presents three examples of Web mapping architectures based on free and open source software (FOSS) and the use of open specifications (OS) that address different users' needs for data sharing, visualization, manipulation, scenario simulations, and map production. The purpose of the paper is to illustrate how the latest developments in OS for geospatial and water-related data collection, storage, and sharing, combined with the use of mature FOSS projects facilitate the creation of sophisticated interoperable Web-based information systems in the water domain.

  6. Handbook of methods for risk-based analysis of technical specification requirements

    Samanta, P.K.; Vesely, W.E.

    1994-01-01

    Technical Specifications (TS) requirements for nuclear power plants define the Limiting Conditions for Operation (LCOs) and Surveillance Requirements (SRs) to assure safety during operation. In general, these requirements were based on deterministic analysis and engineering judgments. Experiences with plant operation indicate that some elements of the requirements are unnecessarily restrictive, while others may not be conducive to safety. Improvements in these requirements are facilitated by the availability of plant specific Probabilistic Safety Assessments (PSAs). The use of risk and reliability-based methods to improve TS requirements has gained wide interest because these methods can: Quantitatively evaluate the risk and justify changes based on objective risk arguments; Provide a defensible basis for these requirements for regulatory applications. The US NRC Office of Research is sponsoring research to develop systematic risk-based methods to improve various aspects of TS requirements. The handbook of methods, which is being prepared, summarizes such risk-based methods. The scope of the handbook includes reliability and risk-based methods for evaluating allowed outage times (AOTs), action statements requiring shutdown where shutdown risk may be substantial, surveillance test intervals (STIs), defenses against common-cause failures, managing plant configurations, and scheduling maintenances. For each topic, the handbook summarizes methods of analysis and data needs, outlines the insights to be gained, lists additional references, and presents examples of evaluations

  7. Handbook of methods for risk-based analysis of Technical Specification requirements

    Samanta, P.K.; Vesely, W.E.

    1993-01-01

    Technical Specifications (TS) requirements for nuclear power plants define the Limiting Conditions for Operation (LCOs) and Surveillance Requirements (SRs) to assure safety during operation. In general, these requirements were based on deterministic analysis and engineering judgments. Experiences with plant operation indicate that some elements of the requirements are unnecessarily restrictive, while others may not be conducive to safety. Improvements in these requirements are facilitated by the availability of plant specific Probabilistic Safety Assessments (PSAs). The use of risk and reliability-based methods to improve TS requirements has gained wide interest because these methods can: quantitatively evaluate the risk impact and justify changes based on objective risk arguments. Provide a defensible basis for these requirements for regulatory applications. The United States Nuclear Regulatory Commission (USNRC) Office of Research is sponsoring research to develop systematic risk-based methods to improve various aspects of TS requirements. The handbook of methods, which is being prepared, summarizes such risk-based methods. The scope of the handbook includes reliability and risk-based methods for evaluating allowed outage times (AOTs), action statements requiring shutdown where shutdown risk may be substantial, surveillance test intervals (STIs), defenses against common-cause failures, managing plant configurations, and scheduling maintenances. For each topic, the handbook summarizes methods of analysis and data needs, outlines the insights to be gained, lists additional references, and presents examples of evaluations

  8. Experiences with formal engineering: model-based specification, implementation and testing of a software bus at Neopost

    Sijtema, M.; Salaün, G.; Schätz, B.; Belinfante, Axel; Stoelinga, Mariëlle Ida Antoinette; Marinelli, L.

    2014-01-01

    We report on the actual industrial use of formal methods during the development of a software bus. During an internship at Neopost Inc., of 14 weeks, we developed the server component of a software bus, called the XBus, using formal methods during the design, validation and testing phase: we modeled

  9. Experiences with Formal Engineering : Model-Based Specification, Implementation and Testing of a Software Bus at Neopost

    Sijtema, Marten; Stoelinga, Mariëlle Ida Antoinette; Belinfante, Axel; Marinelli, Lawrence; Salaün, Gwen; Schätz, Bernhard

    We report on the actual industrial use of formal methods during the development of a software bus. At Neopost Inc., we developed the server component of a software bus, called the XBus, using formal methods during the design, validation and testing phase: We modeled our design of the XBus in the

  10. The impact of technical specification surveillance requirements and allowable outage times on plant availability

    Webster, S.A.; Finnicum, D.J.

    1985-01-01

    Surveillances required to be conducted by a plant's Technical Specifications have resulted in plant shutdowns and lost availability. This paper looks at shutdowns which have occurred due to required surveillance testing and insufficient repair time allowed by Technical Specifications. A loss of plant availability of almost 3% per plant year was found for U.S. pressurized water reactors during the five year period, 1979 to 1984. This figure excludes major problems which required plant shutdown whether or not mandated by the Technical Specifications. In addition to their affect on availability, such shutdowns can add to the challenges to plant safety systems and can affect plant aging by increasing the thermal cycles on plant components

  11. A Requirements-Based Exploration of Open-Source Software Development Projects--Towards a Natural Language Processing Software Analysis Framework

    Vlas, Radu Eduard

    2012-01-01

    Open source projects do have requirements; they are, however, mostly informal, text descriptions found in requests, forums, and other correspondence. Understanding such requirements provides insight into the nature of open source projects. Unfortunately, manual analysis of natural language requirements is time-consuming, and for large projects,…

  12. Specification of safety requirements for waste packages with respect to practicable quality control measures

    Gruendler, D.; Wurtinger, W.

    1987-01-01

    Waste packages for disposal in a repository in the Federal Republic of Germany have to meet safety requirements derived from site specific safety analyses. The examination of the waste packages with regard to compliance with these requirements is the main objective of quality control measures. With respect to quality control the requirements have to be specified in a way that practicable control measures can be applied. This is dealt with for the quality control of the activity inventory and the quality control of the waste form. The paper discusses the determination of the activity of hard-to-measure radionuclides and the specification of safety related requirements for the waste form and the packaging using typical examples

  13. Practical support for Lean Six Sigma software process definition using IEEE software engineering standards

    Land, Susan K; Walz, John W

    2012-01-01

    Practical Support for Lean Six Sigma Software Process Definition: Using IEEE Software Engineering Standards addresses the task of meeting the specific documentation requirements in support of Lean Six Sigma. This book provides a set of templates supporting the documentation required for basic software project control and management and covers the integration of these templates for their entire product development life cycle. Find detailed documentation guidance in the form of organizational policy descriptions, integrated set of deployable document templates, artifacts required in suppo

  14. Guidance and methods for satisfying low specific activity material and surface contaminated object regulatory requirements

    Pope, R.B.; Shappert, L.B.; Michelhaugh, R.D.; Boyle, R.W.; Easton, E.P.; Coodk, J.R.

    1998-01-01

    The U.S. Department of Transportation (DOT) and the U.S. Nuclear Regulatory Commission (NRC) have prepared a comprehensive set of draft guidance for shippers and inspectors to use when applying the newly imposed regulatory requirements for low specific activity (LSA) material and surface contaminated objects (SCOs). These requirements represent significant departures in some areas from the manner in which these materials and objects were regulated by the earlier versions of the regulations. The proper interpretation and application of the regulatory criteria can require a fairly complex set of decisions be made. To assist those trying these regulatory requirements, a detailed set of logic-flow diagrams representing decisions related to multiple factors were prepared and included in the draft report for comment on Categorizing and Transporting Low Specific Activity Materials and Surface Contaminated Objects, (DOT/NRC, 1997). These logic-flow diagrams, as developed, are specific to the U.S. regulations, but were readily adaptable to the IAEA regulations. The diagrams have been modified accordingly and tied directly to specific paragraphs in IAEA Safety Series No. 6. This paper provides the logic-flow diagrams adapted in the IAEA regulations, and demonstrated how these diagrams can be used to assist consignors and inspectors in assessing compliance of shipments with the LSA material and SCO regulatory requirements. (authors)

  15. Satellite-enabled educational services specification and requirements analysis based on user feedback

    Tsekeridou, Sofia; Tiropanis, Thanassis; Rorris, Dimitris; Constantinos, Makropoulos; Serif, Tacha; Stergioulas, Lampros

    2008-01-01

    Advanced tele-education services provision in remote geographically dispersed user communities (such as agriculture and maritime), based on the specific needs and requirements of such communities, implies significant infrastructural and broadband connectivity requirements for rich media, timely and quality-assured content delivery and interactivity. The solution to broadband access anywhere is provided by satellite-enabled communication infrastructures. This paper aims to present such satelli...

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

    Mckee, James W.

    1990-01-01

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

  17. Software Assurance Competency Model

    2013-03-01

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

  18. The applies specific technical requirements to the services of radiological protection according to the 17025

    Marrero Garcia, M.; Fernandez Gomez, I. M.; Prendes Alonso, M.; Molina Perez, D.

    2004-07-01

    The employment in the Center of Radiation Protection and Hygiene (CRPH) of Cuba, of the standard 17025 for the administration of the quality of the calibration laboratories and test that offer services of radiological protection requires of a technical complement to really determine the technical competence. In the standard 17025, the specific requirements, are mentioned in the annex B (with informative character), where it points out that: {sup T}he requirements specified in the standard 17025 are established in general terms and, although they can be applied to all the test laboratories and applications, they could be necessary applications{sup .} In the CRPH these applications are translated in indispensable technical requirements to evaluate the performance of the services of radiological protection that offers, specifically those of personal monitoring, the calibration of instruments and the metrology of radionuclides. Although the standard 17025 is quite rigorous in the evaluation of technical requirements, to have specific materials not serves alone of tool to the laboratories, but also for the body of accreditation . In the CRPH the permanent employment of this tool has not constituted a practice, but had been good before our clients certain nonconformities to evaluate the performance of the laboratory and to achieve the recovery of the trust in its results. With this work we seek to expose some of these experiences. The experiences of the application of some of the technical requirements, in our case, they have been applied to the service of personal monitoring that offers the Laboratory of Personal Dosimetry. This laboratory is accredited by the National Accreditation Board of the Republic of Cuba (NABC) and besides fulfilling that settled down in 17025, the Approaches of Accreditation for test laboratories and calibration and it should also implant that settled down as specific technical requirements for the recognition of technical competence. (Author

  19. Challenges in balancing the amount of solution information in requirement specifications for embedded products

    Savolainen, Juha; Hauksdóttir, Dagný; Mannion, Mike

    2013-01-01

    customers have such intimate knowledge of their products that their requirements tend to be very specific, and if the customer knows the exact solution needed that naturally will reduce the cost of the requirements elicitation as well as design activities. Practitioners are challenged to understand when......Requirements are traditionally viewed as being free of the details of an envisioned solution and specified using purely problem domain entities. Preventing premature design in the requirements permits the available design space not to be restricted too early which might inhibit innovative designs....... In practice, on many industrial projects, separating the problem and solution domain entities can be difficult, and arguably there are benefits for not doing so. Many customers feel more confident describing their requirements, often as the difference between the existing products and their needs, some...

  20. Computer-Aided Software Engineering - An approach to real-time software development

    Walker, Carrie K.; Turkovich, John J.

    1989-01-01

    A new software engineering discipline is Computer-Aided Software Engineering (CASE), a technology aimed at automating the software development process. This paper explores the development of CASE technology, particularly in the area of real-time/scientific/engineering software, and a history of CASE is given. The proposed software development environment for the Advanced Launch System (ALS CASE) is described as an example of an advanced software development system for real-time/scientific/engineering (RT/SE) software. The Automated Programming Subsystem of ALS CASE automatically generates executable code and corresponding documentation from a suitably formatted specification of the software requirements. Software requirements are interactively specified in the form of engineering block diagrams. Several demonstrations of the Automated Programming Subsystem are discussed.

  1. 24 CFR 200.943 - Supplementary specific requirements under the HUD building product standards and certification...

    2010-04-01

    ... under the HUD building product standards and certification program for the grademarking of lumber. 200... Supplementary specific requirements under the HUD building product standards and certification program for the... compliance with the U.S. Department of Commerce Voluntary Product Standard PS 20-94 American Softwood Lumber...

  2. 24 CFR 200.952 - Supplementary specific requirements under the HUD building product standards and certification...

    2010-04-01

    ... under the HUD building product standards and certification program for particleboard interior stair... Supplementary specific requirements under the HUD building product standards and certification program for... forth in § 200.935(d)(6) concerning labeling of a product, the administrator's validation mark and the...

  3. 24 CFR 200.954 - Supplementary specific requirements under the HUD building product standard and certification...

    2010-04-01

    ... under the HUD building product standard and certification program for construction adhesives for wood... § 200.954 Supplementary specific requirements under the HUD building product standard and certification...) concerning labeling of a product, the administrator's validation mark and the manufacturer's certification of...

  4. Development Modules for Specification of Requirements for a System of Verification of Parallel Algorithms

    Vasiliy Yu. Meltsov

    2012-05-01

    Full Text Available This paper presents the results of the development of one of the modules of the system verification of parallel algorithms that are used to verify the inference engine. This module is designed to build the specification requirements, the feasibility of which on the algorithm is necessary to prove (test.

  5. The impact of customer-specific requirements on supply chain management

    Hubert I.P. Conceivious

    2010-11-01

    Full Text Available The complexities of being a supplier to motorcar manufacturers, also known as original equipment manufacturers (OEMs, provide an array of challenges to component manufacturers. Customer-specific requirements (CSRs add to the convolutions of a supplier’s quality management systems when producing components for the various motor manufacturers. The catalytic converter industry (CCI forms part of the component supply chain in the motor industry. The CCI consists of a plethora of suppliers to produce the catalytic converter. This paper focuses on three of the five main suppliers, namely the ‘monolith substrate manufacturers’, the ‘coaters’, and the ‘canners’. Most OEMs required that critical and strategic suppliers should be ISO/TS 16949:2009 certified. ISO/TS 16949:2009 refers to an internationally recognised specification, specifically adapted for the motor industry. The specification indicates the minimum requirements and also makes provision for additional requirements known as CSRs that can be specified by the OEM.

  6. 40 CFR 270.24 - Specific part B information requirements for process vents.

    2010-07-01

    ... incinerator, flare, boiler, process heater, condenser, or carbon adsorption system to comply with the... each compliance test required by § 264.1033(k). (3) A design analysis, specifications, drawings... texts acceptable to the Regional Administrator that present basic control device information. The design...

  7. Software Formal Inspections Guidebook

    1993-01-01

    The Software Formal Inspections Guidebook is designed to support the inspection process of software developed by and for NASA. This document provides information on how to implement a recommended and proven method for conducting formal inspections of NASA software. This Guidebook is a companion document to NASA Standard 2202-93, Software Formal Inspections Standard, approved April 1993, which provides the rules, procedures, and specific requirements for conducting software formal inspections. Application of the Formal Inspections Standard is optional to NASA program or project management. In cases where program or project management decide to use the formal inspections method, this Guidebook provides additional information on how to establish and implement the process. The goal of the formal inspections process as documented in the above-mentioned Standard and this Guidebook is to provide a framework and model for an inspection process that will enable the detection and elimination of defects as early as possible in the software life cycle. An ancillary aspect of the formal inspection process incorporates the collection and analysis of inspection data to effect continual improvement in the inspection process and the quality of the software subjected to the process.

  8. An Interoperability Framework and Capability Profiling for Manufacturing Software

    Matsuda, M.; Arai, E.; Nakano, N.; Wakai, H.; Takeda, H.; Takata, M.; Sasaki, H.

    ISO/TC184/SC5/WG4 is working on ISO16100: Manufacturing software capability profiling for interoperability. This paper reports on a manufacturing software interoperability framework and a capability profiling methodology which were proposed and developed through this international standardization activity. Within the context of manufacturing application, a manufacturing software unit is considered to be capable of performing a specific set of function defined by a manufacturing software system architecture. A manufacturing software interoperability framework consists of a set of elements and rules for describing the capability of software units to support the requirements of a manufacturing application. The capability profiling methodology makes use of the domain-specific attributes and methods associated with each specific software unit to describe capability profiles in terms of unit name, manufacturing functions, and other needed class properties. In this methodology, manufacturing software requirements are expressed in terns of software unit capability profiles.

  9. Advanced information processing system: Input/output network management software

    Nagle, Gail; Alger, Linda; Kemp, Alexander

    1988-01-01

    The purpose of this document is to provide the software requirements and specifications for the Input/Output Network Management Services for the Advanced Information Processing System. This introduction and overview section is provided to briefly outline the overall architecture and software requirements of the AIPS system before discussing the details of the design requirements and specifications of the AIPS I/O Network Management software. A brief overview of the AIPS architecture followed by a more detailed description of the network architecture.

  10. Sharing data between mobile devices, connected vehicles, and infrastructure task 3: system requirements specifications (SyRS) final.

    2016-07-14

    This report describes the system requirements specifications (SyRS) for the use of mobile devices in a connected vehicle environment. Specifically, it defines the different types of requirements (functional, interface, performance, security, data, an...

  11. Safety of Nuclear Power Plants: Design. Specific Safety Requirements (Spanish Edition)

    2012-01-01

    This publication is a revision of Safety Requirements No. NS-R-1, Safety of Nuclear Power Plants: Design. It establishes requirements applicable to the design of nuclear power plants and elaborates on the safety objective, safety principles and concepts that provide the basis for deriving the safety requirements that must be met for the design of a nuclear power plant. It will be useful for organizations involved in the design, manufacture, construction, modification, maintenance, operation and decommissioning of nuclear power plants, as well as for regulatory bodies. Contents: 1. Introduction; 2. Applying the safety principles and concepts; 3. Management of safety in design; 4. Principal technical requirements; 5. General plant design; 6. Design of specific plant systems.

  12. Safety of Nuclear Power Plants: Design. Specific Safety Requirements (Russian Edition)

    2012-01-01

    This publication is a revision of Safety Requirements No. NS-R-1, Safety of Nuclear Power Plants: Design. It establishes requirements applicable to the design of nuclear power plants and elaborates on the safety objective, safety principles and concepts that provide the basis for deriving the safety requirements that must be met for the design of a nuclear power plant. It will be useful for organizations involved in the design, manufacture, construction, modification, maintenance, operation and decommissioning of nuclear power plants, as well as for regulatory bodies. Contents: 1. Introduction; 2. Applying the safety principles and concepts; 3. Management of safety in design; 4. Principal technical requirements; 5. General plant design; 6. Design of specific plant systems.

  13. CRISP. Requirements Specifications of Intelligent ICT Simulation Tools for Power Applications

    Warmer, C.J.; Kester, J.C.P.; Kamphuis, I.G. [ECN Energy in the Built Environment and Networks, Petten (Netherlands); Carlsson, P [EnerSearch, Malmoe (Sweden); Fontela, M. [Laboratory of Electrical Engineering LEG, Grenoble (France); Gustavsson, R. [Blekinge Institute of Technology BTH, Karlskrona (Sweden)

    2003-10-15

    This report, deliverable D2.1 in the CRISP project, serves as a preparation report for the development of simulation tools and prototype software which will be developed in forthcoming stages of the CRISP project. Application areas for these simulations are: fault detection and diagnosis, supply and demand matching and intelligent load shedding. The context in which these applications function is the power network with a high degree of distributed generation, including renewables. In order to control a so called distributed grid we can benefit from a high level of distributed control and intelligence. This requires, on top of the power system network, an information and communication network.. We argue that such a network should be seen as an enabler of distributed control and intelligence. The applications, through which control and intelligence is implemented, then form a third network layer, the service oriented network. Building upon this three-layered network model we derive in this report the requirements for a simulation tool and experiments which study new techniques for fault detection and diagnostics and for simulation tools and experiments implementing intelligent load shedding and supply and demand matching scenarios. We also look at future implementation of these services within the three-layered network model and the requirements that follow for the core information and communication network and for the service oriented network. These requirements, supported by the studies performed in the CRISP Workpackage 1, serve as a basis for development of the simulation tools in the tasks 2.2 to 2.4.

  14. CRISP. Requirements Specifications of Intelligent ICT Simulation Tools for Power Applications

    Warmer, C.J.; Kester, J.C.P.; Kamphuis, I.G.; Carlsson, P; Fontela, M.; Gustavsson, R.

    2003-10-01

    This report, deliverable D2.1 in the CRISP project, serves as a preparation report for the development of simulation tools and prototype software which will be developed in forthcoming stages of the CRISP project. Application areas for these simulations are: fault detection and diagnosis, supply and demand matching and intelligent load shedding. The context in which these applications function is the power network with a high degree of distributed generation, including renewables. In order to control a so called distributed grid we can benefit from a high level of distributed control and intelligence. This requires, on top of the power system network, an information and communication network.. We argue that such a network should be seen as an enabler of distributed control and intelligence. The applications, through which control and intelligence is implemented, then form a third network layer, the service oriented network. Building upon this three-layered network model we derive in this report the requirements for a simulation tool and experiments which study new techniques for fault detection and diagnostics and for simulation tools and experiments implementing intelligent load shedding and supply and demand matching scenarios. We also look at future implementation of these services within the three-layered network model and the requirements that follow for the core information and communication network and for the service oriented network. These requirements, supported by the studies performed in the CRISP Workpackage 1, serve as a basis for development of the simulation tools in the tasks 2.2 to 2.4

  15. Techniques and tools for software qualification in KNICS

    Cha, Kyung H.; Lee, Yeong J.; Cheon, Se W.; Kim, Jang Y.; Lee, Jang S.; Kwon, Kee C.

    2004-01-01

    This paper describes techniques and tools for qualifying safety software in Korea Nuclear Instrumentation and Control System (KNICS). Safety software are developed and applied for a Reactor Protection System (RPS), an Engineered Safety Features and Component Control System (ESF-CCS), and a safety Programmable Logic Controller (PLC) in the KNICS. Requirements and design specifications of safety software are written by both natural language and formal specification languages. Statechart is used for formal specification of software of the ESF-CCS and the safety PLC while NuSCR is used for formal specification of them of the RPS. pSET (POSCON Software Engineering Tool) as a software development tool has been developed and utilized for the IEC61131-3 based PLC programming. The qualification of the safety software consists of software verification and validation (V and V) through software life cycle, software safety analysis, and software configuration management, software quality assurance, and COTS (Commercial-Off-The-Shelf) dedication. The criteria and requirements for qualifying the safety software have been established with them in Software Review Plan (SRP)/Branch Technical Positions (BTP)-14, IEEE Std. 7-4.3.2-1998, NUREG/CR-6463, IEEE Std. 1012-1998, and so on. Figure 1 summarizes qualification techniques and tools for the safety software

  16. Requirement for specific gravity and creatinine adjustments for urinary steroids and luteinizing hormone concentrations in adolescents.

    Singh, Gurmeet K S; Balzer, Ben W R; Desai, Reena; Jimenez, Mark; Steinbeck, Katharine S; Handelsman, David J

    2015-11-01

    Urinary hormone concentrations are often adjusted to correct for hydration status. We aimed to determine whether first morning void urine hormones in growing adolescents require adjustments and, if so, whether urinary creatinine or specific gravity are better adjustments. The study population was adolescents aged 10.1 to 14.3 years initially who provided fasting morning blood samples at 0 and 12 months (n = 343) and first morning urine every three months (n = 644). Unadjusted, creatinine and specific gravity-adjusted hormonal concentrations were compared by Deming regression and Bland-Altman analysis and grouped according to self-rated Tanner stage or chronological age. F-ratios for self-rated Tanner stages and age groups were used to compare unadjusted and adjusted hormonal changes in growing young adolescents. Correlations of paired serum and urinary hormonal concentration of unadjusted and creatinine and specific gravity-adjusted were also compared. Fasting first morning void hormone concentrations correlated well and were unbiased between unadjusted or adjusted by either creatinine or specific gravity. Urine creatinine concentration increases with Tanner stages, age and male gender whereas urine specific gravity was not influenced by Tanner stage, age or gender. Adjustment by creatinine or specific gravity of urinary luteinizing hormone, estradiol, testosterone, dihydrotestosterone and dehydroepiandrosterone concentrations did not improve correlation with paired serum concentrations. Urine steroid and luteinizing hormone concentrations in first morning void samples of adolescents are not significantly influenced by hydration status and may not require adjustments; however, if desired, both creatinine and specific gravity adjustments are equally suitable. © The Author(s) 2015.

  17. Testing Requirements to Manage Data Exchange Specifications in Enterprise Integration - A Schema Design Quality Focus.

    Kulvatunyou, Boonserm [ORNL; Ivezic, Nenad [ORNL; Buhwan, Jeong [POSTECH University, South Korea

    2004-07-01

    In this paper, we describe the requirements to test W3C XML Schema usage when defining message schemas for data exchange in any large and evolving enterprise integration project. We then decompose the XML Schema testing into four (4) aspects including the message schema conformance to the XML Schema specification grammar, the message schema conformance to the XML Schema specification semantics, the message schema conformance to design quality testing, and canonical semantics testing of the message schema. We describe these four testing aspects in some detail and point to other related efforts. We further focus to provide some technical details for the message schema design quality testing. As a future work, we describe the requirements for canonical semantics testing and potential solution approaches. Finally, we describe an implementation architecture for the message schema design quality testing.

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

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

    2013-01-01

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

  19. Dynamic visualization techniques for high consequence software

    Pollock, G.M.

    1998-02-01

    This report documents a prototype tool developed to investigate the use of visualization and virtual reality technologies for improving software surety confidence. The tool is utilized within the execution phase of the software life cycle. It provides a capability to monitor an executing program against prespecified requirements constraints provided in a program written in the requirements specification language SAGE. The resulting Software Attribute Visual Analysis Tool (SAVAnT) also provides a technique to assess the completeness of a software specification. The prototype tool is described along with the requirements constraint language after a brief literature review is presented. Examples of how the tool can be used are also presented. In conclusion, the most significant advantage of this tool is to provide a first step in evaluating specification completeness, and to provide a more productive method for program comprehension and debugging. The expected payoff is increased software surety confidence, increased program comprehension, and reduced development and debugging time.

  20. Statistical Study to Check the Conformity of Aggregate in Kirkuk City to Requirement of Iraqi Specification

    Ammar Saleem Khazaal; Nizar N Ismeel; Abdel fattah K. Hussein

    2018-01-01

    This research reviews a statistical study to check the conformity of aggregates (Coarse and Fine) was used in Kirkuk city to the requirements of the Iraqi specifications. The data of sieve analysis (215 samples) of aggregates being obtained from of National Central Construction Laboratory and Technical College Construction Laboratory in Kirkuk city have analyzed using the statistical program SAS. The results showed that 5%, 17%, and 18% of fine aggregate samples are passing sieve sizes 10 mm,...

  1. Appraisal of work ability in relation to job-specific health requirements in ambulance workers.

    van Schaaijk, A; Boschman, J S; Frings-Dresen, M H W; Sluiter, J K

    2017-01-01

    To gain insight into which job-specific health requirements relate to work ability, the following two research questions were formulated: Which job-specific health requirements are associated with the appraisal of work ability in ambulance drivers and paramedics? How are appraisals of physical and mental work ability associated with the appraisal of overall work ability in ambulance drivers and paramedics? Workers Health Surveillance cross-sectional data of 506 ambulance workers (236 drivers and 270 paramedics) were used. The tests for specific job requirements were divided into six categories. Work ability was appraised as overall, physical and mental/emotional. Multiple linear stepwise regression analyses were used to model the associations. Outcomes in 'raised alertness and judgment ability' (R 2  = 0.09), 'job-specific physical abilities' (R 2  = 0.10) and 'emotional peak load' (R 2  = 0.07) significantly explained appraised overall, physical and mental/emotional work ability. Physical and mental/emotional work ability together explained 48.3% of the variance of overall work ability. The explained variance by physical and mental/emotional work ability was almost 4% higher in drivers than in paramedics. Overall work ability was significantly explained by outcomes in 'raised alertness and judgment ability' and 'emotional peak load.' Physical work ability was significantly explained by 'job-specific physical abilities' and 'raised alertness and judgment ability' outcomes, while 'emotional peak load' and 'raised alertness and judgment ability' outcomes significantly explained mental/emotional work ability. Physical and mental/emotional work ability explains the same proportion of variance in overall work ability.

  2. AMTD: update of engineering specifications derived from science requirements for future UVOIR space telescopes

    Stahl, H. Philip; Postman, Marc; Mosier, Gary; Smith, W. Scott; Blaurock, Carl; Ha, Kong; Stark, Christopher C.

    2014-08-01

    The Advance Mirror Technology Development (AMTD) project is in Phase 2 of a multiyear effort, initiated in FY12, to mature by at least a half TRL step six critical technologies required to enable 4 meter or larger UVOIR space telescope primary mirror assemblies for both general astrophysics and ultra-high contrast observations of exoplanets. AMTD uses a science-driven systems engineering approach. We mature technologies required to enable the highest priority science AND provide a high-performance low-cost low-risk system. To give the science community options, we are pursuing multiple technology paths. A key task is deriving engineering specifications for advanced normal-incidence monolithic and segmented mirror systems needed to enable both general astrophysics and ultra-high contrast observations of exoplanets missions as a function of potential launch vehicles and their mass and volume constraints. A key finding of this effort is that the science requires an 8 meter or larger aperture telescope.

  3. World Workshop on Oral Medicine VI: Utilization of Oral Medicine-specific software for support of clinical care, research, and education: current status and strategy for broader implementation.

    Brailo, Vlaho; Firriolo, Francis John; Tanaka, Takako Imai; Varoni, Elena; Sykes, Rosemary; McCullough, Michael; Hua, Hong; Sklavounou, Alexandra; Jensen, Siri Beier; Lockhart, Peter B; Mattsson, Ulf; Jontell, Mats

    2015-08-01

    To assess the current scope and status of Oral Medicine-specific software (OMSS) utilized to support clinical care, research, and education in Oral Medicine and to propose a strategy for broader implementation of OMSS within the global Oral Medicine community. An invitation letter explaining the objectives was sent to the global Oral Medicine community. Respondents were interviewed to obtain information about different aspects of OMSS functionality. Ten OMSS tools were identified. Four were being used for clinical care, one was being used for research, two were being used for education, and three were multipurpose. Clinical software was being utilized as databases developed to integrate of different type of clinical information. Research software was designed to facilitate multicenter research. Educational software represented interactive, case-orientated technology designed for clinical training in Oral Medicine. Easy access to patient data was the most commonly reported advantage. Difficulty of use and poor integration with other software was the most commonly reported disadvantage. The OMSS presented in this paper demonstrate how information technology (IT) can have an impact on the quality of patient care, research, and education in the field of Oral Medicine. A strategy for broader implementation of OMSS is proposed. Copyright © 2015 Elsevier Inc. All rights reserved.

  4. Identifying context-specific competencies required by community Australian Football sports trainers.

    Donaldson, Alex; Finch, Caroline F

    2012-08-01

    First-aid is a recommended injury prevention and risk management strategy in community sport; however, little is known about the sport-specific competencies required by first-aid providers. To achieve expert consensus on the competencies required by community Australian Football (community-AF) sports trainers. A three-round online Delphi process. Community-AF. 16 Australian sports first-aid and community-AF experts. Rating of competencies as either 'essential', 'expected', 'ideal' or 'not required'. Results After Round 3, 47 of the 77 (61%) competencies were endorsed as 'essential' or 'expected' for a sports trainer to effectively perform the activities required to the standards expected at a community-AF club by ≥75% of experts. These competencies covered: the role of the sports trainer; the responsibilities of the sports trainer; emergency management; injury and illness assessment and immediate management; taping; and injury prevention and risk management. Four competencies (5%) were endorsed as 'ideal' or 'not required' by ≥85% of experts and were excluded from further consideration. The 26 competencies where consensus was not reached were retained as second-tier, optional competencies. Sports trainers are important members of on-field first-aid teams, providing support to both injured players and other sports medicine professionals. The competencies identified in this study provide the basis of a proposed two-tiered community-AF-specific sports trainer education structure that can be implemented by the peak sports body. This includes six mandatory modules, relating to the 'required' competencies, and a further six optional modules covering competencies on which consensus was not reached.

  5. 40 CFR 86.1306-07 - Equipment required and specifications; overview.

    2010-07-01

    ... the hardware and software included in the alternate system. Dimensioned drawings, flow-charts... NIST traceable standards, or equivalent national standards. Diagrams, schematics, and other graphics...

  6. Implementing Software Safety in the NASA Environment

    Wetherholt, Martha S.; Radley, Charles F.

    1994-01-01

    Until recently, NASA did not consider allowing computers total control of flight systems. Human operators, via hardware, have constituted the ultimate safety control. In an attempt to reduce costs, NASA has come to rely more and more heavily on computers and software to control space missions. (For example. software is now planned to control most of the operational functions of the International Space Station.) Thus the need for systematic software safety programs has become crucial for mission success. Concurrent engineering principles dictate that safety should be designed into software up front, not tested into the software after the fact. 'Cost of Quality' studies have statistics and metrics to prove the value of building quality and safety into the development cycle. Unfortunately, most software engineers are not familiar with designing for safety, and most safety engineers are not software experts. Software written to specifications which have not been safety analyzed is a major source of computer related accidents. Safer software is achieved step by step throughout the system and software life cycle. It is a process that includes requirements definition, hazard analyses, formal software inspections, safety analyses, testing, and maintenance. The greatest emphasis is placed on clearly and completely defining system and software requirements, including safety and reliability requirements. Unfortunately, development and review of requirements are the weakest link in the process. While some of the more academic methods, e.g. mathematical models, may help bring about safer software, this paper proposes the use of currently approved software methodologies, and sound software and assurance practices to show how, to a large degree, safety can be designed into software from the start. NASA's approach today is to first conduct a preliminary system hazard analysis (PHA) during the concept and planning phase of a project. This determines the overall hazard potential of

  7. The NIMA Kinase Is Required To Execute Stage-Specific Mitotic Functions after Initiation of Mitosis

    Govindaraghavan, Meera; Lad, Alisha A.

    2014-01-01

    The G2-M transition in Aspergillus nidulans requires the NIMA kinase, the founding member of the Nek kinase family. Inactivation of NIMA results in a late G2 arrest, while overexpression of NIMA is sufficient to promote mitotic events independently of cell cycle phase. Endogenously tagged NIMA-GFP has dynamic mitotic localizations appearing first at the spindle pole body and then at nuclear pore complexes before transitioning to within nuclei and the mitotic spindle and back at the spindle pole bodies at mitotic exit, suggesting that it functions sequentially at these locations. Since NIMA is indispensable for mitotic entry, it has been difficult to determine the requirement of NIMA for subaspects of mitosis. We show here that when NIMA is partially inactivated, although mitosis can be initiated, a proportion of cells fail to successfully generate two daughter nuclei. We further define the mitotic defects to show that normal NIMA function is required for the formation of a bipolar spindle, nuclear pore complex disassembly, completion of chromatin segregation, and the normal structural rearrangements of the nuclear envelope required to generate two nuclei from one. In the remaining population of cells that enter mitosis with inadequate NIMA, two daughter nuclei are generated in a manner dependent on the spindle assembly checkpoint, indicating highly penetrant defects in mitotic progression without sufficient NIMA activity. This study shows that NIMA is required not only for mitotic entry but also sequentially for successful completion of stage-specific mitotic events. PMID:24186954

  8. Disease specific stress of tumor patients at the beginning of radiotherapy. Effect on psychosocial support requirement

    Sehlen, S.; Hollenhorst, H.; Schymura, B.; Firsching, M.; Duehmke, E.; Herschbach, P.

    2001-01-01

    Purpose: Radiotherapy brings a tumor patient into a special life situation in which different variables play a role of often unknown importance. The goal of this study was to investigate disease specific stress of tumor patients at the beginning of radiotherapy with established psychodiagnostic questionnaires and to evaluate the effect on psychosocial support requirement in order to reduce stress and to improve quality of life and compliance during radiotherapeutical treatment. Patients and Methods: 732 patients were screened, of whom 446 (60.9%) fulfilled the criteria for inclusion (refusals 21.0%, low Karnofsky performance status 6.6%, management problems 3.4%, language barriers 3.0%, cognitive restrictions 2.6%, death 2.5%). Disease specific aspects of stress in the questionnaire (Fragebogen zur Belastung von Krebspatienten, FBK), life situation (LS) and self-defined care requirements (BB) were self-rated by patients with different tumor types before radiotherapy. Medical and sociodemographic data were also documented. We investigated 446 patients (262 male, 184 female; median age 60.0 years) with different diagnoses. Results: Stress was observed mainly due to reduction of efficiency, anxiety and pain on the subscales. Women had a significant higher stress on subscales of pain (p=0.016) and anxiety (p=0.009), patients younger than 45 years in the subscale information (p=0.002) and patients older than 45 and younger than 60 years in the subscale anxiety (p=0.002) and the total score (p=0.003). Patients with mamma carcinoma had the highest stress. The maximum percentages of patients under high stress were found for the subscales of efficiency (43%) and anxiety (40%). The support requirement was characterized by the need of more medical information and dialogue with the doctor. We saw a significant correlation of high stress and high care requirement. Conclusions: Psychosocial support should be founded on psychosocial stress diagnostic and self-defined care

  9. HPV specific testing: a requirement for oropharyngeal squamous cell carcinoma patients.

    Robinson, Max; Schache, Andrew; Sloan, Philip; Thavaraj, Selvam

    2012-07-01

    Human papillomavirus (HPV) testing is now recommended as part of the work up for patients with oropharyngeal squamous cell carcinoma (OPSCC) and those patients with cervical lymph node metastasis of unknown origin. The laboratory testing strategy should accurately assess the presence or absence of oncogenic HPV infection in routinely collected tumour samples that are subject to standard fixation protocols, alcohol-fixed cytological preparations and formalin-fixed tissue samples. The HPV status should correlate with biologically relevant outcome measures such as overall, disease-specific and disease-free survival. Whilst increased expression of p16 by immunohistochemistry is considered to be a surrogate marker of oncogenic HPV infection and is a validated independent prognostic biomarker, only HPV specific tests provide definitive evidence of the aetiological agent. We provide an overview of HPV testing in OPSCC, justifying the use of HPV specific tests. We examine the analytical accuracy of HPV specific tests against the 'reference' test--high risk HPV mRNA in fresh tissue--and contrast this with the performance of p16 immunohistochemistry as a stand alone test. We highlight the added value of HPV specific tests in prognostication, clinical trial design, and population-based disease surveillance. We consider that HPV specific testing is the starting point for developing increasingly informative biomarker panels in the context of 'stratified medicine'. We briefly frame test information in the context of disclosure of HPV status to patients. We conclude that only a testing strategy that includes HPV specific tests can deliver more effective care for patients with OPSCC. The international head and neck oncology community should work together to clearly define the minimum requirements for assigning a diagnosis of HPV-related OPSCC in order to ensure consistent reporting of this emerging and increasingly prevalent disease.

  10. Poliovirus intrahost evolution is required to overcome tissue-specific innate immune responses.

    Xiao, Yinghong; Dolan, Patrick Timothy; Goldstein, Elizabeth Faul; Li, Min; Farkov, Mikhail; Brodsky, Leonid; Andino, Raul

    2017-08-29

    RNA viruses, such as poliovirus, have a great evolutionary capacity, allowing them to quickly adapt and overcome challenges encountered during infection. Here we show that poliovirus infection in immune-competent mice requires adaptation to tissue-specific innate immune microenvironments. The ability of the virus to establish robust infection and virulence correlates with its evolutionary capacity. We further identify a region in the multi-functional poliovirus protein 2B as a hotspot for the accumulation of minor alleles that facilitate a more effective suppression of the interferon response. We propose that population genetic dynamics enables poliovirus spread between tissues through optimization of the genetic composition of low frequency variants, which together cooperate to circumvent tissue-specific challenges. Thus, intrahost virus evolution determines pathogenesis, allowing a dynamic regulation of viral functions required to overcome barriers to infection.RNA viruses, such as polioviruses, have a great evolutionary capacity and can adapt quickly during infection. Here, the authors show that poliovirus infection in mice requires adaptation to innate immune microenvironments encountered in different tissues.

  11. RET Functions as a Dual-Specificity Kinase that Requires Allosteric Inputs from Juxtamembrane Elements

    Iván Plaza-Menacho

    2016-12-01

    Full Text Available Receptor tyrosine kinases exhibit a variety of activation mechanisms despite highly homologous catalytic domains. Such diversity arises through coupling of extracellular ligand-binding portions with highly variable intracellular sequences flanking the tyrosine kinase domain and specific patterns of autophosphorylation sites. Here, we show that the juxtamembrane (JM segment enhances RET catalytic domain activity through Y687. This phospho-site is also required by the JM region to rescue an otherwise catalytically deficient RET activation-loop mutant lacking tyrosines. Structure-function analyses identified interactions between the JM hinge, αC helix, and an unconventional activation-loop serine phosphorylation site that engages the HRD motif and promotes phospho-tyrosine conformational accessibility and regulatory spine assembly. We demonstrate that this phospho-S909 arises from an intrinsic RET dual-specificity kinase activity and show that an equivalent serine is required for RET signaling in Drosophila. Our findings reveal dual-specificity and allosteric components for the mechanism of RET activation and signaling with direct implications for drug discovery.

  12. Software engineering the current practice

    Rajlich, Vaclav

    2011-01-01

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

  13. SigmaPlot 2000, Version 6.00, SPSS Inc. Computer Software Project Management, Requirements, and Design Document

    HURLBUT, S.T.

    2000-10-24

    SigmaPlot is a vendor software product that will be used to convert the area under an absorbance curve generated by a Fourier transform infrared spectrometer (FTIR) to a relative area. SigmaPlot will be used in conjunction with procedure ZA-565-301, ''Determination of Moisture by Supercritical Fluid Extraction and Infrared Detection.''

  14. Computing and software

    White, G. C.

    2004-06-01

    Full Text Available The reality is that the statistical methods used for analysis of data depend upon the availability of software. Analysis of marked animal data is no different than the rest of the statistical field. The methods used for analysis are those that are available in reliable software packages. Thus, the critical importance of having reliable, up–to–date software available to biologists is obvious. Statisticians have continued to develop more robust models, ever expanding the suite of potential analysis methods available. But without software to implement these newer methods, they will languish in the abstract, and not be applied to the problems deserving them. In the Computers and Software Session, two new software packages are described, a comparison of implementation of methods for the estimation of nest survival is provided, and a more speculative paper about how the next generation of software might be structured is presented. Rotella et al. (2004 compare nest survival estimation with different software packages: SAS logistic regression, SAS non–linear mixed models, and Program MARK. Nests are assumed to be visited at various, possibly infrequent, intervals. All of the approaches described compute nest survival with the same likelihood, and require that the age of the nest is known to account for nests that eventually hatch. However, each approach offers advantages and disadvantages, explored by Rotella et al. (2004. Efford et al. (2004 present a new software package called DENSITY. The package computes population abundance and density from trapping arrays and other detection methods with a new and unique approach. DENSITY represents the first major addition to the analysis of trapping arrays in 20 years. Barker & White (2004 discuss how existing software such as Program MARK require that each new model’s likelihood must be programmed specifically for that model. They wishfully think that future software might allow the user to combine

  15. The CSSIAR v.1.00 Software: A new tool based on SIAR to assess soil redistribution using Compound Specific Stable Isotopes

    de los Santos-Villalobos Sergio

    2017-01-01

    Full Text Available Soil erosion is one of the biggest challenges for food production around the world. Many techniques have been used to evaluate and mitigate soil degradation. Nowadays isotopic techniques are becoming a powerful tool to assess soil apportionment. One of the innovative techniques used is the Compound Specific Stable Isotopes (CSSI analysis, which has been used to track down sediments and specify their sources by the isotopic signature of δ13C in specific fatty acids. The application of this technique on soil apportionment has been recently developed, however there is a lack of user-friendly Software for data processing and interpretation. The aim of this article is to introduce a new open source tool for working with data sets generated by the use of the CSSI technique to assess soil apportionment, called the CSSIARv1.00 Software

  16. The CSSIAR v.1.00 Software: A new tool based on SIAR to assess soil redistribution using Compound Specific Stable Isotopes

    Sergio, de los Santos-Villalobos; Claudio, Bravo-Linares; dos Anjos Roberto, Meigikos; Renan, Cardoso; Max, Gibbs; Andrew, Swales; Lionel, Mabit; Gerd, Dercon

    Soil erosion is one of the biggest challenges for food production around the world. Many techniques have been used to evaluate and mitigate soil degradation. Nowadays isotopic techniques are becoming a powerful tool to assess soil apportionment. One of the innovative techniques used is the Compound Specific Stable Isotopes (CSSI) analysis, which has been used to track down sediments and specify their sources by the isotopic signature of δ13 C in specific fatty acids. The application of this technique on soil apportionment has been recently developed, however there is a lack of user-friendly Software for data processing and interpretation. The aim of this article is to introduce a new open source tool for working with data sets generated by the use of the CSSI technique to assess soil apportionment, called the CSSIARv1.00 Software

  17. Great software debates

    Davis, A

    2004-01-01

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

  18. Software Quality Assurance for Nuclear Safety Systems

    Sparkman, D R; Lagdon, R

    2004-01-01

    -critical software and applies the highest level of rigor for those systems. DOE has further defined a risk approach to nuclear safety system software consistent with the analyses required for operation of nuclear facilities. This requires the grading of software in terms of safety class and safety significant structures, systems and components (SSCs). Safety-class SSCs are related to public safety where as safety-significant SSCs are identified for specific aspects of defense-in-depth and worker safety. Industry standards do not directly categorize nuclear safety software and DOE sites are not consistent in their approach to nuclear safety software quality assurance. DOE is establishing a more detailed graded approach for software associated with safety class and safety significant systems. This paper presents the process and results that DOE utilized to develop a detailed classification scheme for nuclear safety software

  19. Agile Software Development

    Biju, Soly Mathew

    2008-01-01

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

  20. Economics of the specification 6M safety re-evaluation and regulatory requirements

    Hopper, C.M.

    1985-01-01

    The objective of this work was to examine the potential economic impact of the DOT Specification 6M criticality safety re-evaluation and regulatory requirements. The examination was based upon comparative analyses of current authorized fissile material load limits for the 6M, current Federal regulations (and interpretations) limiting the contents of Type B fissile material packages, limiting aggregates of fissile material packages, and recent proposed fissile material mass limits derived from specialized criticality safety analyses of the 6M package. The work examines influences on cost in transportation, handling, and storage of fissile materials. Depending upon facility throughput requirements (and assumed incremental costs of fissile material packaging, storage, and transport), operating, facility storage capacity, and transportation costs can be reduced significantly. As an example of the pricing algorithm application based upon reasonable cost influences, the magnitude of the first year cost reductions could extend beyond four times the cost of the packaging nuclear criticality safety re-evaluation. 1 tab

  1. A study to develop the domestic functional requirements of the specific safety systems of CANDU

    Kim, Man Woong [Korea Institute of Nuclear Safety, Taejon (Korea, Republic of); Lee, Jae Young; Park, Kun Chul [Handong Global Univ., Pohang (Korea, Republic of)] (and others)

    2003-03-15

    The present research has been made to develop and review critically the functional requirements of the specific safety systems of CANDU such as SDS-1, SDS2, ECCS, and containment. Based on R documents for this, a systematic study was made to develop the domestic regulation statements. Also, the conventional laws are carefully reviewed to see the compatibility to CANDU. Also, the safety assessment method for CANDU was studied by reviewing C documents and recommendation of IAEA. Through the present works, the vague policy in the CANDU safety regulation is cleaning up in a systematic form and a new frame to measure the objective risk of nuclear power plants was developed.

  2. Requirements, design and specifications of a multipurpose 7 Tesla NMR-system

    Mehlkopf, A.F.

    1978-01-01

    The requirements as well as the design and the specifications of a multi-purpose high resolution nuclear magnetic resonance spectrometer with superconducting magnet are described. The spectrometer operates at a magnetic fluxdensity of 7 Tesla and has 5 transmitter channels with 4 different frequencies, which can have values between 20 and 300 MHz. With this spectrometer almost all the current high resolution magnetic resonance techniques can be performed under computer control. It can also operate in the non-computer controlled slow passage mode. (Auth.)

  3. A study to develop the domestic functional requirements of the specific safety systems of CANDU

    Kim, Man Woong; Lee, Jae Young; Bang, Kwang Hyun [Handong Global Univ., Pohang (Korea, Republic of)] (and others)

    2001-03-15

    The present research has been made to develop and review critically the functional requirements of the specific safety systems of CANDU such as SOS-1, SOS-2, ECCS and containment. Based on R documents for this, a systematic study was made to develop the domestic regulation statements. Also, the conventional laws are carefully reviewed to see the compatibility to CANDU. Also, the safety assessment method for CANDU was studied by reviewing C documents and recommendation of IAEA. Through the present works, the vague policy in the CANDU safety regulation is cleaning up in a systematic form and a new frame to measure the objective risk of nuclear power plants was developed.

  4. Statistical Study to Check the Conformity of Aggregate in Kirkuk City to Requirement of Iraqi Specification

    Ammar Saleem Khazaal

    2018-01-01

    Full Text Available This research reviews a statistical study to check the conformity of aggregates (Coarse and Fine was used in Kirkuk city to the requirements of the Iraqi specifications. The data of sieve analysis (215 samples of aggregates being obtained from of National Central Construction Laboratory and Technical College Construction Laboratory in Kirkuk city have analyzed using the statistical program SAS. The results showed that 5%, 17%, and 18% of fine aggregate samples are passing sieve sizes 10 mm, 4.75 mm, and 2.36 mm, respectively, which were less than the minimum limit allowed by the Iraqi specifications for each sieve. The percentages passing sieve sizes 1.18mm, 600micrometers, and 300micrometers were more than the upper limit of specification by 5%, 20%, and 30% respectively. The samples were passing sieve sizes 1.18mm, and 600micrometers less than the minimum limit of specification by 17%, and 4%, respectively. The results showed that the deviation in a sieve size of 150 micrometers for the upper limit of the specification performs 2% of the total number of samples. For Coarse aggregate, the samples passing sieves size 37.5mm and 20mm were comforting the Iraqi specifications by 100% and 83% respectively, it has found that the samples were passing sieve sizes 10 mm was 5% was more than the higher limit of Iraqi specifications, and 27% of these samples were less than the minimum limit, whereas sample passing sieve size 5mm was 1% which is more than the upper limit of the Iraqi specification. As a result of statistical analysis of data for fine aggregate, it has found that the samples were passing sieve sizes 10 mm, 2.36 mm, 1.18 mm and 150micrometers conforming from statistical point of view the Iraqi specifications, whereas the samples were passing sieve sizes 4.75 mm, 600micrometers and 300 micrometers didn’t conform. Statistical analysis of the results of the coarse aggregates also showed that conforming to sieve sizes of 37.5 mm and 20 mm and

  5. Software Reviews.

    Kinnaman, Daniel E.; And Others

    1988-01-01

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

  6. Software Review.

    McGrath, Diane, Ed.

    1989-01-01

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

  7. Neurotransmitter Transporter-Like: a male germline-specific SLC6 transporter required for Drosophila spermiogenesis.

    Nabanita Chatterjee

    2011-01-01

    Full Text Available The SLC6 class of membrane transporters, known primarily as neurotransmitter transporters, is increasingly appreciated for its roles in nutritional uptake of amino acids and other developmentally specific functions. A Drosophila SLC6 gene, Neurotransmitter transporter-like (Ntl, is expressed only in the male germline. Mobilization of a transposon inserted near the 3' end of the Ntl coding region yields male-sterile mutants defining a single complementation group. Germline transformation with Ntl cDNAs under control of male germline-specific control elements restores Ntl/Ntl homozygotes to normal fertility, indicating that Ntl is required only in the germ cells. In mutant males, sperm morphogenesis appears normal, with elongated, individualized and coiled spermiogenic cysts accumulating at the base of the testes. However, no sperm are transferred to the seminal vesicle. The level of polyglycylation of Ntl mutant sperm tubulin appears to be significantly lower than that of wild type controls. Glycine transporters are the most closely related SLC6 transporters to Ntl, suggesting that Ntl functions as a glycine transporter in developing sperm, where augmentation of the cytosolic pool of glycine may be required for the polyglycylation of the massive amounts of tubulin in the fly's giant sperm. The male-sterile phenotype of Ntl mutants may provide a powerful genetic system for studying the function of an SLC6 transporter family in a model organism.

  8. Differential requirements for Gli2 and Gli3 in the regional specification of the mouse hypothalamus

    Roberta eHaddad-Tóvolli

    2015-03-01

    Full Text Available Secreted protein Sonic hedgehog (Shh ventralizes the neural tube by modulating the crucial balance between activating and repressing functions (GliA, GliR of transcription factors Gli2 and Gli3. This balance—the Shh-Gli code—is species- and context-dependent and has been elucidated for the mouse spinal cord. The hypothalamus, a forebrain region regulating vital functions like homeostasis and hormone secretion, shows dynamic and intricate Shh expression as well as complex regional differentiation. Here we asked if particular combinations of Gli2 and Gli3 and of GliA and GliR functions contribute to the variety of hypothalamic regions, i.e. we wanted to clarify the hypothalamic version of the Shh-Gli code. Based on mouse mutant analysis, we show that: 1 hypothalamic regional heterogeneity is based in part on differentially stringent requirements for Gli2 or Gli3; 2 another source of diversity are differential requirements for Shh of neural vs non-neural origin; 3 Gli2 is indispensable for the specification of a medial progenitor domain generating several essential hypothalamic nuclei plus the pituitary and median eminence; 4 the suppression of Gli3R by neural and non-neural Shh is essential for hypothalamic specification. Finally, we have mapped our results on a recent model which considers the hypothalamus as a transverse region with alar and basal portions. Our data confirm the model and are explained by it.

  9. Nodal-dependent mesendoderm specification requires the combinatorial activities of FoxH1 and Eomesodermin.

    Christopher E Slagle

    2011-05-01

    Full Text Available Vertebrate mesendoderm specification requires the Nodal signaling pathway and its transcriptional effector FoxH1. However, loss of FoxH1 in several species does not reliably cause the full range of loss-of-Nodal phenotypes, indicating that Nodal signals through additional transcription factors during early development. We investigated the FoxH1-dependent and -independent roles of Nodal signaling during mesendoderm patterning using a novel recessive zebrafish FoxH1 mutation called midway, which produces a C-terminally truncated FoxH1 protein lacking the Smad-interaction domain but retaining DNA-binding capability. Using a combination of gel shift assays, Nodal overexpression experiments, and genetic epistasis analyses, we demonstrate that midway more accurately represents a complete loss of FoxH1-dependent Nodal signaling than the existing zebrafish FoxH1 mutant schmalspur. Maternal-zygotic midway mutants lack notochords, in agreement with FoxH1 loss in other organisms, but retain near wild-type expression of markers of endoderm and various nonaxial mesoderm fates, including paraxial and intermediate mesoderm and blood precursors. We found that the activity of the T-box transcription factor Eomesodermin accounts for specification of these tissues in midway embryos. Inhibition of Eomesodermin in midway mutants severely reduces the specification of these tissues and effectively phenocopies the defects seen upon complete loss of Nodal signaling. Our results indicate that the specific combinations of transcription factors available for signal transduction play critical and separable roles in determining Nodal pathway output during mesendoderm patterning. Our findings also offer novel insights into the co-evolution of the Nodal signaling pathway, the notochord specification program, and the chordate branch of the deuterostome family of animals.

  10. A small asparagine-rich protein required for S-allele-specific pollen rejection in Nicotiana.

    McClure, B; Mou, B; Canevascini, S; Bernatzky, R

    1999-11-09

    Although S-locus RNases (S-RNases) determine the specificity of pollen rejection in self-incompatible (SI) solanaceous plants, they alone are not sufficient to cause S-allele-specific pollen rejection. To identify non-S-RNase sequences that are required for pollen rejection, a Nicotiana alata cDNA library was screened by differential hybridization. One clone, designated HT, hybridized strongly to RNA from N. alata styles but not to RNA from Nicotiana plumbaginifolia, a species known to lack one or more factors necessary for S-allele-specific pollen rejection. Sequence analysis revealed a 101-residue ORF including a putative secretion signal and an asparagine-rich domain near the C terminus. RNA blot analysis showed that the HT-transcript accumulates in the stigma and style before anthesis. The timing of HT-expression lags slightly behind S(C10)-RNase in SI N. alata S(C10)S(C10) and is well correlated with the onset of S-allele-specific pollen rejection in the style. An antisense-HT construct was prepared to test for a role in pollen rejection. Transformed (N. plumbaginifolia x SI N. alata S(C10)S(C10)) hybrids with reduced levels of HT-protein continued to express S(C10)-RNase but failed to reject S(C10)-pollen. Control hybrids expressing both S(C10)-RNase and HT-protein showed a normal S-allele-specific pollen rejection response. We conclude that HT-protein is directly implicated in pollen rejection.

  11. Context-specific requirements of functional domains of the Spectraplakin Short stop in vivo.

    Bottenberg, Wolfgang; Sanchez-Soriano, Natalia; Alves-Silva, Juliana; Hahn, Ines; Mende, Michael; Prokop, Andreas

    2009-07-01

    Spectraplakins are large multifunctional cytoskeletal interacting molecules implicated in various processes, including gastrulation, wound healing, skin blistering and neuronal degeneration. It has been speculated that the various functional domains and regions found in Spectraplakins are used in context-specific manners, a model which would provide a crucial explanation for the multifunctional nature of Spectraplakins. Here we tested this possibility by studying domain requirements of the Drosophila Spectraplakin Short stop (Shot) in three different cellular contexts in vivo: (1) neuronal growth, which requires dynamic actin-microtubule interaction; (2) formation and maintenance of tendon cells, which depends on highly stabilised arrays of actin filaments and microtubules, and (3) compartmentalisation in neurons, which is likely to involve cortical F-actin networks. Using these cellular contexts for rescue experiments with Shot deletion constructs in shot mutant background, a number of differential domain requirements were uncovered. First, binding of Shot to F-actin through the first Calponin domain is essential in neuronal contexts but dispensable in tendon cells. This finding is supported by our analyses of shot(kakP2) mutant embryos, which produce only endogenous isoforms lacking the first Calponin domain. Thus, our data demonstrate a functional relevance for these isoforms in vivo. Second, we provide the first functional role for the Plakin domain of Shot, which has a strong requirement for compartmentalisation in neurons and axonal growth, demonstrating that Plakin domains of long Spectraplakin isoforms are of functional relevance. Like the Calponin domain, also the Plakin domain is dispensable in tendon cells, and the currently assumed role of Shot as a linker of microtubules to the tendon cell surface may have to be reconsidered. Third, we demonstrate a function of Shot as an actin-microtubule linker in dendritic growth, thus shedding new light into

  12. Software requirements, design, and verification and validation for the FEHM application - a finite-element heat- and mass-transfer code

    Dash, Z.V.; Robinson, B.A.; Zyvoloski, G.A.

    1997-07-01

    The requirements, design, and verification and validation of the software used in the FEHM application, a finite-element heat- and mass-transfer computer code that can simulate nonisothermal multiphase multicomponent flow in porous media, are described. The test of the DOE Code Comparison Project, Problem Five, Case A, which verifies that FEHM has correctly implemented heat and mass transfer and phase partitioning, is also covered

  13. Requirements and prototype for supporting the planning of patient specific thermal ablation interventions

    Schramm, W.

    2010-01-01

    registration. Conclusion FEA is established as a robust technique for simulation and treatment outcome estimation for ablations. Because of the time required to simulate an ablation using FEA, it is not the technique of choice when used in a clinical setting. Since ablations are a time sensitive process, treatment planning must not impose additional effort on the physician. The simplified approach as defined during the course of the requirements engineering has received positive feedback and may be a suitable alternative to time consuming FEA simulations. Because of the free availability of the base software and the low hardware requirements, this solution is also ideally suited for medical training. (author)

  14. Views on Software Testability

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

    1994-01-01

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

  15. Runtime Instrumentation of SystemC/TLM2 Interfaces for Fault Tolerance Requirements Verification in Software Cosimulation

    Antonio da Silva

    2014-01-01

    Full Text Available This paper presents the design of a SystemC transaction level modelling wrapping library that can be used for the assertion of system properties, protocol compliance, or fault injection. The library uses C++ virtual table hooks as a dynamic binary instrumentation technique to inline wrappers in the TLM2 transaction path. This technique can be applied after the elaboration phase and needs neither source code modifications nor recompilation of the top level SystemC modules. The proposed technique has been successfully applied to the robustness verification of the on-board boot software of the Instrument Control Unit of the Solar Orbiter’s Energetic Particle Detector.

  16. Evolution of New cis-Regulatory Motifs Required for Cell-Specific Gene Expression in Caenorhabditis.

    Michalis Barkoulas

    2016-09-01

    Full Text Available Patterning of C. elegans vulval cell fates relies on inductive signaling. In this induction event, a single cell, the gonadal anchor cell, secretes LIN-3/EGF and induces three out of six competent precursor cells to acquire a vulval fate. We previously showed that this developmental system is robust to a four-fold variation in lin-3/EGF genetic dose. Here using single-molecule FISH, we find that the mean level of expression of lin-3 in the anchor cell is remarkably conserved. No change in lin-3 expression level could be detected among C. elegans wild isolates and only a low level of change-less than 30%-in the Caenorhabditis genus and in Oscheius tipulae. In C. elegans, lin-3 expression in the anchor cell is known to require three transcription factor binding sites, specifically two E-boxes and a nuclear-hormone-receptor (NHR binding site. Mutation of any of these three elements in C. elegans results in a dramatic decrease in lin-3 expression. Yet only a single E-box is found in the Drosophilae supergroup of Caenorhabditis species, including C. angaria, while the NHR-binding site likely only evolved at the base of the Elegans group. We find that a transgene from C. angaria bearing a single E-box is sufficient for normal expression in C. elegans. Even a short 58 bp cis-regulatory fragment from C. angaria with this single E-box is able to replace the three transcription factor binding sites at the endogenous C. elegans lin-3 locus, resulting in the wild-type expression level. Thus, regulatory evolution occurring in cis within a 58 bp lin-3 fragment, results in a strict requirement for the NHR binding site and a second E-box in C. elegans. This single-cell, single-molecule, quantitative and functional evo-devo study demonstrates that conserved expression levels can hide extensive change in cis-regulatory site requirements and highlights the evolution of new cis-regulatory elements required for cell-specific gene expression.

  17. Software qualification for digital safety system in KNICS project

    Kwon, Kee-Choon; Lee, Dong-Young; Choi, Jong-Gyun

    2012-01-01

    In order to achieve technical self-reliance in the area of nuclear instrumentation and control, the Korea Nuclear Instrumentation and Control System (KNICS) project had been running for seven years from 2001. The safety-grade Programmable Logic Controller (PLC) and the digital safety system were developed by KNICS project. All the software of the PLC and digital safety system were developed and verified following the software development life cycle Verification and Validation (V and V) procedure. The main activities of the V and V process are preparation of software planning documentations, verification of the Software Requirement Specification (SRS), Software Design Specification (SDS) and codes, and a testing of the software components, the integrated software, and the integrated system. In addition, a software safety analysis and a software configuration management are included in the activities. For the software safety analysis at the SRS and SDS phases, the software Hazard Operability (HAZOP) was performed and then the software fault tree analysis was applied. The software fault tree analysis was applied to a part of software module with some critical defects identified by the software HAZOP in SDS phase. The software configuration management was performed using the in-house tool developed in the KNICS project. (author)

  18. Paladin Software Support Lab

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

  19. Spotting software errors sooner

    Munro, D.

    1989-01-01

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

  20. Automated Software Testing : A Study of the State of Practice

    Rafi, Dudekula Mohammad; Reddy, Kiran Moses Katam

    2012-01-01

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

  1. 49 CFR 173.427 - Transport requirements for low specific activity (LSA) Class 7 (radioactive) materials and...

    2010-10-01

    ... 49 Transportation 2 2010-10-01 2010-10-01 false Transport requirements for low specific activity... SHIPMENTS AND PACKAGINGS Class 7 (Radioactive) Materials § 173.427 Transport requirements for low specific... must be transported in accordance with the following conditions: (1) The external dose rate may not...

  2. Workflow-Based Software Development Environment

    Izygon, Michel E.

    2013-01-01

    The Software Developer's Assistant (SDA) helps software teams more efficiently and accurately conduct or execute software processes associated with NASA mission-critical software. SDA is a process enactment platform that guides software teams through project-specific standards, processes, and procedures. Software projects are decomposed into all of their required process steps or tasks, and each task is assigned to project personnel. SDA orchestrates the performance of work required to complete all process tasks in the correct sequence. The software then notifies team members when they may begin work on their assigned tasks and provides the tools, instructions, reference materials, and supportive artifacts that allow users to compliantly perform the work. A combination of technology components captures and enacts any software process use to support the software lifecycle. It creates an adaptive workflow environment that can be modified as needed. SDA achieves software process automation through a Business Process Management (BPM) approach to managing the software lifecycle for mission-critical projects. It contains five main parts: TieFlow (workflow engine), Business Rules (rules to alter process flow), Common Repository (storage for project artifacts, versions, history, schedules, etc.), SOA (interface to allow internal, GFE, or COTS tools integration), and the Web Portal Interface (collaborative web environment

  3. The MINERVA Software Development Process

    Narkawicz, Anthony; Munoz, Cesar A.; Dutle, Aaron M.

    2017-01-01

    This paper presents a software development process for safety-critical software components of cyber-physical systems. The process is called MINERVA, which stands for Mirrored Implementation Numerically Evaluated against Rigorously Verified Algorithms. The process relies on formal methods for rigorously validating code against its requirements. The software development process uses: (1) a formal specification language for describing the algorithms and their functional requirements, (2) an interactive theorem prover for formally verifying the correctness of the algorithms, (3) test cases that stress the code, and (4) numerical evaluation on these test cases of both the algorithm specifications and their implementations in code. The MINERVA process is illustrated in this paper with an application to geo-containment algorithms for unmanned aircraft systems. These algorithms ensure that the position of an aircraft never leaves a predetermined polygon region and provide recovery maneuvers when the region is inadvertently exited.

  4. Direct effects of ionizing radiation on integral membrane proteins. Noncovalent energy transfer requires specific interpeptide interactions

    Jhun, E.; Jhun, B.H.; Jones, L.R.; Jung, C.Y.

    1991-01-01

    The 12 transmembrane alpha helices (TMHs) of human erythrocyte glucose transporter were individually cut by pepsin digestion as membrane-bound 2.5-3.5-kDa peptide fragments. Radiation-induced chemical degradation of these fragments showed an average target size of 34 kDa. This is 10-12 x larger than the average size of an individual TMH, demonstrating that a significant energy transfer occurs among these TMHs in the absence of covalent linkage. Heating this TMH preparation at 100 degree C for 15 min reduced the target size to 5 kDa or less, suggesting that the noncovalent energy transfer requires specific helix-helix interactions. Purified phospholamban, a small (6-kDa) integral membrane protein containing a single TMH, formed a pentameric assembly in sodium dodecyl sulfate. The chemical degradation target size of this phospholamban pentamer was 5-6 kDa, illustrating that not all integral membrane protein assemblies permit intersubunit energy transfer. These findings together with other published observations suggest strongly that significant noncovalent energy transfer can occur within the tertiary and quaternary structure of membrane proteins and that as yet undefined proper molecular interactions are required for such covalent energy transfer. Our results with pepsin-digested glucose transporter also illustrate the importance of the interhelical interaction as a predominating force in maintaining the tertiary structure of a transmembrane protein

  5. Recommendations for equipment requirements and specifications for digital and interventional radiology: Dosimetric aspects

    Suliman, I.I.; Zoetelief, J.

    2002-01-01

    The recognition of radiation induced injuries from fluoroscopically guided interventional procedures has resulted in the current demand for development of recommendations and standards to limit dose to both patients and staff. This paper outlines the recommendations drafted within the framework of European Project DIMOND III. The actual work involves survey and review of national and international documents as well as scientific publications in areas relevant to the digital and/or interventional radiology with an aim of developing recommendations for equipment requirements and specifications for digital and interventional radiology. A pilot study of experimental investigations in at least three hospitals will be conducted to test the requirements and the specifications, the result of which will be presented. The recommendations are expected to provide an effective means of dose reduction to both patients and staff while maintaining image quality adequate for the specific diagnosis or interventional procedure. Different components of x-ray systems that have direct impact on patient and staff doses have been considered. Where necessary a compromise between patient dose and image quality has been made. The dosimetric aspects of the recommendations propose detailed descriptions and limits to dosimetric information relevant to patient and staff doses. International recommendations on maximum patient entrance surface dose rate vary in the range from 25 to 65 mGy.min -1 for normal mode fluoroscopy. Maximum image intensifier or image receptor input dose rate around 0.1 Gy min -1 at a distance 30 cm from the image intensifier input surface has been generally recommended. Maximum fluoroscopic dose rate in air must not exceed 50 mGy.min -1 at a location depending on the configuration e.g. for undertable x-ray tube at 10 mm from the patient support on the patient side of the support. The use of pulsed fluoroscopy or low dose fluoroscopy is proposed as good options to minimize

  6. Business engineering. Generic Software Architecture in an Object Oriented View

    Mihaela MURESAN

    2006-01-01

    Full Text Available The generic software architecture offers a solution for the the information system's development and implementation. A generic software/non-software model could be developed by integrating the enterprise blueprint concept (Zachman and the object oriented paradigm (Coad's archetype concept. The standardization of the generic software architecture for various specific software components could be a direction of crucial importance, offering the guarantee of the quality of the model and increasing the efficiency of the design, development and implementation of the software. This approach is also useful for the implementation of the ERP systems designed to fit the user’s particular requirements.

  7. 40 CFR 152.95 - Citation of all studies in the Agency's files pertinent to a specific data requirement.

    2010-07-01

    ... PROCEDURES Procedures To Ensure Protection of Data Submitters' Rights § 152.95 Citation of all studies in the... requirement. The applicant who selects this cite-all option must submit to the Agency: (a) A general offer to... may be limited to apply only to data pertinent to the specific data requirement(s) for which the cite...

  8. Software testing in roughness calculation

    Chen, Y L; Hsieh, P F; Fu, W E

    2005-01-01

    A test method to determine the function quality provided by the software for roughness measurement is presented in this study. The function quality of the software requirements should be part of and assessed through the entire life cycle of the software package. The specific function, or output accuracy, is crucial for the analysis of the experimental data. For scientific applications, however, commercial software is usually embedded with specific instrument, which is used for measurement or analysis during the manufacture process. In general, the error ratio caused by the software would be more apparent especially when dealing with relatively small quantities, like the measurements in the nanometer-scale range. The model of 'using a data generator' proposed by NPL of UK was applied in this study. An example of the roughness software is tested and analyzed by the above mentioned process. After selecting the 'reference results', the 'reference data' was generated by a programmable 'data generator'. The filter function of 0.8 mm long cutoff value, defined in ISO 11562 was tested with 66 sinusoid data at different wavelengths. Test results from commercial software and CMS written program were compared to the theoretical data calculated from ISO standards. As for the filter function in this software, the result showed a significant disagreement between the reference and test results. The short cutoff feature for filtering at the high frequencies does not function properly, while the long cutoff feature has the maximum difference in the filtering ratio, which is more than 70% between the wavelength of 300 μm and 500 μm. Conclusively, the commercial software needs to be tested more extensively for specific application by appropriate design of reference dataset to ensure its function quality

  9. Tools for Embedded Computing Systems Software

    1978-01-01

    A workshop was held to assess the state of tools for embedded systems software and to determine directions for tool development. A synopsis of the talk and the key figures of each workshop presentation, together with chairmen summaries, are presented. The presentations covered four major areas: (1) tools and the software environment (development and testing); (2) tools and software requirements, design, and specification; (3) tools and language processors; and (4) tools and verification and validation (analysis and testing). The utility and contribution of existing tools and research results for the development and testing of embedded computing systems software are described and assessed.

  10. Example of software configuration management model

    Roth, P.

    2006-01-01

    Software configuration management is the mechanism used to track and control software changes and may include the following actions: A tracking system should be established for any changes made to the existing software configuration. Requirement of the configuration management system are the following: - Backup the different software configuration; - Record the details (the date, the subject, the filenames, the supporting documents, the tests, ...) of the changes introduced in the new configuration; - Document all the differences between the different versions. Configuration management allows simultaneous exploitation of one specific version and development of the next version. Minor correction can be perform in the current exploitation version

  11. Verification and validation process for the safety software in KNICS

    Kwon, Kee-Choon; Lee, Jang-Soo; Kim, Jang-Yeol

    2004-01-01

    This paper describes the Verification and Validation (V and V ) process for safety software of Programmable Logic Controller (PLC), Digital Reactor Protection System (DRPS), and Engineered Safety Feature-Component Control System (ESF-CCS) that are being developed in Korea Nuclear Instrumentation and Control System (KNICS) projects. Specifically, it presents DRPS V and V experience according to the software development life cycle. The main activities of DRPS V and V process are preparation of software planning documentation, verification of Software Requirement Specification (SRS), Software Design Specification (SDS) and codes, and testing of the integrated software and the integrated system. In addition, they include software safety analysis and software configuration management. SRS V and V of DRPS are technical evaluation, licensing suitability evaluation, inspection and traceability analysis, formal verification, preparing integrated system test plan, software safety analysis, and software configuration management. Also, SDS V and V of RPS are technical evaluation, licensing suitability evaluation, inspection and traceability analysis, formal verification, preparing integrated software test plan, software safety analysis, and software configuration management. The code V and V of DRPS are traceability analysis, source code inspection, test case and test procedure generation, software safety analysis, and software configuration management. Testing is the major V and V activity of software integration and system integration phase. Software safety analysis at SRS phase uses Hazard Operability (HAZOP) method, at SDS phase it uses HAZOP and Fault Tree Analysis (FTA), and at implementation phase it uses FTA. Finally, software configuration management is performed using Nu-SCM (Nuclear Software Configuration Management) tool developed by KNICS project. Through these activities, we believe we can achieve the functionality, performance, reliability and safety that are V

  12. Software Dependability and Safety Evaluations ESA's Initiative

    Hernek, M.

    ESA has allocated funds for an initiative to evaluate Dependability and Safety methods of Software. The objectives of this initiative are; · More extensive validation of Safety and Dependability techniques for Software · Provide valuable results to improve the quality of the Software thus promoting the application of Dependability and Safety methods and techniques. ESA space systems are being developed according to defined PA requirement specifications. These requirements may be implemented through various design concepts, e.g. redundancy, diversity etc. varying from project to project. Analysis methods (FMECA. FTA, HA, etc) are frequently used during requirements analysis and design activities to assure the correct implementation of system PA requirements. The criticality level of failures, functions and systems is determined and by doing that the critical sub-systems are identified, on which dependability and safety techniques are to be applied during development. Proper performance of the software development requires the development of a technical specification for the products at the beginning of the life cycle. Such technical specification comprises both functional and non-functional requirements. These non-functional requirements address characteristics of the product such as quality, dependability, safety and maintainability. Software in space systems is more and more used in critical functions. Also the trend towards more frequent use of COTS and reusable components pose new difficulties in terms of assuring reliable and safe systems. Because of this, its dependability and safety must be carefully analysed. ESA identified and documented techniques, methods and procedures to ensure that software dependability and safety requirements are specified and taken into account during the design and development of a software system and to verify/validate that the implemented software systems comply with these requirements [R1].

  13. Software Engineering Improvement Plan

    2006-01-01

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

  14. Niche-Specific Requirement for Hyphal Wall protein 1 in Virulence of Candida albicans

    Staab, Janet F.; Datta, Kausik; Rhee, Peter

    2013-01-01

    Specialized Candida albicans cell surface proteins called adhesins mediate binding of the fungus to host cells. The mammalian transglutaminase (TG) substrate and adhesin, Hyphal wall protein 1 (Hwp1), is expressed on the hyphal form of C. albicans where it mediates fungal adhesion to epithelial cells. Hwp1 is also required for biofilm formation and mating thus the protein functions in both fungal-host and self-interactions. Hwp1 is required for full virulence of C. albicans in murine models of disseminated candidiasis and of esophageal candidiasis. Previous studies correlated TG activity on the surface of oral epithelial cells, produced by epithelial TG (TG1), with tight binding of C. albicans via Hwp1 to the host cell surfaces. However, the contribution of other Tgs, specifically tissue TG (TG2), to disseminated candidiasis mediated by Hwp1 was not known. A newly created hwp1 null strain in the wild type SC5314 background was as virulent as the parental strain in C57BL/6 mice, and virulence was retained in C57BL/6 mice deleted for Tgm2 (TG2). Further, the hwp1 null strains displayed modestly reduced virulence in BALB/c mice as did strain DD27-U1, an independently created hwp1Δ/Δ in CAI4 corrected for its ura3Δ defect at the URA3 locus. Hwp1 was still needed to produce wild type biofilms, and persist on murine tongues in an oral model of oropharyngeal candidiasis consistent with previous studies by us and others. Finally, lack of Hwp1 affected the translocation of C. albicans from the mouse intestine into the bloodstream of mice. Together, Hwp1 appears to have a minor role in disseminated candidiasis, independent of tissue TG, but a key function in host- and self-association to the surface of oral mucosa. PMID:24260489

  15. The rapidly evolving centromere-specific histone has stringent functional requirements in Arabidopsis thaliana.

    Ravi, Maruthachalam; Kwong, Pak N; Menorca, Ron M G; Valencia, Joel T; Ramahi, Joseph S; Stewart, Jodi L; Tran, Robert K; Sundaresan, Venkatesan; Comai, Luca; Chan, Simon W-L

    2010-10-01

    Centromeres control chromosome inheritance in eukaryotes, yet their DNA structure and primary sequence are hypervariable. Most animals and plants have megabases of tandem repeats at their centromeres, unlike yeast with unique centromere sequences. Centromere function requires the centromere-specific histone CENH3 (CENP-A in human), which replaces histone H3 in centromeric nucleosomes. CENH3 evolves rapidly, particularly in its N-terminal tail domain. A portion of the CENH3 histone-fold domain, the CENP-A targeting domain (CATD), has been previously shown to confer kinetochore localization and centromere function when swapped into human H3. Furthermore, CENP-A in human cells can be functionally replaced by CENH3 from distantly related organisms including Saccharomyces cerevisiae. We have used cenh3-1 (a null mutant in Arabidopsis thaliana) to replace endogenous CENH3 with GFP-tagged variants. A H3.3 tail domain-CENH3 histone-fold domain chimera rescued viability of cenh3-1, but CENH3's lacking a tail domain were nonfunctional. In contrast to human results, H3 containing the A. thaliana CATD cannot complement cenh3-1. GFP-CENH3 from the sister species A. arenosa functionally replaces A. thaliana CENH3. GFP-CENH3 from the close relative Brassica rapa was targeted to centromeres, but did not complement cenh3-1, indicating that kinetochore localization and centromere function can be uncoupled. We conclude that CENH3 function in A. thaliana, an organism with large tandem repeat centromeres, has stringent requirements for functional complementation in mitosis.

  16. Object Oriented Modeling : A method for combining model and software development

    Van Lelyveld, W.

    2010-01-01

    When requirements for a new model cannot be met by available modeling software, new software can be developed for a specific model. Methods for the development of both model and software exist, but a method for combined development has not been found. A compatible way of thinking is required to

  17. PL-DA-PS: A hardware architecture and software toolbox for neurophysiology requiring complex visual stimuli and online behavioral control

    Kyler M. Eastman

    2012-01-01

    Full Text Available Neurophysiological studies in awake, behaving primates (both human and nonhuman primates have focused with increasing scrutiny on the temporal relationship between neural signals and behaviors. Consequently, laboratories are often faced with the problem of developing experimental equipment that can support data recording with high temporal precision and also be flexible enough to accommodate a wide variety of experimental paradigms. To this end, we have developed an architecture that integrates several modern pieces of equipment, but still grants experimenters a high degree of flexibility. Our hardware architecture and software tools take advantage of three popular and powerful technologies: the PLexon apparatus for neurophysiological recordings (Plexon, Inc., Dallas TX, a DAtapixx box (Vpixx Technologies, Saint-Bruno, QC, Canada for analog, digital, and video signal input-output control, and the PSychtoolbox MATLAB toolbox for stimulus generation (Brainard, 1997. The PL-DA-PS (Platypus system is designed to support the study of the visual systems of awake, behaving primates during multi-electrode neurophysiological recordings, but can be easily applied to other related domains. Despite its wide range of capabilities and support for cutting-edge video displays and neural recording systems, the PLDAPS system is simple enough for someone with basic MATLAB programming skills to design their own experiments.

  18. 78 FR 30245 - Electric Reliability Organization Interpretation of Specific Requirements of the Disturbance...

    2013-05-22

    ... contingency reserve policy; and (3) refers to the ERO rather than the NERC Operating Committee in Requirements... the proposed interpretation, Requirements R3 and R4 provide: R3. Each Balancing Authority or Reserve... Requirement R4 requires that: ``[A] Balancing Authority or Reserve Sharing Group shall meet the Disturbance...

  19. Diverse Requirements for Microglial Survival, Specification, and Function Revealed by Defined-Medium Cultures.

    Bohlen, Christopher J; Bennett, F Chris; Tucker, Andrew F; Collins, Hannah Y; Mulinyawe, Sara B; Barres, Ben A

    2017-05-17

    Microglia, the resident macrophages of the CNS, engage in various CNS-specific functions that are critical for development and health. To better study microglia and the properties that distinguish them from other tissue macrophage populations, we have optimized serum-free culture conditions to permit robust survival of highly ramified adult microglia under defined-medium conditions. We find that astrocyte-derived factors prevent microglial death ex vivo and that this activity results from three primary components, CSF-1/IL-34, TGF-β2, and cholesterol. Using microglial cultures that have never been exposed to serum, we demonstrate a dramatic and lasting change in phagocytic capacity after serum exposure. Finally, we find that mature microglia rapidly lose signature gene expression after isolation, and that this loss can be reversed by engrafting cells back into an intact CNS environment. These data indicate that the specialized gene expression profile of mature microglia requires continuous instructive signaling from the intact CNS. Copyright © 2017 Elsevier Inc. All rights reserved.

  20. Comparación de efectividad de las técnicas de educción de requisitos software: visión novel y experta Comparison on effectiveness of the software requirements elicitation techniques: novice and expert vision

    Dante Carrizo Moreno

    2012-12-01

    Full Text Available La Ingeniería de Requisitos puede hacer uso de una gran cantidad de técnicas para educir las necesidades de los usuarios. No obstante, apenas existen guías y criterios prácticos para realizar la selección de técnicas en un proyecto de desarrollo de software. Este artículo intenta conocer la visión que tienen los ingenieros de requisitos noveles acerca de la efectividad de las técnicas de educción y compararlas con la visión de expertos en requisitos. Para efectuar la comparación se utiliza la técnica de emparrillado que permite conocer indirectamente la opinión de los sujetos respecto de las técnicas. Los resultados muestran una sustancial diferencia entre ambas visiones respecto a la efectividad de las técnicas y contexto de la educción. Esto implica que una más amplia formación, y principalmente práctica, es necesaria para que los ingenieros noveles puedan reconocer diferencias de efectividad de las técnicas y poder decidir con mayor certeza sobre las técnicas más adecuadas a utilizar en las sesiones de educción de requisitos.Requirements engineering can use a lot of techniques to gather the users' needs. However, currently there are few practical guidelines and criteria for selecting techniques in a software development project. This paper tries to know the vision that novice requirements engineers have about the effectiveness of requirements elicitation techniques and compare it with the requirements experts' vision. To carry out the comparison, repertory grid technique was used. This technique allows knowing indirectly the subject's opinion on the techniques. The results show a substantial difference between both visions with regard to the techniques and elicitation context. This implies that a more extensive training, and primarily practice, is necessary in order for novice engineers to recognize differences in techniques effectiveness and decide with greater certainty about the most appropriate techniques to use in

  1. Software Quality Assurance Metrics

    McRae, Kalindra A.

    2004-01-01

    Software Quality Assurance (SQA) is a planned and systematic set of activities that ensures conformance of software life cycle processes and products conform to requirements, standards and procedures. In software development, software quality means meeting requirements and a degree of excellence and refinement of a project or product. Software Quality is a set of attributes of a software product by which its quality is described and evaluated. The set of attributes includes functionality, reliability, usability, efficiency, maintainability, and portability. Software Metrics help us understand the technical process that is used to develop a product. The process is measured to improve it and the product is measured to increase quality throughout the life cycle of software. Software Metrics are measurements of the quality of software. Software is measured to indicate the quality of the product, to assess the productivity of the people who produce the product, to assess the benefits derived from new software engineering methods and tools, to form a baseline for estimation, and to help justify requests for new tools or additional training. Any part of the software development can be measured. If Software Metrics are implemented in software development, it can save time, money, and allow the organization to identify the caused of defects which have the greatest effect on software development. The summer of 2004, I worked with Cynthia Calhoun and Frank Robinson in the Software Assurance/Risk Management department. My task was to research and collect, compile, and analyze SQA Metrics that have been used in other projects that are not currently being used by the SA team and report them to the Software Assurance team to see if any metrics can be implemented in their software assurance life cycle process.

  2. Strategic Mobility 21, Inland Port - Multi-Modal Terminal Operating System Design Specification

    Mallon, Lawrence G; Dougherty, Edmond J

    2007-01-01

    ...) Specification identifies technical and functional requirements for procuring and integrating services required for a multi-modal node operating software system operating within a Service Oriented Architecture (SOA...

  3. Software Architecture Evolution

    Barnes, Jeffrey M.

    2013-01-01

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

  4. Requirement for Pdx1 in specification of latent endocrine progenitors in zebrafish

    Ellertsdottir Elin

    2011-10-01

    Full Text Available Abstract Background Insulin-producing beta cells emerge during pancreas development in two sequential waves. Recently described later-forming beta cells in zebrafish show high similarity to second wave mammalian beta cells in developmental capacity. Loss-of-function studies in mouse and zebrafish demonstrated that the homeobox transcription factors Pdx1 and Hb9 are both critical for pancreas and beta cell development and discrete stage-specific requirements for these genes have been uncovered. Previously, exocrine and endocrine cell recovery was shown to follow loss of pdx1 in zebrafish, but the progenitor cells and molecular mechanisms responsible have not been clearly defined. In addition, interactions of pdx1 and hb9 in beta cell formation have not been addressed. Results To learn more about endocrine progenitor specification, we examined beta cell formation following morpholino-mediated depletion of pdx1 and hb9. We find that after early beta cell reduction, recovery occurs following loss of either pdx1 or hb9 function. Unexpectedly, simultaneous knockdown of both hb9 and pdx1 leads to virtually complete and persistent beta cell deficiency. We used a NeuroD:EGFP transgenic line to examine endocrine cell behavior in vivo and developed a novel live-imaging technique to document emergence and migration of late-forming endocrine precursors in real time. Our data show that Notch-responsive progenitors for late-arising endocrine cells are predominantly post mitotic and depend on pdx1. By contrast, early-arising endocrine cells are specified and differentiate independent of pdx1. Conclusions The nearly complete beta cell deficiency after combined loss of hb9 and pdx1 suggests functional cooperation, which we clarify as distinct roles in early and late endocrine cell formation. A novel imaging approach permitted visualization of the emergence of late endocrine cells within developing embryos for the first time. We demonstrate a pdx1-dependent

  5. Computer software quality assurance

    Ives, K.A.

    1986-06-01

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

  6. SB certification handout material requirements, test methods, responsibilities, and minimum classification levels for mixture-based specification for flexible base.

    2012-10-01

    A handout with tables representing the material requirements, test methods, responsibilities, and minimum classification levels mixture-based specification for flexible base and details on aggregate and test methods employed, along with agency and co...

  7. Transcription factor Tbx3 is required for the specification of the atrioventricular conduction system

    Bakker, Martijn L.; Boukens, Bastiaan J.; Mommersteeg, Mathilda T. M.; Brons, Janynke F.; Wakker, Vincent; Moorman, Antoon F. M.; Christoffels, Vincent M.

    2008-01-01

    The cardiac conduction system consists of distinctive heart muscle cells that initiate and propagate the electric impulse required for coordinated contraction. The conduction system expresses the transcriptional repressor Tbx3, which is required for vertebrate development and controls the formation

  8. Development of requirements and functional specifications for crash event data recorders : final report

    2004-12-01

    The U.S. DOT has conducted research on the requirements for a Crash Event Data Recorder to facilitate the reconstruction of commercial motor vehicle crashes. This report documents the work performed on the Development of Requirements and Functiona...

  9. 49 CFR 179.201 - Individual specification requirements applicable to non-pressure tank car tanks.

    2010-10-01

    ... to non-pressure tank car tanks. 179.201 Section 179.201 Transportation Other Regulations Relating to... MATERIALS REGULATIONS SPECIFICATIONS FOR TANK CARS Specifications for Non-Pressure Tank Car Tanks (Classes... car tanks. ...

  10. EDS operator and control software

    Ott, L.L.

    1985-04-01

    The Enrichment Diagnostic System (EDS) was developed at Lawrence Livermore National Laboratory (LLNL) to acquire, display and analyze large quantities of transient data for a real-time Advanced Vapor Laser Isotope Separation (AVLIS) experiment. Major topics discussed in this paper are the EDS operator interface (SHELL) program, the data acquisition and analysis scheduling software, and the graphics software. The workstation concept used in EDS, the software used to configure a user's workstation, and the ownership and management of a diagnostic are described. An EDS diagnostic is a combination of hardware and software designed to study specific aspects of the process. Overall system performance is discussed from the standpoint of scheduling techniques, evaluation tools, optimization techniques, and program-to-program communication methods. EDS is based on a data driven design which keeps the need to modify software to a minimum. This design requires a fast and reliable data base management system. A third party data base management product, Berkeley Software System Database, written explicitly for HP1000's, is used for all EDS data bases. All graphics is done with an in-house graphics product, Device Independent Graphics Library (DIGLIB). Examples of devices supported by DIGLIB are: Versatec printer/plotters, Raster Technologies Graphic Display Controllers, and HP terminals (HP264x and HP262x). The benefits derived by using HP hardware and software as well as obstacles imposed by the HP environment are presented in relation to EDS development and implementation

  11. Software Innovation in a Mission Critical Environment

    Fredrickson, Steven

    2015-01-01

    Operating in mission-critical environments requires trusted solutions, and the preference for "tried and true" approaches presents a potential barrier to infusing innovation into mission-critical systems. This presentation explores opportunities to overcome this barrier in the software domain. It outlines specific areas of innovation in software development achieved by the Johnson Space Center (JSC) Engineering Directorate in support of NASA's major human spaceflight programs, including International Space Station, Multi-Purpose Crew Vehicle (Orion), and Commercial Crew Programs. Software engineering teams at JSC work with hardware developers, mission planners, and system operators to integrate flight vehicles, habitats, robotics, and other spacecraft elements for genuinely mission critical applications. The innovations described, including the use of NASA Core Flight Software and its associated software tool chain, can lead to software that is more affordable, more reliable, better modelled, more flexible, more easily maintained, better tested, and enabling of automation.

  12. Software engineer's pocket book

    Tooley, Michael

    2013-01-01

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

  13. The Paradox of "Structured" Methods for Software Requirements Management: A Case Study of an e-Government Development Project

    Conboy, Kieran; Lang, Michael

    This chapter outlines the alternative perspectives of "rationalism" and "improvisation" within information systems development and describes the major shortcomings of each. It then discusses how these shortcomings manifested themselves within an e-government case study where a "structured" requirements management method was employed. Although this method was very prescriptive and firmly rooted in the "rational" paradigm, it was observed that users often resorted to improvised behaviour, such as privately making decisions on how certain aspects of the method should or should not be implemented.

  14. Self-assembling software generator

    Bouchard, Ann M [Albuquerque, NM; Osbourn, Gordon C [Albuquerque, NM

    2011-11-25

    A technique to generate an executable task includes inspecting a task specification data structure to determine what software entities are to be generated to create the executable task, inspecting the task specification data structure to determine how the software entities will be linked after generating the software entities, inspecting the task specification data structure to determine logic to be executed by the software entities, and generating the software entities to create the executable task.

  15. NASA Software Engineering Benchmarking Study

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

    2013-01-01

    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

  16. Towards Archetypes-Based Software Development

    Piho, Gunnar; Roost, Mart; Perkins, David; Tepandi, Jaak

    We present a framework for the archetypes based engineering of domains, requirements and software (Archetypes-Based Software Development, ABD). An archetype is defined as a primordial object that occurs consistently and universally in business domains and in business software systems. An archetype pattern is a collaboration of archetypes. Archetypes and archetype patterns are used to capture conceptual information into domain specific models that are utilized by ABD. The focus of ABD is on software factories - family-based development artefacts (domain specific languages, patterns, frameworks, tools, micro processes, and others) that can be used to build the family members. We demonstrate the usage of ABD for developing laboratory information management system (LIMS) software for the Clinical and Biomedical Proteomics Group, at the Leeds Institute of Molecular Medicine, University of Leeds.

  17. Qualification of safety-critical software for digital reactor safety system in nuclear power plants

    Kwon, Kee-Choon; Park, Gee-Yong; Kim, Jang-Yeol; Lee, Jang-Soo

    2013-01-01

    This paper describes the software qualification activities for the safety-critical software of the digital reactor safety system in nuclear power plants. The main activities of the software qualification processes are the preparation of software planning documentations, verification and validation (V and V) of the software requirements specifications (SRS), software design specifications (SDS) and codes, and the testing of the integrated software and integrated system. Moreover, the software safety analysis and software configuration management are involved in the software qualification processes. The V and V procedure for SRS and SDS contains a technical evaluation, licensing suitability evaluation, inspection and traceability analysis, formal verification, software safety analysis, and an evaluation of the software configuration management. The V and V processes for the code are a traceability analysis, source code inspection, test case and test procedure generation. Testing is the major V and V activity of the software integration and system integration phases. The software safety analysis employs a hazard operability method and software fault tree analysis. The software configuration management in each software life cycle is performed by the use of a nuclear software configuration management tool. Through these activities, we can achieve the functionality, performance, reliability, and safety that are the major V and V objectives of the safety-critical software in nuclear power plants. (author)

  18. HAZARD ANALYSIS SOFTWARE

    Sommer, S; Tinh Tran, T.

    2008-01-01

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

  19. Modular Software Performance Monitoring

    Kruse, D F

    2011-01-01

    CPU clock frequency is not likely to be increased significantly in the coming years, and data analysis speed can be improved by using more processors or buying new machines, only if one is willing to change the paradigm to a parallel one. Therefore, performance monitoring procedures and tools are needed to help programmers to optimize existing software running on current and future hardware. Low level information from hardware performance counters is vital to spot specific performance problems slowing program execution. HEP software is often huge and complex, and existing tools are unable to give results with the required granularity. We will report on the approach we have chose to solve this problem that involves decomposing the application into parts and monitoring each of them separately. Both counting and sampling methods are used to allow an analysis with the required custom granularity: from global level, up to the function level. A set of tools (based on perfmon2 – a software interface to hardware co...

  20. From Software Development to Software Assembly

    Sneed, Harry M.; Verhoef, Chris

    2016-01-01

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

  1. Software as a service approach to sensor simulation software deployment

    Webster, Steven; Miller, Gordon; Mayott, Gregory

    2012-05-01

    Traditionally, military simulation has been problem domain specific. Executing an exercise currently requires multiple simulation software providers to specialize, deploy, and configure their respective implementations, integrate the collection of software to achieve a specific system behavior, and then execute for the purpose at hand. This approach leads to rigid system integrations which require simulation expertise for each deployment due to changes in location, hardware, and software. Our alternative is Software as a Service (SaaS) predicated on the virtualization of Night Vision Electronic Sensors (NVESD) sensor simulations as an exemplary case. Management middleware elements layer self provisioning, configuration, and integration services onto the virtualized sensors to present a system of services at run time. Given an Infrastructure as a Service (IaaS) environment, enabled and managed system of simulations yields a durable SaaS delivery without requiring user simulation expertise. Persistent SaaS simulations would provide on demand availability to connected users, decrease integration costs and timelines, and benefit the domain community from immediate deployment of lessons learned.

  2. SNM gamma-ray fingerprint monitor functional requirements and design specifications

    Bieber, A.M. Jr.; Kane, W.R.

    1994-07-01

    A number of DOE facilities need to perform confirmatory inventory measurements on items of special nuclear material (SNM). The DOE Office of Safeguards and Security (OSS) has tasked the Safeguards, Safety and Nonproliferation Division (SSN) of the Department of Advanced Technology at Brookhaven National Laboratory (BNL) to develop a high-resolution gamma-ray-spectroscopy-based instrument for performing confirmatory inventory measurements on such materials, a ''gamma-ray fingerprint monitor'' (GRFM). This document is a conceptual design for the SSN GRFM system. This conceptual design is based on previous experience with measurements of plutonium-bearing materials and comparison of gamma-ray spectrum features, not on actual tests of the procedures or hardware described. As a result, modifications may be necessary when actual prototype hardware and software are tested in realistic circumstances on actual materials of interest

  3. Circuit architecture derivation starting from a formal requirements specification considering a DDS as example

    Garbe, H.; Richter, R.; Jentschel, H.-J.

    2004-05-01

    Based on a formal specification of a direct digital synthesis (DDS) and assuming the availability of a set of possible circuit architectures we derive a customised system configuration. e calculate the design parameters that can be used for the specification to synthesise the circuit components. We show how the derived parameters and the selected IC technology influence the complexity of the circuit implementation.

  4. 46 CFR 164.009-3 - Noncombustible materials not requiring specific approval.

    2010-10-01

    ...) EQUIPMENT, CONSTRUCTION, AND MATERIALS: SPECIFICATIONS AND APPROVAL MATERIALS Noncombustible Materials for... noncombustible materials may be used in merchant vessel construction though not specifically approved under this subpart: (a) Sheet glass, block glass, clay, ceramics, and uncoated fibers. (b) All metals, except...

  5. 49 CFR 179.101 - Individual specification requirements applicable to pressure tank car tanks.

    2010-10-01

    ... to pressure tank car tanks. 179.101 Section 179.101 Transportation Other Regulations Relating to... MATERIALS REGULATIONS SPECIFICATIONS FOR TANK CARS Specifications for Pressure Tank Car Tanks (Classes DOT... tank car tanks. Editorial Note: At 66 FR 45186, Aug. 28, 2001, an amendment published amending a table...

  6. A quantitative calculation for software reliability evaluation

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

    2016-10-15

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

  7. Generic requirements specification for qualifying a commercially available PLC for safety-related applications in nuclear power plants. Final report

    Ostenso, A.; May, R.

    1996-12-01

    This is a specification for qualifying a commercially available PLC for application to safety systems in nuclear power plants. The specifications are suitable for evaluating a particular PLC product line as a platform for safety-related applications, establishing a suitable qualification test program, and confirming that the manufacturer has a quality assurance program that is adequate for safety-related applications or is sufficiently complete that, with a reasonable set of compensatory actions, it can be brought into conformance. The specification includes requirements for: (1) quality assurance measures applied to the qualification activities, (2) documentation to support the qualification, and (3) documentation to provide the information needed for applying the qualified PLC platform to a specific application. The specifications are designed to encompass a broad range of safety applications; however, qualifying a particular platform for a different range of applications can be accomplished by appropriate adjustments to the requirements

  8. Safety of Nuclear Power Plants: Design. Specific Safety Requirements (French Edition)

    2017-01-01

    This publication establishes requirements applicable to the design of nuclear power plants and elaborates on the safety objective, safety principles and concepts that provide the basis for deriving the safety requirements that must be met for the design of a nuclear power plant. It will be useful for organizations involved in design, manufacture, construction, modification, maintenance, operation and decommissioning of nuclear power plants, as well as for regulatory bodies. A review of Safety Requirements publications was commenced in 2011 following the accident in the Fukushima Daiichi nuclear power plant in Japan. The review revealed no significant areas of weakness and resulted in just a small set of amendments to strengthen the requirements and facilitate their implementation, which are contained in the present publication.

  9. Safety of Nuclear Power Plants: Design. Specific Safety Requirements (Russian Edition)

    2016-01-01

    This publication establishes requirements applicable to the design of nuclear power plants and elaborates on the safety objective, safety principles and concepts that provide the basis for deriving the safety requirements that must be met for the design of a nuclear power plant. It will be useful for organizations involved in design, manufacture, construction, modification, maintenance, operation and decommissioning of nuclear power plants, as well as for regulatory bodies. A review of Safety Requirements publications was commenced in 2011 following the accident in the Fukushima Daiichi nuclear power plant in Japan. The review revealed no significant areas of weakness and resulted in just a small set of amendments to strengthen the requirements and facilitate their implementation, which are contained in the present publication.

  10. Safety of Nuclear Power Plants: Commissioning and Operation. Specific Safety Requirements (French Edition)

    2016-01-01

    This publication describes the requirements to be met to ensure the safe operation of nuclear power plants. It takes into account developments in areas such as long term operation of nuclear power plants, plant ageing, periodic safety review, probabilistic safety analysis and risk informed decision making processes. In addition, the requirements are governed by, and must apply, the safety objective and safety principles that are established in the IAEA Safety Standards Series No. SF-1, Fundamental Safety Principles. A review of Safety Requirements publications was commenced in 2011 following the accident in the Fukushima Daiichi nuclear power plant in Japan. The review revealed no significant areas of weakness and resulted in just a small set of amendments to strengthen the requirements and facilitate their implementation, which are contained in the present publication.

  11. Safety of Nuclear Power Plants: Commissioning and Operation. Specific Safety Requirements

    2016-01-01

    This publication describes the requirements to be met to ensure the safe operation of nuclear power plants. It takes into account developments in areas such as long term operation of nuclear power plants, plant ageing, periodic safety review, probabilistic safety analysis and risk informed decision making processes. In addition, the requirements are governed by, and must apply, the safety objective and safety principles that are established in the IAEA Safety Standards Series No. SF-1, Fundamental Safety Principles. A review of Safety Requirements publications was commenced in 2011 following the accident in the Fukushima Daiichi nuclear power plant in Japan. The review revealed no significant areas of weakness and resulted in just a small set of amendments to strengthen the requirements and facilitate their implementation, which are contained in the present publication

  12. Safety of Nuclear Power Plants: Design. Specific Safety Requirements (Arabic Edition)

    2017-01-01

    This publication establishes requirements applicable to the design of nuclear power plants and elaborates on the safety objective, safety principles and concepts that provide the basis for deriving the safety requirements that must be met for the design of a nuclear power plant. It will be useful for organizations involved in design, manufacture, construction, modification, maintenance, operation and decommissioning of nuclear power plants, as well as for regulatory bodies. A review of Safety Requirements publications was commenced in 2011 following the accident in the Fukushima Daiichi nuclear power plant in Japan. The review revealed no significant areas of weakness and resulted in just a small set of amendments to strengthen the requirements and facilitate their implementation, which are contained in the present publication.

  13. The Specific Direction Requirement for Aiding and Abetting: A Call for Revisiting Comparative Criminal Law

    Aksenova, Marina

    2015-01-01

    . After this judgment, the prosecution filed a motion to reconsider the acquittal in Perišić, which the Appeals Chamber denied. In sum, these developments diluted and mischaracterized the standard of aiding and abetting. Accordingly, this article has two purposes. First, it demonstrates......The ‘specific direction’ saga has been dominating the jurisprudence of the ICTY for nearly two years, and the end is yet to be seen. The story centers on the correct interpretation of liability for aiding and abetting, while, at the same time, exposing broader concerns of international criminal law....... The saga started with unexpected acquittals of Perišić, Stanišić, and Simatović due to a lack of specific direction in their aid and assistance towards specific offences. More specifically, the tribunal found that the traditional test - the provision of aid with the awareness that it would have...

  14. 49 CFR 178.320 - General requirements applicable to all DOT specification cargo tank motor vehicles.

    2010-10-01

    ... removed from the motor vehicle; and (3) Is not fabricated under a specification for cylinders... determine leak tightness of the cargo tank when testing with pneumatic pressure. Internal self-closing stop...

  15. Validation testing of safety-critical software

    Kim, Hang Bae; Han, Jae Bok

    1995-01-01

    A software engineering process has been developed for the design of safety critical software for Wolsung 2/3/4 project to satisfy the requirements of the regulatory body. Among the process, this paper described the detail process of validation testing performed to ensure that the software with its hardware, developed by the design group, satisfies the requirements of the functional specification prepared by the independent functional group. To perform the tests, test facility and test software were developed and actual safety system computer was connected. Three kinds of test cases, i.e., functional test, performance test and self-check test, were programmed and run to verify each functional specifications. Test failures were feedback to the design group to revise the software and test results were analyzed and documented in the report to submit to the regulatory body. The test methodology and procedure were very efficient and satisfactory to perform the systematic and automatic test. The test results were also acceptable and successful to verify the software acts as specified in the program functional specification. This methodology can be applied to the validation of other safety-critical software. 2 figs., 2 tabs., 14 refs. (Author)

  16. Safety of Nuclear Power Plants: Commissioning and Operation. Specific Safety Requirements (Arabic Edition)

    2017-01-01

    This publication is a revision of IAEA Safety Standards Series No. NS-R-2, Safety of Nuclear Power Plants: Operation, and has been extended to cover the commissioning stage. It describes the requirements to be met to ensure the safe commissioning, operation, and transition from operation to decommissioning of nuclear power plants. Over recent years there have been developments in areas such as long term operation of nuclear power plants, plant ageing, periodic safety review, probabilistic safety analysis review and risk informed decision making processes. It became necessary to revise the IAEA’s Safety Requirements in these areas and to correct and/or improve the publication on the basis of feedback from its application by both the IAEA and its Member States. In addition, the requirements are governed by, and must apply, the safety objective and safety principles that are established in the IAEA Safety Standards Series No. SF-1, Fundamental Safety Principles. A review of Safety Requirements publications, initiated in 2011 following the accident in the Fukushima Daiichi nuclear power plant in Japan, revealed no significant areas of weakness but resulted in a small set of amendments to strengthen the requirements and facilitate their implementation. These are contained in the present publication.

  17. Safety of Nuclear Power Plants: Commissioning and Operation. Specific Safety Requirements

    2017-01-01

    This publication is a revision of IAEA Safety Standards Series No. NS-R-2, Safety of Nuclear Power Plants: Operation, and has been extended to cover the commissioning stage. It describes the requirements to be met to ensure the safe commissioning, operation, and transition from operation to decommissioning of nuclear power plants. Over recent years there have been developments in areas such as long term operation of nuclear power plants, plant ageing, periodic safety review, probabilistic safety analysis review and risk informed decision making processes. It became necessary to revise the IAEA’s Safety Requirements in these areas and to correct and/or improve the publication on the basis of feedback from its application by both the IAEA and its Member States. In addition, the requirements are governed by, and must apply, the safety objective and safety principles that are established in the IAEA Safety Standards Series No. SF-1, Fundamental Safety Principles. A review of Safety Requirements publications, initiated in 2011 following the accident in the Fukushima Daiichi nuclear power plant in Japan, revealed no significant areas of weakness but resulted in a small set of amendments to strengthen the requirements and facilitate their implementation. These are contained in the present publication.

  18. Functional Testing Protocols for Commercial Building Efficiency Baseline Modeling Software

    Jump, David; Price, Phillip N.; Granderson, Jessica; Sohn, Michael

    2013-09-06

    This document describes procedures for testing and validating proprietary baseline energy modeling software accuracy in predicting energy use over the period of interest, such as a month or a year. The procedures are designed according to the methodology used for public domain baselining software in another LBNL report that was (like the present report) prepared for Pacific Gas and Electric Company: ?Commercial Building Energy Baseline Modeling Software: Performance Metrics and Method Testing with Open Source Models and Implications for Proprietary Software Testing Protocols? (referred to here as the ?Model Analysis Report?). The test procedure focuses on the quality of the software?s predictions rather than on the specific algorithms used to predict energy use. In this way the software vendor is not required to divulge or share proprietary information about how their software works, while enabling stakeholders to assess its performance.

  19. TECHNICAL BASIS FOR VENTILATION REQUIREMENTS IN TANK FARMS OPERATING SPECIFICATIONS DOCUMENTS

    BERGLIN, E J

    2003-06-23

    This report provides the technical basis for high efficiency particulate air filter (HEPA) for Hanford tank farm ventilation systems (sometimes known as heating, ventilation and air conditioning [HVAC]) to support limits defined in Process Engineering Operating Specification Documents (OSDs). This technical basis included a review of older technical basis and provides clarifications, as necessary, to technical basis limit revisions or justification. This document provides an updated technical basis for tank farm ventilation systems related to Operation Specification Documents (OSDs) for double-shell tanks (DSTs), single-shell tanks (SSTs), double-contained receiver tanks (DCRTs), catch tanks, and various other miscellaneous facilities.

  20. Open Data, Open Specifications and Free and Open Source Software: A powerful mix to create distributed Web-based water information systems

    Arias, Carolina; Brovelli, Maria Antonia; Moreno, Rafael

    2015-04-01

    We are in an age when water resources are increasingly scarce and the impacts of human activities on them are ubiquitous. These problems don't respect administrative or political boundaries and they must be addressed integrating information from multiple sources at multiple spatial and temporal scales. Communication, coordination and data sharing are critical for addressing the water conservation and management issues of the 21st century. However, different countries, provinces, local authorities and agencies dealing with water resources have diverse organizational, socio-cultural, economic, environmental and information technology (IT) contexts that raise challenges to the creation of information systems capable of integrating and distributing information across their areas of responsibility in an efficient and timely manner. Tight and disparate financial resources, and dissimilar IT infrastructures (data, hardware, software and personnel expertise) further complicate the creation of these systems. There is a pressing need for distributed interoperable water information systems that are user friendly, easily accessible and capable of managing and sharing large volumes of spatial and non-spatial data. In a distributed system, data and processes are created and maintained in different locations each with competitive advantages to carry out specific activities. Open Data (data that can be freely distributed) is available in the water domain, and it should be further promoted across countries and organizations. Compliance with Open Specifications for data collection, storage and distribution is the first step toward the creation of systems that are capable of interacting and exchanging data in a seamlessly (interoperable) way. The features of Free and Open Source Software (FOSS) offer low access cost that facilitate scalability and long-term viability of information systems. The World Wide Web (the Web) will be the platform of choice to deploy and access these systems

  1. Tethys: The Marine and Hydrokinetic Technology Environmental Impacts Knowledge Management System -- Requirements Specification -- Version 1.0

    Butner, R. Scott; Snowden-Swan, Lesley J.; Ellis, Peter C.

    2010-11-09

    The marine and hydrokinetic (MHK) environmental impacts knowledge management system (KMS), dubbed Tethys after the mythical Greek goddess of the seas, is being developed for the U.S. Department of Energy (DOE) Office of Energy Efficiency and Renewable Energy Wind and Hydropower Technologies Program (WHTP) by Pacific Northwest National Laboratory (PNNL). This requirements specification establishes the essential capabilities required of Tethys and clarifies for WHTP and the Tethys development team the results that must be achieved by the system.

  2. Comparison between In-house developed and Diamond commercial software for patient specific independent monitor unit calculation and verification with heterogeneity corrections.

    Kuppusamy, Vijayalakshmi; Nagarajan, Vivekanandan; Jeevanandam, Prakash; Murugan, Lavanya

    2016-02-01

    The study was aimed to compare two different monitor unit (MU) or dose verification software in volumetric modulated arc therapy (VMAT) using modified Clarkson's integration technique for 6 MV photons beams. In-house Excel Spreadsheet based monitor unit verification calculation (MUVC) program and PTW's DIAMOND secondary check software (SCS), version-6 were used as a secondary check to verify the monitor unit (MU) or dose calculated by treatment planning system (TPS). In this study 180 patients were grouped into 61 head and neck, 39 thorax and 80 pelvic sites. Verification plans are created using PTW OCTAVIUS-4D phantom and also measured using 729 detector chamber and array with isocentre as the suitable point of measurement for each field. In the analysis of 154 clinically approved VMAT plans with isocentre at a region above -350 HU, using heterogeneity corrections, In-house Spreadsheet based MUVC program and Diamond SCS showed good agreement TPS. The overall percentage average deviations for all sites were (-0.93% + 1.59%) and (1.37% + 2.72%) for In-house Excel Spreadsheet based MUVC program and Diamond SCS respectively. For 26 clinically approved VMAT plans with isocentre at a region below -350 HU showed higher variations for both In-house Spreadsheet based MUVC program and Diamond SCS. It can be concluded that for patient specific quality assurance (QA), the In-house Excel Spreadsheet based MUVC program and Diamond SCS can be used as a simple and fast accompanying to measurement based verification for plans with isocentre at a region above -350 HU. Copyright © 2016 Associazione Italiana di Fisica Medica. Published by Elsevier Ltd. All rights reserved.

  3. Quality assurance of the modernized Dukovany I and C safety system software

    Karpeta, C.

    2005-01-01

    The approach to quality assurance of the software that implements the instrumentation and control functions for safety category A as per IEC 61226, which has been adopted within the 'NPP Dukovany I and C Refurbishment' project, is described. A survey of the requirements for software quality assurance of the systems that initiate protection interventions in the event of anticipated operational occurrences or accident conditions is given. The software development process applied by the system designers and manufacturers, from the software requirements specification phase to the software testing phase, is outlined. Basic information on technical audits of the software development process is also provided. (orig.)

  4. 24 CFR 200.945 - Supplementary specific requirements under the HUD building product standards and certification...

    2010-04-01

    ... under the HUD building product standards and certification program for carpet. 200.945 Section 200.945... requirements under the HUD building product standards and certification program for carpet. (a) Applicable.... (b) Labeling. Under the procedures set forth in § 200.935(d)(6) concerning labeling of a product, the...

  5. Risk-Based Confidentiality Requirements Specification for Outsourced IT Systems (Extended Version)

    Morali, A.; Wieringa, Roelf J.

    2010-01-01

    Today, companies are required to be in control of their IT assets, and to provide proof of this in the form of independent IT audit reports. However, many companies have outsourced various parts of their IT systems to other companies, which potentially threatens the control they have of their IT

  6. 40 CFR 270.17 - Specific part B information requirements for surface impoundments.

    2010-07-01

    ... migration of any hazardous constituents into the ground water or surface water at any future time; (2) The....19 of this chapter; (5) Proposed action leakage rate, with rationale, if required under § 264.222 of..., including the double liner system, leak detection system, cover system, and appurtenances for control of...

  7. 40 CFR 60.2095 - What site-specific documentation is required?

    2010-07-01

    .... (5) Procedures for operating the incinerator and associated air pollution control systems within the... incinerator operating limits. (7) Reporting and recordkeeping procedures. (8) The waste management plan... required? 60.2095 Section 60.2095 Protection of Environment ENVIRONMENTAL PROTECTION AGENCY (CONTINUED) AIR...

  8. Formal Functional Test Designs: Bridging the Gap Between Test Requirements and Test Specifications

    Hops, Jonathan

    1993-01-01

    This presentation describes the testing life cycle, the purpose of the test design phase, and test design methods and gives an example application. Also included is a description of Test Representation Language (TRL), a summary of the language, and an example of an application of TRL. A sample test requirement and sample test design are included.

  9. 49 CFR 180.407 - Requirements for test and inspection of specification cargo tanks.

    2010-10-01

    ... may not prevent detection of leaks or damage the venting devices and must be removed immediately after... PIPELINE AND HAZARDOUS MATERIALS SAFETY ADMINISTRATION, DEPARTMENT OF TRANSPORTATION HAZARDOUS MATERIALS... percent of the required set pressure, and must reseat to a leak-tight condition at no less than 90 percent...

  10. The requirements and specific features related to power supply in telecommunications of Ukraine

    Lubashenko, T. [Inst. Giprosvijaz, Kiev (Ukraine); Gordon, A. [ProElectro Ltd., Kiev (Ukraine)

    2000-07-01

    The article deals with the description of trends of power supplies in the telecommunication sector. The basic normative documents regarding the design of the power supplies are pointed out. The requirements concerning the design of the power supplies are outlined. The peculiarities of the power supplies in Ukrainian telecommunications are given. (orig.)

  11. NKT sublineage specification and survival requires the ubiquitin-modifying enzyme TNF AIP3/A20

    Drennan, M.B. (Michael B.); Govindarajan, S. (Srinath); Verheugen, E. (Eveline); Coquet, J.M. (Jonathan M.); Staal, J. (Jens); McGuire, C. (Conor); T. Taghon (Tom); G. Leclercq (Georges); R. Beyaert (Rudi); G. van Loo (Geert); B.N.M. Lambrecht (Bart); Elewaut, D. (Dirk)

    2016-01-01

    textabstractNatural killer T (NKT) cells are innate lymphocytes that differentiate into NKT1, NKT2, and NKT17 sublineages during development. However, the signaling events that control NKT sublineage specification and differentiation remain poorly understood. Here, we demonstrate that the

  12. 40 CFR 270.25 - Specific part B information requirements for equipment.

    2010-07-01

    ..., boiler, process heater, condenser, or carbon adsorption system and chooses to use test data to determine....1033(j). (3) A design analysis, specifications, drawings, schematics, and piping and instrumentation... Administrator that present basic control device information. The design analysis shall address the vent stream...

  13. Proliferation requirements of cytomegalovirus-specific, effector-type human CD8+ T cells

    van Leeuwen, Ester M.; Gamadia, Laila E.; Baars, Paul A.; Remmerswaal, Ester B.; ten Berge, Ineke J.; van Lier, René A.

    2002-01-01

    Two prototypic types of virus-specific CD8(+) T cells can be found in latently infected individuals: CD45R0(+)CD27(+)CCR7(-) effector-memory, and CD45RA(+)CD27(-)CCR7(-) effector-type cells. It has recently been implied that CD45RA(+)CD27(-)CCR7(-) T cells are terminally differentiated effector

  14. Interleukin-1 is required for cancer eradication mediated by tumor-specific Th1 cells.

    Haabeth, Ole Audun Werner; Lorvik, Kristina Berg; Yagita, Hideo; Bogen, Bjarne; Corthay, Alexandre

    The role of inflammation in cancer is controversial as both tumor-promoting and tumor-suppressive aspects of inflammation have been reported. In particular, it has been shown that pro-inflammatory cytokines, like interleukin-1α (IL-1α), IL-1β, IL-6, and tumor necrosis factor α (TNFα), may either promote or suppress cancer. However, the cellular and molecular basis underlying these opposing outcomes remains enigmatic. Using mouse models for myeloma and lymphoma, we have recently reported that inflammation driven by tumor-specific T helper 1 (Th1) cells conferred protection against B-cell cancer and that interferon-γ (IFN-γ) was essential for this process. Here, we have investigated the contribution of several inflammatory mediators. Myeloma eradication by Th1 cells was not affected by inhibition of TNF-α, TNF-related weak inducer of apoptosis (TWEAK), or TNF-related apoptosis-inducing ligand (TRAIL). In contrast, cancer elimination by tumor-specific Th1 cells was severely impaired by the in vivo neutralization of both IL-1α and IL-1β (collectively named IL-1) with IL-1 receptor antagonist (IL-1Ra). The antitumor functions of tumor-specific Th1 cells and tumor-infiltrating macrophages were both affected by IL-1 neutralization. Secretion of the Th1-derived cytokines IL-2 and IFN-γ at the incipient tumor site was severely reduced by IL-1 blockade. Moreover, IL-1 was shown to synergize with IFN-γ for induction of tumoricidal activity in tumor-infiltrating macrophages. This synergy between IL-1 and IFN-γ may explain how inflammation, when driven by tumor-specific Th1 cells, represses rather than promotes cancer. Collectively, the data reveal a central role of inflammation, and more specifically of the canonical pro-inflammatory cytokine IL-1, in enhancing Th1-mediated immunity against cancer.

  15. GENII Version 2 Software Design Document

    Napier, Bruce A.; Strenge, Dennis L.; Ramsdell, James V.; Eslinger, Paul W.; Fosmire, Christian J.

    2004-03-08

    This document describes the architectural design for the GENII-V2 software package. This document defines details of the overall structure of the software, the major software components, their data file interfaces, and specific mathematical models to be used. The design represents a translation of the requirements into a description of the software structure, software components, interfaces, and necessary data. The design focuses on the major components and data communication links that are key to the implementation of the software within the operating framework. The purpose of the GENII-V2 software package is to provide the capability to perform dose and risk assessments of environmental releases of radionuclides. The software also has the capability of calculating environmental accumulation and radiation doses from surface water, groundwater, and soil (buried waste) media when an input concentration of radionuclide in these media is provided. This report represents a detailed description of the capabilities of the software product with exact specifications of mathematical models that form the basis for the software implementation and testing efforts. This report also presents a detailed description of the overall structure of the software package, details of main components (implemented in the current phase of work), details of data communication files, and content of basic output reports. The GENII system includes the capabilities for calculating radiation doses following chronic and acute releases. Radionuclide transport via air, water, or biological activity may be considered. Air transport options include both puff and plume models, each allow use of an effective stack height or calculation of plume rise from buoyant or momentum effects (or both). Building wake effects can be included in acute atmospheric release scenarios. The code provides risk estimates for health effects to individuals or populations; these can be obtained using the code by applying

  16. A concept of software testing for SMART MMIS software

    Seo, Yong Seok; Seong, Seung Hwan; Park, Keun Ok; Hur, Sub; Kim, Dong Hoon

    2001-01-01

    In order to achieve high quality of SMART MMIS software, the well-constructed software testing concept shall be required. This paper established software testing concept which is to be applied to SMART MMIS software, in terms of software testing organization, documentation. procedure, and methods. The software testing methods are classified into source code static analysis and dynamic testing. The software dynamic testing methods are discussed with two aspects: white-box and black-box testing. As software testing concept introduced in this paper is applied to the SMART MMIS software. the high quality of the software will be produced. In the future, software failure data will be collected through the construction of SMART MMIS prototyping facility which the software testing concept of this paper is applied to

  17. Computational Homology for Software Validation

    2015-03-01

    involving compound data-types. 15. SUBJECT TERMS Abstract datatypes , convergence structure, topological methods, specification logics, hybrid software...composite datatype values are networks strewn through the device’s memory; think of a variable whose type is an array of balanced trees. Some means...structural in nature, is required to rigorously specify the evolution of composite states involving non-numerical, non-metric components. Composite datatypes

  18. Multiphysics software and the challenge to validating physical models

    Luxat, J.C.

    2008-01-01

    This paper discusses multi physics software and validation of physical models in the nuclear industry. The major challenge is to convert the general purpose software package to a robust application-specific solution. This requires greater knowledge of the underlying solution techniques and the limitations of the packages. Good user interfaces and neat graphics do not compensate for any deficiencies

  19. Process based unification for multi-model software process improvement

    Kelemen, Z.D.

    2013-01-01

    Many different quality approaches are available in the software industry. Some of the ap-proaches, such as ISO 9001 are not software specific, i.e. they define general requirements for an organization and they can be used at any company. Others, such as Automotive SPICE have been derived from a

  20. PABRE-Proj: applying patterns in requirements elicitation

    Palomares Bonache, Cristina; Quer Bosor, Maria Carme; Franch Gutiérrez, Javier

    2013-01-01

    Software requirement patterns have been proposed as a type of artifact for fostering requirements reuse. In this paper, we present PABRE-Proj, a tool aimed at supporting requirements elicitation and specification. Peer Reviewed

  1. The stylar 120 kDa glycoprotein is required for S-specific pollen rejection in Nicotiana.

    Hancock, C Nathan; Kent, Lia; McClure, Bruce A

    2005-09-01

    S-RNase participates in at least three mechanisms of pollen rejection. It functions in S-specific pollen rejection (self-incompatibility) and in at least two distinct interspecific mechanisms of pollen rejection in Nicotiana. S-specific pollen rejection and rejection of pollen from Nicotiana plumbaginifolia also require additional stylar proteins. Transmitting-tract-specific (TTS) protein, 120 kDa glycoprotein (120K) and pistil extensin-like protein III (PELP III) are stylar glycoproteins that bind S-RNase in vitro and are also known to interact with pollen. Here we tested whether these glycoproteins have a direct role in pollen rejection. 120K shows the most polymorphism in size between Nicotiana species. Larger 120K-like proteins are often correlated with S-specific pollen rejection. Sequencing results suggest that the polymorphism primarily reflects differences in glycosylation, although indels also occur in the predicted polypeptides. Using RNA interference (RNAi), we suppressed expression of 120K to determine if it is required for S-specific pollen rejection. Transgenic SC N. plumbaginifolia x SI Nicotiana alata (S105S105 or SC10SC10) hybrids with no detectable 120K were unable to perform S-specific pollen rejection. Thus, 120K has a direct role in S-specific pollen rejection. However, suppression of 120K had no effect on rejection of N. plumbaginifolia pollen. In contrast, suppression of HT-B, a factor previously implicated in S-specific pollen rejection, disrupts rejection of N. plumbaginifolia pollen. Thus, S-specific pollen rejection and rejection of N. plumbaginifolia pollen are mechanistically distinct, because they require different non-S-RNase factors.

  2. Recruitment of Mediator Complex by Cell Type and Stage-Specific Factors Required for Tissue-Specific TAF Dependent Gene Activation in an Adult Stem Cell Lineage.

    Lu, Chenggang; Fuller, Margaret T

    2015-12-01

    Onset of terminal differentiation in adult stem cell lineages is commonly marked by robust activation of new transcriptional programs required to make the appropriate differentiated cell type(s). In the Drosophila male germ line stem cell lineage, the switch from proliferating spermatogonia to spermatocyte is accompanied by one of the most dramatic transcriptional changes in the fly, as over 1000 new transcripts turn on in preparation for meiosis and spermatid differentiation. Here we show that function of the coactivator complex Mediator is required for activation of hundreds of new transcripts in the spermatocyte program. Mediator appears to act in a sequential hierarchy, with the testis activating Complex (tMAC), a cell type specific form of the Mip/dREAM general repressor, required to recruit Mediator subunits to the chromatin, and Mediator function required to recruit the testis TAFs (tTAFs), spermatocyte specific homologs of subunits of TFIID. Mediator, tMAC and the tTAFs co-regulate expression of a major set of spermatid differentiation genes. The Mediator subunit Med22 binds the tMAC component Topi when the two are coexpressed in S2 cells, suggesting direct recruitment. Loss of Med22 function in spermatocytes causes meiosis I maturation arrest male infertility, similar to loss of function of the tMAC subunits or the tTAFs. Our results illuminate how cell type specific versions of the Mip/dREAM complex and the general transcription machinery cooperate to drive selective gene activation during differentiation in stem cell lineages.

  3. Recruitment of Mediator Complex by Cell Type and Stage-Specific Factors Required for Tissue-Specific TAF Dependent Gene Activation in an Adult Stem Cell Lineage.

    Chenggang Lu

    2015-12-01

    Full Text Available Onset of terminal differentiation in adult stem cell lineages is commonly marked by robust activation of new transcriptional programs required to make the appropriate differentiated cell type(s. In the Drosophila male germ line stem cell lineage, the switch from proliferating spermatogonia to spermatocyte is accompanied by one of the most dramatic transcriptional changes in the fly, as over 1000 new transcripts turn on in preparation for meiosis and spermatid differentiation. Here we show that function of the coactivator complex Mediator is required for activation of hundreds of new transcripts in the spermatocyte program. Mediator appears to act in a sequential hierarchy, with the testis activating Complex (tMAC, a cell type specific form of the Mip/dREAM general repressor, required to recruit Mediator subunits to the chromatin, and Mediator function required to recruit the testis TAFs (tTAFs, spermatocyte specific homologs of subunits of TFIID. Mediator, tMAC and the tTAFs co-regulate expression of a major set of spermatid differentiation genes. The Mediator subunit Med22 binds the tMAC component Topi when the two are coexpressed in S2 cells, suggesting direct recruitment. Loss of Med22 function in spermatocytes causes meiosis I maturation arrest male infertility, similar to loss of function of the tMAC subunits or the tTAFs. Our results illuminate how cell type specific versions of the Mip/dREAM complex and the general transcription machinery cooperate to drive selective gene activation during differentiation in stem cell lineages.

  4. Cell-specific differences in the requirements for translation quality control

    Reynolds, Noah M; Ling, Jiqiang; Roy, Hervé

    2010-01-01

    Protein synthesis has an overall error rate of approximately 10(-4) for each mRNA codon translated. The fidelity of translation is mainly determined by two events: synthesis of cognate amino acid:tRNA pairs by aminoacyl-tRNA synthetases (aaRSs) and accurate selection of aminoacyl-tRNAs (aa-tRNAs)...... divergent requirements for quality control in different cell compartments and suggest that the limits of translational accuracy may be largely determined by cellular physiology....

  5. Specification and time required for the application of a lime-based render inside historic buildings

    Vasco Peixoto de Freitas

    2008-01-01

    Full Text Available Intervention in ancient buildings with historical and architectural value requires traditional techniques, such as the use of lime mortars for internal and external wall renderings. In order to ensure the desired performance, these rendering mortars must be rigorously specified and quality controls have to be performed during application. The choice of mortar composition should take account of factors such as compatibility with the substrate, mechanical requirements and water behaviour. The construction schedule, which used to be considered a second order variable, nowadays plays a decisive role in the selection of the rendering technique, given its effects upon costs. How should lime-based mortars be specified? How much time is required for the application and curing of a lime-based render? This paper reflects upon the feasibility of using traditional lime mortars in three-layer renders inside churches and monasteries under adverse hygrothermal conditions and when time is critical. A case study is presented in which internal lime mortar renderings were applied in a church in Northern Portugal, where the very high relative humidity meant that several months were necessary before the drying process was complete.

  6. Activation of germline-specific genes is required for limb regeneration in the Mexican axolotl

    Zhu, Wei; Pao, Gerald M; Satoh, Akira; Cummings, Gillian; Monaghan, James R; Harkins, Timothy T; Bryant, Susan V; Voss, S Randal; Gardiner, David M; Hunter, Tony

    2013-01-01

    The capacity for tissue and organ regeneration in humans is dwarfed by comparison to that of salamanders. Emerging evidence suggests that mechanisms learned from the early phase of salamander limb regeneration – wound healing, cellular dedifferentiation and blastemal formation – will reveal therapeutic approaches for tissue regeneration in humans. Here we describe a unique transcriptional fingerprint of regenerating limb tissue in the Mexican axolotl (Ambystoma mexicanum) that is indicative of cellular reprogramming of differentiated cells to a germline-like state. Two genes that are required for self-renewal of germ cells in mice and flies, Piwi-like 1 (PL1) and Piwi-like 2 (PL2), are expressed in limb blastemal cells, the basal layer keratinocytes and the thickened apical epithelial cap in the wound epidermis in the regenerating limb. Depletion of PL1 and PL2 by morpholino oligonucleotides decreased cell proliferation and increased cell death in the blastema leading to a significant retardation of regeneration. Examination of key molecules that are known to be required for limb development or regeneration further revealed that FGF8 is transcriptionally downregulated in the presence of the morpholino oligos, indicating PL1 and PL2 might participate in FGF signaling during limb regeneration. Given the requirement for FGF signaling in limb development and regeneration, the results suggest that PL1 and PL2 function to establish a unique germline-like state that is associated with successful regeneration. PMID:22841627

  7. Agile Scientists? : Investigating Agile Practices in Scientific Software Development

    Sletholt, Magnus Thorstein

    2011-01-01

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

  8. Learning Theories Applied to Teaching Technology: Constructivism versus Behavioral Theory for Instructing Multimedia Software Programs

    Reed, Cajah S.

    2012-01-01

    This study sought to find evidence for a beneficial learning theory to teach computer software programs. Additionally, software was analyzed for each learning theory's applicability to resolve whether certain software requires a specific method of education. The results are meant to give educators more effective teaching tools, so students…

  9. Structure-guided mutational analysis reveals the functional requirements for product specificity of DOT1 enzymes.

    Dindar, Gülcin; Anger, Andreas M; Mehlhorn, Christine; Hake, Sandra B; Janzen, Christian J

    2014-11-12

    DOT1 enzymes are conserved methyltransferases that catalyse the methylation of lysine 79 on histone H3 (H3K79). Most eukaryotes contain one DOT1 enzyme, whereas African trypanosomes have two homologues, DOT1A and DOT1B, with different enzymatic activities. DOT1A mediates mono- and dimethylation of H3K76, the homologue of H3K79 in other organisms, whereas DOT1B additionally catalyses H3K76 trimethylation. However, it is unclear how these different enzymatic activities are achieved. Here we employ a trypanosomal nucleosome reconstitution system and structure-guided homology modelling to identify critical residues within and outside the catalytic centre that modulate product specificity. Exchange of these residues transfers the product specificity from one enzyme to the other, and reveals the existence of distinct regulatory domains adjacent to the catalytic centre. Our study provides the first evidence that a few crucial residues in DOT1 enzymes are sufficient to catalyse methyl-state-specific reactions. These results might also have far-reaching consequences for the functional understanding of homologous enzymes in higher eukaryotes.

  10. SWEBOS – The Software Engineering Body of Skills

    Yvonne Sedelmaier

    2015-02-01

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

  11. Software engineering

    Sommerville, Ian

    2010-01-01

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

  12. Sex-specific signaling in the blood-brain barrier is required for male courtship in Drosophila.

    Valbona Hoxha

    Full Text Available Soluble circulating proteins play an important role in the regulation of mating behavior in Drosophila melanogaster. However, how these factors signal through the blood-brain barrier (bbb to interact with the sex-specific brain circuits that control courtship is unknown. Here we show that male identity of the blood-brain barrier is necessary and that male-specific factors in the bbb are physiologically required for normal male courtship behavior. Feminization of the bbb of adult males significantly reduces male courtship. We show that the bbb-specific G-protein coupled receptor moody and bbb-specific Go signaling in adult males are necessary for normal courtship. These data identify sex-specific factors and signaling processes in the bbb as important regulators of male mating behavior.

  13. Seismology software: state of the practice

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

    2018-05-01

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

  14. Seismology software: state of the practice

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

    2018-02-01

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

  15. 47 CFR 95.1119 - Specific requirements for wireless medical telemetry devices operating in the 608-614 MHz band.

    2010-10-01

    ... devices operating in the 608-614 MHz band. For a wireless medical telemetry device operating within the... 47 Telecommunication 5 2010-10-01 2010-10-01 false Specific requirements for wireless medical telemetry devices operating in the 608-614 MHz band. 95.1119 Section 95.1119 Telecommunication FEDERAL...

  16. 47 CFR 95.1121 - Specific requirements for wireless medical telemetry devices operating in the 1395-1400 and 1427...

    2010-10-01

    ... wireless medical telemetry devices operating in the 1395-1400 and 1427-1432 MHz bands. Due to the critical... 47 Telecommunication 5 2010-10-01 2010-10-01 false Specific requirements for wireless medical telemetry devices operating in the 1395-1400 and 1427-1432 MHz bands. 95.1121 Section 95.1121...

  17. 40 CFR Table C-1 to Subpart C of... - Test Concentration Ranges, Number of Measurements Required, and Maximum Discrepancy Specification

    2010-07-01

    ... Measurements Required, and Maximum Discrepancy Specification C Table C-1 to Subpart C of Part 53 Protection of... Reference Methods Pt. 53, Subpt. C, Table C-1 Table C-1 to Subpart C of Part 53—Test Concentration Ranges..., June 22, 2010, table C-1 to subpart C was revised, effective Aug. 23, 2010. For the convenience of the...

  18. Progress towards the professionalization of Software Engineering

    Janeth McAlister

    2014-12-01

    Full Text Available Software Engineer provides a theoretical framework, methods, and tools needed to develop quality software, and has impulse the revolution of Information and Knowledge Society, because without their contributions computers would be just a tool without a specific utility. Furthermore, despite of advances in hardware, the impact and potentiation of technological development just was possible thanks to software products. On the other hand, current Society is starting to be recognize as software–dependent, since in this century software is part of all devices required to manipulated information, and which people used in their daily activities. In this article is presented an analysis to the process of search professionalize software engineer and their products, having as base the work develop since the GSwE2009.

  19. Some design constraints required for the use of generic software in embedded systems: Packages which manage abstract dynamic structures without the need for garbage collection

    Johnson, Charles S.

    1986-01-01

    The embedded systems running real-time applications, for which Ada was designed, require their own mechanisms for the management of dynamically allocated storage. There is a need for packages which manage their own internalo structures to control their deallocation as well, due to the performance implications of garbage collection by the KAPSE. This places a requirement upon the design of generic packages which manage generically structured private types built-up from application-defined input types. These kinds of generic packages should figure greatly in the development of lower-level software such as operating systems, schedulers, controllers, and device driver; and will manage structures such as queues, stacks, link-lists, files, and binary multary (hierarchical) trees. Controlled to prevent inadvertent de-designation of dynamic elements, which is implicit in the assignment operation A study was made of the use of limited private type, in solving the problems of controlling the accumulation of anonymous, detached objects in running systems. The use of deallocator prodecures for run-down of application-defined input types during deallocation operations during satellites.

  20. PINK1 is required for timely cell-type specific mitochondrial clearance during Drosophila midgut metamorphosis.

    Liu, Yan; Lin, Jingjing; Zhang, Minjie; Chen, Kai; Yang, Shengxi; Wang, Qun; Yang, Hongqin; Xie, Shusen; Zhou, Yongjian; Zhang, Xi; Chen, Fei; Yang, Yufeng

    2016-11-15

    Mitophagy is the selective degradation of mitochondria by autophagy, which is an important mitochondrial quality and quantity control process. During Drosophila metamorphosis, the degradation of midgut involves a large change in length and organization, which is mediated by autophagy. Here we noticed a cell-type specific mitochondrial clearance process that occurs in enterocytes (ECs), while most mitochondria remain in intestinal stem cells (ISCs) during metamorphosis. Although PINK1/PARKIN represent the canonical pathway for the elimination of impaired mitochondria in varied pathological conditions, their roles in developmental processes or normal physiological conditions have been less studied. To examine the potential contribution of PINK1 in developmental processes, we monitored the dynamic expression pattern of PINK1 in the midgut development by taking advantage of a newly CRISPR/Cas9 generated knock-in fly strain expressing PINK1-mCherry fusion protein that presumably recapitulates the endogenous expression pattern of PINK1. We disclosed a spatiotemporal correlation between the expression pattern of PINK1 and the mitochondrial clearance or persistence in ECs or ISCs respectively. By mosaic genetic analysis, we then demonstrated that PINK1 and PARKIN function epistatically to mediate the specific timely removal of mitochondria, and are involved in global autophagy in ECs during Drosophila midgut metamorphosis, with kinase-dead PINK1 exerting dominant negative effects. Taken together, our studies concluded that the PINK1/PARKIN is crucial for timely cell-type specific mitophagy under physiological conditions and demonstrated again that Drosophila midgut metamorphosis might serve as an elegant in vivo model to study autophagy. Copyright © 2016 Elsevier Inc. All rights reserved.