In Quest for Proper Mediums for Technology Transfer in Software Engineering

Successful transfer of the results of research projects into practice is of great interest to all project participants. It can be assumed that different transfer mediums fulfill technology transfer (TT) with different levels of success and that they are impaired by different kinds of barriers. The goal of this study is to gain a better understanding about the different mediums used for TT in software engineering, and to identify barriers weakening the success of the application of such mediums. We conducted an exploratory study implemented by a survey in the context of a German research project with a broad range of used mediums. The main reported barriers were low expectations of usefulness, no awareness of existence, lack of resources, or inadequateness in terms of outdated material or being in an immature state. We interpreted our results as symptoms of a lack of a dissemination plan in the project. Further work will be needed to explore the implications for the transfer of research results (knowledge and techniques) to practice.Comment: Proceedings of the International Conference on Empirical Software Engineering and Measurement, 201

Learning requirements engineering within an engineering ethos

An interest in educating software developers within an engineering ethos may not align well with the characteristics of the discipline, nor address the underlying concerns of software practitioners. Education for software development needs to focus on creativity, adaptability and the ability to transfer knowledge. A change in the way learning is undertaken in a core Software Engineering unit within a university's engineering program demonstrates one attempt to provide students with a solid foundation in subject matter while at the same time exposing them to these real-world characteristics. It provides students with a process to deal with problems within a metacognitive-rich framework that makes complexity apparent and lets students deal with it adaptively. The results indicate that, while the approach is appropriate, student-learning characteristics need to be investigated further, so that the two aspects of learning may be aligned more closely

SMEs: ERP or virtual collaboration teams

Small firms are indeed the engines of global economic growth. Small and Medium Enterprises (SMEs) play an important role to promote economic development. SMEs in the beginning of implementing new technologies always face capital shortage and need technological assistance. Available ERP systems do not fulfil the specific requirements of Small firms. SMEs has scarce resources and manpower therefore many SMEs don?t have the possessions to buy and operate an ERP System. On the other hand competition and competitiveness of SMEs have to be strengthened. This paper briefly reviews the existing perspectives on virtual teams and their effect on SMEs management. It also discusses the main characteristics of virtual teams and clarifies the differences aspects of virtual team application in SMEs. After outlining some of the main advantages and pitfall of such teams, it concentrates on comparing of ERP and virtual collaborative teams in SMEs. Finally, it provides evidence for the need of ?Software as a Service (SaaS)? where an application is hosted as a service provided to customers across the web for SMEs as an alternative of ERP. It has been widely argued that ERP disadvantage in SMEs such as administrative expenditure and cost, isolated structure, severe lack of software flexibility, insufficient support of SMEs business and high operating cost, lead SMEs to use virtual collaborative team which is net work base solution

Design science, engineering science and requirements engineering

For several decades there has been a debate in the computing sciences about the relative roles of design and empirical research, and about the contribution of design and research methodology to the relevance of research results. In this minitutorial we review this debate and compare it with evidence about the relation between design and research in the history of science and technology. Our review shows that research and design are separate but concurrent activities, and that relevance of research results depends on problem setting rather than on rigorous methods. We argue that rigorous scientific methods separate design from research, and we give simple model for how to do this in a problem-driven way

The development of service provider's BPO-IT framework

Purpose The decision to operate BPO-IT organisational model by a business process outsourcing (BPO) service provider has far reaching benefits. The purpose of this paper is to develop a service provider’s BPO-IT framework that provides in-house IT function (software) required to process client services. Design/methodology/approach The multi-case study adopted an exploratory sequential mixed method research approach. In the first instance, seven BPO service provider organisations were investigated in the qualitative phase and 156 in the quantitative phase, respectively. Findings The adoption of the developed framework indicates that it could reduce failures in BPO relationships through reduced turnaround time in processing client services, improved quality of service, reduced cost, improved client and provider’s competitiveness, and confidentiality of client operations. Outsourcing clients could lay the foundation for a successful relationship by adopting a selection process that could choose the right provider. Originality/value The paper reveals BPO-IT organisation’s operation towards in-house provision of software required to process client services. A research exploring BPO service providers from a top outsourcing destination like India could provide offshore outsourcing clients the information to move towards onshore outsourcing. </jats:sec

Case Studies in Industry: What We Have Learnt

Case study research has become an important research methodology for exploring phenomena in their natural contexts. Case studies have earned a distinct role in the empirical analysis of software engineering phenomena which are difficult to capture in isolation. Such phenomena often appear in the context of methods and development processes for which it is difficult to run large, controlled experiments as they usually have to reduce the scale in several respects and, hence, are detached from the reality of industrial software development. The other side of the medal is that the realistic socio-economic environments where we conduct case studies -- with real-life cases and realistic conditions -- also pose a plethora of practical challenges to planning and conducting case studies. In this experience report, we discuss such practical challenges and the lessons we learnt in conducting case studies in industry. Our goal is to help especially inexperienced researchers facing their first case studies in industry by increasing their awareness for typical obstacles they might face and practical ways to deal with those obstacles.Comment: Proceedings of the 4th International Workshop on Conducting Empirical Studies in Industry, co-located with ICSE, 201