Team Member

Dr. Christian Pfaller


… is consultant for continuous quality control
and quality improvement processes.

  • +49 space::176 space::10090694
  • pfaller@invalid::cqse.eu
  • @ChPfaller

Blog Posts


In this blog-post I’d like to give a few insights on how we do ABAP programming at CQSE, which might be quite different than in most other ABAP development teams.

Read more...


During the last years, we have deeply integrated analyses for ABAP in Teamscale (and formerly in ConQAT). These analyses are used by SAP customers to keep the quality of their custom code high. However, since SAP is introducing many new programming technologies, more and more SAP users are confronted with new languages besides ABAP. One of these is SAP HANA SQLScript, which is used to develop high-performance stored procedures for the SAP HANA in-memory database. Unfortunately, SAP did not provide any static code analysis for SQLScript (in contrast to SAP Code Inspector for ABAP). Moreover, there are no precise guidelines how to develop good SQLScript code so far. In this post I’ll present our initial thoughts on assessing the code quality of SQLScript.

Read more...


Analysis tools for your source code, like Teamscale and others, produce a list of findings—or issues—identified in your code. When you go over the list of findings, you will probably encounter some individual findings you will not fully agree with. These issues might be not valid, not a problem or not worth to fix for you. For these cases, professional quality analysis tools offer blacklisting features. Blacklisting allows you to hide individual findings. The question »What should be put on the blacklist?« will be answered quite differently, depending who you ask. Developers may tend to »everything I cannot fix should be on the blacklist«. A QA manager might answer something like »only false positives may be put on the blacklist«.

Read more...


From the code audits and quality control of ABAP projects we do, we observe again and again that ABAP code tends to contain a relative high rate of duplication within the custom code. The data of our benchmark confirm this impression: From the ten projects with the highest rate of duplicated code, six projects are written in ABAP (but only 16% of all projects in the benchmark are ABAP projects). In this post I will discuss what are the reasons for the tendency to clones in ABAP.

Read more...


Nils summarized the benefits of short methods in his post from November: These are easier to comprehend, do better document the code (by the method name), are better to reuse and simplify testing as well as debugging or profiling. As the examples were in Java, one may intend that this will work for modern languages—but not in general, and maybe not for a language like ABAP. In this post I’ll focus if short procedures (e.g., methods, function modules, or form routines) have the same relevance for ABAP or if longer procedures are to legitimate or can not be avoided.

Read more...


Talks


Christian Pfaller:

Combining Structural and Functional Test Case Generation.

Talk at Software Engineering 2008, 2008.

Christian Pfaller:

Multi-Dimensional Measures for Test Case Quality.

Talk at the First International Conference on Software Testing Verification and Validation (ICST’08), 2008.

Christian Pfaller:

Requirements-based test case specification by using information from model construction.

Talk at the International Workshop on Automation of Software Test (AST’08), 2008.

Christian Pfaller:

On the integration of design and test: a model-based approach for embedded systems.

Talk at the International Workshop on Automation of Software Test (AST’06), 2006.

Publications


Bernhard Schätz, Christian Pfaller:

Integrating Component Tests to System Tests.

Electronic Notes in Theoretical Computer Science, Vol. 260, 2010.

Bernhard Schätz, Christian Pfaller:

Test Case Integration: From Components to Systems.

Proceedings of the Dagstuhl-Workshop MBEES: Modellbasierte Entwicklung eingebetteter Systeme, 2010.

Martin Feilkas, Andreas Fleischmann, Florian Hölzl, Christian Pfaller, Kathrin Scheidemann, Maria Spichkova, David Trachtenherz:

A Top-Down Methodology for the Development of Automotive Software.

Report TUM-I0902. Technische Universität München, 2009.

Christian Pfaller, Markus Pister:

Combining Structural and Functional Test Case Generation.

Software Engineering 2008, 2008.

Orna Grumberg, Tobias Nipkow, Christian Pfaller:

Formal Logical Methods for System Security and Correctness.

Unsupported type: book, 2008.

Christian Pfaller, Stefan Wagner, Jörg Gericke, Matthias Wiemann:

Multi-Dimensional Measures for Test Case Quality.

Proceedings of the First International Conference on Software Testing Verification and Validation (ICST’08), 2008.

Christian Pfaller:

Requirements-based test case specification by using information from model construction.

Proceedings of the 3rd international workshop on Automation of software test (AST’08), 2008.

Sebastian Herold, Holger Klus, Yannick Welsch, Constanze Deiters, Andreas Rausch, Ralf Reussner, Klaus Krogmann, Heiko Koziolek, Raffaela Mirandola, Benjamin Hummel, Michael Meisinger, Christian Pfaller:

CoCoME - The Common Component Modeling Example.

The Common Component Modeling Example: Comparing Software Component Models, 2007.

Doris Wild, Andreas Fleischmann, Judith Hartmann, Christian Pfaller, Martin Rappl, Sabine Rittmann:

An Architecture-Centric Approach towards the Construction of Dependable Automotive Software.

Proceedings of the SAE 2006 World Congress, 2006.

Judith Hartmann, Andreas Fleischmann, Christian Pfaller, Martin Rappl, Sabine Rittmann, Doris Wild:

Feature Net - ein Ansatz zur Modellierung von automobilspezifischem Domänenwissen und Anforderungen.

GI Jahrestagung, 2006.

Christian Pfaller, Andreas Fleischmann, Judith Hartmann, Martin Rappl, Sabine Rittmann, Doris Wild:

On the integration of design and test: a model-based approach for embedded systems.

Proceedings of the 2006 international workshop on Automation of software test (AST’06), 2006.

Andreas Fleischmann, Judith Hartmann, Christian Pfaller, Martin Rappl, Sabine Rittmann, Doris Wild:

Concretization and Formalization of Requirements for Automotive Embedded Software Systems Development.

Proceedings of the Tenth Australian Workshop on Requiremements Engineering (AWRE’05), 2005.

Sabine Rittmann, Andreas Fleischmann, Judith Hartmann, Christian Pfaller, Martin Rappl, Doris Wild:

Integrating Service Specifications at Different Levels of Abstraction.

Proceedings of the IEEE International Workshop on Service-Oriented System Engineering (SOSE’05), 2005.