AboutSubmit my research

Methodology

Research articles · 2010

Techniques for managing changes to existing simulation models

Sally Edwards

Department for Work and Pensions (DWP), Model Development Unit, United Kingdom

Volume 3(2) Autumn 2010

Cite as: S. Edwards; 2010; Techniques for managing changes to existing simulation models; International Journal of Microsimulation; 3(2); 80–89. doi: 10.34196/ijm.00040

Abstract

In This paper provides guidance for managing the enhancement and maintenance of an existing microsimulation model. It focuses on techniques and practices that have been developed to maintain Pensim2; the Department for Work and Pensions (DWP) dynamic microsimulation model that simulates state and private pension entitlement. This guidance is appropriate for any type of model. Standard project management techniques and bespoke simulation model procedures are explained. This guidance is aimed at new modellers and project managers and is particularly relevant for models that are supported by a team, rather than an individual.

Models are generally used for many years after they are launched, so it is essential that strong maintenance procedures and project governance structures are put in place. Specifically, this paper includes guidance and examples of structured Change Control processes that are used to manage enhancements and fixes to the model. The Change Control process includes: defining requirements, estimation, design, code reviews, testing/validation, managing multiple modellers changing the same programs and the use of development checklists. Structured Release management guidance is also included in this paper

Jump to

This article contains 7 figures.

Figures

Figure 1. Change management and problem management process, as detailed in Section 4.2.
Figure 2. Sample change control register, as detailed in Section 4.2.
Figure 3. Sample change request, as detailed in Section 4.2.
Figure 4. Sample release control log, showing how each change is added to the model code and signed off one at a time.
Figure 5. Sample release checklist.
Figure 6. Sample spreadsheet used for software configuration management.
Figure 7. Sample high level plan, showing anticipated involvement from user teams.