S oftware Analysis And Transformation Organising a research team around the research software around the research team in software engineering Motivation, experiences, lessons Jurgen J. Vinju B
Master SE • National Centre Mathematics & Computer Science • Programming languages and systems SWAT ATEAMS • Algol, Python • ASF+SDF, Rascal • MonetDB, W3C • Software Improvement Group (spin-off) • Software Quality Assessment & Monitoring • Reverse Engineering • CWI SWAT ≡ INRIA ATEAMS • all about source code • supporting the tasks of programmers to {make,maintain} better software, cheaper • understanding and controlling software complexity • Master Software Engineering @{Universiteit van Amsterdam, VU, HvA} SWAT - S oftWare Analysis And Transformation
Team Research collaboration HR methods Research Societal Research Impact team(s) field Funding External collaboration Education SWAT - S oftWare Analysis And Transformation
domain- pragmatic code = data dependent Software Analysis & Transformation creative, undecidable multi-faceted innovative infeasible SWAT - S oftWare Analysis And Transformation
Software is wonderful , literally amazing. Our imagination is our only real constraint. SWAT - S oftWare Analysis And Transformation
Understand this little piece of code [Kees van der Laan] 6
Analysis 7
Analyse 8
Understanding software •Simple code •Simple question •Complex domain-specific analysis •Answer: absurd art [Penrose,Escher] 9
the source code of ls ls.c 3894 lines 77 pages 541 choices “its complicated”
Internal Research collaboration People methods Research Societal Research Impact team(s) field Funding External collaboration Education SWAT - S oftWare Analysis And Transformation
Rascal enable more € and better tools PL “valorisation” (application) experiment (empirical methods) Tools € SE knowledge exchange Research Industry (necessary domain knowledge) 12
results in education industry different support uptake domains PL SE surprisingly, Forensics Finance it works! High-tech project + contract community fun funding ATEAMS/SWAT very well evaluated 13
14
A research team is not a software team 15
fewer resources = more investment in efficiency (accidentally) sold as research output 16
team members prioritise for academic output which is not software 17
“win-win” situation needs weekly recalibration short-term goals has highest priority while long-term tactics enables it all 18
seniors take long term perspective: maintenance, engineering documentation, UX, teaching material community management 19
giving more control to phd students: - failure modes - learning from students - team spirit 20
taking losses: - throwing away code - weekends and holidays - rotten low hanging fruit - [illusion of] self-interest 21
We want (even) more: intuition for software by society patience with solving hard problems interaction with domain experts empirical evidence out-of-the-box thinking online social interaction 22
We need less: code (surprise!) competition for attention commercial rationalisation 23
Summary: we take more risk we burn more energy but we have more impact we make more mistakes and have more problems but also more solutions and more fun ; we create . 24
http://www.usethesource.io Rascal http://www.rascal-mpl.org Tools € Research Industry 25
Recommend
More recommend
