Welcome to the Wiki of the international workshop on Object-Oriented Reengineering

As with previous editions, the 7th edition will be hosted at the 20th European Conference on Object-Oriented Programming (ECOOP 2006) http://2006.ecoop.org/ and will take place on the 4th of July 2006, in Nantes, France.

Schedule of the Workshop

Accepted position papers follow in random order with attending participants in bold:

• (WOOR2006 Paper 1) Reverse-engineering of UML 2.0 Sequence Diagrams from Execution Traces by Romain Delamare, Benoit Baudry, and Yves Le Traon.
• (WOOR2006 Paper 2) ModelExtractor: An Automatic Parametric Model Extractor by Régis Chevrel, Jean Bézivin, Hugo Brunelière, Albin Jossic, William Piers, and Frédéric Jouault.
• (WOOR2006 Paper 3) Program Comprehension and Design Pattern Detection: An Experience Report by Claudia Raibulet and Francesca Arcelli.
• (WOOR2006 Paper 4) Extending a Taxonomy of Bad Code Smells with Metrics by Raúl Marticorena, Carlos López, and Yania Crespo.
• (WOOR2006 Paper 5) Difference Visualization: Impact Interaction between Code and Model by Susanne Jucknath-John and Sebastian Doltze.
• (WOOR2006 Paper 6) Correction of High-Level Design Defects with Refactorings by Naouel Moha, Saliha Bouden, and Yann-Gaël Guéhéneuc.
• (WOOR2006 Paper 7) Refactoring of Assertions in Design by Contract by Daniel Rodriguez, Manonjaran Satpathy, Josep Covas, and Juan-Jose Cuadrado.

Other participants:

• Cédric Bardet
• Thomas Fritz
• Juergen Wolff von Gudenberg
• Christian F.J. Lange

The workshop is specifically scheduled to increase fruitful interactions and discussions. After a short welcome session during which participants will introduce themselves, participants will split in two groups: one group focusing on the taxonomy and the comparison of design recovery tools, the other group discussing experience reports and advances in research. Then, all participants will meet again to summarise their discussions and findings.

Specifically, the schedule so far is planned as:

• 09:00-09:30 — Introduction

            Getting acquainted among participants             Formulation of goals and research questions             Practical arrangements

• 09:30-10:30 — Session 1: Getting the models

            Presentation of papers 1, 2, 3, and 5             - Romain or Benoit will present Régis, Jean, Hugo, Albin, and Wiliam’s paper entitled "ModelExtractor: An Automatic Parametric Model Extractor"

            - Régis, Jean, Hugo, Albin, or Wiliam will present Claudia and Francesca’s paper entitled "Program Comprehension and Design Pattern Detection"

            - Claudia or Francesca will present Susanne and Sebastian’s paper entitled "Difference Visualization: Impact Interaction between Code and Model"

            - Susanne or Sebastian will present Romain, Benoit, and Yves’s paper entitled "Reverse-engineering of UML 2.0 Sequence Diagrams from Execution Traces"

• 10:30-11:00 — Coffee Break

• 11:00- 11:45 — Session 2: Using refactorings

            Presentation of papers 4, 6, and 7             - Raúl or Carlos will present Naouel, Saliha, and Yann-Gaël’s paper entitled "Correction of High-Level Design Defects with Refactorings"

            - Naouel or Yann-Gaël will present Daniel, Manonjaran, Josep, and Juan-Jose’s paper entitled "Refactoring of Assertions in Design by Contract"

            - Daniel will present Raúl, López, and Yania’s paper entitled "Extending a Taxonomy of Bad Code Smells with Metrics"

• 11:45-12:30 — Preliminary research questions and split-up in working groups

• 12:30-14:00 — Lunch break

• 14:00-15:30 — Discussions

            The discussion groups will meet in a separate location.             One reporter should be chosen.

• 15:30-16:00 — Coffee Break

• 16:00 - 17:00 — Reporting

            Each discussion group will report its results

• 17:00-17:30 — Wraping-up

            Some practical arrangements             (Workshop reader, next workshop, dinner, ...)

Outcome of the Workshop

This year again, the workshop has been successful in stirring new ideas and in creating new collaborations. In particular, the two "halves" of the workshop worked tirelessly to provide directions to some issues raised during the presentations (one half) and (other half) to sketch a solution to the research question "Are implicit design patterns useful in program comprehension" collaboratively. A workshop report and more detailled results will be posted here soon. In the meantime, here are some pictures of the participants: WOOR2006 Photo 1 and WOOR2006 Photo 2.

Below is legacy information related to the call to submission and participation.

Important Dates

Workshop Contribution Submission: 15th of April 2006. (The deadline is over but feel free to contact us to check if it is still possible to contribute1) Notification of acceptance: 1st of May 2006. (Notifications has been sent to the authods on the 3rd of May, if you did not receive any, please contact the organisers.) Workshop date: 4th of July 2006.

Contributions: Building on Previous Years

In previous years, participants to the workshop have been actively contributing to the state-of-the-art on reengineering of object-oriented systems. In particular, they developed a taxonomy to classify design recovery tools, at the heart of any reengineering effort. Recognising the importance of this endeavour and the need for the community’s feedback and support, the workshop expects two forms of contributions:

1. The first form of contributions targets design recovery tool builders and users. It consists in filling out the questionnaire (soon) available at this Form and submitting it along with a short text detailing the rationale for the choice of the tools. This information, in addition to the discussions during the workshop, will help building a map of the design recovery tools out there. If you are interested in this form of contribution or have any question, please contact either Yann-Gaël Guéhéneuc (guehene@iro.umontreal.ca) or Roel Wuyts (roel.wuyts@ulb.ac.be). (The questionnaire will be soon available at http://smallwiki.unibe.ch/woor/questionnaire/.)
2. The second form of contributions targets researchers and industrials active in reengineering. We explicitly solicit experience reports from the software industry as well as contributions from researchers, tool producers, and methodology providers. Areas of interests include, but are not limited to:

• Experiences on re-engineering large object-oriented systems
• Design model extraction
• Documentation and re-use of object-oriented systems
• Analysis of object-oriented systems with respect to re-usability and flexibility
• Abstract models of object-oriented systems that help to understand and re-engineer large programs
• Methodological support for the transformation of object-oriented systems into frameworks
• Refactoring Operations
• Software Evolution
• Metrics or heuristics to measure the need for, the progress of, and improvement to object-oriented design
• Design patterns in reengineering practices
• Reengineering object-oriented software to an aspect-oriented solution
• Tools supporting any of the above activities.

Workshop on Object-Oriented Reengineering

The ability to reengineer object-oriented legacy systems has become a vital matter in today’s software industry. Early adopters of the object-oriented programming paradigm are now facing the problem of transforming their object-oriented "legacy" systems into full-fledged frameworks. Some are even starting to face the problem of reengineering their systems from object-oriented to aspect-oriented. We claim that software evolution and reengineering are among the core issues of software engineering, including object-oriented systems. Unfortunately, their importance is not yet fully acknowledged by current research and industrial efforts.

This workshop on Object-Oriented Reengineering is a unique opportunity for people working on object-oriented legacy systems to exchange ideas.

Intended Audience

The workshop is intended to software engineering professionals with experience in object-oriented reengineering; either people who are actively engaged in reengineering projects, or people who develop or research methodologies and tools. Each participant is requested to submit a contribution (see above) in advance.

Preparation

We pay special attention to the preparation of the workshop to make an efficient use of the day. We request each participant to submit a contribution in advance. Each participant is expected to read the material submitted by the other participants, so that all participants are acquainted with the ideas that exist within the group and that the workshop can be devoted to discussions instead of presentations. Submissions will be made electronically to ease the rapid exchange of information.

The upper limit for the number of participants is about 25 and the participants will be selected on the basis of the submitted contribution.

Submission Guidelines

If you submit a contribution of the second form (i.e., an industrial or academic experience report), we suggest the following guidelines:

• BE STANDARD. There exists a lot of work on re-engineering, which may give rise to some terminology conflicts. We encourage people to use the re-engineering taxonomy defined in Reverse Engineering and Design Recovery: A Taxonomy by E.J. Chikofsky and J.H. Cross II - IEEE Software, January 1990. Check http://www.tcse.org/revengr/taxonomy.html for an online summary.

• BE ELECTRONIC. Submit your position paper in HTML, PostScript, or PDF (preferred), so that we can collect all of the submissions on the web-site. A separate abstract including the e-mail addresses of the authors and a URL to their home pages MUST be submitted in HTML. Submit everything by e-mail to both of the two following e-mail addresses guehene@iro.umontreal.ca and roel.wuyts@ulb.ac.be.

• BE SHORT. Propose only one idea. We all know that you are a quality researcher with plenty of good ideas. Only, we have limited resources and we must focus. Please keep all position papers under five pages. Perhaps a workshop reader will be organized again this year.

• BE INNOVATIVE. It is okay to propose a recent idea that still has some unfinished sides to it. It is supposed to be a WORKshop, not a mini-conference.

• BE A REBEL. Neglect these guidelines if you feel that your idea needs a special treatment in some way.

About the Organisers

• Serge Demeyer

University of Antwerp (Belgium) Department of Mathematics and Computer Science http://www.win.ua.ac.be/~sdemey Prof. Serge Demeyer is leading a research group investigating "Software Reengineering" (LORE - Lab On REengineering).

• Stéphane Ducasse

University of Savoie (France) LISTIC http://www.listic.univ-savoie.fr/~ducasse Prof. Stéphane Ducasse, from the University of Savoie, is a former member of the Software Composition Group led by Prof. Oscar Nierstrasz at University of Bern (Switzerland).

• Yann-Gaël Guéhéneuc

University of Montreal (Quebec, Canada) Department of Informatics and Operations Research http://www.iro.umontreal.ca/~guehene Prof. Yann-Gaël Guéhéneuc leads the Ptidej project (in research Group on Open, Distributed Systems, Experimental Software Engineering) developing theories, methods, and tools, to evaluate and to improve the quality of object-oriented programs by promoting the use of idioms, design patterns, and architectural patterns.

• Kim Mens

Université catholique de Louvain (Belgium) Department of Computing Science and Engineering http://www.info.ucl.ac.be/~km Prof. Kim Mens is one of the originators of the ’reuse contract’ technique, he is the spokesperson of the Research Center on Structural Software Improvement and currently conducts research on ’co-evolution’ between source code and earlier life-cycle software artifacts, as well as on aspect identification and refactoring.

• Roel Wuyts

Université Libre de Bruxelles (Belgium) D’epartement d’Informatique http://homepages.ulb.ac.be/~rowuyts Prof. Roel Wuyts bootstrapped research in co-evolution of design and implementation with the declarative meta-programming language Soul.