Change search
CiteExportLink to record
Permanent link

Direct link
Cite
Citation style
  • apa
  • harvard1
  • ieee
  • modern-language-association-8th-edition
  • vancouver
  • Other style
More styles
Language
  • de-DE
  • en-GB
  • en-US
  • fi-FI
  • nn-NO
  • nn-NB
  • sv-SE
  • Other locale
More languages
Output format
  • html
  • text
  • asciidoc
  • rtf
A Framework for Software System Handover
KTH, School of Information and Communication Technology (ICT), Software and Computer systems, SCS.
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.
Series
Trita-ICT-ECS AVH, ISSN 1653-6363 ; 13:12
National Category
Computer Science
Identifiers
URN: urn:nbn:se:kth:diva-122270ISBN: 978-91-7501-739-6 (print)OAI: oai:DiVA.org:kth-122270DiVA: diva2:621638
Public defence
2013-06-04, Sal D, Forum 100, Isafjordsgatan 39, Kista, Stockholm, 13:00 (English)
Opponent
Supervisors
Note

QC 20130516

Available from: 2013-05-16 Created: 2013-05-16 Last updated: 2013-05-16Bibliographically approved
List of papers
1. Core Handover Problems
Open this publication in new window or tab >>Core Handover Problems
2010 (English)In: PROFES '10 Proceedings of the 11th International Conference on Product Focused Software, ACM New York, NY, USA , 2010, 135-139 p.Conference paper, Published paper (Refereed)
Abstract [en]

Even if a handover process is a critical stage in the software lifecycle, little is known about the problems encountered when transferring a software system from development to maintenance. In this paper, we have elicited five core handover problems as faced by five IT organizations today. These are (1) insufficient system knowledge, (2) lack of domain knowledge, (3) insufficient communication, (4) inadequate documentation, and (5) difficulties in tracking changes.

Place, publisher, year, edition, pages
ACM New York, NY, USA, 2010
Keyword
Deployment, maintenance, documentation, pair programming, system knowledge
National Category
Software Engineering
Identifiers
urn:nbn:se:kth:diva-90212 (URN)10.1145/1961258.1961292 (DOI)2-s2.0-80053191611 (Scopus ID)978-1-4503-0281-4 (ISBN)
Conference
11th International Conference on Product Focused Software, PROFES 2010
Note
QC 20120223Available from: 2012-02-23 Created: 2012-02-20 Last updated: 2013-05-16Bibliographically approved
2. Taxonomy of Handover Activities
Open this publication in new window or tab >>Taxonomy of Handover Activities
2010 (English)In: PROFES '10 Proceedings of the 11th International Conference on Product Focused Software, ACM Press, 2010, 131-134 p.Conference paper, Published paper (Refereed)
Abstract [en]

Handover of software systems is a critical stage in the system lifecycle. Despite this, it is still an under researched area. In this paper, we have developed an initial taxonomy of activities for software handover. Our taxonomy consists of seven process components where each component clusters logically coherent activities. The process components are Management and Administration, Maintenance Environment, Version and Configuration Management, Deployment, Training, Documentation and, Maintainability Management.

Place, publisher, year, edition, pages
ACM Press, 2010
Keyword
Transition, testing, deployment, training, documentation
National Category
Software Engineering
Identifiers
urn:nbn:se:kth:diva-90208 (URN)10.1145/1961258.1961291 (DOI)2-s2.0-80053207004 (Scopus ID)978-1-4503-0281-4 (ISBN)
Conference
11th International Conference on Product Focused Software, PROFES 2010
Note
Qc 20120223Available from: 2012-02-23 Created: 2012-02-20 Last updated: 2013-05-16Bibliographically approved
3. Demarcating the Scope of a Handover Process
Open this publication in new window or tab >>Demarcating the Scope of a Handover Process
2010 (English)In: Fifth International Conference on Software Engineering Advances (ICSEA), 2010, IEEE Computer Society Digital Library, 2010, 244-251 p.Conference paper, Published paper (Refereed)
Abstract [en]

Despite the fact that a handover process is just as frequently performed as any development process, little is known about it. Still, it is regarded as one of the lifecycle processes that is not well explored and defined. In this paper, we study the handover process within eighteen companies with the purpose of demarcating its scope within software lifecycle. Our goal is to find out how industry understands handover process and how it places it within software lifecycle. As a result, we have identified seven different scope contexts for the handover process. We have also provided evidence of its wide lifecycle span and its overlap with development, predelivery and postdelivery maintenance processes.

Place, publisher, year, edition, pages
IEEE Computer Society Digital Library, 2010
Keyword
Transition, predelivery maintenance, transition, shift, rollout, deployment
National Category
Software Engineering
Identifiers
urn:nbn:se:kth:diva-90207 (URN)10.1109/ICSEA.2010.44 (DOI)2-s2.0-78649873071 (Scopus ID)978-0-7695-4144-0 (ISBN)978-1-4244-7788-3 (ISBN)
Conference
Fifth International Conference on Software Engineering Advances (ICSEA), 22-27 Aug. 2010, Nice
Note
© 2010 IEEE. Personal use of this material is permitted. Permission from IEEE must be obtained for all other uses, in any current or future media, including reprinting/republishing this material for advertising or promotional purposes, creating new collective works, for resale or redistribution to servers or lists, or reuse of any copyrighted component of this work in other works. Qc 20120223Available from: 2012-02-23 Created: 2012-02-20 Last updated: 2013-05-16Bibliographically approved
4. Evaluating A Taxonomy of Handover Activities in One Swedish Company
Open this publication in new window or tab >>Evaluating A Taxonomy of Handover Activities in One Swedish Company
2010 (English)In: 36th EUROMICRO Conference on Software Engineering and Advanced Applications (SEAA), 2010, IEEE Computer Society, 2010, 324-349 p.Conference paper, Published paper (Refereed)
Abstract [en]

Handing over a software system from development to maintenance is still an under-researched domain. The software community has a hazy insight into its constellation and inherent activities. In this paper, we have evaluated a preliminary version of a taxonomy of handover activities within one Swedish software company. The evaluation is conducted in an in-house handover context only. Despite this, our results provide evidence of its enormous complexity, variability and strong dependency on many other software engineering processes.

Place, publisher, year, edition, pages
IEEE Computer Society, 2010
Keyword
transtion, training, deployment, predelivery maintenance, maintainabilty, maintenance plan
National Category
Software Engineering
Identifiers
urn:nbn:se:kth:diva-90204 (URN)10.1109/SEAA.2010.41 (DOI)2-s2.0-78449294426 (Scopus ID)978-0-7695-4170-9 (ISBN)978-1-4244-7901-6 (ISBN)
Conference
36th EUROMICRO Conference on Software Engineering and Advanced Applications (SEAA), 2010
Note
© 2010 IEEE. Personal use of this material is permitted. Permission from IEEE must be obtained for all other uses, in any current or future media, including reprinting/republishing this material for advertising or promotional purposes, creating new collective works, for resale or redistribution to servers or lists, or reuse of any copyrighted component of this work in other works. QC 20120223Available from: 2012-02-23 Created: 2012-02-20 Last updated: 2013-05-16Bibliographically approved
5. Towards Taxonomizing of Core Software Handover Activities
Open this publication in new window or tab >>Towards Taxonomizing of Core Software Handover Activities
2010 (English)Conference paper, Published paper (Refereed)
Abstract [en]

Handover is an essential component in the total lifecycle management of software systems. Despite this, the software community has not agreed on its basic activities and concepts yet.  In this paper, we evaluate a preliminary version of EM3 taxonomy of handover activities. Our goal is to evaluate its credibility in an industrial setting and find feedback for creating a transition process.  The evaluation is made in the context of an in-house handover process.

Place, publisher, year, edition, pages
IEEE Computer Society, 2010
Keyword
Transition, Maintenance, Deployment
National Category
Software Engineering
Identifiers
urn:nbn:se:kth:diva-90217 (URN)
Conference
17th Asia Pacific Software Engineering Conference, APSEC 2010, Sydney, Australia, November 30 - December 3, 2010. IEEE Computer Society 2010
Note
QC 20120221Available from: 2012-02-21 Created: 2012-02-20 Last updated: 2013-05-16Bibliographically approved
6. Evaluation of Handover Activities from the Perspective of the System Acquisition and Front-End Support
Open this publication in new window or tab >>Evaluation of Handover Activities from the Perspective of the System Acquisition and Front-End Support
2010 (English)In: Computer Sciences and Convergence Information Technology (ICCIT), 2010 5th International Conference on, IEEE Computer Society Digital Library, 2010, 326-332 p.Conference paper, Published paper (Refereed)
Abstract [en]

Even if software handover is a critical process in the lifecycle of a software system, there is still very little research   done within its domain. In this paper, we evaluate the taxonomy of handover activities as defined in EM3: Handover Process Model. We do it in an industrial setting in a context where a software system is handed over from a vendor conducting system development, evolution and maintenance to an acquirer using the system and conducting front-end support. Our results show that the taxonomy is realistic in the context studied. However, it misses some important deployment and training activities.

Place, publisher, year, edition, pages
IEEE Computer Society Digital Library, 2010
Keyword
transition; deployment; acquisition; version and configuration management; documentation; maintainability
National Category
Software Engineering
Identifiers
urn:nbn:se:kth:diva-90201 (URN)10.1109/ICCIT.2010.5711079 (DOI)2-s2.0-79952669956 (Scopus ID)978-1-4244-8567-3 (ISBN)978-89-88678-30-5 (ISBN)
Conference
5th International Conference on Computer Sciences and Convergence Information Technology (ICCIT), Nov. 30 2010-Dec. 2, 2010, Seoul
Note
© 2010 IEEE. Personal use of this material is permitted. Permission from IEEE must be obtained for all other uses, in any current or future media, including reprinting/republishing this material for advertising or promotional purposes, creating new collective works, for resale or redistribution to servers or lists, or reuse of any copyrighted component of this work in other works. QC 20120223Available from: 2012-02-23 Created: 2012-02-20 Last updated: 2013-05-16Bibliographically approved
7. Walking a Software Handover Process
Open this publication in new window or tab >>Walking a Software Handover Process
2010 (English)Conference paper, Published 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
Identifiers
urn:nbn:se:kth:diva-90213 (URN)
Conference
17th Working Conference on Reverse Engineering, WCRE, 2010, Massachusetts, USA
Note
QC 20120221Available from: 2012-02-21 Created: 2012-02-20 Last updated: 2013-05-16Bibliographically approved
8. Identifying and Tackling Diversity of Management and Administration of a Handover Process
Open this publication in new window or tab >>Identifying and Tackling Diversity of Management and Administration of a Handover Process
2011 (English)In: Product-Focused Software Process Improvement: 12th International Conference, PROFES 2011, Torre Canne, Italy, June 20-22, 2011 Proceedings / [ed] Danilo Caivano, Markku Oivo, Maria Teresa Baldassarre, Giuseppe Visaggio, Springer Berlin/Heidelberg, 2011, 156-170 p.Conference paper, Published paper (Refereed)
Abstract [en]

Software handover is a de facto process in all software organizations. It is one of the most business critical and complex processes. It is also one of the most diverse processes, and thereby, one of the most difficult processes to define. Despite this, software handover is not well recognized within the academia. Right now, there are no software handover process models whatsoever although software organizations desperately need guidelines for how to perform this important and critical task. To aid them in defining their handover process models, we are in the process of creating Evolution and Maintenance Management Model (EM 3 ): Software Handover focusing on handover (alias transition) of a software system from developer to maintainer. In this paper, we evaluate one of the EM 3 components, Management and Administration (MA), addressing activities for planning and controlling the transition process, its schedule, budget and resources. We do it within 29 organizations. Our primary goal is to find out whether the component is realistic and whether it meets the needs and requirements of the software industry today. Using the feedback from the industry, we tackle process diversity using the C ontext- D riven P rocess Orchestration M ethod (CoDPOM).

Place, publisher, year, edition, pages
Springer Berlin/Heidelberg, 2011
Series
Lecture Notes in Computer Science, 6759
Keyword
Transition, transition plan, transition schedule, diversity
National Category
Software Engineering
Identifiers
urn:nbn:se:kth:diva-90189 (URN)10.1007/978-3-642-21843-9_14 (DOI)2-s2.0-79960276563 (Scopus ID)978-3-642-21842-2 (ISBN)
Conference
12th International Conference on Product- focused software process improvement, Torre Canne, Italy, June 20-22, 2011
Note

QC 20120223

Available from: 2012-02-23 Created: 2012-02-20 Last updated: 2013-05-16Bibliographically approved
9. Managing versions and configurations in a software handover process
Open this publication in new window or tab >>Managing versions and configurations in a software handover process
2012 (English)In: Proceedings - 2012 8th International Conference on Computing Technology and Information Management, ICCM 2012, 2012, 252-258 p.Conference paper, Published 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.

Keyword
change, control, software, transition
National Category
Computer and Information Science
Identifiers
urn:nbn:se:kth:diva-105463 (URN)2-s2.0-84866977585 (Scopus ID)978-898867867-1 (ISBN)
Conference
2012 8th International Conference on Computing Technology and Information Management, ICCM 2012, 24 April 2012 through 26 April 2012, Seoul
Note

QC 20121122

Available from: 2012-11-22 Created: 2012-11-21 Last updated: 2014-01-24Bibliographically approved
10. Evaluating the role of maintenance environment activities in software handover
Open this publication in new window or tab >>Evaluating the role of maintenance environment activities in software handover
2012 (English)In: Proceedings - 2012 8th International Conference on Computing Technology and Information Management, ICCM 2012, 2012, 230-237 p.Conference paper, Published paper (Refereed)
Abstract [en]

Evaluating and managing software maintenance environment is an important prerequisite for enabling system handover and for commencing maintenance. Despite this, there are no process models dealing with the subject. In this paper, we suggest activities required for managing software maintenance environment in the context of software handover and evaluate them in twenty nine organizations. Our results show that the activities are highly relevant and critical for the successful software handover. Their implementation however strongly varies depending on whether maintenance stays with development or whether it is performed by a separate maintainer.

Keyword
process, software, support, tranfer, transition
National Category
Computer and Information Science
Identifiers
urn:nbn:se:kth:diva-105459 (URN)2-s2.0-84866984638 (Scopus ID)978-898867867-1 (ISBN)
Conference
2012 8th International Conference on Computing Technology and Information Management, ICCM 2012, 24 April 2012 through 26 April 2012, Seoul
Note

QC 20121122

Available from: 2012-11-22 Created: 2012-11-21 Last updated: 2014-01-24Bibliographically approved
11. Evaluating a Training Process in a Software Handover Context
Open this publication in new window or tab >>Evaluating a Training Process in a Software Handover Context
2011 (English)In: 37th EUROMICRO Conference on Software Engineering and Advanced Applications, Aug. 30 2011-Sept. 2, 2011, Oulu, Finland, IEEE Computer Society Digital Library, 2011, 443-450 p.Conference paper, Published paper (Refereed)
Abstract [en]

Although there exist some people management process models related to the education and training of software engineers, there are no process models that are adapted to specific software engineering contexts and processes. In this paper, we suggest a set of education and training activities that are applicable in the context of a handover process. We then evaluate these activities within twenty organizations. Although our results reveal great diversity of using these activities, they still show that they are realistic and appropriately mirror the industrial status within a software handover context. 

Place, publisher, year, edition, pages
IEEE Computer Society Digital Library, 2011
Keyword
education, transition, knowledge, transfer
National Category
Software Engineering
Research subject
SRA - ICT
Identifiers
urn:nbn:se:kth:diva-90182 (URN)10.1109/SEAA.2011.68 (DOI)2-s2.0-82955227589 (Scopus ID)978-1-4577-1027-8 (ISBN)
Conference
37th EUROMICRO Conference on Software Engineering and Advanced Applications, Aug. 30 2011-Sept. 2 2011, Oulu, Finland
Note

© 2011 IEEE. Personal use of this material is permitted. Permission from IEEE must be obtained for all other uses, in any current or future media, including reprinting/republishing this material for advertising or promotional purposes, creating new collective works, for resale or redistribution to servers or lists, or reuse of any copyrighted component of this work in other works. QC 20120223

Available from: 2012-02-23 Created: 2012-02-20 Last updated: 2013-05-16Bibliographically approved
12. Analyzing deployment from the perspective of software handover and maintenance
Open this publication in new window or tab >>Analyzing deployment from the perspective of software handover and maintenance
2012 (English)In: Proceedings - 2012 8th International Conference on Computing Technology and Information Management, ICCM 2012, 2012, 244-251 p.Conference paper, Published paper (Refereed)
Abstract [en]

Deployment is an important constituent process in software handover and a critical prerequisite step to software maintenance. Despite this, there are no studies dealing with the role of deployment within software handover and maintenance. In this paper, we study deployment activities that are critical for a successful software handover and maintenance. We evaluate them in twenty software organizations. Our goal is to investigate their status and usefulness from the handover and maintenance perspective. Our results show that the deployment process, although it strongly varies in the organizations studied, adheres to our process model and provides good support for executing handover and for determining future maintenance effort.

Keyword
installation, processe, transition, Deployment process, Handover, Process model, Software organization, Information management, Computer software maintenance
National Category
Computer and Information Science
Identifiers
urn:nbn:se:kth:diva-105458 (URN)2-s2.0-84866998838 (Scopus ID)978-898867867-1 (ISBN)
Conference
2012 8th International Conference on Computing Technology and Information Management, ICCM 2012, 24 April 2012 through 26 April 2012, Seoul
Note

QC 20121122

Available from: 2012-11-22 Created: 2012-11-21 Last updated: 2014-01-24Bibliographically approved
13. Management of documentation and maintainability in the context of software handover
Open this publication in new window or tab >>Management of documentation and maintainability in the context of software handover
2012 (English)In: Proceedings - 2012 8th International Conference on Computing Technology and Information Management, ICCM 2012, 2012, 238-243 p.Conference paper, Published paper (Refereed)
Abstract [en]

It is critical that documentation and maintainability are defined and followed throughout the system lifecycle. If neglected, they may lead to poor system quality, costly evolution and maintenance and even to early retirement. In this paper, we study the management of documentation and maintainability in the context of software handover within thirty six organizations. Our goal is to find out about the industrial status of managing documentation and maintainability and explore knowledge that might be useful for developing a software handover process.

Keyword
development, knowledge, maintenance, manual, process, specification, transition, Information management, Specifications, Maintainability
National Category
Computer and Information Science
Identifiers
urn:nbn:se:kth:diva-105460 (URN)2-s2.0-84866972512 (Scopus ID)978-898867867-1 (ISBN)
Conference
2012 8th International Conference on Computing Technology and Information Management, ICCM 2012, 24 April 2012 through 26 April 2012, Seoul
Note

QC 20121122

Available from: 2012-11-22 Created: 2012-11-21 Last updated: 2014-01-24Bibliographically approved
14. Evaluating and Acting on Handover Framework in a special case of Project Parking
Open this publication in new window or tab >>Evaluating and Acting on Handover Framework in a special case of Project Parking
(English)In: Journal of Software Maintenance and Evolution, ISSN 1532-0618Article in journal (Other academic) Submitted
Abstract [en]

A well-defined handover process model is imperative and critical for succeeding with the transfer of a software system from one party to another. Despite this, there still do not exist any up-to date handover process models. Recently, however, we have developed EM3: Handover Framework aiding organizations in constructing their own handover process models. In this paper, we apply and evaluate EM3: Handover Framework in one Swedish software organization via participatory observation. Our goal is to examine the framework’s applicability and usefulness in a real-world industrial scenario. The handover process studied was of a self-to-self type and it was conducted in a project parking context. Our results show that our framework is fully applicable in an industrial handover setting. Almost all of its activities were relevant and fully applied in the context studied. 

National Category
Computer Systems
Identifiers
urn:nbn:se:kth:diva-122266 (URN)
Note

QS 2013

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

Open Access in DiVA

FSSH(1934 kB)11531 downloads
File information
File name FULLTEXT01.pdfFile size 1934 kBChecksum SHA-512
7c17761328352fa8916a57c3013cf01c35c315772c989b836423ddbde248e208c1812782a77cd77fa24d6d6b28040d093d204e933afe012ba10ac170999483e2
Type fulltextMimetype application/pdf

Search in DiVA

By author/editor
Khan, Ahmad Salman
By organisation
Software and Computer systems, SCS
Computer Science

Search outside of DiVA

GoogleGoogle Scholar
Total: 11531 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

isbn
urn-nbn

Altmetric score

isbn
urn-nbn
Total: 1816 hits
CiteExportLink to record
Permanent link

Direct link
Cite
Citation style
  • apa
  • harvard1
  • ieee
  • modern-language-association-8th-edition
  • vancouver
  • Other style
More styles
Language
  • de-DE
  • en-GB
  • en-US
  • fi-FI
  • nn-NO
  • nn-NB
  • sv-SE
  • Other locale
More languages
Output format
  • html
  • text
  • asciidoc
  • rtf