Financial impact on the adoption of software validation tasks in the analysis phase: A business case David Allasi 1 , Abraham Dávila 2 1 Escuela de Posgrado, Pontificia Universidad Católica del Perú, Lima 32, Lima, Perú 2 Departamento de Ingeniería, Pontificia Universidad Católica del Perú, Lima 32, Lima, Perú {dallasi, abraham.davila}@pucp.edu.pe Abstract. Some information systems in a group of kind of organizations (for example government administrative organizations) have a critical role so they must achieve requirements in a rigorous way. However, it is not a common practice to use validation tasks, so these requirements usually do not correspond to the need. This study aims to analyze the financial impact on the adoption of practices related to validation in the phase of requirements management and analysis of software development. This study was carried out based on pre-test and post-test approach; in our case, we perform: first, an evaluation of a relevant and representative project; second, the organization introduces software validation tasks; and finally, an evaluation of a equivalence project with the improved process. We found that both project performed change during software life cycle. However, in the first one, the change was performed in the final stage, while the second project was made during the analysis stage. The requirements management and analysis process were improved and the results were observed during first stages and it is represents a 16% of saved. Keywords: validation, requirement management, software process improvement. 1 Introduction The most used criteria to measure the project successful are: the fulfillment of the objectives of times, cost, functionality and quality [1] [2] [3]. In particular, in software development project, the software functional requirements management is critical and it is compound of a set of activities that help to the work team to identify, control [4] and follow the requirements and it changes at any time. The well defined software functional requirements help to work team to get right scope of the project that must be implemented in the software [5] and this will allow to avoid over-costs by wrong implementation based on requirements incomplete, not understand, incorrect or out of scope [6]. The Chaos Report [7] points out that around of 29% of the projects are considered successful and in this report also show that around 6 of 10 causes why software development project fail are attributable to related to software requirements. In the Peruvian software industry, we identify the same problems descripted in Chaos report © Springer International Publishing AG 2018 J. Mejia et al. (eds.), Trends and Applications in Software Engineering, Advances in Intelligent Systems and Computing 688, https://doi.org/10.1007/978-3-319-69341-5_10