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

Andre Engberts

dblp:89/1902 · DBLP profile ↗
← Back
3ranked-venue papers
1as first author
0since 2021 · last 1994
—ORCID · none

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

Software engineering, systems software and programming languages · 3 · 1 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 · 67% Compilers and program optimization · 33%

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

TopicWeightPapersLastEvidence papers
Software maintenance and evolution
program comprehension
0.011992
Program Concept Recognition and Transformation · IEEE Trans. Software Eng. 1992
Compilers and program optimization
program transformation
0.011992
Program Concept Recognition and Transformation · IEEE Trans. Software Eng. 1992
Software maintenance and evolution
software reengineering
0.011992
Program Concept Recognition and Transformation · IEEE Trans. Software Eng. 1992

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

automated concept recognition · 0.0abstract concept transformation · 0.0
YearPublicationVenuePosition
1994 Transferring Reengineering Technology to a Software Development and Maintenance Organization: An Experience Report
abstract
Technology transfer does not happen spontaneously after research results and prototypes have been demonstrated. Researchers need to get more actively involved in "pushing technology out of the door." This paper describes an experiment that we conducted in 1993 to facilitate technology transfer. There are two aspects of this experiment: the integration of a re-engineering process into an existing software development and maintenance organization; and the evaluation of a research prototype in a "real world" situation. The experiment resulted in recommendations on adaptation of the tool functionality and on a configuration for use by different teams within the target organization.>
M. Solinger, Andre Engberts, Jim Q. Ning
ICSM2
1992 Program Concept Recognition and Transformation
abstract
The automated recognition of abstract high-level conceptual information or concepts, which can greatly aid the understanding of programs and therefore support many software maintenance and reengineering activities, is considered. An approach to automated concept recognition and its application to maintenance-related program transformations are described. A unique characteristic of this approach is that transformations of code can be expressed as transformations of abstract concepts. This significantly elevates the level of transformation specifications.>
Wojtek Kozaczynski, Jim Q. Ning, Andre Engberts
IEEE Trans. Software Eng.3
1991 Concept recognition-based program transformation
abstract
An approach is described that applies a transformation paradigm to automate software maintenance activities. The approach to code-to-code (horizontal) transformation is based on a high-level understanding of the programming and application domain concepts represented by the code. A very unique characteristic of this approach is its use of concept recognition, the understanding and abstraction of high-level programming and application domain entities in programs, as the basis for transformations. A program transformation tool has been developed to support the migration of a large manufacturing control system written in COBOL.>
Andre Engberts, Wojtek Kozaczynski, Jim Q. Ning
ICSM1