63,720 research outputs found

    How Do You Feel, Developer? An Explanatory Theory of the Impact of Affects on Programming Performance

    Full text link
    Affects---emotions and moods---have an impact on cognitive activities and the working performance of individuals. Development tasks are undertaken through cognitive processes, yet software engineering research lacks theory on affects and their impact on software development activities. In this paper, we report on an interpretive study aimed at broadening our understanding of the psychology of programming in terms of the experience of affects while programming, and the impact of affects on programming performance. We conducted a qualitative interpretive study based on: face-to-face open-ended interviews, in-field observations, and e-mail exchanges. This enabled us to construct a novel explanatory theory of the impact of affects on development performance. The theory is explicated using an established taxonomy framework. The proposed theory builds upon the concepts of events, affects, attractors, focus, goals, and performance. Theoretical and practical implications are given.Comment: 24 pages, 2 figures. Postprin

    Operations capability, productivity and business performance: the moderating effect of environmental dynamism

    Get PDF
    Purpose – The purpose of this study is to investigate the relationships between operations capability, productivity and business performance in the context of environmental dynamism. Design/methodology/approach – A proposed conceptual framework grounded in the resourcebased view (RBV) and dynamic capability view (DCV) is analysed using archival data from 193 automakers in the UK. Findings – The results show that operations capability, as an important dynamic capability, has a significant positive effect on productivity, which in turn leads to improved business performance. The results also suggest that productivity fully mediates the relationship between operations capability and business performance, and that environmental dynamism significantly moderates the relationship between operations capability and productivity. Practical implications – The research findings provide practical insights that will help managers develop operations capability to gain greater productivity and business performance in a dynamic environment

    A Programming Environment Evaluation Methodology for Object-Oriented Systems

    Get PDF
    The object-oriented design strategy as both a problem decomposition and system development paradigm has made impressive inroads into the various areas of the computing sciences. Substantial development productivity improvements have been demonstrated in areas ranging from artificial intelligence to user interface design. However, there has been very little progress in the formal characterization of these productivity improvements and in the identification of the underlying cognitive mechanisms. The development and validation of models and metrics of this sort require large amounts of systematically-gathered structural and productivity data. There has, however, been a notable lack of systematically-gathered information on these development environments. A large part of this problem is attributable to the lack of a systematic programming environment evaluation methodology that is appropriate to the evaluation of object-oriented systems

    Comparison of Frontier Efficiency Methods: An Application to the U.S. Life Insurance Industry

    Get PDF
    The objective of this paper is to provide new information on the performance of efficiency estimation methods by applying a wide range of econometric and mathematical programming techniques to a sample of U.S. life insurers. Average efficiencies differ significantly across methods. The efficiency rankings are well-preserved among the econometric methods; but the rankings are less consistent between the econometric and mathematical programming methods and between the data envelopment analysis and free disposal hull techniques. Thus, the choice of estimation method can have a significant effect on the conclusions of an efficiency study. Most of the insurers in the sample display either increasing or decreasing returns to scale, and stock and mutual insurers are found to be equally efficient after controlling for firm size. Key words: Efficiency estimation, stochastic frontiers, data envelopment analysis, free disposal hull, life insurance industry, organizational form.

    Ada software productivity prototypes: A case study

    Get PDF
    A case study of the impact of Ada on a Command and Control project completed at the Jet Propulsion Laboratory (JPL) is given. The data for this study was collected as part of a general survey of software costs and productivity at JPL and other NASA sites. The task analyzed is a successful example of the use of rapid prototyping as applied to command and control for the U.S. Air Force and provides the U.S. Air Force Military Airlift Command with the ability to track aircraft, air crews and payloads worldwide. The task consists of a replicated database at several globally distributed sites. The local databases at each site can be updated within seconds after changes are entered at any one site. The system must be able to handle up to 400,000 activities per day. There are currently seven sites, each with a local area network of computers and a variety of user displays; the local area networks are tied together into a single wide area network. Using data obtained for eight modules, totaling approximately 500,000 source lines of code, researchers analyze the differences in productivities between subtasks. Factors considered are percentage of Ada used in coding, years of programmer experience, and the use of Ada tools and modern programming practices. The principle findings are the following. Productivity is very sensitive to programmer experience. The use of Ada software tools and the use of modern programming practices are important; without such use Ada is just a large complex language which can cause productivity to decrease. The impact of Ada on development effort phases is consistent with earlier reports at the project level but not at the module level
    corecore