Analyzing Software Requirements Errors in Safety-Critical, Embedded Systems

Science.gov (United States)

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.

Identify and Manage the Software Requirements Volatility

OpenAIRE

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

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

Science.gov (United States)

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.

Avaliação de alunos e professores acerca do software "Sinais Vitais" Evaluación de estudiantes y profesores acerca del software "señales vitales" Evaluation of students and teachers concerning the "vital signs" software

Directory of Open Access Journals (Sweden)

Marcos Venícios de Oliveira Lopes

2004-12-01

Full Text Available Este artigo teve por objetivo levantar as opiniões de alunos e professores sobre o software "Sinais Vitais". O trabalho foi desenvolvido no Departamento de Enfermagem da Universidade Federal do Ceará. Trabalhou-se com um total de seis alunos e três professores, os quais foram submetidos a uma entrevista após a utilização do software. As entrevistas geraram dez categorias, as quais foram separadas em dois temas: Características que estimularam a utilização do software "Sinais Vitais" e Software educacionalmente correto. Concluiu-se que os professores valorizaram a correção do conteúdo, enquanto os alunos enfocaram mais a dinâmica do programa.Este artículo tuvo por objetivo levantar las opiniones de alumnos y profesores sobre el software "Señales Vitales". El trabajo fue desarrollado en el Departamento de Enfermería de la Universidad Federal de Ceará. Se trabajó con un total de 6 alumnos y 3 profesores, los cuales fueron sometidos a una entrevista después de la utilización del software. Las entrevistas generaron 10 categorías, que fueron separadas en dos temas: Características que estimularon la utilización del software "Señales Vitales"; y software educativamente correcto. Se concluyó que los profesores valoraron la corrección del contenido, mientras que los alumnos enfocaron más la dinámica del programa.This article had for objective to get students' and teacher's opinions about "Vital Signals" software. The investigation was developed in the Nursing Department of the Federal University of Ceará. The sample population was a total of 6 students and 3 teachers, who were submitted to an interview after using the software. The interviews generated 10 categories, which were separated in two themes: Features which stimulated the use of the "Vital Signals" software; and software educationally correct. The results showed that the teachers valued the correction of the content, while the students focused more on the dynamics

Proposing an Evidence-Based Strategy for Software Requirements Engineering.

Science.gov (United States)

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.

Capturing security requirements for software systems.

Science.gov (United States)

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.

Capturing security requirements for software systems

Directory of Open Access Journals (Sweden)

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.

Capturing security requirements for software systems

Science.gov (United States)

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

Training Requirements and Information Management System. Software user guide

Energy Technology Data Exchange (ETDEWEB)

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.

A Cloverleaf of Software Engineering

DEFF Research Database (Denmark)

Bjørner, Dines

2005-01-01

, however "lite". Third, despite 35 years of formal methods, the SE industry, maturity-wise still lags far behind that of other engineering disciplines. So we examine why. Finally, in several areas, in health care, in architecture, and others, we see that major undertakings are primarily spearheaded...... by senior academic staff. Professors of medicine daily perform specialized surgery and treatments at hospitals. Professors of architecture design new, daring buildings for industry, and professors of civil engineering head the engineering structural design of new, daring bridges. So we speculate what......We shall touch upon four issues of software engineering (SE): domain engineering, formal techniques, SE sociology, and academic software architects. First, before software can be designed one must understand its requirements; but before requirements can be formulated one must understand the domain...

Requirements engineering for software and systems

CERN Document Server

Laplante, Phillip A

2014-01-01

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

The Use of UML for Software Requirements Expression and Management

Science.gov (United States)

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

Traceability of Requirements and Software Architecture for Change Management

NARCIS (Netherlands)

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

Software requirements management based on use cases

International Nuclear Information System (INIS)

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)

Traceability of Software Safety Requirements in Legacy Safety Critical Systems

Science.gov (United States)

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?

A Method for Software Requirement Volatility Analysis Using QFD

Directory of Open Access Journals (Sweden)

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.

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

OpenAIRE

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

Development of requirements tracking and verification technology for the NPP software

Energy Technology Data Exchange (ETDEWEB)

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.

Development of requirements tracking and verification technology for the NPP software

International Nuclear Information System (INIS)

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

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

Science.gov (United States)

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

A SYSTEMATIC LITERATURE REVIEW ABOUT SOFTWARE REQUIREMENTS ELICITATION

Directory of Open Access Journals (Sweden)

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.

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

Directory of Open Access Journals (Sweden)

Abdulaziz Alsahli

2016-01-01

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

More about software requirements thorny issues and practical advice

CERN Document Server

Wiegers, Karl E

2006-01-01

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

Software configuration management plan for the Hanford site technical database

International Nuclear Information System (INIS)

GRAVES, N.J.

1999-01-01

The Hanford Site Technical Database (HSTD) is used as the repository/source for the technical requirements baseline and programmatic data input via the Hanford Site and major Hanford Project Systems Engineering (SE) activities. The Hanford Site SE effort has created an integrated technical baseline for the Hanford Site that supports SE processes at the Site and project levels which is captured in the HSTD. The HSTD has been implemented in Ascent Logic Corporation (ALC) Commercial Off-The-Shelf (COTS) package referred to as the Requirements Driven Design (RDD) software. This Software Configuration Management Plan (SCMP) provides a process and means to control and manage software upgrades to the HSTD system

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

Science.gov (United States)

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.

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

OpenAIRE

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

Análisis de la implementación software de un conformador de señales ultrasónicas para tiempo real

Directory of Open Access Journals (Sweden)

D. Romero-Laorden

2016-10-01

Full Text Available Resumen: Este trabajo analiza la implementación software en un sistema de imagen ultrasónica del Total Focusing Method para la compensación dinámica en tiempo real de los tiempos de vuelo para emisión y recepción de todos los puntos de la imagen. Para ello, haciendo uso de técnicas GPGPU, se analizan dos diferentes alternativas de implementación, mostrando como una planificación adecuada de acceso a los datos permite mejorar los tiempos de ejecución del algoritmo. Abstract: This paper studies the software implementation in an ultrasonic imaging system of Total Focusing Method. In order to accomplish real-time requirements parallel programming techniques have been used. Then, using GPGPU techniques, two different implementation alternatives are analysed, showing how proper planning of access to data improves the performance of the algorithm. Palabras clave: Imagen Ultrasónica, Procesamiento de Señal, Computación Paralela, GPU, CUDA, Keywords: Ultrasonic imaging GPU Signal Processing Parallel computing CUDA

Application Reuse Library for Software, Requirements, and Guidelines

Science.gov (United States)

Malin, Jane T.; Thronesbery, Carroll

1994-01-01

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

Sample Set (SE): SE20 [Metabolonote[Archive

Lifescience Database Archive (English)

Full Text Available SE20 Arabidopsis thaliana leaf metabolite analysis for a software test Investigatio...es that were investigated to optimize the parameters of PowerGet software for better metabolite annotation i

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

Science.gov (United States)

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.

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

International Nuclear Information System (INIS)

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

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

Science.gov (United States)

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

The SE Book: Principles and Techniques of Software Engineering or orAn ABZ of The Theory & Practice of Software Engineering

DEFF Research Database (Denmark)

Bjørner, Dines

) the TripTych of domain analysis, requirements engineering and software design -- and much much more. It relates all aspects of (12) platform technologies, (13) legal issues of software, (14) quality assurance, and (15) project and product management to the above (1-11 incl.). Highlights of the book series......This ``epos'' emphasises (1) software development from both a formal and an informal approach; (2) the use of mathematics, logic and algebras, as well as discrete mathematics: Sets, Cartesians, lists, functions, maps; (3) property as well as model-oriented specifications; (4) semiotics in the form...... are: (A) Emphasis on design: Literally a thousand development examples are given; and on ``Calculi'' of (B) domain and (C) requirements engineering: Domain facet ``operators'' like: (d.1) Instrinsics, (d.2) support technology, (d.3) management & organisation, (d.4) rules & regulations, (d.5) human...

Generic Safety Requirements for Developing Safe Insulin Pump Software

Science.gov (United States)

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

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

Science.gov (United States)

1976-01-01

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

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

International Nuclear Information System (INIS)

Glasscock, J.A.

1995-01-01

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

Software Testing Requires Variability

DEFF Research Database (Denmark)

Christensen, Henrik Bærbak

2003-01-01

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

Quality assurance requirements for the computer software and safety analyses

International Nuclear Information System (INIS)

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

IAEA/NDS requirements related to database software

International Nuclear Information System (INIS)

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

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

International Nuclear Information System (INIS)

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)

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

Energy Technology Data Exchange (ETDEWEB)

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

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

International Nuclear Information System (INIS)

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

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

Energy Technology Data Exchange (ETDEWEB)

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.

Spectrum analysis on quality requirements consideration in software design documents.

Science.gov (United States)

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.

Incubator Display Software Cost Reduction Toolset Software Requirements Specification

Science.gov (United States)

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.

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

Science.gov (United States)

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.

Arquitectura orientada a servicios para software de apoyo para el proceso personal de software A service oriented architecture for the implementation of the personal software process

Directory of Open Access Journals (Sweden)

Erick Salinas

2011-06-01

Full Text Available El presente trabajo describe una arquitectura orientada a servicios para un software que tiene como objetivo facilitar la implementación de un Proceso Personal de Software en un equipo de desarrollo u organización. Entre las características que posee este software y que son relevantes de mencionar están las de entregar extensibilidad e independencia, esto se ve reflejado en la facilidad para agregar nuevas herramientas al proceso de desarrollo de software integradas al Proceso Personal de Software con un máximo de independencia de sistemas operativos y lenguajes de programación. El software implementado realiza la recolección de los datos necesarios para el Proceso Personal de Software casi completamente automática, considerando que el administrador solamente clasifica los errores que pueden ocurrir cuando se utiliza algún lenguaje de programación en particular, entre otras pequeñas tareas. Esta facilidad de uso hace que la implementación del Proceso Personal de Software se realice exitosamente con un bajo esfuerzo requerido por los integrantes del equipo de desarrollo.This work describes a service oriented architecture of a software application that facilitates the implementation of the Personal Software Process by a development team or an organization. Some of the characteristics of this software and which are important to mention are extensibility and technical environment independence. These characteristics facilitate the process of adding new tools to the software development process integrating them to the Personal Software Process independently of the operating systems and programming languages being used. The implemented software undertakes the data collection necessary to the Personal Software Process almost automatically, since the administrator must only classify the errors that may occur when a particular programming language is used, among other small tasks. This ease of use approach helps to make the implementation of

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

Science.gov (United States)

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

A report on NASA software engineering and Ada training requirements

Science.gov (United States)

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.

The Antiphagocytic Activity of SeM of Streptococcus equi Requires Capsule.

Science.gov (United States)

Timoney, John F; Suther, Pranav; Velineni, Sridhar; Artiushin, Sergey C

2014-01-01

Resistance to phagocytosis is a crucial virulence property of Streptococcus equi (Streptococcus equi subsp. equi; Se), the cause of equine strangles. The contribution and interdependence of capsule and SeM to killing in equine blood and neutrophils were investigated in naturally occurring strains of Se. Strains CF32, SF463 were capsule and SeM positive, strains Lex90, Lex93 were capsule negative and SeM positive and strains Se19, Se1-8 were capsule positive and SeM deficient. Phagocytosis and killing of Se19, Se1-8, Lex90 and Lex93 in equine blood and by neutrophils suspended in serum were significantly (P ≤ 0.02) greater compared to CF32 and SF463. The results indicate capsule and SeM are both required for resistance to phagocytosis and killing and that the anti-phagocytic property of SeM is greatly reduced in the absence of capsule.

Metric-based method of software requirements correctness improvement

Directory of Open Access Journals (Sweden)

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.

Knowledge-based requirements analysis for automating software development

Science.gov (United States)

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.

Specification for Visual Requirements of Work-Centered Software Systems

National Research Council Canada - National Science Library

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

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

OpenAIRE

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

Functional requirements for gas characterization system computer software

International Nuclear Information System (INIS)

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

Marketing Mix del Software.

Directory of Open Access Journals (Sweden)

Yudith del Carmen Rodríguez Pérez

2006-03-01

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

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

DEFF Research Database (Denmark)

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

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

Directory of Open Access Journals (Sweden)

Castro Mecías, L.T.

2015-06-01

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

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

Directory of Open Access Journals (Sweden)

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.

Taxonomía de riesgos de outsourcing de software Software outsourcing risk taxonomy

Directory of Open Access Journals (Sweden)

Gloria Piedad Gasca-Hurtado

2013-04-01

Full Text Available Para las organizaciones la estrategia de outsourcing de software (OS se ha constituido en una alternativa estratégica de reducción de costos y mejora de la calidad de software. Sin embargo, la complejidad de la gestión de este tipo de proyectos aumenta, debido a la relación de actores diferentes (cliente y proveedor, de la cual depende en gran medida el éxito de estos proyectos. Identificar, analizar y gestionar los riesgos que afectan este tipo de proyectos, son buenas prácticas que se pueden llevar a cabo para establecer indicadores de gestión claves para el éxito de los proyectos. Es por esta razón que el objetivo de este trabajo es diseñar una taxonomía de riesgos de OS, es decir, una estructura de clasificación jerárquica de riesgos basada en los proyectos de OS que facilite la identificación de riesgos, que contribuya a la realización de un análisis de riesgos ágil y preciso, para su posterior gestión a lo largo de todo el proceso de OS. La taxonomía que se propone ha sido validada en un caso de estudio correspondiente a un proyecto de compra de software preelaborado. Los resultados se muestran en la última parte de este trabajo y se analiza la forma como dichos resultados impacta el proyecto en el cual fue implementada la taxonomía y su utilidad en el refinamiento de los procesos organizacionales de la empresa, a partir de las lecciones aprendidas.In recent years, the software outsourcing (SO strategy for organizations has become a useful and important alternative, as well as SO projects. SO projects have many complexities due to several factors affecting management. These complexities and importance of SO require that successfull projects meet a parameter set: budget, cost, schedule, among others. This requirement can be met through the implementation of methods and techniques of risk management (RM. RM is a process to prevent problems, establish actions to follow, and monitor the project to ensure success. Likewise

Towards an Understanding of Enabling Process Knowing in Global Software Development: A Case Study

DEFF Research Database (Denmark)

Zahedi, Mansooreh; Babar, Muhammad Ali

2014-01-01

Shared understanding of Software Engineering (SE) processes, that we call process knowing, is required for effective communication and coordination and communication within a team in order to improve team performance. SE Process knowledge can include roles, responsibilities and flow of informatio...... challenges of lack of process knowing and how an organization can enable process knowing for achieving the desired results that also help in increasing social interactions and positive behavioral changes......Shared understanding of Software Engineering (SE) processes, that we call process knowing, is required for effective communication and coordination and communication within a team in order to improve team performance. SE Process knowledge can include roles, responsibilities and flow of information...... over a project lifecycle. Developing and sustaining process knowledge can be more challenging in Global Software Development (GSD). GSD distances can limit the ability of a team to develop a common understanding of processes. Anecdotes of the problems caused by lack of common understanding of processes...

SeDA: A software package for the statistical analysis of the instrument drift

International Nuclear Information System (INIS)

Lee, H. J.; Jang, S. C.; Lim, T. J.

2006-01-01

The setpoints for safety-related equipment are affected by many sources of an uncertainty. ANSI/ISA-S67.04.01-2000 [1] and ISA-RP6 7.04.02-2000 [2] suggested the statistical approaches for ensuring that the safety-related instrument setpoints were established and maintained within the technical specification limits [3]. However, Jang et al. [4] indicated that the preceding methodologies for a setpoint drift analysis might be insufficient to manage a setpoint drift on an instrumentation device and proposed new statistical analysis procedures for the management of a setpoint drift, based on the plant specific as-found/as-left data. Although IHPA (Instrument History Performance Analysis) is a widely known commercial software package to analyze an instrument setpoint drift, several steps in the new procedure cannot be performed by using it because it is based on the statistical approaches suggested in the ANSI/ISA-S67.04.01 -2000 [1] and ISA-RP67.04.02-2000 [2], In this paper we present a software package (SeDA: Setpoint Drift Analysis) that implements new methodologies, and which is easy to use, as it is accompanied by powerful graphical tools. (authors)

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

Energy Technology Data Exchange (ETDEWEB)

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)

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

Energy Technology Data Exchange (ETDEWEB)

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)

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

International Nuclear Information System (INIS)

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

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

Energy Technology Data Exchange (ETDEWEB)

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.

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

International Nuclear Information System (INIS)

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

2005-01-01

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

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

Science.gov (United States)

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.

Thickness calculation software of the thermal insulation in facilities using thermal solar energy; Software para el calculo de espesores del aislante termico en instalaciones de aprovechamiento de energia solar termica

Energy Technology Data Exchange (ETDEWEB)

Portillo Jimenez, Canek [Universidad Autonoma de Sinaloa, Culiacan, Sinaloa (Mexico)]. E-mail: cnk@uas.uasnet.mx

2010-11-15

It is presented a software application for calculating the thickness of the thermal insulation used in various facilities where there are thermal systems using solar energy. The software facilitates the calculation of the thermal cover thickness over components such as pipes (flat or round), storage and other devices that require thermal protection, installed in outdoors or indoors. The software was programmed in Visual Basic by following the technical specifications of the current regulations in the field. Application examples are performed, obtaining certain results that are discussed briefly. [Spanish] Se presenta un software de aplicacion para el calculo de los espesores de los aislantes termicos, utilizados en diferentes instalaciones donde existen sistemas de aprovechamiento termico de energia solar. El software facilita el calculo del grosor del recubrimiento termico en componentes tales como: tuberias (planas o circulares), depositos acumuladores y otros aparatos que necesiten proteccion termica, instalados en exteriores o en interiores. El software fue programado en Visual Basic siguiendo las especificaciones tecnicas de la normatividad vigente en la materia. Se realizan ejemplos de aplicacion, donde se obtienen ciertos resultados de los cuales se hace una breve discusion.

Calidad del software: camino hacia una verdadera industria del software

Directory of Open Access Journals (Sweden)

Saulo Ernesto Rojas Salamanca

1999-07-01

Full Text Available El software es quizá uno de los productos de la ingeniería que más ha evolucionado en muy poco tiempo, pasando desde el software empírico o artesanal hasta llegar al software desarrollado bajo los principios y herramientas de la ingeniería del software. Sin embargo, dentro de estos cambios, las personas encargadas de la elaboración del software se han enfrentado a problemas muy comunes: unos debido a la exigencia cada vez mayor en la capacidad de resultados del software, debido al permanente cambio de condiciones lo que aumenta su complejidad y obsolescencia; y otros, debido a la carencia de herramientas adecuadas y estándares de tipo organizacional encaminados al mejoramiento de los procesos en el desarrollo del software. Hacia la búsqueda de mecanismos de solución de estos últimos problemas se orienta este artículo...

Software requirements definition Shipping Cask Analysis System (SCANS)

International Nuclear Information System (INIS)

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

Treated effluent disposal system process control computer software requirements and specification

International Nuclear Information System (INIS)

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

Free software, Open source software, licenses. A short presentation including a procedure for research software and data dissemination

OpenAIRE

Gomez-Diaz , Teresa

2014-01-01

4 pages. Spanish version: Software libre, software de código abierto, licencias. Donde se propone un procedimiento de distribución de software y datos de investigación; The main goal of this document is to help the research community to understand the basic concepts of software distribution: Free software, Open source software, licenses. This document also includes a procedure for research software and data dissemination.

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

Directory of Open Access Journals (Sweden)

Tomasz  Grasza

2014-06-01

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

Statistical Software Engineering

Science.gov (United States)

1998-04-13

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

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

Directory of Open Access Journals (Sweden)

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.

The Business Case for Automated Software Engineering

Science.gov (United States)

Menzies, Tim; Elrawas, Oussama; Hihn, Jairus M.; Feather, Martin S.; Madachy, Ray; Boehm, Barry

2007-01-01

Adoption of advanced automated SE (ASE) tools would be more favored if a business case could be made that these tools are more valuable than alternate methods. In theory, software prediction models can be used to make that case. In practice, this is complicated by the 'local tuning' problem. Normally. predictors for software effort and defects and threat use local data to tune their predictions. Such local tuning data is often unavailable. This paper shows that assessing the relative merits of different SE methods need not require precise local tunings. STAR 1 is a simulated annealer plus a Bayesian post-processor that explores the space of possible local tunings within software prediction models. STAR 1 ranks project decisions by their effects on effort and defects and threats. In experiments with NASA systems. STARI found one project where ASE were essential for minimizing effort/ defect/ threats; and another project were ASE tools were merely optional.

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

NARCIS (Netherlands)

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

NaviSE: superenhancer navigator integrating epigenomics signal algebra.

Science.gov (United States)

Ascensión, Alex M; Arrospide-Elgarresta, Mikel; Izeta, Ander; Araúzo-Bravo, Marcos J

2017-06-06

Superenhancers are crucial structural genomic elements determining cell fate, and they are also involved in the determination of several diseases, such as cancer or neurodegeneration. Although there are pipelines which use independent pieces of software to predict the presence of superenhancers from genome-wide chromatin marks or DNA-interaction protein binding sites, there is not yet an integrated software tool that processes automatically algebra combinations of raw data sequencing into a comprehensive final annotated report of predicted superenhancers. We have developed NaviSE, a user-friendly streamlined tool which performs a fully-automated parallel processing of genome-wide epigenomics data from sequencing files into a final report, built with a comprehensive set of annotated files that are navigated through a graphic user interface dynamically generated by NaviSE. NaviSE also implements an 'epigenomics signal algebra' that allows the combination of multiple activation and repression epigenomics signals. NaviSE provides an interactive chromosomal landscaping of the locations of superenhancers, which can be navigated to obtain annotated information about superenhancer signal profile, associated genes, gene ontology enrichment analysis, motifs of transcription factor binding sites enriched in superenhancers, graphs of the metrics evaluating the superenhancers quality, protein-protein interaction networks and enriched metabolic pathways among other features. We have parallelised the most time-consuming tasks achieving a reduction up to 30% for a 15 CPUs machine. We have optimized the default parameters of NaviSE to facilitate its use. NaviSE allows different entry levels of data processing, from sra-fastq files to bed files; and unifies the processing of multiple replicates. NaviSE outperforms the more time-consuming processes required in a non-integrated pipeline. Alongside its high performance, NaviSE is able to provide biological insights, predicting cell

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

Science.gov (United States)

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.

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

Science.gov (United States)

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

2012-03-09

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

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

Directory of Open Access Journals (Sweden)

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.

Development to requirements for a procedures software tool

International Nuclear Information System (INIS)

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

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

Energy Technology Data Exchange (ETDEWEB)

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

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

National Research Council Canada - National Science Library

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

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

NARCIS (Netherlands)

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

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

International Nuclear Information System (INIS)

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

National Ignition Facility subsystem design requirements supervisory control software SSDR 1.5.2

International Nuclear Information System (INIS)

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)

Defining DSL design principles for enhancing the requirements elicitation process

Directory of Open Access Journals (Sweden)

Gustavo Arroyo

2012-03-01

Full Text Available La Elicitación de Requisitos propicia el entendimiento de las necesidades de los usuarios con respecto a un desarrollo de software. Los métodos que se emplean provienen de las ciencias sociales por lo que se carece de una retroalimentación ejecutable. Consecuentemente, la primera versión del software podría no cumplir con las expectativas. El uso de DSLs como herramientas para el descubrimiento de requisitos es una idea aceptada, desafortunadamente, muy pocos trabajos en la literatura se enfocan en la definición de principios de diseño de DSLs. En este trabajo planteamos principios de diseño de DSLs orientados a la elicitación de requisitos, enseguida, generamos casos de prueba en ANTLR, Ruby y Curry. También, enunciamos el perfil que debe tener el nuevo analista de software. Con ello, se incrementa la retroalimentación entre los involucrados en el desarrollo de software y se mejora el producto.Requirements elicitation is concerned with learning and understanding the needs of users w.r.t. a new software development. Frequently the methods employed for requirements elicitation are adapted from areas like social sciences that do not include executable (prototype based on feedback. As a consequence, it is relatively common to discover that the first release does not fit the requirements defined at the beginning of the project. Using domain-specific languages (DSLs as an auxiliary tool for requirements elicitation is a commonly well accepted idea. Unfortunately, there are few works in the literature devoted to the definition of design principles for DSLs to be experienced in the frameworks for DSL developing such as ANTLR, Ruby, and Curry. We propose design principles for the DSL development (regardless of paradigm which are sufficient to model the domain in a requirements phase. Further more we enunciate a new profile for the requirements analyst and a set of elicitation steps. The use of DSLs not only giveus an immediate feedback with

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

Science.gov (United States)

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

2016-08-01

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

THE USE OF ANALOG PROCESSES AS A FACTOR TO IMPROVE SOFTWARE QUALITY: A CASE STUDY OF ORTHO-MEDICAL SOFTWARE

OpenAIRE

GABRIEL VIEIRA MONTEIRO

2003-01-01

A presente dissertação avalia um software médico através de parâmetros e critérios ergonômicos. Primeiramente descrevem- se os conceitos relativos a Tecnologia da Informação e conceitua-se o software como um dos subsistemas de qualquer sistema de Tecnologia da Informação. A partir de então, verificou-se as etapas de desenvolvimento de software, relacionados ao contexto de usabilidade. Levantaram-se também os principais problemas de interação encontrados no...

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

International Nuclear Information System (INIS)

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

Requirements Specification for Open Source Software Selection

OpenAIRE

YANG, YING

2008-01-01

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

A software engineering process for safety-critical software application

International Nuclear Information System (INIS)

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

1995-01-01

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

Formalization of software requirements for information systems using fuzzy logic

Science.gov (United States)

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.

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

Science.gov (United States)

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.

Metodología de desarrollo y mantenimiento de software para una fábrica de software

OpenAIRE

Ocola Agüero, Robert Percy; Ocola Agüero, Robert Percy

2012-01-01

Actualmente la fábrica de software se encarga de ejecutar proyectos de desarrollo y mantenimiento de sistemas de información para empresas y entidades estatales. Esta tesis plantea proponer una nueva metodología que mejore el desarrollo y mantenimiento de la fábrica de software. Para ello se realizó un análisis de las diversas fases de desarrollo de la metodología actualmente existente y con los resultados obtenidos se propuso una metodología que agregue valor. Finalmente se realizó la aplica...

Software quality assurance plans for safety-critical software

International Nuclear Information System (INIS)

Liddle, P.

2006-01-01

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

Software libre, software de código abierto, licencias. Donde se propone un procedimiento de distribución de software y datos de investigación

OpenAIRE

Gomez-Diaz, Teresa

2015-01-01

English version: Free software, Open source software, licenses. A short presentation including a procedure for research software and data dissemination; El objetivo de este documento es ayudar a la comunidad de investigación a entender los conceptos básicos de la distribución de software: software libre, software de código abierto, licencias. Este documento incluye igualmente un procedimiento para la distribución de datos y software de investigación.

The Design and Development of a Computerized Tool Support for Conducting Senior Projects in Software Engineering Education

Science.gov (United States)

Chen, Chung-Yang; Teng, Kao-Chiuan

2011-01-01

This paper presents a computerized tool support, the Meetings-Flow Project Collaboration System (MFS), for designing, directing and sustaining the collaborative teamwork required in senior projects in software engineering (SE) education. Among many schools' SE curricula, senior projects serve as a capstone course that provides comprehensive…

Software library of meteorological routines for air quality models; Libreria de software de procedimientos meteorologicos para modelos de dispersion de contaminantes

Energy Technology Data Exchange (ETDEWEB)

Galindo Garcia, Ivan Francisco

1999-04-01

Air quality models are an essential tool for most air pollution studies. The models require, however, certain meteorological information about the model domain. Some of the required meteorological parameters can be measured directly, but others must be estimated from available measured data. Therefore, a set of procedures, routines and computational programs to obtain all the meteorological and micrometeorological input data is required. The objective in this study is the identification and implementation of several relationships and methods for the determination of all the meteorological parameters required as input data by US-EPA recommended air pollution models. To accomplish this, a study about air pollution models was conducted, focusing, particularly, on the model meteorological input data. Also, the meteorological stations from the Servicio Meteorologico Nacional (SMN) were analyzed. The type and quality of the meteorological data produced was obtained. The routines and methods developed were based, particularly, on the data produced by SMN stations. Routines were organized in a software library, which allows one to build the specific meteorological processor needed, independently of the model used. Methods were validated against data obtained from an advanced meteorological station owned and operated by the Electrical Research Institute (Instituto de Investigaciones Electricas (IIE)). The results from the validation show that the estimation of the parameters required by air pollution models from routinely available data from Mexico meteorological stations is feasible and therefore let us take full advantage of the use of air pollution models. As an application example of the software library developed, the building of a meteorological processor for a specific air pollution model (CALPUFF) is described. The big advantage the library represents is evident from this example. [Espanol] Los modelos de dispersion de contaminantes constituyen una herramienta

Software attribute visualization for high integrity software

Energy Technology Data Exchange (ETDEWEB)

Pollock, G.M.

1998-03-01

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

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

Science.gov (United States)

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.

Las ontologías en la ingeniería de software: un acercamiento de dos grandes áreas del conocimiento Ontologies in software engineering: approaching two great knowledge areas

Directory of Open Access Journals (Sweden)

Carlos Mario Zapata Jaramillo

2010-01-01

Full Text Available Los conceptos ontológicos se suelen acercar más a la ingeniería del conocimiento, por lo que los ingenieros del software no los suelen aplicar para resolver problemas de su área. Es necesario que los ingenieros de software se apropien de las ontologías, pues éstas proporcionan un vocabulario común, que podría contribuir en la solución de problemas recurrentes en ingeniería del software, tales como la dificultad de la comunicación entre analista e interesado para definir los requisitos de un sistema, la baja reutilización de componentes y la escasa generación automática de código, entre otros. En este artículo se presenta un primer enlace entre las ontologías y la ingeniería de software mediante la recopilación y análisis de la literatura relativa a la utilización de las ontologías en las diferentes fases del ciclo de vida de un producto de software.Ontology concepts have been traditionally linked to knowledge engineering and software engineers have not applied them to solve problems of this area. It is necessary that software engineers use these ontologies, since they provide a common language, which can contribute to the solution of some common software engineering problems like difficulties in communication between the analyst and the interested person in order to define a system requirements, the low components re-use, and scarce automatic generation in code generation, among others. In this paper, a first encounter between ontologies and software engineering by means of a state-of-the-art analysis related to the use of ontologies in several phases of software development life cycle is presented.

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

Science.gov (United States)

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…

Identifying Relevant Studies in Software Engineering

DEFF Research Database (Denmark)

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

2011-01-01

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

NASA software documentation standard software engineering program

Science.gov (United States)

1991-01-01

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

BALALU: Anticipar los cambios en un Software OA

Directory of Open Access Journals (Sweden)

Cecilia Andrea Fuentes Zamorano

2014-06-01

Full Text Available El mantenimiento y evolución del software muchas veces se vuelve una tarea engorrosa, debido a que el software no se encuentra adecuadamente documentado, o bien las personas destinadas a realizar los cambios no son los propios desarrolladores del software, haciendo que la comprensión del código fuente sea un trabajo complejo. Esto se vuelve más difícil cuando se utilizan aspectos debido a que el código fuente base implícitamente invoca al código de los aspectos. La invocación implícita es especificada por los constructores específicos aspectuales (pointcuts agregando un nivel extra de indirección, que hace más difícil comprender el comportamiento total del software. Diversos problemas como pointcuts frágiles e interacciones entre aspectos se producen fácil e inadvertidamente en la evolución del software orientado a aspectos, ya sea a partir de simples cambios en el código o bien por la aplicación de refactorings. Los desarrolladores deben analizar manualmente el código fuente (de aspectos y clases para identificar estas ocurrencias, agregar más pruebas, en definitiva, se aumentan los costos y esfuerzos durante la evolución y mantenimiento. Consecuentemente, existe la necesidad de plantear estrategias, técnicas y herramientas que permitan a los desarrolladores de software anticipar, analizar y evaluar los efectos e impactos en el software con aspectos, producto de la evolución del software. En este trabajo planteamos como las características de la Programación Orientada a Aspectos (POA mencionadas, inciden negativamente en la evolución y mantenimiento de aplicaciones OA, y proponemos la herramienta BaLaLu cuya finalidad es anticipar las consecuencias que un cambio podrá tener en una aplicación que usa aspectos. La estructura de este informe se encuentra conformada en base a los siguientes elementos que se detallan: la Sección 2 corresponde a una breve introducción a la POA y al Lenguaje Orientado a Aspectos Aspect

Graph Based Verification of Software Evolution Requirements

NARCIS (Netherlands)

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

Planejamento da assistência de enfermagem: proposta de um software-protótipo Planificación del cuidado de enfermería: propuesta de un software-prototipo Nursing care planning: proposal for a software prototype

Directory of Open Access Journals (Sweden)

Dircelene Jussara Sperandio

2005-12-01

Full Text Available O propósito deste estudo foi descrever as etapas de desenvolvimento de um software-protótipo que possibilite aos enfermeiros, no âmbito hospitalar, atender ao planejamento da assistência de enfermagem, prescrição de enfermagem e a documentação de forma informatizada. A metodologia utilizada fundamentou-se no conceito do ciclo de vida de prototipação. Sedimentou-se em duas fases: a de definição e a de desenvolvimento. A fase de definiç��o iniciou-se com a etapa de planejamento, seguida pela definição e análise dos requisitos necessários para a construção e culminou com a produção da especificação de requisitos do software. A fase de desenvolvimento traduziu o conjunto de requisitos em um modelo informatizado, com 10 módulos, referentes ao processo de sistematização da assistência de enfermagem. A avaliação desse recurso inovador para a Sistematização da Assistência de Enfermagem nos diferentes estágios do seu processo será objeto de estudo posterior.El propósito de este estudio es desarrollar un software-prototipo para ayudar las enfermeras planear el cuidado de enfermería, hacer intervenciones y toda la documentación de una manera informatizada. La metodología se basa en el ciclo de vida de desarrollo del sistema, particularmente el concepto del prototipo, siguiendo dos fases: la definición y el desarrollo. La fase de la definición empezó con una etapa de planificación, seguido por la definición y el análisis de los requisitos para la construcción, y culminó con la especificación de los requisitos del software. La fase de desarrollo tradujo el grupo de requisitos en modelo informatizado, estructurado en 10 módulos, con respecto al proceso de alimentar el sistema del cuidado. El desempeño de este recurso innovador en las diferentes etapas del proceso de sistematización de la atención de enfermería será objeto de un estudio subsiguiente.This study aims to develop a software prototype to help

Herramientas software para una óptima gestión del proceso de desarrollo de software, a utilizarse en las empresas de software de la provincia de Catamarca

OpenAIRE

Haustein, María Carolina; Palliotto, Diana; Korzenieswki, María Isabel

2013-01-01

Una de las metas siempre vigente en las empresas desarrolladoras de software, es mejorar el proceso de desarrollo, para lo cual, se fueron fijando y ejecutando distintas estrategias, la más recurrente fue la creación de nuevas metodologías. Hasta que a principios del siglo XXI, se advirtió que lo que fallaba en la gran parte de las empresas, era la gestión en el desarrollo de software, tarea esta, sumamente importante, ya que se encarga de la planificación, asignación de recursos, la document...

Software industrial flexible

OpenAIRE

Díaz Araya, Daniel; Muñoz, Leandro; Sirerol, Daniel; Oviedo, Sandra; Ibáñez, Francisco S.

2012-01-01

En este trabajo se pretende investigar y proponer técnicas, métodos y tecnologías que permitan el desarrollo de software flexible en ambientes industriales. El objetivo es generar métodos y técnicas para facilitar el desarrollo de software flexible en ambientes industriales. Las áreas de investigación son los sistemas de scheduling de producción, la generación de software para plataformas de hardware abiertas y la innovación.

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

DEFF Research Database (Denmark)

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

ARQUITECTURA DE SOFTWARE, ESQUEMAS Y SERVICIOS

Directory of Open Access Journals (Sweden)

Pedro Ángel Romero

2006-04-01

Full Text Available

Cuando en la industria de software los productos tienen requerimientos cada vez más complejos y dinámicos, y los tiempos para desarrollarlos son cada vez menores; la reutilización y el bajo acoplamiento entre los componentes cobran vital importancia. En este trabajo, partiendo de las definiciones de arquitectura de software y esquema se tratan las características del paradigma de arquitectura orientada a servicios y se exponen algunos elementos significativos que muestran cómo los servicios son la evolución natural de los componentes de software. También se comentan algunas cuestiones a tener en cuenta a la hora de diseñar orientado a servicios.

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

International Nuclear Information System (INIS)

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

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

International Nuclear Information System (INIS)

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

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

Energy Technology Data Exchange (ETDEWEB)

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.

Great software debates

CERN Document Server

Davis, A

2004-01-01

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

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

Directory of Open Access Journals (Sweden)

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.

¿COLOMBIA DEBE APOSTARLE AL SOFTWARE LIBRE, AL DE FUENTE ABIERTA O AL PROPIETARIO?

Directory of Open Access Journals (Sweden)

Luis Alberto Girón Murillo

2014-06-01

Full Text Available Es complejo para gestores y administradores conocer las implicaciones que la adopción de modelos de desarrollo de software tendría para una región. Este artículo ofrece una evaluación de las implicaciones dinámicas que para el desarrollo de software de una región tendría el apostar de forma excluyente al software libre, al software de fuente abierta y al software propietario. Se desarrolló un modelo de simulación en Vensim de la dinámica de sistemas en donde se evaluaron 3 escenarios: uno en donde se adopta de forma excluyente el software libre, uno en donde se adopta el software propietario y uno en donde se adopta el software de fuente abierta. Se ofrecen descripciones y explicaciones de los resultados que sugieren las potencialidades de cada uno de los modelos de desarrollo evaluados.

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

Energy Technology Data Exchange (ETDEWEB)

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.

ANÁLISIS DE LA INGENIERÍA DE REQUISITOS ORIENTADA POR ASPECTOS SEGÚN LA INDUSTRIA DEL SOFTWARE

Directory of Open Access Journals (Sweden)

Luis Fernando Londoño

2008-07-01

Full Text Available La aplicación de buenas prácticas en la gestión de requisitos de software es una condición fundamental para lograr productos de calidad. Por lo tanto, es importante que las compañías de desarrollo de software mantengan una investigación constante alrededor de nuevas técnicas que mejoren actividades de requisitos tales como levantamiento, especificación y modelado. En este artículo se presenta un estudio de los enfoques más representativos de la ingeniería de requisitos orientada por aspectos que podrían ayudar a resolver problemas que enfrentan las compañías de software durante las etapas tempranas de desarrollo. Se hace un análisis comparativo entre los enfoques, a partir de los criterios de alcance, trazabilidad, composición de requisitos, manejo de conflictos, mapeo, validación-verificación y escalabilidad. Los resultados obtenidos permiten detectar las oportunidades que el enfoque de aspectos ofrece para mejorar el proceso de los requisitos.Applying good practices to manage software requirements is a basic condition to obtain quality products. Therefore, it is important that software companies maintain a constant research around of new techniques and mechanisms to improve requirements activities such as elicitation, specification, and modeling. In this paper, we present a study of most representative aspect-oriented requirement approaches in order to analyze the way how these could support issues confronted by software companies during early stages of the lifecycle. Thus, we make a comparative analysis among approaches under criteria defined such as scope, traceability, requirements composition, conflict management, mapping, validation-verification, and scalability. Results achieved allowing us to know opportunities offered by aspect-oriented approaches so as to improve the requirement process.

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

International Nuclear Information System (INIS)

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

1992-01-01

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

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

NARCIS (Netherlands)

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.

Socio-Cultural Challenges in Global Software Engineering Education

Science.gov (United States)

Hoda, Rashina; Babar, Muhammad Ali; Shastri, Yogeshwar; Yaqoob, Humaa

2017-01-01

Global software engineering education (GSEE) is aimed at providing software engineering (SE) students with knowledge, skills, and understanding of working in globally distributed arrangements so they can be prepared for the global SE (GSE) paradigm. It is important to understand the challenges involved in GSEE for improving the quality and…

Armonización de modelos de calidad del software

Directory of Open Access Journals (Sweden)

Gabriel Alberto Garcia Mireles

2013-06-01

Full Text Available La tendencia actual entre las organizaciones que desarrollan software es la adopción de más de un modelo de calidad para estar en condiciones de competir en diversos sectores del mercado. En esa situación, las organizaciones se enfrentan al problema de coordinar la implantación de múltiples modelos de tal manera que cada modelo logre los beneficios esperados, y al mismo tiempo, que los costos y esfuerzo de implantación sean mínimos. Como respuesta a este problema, surge la armonización de modelos de calidad del software. Actualmente los estudios se centran en la composición de modelos de calidad que abordan prácticas del proceso de desarrollo de software. Sin embargo, las organizaciones también deberían considerar la perspectiva de la calidad del producto. En este artículo, se presenta un avance de la investigación en la armonización de modelos de calidad que toma en cuenta ambas perspectivas, proceso y producto. Se describe la técnica que se propuso para realizar comparaciones de bajo nivel en este contexto. La técnica se aplica en los modelos CMMI-DEV, ISO 12207 e ISO 25010 y, como resultado, se encuentra que los modelos que abordan la perspectiva de proceso contienen prácticas, que corresponden a las etapas de análisis y diseño de software, en donde se debería prestar más atención a la calidad del producto de software.

Calidad de software: Actividades en curso para contribuir al desarrollo de la industria del software en la región NEA

OpenAIRE

Estayno, Marcelo G.; Dapozo, Gladys N.; Cuenca Pletsch, Liliana Raquel; Greiner, Cristina L.; Medina, Yenisley; Tomaselli, G.; Chica, N.; Bernal, N.; Méndez, G.

2010-01-01

Este trabajo describe los resultados preliminares y las actividades de investigación y desarrollo que se llevan a cabo en el marco del proyecto mencionado. Se realizó un estudio de las características de las pymes de software de la región que se utilizará como marco de referencia de las actividades del proyecto, se definieron propuestas metodológicas orientadas a la vinculación entre las universidades participantes y las empresas de software nucleadas en polos tecnológicos que dieron lugar...

HAZARD ANALYSIS SOFTWARE

International Nuclear Information System (INIS)

Sommer, S; Tinh Tran, T.

2008-01-01

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

El movimiento del software libre

OpenAIRE

Prudencio Óscar Mochi Alemán

2002-01-01

El objetivo de este trabajo es describir el surgimiento y desarrollo del movimiento de software libre. Para ello se analizan algunas características importantes que dan cuenta del origen y desarrollo del mismo, así como de sus momentos más críticos y sus tensiones, sus desafíos y sus retos. Otra de las grandes inquietudes de este trabajo, es intentar descifrar cómo el movimiento del software libre y Linux, en su versión más conocida, sobrevivieron y se afirmaron hasta llegar a ...

EDITORIAL: Para mejorar la calidad del software

Directory of Open Access Journals (Sweden)

Edgar Serna M.

2015-12-01

Full Text Available Se podría decir que somos software-dependientes, porque como sociedad moderna la mayoría de nuestras actividades y relaciones están condicionadas por, o dependen de, este desarrollo tecnológico. Pero de acuerdo con los organismos encargados de su control y los mismos usuarios, al parecer los procedimientos con los cuales se produce todavía no han superado la llamada crisis del software de los años 60, y se continúa entregando con deficiencias en calidad, seguridad y fiabilidad

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

National Research Council Canada - National Science Library

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

Diversity requirements for safety critical software-based automation systems

International Nuclear Information System (INIS)

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)

Ingeniería dirigida por modelos y calidad de software

OpenAIRE

Ruiz-Rube, Iván

2014-01-01

La gestión de la calidad del software tiene por objetivo planificar, asegurar, controlar y mejorar la calidad del software que se desarrolla o se mantiene. Sin embargo, suele ser habitual que no se le dediquen los esfuerzos y recursos necesarios para su puesta en marcha, aludiendo a que las actividades de gestión de la calidad no conducen a producir software. Por este motivo, es importante investigar nuevas maneras de llevar a cabo actividades de calidad, con el menor esfuerzo posible. En...

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

Science.gov (United States)

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.

Software engineering the current practice

CERN Document Server

Rajlich, Vaclav

2011-01-01

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

DISEÑO DE SOFTWARE EDUCATIVO BASADO EN COMPETENCIAS

Directory of Open Access Journals (Sweden)

Manuel Fernando Caro Piñeres

2009-01-01

Full Text Available El presente artículo describe un modelo de diseño de software educativo basado en competencias, el cual presenta una visión integral del desarrollo de estas aplicaciones mediante la combinación de componentes pedagógicos, didácticos, multimediales y de ingeniería de software. El modelo sugerido se compone de cinco fases que detallan paso a paso los aspectos que se deben tener en cuenta para la creación de softwareeducativo. La fase inicial constituye la descripción del diseño educativo, en la cual se analiza la necesidad educativa, se plantean los objetivos de aprendizaje y se describen las competencias que se pretenden desarrollar con la aplicación; del diseño de éstas resultan las siguientes subfases: diseño de contenidos, diseño pedagógico y diseño de aprendizaje. Las competencias son el aspecto fundamental que abarca el desarrollo de este modelo, las cuales son primordiales para la realización de las fases a seguir conformadas por el diseño computacional y el diseño multimedial, estas se encargan del análisis y modelado del software, y del sistema de comunicación hombre-máquina. En la fase de producción se ensamblan los componentes elaborados o recolectados, según el caso. La última fase es la de aplicación, donde se hacen las pruebas de rigor para evaluar el desempeño del software en los contextos para los que fue desarrollado.

DIRECTRICES PARA LA CONSTRUCCIÓN DE ARTEFACTOS DE PERSISTENCIA EN EL PROCESO DE DESARROLLO DE SOFTWARE

Directory of Open Access Journals (Sweden)

Juan Bernardo Quintero

2008-07-01

Full Text Available El almacenamiento de datos es uno de los procesos que se halla en casi la totalidad de los sistemas de información. El tratamiento que se les da a las bases de datos durante el desarrollo de software resulta un factor determinante para el buen desempeño de un sistema. La acelerada evolución tecnológica y el desarrollo de la industria del software han conducido al surgimiento de diversas estrategias de modelado y numerosas técnicas de acceso a datos. En este trabajo se precisan los referentes conceptuales y prácticos para la construcción de los productos relacionados con las bases de datos, el acceso a estas y el tratamiento que se les da en la industria a los llamados artefactos de persistencia.Data storage is a process required in almost every information system nowadays; the treatment given to databases during the software development can be a determining factor in order to achieve good performance of a resulting system. The accelerated technological evolution and the progress of the software enterprises have given rise to diverse modeling strategies and several data access techniques. This work explains the practical and conceptual references for the construction of products related to databases, the access techniques to them and the handling that so-called persistence artifacts have at an industrial level.

Software Engineering Improvement Plan

Science.gov (United States)

2006-01-01

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

Software del sistema osteomioarticular

Directory of Open Access Journals (Sweden)

Dianelys León Medina

2015-06-01

Full Text Available Introducción: la aplicación en la enseñanza de las Tecnologías de la Informática y las Comunicaciones, es una de las líneas que ha trazado el sistema de salud cubano en estudiantes de las ciencias médicas. La anatomía es una de las ciencias que integra la disciplina de Morfofisiología y para facilitar su comprensión resulta necesario el empleo de recursos y estrategias, entre los que puede figurar un software educativo. Objetivo: diseñar un software sobre la anatomía del sistema osteomioarticular de cabeza y cuello para los estudiantes de primer año de la carrera de Estomatología de Pinar del Río. Material y método: se realizó un estudio cualitativo. Para obtener los resultados se utilizó el método materialista dialéctico. Para la dialéctica del desarrollo del proceso estudiado se utilizaron los métodos teóricos, empíricos, el estudio profundo del tema, tipo de plataforma a utilizar y criterios de los especialistas. Para su procesamiento se utilizaron técnicas estadísticas descriptivas e inferenciales no paramétricas. Resultados: debido a la necesidad de fortalecer en los estudiantes las habilidades en la utilización de las tecnologías de la informática y las comunicaciones, se elaboró el software de la anatomía del sistema osteomioarticular de cabeza y cuello "Aprendiendo anatomía" mediante imágenes, videos y textos. Conclusiones: el software constituye un aporte al proceso enseñanza aprendizaje, el cual facilita el trabajo independiente y autopreparación mediante la interactividad con el contenido, retroalimentación y evaluación utilizando medios de enseñanza modernos, lo cual tributa al modo de actuación del futuro egresado.

Señas Mexicano

Directory of Open Access Journals (Sweden)

Juan F. García Mejía

2007-01-01

Full Text Available En este artículo se muestra un sistema que permite el estudio y práctica del Lenguaje de Señas Mexicano (LMS, el cual es el método de comunicación de las personas que padecen un trastorno de procesamiento auditivo. El sistema propuesto en este artículo consta de un guante de tela instrumentado con sensores de flexión, una etapa de acondicionamiento de señales y una tarjeta de adquisición de datos; que en su conjunto constituyen el Hardware. El software esta formado por un programa de adquisición de datos y una interfaz de usuario, ambos codificados en Visual Basic Net. El sistema propuesto se modela por medio del lenguaje de modelado unificado (UML, ya que Visual Basic es un lenguaje orientado a eventos.

Software quality assurance: in large scale and complex software-intensive systems

NARCIS (Netherlands)

Mistrik, I.; Soley, R.; Ali, N.; Grundy, J.; Tekinerdogan, B.

2015-01-01

Software Quality Assurance in Large Scale and Complex Software-intensive Systems presents novel and high-quality research related approaches that relate the quality of software architecture to system requirements, system architecture and enterprise-architecture, or software testing. Modern software

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

Science.gov (United States)

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…

Software Defined Networking Demands on Software Technologies

DEFF Research Database (Denmark)

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

2015-01-01

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

Propuesta de un proceso de enseñanza-aprendizaje para la asignatura Diseño de Software como proceso de software

Directory of Open Access Journals (Sweden)

Lund, María Inés

2014-04-01

Full Text Available La cátedra Diseño de Software se dicta actualmente en 4º año de las carreras del Departamento de Informática de la Facultad de Ciencias Exactas, Físicas y Naturales (FCEFN de la Universidad Nacional de San Juan (UNSJ. Esta materia se enfoca principalmente al Diseño Orientado a Objetos (DOO, brindando conceptos y conocimientos desarrollados en forma teórica y con un fuerte componente práctico, de todos los diagramas de modelado de software que provee el Lenguaje de Modelado Unificado (UML, con el fin de comprender acabadamente el objetivo que se persigue con cada uno de ellos y en qué casos es conveniente o útil aplicarlos. El presente trabajo se sustenta de la experiencia adquirida en la práctica aplicada para la enseñanza de DOO, utilizando UML para el modelado, donde las actividades prácticas abarcan desde el análisis hasta llegar a una propuesta de diseño de implementación. Se presenta un modelo de proceso de enseñanza aprendizaje, como proceso de software, y los artefactos utilizados para guiar al alumno en la resolución de un problema de desarrollo de software específico, utilizando para su especificación el lenguaje de metamodelado de procesos SPEM 2.0 y para generar el modelado del proceso de software la herramienta Eclipse Process Framework Composer (EPFC.

From Software Development to Software Assembly

NARCIS (Netherlands)

Sneed, Harry M.; Verhoef, Chris

2016-01-01

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

Global Software Engineering: A Software Process Approach

Science.gov (United States)

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

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

EL SOFTWARE LIBRE Y SUS IMPLICACIONES JURÍDICAS

Directory of Open Access Journals (Sweden)

Gladys Stella Rodríguez

2008-01-01

(hardware, software, conocimientos, entre otros. Sólo que esta práctica se ha desnaturalizado creando riesgos de mantenerse el conocimiento y su acceso a un grupo selecto hegemónico. En consecuencia, hoy existe la posibilidad de que a través de licencias públicas generales se consagren derechos a los autores, en un marco de mayor flexibilidad (copyleft. La metodología es descriptiva - explicativa, con una revisión bibliográfica y hemerográficas sobre el tema. Asimismo, se consultó a Fundación para la Ciencia y la Tecnología (FUNDACITE ZULIA, a través de la Misión Ciencia. Se concluye que el software libre es una oportunidad para democratizar el acceso a la información en países en desarrollo, y es un reto para el desarrollador de softwares.

Herramientas libres para modelar software Free tools to model software

Directory of Open Access Journals (Sweden)

Mauro Callejas Cuervo Óscar Yovany Baquero Moreno

2010-11-01

Full Text Available Observación acerca del  software libre y de suimplicación en procesos de desarrollo de  softwarecon herramientas 4G por parte de entidades opersonas sin capitales astronómicos y sin lamentalidad acaparadora de dominar el mercado conproductos costosos que las hagan multimillonarias yque no ofrecen una garantía real, ni la posibilidadsiquiera de conocer el  software por el que se hapagado, y mucho menos de modificarlo si no cumplenuestras expectativas.

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

Energy Technology Data Exchange (ETDEWEB)

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.

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

National Research Council Canada - National Science Library

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

CONSIDERACIONES RELACIONADAS CON LAS INSPECCIONES DE SOFTWARE

Directory of Open Access Journals (Sweden)

Bexy Alfonso Espinosa

2006-04-01

Full Text Available

Software Atom: An approach towards software components structuring to improve reusability

Directory of Open Access Journals (Sweden)

Muhammad Hussain Mughal

2017-12-01

Full Text Available Diversity of application domain compelled to design sustainable classification scheme for significantly amassing software repository. The atomic reusable software components are articulated to improve the software component reusability in volatile industry.  Numerous approaches of software classification have been proposed over past decades. Each approach has some limitations related to coupling and cohesion. In this paper, we proposed a novel approach by constituting the software based on radical functionalities to improve software reusability. We analyze the element's semantics in Periodic Table used in chemistry to design our classification approach, and present this approach using tree-based classification to curtail software repository search space complexity and further refined based on semantic search techniques. We developed a Global unique Identifier (GUID for indexing the functions and related components. We have exploited the correlation between chemistry element and software elements to simulate one to one mapping between them. Our approach is inspired from sustainability chemical periodic table. We have proposed software periodic table (SPT representing atomic software components extracted from real application software. Based on SPT classified repository tree parsing & extraction to enable the user to program their software by customizing the ingredients of software requirements. The classified repository of software ingredients assist user to exploits their requirements to software engineer and enable requirement engineer to develop a rapid large-scale prototype with great essence. Furthermore, we would predict the usability of the categorized repository based on feedback of users.  The continuous evolution of that proposed repository will be fine-tuned based on utilization and SPT would be gradually optimized by ant colony optimization techniques. Succinctly would provoke automating the software development process.

A Multidimensional Software Engineering Course

Science.gov (United States)

Barzilay, O.; Hazzan, O.; Yehudai, A.

2009-01-01

Software engineering (SE) is a multidimensional field that involves activities in various areas and disciplines, such as computer science, project management, and system engineering. Though modern SE curricula include designated courses that address these various subjects, an advanced summary course that synthesizes them is still missing. Such a…

Data Analysis Details (DS): SE53_DS03 [Metabolonote[Archive

Lifescience Database Archive (English)

Full Text Available SE53_DS03 In-house software An original data file (.wiff) was converted to an uniqu...e binary file (.kiff) using in-house software (nondisclosure). Peak picking and alignment were performed usi...s including internal standards, peaks were annotated automatically using the same software. For normalizatio...ng the another in-house software (nondisclosure), peaks were picked and aligned among samples automatically.

A CLASSROOM GAME FOR TEACHING MANAGEMENT OF SOFTWARE COMPANIES

Directory of Open Access Journals (Sweden)

CARLOS M. ZAPATA

2010-01-01

Full Text Available La gestión en ingeniería de software necesita algunas destrezas especiales. A menudo, esas destrezas no se pueden desarrollar a partir de los métodos tradicionales de enseñanza. Otras disciplinas administrativas usan aprendizaje activo (v. g. aprendizaje mediante juegos para desarrollar esas destrezas, pero los profesores en ingeniería de software no suelen conducir experiencias similares. En este artículo se propone un juego de clase para simular el comportamiento de varios roles pertenecientes a una compañía de software. Nuestra meta es la "práctica", en un ambiente similar al entorno real, de las destrezas que requieren los miembros de los equipos de desarrollo de software. Además, se compendian los resultados de la práctica del juego con dos grupos de estudiantes.

A concept of software testing for SMART MMIS software

International Nuclear Information System (INIS)

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

Diseño de software interactivo en las matemáticas

Directory of Open Access Journals (Sweden)

María Nivela Cornejo

2018-02-01

Full Text Available El propósito de esta investigación fue crear un Software Educativo que permita la integración del uso de las matemáticas al Aprendizaje Significativo. La investigación está marcada en documental y campo. El método utilizado fue el estudio de casos. El procedimiento que se llevó a cabo en esta investigación se dividió en tres fases: (a Análisis, se investigaron y analizaron las teorías, estrategias y etapas que existen para el desarrollo de software educativo. (b Diseño del Software Educativo, se planteó la incorporación del computador como instrumento para el aprendizaje de la informática a través del software educativo. (c Implantación y evaluación. Las técnicas e instrumentos utilizados para recolección de datos fueron la entrevista semiestructuradas, la observación participativa y las evidencias documentales. Los resultados que se obtuvieron permitieron verificar la factibilidad que tuvo el software educativo en el Aprendizaje Significativo de las matemáticas.

What information do software engineering practitioners need?

OpenAIRE

Punter, T.

2003-01-01

This position paper addresses an important question for the discipline of Empirical or Evidence-based Software Engineering (SE), namely ´what information do software engineering practitioners need from the empirical studies´. The paper contributes to answering this question by presenting survey results on two sub-questions: 1) what are the topics that interest practitioners? and 2) what type of information is needed by practitioners? Answering the first question results in a set of SE topics,...

Software Radar Technology

Directory of Open Access Journals (Sweden)

Tang Jun

2015-08-01

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

Validation of software for calculating the likelihood ratio for parentage and kinship.

Science.gov (United States)

Drábek, J

2009-03-01

Although the likelihood ratio is a well-known statistical technique, commercial off-the-shelf (COTS) software products for its calculation are not sufficiently validated to suit general requirements for the competence of testing and calibration laboratories (EN/ISO/IEC 17025:2005 norm) per se. The software in question can be considered critical as it directly weighs the forensic evidence allowing judges to decide on guilt or innocence or to identify person or kin (i.e.: in mass fatalities). For these reasons, accredited laboratories shall validate likelihood ratio software in accordance with the above norm. To validate software for calculating the likelihood ratio in parentage/kinship scenarios I assessed available vendors, chose two programs (Paternity Index and familias) for testing, and finally validated them using tests derived from elaboration of the available guidelines for the field of forensics, biomedicine, and software engineering. MS Excel calculation using known likelihood ratio formulas or peer-reviewed results of difficult paternity cases were used as a reference. Using seven testing cases, it was found that both programs satisfied the requirements for basic paternity cases. However, only a combination of two software programs fulfills the criteria needed for our purpose in the whole spectrum of functions under validation with the exceptions of providing algebraic formulas in cases of mutation and/or silent allele.

Software testability and its application to avionic software

Science.gov (United States)

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

1993-01-01

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

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

Science.gov (United States)

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.

The Software Invention Cube: A classification scheme for software inventions

NARCIS (Netherlands)

Bergstra, J.A.; Klint, P.

2008-01-01

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

SPEM: Software Process Engineering Metamodel

Directory of Open Access Journals (Sweden)

Víctor Hugo Menéndez Domínguez

2015-05-01

Full Text Available Todas las organizaciones involucradas en el desarrollo de software necesitan establecer, gestionar y soportar el trabajo de desarrollo. El término “proceso de desarrollo de software” tiende a unificar todas las actividades y prácticas que cubren esas necesidades. Modelar el proceso de software es una forma para mejorar el desarrollo y la calidad de las aplicaciones resultantes. De entre todos los lenguajes existentes para el modelado de procesos, aquellos basados en productos de trabajo son los más adecuados. Uno de tales lenguajes es SPEM (Software Process Engineering Metamodel. SPEM fue creado por OMG (Object Management Group como un estándar de alto nivel, que está basado en MOF (MetaObject Facility y es un metamodelo UML (Uniform Model Language. Constituye un tipo de ontología de procesos de desarrollo de software. En este artículo se ofrece una descripción, en términos generales, del estándar SPEM. También se destacan los cambios que ha experimentado entre la versión 1.1 y la versión 2.0, presentando tanto las ventajas como las desventajas encontradas entre ambas versiones.

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

Science.gov (United States)

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.

Agile Software Development

Science.gov (United States)

Biju, Soly Mathew

2008-01-01

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

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

Science.gov (United States)

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.

Software Assurance Competency Model

Science.gov (United States)

2013-03-01

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

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

Science.gov (United States)

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

2014-12-01

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

Método para generar casos de prueba funcional en el desarrollo de software Generating functional testing case method in software development

Directory of Open Access Journals (Sweden)

Liliana González Palacio

2009-07-01

Full Text Available Un aspecto crucial en el control de calidad del desarrollo de software son las pruebas y, dentro de estas, las pruebas funcionales, en las cuales se hace una verificación dinámica del comportamiento de un sistema, basada en la observación de un conjunto seleccionado de ejecuciones controladas o casos de prueba. Para hacer pruebas funcionales se requiere una planificación que consiste en definir los aspectos a chequear y la forma de verificar su correcto funcionamiento, punto en el cual adquieren sentido los casos de prueba. En este artículo derivado de investigación se define un método para generar casos de prueba funcional a partir de casos de uso del sistema, como producto intermedio del proyecto cofinanciado titulado "Herramienta para la documentación de pruebas funcionales"Testing is a main aspect in quality control of software development, especially functional tests. The aim of functional testing is to dynamically verify the system behavior, based on the observation of a given set of controlled executions or test cases. Planning is required to make functional tests, defining the aspects to be checked and the way to verify its proper operation; this allows test cases make sense. In this paper (research based, we propose a method to generate functional test cases from system use cases, based on the co-financed project "Tool for Documenting Functional Testing."

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

Science.gov (United States)

Hayhurst, Kelly J.

1998-01-01

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

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

Science.gov (United States)

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.

Software Architecture Evolution

Science.gov (United States)

Barnes, Jeffrey M.

2013-01-01

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

NASA's Software Safety Standard

Science.gov (United States)

Ramsay, Christopher M.

2007-01-01

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

A study of software safety analysis system for safety-critical software

International Nuclear Information System (INIS)

Chang, H. S.; Shin, H. K.; Chang, Y. W.; Jung, J. C.; Kim, J. H.; Han, H. H.; Son, H. S.

2004-01-01

The core factors and requirements for the safety-critical software traced and the methodology adopted in each stage of software life cycle are presented. In concept phase, Failure Modes and Effects Analysis (FMEA) for the system has been performed. The feasibility evaluation of selected safety parameter was performed and Preliminary Hazards Analysis list was prepared using HAZOP(Hazard and Operability) technique. And the check list for management control has been produced via walk-through technique. Based on the evaluation of the check list, activities to be performed in requirement phase have been determined. In the design phase, hazard analysis has been performed to check the safety capability of the system with regard to safety software algorithm using Fault Tree Analysis (FTA). In the test phase, the test items based on FMEA have been checked for fitness guided by an accident scenario. The pressurizer low pressure trip algorithm has been selected to apply FTA method to software safety analysis as a sample. By applying CASE tool, the requirements traceability of safety critical system has been enhanced during all of software life cycle phases

Band structure calculation of GaSe-based nanostructures using empirical pseudopotential method

International Nuclear Information System (INIS)

Osadchy, A V; Obraztsova, E D; Volotovskiy, S G; Golovashkin, D L; Savin, V V

2016-01-01

In this paper we present the results of band structure computer simulation of GaSe- based nanostructures using the empirical pseudopotential method. Calculations were performed using a specially developed software that allows performing simulations using cluster computing. Application of this method significantly reduces the demands on computing resources compared to traditional approaches based on ab-initio techniques and provides receiving the adequate comparable results. The use of cluster computing allows to obtain information for structures that require an explicit account of a significant number of atoms, such as quantum dots and quantum pillars. (paper)

Interplay between usability evaluation and software development (I-USED 2009)

DEFF Research Database (Denmark)

Abrahão, S.; Hornbæk, Kasper Anders Søren; Law, E.

2009-01-01

This workshop is aimed at bringing together researchers and practitioners from the Human-Computer Interaction (HCI) and Software Engineering (SE) fields to determine the state-of-the-art in the interplay between usability evaluation and software development and to generate ideas for new...... and improved relations between these activities. The aim is to base the determination of the current state on empirical studies. Presentations of new ideas on how to improve the interplay between HCI & SE to the design of usable software systems should also be based on empirical studies....

Workshop on Software Development Tools for Petascale Computing

Energy Technology Data Exchange (ETDEWEB)

Vetter, Jeffrey [Oak Ridge National Lab. (ORNL), Oak Ridge, TN (United States); Georgia Inst. of Technology, Atlanta, GA (United States)

2007-08-01

Petascale computing systems will soon be available to the DOE science community. Recent studies in the productivity of HPC platforms point to better software environments as a key enabler to science on these systems. To prepare for the deployment and productive use of these petascale platforms, the DOE science and general HPC community must have the software development tools, such as performance analyzers and debuggers that meet application requirements for scalability, functionality, reliability, and ease of use. In this report, we identify and prioritize the research opportunities in the area of software development tools for high performance computing. To facilitate this effort, DOE hosted a group of 55 leading international experts in this area at the Software Development Tools for PetaScale Computing (SDTPC) Workshop, which was held in Washington, D.C. on August 1 and 2, 2007. Software development tools serve as an important interface between the application teams and the target HPC architectures. Broadly speaking, these roles can be decomposed into three categories: performance tools, correctness tools, and development environments. Accordingly, this SDTPC report has four technical thrusts: performance tools, correctness tools, development environment infrastructures, and scalable tool infrastructures. The last thrust primarily targets tool developers per se, rather than end users. Finally, this report identifies non-technical strategic challenges that impact most tool development. The organizing committee emphasizes that many critical areas are outside the scope of this charter; these important areas include system software, compilers, and I/O.

Desarrollo de software educativo: una propuesta metodológica

Directory of Open Access Journals (Sweden)

Hugo Quintero

2005-09-01

Full Text Available En este trabajo se propone una metodología para el diseño de software en educación, la cual reúne tanto los elementos educativos como los de análisis t diseño de sistemas, integrando las etapas de realización de software con las teorías de aprendizaje. Esta se ha puesto en práctica en los software denominados “Aprendiendo Física con Experimentos” y “Conociendo algunos físicos”, los cuales están en proceso de validación de usuarios finales, quienes solicitan el material para ponerlo en práctica en su aula, a un 81,2% le pareció fácil la utilización del mismo, el 84% se sintió cómodo con la utilización del mismo.

48 CFR 227.7203-2 - Acquisition of noncommercial computer software and computer software documentation.

Science.gov (United States)

2010-10-01

... at one site or multiple site licenses, and the format and media in which the software or... noncommercial computer software and computer software documentation. 227.7203-2 Section 227.7203-2 Federal... CONTRACTING REQUIREMENTS PATENTS, DATA, AND COPYRIGHTS Rights in Computer Software and Computer Software...

LA MODELACIÓN MATEMÁTICA EN SITUACIONES COTIDIANAS CON LOS SOFTWARE AVIMECA Y MATHCAD.

Directory of Open Access Journals (Sweden)

Rafael Pantoja Rangel

2013-08-01

Full Text Available Los procesos de modelación a través del planteamiento de relaciones funcionales, son considerados tanto por estudiantes y profesores, como tareas difíciles, ya que las actividades requieren de una destreza eficiente y creativa para articular y manejar diferentes representaciones de una situación de la vida cotidiana y relacionarlas con la modelación matemática. Además del bagaje de conocimiento matemático que los alumnos requieren a la hora de establecer un plan de solución, la resolución de problemas y trabajo colaborativo, son fundamentales para promover el aprendizaje. En este reporte se presentan como situaciones de la vida cotidiana, el llenado de recipientes, el atletismo y el ciclismo, y se trata de que el estudiante identifique las relaciones entre las variables que intervienen, así cómo determinar la función que modela su comportamiento. La actividad se filma en video, y con el software AVIMECA se obtienen datos en tiempo real del video, mismos que se tratan con Excel y se seleccionan para obtener su representación gráfica: tiempo-distancia. A partir de estos datos, con el programa MathCad se desarrolla el algoritmo de mínimos cuadrados y obtiene la expresión de la función que modela el fenómeno.ABSTRACTModeling processes through the approach of functional relationships are considered by both, students and teachers, as a difficult task since the activities require efficient and creative skills to connect and manage different representations of a situation of daily life, and relate with mathematical modeling. In addition to the background of mathematical knowledge that students require when establishing a solution plan, problem solving and collaborative work are essential to promote learning. This report presents as everyday life situations activities relating to filling containers, athletics and cycling. The goal is that the student identifies the relationships between the variables involved in the phenomenon and

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

CERN Document Server

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

Software as a service approach to sensor simulation software deployment

Science.gov (United States)

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.

Construção de um software educativo sobre transtornos da personalidade

Directory of Open Access Journals (Sweden)

Nadja Cristiane Lappann Botti

2011-12-01

Full Text Available O estudo objetivou relatar a experiência da construção de um software educativo na área da saúde mental. O software foi desenvolvido visando capacitar o estudante de enfermagem a identificar os principais transtornos da personalidade. Nesse processo, aplicou-se o referencial pedagógico de Vygotsky e o referencial teórico dos critérios diagnósticos definidos pelo DSM-IV. A partir destes referenciais identificaram-se transtornos da personalidade em personagens de histórias e/ou filmes infantis. Para desenvolvimento do software construiu-se banco de multimídias com dados gráficos, sonoros e explicativos. O software desenvolvido foi um jogo educativo do tipo quiz composto por perguntas com níveis crescentes de dificuldade. O software foi desenvolvido no programa Microsoft PowerPoint Office 2007. Este programa com seus mecanismos de botões de ação e hiperlink possibilitam configurar ações. Acredita-se na validade desta estratégia para o ensino-aprendizagem de conteúdos relativos à área da Enfermagem em Saúde Mental.

Software life after in-service

International Nuclear Information System (INIS)

Tseng, M.; Eng, P.

1993-01-01

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

Modelo formal de pruebas funcionales de software para alcanzar el Nivel de Madurez Integrado 2

Directory of Open Access Journals (Sweden)

Milton Eduardo Escobar-Sánchez

2015-05-01

Full Text Available Las aplicaciones de software son cada vez más importantes para las organizaciones debido a que permiten llevar a cabo efiientemente sus tareas primordiales; por ello es mandatorio realizar las pruebas de calidad de software. Esta investigación se enfocó en diseñar un modelo formal para desarrollar pruebas funcionales de software que permitan alcanzar el nivel de calidad 2 del Modelo de Madurez de Pruebas Integrado (TMMI. El proceso se inició con un diagnóstico situacional, aplicando la norma ISO-9001-2000; luego, se evaluaron diversos modelos de prueba de calidad de software, como el ISO/IEC 9126, el TMM, el TMMI, el Proceso de Mejoramiento de Pruebas (TPI y el Enfoque de Gestión de Pruebas (TMAP, realizando una comparación bajo algunos criterios como año de publicación, licenciamiento, niveles, factorías y riesgos. Con esta información se diseñó el modelo propuesto, que es independiente del proceso de desarrollo de software. Concretamente, se fundamentó en el ciclo de prueba, y se compone de cuatro fases: Especifiación, Planifiación, Ejecución y Evaluación, en el que se contrasta en forma real el comportamiento esperado del software. Como caso de estudio y validación se aplicó este modelo a una PYME; los resultados mostraron la efiiencia del modelo y revelaron que es preciso desarrollar una cultura de calidad organizacional en esta empresa.

Calidad en el desarrollo de Sistemas de Software

OpenAIRE

Pesado, Patricia Mabel; Bertone, Rodolfo Alfredo; Esponda, Silvia; Pasini, Ariel C.; Martorelli, Sabrina Lorena

2010-01-01

El objetivo del subproyecto “Calidad en el desarrollo de Sistemas de Software" es analizar, investigar y desarrollar propuestas en temas relacionados con el aseguramiento de la calidad en cada una de las etapas del desarrollo de Sistemas de Software. En particular se ha trabajado y estudiado las normas de calidad más ampliamente difundidas, líneas ISO y CMMI, y su incidencia en entornos como la pequeña y mediana industria de nuestro país. Desde el año 2006, se ha trabajado en la adecuación...

Hackers: de piratas a defensores del software libre

OpenAIRE

Jorge Lizama Mendoza

2002-01-01

El presente artículo consta de dos partes: en la primera se ofrecen argumentos que permiten definir a los hackers como un grupo de expertos en informática que, mediante la práctica de unos principios éticos tales como el acceso a las computadoras debe ser libre, Crea software y compártelo con la comunidad internet; han inaugurado una nueva dinámica de trabajo entre los usuarios de la red para desarrollar software libre. En la segunda parte se analiza la historia de Linux, un si...

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

Energy Technology Data Exchange (ETDEWEB)

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.

LDUA software custodian's notebook

International Nuclear Information System (INIS)

Aftanas, B.L.

1998-01-01

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

Success Factors for Using Case Method in Teaching and Learning Software Engineering

Science.gov (United States)

Razali, Rozilawati; Zainal, Dzulaiha Aryanee Putri

2013-01-01

The Case Method (CM) has long been used effectively in Social Science education. Its potential use in Applied Science such as Software Engineering (SE) however has yet to be further explored. SE is an engineering discipline that concerns the principles, methods and tools used throughout the software development lifecycle. In CM, subjects are…

Computing and software

Directory of Open Access Journals (Sweden)

White, G. C.

2004-06-01

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

Software testing for evolutionary iterative rapid prototyping

OpenAIRE

Davis, Edward V., Jr.

1990-01-01

Approved for public release; distribution unlimited. Rapid prototyping is emerging as a promising software development paradigm. It provides a systematic and automatable means of developing a software system under circumstances where initial requirements are not well known or where requirements change frequently during development. To provide high software quality assurance requires sufficient software testing. The unique nature of evolutionary iterative prototyping is not well-suited for ...

Modelo de calidad para el software orientado a objetos

OpenAIRE

Fuertes Castro, José Luis

2002-01-01

El software ha obtenido en la actualidad una gran importancia en todos los ámbitos de la vida cotidiana. Es indudable que la calidad del software juega un papel fundamental en todo desarrollo informático, aunque en ocasiones no se le presta la suficiente atención, quizás debido a los relativamente escasos trabajos relacionados con este tema desarrollados hasta la fecha. En el presente trabajo, se plantea la necesidad de un modelo de calidad completo. Para cubrir esta necesid...

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

Directory of Open Access Journals (Sweden)

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

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

International Nuclear Information System (INIS)

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

Towards a Theory of Affect and Software Developers' Performance

OpenAIRE

Graziotin, Daniel

2016-01-01

For more than thirty years, it has been claimed that a way to improve software developers' productivity and software quality is to focus on people. The underlying assumption seems to be that "happy and satisfied software developers perform better". More specifically, affects-emotions and moods-have an impact on cognitive activities and the working performance of individuals. Development tasks are undertaken heavily through cognitive processes, yet software engineering research (SE) lacks theo...

La programación de software como competencia profesional del ingeniero en sistemas informáticos / Software programming as a professional competence of computing system engineers

Directory of Open Access Journals (Sweden)

San Andrés, Esthela María

2016-01-01

Full Text Available En el nuevo milenio con el impetuoso avance de las TIC las organizaciones y empresas demandan el desarrollo de sistemas computacionales para la automatización de diferentes procesos que permitan mejorar e incrementar su productividad y eficiencia, por lo que exigen de las instituciones de educación superior la preparación de profesionales que puedan aportar sus esfuerzos en la construcción de soluciones de negocio utilizando la tecnología computacional de vanguardia en la programación de software. El presente artículo describe los resultados parciales de una investigación que se realiza con el objetivo de formar y desarrollar la competencia profesional programar software en los Ingenieros en Sistemas Informáticos. Se realizó un diagnóstico en la carrera de Ingeniería en Sistemas Informáticos de la UTM donde se aplicaron encuestas, entrevistas y observaciones a clases, tomando una muestra de 179 estudiantes y siete profesores, los resultados identificaron insuficiencias de los estudiantes en la formación teórico-práctica en programación, lo que limita su futuro desempeño profesional. En el desarrollo de la investigación, también se utilizó el análisis y la síntesis para resumir los fundamentos teóricos esenciales que sirven de sustento a los resultados que se presentan, a través de la asignatura Programación I se muestra la relación entre la competencia y la asignatura y los resultados de aprendizaje que se deben alcanzar con las respectivas evidencias para su evaluación. Palabras clave: competencias, competencias profesionales, aprendizaje, ABSTRACT: In the new millennium with the impetuous progress of ICTs the organizations and companies demand the development of computer systems for automatizing processes which allow improving and increasing their productivity and efficiency, so they require from the higher education institutions the training of professionals capable of contributing to develop business solutions

Views on Software Testability

OpenAIRE

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

1994-01-01

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

Integrando mediante patrones de software una estrategia Fuzzy-Logic, en un servicio de balanceo dinámico de carga bajo CORBA

OpenAIRE

Gricelda Medina Veloz; Francisco Javier Luna Rosas; Jaime Muñoz Arteaga; Julio César Martínez Romo

2008-01-01

El enfoque del uso de patrones en el desarrollo de software se ha popularizado a nivel mundial y dentro de la ingeniería de software se ha extendido cada vez más su uso, a tal grado que se han creado y se siguen creando catálogos de patrones para solucionar problemas en el desarrollo de software a distintos niveles de abstracción. Este trabajo se centra en destacar el diseño mediante patrones de software de un servicio de balanceo de carga para aplicaciones distribuidas desarrolladas bajo el ...

Software Quality Assurance Metrics

Science.gov (United States)

McRae, Kalindra A.

2004-01-01

Software Quality Assurance (SQA) is a planned and systematic set of activities that ensures conformance of software life cycle processes and products conform to requirements, standards and procedures. In software development, software quality means meeting requirements and a degree of excellence and refinement of a project or product. Software Quality is a set of attributes of a software product by which its quality is described and evaluated. The set of attributes includes functionality, reliability, usability, efficiency, maintainability, and portability. Software Metrics help us understand the technical process that is used to develop a product. The process is measured to improve it and the product is measured to increase quality throughout the life cycle of software. Software Metrics are measurements of the quality of software. Software is measured to indicate the quality of the product, to assess the productivity of the people who produce the product, to assess the benefits derived from new software engineering methods and tools, to form a baseline for estimation, and to help justify requests for new tools or additional training. Any part of the software development can be measured. If Software Metrics are implemented in software development, it can save time, money, and allow the organization to identify the caused of defects which have the greatest effect on software development. The summer of 2004, I worked with Cynthia Calhoun and Frank Robinson in the Software Assurance/Risk Management department. My task was to research and collect, compile, and analyze SQA Metrics that have been used in other projects that are not currently being used by the SA team and report them to the Software Assurance team to see if any metrics can be implemented in their software assurance life cycle process.

Verification of safety critical software

International Nuclear Information System (INIS)

Son, Ki Chang; Chun, Chong Son; Lee, Byeong Joo; Lee, Soon Sung; Lee, Byung Chai

1996-01-01

To assure quality of safety critical software, software should be developed in accordance with software development procedures and rigorous software verification and validation should be performed. Software verification is the formal act of reviewing, testing of checking, and documenting whether software components comply with the specified requirements for a particular stage of the development phase[1]. New software verification methodology was developed and was applied to the Shutdown System No. 1 and 2 (SDS1,2) for Wolsung 2,3 and 4 nuclear power plants by Korea Atomic Energy Research Institute(KAERI) and Atomic Energy of Canada Limited(AECL) in order to satisfy new regulation requirements of Atomic Energy Control Boars(AECB). Software verification methodology applied to SDS1 for Wolsung 2,3 and 4 project will be described in this paper. Some errors were found by this methodology during the software development for SDS1 and were corrected by software designer. Outputs from Wolsung 2,3 and 4 project have demonstrated that the use of this methodology results in a high quality, cost-effective product. 15 refs., 6 figs. (author)

Metodología LEAN para el desarrollo de software. Ejemplo práctico de aplicación en empresa de desarrollo de software

OpenAIRE

Sanz Mateo, María Isabel

2015-01-01

Este proyecto pretende mostrar la aplicación de la metodología Lean. Al ser ésta una metodología no específica del desarrollo de software, se hace una exposición de los principales conceptos, principios y técnicas relacionados con la filosofía Lean y para los que se ha encontrado referencia en el ámbito de la Ingeniería del Software. Grado en Ingeniería Técnica en Informática de Gestión

ENGLISH COMMUNICATIVE COMPETENCE WITH THE USE OF THE EDUCATIVE SOFTWARE / COMPETENCIA COMUNICATIVA EN INGLÉS CON EL USO DEL SOFTWARE EDUCATIVO

Directory of Open Access Journals (Sweden)

Oldy Medina Betancourt

2013-12-01

Full Text Available The authors supported the formation and development of the communicative competence in English with the use of the educative software for Senior High School students which constitutes a tool for all teachers and students because of the advantages that the modern technology offers to the lessons. Communicative competence has a paramount importance for human communication, which is its goal. The content of the article provides the theoretic, basically didactical sustains to the use of the software in the English lessons as a scientific newness. This technology, well used, could help the teaching learning process of this subject. In this article, some key categories are redefined and the treatment to the diagnosis and stimulation of some cognitive elements is also presented. These are of substantive importance for using new technology in the solution of the scientific problem dealt with. RESUMEN Se abordó la formación y desarrollo de la competencia comunicativa en inglés con el uso del software educativo para los estudiantes de preuniversitario, que se constituye en herramienta al alcance de los profesores y estudiantes por las ventajas que ofrece el uso de medios modernos en el aula. La competencia comunicativa, reviste importancia capital para la comunicación humana, que es definitivamente su fin. Su contenido recoge los sustentos teóricos, básicamente didácticos, para el uso del software en las clases de inglés como elemento de novedad científica. Esta tecnología, bien utilizada, sirve de soporte al proceso de enseñanza-aprendizaje de esta lengua. En el artículo se redefinen categorías clave para el proceso que se modela, así como se le da tratamiento al diagnóstico y estimulación de elementos de naturaleza cognitiva, que son de importancia sustantiva para la utilización del novedoso medio en función de dar solución al problema científico que se abordó.

Arquitectura software para robots móviles aplicando la metodología mdasr

OpenAIRE

Londoño Ospina, Nelson de J.

2011-01-01

Se aplica la Metodología de Desarrollo de Arquitecturas Software para Robots –MDASR, como herramienta de especificación, análisis y diseño de una Arquitectura de Control Reactiva. La metodología se apoya en métodos y lenguajes ampliamente adoptados como el P U (Proceso Unificado de Desarrollo de Software) y UML (Lenguaje Unificado de Modelado), apropiando conceptos y métodos empleados en Ingeniería Software

Aplicación del modelo mgrsoft en la reutilización de revisiones a requsitos de software

Directory of Open Access Journals (Sweden)

Martha Dunia Delgado Dapena

2010-04-01

Full Text Available En este trabajo se presentan las experiencias de la implementación de un Modelo para la Gestión de Revisiones (MGRSoft, haciendo énfasis en la utilización de mecanismos de reuti-lización para las revisiones de los requisitos a nuevos proyectos de software. Se exponen las características de una herramienta que reutiliza revisiones anteriores y su utilización dentro del modelo MGRSoft. Se presentan, además, los resultados obtenidos en una prueba rea-lizada a proyectos reales, que evidencia el aprovechamiento de la experiencia acumulada utilizando los mecanismos de reutilización incluidos en el modelo. This paper presents the implementation experiences of the Manage Revisions Model (MGR-Soft, making emphasis in the use of reutilization mechanisms for revisions to requirements in new software projects. It includes the characteristics of a tool that reuse previous revisions and its use inside the MGRSoft model. The results of the results of a test on real projects, which demonstrates the use of experience using the reuse mechanisms included in the mo-del.

Belle II Software

International Nuclear Information System (INIS)

Kuhr, T; Ritter, M

2016-01-01

Belle II is a next generation B factory experiment that will collect 50 times more data than its predecessor, Belle. The higher luminosity at the SuperKEKB accelerator leads to higher background levels and requires a major upgrade of the detector. As a consequence, the simulation, reconstruction, and analysis software must also be upgraded substantially. Most of the software has been redesigned from scratch, taking into account the experience from Belle and other experiments and utilizing new technologies. The large amount of experimental and simulated data requires a high level of reliability and reproducibility, even in parallel environments. Several technologies, tools, and organizational measures are employed to evaluate and monitor the performance of the software during development. (paper)

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

Science.gov (United States)

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…

Test process for the safety-critical embedded software

International Nuclear Information System (INIS)

Sung, Ahyoung; Choi, Byoungju; Lee, Jangsoo

2004-01-01

Digitalization of nuclear Instrumentation and Control (I and C) system requires high reliability of not only hardware but also software. Verification and Validation (V and V) process is recommended for software reliability. But a more quantitative method is necessary such as software testing. Most of software in the nuclear I and C system is safety-critical embedded software. Safety-critical embedded software is specified, verified and developed according to V and V process. Hence two types of software testing techniques are necessary for the developed code. First, code-based software testing is required to examine the developed code. Second, after code-based software testing, software testing affected by hardware is required to reveal the interaction fault that may cause unexpected results. We call the testing of hardware's influence on software, an interaction testing. In case of safety-critical embedded software, it is also important to consider the interaction between hardware and software. Even if no faults are detected when testing either hardware or software alone, combining these components may lead to unexpected results due to the interaction. In this paper, we propose a software test process that embraces test levels, test techniques, required test tasks and documents for safety-critical embedded software. We apply the proposed test process to safety-critical embedded software as a case study, and show the effectiveness of it. (author)

Paladin Software Support Lab

Data.gov (United States)

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

48 CFR 12.212 - Computer software.

Science.gov (United States)

2010-10-01

... 48 Federal Acquisition Regulations System 1 2010-10-01 2010-10-01 false Computer software. 12.212... software. (a) Commercial computer software or commercial computer software documentation shall be acquired... required to— (1) Furnish technical information related to commercial computer software or commercial...

Manufactura Esbelta: una contribución para el desarrollo de software con calidad

Directory of Open Access Journals (Sweden)

José Cadenas

2010-09-01

Full Text Available Esta investigación es una contribución a la mejora de la calidad del software que tiene como premisa que losdesarrollos de software efectuados a la fecha no satisfacen las expectativas de tiempo de desarrollo, fiabilidad, mantenibilidad,portabilidad y calidad. Se trata de una investigación de campo, apoyada en una revisión documental de tipono experimental, descriptiva y transeccional con el fin de evaluar la versión 4 del SQLfi. Para ello, se empleó el modelosistémico de calidad del software (MOSCA con una población de 26 personas miembros del equipo de investigación,de los cuales se tomó una muestra intencional de 11, los cuales evaluaron el producto SQLfi versión 4. Se obtuvo unnivel sistémico de calidad nulo, y como conclusión se propone la adopción de un modelo de desarrollo para la construcciónde software de calidad basado en estándares establecidos de manufactura esbelta (Lean Manufacturing,complementado con los aportes derivados de la evaluación a través de MOSCA y la experiencia de los investigadores.La contribución corresponde a una mejora de la calidad sistémica de desarrollo software que permite obtener productosen forma ágil, a un costo razonable y con los recursos presupuestados. Se recomienda evaluar si hay aumento en elnivel de madurez en los procesos de desarrollo de un grupo en un entorno científico y académico.

Towards an Ontology of Software

OpenAIRE

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

SOFTWARE LIBRE: OPORTUNIDADES Y RETOS CON ESPECIAL REFERENCIA A VENEZUELA

Directory of Open Access Journals (Sweden)

Gladys Rodríguez

2008-11-01

Full Text Available En este trabajo se abordan algunas consideraciones en torno al software libre, sus oportunidades pero también sus desafíos, a la vez que se expone el marco legal de esta figura a partir de su implementación en Venezuela. Se ha empleado una metodología descriptivo-explicativa, partiendo de la revisión bibliográfica conjuntamente con la legislación nacional sobre el tema. Asimismo, se consultó a FUNDACITE ZULIA, a través de la Misión Ciencia, y se concluye que el software libre es una oportunidad para desarrollar programas que atiendan necesidades particulares, y hay quienes consideran que resulta una herramienta especialmente útil para democratizar el acceso a la información en países en desarrollo; sin embargo, planteamos la realidad de una brecha digital entre países en desarrollo y desarrollados

Uso de software libre en las empresas colombianas

Directory of Open Access Journals (Sweden)

Carlos Nelson Henrìquez Miranda

2009-01-01

Full Text Available ResumenActualmente las empresas usan la tecnología de punta para apoyar sus procesos comerciales, sin embargo en elámbito local podemos darnos cuenta que existen muchas empresas que no tienen conocimiento de la existenciade herramientas informáticas (software que les ayuden en sus labores empresariales. Algunos empresarios pordesconocimiento adquieren aplicaciones de software (propietario que son muy costosas y las cuales usan en unporcentaje muy bajo de sus verdaderas funcionalidades. Entonces hacen una gran inversión que no es redimibleen el futuro porque necesitan demasiadas asesorías y consultorías de estas empresas que comercializan la herramienta.Además si las empresas van creciendo e incluyen nuevas estaciones de trabajo, se necesita comprarmás software, porque este tipo de producto se vende normalmente bajo el término de licencia propietaria. Entoncesencontramos dos situaciones, aquellas empresas que no invierten en software porque es muy costoso, y aquellasque lo hacen pero a la inversión hecha, que a veces es muy alta, no le sacan provecho real por desconocimiento, odebido a una mala asesoría. Ante esta situación hay que buscar nuevas alternativas para lograr que las empresaspequeñas y medianas logren tener en sus manos todas las bondades que trae el uso de la computación (rapidez,eficiencia, organización entre otras. Una opción para este problema es la adopción de programas que no tienencosto o su costo es relativamente bajo, estos programas están enmarcados en el movimiento conocido como “SoftwareLibre”. Este nace como alternativa para uso de productos de una buena calidad a un bajo costo que permitala sistematización parcial o total de las empresas, además de usar programas ofimáticos para el manejo de lainformación de las oficinas.El uso de Software Libre en las empresas colombianas permitirá aumentar sus nivelesde competitividad, bajando un poco la inversión en software y mantenimiento, logrando una

Design and validation of Segment - freely available software for cardiovascular image analysis

International Nuclear Information System (INIS)

Heiberg, Einar; Sjögren, Jane; Ugander, Martin; Carlsson, Marcus; Engblom, Henrik; Arheden, Håkan

2010-01-01

Commercially available software for cardiovascular image analysis often has limited functionality and frequently lacks the careful validation that is required for clinical studies. We have already implemented a cardiovascular image analysis software package and released it as freeware for the research community. However, it was distributed as a stand-alone application and other researchers could not extend it by writing their own custom image analysis algorithms. We believe that the work required to make a clinically applicable prototype can be reduced by making the software extensible, so that researchers can develop their own modules or improvements. Such an initiative might then serve as a bridge between image analysis research and cardiovascular research. The aim of this article is therefore to present the design and validation of a cardiovascular image analysis software package (Segment) and to announce its release in a source code format. Segment can be used for image analysis in magnetic resonance imaging (MRI), computed tomography (CT), single photon emission computed tomography (SPECT) and positron emission tomography (PET). Some of its main features include loading of DICOM images from all major scanner vendors, simultaneous display of multiple image stacks and plane intersections, automated segmentation of the left ventricle, quantification of MRI flow, tools for manual and general object segmentation, quantitative regional wall motion analysis, myocardial viability analysis and image fusion tools. Here we present an overview of the validation results and validation procedures for the functionality of the software. We describe a technique to ensure continued accuracy and validity of the software by implementing and using a test script that tests the functionality of the software and validates the output. The software has been made freely available for research purposes in a source code format on the project home page (http://segment.heiberg.se). Segment

Implementing Software Safety in the NASA Environment

Science.gov (United States)

Wetherholt, Martha S.; Radley, Charles F.

1994-01-01

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

Software Product Manager: A Mechanism to manage software products in small and medium ISVs

NARCIS (Netherlands)

Katchow, R.; van de Weerd, I.; Brinkkemper, S.; Rooswinkel, A.

2009-01-01

In this paper, we present SP Manager as an innovative tool for managing software products in small and medium independent software vendors (ISVs). This tool incorporates the operational software product management (SPM) processes focused on requirements management and release planning. By using

Expected requirements in support tool for software process improvement in SMEs

OpenAIRE

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

Hackers: de piratas a defensores del software libre

Directory of Open Access Journals (Sweden)

Jorge Lizama Mendoza

2002-01-01

Full Text Available El presente artículo consta de dos partes: en la primera se ofrecen argumentos que permiten definir a los hackers como un grupo de expertos en informática que, mediante la práctica de unos principios éticos tales como “el acceso a las computadoras debe ser libre”, “Crea software y compártelo con la comunidad internet”; han inaugurado una nueva dinámica de trabajo entre los usuarios de la red para desarrollar software libre. En la segunda parte se analiza la historia de Linux, un sistema operativo gratuito que busca competir con las generaciones Windows de Microsoft, a fin de proporcionar un ejemplo de cómo se desarrolla la cultura hacker a través del trabajo colectivo, la innovación tecnológica y la economía regalo. El trabajo cierra con una referencia al proyecto del e-México, proponiendo que los hackers y el software libre (Linux podrían generar una nueva cultura de apropiación y usos tecnológicos para el país.

Software

Energy Technology Data Exchange (ETDEWEB)

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

2010-07-15

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

Models for composing software : an analysis of software composition and objects

NARCIS (Netherlands)

Bergmans, Lodewijk

1999-01-01

In this report, we investigate component-based software construction with a focus on composition. In particular we try to analyze the requirements and issues for components and software composition. As a means to understand this research area, we introduce a canonical model for representing

Increasing the impact of usability work in software development

DEFF Research Database (Denmark)

Uldall-Espersen, Tobias; Frøkjær, Erik

2006-01-01

Usability, Case Study, Software Engineering, Software Quality, Organizational Impact, Usability Requirement Management, CHI 2007 workshop......Usability, Case Study, Software Engineering, Software Quality, Organizational Impact, Usability Requirement Management, CHI 2007 workshop...

Assuring Software Reliability

Science.gov (United States)

2014-08-01

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

Strengthening Software Authentication with the ROSE Software Suite

International Nuclear Information System (INIS)

White, G

2006-01-01

Many recent nonproliferation and arms control software projects include a software authentication regime. These include U.S. Government-sponsored projects both in the United States and in the Russian Federation (RF). This trend toward requiring software authentication is only accelerating. Demonstrating assurance that software performs as expected without hidden ''backdoors'' is crucial to a project's success. In this context, ''authentication'' is defined as determining that a software package performs only its intended purpose and performs said purpose correctly and reliably over the planned duration of an agreement. In addition to visual inspections by knowledgeable computer scientists, automated tools are needed to highlight suspicious code constructs, both to aid visual inspection and to guide program development. While many commercial tools are available for portions of the authentication task, they are proprietary and not extensible. An open-source, extensible tool can be customized to the unique needs of each project (projects can have both common and custom rules to detect flaws and security holes). Any such extensible tool has to be based on a complete language compiler. ROSE is precisely such a compiler infrastructure developed within the Department of Energy (DOE) and targeted at the optimization of scientific applications and user-defined libraries within large-scale applications (typically applications of a million lines of code). ROSE is a robust, source-to-source analysis and optimization infrastructure currently addressing large, million-line DOE applications in C and C++ (handling the full C, C99, C++ languages and with current collaborations to support Fortran90). We propose to extend ROSE to address a number of security-specific requirements, and apply it to software authentication for nonproliferation and arms control projects

Software Dependability and Safety Evaluations ESA's Initiative

Science.gov (United States)

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

Workflow-Based Software Development Environment

Science.gov (United States)

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

48 CFR 227.7203-10 - Contractor identification and marking of computer software or computer software documentation to...

Science.gov (United States)

2010-10-01

... operation of the software to display a restrictive rights legend or other license notice; and (2) Requires a... and marking of computer software or computer software documentation to be furnished with restrictive... Rights in Computer Software and Computer Software Documentation 227.7203-10 Contractor identification and...

What Counts in Software Process?

DEFF Research Database (Denmark)

Cohn, Marisa

2009-01-01

and conversations in negotiating between prescriptions from a model and the contingencies that arise in an enactment. A qualitative field study at two Agile software development companies was conducted to investigate the role of artifacts in the software development work and the relationship between these artifacts...... and the Software Process. Documentation of software requirements is a major concern among software developers and software researchers. Agile software development denotes a different relationship to documentation, one that warrants investigation. Empirical findings are presented which suggest a new understanding...

Software Engineering Reviews and Audits

CERN Document Server

Summers, Boyd L

2011-01-01

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

UN MODELO DE DIÁLOGO PARA LA EDUCCIÓN DE REQUISITOS DE SOFTWARE

Directory of Open Access Journals (Sweden)

CARLOS M. ZAPATA

2010-01-01

Full Text Available La educción de requisitos es importante en el desarrollo de software pues, dependiendo de la calidad de este proceso, se pueden desarrollar mejores aplicaciones de software. En la educción de requisitos, las entrevistas suelen ser el método más utilizado y se consideran diálogos entre analistas e interesados. Los trabajos realizados al respecto, presentan limitaciones como la carencia de una estructura definida para las entrevistas analistainteresado, obligando al analista a realizar de manera subjetiva el proceso de educción. En este artículo, se presenta una propuesta de estructura para un modelo de diálogo encaminado a la educción de requisitos de software. Además, se presenta la manera de realizar las preguntas durante una entrevista del proceso de educción, por medio de un caso de estudio.

Software educativo para enfermería

Directory of Open Access Journals (Sweden)

Mac Gaul de Jorge, Marcia Ivonne

2009-01-01

Full Text Available El presente trabajo relata la experiencia de investigación del proyecto investigación del proyecto Nº 1531 del CIUNSa, "Software Educativo para Enfermería del Adulto". El equipo integra a enfermeras, quienes en el año 2003 elaboraron un material que responde a la realidad epidemiológica de nuestro país, marcadamente diferente a textos clásicos provenientes de otras regiones del mundo. Convencidos que las universidades deben dar respuestas a los problemas regionales, se están desarrollando materiales educativos que, aprovechan las ventajas que la Informática brinda (altamente interactivos y que pueden actualizarse permanentemente. Esta investigación está finalizando su etapa diagnóstica, la cual posee dos objetivos específicos para el desarrollo del producto software: uno tendiente a indagar las competencias de los alumnos de Ciencias de la Salud con relación al uso de materiales educativos informatizados; el otro, modelar el sistema informático del cual serán usuarios los alumnos y docentes, para lo cual se están realizando actividades de Ingeniería de Requerimientos que permitan establecer el contexto en el que se utilizará el software desarrollado. Creemos que el estudio diagnóstico culminado sitúa a nuestros alumnos en la misma sintonía de los desarrolladores. Sus expectativas por un recurso efectivamente didáctico coinciden con nuestras directrices de diseño.

Acercamiento ontológico a la gestión del conocimiento en el mantenimiento del software

Directory of Open Access Journals (Sweden)

Edgar Serna Montoya

2010-01-01

Full Text Available Muchos documentos describen diseños ontológicos, pero pocos explican cómo se puede diseñar una ontología; además, muy pocos se enfocan en la aplicación de técnicas de gestión del conocimiento para el mantenimiento del software. En este trabajo se hace un análisis de varias de las ontologías propuestas para responder a esta necesidad, con la finalidad de que algunas de sus ideas puedan ayudar a las organizaciones de desarrollo de software en trabajos similares, y se describe una metodología para estructurar una ontología que, además del área del mantenimiento del software, se pueda aplicar a otras áreas del conocimiento.

Patterns for Parallel Software Design

CERN Document Server

Ortega-Arjona, Jorge Luis

2010-01-01

Essential reading to understand patterns for parallel programming Software patterns have revolutionized the way we think about how software is designed, built, and documented, and the design of parallel software requires you to consider other particular design aspects and special skills. From clusters to supercomputers, success heavily depends on the design skills of software developers. Patterns for Parallel Software Design presents a pattern-oriented software architecture approach to parallel software design. This approach is not a design method in the classic sense, but a new way of managin

Análisis de Desarrollo de Software Orientado a Feature - Línea de Producto de Software para Aplicaciones de TVDI

Directory of Open Access Journals (Sweden)

Mirtha Fabiana Miranda

2015-08-01

Full Text Available El Desarrollo de Software Orientado a Features (FOSD consiste en la construcción de sistemas a partir de un conjunto de características, cada feature o característica es una unidad funcional que satisface un requisito de software. Las fases son análisis del dominio, diseño e implementación del dominio, configuración y generación del producto de software, obteniendo así una Línea de Productos de Software (SPL. El presente trabajo realiza una comparación de herramientas para su implementación y, se analiza un conjunto de aplicaciones que modelan features. Resultando un espacio de estudio abierto para modelar aplicaciones para la Televisión Digital Interactiva (TVDi. Además se han encontrado diversos métodos, artefactos y patrones de diseño para el modelado de una aplicación de TVDi en particular, reflejando un estudio para el modelado de variabilidad. El objetivo principal es estudiar SPL / FOSD, empleando los Patrones de Diseño de Interacción (PDI para el dominio de las aplicaciones de TVDi.

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

International Nuclear Information System (INIS)

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)

Análisis del software libre como herramienta de producción

Directory of Open Access Journals (Sweden)

Eduardo Miguel De la Hoz Correa

2010-01-01

Full Text Available En este artículo se muestran datos cuantitativos que permiten tener una idea más clara al momento de la evaluación en la adquisición de software y la implementación de código abierto y software libre. En él se examinan variables como el mercado objetivo, la fiabilidad, el rendimiento, la escalabilidad, seguridad y el costo de adquisición al momento de mirar al código abierto como alternativa viable con respecto al software propietario desde una perspectiva objetiva teniendo como base estudios a fondo a nivel mundial de aquellos factores que influyen en la toma de decisiones en todos los niveles de implementación del software de todo tipo.

Software engineering methodologies and tools

Science.gov (United States)

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.

Autonomous Real Time Requirements Tracing

Science.gov (United States)

Plattsmier, George; Stetson, Howard

2014-01-01

One of the more challenging aspects of software development is the ability to verify and validate the functional software requirements dictated by the Software Requirements Specification (SRS) and the Software Detail Design (SDD). Insuring the software has achieved the intended requirements is the responsibility of the Software Quality team and the Software Test team. The utilization of Timeliner-TLX(sup TM) Auto- Procedures for relocating ground operations positions to ISS automated on-board operations has begun the transition that would be required for manned deep space missions with minimal crew requirements. This transition also moves the auto-procedures from the procedure realm into the flight software arena and as such the operational requirements and testing will be more structured and rigorous. The autoprocedures would be required to meet NASA software standards as specified in the Software Safety Standard (NASASTD- 8719), the Software Engineering Requirements (NPR 7150), the Software Assurance Standard (NASA-STD-8739) and also the Human Rating Requirements (NPR-8705). The Autonomous Fluid Transfer System (AFTS) test-bed utilizes the Timeliner-TLX(sup TM) Language for development of autonomous command and control software. The Timeliner-TLX(sup TM) system has the unique feature of providing the current line of the statement in execution during real-time execution of the software. The feature of execution line number internal reporting unlocks the capability of monitoring the execution autonomously by use of a companion Timeliner-TLX(sup TM) sequence as the line number reporting is embedded inside the Timeliner-TLX(sup TM) execution engine. This negates I/O processing of this type data as the line number status of executing sequences is built-in as a function reference. This paper will outline the design and capabilities of the AFTS Autonomous Requirements Tracker, which traces and logs SRS requirements as they are being met during real-time execution of the

Acometer contra un ERP con Software Libre

Directory of Open Access Journals (Sweden)

Esteban Crespo

2018-03-01

Full Text Available La seguridad de la información es una preocupación creciente en empresas y organizaciones, siendo más alta aun cuando se vincula a plataformas financieras donde existe información sensible. Este artículo resume las técnicas utilizadas en el pentesting realizado al software ERP desarrollado en APEX 5 por la Universidad del Azuay; para ello se han contemplado seis etapas que sugiere una prueba de penetración: i la conceptualización, donde se define el alcance de las pruebas a realizar; ii la preparación del laboratorio, en la que se identifican algunas de las herramientas que servirán para el inicio de las pruebas de seguridad; iii la obtención de información, donde se hace el reconocimiento y escaneo de posibles objetivos que posteriormente serán explorados con mayor profundidad para identificar características intrínsecas que puedan ser aprovechadas; iv el análisis de las vulnerabilidades encontradas en la etapa anterior; v la explotación de vulnerabilidades; y vi la post explotación, etapa que contempla la destrucción de evidencias del ataque y la conservación de la conexión y los accesos logrados para extraer información. Todas estas etapas fueron efectuadas dentro de las instalaciones de la Universidad del Azuay, considerando el ambiente de desarrollo en el que actualmente se encuentra este software.

Integrated modeling of software cost and quality

International Nuclear Information System (INIS)

Rone, K.Y.; Olson, K.M.

1994-01-01

In modeling the cost and quality of software systems, the relationship between cost and quality must be considered. This explicit relationship is dictated by the criticality of the software being developed. The balance between cost and quality is a viable software engineering trade-off throughout the life cycle. Therefore, the ability to accurately estimate the cost and quality of software systems is essential to providing reliable software on time and within budget. Software cost models relate the product error rate to the percent of the project labor that is required for independent verification and validation. The criticality of the software determines which cost model is used to estimate the labor required to develop the software. Software quality models yield an expected error discovery rate based on the software size, criticality, software development environment, and the level of competence of the project and the developers with respect to the processes being employed

Anticipating requirements changes-using futurology in requirements elicitation

OpenAIRE

Pimentel, João Henrique; Santos, Emanuel; Castro, Jaelson; Franch Gutiérrez, Javier

2012-01-01

It is well known that requirements changes in a later phase of software developments is a major source of software defects and costs. Thus, the need of techniques to control or reduce the amount of changes during software development projects. The authors advocate the use of foresight methods as a valuable input to requirements elicitation, with the potential to decrease the number of changes that would be required after deployment, by anticipating them. In this paper, the authors define a pr...

Un modelo para la solución de requerimientos no alineados: El caso del Software lúdico para la divulgación

Directory of Open Access Journals (Sweden)

Héctor G. Pérez-González

2015-12-01

Full Text Available Este artículo propone lineamientos metodológicos para ser aplicados en el proceso de requerimientos cuando estos se presentan como “No alineados”. Se considera que esta situación se da cuando los objetivos del propietario del software son distintos a los del usuario del mismo. Como caso de estudio se utiliza el desarrollo de software lúdico (también conocido como juegos digitales, videojuegos, o juegos serios con fines de divulgación. Esto involucra generalmente un conjunto de stakeholders más heterogéneo que el del software convencional. Adicionalmente, si el software se utiliza con objetivos de divulgación de ciencia, tecnología o innovación se agrega la complicación de la presencia de objetivos no alineados ya que el usuario final puede ignorar el objetivo real del software que utilizará. Consecuentemente el análisis de requerimientos cobra una importancia crucial. La literatura presenta propuestas para adaptar el proceso completo de software con objetivos educativos, sin poner atención al proceso de requerimientos ni a los objetivos de divulgación. Esta propuesta puede ser extrapolada a cualquier proceso de Ingeniería de requerimientos de Software donde se involucren requerimientos no alineados.

Software architecture evolution

DEFF Research Database (Denmark)

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

2008-01-01

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

Essential software architecture

CERN Document Server

Gorton, Ian

2011-01-01

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

The ATLAS Trigger Simulation with Legacy Software

CERN Document Server

Bernius, Catrin; The ATLAS collaboration

2017-01-01

Physics analyses at the LHC require accurate simulations of the detector response and the event selection processes, generally done with the most recent software releases. The trigger response simulation is crucial for determination of overall selection efficiencies and signal sensitivities and should be done with the same software release with which data were recorded. This requires potentially running with software dating many years back, the so-called legacy software. Therefore having a strategy for running legacy software in a modern environment becomes essential when data simulated for past years start to present a sizeable fraction of the total. The requirements and possibilities for such a simulation scheme within the ATLAS software framework were examined and a proof-of-concept simulation chain has been successfully implemented. One of the greatest challenges was the choice of a data format which promises long term compatibility with old and new software releases. Over the time periods envisaged, data...

Clinical software for MR imaging system, 4

International Nuclear Information System (INIS)

Shimizu, Koji; Kasai, Akira; Okamura, Shoichi

1992-01-01

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

A measurement system for large, complex software programs

Science.gov (United States)

Rone, Kyle Y.; Olson, Kitty M.; Davis, Nathan E.

1994-01-01

This paper describes measurement systems required to forecast, measure, and control activities for large, complex software development and support programs. Initial software cost and quality analysis provides the foundation for meaningful management decisions as a project evolves. In modeling the cost and quality of software systems, the relationship between the functionality, quality, cost, and schedule of the product must be considered. This explicit relationship is dictated by the criticality of the software being developed. This balance between cost and quality is a viable software engineering trade-off throughout the life cycle. Therefore, the ability to accurately estimate the cost and quality of software systems is essential to providing reliable software on time and within budget. Software cost models relate the product error rate to the percent of the project labor that is required for independent verification and validation. The criticality of the software determines which cost model is used to estimate the labor required to develop the software. Software quality models yield an expected error discovery rate based on the software size, criticality, software development environment, and the level of competence of the project and developers with respect to the processes being employed.

Tipología de Replicaciones para la Síntesis de Experimentos en Ingeniería del Software

OpenAIRE

Gómez Gómez, Omar Salvador

2012-01-01

La Ingenieria del Software Experimental (ISE) traslada a la Ingenieria del Software (IS) el paradigma experimental que se ha aplicado con exito en diversas disciplinas cientificas. El objetivo de la ISE es hacer de la construccion del software una actividad predecible gracias al conocimiento de las relaciones entre los procesos de produccion del software y los productos que se obtienen. Para avanzar en el paradigma experimental en IS no es suficiente aplicar las tecnicas de diseno experimenta...

Some remarks on software reliability

International Nuclear Information System (INIS)

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)

TWRS engineering bibliography software listing

International Nuclear Information System (INIS)

Husa, E.I.

1995-01-01

This document contains the computer software listing for Engineering Bibliography software, developed by E. Ivar Husa. This software is in the working prototype stage of development. The code has not been tested to requirements. TWRS Engineering created this software for engineers to share bibliographic references across the Hanford site network (HLAN). This software is intended to store several hundred to several thousand references (a compendium with limited range). Coded changes are needed to support the larger number of references

INGENIERÍA DE SOFTWARE ORIENTADA A AGENTES: ROLES Y METODOLOGÍAS

Directory of Open Access Journals (Sweden)

Joaquín Pina Amargós

2006-12-01

Full Text Available

Hoy los estándares de ingeniería de software, RUP como proceso de desarrollo y UML como lenguaje de modelado, enfrentan retos debido a los paradigmas distribuidos: Servicios Web y agentes. Los agentes, paradigma prometedor para la ingeniería de software, tienen un gran reto, la falta de estándares metodológicos para su desarrollo. En este trabajo se realiza un estudio comparativo de nueve metodologías de agentes, se analizan roles de personas en la ingeniería de software orientada a agentes y se proponen algunos roles no presentes en RUP y recomendaciones para otros sí presentes que parecen necesarios con este nuevo paradigma.

Software Engineering Improvement Activities/Plan

Science.gov (United States)

2003-01-01

bd Systems personnel accomplished the technical responsibilities for this reporting period, as planned. A close working relationship was maintained with personnel of the MSFC Avionics Department Software Group (ED14). Work accomplishments included development, evaluation, and enhancement of a software cost model, performing literature search and evaluation of software tools available for code analysis and requirements analysis, and participating in other relevant software engineering activities. Monthly reports were submitted. This support was provided to the Flight Software Group/ED 1 4 in accomplishing the software engineering improvement engineering activities of the Marshall Space Flight Center (MSFC) Software Engineering Improvement Plan.

Prácticas dirigidas a la mejora de la usabilidad del software

Directory of Open Access Journals (Sweden)

Gabriel Alberto García Mireles

2014-06-01

Full Text Available La usabilidad es un atributo del software (y sistema que considera la experiencia de las personas cuando interaccionan con las interfaces de un producto software. Una meta potencial de las organizaciones de desarrollo de software es mejorar la usabilidad de sus productos. Por otra parte, el software se desarrolla aplicando un proceso, el cual tiene un impacto significativo en la calidad final del producto, incluyendo su usabilidad. Teniendo esto en cuenta, en este trabajo se presenta un enfoque basado en el proceso de software en el cual nos interesa conocer las actividades, prácticas y métodos que podrían mejorar la usabilidad del software. Para ello, a partir de una revisión sistemática de literatura, identificamos los procesos de software que podrían ser complementados con prácticas de usabilidad. Adicionalmente, los métodos y técnicas de soporte a la usabilidad los relacionamos con cada proceso. Este es un primer paso en el desarrollo de una estrategia que permita introducir cambios en el proceso de software de cara a mejorar la usabilidad del producto.

Software para la enseñanza-aprendizaje de algoritmos estructurados

Directory of Open Access Journals (Sweden)

Arellano Pimentel, J. Jesús

2012-12-01

Full Text Available Actualmente existen diversas herramientas de software que sirven como recurso didáctico en la enseñanza-aprendizaje de algoritmos estructurados a nivel superior. Sin embargo, la gran mayoría solo hace énfasis en el diseño y prueba de los algoritmos. En el presente trabajo se propone un nuevo software, con base en la heurística de resolución de problemas de Polya, que da soporte a las fases de análisis y planteamiento del problema, además del diseño y traza completa de la prueba. Se realiza un análisis cualitativo entre el software propuesto y otras tres herramientas ampliamente utilizadas a nivel superior. La estructura y funcionalidad del software propuesto contribuye a que el estudiante adquiera, practique y ejercite la capacidad de resolver problemas de forma metódica a través de soluciones algorítmicas estructuradas.

Expression and crystallization of SeDsbA, SeDsbL and SeSrgA from Salmonella enterica serovar Typhimurium

International Nuclear Information System (INIS)

Jarrott, R.; Shouldice, S. R.; Gunčar, G.; Totsika, M.; Schembri, M. A.; Heras, B.

2010-01-01

The cloning, purification, crystallization and preliminary crystallographic studies of three DsbA-like proteins present in S. enterica serovar Typhimurium, SeDsbA, SeDsbL and SeSrgA, are reported. Pathogens require protein-folding enzymes to produce functional virulence determinants. These foldases include the Dsb family of proteins, which catalyze oxidative folding in bacteria. Bacterial disulfide catalytic processes have been well characterized in Escherichia coli K-12 and these mechanisms have been extrapolated to other organisms. However, recent research indicates that the K-12 complement of Dsb proteins is not common to all bacteria. Importantly, many pathogenic bacteria have an extended arsenal of Dsb catalysts that is linked to their virulence. To help to elucidate the process of oxidative folding in pathogens containing a wide repertoire of Dsb proteins, Salmonella enterica serovar Typhimurium has been focused on. This Gram-negative bacterium contains three DsbA proteins: SeDsbA, SeDsbL and SeSrgA. Here, the expression, purification, crystallization and preliminary diffraction analysis of these three proteins are reported. SeDsbA, SeDsbL and SeSrgA crystals diffracted to resolution limits of 1.55, 1.57 and 2.6 Å and belonged to space groups P2 1 , P2 1 2 1 2 and C2, respectively

Software for Optimizing Quality Assurance of Other Software

Science.gov (United States)

Feather, Martin; Cornford, Steven; Menzies, Tim

2004-01-01

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

Software Reuse Within the Earth Science Community

Science.gov (United States)

Marshall, James J.; Olding, Steve; Wolfe, Robert E.; Delnore, Victor E.

2006-01-01

Scientific missions in the Earth sciences frequently require cost-effective, highly reliable, and easy-to-use software, which can be a challenge for software developers to provide. The NASA Earth Science Enterprise (ESE) spends a significant amount of resources developing software components and other software development artifacts that may also be of value if reused in other projects requiring similar functionality. In general, software reuse is often defined as utilizing existing software artifacts. Software reuse can improve productivity and quality while decreasing the cost of software development, as documented by case studies in the literature. Since large software systems are often the results of the integration of many smaller and sometimes reusable components, ensuring reusability of such software components becomes a necessity. Indeed, designing software components with reusability as a requirement can increase the software reuse potential within a community such as the NASA ESE community. The NASA Earth Science Data Systems (ESDS) Software Reuse Working Group is chartered to oversee the development of a process that will maximize the reuse potential of existing software components while recommending strategies for maximizing the reusability potential of yet-to-be-designed components. As part of this work, two surveys of the Earth science community were conducted. The first was performed in 2004 and distributed among government employees and contractors. A follow-up survey was performed in 2005 and distributed among a wider community, to include members of industry and academia. The surveys were designed to collect information on subjects such as the current software reuse practices of Earth science software developers, why they choose to reuse software, and what perceived barriers prevent them from reusing software. In this paper, we compare the results of these surveys, summarize the observed trends, and discuss the findings. The results are very

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

International Nuclear Information System (INIS)

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

1997-07-01

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

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

Energy Technology Data Exchange (ETDEWEB)

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

1997-07-01

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

Safety-Critical Partitioned Software Architecture: A Partitioned Software Architecture for Robotic

Science.gov (United States)

Horvath, Greg; Chung, Seung H.; Cilloniz-Bicchi, Ferner

2011-01-01

The flight software on virtually every mission currently managed by JPL has several major flaws that make it vulnerable to potentially fatal software defects. Many of these problems can be addressed by recently developed partitioned operating systems (OS). JPL has avoided adopting a partitioned operating system on its flight missions, primarily because doing so would require significant changes in flight software design, and the risks associated with changes of that magnitude cannot be accepted by an active flight project. The choice of a partitioned OS can have a dramatic effect on the overall system and software architecture, allowing for realization of benefits far beyond the concerns typically associated with the choice of OS. Specifically, we believe that a partitioned operating system, when coupled with an appropriate architecture, can provide a strong infrastructure for developing systems for which reusability, modifiability, testability, and reliability are essential qualities. By adopting a partitioned OS, projects can gain benefits throughout the entire development lifecycle, from requirements and design, all the way to implementation, testing, and operations.

Quality Assurance in Software Development: An Exploratory Investigation in Software Project Failures and Business Performance

Science.gov (United States)

Ichu, Emmanuel A.

2010-01-01

Software quality is perhaps one of the most sought-after attributes in product development, however; this goal is unattained. Problem factors in software development and how these have affected the maintainability of the delivered software systems requires a thorough investigation. It was, therefore, very important to understand software…

Developing Software Simulations

Directory of Open Access Journals (Sweden)

Tom Hall

2007-06-01

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

48 CFR 227.7203-14 - Conformity, acceptance, and warranty of computer software and computer software documentation.

Science.gov (United States)

2010-10-01

... 48 Federal Acquisition Regulations System 3 2010-10-01 2010-10-01 false Conformity, acceptance... Software Documentation 227.7203-14 Conformity, acceptance, and warranty of computer software and computer...) Conformity and acceptance. Solicitations and contracts requiring the delivery of computer software shall...

Ensayo del modelo de calidad aplicado a software de minería de datos

OpenAIRE

García Márquez, Marilupe

2015-01-01

Este trabajo presenta una investigación acerca de los estándares de calidad de software ISO-IEC 9126 e ISO-IEC 14598, con la finalidad de reconocer la importancia de su aplicación durante la etapa de desarrollo de software. En este sentido, se plantea la necesidad de aplicar la calidad de software en las etapas de diseño, construcción e implantación para lograr un producto final con un alto porcentaje de calidad. Asimismo, con el propósito de medir la calidad, se establece la necesida...

Characterizing the contribution of quality requirements to software sustainability

NARCIS (Netherlands)

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

El software matemático y los lenguajes de programación

OpenAIRE

Quesada, José

1996-01-01

Se lleva a cabo un análisis de los lenguajes de programación desde el punto de vista de sus relaciones con el software matemático. Para ello se comienza con una definición bastante flexible de software matemático, para continuar con un análisis metodológico de los lenguajes de programación, estudiando los paradigmas imperativo, funcional, la programación lógica y la orientación a objetos. Por último se realiza un estudio histórico de los lenguajes de programación, así como de los lenguajes de...

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

Energy Technology Data Exchange (ETDEWEB)

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.

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

International Nuclear Information System (INIS)

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

Gestión de conocimiento: la solución para disminuir el reproceso en las pruebas de software

Directory of Open Access Journals (Sweden)

Luz A. Perona Ossaba

2012-12-01

Full Text Available La gestión de conocimiento se ha convertido en una clave fundamental en los procesos de la ingeniería de software, permitiendo mejorar y optimizar cada una de las actividades que se ejecutan durante todo el ciclo de desarrollo de software. Cada una de las etapas de la ingeniería de software ha adoptado de la gestión de conocimiento algunas características, de acuerdo con las necesidades que se presentan, adecuándolos y fortaleciéndolos para reducir los tiempos y disminuir la fuga de información dentro de las organizaciones. Es por esto que las pruebas de software han adoptado la gestión de conocimiento como la alternativa para disminuir el reproceso en las pruebas de software.

Software essentials design and construction

CERN Document Server

Dingle, Adair

2014-01-01

About the Cover: Although capacity may be a problem for a doghouse, other requirements are usually minimal. Unlike skyscrapers, doghouses are simple units. They do not require plumbing, electricity, fire alarms, elevators, or ventilation systems, and they do not need to be built to code or pass inspections. The range of complexity in software design is similar. Given available software tools and libraries-many of which are free-hobbyists can build small or short-lived computer apps. Yet, design for software longevity, security, and efficiency can be intricate-as is the design of large-scale sy

Arquitectura de Software de Referencia para Objetos Inteligentes en Internet de las Cosas

Directory of Open Access Journals (Sweden)

Ariel Alejandro Segura

2016-06-01

Full Text Available La evolución de los sistemas embebidos, que tuvo lugar junto al bajo costo y ubicuidad de internet, ha tenido como resultado el paradigma Internet de las Cosas. El objetivo de este paradigma es convertir los objetos que nos rodean en objetos inteligentes de forma tal que, comunicándose a través de Internet, puedan percibir lo que sucede en su entorno y poder reaccionar frente a ello. Se han llevado a cabo numerosos trabajos en materia de estandarización para este paradigma como, por ejemplo, protocolos de comunicación, topologías de red y arquitecturas software de alto nivel que consideran, por sobre todas las cosas, cómo integrar todas las piezas de una solución de Internet de las Cosas en un solo sistema. Sin embargo, no se han identificado arquitecturas de software para la construcción del software de un objeto inteligente que describa los componentes básicos que se deben incluir. En este trabajo se propone una arquitectura de referencia para la construcción de objetos inteligentes en Internet de las Cosas cuyo objetivo es que los ingenieros de software tengan una estructura en la cual basarse y poder reutilizar.

GIMS-Software for asset market experiments.

Science.gov (United States)

Palan, Stefan

2015-03-01

In this article we lay out requirements for an experimental market software for financial and economic research. We then discuss existing solutions. Finally, we introduce GIMS, an open source market software which is characterized by extensibility and ease of use, while offering nearly all of the required functionality.

Standards Interoperability: Application of Contemporary Software Safety Assurance Standards to the Evolution of Legacy Software

National Research Council Canada - National Science Library

Meacham, Desmond J

2006-01-01

.... The proposed formal model is then applied to the requirements for RTCA DO-178B and MIL-STD-498 as representative examples of contemporary and legacy software standards. The results provide guidance on how to achieve airworthiness certification for modified legacy software, whilst maximizing the use of software products from the previous development.

SWEBOS – The Software Engineering Body of Skills

Directory of Open Access Journals (Sweden)

Yvonne Sedelmaier

2015-02-01

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

La Esencia de la Ingeniería de Software: El Núcleo de Semat

Directory of Open Access Journals (Sweden)

Ivar Jacobson

2013-06-01

Full Text Available Esta es una traducción del artículo que se publicó en Communications of the ACM en Diciembre de 2012 bajo el título “The Essence of Software Engineering: The SEMAT Kernel” y se realiza debido a la importancia que adquiere el tema para la audiencia de hispanoparlantes, de forma que se pueda generar un acceso a lo que constituye uno de los últimos adelantos en Ingeniería de Software. Nota: Artículo publicado originalmente en Communications of the ACM, vol. 55, no. 12, december 2012, pp. 42-49. El traductor declara tener autorización de los autores para difundir la versión en español en la Revista Latinoamericana de Ingeniería de Software, sin que ello presente incompatibilidades o vulnere los derechos de Communications of the ACM.

Selecting the Right Software.

Science.gov (United States)

Shearn, Joseph

1987-01-01

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

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

Science.gov (United States)

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.

SMART-P MMIS Software Development by Considering the Software License for Nuclear Power Plants and the Development Cost

International Nuclear Information System (INIS)

Suh, Yong Suk; Park, Jae Hong; Park, Heui Youn; Son, Ki Sung; Lee, Ki Hyun; Kim, Hyeon Soo

2005-01-01

The acceptance criteria of software for safety system functions in NPPs (Nuclear Power Plants) are as follows: 1) acceptable plans should be prepared to control the software development activities, 2) the plans should be followed in an acceptable software life cycle, and 3) the process should produce acceptable design outputs. The KINS (Korea Institute of Nuclear Safety) recommended that the software life cycle should be established based on the IEEE Std 1074 with a supplementary requirement of a software safety analysis. The KINS emphasized that the software should be developed to show its high qualities. This paper identifies the major requirements to achieve the software license from the KINS and presents the major facts reflected in the SMART-P (System-integrated Modular Advanced ReacTor-Pilot) MMIS (Man-Machine Interface Systems) which is being developed by KAERI and targeted to start operation in 2010. This paper also addresses major concerns on the development of a safety critical software and the facts reflected in the SMART-P MMIS

Certificación de la Mantenibilidad del Producto Software: Un Caso Práctico

Directory of Open Access Journals (Sweden)

Moisés Rodríguez

2015-07-01

Full Text Available La calidad del software está adquiriendo durante los últimos años una gran importancia, principalmente debido a que el software está presente en prácticamente todo lo que nos rodea y se hace necesario asegurar su correcto funcionamiento. Sin embargo, hasta ahora la mayor parte de los estudios se han centrado en evaluar la calidad de los procesos de desarrollo, y aunque existen trabajos centrados en la calidad del producto software, no existe todavía una propuesta completa para la evaluación y certificación de la calidad del producto software, basada en la nueva familia de normas ISO/IEC 25000. El presente artículo expone un caso de estudio de evaluación, mejora y certificación de la mantenibilidad de un producto software, en el que han participado una empresa desarrolladora de software, un laboratorio de evaluación acreditado y una entidad de certificación. Para ello, se presentarán las características de este tipo de evaluaciones, el rol que cumple cada una de las entidades participantes y el proceso seguido desde la evaluación inicial hasta la certificación definitiva

GIMS—Software for asset market experiments

Science.gov (United States)

Palan, Stefan

2015-01-01

In this article we lay out requirements for an experimental market software for financial and economic research. We then discuss existing solutions. Finally, we introduce GIMS, an open source market software which is characterized by extensibility and ease of use, while offering nearly all of the required functionality. PMID:26525085

Non-intrusive Instance Level Software Composition

NARCIS (Netherlands)

Hatun, Kardelen

2014-01-01

A software system is comprised of parts, which interact through shared interfaces. Certain qualities of integration, such as loose-coupling, requiring minimal changes to the software and fine-grained localisation of dependencies, have impact on the overall software quality. Current general-purpose

EMULACIÓN DE ESCENARIOS VIRTUALES, EN UNA SDWLAN (SOFTWARE DEFINED WIRELESS LOCAL AREA NETWORK, DE UN CAMPUS UNIVERSITARIO

Directory of Open Access Journals (Sweden)

Gerlyn Duarte

2015-07-01

Full Text Available Las redes definidas por software (SDN = Software Defined Network es una arquitectura de red emergente que se destaca como una tecnología capaz de ofrecer un control más flexible y dinámico a la hora de gestionar el diseño y funciones de la red, donde se separan los planos de control y enrutamiento. Esto permite la centralización de los controles de la red basada en software. Se puede decir que es posible tener flexibilidad y rapidez al momento de configurar, implementar y administrar diferentes protocolos personalizados para los requerimientos de distintas redes. Actualmente, en una red convencional, cada conmutador y/o enrutador tienen software propietario que le dice qué hacer. SDN se centra principalmente en la parte cableada de la red de datos. Sin embargo, todas las ventajas de las SDN sólo se obtienen si se logra abarcar la totalidad de la infraestructura, desde el centro de datos al extremo de la red, permitiendo extender todos los beneficios de SDN hasta la red inalámbrica, para conseguir a su vez una red inalámbrica de área local definida por software (SDWLAN = Software Define Wireless Local Area Network. Es por ello que en el presente trabajo, se emuló parte de una SDWLAN de un campus universitario para observar la factibilidad de implementar SDN en la misma. Para la emulación se utilizó una variante del emulador Mininet que permite trabajar con redes inalámbricas. De igual forma, se efectuaron mediciones del ancho de banda de las SDWLAN emuladas, así como la interconectividad entre ellas. Se evidenció la facilidad y el rendimiento de trabajar con las herramientas de emulación de SDWLAN empleadas, permitiendo de igual forma la estructuración de distintas topologías de SDWLAN. Se comprobó que el emulador, el cual está aún en la fase beta, permite interactuar y ejecutar cualquier proceso como si se ejecutara directamente en un equipo con GNU/Linux de forma eficaz.

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

International Nuclear Information System (INIS)

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

REVISIÓN, VERIFICACIÓN Y VALIDACIÓN EN UN PROCESO DE DESARROLLO DE SOFTWARE / REVIEW, VERIFICATION AND VALIDATION IN A SOFTWARE DEVELOPMENT PROCESS

Directory of Open Access Journals (Sweden)

Javier Blanco Llano

2011-03-01

Full Text Available

En el presente artículo se expone una interpretación, a través de una metodología en los proyectos de desarrollo de software, del requisito ISO para el diseño. Esto responde a la necesidad de brindar aplicaciones informáticas que respondan con calidad a los requisitos de los clientes, para poder cumplir con la misión asignada de brindar soluciones integrales eficaces en Tecnologías de la Información y las Comunicaciones (TIC a la sociedad cubana. Dicha metodología, que responde a las etapas establecidas en el Ciclo Shewhart/Deming , clarifica qué hacer en el control de la calidad para aplicar el requisito ISO y está en fase de implementación en la empresa Desoft S.A.

Abstract

This article offers an interpretation of the ISO requirements to design using a methodology in software development projects. This responds to the need of giving informatic solutions which may satisfy the client´s requirements with quality. This let us accomplish the assigned mission of giving ICT efficient and integral solutions to Cuban society. This methodology, which follows the established steps on Shewhart/Deming Cycle, explains what to do regarding quality control to apply the ISO requirements and it is in an implementation phase in Desoft S.A. enterprise.

FY1995 study of very flexible software structures based on soft-software components; 1995 nendo yawarankana software buhin ni motozuku software no choju kozo ni kansuru kenkyu

Energy Technology Data Exchange (ETDEWEB)

NONE

1997-03-01

The purpose of this study is to develop the method and tools for changing the software structure flexibly along with the continuous continuous change of its environment and conditions of use. The goal is the software of very high adaptability by using soft-software components and flexible assembly. The CASE tool platform Sapid based on a fine-grained repository was developed and enforced for raising the abstraction level of program code and for mining potential flexible components. To reconstruct the software adaptable to a required environment, the SQM (Software Quark Model) was used in managing interconnectivity and other semantic relationships of among components. On these two basic systems, we developed various methods and tools such as those for static and dynamic analysis of very flexible software structures, program transformation description, program pattern extraction and composition component optimization by partial evaluation, component extraction by function slicing, code encapsulation, and component navigation and application. (NEDO)

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

Science.gov (United States)

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

Review of Bruce A reactor regulating system software

Energy Technology Data Exchange (ETDEWEB)

NONE

1995-12-01

Each of the four reactor units at the Ontario Hydro Bruce A Nuclear Generating Station is controlled by the Reactor Regulating System (RRS) software running on digital computers. This research report presents an assessment of the quality and reliability of the RRS software based on a review of the RRS design documentation, an analysis of certain significant Event Reports (SERs), and an examination of selected software changes. We found that the RRS software requirements (i.e., what the software should do) were never clearly documented, and that design documents, which should describe how the requirements are implemented, are incomplete and inaccurate. Some RRS-related SERs (i.e., reports on unexpected incidents relating to the reactor control) implied that there were faults in the RRS, or that RRS changes should be made to help prevent certain unexpected events. The follow-up investigations were generally poorly documented, and so it could not usually be determined that problems were properly resolved. The Bruce A software change control procedures require improvement. For the software changes examined, there was insufficient evidence provided by Ontario Hydro that the required procedures regarding change approval, independent review, documentation updates, and testing were followed. Ontario Hydro relies on the expertise of their technical staff to modify the RRS software correctly; they have confidence in the software code itself, even if the documentation is not up-to-date. Ontario Hydro did not produce the documentation required for an independent formal assessment of the reliability of the RRS. (author). 37 refs., 3 figs.

Review of Bruce A reactor regulating system software

International Nuclear Information System (INIS)

1995-12-01

Each of the four reactor units at the Ontario Hydro Bruce A Nuclear Generating Station is controlled by the Reactor Regulating System (RRS) software running on digital computers. This research report presents an assessment of the quality and reliability of the RRS software based on a review of the RRS design documentation, an analysis of certain significant Event Reports (SERs), and an examination of selected software changes. We found that the RRS software requirements (i.e., what the software should do) were never clearly documented, and that design documents, which should describe how the requirements are implemented, are incomplete and inaccurate. Some RRS-related SERs (i.e., reports on unexpected incidents relating to the reactor control) implied that there were faults in the RRS, or that RRS changes should be made to help prevent certain unexpected events. The follow-up investigations were generally poorly documented, and so it could not usually be determined that problems were properly resolved. The Bruce A software change control procedures require improvement. For the software changes examined, there was insufficient evidence provided by Ontario Hydro that the required procedures regarding change approval, independent review, documentation updates, and testing were followed. Ontario Hydro relies on the expertise of their technical staff to modify the RRS software correctly; they have confidence in the software code itself, even if the documentation is not up-to-date. Ontario Hydro did not produce the documentation required for an independent formal assessment of the reliability of the RRS. (author). 37 refs., 3 figs

Design Principles for Interactive Software

DEFF Research Database (Denmark)

The book addresses the crucial intersection of human-computer interaction (HCI) and software engineering by asking both what users require from interactive systems and what developers need to produce well-engineered software. Needs are expressed as...

A Guideline of Using Case Method in Software Engineering Courses

Science.gov (United States)

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

2014-01-01

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

El desarrollo de software dirigido por modelos en los repositorios institucionales

Directory of Open Access Journals (Sweden)

Jose Texier

2014-01-01

Full Text Available Los Repositorios Institucionales (RI se han consolidado en la academia, prueba de ello es el crecimiento en número de registros en los directorios existentes realizado por diferentes vías: autoarchivo por parte de autores, la incorporación de material a cargo de bibliotecarios, entre otras. En este trabajo se hace un relevamiento bibliográfico sobre el uso del enfoque de Desarrollo de Software Dirigido por Modelos (MDD en los sistemas de RI con el propósito de establecer una relación entre ellos. El MDD es un paradigma de construcción de software que asigna a los modelos un rol central y se derivan modelos que van desde los más abstractos a los más concretos. Este paradigma, además, proporciona un marco de trabajo que permite a los interesados compartir sus puntos de vista y manipular las representaciones de las entidades del dominio. En conclusión, el seguimiento de las diferentes investigaciones relevadas y lo aquí expuesto permiten incentivar implementaciones de software para los RI.

Terminological recommendations for software localization

Directory of Open Access Journals (Sweden)

Klaus-Dirk Schmitz

2012-08-01

Full Text Available After an explosive growth of data processing and software starting at the beginning of the 1980s, the software industry shifted toward a strong orientation in non-US markets at the beginning of the 1990s. Today we see the global marketing of software in almost all regions of the world. Since software is no longer used by IT experts only, and since European and national regulations require user interfaces, manuals and documentation to be provided in the language of the customer, the market for software translation, i.e. for software localization, is the fastest growing market in the translation business.

Terminological recommendations for software localization

Directory of Open Access Journals (Sweden)

Klaus-Dirk Schmitz

2009-03-01

Full Text Available After an explosive growth of data processing and software starting at the beginning of the 1980s, the software industry shifted toward a strong orientation in non-US markets at the beginning of the 1990s. Today we see the global marketing of software in almost all regions of the world. Since software is no longer used by IT experts only, and since European and national regulations require user interfaces, manuals and documentation to be provided in the language of the customer, the market for software translation, i.e. for software localization, is the fastest growing market in the translation business.

RESEÑA DEL SOFTWARE DISPONIBLE EN COLOMBIA PARA LA GESTIÓN DE INVENTARIOS EN CADENAS DE ABASTECIMIENTO

Directory of Open Access Journals (Sweden)

VALENTINA GUTIÉRREZ

2009-01-01

Full Text Available La gestión de los diferentes tipos de inventario a lo largo de una cadena de abastecimiento es un problema complejo que, en la mayoría de los casos de la industria colombiana e internacional, se aborda mediante la implementación de herramientas de software. Sin embargo, la decisión de implementar dichas herramientas está en muchos casos limitada por la capacidad financiera para invertir en ellas y por el desconocimiento de la oferta de software disponible en Colombia. Este artículo presenta una reseña del software disponible en Colombia para la gestión de inventarios con el fin de brindar a las empresas que se enfrentan a la decisión de implementar un software, una herramienta de soporte que indique cuál es la oferta en Colombia y cuáles son las características de los sistemas disponibles. Para esto se presenta primero el estado del arte, en el cual se identifica el resultado de la revisión de la literatura y el uso de las herramientas de software en la industria colombiana. Seguidamente se presenta la caracterización de los productos de software disponibles en el país. Dicha caracterización permite identificar la configuración general de los productos, los módulos de gestión con los que cuenta, las opciones de integración con otras herramientas informáticas, y la información general de precios e instalación. Finalmente se presentan las conclusiones del estudio y las futuras oportunidades de investigación.

Optimización de estados en la mejora de procesos de software

Directory of Open Access Journals (Sweden)

Ana Marys García Rodríguez

2016-08-01

Full Text Available En el desarrollo de software, se refleja una tendencia orientada hacia la definición y mejora continua de los procesos que promueven estratégicamente el respaldo y logro de las metas de una organización. En función de ello, el objetivo del artículo es desarrollar un proceso para la optimización de estados en la mejora de procesos de software, tomando como referencia los factores críticos de éxito. Se fundamenta en una investigación descriptiva bajo un enfoque racionalista crítico, método de análisis cuantitativo, lo cual permitió la efectividad del diseño del modelo. Se determina en los resultados que en la mejora de procesos de software existen considerable fracasos, lo cual se atribuye a que no se tiene en cuenta el estado de la organización integralmente, ni su ámbito de actuación en lo socio-cultural. Se concluye, sobre la importancia de definir una evaluación integral de las organizaciones, considerando los factores críticos del éxito, previo al inicio de una mejora de procesos, asimismo se recomienda el diseño propuesto como soporte tecnológico, que basado en un algoritmo genético, obtiene estados de mejora requeridos por las organizaciones como apoyo a la toma de decisiones a partir de su estado inicial y las buenas prácticas que puede aplicar para mejorarlo.

Combined application of Product Lifecycle and Software Configuration Management systems for ITER remote handling

International Nuclear Information System (INIS)

Muhammad, Ali; Esque, Salvador; Aha, Liisa; Mattila, Jouni; Siuko, Mikko; Vilenius, Matti; Jaervenpaeae, Jorma; Irving, Mike; Damiani, Carlo; Semeraro, Luigi

2009-01-01

The advantages of Product Lifecycle Management (PLM) systems are widely understood among the industry and hence a PLM system is already in use by International Thermonuclear Experimental Reactor (ITER) Organization (IO). However, with the increasing involvement of software in the development, the role of Software Configuration Management (SCM) systems have become equally important. The SCM systems can be useful to meet the higher demands on Safety Engineering (SE), Quality Assurance (QA), Validation and Verification (V and V) and Requirements Management (RM) of the developed software tools. In an experimental environment, such as ITER, the new remote handling requirements emerge frequently. This means the development of new tools or the modification of existing tools and the development of new remote handling procedures or the modification of existing remote handling procedures. PLM and SCM systems together can be of great advantage in the development and maintenance of such remote handling system. In this paper, we discuss how PLM and SCM systems can be integrated together and play their role during the development and maintenance of ITER remote handling system. We discuss the possibility to investigate such setup at DTP2 (Divertor Test Platform 2), which is the full scale mock-up facility to verify the ITER divertor remote handling and maintenance concepts.

Arquitectura de software para los actuales Sistemas Ciber-Físicos

Directory of Open Access Journals (Sweden)

Jeannette S. Ting

2011-06-01

Full Text Available La próxima generación de sistemas ciber-físicos –CPS– plantea grandes desafíos en el diseño de software. No se trata sólo de diseñar un sistema en torno a los plazos de ejecución, lo más importante es maximizar la utilización de recursos. En este artículo se propone un sistema de base para la arquitectura de software en el que los servicios se puedan diseñar e implementar y componer fácilmente de acuerdo con la demanda y mediante aplicaciones individuales, de manera que satisfagan requisitos específicos de confianza, seguridad, eficiencia, confiabilidad y previsibilidad, mientras que permanecen dentro de la límites de las capacidades del hardware determinado.

Sandia National Laboratories Advanced Simulation and Computing (ASC) software quality plan : ASC software quality engineering practices Version 3.0.

Energy Technology Data Exchange (ETDEWEB)

Turgeon, Jennifer L.; Minana, Molly A.; Hackney, Patricia; Pilch, Martin M.

2009-01-01

The purpose of the Sandia National Laboratories (SNL) Advanced Simulation and Computing (ASC) Software Quality Plan is to clearly identify the practices that are the basis for continually improving the quality of ASC software products. Quality is defined in the US Department of Energy/National Nuclear Security Agency (DOE/NNSA) Quality Criteria, Revision 10 (QC-1) as 'conformance to customer requirements and expectations'. This quality plan defines the SNL ASC Program software quality engineering (SQE) practices and provides a mapping of these practices to the SNL Corporate Process Requirement (CPR) 001.3.6; 'Corporate Software Engineering Excellence'. This plan also identifies ASC management's and the software project teams responsibilities in implementing the software quality practices and in assessing progress towards achieving their software quality goals. This SNL ASC Software Quality Plan establishes the signatories commitments to improving software products by applying cost-effective SQE practices. This plan enumerates the SQE practices that comprise the development of SNL ASC's software products and explains the project teams opportunities for tailoring and implementing the practices.

Proceso de desarrollo de software con técnicas de creatividad, para las pymes de la ciudad de Neiva

OpenAIRE

Martínez Vidal, Eduardo

2017-01-01

El proyecto que se presenta en este artículo se origina a partir de una necesidad identificada en empresas de desarrollo de software del municipio de Neiva, relacionada con hacer uso de buenas prácticas en el proceso de desarrollo de software, que permitieran la construcción de productos de calidad con un factor diferenciador. Para dar respuesta a esta necesidad, se realizó la adaptación de un proceso de desarrollo de software, a partir del proceso DAD (Disciplined Agile Delivery), e incorpor...

Software for safety critical applications

International Nuclear Information System (INIS)

Kropik, M.; Matejka, K.; Jurickova, M.; Chudy, R.

2001-01-01

The contribution gives an overview of the project of the software development for safety critical applications. This project has been carried out since 1997. The principal goal of the project was to establish a research laboratory for the development of the software with the highest requirements for quality and reliability. This laboratory was established at the department, equipped with proper hardware and software to support software development. A research team of predominantly young researchers for software development was created. The activities of the research team started with studying and proposing the software development methodology. In addition, this methodology was applied to the real software development. The verification and validation process followed the software development. The validation system for the integrated hardware and software tests was brought into being and its control software was developed. The quality of the software tools was also observed, and the SOSAT tool was used during these activities. National and international contacts were established and maintained during the project solution.(author)

Light Duty Utility Arm Software Test Plan

International Nuclear Information System (INIS)

Kiebel, G.R.

1995-01-01

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

The Legacy of Space Shuttle Flight Software

Science.gov (United States)

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

2011-01-01

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

Computer software configuration management

International Nuclear Information System (INIS)

Pelletier, G.

1987-08-01

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

Software for microcircuit systems

International Nuclear Information System (INIS)

Kunz, P.F.

1978-10-01

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

Herramienta de gestión de Modelos Ontológicos aplicados a la Mejora de Procesos Software

Directory of Open Access Journals (Sweden)

José Eduardo Guadalupe Gaytán Solís

2013-12-01

Full Text Available Actualmente el software representa un componente principal en el desarrollo de las actividades dentro de las organizaciones. Este hecho hace que la calidad del software sea uno de los principales factores claves a los que se dedica mucho esfuerzo. La calidad del software permite de manera implícita la creación de valor agregado al software durante su desarrollo, resultando en un factor de competitividad en estas organizaciones. Éste trabajo propone una solución inteligente mediante el uso de gestión del conocimiento, con el fin de hacer que la aplicación de teorías de ingeniería de software, modelos y estándares de mejora de procesos sea de fácil implementación y a un menor costo. Específicamente, en este trabajo se presenta el desarrollo de un modelo ontológico basado el Cuerpo de Conocimientos de la Ingeniería de Software (SWEBOK por las siglas en inglés de Software Engineering Body of Knowledge así como su aplicación práctica mediante un sistema software. Finalmente se presentan los resultados de la implementación de técnicas, métricas y actividades correspondientes al área de conocimiento de pruebas de software de SWEBOK. Así mismo se presentan resultados de la integración del marco base de datos de lenguaje ontológico web (OWLDB por las siglas en ingles ontology web language data base, con el objetivo de almacenar datos de manera persistente durante la aplicación.

Pruebas de Software. Fundamentos y Técnicas

OpenAIRE

Sánchez Peño, José Manuel

2015-01-01

Este proyecto estudia los fundamentos y las técnicas de las pruebas de software. Veremos lo importante que pueden llegar a ser las pruebas, mostrando diferentes desastres causados por fallos en el software. También estudiaremos las diferentes herramientas que se utilizan para llevar a cabo la gestión, administración y ejecución de estas pruebas. Finalmente aplicaremos los conceptos estudiados mediante un caso práctico. Crearemos los casos de prueba funcionales basándonos en las espec...

Software refactoring at the package level using clustering techniques

KAUST Repository

Alkhalid, A.; Alshayeb, M.; Mahmoud, S. A.

2011-01-01

Enhancing, modifying or adapting the software to new requirements increases the internal software complexity. Software with high level of internal complexity is difficult to maintain. Software refactoring reduces software complexity and hence

Clinical software development for the Web: lessons learned from the BOADICEA project.

Science.gov (United States)

Cunningham, Alex P; Antoniou, Antonis C; Easton, Douglas F

2012-04-10

In the past 20 years, society has witnessed the following landmark scientific advances: (i) the sequencing of the human genome, (ii) the distribution of software by the open source movement, and (iii) the invention of the World Wide Web. Together, these advances have provided a new impetus for clinical software development: developers now translate the products of human genomic research into clinical software tools; they use open-source programs to build them; and they use the Web to deliver them. Whilst this open-source component-based approach has undoubtedly made clinical software development easier, clinical software projects are still hampered by problems that traditionally accompany the software process. This study describes the development of the BOADICEA Web Application, a computer program used by clinical geneticists to assess risks to patients with a family history of breast and ovarian cancer. The key challenge of the BOADICEA Web Application project was to deliver a program that was safe, secure and easy for healthcare professionals to use. We focus on the software process, problems faced, and lessons learned. Our key objectives are: (i) to highlight key clinical software development issues; (ii) to demonstrate how software engineering tools and techniques can facilitate clinical software development for the benefit of individuals who lack software engineering expertise; and (iii) to provide a clinical software development case report that can be used as a basis for discussion at the start of future projects. We developed the BOADICEA Web Application using an evolutionary software process. Our approach to Web implementation was conservative and we used conventional software engineering tools and techniques. The principal software development activities were: requirements, design, implementation, testing, documentation and maintenance. The BOADICEA Web Application has now been widely adopted by clinical geneticists and researchers. BOADICEA Web

The ATLAS Trigger Simulation with Legacy Software

CERN Document Server

Bernius, Catrin; The ATLAS collaboration

2017-01-01

Physics analyses at the LHC which search for rare physics processes or measure Standard Model parameters with high precision require accurate simulations of the detector response and the event selection processes. The accurate simulation of the trigger response is crucial for determination of overall selection efficiencies and signal sensitivities. For the generation and the reconstruction of simulated event data, generally the most recent software releases are used to ensure the best agreement between simulated data and real data. For the simulation of the trigger selection process, however, the same software release with which real data were taken should be ideally used. This requires potentially running with software dating many years back, the so-called legacy software. Therefore having a strategy for running legacy software in a modern environment becomes essential when data simulated for past years start to present a sizeable fraction of the total. The requirements and possibilities for such a simulatio...

Dynamic visualization techniques for high consequence software

Energy Technology Data Exchange (ETDEWEB)

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.

Modelo de aseguramiento de la calidad en el proceso de desarrollo de software basado en los modelos de madurez de capacidades (CMMi), proceso de software para equipos (TSP) y personas (PSP)

OpenAIRE

Espejo Chavarría, Alex José

2016-01-01

Genera e implementa un modelo de aseguramiento de la calidad en el proceso de desarrollo de software con un enfoque orientado al factor humano; factor que es responsable de introducir y gestionar la calidad en el proceso de desarrollo de software. El modelo propuesto se basa en tres modelos “Modelos de Madurez de Capacidades Integrado, Proceso de Software para Equipos y Proceso de Software para Personas. Tesis

Storage system software solutions for high-end user needs

Science.gov (United States)

Hogan, Carole B.

1992-01-01

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

Simple solution to the medical instrumentation software problem

Science.gov (United States)

Leif, Robert C.; Leif, Suzanne B.; Leif, Stephanie H.; Bingue, E.

1995-04-01

Medical devices now include a substantial software component, which is both difficult and expensive to produce and maintain. Medical software must be developed according to `Good Manufacturing Practices', GMP. Good Manufacturing Practices as specified by the FDA and ISO requires the definition and compliance to a software processes which ensures quality products by specifying a detailed method of software construction. The software process should be based on accepted standards. US Department of Defense software standards and technology can both facilitate the development and improve the quality of medical systems. We describe the advantages of employing Mil-Std-498, Software Development and Documentation, and the Ada programming language. Ada provides the very broad range of functionalities, from embedded real-time to management information systems required by many medical devices. It also includes advanced facilities for object oriented programming and software engineering.

A Study on the Software Quality Assurance Plan

International Nuclear Information System (INIS)

Kim, Hyun Tae

2006-01-01

On 25 August 2006, the CMMI V1.2 (Capability Maturity Model Integration Version 1.2) was released with the new title CMMI-DEV (CMMI for Development) which supersedes the CMMI-SE/SW (CMMI for systems engineering and software engineering) V1.1. This study discusses the application of IEEE Std 730-2002, IEEE Standard for Software Quality Assurance Plans, for the implementation of the Process and Product Quality Assurance (PPQA) process area (PA) of the CMMI-DEV

Petroleum software and the road ahead

International Nuclear Information System (INIS)

Heggelund, D.G.

1996-01-01

Regardless of what software vendors want to do, in the end, it is the user, through his/her choices of software products, who will decide what the software of the petroleum-engineering industry will look like. In this article, the author has looked at several items that will impact the future of petroleum-engineering software. Out of these, two will stand out: (1) the adoption of a single integrated dynamic reservoir model and (2) the move to a client/server architecture. However, the biggest challenge for both vendors and users will be to manage change. This will require users to participate more actively in the development of new technology and to be willing to pay for it, and it will require vendors to adopt standards more readily

Upgrade Software and Computing

CERN Document Server

The LHCb Collaboration, CERN

2018-01-01

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

Hybrid 95: Software for the design of hybrid systems, Potrerillo of Santa Teresa; Hybrid 95: Software de diseno de sistemas hibridos, Potrerillo de Santa Teresa

Energy Technology Data Exchange (ETDEWEB)

Casaravilla, G.; Chaer, R. [Instituto de Ingenieria Electrica, Facultad de Ingenieria, Universidad de la Republica, Montevideo (Uruguay)

1997-12-31

This paper describes the software Hybrid 95 and how it is used for the design of hybrid systems. As an application example some of the design stages are looked over (determination of the wind resource, simulations for sizing generation/storage and topology) of the Potrerillo installation. Taking into account the site clear ecological connotations, during the design consideration is made of the visual impact that represents the possible wind-generator, therefore several locations and wind-generator heights are studied, even arriving to the wind-generation elimination. [Espanol] Este trabajo describe el software Hybrid 95 y como se utiliza a los efectos del diseno de sistemas hibridos. Como ejemplo de aplicacion se recorren algunas de las etapas del diseno (determinacion del recurso eolico, simulaciones para el dimensionado de generacion/acumulacion y topologia) de la instalacion de Potrerillo. Teniendo en cuenta las claras connotaciones ecologistas del lugar, durante el diseno se tiene presente el impacto visual que representa el eventual aerogenerador por lo que se estudian diversas ubicaciones y alturas de aerogenerador, llegandose incluso a estudiar la eliminacion de la generacion eolica.

Hybrid 95: Software for the design of hybrid systems, Potrerillo of Santa Teresa; Hybrid 95: Software de diseno de sistemas hibridos, Potrerillo de Santa Teresa

Energy Technology Data Exchange (ETDEWEB)

Casaravilla, G; Chaer, R [Instituto de Ingenieria Electrica, Facultad de Ingenieria, Universidad de la Republica, Montevideo (Uruguay)

1998-12-31

This paper describes the software Hybrid 95 and how it is used for the design of hybrid systems. As an application example some of the design stages are looked over (determination of the wind resource, simulations for sizing generation/storage and topology) of the Potrerillo installation. Taking into account the site clear ecological connotations, during the design consideration is made of the visual impact that represents the possible wind-generator, therefore several locations and wind-generator heights are studied, even arriving to the wind-generation elimination. [Espanol] Este trabajo describe el software Hybrid 95 y como se utiliza a los efectos del diseno de sistemas hibridos. Como ejemplo de aplicacion se recorren algunas de las etapas del diseno (determinacion del recurso eolico, simulaciones para el dimensionado de generacion/acumulacion y topologia) de la instalacion de Potrerillo. Teniendo en cuenta las claras connotaciones ecologistas del lugar, durante el diseno se tiene presente el impacto visual que representa el eventual aerogenerador por lo que se estudian diversas ubicaciones y alturas de aerogenerador, llegandose incluso a estudiar la eliminacion de la generacion eolica.

SCaN Testbed Software Development and Lessons Learned

Science.gov (United States)

Kacpura, Thomas J.; Varga, Denise M.

2012-01-01

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

INCOSE Systems Engineering Handbook v3.2: Improving the Process for SE Practitioners

Energy Technology Data Exchange (ETDEWEB)

R. Douglas Hamelin; David D. Walden; Michael E. Krueger

2010-07-01

The INCOSE Systems Engineering Handbook is the official INCOSE reference document for understanding systems engineering (SE) methods and conducting SE activities. Over the years, the Handbook has evolved to accommodate advances in the SE discipline and now serves as the basis for the Certified Systems Engineering Professional (CSEP) exam. Due to its evolution, the Handbook had become somewhat disjointed in its treatment and presentation of SE topics and was not aligned with the latest version of International Organization for Standardization (ISO)/International Electrotechnical Commission (IEC) 15288:2008, Systems and Software Engineering. As a result, numerous inconsistencies were identified that could confuse practitioners and directly impact the probability of success in passing the CSEP exam. Further, INCOSE leadership had previously submitted v3.1 of the Handbook to ISO/IEC for consideration as a Technical Report, but was told that the Handbook would have to be updated to conform with the terminology and structure of new ISO/IEC15288:2008, Systems and software engineering, prior to being considered. The revised INCOSE Systems Engineering Handbook v3.2 aligns with the structure and principles of ISO/IEC 15288:2008 and presents the generic SE life-cycle process steps in their entirety, without duplication or redundancy, in a single location within the text. As such, the revised Handbook v3.2 serves as a comprehensive instructional and reference manual for effectively understanding SE processes and conducting SE and better serves certification candidates preparing for the CSEP exam.

SeDiCI: Servicio de Difusión de la Creación Intelectual

Directory of Open Access Journals (Sweden)

Marisa R. de Giusti

2008-07-01

Full Text Available Presenta el Servicio de Difusión de la Creación Intelectual (SeDiCI de la Universidad Nacional de La Plata (UNLP, Argentina, desde el punto de vista de los objetivos que condujeron a la UNLP a su creación. Se describen en detalle las etapas por las que se atravesó para poner en marcha este repositorio institucional y especialmente las facilidades que provee el software Celsius-DL desarrollado en la UNLP que soporta el Portal de SeDiCI.

Metodología iterativa de desarrollo de software para microempresas

Directory of Open Access Journals (Sweden)

Luis Alexander Calvo-Valverde

2015-09-01

El presente trabajo hace un diagnóstico sobre las características de las microempresas costarricenses de desarrollo de software; seguidamente, determina las mejores prácticas en las metodologías de desarrollo de software, para luego hacer un análisis comparativo y proponer una metodología de desarrollo que se adecúe a este tipo de organizaciones.

Seven Processes that Enable NASA Software Engineering Technologies

Science.gov (United States)

Housch, Helen; Godfrey, Sally

2011-01-01

This slide presentation reviews seven processes that NASA uses to ensure that software is developed, acquired and maintained as specified in the NPR 7150.2A requirement. The requirement is to ensure that all software be appraised for the Capability Maturity Model Integration (CMMI). The enumerated processes are: (7) Product Integration, (6) Configuration Management, (5) Verification, (4) Software Assurance, (3) Measurement and Analysis, (2) Requirements Management and (1) Planning & Monitoring. Each of these is described and the group(s) that are responsible is described.

Customizable software architectures in the accelerator control system environment

CERN Document Server

Mejuev, I; Kadokura, E

2001-01-01

Tailoring is further evolution of an application after deployment in order to adapt it to requirements that were not accounted for in the original design. End-user customization has been extensively researched in applied computer science from HCI and software engineering perspectives. Customization allows coping with flexibility requirements, decreasing maintenance and development costs of software products. In general, dynamic or diverse software requirements constitute the need for implementing end-user customization in computer systems. In accelerator physics research the factor of dynamic requirements is especially important, due to frequent software and hardware modifications resulting in correspondingly high upgrade and maintenance costs. We introduce the results of feasibility study on implementing end-user tailorability in the software for accelerator control system, considering the design and implementation of a distributed monitoring application for the 12 GeV KEK Proton Synchrotron as an example. T...

Prueba del software: más que una fase en el ciclo de vida/Software testing: more than a stage in the life cycle

Directory of Open Access Journals (Sweden)

Edgar Serna

2011-12-01

Full Text Available La prueba de software es probablemente la parte menos comprendida del ciclo de vida del desarrollo de software. En este trabajo, mediante una propuesta metodológica de cuatro fases, se muestra por qué es difícil detectar y eliminar errores, por qué es complejo el proceso de realizar pruebas y por qué es necesario prestarle más atención.Software testing probably is the least understood part of the software testing life cycle. In this work, by means of a methodological proposal of four stages, is showed why is complex the process of carrying out the testing software, why is necessary to pay it more attention and why is so difficult to detect and delete the mistakes.

Validation testing of safety-critical software

International Nuclear Information System (INIS)

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)

R D software quality assurance

Energy Technology Data Exchange (ETDEWEB)

Hood, F.C.

1991-10-01

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

PRAPRAG: software para planejamento racional de máquinas agrícolas PRAPRAG: software for rational planning of agricultural machines

Directory of Open Access Journals (Sweden)

Erivelto Mercante

2010-04-01

Full Text Available O software PRAPRAG é uma ferramenta de escolha de máquinas e implementos agrícolas que apresentam o menor custo por área ou por quantidade produzida, bem como, faz o planejamento de aquisição das máquinas para a propriedade agrícola, do ponto de vista técnico e econômico. Foi utilizada a linguagem de programação Borland Delphi 3.0 e, a partir de prospectos das máquinas e implementos, criou-se um banco de dados onde o usuário pode cadastrar e modificar suas características de uso. O software mostrou-se uma ferramenta útil e uso amigável. O software proporciona maior rapidez, segurança e confiabilidade ao processo produtivo e econômico das propriedades, na seleção e aquisição de conjuntos mecanizados agrícolas, e na determinação de custos com a mão de obra utilizada.The software PRAPRAG is a tool used for choosing agricultural machines and implements that present the lowest cost per area or produced amount, as well as, to it makes the machines acquisition planning for the agricultural property, from both technical and economical points of view. It was used the programming language Borland Delphi 3.0. From the machine and implement handouts, it was created a database where the user can register and modify their characteristics of use. The software showed to be a useful and friendly tool. The software provides high speed, safety and reliability for the productive and economical process of the properties, at the selection and acquisition of agricultural systems, as well as for the determination of costs with the used labor.

SWiFT Software Quality Assurance Plan.

Energy Technology Data Exchange (ETDEWEB)

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

2016-01-01

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

Risk reduction using DDP (Defect Detection and Prevention): Software support and software applications

Science.gov (United States)

Feather, M. S.

2001-01-01

Risk assessment and mitigation is the focus of the Defect Detection and Prevention (DDP) process, which has been applied to spacecraft technology assessments and planning, both hardware and software. DDP's major elements and their relevance to core requirement engineering concerns are summarized. The accompanying research demonstration illustrates DDP's tool support, and further customizations for application to software.

Techniques and tools for software qualification in KNICS

International Nuclear Information System (INIS)

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

Software for microcircuit systems

International Nuclear Information System (INIS)

Kunz, P.F.

1978-01-01

Modern Large Scale Integration (LSI) microcircuits are meant to be programmed in order to control the function that they perform. In the previous paper the author has already discussed the basics of microprogramming and have studied in some detail two types of new microcircuits. In this paper, methods of developing software for these microcircuits are explored. This generally requires a package of support software in order to assemble the microprogram, and also some amount of support software to test the microprograms and to test the microprogrammed circuit itself. (Auth.)

SOFTWARE FOR FAULT DIAGNOSIS USING KNOWLEDGE MODELS IN PETRI NETS

Directory of Open Access Journals (Sweden)

ADRIAN ARBOLEDA

2012-01-01

Full Text Available Los sistemas de diagnóstico de fallas en empresas asociadas al sector eléctrico requieren propiedades de precisión y flexibilidad cuando surgen eventos de falla. Actualmente existen sistemas que pretenden mejorar el proceso de diagnóstico mediante varios métodos y técnicas computacionales, reduciendo el tiempo de respuesta a perturbaciones. Sin embargo, son pocas las propuestas que unifican modelos gráficos de conocimiento con las señales de un proceso que pueden ofrecer dispositivos como controladores lógicos programables (PLCs. Este artículo propone un software novedoso guiado por modelos basados en redes de Petri e integrado con señales del proceso, para el diagnóstico de falla en centrales de generación eléctrica. Un caso de estudio demuestra la flexibilidad y adaptabilidad del software cuando nuevas nociones en los modelos de conocimiento cambian, sin realizar procedimientos de reingeniería al software.

Repositorios digitales y software open source

Directory of Open Access Journals (Sweden)

Doria, María Vanesa

2015-06-01

Full Text Available En la actualidad las universidades se encuentran en constante evolución, fruto de la transformación generada por la sociedad de la información y el conocimiento, donde la transversalidad son las Tecnologías de la Información y Comunicación (TIC, que tienen como objetivo ampliar el acceso a la información y el conocimiento a través de su herramienta digital más distinguida, Internet. Las universidades retroalimentan su conocimiento e información, mediante las producciones científicasacadémicas, y para promover el acceso a ellas, muchas universidades están inclinándose al movimiento del Acceso Abierto (AA siguiendo la vía verde en el desarrollo de repositorios digitales (RD. Para la creación de RD es necesario analizar los software open source disponibles, dado que estos son las herramientas que facilitan la automatización de los mismos. El presente estudio se centra en el análisis de los software open source existentes en el mercado.

Physics Validation of the LHC Software

CERN Multimedia

CERN. Geneva

2004-01-01

The LHC Software will be confronted to unprecedented challenges as soon as the LHC will turn on. We summarize the main Software requirements coming from the LHC detectors, triggers and physics, and we discuss several examples of Software components developed by the experiments and the LCG project (simulation, reconstruction, etc.), their validation, and their adequacy for LHC physics.

Reviews in innovative software development

DEFF Research Database (Denmark)

Aaen, Ivan; Boelsmand, Jeppe Vestergaard; Jensen, Rasmus

2009-01-01

This paper proposes a new review approach for innovative software development. Innovative software development implies that requirements are rarely available as a basis for reviewing and that the purpose of a review is as much to forward additional ideas, as to validate what has been accomplished...

The Systems Biology Research Tool: evolvable open-source software

OpenAIRE

Wright, J; Wagner, A

2008-01-01

Abstract Background Research in the field of systems biology requires software for a variety of purposes. Software must be used to store, retrieve, analyze, and sometimes even to collect the data obtained from system-level (often high-throughput) experiments. Software must also be used to implement mathematical models and algorithms required for simulation and theoretical predictions on the system-level. Results We introduce a free, easy-to-use, open-source, integrated software platform calle...

Software Quality Assurance for Nuclear Safety Systems

International Nuclear Information System (INIS)

Sparkman, D R; Lagdon, R

2004-01-01

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

Secure Software Configuration Management Processes for nuclear safety software development environment

International Nuclear Information System (INIS)

Chou, I.-Hsin

2011-01-01

Highlights: → The proposed method emphasizes platform-independent security processes. → A hybrid process based on the nuclear SCM and security regulations is proposed. → Detailed descriptions and Process Flow Diagram are useful for software developers. - Abstract: The main difference between nuclear and generic software is that the risk factor is infinitely greater in nuclear software - if there is a malfunction in the safety system, it can result in significant economic loss, physical damage or threat to human life. However, secure software development environment have often been ignored in the nuclear industry. In response to the terrorist attacks on September 11, 2001, the US Nuclear Regulatory Commission (USNRC) revised the Regulatory Guide (RG 1.152-2006) 'Criteria for use of computers in safety systems of nuclear power plants' to provide specific security guidance throughout the software development life cycle. Software Configuration Management (SCM) is an essential discipline in the software development environment. SCM involves identifying configuration items, controlling changes to those items, and maintaining integrity and traceability of them. For securing the nuclear safety software, this paper proposes a Secure SCM Processes (S 2 CMP) which infuses regulatory security requirements into proposed SCM processes. Furthermore, a Process Flow Diagram (PFD) is adopted to describe S 2 CMP, which is intended to enhance the communication between regulators and developers.

Science and Software

Science.gov (United States)

Zelt, C. A.

2017-12-01

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

Una Revisión Sistemática en los Marcos de Trabajo de Desarrollo Software en las MiPyMEs Productoras de Software

OpenAIRE

Antonio A. Aguileta; Grisel B. Ancona; Edwin J. León; Juan P. Ucán

2015-01-01

Una revisión sistemática es considerada como un método o protocolo que permite sintetizar investigaciones científicas de diversas áreas, la Ingeniería de Software no es la excepción. En este artículo se presenta este protocolo aplicado en la búsqueda de publicaciones relacionadas con las adaptaciones a los marcos de trabajo de desarrollo de software llevadas a cabo en MiPyMEs desarrolladoras de software, en el período comprendido de 1995 al 2013, centrándose en tendencias, países y sectores q...

Interface-based software integration

Directory of Open Access Journals (Sweden)

Aziz Ahmad Rais

2016-07-01

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

Effective Software Engineering Leadership for Development Programs

Science.gov (United States)

Cagle West, Marsha

2010-01-01

Software is a critical component of systems ranging from simple consumer appliances to complex health, nuclear, and flight control systems. The development of quality, reliable, and effective software solutions requires the incorporation of effective software engineering processes and leadership. Processes, approaches, and methodologies for…

Software efical para la gestión eficiente de motores en la industria; Software Efical for Efficient Management of Motors in the Industry

Directory of Open Access Journals (Sweden)

Elías V de la Rosa Masdueño

2011-02-01

Full Text Available En este trabajo se explica el diseño, e implementación de una herramienta capaz de controlar y gestionareficientemente los motores eléctricos de una industria. Para ello se elaboró un software de fácil manejoque resolviera el problema y que además brindara otras opciones a los usuarios que hicieran uso delmismo. EFICAL®, controla el inventario de los motores y sus equipos accionados, sus parámetrosnominales, mantenimientos y ensayos, permite calcular la eficiencia por distintos métodos y brinda ademásdatos de catálogos de diversos fabricantes.  This work explains the developing and application of a software tool for efficient management of electricmotors in the industry. For this it was develop friendly software that solve the problem and more over givesanother option to users. EFICAL®, controls the motor inventory and the equipment that they drive, theirnominal parameters, maintenance, and testing; also allow the efficiency calculations by various methodsand gives the catalog data of some manufacturers.

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

International Nuclear Information System (INIS)

KOCH, M.R.

1999-01-01

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

A Method to Improve the Software Acceptance Criteria for Nuclear Power Plants

International Nuclear Information System (INIS)

Suh, Yong Suk; Park, Heui Youn; Son, Ki Sung; Lee, Ki Hyun; Kim, Hyeon Soo

2005-01-01

The license is a mandatory process required by a governmental authority and the certification is a voluntary process administrated by a professional community. A software certification is a result of an assessment that the certified software conforms to required criteria or standards. The certification is used as a committed promise to produce a high quality software, so software acquirers are requiring it from their suppliers. For example, US DoD (Department of Defense) requires an achievement of CMMI-SW (Capability Maturity Model Integration-Software) certification for participating in a major military software project. It is commonly said that the purpose of achieving a certification is to improve the product quality. In the nuclear area, a software certification has been rarely concerned with or required for the software used in a safety function of NPPs (Nuclear Power Plants). The safety critical software for NPPs is accepted by the nuclear regulators when the following three criteria are met: acceptable plans should be prepared to control the software development activities, the plans should be followed in an acceptable software life cycle, and the process should produce acceptable design outputs. The acceptance criteria are so abstractive that the nuclear regulators may assess the software development plans, activities, outputs based on their subjective engineering judgments. This is inevitable because a software has invisible or intangible characteristics. It is hard to assess the totality of a software prior to running it. These have caused the judgments to be biased. The regulators may want some objectiveness in assessing how much capability for software development the supplier possesses. In that case, the software certification can assist them for such an assessment. This paper proposes a method to improve the software acceptance criteria by applying the software certification to the criteria. This will assist the regulators to assess the supplier

Reseña del Software Disponible en Colombia Para la Gestión de Inventarios en Cadenas de Abastecimiento

Directory of Open Access Journals (Sweden)

Valentina Gutiérrez

2009-01-01

Full Text Available La gestión de los diferentes tipos de inventario a lo largo de una cadena de abastecimiento es un problema complejo que, en la mayoría de los casos de la industria colombiana e internacional, se aborda mediante la implementación de herramientas de software. Sin embargo, la decisión de implementar dichas herramientas está en muchos casos limitada por la capacidad financiera para invertir en ellas y por el desconocimiento de la oferta de software disponible en Colombia. Este artículo presenta una reseña del software disponible en Colombia para la gestión de inventarios con el fin de brindar a las empresas que se enfrentan a la decisión de implementar un software, una herramienta de soporte que indique cuál es la oferta en Colombia y cuáles son las características de los sistemas disponibles. Para esto se presenta primero el estado del arte, en el cual se identifica el resultado de la revisión de la literatura y el uso de las herramientas de software en la industria colombiana. Seguidamente se presenta la caracterización de los productos de software disponibles en el país. Dicha caracterización permite identificar la configuración general de los productos, los módulos de gestión con los que cuenta, las opciones de integración con otras herramientas informáticas, y la información general de precios e instalación. Finalmente se presentan las conclusiones del estudio y las futuras oportunidades de investigación.

OCRWM procedure for reporting software baseline change information

International Nuclear Information System (INIS)

1994-07-01

The purpose of this procedure is to establish a requirement and method for participant organizations to report software baseline change information to the M ampersand O Configuration Management (CM) organization for inclusion in the OCRWM Configuration Information System (CIS). (The requirements for performing software configuration management (SCM) are found in the OCRWM Quality Assurance Requirements and Description (QARD) document and in applicable DOE orders, and not in this procedure.) This procedure provides a linkage between each participant's SCM system and the CIS, which may be accessed for identification, descriptive, and contact information pertaining to software released by a participant. Such information from the CIS will enable retrieval of details and copies of software code and documentation from the participant SCM system

Improving Software Systems By Flow Control Analysis

Directory of Open Access Journals (Sweden)

Piotr Poznanski

2012-01-01

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

Ten recommendations for software engineering in research.

Science.gov (United States)

Hastings, Janna; Haug, Kenneth; Steinbeck, Christoph

2014-01-01

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

Online Rule Generation Software Process Model

OpenAIRE

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

Software Reviews.

Science.gov (United States)

Kinnaman, Daniel E.; And Others

1988-01-01

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

Software as a Service - Common Service Bus (SAAS-CSB)

OpenAIRE

Swaminathan, R.; Karnavel, K.

2013-01-01

Software-as-a-Service (SaaS) is a form of cloud computing that relieves the user from the concern of hardware, software installation and management. It is an emerging business model that delivers software applications to the users through Web-based technology. Software vendors have varying requirements and SaaS applications most typically support such requirements. The various applications used by unique customers in a single instance are known as Multi-Tenancy. There would be a delay in serv...

Software para Controle de Temperatura em Estufas

OpenAIRE

Silva, Antonio Carlos Alves; Universidade Federal de Lavras; Kanazawa, Edna Mie; Universidade Federal de Lavras; de Carvalho, Karina Dutra; Universidade Federal de Lavras; Kinoshita, Vanessa Godoy; Universidade Federal de Lavras; Uchoa, Joaquim Quinteiro; Universidade Federal de Lavras; Lacerda, Wilian Soares; Universidade Federal de Lavras; Schneider, Bruno de Oliveira; Universidade Federal de Lavras

2004-01-01

Neste trabalho é apresentado o projeto desenvolvido para controle de temperatura em estufas, denominado CTE, utilizando uma Interface de Aquisição e Controle de Dados. Todo o controle é feito via software, onde pode-se optar por dois tipos de controle: o controle automático, onde é possível definir-se a temperatura mínima e máxima; ou o controle manual, onde o usuário poderá optar por acionar periféricos de aquecimento, resfriamento e desligamento da estufa. Foi desenvolvida também uma interf...

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

International Nuclear Information System (INIS)

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

PSPVDC: Una Propuesta que Incorpora el Diseño por Contrato Verificado al Personal Software Process

Directory of Open Access Journals (Sweden)

Silvana Moreno

2013-10-01

Full Text Available El desarrollo de software se ha vuelto una actividad muy importante en el mundo actual. Existen números procesos de desarrollo de software que buscan aumentar la calidad de los productos y disminuir los tiempos de salida al mercado. Sin embargo, el software contiene defectos y éstos causan fallas potencialmente graves durante su ejecución. Este trabajo propone un nuevo proceso de desarrollo de software denominado PSPVDC que combina el enfoque del Personal Software Process (PSP y del Diseño por Contrato Verificado (VDbC con el objetivo de mejorar la calidad de los productos con respecto al PSP. Además se presenta una revisión sistemática de la literatura que busca conocer las adaptaciones al PSP que hayan sido documentadas, en particular aquellas que incorporan métodos formales.

Software process in Geant4

International Nuclear Information System (INIS)

Cosmo, G.

2001-01-01

Since its erliest years of R and D, the GEANT4 simulation toolkit has been developed following software process standards which dictated the overall evolution of the project. The complexity of the software involved, the wide areas of application of the software product, the huge amount of code and Category complexity, the size and distributed nature of the Collaboration itself are all ingredients which involve and correlate together a wide variety of software processes. Although in 'production' and available to the public since December 1998, the GEANT4 software product includes Category Domains which are still under active development. Therefore they require different treatment also in terms of improvement of the development cycle, system testing and user support. The author is meant to describe some of the software processes as they are applied in GEANT4 for both development, testing and maintenance of the software

Comunidades de software libre en Argentina: motivaciones, participación, militancia

Directory of Open Access Journals (Sweden)

Agustín Zanotti

2014-12-01

Full Text Available El artículo retoma indagaciones sobre comunidades de software libre en Argentina para analizar sus formas de participación y militancia. Nos enfocamos en las motivaciones que convocan a los miembros de comunidades y proyectos, las cuales se asocian a las potencialidades tanto técnicas como sociales del modelo libre de producción de software. El análisis nos lleva a comprender que las formas de solidaridad al interior de estos grupos se encuentran inescindiblemente unidas a una búsqueda personal y a necesidades cotidianas de sus participantes. Las comunidades generan y distribuyen capitales o recursos de manera retributiva, en función de sus contribuciones y aportes. Sobre la base de ciertas identidades geeks/hackers ligadas a estos entusiastas informáticos, tales espacios fortalecen vínculos, relaciones de pertenencia y experiencias compartidas. Junto con ello se van construyendo definiciones éticas y políticas en relación al software y los diferentes temas que hacen a la agenda local de los colectivos.El texto abre la discusión sobre las formas de militancia que existen detrás de estos colectivos y la construcción del software libre como un objeto político. Inscribimos de este modo el debate en una reflexión más amplia sobre la acción colectiva y los movimientos sociales contemporáneos.

Tool-based requirement traceability between requirement and design artifacts

CERN Document Server

Turban, Bernhard

2013-01-01

Processes for developing safety-critical systems impose special demands on ensuring requirements traceability. Achieving valuable traceability information, however, is especially difficult concerning the transition from requirements to design. Bernhard Turban analyzes systems and software engineering theories cross-cutting the issue (embedded systems development, systems engineering, software engineering, requirements engineering and management, design theory and processes for safety-critical systems). As a solution, the author proposes a new tool approach to support designers in their thinkin

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

International Nuclear Information System (INIS)

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

Contribuição dos modelos de qualidade e maturidade na melhoria dos processos de software Contribution of quality and maturity models to software process improvement

Directory of Open Access Journals (Sweden)

Antonio Carlos Tonini

2008-01-01

Full Text Available Grande parte das empresas desenvolvedoras de software criou seu próprio processo de trabalho. Devido à rápida expansão do mercado de software, a concorrência ocorre muito mais em custo do que em diferenciação. Para obter vantagem competitiva, as empresas devem atualizar-se continuamente na tecnologia, buscar a maturidade nos processos e eliminar a ineficiência operacional. Isso requer um envolvimento das pessoas, dos processos e da organização como um todo. O artigo discute a implementação de melhorias nos processos de software segundo os principais modelos de qualidade e de maturidade. Com base em um Estudo de Casos Múltiplos, verifica-se que a melhoria dos processos de software requer que a melhoria ocorra primeiramente entre cada um dos desenvolvedores e, a seguir, envolva os grupos de desenvolvimento e por fim, a organização como um todo. A pesquisa conclui que os modelos de qualidade e maturidade servem como orientadores do processo de melhoria.Many software development companies have developed their own work method. Due to the fast software market growth, the competition focuses more on cost than on differentiation. To achieve competitive advantage, software developer organizations must continually update their technology, reach high level process maturity and eliminate all the operational inefficiency. These procedures involve people, processes and the whole organization. The aim of the paper is to discuss software process improvement implementation according to the most important quality and maturity models. Based on a Multiple Case Study, it is verified that the software process improvement needs firstly individual improvement and, later, it involves the developer teams and the whole organization. The research concludes that the quality and maturity models must be used as improvement process drivers.

The dynamics of software development project management: An integrative systems dynamic perspective

Science.gov (United States)

Vandervelde, W. E.; Abdel-Hamid, T.

1984-01-01

Rather than continuing to focus on software development projects per se, the system dynamics modeling approach outlined is extended to investigate a broader set of issues pertaining to the software development organization. Rather than trace the life cycle(s) of one or more software projects, the focus is on the operations of a software development department as a continuous stream of software products are developed, placed into operation, and maintained. A number of research questions are ""ripe'' for investigating including: (1) the efficacy of different organizational structures in different software development environments, (2) personnel turnover, (3) impact of management approaches such as management by objectives, and (4) the organizational/environmental determinants of productivity.

An Interoperability Framework and Capability Profiling for Manufacturing Software

Science.gov (United States)

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.

Advanced information processing system: Input/output network management software

Science.gov (United States)

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.

Cost estimation in software engineering projects with web components development

Directory of Open Access Journals (Sweden)

Javier de Andrés

2015-01-01

Full Text Available Existen multitud de modelos propuestos para la predicción de co stes en proyectos de software, al gunos orientados específicamen te para proyectos Web. Este trabajo analiza si los modelos específicos para proyectos Web están justifi cados, examinando el comportami ento diferencial de los costes entre proyectos de desarrollo softwar e Web y no Web. Se analizan dos aspectos del cálculo de costes: las deseconomías de escala, y el im pacto de algunas características de estos proyectos que son utilizadas como cost drivers. Se en uncian dos hipótesis: (a en estos proyect os las deseconomías de escala so n mayores y (b el incremento de coste que provocan los cost dr ivers es menor para los proyectos Web. Se contrastaron estas hipótesis a nalizando un conjunto de proyectos reales. Los resultados sugie ren que ambas hipótesis se cumplen. Por lo tanto, la principal contribu ción a la literatura de esta inv estigación es que el desarrollo de modelos específicos para los proyectos Web está justificado.

METODOLOGÍA PARA IMPLANTAR UN SISTEMA DE GESTIÓN DE LA CALIDAD EN UNA EMPRESA PRODUCTORA DE SOFTWARE

Directory of Open Access Journals (Sweden)

Mercedes Delgado Fernández

2002-10-01

Full Text Available

A mediado de los 80, los procesos de desarrollo y mantenimiento del software eran con frecuencia imprevisibles y la garantía de funcionamiento y calidad del software desiguales. En general, los problemas principales presentados por los productos software: entrega tardía, costo elevado, imperfecciones, poco fiables, parecen en gran parte, debido a problemas de proceso. Es precisamente por esto que en las empresas del país se trabaja hoy en día en sistemas que ayuden a mejorar la productividad, la eficiencia y la calidad de los productos software. En este artículo se parte de un estudio de los principales conceptos de la gestión de la calidad y su aplicación en la producción de software, y se propone una metodología para diseñar un sistema de gestión de la calidad en las empresas productoras de software, basado en las normas ISO 9000, el modelo de madurez de las capacidades, y el modelo europeo de calidad total.

Sistema de software de adquisición y procesado de EEG mediante MATLAB

OpenAIRE

Pérez‐Muelas Noguera, Alberto

2017-01-01

Extraer conocimiento de las señales de electroencefalograma (EEG) se ha convertido en un importante área de investigación de la ingeniería biomédica. A sus aplicaciones iniciales de diagnosis médica, hoy día, se le suman numerosos esfuerzos, para desarrollar aplicaciones que permitan a los usuarios controlar dispositivos externos, únicamente con su actividad cerebral. Este proyecto se plantea, para desarrollar un software de procesado en tiempo real de señales EEG, desarrollado...

[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"].

Science.gov (United States)

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.

Metodologías para desarrollar software seguro

Directory of Open Access Journals (Sweden)

Carlos Joaquín Brito Abundis

2013-12-01

Full Text Available La seguridad ha pasado de ser un requerimiento no funcional, que podía implementarse como parte de la calidad del software a un elemento primordial de cualquier aplicación. Los hackers y grupos criminales evolucionan día a día y se han convertido expertos en explotar las vulnerabilidades de las aplicaciones y sitios en internet. Para hacer frente a estas amenazas, es necesaria la implementación de metodologías que contemplen en su proceso de desarrollo de software la eliminación de vulnerabilidades y la inclusión de la seguridad como un elemento básico en la arquitectura de cualquier producto de software. Este trabajo revisa algunas de las metodologías que contemplan la seguridad en su proceso.

Agile Software Development in the Department of Defense Environment

Science.gov (United States)

2017-03-31

traditional project/program life cycle (i.e., waterfall ). In the traditional model , security requirements are not evaluated until development is...2015), which may better facilitate adoption of Agile software development in the DoD. Several models are provided for software-dominant and software...the DoD has historically used a traditional, waterfall approach for acquiring systems and services), and oversight requirements that are

Modular Software Performance Monitoring

CERN Document Server

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

A Component-Oriented Programming for Embedded Mobile Robot Software