Mapping Social Network to Software Architecture to Detect Structure Clashes in Agile Software Development

Research output: Chapter in Book/Report/Conference proceedingConference contributionAcademicpeer-review

2 Citations (Scopus)
198 Downloads (Pure)

Abstract

Software development is rarely an individual effort and generally involves teams of developers collaborating together in order to generate reliable code. Such collaborations require proper communication and regular coordination among the team members. In addition, coordination is required to sort out problems due to technical dependencies that exist when components of one part of the architecture requires services or data input from components of another part of the architecture. The dynamic allocation of the different tasks to people results in various socio-technical structure clashes (STSCs). These STSCs become more pronounced in an Agile Software Development environment and managerial intervention is constantly required to alleviate problems due to STSCs. In this paper we provide a method to detect these STSCs in a longitudinal fashion with the help of a tool that we are developing. We test this method in a case study of a software company and show how such structure clashes can be detected by analyzing the social network (along with the betweenness centrality index) in relation to the task dependencies due to the software architec.
Original languageUndefined
Title of host publicationElectronic Proceedings ECIS
Place of PublicationSankt Gallen
PublisherECIS
Pages-
Publication statusPublished - 6 Jun 2007
Event15th European Conference on Information Systems, ECIS 2007: Relevant rigour - Rigorous relevance - St. Gallen, Switzerland
Duration: 7 Jun 20079 Jun 2007
Conference number: 15

Conference

Conference15th European Conference on Information Systems, ECIS 2007
Abbreviated titleECIS
CountrySwitzerland
CitySt. Gallen
Period7/06/079/06/07

Keywords

  • Social Network
  • Software Architecture
  • Agile Software Development
  • IR-60285
  • METIS-243864

Cite this