Software release planning: an evolutionary and iterative approach
By D. Greer, G. Ruhe. Information and Software Technology, 2004
476 citations recorded by the source corpus.
Subfields: Information Systems, Software
View Paper: https://www.semanticscholar.org/paper/532ab8c21096ec181e0b9d4f39d04603f98ccce5
How researchers see this paper
The researchers whose trusted networks rank it highest, strongest advocate first. Every researcher gets a different order.
In Information Systems
- Mark Harman
- Phil McMinn
- Yuanyuan Zhang
- S. Afshin Mansouri
- Ali Selamat
- Philip Achimugu
- Roliana Ibrahim
- Mohd Naz'ri Mahrin
In Software
- Mark Harman
- Phil McMinn
- Yuanyuan Zhang
- S. Afshin Mansouri
- Ali Selamat
- Philip Achimugu
- Roliana Ibrahim
- Mohd Naz'ri Mahrin
Citations in the corpus
- A systematic literature review of software requirements prioritization research (2014, methodology): “Prominent machine learning techniques that suffer from this limitation are case base ranking [13]; interactive genetic algorithm prioritization technique [14]; Binary search tree [25] and EVOLVE [22].”
- The Current State and Future of Search Based Software Engineering (2007, methodology): “Greer and Ruhe proposed a GA-based approach for planning software releases [35].”
- Search Based Software Engineering: A Comprehensive Analysis and Review of Trends Techniques and Applications (2009, methodology): “Greer and Ruhe proposed a GA-based approach for planning software releases [200].”
- A Theoretical and Empirical Study of Search-Based Testing: Local, Global, and Hybrid Search (2010, background): “activities right across the software engineering life cycle, including requirements engineering [4], [19], [21], project planning and cost estimation [2], [3], [17] maintenance [10], [37], [46], refactoring [28], [50], [54], service-oriented software engineering [14], and quality assessment [11], [3”
- Search-based software engineering: Trends, techniques and applications (2012, unknown): “Greer [Greer and Ruhe 2004] also provided a method for optimally allocating requirements to increments, based on:”