| 2013 | ||
|---|---|---|
| j16 | Elke Bouillon, Baris Güldali, Andrea Herrmann, Thorsten Keuler, Daniel Moldt, Matthias Riebisch: Leichtgewichtige Traceability im agilen Entwicklungsprozess am Beispiel von Scrum. Softwaretechnik-Trends 33(1) (2013) | |
| j15 | Andrea Herrmann, Alexander-Marc Merten: Best Practices für den Umgang mit Macht und Politik im Requirements Engineering. Softwaretechnik-Trends 33(1) (2013) | |
| j14 | Eric Knauss, Andrea Herrmann, Ralf Fahney, Thomas Gartung, Jörg Glunde, Anne Hoffmann, Uwe Valentini, Rüdiger Weißbach: Requirements Engineering und Projektmanagement: Erfahrungen mit der Suche nach Best Practices. Softwaretechnik-Trends 33(1) (2013) | |
| c17 | Maya Daneva, Luigi Buglione, Andrea Herrmann: Software Architects' Experiences of Quality Requirements: What We Know and What We Do Not Know? REFSQ 2013: 1-17 | |
| c16 | Andrea Herrmann: Requirements Engineering in Practice: There Is No Requirements Engineer Position. REFSQ 2013: 347-361 | |
| 2012 | ||
| j13 | Andrea Herrmann, Maya Daneva, Jörg Dörr, Kurt Schneider: 2nd international workshop on creativity in requirements engineering: CreaRE 2012. ACM SIGSOFT Software Engineering Notes 37(4): 30-31 (2012) | |
| j12 | ||
| j11 | ||
| 2011 | ||
| c15 | Andrea Herrmann, Ayse Morali, Sandro Etalle, Roel Wieringa: Risk and Business Goal Based Security Requirement and Countermeasure Prioritization. BIR Workshops 2011: 64-76 | |
| c14 | Maya Daneva, Andrea Herrmann: EPIC 2011: Third Workshop on Leveraging Empirical Research Results for Software Business Success. ICSOB 2011: 187 | |
| c13 | Zornitza Bakalova, Maya Daneva, Andrea Herrmann, Roel Wieringa: Agile Requirements Prioritization: What Happens in Practice and What Is Described in Literature. REFSQ 2011: 181-195 | |
| 2010 | ||
| c12 | Zornitza Racheva, Maya Daneva, Andrea Herrmann: A conceptual model of client-driven agile requirements prioritization: results of a case study. ESEM 2010 | |
| c11 | Zornitza Racheva, Maya Daneva, Andrea Herrmann, Roel Wieringa: A conceptual model and process for client-driven agile requirements prioritization. RCIS 2010: 287-298 | |
| c10 | Zornitza Racheva, Maya Daneva, Klaas Sikkel, Andrea Herrmann, Roel Wieringa: Do We Know Enough about Requirements Prioritization in Agile Projects: Insights from a Case Study. RE 2010: 147-156 | |
| 2009 | ||
| j10 | Andrea Herrmann, Barbara Paech: Practical challenges of requirements prioritization based on risk estimation. Empirical Software Engineering 14(6): 644-684 (2009) | |
| j9 | Karl-Heinz Dorn, Ralf Fahney, Andrea Herrmann, Rüdiger Weißbach: Bericht des GI-Arbeitskreises "Requirements Engineering und Projektmanagement" über das Jahr 2008. Softwaretechnik-Trends 29(1) (2009) | |
| c9 | Andrea Herrmann, Daniel Weiß: Alignment of Software Specifications with Quality- and Business Goals in the SIKOSA Method. PRIMIUM 2009: 27-42 | |
| c8 | Andrea Herrmann, Armin Wallnöfer, Barbara Paech: Specifying Changes Only - A Case Study on Delta Requirements. REFSQ 2009: 45-58 | |
| 2008 | ||
| j8 | Andrea Herrmann, Barbara Paech: MOQARE: misuse-oriented quality requirements engineering. Requir. Eng. 13(1): 73-86 (2008) | |
| j7 | Ralf Fahney, Andrea Herrmann, Rüdiger Weißbach: Bericht des AK Requirements Engineering und Projektmanagement über das Jahr 2007. Softwaretechnik-Trends 28(1) (2008) | |
| j6 | Andrea Herrmann, Timea Illes-Seifert, Michael Geisser, Tobias Hildenbrand: Aktuelle Herausforderungen in verteilten RE-Prozessen. Softwaretechnik-Trends 28(1) (2008) | |
| c7 | Andrea Herrmann, Daniel Weiß: Alignment of Software Specifications with Quality- and Business Goals in the SIKOSA Methodology. PRIMIUM 2008 | |
| c6 | Andrea Herrmann, Maya Daneva: Requirements Prioritization Based on Benefit and Cost Prediction: An Agenda for Future Research. RE 2008: 125-134 | |
| c5 | Andrea Herrmann: Qualitätsrisiken und deren Abhängigkeiten. Software Engineering (Workshops) 2008: 457-463 | |
| c4 | Maya Daneva, Andrea Herrmann: Requirements Prioritization Based on Benefit and Cost Prediction: A Method Classification Framework. EUROMICRO-SEAA 2008: 240-247 | |
| 2007 | ||
| j5 | Daniel Weiß, Jörn Kaack, Stefan Kirn, Maike Gilliot, Lutz Lowis, Günter Müller, Andrea Herrmann, Carsten Binnig, Timea Illes, Barbara Paech, Donald Kossmann: Die SIKOSA-Methodik. Wirtschaftsinformatik 49(3): 188-198 (2007) | |
| c3 | Vandana Kabilan, Paul Johannesson, Sini Ruohomaa, Pirjo Moen, Andrea Herrmann, Rose-Marie Åhlfeldt, Hans Weigand: Introducing the Common Non-Functional Ontology. IESA 2007: 633-645 | |
| c2 | Andrea Herrmann, Daniel Kerkow, Jörg Dörr: Exploring the Characteristics of NFR Methods - A Dialogue About Two Approaches. REFSQ 2007: 320-334 | |
| c1 | Ralf Fahney, Andrea Herrmann, Rüdiger Weißbach: WH5: Wie viel Requirements Engineering steckt im Software Engineering? Software Engineering 2007: 303-304 | |
| 2006 | ||
| j4 | Andrea Herrmann, Barbara Paech, Damian Plaza: Icrad: an Integrated Process for the Solution of Requirements Conflicts and Architectural Design. International Journal of Software Engineering and Knowledge Engineering 16(6): 917-950 (2006) | |
| j3 | Andrea Herrmann, Barbara Paech: MOQARE "Misuse-oriented Quality Requirements Engineering" - Über den Nutzen von Bedrohungsszenarien beim RE von Qualitätsanforderungen. Softwaretechnik-Trends 26(1) (2006) | |
| j2 | Andrea Herrmann, Barbara Paech: Lernen aus dokumentierten Architektur-Entscheidungen. Softwaretechnik-Trends 26(4) (2006) | |
| 2004 | ||
| j1 | Andrea Herrmann: Kommunikation in IT-Projekten und heimliche Saboteure. Softwaretechnik-Trends 24(4) (2004) | |
Colors in the list of coauthors
Last update Thu May 23 23:17:14 2013 CET by the DBLP Team —
Data released under the ODC-BY 1.0 license — See also our legal information page