 | 2012 |
| 24 |  | Eric Knauss,
Kurt Schneider:
Supporting Learning Organisations in Writing Better Requirements Documents Based on Heuristic Critiques.
REFSQ 2012: 165-171 |
| 23 |  | Harald Klein,
Eric Knauss,
Andreas Rausch:
Scaling Software Development Methods from Co-located to Distributed.
SWQD 2012: 71-83 |
| 22 |  | Kurt Schneider,
Eric Knauss,
Siv Hilde Houmb,
Shareeful Islam,
Jan Jürjens:
Enhancing security requirements engineering by organizational learning.
Requir. Eng. 17(1): 35-56 (2012) |
| 2011 |
| 21 |  | Anna Averbakh,
Eric Knauss,
Olga Liskin:
An experience base with rights management for global software engineering.
I-KNOW 2011: 10 |
| 20 |  | Constanze Deiters,
Christoph Herrmann,
Roland Hildebrandt,
Eric Knauss,
Marco Kuhrmann,
Andreas Rausch,
Bernhard Rumpe,
Kurt Schneider:
GloSE-Lab: Teaching Global Software Engineering.
ICGSE 2011: 156-160 |
| 19 |  | Kai Stapel,
Eric Knauss,
Kurt Schneider,
Nico Zazworka:
FLOW Mapping: Planning and Managing Communication in Distributed Teams.
ICGSE 2011: 190-199 |
| 18 |  | Olesia Brill,
Eric Knauss:
Structured and unobtrusive observation of anonymous users and their context for requirements elicitation.
RE 2011: 175-184 |
| 17 |  | Eric Knauss,
Siv Hilde Houmb,
Kurt Schneider,
Shareeful Islam,
Jan Jürjens:
Supporting Requirements Engineers in Recognising Security Issues.
REFSQ 2011: 4-18 |
| 2010 |
| 16 |  | Nico Zazworka,
Kai Stapel,
Eric Knauss,
Forrest Shull,
Victor R. Basili,
Kurt Schneider:
Are developers complying with the process: an XP study.
ESEM 2010 |
| 15 |  | Sebastian Meyer,
Eric Knauss,
Kurt Schneider:
Distributing a Lean Organization: Maintaining Communication While Staying Agile.
LESS 2010: 99-103 |
| 14 |  | Olesia Brill,
Kurt Schneider,
Eric Knauss:
Videos vs. Use Cases: Can Videos Capture More Requirements under Time Pressure?
REFSQ 2010: 30-44 |
| 13 |  | Kai Stapel,
Eric Knauss,
Kurt Schneider,
Matthias Becker:
Towards Understanding Communication Structure in Pair Programming.
XP 2010: 117-131 |
| 12 |  | Siv Hilde Houmb,
Shareeful Islam,
Eric Knauss,
Jan Jürjens,
Kurt Schneider:
Eliciting security requirements and tracing them to design: an integration of Common Criteria, heuristics, and UMLsec.
Requir. Eng. 15(1): 63-93 (2010) |
| 2009 |
| 11 |  | Leif Singer,
Eric Knauss,
Kurt Schneider:
Requirements Engineering in IT-Ökosystemen mit Hilfe von Archetypen.
GI Jahrestagung 2009: 3865-3874 |
| 10 |  | Christian Bartelt,
Manfred Broy,
Christoph Herrmann,
Eric Knauss,
Marco Kuhrmann,
Andreas Rausch,
Bernhard Rumpe,
Kurt Schneider:
Orchestration of Global Software Engineering Projects - Position Paper.
ICGSE 2009: 332-337 |
| 9 |  | Eric Knauss,
Daniel Lübke,
Sebastian Meyer:
Feedback-driven requirements engineering: The Heuristic Requirements Assistant.
ICSE 2009: 587-590 |
| 8 |  | Eric Knauss,
Christian El Boustani,
Thomas Flohr:
Investigating the Impact of Software Requirements Specification Quality on Project Success.
PROFES 2009: 28-42 |
| 7 |  | Eric Knauss,
Kurt Schneider,
Kai Stapel:
Learning to Write Better Requirements through Heuristic Critiques.
RE 2009: 387-388 |
| 6 |  | Matthias Weidlich,
Alexander Großkopf,
Daniel Lübke,
Kurt Schneider,
Eric Knauss,
Leif Singer:
Verzahnung von Requirements Engineering und Geschäftsprozessdesign.
Software Engineering (Workshops) 2009: 229-236 |
| 2008 |
| 5 |  | Eric Knauss,
Daniel Lübke:
Using the Friction between Business Processes and Use Cases in SOA Requirements.
COMPSAC 2008: 601-606 |
| 4 |  | Julia Pilarski,
Eric Knauss:
Transformationen zwischen UML-Use-Case-Diagrammen und tabellarischen Darstellungen.
DSML 2008: 45-58 |
| 3 |  | Kai Stapel,
Eric Knauss,
Christian Allmann:
Lightweight Process Documentation: Just Enough Structure in Automotive Pre-development.
EuroSPI 2008: 142-151 |
| 2 |  | Kai Stapel,
Daniel Lübke,
Eric Knauss:
Best practices in extreme programming course design.
ICSE 2008: 769-776 |
| 1 |  | Eric Knauss,
Christian El Boustani:
Assessing the Quality of Software Requirements Specifications.
RE 2008: 341-342 |