| 2010 |
13 | | Manfred Broy,
David Cruz,
Martin Deubler,
Kim Lauenroth,
Klaus Pohl,
Ernst Sikora:
Erster Workshop zur Zukunft der Entwicklung softwareintensiver, eingebetteter Systeme (ENVISION2020).
Software Engineering 2010: 240 |
| 2009 |
12 | | Kim Lauenroth,
Klaus Pohl,
Simon Toehning:
Model Checking of Domain Artifacts in Product Line Engineering.
ASE 2009: 269-280 |
| 2008 |
11 | | Kim Lauenroth,
Klaus Pohl:
Dynamic Consistency Checking of Domain Requirements in Product Line Engineering.
RE 2008: 193-202 |
10 | | Steffen Lohmann,
Philipp Heim,
Kim Lauenroth:
Web-based Stakeholder Participation in Distributed Requirements Elicitation.
RE 2008: 323-324 |
9 | | Kim Lauenroth,
Klaus Pohl:
Ein Rahmenwerk zur Konsistenzprüfung von Domänen-anforderungsspezifikationen in der Produktlinienentwicklung.
Software Engineering 2008: 169-182 |
| 2007 |
8 | | Kim Lauenroth,
Klaus Pohl:
Towards automated consistency checks of product line requirements specifications.
ASE 2007: 373-376 |
7 | | Thomas Riechert,
Kim Lauenroth,
Jens Lehmann:
SWORE - SoftWiki Ontology for Requirements Engineering.
CSSW 2007: 111-118 |
6 | | Mariele Hagen,
Berit Jungmann,
Kim Lauenroth:
A Processmodel for Wiki-Based Requirements Engineering Supported by Semantic Web Technologies.
CSSW 2007: 119-138 |
5 | | Kim Lauenroth,
Ernst Sikora,
Klaus Pohl:
Positive Effekte von Szenarien und Features in einem Softwarepraktikum.
SEUH 2007: 27-40 |
| 2006 |
4 | | Stan Bühne,
Günter Halmans,
Kim Lauenroth,
Klaus Pohl:
Scenario-Based Application Requirements Engineering.
Software Product Lines 2006: 161-194 |
| 2005 |
3 | | Andreas Metzger,
Stan Bühne,
Kim Lauenroth,
Klaus Pohl:
Considering Feature Interactions in Product Lines: Towards the Automatic Derivation of Dependencies between Product Variants.
FIW 2005: 198-216 |
2 | | Stan Bühne,
Kim Lauenroth,
Klaus Pohl:
Modelling Requirements Variability across Product Lines.
RE 2005: 41-52 |
| 2004 |
1 | | Stan Bühne,
Kim Lauenroth,
Klaus Pohl:
Anforderungsmanagement in der Automobilindustrie: Variabilität in Zielen, Szenarien und Anforderungen.
GI Jahrestagung (2) 2004: 23-27 |