Towards a Capability Model for Release Planning of Software Intensive Systems

Release planning is an early product development activity concerned with deciding which features and quality improvements that should be pursued in product development projects, i.e., it is an acti ...

[1]  Günther Ruhe,et al.  The art and science of software release planning , 2005, IEEE Software.

[2]  K. Beck,et al.  Extreme Programming Explained , 2002 .

[3]  Tony Gorschek,et al.  Software quality attributes and trade-offs , 2005 .

[4]  Rick Kazman,et al.  Using Economic Considerations to Choose Among Architecture Design Alternatives , 2001 .

[5]  P. Krutchen,et al.  The Rational Unified Process: An Introduction , 2000 .

[6]  Rick Kazman,et al.  Making Architecture Design Decisions: An Economic Approach , 2002 .

[7]  Joachim Karlsson,et al.  Improved practical support for large-scale requirements prioritising , 1997, Requirements Engineering.

[8]  Anders Wall,et al.  Importance of Software Architecture during Release Planning , 2008, Seventh Working IEEE/IFIP Conference on Software Architecture (WICSA 2008).

[9]  Per Runeson,et al.  Checklists for Software Engineering Case Study Research , 2007, First International Symposium on Empirical Software Engineering and Measurement (ESEM 2007).

[10]  Ivar Jacobson,et al.  The Unified Software Development Process , 1999 .

[11]  Björn Regnell,et al.  Supporting Roadmapping of Quality Requirements , 2008, IEEE Software.

[12]  Claes Wohlin,et al.  Quest for a Silver Bullet: Creating Software Product Value through Requirements Selection , 2006, 32nd EUROMICRO Conference on Software Engineering and Advanced Applications (EUROMICRO'06).

[13]  M.M. Lehman,et al.  Programs, life cycles, and laws of software evolution , 1980, Proceedings of the IEEE.

[14]  Martin Höst,et al.  An analytical model for requirements selection quality evaluation in product software development , 2003, Proceedings. 11th IEEE International Requirements Engineering Conference, 2003..

[15]  Anders Wall,et al.  Towards a Capability Model for the Software Release Planning Process - Based on a Multiple Industrial Case Study , 2008, PROFES.

[16]  Joachim Karlsson,et al.  A Cost-Value Approach for Prioritizing Requirements , 1997, IEEE Softw..

[17]  Philippe Kruchten,et al.  The Rational Unified Process: An Introduction , 1998 .

[18]  Alexander L. Wolf,et al.  Acm Sigsoft Software Engineering Notes Vol 17 No 4 Foundations for the Study of Software Architecture , 2022 .

[19]  Anders Wall,et al.  A Method for Balancing Short- and Long-Term Investments: Quality vs. Features , 2008, 2008 34th Euromicro Conference Software Engineering and Advanced Applications.

[20]  Paul Clements,et al.  ATAM: Method for Architecture Evaluation , 2000 .

[21]  Claes Wohlin,et al.  An evaluation of methods for prioritizing software requirements , 1998, Inf. Softw. Technol..

[22]  Philippe Kruchten,et al.  The Rational Unified Process: An Introduction, Second Edition , 2000 .

[23]  Anas N. Al-Rabadi,et al.  A comparison of modified reconstructability analysis and Ashenhurst‐Curtis decomposition of Boolean functions , 2004 .

[24]  Gary DeGregorio,et al.  Technology management via a set of dynamically linked roadmaps , 2000, Proceedings of the 2000 IEEE Engineering Management Society. EMS - 2000 (Cat. No.00CH37139).

[25]  Marjo Kauppinen,et al.  Linking the business view to requirements engineering: long-term product planning by roadmapping , 2005, 13th IEEE International Conference on Requirements Engineering (RE'05).

[26]  Kari Smolander,et al.  Challenges of Knowledge and Collaboration in Roadmapping , 2006, 2006 International Workshop on Software Product Management (IWSPM'06 - RE'06 Workshop).

[27]  James M. Bieman,et al.  The FreeBSD project: a replication case study of open source development , 2005, IEEE Transactions on Software Engineering.

[28]  Mike Robey,et al.  A Case Study: GQM and TSP in a Software Engineering Capstone Project , 2005, 18th Conference on Software Engineering Education & Training (CSEET'05).

[29]  Markus Lindgren,et al.  Measurement and simulation based techniques for real-time systems analysis , 2000 .

[30]  Ho-Won Jung,et al.  Optimizing Value and Cost in Requirements Analysis , 1998, IEEE Softw..

[31]  Eila Niemelä,et al.  A Survey on Software Architecture Analysis Methods , 2002, IEEE Trans. Software Eng..

[32]  Alan M. Davis,et al.  The Art of Requirements Triage , 2003, Computer.

[33]  Günther Ruhe,et al.  Supporting Software Release Planning Decisions for Evolving Systems , 2005, 29th Annual IEEE/NASA Software Engineering Workshop.

[34]  Paul Clements,et al.  Software architecture in practice , 1999, SEI series in software engineering.

[35]  Pekka Abrahamsson,et al.  Integrating agile software development and software process improvement: a longitudinal case study , 2005, 2005 International Symposium on Empirical Software Engineering, 2005..

[36]  Kent L. Beck,et al.  Extreme programming explained - embrace change , 1990 .

[37]  Martin Fowler,et al.  Refactoring - Improving the Design of Existing Code , 1999, Addison Wesley object technology series.

[38]  Barry W. Boehm,et al.  Get Ready for Agile Methods, with Care , 2002, Computer.

[39]  Günther Ruhe,et al.  Software release planning for evolving systems , 2005, Innovations in Systems and Software Engineering.

[40]  David Lorge Parnas,et al.  Software aging , 1994, Proceedings of 16th International Conference on Software Engineering.

[41]  A. Susi,et al.  An Empirical Study to Compare the Accuracy of AHP and CBRanking Techniques for Requirements Prioritization , 2007, 2007 Fifth International Workshop on Comparative Evaluation in Requirements Engineering.

[42]  Paul Grünbacher.  Collaborative requirements negotiation with EasyWinWin , 2000, Proceedings 11th International Workshop on Database and Expert Systems Applications.

[43]  Jean Hartley,et al.  Case study research , 2004 .

[44]  R. Yin.  Case Study Research: Design and Methods , 1984 .

[45]  Barry W. Boehm,et al.  Theory-W Software Project Management: Principles and Examples , 1989, IEEE Trans. Software Eng..

[46]  Anselm L. Strauss,et al.  Basics of qualitative research : techniques and procedures for developing grounded theory , 1998 .

[47]  Anders Wall,et al.  Key Aspects of Software Release Planning in Industry , 2008 .

[48]  Markus Lindgren,et al.  Release Planning in Industry: Interview Data , 2007 .

[49]  Joachim Karlsson,et al.  Software requirements prioritizing , 1996, Proceedings of the Second International Conference on Requirements Engineering.

[50]  Thomas Thelin,et al.  An industrial case study of the verification and validation activities , 2003, Proceedings. 5th International Workshop on Enterprise Networking and Computing in Healthcare Industry (IEEE Cat. No.03EX717).

[51]  Diomidis Spinellis.  Silver Bullets and Other Mysteries , 2007, IEEE Software.

[52]  Pär Carlshamre,et al.  Release Planning in Market-Driven Software Product Development: Provoking an Understanding , 2002, Requirements Engineering.

[53]  J. Gosby.  MEDIA REVIEWS: Basics of Qualitative Research - Techniques and Procedures for Developing Grounded Theory 2nd Edition by A. Strauss and J. Corbin. Sage Publications, , 2000 .

[54]  Mario R. Barbacci,et al.  Quality Attribute Workshops (QAWs), Third Edition , 2003 .

[55]  Mary Shaw,et al.  What makes good research in software engineering? , 2002, International Journal on Software Tools for Technology Transfer.

[56]  Paolo Toth,et al.  Knapsack Problems: Algorithms and Computer Implementations , 1990 .

[57]  T. Saaty.  Decision making — the Analytic Hierarchy and Network Processes (AHP/ANP) , 2004 .

[58]  Barry W. Boehm,et al.  Developing Groupware for Requirements Negotiation: Lessons Learned , 2001, IEEE Softw..

[59]  R. Land.  Software Deterioration And Maintainability – A Model Proposal , 2002 .

[60]  Lena Karlsson,et al.  Requirements Prioritisation and Retrospective Analysis for Release Planning Process Improvement , 2006 .