Logging software upgrade

Vaisala weather instruments testing requires data logging to produce information for decisions making. Data logging is increasingly becoming database focused. Database logging was not usable and available to all users easily, for which reason this thesis aimed to bring database logging into internally used logging software. VB.NET based software was to be updated bringing database logging available to all users. The thesis and development of the software update used empirical research. Software principles were applied from theoretical literacy sources. Not all theoretical principles were applied to the internal software. Most software acceptance requirements were met, and software was evaluated acceptable to use. Especially its productivity was remarkable. However, its development should continue to bring all evaluation subjects to fully satisfying level. Some erroneous issues can escalate in wider use. The software was successfully updated, and it began a new era in its development lifecycle. Software was uploaded into GIT and should continue to be improved to better serve the company and its needs

Concurrency Control in Advanced Database Applications

Concurrency control has been thoroughly studied in the context of traditional database applications such as banking and airline reservations systems. There are relatively few studies, however, that address the concurrency control issues of advanced database applications such as CAD/CAM and software development environments. The concurrency control requirements in such applications are different from those in conventional database applications; in particular, there is a need to support non-serializable cooperation among users whose transactions are long-lived and interactive, and to integrate concurrency control mechanisms with version and configuration control. This paper outlines the characteristics of data and operations in some advanced database applications, discusses their concurrency control requirements, and surveys the mechanisms proposed to address these requirements

Concurrency Control in Advanced Database Applications

Concurrency control has been thoroughly studied in the context of traditional database applications such as banking and airline reservations systems. There are relatively few studies, however, that address the concurrency control issues of advanced database applications such as CAD/CAM and software development environments. The concurrency control requirements in such applications are different from those in conventional database applications; in particular, there is a need to support non-serializable cooperation among users whose transactions are long-lived and interactive, and to integrate concurrency control mechanisms with version and configuration control. This paper outlines the characteristics of data and operations in some advanced database applications, discusses their concurrency control requirements, and surveys the mechanisms proposed to address these requirements

Investigating requirements volatility during software development projects : an empirical study

University of Technology, Sydney. Faculty of Information Technology.Changes to software requirements are inevitable during the development process. Despite advances in software engineering over the past three decades, requirements changes are a source of project risk in software development, particularly when businesses and technologies are evolving rapidly. This so-called requirements volatility has attracted much attention, but its extent and consequences are not well understood. The research literature lacks empirical studies investigating requirements volatility, particularly its underlying causes and consequences, and there are no effective strategies to deal with the associated problems throughout software development. We address these issues with a long-term case study in an industrial software development setting to identify and characterise the causes of requirements volatility, its impacts on the software development process, and the strategies used by current system development practitioners to deal with requirements volatility problems. We analysed requirements change request data from two software project releases, and investigated the organisation's handling of requirements changes. Our data include the change request database, project documents, interviews, observations, and regular discussions with the key informants from the project members. We used a combination of qualitative and quantitative research techniques. We first present a critical review of the literature on requirements volatility issues, from which an analytic synthesis for a currently lacking comprehensive coverage of requirements volatility phenomena is derived. The review clarifies the terms used, the sources and adverse impacts of requirements volatility, and the strategies available to current software development teams. We also provide a detailed description of a repeatable research design that researchers and practitioners could use to conduct similar investigation of requirements volatility in any industry setting. We developed requirements change classifications from the change request data. Project members also classified requirements change requests using a card sorting technique. The resulting categories play a vital role in the empirical analysis of several aspects of requirements volatility. Its extent can be characterised by such classification attributes as the types of change (addition, deletion, and modification), reasons for change, and change origin. The classification is useful in analysing the cost of requirements change in terms of rework or effort required. Based on an empirical analysis using the proposed classification, effective strategies were defined to match organisational needs. The organisation was able to use these results to improve its change control process and its change request form, thereby improving management and reducing the impacts of requirements volatility

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

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

CREATING WEB MAPS OF FOREST RESTORATION PLOTS AT IRACAMBI ATLANTIC RAINFOREST RESEARCH CENTER, MINAS GERAIS, BRAZIL

The purpose of this report is to provide a detailed account, discussion, and analysis of my internship at Iracambi Atlantic Rainforest Research Center in Minas Gerais, Brazil during the summer of 2017, where I worked under the direction of GIS Supervisor Mr. Cliff Jones. The central focus of my work dealt with consolidating existing GIS data on the organization’s rainforest restoration effort into a single normalized database - based on the Atlantic Forest Restoration Pact, creating a structure for future forest restoration volunteers including enabling offline field collection using Collector for ArcGIS, then creating an ArcGIS Online web map based on this new single database. I also was educated on environmental issues related to mining in the area, including taking a guided tour of bauxite mining. This internship was a great environmental and cultural educational experience that afforded me the opportunity to work on environmental issues in the field, in a very unique setting. I developed GIS technical skills in web mapping, field data collection, and database management, using a number of new software tools. Following the requirements of the Master of Science in Geographic Information Science for Development & Environment program at Clark University, this report provides information on the purpose and structure of the organization, a detailed account of my internship, and a personal assessment of my internship

Requirements elicitation techniques for software development: a systematic review of literature

Introduction: Requirements elicitation (RE) is a difficult task in which there are issues related to information ambiguity, incomplete and inconsistent data. It seeks to discover and understand the users' problems and needs. The success of software development depends on the correct elicitation of requirements, and its quality is influenced by the techniques used.  This research aims to identify the RE techniques most cited in the literature of software development projects within this context. Method: a systematic literature review was carried out, which analyzed 61 articles from the Scopus database. Results: We identified the 10 RE techniques most cited in the literature. The ranking of these techniques showed that those obtained by stakeholders' groups' involvement were the least mentioned. Conclusions: the research identified the opportunity and relevance for developing a descriptive or confirmatory analysis of RE techniques based on the interaction between groups of users and members of the software development team.Introdução: A elicitação de requisitos (ER) é uma tarefa difícil na qual é necessário lidar com ambiguidade de informações, dados incompletos e inconsistentes. Ela busca descobrir e entender o real problema e as necessidades dos usuários. O sucesso do desenvolvimento de software depende da elicitação correta dos requisitos, e a qualidade deles é influenciada pelas técnicas usadas. Dentro deste contexto, o objetivo desta pesquisa é identificar as técnicas de ER mais citadas na literatura em projetos de desenvolvimento de software. Método: Foi realizada uma revisão sistemática da literatura, que analisou 61 artigos da base de dados Scopus. Resultados: Foram identificadas as 10 técnicas de ER mais citadas na literatura. A classificação dessas técnicas mostrou que aquelas obtidas pelo envolvimento de grupos de stakeholders foram as menos citadas. Conclusão: A pesquisa identificou a oportunidade e relevância para o desenvolvimento de pesquisa acadêmica descritiva ou confirmatória sobre técnicas de ER baseadas na interação entre grupos de usuários e membros da equipe de desenvolvimento de software

Software tools for sustainable water resources management: The GIS-integrated FREEWAT platform

This paper aims at presenting the open source and public domain FREEWAT platform capabilities for water resource management, including: (i) pre-processing modules to facilitate the preparation of input data, (ii) modelling tools for the analysis of several processes aimed at supporting water resource management, and (iii) post-processing tools to present results. The FREEWAT platform is based on open source solutions to perform an integrated coupling between the QGIS desktop software, surface and subsurface model engines, mostly based on fully distributed and numerically-based codes developed by the USGS, and other software applications, and the SpatiaLite spatial database. The development of the FREEWAT platform was supported by the main needs and priorities expressed by relevant stakeholders from the water sector involved in the early stage of the project. Extensive testing on the platform is still going on and training material and six User Manuals were prepared to disseminate its use as a standard software for managing surface/sub-surface water quantity and quality dynamics under demand-driven and supply-constrained conditions. The testing phase also includes demonstration of the platform capabilities on 14 case studies at European scale and beyond, to address specific water management issues. Nine of them are devoted to the application of EU water-related Directives, while the others address water management issues in the rural environment under the requirements of EU and/or national/local regulations. Beyond software testing, this demonstration is thought as an experiment on involving stakeholders in the formation of water plans yet during the technical phase of the analysis

Developing A New Decision Support System for University Student Recruitment

This paper investigates the practical issues surrounding the development and implementation of Decision Support Systems (DSS). The paper describes the traditional development approaches analyzing their drawbacks and introduces a new DSS development methodology. The proposed DSS methodology is based upon four modules; needs’ analysis, data warehouse (DW), knowledge discovery in database (KDD), and a DSS module. The proposed DSS methodology is applied to and evaluated using the admission and registration functions in Egyptian Universities. The paper investigates the organizational requirements that are required to underpin these functions in Egyptian Universities. These requirements have been identified following an in-depth survey of the recruitment process in the Egyptian Universities. This survey employed a multi-part admission and registration DSS questionnaire (ARDSSQ) to identify the required data sources together with the likely users and their information needs. The questionnaire was sent to senior managers within the Egyptian Universities (both private and government) with responsibility for student recruitment, in particular admission and registration. Further, access to a large database has allowed the evaluation of the practical suitability of using a DW structure and knowledge management tools within the decision making framework. 2000 records have been used to build and test the data mining techniques within the KDD process. The records were drawn from the Arab Academy for Science and Technology and Maritime Transport (AASTMT) students’ database (DB). Moreover, the paper has analyzed the key characteristics of DW and explored the advantages and disadvantages of such data structures. This evaluation has been used to build a DW for the Egyptian Universities that handle their admission and registration related archival data. The decision makers’ potential benefits of the DW within the student recruitment process will be explored. The design of the proposed admission and registration DSS (ARDSS) will be developed and tested using Cool: Gen (5.0) CASE tools by Computer Associates (CA), connected to a MS-SQL Server (6.5), in a Windows NT (4.0) environment. Crystal Reports (4.6) by Seagate will be used as a report generation tool. CLUSTAN Graphics (5.0) by CLUSTAN software will also be used as a clustering package. The ARDSS software could be adjusted for usage in different countries for the same purpose, it is also scalable to handle new decision situations and can be integrated with other systems