{"id":135,"date":"2019-07-05T11:31:25","date_gmt":"2019-07-05T11:31:25","guid":{"rendered":"https:\/\/projects.lsv.ens-paris-saclay.fr\/confsrentree\/?page_id=135"},"modified":"2019-07-05T11:31:25","modified_gmt":"2019-07-05T11:31:25","slug":"ever-running-systems-code-analysis-and-reflective-systems-in-love","status":"publish","type":"page","link":"https:\/\/projects.lsv.ens-paris-saclay.fr\/confsrentree\/?page_id=135","title":{"rendered":"Ever-running systems: Code analysis and reflective systems in love"},"content":{"rendered":"<p><img loading=\"lazy\" decoding=\"async\" class=\"alignright wp-image-103\" src=\"https:\/\/stephane.ducasse.free.fr\/StefFingerOnNose128.jpg\" alt=\"\" width=\"112\" height=\"170\" \/><\/p>\n<p><a href=\"https:\/\/stephane.ducasse.free.fr\/\">St\u00e9phane Ducasse<\/a>, \u00e9quipe <a href=\"https:\/\/rmod.inria.fr\/web\/\">RMoD<\/a>, <a href=\"https:\/\/www.inria.fr\/\">INRIA Lille<\/a>.<\/p>\n<p>In the first part of this seminar I will present the challenges any reasonable software is facing: the urge to evolve.<\/p>\n<p>I will present the characteristics of large industrial systems and sketch a vision around what could build our industry: ever-running systems. Imagine software running uninterrupted during 30 years. (GemstoneSyst Corp is one of the rare companies supporting this. They sign contracts stating that an application can not be off more than 30 min per year, every extra minute is charged 30 K$).<\/p>\n<p>I will also present some research we did over the last 10 years around software evolution using the Moose platform (<a class=\"\" href=\"https:\/\/moosetechnology.org\">https:\/\/moosetechnology.org<\/a>).<\/p>\n<p>I will cover visualisations, metrics, refactorings, automated migration, automated software update, UI migration, test selection.<\/p>\n<p>In the second part of this seminar I will talk about reflective systems.<\/p>\n<p>Indeed, if we want to be able to build ever-running systems we should think that the systems should have a causal connexion of their own representation. As an example I will take Pharo (<a class=\"\" href=\"https:\/\/www.pharo.org\">https:\/\/www.pharo.org<\/a>), the language we develop with its consortium (<a class=\"\" href=\"https:\/\/consortium.pharo.org\">https:\/\/consortium.pharo.org<\/a>).<\/p>\n<p>I will show what it is to program in a live environment where the programmer can mold the object representation to its own focus. Then I will show that with on demand stack reification, we can easily build control flow break point or automatic code transformation at runtime. I will sketch some research challenges for such systems.<\/p>\n<h2>Bio<\/h2>\n<p>St\u00e9phane Ducasse is INRIA Research Director.\u00a0 He leads the <a href=\"https:\/\/rmod.inria.fr\/web\">RMoD<\/a> team.\u00a0 He is an expert in language design and reengineering.\u00a0 He has worked on traits, which were introduced in Pharo, Perl, PHP, and under a variant into Scala, Groovy and Fortress. He is an expert on software quality, program understanding, program visualisations, reengineering and metamodeling. He is one of the developers of <a href=\"https:\/\/moosetechnology.org\/\">Moose<\/a>, an open-source software analysis platform.\u00a0 He created Synectique, a company building dedicated tools for advanced software analyses. He is one of the leaders of <a href=\"https:\/\/www.pharo.org\/\">Pharo<\/a>, a dynamic reflective object-oriented language supporting live programming. He has built the <a href=\"https:\/\/consortium.pharo.org\/\">industrial Pharo consortium<\/a>. He works regularly with companies (Thales, Wordline, Siemens, Berger-Levrault, Arolla,&#8230;) on software evolution problems.<br \/>\nHe has written a couple hundred articles and several books. According to Google his h-index is 55 for more than 12800 citations. He likes to help people becoming what they want and building things.<\/p>\n","protected":false},"excerpt":{"rendered":"<p>St\u00e9phane Ducasse, \u00e9quipe RMoD, INRIA Lille. In the first part of this seminar I will present the challenges any reasonable software is facing: the urge to evolve. I will present the characteristics of large industrial systems and sketch a vision around what could build our industry: ever-running systems. Imagine software running uninterrupted during 30 years. [&hellip;]<\/p>\n","protected":false},"author":1,"featured_media":0,"parent":0,"menu_order":0,"comment_status":"closed","ping_status":"closed","template":"","meta":{"footnotes":""},"class_list":["post-135","page","type-page","status-publish","hentry"],"_links":{"self":[{"href":"https:\/\/projects.lsv.ens-paris-saclay.fr\/confsrentree\/index.php?rest_route=\/wp\/v2\/pages\/135","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/projects.lsv.ens-paris-saclay.fr\/confsrentree\/index.php?rest_route=\/wp\/v2\/pages"}],"about":[{"href":"https:\/\/projects.lsv.ens-paris-saclay.fr\/confsrentree\/index.php?rest_route=\/wp\/v2\/types\/page"}],"author":[{"embeddable":true,"href":"https:\/\/projects.lsv.ens-paris-saclay.fr\/confsrentree\/index.php?rest_route=\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/projects.lsv.ens-paris-saclay.fr\/confsrentree\/index.php?rest_route=%2Fwp%2Fv2%2Fcomments&post=135"}],"version-history":[{"count":2,"href":"https:\/\/projects.lsv.ens-paris-saclay.fr\/confsrentree\/index.php?rest_route=\/wp\/v2\/pages\/135\/revisions"}],"predecessor-version":[{"id":137,"href":"https:\/\/projects.lsv.ens-paris-saclay.fr\/confsrentree\/index.php?rest_route=\/wp\/v2\/pages\/135\/revisions\/137"}],"wp:attachment":[{"href":"https:\/\/projects.lsv.ens-paris-saclay.fr\/confsrentree\/index.php?rest_route=%2Fwp%2Fv2%2Fmedia&parent=135"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}