1. Pressman, R. S., & Maxim, B. R. (2020). Software Engineering: A Practitioner's Approach (9th ed.). McGraw-Hill. In Chapter 17, "Software Quality Assurance," Section 17.3.2 discusses statistical SQA and the application of Pareto analysis to identify the "vital few" defect causes that lead to the majority of errors (p. 469).
2. Naik, K., & Tripathy, P. (2008). Software Testing and Quality Assurance: Theory and Practice. Wiley. Chapter 16, "Software Quality," describes the seven basic quality tools. Section 16.4.1 specifically details the Pareto chart as a tool for prioritizing problems by arranging them in decreasing order of importance, often based on defect counts (pp. 458-459).
3. Ahmed, A. A. E., Abd El-Gawad, I. A., & El-Wahab, A. A. A. (2016). A proposed approach for analyzing software defects using Pareto principle. 2016 IEEE 7th Annual Information Technology, Electronics and Mobile Communication Conference (IEMCON), 1-6. This paper explicitly states, "Pareto chart is one of the most powerful quality tools. It is a graphical tool to map and rank business process problems from the most recurrent to the least frequent." (Section III.A). https://doi.org/10.1109/IEMCON.2016.7746331