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

Peter Knauber

dblp:86/934 · DBLP profile ↗
← Back
9ranked-venue papers
6as first author
0since 2021 · last 2008
—ORCID · none

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

Software engineering, systems software and programming languages · 9 · 6 first-authorArtificial intelligence and machine learning · 3 · 2 first-authorApplied, interdisciplinary, general and emerging computing · 3 · 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
5 papers
Requirements engineering and software design · 79% Software maintenance and evolution · 18% Empirical software engineering · 3%

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

TopicWeightPapersLastEvidence papers
Requirements engineering and software design
software product lines
0.132002
Third ICSE workshop on software product lines: economics, architectures, and implications · ICSE 2002
Second ICSE Workshop on Software Product Lines: Economics, Architectures, and Applications · ICSE 2001
Software product lines: economics, architectures, and applications (workshop) · ICSE 2000
Requirements engineering and software design › software product lines
variability management
0.012003
ICSE Workshop on Software Variability Management · ICSE 2003
Software maintenance and evolution › software evolution
software product line evolution
0.042003
ICSE Workshop on Software Variability Management · ICSE 2003
Third ICSE workshop on software product lines: economics, architectures, and implications · ICSE 2002
Second ICSE Workshop on Software Product Lines: Economics, Architectures, and Applications · ICSE 2001
Requirements engineering and software design
model-driven engineering
0.012000
Introducng a software modeling concept in a medium-sized company · ICSE 2000
Requirements engineering and software design
software architecture
0.012000
Introducng a software modeling concept in a medium-sized company · ICSE 2000
Requirements engineering and software design
software modeling
0.012000
Introducng a software modeling concept in a medium-sized company · ICSE 2000
Software maintenance and evolution
software process improvement
0.012000
Introducng a software modeling concept in a medium-sized company · ICSE 2000
Empirical software engineering
technology transfer
0.012000
Introducng a software modeling concept in a medium-sized company · ICSE 2000

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

quality improvement paradigm · 0.0
YearPublicationVenuePosition
2008 The 5th Software Product Lines Testing Workshop (SPLiT 2008)
abstract
Software product line engineering (SPLE) has shown to be a very successful paradigm for developing a diversity of similar software products at low cost, in short time, and with high quality.
Peter Knauber, Andreas Metzger, John D. McGregor
SPLC1
2006 Software Product Line Testing - SPLiT
abstract
Product Line Engineering (PLE) has become a major topic in industrial software development and many organizations have started to consider PLE as state-of-practice. In PLE we aim to exploit the commonalities and variabilities of a product line for a more efficient way of developing and maintaining the product-line members. Systematic exploitation usually results in a product line (PL) infrastructure containing variation points that support the family members’ variabilities.
Peter Knauber, Charles W. Krueger, Tim Trew
SPLC1
2003 ICSE Workshop on Software Variability Management
abstract
During recent years, the amount of variability that has to be supported by a software artifact is growing considerably and its management is developing as a main challenge during development, usage, and evolution of software artifacts. Successful management of variability in software artifacts leads to better customizable software products that are in turn likely to result in higher market success. The aim of this workshop is to study software variability management both from a 'problems' and from a 'solutions' perspective by bringing together people from industrial practice and from applied research in academia to present and discuss their respective experience. Issues to be addressed include, but are not limited to, technological, process, and organizational aspects as well as notation, assessment, design, and evolution aspects.
Peter Knauber, Jan Bosch
ICSE1
2002 Third ICSE workshop on software product lines: economics, architectures, and implications
abstract
No abstract available.
Peter Knauber, Giancarlo Succi
ICSE1
2002 Adopting and Institutionalizing a Product Line Culture
Günter Böckle, Jesús Bermejo Muñoz, Peter Knauber, Charles W. Krueger, Julio César Sampaio do Prado Leite, Frank van der Linden 0001, Linda M. Northrop, Michael E. Stark, David M. Weiss 0001
SPLC3
2001 Second ICSE Workshop on Software Product Lines: Economics, Architectures, and Applications
abstract
S.753-754 : Ill.
Peter Knauber, Giancarlo Succi
ICSE1
2000 Software product lines: economics, architectures, and applications (workshop)
abstract
No abstract available.
Peter Knauber, Giancarlo Succi
ICSE1
2000 Introducng a software modeling concept in a medium-sized company
abstract
Describes, using the Quality Improvement Paradigm (QIP), how an improvement project aimed at improving the modeling and documentation approach of a medium-sized company (Markant Su/spl uml/dwest Software und Dienstleistungs GmbH) was conducted. We discuss the new modeling approach, which may serve for other companies as a template for deriving their own adapted approach. Further, we illustrate our insights from this project that can help in future technology transfer projects. A major characteristic of this project was that it was embedded in a long-term consulting relationship.
Klaus Schmid, Ulrike Becker-Kornstaedt, Peter Knauber, Florian Bernauer
ICSE3
2000 Issues and Models in Software Product Lines
abstract
Software product lines are one of the most promising fields in software engineering. They aim at the synergistic construction of software products. A successful introduction of software product lines requires three essential ingredients: a business analysis of the overall advantages that can come from product lines, the definition of a systematic process for product lines development, and the definition of general models, in a standard format, which can guide the development process.
Jorge L. Díaz-Herrera, Peter Knauber, Giancarlo Succi
Int. J. Softw. Eng. Knowl. Eng.2