Abstract

In the elicitation of software requirements, one of the most uncertain aspects is knowing when to end the process. That is, when there is sufficient information from stakeholders and other sources to specify the requirements of the software system. There is no guidance that prescribes heuristics for this. The most relevant approach is the information capture progression model that aims to reflect how the elicitation session has developed in terms of the information that has been captured. In this article an analytical method is applied, based on patterns of the user experience, to evaluate the notation used in the model and identify aspects to improve in the future. The results are positive, giving an overall evaluation of 75%.