A Situational Approach for the Definition and Tailoring of a Data-Driven Software Evolution Method

Successful software evolution heavily depends on the selection of the right features to be included in the next release. Such selection is difficult, and companies often report bad experiences about user acceptance. To overcome this challenge, there is an increasing number of approaches that propose intensive use of data to drive evolution. This trend has motivated the SUPERSEDE method, which proposes the collection and analysis of user feedback and monitoring data as the baseline to elicit and prioritize requirements, which are then used to plan the next release. However, every company may be interested in tailoring this method depending on factors like project size, scope, etc. In order to provide a systematic approach, we propose the use of Situational Method Engineering to describe SUPERSEDE and guide its tailoring to a particular context.

[1]  Xavier Franch,et al.  Agile Quality Requirements Management Best Practices Portfolio: A Situational Method Engineering Approach , 2017, PROFES.

[2]  Jolita Ralyté,et al.  TOWARDS SITUATIONAL METHODS FOR INFORMATION SYSTEMS DEVELOPMENT: ENGINEERING REUSABLE METHOD CHUNKS , 2014 .

[3]  Isabelle Mirbel,et al.  Situational method engineering: combining assembly-based and roadmap-driven approaches , 2005, Requirements Engineering.

[4]  Xavier Franch,et al.  Replan: A Release Planning Tool , 2017, 2017 IEEE 24th International Conference on Software Analysis, Evolution and Reengineering (SANER).

[5]  Xavier Franch,et al.  iStar 2.0 Language Guide , 2016, ArXiv.

[6]  Mary Shaw,et al.  Engineering Self-Adaptive Systems through Feedback Loops , 2009, Software Engineering for Self-Adaptive Systems.

[7]  Norbert Seyff,et al.  An exploratory study of Twitter messages about software applications , 2017, Requirements Engineering.

[8]  Colette Rolland,et al.  An Approach for Method Reengineering , 2001, ER.

[9]  Anna Perini,et al.  Tool-Supported Collaborative Requirements Prioritisation , 2017, 2017 IEEE 41st Annual Computer Software and Applications Conference (COMPSAC).

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

[11]  Nicola Guarino,et al.  Software as a Social Artifact: A Management and Evolution Perspective , 2014, ER.

[12]  Ulrich Frank,et al.  Domain-Specific Modeling Languages: Requirements Analysis and Design Guidelines , 2013, Domain Engineering, Product Lines, Languages, and Conceptual Models.

[13]  Xavier Franch,et al.  Towards continuous software release planning , 2017, 2017 IEEE 24th International Conference on Software Analysis, Evolution and Reengineering (SANER).

[14]  Raian Ali,et al.  A goal-based framework for contextual requirements modeling and analysis , 2010, Requirements Engineering.

[15]  Xavier Franch,et al.  A precedence-based approach for proactive control in software process modelling , 2002, SEKE '02.

[16]  Tom Mens,et al.  Evolving Software Systems , 2014, Springer Berlin Heidelberg.

[17]  Colette Rolland,et al.  Towards a Generic Model for Situational Method Engineering , 2003, CAiSE.

[18]  Xavier Franch,et al.  OSSAP - A Situational Method for Defining Open Source Software Adoption Processes , 2016, CAiSE.

[19]  Anna Perini,et al.  Analysis of Online Discussions in Support of Requirements Discovery , 2017, CAiSE.

[20]  Norbert Seyff,et al.  Feedback Gathering from an Industrial Point of View , 2017, 2017 IEEE 25th International Requirements Engineering Conference (RE).

[21]  Pär J. Ågerfalk,et al.  Situational Method Engineering , 2014, Springer Berlin Heidelberg.

[22]  Xavier Franch,et al.  A software reference architecture for semantic-aware Big Data systems , 2017, Inf. Softw. Technol..