data science

Perceived Effects of Pair Programming in an Industrial Context

Agile Software Development of Mobile Information Systems

A Comparative Case Study on the Impact of Test-Driven Development on Program Design and Test Coverage

Test-driven development (TDD) is a programming technique in which the tests are written prior to the source code. It is proposed that TDD is one of the most fundamental practices enabling the development of software in an agile and iterative manner. Both the literature and practice suggest that TDD practice yields several benefits. Essentially, it is claimed that TDD leads to an improved software design, which has a dramatic impact on the maintainability and further development of the system. The impact of TDD on program design has seldom come under the researchers' focus. This paper reports the results from a comparative case study of three software development projects where the effect of TDD on program design was measured using object-oriented metrics. The results show that the effect of TDD on program design was not as evident as expected, but the test coverage was significantly superior to iterative test-last development.

Perspectives on Global Software Development: special issue on PROFES 2007

The field of software engineering has evolved significantly over the past decades. It can be argued that software has become the vital element of any system or service. Interestingly, even in the field of automotive industry, 90% of recent innovations stem from software and electronics (ITEA2 2005). Ever since the classic NATO conference in 1968, however, software has been argued to be in some state of crisis. From the 1990s, the crisis has been labeled as a chronic one. It is quite evident that several attempts to improve the state of software industry have taken place with varying levels of success. Software process improvement approaches have been developed since many decades ago. The results have been impressive, on the one hand, but many problems still exist. As an example, the business impact of software process improvement endeavors has been difficult to pinpoint, several of the improvement initiatives appear to fall short of their goals, and overemphasis on comparing processes with fixed reference models may lead an organization astray regarding the product or service perspective. The Profes conference series was established in 1999 to provide a venue for industry and academia to present and discuss the shift from model-based improvement to a product-oriented perspective in the field of software engineering and software process improvement. This includes a context-oriented understanding of the process-product relationships. Recently, the focus in practice and, consequently, in research has been on viewing software development as a global endeavor rather than a local one. There are several reasons for this. To name but a few: The distribution of software development enables the optimum use of competence regardless of the geographical location. The large software-intensive organizations operate in the global space and market, which makes distribution a necessity rather than a choice. On the positive side, distribution enables the development of software and services close to the prominent market area. Despite these relatively clear advantages and 2 benefits, global software development has brought with it several challenges due to increased complexity and cultural as well as technology issues. These challenges are now being tackled by means of research taking place in Europe and elsewhere as witnessed by this special issue of Profes conference research papers. Profes Conference series was established at the end of European IST project called PROFES (PROduct Focused Software process improvement) for disseminating the research results of the project area to industry. The PROFES Consortium included …

A Case Study on the Impact of Refactoring on Quality and Productivity in an Agile Team

‘Lots done, more to do’: the current state of agile systems development research

Failure Prediction using the Cox Proportional Hazard Model

Crashes of software systems may have disruptive, and sometimes tragic effects on users. Being able to forecast such failures is extremely important, even when the failures are inevitable – at least recovery or rescue actions can be taken. In this paper we present a technique to predict the failure of running software systems. We propose to use log messages to predict failures running devices that read log files of running application and warns about the likely failure of the system; the prediction is based on the Cox Proportional Hazards (PH) model that has been applied successfully in various fields of research. We perform an initial validation of the proposed approach on real-world data.

Making the leap to a software platform strategy: Issues and challenges

Context: While there are many success stories of achieving high reuse and improved quality using software platforms, there is a need to investigate the issues and challenges organizations face when transitioning to a software platform strategy. Objective: This case study provides a comprehensive taxonomy of the challenges faced when a medium-scale organization decided to adopt software platforms. The study also reveals how new trends in software engineering (i.e. agile methods, distributed development, and flat management structures) interplayed with the chosen platform strategy. Method: We used an ethnographic approach to collect data by spending time at a medium-scale company in Scandinavia. We conducted 16in-depth interviews with representatives of eight different teams, three of which were working on three separate platforms. The collected data was analyzed using Grounded Theory. Results: The findings identify four classes of challenges, namely: business challenges, organizational challenges, technical challenges, and people challenges. The article explains how these findings can be used to help researchers and practitioners identify practical solutions and required tool support. Conclusion: The organization's decision to adopt a software platform strategy introduced a number of challenges. These challenges need to be understood and addressed in order to reap the benefits of reuse. Researchers need to further investigate issues such as supportive organizational structures for platform development, the role of agile methods in software platforms, tool support for testing and continuous integration in the platform context, and reuse recommendation systems.

Traverse the landscape of the mind by walking: an exploration of a new brainstorming practice

Group brainstorming is a well-known idea generation technique, which plays a key role in software development processes. Despite this, the relevant literature has had little to offer in advancing our understanding of the effectiveness of group brainstorming sessions. In this paper we present a research-in-progress on brainstorming while walking, which is a practice built upon the relationship between thinking and walking. The objective is to better understand how to conduct group brainstorming effectively. We compared two brainstorming sessions, one performed during a mountain walk, the other traditionally in a room. Three preliminary findings are obtained: walking can lead to an effective idea generation session; brainstorming while walking can encourage team members to participate in and contribute to the session in an equal manner; and it can help a team to maintain sustainable mental energy. Our study opens up an avenue for future exploration of effective group brainstorming practices.

A Web-based modeling tool for the SEMAT Essence theory of Software Engineering

As opposed to more mature subjects, software engineering lacks general theories that establish its foundations as a discipline. The Essence Theory of software engineering (Essence) has been proposed by the Software Engineering Methods and Theory (SEMAT) initiative. The goal of Essence is to develop a theoretically sound basis for software engineering practice and its wide adoption. However, Essence is far from reaching academic- and industry-wide adoption. The reasons for this include a struggle to foresee its utilization potential and a lack of tools for implementation. SEMAT Accelerator (SematAcc) is a Web-positioning tool for a software engineering endeavor, which implements the SEMAT’s Essence kernel. SematAcc permits the use of Essence, thus helping to understand it. The tool enables the teaching, adoption, and research of Essence in controlled experiments and case studies.

Foundations and Technological Landscape of Cloud Computing

The cloud computing paradigm has brought the benefits of utility computing to a global scale. It has gained paramount attention in recent years. Companies are seriously considering to adopt this new paradigm and expecting to receive significant benefits. In fact, the concept of cloud computing is not a revolution in terms of technology; it has been established based on the solid ground of virtualization, distributed system, and web services. To comprehend cloud computing, its foundations and technological landscape need to be adequately understood. This paper provides a comprehensive review on the building blocks of cloud computing and relevant technological aspects. It focuses on four key areas including architecture, virtualization, data management, and security issues.

Feature Usage Explorer: Usage Monitoring and Visualization Tool in HTML5 Based Applications

Feature Usage Explorer is a JavaScript library, which automatically detects features in HTML5 based applications and monitors their usage. The collected information can be visualized in a Feature Usage Diagram, which is automatically generated from an input json file. Currently, the users of Feature Usage Explorer have to design their own tool in order to generate the json file from collected usage information. This option remains viable when using the library in order not to constraint the user’s choice of preferred data storage. Feature Usage Explorer can be reused in any HTML5 based applications where an understanding of how users interact with the system is required (i.e. user experience and usability studies, human computer interaction field, or requirement prioritization area).