Large Number Of Software Projects Research Articles

Success Factors Importance Based on Software Project Organization Structure

The main aim of this paper is to identify critical success factors (CSFs) and investigate whether they are the same or not across different project organization structures. The organization structures under the study are: functional, project, and matrix. The study is based on a survey that was conducted on a large number of software projects in Jordan. To rank success factors (SFs) and identify critical ones, we use the importance index of SFs, which is calculated based on the likelihood and impact across different structures. For deeper analysis, we carry out statistical experiments with an ANOVA test and Spearman’s rank correlation test. Analysis results of an ANOVA test partially indicates that the values of the SF importance index are slightly different across the three organization structures. Moreover, the Spearman’s rank correlation test results show a high degree of correlation of the SF importance index between the function and project organization structures and a low degree of correlation between the function and matrix organization structures.

A bug finder refined by a large set of open-source projects

Abstract Context Static bug detection techniques are commonly used to automatically detect software bugs. The biggest obstacle to the wider adoption of static bug detection tools is false positives, i.e., reported bugs that developers do not have to act on. Objective The objective of this study is to reduce false positives resulting from static bug detection tools and to detect new bugs by exploring the effectiveness of a feedback-based bug detection rule design. Method We explored a large number of software projects and applied an iterative feedback-based process to design bug detection rules. The outcome of the process is a set of ten bug detection rules, which we used to build a feedback-based bug finder, FeeFin . Specifically, we manually examined 1622 patches to identify bugs and fix patterns, and implement bug detection rules. Then, we refined the rules by repeatedly using feedback from a large number of software projects. Results We applied FeeFin to the latest versions of the 1880 projects on GitHub to detect previously unknown bugs. FeeFin detected 98 new bugs, 63 of which have been reviewed by developers: 57 were confirmed as true bugs, and 9 were confirmed as false positives. In addition, we investigated the benefits of our FeeFin process in terms of new and improved bug patterns. We verified our bug patterns with four existing tools, namely PMD, FindBugs, Facebook Infer, and Google Error Prone, and found that our FeeFin process has the potential to identify new bug patterns and also to improve existing bug patterns. Conclusion Based on the results, we suggest that static bug detection tool designers identify new bug patterns by mining real-world patches from a large number of software projects. In addition, the FeeFin process is helpful in mitigating false positives generated from existing tools by refining their bug detection rules.

Enabling remote access to projects in a large collaborative environment

In the context of the Integrated Tokamak Modelling Task Force, a large number of software projects are made available to the task force members, including developers and end-users. This has been achieved through a combination of tools and technologies. The front-end is represented by a Java based portal system exposing a PHP project management system, GForge. These two applications are linked by a single sign-on mechanism, Shibboleth [1], and through secure HTTP [2] request rewriting, where appropriate. Furthermore, the underlying storage facility is an OpenAFS [3] distributed file system and the user base comes from both a network information server and an LDAP [4] directory. Security mechanisms are those of a distributed system, with multiple access points and protocols used for reading and writing data. The present paper presents the challenges of integrating these different technologies and programming languages into a single, working, application presented to its users as a web portal. Chaining of the tools is explored through the user perspective, with an in-depth overview of the background transitions between the various systems involved with regard to security requirements for the front-end nodes and the policies as seen by the users.

A New Approach to Software Development Fusion Process Model

There are several software process models that have been proposed and are based on task involved in developing and maintaining software product. The large number of software projects not meeting their expectation in terms of functionality, cost, delivery schedule and effective project management appears to be lacking. In this paper, we present a new software fusion process model, which depicts the essential phases of a software project from initiate stage until the product is retired. Fusion is component based software process model, where each component implements a problem solving model. This approach reduces the risk associated with cost and time, as these risks will be limited to a component only and ensure the overall quality of software system by considering the changing requirements of customer, risk assessment, identification, evaluation and composition of relative concerns at each phase of development process.