Reliability factors in business software: volatility, requirements and end-users

Many business-oriented software applications are subject to frequent changes in requirements. This paper shows that, ceteris paribus, increases in the volatility of system requirements decrease the reliability of software. Further, systems that exhibit high volatility during the development phase are likely to have lower reliability during their operational phase. In addition to the typically higher volatility of requirements, end-users who specify the requirements of business-oriented systems are usually less technically oriented than people who specify the requirements of compilers, radar tracking systems or medical equipment. Hence, the characteristics of software reliability problems for business-oriented systems are likely to differ significantly from those of more technically oriented systems.

Infusing the use of seasonal climate forecasting into crop management practice in North East Australia using discussion support software

Seasonal climate forecasting offers potential for improving management of crop production risks in the cropping systems of NE Australia. But how is this capability best connected to management practice? Over the past decade, we have pursued participative systems approaches involving simulation-aided discussion with advisers and decision-makers. This has led to the development of discussion support software as a key vehicle for facilitating infusion of forecasting capability into practice. In this paper, we set out the basis of our approach, its implementation and preliminary evaluation. We outline the development of the discussion support software Whopper Cropper, which was designed for, and in close consultation with, public and private advisers. Whopper Cropper consists of a database of simulation output and a graphical user interface to generate analyses of risks associated with crop management options. The charts produced provide conversation pieces for advisers to use with their farmer clients in relation to the significant decisions they face. An example application, detail of the software development process and an initial survey of user needs are presented. We suggest that discussion support software is about moving beyond traditional notions of supply-driven decision support systems. Discussion support software is largely demand-driven and can compliment participatory action research programs by providing cost-effective general delivery of simulation-aided discussions about relevant management actions. The critical role of farm management advisers and dialogue among key players is highlighted. We argue that the discussion support concept, as exemplified by the software tool Whopper Cropper and the group processes surrounding it, provides an effective means to infuse innovations, like seasonal climate forecasting, into farming practice. Crown Copyright (C) 2002 Published by Elsevier Science Ltd. All rights reserved.

Portal do software p??blico brasileiro

O Portal do Software P??blico Brasileiro consolida-se como uma iniciativa que conseguiu criar um ambiente comum para compartilhar solu????es de software no setor p??blico, racionalizar a gest??o dos recursos de inform??tica, reaproveitar as solu????es de software existentes para diminuir custos e atividades redundantes, estabelecer parcerias e a????es cooperadas, refor??ar a pol??tica p??blica de estimular o uso de software livre e definir uma forma de licenciamento de software que sustente o compartilhamento de solu????es entre os ??rg??os do setor p??blico de acordo com as prerrogativas legais brasileiras e a Constitui????o Federal. Esta iniciativa trouxe como inova????o o compartilhamento de ???software p??blico???, que oficializou um novo modelo de licenciamento e de gest??o das solu????es desenvolvidas na administra????o p??blica, estabelecendo parceria entre diversos ??rg??os, institui????es, empresas e cidad??os, e hoje conta com mais de 100 mil participantes

Uso do software Estradas para determinação do espaçamento entre desaguadouros em estradas não pavimentadas do interior de Goiás

Estradas não pavimentadas correspondem a aproximadamente 90% da malha rodoviária brasileira. Estas, na maioria das vezes, são construídas sem a realização de estudos prévios, estando sujeitas a vários tipos de problemas. Um dos principais fatores de deterioração dessas vias é a ineficiência do sistema de drenagem. Neste trabalho simulou-se o espaçamento entre desaguadouros em estradas não pavimentadas, utilizando-se um software desenvolvido com base num modelo matemático de dimensionamento de sistemas de drenagem em estradas não pavimentadas. Utilizaram-se valores de erodibilidade, tensão crítica de cisalhamento e massa específica para diferentes solos de estradas, localizadas no Estado de Goiás. Simularam-se cenários considerando alterações na declividade (1, 5, 10 e 15%) e na seção transversal do canal com relações entre altura e largura de 1:1, 1:2, 1:5 e 1:10. O modelo respondeu sensivelmente às alterações na declividade, na seção transversal do canal e nas de resistência do solo. Os espaçamentos obtidos indicaram que, estradas com declividades inferiores a 5%, mesmo com elevados valores de erodibilidade permitiram espaçamentos viáveis em aspectos construtivos. No entanto, para as declividades de 10 e 15%, os espaçamentos, na maioria dos casos, apresentaram dimensões reduzidas, tornando-se impraticáveis, sendo necessário, nestes casos, proteção do canal ou alteração de suas características hidráulicas.

GUIsurfer: A Reverse Engineering Framework for User Interface Software

GUIsurfer: A Reverse Engineering Framework for User Interface Software

The role of coordination analysis in software integration projects

What sort of component coordination strategies emerge in a software integration process? How can such strategies be discovered and further analysed? How close are they to the coordination component of the envisaged architectural model which was supposed to guide the integration process? This paper introduces a framework in which such questions can be discussed and illustrates its use by describing part of a real case-study. The approach is based on a methodology which enables semi-automatic discovery of coordination patterns from source code, combining generalized slicing techniques and graph manipulation

Criminal Liability of Organizations, Corporations, Legal Persons, and Similar Entities on Law of Portuguese Cybercrime: A Brief Discussion on the Issue of Crimes of “False Information,” the “Damage on Other Programs or Computer Data,” the “Computer-Software Sabotage,” the “Illegitimate Access,” the “Unlawful Interception,” and “Illegitimate Reproduction of the Protected Program”

Abstract: in Portugal, and in much of the legal systems of Europe, «legal persons» are likely to be criminally responsibilities also for cybercrimes. Like for example the following crimes: «false information»; «damage on other programs or computer data»; «computer-software sabotage»; «illegitimate access»; «unlawful interception» and «illegitimate reproduction of protected program». However, in Portugal, have many exceptions. Exceptions to the «question of criminal liability» of «legal persons». Some «legal persons» can not be blamed for cybercrime. The legislature did not leave! These «legal persons» are v.g. the following («public entities»): legal persons under public law, which include the public business entities; entities utilities, regardless of ownership; or other legal persons exercising public powers. In other words, and again as an example, a Portuguese public university or a private concessionaire of a public service in Portugal, can not commit (in Portugal) any one of cybercrime pointed. Fair? Unfair. All laws should provide that all legal persons can commit cybercrimes. PS: resumo do artigo em inglês.