The Impact of In-House Software Development Practices on System Usability in the Social Security Funds in Tanzania

In-house software development is a critical phenomenon for the production of efficient and effective software in generating requisite job output. A few studies have devoted efforts towards establishing the impact of in-house software development on software. Therefore, this paper is an effort towards establishing the impact of in-house software development practices on system usability. In pursuit of this paper, a sample of a sample size of 169, at 95% confidence level, with margin error of 5% was drawn from bold software users, i.e. 300 employees who used the all software including those dealing with the main stream activities. A total of 102 respondents actually responded to the questionnaires. The Online Sample Calculator was used to draw the sample. Quantitative data were collected using semi-structured questionnaires and processed using the SPSS. Descriptive statistics were applied in the analysis. Findings of the study indicate that software development practices, specifically usability test and user involvement in software designing and development had an impact on determining software usability for in-house software. The paper concludes that software development practices shape the design of the software; hence influence usability of the software produced. Recommended is therefore that software usability test and user involvement in software designing and development be promoted for effective software production.

ZARP: An automated workflow for processing of RNA-seq data

RNA sequencing (RNA-seq) is a crucial technique for many scientific studies and multiple models, and software packages have been developed for the processing and analysis of such data. Given the plethora of available tools, choosing the most appropriate ones is a time-consuming process that requires an in-depth understanding of the data, as well as of the principles and parameters of each tool. In addition, packages designed for individual tasks are developed in different programming languages and have dependencies of various degrees of complexity, which renders their installation and execution challenging for users with limited computational expertise. The use of workflow languages and execution engines with support for virtualization and encapsulation options such as containers and Conda environments facilitates these tasks considerably. Computational workflows defined in those languages can be reliably shared with the scientific community, enhancing reusability, while improving reproducibility of results by making individual analysis steps more transparent. Here we present ZARP, a general purpose RNA-seq analysis workflow which builds on state-of-the-art software in the field to facilitate the analysis of RNA-seq data sets. ZARP is developed in the Snakemake workflow language using best software development practices. It can run locally or in a cluster environment, generating extensive reports not only of the data but also of the options utilized. It is built using modern technologies with the ultimate goal to reduce the hands-on time for bioinformaticians and non-expert users. ZARP is available under a permissive Open Source license and open to contributions by the scientific community.

A Theory of Coordination in Agile Software Development Projects

<p>Agile software development offers a deceptively simple means to organise complex multi-participant software development while achieving fast delivery of quality software, meeting customer requirements, and coping effectively with project change. There is little understanding, however, of how agile software development projects achieve effective coordination, a critical factor in successful software projects. Agile software development provides a unique set of practices for organising the work of software projects, and these practices seem to achieve effective project coordination. Therefore, this thesis takes a coordination perspective to explore how agile software projects work, and why they are effective. The outcome of this research is a theory of coordination in co-located agile software development projects. To build a coordination theory, evidence was drawn from a multi-case study following the positivist tradition in information systems. Three cases of agile software development contributed to the theory, along with one additional non-agile project that contributed contrasting evidence. The findings show that agile software development practices form a coordination strategy addressing three broad categories of dependency: knowledge dependencies, task dependencies, and resource dependencies. Most coordination is for managing requirement, expertise, historical, and task allocation dependencies; all forms of knowledge dependency. Also present are task dependencies, which include activity or business process dependencies, and resource dependencies, which include technical or entity dependencies. The theory of coordination explains that an agile coordination strategy consists of coordination mechanisms for synchronising the project team, for structuring their relations, and for boundary spanning. A coordination strategy contributes to coordination effectiveness, which has explicit and implicit components. The primary contribution of this theory is an explanation of how agile software development practices act together to achieve effective project coordination. The coordination strategy concept can be used to select practices from agile methods to ensure software projects achieve effective coordination. In addition, once operationalised in future work, the well-grounded theoretical concepts developed in this research will provide valuable tools for measuring the coordination effectiveness of agile method adoption and adaptation.</p>

A Theory of Coordination in Agile Software Development Projects

<p>Agile software development offers a deceptively simple means to organise complex multi-participant software development while achieving fast delivery of quality software, meeting customer requirements, and coping effectively with project change. There is little understanding, however, of how agile software development projects achieve effective coordination, a critical factor in successful software projects. Agile software development provides a unique set of practices for organising the work of software projects, and these practices seem to achieve effective project coordination. Therefore, this thesis takes a coordination perspective to explore how agile software projects work, and why they are effective. The outcome of this research is a theory of coordination in co-located agile software development projects. To build a coordination theory, evidence was drawn from a multi-case study following the positivist tradition in information systems. Three cases of agile software development contributed to the theory, along with one additional non-agile project that contributed contrasting evidence. The findings show that agile software development practices form a coordination strategy addressing three broad categories of dependency: knowledge dependencies, task dependencies, and resource dependencies. Most coordination is for managing requirement, expertise, historical, and task allocation dependencies; all forms of knowledge dependency. Also present are task dependencies, which include activity or business process dependencies, and resource dependencies, which include technical or entity dependencies. The theory of coordination explains that an agile coordination strategy consists of coordination mechanisms for synchronising the project team, for structuring their relations, and for boundary spanning. A coordination strategy contributes to coordination effectiveness, which has explicit and implicit components. The primary contribution of this theory is an explanation of how agile software development practices act together to achieve effective project coordination. The coordination strategy concept can be used to select practices from agile methods to ensure software projects achieve effective coordination. In addition, once operationalised in future work, the well-grounded theoretical concepts developed in this research will provide valuable tools for measuring the coordination effectiveness of agile method adoption and adaptation.</p>

IS IT TIME TO RETHINK OUR SOFTWARE DEVELOPMENT PRACTICES?

Covid-19 has proliferated across the nations with increasing number of cases each day. Thus, IT companies are now forced to operate from remote places with limited IT resources. However, these companies across the globe are on continuous touch with their software development and maintenance teams to ensure that they are productive and are able to deliver their services on the projects on time. We study the challenges faced by the IT companies at this juncture and the need for a different software development approach to complete the projects successfully even during such crisis. In this context, when the IT industries are making attempts to complete their on-going software projects and also to attend to some critical up-gradation in their previously delivered products, the challenges faced by them due to acute shortage of IT resources and transforming the working model from physical setup to remote platform needs to be studied. This calls for studying the existing software development models and practices and defining an alternate one that would suit the present IT scenario.

Translation of Activities in a Global Virtual Teams Software Development

. This study explores Global Virtual Software Teams’ development practices and try to demystify some of the misconceptions about global software development practices based on findings from the global virtual software teams’ experiment that was carried out at DePaul University from 2011 – 2018. The moments of translation from the perspective of actor-network theory (ANT) was employed in the data analysis, to examine how development approach was selected by the global virtual teams. One of the key findings from our research is that the success of a global software development project does not have a strong dependency on the development approach. While we agree that it is one of the key influencing factors, there are other equally strong factors for global virtual software team’s success.

Is It Time to Rethink Our Software Development Practices?

Covid-19 has proliferated across the nations with increasing number of cases each day. Thus, IT companies are now forced to operate from remote places with limited IT resources. However, these companies across the globe are on continuous touch with their software development and maintenance teams to ensure that they are productive and are able to deliver their services on the projects on time. We study the challenges faced by the IT companies at this juncture and the need for a different software development approach to complete the projects successfully even during such crisis. In this context, when the IT industries are making attempts to complete their on-going software projects and also to attend to some critical up-gradation in their previously delivered products, the challenges faced by them due to acute shortage of IT resources and transforming the working model from physical setup to remote platform needs to be studied. This calls for studying the existing software development models and practices and defining an alternate one that would suit the present IT scenario.

A Proposal for Sharing Software Process Provenance Data in Heterogeneous Environments

Software development practices have evolved, and new approaches have emerged, like Global Software Development (GSD). In addition, software development companies started to adopt data-driven practices in parts of their business. However, using and sharing software process data in a distributed and heterogeneous environment, like the GSD context, could be a challenging topic for many software engineers. In this paper, we present a proposal for sharing software process provenance data using a model that extends PROV, the PROV- SwProcess model. An example of applying this model using a process from the industry that deals with error handling and the implementation of new features in an Enterprise Resource Planning system is presented and explains how the model allows sharing software process provenance data, in addition to providing inferences and insights about these data.