Development metrics

Vision

Support the collaborating partners in increasing their market/technology leadership

Mission

Support the continuous improvement of product performance and organizational efficiency by rapid transfer of cutting edge research into novel ways of working

Stepping stones

  1. Quantitative reporting
  2. Infrastructure and language
  3. Efficiency measurement
  4. Pro-active measurements
  5. Product insight patterns
  6. Simulating new market/technology scenarios

Projects

  • Continuous Product and Organizational Performance
  • Quasar@Car - Quantifying meta-model changes
  • VISEE - Verification and Validation of ISO 26262 requirements at the complete EE system level
  • Longitudinal Measurement of Agility and Group Development
  • Size and Quality between Software Development Approaches
  • RAWFP - Resource Aware Functional Programming

RSS Metrics blog

  • Classifying SE research – an article review October 13, 2020
    https://link.springer.com/article/10.1007/s10664-020-09858-z?utm_source=toc&utm_medium=email&utm_campaign=toc_10664_25_5&utm_content=etoc_springer_20200904 Initially, I did not really think that I would put this article on the blog. I actually thought about using it in my writing advice page. However, I’ve read it and then I realized that it’s actually more suitable for this blog. This article shows how we can classify software engineering research. It has […]
    metrics
  • Action research in open source – a nice article October 6, 2020
    https://link.springer.com/article/10.1007/s10664-020-09849-0?utm_source=toc&utm_medium=email&utm_campaign=toc_10664_25_5&utm_content=etoc_springer_20200904 I’ve been looking out for good examples of articles about action research in software engineering for a while. There is a lot of those coming from the participatory design community and ethnography in software engineering. This paper is an example of how one can conduct action research together with an open source community. It […]
    metrics
  • Technical debt from the perspective of practitioners – article review September 29, 2020
    https://link.springer.com/article/10.1007/s10664-020-09832-9?utm_source=toc&utm_medium=email&utm_campaign=toc_10664_25_5&utm_content=etoc_springer_20200904 Technical debt is a great metaphor in software engineering. It provides software engineers with the toolkit to communicate how bad design can affect the product in a long run, and how much it can cost to fix these problems. The metaphor has been implemented in many static analysis tools like SonarQube. Despite its power […]
    metrics
  • Being wrong – book review September 21, 2020
    I’ve picked up this book to continue my reading into our ability to reason and understand the reality around us. I’ve described this journey in my previous posts, e.g. https://metrics.blogg.gu.se/?p=438 This book goes beyond the trust and explores how we can be wrong and how, sometimes, we should actually be wrong. It describes different models […]
    metrics
  • Finding lines of code that require review – my 100 blog post! September 15, 2020
    Working with continuous integration is an exciting new filed. You get your code into the main branch directly. Well, that’s what the theory says. What you really get is feedback directly, at least the feedback from the automated checks for technical debt, testing and similar. What you do not get quickly is the review of […]
    metrics

Theme 3, Leader: Miroslaw Staron

Miroslaw Staron
Professor, Software Engineering division, Department of Computer Science and Engineering, University of Gothenburg

More information

Miroslaw.Staron@cse.gu.se

Phone: +46 31 772 10 81