Implementing systematic requirements management in a large software development programme

This paper describes our experiences in introducing systematic requiremen s managem nt (RM) in a large development programme. The work was done as part of a general process improvement effort based on the Capability Maturity Model (CMM, see Ch.1.2). In our work it soon turned out that the main problems of introducing systematic requirements management are those of changing an organisation’s way of working, while the technical problems are secondary. In this paper, we describe · how the requirements management process was defined · how we went about introducing this process · the problems we encountered in doing so · what we did to overcome these problems · our ”lessons learned ” and future prospects. In contrast to papers on requirements engineering such as [RBE98], this paper is mainly concerned with the process of defining and introducing the RM process, with less emphasis on describing the RM process itself