22nd IEEE International Conference on Software Analysis, Evolution, and Reengineering

User Tools

Site Tools


en:workshops

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision
Previous revision
Last revision Both sides next revision
en:workshops [2014/11/18 13:32]
vincent
en:workshops [2014/12/17 01:55]
vincent
Line 35: Line 35:
 |Workshop ​                | 2 March, 2015 (fixed date TBA) | |Workshop ​                | 2 March, 2015 (fixed date TBA) |
  
-**General Chair**:+**General Chair**
   ***Chanchal K. Roy**, University of Saskatchewan,​ Canada   ***Chanchal K. Roy**, University of Saskatchewan,​ Canada
  
-**Pc Co-Chair**:+**Pc Co-Chair**
   ***Iman Keivanloo**,​ Queen’s University, Canada   ***Iman Keivanloo**,​ Queen’s University, Canada
  
   ***Angela Lozano**, Vrize Universiteir Brussel, Belgium   ***Angela Lozano**, Vrize Universiteir Brussel, Belgium
  
-**Steering Committee**:+**Steering Committee**
   ***James R. Cordy**, Queen’s University, Canada   ***James R. Cordy**, Queen’s University, Canada
  
Line 51: Line 51:
  
 ==== PPAP 2015 ==== ==== PPAP 2015 ====
-[[http://​ppap.soccerlab.polymtl.ca/​ | Second Workshop on Patterns Promotion and Anti-patterns Prevention]] 
  
-Patterns are good solutions to problems reoccurring in certain contexts while anti-patterns are the contrary, i.e., common poor practicesNow, it has been almost two decades since design patterns [Gamma et al., 1994] and anti-patterns [Koenig, 1995] were introduced in the domain of software engineering. Since then, there has been a tremendous number of works mainly ​on the definition, detection, application, ​and impact of design patterns and anti-patterns. These works built a well-established topic of research and a foundation for new families of patterns and anti-patterns. In the past few years, we have seen emerging patterns ​(e.g., testing [Soundarajan et al., 2008], API evolution [Kim et al., 2007], anti-patterns (e.g. linguistic [Abebe et al., 2009; Arnaoudova, 2010], and requirement [Shoemaker, 2007]).+[[http://​ppap.soccerlab.polymtl.ca/ | Second Workshop ​on Patterns Promotion ​and Anti-patterns ​Prevention ​(PPAP) 2015]]
  
-The goal of the the second edition ​of PPAP is to understand to what extent practitioners benefit from the concepts of patterns and anti-patterns and the existing catalogs. In fact, patterns are widely studied in the research community to asses their benefit for program comprehension,​ maintenance,​ and more generally the quality of the software. In addition, many researchers studied to what extent anti-patterns can negatively impact the different software activities and software quality. However, limited feedback exist on how practitioners benefit from the existing body of research on patterns and anti-patterns. Thus, the second edition of PPAP aims at providing a platform for practitioners and researchers to exchange experiences and needs.+**<fc #​ff0000>​DEADLINE EXTENDED</​fc>​** 
 + 
 +Collocated with the 22nd IEEE International Conference on Software Analysis, 
 +Evolution, and Reengineering (SANER'​2015),​ which will be held in 
 +March 2-6 2015, in Polytechnique Montréal, Montréal, Canada. 
 + 
 +Workshop date: TBA (Monday March 2nd OR Friday March 6th), 2015 
 + 
 + 
 +**Highlights** 
 + 
 +  *PPAP Website: http://​ppap.soccerlab.polymtl.ca/​ 
 +  *Abstract submission: by December 8th, 2014 
 +  *Paper submission: by December 8th, 2014 
 +  *Publication:​ in the proceeding of SANER'​2015 
 +  *Contact: ppap@polymtl.ca 
 +  *Submission (via EasyChair) https://​easychair.org/​conferences/?​conf=ppap2015 
 +  *IEEE Proceeding, template at http://​www.ieee.org/​conferences_events/​conferences/​publishing/​templates.html 
 + 
 + 
 +**Workshop** 
 + 
 + 
 +Patterns are good solutions to problems reoccurring in certain contexts 
 +while anti-patterns are the contrary, i.e., common poor practices. 
 +Now, it has been almost two decades since design patterns 
 +[Gamma et al., 1994] and anti-patterns [Koenig, 1995] were introduced 
 +in the domain of software engineering. Since then, there has been 
 +a tremendous number of works mainly on the definition, detection,​ 
 +application,​ and impact of design patterns and anti-patterns. 
 +These works built a well-established topic of research and 
 +a foundation for new families of patterns and anti-patterns. 
 + 
 +The goal of the workshop is to promote the application of patterns and 
 +prevent the spread of anti-patterns. For the second edition, the aim is 
 +to understand to what extent practitioners benefit from the concepts of 
 +patterns and anti-patterns and the existing catalogs. In fact, patterns are 
 +widely studied in the research community to asses their benefit for 
 +program comprehension,​ maintenance,​ and more generally the quality of 
 +the software. In addition, many researchers studied to what extent 
 +anti-patterns can negatively impact the different software activities and 
 +software quality. However, limited feedback exist on how practitioners 
 +benefit from the existing body of research on patterns and anti-patterns. 
 +Thus, the second edition of PPAP aims at providing a platform for 
 +practitioners and researchers to exchange experiences and needs. 
 + 
 +**Topics** 
 + 
 +We invite researchers and practitioners to submit research papers, 
 +position papers, experience reports, and discussion papers. 
 +Topics include but are not limited to: 
 + 
 +  *identifying show-stoppers that prevent to adopt patterns or refactor from anti-patterns;​ 
 +  *impact on software quality, testing; 
 +  *identifying needs for new families of patterns (anti-patterns);​ 
 +  *defining new patterns/​anti-patterns;​ 
 +  *enriching existing patterns/​anti-patterns;​ 
 +  *empirical studies; 
 +  *evolution. 
 + 
 + 
 +**Paper Format** 
 + 
 +Papers should not exceed 4 pages. All papers should be submitted 
 +as PDF file following the IEEE two-column proceedings format: 
 +http://​www.ieee.org/​conferences_events/​conferences/​publishing/​templates.html 
 + 
 +The submission will be done via EasyChair:​ 
 +https://​easychair.org/​conferences/?​conf=ppap2015
  
  
 ^ <fc #​ff0000>​IMPORTANT DATES</​fc>​^^ ^ <fc #​ff0000>​IMPORTANT DATES</​fc>​^^
-|Abstract submission |November 21st, 2014                +|Abstract submission |<​del>​December 8th, 2014</​del> ​     ​
-|Paper submission ​   |November 28th, 2014                |+|Paper submission ​   |<​del>​December 8th, 2014</​del> ​     ​|
 |Notification date   ​|December 23rd, 2014                | |Notification date   ​|December 23rd, 2014                |
 |Camera ready        |January 14th, 2015                 | |Camera ready        |January 14th, 2015                 |
-|Workshop date       |TBA (March 2nd or March 5th) 2015  |+|Workshop date       |TBA (March 2nd or March 6th) 2015  |
  
-**Steering Committee**:+**Steering Committee**
  
   ***Giuliano Antoniol**, Polytechnique Montréal, Canada   ***Giuliano Antoniol**, Polytechnique Montréal, Canada
Line 71: Line 138:
   ***Leon Moonen**, Simula Research Laboratory, Norway   ***Leon Moonen**, Simula Research Laboratory, Norway
  
-**Organizing ​committee**:+**Organizing ​Committee**
  
   ***Surafel Lemma Abebe**, Addis Ababa University, Ethiopia   ***Surafel Lemma Abebe**, Addis Ababa University, Ethiopia
Line 78: Line 145:
   ***Aminata Sabané**, Polytechnique Montréal, Canada   ***Aminata Sabané**, Polytechnique Montréal, Canada
   ***Wei Wu**, Polytechnique Montréal, Canada   ***Wei Wu**, Polytechnique Montréal, Canada
 +
 +**Program Committee**
 +
 +  ***Gabriele Bavota**, University of Sannio, Italy
 +  ***Alexander Chatzigeorgiou**,​ University of Macedonia, Greece
 +  ***Massimiliano Di Penta**, University of Sannio, Italy
 +  ***Latifa Guerrouj**, Concordia University, Canada
 +  ***Zhen Ming (Jack) Jiang**, York University, Canada
 +  ***Foutse Khomh**, Polytechnique Montréal, Canada
 +  ***Ángela Lozano**, Vrije Universiteit Brussel, Belgium
 +  ***Naouel Moha**, Université du Québec à Montréal, Canada
 +  ***Lionel Seinturier**,​ University of Lille 1, France
 +  ***Nikolaos Tsantalis**,​ Concordia University, Canada
 +  ***Stéphane Vaucher**, Benchmark Consulting, Canada
 +  ***Aiko Yamashita**,​ Simula Research Laboratory, Norway
  
 ==== PCODA’15 ==== ==== PCODA’15 ====
Line 108: Line 190:
  
 ^ <fc #​ff0000>​IMPORTANT DATES</​fc>​^^ ^ <fc #​ff0000>​IMPORTANT DATES</​fc>​^^
-|Abstract submission ​     | December 8, 2014 | +|Abstract submission ​     | <del>December 8, 2014</​del> ​
-|Paper submissions ​       | December 12, 2014 |+|Paper submissions ​       | <del>December 12, 2014</​del> ​|
 |Acceptance notification ​ | January 5, 2015  | |Acceptance notification ​ | January 5, 2015  |
 |Camera ready | January 12, 2015 | |Camera ready | January 12, 2015 |
Line 169: Line 251:
  
 **STEERING COMMITEE**: **STEERING COMMITEE**:
-  ***Ayse Bener Ryerson** University, Canada+  ***Ayse Bener**, Ryerson ​University, Canada
   ***Michael W. Godfrey**, Waterloo University, Canada   ***Michael W. Godfrey**, Waterloo University, Canada
   ***Tim Menzies**, North Carolina State University, USA   ***Tim Menzies**, North Carolina State University, USA
Line 195: Line 277:
  
 ^ <fc #​ff0000>​IMPORTANT DATES</​fc>​ (may still be subject to changes)^^ ^ <fc #​ff0000>​IMPORTANT DATES</​fc>​ (may still be subject to changes)^^
-|Abstract submission ​     | December 16, 2014 |+|Abstract submission ​     | <del>December 16, 2014</​del> ​|
 |Paper submissions ​       | December 21, 2014 | |Paper submissions ​       | December 21, 2014 |
 |Acceptance notification ​ | January 19, 2015  | |Acceptance notification ​ | January 19, 2015  |
Line 208: Line 290:
  
 ==== OOPSLE 2015 ==== ==== OOPSLE 2015 ====
-[[http://​oopsle.github.io/​ | Open and Original Problems in Software Language Engineering]]+[[http://​oopsle.github.io/​2015| Open and Original Problems in Software Language Engineering]] 
 + 
 +Everyone is invited to submit a position paper up to 4 pages in length, 
 +sketching an open or original problem, idea or challenge. Submissions are 
 +screened by the workshop chairs, who will select papers based on potential 
 +for discussion and interest to the community, as well as the clarity of 
 +presentation and motivation. 
 + 
 +OOPSLE is not a mini-conference,​ and therefore it is not necessary for the 
 +work to be conclusive yet. The papers will be posted online prior to the 
 +workshop, so the participants have the opportunity to read them in advance. 
 + 
 +Papers should submitted electronically via EasyChair. 
 + 
 +Each accepted paper is presented at the workshop as a brief summary of its 
 +main idea and a set of open questions to be discussed with the  
 +audience. Presenters will ask for input on how to proceed with experiments,​ 
 +validation or refinement of their ideas, collect opinions on the presented 
 +definitions,​ share similar experience. We expect the participants to be 
 +friendly but inquisitive,​ and ask hard questions back that may lead to 
 +deepening the initially presented insights. The workshop is planned to have 
 +short presentations and long discussions to stimulate direct collaboration 
 +afterwards. 
 + 
 +After the workshop, all participants will be invited to submit a full paper 
 +to a special issue in a peer-reviewed journal. Those submissions will 
 +undergo peer review by the members of the program committee consisting of 
 +researchers in software language engineering and reverse engineering. 
 + 
 +^ <fc #​ff0000>​IMPORTANT DATES</​fc>​ (may still be subject to changes)^^ 
 +|Submission deadline | <​del>​December 15, 2014</​del> ​        | 
 +|Workshop ​           | At SANER, March 2–6, 2015 | 
 + 
 +** Links ** 
 + 
 +Submission Page:     ​https://​www.easychair.org/​conferences/?​conf=oopsle2015 
 + 
 +** Relevant topics ** 
 + 
 +We acknowledge the following list as non-exhaustive collection of examples 
 +of topics of interests of the workshop: 
 + 
 +  *Defining an unsolved problem by establishing both its provenance in prior research and the lack of a fully satisfactory solution. 
 + 
 +  *Identifying new problem areas in software language engineering that have  not been previously studied due to lack of understanding,​ techniques, practical interest or scalability issues. 
 + 
 +  *Engaging in technological space travel by identifying similar problems in   ​various sectors of software language engineering (i.e., grammarware,​ modelware, ontoware, XMLware, databases, spreadsheets,​ etc). 
 + 
 +  *Generalising and reformulating of several well-known problems into several sides of one open challenge (e.g., parsing and pretty-printing). 
 + 
 +  *Proposing systematic methods of assessment and comparison of existing and emerging solutions to a problem that is not or cannot be fully solved (e.g., choosing between parsing techniques, metaprogramming methodologies,​ software language workbenches). 
 + 
 +  *Arguing about definitions of terms commonly used in various senses (e.g., software language design, quality of a grammar, transformation). 
 + 
 + 
 +  *Presenting unconventional crossovers of popular research topics and software language engineering concerns (e.g., green IDEs and energy consumption considerations for parsing algorithms). 
 +  
 +  *Making an overview of major hindrances hindering solution of a standing problem (e.g., tool interoperability and reuse, tackling language and metalanguage diversity and versatility,​ consistency management). 
 + 
 +  *Designing open datasets in the software language engineering domain and the way we could share and incorporate them. 
 + 
 +  *Describing novel or unconventional ideas that are promising but are not yet fully validated, or where validation itself may be a challenge. 
 + 
 +  *Revealing solid negative results, failed experiments and disproven hypotheses. 
  
 +  *Constructing future community experiments and considering topics our community expects to see addressed by such a competition,​ if one decides to run it in the future.
  
-The OOPSLE workshop is discussion-oriented and collaborative forum for formulating and addressing with open, unsolved and unsolvable problems in software language ​engineering.+  *Critically reassessing ​problem that is widely assumed to be solved but the solution is either underwhelming or could be “considered harmful” (model-driven ​engineering, domain-specific languages, test-based development).
  
-“Software languages” comprise all kinds of artificial languages used in software development:​ for programming,​ markup, pretty-printing,​ modelling, data description,​ formal specification,​ evolution, etc. Software language engineering is a relatively new research domain of systematic, disciplined and measurable approaches of development,​ evolution and maintenance of such languages. 
  
-**ORGANIZERS**: +** Workshop Co-Chairs ​**: 
-  ***Anya Helene Bagge**, University of Bergen, Norway +  ***Anya Helene Bagge** ​<​anya@ii.uib.no>​, University of Bergen, Norway 
-  ***Vadim Zaytsev**, ​CWI, Amsterdam, The Netherlands+  ***Vadim Zaytsev** ​<​vadim@grammarware.net>​University of Amsterdam, The Netherlands
  
 ====== Call for Workshops ====== ====== Call for Workshops ======
Line 224: Line 370:
  
 ^ <fc #​ff0000>​CLOSED</​fc>:​ [[en:​workshops|Workshops Proposals]] ^^^ ^ <fc #​ff0000>​CLOSED</​fc>:​ [[en:​workshops|Workshops Proposals]] ^^^
-| Proposals submissions ​  | September 30th, 2014 | 23:59 [[http://​en.wikipedia.org/​wiki/​Anywhere_on_Earth|AoE]] | +| Proposals submissions ​  ​| ​<del>September 30th, 2014</​del> ​| 23:59 [[http://​en.wikipedia.org/​wiki/​Anywhere_on_Earth|AoE]] | 
-| Proposals notifications | October ​  15th, 2014 | ::: |+| Proposals notifications | <del>October ​  15th, 2014</​del> ​| ::: |
  
 Workshops at the 22nd edition of the the International Conference on Software Analysis, Evolution, and Reengineering (SANER’15) provide a forum for researchers to exchange and discuss their early innovative scientific ideas on the theory and practice of recovering information from existing software and systems. Young students can get early feedback on their first research endeavors, while seasoned researchers get the opportunity to brainstorm with their peers about emerging topics. SANER’15 workshops are characterised by a focused topic, lively discussion, and enthusiastic participants (the typical group size is between 10 and 20 participants). ​ Workshops at the 22nd edition of the the International Conference on Software Analysis, Evolution, and Reengineering (SANER’15) provide a forum for researchers to exchange and discuss their early innovative scientific ideas on the theory and practice of recovering information from existing software and systems. Young students can get early feedback on their first research endeavors, while seasoned researchers get the opportunity to brainstorm with their peers about emerging topics. SANER’15 workshops are characterised by a focused topic, lively discussion, and enthusiastic participants (the typical group size is between 10 and 20 participants). ​
en/workshops.txt · Last modified: 2014/12/17 18:05 by yann