Abstract

The PORE method guides a software development team to acquire customer requirements and select COTS software products which satisfy these requirements. It supports the iterative process of requirements acquisition and COTS software evaluation/selection. PORE uses this iterative process of requirements acquisition and product evaluation/selection as its main novel approach. The method also describes the most fundamental processes undertaken during COTS software product procurement. MAP is a process meta-model for the design of requirements engineering methods. It proposes a process meta-model allowing to design the goals someone can have while applying a method, and to design the different strategies the method offers to achieve these goals. Constraints can also be specified to prevent from undertaking activities when they should not. When a process model specified with the MAP formalism is applied, the navigation through the different goals and strategies offered by the method is guided. When the user has selected the goal he wants to achieve and the strategy he wants to use to achieve it, the corresponding method tools and guidelines are proposed to him to support him in an active way. This paper presents an experience of modelling of the PORE method with the MAP formalism. This experiment shows that : (i) the MAP process meta-model is adapted to the formalisation of a complex method such as PORE, (ii) the MAP-based guidance of PORE is more flexible than it was originally in the approach, and (iii) implicit information of the PORE method were made explicit when formalising it with MAP.