Towards guidelines for building a business case and gathering evidence of software reference architectures in industry

Background: Software reference architectures are becoming widely adopted by organizations that need to support the design and maintenance of software applications of a shared domain. For organizations that plan to adopt this architecture-centric approach, it becomes fundamental to know the return on investment and to understand how software reference architectures are designed, maintained, and used. Unfortunately, there is little evidence-based support to help organizations with these challenges. Methods: We have conducted action research in an industry-academia collaboration between the GESSI research group and everis, a multinational IT consulting firm based in Spain. Results: The results from such collaboration are being packaged in order to create guidelines that could be used in similar contexts as the one of everis. The main result of this paper is the construction of empirically-grounded guidelines that support organizations to decide on the adoption of software reference architectures and to gather evidence to improve RA-related practices. Conclusions: The created guidelines could be used by other organizations outside of our industry-academia collaboration. With this goal in mind, we describe the guidelines in detail for their use.Peer ReviewedPostprint (published version

Curriculum Guidelines for Undergraduate Programs in Data Science

The Park City Math Institute (PCMI) 2016 Summer Undergraduate Faculty Program met for the purpose of composing guidelines for undergraduate programs in Data Science. The group consisted of 25 undergraduate faculty from a variety of institutions in the U.S., primarily from the disciplines of mathematics, statistics and computer science. These guidelines are meant to provide some structure for institutions planning for or revising a major in Data Science

Comment développer la créativité des études utilisant la théorie enracinée ? Choix épistémologiques et stratégies pratiques dans la quête de créativité.

La théorie enracinée a été initialement développée pour proposer une alternative aux méthodes hypothético-déductives, qui formaient le courant majeur de la sociologie des années 1960, en visant à créer de nouvelles connaissances en se fondant sur les pratiques sociales. Face à l’ambition de vouloir créer de nouvelles connaissances au travers de l’utilisation de la théorie enracinée, de nombreux chercheurs mentionnent les difficultés inhérentes à cette méthode dans le développement de théories innovantes (Fendt & Sachs, 2008; Guillemette, 2006; Shalley, Gilson, & Blum, 2000). Cependant, la créativité reste une notion sous évaluée dans la littérature associée à la théorie enracinée. Les commentaires à propos de la créativité sont soit diffus(Charmaz, 2000 ; Glaser & Strauss, 1967 ; Strauss & Corbin, 1990) , soit limités (Dey, 1999 ; Douglas, 2003 ; Fendt & Sachs, 2008 ; Goulding, 2001 ; Locke, 2001 ; Wells, 1995). Ce papier cherche à clarifier dans quelles mesures la créativité joue un rôle dans le développement d’une théorie enracinée, ainsi que comment atteindre un certain niveau de créativité. Nous discutons d’abord les implications des choix épistémologiques dans les différentes versions de la théorie enracinée sur les potentialités de créativité dans le processus de recherche. Nous montrons que la place de la créativité diffère selon les approches utilisées : orthodoxe (Glaser and Strauss, 1967), pragmatique (Corbin & Strauss, 1990, 2008 ; Strauss & Corbin, 1990, 1998)ou constructiviste (Charmaz, 2000, 2006). Nous proposons trois stratégies de recherche permettant d’aider le chercheur dans sa quête de créativité. Nous nous appuyons sur près de dix années de pratique et d’enseignement de la théorie enracinée pour montrer comment les pratiques mentionnées peuvent aboutir à une meilleure créativité du chercheur. Nous ne proposons pas une liste exhaustive des techniques et stratégies mais mettons l’accent sur trois d’entre elles : le travail en groupe, les connaissances en art et la créativité in vivo.Grounded Theory (GT) methodology was originally proposed as an alternative to hypothetic deductive methods, aiming at creating new knowledge on the basis of the emergence of latent social patterns. While this ambition of creating fresh knowledge seems appropriate, there are difficulties inherent to the development of innovative and creative grounded theories (Fendt & Sachs, 2008 ; Guillemette, 2006 ; Shalley et al., 2000). However, creativity is an under evoked issue in the literature on GT. Mentions of creativity in GT literature is either diffuse (Charmaz, 2000 ; Glaser & Strauss, 1967 ; Strauss & Corbin, 1990) or scant (Dey, 1999 ; Douglas, 2003 ; Fendt & Sachs, 2008 ; Goulding, 2001 ; Locke, 2001 ; Wells, 1995). Our communication contributes to clarify to what extent creativity has a place in GT as well as how to enhance it. We first discuss the implications of epistemological choices underlying different versions of GT on the role of creativity in the research process. From early works of the pioneers (Glaser and Strauss, 1967), new GT versions have been developed, either focusing on the tactics to develop grounded theories in a practical way (Corbin & Strauss, 1990, 2008 ; Strauss & Corbin, 1990, 1998) or on its epistemological background (Charmaz, 2000, 2006). We show that the quest for creativity differs among these existing GT approaches. We also present three creativity-enhancing strategies to help researchers in their quest for creativity. We derive from our almost 10-year experience of developing GT as researchers and instructors to show how these strategies lead to creativity. We do not ambition to give an exhaustive set of techniques and strategies, but we focus on three of them, namely the collective work, the use of art knowledge, and in vivo creativity.méthode de recherche; épistémologie; théorie enracinée; créativité; sensibilité théorique; Management Research; Epistemology; Theoretical Sensitivity; Creativity; Grounded Theory;

Requirements Prioritization Based on Benefit and Cost Prediction: An Agenda for Future Research

In early phases of the software cycle, requirements prioritization necessarily relies on the specified requirements and on predictions of benefit and cost of individual requirements. This paper presents results of a systematic review of literature, which investigates how existing methods approach the problem of requirements prioritization based on benefit and cost. From this review, it derives a set of under-researched issues which warrant future efforts and sketches an agenda for future research in this area

A Survey on Economic-driven Evaluations of Information Technology

The economic-driven evaluation of information technology (IT) has become an important instrument in the management of IT projects. Numerous approaches have been developed to quantify the costs of an IT investment and its assumed profit, to evaluate its impact on business process performance, and to analyze the role of IT regarding the achievement of enterprise objectives. This paper discusses approaches for evaluating IT from an economic-driven perspective. Our comparison is based on a framework distinguishing between classification criteria and evaluation criteria. The former allow for the categorization of evaluation approaches based on their similarities and differences. The latter, by contrast, represent attributes that allow to evaluate the discussed approaches. Finally, we give an example of a typical economic-driven IT evaluation

What to Fix? Distinguishing between design and non-design rules in automated tools

Technical debt---design shortcuts taken to optimize for delivery speed---is a critical part of long-term software costs. Consequently, automatically detecting technical debt is a high priority for software practitioners. Software quality tool vendors have responded to this need by positioning their tools to detect and manage technical debt. While these tools bundle a number of rules, it is hard for users to understand which rules identify design issues, as opposed to syntactic quality. This is important, since previous studies have revealed the most significant technical debt is related to design issues. Other research has focused on comparing these tools on open source projects, but these comparisons have not looked at whether the rules were relevant to design. We conducted an empirical study using a structured categorization approach, and manually classify 466 software quality rules from three industry tools---CAST, SonarQube, and NDepend. We found that most of these rules were easily labeled as either not design (55%) or design (19%). The remainder (26%) resulted in disagreements among the labelers. Our results are a first step in formalizing a definition of a design rule, in order to support automatic detection.Comment: Long version of accepted short paper at International Conference on Software Architecture 2017 (Gothenburg, SE

Prochlo: Strong Privacy for Analytics in the Crowd

The large-scale monitoring of computer users' software activities has become commonplace, e.g., for application telemetry, error reporting, or demographic profiling. This paper describes a principled systems architecture---Encode, Shuffle, Analyze (ESA)---for performing such monitoring with high utility while also protecting user privacy. The ESA design, and its Prochlo implementation, are informed by our practical experiences with an existing, large deployment of privacy-preserving software monitoring. (cont.; see the paper

On Evaluating Commercial Cloud Services: A Systematic Review

Background: Cloud Computing is increasingly booming in industry with many competing providers and services. Accordingly, evaluation of commercial Cloud services is necessary. However, the existing evaluation studies are relatively chaotic. There exists tremendous confusion and gap between practices and theory about Cloud services evaluation. Aim: To facilitate relieving the aforementioned chaos, this work aims to synthesize the existing evaluation implementations to outline the state-of-the-practice and also identify research opportunities in Cloud services evaluation. Method: Based on a conceptual evaluation model comprising six steps, the Systematic Literature Review (SLR) method was employed to collect relevant evidence to investigate the Cloud services evaluation step by step. Results: This SLR identified 82 relevant evaluation studies. The overall data collected from these studies essentially represent the current practical landscape of implementing Cloud services evaluation, and in turn can be reused to facilitate future evaluation work. Conclusions: Evaluation of commercial Cloud services has become a world-wide research topic. Some of the findings of this SLR identify several research gaps in the area of Cloud services evaluation (e.g., the Elasticity and Security evaluation of commercial Cloud services could be a long-term challenge), while some other findings suggest the trend of applying commercial Cloud services (e.g., compared with PaaS, IaaS seems more suitable for customers and is particularly important in industry). This SLR study itself also confirms some previous experiences and reveals new Evidence-Based Software Engineering (EBSE) lessons