Demonstration venue · read-only. Every page can be browsed; the buttons that would change it are switched off. Create an account to run TaxoReview on your own data. A simulation from public publication records: the people listed were not invited and did not agree to review.
? Tutorial for this page

Christian Pichler

dblp:20/7450 · DBLP profile ↗
← Back
5ranked-venue papers
2as first author
0since 2021 · last 2012
0000-0002-3535-818XORCID · corroborated

Domains — the database's venue-derived domains; a paper can count in several

Software engineering, systems software and programming languages · 3 · 1 first-authorSystems, architecture and hardware · 1Databases, data management, data science and information retrieval · 1

Expertise — from the expertise taxonomy: the topics of the expert's papers under the CCF categories. A weight counts papers with recency: 1 for a paper about the topic, 0.3 when the topic is its context, halved every five years.

Software engineering, system software, and programming languages
1 paper
Requirements engineering and software design · 87% Software maintenance and evolution · 13%
Computer architecture, parallel and distributed computing, and storage systems
1 paper
Electronic design automation · 100%
Databases, data mining, and information retrieval
1 paper
Data models and query languages · 100%

Topics — the 5 heaviest of 6, each with the papers that count most for it

TopicWeightPapersLastEvidence papers
Requirements engineering and software design
model-driven engineering
0.112010
A framework for handling variants of software models · ICSE (2) 2010
Requirements engineering and software design › model-driven engineering › model management
model versioning
0.112010
A framework for handling variants of software models · ICSE (2) 2010
Electronic design automation › hardware verification and test › hardware verification › assertion-based verification
assertion failure debugging
0.112009
Untwist your brain: efficient debugging and diagnosis of complex assertions · DAC 2009
Electronic design automation › hardware verification and test
hardware verification
0.112009
Untwist your brain: efficient debugging and diagnosis of complex assertions · DAC 2009
Software maintenance and evolution › software configuration management
version control
0.012010
A framework for handling variants of software models · ICSE (2) 2010

Methods — techniques the papers use, named apart from their topics

software configuration management · 0.2reference modeling · 0.2root cause analysis · 0.1automated debugging · 0.1
YearPublicationVenuePosition
2012 Mining Inter-organizational Business Process Models from EDI Messages: A Case Study from the Automotive Sector
Robert Engel, Wil M. P. van der Aalst, Marco Zapletal, Christian Pichler, Hannes Werthner
CAiSE4
2011 Registry support for core component-based business document models
Philipp Liegl, Christian Huemer, Christian Pichler
Serv. Oriented Comput. Appl.3
2010 A framework for handling variants of software models
abstract
The United Nations Centre for Trade Facilitation and Electronic Business (UN/CEFACT) envisions seamless information exchange between business partners in electronic commerce. Therefore, UN/CEFACT provides the UML Profile for Core Components for the definition of document models based on UML class diagrams. Having used this approach for three years in practice, it became evident that managing document model versions is a prerequisite for successfully utilizing Core Components. While managing software versions in the area of Software Engineering is well understood and successfully applied in industrial projects, the direct application of the same techniques for versioning models is conditionally appropriate. In this research abstract we propose to combine techniques from traditional Software Configuration Management with the concepts of reference modeling, where similar problems are addressed in a different context.
Christian Pichler
ICSE (2)1
2010 Size Matters!? Measuring the Complexity of XML Schema Mapping Models
abstract
Exchanging structured business documents is inevitable for successful collaboration in electronic commerce. A prerequisite, for fostering the interoperability between business partners utilizing different business document standards, is a mapping between different standards. However, the effort involved in creating those mappings is hard to estimate. For example, the complexity of standardized formats is one crucial aspect affecting the effort of the mapping process. Therefore, a notion of complexity is desirable for both, manual as well as automatic mapping processes. For this reason we develop an initial set of metrics, based on well established metrics for XML Schema, allowing to analyze the complexity of business document standards. Having such metrics at hand allows estimating the complexity and hence the mapping effort of a business document standard, prior to the actual mapping process. We demonstrate the complexity metrics on three different business document standards from the electronic commerce domain.
Christian Pichler, Michael Strommer, Christian Huemer
SERVICES1
2009 Untwist your brain: efficient debugging and diagnosis of complex assertions
abstract
Assertions are recognized in the industry to be a major improvement in functional RTL verification flows. Today's standard assertion languages, such as SVA [1] and PSL [2], are very expressive, capable of describing sophisticated temporal design behavior at different abstraction levels. Nevertheless, most assertion users stick to writing simple assertions because of the intricacy and effort required to debug complex assertions -- one of the major bottlenecks in assertion based verification. We present debugging and diagnosis techniques that automatically identify those parts of an assertion that cause the assertion to fail for a given design and that provide additional automation to efficiently identify the root cause of the failure. These techniques enable major effort savings when working with complex assertions, allowing engineers to use the full capabilities of assertion languages. This enables further productivity and quality improvements in functional verification by lifting mainstream assertion usage to higher abstraction levels such as efficient capture and verification of high-level design features, operations, and transactions. Advanced debugging automation is key for this progress - solving a problem that many designers and verification engineers face in their daily work.
Michael Siegel, Adriana Maggiore, Christian Pichler
DAC3