Now showing items 1-6 of 6

    • A Change-based Approach to Software Evolution 

      Robbes R; Lanza M (2007)
      Software evolution research is limited by the amount of information available to researchers: Current version control tools do not store all the information generated by developers. They do not record every intermediate ...
    • Improving code completion with program history 

      Robbes R; Lanza M (2010)
      Code completion is a widely used productivity tool. It takes away the burden of remembering and typing the exact names of methods or classes: As a developer starts typing a name, it provides a progressively refined list ...
    • Object-oriented software extensions in practice 

      Robbes R; Röthlisberger D; Tanter É (Kluwer Academic Publishers, 2015)
      As software evolves, data types have to be extended, possibly with new data variants or new operations. Object-oriented design is well-known to support data extensions well. In fact, most popular books showcase data ...
    • The Small Project Observatory: Visualizing software ecosystems 

      Lungu M; Lanza M; Gîrba T; Robbes R (2010)
      Software evolution research has focused mostly on analyzing the evolution of single software systems. However, it is rarely the case that a project exists as standalone, independent of others. Rather, projects exist in ...
    • WEON: Towards a software ecosystem ontology 

      Gutierrez C; Robbes R (ACM, 2013)
      The natural distributed character of software ecosystems calls for a shared conceptualization and language to describe their architecture and their evolution. In this regards, ontologies play a central role. In this paper: ...
    • When should internal interfaces be promoted to public? 

      Hora A; Valente M; Robbes R; Anquetil N (ACM, 2016)
      Commonly, software systems have public (and stable) interfaces, and internal (and possibly unstable) interfaces. Despite being discouraged, client developers often use internal interfaces, which may cause their systems to ...