Journal of Software: Evolution and Process

Cover image for Vol. 29 Issue 2

Early View (Online Version of Record published before inclusion in an issue)

Edited By: Gerardo Canfora, Darren Dalcher and David Raffo

Impact Factor: 0.729

ISI Journal Citation Reports © Ranking: 2015: 69/106 (Computer Science Software Engineering)

Online ISSN: 2047-7481

Associated Title(s): Concurrency and Computation: Practice and Experience, Software Focus, Software Process: Improvement and Practice, Software Testing, Verification and Reliability, Software: Practice and Experience


  1. 1 - 19

    1. A comprehensive framework for modeling requirements of CSCW systems

      Miguel A. Teruel, Elena Navarro, Víctor López-Jaquero, Francisco Montero and Pascual González

      Version of Record online: 21 FEB 2017 | DOI: 10.1002/smr.1858

      Thumbnail image of graphical abstract

      • A framework, CSRMF, for requirements specification in collaborative environments is introduced.

      • An improved language, CSRML v2, specifies requirements of collaboration and awareness.

      • CSRMF is put in practice by modelling the requirements of a collaborative computer game.

    2. Enabling code transformations with FermaT on simplified bytecode

      Doni Pracner and Zoran Budimac

      Version of Record online: 20 FEB 2017 | DOI: 10.1002/smr.1857

      Thumbnail image of graphical abstract

      This paper presents a new approach for working with Java bytecode that uses existing tools (FermaT and the wide spectrum language) that have been industrially tested and proven in transforming legacy assembly code. The first step has been a successful translator that works with a subset language (MicroJava) and enables the usage of formal transformations in FermaT to restructure the code from a machine level to human readable high-level structures, both automatically and manually. It mostly relies on the existing transformations, but some new ones were introduced in this work, and some old ones were modified.


    1. TMAP: Discovering relevant API methods through text mining of API documentation

      Rahul Pandita, Raoul Jetley, Sithu Sudarsan, Timothy Menzies and Laurie Williams

      Version of Record online: 20 FEB 2017 | DOI: 10.1002/smr.1845


    1. The long-term growth rate of evolving software: Empirical results and implications

      Les Hatton, Diomidis Spinellis and Michiel van Genuchten

      Version of Record online: 16 FEB 2017 | DOI: 10.1002/smr.1847

    2. The relationship between evolutionary coupling and defects in large industrial software

      Serkan Kirbas, Bora Caglayan, Tracy Hall, Steve Counsell, David Bowes, Alper Sen and Ayse Bener

      Version of Record online: 7 FEB 2017 | DOI: 10.1002/smr.1842

    3. Work fragmentation in developer interaction data

      Luis C. Cruz, Heider Sanchez, Víctor M. González and Romain Robbes

      Version of Record online: 30 JAN 2017 | DOI: 10.1002/smr.1839

  4. Special Issue – SANER 2015

    1. Understanding systematic and collaborative code changes by mining evolutionary trajectory patterns

      Qingtao Jiang, Xin Peng, Hai Wang, Zhenchang Xing and Wenyun Zhao

      Version of Record online: 26 JAN 2017 | DOI: 10.1002/smr.1840

      Thumbnail image of graphical abstract

      Code changes are made in a systematic and collaborative way, and individual code changes are often an integral part of high-level changes. Historical commit records can be summarized as trajectory patterns by grouping and aggregating relevant code changes committed over time. Trajectory patterns can reveal various underlying evolution rules and problems that are useful for software evolution management and quality assurance.


    1. Simplifying the construction of source code transformations via automatic syntactic restructurings

      Christian D. Newman, Brian Bartman, Michael L. Collard and Jonathan I. Maletic

      Version of Record online: 20 JAN 2017 | DOI: 10.1002/smr.1831

      Thumbnail image of graphical abstract

    1. Mining unit test cases to synthesize API usage examples

      Mohammad Ghafari, Konstantin Rubinov and Mohammad Mehdi Pourhashem K.

      Version of Record online: 20 JAN 2017 | DOI: 10.1002/smr.1841


    1. There and back again: Can you compile that snapshot?

      Michele Tufano, Fabio Palomba, Gabriele Bavota, Massimiliano Di Penta, Rocco Oliveto, Andrea De Lucia and Denys Poshyvanyk

      Version of Record online: 20 DEC 2016 | DOI: 10.1002/smr.1838

      Thumbnail image of graphical abstract

      We study broken snapshots (i.e., snapshots that cannot be compiled) in 100 Java projects to investigate (1) how frequently they happen and (2) likely causes behind them. The empirical results indicate that broken snapshots occur in 96% of the projects and that they are mainly due to problems related to the resolution of dependencies. The achieved results can be useful to researchers interested in gaining analytical insights by mining (and compiling) the change history of software projects.

    2. Assisting the continuous improvement of Scrum projects using metrics and Bayesian networks

      Mirko Perkusich, Kyller Costa Gorgônio, Hyggo Almeida and Angelo Perkusich

      Version of Record online: 13 NOV 2016 | DOI: 10.1002/smr.1835


    1. An empirical study of portfolio management and Kanban in agile and lean software companies

      Muhammad Ovais Ahmad, Lucy Ellen Lwakatare, Pasi Kuvaja, Markku Oivo and Jouni Markkula

      Version of Record online: 2 NOV 2016 | DOI: 10.1002/smr.1834

      Thumbnail image of graphical abstract

      Adopting agile and lean in software industry has brought challenges in the management of companies' portfolios. Our findings show that agile and lean software companies adapt to minimal use of traditional portfolio management tools and methods. The emphasis is on using tools that facilitate immediate feedback from customers, in order to assess the value of offerings in their portfolio. Additionally, software companies are increasingly adopting Kanban for portfolio management to visualize offerings and balance demand with capability during offerings development.



    1. Detecting duplicate bug reports with software engineering domain knowledge

      Karan Aggarwal, Finbarr Timbers, Tanner Rutgers, Abram Hindle, Eleni Stroulia and Russell Greiner

      Version of Record online: 27 OCT 2016 | DOI: 10.1002/smr.1821

  11. Research Articles

    1. A meta-model of software development project states behavioral study of software projects

      Rehan Akbar, Mohd Fadzil Hassan and Azrai Abdullah

      Version of Record online: 10 OCT 2016 | DOI: 10.1002/smr.1820

    2. A model for assessing and re-assessing the value of software reuse

      Mikael Svahnberg and Tony Gorschek

      Version of Record online: 4 OCT 2016 | DOI: 10.1002/smr.1806

      Thumbnail image of graphical abstract

      Reuse value assessment framework is a framework for assessing and comparing specific value influencing aspects of different reusable software assets. The framework not only enables an informed first reuse decision but also provides a means for re-assessing the value based on updated needs and updated capabilities of the reused assets.

  12. Special Issue – Agile Software Product Development

    1. Cluster-based test cases prioritization and selection technique for agile regression testing

      Passant Kandil, Sherin Moussa and Nagwa Badr

      Version of Record online: 22 JUL 2016 | DOI: 10.1002/smr.1794

      Thumbnail image of graphical abstract

      The proposed model provide fully automated regression testing methodology that prioritizes test cases for regression testing at each sprint of the agile-based projects, and selects test cases to be used in regression testing at the end of the release. It is composed of two main techniques: Weighted Sprint Test cases Prioritization (WSTP) Technique and Cluster-based Release Test cases Selection (CRTS) Technique

    2. You have full text access to this OnlineOpen article
      Assessing the adoption level of scaled agile development: a maturity model for Scaled Agile Framework

      Oktay Turetken, Igor Stojanov and Jos J. M. Trienekens

      Version of Record online: 7 JUL 2016 | DOI: 10.1002/smr.1796

      Thumbnail image of graphical abstract

      Scaled Agile Framework (SAFe) has emerged as a solution to address some of the concerns regarding the scalability and integration of agile practices in large-scale development projects. We developed a maturity model that provides guidance for software-developing organizations in defining a roadmap and assessing the level of SAFe adoption. We took an existing agile maturity model as a basis, extended it with key SAFe practices, refined the model with industry experts using Delphi technique, and applied it in an enterprise.

  13. Special Issue – SANER 2015

    1. A bug reproduction approach based on directed model checking and crash traces

      Mathieu Nayrolles, Abdelwahab Hamou-Lhadj, Sofiène Tahar and Alf Larsson

      Version of Record online: 18 MAY 2016 | DOI: 10.1002/smr.1789


  1. 1 - 19