A Utilização da Astronomia como Tema Interdisciplinar e Aplicações de Objetos de Aprendizagem

NASA Astrophysics Data System (ADS)

da Silva, L. A.; Voelzke, M. R.

2008-09-01

Este trabalho visa analisar a possibilidade de relacionar conteúdos aplicados no ensino fundamental e médio de forma interdisciplinar por intermédio da astronomia, com a intervenção de objetos de aprendizagem que possam integrar as disciplinas e a utilização de recursos tecnológicos. Em uma pesquisa prévia com 20 professores de uma escola estadual situada na cidade de Guarulhos foi observado que apenas 25% dos professores utilizam algum recurso tecnológico para o desenvolvimento de conteúdos pertinentes à sua disciplina, tais como sites e softwares educativos, sendo que a maioria absoluta continua ensinando apenas com livros didáticos. A maior parte dos professores apresenta dificuldades em trabalhar sua disciplina de forma interdisciplinar, ou seja, 75% dos professores preferem aplicar os conteúdos seguindo uma hierarquia linear de tópicos, evitando a discussão de temas que de alguma forma estão relacionados. A astronomia pode vir à fascinar o ser humano e despertar sua curiosidade promovendo um maior interesse no aprendizado, podendo favorecer análises interdisciplinares de forma lógica e objetiva, desta forma colocar a astronomia como tema motivador interdisciplinar, pode ser relevante no que se refere ao distanciamento da fragmentação dos conteúdos. No Estado de São Paulo, a implantação da proposta curricular no ensino fundamental e médio mostra claramente a inserção da astronomia na maior parte das séries, principalmente na 6ª série em que todo o bimestre se fala de astronomia.

NETTAB 2012 on "Integrated Bio-Search"

PubMed Central

2014-01-01

The NETTAB 2012 workshop, held in Como on November 14-16, 2012, was devoted to "Integrated Bio-Search", that is to technologies, methods, architectures, systems and applications for searching, retrieving, integrating and analyzing data, information, and knowledge with the aim of answering complex bio-medical-molecular questions, i.e. some of the most challenging issues in bioinformatics today. It brought together about 80 researchers working in the field of Bioinformatics, Computational Biology, Biology, Computer Science and Engineering. More than 50 scientific contributions, including keynote and tutorial talks, oral communications, posters and software demonstrations, were presented at the workshop. This preface provides a brief overview of the workshop and shortly introduces the peer-reviewed manuscripts that were accepted for publication in this Supplement. PMID:24564635

Implementação de um algoritmo para a limpeza de mapas da RCFM

NASA Astrophysics Data System (ADS)

Souza, C. L.; Wuensche, C. A.

2003-08-01

A Radiação Cósmica de Fundo em Microondas (RCFM), descoberta por Penzias e Wilson em 1965, é uma das ferramentas mais poderosas para o estudo da cosmologia. Com a descoberta de flutuações de temperatura na RCFM, da ordem de uma parte em 105, pelo COBE (1992), uma nova era teve início. Nos últimos onze anos, diversos instrumentos fizeram novas medidas de alta precisão, refinando os resultados apresentados pelo COBE, culminando com os resultados recentes do satélite WMAP. A análise de dados da RCFM, especialmente no caso de experimentos com pequena cobertura do céu, apresenta uma série de dificuldades devido a emissões de contaminantes externos, tais como a emissão da Galáxia e de fontes pontuais, e de ruídos intrínsecos tanto ao sistema de detecção quanto à estratégia de observação do céu. Uma das soluções típicas para a filtragem de dados brutos de um experimento para medir flutuações de temperatura é aplicar um gabarito (template) e um filtro passa alta ao produzir mapas simplificados (sem considerar matrizes de correlação ou covariância). No caso de experimentos que utilizam detectores HEMT, essa combinação de filtros remove, satisfatoriamente, ruídos do tipo 1/f gerados pela instabilidade no ganho do detector acoplado ao movimento do instrumento, definido pela estratégia de observação. Entretanto, o sinal resultante medido, tanto em simulações quanto em séries temporais reais, sugere que parte do sinal cosmológico pode estar sendo removido junto com o ruído dos detectores. Este trabalho descreve as etapas para a produção de um mapa típico (simulado) e os testes preliminares de um algoritmo para remover ruídos do tipo 1/f introduzidos pela estratégia de observação sem prejudicar a qualidade do sinal cosmológico presente no mapa.

Projeto educação em ciências com observatórios virtuais: a participação da Escola Moppe no período 2000-2003

NASA Astrophysics Data System (ADS)

Wuensche, C. A.; Gavioli, E.; Oliveira, A. L. P. R. S.; da Silva, C.; Cardoso, H. P.; Estácio, S.

2003-08-01

O projeto Educação em Ciências com Observatórios Virtuais foi concebido pelo Instituto Astronômico e Geofísico da USP, agregando diversas instituições de ensino e pesquisa no país para desenvolver competências diversas na educação fundamental, média e superior utilizando a astronomia como ferramenta multidisciplinar. Este trabalho descreve a participação da MOPPE, escola-piloto do INPE no projeto, no período de 2000-2003. Serão apresentadas 1) a criação de um clube de ciências (1999 a 2001) cujo tema foi a colonização de Marte e 2) a ementa de astronomia trabalhada com as 7a. e 8a. séries do ensino fundamental. A proposta do projeto Colonizando Marte foi estudar diversos aspectos de uma missão interplanetária e construir experiementos que permitissem quantificar esses aspectos. Os resultados obtidos incluiram apresentações nas SBPC Jovem em 2000 e 2001. Discutiremos também as ementas de astronomia trabalhadas desde 2001 e o envolvimento dos alunos com atividades ligadas a astronomia, fora da aula de ciências. A inclusão de astronomia no currículo das últimas séries motivou a participação de mais alunos culminando com a conquista de duas medalhas para alunos da 7a. série na Olimpiada Brasileira de Astronomia em 2002. Houve também um aumento no número de participantes na OBA 2003 e nos projetos de astronomia mais elaborados nas Feira de Ciências de 2001 e 2002. Destacamos em 2003 a inclusão da MOPPE no projeto TIE - Telescopes in Education - da NASA, que utiliza o telescópio do Observatório de Mount Wilson (EUA) para observações remotas em projetos pedagógicos para o ensino de astronomia.

Telemedicine: challenges to dissemination in Brazil.

PubMed

Maldonado, Jose Manuel Santos de Varge; Marques, Alexandre Barbosa; Cruz, Antonio

2016-11-03

Telemedicine has been seen as an important tool for facing the challenges of universal health systems. The goal of this article is to discuss the main challenges to its full dissemination in Brazil. Being a somewhat new area, there are not many scientific papers that systematize it. This article is an exploratory paper, as it aims to provide an overall perspective on the subject. From an economic point of view, telemedicine is a strategic area due to its an intrinsic potential of being a source for generating innovation, for requiring and incorporating technological breakthroughs from other areas, and for its interdisciplinary nature and dynamic inter-relations that drive different industries. From the social perspective, it has the potential to make access to health services democratic, by connecting remote regions with health services located in hospitals and centers of reference for prevention, diagnosis and treatment. Resumo: A telemedicina está sendo vista como uma ferramenta importante para enfrentar os desafios dos sistemas de saúde universais. O objetivo deste artigo foi discutir os principais desafios para a sua plena disseminação no Brasil. Em função do caráter relativamente emergente desta área, existe uma escassez relativa de trabalhos científicos que a sistematizem. Por isso, este artigo se enquadra na categoria de trabalho exploratório, já que tem por objetivo proporcionar uma visão geral sobre o tema. Destaca-se, que do ponto de vista econômico, a telemedicina se constitui em uma área estratégica por seu potencial intrínseco de ser fonte geradora de inovações, por demandar e incorporar avanços tecnológicos oriundos de outras áreas e, em função da sua natureza interdisciplinar e de suas inter-relações dinâmicas, pela possibilidade de impulsionar diferentes indústrias. Do ponto de vista social, tem o potencial de democratizar o acesso aos serviços de saúde, integrando regiões remotas com serviços de saúde localizados em hospitais e centros de referência no que se refere à prevenção, diagnóstico e tratamento.

Evolução química de galáxias HII anãs

NASA Astrophysics Data System (ADS)

Ferraresi, M., Jr.; Cuisinier, F.; Telles, E.

2003-08-01

Galáxias HII anãs são galáxias de baixa massa, com alto conteúdo de gás, e se encontram em uma fase intensa de formação estelar. A taxa de formação estelar está tão alta nestas galáxias que não pode ter se mantido durante sua vida inteira. O tempo máximo de duração do episódio atual de formação estelar deve ser no máximo de algumas dezenas de milhões de anos, bem inferior à idade destas galáxias. Isto leva naturalmente a idéia de que já aconteceram surtos anteriores. Abundâncias químicas oferecem uma ferramenta poderosa para investigar a história evolutiva destas galáxias, porque aumentam de geração em geração estelar. O hidrogênio, o oxigênio, o nitrogênio produzem algumas das linhas mais importantes em um gás foto-ionizado, permitindo a determinação das abundâncias destes elementos facilmente. A dispersão das abundâncias em oxigênio e nitrogênio é significativa, sendo maior que os erros observacionais. O oxigênio é produzido em estrelas massivas, que explodem quase instâneamente, enquanto o nitrogênio é produzido em estrelas de massa intermediária, que só o liberam depois de um atraso de @ 500 mihões de anos. Construímos um modelo de evolução química semi-analítico, utilizando rendimentos empíricos baseados nas abundâncias observadas destes dois elementos. Conseguimos através deste modelo rudimentar explicar nas galáxias de mais baixas metalicidades as abundâncias de oxigênio e de nitrogênio, assim como a dispersão dos dados observacionais devida a formação estelar descontínua, e isto com um número baixo de surtos (1 ou 2, no máximo 3).

Prevention of chronic complications of diabetes mellitus according to complexity.

PubMed

Salci, Maria Aparecida; Meirelles, Betina Hörner Schlindwein; Silva, Denise Maria Vieira Guerreiro da

2017-01-01

To assess the prevention by primary health care providers of chronic complications of diabetes mellitus according to the complex thinking theoretical approach. Evaluative research based on the complex thinking theoretical approach. The following techniques for data collection were used: interviews with 38 participants; observation in collective and individual appointments; and analysis of medical records of people with diabetes. The triangulation applied for data analysis was the ATLAS.ti software. The prevention and management of chronic complications of diabetes did not meet the requirements set forth by ministerial public policies aimed at this population. Systematic monitoring to prevention of chronic complications showed significant gaps. Primary health care did not consider preventive actions for diabetes mellitus complications. This context was marked by disjunctive, fragmented, and dissociated practices types of care targeted to the totality of the assisted people. Avaliar a prevenção de complicações crônicas do diabetes mellitus a luz do referencial teórico do Pensamento Complexo por integrantes da atenção primária à saúde. Pesquisa avaliativa, que teve como referencial teórico o Pensamento Complexo. Como técnicas de coleta de dados foram utilizadas: entrevista com 38 participantes; observação nos atendimentos coletivos e individuais;e análise em 25 prontuários de pessoas com diabetes. A triangulação subsidiou a análise de dados que teve auxílio do software ATLAS.ti. A prevenção e o manejo das complicações crônicas do diabetes não atendiam ao estabelecido nas políticas públicas ministeriais destinadas a esse público. O acompanhamento sistematizado para controle da prevenção das complicações crônicas apresentou importantes lacunas. A assistência na atenção primária não contemplava ações de prevenção de complicação do diabetes mellitus. Esse contexto era por marcado por práticas disjuntivas, fragmentadas e dissociadas de uma assistência que visa a totalidade das pessoas assistidas.

BSSDATA - um programa otimizado para filtragem de dados em radioastronomia solar

NASA Astrophysics Data System (ADS)

Martinon, A. R. F.; Sawant, H. S.; Fernandes, F. C. R.; Stephany, S.; Preto, A. J.; Dobrowolski, K. M.

2003-08-01

A partir de 1998, entrou em operação regular no INPE, em São José dos Campos, o Brazilian Solar Spectroscope (BSS). O BSS é dedicado às observações de explosões solares decimétricas com alta resolução temporal e espectral, com a principal finalidade de investigar fenômenos associados com a liberação de energia dos "flares" solares. Entre os anos de 1999 e 2002, foram catalogadas, aproximadamente 340 explosões solares classificadas em 8 tipos distintos, de acordo com suas características morfológicas. Na análise detalhada de cada tipo, ou grupo, de explosões solares deve-se considerar a variação do fluxo do sol calmo ("background"), em função da freqüência e a variação temporal, além da complexidade das explosões e estruturas finas registradas superpostas ao fundo variável. Com o intuito de realizar tal análise foi desenvolvido o programa BSSData. Este programa, desenvolvido em linguagem C++, é constituído de várias ferramentas que auxiliam no tratamento e análise dos dados registrados pelo BSS. Neste trabalho iremos abordar as ferramentas referentes à filtragem do ruído de fundo. As rotinas do BSSData para filtragem de ruído foram testadas nos diversos grupos de explosões solares ("dots", "fibra", "lace", "patch", "spikes", "tipo III" e "zebra") alcançando um bom resultado na diminuição do ruído de fundo e obtendo, em conseqüência, dados onde o sinal torna-se mais homogêneo ressaltando as áreas onde existem explosões solares e tornando mais precisas as determinações dos parâmetros observacionais de cada explosão. Estes resultados serão apresentados e discutidos.

Confidence Intervals for Omega Coefficient: Proposal for Calculus.

PubMed

Ventura-León, José Luis

2018-01-01

La confiabilidad es entendida como una propiedad métrica de las puntuaciones de un instrumento de medida. Recientemente se viene utilizando el coeficiente omega (ω) para la estimación de la confiabilidad. No obstante, la medición nunca es exacta por la influencia del error aleatorio, por esa razón es necesario calcular y reportar el intervalo de confianza (IC) que permite encontrar en valor verdadero en un rango de medida. En ese contexto, el artículo plantea una forma de estimar el IC mediante el método de bootstrap para facilitar este procedimiento se brindan códigos de R (un software de acceso libre) para que puedan realizarse los cálculos de una forma amigable. Se espera que el artículo sirva de ayuda a los investigadores de ámbito de salud.

TECHNOLOGICAL INFORMATION REGARDING PREBIOTICS AND PROBIOTICS NUTRITION VERSUS THE PATENT REGISTERS: WHAT IS NEW?

PubMed

Reis, José Maciel Caldas Dos; Pinheiro, Maurício Fortuna; Oti, André Takashi; Feitosa-Junior, Denilson José Silva; Pantoja, Mauro de Souza; Barros, Rui Sérgio Monteiro

2016-01-01

Food is a key factor both in prevention and in promoting human health. Among the functional food are highlighted probiotics and prebiotics. Patent databases are the main source of technological information about innovation worldwide, providing extensive library for research sector. Perform mapping in the main patent databases about pre and probiotics, seeking relevant information regarding the use of biotechnology, nanotechnology and genetic engineering in the production of these foods. Electronic consultation was conducted (online) in the main public databases of patents in Brazil (INPI), United States (USPTO) and the European Patent Bank (EPO). The research involved the period from January 2014 to July 2015, being used in the title fields and summary of patents, the following descriptors in INPI "prebiotic", "prebiotic" "probiotics", "probiotic" and the USPTO and EPO: "prebiotic", "prebiotics", "probiotic", "probiotics". This search haven't found any deposit at the brazilian patents website (INPI) in this period; US Patent &Trademark Office had registered 60 titles in patents and the European Patent Office (EPO) showed 10 documents on the issue. Information technology offered by genetic engineering, biotechnology and nanotechnology deposited in the form of titles and abstracts of patents in relation to early nutritional intervention as functional foods, has increasingly required to decrease the risks and control the progression of health problems. But, the existing summaries, although attractive and promising in this sense, are still incipient to recommend them safely as a therapeutic tool. Therefore, they should be seen more as diet elements and healthy lifestyles. A alimentação é fator primordial tanto na prevenção quanto na promoção para a saúde humana. Dentre os alimentos funcionais destacam-se os probióticos e prebióticos. Os bancos de dados de patentes representam a maior fonte de informação tecnológica acerca de inovação em nível mundial, provendo vasta biblioteca para o setor de pesquisa. Realizar mapeamento nas principais bases de dados de patentes relacionada aos pré e probióticos buscando informações relevantes com relação ao uso da biotecnologia, nanotecnologia e engenharia genética na produção desses alimentos. Foi realizada consulta eletrônica (online) nas principais bases de dados públicas de patentes do Brasil (INPI), Estados Unidos da América (USPTO) e o Banco de Patentes Europeu (EPO). A pesquisa envolveu o período de janeiro de 2014 a julho 2015, sendo utilizado nos campos de título e resumo das patentes, os seguintes descritores no INPI: "prebiótico", "prebióticos" "probiótico", "probióticos" e no USPTO e EPO: "prebiotic", "prebiotics", "probiotic", "probiotics". Não foram observados, no INPI, depósitos de residentes (empresas ou universidades). Já no USPTO foram detectados 60 depósitos e no EPO 10 títulos de interesse à pesquisa. A tecnologia da informação ofertada pela engenharia genética, biotecnologia e nanotecnologia depositada na forma de títulos e resumos das patentes em relação à intervenção nutricional precoce como alimentos funcionais, tem cada vez mais pretendido diminuir os riscos e controlar a progressão de agravos à saúde. Mas, os resumos existentes, embora atraentes e promissores neste sentido, ainda são incipientes para recomendá-los de forma segura como ferramenta terapêutica. Portanto, devem ser encarados mais como integrantes de dieta e estilos de vida saudáveis.

Development of the TabacoQuest app for computerization of data collection on smoking in psychiatric nursing.

PubMed

Oliveira, Renata Marques de; Duarte, Alexandre Freitas; Alves, Domingos; Furegato, Antonia Regina Ferreira

2016-08-29

to develop a mobile app for research on the use of tobacco among psychiatric patients and the general population. applied research with the technological development of an app for data collection on an Android tablet. For its development, we considered three criteria: data security, benefits for participants and optimization of the time of researchers. We performed tests with twenty fictitious participants and a final test with six pilots. the app collects data, stores them in the database of the tablet and export then to an Excel spreadsheet. calculator, stopwatch, offline operation, branching logic, field validation and automatic tabulation. the app prevents human error, increases the quality of the data by validating them during the interview, allows the performing of automatic tabulation and makes the interviews less tiring. Its success may encourage the use of this and other computational resources by nurses as a research tool. desenvolver aplicativo mobile para pesquisa sobre o uso de tabaco entre pacientes psiquiátricos e a população geral. pesquisa aplicada com o desenvolvimento tecnológico de um aplicativo para coleta de dados em tablet Android. Para seu desenvolvimento, consideraram-se três critérios: segurança dos dados, benefícios para os participantes e otimização do tempo dos pesquisadores. Testes com 20 participantes fictícios e teste final com seis pilotos. o aplicativo coleta os dados, armazena-os no banco de dados do tablet e os exporta para planilha Excel. Recursos: calculadora; cronômetro; funcionamento off-line, lógica de ramificação, validação de campos e tabulação automática. o aplicativo previne erros humanos e aumenta a qualidade dos dados ao validá-los durante a entrevista, permite realizar tabulação automática e torna as entrevistas menos cansativas. Seu sucesso poderá incentivar o uso desse e outros recursos computacionais pelos enfermeiros, como ferramenta de pesquisa. desarrollar aplicativo móvil para hacer investigación sobre el uso de tabaco entre pacientes psiquiátricos y la población en general. investigación aplicada con el desarrollo tecnológico de un aplicativo para recolección de datos en tablet Android. Para su desarrollo, se consideraron tres criterios: seguridad de los datos, beneficios para los participantes y optimización del tiempo de los investigadores. Se realizaron pruebas con 20 participantes ficticios y un test piloto final. los datos del aplicativo almacenados en el banco de datos del tablet son exportados para planilla Excel. Recursos: calculadora, cronómetro, funcionamiento off-line, lógica de ramificación, validación de campos y tabulación automática. el aplicativo evita errores humanos y aumenta la calidad de los datos al validarlos durante la entrevista, también permite realizar una tabulación automática y torna las entrevistas menos agotadoras. Su éxito incentivará su uso y el de otros recursos computacionales por parte de los enfermeros, como herramienta de investigación.

Off-label use of rhBMP-2 as bone regeneration strategies in mandibular ameloblastoma unicystic.

PubMed

Silva, Henrique Celestino Lima E; Cheim, Adonai Peixoto; Moreno, Roberto; Miranda, Sérgio Luis de

2017-01-01

Jawbone reconstruction after tumor resection is one of the most challenging clinical tasks for maxillofacial surgeons. Osteogenic, osteoinductive, osteoconductive and non-antigenic properties of autogenous bone place this bone as the gold standard for solving problems of bone availability. However, the need for a second surgical site to harvest the bone graft increases significantly both the cost and the morbidity associated with the reconstructive procedures. Bone grafting gained an important tool with the discovery of bone morphogenetic proteins in 1960. Benefit of obtaining functional and real bone matrix without need of second surgical site seems to be the great advantage of use bone morphogenetic proteins. This study analyzed the use of rhBMP-2 in unicystic ameloblastoma of the mandible, detailing its structure, mechanisms of cell signaling and biological efficacy, in addition to present possible advantages and disadvantages of clinical use of rhBMP-2 as bone regeneration strategy. RESUMO A reconstrução óssea dos maxilares após ressecções tumorais é uma das tarefas mais difíceis para o cirurgião maxilofacial. As propriedades osteogênicas, osteoindutoras, osteocondutoras e não antigênicas do osso autógeno o colocam como o padrão-ouro para a solução de problemas de disponibilidade óssea. Entretanto a coleta do enxerto ósseo necessita de um segundo sítio cirúrgico, aumentando significativamente o custo e a morbidade associados ao procedimento reconstrutivo. A enxertia óssea ganhou uma excelente ferramenta com a descoberta das proteínas ósseas morfogenéticas na década de 1960. O benefício da obtenção de matriz óssea verdadeira e funcional, sem a necessidade de um segundo sítio cirúrgico, parece ser a grande vantagem do uso das proteínas ósseas morfogenéticas. Neste contexto, o objetivo deste estudo foi analisar a utilização da rhBMP-2 na regeneração óssea de ameloblastoma mandibular unicístico, detalhando sua estrutura, seus mecanismos de sinalização celular e sua eficácia biológica, além de apresentar potenciais vantagens e desvantagens da utilização clínica das rhBMP-2, enquanto estratégia regenerativa.

Projeto observatórios virtuais: educação através de telescópios robóticos

NASA Astrophysics Data System (ADS)

Santana, P. H. S.; Shida, R. Y.

2003-08-01

O principal objetivo do projeto Observatórios Virtuais é o ensino na área de ciências através de atividades práticas desenvolvidas em colaboração entre instituições de pesquisa em astronomia e escolas de ensino médio e fundamental. Este ano deverá ser concluída a implantação do programa piloto de estudos, pesquisas e observação astronômica direta, com utilização em tempo real de telescópios robóticos, que assim funcionarão como "observatórios virtuais". O objetivo pedagógico das atividades práticas baseadas nas imagens atronômicas é desenvolver as habilidades e competências dos alunos no uso do método científico. Para isso, serão realizados projetos interdisciplinares, a partir de observações astronômicas, já que a astronomia é uma área interdisciplinar por excelência. Essas atividades terão níveis diferenciados de complexidade, que podem ser adequados aos vários graus do ensino e realidades regionais. Será dada ênfase ao desenvolvimento e aplicação em São Paulo, onde atua a equipe do IAG/USP. Como resultados apresentados no presente trabalho, temos a criação de um software em português para o processamento de imagens obtidas através de CCDs e a elaboração de material para as atividades educacionais relacionadas.

Establishing the Empirical Relationship Between Non-Science Majoring Undergraduate Learners' Spatial Thinking Skills and Their Conceptual Astronomy Knowledge. (Spanish Title: Estableciendo Una Relación Empírica Entre el Razonamiento Espacial de los Estudiantes de Graduación de Carreras no Científicas y su Conocimento Conceptual de la Astronomía.) Estabelecendo Uma Relação Empírica Entre o RacioCínio Espacial dos Estudantes de Graduação EM Carreiras Não Científicas e Seu Conhecimento Conceitual da Astronomia

NASA Astrophysics Data System (ADS)

Heyer, Inge; Slater, Stephanie J.; Slater, Timothy F.

2013-12-01

The astronomy education community has tacitly assumed that learning astronomy is a conceptual domain resting upon spatial thinking skills. As a first step to formally identify an empirical relationship, undergraduate students in a non-major introductory astronomy survey class at a mediumsized, Ph.D. granting, mid-western US university were given pre- and post-astronomy conceptual diagnostics and spatial reasoning diagnostics, Instruments used were the "Test Of Astronomy Standards" and "What Do You Know?" Using only fully matched data for analysis, our sample consisted of 86 undergraduate non-science majors. Students' normalized gains for astronomy surveys were low at .26 and .13 respectively. Students' spatial thinking was measured using an instrument designed specifically for this study. Correlations between the astronomy instruments' pre- to post-course gain scores and the spatial assessment instrument show moderate to strong relationships suggesting the relationship between spatial reasoning and astronomy ability can explain about 25% of the variation in student achievement. La comunidad de educación en astronomía ha supuesto de forma tácita que el aprendizaje de la astronomía consiste en un dominio conceptual fundamentado en el razonamiento espacial. Como un primer paso para identificar formalmente una relación empírica entre estas dos cosas, utilizamos como muestra los estudantes de graduación de carreras no científicas de un curso experimental en una universidad norteamericana del medioeste de porte mediano con programa de Doctorado em curso, en el cual estos estudiantes se sometieron a un diagnóstico de razonamiento espacial y conceptos astronómicos antes e después del mismo. Las herramientas utilizadas fueron el Test Of Astronomy Standards (TOAST) y el cuestionario What do you know? Utilizando solo los datos completamente consistentes para este análisis, nuestra muestra consistió en 86 estudantes de graduación. Las mejoras, depués de normalizadas, en el desempeño de los estudiantes en estos dos asuntos foram pequenas, 0.26 e 0.13 respectivamente. El razonamiento espacial de los estudiantes fue medido utilizando un instrumento específico desarrollado para este trabaljo. Las correlaciones entre los resultados de los tests astronómicos y este instrumento específico, antes y después del curso mostraron una relación entre moderada y fuerte, sugiriendo que la relación entre el razonamiento espacial y el conocimiento astronómico puede explicar hasta un 25% de la variación em el desempeño de los estudiantes. A comunidade da educação em astronomia tem suposto de forma implícita que o aprendizado da astronomia consiste em um domínio conceitual fundamentado no raciocínio espacial. Como um primeiro passo para identificar formalmente uma relação empírica entre estas duas coisas, utilizamos como amostra os estudantes de graduação de carreiras não científicas de um curso exploratório em uma universidade norte-americana do meio-oeste de médio porte com programa de Doutorado em andamento, onde estes estudantes foram submetidos a um diagnóstico de raciocino espacial e conceitos astronômicos antes e depois do mesmo. As ferramentas utilizadas foram o Test Of Astronomy Standards (TOAST) e o questionário What do you know? Utilizando somente dados completamente consistentes para esta análise, nossa amostra consistiu de 86 estudantes de graduação. As melhoras, depois de normalizadas, do desempenho dos estudantes nos dois quesitos foram pequenas, 0.26 e 0.13 respectivamente. O raciocínio espacial dos estudantes foi medido utilizando um instrumento específico desenhado para este trabalho. As correlações entre os resultados dos testes astronômicos e este instrumento específico antes e depois do curso mostraram uma relação entre moderada e forte, sugerindo que a relação entre o raciocínio espacial e o conhecimento astronômico pode explicar até um 25% na variação no desempenho dos estudantes.

Clinical and epidemiological aspects of cornea transplant patients of a reference hospital.

PubMed

Cruz, Giovanna Karinny Pereira; Azevedo, Isabelle Campos de; Carvalho, Diana Paula de Souza Rego Pinto; Vitor, Allyne Fortes; Santos, Viviane Euzébia Pereira; Ferreira, Marcos Antonio

2017-06-08

clinically characterizing cornea transplant patients and their distribution according to indicated and post-operative conditions of cornea transplantation, as well as estimating the average waiting time. a cross-sectional, descriptive and analytical study performed for all cornea transplants performed at a reference service (n=258). Data were analyzed using Statistical Package for the Social Sciences, version 20.0. the main indicator for cornea transplant was keratoconus. The mean waiting time for the transplant was approximately 5 months and 3 weeks for elective transplants and 9 days for urgent cases. An association between the type of corneal disorder with gender, age, previous surgery, eye classification, glaucoma and anterior graft failure were found. keratoconus was the main indicator for cornea transplant. Factors such as age, previous corneal graft failure (retransplantation), glaucoma, cases of surgeries prior to cornea transplant (especially cataract surgery) may be related to the onset corneal endothelium disorders. caracterizar clínicamente los pacientes trasplantados y su distribución, con descripción de las condiciones indicadoras y posoperatorias de los trasplantes de córneas, así como estimar el tiempo promedio en la fila de espera. estudio epidemiológico, transversal, descriptivo y analítico, realizado con todos los trasplantes de córnea realizados en un servicio de referencia (n=258). Los datos fueron analizados con el software Statistical Package for the Social Sciences, versión 20.0. la principal condición indicadora para el trasplante de córnea fue el queratocono. El tiempo promedio en fila de espera para realización del trasplante fue de aproximadamente 5 meses y tres semanas, para trasplantes electivos y de 9 días para los casos de urgencia. Existió asociación entre el tipo de disturbio de la córnea con: sexo, intervalo etario, cirugía previa, clasificación del ojo, glaucoma y rechazo del injerto anterior. el queratocono fue la principal condición indicadora para el trasplante de córnea. Factores como: edad; rechazo de injerto de córnea anterior (retrasplante); glaucoma; y casos de cirugías previas al trasplante de córnea, destacando la cirugía de catarata, pueden estar relacionados con el aparecimiento de disturbios de la córnea de tipo endotelial. caracterizar clinicamente os pacientes transplantados e sua distribuição com descrição das condições indicadoras e pós-operatórias dos transplantes de córneas, bem como estimar o tempo médio em fila de espera. estudo epidemiológico, transversal, descritivo e analítico, realizado com todos os transplantes de córnea realizados em um serviço de referência (n= 258). Os dados foram analisados com uso do software Statistical Package for the Social Sciences, versão 20.0. a principal condição indicadora para o transplante de córnea foi o ceratocone. O tempo médio em fila de espera para realização do transplante foi de aproximadamente 5 meses e três semanas para o transplantes eletivos e 9 dias para os casos de urgência. Existiu associação entre o tipo de distúrbio da córnea com sexo, faixa etária, cirurgia prévia, classificação do olho, glaucoma e falência do enxerto anterior. o ceratocone foi a principal condição indicadora para o transplante de córnea. Fatores como idade, falência de enxerto corneano anterior (retransplante), glaucoma, casos de cirurgias prévias ao transplante de córnea, com destaque para a cirurgia de catarata, podem estar relacionados com o aparecimento de distúrbios da córnea do tipo endotelial.

Telescópio de pequeno porte como suporte ao ensino em cidades com intensa poluição luminosa II

NASA Astrophysics Data System (ADS)

Pereira, P. C. R.; Santos-Júnior, J. M.; Cruz, W. S.

2003-08-01

Para a maioria dos estudantes, sua passagem pelo ensino formal fundamental envolve a transmissão de fatos que devem ser guardados para um exame, a habilidade para lembrar fórmulas e, eventualmente, a repetição de experimentos que devem produzir resultados exigidos pelo professor. O resultado deste modelo de ensino, ao longo dos anos, é conhecido por todos: desconhecimento e descontentamento, por parte dos estudantes, de temas relativos ao papel e aos processos da ciência. Acreditamos que a Astronomia, pelo seu caráter observacional, é uma das áreas do conhecimento que pode contribuir neste cenário. A Fundação Planetário da Cidade do Rio de Janeiro possui um telescópio Meade LX-200 (25cm) que, juntamente com as câmeras CCD ST-7E e ST8E, tem sido utilizado em projetos voltados aos estudantes do ensino médio desde o ano 2000. Tais projetos envolvem a condução de um projeto de pesquisa observacional num nível apropriado, e possibilitam o contato com técnicas e novas tecnologias: computador, software para manipulação de dados e gráficos, programas de tratamento e redução de dados, uso de equipamentos óptico-eletrônicos (telescópio e CCD), bem como o processo de aquisição de conhecimento. Dentro da proposta dos anos anteriores, priorizamos projetos de uma noite, ou seja, procuramos trabalhar com fenômenos que apresentem variabilidade com intervalo de recorrência relativamente curto. Em todos os casos, optamos pela fotometria diferencial, que tem se mostrado bastante eficiente para o céu luminoso como o da cidade do Rio de Janeiro. Neste painel, apresentamos alguns dos projetos desenvolvidos no último ano, com 25 estudantes. Apresentamos os resultados da observação da variável pulsante AI Vel (V = 6,6) e da variável cataclísmica FO Aqr (V = 13,5), e do monitoramento do trânsito da lua de Júpiter, Europa, ocorrido em 30 de abril de 2003. As curvas de luz produzidas para as primeiras estão concordantes com as da literatura, assim como os respectivos períodos encontrados (1h20min e 4h48min). No caso do FO Aqr, ficou evidente, também, a modulação decorrente da rotação da anã branca receptora (21min). O erro estimado é de 0,01 magnitude. Propomos uma maior utilização de telescópios de pequeno porte, como suporte ao ensino (médio e superior) em cidades com poluição luminosa. Escolas e Planetários seriam ambientes propícios para a localização do telescópio. Os critérios adotados na escolha dos objetos e o método observacional empregado são também apresentados.

Effects of H sub 2 S addition on the performance of fresh vs. used CoMo catalysts

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

Rankel, L.A.

1991-01-01

When a Co/Mo catalyst is used for processing vanadium-containing heavy oils, vanadium deposits on the catalyst. As the amount of vanadium on the CoMo catalyst increases, the catalytic effects of CoMo decline and the presence of vanadium starts to influence the hydroprocessing products. Model feeds have been used to explore the changes in the catalytic activity of CoMo, aged CoMo, and VS{sub x} on alumina. Desulfurization, denitrogenation, deoxygenation, aromatics hydrogenation, and metals removal were monitored. This paper reports that, upon the addition of hydrogen sulfide to hydrogen, improvements in the catalysts for aromatics hydrogenation, denitrogenation and metals removal were observed.

Dobutamine Stress Echocardiography Safety in Chagas Disease Patients.

PubMed

Rassi, Daniela do Carmo; Vieira, Marcelo Luiz Campos; Furtado, Rogerio Gomes; Turco, Fabio de Paula; Melato, Luciano Henrique; Hotta, Viviane Tiemi; Nunes, Colandy Godoy de Oliveira; Rassi, Luiz; Rassi, Salvador

2017-02-01

A few decades ago, patients with Chagas disease were predominantly rural workers, with a low risk profile for obstructive coronary artery disease (CAD). As urbanization has increased, they became exposed to the same risk factors for CAD of uninfected individuals. Dobutamine stress echocardiography (DSE) has proven to be an important tool in CAD diagnosis. Despite being a potentially arrhythmogenic method, it is safe for coronary patients without Chagas disease. For Chagas disease patients, however, the indication of DSE in clinical practice is uncertain, because of the arrhythmogenic potential of that heart disease. To assess DSE safety in Chagas disease patients with clinical suspicion of CAD, as well as the incidence of arrhythmias and adverse events during the exam. Retrospective analysis of a database of patients referred for DSE from May/2012 to February/2015. This study assessed 205 consecutive patients with Chagas disease suspected of having CAD. All of them had their serology for Chagas disease confirmed. Their mean age was 64±10 years and most patients were females (65.4%). No patient had significant adverse events, such as acute myocardial infarction, ventricular fibrillation, asystole, stroke, cardiac rupture and death. Regarding arrhythmias, ventricular extrasystoles occurred in 48% of patients, and non-sustained ventricular tachycardia in 7.3%. DSE proved to be safe in this population of Chagas disease patients, in which no potentially life-threatening outcome was found. Até poucas décadas atrás, os pacientes chagásicos eram predominantemente trabalhadores rurais, com baixo perfil de risco para doença obstrutiva coronária. Com a crescente urbanização, passaram a ter os mesmos fatores de risco para doença aterosclerótica que indivíduos não infectados. O ecocardiograma sob estresse com dobutamina (EED) é uma importante ferramenta no diagnóstico de coronariopatia. É referido, porém, como um método potencialmente arritmogênico, mas seguro, em pacientes coronarianos não chagásicos. Entretanto, há insegurança na prática clínica de indicá-lo no paciente chagásico, devido ao potencial arritmogênico já intrínseco nesta cardiopatia. Analisar a segurança do EED em uma população de chagásicos com suspeita clínica de coronariopatia. Análise retrospectiva de um banco de dados de pacientes encaminhados para a realização do EED entre maio/2012 e fevereiro/2015. Avaliou-se pacientes consecutivos portadores de doença de Chagas e com suspeita de coronariopatia. Confirmou-se a sorologia para doença de Chagas em todos os pacientes. A média etária dos 205 pacientes analisados foi de 64 ± 10 anos, sendo a maioria do sexo feminino (65,4%). Nenhum paciente apresentou eventos adversos significativos, como infarto agudo do miocárdio, fibrilação ventricular, assistolia, acidente vascular encefálico, ruptura cardíaca ou morte. Quanto às arritmias, extrassístoles ventriculares frequentes ocorreram em 48% dos pacientes, taquicardia ventricular não sustentada em 7,3%, bigeminismo em 4,4%, taquicardia supraventricular e taquicardia ventricular sustentada em 1% e fibrilação atrial em 0,5%. O EED mostrou ser um exame seguro nessa população de pacientes chagásicos, onde nenhum desfecho grave foi encontrado.

TUBERCULOSIS COMO ENFERMEDAD OCUPACIONAL

PubMed Central

Mendoza-Ticona, Alberto

2014-01-01

Existe evidencia suficiente para declarar a la tuberculosis como enfermedad ocupacional en diversos profesionales especialmente entre los trabajadores de salud. En el Perú están normados y reglamentados los derechos laborales inherentes a la tuberculosis como enfermedad ocupacional, como la cobertura por discapacidad temporal o permanente. Sin embargo, estos derechos aún no han sido suficientemente socializados. En este trabajo se presenta información sobre el riesgo de adquirir tuberculosis en el lugar de trabajo, se revisan las evidencias para declarar a la tuberculosis como enfermedad ocupacional en trabajadores de salud y se presenta la legislación peruana vigente al respecto. PMID:22858771

Cross-cultural adaptation and validation of the teamwork climate scale.

PubMed

Silva, Mariana Charantola; Peduzzi, Marina; Sangaleti, Carine Teles; Silva, Dirceu da; Agreli, Heloise Fernandes; West, Michael A; Anderson, Neil R

2016-08-22

To adapt and validate the Team Climate Inventory scale, of teamwork climate measurement, for the Portuguese language, in the context of primary health care in Brazil. Methodological study with quantitative approach of cross-cultural adaptation (translation, back-translation, synthesis, expert committee, and pretest) and validation with 497 employees from 72 teams of the Family Health Strategy in the city of Campinas, SP, Southeastern Brazil. We verified reliability by the Cronbach's alpha, construct validity by the confirmatory factor analysis with SmartPLS software, and correlation by the job satisfaction scale. We problematized the overlap of items 9, 11, and 12 of the "participation in the team" factor and the "team goals" factor regarding its definition. The validation showed no overlapping of items and the reliability ranged from 0.92 to 0.93. The confirmatory factor analysis indicated suitability of the proposed model with distribution of the 38 items in the four factors. The correlation between teamwork climate and job satisfaction was significant. The version of the scale in Brazilian Portuguese was validated and can be used in the context of primary health care in the Country, constituting an adequate tool for the assessment and diagnosis of teamwork. Adaptar e validar a escala Team Climate Invetory, de medida do clima de trabalho em equipe, para o idioma português, no contexto da atenção primária à saúde no Brasil. Estudo metodológico com abordagem quantitativa de adaptação transcultural (tradução, retrotradução, síntese, comitê de especialistas e pré-teste) e validação com 497 trabalhadores de 72 equipes da Estratégia Saúde da Família no município de Campinas, São Paulo. Verificou-se confiabilidade pelo alfa de Cronbach, validade de construto pela análise fatorial confirmatória pelo software SmartPLS e correlação com escala de satisfação no trabalho. Foi problematizado a sobreposição dos itens 9, 11 e 12 do fator participação na equipe e o fator objetivos da equipe no tocante à sua definição. A validação mostrou que não houve sobreposição dos itens e a confiabilidade variou entre 0,92 a 0,93. A análise fatorial confirmatória indicou adequação do modelo proposto com distribuição dos 38 itens nos quatro fatores. A correlação entre clima de trabalho em equipe e satisfação no trabalho foi significativa. A versão da escala em português falado no Brasil foi validada e pode ser utilizada no contexto da atenção primária à saúde no País, constituindo ferramenta adequada para a avaliação e diagnóstico do trabalho em equipe.

Pain assessment in elderly with dementia: Brazilian validation of the PACSLAC scale.

PubMed

Thé, Karol Bezerra; Gazoni, Fernanda Martins; Cherpak, Guilherme Liausu; Lorenzet, Isabel Clasen; Santos, Luciana Alves Dos; Nardes, Edlene Maria; Santos, Fânia Cristina Dos

2016-01-01

To validate the Pain Assessment Checklist for Seniors with Limited Ability to Communicate - Portuguese in demented elderly and to analyze its measurement properties. We evaluated 50 elderly with dementia, residing in a nursing home and with limited communication ability, when exposed to potentially painful situations. The tool was applied at two different moments. First, two interviewers applied it simultaneously, and the intensity of pain was asked based on the caregiver's opinion. After 14 days, with no analgesic intervention, one of the interviewers applied it again. The sample comprised more females, aged over 80 years, with dementia due to Alzheimer, presenting musculoskeletal pain of moderate to severe intensity. The psychometric properties of the tool demonstrated appropriate internal consistency (Cronbach's alpha coefficient of 0.827). The scale had excellent reproducibility, according to the intraclass correlation coefficient, and the tool has been duly validated. The Pain Assessment Checklist for Seniors with Limited Ability to Communicate - Portuguese had adequate measuring properties for use with elderly presenting limited communication. Validar o Pain Assessment Checklist for Seniors with Limited Ability to Communicate - Portuguese em idosos dementados e analisar as propriedades de suas medições. Foram avaliados 50 idosos dementados, residentes de uma casa de repouso e com capacidade de comunicação verbal limitada, quando expostos a situações potencialmente dolorosas. A ferramenta foi utilizada em dois momentos diferentes. Primeiro, foi aplicada por dois entrevistadores simultaneamente, e a intensidade da dor foi questionada com base na opinião do cuidador. Depois de 14 dias, sem intervenção de analgésico, a ferramenta foi aplicada novamente por um dos entrevistadores. A amostra teve predominância de mulheres, acima de 80 anos de idade, com demência de Alzheimer, apresentando dores musculoesqueléticas com intensidade moderada a grave. As propriedades psicométricas do instrumento demonstraram consistência interna adequada (coeficiente alfa de Cronbach de 0,827). A escala teve excelente reprodutibilidade, de acordo com o coeficiente de correlação intraclasse, e o instrumento demonstrou validade adequada. O Pain Assessment Checklist for Seniors with Limited Ability to Communicate - Portuguese teve propriedades de medição adequadas para idosos com limitações de comunicação.

The Variation of Catalyst and Carrier Gas on Anisole Deoxygenation Reaction

NASA Astrophysics Data System (ADS)

Ariyani, D.; Dwi Nugrahaningtyas, Khoirina; Heraldy, E.

2018-03-01

This research aims to determine the best catalyst and carrier gas in anisole deoxygenation reaction. The reaction was carried out over a flow system with a variation of catalyst CoMo A (CoMo/USY reduction), CoMo B (CoMo/USY oxidation-reduction), and CoMo C (CoMo/ZAA oxidation-reduction). In addition, variation of carrier gas nitrogen and hydrogen was investigated. The result was analyzed using Gas Chromatography-Mass Spectroscopy (GC-MS). The deoxygenation anisole result showed that CoMo A catalyst with hydrogen as the carrier gas has the highest total product yield (50.72 %), intermediate product yield (38.49 % in phenol and 6.99 % in benzaldehyde), and deoxygenation yield (5.24 %). The CoMo C catalyst exhibited the most selective deoxygenation product. The nitrogen carrier gas with the CoMo C catalyst has the best selectivity of benzene product (93.92 %).

Simplificando a luneta com lente de óculos

NASA Astrophysics Data System (ADS)

Canalle, J. B. G.; de Souza, A. C. F.

2003-08-01

A principal ferramenta de trabalho do astrônomo é o telescópio. O manuseio do mesmo é sempre motivo de enorme curiosidade por parte de alunos do ensino fundamental ou médio e até mesmo dos respectivos professores. Visando propiciar o acesso de alunos e professores ou interessados em geral a uma luneta de fácil construção, com materiais alternativos, de fácil localização no comércio, de baixo custo, resistente ao manuseio de alunos, simplificamos a montagem de uma luneta construída com lente de óculos, de 1 ou 2 graus positivos, e monóculo de fotografia, publicado por este autor no CCEF, vol.11(3), 212, 1994. Esta luneta, a qual permite ver as crateras lunares, apresentava como maior dificuldade de construção o tripé e o local de formação da imagem. Substituímos o tripé de madeira por uma simples garrafa PET de 2 litros cheia d'água. No lugar da ocular usamos a lente do monóculo de fotografia (ou visor de fotografia) encaixado dentro de uma bucha de redução curta, de 40 x 32 mm, e esta não mais dentro de uma luva (conexão hidráulica) de 40 mm de diâmetro, mas sim encostada no próprio tubo de PVC móvel (o qual permite o ajuste do foco) de 40 mm de diâmetro e presa a este por outro tubo de 40 mm de diâmetro e 10 cm de comprimento, serrado ao longo do seu comprimento. Com isto podemos ajustar a posição deste tubo de 10 cm também para que uma das suas extremidades coincida com o local de formação da imagem. Desta forma o observador saberá o local exato da formação da imagem, o que não era evidente na montagem anterior e causava uma dificuldade inicial até se descobrir a posição exata em que se deveria colocar o olho. Deste maneira, a montagem inicial que já era simples ficou ainda mais simples, mais barata e mais confortável para o uso. Um exemplar da mesma será exposto durante a XXIX Reunião Anual da Sociedade Astronômica Brasileira para inspeção e uso dos participantes.

Hydro-geochemical modeling of subalpine urbanized area: geochemical characterization of the shallow and deep aquifers of the urban district of Como (first results).

NASA Astrophysics Data System (ADS)

Terrana, Silvia; Brunamonte, Fabio; Frascoli, Francesca; Ferrario, Maria Francesca; Michetti, Alessandro Maria; Pozzi, Andrea; Gambillara, Roberto; Binda, Gilberto

2016-04-01

One of the greatest environmental and social-economics threats is climate change. This topic, in the next few years, will have a significant impact on the availability of water resources of many regions. This is compounded by the strong anthropization of water systems that shows an intensification of conflicts for water resource exploitation. Therefore, it is necessary a sustainable manage of natural resources thorough knowledge of the hosting territories. The development of investigation and data processing methods are essential to reduce costs for the suitable use and protection of resources. Identify a sample area for testing the best approach is crucial. This research aims to find a valid methodology for the characterization, modeling and management of subalpine urban aquifers, and the urban district of Como appears perfect. The city of Como is located at the southern end of the western sector of Lake Como (N Italy). It is a coastal town, placed on a small alluvial plain, therefore in close communication with the lake. The plain is drained by two streams, which are presently artificially buried, and have an underground flow path in the urban section till the mouth. This city area, so, is suitable for this project as it is intensely urbanized, its dimensions is not too extensive and it is characterized by two aquifers very important and little known. These are a shallow aquifer and a deep aquifer, which are important not only for any water supply, but also for the stability of the ground subsidence in the city. This research is also the opportunity to work in a particular well-known area with high scientific significance; however, there is complete absence of information regarding the deep aquifer. Great importance has also the chosen and used of the more powerful open source software for this type of area, such as PHREEQC, EnvironInsite, PHREEQE etc., used for geological and geochemical data processing. The main goal of this preliminary work is the characterization of both aquifers and the comprehension of the interaction between the shallow one and deep one. The first results of geochemical and hydrological analyses in nine piezometer, seven in the shallow aquifer and two in the deep one, permit to identify a general characterization of groundwater: the waters of both the aquifers are calcium bicarbonate, with discontinuous enrichment in sulphate and silicate. The conductibility values are higher in the shallow aquifer then in the deep aquifer, this is an indication of the high flow rate of the deep one and of the higher level of vulnerability of the shallow water respect the urban pollutant. Particular is also the relatively high temperature for the deep water (15.5°C to 16.1°C). The next steps of work are an increase of geochemical analysis, with trace element, and the correlation with hydro-chemical surface water.

Barotrauma em peixes em usinas hidrelétricas: ferramentas para o estudo

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

Do Vale Beirao, Bernardo; Castelo Branco Marciano, Natlia; de Souza Dias, Luma

2015-09-30

The main source of electric power generation in Brazil comes from hydropower plants, nevertheless, the installed power is expected to raise 56.8%, reaching a total of 116,000 MW at the year 2020. The increase at the hydroelectric sector will be responsible for a series of fish community impacts. One of the impacts over the fish community is related to fish kills due to downstream passage through turbines or fish entrance at the draft tube from the tailrace. Usually when there is a maneuver and the turbine stops, fish get attracted and enter the draft tube and, just as the downstreammore » passage through a turbine, when the turbine starts, a rapid decompression occurs and can cause barotrauma. When such events happen, according to Boyle’s law (P1V1=P2V2), swim bladder volume expands at the same rate that the pressure decreases, which can lead to the organ’s rupture.« less

The English as a Foreign Language/Lingua Franca Debate: Sensitising Teachers of English as a Foreign Language towards Teaching English as a Lingua Franca (El debate del inglés como lengua extranjera o como lengua franca: sensibilización de docentes de inglés como lengua extranjera hacia la enseñanza del inglés como lengua franca)

ERIC Educational Resources Information Center

Mansfield, Gillian; Poppi, Franca

2012-01-01

The function of English as a lingua franca for communication needs rethinking in the teaching of English as a foreign language classroom as a consequence of globalisation. The present contribution is an empirical study carried out in an Italian university environment which aims to show how teachers should take on board awareness raising activities…

High-energy asymmetric supercapacitors based on free-standing hierarchical Co-Mo-S nanosheets with enhanced cycling stability.

PubMed

Balamurugan, Jayaraman; Li, Chao; Peera, Shaik Gouse; Kim, Nam Hoon; Lee, Joong Hee

2017-09-21

Layered transition metal sulfides (TMS) are emerging as advanced materials for energy storage and conversion applications. In this work, we report a facile and cost-effective anion exchange technique to fabricate a layered, multifaceted, free standing, ultra-thin ternary cobalt molybdenum sulfide nanosheet (Co-Mo-S NS) architecture grown on a 3D porous Ni foam substrate. The unique Co-Mo layered double hydroxides are first synthesized as precursors and consequently transformed into ultra-thin Co-Mo-S NS. When employed as an electrode for supercapacitors, the Co-Mo-S NS delivered an ultra-high specific capacitance of 2343 F g -1 at a current density of 1 mA cm -2 with tremendous rate capability and extraordinary cycling performance (96.6% capacitance retention after 20 000 cycles). Furthermore, assembled Co-Mo-S/nitrogen doped graphene nanosheets (NGNS) in an asymmetric supercapacitor (ASC) device delivered an excellent energy density of 89.6 Wh kg -1 , an amazing power density of 20.07 kW kg -1 , and superior cycling performance (86.8% capacitance retention after 50 000 cycles). Such exceptional electrochemical performance of Co-Mo-S NS is ascribed to the good electrical contact with the 3D Ni foam, ultra-high contact area with the electrolyte, and enhanced architectural softening during the charging/discharging process. It is expected that the fabricated, unique, ultra-thin Co-Mo-S NS have great potential for future energy storage devices.

A sup 57 Co Moessbauer emission spectrometric study of some supported CoMo hydrodesulfurization catalysts

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

Veen, J.A.R. van; Hendriks, P.A.J.M.; Beens, H.

1992-01-01

A suite of 11 CoMo/Al{sub 2}O{sub 4} (and one CoMo/SiO{sub 2}) catalysts has been prepared employing four preparation routes, viz. one sequential-impregnation route and three different coimpregnation routes. Speciation of the Co present in the oxidic precursors (octahedral vs tetrahedral Co) and in the activated, sulfided catalysts (CoMoS, Co{sub 9}S{sub 8}, and unsulfided Co) was effected with the aid of {sup 57}Co Moessbauer emission spectroscopy (MES). A linear relation between the thiophene-hydrodesulfurization (HDS) activity and wt% Co-in-CoMoS was observed for each preparation route, but no unique correlation was found to exist. This was traced to the fact that the preparationmore » routes differ in the amount of CoMoS I and CoMoS II they produce in the activated catalyst. Although these two phases differ in specific activity, CoMoS II being twice as active in thiophene HDS as CoMoS I, they cannot be distinguished on the basis of their Moessbauer parameters. It appears that octahedral Co is easier to sulfide than tetrahedral Co, but a substantial fraction of the latter is also found to be capable of entering CoMoS upon sulfidation. The reduced effectiveness of high-loading catalysts is traced to their being prone to CoMoO{sub 4} formation in the calcination step. A rationalization of this behavior is offered.« less

Visceral leishmaniasis in the state of Sao Paulo, Brazil: spatial and space-time analysis.

PubMed

Cardim, Marisa Furtado Mozini; Guirado, Marluci Monteiro; Dibo, Margareth Regina; Chiaravalloti, Francisco

2016-08-11

To perform both space and space-time evaluations of visceral leishmaniasis in humans in the state of Sao Paulo, Brazil. The population considered in the study comprised autochthonous cases of visceral leishmaniasis and deaths resulting from it in Sao Paulo, between 1999 and 2013. The analysis considered the western region of the state as its studied area. Thematic maps were created to show visceral leishmaniasis dissemination in humans in the municipality. Spatial analysis tools Kernel and Kernel ratio were used to respectively obtain the distribution of cases and deaths and the distribution of incidence and mortality. Scan statistics were used in order to identify spatial and space-time clusters of cases and deaths. The visceral leishmaniasis cases in humans, during the studied period, were observed to occur in the western portion of Sao Paulo, and their territorial extension mainly followed the eastbound course of the Marechal Rondon highway. The incidences were characterized as two sequences of concentric ellipses of decreasing intensities. The first and more intense one was found to have its epicenter in the municipality of Castilho (where the Marechal Rondon highway crosses the border of the state of Mato Grosso do Sul) and the second one in Bauru. Mortality was found to have a similar behavior to incidence. The spatial and space-time clusters of cases were observed to coincide with the two areas of highest incidence. Both the space-time clusters identified, even without coinciding in time, were started three years after the human cases were detected and had the same duration, that is, six years. The expansion of visceral leishmaniasis in Sao Paulo has been taking place in an eastbound direction, focusing on the role of highways, especially Marechal Rondon, in this process. The space-time analysis detected the disease occurred in cycles, in different spaces and time periods. These meetings, if considered, may contribute to the adoption of actions that aim to prevent the disease from spreading throughout the whole territory of São Paulo or to at least reducing its expansion speed. Avaliar, no espaço e espaço-tempo, a ocorrência da leishmaniose visceral em humanos no estado de São Paulo, Brasil. Considerou-se como população de estudo os casos autóctones e óbitos por leishmaniose visceral em humanos ocorridos em São Paulo entre 1999 e 2013 e, como área de estudo, a região oeste do estado. Construíram-se mapas temáticos que mostraram a disseminação da leishmaniose visceral em humanos nos municípios. Ferramentas de análise espacial Kernel e razão Kernel foram utilizadas para obter, respectivamente, a distribuição dos casos e óbitos e a distribuição da incidência e mortalidade. Utilizaram-se estatísticas de varredura para identificar aglomerados espaciais e espaço-temporais de casos e óbitos. Os casos de leishmaniose visceral em humanos, no período de estudo, ocorreram na parte ocidental de São Paulo e sua expansão territorial seguiu principalmente o curso da rodovia Marechal Rondon, no sentido oeste-leste. As incidências foram caracterizadas como duas sequências de elipses concêntricas com intensidade decrescente. A primeira, com maior intensidade, teve epicentro no município de Castilho (cruzamento da rodovia Marechal Rondon com a divisa com o estado de Mato Grosso do Sul) e a segunda, em Bauru. A mortalidade apresentou comportamento similar ao da incidência. Os aglomerados espaciais e espaço-temporais de casos coincidiram com as duas áreas de maiores incidências. Ambos os aglomerados espaço-temporais identificados, mesmo sem coincidirem temporalmente, tiveram início após três anos da detecção dos casos humanos e tiveram a mesma duração, seis anos. A expansão da leishmaniose visceral em São Paulo vem ocorrendo no sentido oeste-leste, com destaque ao papel das rodovias, especialmente a Marechal Rondon, neste processo. A análise espaço-temporal detectou, em diferentes espaços e períodos de tempo, ciclicidade na ocorrência da doença. Esses encontros, se considerados, podem colaborar para a adoção de ações que visem a evitar que a doença se espalhe por todo o território paulista ou, no mínimo, diminuir sua velocidade de expansão.

Analysis of Family Clinical, vision of service nurses.

PubMed

Raimundi, Daniele Merisio; Ferreira, Francieli Furtado; Lima, Fernanda Cristina Aguiar; Siqueira, Valeria de Carvalho Araújo

2016-06-01

to know the practice of the Family Clinic in Cuiaba and its relationship with the precepts of the expanded clinic, from the perspective of the service nurses. qualitative descriptive research, data collection with semi-structured interviews and results analyzed according to the method of thematic content analysis. for nurses working in the service, this assumes a differentiated and innovative proposal, which seeks to correlate with shared management in its three spheres. Although most do not know the Enlarged Clinic term in his speech cited its main principles and its tools. The greatest potential described were related to the Support Center for Health and popular participation, and as challenges, the lack of community health worker, the national health establishment registration and the difficulty of operation due to the profile of the professionals technical level arising from secondary care. The clinic has positive aspects that can contribute to the advancement of the profession, to train health professionals and an innovative primary care model. Therefore, it emphasizes the need for implementation of continuing education in order to realize its proposal, and further studies on site. conhecer a prática da Clínica da Família em Cuiabá e sua relação com os preceitos da clínica ampliada, sob a perspectiva dos enfermeiros do serviço. pesquisa descritiva qualitativa, coleta de dados com entrevista semi-estruturada e resultados analisados segundo o método de análise de conteúdo do tipo temática. para os enfermeiros atuantes no serviço, este assume uma proposta diferenciada e inovadora, no qual busca se correlacionar com a gestão compartilhada em suas três esferas. Apesar de a maioria não conhecer o termo Clínica Ampliada em suas falas citaram seus principais preceitos e suas ferramentas. As maiores potencialidades descritas foram a relação com o Núcleo de Apoio à Saúde da Família e a participação popular, e como desafios, a falta de agente comunitário de saúde, do cadastro nacional de estabelecimento de saúde e a dificuldade de atuação devido ao perfil dos profissionais de nível técnico advindos da atenção secundária. a clínica possui aspectos positivos que podem contribuir para o progresso da profissão, para a formação de profissionais da saúde e para um modelo de assistência de nível primário inovador. Logo, enfatiza-se a necessidade de implantação da educação permanente com o objetivo de concretizar sua proposta, além de estudos posteriores no local.

Is there a rationale for pulmonary rehabilitation following successful chemotherapy for tuberculosis?

PubMed

Muñoz-Torrico, Marcela; Rendon, Adrian; Centis, Rosella; D'Ambrosio, Lia; Fuentes, Zhenia; Torres-Duque, Carlos; Mello, Fernanda; Dalcolmo, Margareth; Pérez-Padilla, Rogelio; Spanevello, Antonio; Migliori, Giovanni Battista

2016-01-01

The role of tuberculosis as a public health care priority and the availability of diagnostic tools to evaluate functional status (spirometry, plethysmography, and DLCO determination), arterial blood gases, capacity to perform exercise, lesions (chest X-ray and CT), and quality of life justify the effort to consider what needs to be done when patients have completed their treatment. To our knowledge, no review has ever evaluated this topic in a comprehensive manner. Our objective was to review the available evidence on this topic and draw conclusions regarding the future role of the "post-tuberculosis treatment" phase, which will potentially affect several million cases every year. We carried out a non-systematic literature review based on a PubMed search using specific keywords (various combinations of the terms "tuberculosis", "rehabilitation", "multidrug-resistant tuberculosis", "pulmonary disease", "obstructive lung disease", and "lung volume measurements"). The reference lists of the most important studies were retrieved in order to improve the sensitivity of the search. Manuscripts written in English, Spanish, and Russian were selected. The main areas of interest were tuberculosis sequelae following tuberculosis diagnosis and treatment; "destroyed lung"; functional evaluation of sequelae; pulmonary rehabilitation interventions (physiotherapy, long-term oxygen therapy, and ventilation); and multidrug-resistant tuberculosis.The evidence found suggests that tuberculosis is definitively responsible for functional sequelae, primarily causing an obstructive pattern on spirometry (but also restrictive and mixed patterns), and that there is a rationale for pulmonary rehabilitation. We also provide a list of variables that should be discussed in future studies on pulmonary rehabilitation in patients with post-tuberculosis sequelae. RESUMO O papel da tuberculose como uma prioridade de saúde pública e a disponibilidade de ferramentas diagnósticas para avaliar o estado funcional (espirometria, pletismografia e DLCO), a gasometria arterial, a capacidade de realizar exercícios, as lesões (radiografia de tórax e TC) e a qualidade de vida justificam o esforço de se considerar o que deve ser feito quando os pacientes completam seu tratamento. Até onde sabemos, nenhuma revisão avaliou esse tópico de forma abrangente. Nosso objetivo foi revisar as evidências disponíveis e obter algumas conclusões sobre o futuro papel da fase de "tratamento pós-tuberculose", que irá potencialmente impactar milhões de casos todos os anos. Realizou-se uma revisão não sistemática da literatura tendo como base uma pesquisa no PubMed usando palavras-chave específicas (várias combinações dos termos "tuberculose", "reabilitação", "tuberculose multirresistente", "doença pulmonar", "doença pulmonar obstrutiva", e "medidas de volume pulmonar"). As listas de referências dos artigos principais foram recuperadas para melhorar a sensibilidade da busca. Foram selecionados manuscritos escritos em inglês, espanhol e russo. As principais áreas de interesse foram sequelas de tuberculose após diagnóstico e tratamento; "pulmão destruído"; avaliação funcional das sequelas; intervenções de reabilitação pulmonar (fisioterapia, oxigenoterapia de longo prazo e ventilação); e tuberculose multirresistente. As evidências encontradas sugerem que a tuberculose é definitivamente responsável por sequelas funcionais, principalmente causando um padrão obstrutivo na espirometria (mas também padrões restritivos e mistos) e que há razão para a reabilitação pulmonar. Fornecemos também uma lista de variáveis a serem discutidas em futuros estudos sobre reabilitação pulmonar em pacientes com sequelas pós-tuberculose.

Serious game development as a strategy for health promotion and tackling childhood obesity.

PubMed

Dias, Jéssica David; Mekaro, Marcelo Shinyu; Cheng Lu, Jennifer Kaon; Otsuka, Joice Lee; Fonseca, Luciana Mara Monti; Zem-Mascarenhas, Silvia Helena

2016-08-15

to develop and assess a serious game on healthy eating and physical activity to promote health and tackle childhood obesity. a descriptive, applied and methodological study.For the development of the game, the following steps were taken: conceptualization, pre-production with the development of the game documentation, prototyping, production and assessment of thecomputer and health experts. a prototype has been developed up to beta version. The game was positively assessed both in terms of gameplay and mechanics, and in relation to the content presented, standing out as a powerful strategy for health promotion. The information from the assessment phase contributed to the settings in the software in order to make it available in the future for the target population of this research. The greatest advantage of the proposed game is the fact that it is an open educational resource. the expert assessments showed that the game has great educational potential and it is considered suitable for future application to the target audience.The serious game can become a technological teaching resource available for use in schools and health facilities, and can also be reused for the production of other educational games by accessing its source code. desenvolver e avaliar um serious game (Jogo sério) sobre alimentação saudável e exercício físico para promoção da saúde e auxílio ao enfrentamento da obesidade infantil. estudo descritivo, aplicado e metodológico. Para o desenvolvimento do jogo, foram percorridas as seguintes etapas: conceituação, pré-produção com desenvolvimento da documentação do jogo, prototipagem, produção e avaliação de especialistas de computação e saúde. desenvolveu-se um protótipo até a versão beta. O jogo foi avaliado positivamente tanto em relação à jogabilidade e mecânica, quanto em relação ao conteúdo apresentado, destacando-se como uma estratégia potente para a promoção de saúde. As informações oriundas da fase de avaliação serviram de subsídio para adequações no software com a finalidade de disponibilizá-lo futuramente à população alvo da pesquisa. O grande diferencial do jogo proposto é o fato do mesmo ser um recurso educacional aberto. as avaliações com especialistas demonstraram que o jogo tem grande potencial educacional e considerado adequado para a aplicação futura com o público-alvo. O serious game pode ser um recurso didático tecnológico acessível para uso em escolas e unidades de saúde, além de poder ser reutilizado para a produção de outros jogos educacionais através do acesso de seu código fonte. desarrollar y evaluar un serious game (Juego serio) sobre alimentación saludable y ejercicio físico para la promoción de la salud y ayudar en el enfrentamiento de la obesidad infantil. estudio descriptivo, aplicado y metodológico. Para el desarrollo del juego, se iniciaron los siguientes pasos: conceptualización, pre-producción con el desarrollo de la documentación del juego, creación de prototipos, producción y evaluación por expertos informáticos y en salud. un prototipo se ha desarrollado hasta la versión beta. El juego se evaluó positivamente tanto en términos de jugabilidad y mecánica como en relación con el contenido presentado, destacándose como una poderosa estrategia para la promoción de la salud. La información de la fase de evaluación contribuyó a los ajustes en el software con el fin de que esté disponible en el futuro para la población objetivo de esa investigación. La gran vantaja del juego propuesto es el hecho de que es un recurso educativo abierto. las evaluaciones de los expertos mostraron que el juego tiene un gran potencial educativo y es considerado adecuado para la aplicación futura para el público objetivo. El serious game puede convertirse en un recurso para la enseñanza tecnológica disponible para uso en las escuelas y en los centros de salud, y también puede ser reutilizado para la producción de otros juegos educativos mediante el acceso a su código fuente.

CoMoS2/rGO/C3N4 ternary heterojunctions catalysts with high photocatalytic activity and stability for hydrogen evolution under visible light irradiation

NASA Astrophysics Data System (ADS)

Xu, Xuejun; Si, Zhichun; Liu, Liping; Wang, Zehao; Chen, Ze; Ran, Rui; He, Yonghong; Weng, Duan

2018-03-01

Noble metal free MoS2/g-C3N4 catalyst has attracted intense attentions for visible light photocatalytic hydrogen evolution as a result of its earth abundance, low cost and unique heterojunctions stacked with two dimensional sheets. However, the low charge separation efficiency resulted from the poor conductivity of g-C3N4 and MoS2, and lack of abundant active sites from coordinative unsaturated atoms in MoS2, restricts the photocatalytic hydrogen evolution activity and stability enhancement of MoS2/C3N4 composite catalysts. Herein, CoMoS2/rGO/g-C3N4 catalysts with ternary heterojunctions are prepared by facile solvothermal method, which exhibit high visible light photocatalytic activity and stability for hydrogen evolution. The optimal hydrogen evolution rate of CoMoS2/rGO/g-C3N4 catalysts is 684 μmol g-1 h-1 when the content of CoMoS2 is 2% and the content of rGO is 0.5%. The stability of CoMoS2/rGO/C3N4 catalysts just decrease about 3% after 4 cycling runs for 16 h. The good catalytic performances of catalysts are attributed to the synergistic effect among the g-C3N4 nanosheets, rGO nanosheets and CoMoS2 nanosheets. The high conductivity of rGO nanosheets enhances the electron-hole separation and charge transfer, and Co doping increases the active sites for hydrogen evolution due to the increase of unsaturated atoms in CoMoS2 nanosheets.

COMO: a numerical model for predicting furnace performance in axisymmetric geometries. Volume 1. Technical summary. Final report

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

Fiveland, W.A.; Oberjohn, W.J.; Cornelius, D.K.

1985-12-01

This report summarizes the work conducted during a 30-month contract with the United States Department of Energy (DOE) Pittsburgh Energy Technology Center (PETC). The general objective is to develop and verify a computer code capable of modeling the major aspects of pulverized coal combustion. Achieving this objective will lead to design methods applicable to industrial and utility furnaces. The combustion model (COMO) is based mainly on an existing Babcock and Wilcox (B and W) computer program. The model consists of a number of relatively independent modules that represent the major processes involved in pulverized coal combustion: flow, heterogeneous and homogeneousmore » chemical reaction, and heat transfer. As models are improved or as new ones are developed, this modular structure allows portions of the COMO model to be updated with minimal impact on the remainder of the program. The report consists of two volumes. This volume (Volume 1) contains a technical summary of the COMO model, results of predictions for gas phase combustion, pulverized coal combustion, and a detailed description of the COMO model. Volume 2 is the Users Guide for COMO and contains detailed instructions for preparing the input data and a description of the program output. Several example cases have been included to aid the user in usage of the computer program for pulverized coal applications. 66 refs., 41 figs., 21 tabs.« less

Múltiples estados de desorden en el etanol sólido

NASA Astrophysics Data System (ADS)

Fernández-Perea, R.

El diagrama de fases del etanol por debajo de los 169 K será presentado. Se mostrará que el etanol puede solidificarse en tres fases con diversos niveles de desorden,(como un vidrio(G), como un vidrio orientacional (OG) y como un cristal de fase rotora (RP)) además de en una fase totalmente cristalina. Las estructuras de estas tres fases serán presentadas tal y como se deducen a partir de diversas medidas de difracción de neutrones al igual que las proporciones de los isómeros de dicho material en las fases desordenadas y se compararán con los resultados de la fase cristalina y del líquido superenfriado. Igualmente diversas medidas sobre su dinámica serán presentadas, tanto de dispersión de neutrones, como de capacidad calorífica y de medidas dieléctricas y comparadas con modelos teóricos y simulaciones para tratar de explicar los procesos de relajación observados y las transiciones entre las diversas fases.

PubMed

Silva, Cristiane Gonçalves da; Santos, Alessandro Oliveira; Licciardi, Daniele Carli; Paiva, Vera; Parker, Richard

2008-01-01

Esse artigo descreve como jovens religiosos e autoridades religiosas de sua comunidade compreendem a sexualidade, considerando suas experiências pessoais e como membros de comunidades religiosas. A análise pretende contribuir para que políticas públicas dedicadas à promoção da saúde sexual da juventude considerem a religiosidade, no contexto de um estado laico e da promoção do direito à prevenção. Foram realizadas 26 entrevistas abertas e semidirigidas em diferentes comunidades da região metropolitana da cidade de São Paulo (comunidades católicas, da umbanda, do candomblé e de diferentes denominações evangélicas) sobre iniciação sexual, casamento, gravidez, contracepção e prevenção das DST/Aids, homossexualidade, aborto e direitos humanos. Observou-se como jovens e autoridades religiosas convivem com a tensão entre tradição e modernidade e os distintos discursos sobre a sexualidade. Como sujeitos religiosos (do discurso religioso) e sujeitos sexuais (de discursos sobre sexualidade), devem ser incorporados pelos programas como sujeitos de direito nos termos de sua religiosidade.

Portuguese nursing: history of the life and activism of Maria Augusta Sousa.

PubMed

Almeida, Deybson Borba de; Silva, Gilberto Tadeu Reis da; Queirós, Paulo Joaquim Pina; Freitas, Genival Fernandes de; Laitano, Aline Di Carla; Almeida, Sirléia de Sousa; Santos, Victor Porfirio Ferreira Almeida

2016-01-01

To analyze the history of the life and activism of Portuguese nurse Maria Augusta Sousa. Sousa's life story was obtained by means of semi-structured interview swith Sousa as the oral source of data. NVivo qualitative research software was used for data analysis. Content analysis focused on thematic analysis based on the theoretical and philosophical ideas of Michel Foucault, in particular, power and techniques of the self. Alienation and political participation were revealed as pertinent issues. In techniques of production of activist subjects, the following were highlighted: the importance of the review of formal education; actions of involvement with the world, society and the profession; and finally, techniques of the self, techniques of constitution of activist subjects, professional identity and way of being. The constitution of the nurse Maria Augusta Sousa as an activist came about through questioning of how to be, education in the context of her family, and political engagement in Catholic Youth. This impacted her trajectory of contributions to Portuguese nursing, as expressed in the following achievements: the integration of nursing training into higher education; the creation of the Regulation of Nurses Professional Practice; and implementation of the Order of Nurses. Analisar a história de vida e militância da enfermeira Maria Augusta Sousa. História de vida, tendo como fonte oral a entrevista semiestruturada. Na análise de dados utilizou-se do software de pesquisa qualitativa Nvivo, e a análise de conteúdo com foco na análise temática e com base teórico-filosófica de Michel Foucault, em especial, o poder e as técnicas de si. Evidenciaram-se a alienação e a participação política comoquestões pertinentes. Nas técnicas de produção de sujeitos militantes destacam-se a importânciada revisão da educação formal, dos atos de implicação com o mundo, a sociedade e a profissão, e por fim, as técnicas de si, técnicas de constituição de sujeitos militantes, a identidade profissional e o modo de ser. A constituição da enfermeira Maria Augusta Sousa como militante acontece por questões do modo de ser, da educação familiar e do seu engajamento político na Juventude Católica, que repercutiu em uma trajetória de contribuição para enfermagem portuguesa, expressa nas seguintes conquistas: a integração do Ensino de Enfermagem no Ensino Superior, a criação do Regulamento do Exercício Profissional de Enfermagem e a implantação da Ordem dos Enfermeiros.

Dissecção aórtica de tipo B de Stanford: relato de caso e revisão de literatura

PubMed Central

Michaelis, Wilson; Santos, Antônio Lacerda; Yokohama, Rogério Akira; Andretta, Marianne Ariely; Delazari, Mariana Vieira; Vieira, Luciano; Seguro, Erick Fernando; Sarquis, Lucas Mansano

2017-01-01

Resumo O complexo tratamento de dissecção da aorta ainda apresenta controvérsias devido à gravidade do caso e à necessidade de individualização da terapêutica. A gravidade relaciona-se ao difícil diagnóstico pelas queixas inespecíficas e pelas graves complicações inerentes à evolução da doença (ruptura aórtica, síndrome de má perfusão, dissecção retrógrada, dor ou hipertensão refratária). Este relato apresenta um homem de 61 anos, tabagista e hipertenso mal controlado, que evoluiu para dissecção aórtica de tipo B de Stanford. Foi abordado através de técnica endovascular com uso de endoprótese com stent para tratamento do caso após falha do tratamento medicamentoso. O tratamento endovascular mostrou-se uma ferramenta eficaz para o tratamento definitivo, com boa taxa de sobrevida ao final do primeiro ano após o procedimento.

Como Podar Arboles (Spanish Version), How to Prune Trees

Treesearch

Maureen McDonough; Russell; Lisa Burban; Lee Nancarrow; United States Department of Agriculture, Forest Service, Northeastern Area, State and Private Forestry

2004-01-01

Introduccion, El proposito de la poda es tener plantas fuertes, sanas y atractivas. Esta meta se puede alcanzar sabiendo como, cuando y por que podar, y siguiendo unos cuantos principios muy sencillos.

Religiosidade, juventude e sexualidade: entre a autonomia e a rigidez1

PubMed Central

Silva, Cristiane Gonçalves da; Santos, Alessandro Oliveira; Licciardi, Daniele Carli; Paiva, Vera; Parker, Richard

2009-01-01

Esse artigo descreve como jovens religiosos e autoridades religiosas de sua comunidade compreendem a sexualidade, considerando suas experiências pessoais e como membros de comunidades religiosas. A análise pretende contribuir para que políticas públicas dedicadas à promoção da saúde sexual da juventude considerem a religiosidade, no contexto de um estado laico e da promoção do direito à prevenção. Foram realizadas 26 entrevistas abertas e semidirigidas em diferentes comunidades da região metropolitana da cidade de São Paulo (comunidades católicas, da umbanda, do candomblé e de diferentes denominações evangélicas) sobre iniciação sexual, casamento, gravidez, contracepção e prevenção das DST/Aids, homossexualidade, aborto e direitos humanos. Observou-se como jovens e autoridades religiosas convivem com a tensão entre tradição e modernidade e os distintos discursos sobre a sexualidade. Como sujeitos religiosos (do discurso religioso) e sujeitos sexuais (de discursos sobre sexualidade), devem ser incorporados pelos programas como sujeitos de direito nos termos de sua religiosidade. PMID:21886456

Microwave effects on NiMoS and CoMoS single-sheet catalysts.

PubMed

Borges, I; Silva, Alexander M; Modesto-Costa, Lucas

2018-05-04

Single-sheet nanoclusters of MoS 2 , NiMoS or CoMoS are widely used in hydrodesulfurization (HDS) catalysis in the petroleum industry. In HDS reactions under microwave irradiation, experiments indirectly pointed out that for pristine MoS 2 reaction rates are accelerated because hot spots are generated on the catalyst bed. In this work, we investigated NiMoS and CoMoS isolated single-sheet substituted catalysts before and after thiophene adsorption focusing on quantifying the effect of microwave irradiation. For that purpose, density functional theory (DFT) molecular charge densities of each system were decomposed according to the distributed multipole analysis (DMA) of Stone. Site dipole values of each system were directly associated with a larger or smaller interaction with the microwave field according to a proposed general approach. We showed that microwave enhancement of HDS reaction rates can occur more efficiently in the CoMoS and NiMoS promoted clusters compared to pristine MoS 2 in the following order: CoMoS > NiMoS > MoS 2 . The atomic origin of the catalyst hot spots induced by microwaves was clearly established in the promoted clusters.

Dicloruro de paraquat

EPA Pesticide Factsheets

El dicloruro de paraquat, comúnmente conocido como “paraquat,” es uno de los herbicidas registrados de mayor uso en los Estados Unidos. El paraquat también se conoce como Gramaxone (un producto popular de uso final

Evolution of the Active Phase of CoMo/Al2O3 Catalysts under Industrial Conditions: a High-Pressure MES Study

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

Dugulan, A.I.; Overweg, A.R.; Craje, M.W.J.

2005-04-26

The behavior of CoMo/Al2O3 catalysts sulfided in H2S/H2 gas mixture, under industrial conditions, was investigated using Moessbauer emission spectroscopy (MES). An intermediate Co-Mo phase is formed after increasing the sulfidation pressure to 4 MPa, favoring the Co-Mo-S phase formation. An increase in the quadrupole splitting value of the Co-sulfide species after treatment at 573 K is proposed as a prerequisite for the formation of ideal Co-Mo-S structures.

Catalytic functionalities of supported sulfides. I. Effect of support and additives on the CoMo catalyst

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

Muralidhar, G.; Massoth, F.E.; Shabtai, J.

1984-01-01

C-S hydrogenolysis (HDS) of thiophene, hydrogenation (HYD) of 1-hexene, and hydrocracking (HCG) of 2,4,4-trimethyl-1-pentene, were used as separate model test reactions to differentiate and assess the catalytic functionalities of sulfided CoMo catalysts, and their dependence on the nature of the support and incorporation of additives. Rate constants and relative catalyst activities for these three reaction types were determined. HDS and HYD activities of CoMo supported on different types of Al/sub 2/O/sub 3/ were higher, while the HCG activity was lower compared with CoMo supported on SiO/sub 2/-Al/sub 2/O/sub 3/, SiO/sub 2/-MgO, or TiO/sub 2/. For SiO/sub 2/-Al/sub 2/O/sub 3/ supportsmore » both HDS and HYD activities decreased with increase in SiO/sub 2/ content from 10 to 75%, while HCG activity showed the opposite trend. Additives to a finished CoMo catalyst at 0.5% level caused variations in HDS and HCG activities, while HYD was essentially unaffected. HDS was promoted by NH/sub 4/HF/sub 2/ and NH/sub 4/Cl, but depressed by NaNO/sub 3/, Ca(NO/sub 3/)/sub 2/, and H/sub 3/BO/sub 3/. HCG was promoted by NH/sub 4/HF/sub 2/, NH/sub 4/Cl, and H/sub 3/BO/sub 3/. Additives at 5% level, prior to or after CoMo impregnation, showed a strong depressing effect on HDS and a lesser effect on HYD, while HCG was strongly promoted by NH/sub 4/HF/sub 2/, Ti isopropoxide, and H/sub 3/BO/sub 3/. The changes in catalytic functionalities are rationalized in terms of different interactions between CoMo phase, support, and additives. 3 tables, 1 figure.« less

Sistema Solar: de la observación de La Tierra a los planetas gigantes y sus lunas

NASA Astrophysics Data System (ADS)

Rodrigo, R.

La fotoquímica tiene un papel principal en la composición de las atmósferas planetarias. Se examinan diferentes procesos fotoquímicos tanto para atmósferas oxidadas como reductoras, poniendo un especial énfasis en los ciclos químicos más importantes. En este sentido, se presentan diferentes ciclos químicos capaces de producir hidrocarbonos y nitrilos en atmósferas reductoras, así como aquellos capaces de mantener las proporciones de mezcla de las moléculas que contienen oxígeno, tales como CO2, O2 y H2O. También se analizan otros procesos importantes tales como la condensación y procesos de sputtering y de sublimación que han de tenerse en cuenta cuando se realizan modelos sobre la composición atmosférica.

Sky Observation with the Use of the Software Stellarium for Teaching Astronomy in Classes of Youth and Adult Education. (Spanish Title: Observación del Cielo con la Utilización del Software Stellarium en Las Clases de Educación de Jóvenes y Adultos.) Observação do Céu Aliada À Utilização do Software Stellarium no Ensino de Astronomia em Turmas de Educação de Jovens e Adultos (EJA)

NASA Astrophysics Data System (ADS)

Oliveira Bernardes, Adriana

2010-12-01

The aim of this paper is to present a project developed through a partnership between the Astronomy Club of Itaocara Marcos Pontes (CAIMP) and Jaime de Souza Queiroz College, both located in the town of Itaocara, in the Northwest Fluminense, to disseminate Astronomy in adult education (Education for Youth and Adult). Given the interdisciplinary nature of Astronomy, we have developed this work to motivate the learning of this science by students in adult education, who attend the subjects Chemistry, Physics and Biology. Initially, we conducted a research in the school to assess the prior knowledge of Astronomy class of adult education, noting that there is little knowledge of basic concepts of the discipline. With these data, we were able to elaborate several activities that would enable a greater involvement of students with this science, performing in the school a work of improvement of scientific literacy, whose activities will be presented in this article. El objetivo de este artículo es presentar los resultados de un proyecto realizado por el Club de Astronomía de Itaocara "Marcos Pontes" (CAIMP), conjuntamente con el Colegio Estatal" Jaime de Souza Queiroz", ambos de la ciudad de Itaocara (Noroeste Fluminense - RJ, Brasil), para la difusión de la Astronomía entre los estudiantes, tanto adultos como adolescentes. Teniendo en cuenta la naturaleza interdisciplinaria de la Astronomía, se determinó motivar el estudio de esta ciencia en los estudiantes adultos de nivel secundario matriculados en las asignaturas de Química, Física y Biología. Como primer paso, se investigó el grado de conocimiento sobre astronomía del estudiante. Este estudio inicial mostró niveles de conocimiento muy bajos de los conceptos básicos de esta ciencia, muchos de los cuales deberían haber sido asimilados dentro del plan curricular del curso de Física. Este estudio previo permitió determinar las actividades adecuadas para promover un mayor envolvimiento de los estudiantes en las ciencias, o sea, elaborar y desarrollar un plan de alfabetización científica. Se describe en detalle este plan, las actividades realizadas y los resultados obtenidos hasta el presente. O objetivo do presente artigo é apresentar um projeto desenvolvido através de parceria entre o Clube de Astronomia de Itaocara Marcos Pontes (CAIMP) e o Colégio Estadual Jaime Queiroz de Souza, ambos localizados na cidade de Itaocara, no Noroeste Fluminense, no sentido de divulgar junto às turmas de EJA (Ensino de Jovens e Adultos) a disciplina Astronomia. Conhecendo o caráter interdisciplinar da Astronomia, desenvolvemos este trabalho para motivar o aprendizado de Ciências junto a alunos de EJA do Ensino Médio que cursam as disciplinas Química, Física e Biologia. Inicialmente, realizamos na escola pesquisa sobre o conhecimento prévio de Astronomia da turma de EJA, observando que é escasso o conhecimento de conceitos básicos do tema, muitos dos quais deveriam ser assimilados através do conteúdo da disciplina Física. Com esses dados, foi possível elaborar várias atividades que possibilitassem um maior envolvimento dos estudantes com a Ciência, realizando dentro da escola um trabalho de alfabetização científica, cujas atividades serão apresentadas neste artigo.

78 FR 38287 - Bitterroot National Forest, Darby Ranger District, Como Forest Health Project

Federal Register 2010, 2011, 2012, 2013, 2014

2013-06-26

... DEPARTMENT OF AGRICULTURE Forest Service Bitterroot National Forest, Darby Ranger District, Como Forest Health Project AGENCY: Forest Service. ACTION: Notice; Correction. SUMMARY: The Department of Agriculture (USDA), Forest Service, Bitterroot National Forest, Darby Ranger District published a document in...

78 FR 36163 - Bitterroot National Forest, Darby Ranger District, Como Forest Health Project

Federal Register 2010, 2011, 2012, 2013, 2014

2013-06-17

... Lake Como and Lost Horse Roads, about XX miles northwest of Darby in Ravalli County, Montana. The... Lost Horse Road, about three miles northwest of Darby, Montana (R22W,T4N, Sec. 13, 24, 25, 36; R21W,T4N...

Autism spectrum disorders: an updated guide for genetic counseling.

PubMed

Griesi-Oliveira, Karina; Sertié, Andréa Laurato

2017-01-01

Autism spectrum disorder is a complex and genetically heterogeneous disorder, which has hampered the identification of the etiological factors in each patient and, consequently, the genetic counseling for families at risk. However, in the last decades, the remarkable advances in the knowledge of genetic aspects of autism based on genetic and molecular research, as well as the development of new molecular diagnostic tools, have substantially changed this scenario. Nowadays, it is estimated that using the currently available molecular tests, a potential underlying genetic cause can be identified in nearly 25% of cases. Combined with clinical assessment, prenatal history evaluation and investigation of other physiological aspects, an etiological explanation for the disease can be found for approximately 30 to 40% of patients. Therefore, in view of the current knowledge about the genetic architecture of autism spectrum disorder, which has contributed for a more precise genetic counseling, and of the potential benefits that an etiological investigation can bring to patients and families, molecular genetic investigation has become increasingly important. Here, we discuss the current view of the genetic architecture of autism spectrum disorder, and list the main associated genetic alterations, the available molecular tests and the key aspects for the genetic counseling of these families. RESUMO O transtorno do espectro autista é um distúrbio complexo e geneticamente heterogêneo, o que sempre dificultou a identificação de sua etiologia em cada paciente em particular e, por consequência, o aconselhamento genético das famílias. Porém, nas últimas décadas, o acúmulo crescente de conhecimento oriundo das pesquisas sobre os aspectos genéticos e moleculares desta doença, assim como o desenvolvimento de novas ferramentas de diagnóstico molecular, tem mudado este cenário de forma substancial. Atualmente, estima-se que, por meio de testes moleculares, é possível detectar uma alteração genética potencialmente causal em cerca de 25% dos casos. Considerando-se também a avaliação clínica, a história pré-natal e a investigação de outros aspectos fisiológicos, pode-se atribuir uma etiologia para aproximadamente 30 a 40% dos pacientes. Assim, em vista do conhecimento atual sobre a arquitetura genética do transtorno do espectro autista, que tem tornado o aconselhamento genético cada vez mais preciso, e dos potenciais benefícios que a investigação etiológica pode trazer aos pacientes e familiares, tornam-se cada vez mais importantes os testes genéticos moleculares. Apresentamos aqui uma breve discussão sobre a visão atual da arquitetura genética dos transtornos do espectro autista, listando as principais alterações genéticas associadas, os testes moleculares disponíveis e os principais aspectos a se considerar para o aconselhamento genético destas famílias.

Cultural adaptation and the Clavien-Dindo surgical complications classification translated to Brazilian Portuguese.

PubMed

Moreira, Luis Fernando; Pessôa, Marcelo Castro Marçal; Mattana, Diego Sachet; Schmitz, Fernando Fernandes; Volkweis, Bernardo Silveira; Antoniazzi, Jorge Luiz; Ribeiro, Liacyr

2016-01-01

to generate a translated and validated version of the Clavien-Dindo Classification of Surgical Complications (CDC) to Brazilian Portuguese (CDC-BR). the process of translation and adaptation followed the guideline of Beaton et al., 2000. We divided 76 participating surgeons, in different levels of experience, from the Department Surgery of the Hospital de Clínicas de Porto Alegre, into two groups: Group I applied the original version (CDC, n=36);r Group II used the modified version (CDC-BR, n=40). Each group classified 15 clinical cases of surgical complications. We compared performance between the groups (Mann-Whitney test) relating to the level of experience of the surgeon (Kruskal-Wallis test), considering p value <0.05 as significant. the performance of the Group II (CDC-BR) was higher, with 85% accuracy, compared with 79% of Group I (CDC), p-value =0.012. The performance of the groups as for surgeons experience displayed p=0.171 for Group I, p=0.528 for Group II, and p=0.135 for overall performance. we produced a translated and validated version of the CDC for Brazilian Portuguese. The instrument will be a useful tool in the production of evidence on surgical outcomes. gerar uma versão traduzida e validada da Classificação de Complicações Cirúrgicas de Clavien-Dindo (CCD) para o Português-Brasileiro (CCD-BR). o processo de tradução e adaptação seguiu a diretriz de Beaton et al., de 2000. Formaram-se dois grupos, Grupo I, que utilizou a versão original (CCD, n=36) testado em relação ao Grupo II, com a versão modificada (CCD-BR, n=40), com um total de 76 cirurgiões participantes em níveis de experiência distintos do Departamento de Cirurgia do Hospital de Clínicas de Porto Alegre. Quinze casos clínicos de complicações cirúrgicas foram classificados em cada grupo. Comparou-se o desempenho entre grupos (teste de Mann-Whitney) relacionando ao nível de experiência dos cirurgiões (teste de Kruskal-Wallis). Valor de p<0,05 como significativo. o desempenho do Grupo II (CCD-BR) foi superior, com 85% de acertos, contra 79% do Grupo I (CCD), p-valor=0,012 do teste de Mann-Whitney. O desempenho dos grupos em relação à experiência dos cirurgiões foi p-valor=0,171 para o Grupo I, p-valor=0,528 para o Grupo II, e p-valor=0,135 para o desempenho geral, teste de Kruskal-Wallis. foi produzida uma versão traduzida e validada da CCD para o Português-Brasileiro. O instrumento produzido será ferramenta útil na produção de evidências sobre os resultados cirúrgicos.

Good practices in collecting umbilical cord and placental blood.

PubMed

Lopes, Lauren Auer; Bernardino, Elizabeth; Crozeta, Karla; Guimarães, Paulo Ricardo Bittencourt

2016-08-18

to identify the factors related to the quality of umbilical cord and placental blood specimens, and define best practices for their collection in a government bank of umbilical cord and placental blood. this was a descriptive study, quantitative approach, performed at a government umbilical cord and placental blood bank, in two steps: 1) verification of the obstetric, neonatal and operational factors, using a specific tool for gathering data as non-participant observers; 2) definition of best practices by grouping non-conformities observed before, during and after blood collection. The data was analyzed using descriptive statistics and the following statistical software: Statistica(r) and R(r). while there was a correlation with obstetrical and neonatal factors, there was a larger correlation with operational factors, resulting in the need to adjust the professional practices of the nursing staff and obstetrical team involved in collecting this type of blood. Based on these non-conformities we defined best practices for nurses before, during and after blood collection. the best practices defined in this study are an important management tool for the work of nurses in obtaining blood specimens of high cell quality. identificar fatores relacionados à qualidade das amostras do sangue de cordão umbilical e placentário e definir boas práticas para sua coleta em um banco público de sangue de cordão umbilical e placentário. pesquisa descritiva, abordagem quantitativa, realizada em um banco público de sangue de cordão umbilical e placentário, desenvolvida em duas etapas: 1) verificação dos fatores obstétricos, neonatais e operacionais, obtidos por coleta em instrumento próprio e observação não participante; 2) definição das boas práticas, por meio do agrupamento de não-conformidades observadas antes, durante e após a coleta do sangue. Os dados foram analisados por meio da estatística descritiva, utilizando-se dos softwares Statistica(r) e R(r). houve correlação da influência dos fatores obstétricos e neonatais em menor escala quando comparados aos fatores operacionais, resultando na necessidade de readequar a prática profissional do enfermeiro e da equipe obstétrica envolvida no processo da coleta desse tipo de sangue. A partir das não-conformidades foram definidas boas práticas para o enfermeiro antes, durante e após a coleta. as boas práticas definidas neste estudo são importante ferramenta gerencial para o trabalho do enfermeiro na obtenção de amostras de sangue com alta qualidade celular. identificar factores relacionados a la calidad de las muestras de la sangre del cordón umbilical y de la placenta y definir buenas prácticas para su recolección en un banco público de sangre del cordón umbilical y de la placenta. investigación - descriptiva, abordaje cuantitativo, realizada en un banco público de sangre - del cordón umbilical y de la placenta, desarrollada en dos etapas: 1) verificación de los factores obstétricos, neonatales y operacionales, obtenidos por recolección con instrumento propio y observación no participante; 2) definición de las buenas prácticas, por medio del agrupamiento de no-conformidades observadas antes, durante y después de la recolección de la sangre. Los datos fueron analizados por medio de la estadística descriptiva, utilizando los softwares Statistica(r) y R(r). hubo correlación de la influencia de los factores obstétricos y neonatales en menor escala cuando comparados a los factores operacionales, resultando en la necesidad de readecuar la práctica profesional del enfermero y del equipo obstétrico que participa en el proceso de la recolección de ese tipo de sangre. A partir de las no-conformidades fueron definidas buenas prácticas para el enfermero antes, durante y después de la recolección. las buenas prácticas definidas en este estudio son importante herramienta administrativa para el trabajo del enfermero en la obtención de muestras de sangre con alta calidad celular.

Office Computer Software: A Comprehensive Review of Software Programs.

ERIC Educational Resources Information Center

Secretary, 1992

1992-01-01

Describes types of software including system software, application software, spreadsheets, accounting software, graphics packages, desktop publishing software, database, desktop and personal information management software, project and records management software, groupware, and shareware. (JOW)

Recent DDT and PCB contamination in the sediment and biota of the Como Bay (Lake Como, Italy).

PubMed

Bettinetti, R; Quadroni, S; Boggio, E; Galassi, S

2016-01-15

Due to its peculiar geographical and morphological characteristics, Lake Como (Northern Italy) represents an interesting study-case for investigating the sub-basin scale circulation of persistent organic pollutants (POPs) that, despite being banned since the 1970s, have reached surprisingly high concentrations in some southern alpine lakes as a consequence of their release from melting glaciers in recent years. In particular, the Como Bay, which is located in the city of Como, seems noteworthy because its waters have a longer residence time than the other areas of the lake. The analyses of the historical concentration of PCBs, pp′DDT and its metabolites in a sediment core sampled from the Como Bay covering a time-period from their ban to recent times, showed that the DDTs have never experienced a significant (p < 0.05) decrease over time, with concentrations of the most abundant homologue, pp′DDE, ranging from 27 to 75 ng g(-1) d.w. Conversely PCBs significantly (p < 0.05) decreased towards recent times, reaching concentrations around 80 ng g(-1) d.w. The contribution of high altitude and local sources was recorded also in the food web: both zooplankton and the zooplanktivorous fish agone were mainly contaminated by pp′DDE (81.4 ng g(-1) w.w. and 534.6 ng g(-1) w.w. respectively) and by the PCB metabolite hexa-CB (449.7 ng g(-1) w.w. and 1672.1 ng g(-1) w.w. respectively). The DDT concentrations in the agone (sampled during the years 2006–2009) never exceeded the limits for human consumption in Italy, while concentrations of six selected PCBs exceeded human health advisory recommendations in one of the fish samples analysed, when it was approximately two times higher than the recommended value of 125 ng g(-1) w.w.

Software Past, Present, and Future: Views from Government, Industry and Academia

NASA Technical Reports Server (NTRS)

Holcomb, Lee; Page, Jerry; Evangelist, Michael

2000-01-01

Views from the NASA CIO NASA Software Engineering Workshop on software development from the past, present, and future are presented. The topics include: 1) Software Past; 2) Software Present; 3) NASA's Largest Software Challenges; 4) 8330 Software Projects in Industry Standish Groups 1994 Report; 5) Software Future; 6) Capability Maturity Model (CMM): Software Engineering Institute (SEI) levels; 7) System Engineering Quality Also Part of the Problem; 8) University Environment Trends Will Increase the Problem in Software Engineering; and 9) NASA Software Engineering Goals.

Space Flight Software Development Software for Intelligent System Health Management

NASA Technical Reports Server (NTRS)

Trevino, Luis C.; Crumbley, Tim

2004-01-01

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

48 CFR 227.7202 - Commercial computer software and commercial computer software documentation.

Code of Federal Regulations, 2014 CFR

2014-10-01

... software and commercial computer software documentation. 227.7202 Section 227.7202 Federal Acquisition... REQUIREMENTS PATENTS, DATA, AND COPYRIGHTS Rights in Computer Software and Computer Software Documentation 227.7202 Commercial computer software and commercial computer software documentation. ...

48 CFR 227.7203 - Noncommercial computer software and noncommercial computer software documentation.

Code of Federal Regulations, 2012 CFR

2012-10-01

... software and noncommercial computer software documentation. 227.7203 Section 227.7203 Federal Acquisition... REQUIREMENTS PATENTS, DATA, AND COPYRIGHTS Rights in Computer Software and Computer Software Documentation 227.7203 Noncommercial computer software and noncommercial computer software documentation. ...

48 CFR 227.7203 - Noncommercial computer software and noncommercial computer software documentation.

Code of Federal Regulations, 2011 CFR

2011-10-01

... software and noncommercial computer software documentation. 227.7203 Section 227.7203 Federal Acquisition... REQUIREMENTS PATENTS, DATA, AND COPYRIGHTS Rights in Computer Software and Computer Software Documentation 227.7203 Noncommercial computer software and noncommercial computer software documentation. ...

48 CFR 227.7203 - Noncommercial computer software and noncommercial computer software documentation.

Code of Federal Regulations, 2013 CFR

2013-10-01

... software and noncommercial computer software documentation. 227.7203 Section 227.7203 Federal Acquisition... REQUIREMENTS PATENTS, DATA, AND COPYRIGHTS Rights in Computer Software and Computer Software Documentation 227.7203 Noncommercial computer software and noncommercial computer software documentation. ...

48 CFR 227.7202 - Commercial computer software and commercial computer software documentation.

Code of Federal Regulations, 2013 CFR

2013-10-01

... software and commercial computer software documentation. 227.7202 Section 227.7202 Federal Acquisition... REQUIREMENTS PATENTS, DATA, AND COPYRIGHTS Rights in Computer Software and Computer Software Documentation 227.7202 Commercial computer software and commercial computer software documentation. ...

48 CFR 227.7203 - Noncommercial computer software and noncommercial computer software documentation.

Code of Federal Regulations, 2014 CFR

2014-10-01

... software and noncommercial computer software documentation. 227.7203 Section 227.7203 Federal Acquisition... REQUIREMENTS PATENTS, DATA, AND COPYRIGHTS Rights in Computer Software and Computer Software Documentation 227.7203 Noncommercial computer software and noncommercial computer software documentation. ...

48 CFR 227.7202 - Commercial computer software and commercial computer software documentation.

Code of Federal Regulations, 2011 CFR

2011-10-01

... software and commercial computer software documentation. 227.7202 Section 227.7202 Federal Acquisition... REQUIREMENTS PATENTS, DATA, AND COPYRIGHTS Rights in Computer Software and Computer Software Documentation 227.7202 Commercial computer software and commercial computer software documentation. ...

48 CFR 227.7202 - Commercial computer software and commercial computer software documentation.

Code of Federal Regulations, 2010 CFR

2010-10-01

... software and commercial computer software documentation. 227.7202 Section 227.7202 Federal Acquisition... REQUIREMENTS PATENTS, DATA, AND COPYRIGHTS Rights in Computer Software and Computer Software Documentation 227.7202 Commercial computer software and commercial computer software documentation. ...

48 CFR 227.7202 - Commercial computer software and commercial computer software documentation.

Code of Federal Regulations, 2012 CFR

2012-10-01

... software and commercial computer software documentation. 227.7202 Section 227.7202 Federal Acquisition... REQUIREMENTS PATENTS, DATA, AND COPYRIGHTS Rights in Computer Software and Computer Software Documentation 227.7202 Commercial computer software and commercial computer software documentation. ...

48 CFR 227.7203 - Noncommercial computer software and noncommercial computer software documentation.

Code of Federal Regulations, 2010 CFR

2010-10-01

... software and noncommercial computer software documentation. 227.7203 Section 227.7203 Federal Acquisition... REQUIREMENTS PATENTS, DATA, AND COPYRIGHTS Rights in Computer Software and Computer Software Documentation 227.7203 Noncommercial computer software and noncommercial computer software documentation. ...

Software system safety

NASA Technical Reports Server (NTRS)

Uber, James G.

1988-01-01

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

Helenistic Encomium: A Reflection on Comics and Rhetoric

ERIC Educational Resources Information Center

Helms, Jason

2009-01-01

This video reflection starts in a presentation on comics at the Thomas R. Watson Conference last October, which prompted the author to explore the etymology of cosmos and comos through an alternate reading of Gorgias' "Encomium of Helen". The author then works with comos, as revelry, to offer thoughts on comics as a form of multimodal composition…

DESAFÍOS ÉTICOS DE LA INVESTIGACIÓN CON ANIMALES, MANIPULACIÓN GENÉTICA

PubMed Central

Yunta, Eduardo Rodríguez

2012-01-01

En la investigación con animales existen cuestionamientos éticos tanto en el uso como modelos de enfermedades humanas y requisito previo para ensayos en humanos como en la introducción de modificaciones genéticas. Algunos de estos cuestionamientos son: no representar exactamente la condición humana como modelos, realizar pruebas de toxicidad con grave daño para los animales, alterar su naturaleza mediante modificaciones genéticas, riesgos de la introducción de organismos genéticamente modificados. El uso de animales en investigación para beneficio humano, impone al ser humano la responsabilidad moral de respetarlo, no haciéndoles sufrir innecesariamente, al estar trabajando con seres vivientes y sentientes. PMID:23338641

Cúmulos globulares como trazadores de bimodalidad estelar en galaxias cD

NASA Astrophysics Data System (ADS)

Forte, J. C.

Se muestra que tanto la forma de los perfiles de brillo como de color observados en dos galaxias arquetípicas de tipo cD (NGC 1399 y NGC 4486) son compatibles con la presencia de poblaciones estelares bi-modales que comparten la misma distribución espacial y composición química de las familias dominantes de cúmulos globulares asociadas con ellas. El modelo resultante también predice una variación de la frecuencia específica de los cúmulos como función del radio galactocéntrico. Se discute este resultado en el contexto de una variedad de escenarios astrofísicos que intentan describir la formación de galaxias cD.

48 CFR 227.7203-16 - Providing computer software or computer software documentation to foreign governments, foreign...

Code of Federal Regulations, 2011 CFR

2011-10-01

... software or computer software documentation to foreign governments, foreign contractors, or international... Rights in Computer Software and Computer Software Documentation 227.7203-16 Providing computer software or computer software documentation to foreign governments, foreign contractors, or international...

48 CFR 227.7203-16 - Providing computer software or computer software documentation to foreign governments, foreign...

Code of Federal Regulations, 2013 CFR

2013-10-01

... software or computer software documentation to foreign governments, foreign contractors, or international... Rights in Computer Software and Computer Software Documentation 227.7203-16 Providing computer software or computer software documentation to foreign governments, foreign contractors, or international...

48 CFR 227.7203-16 - Providing computer software or computer software documentation to foreign governments, foreign...

Code of Federal Regulations, 2012 CFR

2012-10-01

... software or computer software documentation to foreign governments, foreign contractors, or international... Rights in Computer Software and Computer Software Documentation 227.7203-16 Providing computer software or computer software documentation to foreign governments, foreign contractors, or international...

48 CFR 227.7203-16 - Providing computer software or computer software documentation to foreign governments, foreign...

Code of Federal Regulations, 2014 CFR

2014-10-01

... software or computer software documentation to foreign governments, foreign contractors, or international... Rights in Computer Software and Computer Software Documentation 227.7203-16 Providing computer software or computer software documentation to foreign governments, foreign contractors, or international...

48 CFR 227.7203-16 - Providing computer software or computer software documentation to foreign governments, foreign...

Code of Federal Regulations, 2010 CFR

2010-10-01

... software or computer software documentation to foreign governments, foreign contractors, or international... Rights in Computer Software and Computer Software Documentation 227.7203-16 Providing computer software or computer software documentation to foreign governments, foreign contractors, or international...

Avoidable Software Procurements

DTIC Science & Technology

2012-09-01

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

48 CFR 227.7203-15 - Subcontractor rights in computer software or computer software documentation.

Code of Federal Regulations, 2012 CFR

2012-10-01

... computer software or computer software documentation. 227.7203-15 Section 227.7203-15 Federal Acquisition... REQUIREMENTS PATENTS, DATA, AND COPYRIGHTS Rights in Computer Software and Computer Software Documentation 227.7203-15 Subcontractor rights in computer software or computer software documentation. (a...

48 CFR 227.7203-15 - Subcontractor rights in computer software or computer software documentation.

Code of Federal Regulations, 2014 CFR

2014-10-01

... computer software or computer software documentation. 227.7203-15 Section 227.7203-15 Federal Acquisition... REQUIREMENTS PATENTS, DATA, AND COPYRIGHTS Rights in Computer Software and Computer Software Documentation 227.7203-15 Subcontractor rights in computer software or computer software documentation. (a...

48 CFR 227.7203-15 - Subcontractor rights in computer software or computer software documentation.

Code of Federal Regulations, 2010 CFR

2010-10-01

... computer software or computer software documentation. 227.7203-15 Section 227.7203-15 Federal Acquisition... REQUIREMENTS PATENTS, DATA, AND COPYRIGHTS Rights in Computer Software and Computer Software Documentation 227.7203-15 Subcontractor rights in computer software or computer software documentation. (a...

48 CFR 227.7203-15 - Subcontractor rights in computer software or computer software documentation.

Code of Federal Regulations, 2011 CFR

2011-10-01

... computer software or computer software documentation. 227.7203-15 Section 227.7203-15 Federal Acquisition... REQUIREMENTS PATENTS, DATA, AND COPYRIGHTS Rights in Computer Software and Computer Software Documentation 227.7203-15 Subcontractor rights in computer software or computer software documentation. (a...

48 CFR 227.7203-15 - Subcontractor rights in computer software or computer software documentation.

Code of Federal Regulations, 2013 CFR

2013-10-01

... computer software or computer software documentation. 227.7203-15 Section 227.7203-15 Federal Acquisition... REQUIREMENTS PATENTS, DATA, AND COPYRIGHTS Rights in Computer Software and Computer Software Documentation 227.7203-15 Subcontractor rights in computer software or computer software documentation. (a...

48 CFR 227.7202-3 - Rights in commercial computer software or commercial computer software documentation.

Code of Federal Regulations, 2010 CFR

2010-10-01

... computer software or commercial computer software documentation. 227.7202-3 Section 227.7202-3 Federal... CONTRACTING REQUIREMENTS PATENTS, DATA, AND COPYRIGHTS Rights in Computer Software and Computer Software Documentation 227.7202-3 Rights in commercial computer software or commercial computer software documentation...

48 CFR 227.7202-3 - Rights in commercial computer software or commercial computer software documentation.

Code of Federal Regulations, 2011 CFR

2011-10-01

... computer software or commercial computer software documentation. 227.7202-3 Section 227.7202-3 Federal... CONTRACTING REQUIREMENTS PATENTS, DATA, AND COPYRIGHTS Rights in Computer Software and Computer Software Documentation 227.7202-3 Rights in commercial computer software or commercial computer software documentation...

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

Code of Federal Regulations, 2012 CFR

2012-10-01

... 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 Documentation 227.7203-2 Acquisition of noncommercial computer software and computer software documentation. (a...

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

Code of Federal Regulations, 2011 CFR

2011-10-01

... 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 Documentation 227.7203-2 Acquisition of noncommercial computer software and computer software documentation. (a...

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

Code of Federal Regulations, 2014 CFR

2014-10-01

... 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 Documentation 227.7203-2 Acquisition of noncommercial computer software and computer software documentation. (a...

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

Code of Federal Regulations, 2014 CFR

2014-10-01

... 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 marking of computer software or computer software documentation to be furnished with restrictive markings...

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

Code of Federal Regulations, 2010 CFR

2010-10-01

... 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 Documentation 227.7203-2 Acquisition of noncommercial computer software and computer software documentation. (a...

48 CFR 227.7202-3 - Rights in commercial computer software or commercial computer software documentation.

Code of Federal Regulations, 2013 CFR

2013-10-01

... computer software or commercial computer software documentation. 227.7202-3 Section 227.7202-3 Federal... CONTRACTING REQUIREMENTS PATENTS, DATA, AND COPYRIGHTS Rights in Computer Software and Computer Software Documentation 227.7202-3 Rights in commercial computer software or commercial computer software documentation...

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

Code of Federal Regulations, 2011 CFR

2011-10-01

... 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 marking of computer software or computer software documentation to be furnished with restrictive markings...

48 CFR 227.7202-3 - Rights in commercial computer software or commercial computer software documentation.

Code of Federal Regulations, 2014 CFR

2014-10-01

... computer software or commercial computer software documentation. 227.7202-3 Section 227.7202-3 Federal... CONTRACTING REQUIREMENTS PATENTS, DATA, AND COPYRIGHTS Rights in Computer Software and Computer Software Documentation 227.7202-3 Rights in commercial computer software or commercial computer software documentation...

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

Code of Federal Regulations, 2012 CFR

2012-10-01

... 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 marking of computer software or computer software documentation to be furnished with restrictive markings...

48 CFR 227.7202-3 - Rights in commercial computer software or commercial computer software documentation.

Code of Federal Regulations, 2012 CFR

2012-10-01

... computer software or commercial computer software documentation. 227.7202-3 Section 227.7202-3 Federal... CONTRACTING REQUIREMENTS PATENTS, DATA, AND COPYRIGHTS Rights in Computer Software and Computer Software Documentation 227.7202-3 Rights in commercial computer software or commercial computer software documentation...

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

Code of Federal Regulations, 2010 CFR

2010-10-01

... 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 marking of computer software or computer software documentation to be furnished with restrictive markings...

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

Code of Federal Regulations, 2013 CFR

2013-10-01

... 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 marking of computer software or computer software documentation to be furnished with restrictive markings...

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

Code of Federal Regulations, 2013 CFR

2013-10-01

... 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 Documentation 227.7203-2 Acquisition of noncommercial computer software and computer software documentation. (a...

Software analysis handbook: Software complexity analysis and software reliability estimation and prediction

NASA Technical Reports Server (NTRS)

Lee, Alice T.; Gunn, Todd; Pham, Tuan; Ricaldi, Ron

1994-01-01

This handbook documents the three software analysis processes the Space Station Software Analysis team uses to assess space station software, including their backgrounds, theories, tools, and analysis procedures. Potential applications of these analysis results are also presented. The first section describes how software complexity analysis provides quantitative information on code, such as code structure and risk areas, throughout the software life cycle. Software complexity analysis allows an analyst to understand the software structure, identify critical software components, assess risk areas within a software system, identify testing deficiencies, and recommend program improvements. Performing this type of analysis during the early design phases of software development can positively affect the process, and may prevent later, much larger, difficulties. The second section describes how software reliability estimation and prediction analysis, or software reliability, provides a quantitative means to measure the probability of failure-free operation of a computer program, and describes the two tools used by JSC to determine failure rates and design tradeoffs between reliability, costs, performance, and schedule.

48 CFR 227.7203-3 - Early identification of computer software or computer software documentation to be furnished to...

Code of Federal Regulations, 2010 CFR

2010-10-01

... computer software or computer software documentation to be furnished to the Government with restrictions on..., DATA, AND COPYRIGHTS Rights in Computer Software and Computer Software Documentation 227.7203-3 Early identification of computer software or computer software documentation to be furnished to the Government with...

48 CFR 227.7203-3 - Early identification of computer software or computer software documentation to be furnished to...

Code of Federal Regulations, 2012 CFR

2012-10-01

... computer software or computer software documentation to be furnished to the Government with restrictions on..., DATA, AND COPYRIGHTS Rights in Computer Software and Computer Software Documentation 227.7203-3 Early identification of computer software or computer software documentation to be furnished to the Government with...

48 CFR 227.7203-3 - Early identification of computer software or computer software documentation to be furnished to...

Code of Federal Regulations, 2011 CFR

2011-10-01

... computer software or computer software documentation to be furnished to the Government with restrictions on..., DATA, AND COPYRIGHTS Rights in Computer Software and Computer Software Documentation 227.7203-3 Early identification of computer software or computer software documentation to be furnished to the Government with...

48 CFR 227.7203-3 - Early identification of computer software or computer software documentation to be furnished to...

Code of Federal Regulations, 2013 CFR

2013-10-01

... computer software or computer software documentation to be furnished to the Government with restrictions on..., DATA, AND COPYRIGHTS Rights in Computer Software and Computer Software Documentation 227.7203-3 Early identification of computer software or computer software documentation to be furnished to the Government with...

48 CFR 227.7203-3 - Early identification of computer software or computer software documentation to be furnished to...

Code of Federal Regulations, 2014 CFR

2014-10-01

... computer software or computer software documentation to be furnished to the Government with restrictions on..., DATA, AND COPYRIGHTS Rights in Computer Software and Computer Software Documentation 227.7203-3 Early identification of computer software or computer software documentation to be furnished to the Government with...

Automated Reuse of Scientific Subroutine Libraries through Deductive Synthesis

NASA Technical Reports Server (NTRS)

Lowry, Michael R.; Pressburger, Thomas; VanBaalen, Jeffrey; Roach, Steven

1997-01-01

Systematic software construction offers the potential of elevating software engineering from an art-form to an engineering discipline. The desired result is more predictable software development leading to better quality and more maintainable software. However, the overhead costs associated with the formalisms, mathematics, and methods of systematic software construction have largely precluded their adoption in real-world software development. In fact, many mainstream software development organizations, such as Microsoft, still maintain a predominantly oral culture for software development projects; which is far removed from a formalism-based culture for software development. An exception is the limited domain of safety-critical software, where the high-assuiance inherent in systematic software construction justifies the additional cost. We believe that systematic software construction will only be adopted by mainstream software development organization when the overhead costs have been greatly reduced. Two approaches to cost mitigation are reuse (amortizing costs over many applications) and automation. For the last four years, NASA Ames has funded the Amphion project, whose objective is to automate software reuse through techniques from systematic software construction. In particular, deductive program synthesis (i.e., program extraction from proofs) is used to derive a composition of software components (e.g., subroutines) that correctly implements a specification. The construction of reuse libraries of software components is the standard software engineering solution for improving software development productivity and quality.

Annotated bibliography of Software Engineering Laboratory literature

NASA Technical Reports Server (NTRS)

Morusiewicz, Linda; Valett, Jon D.

1991-01-01

An annotated bibliography of technical papers, documents, and memorandums produced by or related to the Software Engineering Laboratory is given. More than 100 publications are summarized. These publications cover many areas of software engineering and range from research reports to software documentation. All materials have been grouped into eight general subject areas for easy reference: The Software Engineering Laboratory; The Software Engineering Laboratory: Software Development Documents; Software Tools; Software Models; Software Measurement; Technology Evaluations; Ada Technology; and Data Collection. Subject and author indexes further classify these documents by specific topic and individual author.

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

NASA Technical Reports Server (NTRS)

Campbell, Roy H.; Beckman-Davies, C. S.; Benzinger, L.; Beshers, G.; Laliberte, D.; Render, H.; Sum, R.; Smith, W.; Terwilliger, R.

1986-01-01

Research into software development is required to reduce its production cost and to improve its quality. Modern software systems, such as the embedded software required for NASA's space station initiative, stretch current software engineering techniques. The requirements to build large, reliable, and maintainable software systems increases with time. Much theoretical and practical research is in progress to improve software engineering techniques. One such technique is to build a software system or environment which directly supports the software engineering process, i.e., the SAGA project, comprising the research necessary to design and build a software development which automates the software engineering process. Progress under SAGA is described.

Uso de terreno urbano y rural en Puerto Rico

Treesearch

Sebastian Martinuzzi; William A. Gould; Olga M. Ramos Gonzalez; Maya Quinones; Michael E. Jimenez

2008-01-01

El Proyecto de Analisis de Gap de Puerto Rico (PRGAP) (Gould et al. 2008) desarrollo tres usos de terrenos para Puerto Rico: Urbano, Suburbano, y Rural (Martinuzzi et al. 2007). Estas regiones tambien pueden ser consideradas como urbano, densamente-poblado rural, y escasamente-poblado rural, o como urbano y area silvestre con una interfase de area silvestre-urbana. La...

Domestic violence on children: development and validation of an instrument to evaluate knowledge of health professionals.

PubMed

Oliveira, Lanuza Borges; Soares, Fernanda Amaral; Silveira, Marise Fagundes; Pinho, Lucinéia de; Caldeira, Antônio Prates; Leite, Maísa Tavares de Souza

2016-08-18

to develop and validate an instrument to evaluate the knowledge of health professionals about domestic violence on children. this was a study conducted with 194 physicians, nurses and dentists. A literature review was performed for preparation of the items and identification of the dimensions. Apparent and content validation was performed using analysis of three experts and 27 professors of the pediatric health discipline. For construct validation, Cronbach's alpha was used, and the Kappa test was applied to verify reproducibility. The criterion validation was conducted using the Student's t-test. the final instrument included 56 items; the Cronbach alpha was 0.734, the Kappa test showed a correlation greater than 0.6 for most items, and the Student t-test showed a statistically significant value to the level of 5% for the two selected variables: years of education and using the Family Health Strategy. the instrument is valid and can be used as a promising tool to develop or direct actions in public health and evaluate knowledge about domestic violence on children. elaborar e validar um instrumento para avaliação do conhecimento dos profissionais de saúde sobre a violência doméstica contra a criança. estudo realizado com 194 profissionais médicos, enfermeiros e cirurgiões dentistas. Para elaboração dos itens e identificação das dimensões, realizou-se a revisão da literatura. A validação aparente e de conteúdo foram realizadas por meio da análise de três especialistas e de 27 professores universitários da área de saúde da criança. Para a validação de construto, avaliou-se o coeficiente alfa de Cronbach, e o teste Kappa foi usado para verificar a reprodutibilidade. A validação de critério foi conduzida com uso do teste t-student. o instrumento final apresentou 56 itens, o alfa Cronbach foi de 0,734, o teste Kappa revelou concordância superior a 0,6 para a maioria dos itens, e o teste t-student apresentou valor estatisticamente significante até o nível de 5% para as duas variáveis selecionadas, tempo de formação e tempo na Estratégia Saúde da Família. o instrumento apresentou-se válido e, deste modo , pode ser usado como ferramenta promissora para desenvolver ou direcionar as ações em saúde pública e avaliação do conhecimento sobre a violência doméstica contra a criança. elaborar y validar un instrumento para evaluación del conocimiento de los profesionales de la salud sobre la violencia doméstica ejercida contra el niño. estudio realizado con 194 profesionales: médicos, enfermeros y cirujanos dentistas. Para elaboración de los ítems e identificación de las dimensiones, se realizó una revisión de la literatura. La validación aparente y de contenido fueron realizadas por medio del análisis de tres especialistas y de 27 profesores universitarios del área de la salud del niño. Para la validación de constructo, se evaluó el coeficiente alfa de Cronbach, y la prueba Kappa fue usada para verificar la reproductibilidad. La validación de criterio fue realizada con uso de la prueba t de Student. el instrumento final presentó 56 ítems, el alfa Cronbach fue de 0,734, la prueba Kappa reveló concordancia superior a 0,6 para la mayoría de los ítems, y la prueba t de Student presentó valor estadísticamente significativo hasta el nivel de 5% para las dos variables seleccionadas: tiempo de graduación y tiempo en el programa Estrategia Salud de la Familia. el instrumento se presentó válido y, de ese modo, puede ser usado como herramienta promisora para desarrollar o dirigir acciones de salud pública y evaluar el conocimiento sobre la violencia doméstica contra el niño.

Validation of an instrument for evaluating health care services to ostomized people.

PubMed

Moraes, Juliano Teixeira; Amaral, Carlos Faria Santos; Borges, Eline Lima; Ribeiro, Mauro Souza; Guimarães, Eliete Albano Azevedo

2016-12-08

to develop and validate an array of analysis and judgment for the evaluation of Health Care Services of people with stomas. cross-sectional study in 28 health facilities in the state of Minas Gerais. A descriptive analysis of the instrument and a study of its psychometric properties were performed. We used the Delphi technique for the validation of content and appearance. A psychometric analysis was carried out through the study of the reliability and validity of the measures obtained with the instrument. it was possible to construct an array analysis and judgment with 16 components (with scores from zero to five) grouped according to size and structure and process considered essential to evaluate the service. The results achieved in the reliability for structure and process, through the Cronbach alpha coefficient (α = 0.771 and α = 0.809, respectively), and the validity of content and construct demonstrated good internal consistency and satisfactory validity. An exploratory factor analysis indicated the item "main activity performed in the unit" as a limitation of the scale. the study provides a new tool for the evaluation of structure and process of Health Care Services of a Person with a stoma. desenvolver e validar uma matriz de análise e julgamento para a avaliação de Serviços de Atenção à Saúde da Pessoa Estomizada. estudo seccional em 28 unidades de saúde do estado de Minas Gerais. Foi realizada uma análise descritiva do instrumento e um estudo das suas propriedades psicométricas. Para a validação de conteúdo e de aparência foi utilizada a técnica Delphi. A análise psicométrica foi realizada por meio do estudo da confiabilidade e validade das medidas obtidas com o instrumento. foi possível construir uma matriz de análise e julgamento com 16 componentes (pontuados com escores de zero a cinco) agrupados de acordo com as dimensões estrutura e processo considerados fundamentais para a avaliação do serviço. Os resultados alcançados para a confiabilidade para estrutura e processo, por meio do Coeficiente alfa de Cronbach (α = 0,771 e α = 0,809 respectivamente), e validades de conteúdo e de construto, demonstraram boa consistência interna e satisfatória validade. A análise fatorial exploratória apontou o item "principal atividade realizada na unidade" como limitação da escala. o estudo disponibiliza nova ferramenta para a avaliação de estrutura e processo do Serviço de Atenção à Saúde da Pessoa Ostomizada. desarrollar y validar una matriz de análisis y juzgamiento para la evaluación de Servicios de Atención a la Salud de la Persona Ostomizada. estudio seccional en 28 unidades de salud del estado de Minas Gerais. Fue realizado un análisis descriptivo del instrumento y un estudio de sus propiedades psicométricas. Para la validación de contenido y de apariencia fue utilizada la técnica Delphi. El análisis psicométrico fue realizada por medio del estudio de la confiabilidad y validez de las medidas obtenidas con el instrumento. fue posible construir una matriz de análisis y juzgamiento con 16 componentes (evaluados con puntajes de cero a cinco) agrupados de acuerdo con las dimensiones estructura y proceso considerados fundamentales para la evaluación del servicio. Los resultados alcanzados para la confiabilidad para estructura y proceso, por medio del Coeficiente Alfa de Cronbach (α = 0,771 y α = 0,809 respectivamente), y validez de contenido y de constructo, demostraron buena consistencia interna y satisfactoria validez. El análisis factorial exploratória apuntó el ítem "principal actividad realizada en la unidad" como limitación de la escala. el estudio suministra una nueva herramienta para la evaluación de estructura y proceso del Servicio de Atención a la Salud de la Persona Ostomizada.

Innovation in nursing health care practice: expansion of access in primary health care.

PubMed

Lowen, Ingrid Margareth Voth; Peres, Aida Maris; Ros, Carla da; Poli, Paulo; Faoro, Nilza Teresinha

2017-01-01

analyze the reorganization of the health care practice of nurses as an innovative strategy for expansion of access in primary care. qualitative and quantitative study, which interviewed 32 management and care nurses and collected documentary data from public reports of production of nursing consultations from 2010 to 2014, in a municipality in southern Brazil. Data processing for textual analysis was performed by IRAMUTEQ software; for simple descriptive statistical analysis, the program Excel 2013 was used. in the innovative care practice  class, associated with awareness of change, related to implementation of the FHS, its challenges and advantages, the following subclasses were identified: reorganization of schedules, nursing consultation, physical restructuring of BHUs, and shared consultation. the need to expand access to and valorization of care practice encourages the development of innovative strategies. The protagonism of care needs to be discussed in the various spaces so that each professional carry out the respective role with competence and efficacy. analisar a reorganização da prática assistencial do enfermeiro como estratégia inovadora para ampliação do acesso na atenção primária. estudo qualiquantitativo, tendo sido entrevistados 32 enfermeiros gerenciais e assistenciais e coletados dados documentais de relatórios públicos de produção de consultas dos enfermeiros de 2010 a 2014, num município sul-brasileiro. O processamento dos dados para análise textual foi realizado pelo software IRAMUTEQ; para análise estatística descritiva simples, o programa Excel 2013. na classe prática assistencial inovadora, associada à sensibilização para a mudança, relacionada à implantação da ESF, seus desafios e fortalezas, foram identificadas as subclasses: reorganização das agendas, consulta do enfermeiro, reestruturação física das UBS e consulta compartilhada. a necessidade de ampliar o acesso e valorização da prática assistencial incentiva o desenvolvimento de estratégias inovadoras. O protagonismo do cuidado precisa ser discutido nos diversos espaços a fim de que cada profissional desempenhe seu papel com competência e resolutividade.

AIDS and jail: social representations of women in freedom deprivation situations.

PubMed

Trigueiro, Débora Raquel Soares Guedes; Almeida, Sandra Aparecida de; Monroe, Aline Aparecida; Costa, Gilka Paiva Oliveira; Bezerra, Valéria Peixoto; Nogueira, Jordana de Almeida

2016-01-01

To graspthe AIDS social representations built by freedom-deprived women. Descriptive study with a quali-quantitative approach that involved 174 convicted women in a women's prison in a capital city of the Brazilian northeastern region. Aword-association test was applied in October and November 2014, using AIDS as a stimulus. The corpuswas processed usingIramuteq software. Descending Hierarchical Classification and Correspondence Factor Analysis were applied. The content that comprises the social representation of AIDS was influenced by the prison context, which was pervaded by a lack of assistance, lack of knowledge, discrimination, and suffering that disclosed vulnerability to HIV/AIDS factors such as unprotected sex and object sharing. This underlines the stigma and fear of the illness, in addition to favoring and supporting negative feelings and a sense of rejection. To consider the use of this representational amalgam to ensure a comprehensive, contextualized care can help redirect practices, motivate self-care practices, and reduce prejudiced attitudes. Apreenderas representações sociais sobre a aids construídas por mulheres privadas de liberdade. Estudo descritivo, com abordagem quali-quantitativa que envolveu 174 apenadas de Presídio Feminino situado em capital do nordeste brasileiro. Aplicou-se o Teste de Associação Livre de Palavras, em outubro e novembro de 2014, utilizando-se do estímulo aids. O corpus foi processado pelo software Iramuteq, sendo efetuadas a Classificação Hierárquica Descendente e Análise Fatorial de Correspondência. Os conteúdos que compõem a representação social sobre aids são influenciados pelo contexto prisional, permeado dedesassistência, desconhecimento, discriminação e condições de sofrimento, revelando fatores de vulnerabilidade ao HIV/Aids como atividade sexual desprotegida e compartilhamento de objetos; reiterando o estigma e o temor à doença; e favorecendo e sustentando sentimentos negativos e de rejeição. Considerar este amálgama representacional na garantia de um cuidado integral e contextualizado pode contribuir para redirecionar práticas, motivar condutas de autocuidado e reduzir atitudes preconceituosas.

The social disutility of software ownership.

PubMed

Douglas, David M

2011-09-01

Software ownership allows the owner to restrict the distribution of software and to prevent others from reading the software's source code and building upon it. However, free software is released to users under software licenses that give them the right to read the source code, modify it, reuse it, and distribute the software to others. Proponents of free software such as Richard M. Stallman and Eben Moglen argue that the social disutility of software ownership is a sufficient justification for prohibiting it. This social disutility includes the social instability of disregarding laws and agreements covering software use and distribution, inequality of software access, and the inability to help others by sharing software with them. Here I consider these and other social disutility claims against withholding specific software rights from users, in particular, the rights to read the source code, duplicate, distribute, modify, imitate, and reuse portions of the software within new programs. I find that generally while withholding these rights from software users does cause some degree of social disutility, only the rights to duplicate, modify and imitate cannot legitimately be denied to users on this basis. The social disutility of withholding the rights to distribute the software, read its source code and reuse portions of it in new programs is insufficient to prohibit software owners from denying them to users. A compromise between the software owner and user can minimise the social disutility of withholding these particular rights from users. However, the social disutility caused by software patents is sufficient for rejecting such patents as they restrict the methods of reducing social disutility possible with other forms of software ownership.

Proceedings of the Seventeenth Annual Software Engineering Workshop

NASA Technical Reports Server (NTRS)

1992-01-01

Proceedings of the Seventeenth Annual Software Engineering Workshop are presented. The software Engineering Laboratory (SEL) is an organization sponsored by NASA/Goddard Space Flight Center and created to investigate the effectiveness of software engineering technologies when applied to the development of applications software. Topics covered include: the Software Engineering Laboratory; process measurement; software reuse; software quality; lessons learned; and is Ada dying.

M S MOLECULARES Rumo aos limites da miniaturiza o - (Molecular Magnets - towards the limits of miniaturization)

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

Reis, Mario S; Moreira Dos Santos, Antonio F

Por s culos, acreditou-se que o magnetismo s se manifestava em metais, como aqueles contendo ferro; hoje, a imagem mais comum de um m talvez seja a daquelas plaquinhas flex veis coladas geladeira com propagandas dos mais diversos tipos. O leitor conseguiria imaginar um material puramente org nico daqueles que formam os seres vivos como magn tico? E m s do tamanho de mol culas? fato: ambos existem. Esses novos materiais, conhecidos como magnetos moleculares, descobertos e desenvolvidos em v rios laborat rios do mundo, j re nem longa lista de aplica es, do tratamento do c ncer a refrigeradoresmore » ecol gicos, passando pela transmiss o de eletricidade sem perda de calor e a fabrica o de computadores extremamente velozes.« less

Four applications of a software data collection and analysis methodology

NASA Technical Reports Server (NTRS)

Basili, Victor R.; Selby, Richard W., Jr.

1985-01-01

The evaluation of software technologies suffers because of the lack of quantitative assessment of their effect on software development and modification. A seven-step data collection and analysis methodology couples software technology evaluation with software measurement. Four in-depth applications of the methodology are presented. The four studies represent each of the general categories of analyses on the software product and development process: blocked subject-project studies, replicated project studies, multi-project variation studies, and single project strategies. The four applications are in the areas of, respectively, software testing, cleanroom software development, characteristic software metric sets, and software error analysis.

Third-Party Software's Trust Quagmire.

PubMed

Voas, J; Hurlburt, G

2015-12-01

Current software development has trended toward the idea of integrating independent software sub-functions to create more complete software systems. Software sub-functions are often not homegrown - instead they are developed by unknown 3 rd party organizations and reside in software marketplaces owned or controlled by others. Such software sub-functions carry plausible concern in terms of quality, origins, functionality, security, interoperability, to name a few. This article surveys key technical difficulties in confidently building systems from acquired software sub-functions by calling out the principle software supply chain actors.

Space Station Software Issues

NASA Technical Reports Server (NTRS)

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

1985-01-01

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

Software Acquisition: Evolution, Total Quality Management, and Applications to the Army Tactical Missile System

DTIC Science & Technology

1992-06-01

presents the concept of software Total Quality Management (TQM) which focuses on the entire process of software acquisition, as a partial solution to...software TQM can be applied to software acquisition. Software Development, Software Acquisition, Total Quality management (TQM), Army Tactical Missile

48 CFR 252.227-7014 - Rights in noncommercial computer software and noncommercial computer software documentation.

Code of Federal Regulations, 2013 CFR

2013-10-01

... computer software and noncommercial computer software documentation. 252.227-7014 Section 252.227-7014... Rights in noncommercial computer software and noncommercial computer software documentation. As prescribed in 227.7203-6(a)(1), use the following clause. Rights in Noncommercial Computer Software and...

48 CFR 252.227-7014 - Rights in noncommercial computer software and noncommercial computer software documentation.

Code of Federal Regulations, 2012 CFR

2012-10-01

... computer software and noncommercial computer software documentation. 252.227-7014 Section 252.227-7014... Rights in noncommercial computer software and noncommercial computer software documentation. As prescribed in 227.7203-6(a)(1), use the following clause. Rights in Noncommercial Computer Software and...

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

Code of Federal Regulations, 2014 CFR

2014-10-01

..., and warranty of computer software and computer software documentation. 227.7203-14 Section 227.7203-14... GENERAL CONTRACTING REQUIREMENTS PATENTS, DATA, AND COPYRIGHTS Rights in Computer Software and Computer Software Documentation 227.7203-14 Conformity, acceptance, and warranty of computer software and computer...

48 CFR 252.227-7014 - Rights in noncommercial computer software and noncommercial computer software documentation.

Code of Federal Regulations, 2014 CFR

2014-10-01

... computer software and noncommercial computer software documentation. 252.227-7014 Section 252.227-7014... Rights in noncommercial computer software and noncommercial computer software documentation. As prescribed in 227.7203-6(a)(1), use the following clause. Rights in Noncommercial Computer Software and...

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

Code of Federal Regulations, 2010 CFR

2010-10-01

..., and warranty of computer software and computer software documentation. 227.7203-14 Section 227.7203-14... GENERAL CONTRACTING REQUIREMENTS PATENTS, DATA, AND COPYRIGHTS Rights in Computer Software and Computer Software Documentation 227.7203-14 Conformity, acceptance, and warranty of computer software and computer...

48 CFR 252.227-7014 - Rights in noncommercial computer software and noncommercial computer software documentation.

Code of Federal Regulations, 2011 CFR

2011-10-01

... computer software and noncommercial computer software documentation. 252.227-7014 Section 252.227-7014... Rights in noncommercial computer software and noncommercial computer software documentation. As prescribed in 227.7203-6(a)(1), use the following clause. Rights in Noncommercial Computer Software and...

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

Code of Federal Regulations, 2012 CFR

2012-10-01

..., and warranty of computer software and computer software documentation. 227.7203-14 Section 227.7203-14... GENERAL CONTRACTING REQUIREMENTS PATENTS, DATA, AND COPYRIGHTS Rights in Computer Software and Computer Software Documentation 227.7203-14 Conformity, acceptance, and warranty of computer software and computer...

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

Code of Federal Regulations, 2013 CFR

2013-10-01

..., and warranty of computer software and computer software documentation. 227.7203-14 Section 227.7203-14... GENERAL CONTRACTING REQUIREMENTS PATENTS, DATA, AND COPYRIGHTS Rights in Computer Software and Computer Software Documentation 227.7203-14 Conformity, acceptance, and warranty of computer software and computer...

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

Code of Federal Regulations, 2011 CFR

2011-10-01

..., and warranty of computer software and computer software documentation. 227.7203-14 Section 227.7203-14... GENERAL CONTRACTING REQUIREMENTS PATENTS, DATA, AND COPYRIGHTS Rights in Computer Software and Computer Software Documentation 227.7203-14 Conformity, acceptance, and warranty of computer software and computer...

48 CFR 252.227-7014 - Rights in noncommercial computer software and noncommercial computer software documentation.

Code of Federal Regulations, 2010 CFR

2010-10-01

... computer software and noncommercial computer software documentation. 252.227-7014 Section 252.227-7014... Rights in noncommercial computer software and noncommercial computer software documentation. As prescribed in 227.7203-6(a)(1), use the following clause. Rights in Noncommercial Computer Software and...

Software Quality Assurance Metrics

NASA Technical Reports Server (NTRS)

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.

Populações estelares do bojo galáctico

NASA Astrophysics Data System (ADS)

Escudero, A. V.; Costa, R. D. D.; Maciel, W. J.

2003-08-01

Os estudos mais recentes do bojo galáctico têm enfocado essencialmente as abundâncias químicas de elementos pesados, como o ferro, obtidos a partir das estrelas nas regiões centrais da galáxia. Elementos leves, como hélio, nitrogênio, oxigênio e argônio ainda são pouco estudados nestas regiões, devido à difícil determinação de suas abundâncias a partir de estrelas. Nestas condições as nebulosas planetárias desempenham um importante papel, pois permitem a determinação de abundâncias destes elementos usando técnicas de espectroscopia nebular. Neste trabalho, reportamos a análise das abundâncias químicas de uma nova amostra de nebulosas planetárias do bojo, bem como os resultados preliminares de um código numérico destinado a modelar a evolução química desta região. Usamos como vínculos observacionais os resultados obtidos das nebulosas planetárias, bem como de abundâncias estelares da região do bojo, obtidas da literatura. A partir deste modelo da evolução química e dos vínculos observacionais foi possível fazer um diagnóstico mais preciso das populações que constituem o bojo galáctico. O estudo destas populações que compõem a região central de nossa galáxia é de extrema importância para o maior entendimento da evolução química e dinâmica da galáxia como um todo. Por isto, verificamos a importância dos modelos de formação simples e mista utilizados para explicar características da população da região central da galáxia. Algumas destas características são: uma grande dispersão nos valores das abundâncias químicas e um grande espalhamento nas correlações entre as abundâcias de nitrogênio e oxigênio. Estas peculiaridades são dificilmente reproduzidas por modelos de formação simples, e portanto são importantes indícios da validade dos modelos de formação mista, tais como um rápido colapso do bojo seguido de uma evolução secular. (FAPESP, CNPq)

Software Configuration Management Guidebook

NASA Technical Reports Server (NTRS)

1995-01-01

The growth in cost and importance of software to NASA has caused NASA to address the improvement of software development across the agency. One of the products of this program is a series of guidebooks that define a NASA concept of the assurance processes which are used in software development. The Software Assurance Guidebook, SMAP-GB-A201, issued in September, 1989, provides an overall picture of the concepts and practices of NASA in software assurance. Lower level guidebooks focus on specific activities that fall within the software assurance discipline, and provide more detailed information for the manager and/or practitioner. This is the Software Configuration Management Guidebook which describes software configuration management in a way that is compatible with practices in industry and at NASA Centers. Software configuration management is a key software development process, and is essential for doing software assurance.

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

NASA Technical Reports Server (NTRS)

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.

Product-oriented Software Certification Process for Software Synthesis

NASA Technical Reports Server (NTRS)

Nelson, Stacy; Fischer, Bernd; Denney, Ewen; Schumann, Johann; Richardson, Julian; Oh, Phil

2004-01-01

The purpose of this document is to propose a product-oriented software certification process to facilitate use of software synthesis and formal methods. Why is such a process needed? Currently, software is tested until deemed bug-free rather than proving that certain software properties exist. This approach has worked well in most cases, but unfortunately, deaths still occur due to software failure. Using formal methods (techniques from logic and discrete mathematics like set theory, automata theory and formal logic as opposed to continuous mathematics like calculus) and software synthesis, it is possible to reduce this risk by proving certain software properties. Additionally, software synthesis makes it possible to automate some phases of the traditional software development life cycle resulting in a more streamlined and accurate development process.

Software engineering laboratory series: Annotated bibliography of software engineering laboratory literature

NASA Technical Reports Server (NTRS)

Morusiewicz, Linda; Valett, Jon

1992-01-01

This document is an annotated bibliography of technical papers, documents, and memorandums produced by or related to the Software Engineering Laboratory. More than 100 publications are summarized. These publications cover many areas of software engineering and range from research reports to software documentation. This document has been updated and reorganized substantially since the original version (SEL-82-006, November 1982). All materials have been grouped into eight general subject areas for easy reference: (1) the Software Engineering Laboratory; (2) the Software Engineering Laboratory: Software Development Documents; (3) Software Tools; (4) Software Models; (5) Software Measurement; (6) Technology Evaluations; (7) Ada Technology; and (8) Data Collection. This document contains an index of these publications classified by individual author.

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

NASA Technical Reports Server (NTRS)

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

1987-01-01

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

Annotated bibliography of software engineering laboratory literature

NASA Technical Reports Server (NTRS)

Groves, Paula; Valett, Jon

1990-01-01

An annotated bibliography of technical papers, documents, and memorandums produced by or related to the Software Engineering Laboratory is given. More than 100 publications are summarized. These publications cover many areas of software engineering and range from research reports to software documentation. This document has been updated and reorganized substantially since the original version (SEL-82-006, November 1982). All materials have been grouped into eight general subject areas for easy reference: the Software Engineering Laboratory; the Software Engineering Laboratory-software development documents; software tools; software models; software measurement; technology evaluations; Ada technology; and data collection. Subject and author indexes further classify these documents by specific topic and individual author.

Annotated bibliography of Software Engineering Laboratory literature

NASA Technical Reports Server (NTRS)

Morusiewicz, Linda; Valett, Jon

1993-01-01

This document is an annotated bibliography of technical papers, documents, and memorandums produced by or related to the Software Engineering Laboratory. Nearly 200 publications are summarized. These publications cover many areas of software engineering and range from research reports to software documentation. This document has been updated and reorganized substantially since the original version (SEL-82-006, November 1982). All materials have been grouped into eight general subject areas for easy reference: the Software Engineering Laboratory; the Software Engineering Laboratory: software development documents; software tools; software models; software measurement; technology evaluations; Ada technology; and data collection. This document contains an index of these publications classified by individual author.

Proceedings of the Fourth Symposium on Conference on Dynamics of Cosmic Gases, Varenna Italy (Lake of Como), August 18-30, 1960; ATTI DEL IV SYMPOSIUM SULLA DINAMICA DEL GAS COSMICO, VARENNA SUL LAGO DI COMO 18-30 AGOSTO 1960

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

None

1961-01-01

Fifteen papers are included: separate abstracts have been prepared for l0. A single abstract has been prepared to cover the remaining 5 papers, which consist of observational studies. Extensive discussions are included. (T.F.H.)

48 CFR 227.7203-8 - Deferred delivery and deferred ordering of computer software and computer software documentation.

Code of Federal Regulations, 2011 CFR

2011-10-01

... deferred ordering of computer software and computer software documentation. 227.7203-8 Section 227.7203-8... GENERAL CONTRACTING REQUIREMENTS PATENTS, DATA, AND COPYRIGHTS Rights in Computer Software and Computer Software Documentation 227.7203-8 Deferred delivery and deferred ordering of computer software and computer...

48 CFR 227.7203-8 - Deferred delivery and deferred ordering of computer software and computer software documentation.

Code of Federal Regulations, 2012 CFR

2012-10-01

... deferred ordering of computer software and computer software documentation. 227.7203-8 Section 227.7203-8... GENERAL CONTRACTING REQUIREMENTS PATENTS, DATA, AND COPYRIGHTS Rights in Computer Software and Computer Software Documentation 227.7203-8 Deferred delivery and deferred ordering of computer software and computer...

48 CFR 227.7203-8 - Deferred delivery and deferred ordering of computer software and computer software documentation.

Code of Federal Regulations, 2014 CFR

2014-10-01

... deferred ordering of computer software and computer software documentation. 227.7203-8 Section 227.7203-8... GENERAL CONTRACTING REQUIREMENTS PATENTS, DATA, AND COPYRIGHTS Rights in Computer Software and Computer Software Documentation 227.7203-8 Deferred delivery and deferred ordering of computer software and computer...

48 CFR 227.7203-8 - Deferred delivery and deferred ordering of computer software and computer software documentation.

Code of Federal Regulations, 2013 CFR

2013-10-01

... deferred ordering of computer software and computer software documentation. 227.7203-8 Section 227.7203-8... GENERAL CONTRACTING REQUIREMENTS PATENTS, DATA, AND COPYRIGHTS Rights in Computer Software and Computer Software Documentation 227.7203-8 Deferred delivery and deferred ordering of computer software and computer...

48 CFR 227.7203-8 - Deferred delivery and deferred ordering of computer software and computer software documentation.

Code of Federal Regulations, 2010 CFR

2010-10-01

... deferred ordering of computer software and computer software documentation. 227.7203-8 Section 227.7203-8... GENERAL CONTRACTING REQUIREMENTS PATENTS, DATA, AND COPYRIGHTS Rights in Computer Software and Computer Software Documentation 227.7203-8 Deferred delivery and deferred ordering of computer software and computer...

A Framework of the Use of Information in Software Testing

ERIC Educational Resources Information Center

Kaveh, Payman

2010-01-01

With the increasing role that software systems play in our daily lives, software quality has become extremely important. Software quality is impacted by the efficiency of the software testing process. There are a growing number of software testing methodologies, models, and initiatives to satisfy the need to improve software quality. The main…

NASA's Approach to Software Assurance

NASA Technical Reports Server (NTRS)

Wetherholt, Martha

2015-01-01

NASA defines software assurance as: the planned and systematic set of activities that ensure conformance of software life cycle processes and products to requirements, standards, and procedures via quality, safety, reliability, and independent verification and validation. NASA's implementation of this approach to the quality, safety, reliability, security and verification and validation of software is brought together in one discipline, software assurance. Organizationally, NASA has software assurance at each NASA center, a Software Assurance Manager at NASA Headquarters, a Software Assurance Technical Fellow (currently the same person as the SA Manager), and an Independent Verification and Validation Organization with its own facility. An umbrella risk mitigation strategy for safety and mission success assurance of NASA's software, software assurance covers a wide area and is better structured to address the dynamic changes in how software is developed, used, and managed, as well as it's increasingly complex functionality. Being flexible, risk based, and prepared for challenges in software at NASA is essential, especially as much of our software is unique for each mission.

The Implications of Using Integrated Software Support Environment for Design of Guidance and Control Systems Software

DTIC Science & Technology

1990-02-01

inspections are performed before each formal review of each software life cycle phase. * Required software audits are performed . " The software is acceptable... Audits : Software audits are performed bySQA consistent with thegeneral audit rules and an auditreportis prepared. Software Quality Inspection (SQI...DSD Software Development Method 3-34 DEFINITION OF ACRONYMS Acronym Full Name or Description MACH Methode d’Analyse et de Conception Flierarchisee

Evolution of Secondary Software Businesses: Understanding Industry Dynamics

NASA Astrophysics Data System (ADS)

Tyrväinen, Pasi; Warsta, Juhani; Seppänen, Veikko

Primary software industry originates from IBM's decision to unbundle software-related computer system development activities to external partners. This kind of outsourcing from an enterprise internal software development activity is a common means to start a new software business serving a vertical software market. It combines knowledge of the vertical market process with competence in software development. In this research, we present and analyze the key figures of the Finnish secondary software industry, in order to quantify its interaction with the primary software industry during the period of 2000-2003. On the basis of the empirical data, we present a model for evolution of a secondary software business, which makes explicit the industry dynamics. It represents the shift from internal software developed for competitive advantage to development of products supporting standard business processes on top of standardized technologies. We also discuss the implications for software business strategies in each phase.

Secure software practices among Malaysian software practitioners: An exploratory study

NASA Astrophysics Data System (ADS)

Mohamed, Shafinah Farvin Packeer; Baharom, Fauziah; Deraman, Aziz; Yahya, Jamaiah; Mohd, Haslina

2016-08-01

Secure software practices is increasingly gaining much importance among software practitioners and researchers due to the rise of computer crimes in the software industry. It has become as one of the determinant factors for producing high quality software. Even though its importance has been revealed, its current practice in the software industry is still scarce, particularly in Malaysia. Thus, an exploratory study is conducted among software practitioners in Malaysia to study their experiences and practices in the real-world projects. This paper discusses the findings from the study, which involved 93 software practitioners. Structured questionnaire is utilized for data collection purpose whilst statistical methods such as frequency, mean, and cross tabulation are used for data analysis. Outcomes from this study reveal that software practitioners are becoming increasingly aware on the importance of secure software practices, however, they lack of appropriate implementation, which could affect the quality of produced software.

The Role and Quality of Software Safety in the NASA Constellation Program

NASA Technical Reports Server (NTRS)

Layman, Lucas; Basili, Victor R.; Zelkowitz, Marvin V.

2010-01-01

In this study, we examine software safety risk in the early design phase of the NASA Constellation spaceflight program. Obtaining an accurate, program-wide picture of software safety risk is difficult across multiple, independently-developing systems. We leverage one source of safety information, hazard analysis, to provide NASA quality assurance managers with information regarding the ongoing state of software safety across the program. The goal of this research is two-fold: 1) to quantify the relative importance of software with respect to system safety; and 2) to quantify the level of risk presented by software in the hazard analysis. We examined 154 hazard reports created during the preliminary design phase of three major flight hardware systems within the Constellation program. To quantify the importance of software, we collected metrics based on the number of software-related causes and controls of hazardous conditions. To quantify the level of risk presented by software, we created a metric scheme to measure the specificity of these software causes. We found that from 49-70% of hazardous conditions in the three systems could be caused by software or software was involved in the prevention of the hazardous condition. We also found that 12-17% of the 2013 hazard causes involved software, and that 23-29% of all causes had a software control. Furthermore, 10-12% of all controls were software-based. There is potential for inaccuracy in these counts, however, as software causes are not consistently scoped, and the presence of software in a cause or control is not always clear. The application of our software specificity metrics also identified risks in the hazard reporting process. In particular, we found a number of traceability risks in the hazard reports may impede verification of software and system safety.

A UML-based metamodel for software evolution process

NASA Astrophysics Data System (ADS)

Jiang, Zuo; Zhou, Wei-Hong; Fu, Zhi-Tao; Xiong, Shun-Qing

2014-04-01

A software evolution process is a set of interrelated software processes under which the corresponding software is evolving. An object-oriented software evolution process meta-model (OO-EPMM), abstract syntax and formal OCL constraint of meta-model are presented in this paper. OO-EPMM can not only represent software development process, but also represent software evolution.

48 CFR 227.7202-4 - Contract clause.

Code of Federal Regulations, 2012 CFR

2012-10-01

... Software and Computer Software Documentation 227.7202-4 Contract clause. A specific contract clause governing the Government's rights in commercial computer software or commercial computer software..., release, perform, display, or disclose computer software or computer software documentation shall be...

48 CFR 227.7202-4 - Contract clause.

Code of Federal Regulations, 2011 CFR

2011-10-01

... Software and Computer Software Documentation 227.7202-4 Contract clause. A specific contract clause governing the Government's rights in commercial computer software or commercial computer software..., release, perform, display, or disclose computer software or computer software documentation shall be...

48 CFR 227.7202-4 - Contract clause.

Code of Federal Regulations, 2014 CFR

2014-10-01

... Software and Computer Software Documentation 227.7202-4 Contract clause. A specific contract clause governing the Government's rights in commercial computer software or commercial computer software..., release, perform, display, or disclose computer software or computer software documentation shall be...

48 CFR 227.7202-4 - Contract clause.

Code of Federal Regulations, 2013 CFR

2013-10-01

... Software and Computer Software Documentation 227.7202-4 Contract clause. A specific contract clause governing the Government's rights in commercial computer software or commercial computer software..., release, perform, display, or disclose computer software or computer software documentation shall be...

48 CFR 227.7202-4 - Contract clause.

Code of Federal Regulations, 2010 CFR

2010-10-01

... Software and Computer Software Documentation 227.7202-4 Contract clause. A specific contract clause governing the Government's rights in commercial computer software or commercial computer software..., release, perform, display, or disclose computer software or computer software documentation shall be...

Models for Deploying Open Source and Commercial Software to Support Earth Science Data Processing and Distribution

NASA Astrophysics Data System (ADS)

Yetman, G.; Downs, R. R.

2011-12-01

Software deployment is needed to process and distribute scientific data throughout the data lifecycle. Developing software in-house can take software development teams away from other software development projects and can require efforts to maintain the software over time. Adopting and reusing software and system modules that have been previously developed by others can reduce in-house software development and maintenance costs and can contribute to the quality of the system being developed. A variety of models are available for reusing and deploying software and systems that have been developed by others. These deployment models include open source software, vendor-supported open source software, commercial software, and combinations of these approaches. Deployment in Earth science data processing and distribution has demonstrated the advantages and drawbacks of each model. Deploying open source software offers advantages for developing and maintaining scientific data processing systems and applications. By joining an open source community that is developing a particular system module or application, a scientific data processing team can contribute to aspects of the software development without having to commit to developing the software alone. Communities of interested developers can share the work while focusing on activities that utilize in-house expertise and addresses internal requirements. Maintenance is also shared by members of the community. Deploying vendor-supported open source software offers similar advantages to open source software. However, by procuring the services of a vendor, the in-house team can rely on the vendor to provide, install, and maintain the software over time. Vendor-supported open source software may be ideal for teams that recognize the value of an open source software component or application and would like to contribute to the effort, but do not have the time or expertise to contribute extensively. Vendor-supported software may also have the additional benefits of guaranteed up-time, bug fixes, and vendor-added enhancements. Deploying commercial software can be advantageous for obtaining system or software components offered by a vendor that meet in-house requirements. The vendor can be contracted to provide installation, support and maintenance services as needed. Combining these options offers a menu of choices, enabling selection of system components or software modules that meet the evolving requirements encountered throughout the scientific data lifecycle.

On Ensino de Astronomia: Desafios para Implantação

NASA Astrophysics Data System (ADS)

Faria, R. Z.; Voelzke, M. R.

2008-09-01

Em 2002 o ensino de Astronomia foi proposto como um dos temas estruturadores pelos Parâmetros Curriculares Nacionais e sugerido como facilitador para que o aluno compreendesse a Física como construção humana e parte do seu mundo vivencial, mas raramente seus conceitos foram ensinados. A presente pesquisa discute dois aspectos relacionados à abordagem de Astronomia. O primeiro aspecto é se ela está sendo abordada pelos professores do Ensino Médio e o segundo, aborda a maneira como ela está sendo ensinada. Optou-se pela aplicação de um questionário a partir do 2° semestre de 2006 e durante o ano de 2007 com professores que ministram a disciplina de Física, os quais trabalham em escolas estaduais em Rio Grande da Serra, Ribeirão Pires e Mauá no estado São Paulo. Dos 66,2% dos professores que responderam ao questionário nos municípios de Rio Grande da Serra, Ribeirão Pires e Mauá, 57,4% não aplicaram nenhum tópico de astronomia, 70,2% não utilizaram laboratório, 89,4% não utilizaram qualquer tipo de programa computacional, 83,0% nunca fizeram visitas com alunos a museus e planetários e 38,3% não indicaram qualquer tipo de livro ou revista referente à astronomia aos seus alunos. Mesmo considerando a Astronomia um conteúdo potencialmente significativo, esta não fez parte dos planejamentos escolares. Portanto são necessárias propostas que visem estratégias para a educação continuada dos professores como, por exemplo, cursos específicos sobre o ensino em Astronomia.

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

NASA Astrophysics Data System (ADS)

Vinay, S.; Downs, R. R.

2012-12-01

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

Software technology insertion: A study of success factors

NASA Technical Reports Server (NTRS)

Lydon, Tom

1990-01-01

Managing software development in large organizations has become increasingly difficult due to increasing technical complexity, stricter government standards, a shortage of experienced software engineers, competitive pressure for improved productivity and quality, the need to co-develop hardware and software together, and the rapid changes in both hardware and software technology. The 'software factory' approach to software development minimizes risks while maximizing productivity and quality through standardization, automation, and training. However, in practice, this approach is relatively inflexible when adopting new software technologies. The methods that a large multi-project software engineering organization can use to increase the likelihood of successful software technology insertion (STI), especially in a standardized engineering environment, are described.

Software archeology: a case study in software quality assurance and design

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

Macdonald, John M; Lloyd, Jane A; Turner, Cameron J

2009-01-01

Ideally, quality is designed into software, just as quality is designed into hardware. However, when dealing with legacy systems, demonstrating that the software meets required quality standards may be difficult to achieve. As the need to demonstrate the quality of existing software was recognized at Los Alamos National Laboratory (LANL), an effort was initiated to uncover and demonstrate that legacy software met the required quality standards. This effort led to the development of a reverse engineering approach referred to as software archaeology. This paper documents the software archaeology approaches used at LANL to document legacy software systems. A case studymore » for the Robotic Integrated Packaging System (RIPS) software is included.« less

Annotated bibliography of software engineering laboratory literature

NASA Technical Reports Server (NTRS)

Kistler, David; Bristow, John; Smith, Don

1994-01-01

This document is an annotated bibliography of technical papers, documents, and memorandums produced by or related to the Software Engineering Laboratory. Nearly 200 publications are summarized. These publications cover many areas of software engineering and range from research reports to software documentation. This document has been updated and reorganized substantially since the original version (SEL-82-006, November 1982). All materials have been grouped into eight general subject areas for easy reference: (1) The Software Engineering Laboratory; (2) The Software Engineering Laboratory: Software Development Documents; (3) Software Tools; (4) Software Models; (5) Software Measurement; (6) Technology Evaluations; (7) Ada Technology; and (8) Data Collection. This document contains an index of these publications classified by individual author.

Reuse Metrics for Object Oriented Software

NASA Technical Reports Server (NTRS)

Bieman, James M.

1998-01-01

One way to increase the quality of software products and the productivity of software development is to reuse existing software components when building new software systems. In order to monitor improvements in reuse, the level of reuse must be measured. In this NASA supported project we (1) derived a suite of metrics which quantify reuse attributes for object oriented, object based, and procedural software, (2) designed prototype tools to take these measurements in Ada, C++, Java, and C software, (3) evaluated the reuse in available software, (4) analyzed the relationship between coupling, cohesion, inheritance, and reuse, (5) collected object oriented software systems for our empirical analyses, and (6) developed quantitative criteria and methods for restructuring software to improve reusability.

48 CFR 12.212 - Computer software.

Code of Federal Regulations, 2012 CFR

2012-10-01

... 48 Federal Acquisition Regulations System 1 2012-10-01 2012-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...

48 CFR 12.212 - Computer software.

Code of Federal Regulations, 2011 CFR

2011-10-01

... 48 Federal Acquisition Regulations System 1 2011-10-01 2011-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...

48 CFR 227.7203-9 - Copyright.

Code of Federal Regulations, 2010 CFR

2010-10-01

... Software and Computer Software Documentation 227.7203-9 Copyright. (a) Copyright license. (1) The clause at 252.227-7014, Rights in Noncommercial Computer Software and Noncommercial Computer Software... Government to reproduce the software or documentation, distribute copies, perform or display the software or...

48 CFR 227.7203-9 - Copyright.

Code of Federal Regulations, 2013 CFR

2013-10-01

... Software and Computer Software Documentation 227.7203-9 Copyright. (a) Copyright license. (1) The clause at 252.227-7014, Rights in Noncommercial Computer Software and Noncommercial Computer Software... Government to reproduce the software or documentation, distribute copies, perform or display the software or...

48 CFR 227.7203-9 - Copyright.

Code of Federal Regulations, 2011 CFR

2011-10-01

... Software and Computer Software Documentation 227.7203-9 Copyright. (a) Copyright license. (1) The clause at 252.227-7014, Rights in Noncommercial Computer Software and Noncommercial Computer Software... Government to reproduce the software or documentation, distribute copies, perform or display the software or...

48 CFR 12.212 - Computer software.

Code of Federal Regulations, 2014 CFR

2014-10-01

... 48 Federal Acquisition Regulations System 1 2014-10-01 2014-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...

48 CFR 12.212 - Computer software.

Code of Federal Regulations, 2010 CFR

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

48 CFR 227.7203-9 - Copyright.

Code of Federal Regulations, 2014 CFR

2014-10-01

... Software and Computer Software Documentation 227.7203-9 Copyright. (a) Copyright license. (1) The clause at 252.227-7014, Rights in Noncommercial Computer Software and Noncommercial Computer Software... Government to reproduce the software or documentation, distribute copies, perform or display the software or...

48 CFR 12.212 - Computer software.

Code of Federal Regulations, 2013 CFR

2013-10-01

... 48 Federal Acquisition Regulations System 1 2013-10-01 2013-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...

48 CFR 227.7203-9 - Copyright.

Code of Federal Regulations, 2012 CFR

2012-10-01

... Software and Computer Software Documentation 227.7203-9 Copyright. (a) Copyright license. (1) The clause at 252.227-7014, Rights in Noncommercial Computer Software and Noncommercial Computer Software... Government to reproduce the software or documentation, distribute copies, perform or display the software or...

Educational Software Acquisition for Microcomputers.

ERIC Educational Resources Information Center

Erikson, Warren; Turban, Efraim

1985-01-01

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

A Model for Assessing the Liability of Seemingly Correct Software

NASA Technical Reports Server (NTRS)

Voas, Jeffrey M.; Voas, Larry K.; Miller, Keith W.

1991-01-01

Current research on software reliability does not lend itself to quantitatively assessing the risk posed by a piece of life-critical software. Black-box software reliability models are too general and make too many assumptions to be applied confidently to assessing the risk of life-critical software. We present a model for assessing the risk caused by a piece of software; this model combines software testing results and Hamlet's probable correctness model. We show how this model can assess software risk for those who insure against a loss that can occur if life-critical software fails.

NASA space station software standards issues

NASA Technical Reports Server (NTRS)

Tice, G. D., Jr.

1985-01-01

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

LA BIOÉTICA COMO QUEHACER FILOSÓFICO

PubMed Central

Ferrer, Jorge José

2009-01-01

El artículo examina el estatuto epistemológico de la bioética como disciplina académica. El autor sostiene que el estatuto epistemológico de un discurso lo determina la pregunta fundamental que se plantea y la respuesta que se busca, focos integradores del discurso. En el caso de la bioética, la pregunta fundamental es de índole moral. La bioética es pues una disciplina ética que tiene su hogar epistemológico en la filosofía. El autor también defiende el concepto de “éticas aplicadas”. Sugiere finalmente que el método de la bioética, sobre todo la que se hace desde nuestras latitudes, debería adoptar el círculo hermenéutico como metodología para su filosofar. PMID:20463860

Statistical modelling of software reliability

NASA Technical Reports Server (NTRS)

Miller, Douglas R.

1991-01-01

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

Software Engineering Guidebook

NASA Technical Reports Server (NTRS)

Connell, John; Wenneson, Greg

1993-01-01

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

A measurement system for large, complex software programs

NASA Technical Reports Server (NTRS)

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.

Certification Processes for Safety-Critical and Mission-Critical Aerospace Software

NASA Technical Reports Server (NTRS)

Nelson, Stacy

2003-01-01

This document is a quick reference guide with an overview of the processes required to certify safety-critical and mission-critical flight software at selected NASA centers and the FAA. Researchers and software developers can use this guide to jumpstart their understanding of how to get new or enhanced software onboard an aircraft or spacecraft. The introduction contains aerospace industry definitions of safety and safety-critical software, as well as, the current rationale for certification of safety-critical software. The Standards for Safety-Critical Aerospace Software section lists and describes current standards including NASA standards and RTCA DO-178B. The Mission-Critical versus Safety-Critical software section explains the difference between two important classes of software: safety-critical software involving the potential for loss of life due to software failure and mission-critical software involving the potential for aborting a mission due to software failure. The DO-178B Safety-critical Certification Requirements section describes special processes and methods required to obtain a safety-critical certification for aerospace software flying on vehicles under auspices of the FAA. The final two sections give an overview of the certification process used at Dryden Flight Research Center and the approval process at the Jet Propulsion Lab (JPL).

NASA PC software evaluation project

NASA Technical Reports Server (NTRS)

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

1986-01-01

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

User systems guidelines for software projects

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

Abrahamson, L.

1986-04-01

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

48 CFR 208.7400 - Scope of subpart.

Code of Federal Regulations, 2013 CFR

2013-10-01

... OF DEFENSE ACQUISITION PLANNING REQUIRED SOURCES OF SUPPLIES AND SERVICES Enterprise Software... commercial software and software maintenance, including software and software maintenance that is acquired...

48 CFR 208.7400 - Scope of subpart.

Code of Federal Regulations, 2012 CFR

2012-10-01

... OF DEFENSE ACQUISITION PLANNING REQUIRED SOURCES OF SUPPLIES AND SERVICES Enterprise Software... commercial software and software maintenance, including software and software maintenance that is acquired...

48 CFR 208.7400 - Scope of subpart.

Code of Federal Regulations, 2011 CFR

2011-10-01

... OF DEFENSE ACQUISITION PLANNING REQUIRED SOURCES OF SUPPLIES AND SERVICES Enterprise Software... commercial software and software maintenance, including software and software maintenance that is acquired...

48 CFR 208.7400 - Scope of subpart.

Code of Federal Regulations, 2014 CFR

2014-10-01

... OF DEFENSE ACQUISITION PLANNING REQUIRED SOURCES OF SUPPLIES AND SERVICES Enterprise Software... commercial software and software maintenance, including software and software maintenance that is acquired...

Guidance and Control Software Project Data - Volume 1: Planning Documents

NASA Technical Reports Server (NTRS)

Hayhurst, Kelly J. (Editor)

2008-01-01

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

Como preparar un programa de informacion sobre la asistencia economica (Planning a Financial Aid Awareness Program).

ERIC Educational Resources Information Center

Department of Education, Washington, DC.

This booklet, written in Spanish, is intended to be used with a set of slides as part of a presentation to students on "How To Apply for Federal Student Aid" ("Como Solicitar la Asistencia Economica Federal para Estudiantes"). The first part of the book is a script based on the slides. After the script is a guide to hosting a financial aid…

Improving Software Engineering on NASA Projects

NASA Technical Reports Server (NTRS)

Crumbley, Tim; Kelly, John C.

2010-01-01

Software Engineering Initiative: Reduces risk of software failure -Increases mission safety. More predictable software cost estimates and delivery schedules. Smarter buyer of contracted out software. More defects found and removed earlier. Reduces duplication of efforts between projects. Increases ability to meet the challenges of evolving software technology.

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

ERIC Educational Resources Information Center

Parker, Linda L.

2016-01-01

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

Software Assurance Competency Model

DTIC Science & Technology

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

The Elements of an Effective Software Development Plan - Software Development Process Guidebook

DTIC Science & Technology

2011-11-11

standards and practices required for all XMPL software development. This SDP implements the <corporate> Standard Software Process (SSP). as tailored...Developing and integrating reusable software products • Approach to managing COTS/Reuse software implementation • COTS/Reuse software selection...final selection and submit to change board for approval MAINTENANCE Monitor current products for obsolescence or end of support Track new

Software safety - A user's practical perspective

NASA Technical Reports Server (NTRS)

Dunn, William R.; Corliss, Lloyd D.

1990-01-01

Software safety assurance philosophy and practices at the NASA Ames are discussed. It is shown that, to be safe, software must be error-free. Software developments on two digital flight control systems and two ground facility systems are examined, including the overall system and software organization and function, the software-safety issues, and their resolution. The effectiveness of safety assurance methods is discussed, including conventional life-cycle practices, verification and validation testing, software safety analysis, and formal design methods. It is concluded (1) that a practical software safety technology does not yet exist, (2) that it is unlikely that a set of general-purpose analytical techniques can be developed for proving that software is safe, and (3) that successful software safety-assurance practices will have to take into account the detailed design processes employed and show that the software will execute correctly under all possible conditions.

Predicting Software Suitability Using a Bayesian Belief Network

NASA Technical Reports Server (NTRS)

Beaver, Justin M.; Schiavone, Guy A.; Berrios, Joseph S.

2005-01-01

The ability to reliably predict the end quality of software under development presents a significant advantage for a development team. It provides an opportunity to address high risk components earlier in the development life cycle, when their impact is minimized. This research proposes a model that captures the evolution of the quality of a software product, and provides reliable forecasts of the end quality of the software being developed in terms of product suitability. Development team skill, software process maturity, and software problem complexity are hypothesized as driving factors of software product quality. The cause-effect relationships between these factors and the elements of software suitability are modeled using Bayesian Belief Networks, a machine learning method. This research presents a Bayesian Network for software quality, and the techniques used to quantify the factors that influence and represent software quality. The developed model is found to be effective in predicting the end product quality of small-scale software development efforts.

The Effects of Development Team Skill on Software Product Quality

NASA Technical Reports Server (NTRS)

Beaver, Justin M.; Schiavone, Guy A.

2006-01-01

This paper provides an analysis of the effect of the skill/experience of the software development team on the quality of the final software product. A method for the assessment of software development team skill and experience is proposed, and was derived from a workforce management tool currently in use by the National Aeronautics and Space Administration. Using data from 26 smallscale software development projects, the team skill measures are correlated to 5 software product quality metrics from the ISO/IEC 9126 Software Engineering Product Quality standard. in the analysis of the results, development team skill is found to be a significant factor in the adequacy of the design and implementation. In addition, the results imply that inexperienced software developers are tasked with responsibilities ill-suited to their skill level, and thus have a significant adverse effect on the quality of the software product. Keywords: software quality, development skill, software metrics

An ontology based trust verification of software license agreement

NASA Astrophysics Data System (ADS)

Lu, Wenhuan; Li, Xiaoqing; Gan, Zengqin; Wei, Jianguo

2017-08-01

When we install software or download software, there will show up so big mass document to state the rights and obligations, for which lots of person are not patient to read it or understand it. That would may make users feel distrust for the software. In this paper, we propose an ontology based verification for Software License Agreement. First of all, this work proposed an ontology model for domain of Software License Agreement. The domain ontology is constructed by proposed methodology according to copyright laws and 30 software license agreements. The License Ontology can act as a part of generalized copyright law knowledge model, and also can work as visualization of software licenses. Based on this proposed ontology, a software license oriented text summarization approach is proposed which performances showing that it can improve the accuracy of software licenses summarizing. Based on the summarization, the underline purpose of the software license can be explicitly explored for trust verification.

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

Federal Register 2010, 2011, 2012, 2013, 2014

2012-08-22

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

Impact of Agile Software Development Model on Software Maintainability

ERIC Educational Resources Information Center

Gawali, Ajay R.

2012-01-01

Software maintenance and support costs account for up to 60% of the overall software life cycle cost and often burdens tightly budgeted information technology (IT) organizations. Agile software development approach delivers business value early, but implications on software maintainability are still unknown. The purpose of this quantitative study…

77 FR 50724 - Developing Software Life Cycle Processes for Digital Computer Software Used in Safety Systems of...

Federal Register 2010, 2011, 2012, 2013, 2014

2012-08-22

... NUCLEAR REGULATORY COMMISSION [NRC-2012-0195] Developing Software Life Cycle Processes for Digital... Software Life Cycle Processes for Digital Computer Software used in Safety Systems of Nuclear Power Plants... clarifications, the enhanced consensus practices for developing software life-cycle processes for digital...

Proceedings of Tenth Annual Software Engineering Workshop

NASA Technical Reports Server (NTRS)

1985-01-01

Papers are presented on the following topics: measurement of software technology, recent studies of the Software Engineering Lab, software management tools, expert systems, error seeding as a program validation technique, software quality assurance, software engineering environments (including knowledge-based environments), the Distributed Computing Design System, and various Ada experiments.

Reducing Risk in DoD Software-Intensive Systems Development

DTIC Science & Technology

2016-03-01

intensive systems development risk. This research addresses the use of the Technical Readiness Assessment (TRA) using the nine-level software Technology...The software TRLs are ineffective in reducing technical risk for the software component development. • Without the software TRLs, there is no...effective method to perform software TRA or reduce the technical development risk. The software component will behave as a new, untried technology in nearly

Software Formal Inspections Standard

NASA Technical Reports Server (NTRS)

1993-01-01

This Software Formal Inspections Standard (hereinafter referred to as Standard) is applicable to NASA software. This Standard defines the requirements that shall be fulfilled by the software formal inspections process whenever this process is specified for NASA software. The objective of this Standard is to define the requirements for a process that inspects software products to detect and eliminate defects as early as possible in the software life cycle. The process also provides for the collection and analysis of inspection data to improve the inspection process as well as the quality of the software.

Annotated bibliography of software engineering laboratory literature

NASA Technical Reports Server (NTRS)

Buhler, Melanie; Valett, Jon

1989-01-01

An annotated bibliography is presented of technical papers, documents, and memorandums produced by or related to the Software Engineering Laboratory. The bibliography was updated and reorganized substantially since the original version (SEL-82-006, November 1982). All materials were grouped into eight general subject areas for easy reference: (1) The Software Engineering Laboratory; (2) The Software Engineering Laboratory: Software Development Documents; (3) Software Tools; (4) Software Models; (5) Software Measurement; (6) Technology Evaluations; (7) Ada Technology; and (8) Data Collection. Subject and author indexes further classify these documents by specific topic and individual author.

Software Program: Software Management Guidebook

NASA Technical Reports Server (NTRS)

1996-01-01

The purpose of this NASA Software Management Guidebook is twofold. First, this document defines the core products and activities required of NASA software projects. It defines life-cycle models and activity-related methods but acknowledges that no single life-cycle model is appropriate for all NASA software projects. It also acknowledges that the appropriate method for accomplishing a required activity depends on characteristics of the software project. Second, this guidebook provides specific guidance to software project managers and team leaders in selecting appropriate life cycles and methods to develop a tailored plan for a software engineering project.

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

NASA Technical Reports Server (NTRS)

Mckee, James W.

1990-01-01

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

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

NASA Technical Reports Server (NTRS)

Hayhurst, Kelly J. (Editor)

2008-01-01

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

A Probabilistic Software System Attribute Acceptance Paradigm for COTS Software Evaluation

NASA Technical Reports Server (NTRS)

Morris, A. Terry

2005-01-01

Standard software requirement formats are written from top-down perspectives only, that is, from an ideal notion of a client s needs. Despite the exactness of the standard format, software and system errors in designed systems have abounded. Bad and inadequate requirements have resulted in cost overruns, schedule slips and lost profitability. Commercial off-the-shelf (COTS) software components are even more troublesome than designed systems because they are often provided as is and subsequently delivered with unsubstantiated validation of described capabilities. For COTS software, there needs to be a way to express the client s software needs in a consistent and formal manner using software system attributes derived from software quality standards. Additionally, the format needs to be amenable to software evaluation processes that integrate observable evidence garnered from historical data. This paper presents a paradigm that effectively bridges the gap between what a client desires (top-down) and what has been demonstrated (bottom-up) for COTS software evaluation. The paradigm addresses the specification of needs before the software evaluation is performed and can be used to increase the shared understanding between clients and software evaluators about what is required and what is technically possible.

Modular Rocket Engine Control Software (MRECS)

NASA Technical Reports Server (NTRS)

Tarrant, Charlie; Crook, Jerry

1997-01-01

The Modular Rocket Engine Control Software (MRECS) Program is a technology demonstration effort designed to advance the state-of-the-art in launch vehicle propulsion systems. Its emphasis is on developing and demonstrating a modular software architecture for a generic, advanced engine control system that will result in lower software maintenance (operations) costs. It effectively accommodates software requirements changes that occur due to hardware. technology upgrades and engine development testing. Ground rules directed by MSFC were to optimize modularity and implement the software in the Ada programming language. MRECS system software and the software development environment utilize Commercial-Off-the-Shelf (COTS) products. This paper presents the objectives and benefits of the program. The software architecture, design, and development environment are described. MRECS tasks are defined and timing relationships given. Major accomplishment are listed. MRECS offers benefits to a wide variety of advanced technology programs in the areas of modular software, architecture, reuse software, and reduced software reverification time related to software changes. Currently, the program is focused on supporting MSFC in accomplishing a Space Shuttle Main Engine (SSME) hot-fire test at Stennis Space Center and the Low Cost Boost Technology (LCBT) Program.

Software Reuse Within the Earth Science Community

NASA Technical Reports Server (NTRS)

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 similar, with the second, larger survey confirming the basic results of the first, smaller survey. The results suggest that reuse of ESE software can drive down the cost and time of system development, increase flexibility and responsiveness of these systems to new technologies and requirements, and increase effective and accountable community participation.

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

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

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

2006-09-01

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

The Knowledge-Based Software Assistant: Beyond CASE

NASA Technical Reports Server (NTRS)

Carozzoni, Joseph A.

1993-01-01

This paper will outline the similarities and differences between two paradigms of software development. Both support the whole software life cycle and provide automation for most of the software development process, but have different approaches. The CASE approach is based on a set of tools linked by a central data repository. This tool-based approach is data driven and views software development as a series of sequential steps, each resulting in a product. The Knowledge-Based Software Assistant (KBSA) approach, a radical departure from existing software development practices, is knowledge driven and centers around a formalized software development process. KBSA views software development as an incremental, iterative, and evolutionary process with development occurring at the specification level.

Implementing Software Safety in the NASA Environment

NASA Technical Reports Server (NTRS)

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 the system to be built. Shortly thereafter, as the system requirements are being defined, the second iteration of hazard analyses takes place, the systems hazard analysis (SHA). During the systems requirements phase, decisions are made as to what functions of the system will be the responsibility of software. This is the most critical time to affect the safety of the software. From this point, software safety analyses as well as software engineering practices are the main focus for assuring safe software. While many of the steps proposed in this paper seem like just sound engineering practices, they are the best technical and most cost effective means to assure safe software within a safe system.

Software and the future of programming languages.

PubMed

Aho, Alfred V

2004-02-27

Although software is the key enabler of the global information infrastructure, the amount and extent of software in use in the world today are not widely understood, nor are the programming languages and paradigms that have been used to create the software. The vast size of the embedded base of existing software and the increasing costs of software maintenance, poor security, and limited functionality are posing significant challenges for the software R&D community.

Software engineering and the role of Ada: Executive seminar

NASA Technical Reports Server (NTRS)

Freedman, Glenn B.

1987-01-01

The objective was to introduce the basic terminology and concepts of software engineering and Ada. The life cycle model is reviewed. The application of the goals and principles of software engineering is applied. An introductory understanding of the features of the Ada language is gained. Topics addressed include: the software crises; the mandate of the Space Station Program; software life cycle model; software engineering; and Ada under the software engineering umbrella.

40 CFR 725.54 - Suspension of the review period.

Code of Federal Regulations, 2013 CFR

2013-07-01

... generated using e-PMN reporting software and be completed through the finalization step of the software, and e-PMN software must be used to print the request for suspension for submission to EPA. Paper... reporting software and be completed through the finalization step of the software, and e-PMN software must...

47 CFR 2.944 - Software defined radios.

Code of Federal Regulations, 2013 CFR

2013-10-01

... 47 Telecommunication 1 2013-10-01 2013-10-01 false Software defined radios. 2.944 Section 2.944... Authorization § 2.944 Software defined radios. (a) Manufacturers must take steps to ensure that only software that has been approved with a software defined radio can be loaded into the radio. The software must...

47 CFR 2.944 - Software defined radios.

Code of Federal Regulations, 2010 CFR

2010-10-01

... 47 Telecommunication 1 2010-10-01 2010-10-01 false Software defined radios. 2.944 Section 2.944... Authorization § 2.944 Software defined radios. (a) Manufacturers must take steps to ensure that only software that has been approved with a software defined radio can be loaded into the radio. The software must...

40 CFR 725.54 - Suspension of the review period.

Code of Federal Regulations, 2011 CFR

2011-07-01

... generated using e-PMN reporting software and be completed through the finalization step of the software, and e-PMN software must be used to print the request for suspension for submission to EPA. Paper... reporting software and be completed through the finalization step of the software, and e-PMN software must...

40 CFR 725.54 - Suspension of the review period.

Code of Federal Regulations, 2012 CFR

2012-07-01

... generated using e-PMN reporting software and be completed through the finalization step of the software, and e-PMN software must be used to print the request for suspension for submission to EPA. Paper... reporting software and be completed through the finalization step of the software, and e-PMN software must...

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

Federal Register 2010, 2011, 2012, 2013, 2014

2012-08-22

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

47 CFR 2.944 - Software defined radios.

Code of Federal Regulations, 2012 CFR

2012-10-01

... 47 Telecommunication 1 2012-10-01 2012-10-01 false Software defined radios. 2.944 Section 2.944... Authorization § 2.944 Software defined radios. (a) Manufacturers must take steps to ensure that only software that has been approved with a software defined radio can be loaded into the radio. The software must...

78 FR 47011 - Software Unit Testing for Digital Computer Software Used in Safety Systems of Nuclear Power Plants

Federal Register 2010, 2011, 2012, 2013, 2014

2013-08-02

... NUCLEAR REGULATORY COMMISSION [NRC-2012-0195] Software Unit Testing for Digital Computer Software... revised regulatory guide (RG), revision 1 of RG 1.171, ``Software Unit Testing for Digital Computer Software Used in Safety Systems of Nuclear Power Plants.'' This RG endorses American National Standards...

47 CFR 2.944 - Software defined radios.

Code of Federal Regulations, 2011 CFR

2011-10-01

... 47 Telecommunication 1 2011-10-01 2011-10-01 false Software defined radios. 2.944 Section 2.944... Authorization § 2.944 Software defined radios. (a) Manufacturers must take steps to ensure that only software that has been approved with a software defined radio can be loaded into the radio. The software must...

Software Quality Perceptions of Stakeholders Involved in the Software Development Process

ERIC Educational Resources Information Center

Padmanabhan, Priya

2013-01-01

Software quality is one of the primary determinants of project management success. Stakeholders involved in software development widely agree that quality is important (Barney and Wohlin 2009). However, they may differ on what constitutes software quality, and which of its attributes are more important than others. Although, software quality…

47 CFR 2.944 - Software defined radios.

Code of Federal Regulations, 2014 CFR

2014-10-01

... 47 Telecommunication 1 2014-10-01 2014-10-01 false Software defined radios. 2.944 Section 2.944... Authorization § 2.944 Software defined radios. (a) Manufacturers must take steps to ensure that only software that has been approved with a software defined radio can be loaded into the radio. The software must...

40 CFR 725.54 - Suspension of the review period.

Code of Federal Regulations, 2010 CFR

2010-07-01

... generated using e-PMN reporting software and be completed through the finalization step of the software, and e-PMN software must be used to print the request for suspension for submission to EPA. Paper... reporting software and be completed through the finalization step of the software, and e-PMN software must...

High/Scope Buyer's Guide to Children's Software. 11th Edition.

ERIC Educational Resources Information Center

Hohmann, Charles; And Others

This 11th edition of the High/Scope Buyer's Guide to Children's Software was designed to help teachers, caregivers, and parents make good choices when purchasing software to enhance children's learning. The book consists of an introduction, a chapter on finding the best software, software reviews for 48 different software products. The…

Study of fault tolerant software technology for dynamic systems

NASA Technical Reports Server (NTRS)

Caglayan, A. K.; Zacharias, G. L.

1985-01-01

The major aim of this study is to investigate the feasibility of using systems-based failure detection isolation and compensation (FDIC) techniques in building fault-tolerant software and extending them, whenever possible, to the domain of software fault tolerance. First, it is shown that systems-based FDIC methods can be extended to develop software error detection techniques by using system models for software modules. In particular, it is demonstrated that systems-based FDIC techniques can yield consistency checks that are easier to implement than acceptance tests based on software specifications. Next, it is shown that systems-based failure compensation techniques can be generalized to the domain of software fault tolerance in developing software error recovery procedures. Finally, the feasibility of using fault-tolerant software in flight software is investigated. In particular, possible system and version instabilities, and functional performance degradation that may occur in N-Version programming applications to flight software are illustrated. Finally, a comparative analysis of N-Version and recovery block techniques in the context of generic blocks in flight software is presented.

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

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

Turgeon, Jennifer L.; Minana, Molly A.; Hackney, Patricia

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 themore » 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.« less

Shuttle mission simulator software conceptual design

NASA Technical Reports Server (NTRS)

Burke, J. F.

1973-01-01

Software conceptual designs (SCD) are presented for meeting the simulator requirements for the shuttle missions. The major areas of the SCD discussed include: malfunction insertion, flight software, applications software, systems software, and computer complex.

SAO mission support software and data standards, version 1.0

NASA Technical Reports Server (NTRS)

Hsieh, P.

1993-01-01

This document defines the software developed by the SAO AXAF Mission Support (MS) Program and defines standards for the software development process and control of data products generated by the software. The SAO MS is tasked to develop and use software to perform a variety of functions in support of the AXAF mission. Software is developed by software engineers and scientists, and commercial off-the-shelf (COTS) software is used either directly or customized through the use of scripts to implement analysis procedures. Software controls real-time laboratory instruments, performs data archiving, displays data, and generates model predictions. Much software is used in the analysis of data to generate data products that are required by the AXAF project, for example, on-orbit mirror performance predictions or detailed characterization of the mirror reflection performance with energy.

Statistical modeling of software reliability

NASA Technical Reports Server (NTRS)

Miller, Douglas R.

1992-01-01

This working paper discusses the statistical simulation part of a controlled software development experiment being conducted under the direction of the System Validation Methods Branch, Information Systems Division, NASA Langley Research Center. The experiment uses guidance and control software (GCS) aboard a fictitious planetary landing spacecraft: real-time control software operating on a transient mission. Software execution is simulated to study the statistical aspects of reliability and other failure characteristics of the software during development, testing, and random usage. Quantification of software reliability is a major goal. Various reliability concepts are discussed. Experiments are described for performing simulations and collecting appropriate simulated software performance and failure data. This data is then used to make statistical inferences about the quality of the software development and verification processes as well as inferences about the reliability of software versions and reliability growth under random testing and debugging.

Promoting Science Software Best Practices: A Scientist's Perspective (Invited)

NASA Astrophysics Data System (ADS)

Blanton, B. O.

2013-12-01

Software is at the core of most modern scientific activities, and as societal awareness of, and impacts from, extreme weather, disasters, and climate and global change continue to increase, the roles that scientific software play in analyses and decision-making are brought more to the forefront. Reproducibility of research results (particularly those that enter into the decision-making arena) and open access to the software is essential for scientific and scientists' credibility. This has been highlighted in a recent article by Joppa et al (Troubling Trends in Scientific Software Use, Science Magazine, May 2013) that describes reasons for particular software being chosen by scientists, including that the "developer is well-respected" and on "recommendation from a close colleague". This reliance on recommendation, Joppa et al conclude, is fraught with risks to both sciences and scientists. Scientists must frequently take software for granted, assuming that it performs as expected and advertised and that the software itself has been validated and results verified. This is largely due to the manner in which much software is written and developed; in an ad hoc manner, with an inconsistent funding stream, and with little application of core software engineering best practices. Insufficient documentation, limited test cases, and code unavailability are significant barriers to informed and intelligent science software usage. This situation is exacerbated when the scientist becomes the software developer out of necessity due to resource constraints. Adoption of, and adherence to, best practices in scientific software development will substantially increase intelligent software usage and promote a sustainable evolution of the science as encoded in the software. We describe a typical scientist's perspective on using and developing scientific software in the context of storm surge research and forecasting applications that have real-time objectives and regulatory constraints. This include perspectives on what scientists/users of software can contribute back to the software development process and examples of successful scientist/developer interactions, and the competition between "getting it done" and "getting it done right".

Estimaciones de cambio climatico para Michoacan: Implicaciones para el sector agropecuario y forestal y para la conservacion de la Mariposa Monarca [In Spanish

Treesearch

Cuauhtemoc Saenz-Romero; Gerald E. Rehfeldt; Nicholas L. Crookston; Pierre Duval; Jean Beaulieu

2009-01-01

El cambio climatico, conocido comunmente como calentamiento global, es el incremento de la temperatura a nivel mundial y los cambios que de ello derivan, causados por el "efecto invernadero" del bioxido de carbono (CO2) y otros gases emitidos a la atmosfera. El uso de combustibles fosiles (carbon y derivados del petroleo, como gasolina, diesel, combustoleo y...

Percepção Astronômica de Alunos do Ensino Médio da Rede Estadual de São Paulo

NASA Astrophysics Data System (ADS)

de Oliveira, E. F.; Voelzke, M. R.; Amaral, L. H.

2005-08-01

Embora a astronomia seja uma das ciências mais antigas da humanidade e muitos dos conceitos astronômicos serem populares, principalmente nesta época de alta globalização do conhecimento por intermédio de eficientes meios de comunicação e de obtenção da informação, notadamente através da internet, observa-se que uma parcela significativa dos estudantes encontra-se à margem dessas informações. O presente trabalho visa analisar o nível de conhecimento básico dos alunos de Ensino Médio da rede estadual da cidade de Suzano quanto aos fenômenos astronômicos que os rodeiam, tais como a sucessão dos dias e das estações do ano, além de questioná-los sobre fatos genéricos tais como: quais são os astros que se encontram mais próximos do planeta Terra, o que vem a ser o Sol, o Big Bang, um ano-luz, uma estrela cadente, a estrela de Bélem e o que ocasionou a extinção dos dinossauros. Para tanto foi elaborado um formulário constando de questões de múltipla escolha, o qual foi aplicado no primeiro colegial noturno da Escola Estadual Batista Renzi. Num espaço amostral de 34 alunos constatou-se que apenas 29,4% compreendiam a sucessão dos dias da semana, que apenas 20,6% explicaram corretamente as estações do ano, que apenas 20,6% tinham idéia de quais são os objetos celestes mais próximos da Terra, em contraposição 67,6% sabiam classificar corretamente o Sol como estrela, 55,9% relacionavam o Big Bang à origem do universo, apenas 20,6% identificavam um ano-luz como unidade de distância, 32,4% reconheciam uma estrela cadente como meteoro, 41,2% consideravam a estrela de Belém como um cometa e 50,0% explicaram corretamente a extinção dos dinossauros. A presente análise será expandida para as demais classes de primeiro colegial, não somente do período noturno, mas também do diurno da Escola Estadual Batista Renzi, bem como o formulário será devidamente ampliado. Já nesta primeira fase nota-se claramente o pequeno discernimento de eventos astronômicos dos alunos e principalmente a grande confusão sobre o significado correto de termos astronômicos populares.

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

NASA Technical Reports Server (NTRS)

Hancock, David W., III

1999-01-01

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

Coordination and organization of security software process for power information application environment

NASA Astrophysics Data System (ADS)

Wang, Qiang

2017-09-01

As an important part of software engineering, the software process decides the success or failure of software product. The design and development feature of security software process is discussed, so is the necessity and the present significance of using such process. Coordinating the function software, the process for security software and its testing are deeply discussed. The process includes requirement analysis, design, coding, debug and testing, submission and maintenance. In each process, the paper proposed the subprocesses to support software security. As an example, the paper introduces the above process into the power information platform.

Software Engineering Improvement Activities/Plan

NASA Technical Reports Server (NTRS)

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.

A Prototype for the Support of Integrated Software Process Development and Improvement

NASA Astrophysics Data System (ADS)

Porrawatpreyakorn, Nalinpat; Quirchmayr, Gerald; Chutimaskul, Wichian

An efficient software development process is one of key success factors for quality software. Not only can the appropriate establishment but also the continuous improvement of integrated project management and of the software development process result in efficiency. This paper hence proposes a software process maintenance framework which consists of two core components: an integrated PMBOK-Scrum model describing how to establish a comprehensive set of project management and software engineering processes and a software development maturity model advocating software process improvement. Besides, a prototype tool to support the framework is introduced.

The relationships between software publications and software systems

NASA Astrophysics Data System (ADS)

Hogg, David W.

2017-01-01

When we build software systems or software tools for astronomy, we sometimes do and sometimes don't also write and publish standard scientific papers about those software systems. I will discuss the pros and cons of writing such publications. There are impacts of writing such papers immediately (they can affect the design and structure of the software project itself), in the short term (they can promote adoption and legitimize the software), in the medium term (they can provide a platform for all the literature's mechanisms for citation, criticism, and reuse), and in the long term (they can preserve ideas that are embodied in the software, possibly on timescales much longer than the lifetime of any software context). I will argue that as important as pure software contributions are to astronomy—and I am both a preacher and a practitioner—software contributions are even more valuable when they are associated with traditional scientific publications. There are exceptions and complexities of course, which I will discuss.

Building quality into medical product software design.

PubMed

Mallory, S R

1993-01-01

The software engineering and quality assurance disciplines are a requisite to the design of safe and effective software-based medical devices. It is in the areas of software methodology and process that the most beneficial application of these disciplines to software development can be made. Software is a product of complex operations and methodologies and is not amenable to the traditional electromechanical quality assurance processes. Software quality must be built in by the developers, with the software verification and validation engineers acting as the independent instruments for ensuring compliance with performance objectives and with development and maintenance standards. The implementation of a software quality assurance program is a complex process involving management support, organizational changes, and new skill sets, but the benefits are profound. Its rewards provide safe, reliable, cost-effective, maintainable, and manageable software, which may significantly speed the regulatory review process and therefore potentially shorten the overall time to market. The use of a trial project can greatly facilitate the learning process associated with the first-time application of a software quality assurance program.

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

DTIC Science & Technology

2016-01-06

of- breed software components and software products lines (SPLs) that are subject to different IP license and cybersecurity requirements. The... commercially priced closed source software components, to be used in the design, implementation, deployment, and evolution of open architecture (OA... breed software components and software products lines (SPLs) that are subject to different IP license and cybersecurity requirements. The Department

Using software metrics and software reliability models to attain acceptable quality software for flight and ground support software for avionic systems

NASA Technical Reports Server (NTRS)

Lawrence, Stella

1992-01-01

This paper is concerned with methods of measuring and developing quality software. Reliable flight and ground support software is a highly important factor in the successful operation of the space shuttle program. Reliability is probably the most important of the characteristics inherent in the concept of 'software quality'. It is the probability of failure free operation of a computer program for a specified time and environment.

Artificial intelligence approaches to software engineering

NASA Technical Reports Server (NTRS)

Johannes, James D.; Macdonald, James R.

1988-01-01

Artificial intelligence approaches to software engineering are examined. The software development life cycle is a sequence of not so well-defined phases. Improved techniques for developing systems have been formulated over the past 15 years, but pressure continues to attempt to reduce current costs. Software development technology seems to be standing still. The primary objective of the knowledge-based approach to software development presented in this paper is to avoid problem areas that lead to schedule slippages, cost overruns, or software products that fall short of their desired goals. Identifying and resolving software problems early, often in the phase in which they first occur, has been shown to contribute significantly to reducing risks in software development. Software development is not a mechanical process but a basic human activity. It requires clear thinking, work, and rework to be successful. The artificial intelligence approaches to software engineering presented support the software development life cycle through the use of software development techniques and methodologies in terms of changing current practices and methods. These should be replaced by better techniques that that improve the process of of software development and the quality of the resulting products. The software development process can be structured into well-defined steps, of which the interfaces are standardized, supported and checked by automated procedures that provide error detection, production of the documentation and ultimately support the actual design of complex programs.

Software dependability in the Tandem GUARDIAN system

NASA Technical Reports Server (NTRS)

Lee, Inhwan; Iyer, Ravishankar K.

1995-01-01

Based on extensive field failure data for Tandem's GUARDIAN operating system this paper discusses evaluation of the dependability of operational software. Software faults considered are major defects that result in processor failures and invoke backup processes to take over. The paper categorizes the underlying causes of software failures and evaluates the effectiveness of the process pair technique in tolerating software faults. A model to describe the impact of software faults on the reliability of an overall system is proposed. The model is used to evaluate the significance of key factors that determine software dependability and to identify areas for improvement. An analysis of the data shows that about 77% of processor failures that are initially considered due to software are confirmed as software problems. The analysis shows that the use of process pairs to provide checkpointing and restart (originally intended for tolerating hardware faults) allows the system to tolerate about 75% of reported software faults that result in processor failures. The loose coupling between processors, which results in the backup execution (the processor state and the sequence of events) being different from the original execution, is a major reason for the measured software fault tolerance. Over two-thirds (72%) of measured software failures are recurrences of previously reported faults. Modeling, based on the data, shows that, in addition to reducing the number of software faults, software dependability can be enhanced by reducing the recurrence rate.

Testing Scientific Software: A Systematic Literature Review.

PubMed

Kanewala, Upulee; Bieman, James M

2014-10-01

Scientific software plays an important role in critical decision making, for example making weather predictions based on climate models, and computation of evidence for research publications. Recently, scientists have had to retract publications due to errors caused by software faults. Systematic testing can identify such faults in code. This study aims to identify specific challenges, proposed solutions, and unsolved problems faced when testing scientific software. We conducted a systematic literature survey to identify and analyze relevant literature. We identified 62 studies that provided relevant information about testing scientific software. We found that challenges faced when testing scientific software fall into two main categories: (1) testing challenges that occur due to characteristics of scientific software such as oracle problems and (2) testing challenges that occur due to cultural differences between scientists and the software engineering community such as viewing the code and the model that it implements as inseparable entities. In addition, we identified methods to potentially overcome these challenges and their limitations. Finally we describe unsolved challenges and how software engineering researchers and practitioners can help to overcome them. Scientific software presents special challenges for testing. Specifically, cultural differences between scientist developers and software engineers, along with the characteristics of the scientific software make testing more difficult. Existing techniques such as code clone detection can help to improve the testing process. Software engineers should consider special challenges posed by scientific software such as oracle problems when developing testing techniques.

Programming Makes Software; Support Makes Users

NASA Astrophysics Data System (ADS)

Batcheller, A. L.

2010-12-01

Skilled software engineers may build fantastic software for climate modeling, yet fail to achieve their project’s objectives. Software support and related activities are just as critical as writing software. This study followed three different software projects in the climate sciences, using interviews, observation, and document analysis to examine the value added by support work. Supporting the project and interacting with users was a key task for software developers, who often spent 50% of their time on it. Such support work most often involved replying to questions on an email list, but also included talking to users on teleconference calls and in person. Software support increased adoption by building the software’s reputation and showing individuals how the software can meet their needs. In the process of providing support, developers often learned new of requirements as users reported features they desire and bugs they found. As software matures and gains widespread use, support work often increases. In fact, such increases can be one signal that the software has achieved broad acceptance. Maturing projects also find demand for instructional classes, online tutorials and detailed examples of how to use the software. The importance of support highlights the fact that building software systems involves both social and technical aspects. Yes, we need to build the software, but we also need to “build” the users and practices that can take advantage of it.

How Safe Is Control Software

NASA Technical Reports Server (NTRS)

Dunn, William R.; Corliss, Lloyd D.

1991-01-01

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

Software Selection: A Primer on Source and Evaluation.

ERIC Educational Resources Information Center

Burston, Jack

2003-01-01

Provides guidance on making decisions regarding the selection of foreign language instructional software. Identifies sources of foreign language software, indicates sources of foreign language software reviews, and outlines essential procedures of software evaluation. (Author/VWL)

Software Engineering Laboratory Series: Proceedings of the Twentieth Annual Software Engineering Workshop

NASA Technical Reports Server (NTRS)

1995-01-01

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

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

NASA Technical Reports Server (NTRS)

1997-01-01

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

Integrating Testing into Software Engineering Courses Supported by a Collaborative Learning Environment

ERIC Educational Resources Information Center

Clarke, Peter J.; Davis, Debra; King, Tariq M.; Pava, Jairo; Jones, Edward L.

2014-01-01

As software becomes more ubiquitous and complex, the cost of software bugs continues to grow at a staggering rate. To remedy this situation, there needs to be major improvement in the knowledge and application of software validation techniques. Although there are several software validation techniques, software testing continues to be one of the…

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

NASA Technical Reports Server (NTRS)

1996-01-01

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

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

NASA Technical Reports Server (NTRS)

1995-01-01

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

Exploring the Process of Adult Computer Software Training Using Andragogy, Situated Cognition, and a Minimalist Approach

ERIC Educational Resources Information Center

Hurt, Andrew C.

2007-01-01

With technology advances, computer software becomes increasingly difficult to learn. Adults often rely on software training to keep abreast of these changes. Instructor-led software training is frequently used to teach adults new software skills; however there is limited research regarding the best practices in adult computer software training.…

Software cost/resource modeling: Software quality tradeoff measurement

NASA Technical Reports Server (NTRS)

Lawler, R. W.

1980-01-01

A conceptual framework for treating software quality from a total system perspective is developed. Examples are given to show how system quality objectives may be allocated to hardware and software; to illustrate trades among quality factors, both hardware and software, to achieve system performance objectives; and to illustrate the impact of certain design choices on software functionality.

MFV-class: a multi-faceted visualization tool of object classes.

PubMed

Zhang, Zhi-meng; Pan, Yun-he; Zhuang, Yue-ting

2004-11-01

Classes are key software components in an object-oriented software system. In many industrial OO software systems, there are some classes that have complicated structure and relationships. So in the processes of software maintenance, testing, software reengineering, software reuse and software restructure, it is a challenge for software engineers to understand these classes thoroughly. This paper proposes a class comprehension model based on constructivist learning theory, and implements a software visualization tool (MFV-Class) to help in the comprehension of a class. The tool provides multiple views of class to uncover manifold facets of class contents. It enables visualizing three object-oriented metrics of classes to help users focus on the understanding process. A case study was conducted to evaluate our approach and the toolkit.

Software Quality Assurance Audits Guidebooks

NASA Technical Reports Server (NTRS)

1990-01-01

The growth in cost and importance of software to NASA has caused NASA to address the improvement of software development across the agency. One of the products of this program is a series of guidebooks that define a NASA concept of the assurance processes that are used in software development. The Software Assurance Guidebook, NASA-GB-A201, issued in September, 1989, provides an overall picture of the NASA concepts and practices in software assurance. Second level guidebooks focus on specific activities that fall within the software assurance discipline, and provide more detailed information for the manager and/or practitioner. This is the second level Software Quality Assurance Audits Guidebook that describes software quality assurance audits in a way that is compatible with practices at NASA Centers.

Four simple recommendations to encourage best practices in research software

PubMed Central

Jiménez, Rafael C.; Kuzak, Mateusz; Alhamdoosh, Monther; Barker, Michelle; Batut, Bérénice; Borg, Mikael; Capella-Gutierrez, Salvador; Chue Hong, Neil; Cook, Martin; Corpas, Manuel; Flannery, Madison; Garcia, Leyla; Gelpí, Josep Ll.; Gladman, Simon; Goble, Carole; González Ferreiro, Montserrat; Gonzalez-Beltran, Alejandra; Griffin, Philippa C.; Grüning, Björn; Hagberg, Jonas; Holub, Petr; Hooft, Rob; Ison, Jon; Katz, Daniel S.; Leskošek, Brane; López Gómez, Federico; Oliveira, Luis J.; Mellor, David; Mosbergen, Rowland; Mulder, Nicola; Perez-Riverol, Yasset; Pergl, Robert; Pichler, Horst; Pope, Bernard; Sanz, Ferran; Schneider, Maria V.; Stodden, Victoria; Suchecki, Radosław; Svobodová Vařeková, Radka; Talvik, Harry-Anton; Todorov, Ilian; Treloar, Andrew; Tyagi, Sonika; van Gompel, Maarten; Vaughan, Daniel; Via, Allegra; Wang, Xiaochuan; Watson-Haigh, Nathan S.; Crouch, Steve

2017-01-01

Scientific research relies on computer software, yet software is not always developed following practices that ensure its quality and sustainability. This manuscript does not aim to propose new software development best practices, but rather to provide simple recommendations that encourage the adoption of existing best practices. Software development best practices promote better quality software, and better quality software improves the reproducibility and reusability of research. These recommendations are designed around Open Source values, and provide practical suggestions that contribute to making research software and its source code more discoverable, reusable and transparent. This manuscript is aimed at developers, but also at organisations, projects, journals and funders that can increase the quality and sustainability of research software by encouraging the adoption of these recommendations. PMID:28751965

Four simple recommendations to encourage best practices in research software.

PubMed

Jiménez, Rafael C; Kuzak, Mateusz; Alhamdoosh, Monther; Barker, Michelle; Batut, Bérénice; Borg, Mikael; Capella-Gutierrez, Salvador; Chue Hong, Neil; Cook, Martin; Corpas, Manuel; Flannery, Madison; Garcia, Leyla; Gelpí, Josep Ll; Gladman, Simon; Goble, Carole; González Ferreiro, Montserrat; Gonzalez-Beltran, Alejandra; Griffin, Philippa C; Grüning, Björn; Hagberg, Jonas; Holub, Petr; Hooft, Rob; Ison, Jon; Katz, Daniel S; Leskošek, Brane; López Gómez, Federico; Oliveira, Luis J; Mellor, David; Mosbergen, Rowland; Mulder, Nicola; Perez-Riverol, Yasset; Pergl, Robert; Pichler, Horst; Pope, Bernard; Sanz, Ferran; Schneider, Maria V; Stodden, Victoria; Suchecki, Radosław; Svobodová Vařeková, Radka; Talvik, Harry-Anton; Todorov, Ilian; Treloar, Andrew; Tyagi, Sonika; van Gompel, Maarten; Vaughan, Daniel; Via, Allegra; Wang, Xiaochuan; Watson-Haigh, Nathan S; Crouch, Steve

2017-01-01

Scientific research relies on computer software, yet software is not always developed following practices that ensure its quality and sustainability. This manuscript does not aim to propose new software development best practices, but rather to provide simple recommendations that encourage the adoption of existing best practices. Software development best practices promote better quality software, and better quality software improves the reproducibility and reusability of research. These recommendations are designed around Open Source values, and provide practical suggestions that contribute to making research software and its source code more discoverable, reusable and transparent. This manuscript is aimed at developers, but also at organisations, projects, journals and funders that can increase the quality and sustainability of research software by encouraging the adoption of these recommendations.

Software Design Improvements. Part 2; Software Quality and the Design and Inspection Process

NASA Technical Reports Server (NTRS)

Lalli, Vincent R.; Packard, Michael H.; Ziemianski, Tom

1997-01-01

The application of assurance engineering techniques improves the duration of failure-free performance of software. The totality of features and characteristics of a software product are what determine its ability to satisfy customer needs. Software in safety-critical systems is very important to NASA. We follow the System Safety Working Groups definition for system safety software as: 'The optimization of system safety in the design, development, use and maintenance of software and its integration with safety-critical systems in an operational environment. 'If it is not safe, say so' has become our motto. This paper goes over methods that have been used by NASA to make software design improvements by focusing on software quality and the design and inspection process.

Science and Software

NASA Astrophysics Data System (ADS)

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, ideally maintained by someone in a funded position. Perhaps the biggest challenge is the reality that researches who use software, as opposed to develop software, are more attractive university hires because they are more likely to be "big picture" scientists that publish in the highest profile journals, although sometimes the two go together.

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

NASA Astrophysics Data System (ADS)

Hwang, L.; Kellogg, L. H.

2017-12-01

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

Software platform virtualization in chemistry research and university teaching

PubMed Central

2009-01-01

Background Modern chemistry laboratories operate with a wide range of software applications under different operating systems, such as Windows, LINUX or Mac OS X. Instead of installing software on different computers it is possible to install those applications on a single computer using Virtual Machine software. Software platform virtualization allows a single guest operating system to execute multiple other operating systems on the same computer. We apply and discuss the use of virtual machines in chemistry research and teaching laboratories. Results Virtual machines are commonly used for cheminformatics software development and testing. Benchmarking multiple chemistry software packages we have confirmed that the computational speed penalty for using virtual machines is low and around 5% to 10%. Software virtualization in a teaching environment allows faster deployment and easy use of commercial and open source software in hands-on computer teaching labs. Conclusion Software virtualization in chemistry, mass spectrometry and cheminformatics is needed for software testing and development of software for different operating systems. In order to obtain maximum performance the virtualization software should be multi-core enabled and allow the use of multiprocessor configurations in the virtual machine environment. Server consolidation, by running multiple tasks and operating systems on a single physical machine, can lead to lower maintenance and hardware costs especially in small research labs. The use of virtual machines can prevent software virus infections and security breaches when used as a sandbox system for internet access and software testing. Complex software setups can be created with virtual machines and are easily deployed later to multiple computers for hands-on teaching classes. We discuss the popularity of bioinformatics compared to cheminformatics as well as the missing cheminformatics education at universities worldwide. PMID:20150997

Software platform virtualization in chemistry research and university teaching.

PubMed

Kind, Tobias; Leamy, Tim; Leary, Julie A; Fiehn, Oliver

2009-11-16

Modern chemistry laboratories operate with a wide range of software applications under different operating systems, such as Windows, LINUX or Mac OS X. Instead of installing software on different computers it is possible to install those applications on a single computer using Virtual Machine software. Software platform virtualization allows a single guest operating system to execute multiple other operating systems on the same computer. We apply and discuss the use of virtual machines in chemistry research and teaching laboratories. Virtual machines are commonly used for cheminformatics software development and testing. Benchmarking multiple chemistry software packages we have confirmed that the computational speed penalty for using virtual machines is low and around 5% to 10%. Software virtualization in a teaching environment allows faster deployment and easy use of commercial and open source software in hands-on computer teaching labs. Software virtualization in chemistry, mass spectrometry and cheminformatics is needed for software testing and development of software for different operating systems. In order to obtain maximum performance the virtualization software should be multi-core enabled and allow the use of multiprocessor configurations in the virtual machine environment. Server consolidation, by running multiple tasks and operating systems on a single physical machine, can lead to lower maintenance and hardware costs especially in small research labs. The use of virtual machines can prevent software virus infections and security breaches when used as a sandbox system for internet access and software testing. Complex software setups can be created with virtual machines and are easily deployed later to multiple computers for hands-on teaching classes. We discuss the popularity of bioinformatics compared to cheminformatics as well as the missing cheminformatics education at universities worldwide.

Software Fault Tolerance: A Tutorial

NASA Technical Reports Server (NTRS)

Torres-Pomales, Wilfredo

2000-01-01

Because of our present inability to produce error-free software, software fault tolerance is and will continue to be an important consideration in software systems. The root cause of software design errors is the complexity of the systems. Compounding the problems in building correct software is the difficulty in assessing the correctness of software for highly complex systems. After a brief overview of the software development processes, we note how hard-to-detect design faults are likely to be introduced during development and how software faults tend to be state-dependent and activated by particular input sequences. Although component reliability is an important quality measure for system level analysis, software reliability is hard to characterize and the use of post-verification reliability estimates remains a controversial issue. For some applications software safety is more important than reliability, and fault tolerance techniques used in those applications are aimed at preventing catastrophes. Single version software fault tolerance techniques discussed include system structuring and closure, atomic actions, inline fault detection, exception handling, and others. Multiversion techniques are based on the assumption that software built differently should fail differently and thus, if one of the redundant versions fails, it is expected that at least one of the other versions will provide an acceptable output. Recovery blocks, N-version programming, and other multiversion techniques are reviewed.

Software and package applicating for network meta-analysis: A usage-based comparative study.

PubMed

Xu, Chang; Niu, Yuming; Wu, Junyi; Gu, Huiyun; Zhang, Chao

2017-12-21

To compare and analyze the characteristics and functions of software applications for network meta-analysis (NMA). PubMed, EMbase, The Cochrane Library, the official websites of Bayesian inference Using Gibbs Sampling (BUGS), Stata and R, and Google were searched to collect the software and packages for performing NMA; software and packages published up to March 2016 were included. After collecting the software, packages, and their user guides, we used the software and packages to calculate a typical example. All characteristics, functions, and computed results were compared and analyzed. Ten types of software were included, including programming and non-programming software. They were developed mainly based on Bayesian or frequentist theory. Most types of software have the characteristics of easy operation, easy mastery, exact calculation, or excellent graphing. However, there was no single software that performed accurate calculations with superior graphing; this could only be achieved through the combination of two or more types of software. This study suggests that the user should choose the appropriate software according to personal programming basis, operational habits, and financial ability. Then, the choice of the combination of BUGS and R (or Stata) software to perform the NMA is considered. © 2017 Chinese Cochrane Center, West China Hospital of Sichuan University and John Wiley & Sons Australia, Ltd.

Modular Rocket Engine Control Software (MRECS)

NASA Technical Reports Server (NTRS)

Tarrant, C.; Crook, J.

1998-01-01

The Modular Rocket Engine Control Software (MRECS) Program is a technology demonstration effort designed to advance the state-of-the-art in launch vehicle propulsion systems. Its emphasis is on developing and demonstrating a modular software architecture for advanced engine control systems that will result in lower software maintenance (operations) costs. It effectively accommodates software requirement changes that occur due to hardware technology upgrades and engine development testing. Ground rules directed by MSFC were to optimize modularity and implement the software in the Ada programming language. MRECS system software and the software development environment utilize Commercial-Off-the-Shelf (COTS) products. This paper presents the objectives, benefits, and status of the program. The software architecture, design, and development environment are described. MRECS tasks are defined and timing relationships given. Major accomplishments are listed. MRECS offers benefits to a wide variety of advanced technology programs in the areas of modular software architecture, reuse software, and reduced software reverification time related to software changes. MRECS was recently modified to support a Space Shuttle Main Engine (SSME) hot-fire test. Cold Flow and Flight Readiness Testing were completed before the test was cancelled. Currently, the program is focused on supporting NASA MSFC in accomplishing development testing of the Fastrac Engine, part of NASA's Low Cost Technologies (LCT) Program. MRECS will be used for all engine development testing.

An Interoperability Framework and Capability Profiling for Manufacturing Software

NASA Astrophysics Data System (ADS)

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.

Wildlife software: procedures for publication of computer software

USGS Publications Warehouse

Samuel, M.D.

1990-01-01

Computers and computer software have become an integral part of the practice of wildlife science. Computers now play an important role in teaching, research, and management applications. Because of the specialized nature of wildlife problems, specific computer software is usually required to address a given problem (e.g., home range analysis). This type of software is not usually available from commercial vendors and therefore must be developed by those wildlife professionals with particular skill in computer programming. Current journal publication practices generally prevent a detailed description of computer software associated with new techniques. In addition, peer review of journal articles does not usually include a review of associated computer software. Thus, many wildlife professionals are usually unaware of computer software that would meet their needs or of major improvements in software they commonly use. Indeed most users of wildlife software learn of new programs or important changes only by word of mouth.

A Case Study of Measuring Process Risk for Early Insights into Software Safety

NASA Technical Reports Server (NTRS)

Layman, Lucas; Basili, Victor; Zelkowitz, Marvin V.; Fisher, Karen L.

2011-01-01

In this case study, we examine software safety risk in three flight hardware systems in NASA's Constellation spaceflight program. We applied our Technical and Process Risk Measurement (TPRM) methodology to the Constellation hazard analysis process to quantify the technical and process risks involving software safety in the early design phase of these projects. We analyzed 154 hazard reports and collected metrics to measure the prevalence of software in hazards and the specificity of descriptions of software causes of hazardous conditions. We found that 49-70% of 154 hazardous conditions could be caused by software or software was involved in the prevention of the hazardous condition. We also found that 12-17% of the 2013 hazard causes involved software, and that 23-29% of all causes had a software control. The application of the TPRM methodology identified process risks in the application of the hazard analysis process itself that may lead to software safety risk.

AVE-SESAME program for the REEDA System

NASA Technical Reports Server (NTRS)

Hickey, J. S.

1981-01-01

The REEDA system software was modified and improved to process the AVE-SESAME severe storm data. A random access file system for the AVE storm data was designed, tested, and implemented. The AVE/SESAME software was modified to incorporate the random access file input and to interface with new graphics hardware/software now available on the REEDA system. Software was developed to graphically display the AVE/SESAME data in the convention normally used by severe storm researchers. Software was converted to AVE/SESAME software systems and interfaced with existing graphics hardware/software available on the REEDA System. Software documentation was provided for existing AVE/SESAME programs underlining functional flow charts and interacting questions. All AVE/SESAME data sets in random access format was processed to allow developed software to access the entire AVE/SESAME data base. The existing software was modified to allow for processing of different AVE/SESAME data set types including satellite surface and radar data.

Space Station Software Recommendations

NASA Technical Reports Server (NTRS)

Voigt, S. (Editor)

1985-01-01

Four panels of invited experts and NASA representatives focused on the following topics: software management, software development environment, languages, and software standards. Each panel deliberated in private, held two open sessions with audience participation, and developed recommendations for the NASA Space Station Program. The major thrusts of the recommendations were as follows: (1) The software management plan should establish policies, responsibilities, and decision points for software acquisition; (2) NASA should furnish a uniform modular software support environment and require its use for all space station software acquired (or developed); (3) The language Ada should be selected for space station software, and NASA should begin to address issues related to the effective use of Ada; and (4) The space station software standards should be selected (based upon existing standards where possible), and an organization should be identified to promulgate and enforce them. These and related recommendations are described in detail in the conference proceedings.

A Novel Method for Mining SaaS Software Tag via Community Detection in Software Services Network

NASA Astrophysics Data System (ADS)

Qin, Li; Li, Bing; Pan, Wei-Feng; Peng, Tao

The number of online software services based on SaaS paradigm is increasing. However, users usually find it hard to get the exact software services they need. At present, tags are widely used to annotate specific software services and also to facilitate the searching of them. Currently these tags are arbitrary and ambiguous since mostly of them are generated manually by service developers. This paper proposes a method for mining tags from the help documents of software services. By extracting terms from the help documents and calculating the similarity between the terms, we construct a software similarity network where nodes represent software services, edges denote the similarity relationship between software services, and the weights of the edges are the similarity degrees. The hierarchical clustering algorithm is used for community detection in this software similarity network. At the final stage, tags are mined for each of the communities and stored as ontology.

Orbiter subsystem hardware/software interaction analysis. Volume 8: AFT reaction control system, part 2

NASA Technical Reports Server (NTRS)

Becker, D. D.

1980-01-01

The orbiter subsystems and interfacing program elements which interact with the orbiter computer flight software are analyzed. The failure modes identified in the subsystem/element failure mode and effects analysis are examined. Potential interaction with the software is examined through an evaluation of the software requirements. The analysis is restricted to flight software requirements and excludes utility/checkout software. The results of the hardware/software interaction analysis for the forward reaction control system are presented.

Semantic Metrics for Analysis of Software

NASA Technical Reports Server (NTRS)

Etzkorn, Letha H.; Cox, Glenn W.; Farrington, Phil; Utley, Dawn R.; Ghalston, Sampson; Stein, Cara

2005-01-01

A recently conceived suite of object-oriented software metrics focus is on semantic aspects of software, in contradistinction to traditional software metrics, which focus on syntactic aspects of software. Semantic metrics represent a more human-oriented view of software than do syntactic metrics. The semantic metrics of a given computer program are calculated by use of the output of a knowledge-based analysis of the program, and are substantially more representative of software quality and more readily comprehensible from a human perspective than are the syntactic metrics.

Current Practice in Software Development for Computational Neuroscience and How to Improve It

PubMed Central

Gewaltig, Marc-Oliver; Cannon, Robert

2014-01-01

Almost all research work in computational neuroscience involves software. As researchers try to understand ever more complex systems, there is a continual need for software with new capabilities. Because of the wide range of questions being investigated, new software is often developed rapidly by individuals or small groups. In these cases, it can be hard to demonstrate that the software gives the right results. Software developers are often open about the code they produce and willing to share it, but there is little appreciation among potential users of the great diversity of software development practices and end results, and how this affects the suitability of software tools for use in research projects. To help clarify these issues, we have reviewed a range of software tools and asked how the culture and practice of software development affects their validity and trustworthiness. We identified four key questions that can be used to categorize software projects and correlate them with the type of product that results. The first question addresses what is being produced. The other three concern why, how, and by whom the work is done. The answers to these questions show strong correlations with the nature of the software being produced, and its suitability for particular purposes. Based on our findings, we suggest ways in which current software development practice in computational neuroscience can be improved and propose checklists to help developers, reviewers, and scientists to assess the quality of software and whether particular pieces of software are ready for use in research. PMID:24465191

Current practice in software development for computational neuroscience and how to improve it.

PubMed

Gewaltig, Marc-Oliver; Cannon, Robert

2014-01-01

Almost all research work in computational neuroscience involves software. As researchers try to understand ever more complex systems, there is a continual need for software with new capabilities. Because of the wide range of questions being investigated, new software is often developed rapidly by individuals or small groups. In these cases, it can be hard to demonstrate that the software gives the right results. Software developers are often open about the code they produce and willing to share it, but there is little appreciation among potential users of the great diversity of software development practices and end results, and how this affects the suitability of software tools for use in research projects. To help clarify these issues, we have reviewed a range of software tools and asked how the culture and practice of software development affects their validity and trustworthiness. We identified four key questions that can be used to categorize software projects and correlate them with the type of product that results. The first question addresses what is being produced. The other three concern why, how, and by whom the work is done. The answers to these questions show strong correlations with the nature of the software being produced, and its suitability for particular purposes. Based on our findings, we suggest ways in which current software development practice in computational neuroscience can be improved and propose checklists to help developers, reviewers, and scientists to assess the quality of software and whether particular pieces of software are ready for use in research.

The Influence of Software Complexity on the Maintenance Effort: Case Study on Software Developed within Educational Process

ERIC Educational Resources Information Center

Radulescu, Iulian Ionut

2006-01-01

Software complexity is the most important software quality attribute and a very useful instrument in the study of software quality. Is one of the factors that affect most of the software quality characteristics, including maintainability. It is very important to quantity this influence and identify the means to keep it under control; by using…

Proceedings of the Ninth Annual Software Engineering Workshop

NASA Technical Reports Server (NTRS)

1984-01-01

Experiences in measurement, utilization, and evaluation of software methodologies, models, and tools are discussed. NASA's involvement in ever larger and more complex systems, like the space station project, provides a motive for the support of software engineering research and the exchange of ideas in such forums. The topics of current SEL research are software error studies, experiments with software development, and software tools.

Software Engineering Laboratory Series: Proceedings of the Twenty-First Annual Software Engineering Workshop

NASA Technical Reports Server (NTRS)

1996-01-01

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

FMT (Flight Software Memory Tracker) For Cassini Spacecraft-Software Engineering Using JAVA

NASA Technical Reports Server (NTRS)

Kan, Edwin P.; Uffelman, Hal; Wax, Allan H.

1997-01-01

The software engineering design of the Flight Software Memory Tracker (FMT) Tool is discussed in this paper. FMT is a ground analysis software set, consisting of utilities and procedures, designed to track the flight software, i.e., images of memory load and updatable parameters of the computers on-board Cassini spacecraft. FMT is implemented in Java.

Software Engineering Laboratory Series: Proceedings of the Twenty-Second Annual Software Engineering Workshop

NASA Technical Reports Server (NTRS)

1997-01-01

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

In the right order of brush strokes: a sketch of a software philosophy retrospective.

PubMed

Pyshkin, Evgeny

2014-01-01

This paper follows a discourse on software recognized as a product of art and human creativity progressing probably for as long as software exists. A retrospective view on computer science and software philosophy development is introduced. In so doing we discover parallels between software and various branches of human creative manifestations. Aesthetic properties and mutual dependency of the form and matter of art works are examined in their application to software programs. While exploring some philosophical and even artistic reflection on software we consider extended comprehension of technical sciences of programming and software engineering within the realm of liberal arts.

OntoSoft: A Software Registry for Geosciences

NASA Astrophysics Data System (ADS)

Garijo, D.; Gil, Y.

2017-12-01

The goal of the EarthCube OntoSoft project is to enable the creation of an ecosystem for software stewardship in geosciences that will empower scientists to manage their software as valuable scientific assets. By sharing software metadata in OntoSoft, scientists enable broader access to that software by other scientists, software professionals, students, and decision makers. Our work to date includes: 1) an ontology for describing scientific software metadata, 2) a distributed scientific software repository that contains more than 750 entries that can be searched and compared across metadata fields, 3) an intelligent user interface that guides scientists to publish software and allows them to crowdsource its corresponding metadata. We have also developed a training program where scientists learn to describe and cite software in their papers in addition to data and provenance, and we are using OntoSoft to show them the benefits of publishing their software metadata. This training program is part of a Geoscience Papers of the Future Initiative, where scientists are reflecting on their current practices, benefits and effort for sharing software and data. This journal paper can be submitted to a Special Section of the AGU Earth and Space Science Journal.

Requirements: Towards an understanding on why software projects fail

NASA Astrophysics Data System (ADS)

Hussain, Azham; Mkpojiogu, Emmanuel O. C.

2016-08-01

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

Workflow-Based Software Development Environment

NASA Technical Reports Server (NTRS)

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

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

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

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

2005-01-01

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

The development and technology transfer of software engineering technology at NASA. Johnson Space Center

NASA Technical Reports Server (NTRS)

Pitman, C. L.; Erb, D. M.; Izygon, M. E.; Fridge, E. M., III; Roush, G. B.; Braley, D. M.; Savely, R. T.

1992-01-01

The United State's big space projects of the next decades, such as Space Station and the Human Exploration Initiative, will need the development of many millions of lines of mission critical software. NASA-Johnson (JSC) is identifying and developing some of the Computer Aided Software Engineering (CASE) technology that NASA will need to build these future software systems. The goal is to improve the quality and the productivity of large software development projects. New trends are outlined in CASE technology and how the Software Technology Branch (STB) at JSC is endeavoring to provide some of these CASE solutions for NASA is described. Key software technology components include knowledge-based systems, software reusability, user interface technology, reengineering environments, management systems for the software development process, software cost models, repository technology, and open, integrated CASE environment frameworks. The paper presents the status and long-term expectations for CASE products. The STB's Reengineering Application Project (REAP), Advanced Software Development Workstation (ASDW) project, and software development cost model (COSTMODL) project are then discussed. Some of the general difficulties of technology transfer are introduced, and a process developed by STB for CASE technology insertion is described.

Conhecimento Científico e Cotidiano em Astronomia: Uma Investigação com Alunos da Educação Básica

NASA Astrophysics Data System (ADS)

Vieira, J. B.; Longhini, M. D.

2011-12-01

Este texto apresenta resultados de uma investigação que teve como objetivo, investigar como os conhecimentos científicos e do cotidiano relacionados a essa área de conhecimento apresentam na escola de Educação Básica, especialmente, em alunos do Ensino Médio prestes a deixar Educação Básica. Para realização da pesquisa, utilizamos como recurso metodológico a aplicação de um questionário estruturado contendo 47 questões, organizadas em duas categorias: Conhecimento Cotidiano e Conhecimento Científico. As questões da categoria “Conhecimento Cotidiano” possuíam afirmações relacionadas a crendices, contos populares, especulações e temáticas do gênero, as quais, geralmente, estão fora do círculo de discussão da comunidade científica, talvez por não serem consideradas como objeto de estudo da ciência. As questões da categoria “Conhecimento Científico” são relacionadas a conteúdos específicos de Astronomia, as quais são compartilhadas pela comunidade científica e aceitas, pelo menos provisoriamente, como possuindo fundamentação científica. Concluímos que, possuem ainda concepções de temas Astronômicos persistentes à mudança, por exemplo, fases da Lua relacionadas à melhor período para corte de cabelo e também para plantio; estrela cadente e ocasião perfeita para se fazer um pedido. Entretanto, podemos observar no que diz respeito a mitos e superstições, que quase não existe influência destes entre os alunos. Portanto, ao trabalharmos com os alunos determinados conceitos científicos, é importante lembrarmos que o professor não opera no vazio; os alunos são sujeitos de saberes, práticas e, dessa forma constroem e reconstroem saberes. Cabe ao professor ouvir os estudantes reconstruindo junto deles conceitos científicos. Acreditamos que o ensino de Ciências na Educação Básica deve lidar criticamente com o conhecimento cotidiano e científico e, assim, efetivar a Ciência como disciplina educativa, formativa e libertadora.

Software Engineering for Human Spaceflight

NASA Technical Reports Server (NTRS)

Fredrickson, Steven E.

2014-01-01

The Spacecraft Software Engineering Branch of NASA Johnson Space Center (JSC) provides world-class products, leadership, and technical expertise in software engineering, processes, technology, and systems management for human spaceflight. The branch contributes to major NASA programs (e.g. ISS, MPCV/Orion) with in-house software development and prime contractor oversight, and maintains the JSC Engineering Directorate CMMI rating for flight software development. Software engineering teams work with hardware developers, mission planners, and system operators to integrate flight vehicles, habitats, robotics, and other spacecraft elements. They seek to infuse automation and autonomy into missions, and apply new technologies to flight processor and computational architectures. This presentation will provide an overview of key software-related projects, software methodologies and tools, and technology pursuits of interest to the JSC Spacecraft Software Engineering Branch.

Software Design Improvements. Part 1; Software Benefits and Limitations

NASA Technical Reports Server (NTRS)

Lalli, Vincent R.; Packard, Michael H.; Ziemianski, Tom

1997-01-01

Computer hardware and associated software have been used for many years to process accounting information, to analyze test data and to perform engineering analysis. Now computers and software also control everything from automobiles to washing machines and the number and type of applications are growing at an exponential rate. The size of individual program has shown similar growth. Furthermore, software and hardware are used to monitor and/or control potentially dangerous products and safety-critical systems. These uses include everything from airplanes and braking systems to medical devices and nuclear plants. The question is: how can this hardware and software be made more reliable? Also, how can software quality be improved? What methodology needs to be provided on large and small software products to improve the design and how can software be verified?

Software Engineering Improvement Plan

NASA Technical Reports Server (NTRS)

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.

Designing Computerized Provider Order Entry Software in Iran: The Nurses' and Physicians' Viewpoints.

PubMed

Khammarnia, Mohammad; Sharifian, Roxana; Zand, Farid; Keshtkaran, Ali; Barati, Omid

2016-09-01

This study aimed to identify the functional requirements of computerized provider order entry software and design this software in Iran. This study was conducted using review documentation, interview, and focus group discussions in Shiraz University of Medical Sciences, as the medical pole in Iran, in 2013-2015. The study sample consisted of physicians (n = 12) and nurses (n = 2) in the largest hospital in the southern part of Iran and information technology experts (n = 5) in Shiraz University of Medical Sciences. Functional requirements of the computerized provider order entry system were examined in three phases. Finally, the functional requirements were distributed in four levels, and accordingly, the computerized provider order entry software was designed. The software had seven main dimensions: (1) data entry, (2) drug interaction management system, (3) warning system, (4) treatment services, (5) ability to write in software, (6) reporting from all sections of the software, and (7) technical capabilities of the software. The nurses and physicians emphasized quick access to the computerized provider order entry software, order prescription section, and applicability of the software. The software had some items that had not been mentioned in other studies. Ultimately, the software was designed by a company specializing in hospital information systems in Iran. This study was the first specific investigation of computerized provider order entry software design in Iran. Based on the results, it is suggested that this software be implemented in hospitals.

Testing Scientific Software: A Systematic Literature Review

PubMed Central

Kanewala, Upulee; Bieman, James M.

2014-01-01

Context Scientific software plays an important role in critical decision making, for example making weather predictions based on climate models, and computation of evidence for research publications. Recently, scientists have had to retract publications due to errors caused by software faults. Systematic testing can identify such faults in code. Objective This study aims to identify specific challenges, proposed solutions, and unsolved problems faced when testing scientific software. Method We conducted a systematic literature survey to identify and analyze relevant literature. We identified 62 studies that provided relevant information about testing scientific software. Results We found that challenges faced when testing scientific software fall into two main categories: (1) testing challenges that occur due to characteristics of scientific software such as oracle problems and (2) testing challenges that occur due to cultural differences between scientists and the software engineering community such as viewing the code and the model that it implements as inseparable entities. In addition, we identified methods to potentially overcome these challenges and their limitations. Finally we describe unsolved challenges and how software engineering researchers and practitioners can help to overcome them. Conclusions Scientific software presents special challenges for testing. Specifically, cultural differences between scientist developers and software engineers, along with the characteristics of the scientific software make testing more difficult. Existing techniques such as code clone detection can help to improve the testing process. Software engineers should consider special challenges posed by scientific software such as oracle problems when developing testing techniques. PMID:25125798

Software engineering methodologies and tools

NASA Technical Reports Server (NTRS)

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.

Software Engineering Education Directory

DTIC Science & Technology

1990-04-01

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

Finding Helpful Software Reviews.

ERIC Educational Resources Information Center

Kruse, Ted, Comp.

1987-01-01

Provides a list of evaluation services currently producing critical reviews of educational software. Includes information about The Apple K-12 Curriculum Software Reference, The Educational Software Preview, The Educational Software Selector, MicroSIFT, and Only The Best: The Discriminating Guide for Preschool-Grade 12. (TW)

Proceedings of the Thirteenth Annual Software Engineering Workshop

NASA Technical Reports Server (NTRS)

1988-01-01

Topics covered in the workshop included studies and experiments conducted in the Software Engineering Laboratory (SEL), a cooperative effort of NASA Goddard Space Flight Center, the University of Maryland, and Computer Sciences Corporation; software models; software products; and software tools.

TMT approach to observatory software development process

NASA Astrophysics Data System (ADS)

Buur, Hanne; Subramaniam, Annapurni; Gillies, Kim; Dumas, Christophe; Bhatia, Ravinder

2016-07-01

The purpose of the Observatory Software System (OSW) is to integrate all software and hardware components of the Thirty Meter Telescope (TMT) to enable observations and data capture; thus it is a complex software system that is defined by four principal software subsystems: Common Software (CSW), Executive Software (ESW), Data Management System (DMS) and Science Operations Support System (SOSS), all of which have interdependencies with the observatory control systems and data acquisition systems. Therefore, the software development process and plan must consider dependencies to other subsystems, manage architecture, interfaces and design, manage software scope and complexity, and standardize and optimize use of resources and tools. Additionally, the TMT Observatory Software will largely be developed in India through TMT's workshare relationship with the India TMT Coordination Centre (ITCC) and use of Indian software industry vendors, which adds complexity and challenges to the software development process, communication and coordination of activities and priorities as well as measuring performance and managing quality and risk. The software project management challenge for the TMT OSW is thus a multi-faceted technical, managerial, communications and interpersonal relations challenge. The approach TMT is using to manage this multifaceted challenge is a combination of establishing an effective geographically distributed software team (Integrated Product Team) with strong project management and technical leadership provided by the TMT Project Office (PO) and the ITCC partner to manage plans, process, performance, risk and quality, and to facilitate effective communications; establishing an effective cross-functional software management team composed of stakeholders, OSW leadership and ITCC leadership to manage dependencies and software release plans, technical complexities and change to approved interfaces, architecture, design and tool set, and to facilitate effective communications; adopting an agile-based software development process across the observatory to enable frequent software releases to help mitigate subsystem interdependencies; defining concise scope and work packages for each of the OSW subsystems to facilitate effective outsourcing of software deliverables to the ITCC partner, and to enable performance monitoring and risk management. At this stage, the architecture and high-level design of the software system has been established and reviewed. During construction each subsystem will have a final design phase with reviews, followed by implementation and testing. The results of the TMT approach to the Observatory Software development process will only be preliminary at the time of the submittal of this paper, but it is anticipated that the early results will be a favorable indication of progress.

Improving Software Sustainability: Lessons Learned from Profiles in Science.

PubMed

Gallagher, Marie E

2013-01-01

The Profiles in Science® digital library features digitized surrogates of historical items selected from the archival collections of the U.S. National Library of Medicine as well as collaborating institutions. In addition, it contains a database of descriptive, technical and administrative metadata. It also contains various software components that allow creation of the metadata, management of the digital items, and access to the items and metadata through the Profiles in Science Web site [1]. The choices made building the digital library were designed to maximize the sustainability and long-term survival of all of the components of the digital library [2]. For example, selecting standard and open digital file formats rather than proprietary formats increases the sustainability of the digital files [3]. Correspondingly, using non-proprietary software may improve the sustainability of the software--either through in-house expertise or through the open source community. Limiting our digital library software exclusively to open source software or to software developed in-house has not been feasible. For example, we have used proprietary operating systems, scanning software, a search engine, and office productivity software. We did this when either lack of essential capabilities or the cost-benefit trade-off favored using proprietary software. We also did so knowing that in the future we would need to replace or upgrade some of our proprietary software, analogous to migrating from an obsolete digital file format to a new format as the technological landscape changes. Since our digital library's start in 1998, all of its software has been upgraded or replaced, but the digitized items have not yet required migration to other formats. Technological changes that compelled us to replace proprietary software included the cost of product licensing, product support, incompatibility with other software, prohibited use due to evolving security policies, and product abandonment. Sometimes these changes happen on short notice, so we continually monitor our library's software for signs of endangerment. We have attempted to replace proprietary software with suitable in-house or open source software. When the replacement involves a standalone piece of software with a nearly equivalent version, such as replacing a commercial HTTP server with an open source HTTP server, the replacement is straightforward. Recently we replaced software that functioned not only as our search engine but also as the backbone of the architecture of our Web site. In this paper, we describe the lessons learned and the pros and cons of replacing this software with open source software.

Automated support for experience-based software management

NASA Technical Reports Server (NTRS)

Valett, Jon D.

1992-01-01

To effectively manage a software development project, the software manager must have access to key information concerning a project's status. This information includes not only data relating to the project of interest, but also, the experience of past development efforts within the environment. This paper describes the concepts and functionality of a software management tool designed to provide this information. This tool, called the Software Management Environment (SME), enables the software manager to compare an ongoing development effort with previous efforts and with models of the 'typical' project within the environment, to predict future project status, to analyze a project's strengths and weaknesses, and to assess the project's quality. In order to provide these functions the tool utilizes a vast corporate memory that includes a data base of software metrics, a set of models and relationships that describe the software development environment, and a set of rules that capture other knowledge and experience of software managers within the environment. Integrating these major concepts into one software management tool, the SME is a model of the type of management tool needed for all software development organizations.

Gabapentina a dosis de 300 vs. 450 mg como premedicación anestésica para hipertensión reactiva, ansiedad y analgesia.

PubMed

Rascón-Martínez, Dulce María; Guzmán-Sánchez, Joaquín Antonio; Corral-Urdapilleta, Nora Paulina; Arguelles-Uribe, Gema Damaris; Velázquez-Loeza, Jazmín; Soto-Palma, Gustavo; Carrillo-Torres, Orlando

Observar el comportamiento de la gabapentina para aminorar la hipertensión reactiva secundaria a ansiedad y dolor en pacientes sometidos a cirugía oftálmica, así como el consumo de opiáceos entre los grupos. Ensayo clínico controlado aleatorizado y doble ciego que analizó a 125 pacientes divididos en tres grupos: grupo A, gabapentina 300 mg; grupo B, gabapentina 450 mg; grupo C, amaranto en grageas como control 2 horas antes del procedimiento quirúrgico. Se utilizó la prueba de ji al cuadrado para variables sociodemográficas y ANOVA de un factor para variables numéricas continuas. Se consideró como significativo un valor de p < 0.05 para un estudio de dos colas con un poder beta del 80%. La ansiedad y la analgesia transoperatoria y posoperatoria tuvieron diferencias significativas entre los grupos. Se encontró menor consumo de opiáceos en los grupos que usaron gabapentina. La gabapentina por vía oral, 300 o 450 mg, 2 horas antes de la cirugía, reduce el dolor, la ansiedad y el consumo de opiáceos durante el posoperatorio en pacientes sometidos a cirugía oftalmológica. Copyright: © 2018 SecretarÍa de Salud

Software Architecture for Big Data Systems

DTIC Science & Technology

2014-03-27

Software Architecture: Trends and New Directions #SEIswArch © 2014 Carnegie Mellon University Software Architecture for Big Data Systems...AND SUBTITLE Software Architecture for Big Data Systems 5a. CONTRACT NUMBER 5b. GRANT NUMBER 5c. PROGRAM ELEMENT NUMBER 6. AUTHOR(S) 5d. PROJECT...ih - . Software Architecture: Trends and New Directions #SEIswArch © 2014 Carnegie Mellon University WHAT IS BIG DATA ? FROM A SOFTWARE

Statistical Software Engineering

DTIC Science & Technology

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

University Approaches to Software Copyright and Licensure Policies.

ERIC Educational Resources Information Center

Hawkins, Brian L.

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

Software Reviews Since Acquisition Reform - The Artifact Perspective

DTIC Science & Technology

2004-01-01

Risk Management OLD NEW Slide 13Acquisition of Software Intensive Systems 2004 – Peter Hantos Single, basic software paradigm Single processor Low...software risk mitigation related trade-offs must be done together Integral Software Engineering Activities Process Maturity and Quality Frameworks Quality

48 CFR 227.7203-1 - Policy.

Code of Federal Regulations, 2014 CFR

2014-10-01

... OF DEFENSE GENERAL CONTRACTING REQUIREMENTS PATENTS, DATA, AND COPYRIGHTS Rights in Computer Software and Computer Software Documentation 227.7203-1 Policy. (a) DoD policy is to acquire only the computer software and computer software documentation, and the rights in such software or documentation, necessary...

48 CFR 227.7203-1 - Policy.

Code of Federal Regulations, 2011 CFR

2011-10-01

... OF DEFENSE GENERAL CONTRACTING REQUIREMENTS PATENTS, DATA, AND COPYRIGHTS Rights in Computer Software and Computer Software Documentation 227.7203-1 Policy. (a) DoD policy is to acquire only the computer software and computer software documentation, and the rights in such software or documentation, necessary...

48 CFR 227.7203-4 - License rights.

Code of Federal Regulations, 2014 CFR

2014-10-01

... Software and Computer Software Documentation 227.7203-4 License rights. (a) Grant of license. The Government obtains rights in computer software or computer software documentation, including a copyright license, under an irrevocable license granted or obtained by the contractor which developed the software...

48 CFR 227.7203-1 - Policy.

Code of Federal Regulations, 2010 CFR

2010-10-01

... OF DEFENSE GENERAL CONTRACTING REQUIREMENTS PATENTS, DATA, AND COPYRIGHTS Rights in Computer Software and Computer Software Documentation 227.7203-1 Policy. (a) DoD policy is to acquire only the computer software and computer software documentation, and the rights in such software or documentation, necessary...

48 CFR 227.7203-4 - License rights.

Code of Federal Regulations, 2013 CFR

2013-10-01

... Software and Computer Software Documentation 227.7203-4 License rights. (a) Grant of license. The Government obtains rights in computer software or computer software documentation, including a copyright license, under an irrevocable license granted or obtained by the contractor which developed the software...

48 CFR 227.7203-1 - Policy.

Code of Federal Regulations, 2013 CFR

2013-10-01

... OF DEFENSE GENERAL CONTRACTING REQUIREMENTS PATENTS, DATA, AND COPYRIGHTS Rights in Computer Software and Computer Software Documentation 227.7203-1 Policy. (a) DoD policy is to acquire only the computer software and computer software documentation, and the rights in such software or documentation, necessary...

48 CFR 227.7203-4 - License rights.

Code of Federal Regulations, 2012 CFR

2012-10-01

... Software and Computer Software Documentation 227.7203-4 License rights. (a) Grant of license. The Government obtains rights in computer software or computer software documentation, including a copyright license, under an irrevocable license granted or obtained by the contractor which developed the software...

48 CFR 227.7203-1 - Policy.

Code of Federal Regulations, 2012 CFR

2012-10-01

... OF DEFENSE GENERAL CONTRACTING REQUIREMENTS PATENTS, DATA, AND COPYRIGHTS Rights in Computer Software and Computer Software Documentation 227.7203-1 Policy. (a) DoD policy is to acquire only the computer software and computer software documentation, and the rights in such software or documentation, necessary...

48 CFR 227.7203-4 - License rights.

Code of Federal Regulations, 2010 CFR

2010-10-01

... Software and Computer Software Documentation 227.7203-4 License rights. (a) Grant of license. The Government obtains rights in computer software or computer software documentation, including a copyright license, under an irrevocable license granted or obtained by the contractor which developed the software...

48 CFR 227.7203-4 - License rights.

Code of Federal Regulations, 2011 CFR

2011-10-01

... Software and Computer Software Documentation 227.7203-4 License rights. (a) Grant of license. The Government obtains rights in computer software or computer software documentation, including a copyright license, under an irrevocable license granted or obtained by the contractor which developed the software...

48 CFR 227.7205 - Contracts for special works.

Code of Federal Regulations, 2014 CFR

2014-10-01

... Computer Software and Computer Software Documentation 227.7205 Contracts for special works. (a) Use the... a specific need to control the distribution of computer software or computer software documentation..., modification, reproduction, release, performance, display, or disclosure of such software or documentation. Use...

Low Cost Ways to Keep Software Current.

ERIC Educational Resources Information Center

Schultheis, Robert A.

1992-01-01

Discusses strategies for providing students with current computer software technology including acquiring previous versions of software, obtaining demonstration software, using student versions, getting examination software, buying from mail order firms, buying few copies, exploring site licenses, acquiring shareware or freeware, and applying for…

48 CFR 227.7205 - Contracts for special works.

Code of Federal Regulations, 2010 CFR

2010-10-01

... Computer Software and Computer Software Documentation 227.7205 Contracts for special works. (a) Use the... a specific need to control the distribution of computer software or computer software documentation..., modification, reproduction, release, performance, display, or disclosure of such software or documentation. Use...

48 CFR 208.7400 - Scope of subpart.

Code of Federal Regulations, 2010 CFR

2010-10-01

... OF DEFENSE ACQUISITION PLANNING REQUIRED SOURCES OF SUPPLIES AND SERVICES Enterprise Software... commercial software and software maintenance, including software and software maintenance that is acquired— (a) As part of a system or system upgrade, where practicable; (b) Under a service contract; (c) Under...

Infusing Reliability Techniques into Software Safety Analysis

NASA Technical Reports Server (NTRS)

Shi, Ying

2015-01-01

Software safety analysis for a large software intensive system is always a challenge. Software safety practitioners need to ensure that software related hazards are completely identified, controlled, and tracked. This paper discusses in detail how to incorporate the traditional reliability techniques into the entire software safety analysis process. In addition, this paper addresses how information can be effectively shared between the various practitioners involved in the software safety analyses. The author has successfully applied the approach to several aerospace applications. Examples are provided to illustrate the key steps of the proposed approach.

Software for aerospace education: A bibliography, 2nd edition

NASA Technical Reports Server (NTRS)

Vogt, Gregory L.; Roth, Susan Kies; Phelps, Malcom V.

1990-01-01

This is the second aerospace education software bibliography to be published by the NASA Educational Technology Branch in Washington, DC. Unlike many software bibliographies, this bibliography does not evaluate and grade software according to its quality and value to the classroom, nor does it make any endorsements or warrant scientific accuracy. Rather, it describes software, its subject, approach, and technical details. This bibliography is intended as a convenience to educators. The specific software included represents replies to more than 300 queries to software producers for aerospace education programs.

QuantWorm: a comprehensive software package for Caenorhabditis elegans phenotypic assays.

PubMed

Jung, Sang-Kyu; Aleman-Meza, Boanerges; Riepe, Celeste; Zhong, Weiwei

2014-01-01

Phenotypic assays are crucial in genetics; however, traditional methods that rely on human observation are unsuitable for quantitative, large-scale experiments. Furthermore, there is an increasing need for comprehensive analyses of multiple phenotypes to provide multidimensional information. Here we developed an automated, high-throughput computer imaging system for quantifying multiple Caenorhabditis elegans phenotypes. Our imaging system is composed of a microscope equipped with a digital camera and a motorized stage connected to a computer running the QuantWorm software package. Currently, the software package contains one data acquisition module and four image analysis programs: WormLifespan, WormLocomotion, WormLength, and WormEgg. The data acquisition module collects images and videos. The WormLifespan software counts the number of moving worms by using two time-lapse images; the WormLocomotion software computes the velocity of moving worms; the WormLength software measures worm body size; and the WormEgg software counts the number of eggs. To evaluate the performance of our software, we compared the results of our software with manual measurements. We then demonstrated the application of the QuantWorm software in a drug assay and a genetic assay. Overall, the QuantWorm software provided accurate measurements at a high speed. Software source code, executable programs, and sample images are available at www.quantworm.org. Our software package has several advantages over current imaging systems for C. elegans. It is an all-in-one package for quantifying multiple phenotypes. The QuantWorm software is written in Java and its source code is freely available, so it does not require use of commercial software or libraries. It can be run on multiple platforms and easily customized to cope with new methods and requirements.

Ground Software Maintenance Facility (GSMF) system manual

NASA Technical Reports Server (NTRS)

Derrig, D.; Griffith, G.

1986-01-01

The Ground Software Maintenance Facility (GSMF) is designed to support development and maintenance of spacelab ground support software. THE GSMF consists of a Perkin Elmer 3250 (Host computer) and a MITRA 125s (ATE computer), with appropriate interface devices and software to simulate the Electrical Ground Support Equipment (EGSE). This document is presented in three sections: (1) GSMF Overview; (2) Software Structure; and (3) Fault Isolation Capability. The overview contains information on hardware and software organization along with their corresponding block diagrams. The Software Structure section describes the modes of software structure including source files, link information, and database files. The Fault Isolation section describes the capabilities of the Ground Computer Interface Device, Perkin Elmer host, and MITRA ATE.

Software reliability models for critical applications

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

Pham, H.; Pham, M.

This report presents the results of the first phase of the ongoing EG G Idaho, Inc. Software Reliability Research Program. The program is studying the existing software reliability models and proposes a state-of-the-art software reliability model that is relevant to the nuclear reactor control environment. This report consists of three parts: (1) summaries of the literature review of existing software reliability and fault tolerant software reliability models and their related issues, (2) proposed technique for software reliability enhancement, and (3) general discussion and future research. The development of this proposed state-of-the-art software reliability model will be performed in the secondmore » place. 407 refs., 4 figs., 2 tabs.« less

Software reliability models for critical applications

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

Pham, H.; Pham, M.

This report presents the results of the first phase of the ongoing EG&G Idaho, Inc. Software Reliability Research Program. The program is studying the existing software reliability models and proposes a state-of-the-art software reliability model that is relevant to the nuclear reactor control environment. This report consists of three parts: (1) summaries of the literature review of existing software reliability and fault tolerant software reliability models and their related issues, (2) proposed technique for software reliability enhancement, and (3) general discussion and future research. The development of this proposed state-of-the-art software reliability model will be performed in the second place.more » 407 refs., 4 figs., 2 tabs.« less

Advanced software development workstation project: Engineering scripting language. Graphical editor

NASA Technical Reports Server (NTRS)

1992-01-01

Software development is widely considered to be a bottleneck in the development of complex systems, both in terms of development and in terms of maintenance of deployed systems. Cost of software development and maintenance can also be very high. One approach to reducing costs and relieving this bottleneck is increasing the reuse of software designs and software components. A method for achieving such reuse is a software parts composition system. Such a system consists of a language for modeling software parts and their interfaces, a catalog of existing parts, an editor for combining parts, and a code generator that takes a specification and generates code for that application in the target language. The Advanced Software Development Workstation is intended to be an expert system shell designed to provide the capabilities of a software part composition system.

Developing sustainable software solutions for bioinformatics by the “ Butterfly” paradigm

PubMed Central

Ahmed, Zeeshan; Zeeshan, Saman; Dandekar, Thomas

2014-01-01

Software design and sustainable software engineering are essential for the long-term development of bioinformatics software. Typical challenges in an academic environment are short-term contracts, island solutions, pragmatic approaches and loose documentation. Upcoming new challenges are big data, complex data sets, software compatibility and rapid changes in data representation. Our approach to cope with these challenges consists of iterative intertwined cycles of development (“ Butterfly” paradigm) for key steps in scientific software engineering. User feedback is valued as well as software planning in a sustainable and interoperable way. Tool usage should be easy and intuitive. A middleware supports a user-friendly Graphical User Interface (GUI) as well as a database/tool development independently. We validated the approach of our own software development and compared the different design paradigms in various software solutions. PMID:25383181

Software engineering and Ada in design

NASA Technical Reports Server (NTRS)

Oneill, Don

1986-01-01

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

Simple solution to the medical instrumentation software problem

NASA Astrophysics Data System (ADS)

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.

Open Architecture Standard for NASA's Software-Defined Space Telecommunications Radio Systems

NASA Technical Reports Server (NTRS)

Reinhart, Richard C.; Johnson, Sandra K.; Kacpura, Thomas J.; Hall, Charles S.; Smith, Carl R.; Liebetreu, John

2008-01-01

NASA is developing an architecture standard for software-defined radios used in space- and ground-based platforms to enable commonality among radio developments to enhance capability and services while reducing mission and programmatic risk. Transceivers (or transponders) with functionality primarily defined in software (e.g., firmware) have the ability to change their functional behavior through software alone. This radio architecture standard offers value by employing common waveform software interfaces, method of instantiation, operation, and testing among different compliant hardware and software products. These common interfaces within the architecture abstract application software from the underlying hardware to enable technology insertion independently at either the software or hardware layer. This paper presents the initial Space Telecommunications Radio System (STRS) Architecture for NASA missions to provide the desired software abstraction and flexibility while minimizing the resources necessary to support the architecture.

Software assurance standard

NASA Technical Reports Server (NTRS)

1992-01-01

This standard specifies the software assurance program for the provider of software. It also delineates the assurance activities for the provider and the assurance data that are to be furnished by the provider to the acquirer. In any software development effort, the provider is the entity or individual that actually designs, develops, and implements the software product, while the acquirer is the entity or individual who specifies the requirements and accepts the resulting products. This standard specifies at a high level an overall software assurance program for software developed for and by NASA. Assurance includes the disciplines of quality assurance, quality engineering, verification and validation, nonconformance reporting and corrective action, safety assurance, and security assurance. The application of these disciplines during a software development life cycle is called software assurance. Subsequent lower-level standards will specify the specific processes within these disciplines.

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

PubMed Central

2012-01-01

Background 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. Results 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 Application version 1 was released for general use in November 2007. By May 2010, we had > 1200 registered users based in the UK, USA, Canada, South America, Europe, Africa, Middle East, SE Asia, Australia and New Zealand. Conclusions We found that an evolutionary software process was effective when we developed the BOADICEA Web Application. The key clinical software development issues identified during the BOADICEA Web Application project were: software reliability, Web security, clinical data protection and user feedback. PMID:22490389

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

PubMed

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 Application version 1 was released for general use in November 2007. By May 2010, we had > 1200 registered users based in the UK, USA, Canada, South America, Europe, Africa, Middle East, SE Asia, Australia and New Zealand. We found that an evolutionary software process was effective when we developed the BOADICEA Web Application. The key clinical software development issues identified during the BOADICEA Web Application project were: software reliability, Web security, clinical data protection and user feedback.

Telescience Resource Kit (TReK)

NASA Technical Reports Server (NTRS)

Lippincott, Jeff

2015-01-01

Telescience Resource Kit (TReK) is one of the Huntsville Operations Support Center (HOSC) remote operations solutions. It can be used to monitor and control International Space Station (ISS) payloads from anywhere in the world. It is comprised of a suite of software applications and libraries that provide generic data system capabilities and access to HOSC services. The TReK Software has been operational since 2000. A new cross-platform version of TReK is under development. The new software is being released in phases during the 2014-2016 timeframe. The TReK Release 3.x series of software is the original TReK software that has been operational since 2000. This software runs on Windows. It contains capabilities to support traditional telemetry and commanding using CCSDS (Consultative Committee for Space Data Systems) packets. The TReK Release 4.x series of software is the new cross platform software. It runs on Windows and Linux. The new TReK software will support communication using standard IP protocols and traditional telemetry and commanding. All the software listed above is compatible and can be installed and run together on Windows. The new TReK software contains a suite of software that can be used by payload developers on the ground and onboard (TReK Toolkit). TReK Toolkit is a suite of lightweight libraries and utility applications for use onboard and on the ground. TReK Desktop is the full suite of TReK software -most useful on the ground. When TReK Desktop is released, the TReK installation program will provide the option to choose just the TReK Toolkit portion of the software or the full TReK Desktop suite. The ISS program is providing the TReK Toolkit software as a generic flight software capability offered as a standard service to payloads. TReK Software Verification was conducted during the April/May 2015 timeframe. Payload teams using the TReK software onboard can reference the TReK software verification. TReK will be demonstrated on-orbit running on an ISS provided T61p laptop. Target Timeframe: September 2015 -2016. The on-orbit demonstration will collect benchmark metrics, and will be used in the future to provide live demonstrations during ISS Payload Conferences. Benchmark metrics and demonstrations will address the protocols described in SSP 52050-0047 Ku Forward section 3.3.7. (Associated term: CCSDS File Delivery Protocol (CFDP)).

48 CFR 227.7203-6 - Contract clauses.

Code of Federal Regulations, 2010 CFR

2010-10-01

... Software and Computer Software Documentation 227.7203-6 Contract clauses. (a)(1) Use the clause at 252.227-7014, Rights in Noncommercial Computer Software and Noncommercial Computer Software Documentation, in solicitations and contracts when the successful offeror(s) will be required to deliver computer software or...

48 CFR 227.7203-17 - Overseas contracts with foreign sources.

Code of Federal Regulations, 2013 CFR

2013-10-01

... COPYRIGHTS Rights in Computer Software and Computer Software Documentation 227.7203-17 Overseas contracts with foreign sources. (a) The clause at 252.227-7032, Rights in Technical Data and Computer Software... Noncommercial Computer Software and Noncommercial Computer Software Documentation, when the Government requires...

48 CFR 227.7203-17 - Overseas contracts with foreign sources.

Code of Federal Regulations, 2010 CFR

2010-10-01

... COPYRIGHTS Rights in Computer Software and Computer Software Documentation 227.7203-17 Overseas contracts with foreign sources. (a) The clause at 252.227-7032, Rights in Technical Data and Computer Software... Noncommercial Computer Software and Noncommercial Computer Software Documentation, when the Government requires...

48 CFR 227.7203-6 - Contract clauses.

Code of Federal Regulations, 2012 CFR

2012-10-01

... Software and Computer Software Documentation 227.7203-6 Contract clauses. (a)(1) Use the clause at 252.227-7014, Rights in Noncommercial Computer Software and Noncommercial Computer Software Documentation, in solicitations and contracts when the successful offeror(s) will be required to deliver computer software or...

48 CFR 227.7203-17 - Overseas contracts with foreign sources.

Code of Federal Regulations, 2014 CFR

2014-10-01

... COPYRIGHTS Rights in Computer Software and Computer Software Documentation 227.7203-17 Overseas contracts with foreign sources. (a) The clause at 252.227-7032, Rights in Technical Data and Computer Software... Noncommercial Computer Software and Noncommercial Computer Software Documentation, when the Government requires...

48 CFR 227.7203-6 - Contract clauses.

Code of Federal Regulations, 2014 CFR

2014-10-01

... Software and Computer Software Documentation 227.7203-6 Contract clauses. (a)(1) Use the clause at 252.227-7014, Rights in Noncommercial Computer Software and Noncommercial Computer Software Documentation, in solicitations and contracts when the successful offeror(s) will be required to deliver computer software or...

48 CFR 227.7203-6 - Contract clauses.

Code of Federal Regulations, 2011 CFR

2011-10-01

... Software and Computer Software Documentation 227.7203-6 Contract clauses. (a)(1) Use the clause at 252.227-7014, Rights in Noncommercial Computer Software and Noncommercial Computer Software Documentation, in solicitations and contracts when the successful offeror(s) will be required to deliver computer software or...

48 CFR 227.7203-17 - Overseas contracts with foreign sources.

Code of Federal Regulations, 2011 CFR

2011-10-01

... COPYRIGHTS Rights in Computer Software and Computer Software Documentation 227.7203-17 Overseas contracts with foreign sources. (a) The clause at 252.227-7032, Rights in Technical Data and Computer Software... Noncommercial Computer Software and Noncommercial Computer Software Documentation, when the Government requires...

48 CFR 227.7203-17 - Overseas contracts with foreign sources.

Code of Federal Regulations, 2012 CFR

2012-10-01

... COPYRIGHTS Rights in Computer Software and Computer Software Documentation 227.7203-17 Overseas contracts with foreign sources. (a) The clause at 252.227-7032, Rights in Technical Data and Computer Software... Noncommercial Computer Software and Noncommercial Computer Software Documentation, when the Government requires...

48 CFR 227.7203-6 - Contract clauses.

Code of Federal Regulations, 2013 CFR

2013-10-01

... Software and Computer Software Documentation 227.7203-6 Contract clauses. (a)(1) Use the clause at 252.227-7014, Rights in Noncommercial Computer Software and Noncommercial Computer Software Documentation, in solicitations and contracts when the successful offeror(s) will be required to deliver computer software or...

Software security checklist for the software life cycle

NASA Technical Reports Server (NTRS)

Gilliam, D. P.; Wolfe, T. L.; Sherif, J. S.

2002-01-01

A formal approach to security in the software life cycle is essential to protect corporate resources. However, little thought has been given to this aspect of software development. Due to its criticality, security should be integrated as a formal approach in the software life cycle.

NASA's Software Safety Standard

NASA Technical Reports Server (NTRS)

Ramsay, Christopher M.

2005-01-01

NASA (National Aeronautics and Space Administration) 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 (manned or unmanned) launched that did not have a computer on board that provided vital command and control services. Despite this growing dependence on software control and monitoring, there has been no consistent application of software safety practices and methodology to NASA's projects with safety critical software. Led by the NASA Headquarters Office of Safety and Mission Assurance, the NASA Software Safety Standard (STD-18l9.13B) has recently undergone a significant update in an attempt to provide that consistency. This paper will discuss the key features of the new NASA Software Safety Standard. It will start with a brief history of the use and development of software in safety critical applications at NASA. It will then give a brief overview of the NASA Software Working Group and the approach it took to revise the software engineering process across the Agency.

Software Safety Risk in Legacy Safety-Critical Computer Systems

NASA Technical Reports Server (NTRS)

Hill, Janice; Baggs, Rhoda

2007-01-01

Safety-critical computer systems must be engineered to meet system and software safety requirements. For legacy safety-critical computer systems, software safety requirements may not have been formally specified during development. When process-oriented software safety requirements are levied on a legacy system after the fact, where software development artifacts don't exist or are incomplete, the question becomes 'how can this be done?' The risks associated with only meeting certain software safety requirements in a legacy safety-critical computer system must be addressed should such systems be selected as candidates for reuse. This paper proposes a method for ascertaining formally, a software safety risk assessment, that provides measurements for software safety for legacy systems which may or may not have a suite of software engineering documentation that is now normally required. It relies upon the NASA Software Safety Standard, risk assessment methods based upon the Taxonomy-Based Questionnaire, and the application of reverse engineering CASE tools to produce original design documents for legacy systems.

A study of software standards used in the avionics industry

NASA Technical Reports Server (NTRS)

Hayhurst, Kelly J.

1994-01-01

Within the past decade, software has become an increasingly common element in computing systems. In particular, the role of software used in the aerospace industry, especially in life- or safety-critical applications, is rapidly expanding. This intensifies the need to use effective techniques for achieving and verifying the reliability of avionics software. Although certain software development processes and techniques are mandated by government regulating agencies, no one methodology has been shown to consistently produce reliable software. The knowledge base for designing reliable software simply has not reached the maturity of its hardware counterpart. In an effort to increase our understanding of software, the Langley Research Center conducted a series of experiments over 15 years with the goal of understanding why and how software fails. As part of this program, the effectiveness of current industry standards for the development of avionics is being investigated. This study involves the generation of a controlled environment to conduct scientific experiments on software processes.

OAST Space Theme Workshop. Volume 3: Working group summary. 4: Software (E-4). A. Summary. B. Technology needs (form 1). C. Priority assessment (form 2)

NASA Technical Reports Server (NTRS)

1976-01-01

Only a few efforts are currently underway to develop an adequate technology base for the various themes. Particular attention must be given to software commonality and evolutionary capability, to increased system integrity and autonomy; and to improved communications among the program users, the program developers, and the programs themselves. There is a need for quantum improvement in software development methods and increasing the awareness of software by all concerned. Major thrusts identified include: (1) data and systems management; (2) software technology for autonomous systems; (3) technology and methods for improving the software development process; (4) advances related to systems of software elements including their architecture, their attributes as systems, and their interfaces with users and other systems; and (5) applications of software including both the basic algorithms used in a number of applications and the software specific to a particular theme or discipline area. The impact of each theme on software is assessed.

Modeling SMAP Spacecraft Attitude Control Estimation Error Using Signal Generation Model

NASA Technical Reports Server (NTRS)

Rizvi, Farheen

2016-01-01

Two ground simulation software are used to model the SMAP spacecraft dynamics. The CAST software uses a higher fidelity model than the ADAMS software. The ADAMS software models the spacecraft plant, controller and actuator models, and assumes a perfect sensor and estimator model. In this simulation study, the spacecraft dynamics results from the ADAMS software are used as CAST software is unavailable. The main source of spacecraft dynamics error in the higher fidelity CAST software is due to the estimation error. A signal generation model is developed to capture the effect of this estimation error in the overall spacecraft dynamics. Then, this signal generation model is included in the ADAMS software spacecraft dynamics estimate such that the results are similar to CAST. This signal generation model has similar characteristics mean, variance and power spectral density as the true CAST estimation error. In this way, ADAMS software can still be used while capturing the higher fidelity spacecraft dynamics modeling from CAST software.

NASA's Software Safety Standard

NASA Technical Reports Server (NTRS)

Ramsay, Christopher M.

2007-01-01

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

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

NASA Technical Reports Server (NTRS)

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

1992-01-01

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

Empirical studies of software design: Implications for SSEs

NASA Technical Reports Server (NTRS)

Krasner, Herb

1988-01-01

Implications for Software Engineering Environments (SEEs) are presented in viewgraph format for characteristics of projects studied; significant problems and crucial problem areas in software design for large systems; layered behavioral model of software processes; implications of field study results; software project as an ecological system; results of the LIFT study; information model of design exploration; software design strategies; results of the team design study; and a list of publications.

Formal Validation of Aerospace Software

NASA Astrophysics Data System (ADS)

Lesens, David; Moy, Yannick; Kanig, Johannes

2013-08-01

Any single error in critical software can have catastrophic consequences. Even though failures are usually not advertised, some software bugs have become famous, such as the error in the MIM-104 Patriot. For space systems, experience shows that software errors are a serious concern: more than half of all satellite failures from 2000 to 2003 involved software. To address this concern, this paper addresses the use of formal verification of software developed in Ada.

Cost Estimation of Software Development and the Implications for the Program Manager

DTIC Science & Technology

1992-06-01

Software Lifecycle Model (SLIM), the Jensen System-4 model, the Software Productivity, Quality, and Reliability Estimator ( SPQR \\20), the Constructive...function models in current use are the Software Productivity, Quality, and Reliability Estimator ( SPQR /20) and the Software Architecture Sizing and...Estimator ( SPQR /20) was developed by T. Capers Jones of Software Productivity Research, Inc., in 1985. The model is intended to estimate the outcome

Software Library: A Reusable Software Issue.

DTIC Science & Technology

1984-06-01

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

Self-assembling software generator

DOEpatents

Bouchard, Ann M [Albuquerque, NM; Osbourn, Gordon C [Albuquerque, NM

2011-11-25

A technique to generate an executable task includes inspecting a task specification data structure to determine what software entities are to be generated to create the executable task, inspecting the task specification data structure to determine how the software entities will be linked after generating the software entities, inspecting the task specification data structure to determine logic to be executed by the software entities, and generating the software entities to create the executable task.

Software Assurance: Five Essential Considerations for Acquisition Officials

DTIC Science & Technology

2007-05-01

May 2007 www.stsc.hill.af.mil 17 2 • address security concerns in the software development life cycle ( SDLC )? • Are there formal software quality...What threat modeling process, if any, is used when designing the software ? What analysis, design, and construction tools are used by your software design...the-shelf (COTS), government off-the-shelf (GOTS), open- source, embedded, and legacy software . Attackers exploit unintentional vulnerabil- ities or

Factors That Affect Software Testability

NASA Technical Reports Server (NTRS)

Voas, Jeffrey M.

1991-01-01

Software faults that infrequently affect software's output are dangerous. When a software fault causes frequent software failures, testing is likely to reveal the fault before the software is releases; when the fault remains undetected during testing, it can cause disaster after the software is installed. A technique for predicting whether a particular piece of software is likely to reveal faults within itself during testing is found in [Voas91b]. A piece of software that is likely to reveal faults within itself during testing is said to have high testability. A piece of software that is not likely to reveal faults within itself during testing is said to have low testability. It is preferable to design software with higher testabilities from the outset, i.e., create software with as high of a degree of testability as possible to avoid the problems of having undetected faults that are associated with low testability. Information loss is a phenomenon that occurs during program execution that increases the likelihood that a fault will remain undetected. In this paper, I identify two brad classes of information loss, define them, and suggest ways of predicting the potential for information loss to occur. We do this in order to decrease the likelihood that faults will remain undetected during testing.

Survey of Verification and Validation Techniques for Small Satellite Software Development

NASA Technical Reports Server (NTRS)

Jacklin, Stephen A.

2015-01-01

The purpose of this paper is to provide an overview of the current trends and practices in small-satellite software verification and validation. This document is not intended to promote a specific software assurance method. Rather, it seeks to present an unbiased survey of software assurance methods used to verify and validate small satellite software and to make mention of the benefits and value of each approach. These methods include simulation and testing, verification and validation with model-based design, formal methods, and fault-tolerant software design with run-time monitoring. Although the literature reveals that simulation and testing has by far the longest legacy, model-based design methods are proving to be useful for software verification and validation. Some work in formal methods, though not widely used for any satellites, may offer new ways to improve small satellite software verification and validation. These methods need to be further advanced to deal with the state explosion problem and to make them more usable by small-satellite software engineers to be regularly applied to software verification. Last, it is explained how run-time monitoring, combined with fault-tolerant software design methods, provides an important means to detect and correct software errors that escape the verification process or those errors that are produced after launch through the effects of ionizing radiation.

Distributed and Collaborative Software Analysis

NASA Astrophysics Data System (ADS)

Ghezzi, Giacomo; Gall, Harald C.

Throughout the years software engineers have come up with a myriad of specialized tools and techniques that focus on a certain type of software analysissoftware analysis such as source code analysis, co-change analysis or bug prediction. However, easy and straight forward synergies between these analyses and tools rarely exist because of their stand-alone nature, their platform dependence, their different input and output formats and the variety of data to analyze. As a consequence, distributed and collaborative software analysiscollaborative software analysis scenarios and in particular interoperability are severely limited. We describe a distributed and collaborative software analysis platform that allows for a seamless interoperability of software analysis tools across platform, geographical and organizational boundaries. We realize software analysis tools as services that can be accessed and composed over the Internet. These distributed analysis services shall be widely accessible in our incrementally augmented Software Analysis Broker software analysis broker where organizations and tool providers can register and share their tools. To allow (semi-) automatic use and composition of these tools, they are classified and mapped into a software analysis taxonomy and adhere to specific meta-models and ontologiesontologies for their category of analysis.

Guidance and Control Software Project Data - Volume 3: Verification Documents

NASA Technical Reports Server (NTRS)

Hayhurst, Kelly J. (Editor)

2008-01-01

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

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

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

Salomons, G; Kelly, D

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

Software Development as Music Education Research

ERIC Educational Resources Information Center

Brown, Andrew R.

2007-01-01

This paper discusses how software development can be used as a method for music education research. It explains how software development can externalize ideas, stimulate action and reflection, and provide evidence to support the educative value of new software-based experiences. Parallels between the interactive software development process and…

Software Trends and Trendsetters: How They're Shaping an Industry.

ERIC Educational Resources Information Center

McGinty, Tony; And Others

1987-01-01

Discusses trends in educational software and the effects of new developments on publishers and on the computer industry. Marketing prospects for software are examined, and recent advances are highlighted, including integrated learning systems, skill-based software, software tied to textbooks, networking, and freeware. (LRW)

Requirements Engineering in Building Climate Science Software

ERIC Educational Resources Information Center

Batcheller, Archer L.

2011-01-01

Software has an important role in supporting scientific work. This dissertation studies teams that build scientific software, focusing on the way that they determine what the software should do. These requirements engineering processes are investigated through three case studies of climate science software projects. The Earth System Modeling…

75 FR 10439 - Cognitive Radio Technologies and Software Defined Radios

Federal Register 2010, 2011, 2012, 2013, 2014

2010-03-08

... Technologies and Software Defined Radios AGENCY: Federal Communications Commission. ACTION: Final rule. SUMMARY... concerning the use of open source software to implement security features in software defined radios (SDRs... ongoing technical developments in cognitive and software defined radio (SDR) technologies. 2. On April 20...

Sobrevivendo a un tsunami: lecciones de Chile, Hawai y Japon

USGS Publications Warehouse

Compilado por Atwater, Brian F.; Cisternas V., Marco; Bourgeois, Joanne; Dudley, Walter C.; Hendley, James W.; Stauffer, Peter H.

1999-01-01

Este folleto contiene historias veridicas que ilustran como sobrevivir, y como no sobrevivir, a un tsunami. Esta publicacion esta dirigida a las personas que viven, trabajan o, simplemente, se divierten a lo largo de las costas que pueden ser afectadas por un tsunami. Tales costas rodean la mayor parte del Oceano Pacifico pero tambien incluyen algunas areas costeras de los Oceanos Atlantico e Indico. Aunque mucha gente llama a los tsunamis 'olas de marea', estos no estan relacionados a las mareas, sino son una serie de olas, o 'tren de olas', generalmente causadas por cambios en el nivel del fondo marino durante los terremotos. Los tsunamis tambien pueden ser generados por la erupcion de volcanes costeros, islas volconicas, deslizamientos submarinos e impactos de grandes meteoritos en el mar. Como sucedio en Sumatra en el 2004, los tsunamis pueden alcanzar alturas de 15 metros, no tan solo en la costa sino tambien kilometros tierra adentro. Los relatos presentados en este folleto fueron seleccionados de entrevistas realizadas a personas que sobrevivieron al tsunami del Oceano Pacifico de 1960. Muchas de estas personas, incluyendo a la enfermera de la foto, se enfrento a las olas generadas a poca distancia, en la costa chilena. En cambio, otros debieron hacer frente al tsunami muchas horas despues, en Hawai y Japon. La mayoria de las entrevistas fueron realizadas a fines de los anos ochenta y en los noventa. Las historias ofrecen una mezcla de lecciones de supervivencia a un tsunami. En algunos casos se presentan las acciones que confiablemente salvaron vidas: poner atencion a los avisos de la naturaleza, abandonar los bienes, dirigirse rapidamente a un sector alto y permanecer alli hasta que el tsunami realmente haya terminado. Otras historias describen como se encontro refugio al subir a construcciones y arboles o flotar sobre desechos, tacticas que tuvieron diferentes resultados y que pueden ser recomendadas solo como actos desesperados de personas atrapadas en sectores bajos.

Astronomia Motivadora no Ensino Fundamental

NASA Astrophysics Data System (ADS)

Melo, J.; Voelzke, M. R.

2008-09-01

O objetivo principal deste trabalho é procurar desenvolver o interesse dos alunos pelas ciências através da Astronomia. Uma pesquisa com perguntas sobre Astronomia foi realizada junto a 161 alunos do Ensino Fundamental, com o intuito de descobrir conhecimentos prévios dos alunos sobre o assunto. Constatou-se, por exemplo, que 29,3% da 6ª série responderam corretamente o que é eclipse, 30,0% da 8ª série acertaram o que a Astronomia estuda, enquanto 42,3% dos alunos da 5ª série souberam definir o Sol. Pretende-se ampliar as turmas participantes e trabalhar, principalmente de forma prática com: dimensões e escalas no Sistema Solar, construção de luneta, questões como dia e noite, estações do ano e eclipses. Busca-se abordar, também, outros conteúdos de Física tais como a óptica na construção da luneta, e a mecânica no trabalho com escalas e medidas, e ao utilizar uma luminária para representar o Sol na questão do eclipse, e de outras disciplinas como a Matemática na transformação de unidades, regras de três; Artes na modelagem ou desenho dos planetas; a própria História com relação à busca pela origem do universo, e a Informática que possibilita a busca mais rápida por informações, além de permitir simulações e visualizações de imagens importantes. Acredita-se que a Astronomia é importante no processo ensino aprendizagem, pois permite a discussão de temas curiosos como, por exemplo, a origem do universo, viagens espaciais a existência ou não de vida em outros planetas, além de temas atuais como as novas tecnologias.

A Legal Guide for the Software Developer.

ERIC Educational Resources Information Center

Minnesota Small Business Assistance Office, St. Paul.

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

Students' Different Understandings of Class Diagrams

ERIC Educational Resources Information Center

Boustedt, Jonas

2012-01-01

The software industry needs well-trained software designers and one important aspect of software design is the ability to model software designs visually and understand what visual models represent. However, previous research indicates that software design is a difficult task to many students. This article reports empirical findings from a…

Proceedings of the Eighth Annual Software Engineering Workshop

NASA Technical Reports Server (NTRS)

1983-01-01

The four major topics of discussion included: the NASA Software Engineering Laboratory, software testing, human factors in software engineering and software quality assessment. As in the past years, there were 12 position papers presented (3 for each topic) followed by questions and very heavy participation by the general audience.

Software Piracy, Ethics, and the Academician.

ERIC Educational Resources Information Center

Bassler, Richard A.

The numerous software programs available for easy, low-cost copying raise ethical questions. The problem can be examined from the viewpoints of software users, teachers, authors, vendors, and distributors. Software users might hesitate to purchase or use software which prevents the making of back-up copies for program protection. Teachers in…

Software engineering as an engineering discipline

NASA Technical Reports Server (NTRS)

Gibbs, Norman

1988-01-01

The goals of the Software Engineering Institute's Education Program are as follows: to increase the number of highly qualified software engineers--new software engineers and existing practitioners; and to be the leading center of expertise for software engineering education and training. A discussion of these goals is presented in vugraph form.

Agile Software Development

ERIC Educational Resources Information Center

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…

Center for Adaptive Optics | Software

Science.gov Websites

Center for Adaptive Optics A University of California Science and Technology Center home Adaptive Optics Software The Center for Adaptive Optics acts as a clearing house for distributing Software to Institutes it gives specialists in Adaptive Optics a place to distribute their software. All software is

Commercial Literacy Software.

ERIC Educational Resources Information Center

Balajthy, Ernest

1997-01-01

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

21 CFR 801.50 - Labeling requirements for stand-alone software.

Code of Federal Regulations, 2014 CFR

2014-04-01

... 21 Food and Drugs 8 2014-04-01 2014-04-01 false Labeling requirements for stand-alone software....50 Labeling requirements for stand-alone software. (a) Stand-alone software that is not distributed... in packaged form, stand-alone software regulated as a medical device must provide its unique device...

48 CFR 227.7203-13 - Government right to review, verify, challenge and validate asserted restrictions.

Code of Federal Regulations, 2013 CFR

2013-10-01

... REQUIREMENTS PATENTS, DATA, AND COPYRIGHTS Rights in Computer Software and Computer Software Documentation 227..., reproduce, release, or disclose computer software or computer software documentation do not, by themselves, determine the extent of the Government's rights in such software or documentation. The Government may...

22 CFR 121.8 - End-items, components, accessories, attachments, parts, firmware, software, and systems.

Code of Federal Regulations, 2014 CFR

2014-04-01

..., parts, firmware, software, and systems. 121.8 Section 121.8 Foreign Relations DEPARTMENT OF STATE...-items, components, accessories, attachments, parts, firmware, software, and systems. (a) An end-item is.... Firmware includes but is not limited to circuits into which software has been programmed. (f) Software...

48 CFR 227.7203-13 - Government right to review, verify, challenge and validate asserted restrictions.

Code of Federal Regulations, 2011 CFR

2011-10-01

... REQUIREMENTS PATENTS, DATA, AND COPYRIGHTS Rights in Computer Software and Computer Software Documentation 227..., reproduce, release, or disclose computer software or computer software documentation do not, by themselves, determine the extent of the Government's rights in such software or documentation. The Government may...

22 CFR 121.8 - End-items, components, accessories, attachments, parts, firmware, software and systems.

Code of Federal Regulations, 2012 CFR

2012-04-01

..., parts, firmware, software and systems. 121.8 Section 121.8 Foreign Relations DEPARTMENT OF STATE...-items, components, accessories, attachments, parts, firmware, software and systems. (a) An end-item is.... Firmware includes but is not limited to circuits into which software has been programmed. (f) Software...

22 CFR 121.8 - End-items, components, accessories, attachments, parts, firmware, software and systems.

Code of Federal Regulations, 2013 CFR

2013-04-01

..., parts, firmware, software and systems. 121.8 Section 121.8 Foreign Relations DEPARTMENT OF STATE...-items, components, accessories, attachments, parts, firmware, software and systems. (a) An end-item is.... Firmware includes but is not limited to circuits into which software has been programmed. (f) Software...

48 CFR 227.7203-13 - Government right to review, verify, challenge and validate asserted restrictions.

Code of Federal Regulations, 2014 CFR

2014-10-01

... REQUIREMENTS PATENTS, DATA, AND COPYRIGHTS Rights in Computer Software and Computer Software Documentation 227..., reproduce, release, or disclose computer software or computer software documentation do not, by themselves, determine the extent of the Government's rights in such software or documentation. The Government may...

48 CFR 227.7203-13 - Government right to review, verify, challenge and validate asserted restrictions.

Code of Federal Regulations, 2012 CFR

2012-10-01

... REQUIREMENTS PATENTS, DATA, AND COPYRIGHTS Rights in Computer Software and Computer Software Documentation 227..., reproduce, release, or disclose computer software or computer software documentation do not, by themselves, determine the extent of the Government's rights in such software or documentation. The Government may...

22 CFR 121.8 - End-items, components, accessories, attachments, parts, firmware, software and systems.

Code of Federal Regulations, 2010 CFR

2010-04-01

..., parts, firmware, software and systems. 121.8 Section 121.8 Foreign Relations DEPARTMENT OF STATE...-items, components, accessories, attachments, parts, firmware, software and systems. (a) An end-item is.... Firmware includes but is not limited to circuits into which software has been programmed. (f) Software...

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

Federal Register 2010, 2011, 2012, 2013, 2014

2013-08-02

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

48 CFR 227.7203-13 - Government right to review, verify, challenge and validate asserted restrictions.

Code of Federal Regulations, 2010 CFR

2010-10-01

... REQUIREMENTS PATENTS, DATA, AND COPYRIGHTS Rights in Computer Software and Computer Software Documentation 227..., reproduce, release, or disclose computer software or computer software documentation do not, by themselves, determine the extent of the Government's rights in such software or documentation. The Government may...

22 CFR 121.8 - End-items, components, accessories, attachments, parts, firmware, software and systems.

Code of Federal Regulations, 2011 CFR

2011-04-01

..., parts, firmware, software and systems. 121.8 Section 121.8 Foreign Relations DEPARTMENT OF STATE...-items, components, accessories, attachments, parts, firmware, software and systems. (a) An end-item is.... Firmware includes but is not limited to circuits into which software has been programmed. (f) Software...

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

NASA Technical Reports Server (NTRS)

1983-01-01

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

The Emergence of Open-Source Software in China

ERIC Educational Resources Information Center

Pan, Guohua; Bonk, Curtis J.

2007-01-01

The open-source software movement is gaining increasing momentum in China. Of the limited numbers of open-source software in China, "Red Flag Linux" stands out most strikingly, commanding 30 percent share of Chinese software market. Unlike the spontaneity of open-source movement in North America, open-source software development in…

15 CFR 30.37 - Miscellaneous exemptions.

Code of Federal Regulations, 2010 CFR

2010-01-01

... requirements of the licensing Federal agency. (f) Exports of technology and software as defined in 15 CFR 772... required for mass-market software. For purposes of this part, mass-market software is defined as software... of commodities and software intended for use by individual USPPIs or by employees or representatives...

15 CFR 30.37 - Miscellaneous exemptions.

Code of Federal Regulations, 2011 CFR

2011-01-01

... requirements of the licensing Federal agency. (f) Exports of technology and software as defined in 15 CFR 772... required for mass-market software. For purposes of this part, mass-market software is defined as software... of commodities and software intended for use by individual USPPIs or by employees or representatives...

15 CFR 30.37 - Miscellaneous exemptions.

Code of Federal Regulations, 2013 CFR

2013-01-01

... requirements of the licensing Federal agency. (f) Exports of technology and software as defined in 15 CFR 772... required for mass-market software. For purposes of this part, mass-market software is defined as software... of commodities and software intended for use by individual USPPIs or by employees or representatives...

15 CFR 30.37 - Miscellaneous exemptions.

Code of Federal Regulations, 2012 CFR

2012-01-01

... requirements of the licensing Federal agency. (f) Exports of technology and software as defined in 15 CFR 772... required for mass-market software. For purposes of this part, mass-market software is defined as software... of commodities and software intended for use by individual USPPIs or by employees or representatives...

Toward Baseline Software Anomalies in NASA Missions

NASA Technical Reports Server (NTRS)

Layman, Lucas; Zelkowitz, Marvin; Basili, Victor; Nikora, Allen P.

2012-01-01

In this fast abstract, we provide preliminary findings an analysis of 14,500 spacecraft anomalies from unmanned NASA missions. We provide some baselines for the distributions of software vs. non-software anomalies in spaceflight systems, the risk ratings of software anomalies, and the corrective actions associated with software anomalies.

Understanding Acceptance of Software Metrics--A Developer Perspective

ERIC Educational Resources Information Center

Umarji, Medha

2009-01-01

Software metrics are measures of software products and processes. Metrics are widely used by software organizations to help manage projects, improve product quality and increase efficiency of the software development process. However, metrics programs tend to have a high failure rate in organizations, and developer pushback is one of the sources…

Considerations for the Evaluation of Software.

ERIC Educational Resources Information Center

Fields, Thomas A.

1984-01-01

The paper describes the decision process in the determination of software purchase for the professional's use of the microcomputer. Consideration to ensure that the software purchased will be a success, which software will be needed, and options that will facilitate the location and evaluation of software are discussed. (Author/CL)

Evaluation and selection of security products for authentication of computer software

NASA Astrophysics Data System (ADS)

Roenigk, Mark W.

2000-04-01

Software Piracy is estimated to cost software companies over eleven billion dollars per year in lost revenue worldwide. Over fifty three percent of all intellectual property in the form of software is pirated on a global basis. Software piracy has a dramatic effect on the employment figures for the information industry as well. In the US alone, over 130,000 jobs are lost annually as a result of software piracy.

Modernizing Systems and Software: How Evolving Trends in Future Trends in Systems and Software Technology Bode Well for Advancing the Precision of Technology

DTIC Science & Technology

2009-04-23

of Code Need for increased functionality will be a forcing function to bring the fields of software and systems engineering... of Software-Intensive Systems is Increasing 3 How Evolving Trends in Systems and Software Technologies Bode Well for Advancing the Precision of ...Engineering in Continued Partnership 4 How Evolving Trends in Systems and Software Technologies Bode Well for Advancing the

Generic domain models in software engineering

NASA Technical Reports Server (NTRS)

Maiden, Neil

1992-01-01

This paper outlines three research directions related to domain-specific software development: (1) reuse of generic models for domain-specific software development; (2) empirical evidence to determine these generic models, namely elicitation of mental knowledge schema possessed by expert software developers; and (3) exploitation of generic domain models to assist modelling of specific applications. It focuses on knowledge acquisition for domain-specific software development, with emphasis on tool support for the most important phases of software development.

Data systems and computer science: Software Engineering Program

NASA Technical Reports Server (NTRS)

Zygielbaum, Arthur I.

1991-01-01

An external review of the Integrated Technology Plan for the Civil Space Program is presented. This review is specifically concerned with the Software Engineering Program. The goals of the Software Engineering Program are as follows: (1) improve NASA's ability to manage development, operation, and maintenance of complex software systems; (2) decrease NASA's cost and risk in engineering complex software systems; and (3) provide technology to assure safety and reliability of software in mission critical applications.

Software component quality evaluation

NASA Technical Reports Server (NTRS)

Clough, A. J.

1991-01-01

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

The Consumer Juggernaut: Web-Based and Mobile Applications as Innovation Pioneer

NASA Astrophysics Data System (ADS)

Messerschmitt, David G.

As happened previously in electronics, software targeted at consumers is increasingly the focus of investment and innovation. Some of the areas where it is leading is animated interfaces, treating users as a community, audio and video information, software as a service, agile software development, and the integration of business models with software design. As a risk-taking and experimental market, and as a source of ideas, consumer software can benefit other areas of applications software. The influence of consumer software can be magnified by research into the internal organizations and processes of the innovative firms at its foundation.

Executable assertions and flight software

NASA Technical Reports Server (NTRS)

Mahmood, A.; Andrews, D. M.; Mccluskey, E. J.

1984-01-01

Executable assertions are used to test flight control software. The techniques used for testing flight software; however, are different from the techniques used to test other kinds of software. This is because of the redundant nature of flight software. An experimental setup for testing flight software using executable assertions is described. Techniques for writing and using executable assertions to test flight software are presented. The error detection capability of assertions is studied and many examples of assertions are given. The issues of placement and complexity of assertions and the language features to support efficient use of assertions are discussed.

SWiFT Software Quality Assurance Plan.

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

Berg, Jonathan Charles

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

Software Safety Progress in NASA

NASA Technical Reports Server (NTRS)

Radley, Charles F.

1995-01-01

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

Healthcare software assurance.

PubMed

Cooper, Jason G; Pauley, Keith A

2006-01-01

Software assurance is a rigorous, lifecycle phase-independent set of activities which ensure completeness, safety, and reliability of software processes and products. This is accomplished by guaranteeing conformance to all requirements, standards, procedures, and regulations. These assurance processes are even more important when coupled with healthcare software systems, embedded software in medical instrumentation, and other healthcare-oriented life-critical systems. The current Food and Drug Administration (FDA) regulatory requirements and guidance documentation do not address certain aspects of complete software assurance activities. In addition, the FDA's software oversight processes require enhancement to include increasingly complex healthcare systems such as Hospital Information Systems (HIS). The importance of complete software assurance is introduced, current regulatory requirements and guidance discussed, and the necessity for enhancements to the current processes shall be highlighted.

Healthcare Software Assurance

PubMed Central

Cooper, Jason G.; Pauley, Keith A.

2006-01-01

Software assurance is a rigorous, lifecycle phase-independent set of activities which ensure completeness, safety, and reliability of software processes and products. This is accomplished by guaranteeing conformance to all requirements, standards, procedures, and regulations. These assurance processes are even more important when coupled with healthcare software systems, embedded software in medical instrumentation, and other healthcare-oriented life-critical systems. The current Food and Drug Administration (FDA) regulatory requirements and guidance documentation do not address certain aspects of complete software assurance activities. In addition, the FDA’s software oversight processes require enhancement to include increasingly complex healthcare systems such as Hospital Information Systems (HIS). The importance of complete software assurance is introduced, current regulatory requirements and guidance discussed, and the necessity for enhancements to the current processes shall be highlighted. PMID:17238324

Development of a comprehensive software engineering environment

NASA Technical Reports Server (NTRS)

Hartrum, Thomas C.; Lamont, Gary B.

1987-01-01

The generation of a set of tools for software lifecycle is a recurring theme in the software engineering literature. The development of such tools and their integration into a software development environment is a difficult task because of the magnitude (number of variables) and the complexity (combinatorics) of the software lifecycle process. An initial development of a global approach was initiated in 1982 as the Software Development Workbench (SDW). Continuing efforts focus on tool development, tool integration, human interfacing, data dictionaries, and testing algorithms. Current efforts are emphasizing natural language interfaces, expert system software development associates and distributed environments with Ada as the target language. The current implementation of the SDW is on a VAX-11/780. Other software development tools are being networked through engineering workstations.

Compiling software for a hierarchical distributed processing system

DOEpatents

Archer, Charles J; Blocksome, Michael A; Ratterman, Joseph D; Smith, Brian E

2013-12-31

Compiling software for a hierarchical distributed processing system including providing to one or more compiling nodes software to be compiled, wherein at least a portion of the software to be compiled is to be executed by one or more nodes; compiling, by the compiling node, the software; maintaining, by the compiling node, any compiled software to be executed on the compiling node; selecting, by the compiling node, one or more nodes in a next tier of the hierarchy of the distributed processing system in dependence upon whether any compiled software is for the selected node or the selected node's descendents; sending to the selected node only the compiled software to be executed by the selected node or selected node's descendent.

RT-Syn: A real-time software system generator

NASA Technical Reports Server (NTRS)

Setliff, Dorothy E.

1992-01-01

This paper presents research into providing highly reusable and maintainable components by using automatic software synthesis techniques. This proposal uses domain knowledge combined with automatic software synthesis techniques to engineer large-scale mission-critical real-time software. The hypothesis centers on a software synthesis architecture that specifically incorporates application-specific (in this case real-time) knowledge. This architecture synthesizes complex system software to meet a behavioral specification and external interaction design constraints. Some examples of these external constraints are communication protocols, precisions, timing, and space limitations. The incorporation of application-specific knowledge facilitates the generation of mathematical software metrics which are used to narrow the design space, thereby making software synthesis tractable. Success has the potential to dramatically reduce mission-critical system life-cycle costs not only by reducing development time, but more importantly facilitating maintenance, modifications, and extensions of complex mission-critical software systems, which are currently dominating life cycle costs.

Quality measures and assurance for AI (Artificial Intelligence) software

NASA Technical Reports Server (NTRS)

Rushby, John

1988-01-01

This report is concerned with the application of software quality and evaluation measures to AI software and, more broadly, with the question of quality assurance for AI software. Considered are not only the metrics that attempt to measure some aspect of software quality, but also the methodologies and techniques (such as systematic testing) that attempt to improve some dimension of quality, without necessarily quantifying the extent of the improvement. The report is divided into three parts Part 1 reviews existing software quality measures, i.e., those that have been developed for, and applied to, conventional software. Part 2 considers the characteristics of AI software, the applicability and potential utility of measures and techniques identified in the first part, and reviews those few methods developed specifically for AI software. Part 3 presents an assessment and recommendations for the further exploration of this important area.

Data-Driven Software Framework for Web-Based ISS Telescience

NASA Technical Reports Server (NTRS)

Tso, Kam S.

2005-01-01

Software that enables authorized users to monitor and control scientific payloads aboard the International Space Station (ISS) from diverse terrestrial locations equipped with Internet connections is undergoing development. This software reflects a data-driven approach to distributed operations. A Web-based software framework leverages prior developments in Java and Extensible Markup Language (XML) to create portable code and portable data, to which one can gain access via Web-browser software on almost any common computer. Open-source software is used extensively to minimize cost; the framework also accommodates enterprise-class server software to satisfy needs for high performance and security. To accommodate the diversity of ISS experiments and users, the framework emphasizes openness and extensibility. Users can take advantage of available viewer software to create their own client programs according to their particular preferences, and can upload these programs for custom processing of data, generation of views, and planning of experiments. The same software system, possibly augmented with a subset of data and additional software tools, could be used for public outreach by enabling public users to replay telescience experiments, conduct their experiments with simulated payloads, and create their own client programs and other custom software.

Software IV and V Research Priorities and Applied Program Accomplishments Within NASA

NASA Technical Reports Server (NTRS)

Blazy, Louis J.

2000-01-01

The mission of this research is to be world-class creators and facilitators of innovative, intelligent, high performance, reliable information technologies that enable NASA missions to (1) increase software safety and quality through error avoidance, early detection and resolution of errors, by utilizing and applying empirically based software engineering best practices; (2) ensure customer software risks are identified and/or that requirements are met and/or exceeded; (3) research, develop, apply, verify, and publish software technologies for competitive advantage and the advancement of science; and (4) facilitate the transfer of science and engineering data, methods, and practices to NASA, educational institutions, state agencies, and commercial organizations. The goals are to become a national Center Of Excellence (COE) in software and system independent verification and validation, and to become an international leading force in the field of software engineering for improving the safety, quality, reliability, and cost performance of software systems. This project addresses the following problems: Ensure safety of NASA missions, ensure requirements are met, minimize programmatic and technological risks of software development and operations, improve software quality, reduce costs and time to delivery, and improve the science of software engineering

Journal of Open Source Software (JOSS): design and first-year review

NASA Astrophysics Data System (ADS)

Smith, Arfon M.

2018-01-01

JOSS is a free and open-access journal that publishes articles describing research software across all disciplines. It has the dual goals of improving the quality of the software submitted and providing a mechanism for research software developers to receive credit. While designed to work within the current merit system of science, JOSS addresses the dearth of rewards for key contributions to science made in the form of software. JOSS publishes articles that encapsulate scholarship contained in the software itself, and its rigorous peer review targets the software components: functionality, documentation, tests, continuous integration, and the license. A JOSS article contains an abstract describing the purpose and functionality of the software, references, and a link to the software archive. JOSS published more than 100 articles in its first year, many from the scientific python ecosystem (including a number of articles related to astronomy and astrophysics). JOSS is a sponsored project of the nonprofit organization NumFOCUS and is an affiliate of the Open Source Initiative.In this presentation, I'll describes the motivation, design, and progress of the Journal of Open Source Software (JOSS) and how it compares to other avenues for publishing research software in astronomy.

Efficacy of a Newly Designed Cephalometric Analysis Software for McNamara Analysis in Comparison with Dolphin Software.

PubMed

Nouri, Mahtab; Hamidiaval, Shadi; Akbarzadeh Baghban, Alireza; Basafa, Mohammad; Fahim, Mohammad

2015-01-01

Cephalometric norms of McNamara analysis have been studied in various populations due to their optimal efficiency. Dolphin cephalometric software greatly enhances the conduction of this analysis for orthodontic measurements. However, Dolphin is very expensive and cannot be afforded by many clinicians in developing countries. A suitable alternative software program in Farsi/English will greatly help Farsi speaking clinicians. The present study aimed to develop an affordable Iranian cephalometric analysis software program and compare it with Dolphin, the standard software available on the market for cephalometric analysis. In this diagnostic, descriptive study, 150 lateral cephalograms of normal occlusion individuals were selected in Mashhad and Qazvin, two major cities of Iran mainly populated with Fars ethnicity, the main Iranian ethnic group. After tracing the cephalograms, the McNamara analysis standards were measured both with Dolphin and the new software. The cephalometric software was designed using Microsoft Visual C++ program in Windows XP. Measurements made with the new software were compared with those of Dolphin software on both series of cephalograms. The validity and reliability were tested using intra-class correlation coefficient. Calculations showed a very high correlation between the results of the Iranian cephalometric analysis software and Dolphin. This confirms the validity and optimal efficacy of the newly designed software (ICC 0.570-1.0). According to our results, the newly designed software has acceptable validity and reliability and can be used for orthodontic diagnosis, treatment planning and assessment of treatment outcome.

Proceedings of the Twenty-Fourth Annual Software Engineering Workshop

NASA Technical Reports Server (NTRS)

2000-01-01

On December 1 and 2, the Software Engineering Laboratory (SEL), a consortium composed of NASA/Goddard, the University of Maryland, and CSC, held the 24th Software Engineering Workshop (SEW), the last of the millennium. Approximately 240 people attended the 2-day workshop. Day 1 was composed of four sessions: International Influence of the Software Engineering Laboratory; Object Oriented Testing and Reading; Software Process Improvement; and Space Software. For the first session, three internationally known software process experts discussed the influence of the SEL with respect to software engineering research. In the Space Software session, prominent representatives from three different NASA sites- GSFC's Marti Szczur, the Jet Propulsion Laboratory's Rick Doyle, and the Ames Research Center IV&V Facility's Lou Blazy- discussed the future of space software in their respective centers. At the end of the first day, the SEW sponsored a reception at the GSFC Visitors' Center. Day 2 also provided four sessions: Using the Experience Factory; A panel discussion entitled "Software Past, Present, and Future: Views from Government, Industry, and Academia"; Inspections; and COTS. The day started with an excellent talk by CSC's Frank McGarry on "Attaining Level 5 in CMM Process Maturity." Session 2, the panel discussion on software, featured NASA Chief Information Officer Lee Holcomb (Government), our own Jerry Page (Industry), and Mike Evangelist of the National Science Foundation (Academia). Each presented his perspective on the most important developments in software in the past 10 years, in the present, and in the future.

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

NASA Astrophysics Data System (ADS)

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.

Resilience Engineering in Critical Long Term Aerospace Software Systems: A New Approach to Spacecraft Software Safety

NASA Astrophysics Data System (ADS)

Dulo, D. A.

Safety critical software systems permeate spacecraft, and in a long term venture like a starship would be pervasive in every system of the spacecraft. Yet software failure today continues to plague both the systems and the organizations that develop them resulting in the loss of life, time, money, and valuable system platforms. A starship cannot afford this type of software failure in long journeys away from home. A single software failure could have catastrophic results for the spaceship and the crew onboard. This paper will offer a new approach to developing safe reliable software systems through focusing not on the traditional safety/reliability engineering paradigms but rather by focusing on a new paradigm: Resilience and Failure Obviation Engineering. The foremost objective of this approach is the obviation of failure, coupled with the ability of a software system to prevent or adapt to complex changing conditions in real time as a safety valve should failure occur to ensure safe system continuity. Through this approach, safety is ensured through foresight to anticipate failure and to adapt to risk in real time before failure occurs. In a starship, this type of software engineering is vital. Through software developed in a resilient manner, a starship would have reduced or eliminated software failure, and would have the ability to rapidly adapt should a software system become unstable or unsafe. As a result, long term software safety, reliability, and resilience would be present for a successful long term starship mission.

Publishing Platform for Scientific Software - Lessons Learned

NASA Astrophysics Data System (ADS)

Hammitzsch, Martin; Fritzsch, Bernadette; Reusser, Dominik; Brembs, Björn; Deinzer, Gernot; Loewe, Peter; Fenner, Martin; van Edig, Xenia; Bertelmann, Roland; Pampel, Heinz; Klump, Jens; Wächter, Joachim

2015-04-01

Scientific software has become an indispensable commodity for the production, processing and analysis of empirical data but also for modelling and simulation of complex processes. Software has a significant influence on the quality of research results. For strengthening the recognition of the academic performance of scientific software development, for increasing its visibility and for promoting the reproducibility of research results, concepts for the publication of scientific software have to be developed, tested, evaluated, and then transferred into operations. For this, the publication and citability of scientific software have to fulfil scientific criteria by means of defined processes and the use of persistent identifiers, similar to data publications. The SciForge project is addressing these challenges. Based on interviews a blueprint for a scientific software publishing platform and a systematic implementation plan has been designed. In addition, the potential of journals, software repositories and persistent identifiers have been evaluated to improve the publication and dissemination of reusable software solutions. It is important that procedures for publishing software as well as methods and tools for software engineering are reflected in the architecture of the platform, in order to improve the quality of the software and the results of research. In addition, it is necessary to work continuously on improving specific conditions that promote the adoption and sustainable utilization of scientific software publications. Among others, this would include policies for the development and publication of scientific software in the institutions but also policies for establishing the necessary competencies and skills of scientists and IT personnel. To implement the concepts developed in SciForge a combined bottom-up / top-down approach is considered that will be implemented in parallel in different scientific domains, e.g. in earth sciences, climate research and the life sciences. Based on the developed blueprints a scientific software publishing platform will be iteratively implemented, tested, and evaluated. Thus the platform should be developed continuously on the basis of gained experiences and results. The platform services will be extended one by one corresponding to the requirements of the communities. Thus the implemented platform for the publication of scientific software can be improved and stabilized incrementally as a tool with software, science, publishing, and user oriented features.

Spacecraft Software Maintenance: An Effective Approach to Reducing Costs and Increasing Science Return

NASA Technical Reports Server (NTRS)

Shell, Elaine M.; Lue, Yvonne; Chu, Martha I.

1999-01-01

Flight software is a mission critical element of spacecraft functionality and performance. When ground operations personnel interface to a spacecraft, they are typically dealing almost entirely with the capabilities of onboard software. This software, even more than critical ground/flight communications systems, is expected to perform perfectly during all phases of spacecraft life. Due to the fact that it can be reprogrammed on-orbit to accommodate degradations or failures in flight hardware, new insights into spacecraft characteristics, new control options which permit enhanced science options, etc., the on- orbit flight software maintenance team is usually significantly responsible for the long term success of a science mission. Failure of flight software to perform as needed can result in very expensive operations work-around costs and lost science opportunities. There are three basic approaches to maintaining spacecraft software--namely using the original developers, using the mission operations personnel, or assembling a center of excellence for multi-spacecraft software maintenance. Not planning properly for flight software maintenance can lead to unnecessarily high on-orbit costs and/or unacceptably long delays, or errors, in patch installations. A common approach for flight software maintenance is to access the original development staff. The argument for utilizing the development staff is that the people who developed the software will be the best people to modify the software on-orbit. However, it can quickly becomes a challenge to obtain the services of these key people. They may no longer be available to the organization. They may have a more urgent job to perform, quite likely on another project under different project management. If they havn't worked on the software for a long time, they may need precious time for refamiliarization to the software, testbeds and tools. Further, a lack of insight into issues related to flight software in its on-orbit environment, may find the developer unprepared for the challenges. The second approach is to train a member of the flight operations team to maintain the spacecraft software. This can prove to be a costly and inflexible solution. The person assigned to this duty may not have enough work to do during a problem free period and may have too much to do when a problem arises. If the person is a talented software engineer, he/she may not enjoy the limited software opportunities available in this position; and may eventually leave for newer technology computer science opportunities. Training replacement flight software personnel can be a difficult and lengthy process. The third approach is to assemble a center of excellence for on-orbit spacecraft software maintenance. Personnel in this specialty center can be managed to support flight software of multiple missions at once. The variety of challenges among a set of on-orbit missions, can result in a dedicated, talented staff which is fully trained and available to support each mission's needs. Such staff are not software developers but are rather spacecraft software systems engineers. The cost to any one mission is extremely low because the software staff works and charges, minimally on missions with no current operations issues; and their professional insight into on-orbit software troubleshooting and maintenance methods ensures low risk, effective and minimal-cost solutions to on-orbit issues.

Remote software upload techniques in future vehicles and their performance analysis

NASA Astrophysics Data System (ADS)

Hossain, Irina

Updating software in vehicle Electronic Control Units (ECUs) will become a mandatory requirement for a variety of reasons, for examples, to update/fix functionality of an existing system, add new functionality, remove software bugs and to cope up with ITS infrastructure. Software modules of advanced vehicles can be updated using Remote Software Upload (RSU) technique. The RSU employs infrastructure-based wireless communication technique where the software supplier sends the software to the targeted vehicle via a roadside Base Station (BS). However, security is critically important in RSU to avoid any disasters due to malfunctions of the vehicle or to protect the proprietary algorithms from hackers, competitors or people with malicious intent. In this thesis, a mechanism of secure software upload in advanced vehicles is presented which employs mutual authentication of the software provider and the vehicle using a pre-shared authentication key before sending the software. The software packets are sent encrypted with a secret key along with the Message Digest (MD). In order to increase the security level, it is proposed the vehicle to receive more than one copy of the software along with the MD in each copy. The vehicle will install the new software only when it receives more than one identical copies of the software. In order to validate the proposition, analytical expressions of average number of packet transmissions for successful software update is determined. Different cases are investigated depending on the vehicle's buffer size and verification methods. The analytical and simulation results show that it is sufficient to send two copies of the software to the vehicle to thwart any security attack while uploading the software. The above mentioned unicast method for RSU is suitable when software needs to be uploaded to a single vehicle. Since multicasting is the most efficient method of group communication, updating software in an ECU of a large number of vehicles could benefit from it. However, like the unicast RSU, the security requirements of multicast communication, i.e., authenticity, confidentiality and integrity of the software transmitted and access control of the group members is challenging. In this thesis, an infrastructure-based mobile multicasting for RSU in vehicle ECUs is proposed where an ECU receives the software from a remote software distribution center using the road side BSs as gateways. The Vehicular Software Distribution Network (VSDN) is divided into small regions administered by a Regional Group Manager (RGM). Two multicast Group Key Management (GKM) techniques are proposed based on the degree of trust on the BSs named Fully-trusted (FT) and Semi-trusted (ST) systems. Analytical models are developed to find the multicast session establishment latency and handover latency for these two protocols. The average latency to perform mutual authentication of the software vendor and a vehicle, and to send the multicast session key by the software provider during multicast session initialization, and the handoff latency during multicast session is calculated. Analytical and simulation results show that the link establishment latency per vehicle of our proposed schemes is in the range of few seconds and the ST system requires few ms higher time than the FT system. The handoff latency is also in the range of few seconds and in some cases ST system requires less handoff time than the FT system. Thus, it is possible to build an efficient GKM protocol without putting too much trust on the BSs.

Combat Identification Systems COMO Integrated Air Defense Model Evaluation (CISE) Study

DTIC Science & Technology

1989-02-01

use K or IR , whichever one applies) E-6 CAA-SR-89- 3 Subroutine PDECLR 1/21/88 Before label 1000 Insert: IF (IR.GT.10) IR a 10 These changes were made...Internal Distribution: Unclassified Library 2 F-2 CAA-SR-89- 3 GLOSSARY 1. ABBREVIATIONS, ACRONYMS, AND SHORT TERMS ADM2 Air Defense Models Modification...STUDY REPORT ’ , CAA-Sn-89- 3 i , .- CD o COMBAT IDENTIFICATION SYSTEMS N COMO INTEGRATED AIR DEFENSE MODEL EVALUATION (CISE) STUDY FEBRUARY 1989

48 CFR 239.101 - Policy.

Code of Federal Regulations, 2011 CFR

2011-10-01

.... See Subpart 208.74 when acquiring commercial software or software maintenance. See 227.7202 for policy on the acquisition of commercial computer software and commercial computer software documentation...

48 CFR 239.101 - Policy.

Code of Federal Regulations, 2010 CFR

2010-10-01

.... See Subpart 208.74 when acquiring commercial software or software maintenance. See 227.7202 for policy on the acquisition of commercial computer software and commercial computer software documentation...

48 CFR 239.101 - Policy.

Code of Federal Regulations, 2012 CFR

2012-10-01

.... See Subpart 208.74 when acquiring commercial software or software maintenance. See 227.7202 for policy on the acquisition of commercial computer software and commercial computer software documentation...

48 CFR 239.101 - Policy.

Code of Federal Regulations, 2014 CFR

2014-10-01

.... See Subpart 208.74 when acquiring commercial software or software maintenance. See 227.7202 for policy on the acquisition of commercial computer software and commercial computer software documentation...

48 CFR 239.101 - Policy.

Code of Federal Regulations, 2013 CFR

2013-10-01

.... See Subpart 208.74 when acquiring commercial software or software maintenance. See 227.7202 for policy on the acquisition of commercial computer software and commercial computer software documentation...

Software Health Management: A Short Review of Challenges and Existing Techniques

NASA Technical Reports Server (NTRS)

Pipatsrisawat, Knot; Darwiche, Adnan; Mengshoel, Ole J.; Schumann, Johann

2009-01-01

Modern spacecraft (as well as most other complex mechanisms like aircraft, automobiles, and chemical plants) rely more and more on software, to a point where software failures have caused severe accidents and loss of missions. Software failures during a manned mission can cause loss of life, so there are severe requirements to make the software as safe and reliable as possible. Typically, verification and validation (V&V) has the task of making sure that all software errors are found before the software is deployed and that it always conforms to the requirements. Experience, however, shows that this gold standard of error-free software cannot be reached in practice. Even if the software alone is free of glitches, its interoperation with the hardware (e.g., with sensors or actuators) can cause problems. Unexpected operational conditions or changes in the environment may ultimately cause a software system to fail. Is there a way to surmount this problem? In most modern aircraft and many automobiles, hardware such as central electrical, mechanical, and hydraulic components are monitored by IVHM (Integrated Vehicle Health Management) systems. These systems can recognize, isolate, and identify faults and failures, both those that already occurred as well as imminent ones. With the help of diagnostics and prognostics, appropriate mitigation strategies can be selected (replacement or repair, switch to redundant systems, etc.). In this short paper, we discuss some challenges and promising techniques for software health management (SWHM). In particular, we identify unique challenges for preventing software failure in systems which involve both software and hardware components. We then present our classifications of techniques related to SWHM. These classifications are performed based on dimensions of interest to both developers and users of the techniques, and hopefully provide a map for dealing with software faults and failures.

Software Reliability Analysis of NASA Space Flight Software: A Practical Experience

PubMed Central

Sukhwani, Harish; Alonso, Javier; Trivedi, Kishor S.; Mcginnis, Issac

2017-01-01

In this paper, we present the software reliability analysis of the flight software of a recently launched space mission. For our analysis, we use the defect reports collected during the flight software development. We find that this software was developed in multiple releases, each release spanning across all software life-cycle phases. We also find that the software releases were developed and tested for four different hardware platforms, spanning from off-the-shelf or emulation hardware to actual flight hardware. For releases that exhibit reliability growth or decay, we fit Software Reliability Growth Models (SRGM); otherwise we fit a distribution function. We find that most releases exhibit reliability growth, with Log-Logistic (NHPP) and S-Shaped (NHPP) as the best-fit SRGMs. For the releases that experience reliability decay, we investigate the causes for the same. We find that such releases were the first software releases to be tested on a new hardware platform, and hence they encountered major hardware integration issues. Also such releases seem to have been developed under time pressure in order to start testing on the new hardware platform sooner. Such releases exhibit poor reliability growth, and hence exhibit high predicted failure rate. Other problems include hardware specification changes and delivery delays from vendors. Thus, our analysis provides critical insights and inputs to the management to improve the software development process. As NASA has moved towards a product line engineering for its flight software development, software for future space missions will be developed in a similar manner and hence the analysis results for this mission can be considered as a baseline for future flight software missions. PMID:29278255

ISEES: an institute for sustainable software to accelerate environmental science

NASA Astrophysics Data System (ADS)

Jones, M. B.; Schildhauer, M.; Fox, P. A.

2013-12-01

Software is essential to the full science lifecycle, spanning data acquisition, processing, quality assessment, data integration, analysis, modeling, and visualization. Software runs our meteorological sensor systems, our data loggers, and our ocean gliders. Every aspect of science is impacted by, and improved by, software. Scientific advances ranging from modeling climate change to the sequencing of the human genome have been rendered possible in the last few decades due to the massive improvements in the capabilities of computers to process data through software. This pivotal role of software in science is broadly acknowledged, while simultaneously being systematically undervalued through minimal investments in maintenance and innovation. As a community, we need to embrace the creation, use, and maintenance of software within science, and address problems such as code complexity, openness,reproducibility, and accessibility. We also need to fully develop new skills and practices in software engineering as a core competency in our earth science disciplines, starting with undergraduate and graduate education and extending into university and agency professional positions. The Institute for Sustainable Earth and Environmental Software (ISEES) is being envisioned as a community-driven activity that can facilitate and galvanize activites around scientific software in an analogous way to synthesis centers such as NCEAS and NESCent that have stimulated massive advances in ecology and evolution. We will describe the results of six workshops (Science Drivers, Software Lifecycles, Software Components, Workforce Development and Training, Sustainability and Governance, and Community Engagement) that have been held in 2013 to envision such an institute. We will present community recommendations from these workshops and our strategic vision for how ISEES will address the technical issues in the software lifecycle, sustainability of the whole software ecosystem, and the critical issue of computational training for the scientific community. Process for envisioning ISEES.

Advanced communications technology satellite high burst rate link evaluation terminal power control and rain fade software test plan, version 1.0

NASA Technical Reports Server (NTRS)

Reinhart, Richard C.

1993-01-01

The Power Control and Rain Fade Software was developed at the NASA Lewis Research Center to support the Advanced Communications Technology Satellite High Burst Rate Link Evaluation Terminal (ACTS HBR-LET). The HBR-LET is an experimenters terminal to communicate with the ACTS for various experiments by government, university, and industry agencies. The Power Control and Rain Fade Software is one segment of the Control and Performance Monitor (C&PM) Software system of the HBR-LET. The Power Control and Rain Fade Software automatically controls the LET uplink power to compensate for signal fades. Besides power augmentation, the C&PM Software system is also responsible for instrument control during HBR-LET experiments, control of the Intermediate Frequency Switch Matrix on board the ACTS to yield a desired path through the spacecraft payload, and data display. The Power Control and Rain Fade Software User's Guide, Version 1.0 outlines the commands and procedures to install and operate the Power Control and Rain Fade Software. The Power Control and Rain Fade Software Maintenance Manual, Version 1.0 is a programmer's guide to the Power Control and Rain Fade Software. This manual details the current implementation of the software from a technical perspective. Included is an overview of the Power Control and Rain Fade Software, computer algorithms, format representations, and computer hardware configuration. The Power Control and Rain Fade Test Plan provides a step-by-step procedure to verify the operation of the software using a predetermined signal fade event. The Test Plan also provides a means to demonstrate the capability of the software.

A proven approach for more effective software development and maintenance

NASA Technical Reports Server (NTRS)

Pajerski, Rose; Hall, Dana; Sinclair, Craig

1994-01-01

Modern space flight mission operations and associated ground data systems are increasingly dependent upon reliable, quality software. Critical functions such as command load preparation, health and status monitoring, communications link scheduling and conflict resolution, and transparent gateway protocol conversion are routinely performed by software. Given budget constraints and the ever increasing capabilities of processor technology, the next generation of control centers and data systems will be even more dependent upon software across all aspects of performance. A key challenge now is to implement improved engineering, management, and assurance processes for the development and maintenance of that software; processes that cost less, yield higher quality products, and that self-correct for continual improvement evolution. The NASA Goddard Space Flight Center has a unique experience base that can be readily tapped to help solve the software challenge. Over the past eighteen years, the Software Engineering Laboratory within the code 500 Flight Dynamics Division has evolved a software development and maintenance methodology that accommodates the unique characteristics of an organization while optimizing and continually improving the organization's software capabilities. This methodology relies upon measurement, analysis, and feedback much analogous to that of control loop systems. It is an approach with a time-tested track record proven through repeated applications across a broad range of operational software development and maintenance projects. This paper describes the software improvement methodology employed by the Software Engineering Laboratory, and how it has been exploited within the Flight Dynamics Division with GSFC Code 500. Examples of specific improvement in the software itself and its processes are presented to illustrate the effectiveness of the methodology. Finally, the initial findings are given when this methodology was applied across the mission operations and ground data systems software domains throughout Code 500.

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

PubMed

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 first step to create standards for patient registry software system assessments. Copyright © 2017 Elsevier Inc. All rights reserved.

Advanced communications technology satellite high burst rate link evaluation terminal communication protocol software user's guide, version 1.0

NASA Technical Reports Server (NTRS)

Reinhart, Richard C.

1993-01-01

The Communication Protocol Software was developed at the NASA Lewis Research Center to support the Advanced Communications Technology Satellite High Burst Rate Link Evaluation Terminal (ACTS HBR-LET). The HBR-LET is an experimenters terminal to communicate with the ACTS for various experiments by government, university, and industry agencies. The Communication Protocol Software is one segment of the Control and Performance Monitor (C&PM) Software system of the HBR-LET. The Communication Protocol Software allows users to control and configure the Intermediate Frequency Switch Matrix (IFSM) on board the ACTS to yield a desired path through the spacecraft payload. Besides IFSM control, the C&PM Software System is also responsible for instrument control during HBR-LET experiments, uplink power control of the HBR-LET to demonstrate power augmentation during signal fade events, and data display. The Communication Protocol Software User's Guide, Version 1.0 (NASA CR-189162) outlines the commands and procedures to install and operate the Communication Protocol Software. Configuration files used to control the IFSM, operator commands, and error recovery procedures are discussed. The Communication Protocol Software Maintenance Manual, Version 1.0 (NASA CR-189163, to be published) is a programmer's guide to the Communication Protocol Software. This manual details the current implementation of the software from a technical perspective. Included is an overview of the Communication Protocol Software, computer algorithms, format representations, and computer hardware configuration. The Communication Protocol Software Test Plan (NASA CR-189164, to be published) provides a step-by-step procedure to verify the operation of the software. Included in the Test Plan is command transmission, telemetry reception, error detection, and error recovery procedures.

Software Reliability Analysis of NASA Space Flight Software: A Practical Experience.

PubMed

Sukhwani, Harish; Alonso, Javier; Trivedi, Kishor S; Mcginnis, Issac

2016-01-01

In this paper, we present the software reliability analysis of the flight software of a recently launched space mission. For our analysis, we use the defect reports collected during the flight software development. We find that this software was developed in multiple releases, each release spanning across all software life-cycle phases. We also find that the software releases were developed and tested for four different hardware platforms, spanning from off-the-shelf or emulation hardware to actual flight hardware. For releases that exhibit reliability growth or decay, we fit Software Reliability Growth Models (SRGM); otherwise we fit a distribution function. We find that most releases exhibit reliability growth, with Log-Logistic (NHPP) and S-Shaped (NHPP) as the best-fit SRGMs. For the releases that experience reliability decay, we investigate the causes for the same. We find that such releases were the first software releases to be tested on a new hardware platform, and hence they encountered major hardware integration issues. Also such releases seem to have been developed under time pressure in order to start testing on the new hardware platform sooner. Such releases exhibit poor reliability growth, and hence exhibit high predicted failure rate. Other problems include hardware specification changes and delivery delays from vendors. Thus, our analysis provides critical insights and inputs to the management to improve the software development process. As NASA has moved towards a product line engineering for its flight software development, software for future space missions will be developed in a similar manner and hence the analysis results for this mission can be considered as a baseline for future flight software missions.

SEI Software Engineering Education Directory.

DTIC Science & Technology

1987-02-01

Software Design and Development Gilbert. Philip Systems: CDC Cyber 170/750 CDC Cyber 170760 DEC POP 11/44 PRIME AT&T 3B5 IBM PC IBM XT IBM RT...Macintosh VAx 8300 Software System Development and Laboratory CS 480/480L U P X T Textbooks: Software Design and Development Gilbert, Philip Systems: CDC...Acting Chair (618) 692-2386 Courses: Software Design and Development CS 424 U P E Y Textbooks: Software Design and Development, Gilbert, Philip Topics

The Application of Software Safety to the Constellation Program Launch Control System

NASA Technical Reports Server (NTRS)

Kania, James; Hill, Janice

2011-01-01

The application of software safety practices on the LCS project resulted in the successful implementation of the NASA Software Safety Standard NASA-STD-8719.138 and CxP software safety requirements. The GOP-GEN-GSW-011 Hazard Report was the first report developed at KSC to identify software hazard causes and their controls. This approach can be applied to similar large software - intensive systems where loss of control can lead to a hazard.

Software attribute visualization for high integrity software

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

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.

A Matrix Approach to Software Process Definition

NASA Technical Reports Server (NTRS)

Schultz, David; Bachman, Judith; Landis, Linda; Stark, Mike; Godfrey, Sally; Morisio, Maurizio; Powers, Edward I. (Technical Monitor)

2000-01-01

The Software Engineering Laboratory (SEL) is currently engaged in a Methodology and Metrics program for the Information Systems Center (ISC) at Goddard Space Flight Center (GSFC). This paper addresses the Methodology portion of the program. The purpose of the Methodology effort is to assist a software team lead in selecting and tailoring a software development or maintenance process for a specific GSFC project. It is intended that this process will also be compliant with both ISO 9001 and the Software Engineering Institute's Capability Maturity Model (CMM). Under the Methodology program, we have defined four standard ISO-compliant software processes for the ISC, and three tailoring criteria that team leads can use to categorize their projects. The team lead would select a process and appropriate tailoring factors, from which a software process tailored to the specific project could be generated. Our objective in the Methodology program is to present software process information in a structured fashion, to make it easy for a team lead to characterize the type of software engineering to be performed, and to apply tailoring parameters to search for an appropriate software process description. This will enable the team lead to follow a proven, effective software process and also satisfy NASA's requirement for compliance with ISO 9001 and the anticipated requirement for CMM assessment. This work is also intended to support the deployment of sound software processes across the ISC.

An Architecture, System Engineering, and Acquisition Approach for Space System Software Resiliency

NASA Astrophysics Data System (ADS)

Phillips, Dewanne Marie

Software intensive space systems can harbor defects and vulnerabilities that may enable external adversaries or malicious insiders to disrupt or disable system functions, risking mission compromise or loss. Mitigating this risk demands a sustained focus on the security and resiliency of the system architecture including software, hardware, and other components. Robust software engineering practices contribute to the foundation of a resilient system so that the system "can take a hit to a critical component and recover in a known, bounded, and generally acceptable period of time". Software resiliency must be a priority and addressed early in the life cycle development to contribute a secure and dependable space system. Those who develop, implement, and operate software intensive space systems must determine the factors and systems engineering practices to address when investing in software resiliency. This dissertation offers methodical approaches for improving space system resiliency through software architecture design, system engineering, increased software security, thereby reducing the risk of latent software defects and vulnerabilities. By providing greater attention to the early life cycle phases of development, we can alter the engineering process to help detect, eliminate, and avoid vulnerabilities before space systems are delivered. To achieve this objective, this dissertation will identify knowledge, techniques, and tools that engineers and managers can utilize to help them recognize how vulnerabilities are produced and discovered so that they can learn to circumvent them in future efforts. We conducted a systematic review of existing architectural practices, standards, security and coding practices, various threats, defects, and vulnerabilities that impact space systems from hundreds of relevant publications and interviews of subject matter experts. We expanded on the system-level body of knowledge for resiliency and identified a new software architecture framework and acquisition methodology to improve the resiliency of space systems from a software perspective with an emphasis on the early phases of the systems engineering life cycle. This methodology involves seven steps: 1) Define technical resiliency requirements, 1a) Identify standards/policy for software resiliency, 2) Develop a request for proposal (RFP)/statement of work (SOW) for resilient space systems software, 3) Define software resiliency goals for space systems, 4) Establish software resiliency quality attributes, 5) Perform architectural tradeoffs and identify risks, 6) Conduct architecture assessments as part of the procurement process, and 7) Ascertain space system software architecture resiliency metrics. Data illustrates that software vulnerabilities can lead to opportunities for malicious cyber activities, which could degrade the space mission capability for the user community. Reducing the number of vulnerabilities by improving architecture and software system engineering practices can contribute to making space systems more resilient. Since cyber-attacks are enabled by shortfalls in software, robust software engineering practices and an architectural design are foundational to resiliency, which is a quality that allows the system to "take a hit to a critical component and recover in a known, bounded, and generally acceptable period of time". To achieve software resiliency for space systems, acquirers and suppliers must identify relevant factors and systems engineering practices to apply across the lifecycle, in software requirements analysis, architecture development, design, implementation, verification and validation, and maintenance phases.

Influence of H 2O and H 2S on the composition, activity, and stability of sulfided Mo, CoMo, and NiMo supported on MgAl 2O 4 for hydrodeoxygenation of ethylene glycol

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

Dabros, Trine Marie Hartmann; Gaur, Abhijeet; Pintos, Delfina Garcia

Here in this work, density functional theory (DFT), catalytic activity tests, and in-situ X-ray absorption spectroscopy (XAS) was performed to gain detailed insights into the activity and stability of MoS 2, Ni-MoS 2, and Co-MoS 2 catalysts used for hydrodeoxygenation (HDO) of ethylene glycol upon variation of the partial pressures of H 2O and H 2S. The results show high water tolerance of the catalysts and highlight the importance of promotion and H 2S level during HDO. DFT calculations unraveled that the active edge of MoS 2 could be stabilized against SO exchanges by increasing the partial pressure of Hmore » 2S or by promotion with either Ni or Co. The Mo, NiMo, and CoMo catalysts of the present study were all active and fairly selective for ethylene glycol HDO at 400 °C, 27 bar H 2, and 550–2200 ppm H 2S, and conversions of ≈50–100%. The unpromoted Mo/MgAl 2O 4 catalyst had a lower stability and activity per gram catalyst than the promoted analogues. The NiMo and CoMo catalysts produced ethane, ethylene, and C1 cracking products with a C 2/C 1 ratio of 1.5–2.0 at 550 ppm H 2S. This ratio of HDO to cracking could be increased to ≈2 at 2200 ppm H 2S which also stabilized the activity. Removing H 2S from the feed caused severe catalyst deactivation. Both DFT and catalytic activity tests indicated that increasing the H 2S concentration increased the concentration of SH groups on the catalyst, which correspondingly activated and stabilized the catalytic HDO performance. In-situ XAS further supported that the catalysts were tolerant towards water when exposed to increasing water concentration with H2O/H2S ratios up to 300 at 400–450 °C. Raman spectroscopy and XAS showed that MoS2 was present in the prepared catalysts as small and highly dispersed particles, probably owing to a strong interaction with the support. Linear combination fitting (LCF) analysis of the X-ray absorption near edge structure (XANES) spectra obtained during in-situ sulfidation showed that Ni was sulfided faster than Mo and CoMo, and that Mo was sulfided faster when promoted with Ni. Extended X-ray absorption fine structure (EXAFS) results showed the presence of MoS 2 in all sulfided catalysts. Lastly, sulfided CoMo was present as a mixture of CoMoS and Co 9S 8, whereas sulfided NiMo was present as NiMoS.« less

Influence of H 2O and H 2S on the composition, activity, and stability of sulfided Mo, CoMo, and NiMo supported on MgAl 2O 4 for hydrodeoxygenation of ethylene glycol

DOE PAGES

Dabros, Trine Marie Hartmann; Gaur, Abhijeet; Pintos, Delfina Garcia; ...

2017-12-10

Here in this work, density functional theory (DFT), catalytic activity tests, and in-situ X-ray absorption spectroscopy (XAS) was performed to gain detailed insights into the activity and stability of MoS 2, Ni-MoS 2, and Co-MoS 2 catalysts used for hydrodeoxygenation (HDO) of ethylene glycol upon variation of the partial pressures of H 2O and H 2S. The results show high water tolerance of the catalysts and highlight the importance of promotion and H 2S level during HDO. DFT calculations unraveled that the active edge of MoS 2 could be stabilized against SO exchanges by increasing the partial pressure of Hmore » 2S or by promotion with either Ni or Co. The Mo, NiMo, and CoMo catalysts of the present study were all active and fairly selective for ethylene glycol HDO at 400 °C, 27 bar H 2, and 550–2200 ppm H 2S, and conversions of ≈50–100%. The unpromoted Mo/MgAl 2O 4 catalyst had a lower stability and activity per gram catalyst than the promoted analogues. The NiMo and CoMo catalysts produced ethane, ethylene, and C1 cracking products with a C 2/C 1 ratio of 1.5–2.0 at 550 ppm H 2S. This ratio of HDO to cracking could be increased to ≈2 at 2200 ppm H 2S which also stabilized the activity. Removing H 2S from the feed caused severe catalyst deactivation. Both DFT and catalytic activity tests indicated that increasing the H 2S concentration increased the concentration of SH groups on the catalyst, which correspondingly activated and stabilized the catalytic HDO performance. In-situ XAS further supported that the catalysts were tolerant towards water when exposed to increasing water concentration with H2O/H2S ratios up to 300 at 400–450 °C. Raman spectroscopy and XAS showed that MoS2 was present in the prepared catalysts as small and highly dispersed particles, probably owing to a strong interaction with the support. Linear combination fitting (LCF) analysis of the X-ray absorption near edge structure (XANES) spectra obtained during in-situ sulfidation showed that Ni was sulfided faster than Mo and CoMo, and that Mo was sulfided faster when promoted with Ni. Extended X-ray absorption fine structure (EXAFS) results showed the presence of MoS 2 in all sulfided catalysts. Lastly, sulfided CoMo was present as a mixture of CoMoS and Co 9S 8, whereas sulfided NiMo was present as NiMoS.« less

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

ERIC Educational Resources Information Center

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…

Proceedings of the 14th Annual Software Engineering Workshop

NASA Technical Reports Server (NTRS)

1989-01-01

Several software related topics are presented. Topics covered include studies and experiment at the Software Engineering Laboratory at the Goddard Space Flight Center, predicting project success from the Software Project Management Process, software environments, testing in a reuse environment, domain directed reuse, and classification tree analysis using the Amadeus measurement and empirical analysis.

Software Process Improvement through the Removal of Project-Level Knowledge Flow Obstacles: The Perceptions of Software Engineers

ERIC Educational Resources Information Center

Mitchell, Susan Marie

2012-01-01

Uncontrollable costs, schedule overruns, and poor end product quality continue to plague the software engineering field. Innovations formulated with the expectation to minimize or eliminate cost, schedule, and quality problems have generally fallen into one of three categories: programming paradigms, software tools, and software process…

15 CFR Supplement No. 2 to Part 774 - General Technology and Software Notes

Code of Federal Regulations, 2013 CFR

2013-01-01

... 15 Commerce and Foreign Trade 2 2013-01-01 2013-01-01 false General Technology and Software Notes... Software Notes 1. General Technology Note. The export of “technology” that is “required” for the... necessary” information. 2. General Software Note. License Exception TSU (“mass market” software) is...

48 CFR 252.227-7027 - Deferred ordering of technical data or computer software.

Code of Federal Regulations, 2013 CFR

2013-10-01

... technical data or computer software. 252.227-7027 Section 252.227-7027 Federal Acquisition Regulations... data or computer software. As prescribed at 227.7103-8(b), use the following clause: Deferred Ordering of Technical Data or Computer Software (APR 1988) In addition to technical data or computer software...

48 CFR 252.227-7027 - Deferred ordering of technical data or computer software.

Code of Federal Regulations, 2011 CFR

2011-10-01

... technical data or computer software. 252.227-7027 Section 252.227-7027 Federal Acquisition Regulations... data or computer software. As prescribed at 227.7103-8(b), use the following clause: Deferred Ordering of Technical Data or Computer Software (APR 1988) In addition to technical data or computer software...

37 CFR 201.24 - Warning of copyright for software lending by nonprofit libraries.

Code of Federal Regulations, 2012 CFR

2012-07-01

... software lending by nonprofit libraries. 201.24 Section 201.24 Patents, Trademarks, and Copyrights... copyright for software lending by nonprofit libraries. (a) Definition. A Warning of Copyright for Software... States Code, as amended by the Computer Software Rental Amendments Act of 1990, Public Law 101-650. As...

48 CFR 252.227-7027 - Deferred ordering of technical data or computer software.

Code of Federal Regulations, 2012 CFR

2012-10-01

... technical data or computer software. 252.227-7027 Section 252.227-7027 Federal Acquisition Regulations... data or computer software. As prescribed at 227.7103-8(b), use the following clause: Deferred Ordering of Technical Data or Computer Software (APR 1988) In addition to technical data or computer software...

37 CFR 201.24 - Warning of copyright for software lending by nonprofit libraries.

Code of Federal Regulations, 2013 CFR

2013-07-01

... software lending by nonprofit libraries. 201.24 Section 201.24 Patents, Trademarks, and Copyrights... copyright for software lending by nonprofit libraries. (a) Definition. A Warning of Copyright for Software... States Code, as amended by the Computer Software Rental Amendments Act of 1990, Public Law 101-650. As...

Using MATLAB Software on the Peregrine System | High-Performance Computing

Science.gov Websites

| NREL MATLAB Software on the Peregrine System Using MATLAB Software on the Peregrine System Learn how to use MATLAB software on the Peregrine system. Running MATLAB in Batch Mode Using the node. Understanding Versions and Licenses Learn about the MATLAB software versions and licenses

A Comparison of Learning Technologies for Teaching Spacecraft Software Development

ERIC Educational Resources Information Center

Straub, Jeremy

2014-01-01

The development of software for spacecraft represents a particular challenge and is, in many ways, a worst case scenario from a design perspective. Spacecraft software must be "bulletproof" and operate for extended periods of time without user intervention. If the software fails, it cannot be manually serviced. Software failure may…

48 CFR 252.227-7027 - Deferred ordering of technical data or computer software.

Code of Federal Regulations, 2014 CFR

2014-10-01

... technical data or computer software. 252.227-7027 Section 252.227-7027 Federal Acquisition Regulations... data or computer software. As prescribed at 227.7103-8(b), use the following clause: Deferred Ordering of Technical Data or Computer Software (APR 1988) In addition to technical data or computer software...

15 CFR Supplement No. 2 to Part 774 - General Technology and Software Notes

Code of Federal Regulations, 2011 CFR

2011-01-01

... 15 Commerce and Foreign Trade 2 2011-01-01 2011-01-01 false General Technology and Software Notes... Software Notes 1. General Technology Note. The export of “technology” that is “required” for the... necessary” information. 2. General Software Note. License Exception TSU (“mass market” software) is...

15 CFR Supplement No. 2 to Part 774 - General Technology and Software Notes

Code of Federal Regulations, 2012 CFR

2012-01-01

... 15 Commerce and Foreign Trade 2 2012-01-01 2012-01-01 false General Technology and Software Notes... Software Notes 1. General Technology Note. The export of “technology” that is “required” for the... necessary” information. 2. General Software Note. License Exception TSU (“mass market” software) is...

37 CFR 201.24 - Warning of copyright for software lending by nonprofit libraries.

Code of Federal Regulations, 2011 CFR

2011-07-01

... software lending by nonprofit libraries. 201.24 Section 201.24 Patents, Trademarks, and Copyrights... copyright for software lending by nonprofit libraries. (a) Definition. A Warning of Copyright for Software... States Code, as amended by the Computer Software Rental Amendments Act of 1990, Public Law 101-650. As...

48 CFR 252.227-7027 - Deferred ordering of technical data or computer software.

Code of Federal Regulations, 2010 CFR

2010-10-01

... technical data or computer software. 252.227-7027 Section 252.227-7027 Federal Acquisition Regulations... data or computer software. As prescribed at 227.7103-8(b), use the following clause: Deferred Ordering of Technical Data or Computer Software (APR 1988) In addition to technical data or computer software...

37 CFR 201.24 - Warning of copyright for software lending by nonprofit libraries.

Code of Federal Regulations, 2010 CFR

2010-07-01

... software lending by nonprofit libraries. 201.24 Section 201.24 Patents, Trademarks, and Copyrights... copyright for software lending by nonprofit libraries. (a) Definition. A Warning of Copyright for Software... States Code, as amended by the Computer Software Rental Amendments Act of 1990, Public Law 101-650. As...

37 CFR 201.24 - Warning of copyright for software lending by nonprofit libraries.

Code of Federal Regulations, 2014 CFR

2014-07-01

... software lending by nonprofit libraries. 201.24 Section 201.24 Patents, Trademarks, and Copyrights U.S... copyright for software lending by nonprofit libraries. (a) Definition. A Warning of Copyright for Software... States Code, as amended by the Computer Software Rental Amendments Act of 1990, Public Law 101-650. As...

RICIS Software Engineering 90 Symposium: Aerospace Applications and Research Directions Proceedings Appendices

NASA Technical Reports Server (NTRS)

1990-01-01

Papers presented at RICIS Software Engineering Symposium are compiled. The following subject areas are covered: flight critical software; management of real-time Ada; software reuse; megaprogramming software; Ada net; POSIX and Ada integration in the Space Station Freedom Program; and assessment of formal methods for trustworthy computer systems.

Quality Market: Design and Field Study of Prediction Market for Software Quality Control

ERIC Educational Resources Information Center

Krishnamurthy, Janaki

2010-01-01

Given the increasing competition in the software industry and the critical consequences of software errors, it has become important for companies to achieve high levels of software quality. While cost reduction and timeliness of projects continue to be important measures, software companies are placing increasing attention on identifying the user…

Evaluation of Agricultural Accounting Software. Improved Decision Making. Third Edition.

ERIC Educational Resources Information Center

Lovell, Ashley C., Comp.

Following a discussion of the evaluation criteria for choosing accounting software, this guide contains reviews of 27 accounting software programs that could be used by farm or ranch business managers. The information in the reviews was provided by the software vendors and covers the following points for each software package: general features,…

Pre Service Teachers' Usage of Dynamic Mathematics Software

ERIC Educational Resources Information Center

Bulut, Mehmet; Bulut, Neslihan

2011-01-01

Aim of this study is about mathematics education and dynamic mathematics software. Dynamic mathematics software provides new opportunities for using both computer algebra system and dynamic geometry software. GeoGebra selected as dynamic mathematics software in this research. In this study, it is investigated that what is the usage of pre service…

Sustaining Software-Intensive Systems

DTIC Science & Technology

2006-05-01

2.2 Multi- Service Operational Test and Evaluation .......................................4 2.3 Stable Software Baseline...or equivalent document • completed Multi- Service Operational Test and Evaluation (MOT&E) for the potential production software package (or OT&E if...not multi- service ) • stable software production baseline • complete and current software documentation • Authority to Operate (ATO) for an

Multimedia Software Evaluation Form for Teachers

ERIC Educational Resources Information Center

Herring, Donna F.; Notar, Charles E.; Wilson, Janell D.

2005-01-01

Schools are currently receiving increased funds for multimedia software for classrooms. There is a need for good software in the schools, and there is a need to know how to evaluate software and not naively rely on advertisements. Evaluators of multimedia software for education must have the skills to critically evaluate and make decisions not…

Modeling software systems by domains

NASA Technical Reports Server (NTRS)

Dippolito, Richard; Lee, Kenneth

1992-01-01

The Software Architectures Engineering (SAE) Project at the Software Engineering Institute (SEI) has developed engineering modeling techniques that both reduce the complexity of software for domain-specific computer systems and result in systems that are easier to build and maintain. These techniques allow maximum freedom for system developers to apply their domain expertise to software. We have applied these techniques to several types of applications, including training simulators operating in real time, engineering simulators operating in non-real time, and real-time embedded computer systems. Our modeling techniques result in software that mirrors both the complexity of the application and the domain knowledge requirements. We submit that the proper measure of software complexity reflects neither the number of software component units nor the code count, but the locus of and amount of domain knowledge. As a result of using these techniques, domain knowledge is isolated by fields of engineering expertise and removed from the concern of the software engineer. In this paper, we will describe kinds of domain expertise, describe engineering by domains, and provide relevant examples of software developed for simulator applications using the techniques.

Intelligent Agents for Design and Synthesis Environments: My Summary

NASA Technical Reports Server (NTRS)

Norvig, Peter

1999-01-01

This presentation gives a summary of intelligent agents for design synthesis environments. We'll start with the conclusions, and work backwards to justify them. First, an important assumption is that agents (whatever they are) are good for software engineering. This is especially true for software that operates in an uncertain, changing environment. The "real world" of physical artifacts is like that: uncertain in what we can measure, changing in that things are always breaking down, and we must interact with non-software entities. The second point is that software engineering techniques can contribute to good design. There may have been a time when we wanted to build simple artifacts containing little or no software. But modern aircraft and spacecraft are complex, and rely on a great deal of software. So better software engineering leads to better designed artifacts, especially when we are designing a series of related artifacts and can amortize the costs of software development. The third point is that agents are especially useful for design tasks, above and beyond their general usefulness for software engineering, and the usefulness of software engineering to design.

Software System Safety and the NASA Aeronautics Blueprint

NASA Technical Reports Server (NTRS)

Holloway, C. Michael; Hayhurst, Kelly J.

2002-01-01

NASA's Aeronautics Blueprint lays out a research agenda for the Agency s aeronautics program. The word software appears only four times in this Blueprint, but the critical importance of safe and correct software to the fulfillment of the proposed research is evident on almost every page. Most of the technology solutions proposed to address challenges in aviation are software dependent technologies. Of the fifty-two specific technology solutions described in the Blueprint, forty-one depend, at least in part, on software for success. For thirty-five of these forty-one, software is not only critical to success, but also to human safety. That is, implementing the technology solutions will require using software in such a way that it may, if not specified, designed, and implemented properly, lead to fatal accidents. These results have at least two implications for the research based on the Blueprint: (1) knowledge about the current state-of-the-art and state-of-the-practice in software engineering and software system safety is essential, and (2) research into current unsolved problems in these software disciplines is also essential.

Automated Software Development Workstation (ASDW)

NASA Technical Reports Server (NTRS)

Fridge, Ernie

1990-01-01

Software development is a serious bottleneck in the construction of complex automated systems. An increase of the reuse of software designs and components has been viewed as a way to relieve this bottleneck. One approach to achieving software reusability is through the development and use of software parts composition systems. A software parts composition system is a software development environment comprised of a parts description language for modeling parts and their interfaces, a catalog of existing parts, a composition editor that aids a user in the specification of a new application from existing parts, and a code generator that takes a specification and generates an implementation of a new application in a target language. The Automated Software Development Workstation (ASDW) is an expert system shell that provides the capabilities required to develop and manipulate these software parts composition systems. The ASDW is now in Beta testing at the Johnson Space Center. Future work centers on responding to user feedback for capability and usability enhancement, expanding the scope of the software lifecycle that is covered, and in providing solutions to handling very large libraries of reusable components.

Maintaining the Health of Software Monitors

NASA Technical Reports Server (NTRS)

Person, Suzette; Rungta, Neha

2013-01-01

Software health management (SWHM) techniques complement the rigorous verification and validation processes that are applied to safety-critical systems prior to their deployment. These techniques are used to monitor deployed software in its execution environment, serving as the last line of defense against the effects of a critical fault. SWHM monitors use information from the specification and implementation of the monitored software to detect violations, predict possible failures, and help the system recover from faults. Changes to the monitored software, such as adding new functionality or fixing defects, therefore, have the potential to impact the correctness of both the monitored software and the SWHM monitor. In this work, we describe how the results of a software change impact analysis technique, Directed Incremental Symbolic Execution (DiSE), can be applied to monitored software to identify the potential impact of the changes on the SWHM monitor software. The results of DiSE can then be used by other analysis techniques, e.g., testing, debugging, to help preserve and improve the integrity of the SWHM monitor as the monitored software evolves.

Taking the Observatory to the Astronomer

NASA Astrophysics Data System (ADS)

Bisque, T. M.

1997-05-01

Since 1992, Software Bisque's Remote Astronomy Software has been used by the Mt. Wilson Institute to allow interactive control of a 24" telescope and digital camera via modem. Software Bisque now introduces a comparable, relatively low-cost observatory system that allows powerful, yet "user-friendly" telescope and CCD camera control via the Internet. Utilizing software developed for the Windows 95/NT operating systems, the system offers point-and-click access to comprehensive celestial databases, extremely accurate telescope pointing, rapid download of digital CCD images by one or many users and flexible image processing software for data reduction and analysis. Our presentation will describe how the power of the personal computer has been leveraged to provide professional-level tools to the amateur astronomer, and include a description of this system's software and hardware components. The system software includes TheSky Astronomy Software?, CCDSoft CCD Astronomy Software?, TPoint Telescope Pointing Analysis System? software, Orchestrate? and, optionally, the RealSky CDs. The system hardware includes the Paramount GT-1100? Robotic Telescope Mount, as well as third party CCD cameras, focusers and optical tube assemblies.

Software Defined Radio with Parallelized Software Architecture

NASA Technical Reports Server (NTRS)

Heckler, Greg

2013-01-01

This software implements software-defined radio procession over multicore, multi-CPU systems in a way that maximizes the use of CPU resources in the system. The software treats each processing step in either a communications or navigation modulator or demodulator system as an independent, threaded block. Each threaded block is defined with a programmable number of input or output buffers; these buffers are implemented using POSIX pipes. In addition, each threaded block is assigned a unique thread upon block installation. A modulator or demodulator system is built by assembly of the threaded blocks into a flow graph, which assembles the processing blocks to accomplish the desired signal processing. This software architecture allows the software to scale effortlessly between single CPU/single-core computers or multi-CPU/multi-core computers without recompilation. NASA spaceflight and ground communications systems currently rely exclusively on ASICs or FPGAs. This software allows low- and medium-bandwidth (100 bps to approx.50 Mbps) software defined radios to be designed and implemented solely in C/C++ software, while lowering development costs and facilitating reuse and extensibility.

Software Defined Radio with Parallelized Software Architecture

NASA Technical Reports Server (NTRS)

Heckler, Greg

2013-01-01

This software implements software-defined radio procession over multi-core, multi-CPU systems in a way that maximizes the use of CPU resources in the system. The software treats each processing step in either a communications or navigation modulator or demodulator system as an independent, threaded block. Each threaded block is defined with a programmable number of input or output buffers; these buffers are implemented using POSIX pipes. In addition, each threaded block is assigned a unique thread upon block installation. A modulator or demodulator system is built by assembly of the threaded blocks into a flow graph, which assembles the processing blocks to accomplish the desired signal processing. This software architecture allows the software to scale effortlessly between single CPU/single-core computers or multi-CPU/multi-core computers without recompilation. NASA spaceflight and ground communications systems currently rely exclusively on ASICs or FPGAs. This software allows low- and medium-bandwidth (100 bps to .50 Mbps) software defined radios to be designed and implemented solely in C/C++ software, while lowering development costs and facilitating reuse and extensibility.

Software for Improved Extraction of Data From Tape Storage

NASA Technical Reports Server (NTRS)

Cheng, Chiu-Fu

2003-01-01

A computer program has been written to replace the original software of Racal Storeplex Delta tape recorders, which are used at Stennis Space Center. The original software could be activated by a command- line interface only; the present software offers the option of a command-line or graphical user interface. The present software also offers the option of batch-file operation (activation by a file that contains command lines for operations performed consecutively). The present software is also more reliable than was the original software: The original software was plagued by several deficiencies that made it difficult to execute, modify, and test. In addition, when using the original software to extract data that had been recorded within specified intervals of time, the resolution with which one could control starting and stopping times was no finer than about a second (or, in some cases, several seconds). In contrast, the present software is capable of controlling playback times to within 1/100 second of times specified by the user, assuming that the tape-recorder clock is accurate to within 1/100 second.

Software for Improved Extraction of Data From Tape Storage

NASA Technical Reports Server (NTRS)

Cheng, Chiu-Fu

2002-01-01

A computer program has been written to replace the original software of Racal Storeplex Delta tape recorders, which are still used at Stennis Space Center but have been discontinued by the manufacturer. Whereas the original software could be activated by a command-line interface only, the present software offers the option of a command-line or graphical user interface. The present software also offers the option of batch-file operation (activation by a file that contains command lines for operations performed consecutively). The present software is also more reliable than was the original software: The original software was plagued by several deficiencies that made it difficult to execute, modify, and test. In addition, when using the original software to extract data that had been recorded within specified intervals of time, the resolution with which one could control starting and stopping times was no finer than about a second (or, in some cases, several seconds). In contrast, the present software is capable of controlling playback times to within 1/100 second of times specified by the user, assuming that the tape-recorder clock is accurate to within 1/100 second.

A Novel Rules Based Approach for Estimating Software Birthmark

PubMed Central

Binti Alias, Norma; Anwar, Sajid

2015-01-01

Software birthmark is a unique quality of software to detect software theft. Comparing birthmarks of software can tell us whether a program or software is a copy of another. Software theft and piracy are rapidly increasing problems of copying, stealing, and misusing the software without proper permission, as mentioned in the desired license agreement. The estimation of birthmark can play a key role in understanding the effectiveness of a birthmark. In this paper, a new technique is presented to evaluate and estimate software birthmark based on the two most sought-after properties of birthmarks, that is, credibility and resilience. For this purpose, the concept of soft computing such as probabilistic and fuzzy computing has been taken into account and fuzzy logic is used to estimate properties of birthmark. The proposed fuzzy rule based technique is validated through a case study and the results show that the technique is successful in assessing the specified properties of the birthmark, its resilience and credibility. This, in turn, shows how much effort will be required to detect the originality of the software based on its birthmark. PMID:25945363

Report: Scientific Software.

ERIC Educational Resources Information Center

Borman, Stuart A.

1985-01-01

Discusses various aspects of scientific software, including evaluation and selection of commercial software products; program exchanges, catalogs, and other information sources; major data analysis packages; statistics and chemometrics software; and artificial intelligence. (JN)