---

I giorni 20-21-22 febbraio a partire dalle ore 9:00 il dott. Esteban Lorenzano - INRIA Lille - FR terra' un seminario dal titolo: "The Pharo Suite" La durata e' di 15 ore, inclusa la prova finale, per un totale di 3 CFU. Il seminario si terra' in aula C Pharo is a pure object-oriented programming language in the tradition of Smalltalk. It offers a unique developing experience in constant interaction with live objects. Pharo is elegant, fun to use and very powerful. It is very easy to learn and enables to understand advanced concept in a natural way. When programming in Pharo, you are immersed in a world of live objects. You have immediate feedback at any moment of your development on objects representing web applications, code itself, graphics, network and more. In the course, we will present Pharo as a language and environment. with special attention to object oriented design and is basic principles as extreme late binding, polymorphism, messages, duck typing and important design patterns. We will see its introspection (reflection) capabilities and what can we do which such infrastructure. The course is intended for people with programming experience and it will focus on Pharo but is also a good way to understand object oriented programming in deep, and it will change the common (miss)understandings around it.

Il giorno 23 febbraio a partire dalle ore 9:00 la prof.ssa Lenarduzzi - OULU University - FI terra' un seminario dal titolo:"The dark side of developing: Software Maintenance and Technical Debt." La durata e' di 5 ore, inclusa la prova finale, per un totale di 1 CFU. Il seminario si terra' in aula II The dark side of developing: Software Maintenance and Technical Debt. Software is always evolving. On one side, companies need to keep on adding new features to maintain their competitive advantage. On the other side, companies need to maintain the software, fixing bugs and updating with new technologies, but also paying attention to security vulnerabilities. The lack of software maintenance could quickly turn the software obsolete provide a higher competitive advantage to competitors. However, software maintenance activities are usually assigned with a lower priority compared to new features. The reason is because maintenance activities do not return into immediate revenues. Therefore, developers commonly postpone maintenance, accumulating the so called Technical Debt (TD). Technical Debt (TD) is a metaphor from the economic domain that refers to different software maintenance activities that are postponed in favour of the development of new features to get short-term payoff . The growth of the TD commonly slows down the development process. In the last few years, the number of publications on TD is constantly increasing. Moreover, several companies started to adopt TD analysis tools such as SonarQube and Cast, investing a relevant amount of budget on refactoring activities recommended by these tools, with the hope of reducing bugs or ease the software maintenance. This is certainly a very encouraging sign, where software engineering research topics receive balanced attention by both communities. Several researchers also proposed methods to estimate TD. Unfortunately, there is still a gap on the identification of the relationship between TD and software qualities and how to determine the impact of TD on software quality. In this seminar, we go through the stages of bad and best practices for software maintenance and how to manage TD.