Change search
ReferencesLink to record
Permanent link

Direct link
Walking a Software Handover Process
KTH, School of Information and Communication Technology (ICT), Communication: Services and Infrastucture, Software and Computer Systems, SCS. (SCS)
KTH, School of Information and Communication Technology (ICT), Communication: Services and Infrastucture, Software and Computer Systems, SCS. (SCS)ORCID iD: 0000-0002-1780-0683
2010 (English)Conference paper (Refereed)
Abstract [en]

To assure that process models correctly mirror the industrial reality, they need to be extracted and evaluated in many different contexts.  In this paper, we walk a handover process in a Pakistani company, called VAST Pakistanusing the EM3 taxonomy of activities as a roadmap. We walk the process by following VAST Pakistan’s software lifecycle phases and by placing EM3 activities on them. The context studied covers handover of a software system from the vendor conducting system development, evolution and maintenance to an acquirer organization being the end-user and front-end support provider. The study is made from the acquirer’s perspective. Our results show that the EM3 taxonomy of activities covers correct handover activities. Due to its specific context, however, the process studied did not utilize all the activities as defined in EM3. Their choice is strongly dependent on the handover process context under study. 

Place, publisher, year, edition, pages
IEEE Computer Society, 2010.
National Category
Software Engineering
URN: urn:nbn:se:kth:diva-90213OAI: diva2:504448
17th Working Conference on Reverse Engineering, WCRE, 2010, Massachusetts, USA
QC 20120221Available from: 2012-02-21 Created: 2012-02-20 Last updated: 2013-05-16Bibliographically 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

fulltext(115 kB)1816 downloads
File information
File name FULLTEXT01.pdfFile size 115 kBChecksum SHA-512
Type fulltextMimetype application/pdf

Other links

Search in DiVA

By author/editor
Ullah, KaleemKhan, Ahmad SalmanKajko-Mattsson, Mira
By organisation
Software and Computer Systems, SCS
Software Engineering

Search outside of DiVA

GoogleGoogle Scholar
Total: 1816 downloads
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: 130 hits
ReferencesLink to record
Permanent link

Direct link