191,052 research outputs found

    We Don't Need Another Hero? The Impact of "Heroes" on Software Development

    Full text link
    A software project has "Hero Developers" when 80% of contributions are delivered by 20% of the developers. Are such heroes a good idea? Are too many heroes bad for software quality? Is it better to have more/less heroes for different kinds of projects? To answer these questions, we studied 661 open source projects from Public open source software (OSS) Github and 171 projects from an Enterprise Github. We find that hero projects are very common. In fact, as projects grow in size, nearly all project become hero projects. These findings motivated us to look more closely at the effects of heroes on software development. Analysis shows that the frequency to close issues and bugs are not significantly affected by the presence of project type (Public or Enterprise). Similarly, the time needed to resolve an issue/bug/enhancement is not affected by heroes or project type. This is a surprising result since, before looking at the data, we expected that increasing heroes on a project will slow down howfast that project reacts to change. However, we do find a statistically significant association between heroes, project types, and enhancement resolution rates. Heroes do not affect enhancement resolution rates in Public projects. However, in Enterprise projects, the more heroes increase the rate at which project complete enhancements. In summary, our empirical results call for a revision of a long-held truism in software engineering. Software heroes are far more common and valuable than suggested by the literature, particularly for medium to large Enterprise developments. Organizations should reflect on better ways to find and retain more of these heroesComment: 8 pages + 1 references, Accepted to International conference on Software Engineering - Software Engineering in Practice, 201

    Complexity in the Context of Information Systems Project Management

    Get PDF
    Complexity is an inherent attribute of any project. The purpose of defining and documenting complexity is to enable a project team to foresee resulting challenges in a timely manner, and take steps to alleviate them.The main contribution of this article is to present a systematic view of complexity in project management by identifying its key attributes and classifying complexity by these attributes. A “complexity taxonomy” is developed and discussed within three levels: the product, the project and the external environment.Complexity types are described through simple real-life examples. Then a framework (tool) is developed for applying the notion of complexity as an early warning tool.The article is intended for researchers in complexity, project management, information systems, technology solutions and business management, and also for information specialists, project managers, program managers, financial staff and technology directors

    Investigating grid computing technologies for use with commercial simulation packages

    Get PDF
    As simulation experimentation in industry become more computationally demanding, grid computing can be seen as a promising technology that has the potential to bind together the computational resources needed to quickly execute such simulations. To investigate how this might be possible, this paper reviews the grid technologies that can be used together with commercial-off-the-shelf simulation packages (CSPs) used in industry. The paper identifies two specific forms of grid computing (Public Resource Computing and Enterprise-wide Desktop Grid Computing) and the middleware associated with them (BOINC and Condor) as being suitable for grid-enabling existing CSPs. It further proposes three different CSP-grid integration approaches and identifies one of them to be the most appropriate. It is hoped that this research will encourage simulation practitioners to consider grid computing as a technologically viable means of executing CSP-based experiments faster

    Strategic Predictors of Successful Enterprise Systems Deployment

    Get PDF
    Purpose The delivered wisdom to date has enterprise system purchase and implementation as one of the most hazardous projects any organization can undertake. The aim was to reduce this risk by both theoretically and empirically finding those key predictors of a successful enterprise system deployment. Design/methodology/approach A representative sample of 60 firms drawn from the Fortune 1000 that had recently (1999-2000) adopted enterprise resource planning (ERP) systems was used to test a model of adoption performance with significant results. Findings Leadership (social learning theory), business process re-engineering (change the company not the technology) and acquisition strategy (buy, do not make) were found to be significant predictors of adoption performance (final model R 2=43 percent, F=5.5, pp Originality/value The “four factor” model we validate is a robust predictor of ERP adoption success and can be used by any organization to audit plans and progress for this undertaking

    Strategic Predictors of Successful Enterprise Systems Deployment

    Get PDF
    Purpose The delivered wisdom to date has enterprise system purchase and implementation as one of the most hazardous projects any organization can undertake. The aim was to reduce this risk by both theoretically and empirically finding those key predictors of a successful enterprise system deployment. Design/methodology/approach A representative sample of 60 firms drawn from the Fortune 1000 that had recently (1999-2000) adopted enterprise resource planning (ERP) systems was used to test a model of adoption performance with significant results. Findings Leadership (social learning theory), business process re-engineering (change the company not the technology) and acquisition strategy (buy, do not make) were found to be significant predictors of adoption performance (final model R 2=43 percent, F=5.5, pp Originality/value The “four factor” model we validate is a robust predictor of ERP adoption success and can be used by any organization to audit plans and progress for this undertaking

    Construction informatics in Turkey: strategic role of ICT and future research directions

    Get PDF
    Construction Informatics deals with subjects ranging from strategic management of ICTs to interoperability and information integration in the construction industry. Studies on defining research directions for Construction Informatics have a history over 20 years. The recent studies in the area highlight the priority themes for Construction Informatics research as interoperability, collaboration support, intelligent sites and knowledge sharing. In parallel, today it is widely accepted in the Architecture/Engineering/Construction (AEC) industry that ICT is becoming a strategic asset for any organisation to deliver business improvement and achieve sustainable competitive advantage. However, traditionally the AEC industry has approached investing in ICT with a lack of strategic focus and low level of priority to the business. This paper presents a recent study from Turkey that is focused on two themes. The first theme investigates the strategic role of ICT implementations from an industrial perspective, and explores if organisations within the AEC industry view ICT as a strategic resource for their business practice. The second theme investigates the ‘perspective of academia’ in terms of future research directions of Construction Informatics. The results of the industrial study indicates that ICT is seen as a value-adding resource, but a shift towards the recognition of the importance of ICT in terms of value adding in winning work and achieving strategic competitive advantage is observed. On the other hand, ICT Training is found to be the theme of highest priority from the academia point of view

    SIMDAT

    No full text

    Federated Embedded Systems – a review of the literature in related fields

    Get PDF
    This report is concerned with the vision of smart interconnected objects, a vision that has attracted much attention lately. In this paper, embedded, interconnected, open, and heterogeneous control systems are in focus, formally referred to as Federated Embedded Systems. To place FES into a context, a review of some related research directions is presented. This review includes such concepts as systems of systems, cyber-physical systems, ubiquitous computing, internet of things, and multi-agent systems. Interestingly, the reviewed fields seem to overlap with each other in an increasing number of ways
    • 

    corecore