A framework for understanding the factors influencing pair programming success

Pair programming is one of the more controversial aspects of several Agile system development methods, in particular eXtreme Programming (XP). Various studies have assessed factors that either drive the success or suggest advantages (and disadvantages) of pair programming. In this exploratory study the literature on pair programming is examined and factors distilled. These factors are then compared and contrasted with those discovered in our recent Delphi study of pair programming. Gallis et al. (2003) have proposed an initial framework aimed at providing a comprehensive identification of the major factors impacting team programming situations including pair programming. However, this study demonstrates that the framework should be extended to include an additional category of factors that relate to organizational matters. These factors will be further refined, and used to develop and empirically evaluate a conceptual model of pair programming (success)

Evolving information systems: meeting the ever-changing environment

To meet the demands of organizations and their ever-changing environment, information systems are required which are able to evolve to the same extent as organizations do. Such a system has to support changes in all time-and application-dependent aspects. In this paper, requirements and a conceptual framework for evolving information systems are presented. This framework includes an architecture for such systems and a revision of the traditional notion of update. Based on this evolutionary notion of update (recording, correction and forgetting) a state transition-oriented model on three levels of abstraction (event level, recording level, correction level) is introduced. Examples are provided to illustrate the conceptual framework for evolving information systems

Component identification through program slicing

This paper reports on the development of specific slicing techniques for functional programs and their use for the identification of possible coherent components from monolithic code. An associated tool is also introduced. This piece of research is part of a broader project on program understanding and re-engineering of legacy code supported by formal methodsFundação para a Ciência e a Tecnologia (FCT) - POSI/ICHS/44304/2002, in the context of the PURe project

Contextualisation of Data Flow Diagrams for security analysis

Data flow diagrams (DFDs) are popular for sketching systems for subsequent threat modelling. Their limited semantics make reasoning about them difficult, but enriching them endangers their simplicity and subsequent ease of take up. We present an approach for reasoning about tainted data flows in design-level DFDs by putting them in context with other complementary usability and requirements models. We illustrate our approach using a pilot study, where tainted data flows were identified without any augmentations to either the DFD or its complementary models

Affection not affliction: The role of emotions in information systems and organizational change

Most IS research in both the technical/rational and socio-technical traditions ignores or marginalizes the emotionally charged behaviours through which individuals engage in, and cope with the consequences of, IS practice and associated organizational change. Even within the small body of work that engages with emotions through particular conceptual efforts, affections are often conceived as a phenomenon to be eradicated – an affliction requiring a cure. In this paper, I argue that emotions are always implicated in our lived experiences, crucially influencing how we come to our beliefs about what is good or bad, right or wrong. I draw from the theoretical work of Michel Foucault to argue for elaborating current notions of IS innovation as a moral and political struggle in which individuals’ beliefs and feelings are constantly tested. Finally, I demonstrate these ideas by reference to a case study that had considerable emotional impact, and highlight the implications for future work