45,936 research outputs found

    Supporting Defect Causal Analysis in Practice with Cross-Company Data on Causes of Requirements Engineering Problems

    Full text link
    [Context] Defect Causal Analysis (DCA) represents an efficient practice to improve software processes. While knowledge on cause-effect relations is helpful to support DCA, collecting cause-effect data may require significant effort and time. [Goal] We propose and evaluate a new DCA approach that uses cross-company data to support the practical application of DCA. [Method] We collected cross-company data on causes of requirements engineering problems from 74 Brazilian organizations and built a Bayesian network. Our DCA approach uses the diagnostic inference of the Bayesian network to support DCA sessions. We evaluated our approach by applying a model for technology transfer to industry and conducted three consecutive evaluations: (i) in academia, (ii) with industry representatives of the Fraunhofer Project Center at UFBA, and (iii) in an industrial case study at the Brazilian National Development Bank (BNDES). [Results] We received positive feedback in all three evaluations and the cross-company data was considered helpful for determining main causes. [Conclusions] Our results strengthen our confidence in that supporting DCA with cross-company data is promising and should be further investigated.Comment: 10 pages, 8 figures, accepted for the 39th International Conference on Software Engineering (ICSE'17

    Goal Congruence, Trust and Organisational Culture: Strengthening Knowledge Links

    Get PDF
    Collaboration between organizations benefits from knowledge links -- a form of strategic alliance that gives organizations access to the skills and capabilities of their partner and opportunity to create new capabilities together. Using the example of alliances between two universities and SAP AG, the market leader in Enterprise Software, the paper suggests some management practices to improve goal congruence, trust and alignment between different organizational cultures. For example, face-to-face interactions are critical for building a close relationship over time. A theoretical framework of the five phases of partnership development and the three challenges faced by knowledge link partnerships is proposed, along with implications for management, universities and research

    TOWARDS ENHANCED E-COLLABORATION IN ACADEMIA A HOLISTIC MODEL FOR DEVELOPMENT OF E-COLLABORATION SOFTWARE

    Get PDF
    Henriksson, Aron. Neculau, Andrei. 2008. Towards Enhanced E-collaboration in Academia. A Holistic Model for Development E-collaboration Software. The Royal Institute of Technology, Stockholm, Sweden. Information and Communication Technology.E-collaboration is an inherently complex activity that encompasses many factors that supplement the pivotal technical elements. This paper investigates the various aspects of e-collaboration from an academic viewpoint, and reiterates the call for a holistic approach towards e-collaboration research and development. Moreover, the use of collaboration tools by IT students is surveyed, which substantiates the belief that e-collaboration needs to be further promoted in academia. We present a conceptual model that hopefully can provide some guidance for further research on e-collaboration and development of e-collaboration suites.E-collaboration, Academia, Requirements, Boundaries, Holistic

    Towards a lean model for production management of refurbishment projects, VTT Technology: 94

    Get PDF
    This is the Stage 3 Report for the ApRemodel project, which aims at improving processes for multi-occupancy retrofit by generating a lean model for project delivery. In this respect, a process-driven approach has been adopted to investigate what can be done to improve the way that retrofits projects are delivered. An initial literature review, focused on the management of refurbishment works, revealed that the research on this matter is scarce. There are plenty of studies related to the broad refurbishment area, however only a small number refer to the way that those construction projects are delivered. According to the literature, construction organisations have predominantly used traditional methods for managing the production of refurbishment projects. The problem is that those tools and techniques are not often appropriate to cope with the complex characteristics inherent to construction projects, especially in the case of refurbishments. Moreover, they have often not been based on a clear theoretical foundation. As a result, numerous types of waste have been identified in refurbishment projects such as waiting time, disruptions in performing tasks on site, rework, among others. This has led to unsatisfactory project performance in terms of low productivity, project delays, and cost overrun. The first step towards better production management in refurbishment projects is recognising the complexity of the sector in order to adopt the correct approach to cope with this specific scenario. In this respect, lean construction is identified as an appropriate way to deal with the complexity and uncertainty inherent in refurbishment projects, given that this management philosophy fully integrates the conversion, flow, and value views. This document builds on the findings from the literature review as well as evidence from case studies. Managerial practices based on lean construction principles have presented successful results in the management of complex projects. Case studies available in the literature report the feasibility and usefulness of this theoretical foundation. Moreover, the evidence from these studies show considerable potential for improving the management of refurbishment works. A list of methods, tools, and techniques are identified. This report may be used by construction refurbishment organisations and housing associations as a starting point for improving the efficiency in managing production of refurbishment projects. To this end, partnerships between industry and academia are strongly recommended. 4 Although the usefulness of lean principles in complex projects is already proved, further work is needed to check what practices are best for the respective refurbishment context, as well as identifying enablers and barriers for practical adoption. Furthermore, additional studies would be also necessary to better understand the extent to which the implementation of lean philosophy might influence performance of refurbishment projects. This report should be seen as work in progress with much more to learn, as detailed research work around the sustainable retrofit process in a lean way is further developed

    Report on the Second Workshop on Sustainable Software for Science: Practice and Experiences (WSSSPE2)

    Get PDF
    This technical report records and discusses the Second Workshop on Sustainable Software for Science: Practice and Experiences (WSSSPE2). The report includes a description of the alternative, experimental submission and review process, two workshop keynote presentations, a series of lightning talks, a discussion on sustainability, and five discussions from the topic areas of exploring sustainability; software development experiences; credit & incentives; reproducibility & reuse & sharing; and code testing & code review. For each topic, the report includes a list of tangible actions that were proposed and that would lead to potential change. The workshop recognized that reliance on scientific software is pervasive in all areas of world-leading research today. The workshop participants then proceeded to explore different perspectives on the concept of sustainability. Key enablers and barriers of sustainable scientific software were identified from their experiences. In addition, recommendations with new requirements such as software credit files and software prize frameworks were outlined for improving practices in sustainable software engineering. There was also broad consensus that formal training in software development or engineering was rare among the practitioners. Significant strides need to be made in building a sense of community via training in software and technical practices, on increasing their size and scope, and on better integrating them directly into graduate education programs. Finally, journals can define and publish policies to improve reproducibility, whereas reviewers can insist that authors provide sufficient information and access to data and software to allow them reproduce the results in the paper. Hence a list of criteria is compiled for journals to provide to reviewers so as to make it easier to review software submitted for publication as a “Software Paper.

    Summary of the First Workshop on Sustainable Software for Science: Practice and Experiences (WSSSPE1)

    Get PDF
    Challenges related to development, deployment, and maintenance of reusable software for science are becoming a growing concern. Many scientists’ research increasingly depends on the quality and availability of software upon which their works are built. To highlight some of these issues and share experiences, the First Workshop on Sustainable Software for Science: Practice and Experiences (WSSSPE1) was held in November 2013 in conjunction with the SC13 Conference. The workshop featured keynote presentations and a large number (54) of solicited extended abstracts that were grouped into three themes and presented via panels. A set of collaborative notes of the presentations and discussion was taken during the workshop. Unique perspectives were captured about issues such as comprehensive documentation, development and deployment practices, software licenses and career paths for developers. Attribution systems that account for evidence of software contribution and impact were also discussed. These include mechanisms such as Digital Object Identifiers, publication of “software papers”, and the use of online systems, for example source code repositories like GitHub. This paper summarizes the issues and shared experiences that were discussed, including cross-cutting issues and use cases. It joins a nascent literature seeking to understand what drives software work in science, and how it is impacted by the reward systems of science. These incentives can determine the extent to which developers are motivated to build software for the long-term, for the use of others, and whether to work collaboratively or separately. It also explores community building, leadership, and dynamics in relation to successful scientific software
    corecore