EMAIL: info@cqse.eu
PHONE: +49 89 9982717 51
PHONE: +49 89 9982717 51
… is consultant for software and systems engineering at CQSE. He studied computer science at Technische Universität München and received a PhD in software engineering from Technische Universität München. He holds two patents.
Since this post accompanies a talk in German, it is written in German, too.
Posted on 05/23/2018 by Dr. Dennis Pagano
Software is made of code. Well, yes, but not exclusively. Software engineering involves working with many other artifacts, such as models, architectures, tickets, build scripts, … and tests.
The goal of Teamscale is to provide meaningful and useful information about all aspects of software engineering. This is what we call »Software Intelligence«.
Consequently, in addition to providing profound insights into code quality, Teamscale performs many other sophisticated analyses, including architecture conformance analysis, analysis of issue tracker data, team evolution analysis, code ownership analysis, or data taint security analysis.
Moreover, Teamscale contains a bunch of analyses for
Since this post accompanies a talk in German, it is written in German, too.
Since this post accompanies a talk in German, it is written in German, too.
Posted on 11/09/2017 by Dr. Dennis Pagano
Am 25. Oktober 2017 fand zum zweiten Mal der CQSE Software Intelligence Workshop statt. Der Workshop lief dieses Jahr unter dem Motto »Software Intelligence bei…«.
Hauptbestandteil des Workshops waren Vorträge unserer Kunden mit Erfahrungsberichten, wie Software Intelligence bei ihnen jeweils konkret zum Einsatz kommt. Wir möchten uns bei den über 100 Teilnehmern herzlich für die wertvollen Diskussionsbeiträge bedanken.
Since this post accompanies a talk in German, it is written in German, too.
Since this post accompanies a talk in German, it is written in German, too.
Posted on 07/06/2017 by Dr. Dennis Pagano
Test Gap Analysis identifies changed code that was never tested before a release. Often, these code areas—the so called test gaps—are way more error prone than the rest of the system, which is why test managers typically try to test them most thoroughly.
We introduced Test Gap Analysis in many projects and used it on a wide range of different projects: from enterprise information systems to embedded software, from C/C++ to Java, C#, Python and even ABAP.
We thereby learnt a lot about factors that affect the complexity of the introduction. In this post, I want to highlight a few important factors, which I think are good to know before starting with Test Gap Analysis.
Since this post accompanies a talk in German, it is written in German, too.
Since this post accompanies a talk in German, it is written in German, too.
Since this post accompanies a talk in German, it is written in German, too.
Posted on 12/02/2016 by Dr. Dennis Pagano
Since this post relates to a paper in German, it is written in German, too.
Wir freuen uns, dass unser Paper zur Test-Gap-Analyse auf dem QS-Tag 2016 mit dem Best Paper Award ausgezeichnet wurde. Das Paper ist hier als Download verfügbar.
Posted on 11/21/2016 by Dr. Dennis Pagano
Am 27. Oktober 2016 fand der erste CQSE Software Intelligence Workshop statt. Hauptbestandteil des Workshops waren Vorträge mit Erfahrungsberichten zu Themen wie Test-Gap-Analyse und Quality Control durch unsere Kunden und Kollegen. Wir möchten uns bei den etwa 100 Teilnehmern herzlich für die wertvollen Diskussionsbeiträge bedanken.
Since this post accompanies a talk in German, it is written in German, too.
Posted on 09/30/2016 by Dr. Dennis Pagano
In a recent blog post, I wrote about Test Gap analysis—our analysis that identifies changed code that was never tested before a release. Often, these areas—the so called test gaps—are way more error prone than the rest of the system, which is why test managers try to test them most thoroughly.
Test Gap analysis provides test managers with an overview of remaining test gaps during the test phase. In practice, our code quality software Teamscale identifies changed but untested methods in the source code and displays the results on a treemap.
However, in many projects testers are non-coders or do not know the source code,
Posted on 06/20/2016 by Dr. Dennis Pagano
Since this post accompanies a talk in German, it is written in German, too.
Posted on 04/27/2016 by Dr. Dennis Pagano
Many companies employ sophisticated testing processes, but still bugs find their way into production. Often they hide among the subset of changes that were not tested. Actually, we found that untested changes are five times more error prone than the rest of the system.
To avoid that untested changes go into production, we came up with Test Gap analysis—an automated way of identifying changed code that was never executed before a release. We call these areas test gaps. Knowing them allows test managers to make a conscious decision, which test gaps have to be tested before shipping and which ones are of low risk and can be left untested.
A short while ago, we introduced Test Gap analysis into our code quality software Teamscale. In
Since this post accompanies a talk in German, it is written in German, too.
Haben wir alle wichtigen Features getestet? Ticket-Coverage live am Beispiel.
Talk at SWQD 2018, 2018.
Haben wir das Richtige getestet? Erfahrungen mit Test-Gap-Analyse und Ticket Coverage in der Praxis.
Keynote at Fachgruppe TAV 2018, 2018.
Beobachtest du noch oder verbesserst du schon? Kontinuierliche Qualitätsverbesserung in der Praxis.
Talk at Seacon 2017, 2017.
Don’t Look Back in Anger – Wie uns Historienanalyse dabei hilft, unsere Entwicklung zu verbessern.
Talk at Java Forum Stuttgart 2017, 2017.
Haben wir das Richtige getestet? Oh nein! Erfahrungen mit Test-Gap-Analyse in der Praxis.
Talk at OOP 2017, 2017.
Was kann man aus der Versionshistorie eins Softwareprojekts lernen?
Talk at JUG Hamburg 2017, 2017.
Was kann man aus der Versionshistorie eines Softwareprojekts lernen?
Talk at OOP 2016, 2016.
Was kann man aus der Versionshistorie eins Softwareprojekts lernen?
Talk at JUG Hamburg 2016, 2016.
User Involvement in Software Evolution Practice: A Case Study.
Talk at International Conference on Software Engineering (ICSE’13), 2013.
FastFix: Monitoring Control for Remote Software Maintenance.
Talk at International Conference on Software Engineering (ICSE’12), 2012.
How Do Developers Blog? An Exploratory Study.
Talk at Working Conference on Mining Software Repositories (MSR’11), 2011.
Engineering Document Applications - From UML Models to XML Schemas.
Talk at Balisage: The Markup Conference, 2009.
Erfahrungen mit Test-Gap-Analyse und Ticket Coverage in der Praxis.
OBJEKTspektrum, 2018.
Test Impact Analysis: Detecting Errors Early Despite Large, Long-Running Test Suites.
Whitepaper. CQSE GmbH, 2018.
Ticket Coverage: Putting Test Coverage into Context.
Proceedings of the 8th Workshop on Emerging Trends in Software Metrics (WETSoM’17), 2017.
Did We Test the Right Thing? Experiences with Test Gap Analysis in Practice.
Whitepaper. CQSE GmbH, 2016.
Haben wir das Richtige getestet? Erfahrungen mit Test-Gap-Analyse in der Praxis.
Whitepaper. CQSE GmbH, 2016.
Can Collaborative Tagging Improve User Feedback? A Case Study.
6th International Workshop on Social Software Engineering, 2014.
An Overview of Recommender Systems in Requirements Engineering.
Managing Requirements Knowledge. Springer Verlag, 2013.
Portneuf - A Framework for Continuous User Involvement.
Dissertation. Technische Universität München, 2013.
Towards Automated Detection of Mobile Usability Issues.
Proceedings of the First European Workshop on Mobile Engineering, 2013.
User Feedback in the AppStore: An Empirical Study.
Proceedings of the 21st International Requirements Engineering Conference (RE’13), 2013.
User Involvement in Software Evolution Practice: A Case Study.
Proceedings of the 35th International Conference on Software Engineering (ICSE’13), 2013.
FastFix: Monitoring Control for Remote Software Maintenance.
Proceedings of the 34th International Conference of Software Engineering (ICSE’12), 2012.
FastFix: Monitoring Control for Remote Software Maintenance.
Proceedings of the 34th International Conference on Software Engineering (ICSE’12), 2012.
Group Decision Support for Requirements Negotiation.
Advances in User Modeling - Lecture Notes in Computer Science Volume 7138. Springer Berlin Heidelberg, 2012.
How Do Open Source Communities Blog?
International Journal on Empirical Software Engineering, 2012.
How Do Developers Blog? An Exploratory Study.
Proceedings of the 8th Working Conference on Mining Software Repositories (MSR’11), 2011.
On the Socialness of Software.
Proceedings of the International Conference on Social Computing and its Applications, 2011.
Towards Systematic Analysis of Continuous User Input.
Proceedings of the 4th International Workshop on Social Software Engineering, 2011.
Reverse Modeling for Domain-Driven Engineering of Publishing Technology.
Proceedings of Balisage: The Markup Conference, 2010.
Engineering Document Applications - From UML Models to XML Schemas.
Proceedings of Balisage: The Markup Conference, 2009.