Change search
ReferencesLink to record
Permanent link

Direct link
Managing versions and configurations in a software handover process
KTH, School of Information and Communication Technology (ICT), Software and Computer systems, SCS.
KTH, School of Information and Communication Technology (ICT), Software and Computer systems, SCS.ORCID iD: 0000-0002-1780-0683
2012 (English)In: Proceedings - 2012 8th International Conference on Computing Technology and Information Management, ICCM 2012, 2012, 252-258 p.Conference paper (Refereed)
Abstract [en]

Tracking and controlling versions and configurations of software systems is a challenging task. It becomes especially challenging during handover, a process during which a software system is transferred from a development to a maintenance team. Although there exist many process models dealing with version and configuration today, little has been done to study them from the perspective of a software system handover and its needs. In this paper, we have evaluated version and configuration activities from the handover perspective in 29 organizations. Our goal was to explore their relevancy within software handover. Our results shows that the version and configuration activities studied are highly relevant and critical in the software handover context.

Place, publisher, year, edition, pages
2012. 252-258 p.
Keyword [en]
change, control, software, transition
National Category
Computer and Information Science
URN: urn:nbn:se:kth:diva-105463ScopusID: 2-s2.0-84866977585ISBN: 978-898867867-1OAI: diva2:571390
2012 8th International Conference on Computing Technology and Information Management, ICCM 2012, 24 April 2012 through 26 April 2012, Seoul

QC 20121122

Available from: 2012-11-22 Created: 2012-11-21 Last updated: 2014-01-24Bibliographically approved
In thesis
1. A Framework for Software System Handover
Open this publication in new window or tab >>A Framework for Software System Handover
2013 (English)Doctoral thesis, comprehensive summary (Other academic)
Abstract [en]

A transfer of a software system from a party responsible for its development to a party responsible for its maintenance is referred to as software system handover or transition. It does not only include a transfer of a software system or system part, but also a transfer of all the knowledge, experience and responsibilities that are required for managing the system during a software system lifecycle. It is a complex process overarching many different processes such as development, testing, version and configuration management, deployment, and maintenance, just to mention a few.

Handover is a critical process in the software lifecycle and it is important that it is performed as smoothly as possible. It can become very expensive and protracted if the organizations are not well prepared for performing it. The productivity of the groups taking over the system and the quality of their outputs may be strongly dependent on how handover is performed. Overall, failing to transfer software systems may lead to loss of productivity, loss of maintainer credibility, loss of system and maintenance process quality, and sometimes, even loss of business. Therefore, a good handover process model is imperative and critical for planning for and managing transition and for alleviating many transition problems.

Regrettably, the issue of the software handover is still a strongly under-researched and neglected domain. There still do not exist any up-to date handover process models that designate important features of a handover process. So far, the research community has not paid much attention to this particular process domain. The published handover process models are either too old or they deal with handover on a very general level.

In this thesis, we suggest a framework for software system handover that provides a basis for creating handover process models. The framework is called EM3: Handover Framework and it is part of Evolution and Maintenance Management Model (EM3). The framework comprises six major parts: taxonomy of handover activities, handover contexts, handover types, handover roles, handover lifecycle roadmap, and handover guidelines. These parts may be combined in different ways for creating handover process models for specific handover contexts.

The research method used was of qualitative character including explorative case studies and participatory studies. It is based on data collected within 61 companies during which the theory about the handover process domain was explored, evolved and evaluated. The primary research tools used were semi-structured interviews and observation.

EM3: Handover Framework guides organizations in implementing their handover processes and in identifying problems and challenges they may face before, during and after the handover. Organizations can use it to conduct their own handover processes and researchers can further evaluate it in other industrial contexts, extend it, and/or use it for suggesting their own handover process models.

Place, publisher, year, edition, pages
Stockholm: KTH Royal Institute of Technology, 2013. 150 p.
Trita-ICT-ECS AVH, ISSN 1653-6363 ; 13:12
National Category
Computer Science
urn:nbn:se:kth:diva-122270 (URN)978-91-7501-739-6 (ISBN)
Public defence
2013-06-04, Sal D, Forum 100, Isafjordsgatan 39, Kista, Stockholm, 13:00 (English)

QC 20130516

Available from: 2013-05-16 Created: 2013-05-16 Last updated: 2013-05-16Bibliographically approved

Open Access in DiVA

No full text


Search in DiVA

By author/editor
Khan, Ahmad SalmanKajko-Mattsson, Mira
By organisation
Software and Computer systems, SCS
Computer and Information Science

Search outside of DiVA

GoogleGoogle Scholar
The number of downloads is the sum of all downloads of full texts. It may include eg previous versions that are now no longer available

Total: 41 hits
ReferencesLink to record
Permanent link

Direct link