The Object Management Group's (OMG) Model Driven Architecture (MDA) strategy envisages a world where models play a more direct role in software production, being amenable to manipulation and transformation by machine. Model Driven Engineering (MDE) is wider in scope than MDA. MDE combines process and analysis with architecture. This article sets out a framework for model driven engineering, which can be used as a point of reference for activity in this area. It proposes an organisation of the modelling 'space' and how to locate models in that space. It discusses different kinds of mappings between models. It explains why process and architecture are tightly connected. It discusses the importance and nature of tools. It identifies the need for defining families of languages and transformations, and for developing techniques for generating/configuring tools from such definitions. It concludes with a call to align metamodelling with formal language engineering techniques.

Model Driven Engineering

Connections: New Ways of Working in the Networked Organization

Over the past decade, there has been increasing interest in the use of grounded theory in information systems research. Grounded theory is a qualitative research method that seeks to develop theory that is grounded in data systematically gathered and analysed. The purpose of this paper is to suggest guidelines for grounded theory studies in information systems. Our guidelines are based on a framework for theorizing in grounded theory studies that focuses on conceptualization and theory scope. Our hope is that the guidelines will help to raise the quality and aspirations of grounded theory studies in information systems.

Putting the ‘theory’ back into grounded theory: guidelines for grounded theory studies in information systems

Awareness and use of agile methods has grown rapidly among the information systems development (ISD) community in recent years. Like most previous methods, the development and promotion of these methods have been almost entirely driven by practitioners and consultants, with little participation from the research community during the early stages of evolution. While these methods are now the focus of more and more research efforts, most studies are still based on XP, Scrum, and other industry-driven foundations, with little or no conceptual studies of ISD agility in existence. As a result, this study proposes that there are a number of significant conceptual shortcomings with agile methods and the associated literature in its current state, including a lack of clarity, theoretical glue, parsimony, limited applicability, and naivety regarding the evolution of the concept of agility in fields outside systems development. Furthermore, this has significant implications for practitioners, rendering agile method comparison and many other activities very difficult, especially in instances such as distributed development and large teams that are not conducive to many of the commercial agile methods. This study develops a definition and formative taxonomy of agility in an ISD context, based on a structured literature review of agility across a number of disciplines, including manufacturing and management where the concept originated, matured, and has been applied and tested thoroughly over time. The application of the texonomy in practice is then demonstrated through a series of thought trials conducted in a large multinational organization. The intention is that the definition and taxonomy can then be used as a starting point to study ISD method agility regardless of whether the method is XP or Scrum, agile or traditional, complete or fragmented, out-of-the-box or in-house, used as is or tailored to suit the project context.

https://ulir.ul.ie/bitstream/handle/10344/574/L%201.pdf;sequence=2

Agility from First Principles: Reconstructing the Concept of Agility in Information Systems Development

Recognized as one of the trends of the 21st century, globalization of the world economies brought significant changes to nearly all industries, and in particular it includes software development. Many companies started global software engineering (GSE) to benefit from cheaper, faster and better development of software systems, products and services. However, empirical studies indicate that achieving these benefits is not an easy task. Here, we report our findings from investigating empirical evidence in GSE-related research literature. By conducting a systematic review we observe that the GSE field is still immature. The amount of empirical studies is relatively small. The majority of the studies represent problem-oriented reports focusing on different aspects of GSE management rather than in-depth analysis of solutions for example in terms of useful practices or techniques. Companies are still driven by cost reduction strategies, and at the same time, the most frequently discussed recommendations indicate a necessity of investments in travelling and socialization. Thus, at the same time as development goes global there is an ambition to minimize geographical, temporal and cultural separation. These are normally integral parts of cross-border collaboration. In summary, the systematic review results in several descriptive classifications of the papers on empirical studies in GSE and also reports on some best practices identified from literature.

/pdf/empirical-evidence-in-global-software-engineering-a-1bsjqubpg9.pdf

Empirical evidence in global software engineering: a systematic review

In this paper we present an overview of the field of distributed development of software systems and applications (DD). Based on an analysis of the published literature, we consider threats to communication, coordination and control in DD caused by Temporal Distance, Geographical Distance, and Socio-Cultural Distance. The analysis results in a more complete framework for reasoning in the DD domain which should be a useful resource for both academic researchers and practitioners.

https://ulir.ul.ie/bitstream/handle/10344/2347/2005_Agerfalk_framework.pdf?sequence=2

A framework for considering opportunities and threats in distributed software development

WHIPS-Volvo's Whiplash Protection Study

Sustainability of Open Source software communities beyond a fork: How and why has the LibreOffice project evolved?

As open source development's acceptance has increased, many companies have incorporated it into heterogeneous development, which creates products by combining software that's from many sources and built with many different processes. To be effective, heterogeneous development must bridge the gap between industrial and open source software (OSS) development practices. One aspect of this approach is inner-source development, which aims to deploy key aspects of OSS development within a limited scope - for example, a division, a company, or even a consortium. So, industrial software development must be extended with knowledge of how to cooperate in open source and inner-source communities. To compete successfully, software-intensive companies will need to adopt new forms of collaborative development involving open source software.

Commodification of Industrial Software: A Case for Open Source

Distributed development (DD) of software systems is an issue of increasing significance for organisations today, all the more so given the current trend towards globalisation. In this paper we present a reference model which can be used as a reference point for any company wishing to review their own DD scenario. This is particularised in two forms, one as an exemplar model for a global (GSD) development scenario and one as a particularisation of this for intra-national DD scenarios. By drawing from eight case-studies on DD, we present ten general strategies for successful DD together with our reference model which characterises an ideal DD situation.

/pdf/a-reference-model-for-successful-distributed-development-of-7ua5qoqndm.pdf

Björn Lundell

Papers

A framework for considering opportunities and threats in distributed software development

WHIPS-Volvo's Whiplash Protection Study

Sustainability of Open Source software communities beyond a fork: How and why has the LibreOffice project evolved?

Commodification of Industrial Software: A Case for Open Source

A reference model for successful Distributed Development of Software Systems