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

User Tools

Site Tools


en:accepted_tutorials

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
en:accepted_tutorials [2015/01/06 14:44]
krinkeje [Software Risk Management in Practice – Shed Light on Your Software Product]
en:accepted_tutorials [2015/03/30 13:48]
yann
Line 18: Line 18:
 research or industrial practice. research or industrial practice.
  
 +{{ :​en:​jim_cordy.jpg?​180|}}
 **James R. Cordy – Queen’s University, Canada** **James R. Cordy – Queen’s University, Canada**
 +
 +James Cordy is Professor and past Director of the School of Computing at Queen’s University at Kingston, Canada. ​ As leader of the TXL source transformation project with hundreds of academic and industrial users worldwide, he is the author of more than 160 refereed contributions in programming languages, software engineering and artificial intelligence. ​ From 1995-2001 he was Vice President and Chief Research Scientist at Legasys Corporation,​ whose LS/2000 source code analysis system was responsible for the analysis and reprogramming of over 4.5 billion lines of financial code of the largest Canadian banks for the Year 2000 problem. ​ Dr. Cordy is an ACM Distinguished Scientist, a senior member of the IEEE, and an IBM CAS faculty fellow.
 +
 ==== Software Risk Management in Practice – Shed Light on Your Software Product ==== ==== Software Risk Management in Practice – Shed Light on Your Software Product ====
  
Line 29: Line 33:
 Participants of the tutorial will receive an introduction to the techniques in theory and will then apply them in practice in interactive exercises. This enables participants to learn how to shed light on the internals of their software and how to make risk management decisions efficiently and effectively. Participants of the tutorial will receive an introduction to the techniques in theory and will then apply them in practice in interactive exercises. This enables participants to learn how to shed light on the internals of their software and how to make risk management decisions efficiently and effectively.
  
-**Jens Knodel, Matthias Naab -- Fraunhofer Institute for Experimental Software Engineering IESE Kaiserslautern,​ Germany +{{ :​en:​knodelnaab.jpg?​180|}} 
-Eric Bouwers, Joost Visser -- Software Improvement Group (SIG) Amsterdam, The Netherlands** +**Jens Knodel, Matthias Naab -- Fraunhofer Institute for Experimental Software Engineering ​(IESE), Kaiserslautern,​ Germany** 
-====== Technical Briefings ======+ 
 +Dr. Jens Knodel and Dr. Matthias Naab are software architects. Their expertise –- consolidated experiences and lessons learned from more than 50 projects with industry in domains like Embedded Systems, Information Systems, and Smart Ecosystems –- lies in the definition, improvement,​ and assessment of software architectures. 
 + 
 + 
 + 
 +Jens and Matthias are senior researchers at the Fraunhofer Institute for Experimental Software Engineering IESE in Kaiserslautern,​ Germany. They are responsible for project management,  
 +method development,​ and technology transfer in research and industry projects and are leading research activities in the area of software and systems architecture at IESE.  
 + 
 + 
 +In addition, Jens Knodel, and Matthias Naab regularly coach practitioners on software architecture. They also give tutorials at conferences and hold lectures at the Fraunhofer Academy and at the University of Kaiserslautern on the same topics. They are the authors of more than 100 scientific, peer-reviewed publications in the areas of software architecture,​ ecosystems, maintenance,​ and evolution. 
 + 
 +{{ :​en:​bouwersvisser.jpg?​180|}} 
 +**Eric Bouwers, Joost Visser -- Software Improvement Group (SIG)Amsterdam, The Netherlands** 
 + 
 +Eric Bouwers is a qualified teacher and technical consultant at the Software Improvement Group in Amsterdam, The Netherlands. He is interested in how software metrics can assist in quantifying the architectural aspects of software quality. In the past six years, this interest has led to the design, evaluation, and application of two architecture-level metrics that are now embedded in a benchmark-based model for software quality.  
 + 
 +Joost Visser is head of research at the Software Improvement Group (SIG) in Amsterdam, The Netherlands,​ and holds a position as professor of large-scale software systems at Radboud University Nijmegen, The Netherlands. At the SIG, Joost is responsible for innovation of tools and services, academic relations, internship coordination,​ and general research. In the past eight years, he has been involved in the development,​ evaluation, and application of a benchmark-based model for software quality. 
 + 
 +====== ​90 Minute ​Technical Briefings ====== 
 + 
 +==== [[http://​www.slideshare.net/​metimir/​software-architecture-reconstruction-why-what-and-how|Software Architecture Reconstruction:​ Why? What? and How?]] ==== 
 + 
 +//Tuesday, 03/​03/​2015//​ 
 + 
 +Every system is a legacy system, the moment a programmer writes a line of code it 
 +becomes a legacy. Therefore in even relatively new systems similar to long lived systems, 
 +developers are faced with a body of code that they need to understand, and from which 
 +they need to extract architectural knowledge. Unfortunately,​ anecdotal evidence has shown 
 +that such knowledge tends to be tacit in nature, stored in the heads of people, and 
 +inconsistently scattered across various software artifacts and repositories. Furthermore,​ 
 +architectural knowledge vaporizes over time. Given the size, complexity, and longevity of 
 +many projects, developers therefore often lack a comprehensive knowledge of architectural 
 +design decisions and consequently make changes in the code that inadvertently degrade 
 +the underlying design and compromise its qualities. 
 + 
 +This technical briefing will answer three fundamental questions about software architecture recovery: Why? What? and How? Through several examples it articulates and synthesizes technical 
 +forces and financial motivations that make software companies to invest in software 
 +architecture recovery. It discusses “what” are the pieces of design knowledge that can be 
 +recovered and lastly demonstrates a methodology as well as required tools for answering 
 +“how” to reconstruct architecture from implementation artifacts. 
 + 
 +{{ :​en:​mehdi.jpg?​180|}} 
 +**Mehdi Mirakhorli – Rochester Institute of Technology, USA** 
 + 
 +Mehdi Mirakhorli is an assistant professor at Rochester Institute of Technology. His research interest focuses on the application of data mining and information retrieval techniques to solve software engineering problems, “software architecture design, implementation,​ maintenance and reconstruction”,​ requirements engineering and software traceability. Previously, he worked for seven years as a software architect on large data-intensive software systems in banking, health care and meteorological domains. Dr. Mirakhorli has served as Guest Editor for a special edition of IEEE Software and organizer, committee member and reviewer for several software engineering conferences. Dr. Mirakhorli has received two ACM SIGSOFT Distinguished Paper Awards at the International Conference on Software Engineering. Furthermore he has been speaker in several technical venues such as ALTA Distinguished Speaker at Alcatel-Lucent. 
 + 
 + 
  
en/accepted_tutorials.txt · Last modified: 2015/03/30 13:48 by yann