A software maintenance process is important for reducing maintenance effort and for improving software quality. In recent years, the Lean-Kanban approach has been widely applied in software practice including software maintenance. This approach minimizes Work-In-Progress (WIP), which is the number of items that are worked on by the team at any given time, thus improving the maintenance process. In this paper, we describe our simulation studies, which show that the Lean-Kanban approach can indeed help reduce the average time needed to complete maintenance requests. We develop a process simulator, which can simulate both existing maintenance processes that do not use a WIP limit, and that adopt it. We perform two case studies using real maintenance data collected from a Microsoft project and from a Chinese software firm. The main results of our study are two-fold. First, we demonstrate that it is possible to effectively model and simulate, using actors and events, a maintenance process where a flow of issues is processed through a sequence of activities, correctly reproducing key statistics of real data. Second, our results confirm that the WIP-limited process could be useful to increase the efficiency of software maintenance, as reported in previous industrial practices.
Simulation of Software Maintenance Process, with and without a Work-In-Process Limit
LUNESU, MARIA ILARIA;MARCHESI, MICHELE;
2013-01-01
Abstract
A software maintenance process is important for reducing maintenance effort and for improving software quality. In recent years, the Lean-Kanban approach has been widely applied in software practice including software maintenance. This approach minimizes Work-In-Progress (WIP), which is the number of items that are worked on by the team at any given time, thus improving the maintenance process. In this paper, we describe our simulation studies, which show that the Lean-Kanban approach can indeed help reduce the average time needed to complete maintenance requests. We develop a process simulator, which can simulate both existing maintenance processes that do not use a WIP limit, and that adopt it. We perform two case studies using real maintenance data collected from a Microsoft project and from a Chinese software firm. The main results of our study are two-fold. First, we demonstrate that it is possible to effectively model and simulate, using actors and events, a maintenance process where a flow of issues is processed through a sequence of activities, correctly reproducing key statistics of real data. Second, our results confirm that the WIP-limited process could be useful to increase the efficiency of software maintenance, as reported in previous industrial practices.
I documenti in IRIS sono protetti da copyright e tutti i diritti sono riservati, salvo diversa indicazione.
