Evaluating a Taxonomy of Handover Activities in One Swedish Company

Abstract

Abstract-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.

Evaluation of handover activities from the perspective of the system acquisition and front-end support

“…Here, we compared the activities in EM 3 : Handover Process Model with its industrial correspondences at VAST Pakistan. We did it by conducting a series of open-ended interviews and discussions using very simple questionnaires.…”

“…Finally, the internal validity is not relevant for our context due to the exploratory nature of our study. 3 : Handover Process Model categorizes the handover activities into seven different components [1]. As shown in Figure 2 Tables I-VII. The Management and Administration component describes the activities required for managing and administering the handover process.…”

“…These are [7][8] [9]. Currently, a handover process model being developed is EM 3 : Handover Process Model. EM 3 stand for Evolution and Maintenance Management Model [6].…”

“…EM 3 stand for Evolution and Maintenance Management Model [6]. Right now, it only contains a taxonomy of handover activities [1][2] [3].…”

“…In this paper, we evaluate the taxonomy activities as defined in EM 3 : Handover Process Model in an industrial setting. The context studied covers the handover of a software system from the vendor conducting system development, evolution and maintenance to an acquirer organization using the end product and conducting front-end support [4].…”