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

Patrycja Wegrzynowicz

dblp:17/1690 · DBLP profile ↗
← Back
4ranked-venue papers
3as first author
0since 2021 · last 2013
—ORCID · none

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

Software engineering, systems software and programming languages · 4 · 3 first-authorArtificial intelligence and machine learning · 2 · 2 first-authorApplied, interdisciplinary, general and emerging computing · 2 · 2 first-author

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
Software maintenance and evolution · 61% Software testing · 30% Empirical software engineering · 9%

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

TopicWeightPapersLastEvidence papers
Software maintenance and evolution › reverse engineering
design pattern detection
0.112009
Towards a Comprehensive Test Suite for Detectors of Design Patterns · ASE 2009
Software maintenance and evolution
reverse engineering
0.112009
Towards a Comprehensive Test Suite for Detectors of Design Patterns · ASE 2009
Software testing › test process › test design
test suite design
0.112009
Towards a Comprehensive Test Suite for Detectors of Design Patterns · ASE 2009
Empirical software engineering
mining software repositories
0.012009
Towards a Comprehensive Test Suite for Detectors of Design Patterns · ASE 2009

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

test suite construction · 0.1
YearPublicationVenuePosition
2013 Performance Antipatterns of One to Many Association in Hibernate
Patrycja Wegrzynowicz
FedCSIS1
2013 Relaxing Queries to Detect Variants of Design Patterns
Patrycja Wegrzynowicz, Krzysztof Stencel
FedCSIS1
2009 Towards a Comprehensive Test Suite for Detectors of Design Patterns
abstract
Detection of design patterns is an important part of reverse engineering. Availability of patterns provides for a better understanding of code and also makes analysis more efficient in terms of time and cost. In recent years, we have observed a continual improvement in the field of automatic detection of design patterns in source code. Existing approaches can detect a fairly broad range of design patterns, targeting both structural and behavioral aspects of patterns. However, it is not straightforward to assess and compare these approaches. There is no common ground on which to evaluate the accuracy of the detection approaches, given the existence of variants and specific code constructs used to implement a design pattern. We propose a systematic approach to constructing a comprehensive test suite for detectors of design patterns. This approach is applied to construct a test suite covering the Singleton pattern. The test suite contains many implementation variants of these patterns, along with such code constructs as method forwarding, access modifiers, and long inheritance paths. Furthermore, we use this test suite to compare three detection tools and to identify their strengths and weaknesses.
Patrycja Wegrzynowicz, Krzysztof Stencel
ASE1
2008 Detection of Diverse Design Pattern Variants
abstract
We propose a method for automatic detection of occurrences of design patterns. We also describe its proof-of-concept implementation and the results of comparative experiments with other tools. The method presented here is able to detect many nonstandard implementation variants of design patterns, while its efficiency is comparable to other state-of-the-art detection tools. Moreover, the method is highly customizable because an analyst can introduce a new pattern retrieval query or modify an existing one and then repeat the detection using the results of earlier source code analysis stored in a relational database.
Krzysztof Stencel, Patrycja Wegrzynowicz
APSEC2