Introduction and assessment of the thematic hierarchy process method for prioritisation of requirements for software product lines
David Egan & Cristina Luca
What the paper says
This paper introduces a novel prioritisation method, the Thematic Hierarchy Process, designed to work with software release cycles in a matrix product development organisation with software product lines and multiple business lines. Three challenges are identified for prioritisation of requirements for software product lines with multiple business lines: scale, complexity and stakeholder discordance. The paper reviews current prioritisation methods and assesses their application to software product lines with multiple business lines with respect to these three challenges, and concludes that none of the existing methods can satisfactorily address all of them. In this paper we define the Thematic Hierarchy Process method, and provide a framework that can be applied by software product managers and researchers to their own software releases and requirements data. The Thematic Hierarchy Process was assessed using requirements data from Company A demonstrating strong alignment with real software release cycles, as shown by the high similarity scores of 0.87 and 0.91 in predicting release contents. Interviews carried out with domain experts to evaluate the Thematic Hierarchy Process to supplement the assessments also showed positive results. We conclude that the Thematic Hierarchy Process can satisfy the prioritisation challenges of scale, complexity and stakeholder discordance with software product lines with multiple business lines.
Evidence weight
Balanced mode · F 0.40 / M 0.15 / V 0.05 / R 0.40
| F · citation impact | 0.50 × 0.4 = 0.20 |
| M · momentum | 0.50 × 0.15 = 0.07 |
| V · venue signal | 0.50 × 0.05 = 0.03 |
| R · text relevance † | 0.50 × 0.4 = 0.20 |
† Text relevance is estimated at 0.50 on the detail page — for your query’s actual relevance score, open this paper from a search result.