11 research outputs found
The Interplay Among Software Volatility, Complexity and Development Outcomes: Evidence From Open Source Software
The study posits a mediating role of software complexity in the association between software volatility and different software development outcomes. Empirical tests using data from 326 open source software projects support such a partial mediating role of software complexity in the association between software volatility and development outcomes. Archival data is tested using an ordinary least squares mediated model. The paper uses productivity, defect count and development speed as dependent variables
Structural Changes Associated with Temporal Dispersion in Software Development Teams: Evidence from Open Source Software Project Teams
Collaboration structure and temporal dispersion (TD) in teams have been studied independently so far. This study uses Media Synchronicity Theory (MST) to derive hypotheses positing that the structure of collaboration networks in distributed teams changes when those teams are more temporally dispersed. The empirical test of hypotheses using ordinary least squares with archival data from 230 open source software (OSS) projects shows that the collaboration structure networks of those OSS teams that are more temporally dispersed are sparser and more centralised, and these associations are stronger in those teams exhibiting higher relative performance. Theoretical and practical consequences are discussed
Performance Implications of Stage-Wise Lead User Participation in Software Development Problem Solving
The problem-solving view of new product development sees the innovation process as a series of problem-solving loops broken down into three stages: problem detection, analysis and removal. We link this framework with lead user-driven innovation regarding software and show that effort by lead users (LUs) in each stage of the innovation problem solving process is, in varying degrees, associated with the source code’s quality, the productivity of the development process and the software’s popularity. We also test whether front loading the problem solving process is associated with development performance and we find that front loading is associated with increased code quality but decreased development productivity. Empirical tests are carried out with data from open source software projects. Findings potentially impact the design and management of online communities to help product development
Mitigating the Effects of Structural Complexity on Open Source Software Maintenance through Accountability
In this research, we investigate the relationships between structural complexity, accountability, and software maintenance performance in Open Source Software development projects. Additionally, we investigate the moderating role of monetary incentives on various relationships. We collected data on 5,000 bug reports from the SourceForge database and perceptual data from 181 open source software developers registered on SourceForge for model validation. Results support our hypotheses. The important implications of the results are discussed
Following the Sun: Temporal Dispersion and Performance in Open Source Software Project Teams
Dispersion in working teams has been addressed by extant research mostly in terms of the physical distance that separates team members. Recently, the focus has shifted toward an examination of a newer construct –temporal dispersion (TD). The study of TD so far has been constrained mostly to conceptual work. This study furthers the understanding of TD through an empirical investigation of its relationship with open source software (OSS) team performance. In this paper, hypotheses are developed based on coordination theory, and analyses are performed using data collected from multiple archival sources comprising 100 OSS development teams. Results indicate that TD positively affects development speed and quality and that software complexity moderates the relation between TD and software quality. Theoretical and practical implications are discussed. *Both authors contributed equally to the paper
Recommended from our members
Design and code traceability using a PDL metrics tool
This paper describes an analysis tool that extracts complexity metrics from Program Design Language (PDL) as contained in design specification documents. The tool analyzes pseudocode and computes token-count metrics of PDL complexity on a module by module basis. We used the tool to measure consistency within and across modules and for assessing traceability between PDL and the corresponding source code. In applications of the tool we were able to identify PDL descriptions that were too detailed, those lacking sufficient detail, identify inconsistent PDL descriptions, and measure traceability between the PDL description and the corresponding source code
Review of management information systems research: A management support emphasis
This article organizes, describes, and evaluates MIS research from 1981 through 1985 in order to provide an understanding of what constitutes MIS research and to indicate potentially rich areas for future research. The review emphasizes information systems research in support of management decision making as opposed, for example, to research into the management of information resources or the development of strategic information systems.Preliminary work includes developing a definition of MIS, adopting an organizing framework, and choosing journals for review. Once this foundation is laid, MIS research content and methodology up to 1980 are summarized based upon the findings of the First International Conference on Information Systems. Finally, MIS research from 1981 to 1985 is described and evaluated in terms of content and methodology.It was found that more progress has been made in identifying appropriate research questions than in answering those questions. Significant progress in generating answers may be made in the future due to a healthy shift in the choice of methodologies (shift from more speculative-conceptual to more theory-based/theory-generating empirical). However, progress toward developing a global notion (theory) of MIS seems relatively slow. This lack of progress seems to be a symptom of: - Lack of progress in defining the product of MIS (information). - Too much research focus upon what relationships exist instead of focusing upon why relationships exist. - Underlying problems in the natural sciences paradigm currently associated with MIS research.Peer Reviewedhttp://deepblue.lib.umich.edu/bitstream/2027.42/27465/1/0000506.pd
Recommended from our members
Web information systems: A study of maintenance, change and flexibility
This thesis was submitted for the degree of Doctor of Philosophy and awarded by Brunel University.Information Systems (IS’s) have provided organisations with huge efficiency gains and benefits over the years; however an outstanding problem that is yet to be successfully tackled is that of the troublesome maintenance phase. Consuming vast resources and thwarting business progression in a competitive global market place, system maintenance has been recognised as one of the key areas where IS is failing organisations. Organisations are too often faced with the dilemma of either replacement or the continual upkeep of an unwieldy system. The ability for IS’s to be able to adapt to exogenous influences is even more acute today than at any time in the past. This is due to IS’s namely, Web Information Systems (WIS’s) increasingly and continually having to accommodate the needs of organisations to interconnect with a plethora of additional systems as well as supporting evolving business models. The richness of the interconnectivity, functionalities and services WIS’s now offer are shaping social, cultural and economic behaviour on a truly global scale, making the maintenance of such systems and evermore pertinent issue. The growth and proliferation of WIS’s shows no sign of abating which leads to the conclusion that what some have termed as the ‘maintenance iceberg’ should not be ignored.
The quandary that commercial organisations face is typically driven by two key aspects; firstly, systems are built on the cultural premise of using fixed requirements, with not enough thought or attention being paid to systems abilities to deviate from these requirements. Secondly, systems do not generally cope well with adapting to unpredictable change arising from outside of the organisations environment. Over the recent past, different paradigms, approaches and methods have attempted to make software development more predictable, controllable and adaptable, however, the benefits of such measures in relation to the maintenance dilemma have been limited. The concept of flexible systems that are able to cope with such change in an efficient manner is currently an objective that few can claim to have realised successfully.
The primary focus of the thesis was to examine WIS post-development change in order to empirically substantiate and understand the nature of the maintenance phase. This was done with the intention to determine exactly ‘where’ and ‘how’ flexibility could be targeted to address these changes. This study uses an emergent analytical approach to identify and catalogue the nature of change occurring within WIS maintenance. However, the research framework design underwent a significant revision as the initial results indicated that a greater emphasis and refocus was required to achieve the research objective. To study WIS’s in an appropriate and detailed context, a single case study was conducted in a web development software house. In total the case study approach was used to collect empirical evidence from four projects that investigated post-development change requests in order to identify areas of the system susceptible to change. The maintenance phases of three WIS projects were considered in-depth, resulting in the collection of over four hundred change requests. The fourth project served as a validation case. The results are presented and the findings are used to identify key trends and characteristics that depict WIS maintenance change. The analytical information derived from the change requests is consolidated and shown diagrammatically for the key areas of change using profile models developed in this thesis. Based on the results, the thesis concludes and contributes to the ongoing debate that there is a discernable difference when considering WIS maintenance change compared to that of traditional IS maintenance. The detailed characteristics displayed in the profile models are then used to map specific flexibility criteria that ultimately are required to facilitate change. This is achieved using the Flexibility Matrix of Change (FMoC) tool which was developed within the remit of this research. This tool is a qualitative measurement scheme that aligns WIS maintenance changes to a reciprocal flexibility attribute. Thus, the wider aim of this thesis is to also expand the awareness of flexibility and its importance as a key component of the WIS lifecycle
Recommended from our members
A taxonomic analysis of typographic programming style
Program comprehension is important in program testing, debugging, and maintenance. Programming style impacts program understanding. However, there has not been any systematic identification of individual style factors and their contribution to program comprehension. In this thesis we present a programming style taxonomy composed of three classes: typographic (program layout and commenting), control structures, and information structures. Each class is further subdivided into macro (whole program or system) and micro (module or statement) subclasses. The taxonomy reveals many conflicting and unsubstantiated rules in collections of style rules from various publications on programming style. Further, it provides plausible explanations for some of the inconsistent results in programming style research. This thesis concentrates on the isolation of typographic style factors and analysis of their affects on programmer comprehension. General principles of good macro- and microtypographic style are identified and the "book paradigm," a mechanism for implementing the principles, is presented. Four experiments, involving both student and professional programmers, demonstrate that the macro- and micro-typographic principles incorporated into the book paradigm significantly improved program comprehension and maintenance. These results have direct application to programming language design and programming tools such as pretty-printers, language directed editors, style analyzers, and source code control systems