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

Ernst Ellmer

dblp:28/4530 · DBLP profile ↗
← Back
4ranked-venue papers
2as first author
0since 2021 · last 2003
—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-authorArtificial intelligence and machine learning · 1 · 1 first-authorDatabases, data management, data science and information retrieval · 1 · 1 first-authorApplied, interdisciplinary, general and emerging computing · 1 · 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
2 papers
Requirements engineering and software design · 53% Software maintenance and evolution · 42% Services computing and microservices · 5%
Computer architecture, parallel and distributed computing, and storage systems
1 paper
Distributed systems · 100%

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

TopicWeightPapersLastEvidence papers
Requirements engineering and software design › inconsistency management
consistency checking
0.012003
Flexible consistency checking · ACM Trans. Softw. Eng. Methodol. 2003
Software maintenance and evolution
incremental consistency checking
0.012003
Flexible consistency checking · ACM Trans. Softw. Eng. Methodol. 2003
Software maintenance and evolution
software evolution
0.012003
Flexible consistency checking · ACM Trans. Softw. Eng. Methodol. 2003
Requirements engineering and software design › software architecture
architectural style
0.012001
TIGRA - An Architectural Style for Enterprise Application Integration · ICSE 2001
Requirements engineering and software design
software architecture
0.012001
TIGRA - An Architectural Style for Enterprise Application Integration · ICSE 2001
Distributed systems
distributed software development
0.012003
Flexible consistency checking · ACM Trans. Softw. Eng. Methodol. 2003
Services computing and microservices
enterprise application integration
0.012001
TIGRA - An Architectural Style for Enterprise Application Integration · ICSE 2001

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

xlinkit · 0.1internet technologies · 0.1
YearPublicationVenuePosition
2003 Flexible consistency checking
abstract
The problem of managing the consistency of heterogeneous, distributed software engineering documents is central to the development of large and complex systems. We show how this problem can be addressed using xlinkit, a lightweight framework for consistency checking that leverages standard Internet technologies. xlinkit provides flexibility, strong diagnostics, and support for distribution and document heterogeneity. We use xlinkit in a comprehensive case study that demonstrates how design, implementation and deployment information of an Enterprise JavaBeans system can be checked for consistency, and rechecked incrementally when changes are made.
Christian Nentwich, Wolfgang Emmerich, Anthony Finkelstein, Ernst Ellmer
ACM Trans. Softw. Eng. Methodol.4
2001 TIGRA - An Architectural Style for Enterprise Application Integration
Wolfgang Emmerich, Ernst Ellmer, Henry Fieglein
ICSE2
1996 Process Model Reuse to Promote Organizational Learning in Software Development
abstract
Software development often suffers from well-known problems such as wrong schedules and cost estimations, low productivity, and low product quality. In order to overcome these problems we suggest adapting the concepts of "organizational memory" and "organizational learning" and we argue in favor of establishing a reuse culture of software process models. We introduce an approach based on the process definition/instantiation/enaction paradigm and on the reuse of explicit software process descriptions (process models). The key features of our approach are the division of process descriptions into a goal-oriented process definition document and a formal implementation-oriented process model on the one hand and the use of an artificial neural network, more precisely a self-organizing map, for classification and retrieval purposes on the other. We present an exposition of our approach and discuss the promising results of an experiment in structuring a software process library and retrieving reuse candidates for upcoming projects.
Ernst Ellmer, Dieter Merkl, Gerald Quirchmayr, A Min Tjoa
COMPSAC1
1996 Automatic Classification of Semantic Concepts in View Specifications
Ernst Ellmer, Christian Huemer, Dieter Merkl, Günther Pernul
DEXA1