Detecting Coordination Problems in Collaborative Software Development Environments

Software development is rarely an individual effort and generally involves teams of developers collaborating to generate good reliable code. Among the software code there exist technical dependencies that arise from software components using services from other components. The different ways of assigning the design, development, and testing of these software modules to people can cause various coordination problems among them. We claim\ud that the collaboration of the developers, designers and testers must be related to and governed by the technical task structure. These collaboration practices are handled in what we call Socio-Technical Patterns.\ud The TESNA project (Technical Social Network Analysis) we report on in this paper addresses this issue. We propose a method and a tool that a project manager can use in order to detect the socio-technical coordination problems. We test the method and tool in a case study of a small and innovative software product company

TESNA: A Tool for Detecting Coordination Problems

Detecting problems in coordination can prove to be very difficult. This is especially true in large globally distributed environments where the Software Development can quickly go out of the Project Manager’s control. In this paper we outline a methodology to analyse the socio-technical coordination structures. We also show how this can be made easier with the help of a tool called TESNA that we have developed

ERP customization failure: Institutionalized accounting practices, power relations and market forces

Purpose: This paper examines a detailed case study of Enterprise Resource Planning (ERP) customization failure in an Egyptian state-owned company (AML) by drawing on new institutional sociology and its extensions. It explains how ERP customization failure is shaped by the interplay between institutionalised accounting practices, conflicting institutions, power relations and market forces. Methodology/Approach: The research methodology is based on using an intensive case study informed by new institutional sociology, especially the interplay between conflicting institutions, power relations and market forces. Data were collected from multiple sources, including interviews, observations, discussions and documentary analysis. Findings: The findings revealed that the inability of the ERP system to meet the core accounting requirements of the control authorities (the Central Agency for Accountability) was the explicit reason cited for the ERP failure. The externally imposed requirements of the Uniform Accounting System and planning budgets were used to resist both other institutional pressures (from the Holding Company for Engineering Industries) and market and competitive pressures. Research limitations: There are some limitations associated with the use of the case study method, including the inability to generalize from the findings of a single case study, some selectivity in the individuals interviewed, and the subjective interpretation by the researchers of the empirical data. Practical implications: The paper identifies that the interplay between institutional pressures, institutionalised accounting practices, intra-organizational power relations, and market forces contributed to the failure to embed ERP in a major company. Understanding such relationships can help other organisations to become more aware of the factors affecting successful implementation of new ERP systems and provide a better basis for planning the introduction of new technologies. Originality/value of paper: This paper draws on recent research and thinking in sociology, especially the development and application of new institutional sociology. In addition, the paper is concerned with ERP implementation and use and management accounting in a transitional economy, Egypt, and hence contributes to debate about exporting Western accounting practices and other technologies to countries with different cultures and different stages of economic and political development. Classification: Research paper/ case stud

Norm-based and commitment-driven agentification of the Internet of Things

There are no doubts that the Internet-of-Things (IoT) has conquered the ICT industry to the extent that many governments and organizations are already rolling out many anywhere,anytime online services that IoT sustains. However, like any emerging and disruptive technology, multiple obstacles are slowing down IoT practical adoption including the passive nature and privacy invasion of things. This paper examines how to empower things with necessary capabilities that would make them proactive and responsive. This means things can, for instance reach out to collaborative peers, (un)form dynamic communities when necessary, avoid malicious peers, and be “questioned” for their actions. To achieve such empowerment, this paper presents an approach for agentifying things using norms along with commitments that operationalize these norms. Both norms and commitments are specialized into social (i.e., application independent) and business (i.e., application dependent), respectively. Being proactive, things could violate commitments at run-time, which needs to be detected through monitoring. In this paper, thing agentification is illustrated with a case study about missing children and demonstrated with a testbed that uses different IoT-related technologies such as Eclipse Mosquitto broker and Message Queuing Telemetry Transport protocol. Some experiments conducted upon this testbed are also discussed

Applying inspection to object-oriented software

The benefits of the object-oriented paradigmare widely cited. At the same time, inspection is deemed to be the most cost-effective means of detecting defects in software products. Why then, is there no published experience, let alone quantitative data, on the application of inspection to object-oriented systems? We describe the facilities of the object-oriented paradigm and the issues that these raise when inspecting object-oriented code. Several problems are caused by the disparity between the static code structure and its dynamic runtime behaviour. The large number of small methods in object-oriented systems can also cause problems. We then go on to describe three areas which may help mitigate problems found. Firstly, the use of various programming methods may assist in making object-oriented code easier to inspect. Secondly, improved program documentation can help the inspector understand the code which is under inspection. Finally, tool support can help the inspector to analyse the dynamic behaviour of the code. We conclude that while both the object-oriented paradigm and inspection provide excellent benefits on their own, combining the two may be a difficult exercise, requiring extensive support if it is to be successful

The i* framework for goal-oriented modeling

The final publication is available at Springer via http://dx.doi.org/10.1007/978-3-319-39417-6i* is a widespread framework in the software engineering field that supports goal-oriented modeling of socio-technical systems and organizations. At its heart lies a language offering concepts such as actor, dependency, goal and decomposition. i* models resemble a network of interconnected, autonomous, collaborative and dependable strategic actors. Around this language, several analysis techniques have emerged, e.g. goal satisfaction analysis and metrics computation. In this work, we present a consolidated version of the i* language based on the most adopted versions of the language. We define the main constructs of the language and we articulate them in the form of a metamodel. Then, we implement this version and a concrete technique, goal satisfaction analys is based on goal propagation, using ADOxx. Throughout the chapter, we used an example based on open source software adoption to illustrate the concepts and test the implementation.Peer ReviewedPostprint (author's final draft

Scaling the Management of Extreme Programming Projects

XP is a code-oriented, light-weight software engineering methodology, suited merely for small-sized teams who develop software that relies on vague or rapidly changing requirements. Being very code-oriented, the discipline of systems engineering knows it as approach of incremental system change. In this contribution, we discuss the enhanced version of a concept on how to extend XP on large scale projects with hundreds of software engineers and programmers, respectively. Previous versions were already presented in [1] and [12]. The basic idea is to apply the "hierarchical approach", a management principle of reorganizing companies, as well as well-known moderation principles to XP project organization. We show similarities between software engineering methods and company reorganization processes and discuss how the elements of the hierarchical approach can improve XP. We provide guidelines on how to scale up XP to very large projects e.g. those common in telecommunication industry and IT technology consultancy firms by using moderation techniques.Comment: 7 pages, 4 figure

A framework for the successful implementation of food traceability systems in China

Implementation of food traceability systems in China faces many challenges due to the scale, diversity and complexity of China’s food supply chains. This study aims to identify critical success factors specific to the implementation of traceability systems in China. Twenty-seven critical success factors were identified in the literature. Interviews with managers at four food enterprises in a pre-study helped identify success criteria and five additional critical success factors. These critical success factors were tested through a survey of managers in eighty-three food companies. This study identifies six dimensions for critical success factors: laws, regulations and standards; government support; consumer knowledge and support; effective management and communication; top management and vendor support; and information and system quality